Just wandered if the new TXTlogToCSVtool.exe works on the newer flight records, last i heard it didnt
TXTlogToCSVtool.exe does it handle the newer flight logs yet?
- Thread starter Exphantomflyer
- Start date
Part of the log is translated, few tables are broken. Not working right now. I was trying to make a profile for Dashware for the Mavic 3 but need some work to make it work.
Yes but seeing as how its the same tool i just used the generic name for it
I have been semi successful in creating a profile, I downloaded a CSV file from AirData website, I can get everything working except distance and max distance, the values in the CSV are massive.
I used the Flytrex dataset as it had the map values, then added Satellites to it and then had to remap all the other values for the gauges.
I used the Flytrex dataset as it had the map values, then added Satellites to it and then had to remap all the other values for the gauges.
Try the two XML files.
Copy DJI Mavic MM-MA2-M2P.xml (Data Profile) to C:\Users\your_username\Documents\DashWare\DataProfiles
Copy CustomDataTypes.xml (Custom Data Types) to C:\Users\your_username\Documents\DashWare\Settings
Import included gauges (.dashware extension) from Gauge Toolbox in DashWare
Copy DJI Mavic MM-MA2-M2P.xml (Data Profile) to C:\Users\your_username\Documents\DashWare\DataProfiles
Copy CustomDataTypes.xml (Custom Data Types) to C:\Users\your_username\Documents\DashWare\Settings
Import included gauges (.dashware extension) from Gauge Toolbox in DashWare
Thanks for the files but they are no different to the ones I have and dont work with a CSV from airdata website, if you try to convert the txt file the tool just hangs
Last edited:
I have a profile that I am testing for the Mavic 3. Also,
So far I can confirm the profile works for DJI Mini2, Mavic Air 2, Mavic 2 Pro, Mavic 3.
Also, keep in mind this is made for imperial. I need to work on fixing the metric system as well. It just takes time. I have long hours working with that.
If you need instructions on how to install that let me know.
Do not use the converter. Use the Airdata CSV. The profile is adapted to that CSV. I need to send an email to airdata and see if they can provide the Vertical Speed data in the CSV.
I will be releasing everything in friendly version with instructions in a separate post.
Last edited:
I have it all working for the mini 2, except for vertical climb speed as the CSV from Airdata gives negative figures for climb and postive figures for descent, its listed as zSpeed(mph) in the CSV.
Otherwise I think I have it all working
Metric is easy, just change your measurements to Metric and the flight log will give metric figures, you just need to build or adapt a gauge to use the metric system
here is mine
DJI MINI2.xml
drive.google.com
Just to confirm the data profile works Mavic Air 2, DJI Mini 2, Mavic 2 Pro, Mavic 3.
Can somebody send me a Flylog or CSV file from airdata from a Mavic Air 2S to test ???
Can somebody send me a Flylog or CSV file from airdata from a Mavic Air 2S to test ???
I built my own, here is a link to it and the gauge I have built
DJI MINI2 FMP.rar
drive.google.com
Do you have a working gauge that shows all the readouts as i show in post #6
I tried your file with my gauge and most of the figures dont work
Mine are working perfectly. Still missing the Vertical Speed because the zspeed does not work. Also the Sticks imputes. Still working on that. Here is my Gauges. Everting in one bar to keep it clean.
in one bar. Looks more clean.
in one bar. Looks more clean.
Here is the problem with the sticks. In the Old CSV files produced by the TXTlogToCSVtool.exe the table had different names than the CSV from Airdata and obviously that is the reason the gauges was not working. No problem I fix that.
The biggest problem is the old values for the dead stick where in 0 and that's fine but in the new one from Airdata, the death stick reads 1024. The stick formula was the aileron value divided in 100 if I am not mistaken. I am not sure what kind of values they are using now to convert this in the stick inputs.
The biggest problem is the old values for the dead stick where in 0 and that's fine but in the new one from Airdata, the death stick reads 1024. The stick formula was the aileron value divided in 100 if I am not mistaken. I am not sure what kind of values they are using now to convert this in the stick inputs.
Can you send the gauge please mate, i tried your file again and its still a no go with my XML file
You need to install the gauge. I did made this video like a year ago and I explain how to do it.
I will do a new video since there a different way to work with the CSV and i will ad new techniques.
I know how to import gauges mate, Im happy to say that I have it all working now including Zspeed working the right way
