Panoramas in Missions?

[yarrr]

Just updated to latest firmware, and panoramas are no longer an option for missions.

I have several "Live Recorded" missions that included panoramas at set locations. This action has disappeared from the waypoint, it is not possible to add via the map, live recording, or as an 'action' when editing the mission.

Can anyone suggest a workaround?

 

[akdrone]

Couldn't you set to to hold shoot the pano and continue? Something like that?

 

[yarrr]

Couldn't you set to to hold shoot the pano and continue? Something like that?

Yeah, that would be a rudimentary solution. Probably the best we'll get.

 

[yarrr]

I dug into the exported KMZ of a previous mission, and I'm wondering if the panorama is dictated by this code- I really don't understand it.

<wpml:actionGroup>
<wpml:actionGroupId>9</wpml:actionGroupId>
<wpml:actionGroupStartIndex>19</wpml:actionGroupStartIndex>
<wpml:actionGroupEndIndex>19</wpml:actionGroupEndIndex>
<wpml:actionGroupMode>sequence</wpml:actionGroupMode>
<wpml:actionTrigger>
<wpml:actionTriggerType>reachPoint</wpml:actionTriggerType>
</wpml:actionTrigger>
<wpml:action>
<wpml:actionId>0</wpml:actionId>
<wpml:actionActuatorFunc>rotateYaw</wpml:actionActuatorFunc>
<wpml:actionActuatorFuncParam>
<wpml:aircraftHeading>-12</wpml:aircraftHeading>
<wpml:aircraftPathMode>counterClockwise</wpml:aircraftPathMode>
</wpml:actionActuatorFuncParam>
</wpml:action>
<wpml:action>
<wpml:actionId>1</wpml:actionId>
<wpml:actionActuatorFunc>gimbalRotate</wpml:actionActuatorFunc>
<wpml:actionActuatorFuncParam>
<wpml:gimbalRotateMode>absoluteAngle</wpml:gimbalRotateMode>
<wpml:gimbalPitchRotateEnable>1</wpml:gimbalPitchRotateEnable>
<wpml:gimbalPitchRotateAngle>-12.1000003814697</wpml:gimbalPitchRotateAngle>
<wpml:gimbalRollRotateEnable>1</wpml:gimbalRollRotateEnable>
<wpml:gimbalRollRotateAngle>0</wpml:gimbalRollRotateAngle>
<wpml:gimbalYawRotateEnable>1</wpml:gimbalYawRotateEnable>
<wpml:gimbalYawRotateAngle>-11.8759117126465</wpml:gimbalYawRotateAngle>
<wpml:gimbalRotateTimeEnable>0</wpml:gimbalRotateTimeEnable>
<wpml:gimbalRotateTime>10</wpml:gimbalRotateTime>
<wpmlayloadPositionIndex>0</wpmlayloadPositionIndex>
</wpml:actionActuatorFuncParam>
</wpml:action>

 

[DJ Wes]

<wpml:actionGroup>
<wpml:actionGroupId>9</wpml:actionGroupId>
<wpml:actionGroupStartIndex>19</wpml:actionGroupStartIndex>
<wpml:actionGroupEndIndex>19</wpml:actionGroupEndIndex>
<wpml:actionGroupMode>sequence</wpml:actionGroupMode>
<wpml:actionTrigger>
<wpml:actionTriggerType>reachPoint</wpml:actionTriggerType>
</wpml:actionTrigger>
<wpml:action>
<wpml:actionId>0</wpml:actionId>
<wpml:actionActuatorFunc>rotateYaw</wpml:actionActuatorFunc>
<wpml:actionActuatorFuncParam>
<wpml:aircraftHeading>-12</wpml:aircraftHeading>
<wpml:aircraftPathMode>counterClockwise</wpml:aircraftPathMode>
</wpml:actionActuatorFuncParam>
</wpml:action>
<wpml:action>
<wpml:actionId>1</wpml:actionId>
<wpml:actionActuatorFunc>gimbalRotate</wpml:actionActuatorFunc>
<wpml:actionActuatorFuncParam>
<wpml:gimbalRotateMode>absoluteAngle</wpml:gimbalRotateMode>
<wpml:gimbalPitchRotateEnable>1</wpml:gimbalPitchRotateEnable>
<wpml:gimbalPitchRotateAngle>-12.1000003814697</wpml:gimbalPitchRotateAngle>
<wpml:gimbalRollRotateEnable>1</wpml:gimbalRollRotateEnable>
<wpml:gimbalRollRotateAngle>0</wpml:gimbalRollRotateAngle>
<wpml:gimbalYawRotateEnable>1</wpml:gimbalYawRotateEnable>
<wpml:gimbalYawRotateAngle>-11.8759117126465</wpml:gimbalYawRotateAngle>
<wpml:gimbalRotateTimeEnable>0</wpml:gimbalRotateTimeEnable>
<wpml:gimbalRotateTime>10</wpml:gimbalRotateTime>
<wpmlayloadPositionIndex>0</wpmlayloadPositionIndex>
</wpml:actionActuatorFuncParam>
</wpml:action>

That WPML code defines an "Action Group" -- a group of actions to execute at a waypoint.

The start index is "19" which means it is exectuted at waypoint #20. The individual actions will occur in "sequence" instead of "parallel". The "reachPoint" value instructs the drone to begin execution when the drone reaches the waypoint.

Two actions are defined. The first is to change the aircraft heading to -12 degrees. The second is to change the gimbal pitch angle to -12 degrees and the gimbal yaw to -11.9 degrees.

 

[yarrr]

Thanks @DJ Wes , I've been looking at your Lichi to M3E tool.

Would you be able to share the WPML code for a Panorama?

 

[DJ Wes]

Would you be able to share the WPML code for a Panorama?

To see the WPML code, follow these steps:

1. Create a simple panorama mission using my "Litchi Mission to Panorama Mission" utility.
2. Convert that mission using my "Litchi Mission to DJI Fly Waypoints" utility.
3. Unzip the resulting KMZ file and then view the "waylines.wpml" file using a plain text editor.

 

[yarrr]

To see the WPML code, follow these steps:

1. Create a simple panorama mission using my "Litchi Mission to Panorama Mission" utility.
2. Convert that mission using my "Litchi Mission to DJI Fly Waypoints" utility.
3. Unzip the resulting KMZ file and then view the "waylines.wpml" file using a plain text editor.

Yeah, I tried that, but the resulting waylines.wpml file is empty. I can see in the csv "how" the pano works, but I was hoping to just cut/paste the sequence into some of my older .wpml files.

 

[DJ Wes]

Yeah, I tried that, but the resulting waylines.wpml file is empty.

Ahh yes. You have a Mavic 3 Enterprise. DJI is not consistent in how their various M3 drones interact with the data in the KMZ file.

For the Mavic 3 Enterprise, the waylines.wpml file will be empty. For this drone you must look in the template.kml file for the WPML instructions. If you were to create a KMZ file for the Mavic 3 (pro-sumer drones), the WPML data would be in the waylines.wpml file.

I was hoping to just cut/paste the sequence into some of my older .wpml files

A simple cut and paste is unlikely to work. "Action Groups" must reference specific waypoint "Index IDs". You can try copying and pasting but unless you understand the language and make the necessary tweaks, it is unlikely to work.

 

[yarrr]

Couldn't you set to to hold shoot the pano and continue? Something like that?

Tried this out on a job this week, and it is really annoying. Running the pano stops the waypoint mission. Then it needs to be 'resumed', which involves re-sending the mission, and depending on exactly when the mission was paused, flying to the breakpoint. Essentially unusable in my opinion. My work around will be to have the waypoints loaded on the map, and just fly to them manually. Will require manually noting and adjusting altitude. Luckily my projects generally only have 5 or 6 panos.