many of us are using EagleTree data recorder. Sometimes I have several logs that I need to merge between the autopilots and EagleTree. The manual states that you can contact them about file format and they will respond. Unfortunately this is not the case. Therefore maybe somebody has a clue about what the file content means:
TESTPLANE
0 0 0 255 1 0 0 0 255 1 254 0 0 1 0 0 0 255 0 0 0 1 100 74 1536 10.04 8205 1 1073758292
All Sessions
0 19456
Session 1
0 19456
Milliseconds IsEvent EventError EventData Altitude Airspeed ServoCurrent*100 Throttle PackVolt*100 Amps*100 GForceX*100 GForceY*100 GForceZ*100 Temp1*10 Temp2*10 Temp3*10 RPM RPM2 GPSLat GPSLon GPSAlt GPSSpeed GPSCourse GPSDist GPSUTC NumSats GPSFlags SpektrumHolds SpektrumLostFrames SpektrumAFades SpektrumBFades SpektrumLeftFades SpektrumRightFades GPSUTC-ASCII HDOP*10
0 1 9 14 0 0 0 0 1265 48 0 0 0 0 0 0 0 0 0.000000000000 0.000000000000 0.0 0.0 0.0 0.0 0.0000 0 0 0 0 0 0 0 0 04/06/2012,01:00:00.89 0
100 0 0 0 0 0 0 0 1265 48 0 0 0 0 0 0 0 0 0.000000000000 0.000000000000 0.0 0.0 0.0 0.0 0.0000 0 0 0 0 0 0 0 0 04/06/2012,01:00:00.89 0
200 0 0 0 0 0 0 0 1265 48 0 0 0 0 0 0 0 0 0.000000000000 0.000000000000 0.0 0.0 0.0 0.0 0.0000 0 0 0 0 0 0 0 0 04/06/2012,01:00:00.89 0
300 0 0 0 0 0 0 0 1265 48 0 0 0 0 0 0 0 0 0.000000000000 0.000000000000 0.0 0.0 0.0 0.0 0.0000 0 0 0 0 0 0 0 0 04/06/2012,01:00:00.89 0
400 0 0 0 0 0 0 0 1265 48 0 0 0 0 0 0 0 0 0.000000000000 0.000000000000 0.0 0.0 0.0 0.0 0.0000 0 0 0 0 0 0 0 0 04/06/2012,01:00:00.89 0
Obviously 19456 is just the number of samples, the rest are easily decoded ASCII data, but the line in BOLD contains some magic flags and options, one of them is related to time step. Any ideas?
EDIT: The field in red is milliseconds timestep size, it accepts .6 format also, and Milliseconds from the first column are ignored.
Not sure if the application can plot precisely timesteps like 333.333333 or will just truncate to 333.
Other fields remain a mystery.
BTW somebody mentioned
http://www.heliguru.ru/download/-manual/eagletree/597-pro-glide-fli...
but it doesn't explain beyond:
Second Line: Data about your model’s setup, in an internal.
This line is needed to allow sharing of your data files with others.
Oh yes, for sure.
It also adds
Email us if you need more information on the file format.
Without promise of answering to that mail.
PLEASE POST HERE YOUR RECORDINGS *.FDR SO I CAN PICK DIFFERENCES COMING FROM DIFFERENT SOFTWARE VERSIONS - IT WILL BE EASIER TO REVERSE-ENGINEER THIS WAY.
Comment by Bertrand Duchiron on June 1, 2012 at 9:32am Did you try to modify the setup of the log software and look a the modifcication of the 2d line ?
Comment by healthyfatboy on June 3, 2012 at 6:40am What exactly are you trying to find? I've worked with the data some before and can help if I know what exactly is confusing you.
Comment by Krzysztof Bosak on June 3, 2012 at 7:12am I would like to know the meaning of every parameter marked in Bold. are those setups like units (imperial vs SI) or other stuff, since I want to not waste time comparing with data recorded with EargleTree and figurign out why certain things are not as usual.
Comment by healthyfatboy on June 3, 2012 at 3:08pm Ah, okay. I'm not sure about those parameters. I used everything but those before.
Comment by Jani on June 3, 2012 at 4:40pm I looked quickly a log file and found:
0 0 0 255 1 0 0 0 255 1 254 0 0 1 0 0 0 255 0 0 0 1 100 74 1536 10.04 8205 1 1073758292
| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
A BC D E FG H I J K L MNO PQ R S TU VW X Y Z 1 2 3
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X = Looks logger hardware identifier?? Elogger V3 = 73 and Elogger V4 = 74 ??
Y
Z = Data Recorder software version like 8.63, 9.13 and 10.04
1
2 = number of sessions in file
3
Comment by Jani on June 4, 2012 at 11:29am Looked a bit more. Correction for above post:
X = Logger firmware effects to this value also. Elogger V3 with old firmware = 73 ,but with 5.84 firmware = 74
3 = At least connected rpm sensors change this value, perhaps something more effects too. For example Elogger V3 gives with Brushless rpm sensor = 84 ,no rpm measuring = 84 ?? , magnetic sensor = 16468
Comment by Krzysztof Bosak on June 18, 2012 at 12:28pm Thanks Jani all this works. I am still working on GPS flags column... looks it is still ignoring GPS time.
What I am generating is this:
FLEXIPILOT
0 0 0 255 1 0 0 0 255 1 254 0 0 1 0 0 0 255 0 0 0 1 250.000000 74 1536 10.04 8205 1 1073766484
All Sessions
0 3887
Session 1
0 3887
Milliseconds IsEvent EventError EventData Altitude Airspeed ServoCurrent*100 Throttle PackVolt*100 Amps*100 GForceX*100 GForceY*100 GForceZ*100 Temp1*10 Temp2*10 Temp3*10 RPM RPM2 GPSLat GPSLon GPSAlt GPSSpeed GPSCourse GPSDist GPSUTC NumSats GPSFlags SpektrumHolds SpektrumLostFrames SpektrumAFades SpektrumBFades SpektrumLeftFades SpektrumRightFades GPSUTC-ASCII HDOP*10
0 0 0 0 0 5 0 17 1202 203 29 3 90 223 162 0 0 0 51.148418 16.996267 108.7 1.4 296 0.000 0 9 4 0 0 0 0 0 0 04/01/2012,14:17:08.00 9
250 0 0 0 -1 5 0 22 1202 214 36 5 96 223 162 0 0 0 51.148418 16.996267 108.6 1.4 295 0.000 0 9 4 0 0 0 0 0 0 04/01/2012,14:17:08.199 9
500 0 0 0 -1 6 0 28 1191 335 37 5 91 223 162 0 0 0 51.148418 16.996265 108.6 0.7 295 0.000 0 9 4 0 0 0 0 0 0 04/01/2012,14:17:08.398 9
750 0 0 0 -1 6 0 33 1177 558 33 1 92 223 162 0 0 0 51.148418 16.996265 108.6 0.7 297 0.000 0 9 4 0 0 0 0 0 0 04/01/2012,14:17:08.801 9
1000 0 0 0 0 6 0 39 1157 827 37 6 96 223 162 0 0 0 51.148418 16.996265 108.6 0.7 297 0.000 0 9 4 0 0 0 0 0 0 04/01/2012,14:17:09.00 9
1250 0 0 0 0 6 0 45 1133 1225 39 8 96 223 162 0 0 0 51.148418 16.996265 108.6 0.7 296 0.000 0 9 4 0 0 0 0 0 0 04/01/2012,14:17:09.199 9
Comment
Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.24 members
1298 members
47 members
87 members
183 members
© 2013 Created by Chris Anderson.
Powered by

You need to be a member of DIY Drones to add comments!
Join DIY Drones