Can you display The heading and gimbal pitch angle on the waypoint tab as in version 1? I use “point of interest” mode most often in my mission planning. The tab tells me I’m in point of interest mode, but does not tell me the gimbal pitch at the waypoint. Seeing this number helps me frame the shot without needing to run a simulation. For example, with my drone I know that a gimbal pitch of -17 degrees will show me a sliver of the sky.
Dear Litchi Team,
We’ve implemented meters as a global setting, as it’s much more intuitive for our users. The formula to calculate the turning radius is too complex for most of them to understand easily - and during a survey flight, we don’t want to risk missing any areas.
For example, tight waypoint angles can lead to the drone taking shortcuts, which results in certain areas being skipped. Using meters directly helps us avoid this issue reliably.
Thanks again for your great work - and have a wonderful day!
Best regards,
Bruno
KMZ Export Feedback
- The “droneEnumValue” value written to the file is “65535”. The value DJI stores for all consumer drones is “68”. For DJI Enterprise drones, the value used must match that for the specific drone. Perhaps the value used for consumer drones is not as important. Is there a reason why “65535” is used instead of “68”?
- Every “Placemark” element of the waylines.wpml content is separated by a comma. I don’t know if this is a bug but I don’t think it should be necessary. Here is what is currently written to the waylines.wpml content:
</Placemark>,
<Placemark>
That comma could be removed. - The “actionGroupEndIndex” includes an extraneous space character at the end. I know this is nitpicking and doesn’t affect anything. It is just something that shows when closely examining and comparing output.
"<wpml:actionGroupEndIndex>1</wpml:actionGroupEndIndex> " <— right here
Gimbal Pitch Bug
If a mission is created for a DJI Fly waypoint drone (my test done for Air 3S) and then changed to a non-DJI Fly waypoint drone (my test done for an Air 2S), the gimbal pitch angles are reset to 0 (zero).
Steps to reproduce error:
- Create a new mission in Hub v2 for an Air 3S.
- Set the global “Gimbal Pitch Mode” to “Transition”.
- Place a few waypoints and set their gimbal pitch to various angles.
- Change the “Drone Model” to “Air 2S”.
- Open the saved mission in Hub v1.
- Note that all gimbal pitch angles are 0 (zero).
Expected result: The gimbal pitch angles should be retained when switching from one drone model to another.
Hi. Just tried to use the new Beta Hub but failed. Message was “upload failed. Invalid parameters in waypoint.” However i replicated my settings in the old Mission Hub and all worked well. I’m very impressed with the GoogleEarth facity with the Beta version but seems I have a problem with using it.
Did you log out of the old version before logging into the new
Welcome to the forum.
It sounds like you are trying to import a mission. Is this a CSV import? This has worked for me so there must be something in your CSV file that is out of range. More details will be needed from you to troubleshoot this.
Are you suggesting that he needs to log out of the old Mission Hub before using the new Mission Hub? Or, that logging out of the old Mission Hub caused this error?
I can successfully use the new Mission Hub whether logged in or logged out of the old Mission Hub.
When I tried it, I couldn’t use the location search in the new hub, till I logged out of the old one
Both “My Location” and “Location Search” work for me. I am logged into both the old Mission Hub and the New. Despite this descrepancy, I don’t think this has anything to do with Fred’s issue.
Was just a thought, that was all
Hello! - I have Mavic 2 Pro’s - are there any plans on making those “old” drones, compatible to the new Hub? Thanks!
Andreas
They already are compatible. I use my Mavic 2 Pro without problem.
Your question appears to be about the new Mission Hub. However, you posted your question in the Litchi Pilot thread. I have moved this post and the reply to the Mission Hub thread.
Just updated several old flights: great improvements to the UI!
One minor annoyance though… When I rename a flight, pressing Delete to edit within the name also deletes the current waypoint (so it disappears from the flight). I can select and type over to avoid this, but it is easy to forget.
I’didn’t log out of the old maybe next Ill try this.
I did setup the mission in the Beta Hub but this failed. And then I manually set up the same mission in the old Hub. This worked. But I did make adjustmets that I noticed when using Google Earth facility in the Beta.
65535 means Unknown drone model for DJI - I don’t believe the drone model matters when we’re just outputing a simple waypoint flight?
For 2&3: will be fixed in next build, thanks for letting us know
I think you are correct for consumer drones. I do know from experimentation that the drone model does matter for enterprise drones. I ended up using “68” for DJI Fly drones because that is what DJI uses for consumer drones.
Internally in Litchi Pilot we don’t specify the drone, the DJI SDK is responsible for generating the KMZ and it outputs Unknown (drone model) in the KMZ that gets uploaded to the drone which works fine with our enterprise drones. It is possible that Unknown won’t work with DJI Pilot KMZ import however for now the Litchi Hub’s KMZ export is only meant to be used with DJI Fly. For DJI Pilot drones, it’s not really necessary since you can use Litchi Pilot.
2 Likes
I’m an environmental scientist focusing on windspeed measurements. Your tool helps me out immensely and I’m very thankful for your dedicated work. Please keep going and improve this application. Awesome!
1 Like