Anyone figured out a way to be able to read /decipher the flight data for your previous flight path

Discussion in 'X-Star / X-Star Premium' started by DroneOut, Aug 10, 2016.

  1. Just curious to know if anyone has been successful in being able to understand/interpret any of the data on the micro-sd card regarding your previous flight path. For instance, if someone said you flew over their property at a certain height and at certain time of the day... if you can read the info from previous flight paths, you are then able to say and show you did not...
     
  2. What data are you referring to? There is an mislabeled option to save .srn files for close captions. The files are actually .ass files, Aegisub Advanced Substation. A free utility is available, http://www.aegisub.org/

    The generated files are not really suitable for close captions without substantial filtering but they do include lat/lon. I just pulled up an example and discovered a major problem. Lat/lon are only recorded to the 4th decimal. This is not good enough to show an accurate track. These files are only generated while recording video, which is a disadvantage.

    Code:
    [Events]
    Format: Layer, Start, End, Style, Name, MarginL, MarginR, MarginV, Effect, Text
    Dialogue: 0,00:00:00.50,00:00:01.00,*Default,,0000,0000,0000,,HOME(-86.5791, 34.6427) 2016.8.10 19:21:28
    GPS(W:86.5795, N:34.6420, 256) ReH:80
    ISO:100 SHUTTER:50 EV:0 F-NUM:F2.8
    Dialogue: 0,00:00:01.00,00:00:01.50,*Default,,0000,0000,0000,,HOME(-86.5791, 34.6427) 2016.8.10 19:21:29
    GPS(W:86.5795, N:34.6420, 256) ReH:80
    ISO:100 SHUTTER:50 EV:0 F-NUM:F2.8
    Dialogue: 0,00:00:01.50,00:00:02.00,*Default,,0000,0000,0000,,HOME(-86.5791, 34.6427) 2016.8.10 19:21:29
    GPS(W:86.5795, N:34.6420, 256) ReH:80
    ISO:100 SHUTTER:50 EV:0 F-NUM:F2.8
    Dialogue: 0,00:00:02.00,00:00:02.50,*Default,,0000,0000,0000,,HOME(-86.5791, 34.6427) 2016.8.10 19:21:30
    GPS(W:86.5795, N:34.6420, 256) ReH:80
    ISO:100 SHUTTER:50 EV:0 F-NUM:F2.8
    Dialogue: 0,00:00:02.50,00:00:03.00,*Default,,0000,0000,0000,,HOME(-86.5791, 34.6427) 2016.8.10 19:21:30
    GPS(W:86.5795, N:34.6420, 256) ReH:80
    ISO:100 SHUTTER:50 EV:0 F-NUM:F2.8
    Dialogue: 0,00:00:03.00,00:00:03.50,*Default,,0000,0000,0000,,HOME(-86.5791, 34.6427) 2016.8.10 19:21:31
    GPS(W:86.5795, N:34.6420, 256) ReH:80
    ISO:100 SHUTTER:50 EV:0 F-NUM:F2.8
    
    There are log files that are available under Flight Control Settings:Advanced Settings:Read Flight Data Reading them requires a USB connection between the X-Star and a computer. I asked Autel about them:
    Apparently the log files are a variant of 'sd2log' There are the field names, as extracted by sd2log_dump.py

    It does include GPS_GPSTime, GPS_Lat, GPS_Lon, GPS_Alt

    Code:
    ATT_Roll
    ATT_Pitch
    ATT_Yaw
    ATT_RollRate
    ATT_PitchRate
    ATT_YawRate
    ATT_GX
    ATT_GY
    ATT_GZ
    ATSP_RollSP
    ATSP_PitchSP
    ATSP_YawSP
    ATSP_ThrustSP
    IMU_AccX
    IMU_AccY
    IMU_AccZ
    IMU_GyroX
    IMU_GyroY
    IMU_GyroZ
    IMU_MagX
    IMU_MagY
    IMU_MagZ
    IMU_Temprature
    SENS_BaroPres
    SENS_BaroAlt
    SENS_BaroTemp
    SENS_DiffPres
    SENS_DiffPresFilt
    LPOS_X
    LPOS_Y
    LPOS_Z
    LPOS_Dist
    LPOS_DistR
    LPOS_VX
    LPOS_VY
    LPOS_VZ
    LPOS_AX
    LPOS_AY
    LPOS_AZ
    LPOS_GFlg
    LPOS_SOfS
    LPOS_BOfS
    LPOS_CSnr
    LPOS_CSnrF
    LPSP_X
    LPSP_Y
    LPSP_Z
    LPSP_Yaw
    GPS_GPSTime
    GPS_Fix
    GPS_EPH
    GPS_EPV
    GPS_Lat
    GPS_Lon
    GPS_Alt
    GPS_VelN
    GPS_VelE
    GPS_VelD
    GPS_nSat
    ATTC_Roll
    ATTC_Pitch
    ATTC_Yaw
    ATTC_Thrust
    STAT_Main
    STAT_Nav
    STAT_Arm
    STAT_Load
    STAT_RCLost
    RC_Ch0
    RC_Ch1
    RC_Ch2
    RC_Ch3
    RC_Ch4
    RC_Ch5
    RC_Ch6
    RC_Ch7
    RC_Count
    RC_SignalLost
    OUT0_Out0
    OUT0_Out1
    OUT0_Out2
    OUT0_Out3
    OUT0_Out4
    OUT0_Out5
    OUT0_Out6
    OUT0_Out7
    ARSP_RollRateSP
    ARSP_PitchRateSP
    ARSP_YawRateSP
    FLOW_RawX
    FLOW_RawY
    FLOW_Gx
    FLOW_Gy
    FLOW_Gz
    FLOW_Gtemp
    FLOW_GD
    FLOW_Q
    FLOW_id
    FLOW_Count
    FLOW_TS
    FLOW_Tspan
    FLOW_Tsince
    GPOS_Lat
    GPOS_Lon
    GPOS_Alt
    GPOS_VelN
    GPOS_VelE
    GPOS_VelD
    GPOS_EPH
    GPOS_EPV
    GVSP_VX
    GVSP_VY
    GVSP_VZ
    BATT_V
    BATT_VFilt
    BATT_Curr
    BATT_Capacity
    PWR_Periph5V
    PWR_Servo5V
    PWR_RSSI
    PWR_UsbOk
    PWR_BrickOk
    PWR_ServoOk
    PWR_PeriphOC
    PWR_HipwrOC
    STM1_X
    STM1_Y
    STM1_Z
    STM1_VX
    STM1_VY
    STM1_VZ
    STM1_AX
    STM1_AY
    STM1_AZ
    STM1_Roll
    STM1_Pitch
    STM1_Yaw
    STM1_g
    STM1_RstXY
    STM1_RstZ
    STM1_D_eph
    STM2_ActX
    STM2_ActY
    STM2_ActZ
    STM2_ThrIX
    STM2_ThrIY
    STM2_ThrIZ
    STM2_FltSt
    STM2_FltMd
    STM2_YawA
    STM2_Warn
    STM2_Valid
    STM2_Dbg
    DBUG_F1
    DBUG_F2
    DBUG_F3
    DBUG_F4
    DBUG_F5
    DBUG_F6
    DBUG_F7
    DBUG_F8
    DBUG_F9
    DBUG_F10
    DBUG_F11
    DBUG_F12
    DBUG_F13
    HOME_X
    HOME_Y
    HOME_Lat
    HOME_Lon
    HOME_Alt
    STAR_Cmd
    STAR_Lmode
    STAR_Lx
    STAR_Ly
    STAR_R
    STAR_Vsp
    STAR_RTH
    STAR_LN
    STAR_Endmode
    STAR_Ldir
    STAR_CYaw
    TIME_StartTime
    VER_Arch
    VER_FwGit
    PARM_Name
    PARM_Value
    
     

  3. The logs are the way to go because it wil capture the data for the whole flight not just the recording time. As TomK mentioned the GPS log items have the coords you need and you can also use the GPOS log items.

    I have have been digging deep into the logs in the last view weeks and plan to release a tool to analyze the logs, In the mean time for your use-case I suggest you parse out the coors and convert to a KML file to view on google Earth.

    Here are my findings for the GPS/GPOS logs:

    GPS: QBffLLffffB, GPSTime,Fix,EPH,EPV,Lat,Lon,Alt,VelN,VelE,VelD,nSat
    GPOS: LLffffff, Lat,Lon,Alt,VelN,VelE,VelD,EPH,EPV

    GPSTime = Timestamp (microseconds since UNIX epoch (1/1/1970)
    fix = 0-1: no fix, 2: 2D fix, 3: 3D fix, 4: DGPS, 5: RTK. Some applications will not use the value of this field unless it is at least two, so always correctly fill in the fix.
    lat = Latitude (WGS84), in degrees * 1E7
    lon = Longitude (WGS84), in degrees * 1E7
    alt = Altitude (AMSL, NOT WGS84), in meters (positive for up). Note that virtually all GPS modules provide the AMSL altitude in addition to the WGS84 altitude.
    eph = GPS HDOP horizontal dilution of position (unitless).
    epv = GPS VDOP vertical dilution of position (unitless).
    veln = GPS ground speed (m/s). (N)orth, (E)ast, (D)own
    nSat = Number of satellites visible. If unknown, set to 255 2016-08-11_1313.png
     
    4 people like this.
  4. What field is equivalent to heading? ATT_Yaw?
     

  5. Yup, thats what I map the heading to when doing a GPX export using the logViewer.

    http://xslogs.weebly.com/docs.html
     
  6. I was trying to find this thread with the Search and couldn't. "log" is too short and "log file" doesn't find it.

    These terms should make it easier to find . XStarLogViewer Log Viewer

    Is ATT_Yaw -pi..pi , with 0.0 = North?
     

    Attached Files:

  7. Yes, North = 0.0 radians... and E = +pi/2 and W = -pi/2 and S = -pi(CCW) or +pi (CW)

    You will want to search the .log file for ATT not ATT_RAW the python script to csv creates a row for each log entry and field where the .log file just creates a row for each log entry in the following format for ATT.

    ATT, Roll,Pitch,Yaw,RollRate,PitchRate,YawRate,GX,GY,GZ

    another tip if you are trying to read the log file generated by the XStarViewer using Excel then open up a blank excel sheet go to data->import from Text, using wizard select log file, choose delimited then comma.
     

    Attached Files:

    • ATT.png
      ATT.png
      File size:
      35.7 KB
      Views:
      10
  8. TomK,

    I saw in another post that you were looking into create a .ass file from the logs. If you can give me and example of the output of that file I could potentially add as another export format.
     
  9. The .ass file is created for you. Set the mislabeled "Close Caption .srn" option and there will be a .ass file for each video clip. It is not very usable though, with a lot more text than one would want as a caption, including Home lat/lon and f-stop. It does not include heading or altitude, which I would take over Home.
     
  10. TomKnAL, did you write this program? If so, wow! This help me a lot. If not, wow to whoever did and thank you for the huge investment in time and effort.
     
  11. OK so I have been trying to get the XStarLogViewer to read my log. This is a brand new unit so this was the only file on the drive after a 10 minute flight. Connected from the XSP to PC. I copied the file to my hard drive on my computer and opened it up in XStarLogViewer. Some information is there but there seems to be no GPS info? Is there a setting I should have checked on the app to record this ? I'm confused :) Just trying to get this to work so I can upload a track to GPS Visualizer or similar sites.
    Here is a link to my log file that I got of the xsp if you care to look. Maybe you can tell what I a m doing wrong :)

    https://drive.google.com/file/d/0B2uHATow-FIlRWJGZmsycWVjYkk/view?usp=sharing
     
  12. New user flying the orange bird up here in Montana. Love the bird, but unsure about long term health of Autel. I've been able to download the log file and view it in XStarLogViewer successfully. The question I have is, does anyone know if the data for when the camera shutter is activated is stored in the log file. I want to have camera position and x, y, z and yaw for each camera shot

    Thanks,
    cooksa
     

Share This Page