MVO:PosX, MVP:PosY
north-south = MVO:posX * 100 - 6
east-west = MVO:posY * 100 - 21
Interesting... See if I can make a Google maps overlay, calculate & draw it on maps itself after setting a start point.Another cool feature is plotting Tello's flight path.
You only need to export .DAT file to .XLS (microsoft Excel sheet format). Then, select columnsand choose Insert Graphic from Excel toolbar. Setting clear background graphic and adding a google maps screeen-captured layer below you will get something like this:Code:MVO:PosX, MVP:PosY
View attachment 1710
Take into account Tello's visual positioning is not 100% accuracy. Flight takeoff and landing spot were the same, althought in the map they are about 30 meters appart.
Note: If you notice Tello's path is reversed and displaced some Excel formula is needed. For this flight I really plotted:
Code:north-south = MVO:posY * 100 - 6 east-west = MVO:posY * 100 - 21
CsvView will accept the .DAT file directly. It uses DatCon internally to first do the conversion to a .csv.So I need to use DatCon to extract first, then use Csv?
north-south = MVO:posX * 100 - offset_x
east-west = MVO:posY * 100 - offset_y
Try this. Edit the file <CsvViewInstallDir>/defs/datGenericPlayers.pmlHi, @BudWalker
Congratulations for your great apps. I would like to suggest you adding CsvView ability to plot Tello's route plotting values (MVO: PosX, MVP: PosY). Only math you need is:
Code:north-south = MVO:posX * 100 - offset_x east-west = MVO:posY * 100 - offset_y
Where offset_x and offset_y are the very first values detected by tello VPS.
Of course, you should plot route over a blank map page becouse data is not georeferenced.
Zip file attached for reference in this post. It contains a DAT flight log file sample and a Microsoft Excel Sheet plotting route and values.
Thank you for your excellent work.
Raul
<geoPlayer>
<geopath>
<name>AC</name>
<symbol>A</symbol>
<Latitude>IMU_ATTI(0):Latitude</Latitude>
<Longitude>IMU_ATTI(0):Longitude</Longitude>
<Altitude>General:relativeHeight</Altitude>
<headingSignal>IMU_ATTI(0):yaw</headingSignal>
<headingSignal>IMU_ATTI(0):magYaw</headingSignal>
</geopath>
<geoPath>
<name>Home</name>
<symbol>H</symbol>
<Latitude>HP:Latitude</Latitude>
<Longitude>HP:Longitude</Longitude>
</geoPath>
<geoPath>
<name>MVO</name>
<symbol>M</symbol>
<Latitude>MVO:posY</Latitude>
<Longitude>MVO:posX</Longitude>
</geoPath>
</geoPlayer>
I suspect that the orientation isn't flipped in both axes. It's rotated 180°. You can avoid this problem by launching with the Tello pointing true North.@BudWalker ,
It worked ! It is amazing ! Thanks a lot for your helpl
I got this plot into CsvView GeoPath window:
View attachment 1973
As you can see it's exactly the same shape as my previous Microsoft Excel attemp.
Only problem is route is not well oriented (it seems flipped on both axes)
By the way, Is there any chance showing a distance ruler in the window ?
My datGenericPlayers.pml bottom file is now this way:
Code:<geoPlayer> <geopath> <name>AC</name> <symbol>A</symbol> <Latitude>IMU_ATTI(0):Latitude</Latitude> <Longitude>IMU_ATTI(0):Longitude</Longitude> <Altitude>General:relativeHeight</Altitude> <headingSignal>IMU_ATTI(0):yaw</headingSignal> <headingSignal>IMU_ATTI(0):magYaw</headingSignal> </geopath> <geoPath> <name>Home</name> <symbol>H</symbol> <Latitude>HP:Latitude</Latitude> <Longitude>HP:Longitude</Longitude> </geoPath> <geoPath> <name>MVO</name> <symbol>M</symbol> <Latitude>MVO:posY</Latitude> <Longitude>MVO:posX</Longitude> </geoPath> </geoPlayer>
I suspect that the orientation isn't flipped in both axes. It's rotated 180°. You can avoid this problem by launching with the Tello pointing true North.
The GeoPlayer is based on lat/long coords. The MVO positional data is in meters I believe. So the GeoPlayer is being fooled into thinking the MVO data is actually lat/long data.
I'm involved in another (non drone) project for the next 6 to 9 months and don't have much time to implement new features. I'm just doing bug fixes and the like.
<geoPath>
<name>MVO</name>
<symbol>M</symbol>
<Latitude>-MVO:posY</Latitude>
<Longitude>MVO:posX</Longitude>
</geoPath>
<geoPlayer>
<geoPath>
<name>MVO</name>
<symbol>M</symbol>
<Latitude>MVO:posX</Latitude>
<Longitude>MVO:posY</Longitude>
<Altitude>MVO:height</Altitude>
</geoPath>
</geoPlayer>
<geoPlayer>
<geoPath>
<name>MVO</name>
<symbol>M</symbol>
<Latitude>MVO:posX</Latitude>
<Longitude>MVO:posY</Longitude>
<Altitude>MVO:height</Altitude>
</geoPath>
<geoPath>
<name>40Meters</name>
<symbol>4</symbol>
<Latitude>err_code:mag_stat</Latitude>
<Longitude>IMU_ATTI(0):quatY</Longitude>
</geoPath>
<geoPath>
<name>100Meters</name>
<symbol>1</symbol>
<Latitude>err_code:mag_stat</Latitude>
<Longitude>IMU_ATTI(0):quatW</Longitude>
</geoPath>
<geoPath>
<name>200Meters</name>
<symbol>2</symbol>
<Latitude>IMU_ATTI(0):quatZ</Latitude>
<Longitude>err_code:mag_stat</Longitude>
</geoPath>
</geoPlayer>
Well, of course they were switched. Sorry about that.I got it !
It was so simple as swapping X and Y coordinates into datGenericPlayers.pml this way:
Code:<geoPlayer> <geoPath> <name>MVO</name> <symbol>M</symbol> <Latitude>MVO:posX</Latitude> <Longitude>MVO:posY</Longitude> <Altitude>MVO:height</Altitude> </geoPath> </geoPlayer>
Path is now showed perfect. No flipped route anymore.
View attachment 1984
It's great !
Raul.
GeoPath 40Meters has signal err_code:mag_stat that isn't defined
GeoPath 100Meters has signal err_code:mag_stat that isn't defined
GeoPath 200Meters has signal err_code:mag_stat that isn't defined
We use essential cookies to make this site work, and optional cookies to enhance your experience.