Why do my altitudes get converted to 500m when I do a conversion from Litchi to DJI using that utility? I don’t have a 500m limit in Fly anymore…?
That is not the expected behavior so more information is needed. For starters, you could share the Litchi mission by unchecking the “Private” checkbox and posting the URL here.
This flight is not something I’d publish…I’ll recreate the problem I’m having on another flight in the next couple of days and make it public.
Here is a cut-and-paste from a transiton to 500+m above take-off and then back down to <500m above take-off:
1620.73496 288 40.08048299 0 2 3.7 0 0 0 0 0 0 -1 -1
1640 289.4 49.36848074 0 2 3.7 0 0 0 0 0 0 -1 -1
1640 287.9 50.04327841 0 2 3.7 0 0 0 0 0 0 -1 -1
Transition back to <500m above take-off:
1640 119.8 51.19744284 0 2 -19.1 0 0 0 0 0 0 -1 -1
1640 119.7 50.7720994 0 2 -19.3 0 0 0 0 0 0 -1 -1
1626.968556 120.1 48.64374026 0 2 -19.4 0 0 0 0 0 0 -1 -1
1593.175904 119.7 48.64374026 0 2 -19.5 0 0 0 0 0 0 -1 -1
Data from the flight logs:
1635.826824
1637.467244
1639.435748
1641.404252
1643.372756
1645.669344
1647.309764
1649.278268
1650.918688
So, the flight log isn’t the problem.
I cannot come to any conclusions from the data you provided. More information is needed. You mentioned that the heights get converted to 500m but you don’t say what heights were used as inputs. I would need to see the CSV file you are converting.
I flew the drone up past 500m (1640’) and have 2 csv files…one a download from Airdata and the other from the AirData to Litchi Converter…Airdata is fine…the Litchi conversion limited the altitude to 500m (1640’).
35.68384217 -117.909184 1518.372752 51 27.58531879
35.68393687 -117.9090388 1604.33076 50.7 27.58531879
35.68410398 -117.9087973 1640 39.1 47.00382235 0
35.68433586 -117.9086113 1640 33.3 50.34357219 0
35.68459436 -117.9084922 1640 5.9 50.25653775 0
35.68486764 -117.9085354 1640 340.2 50.25653775 0
35.68513174 -117.9086354 1640 349.7 50.24075243 0
35.68540257 -117.9086972 1640 346.2 50.16007514 0
35.68567235 -117.9087628 1640 346.4 50.16007514 0
35.68594226 -117.908831 1640 347.2 50.25894734 0
35.68620806 -117.9089261 1640 332.3 50.19762394 0
35.68638252 -117.9091881 1640 282.7 50.19762394 0
35.68627372 -117.9095 1640 208.2 50.06528015 0
35.68600429 -117.9095645 1640 198 50.06528015 0
35.68574054 -117.9096628 1640 198.2 50.05462603 0
35.68547893 -117.9097648 1640 197.6 50.05462603 0
35.68521413 -117.9098641 1640 199.3 50.48896176 0
35.68496906 -117.9100252 1640 232.1 50.09674154 0
35.68482377 -117.9103121 1640 240 50.09674154 0
35.68468637 -117.9106069 1632.874068 239.7 26.68658693
35.68461469 -117.9107639 1548.228396 239.5 26.6043319
Here’s a link to the Airdata file: Jan 27th, 2025 09:45AM | General | DJI Fly log 1.16.0 | United States | Airdata UAV
It’s a pretty flaky flight…windy and cold…I sat in the truck…only purpose was to get you some data…TIA for fixing this…
Oh. Your first message didn’t clearly state what converter you were using. This message shows that you are converting an AirData CSV file to a Litchi CSV file. That converter will limit the heights to a value between -655 … 1640 on purpose. Anything outside of that range will prevent the resulting file from being imported into Litchi’s Mission Hub.
One last question: If I manipulate the data in the Litchi CSV before converting it to DJI, will I get valid results, or is the program going to use the same -655 … 1640 limits? Thanks.
I answered my own question…I’m seeing the altitude numbers I need to see after the manipulation…now to see what the KMZ looks like…
As you have discovered, the “Litchi to DJI” converter does not limit the altitudes.
My goal and reasoning for this is to make all of my utilities work with Litchi. Therefore, I try to make sure any CSV file created for Litchi, is compatible with Litchi. That is why I range-check AirData values before exporting to a Litchi-compatible CSV file.
Makes sense…I can imagine the chaos…
For the record, I’m doing these things (reg violations obviously - but sate - nothing to be harmed when I’m doing this - always desolate terrain…) in the hope that 108 will open things up to Autonomous Flights…these drones are obviously way smart…Lots of SAR Missions in my dreams that may avoid injury to Human SAR Members…and maybe save a few lives…
Using your tools and Excel, I’m able to kludge together waypoint missions…that work…for Free…in Extreme Terrain…I flew a proof-of-concept this morning where I just put the drone down outside my car door and told it to Go…it did and came back…No DJi Care Refresh required…
As long as you know that you are venturing into Class E air space (1200 feet AGL to 18,000 feet) not to mention the 400 foot AGL limit for drones or worse depending on the exact location.
That’s good to know.