Q500log2kml User Manual - B

Transcript

Q500log2kml user manual FlightLog data evaluation for Yuneec quad or hexa copter Version 2.8 Author: Issue: Q500log2kml, Version 2.8 02//2017 Helmut Elsner 02/2017 Page 1/17 Q500log2kml - FlightLog data evaluation for Yuneec copter Table of Contents Q500log2kml - FlightLog data evaluation for Yuneec copter .................................................................. 2 Introduction ......................................................................................................................................... 3 Features (overview) ............................................................................................................................. 4 Installation ........................................................................................................................................... 4 Detailed description of the features ................................................................................................... 4 Read data: ....................................................................................................................................... 4 Archive: ............................................................................................................................................ 6 Convert data: ................................................................................................................................... 7 Elevation histogram:........................................................................................................................ 7 Data analysis: ................................................................................................................................... 8 Settings: ........................................................................................................................................... 9 CCC Waypoints (development discontinued, no support): ........................................................... 11 Appendix............................................................................................................................................ 13 Error Flags (set bitwise): ................................................................................................................ 13 Vehicle types: ................................................................................................................................ 13 Meaning of the columns in the raw data tables: .......................................................................... 13 Yuneec Breeze raw data: ............................................................................................................... 15 Flight Modes: ................................................................................................................................. 15 Continuation Flight Modes (Blade 350QX: found by try and error): ............................................. 16 Thresholds / color coding: ............................................................................................................. 17 Short description – Prepare telemetry for Dashware: .................................................................. 17 Q500log2kml, Version 2.8 02//2017 Page 2/17 Introduction This application was made to evaluate the FlightLog data sent by Yuneec driven copter (like Q500, Typhoon H, Breeze, but also Blade Chroma or 350QX). Those flight log data are available on ground station ST10+ (or ST10 with latest firmware) and will be stored if a micro SD card was placed into the ground station. The slot for the micro SD card is located under the battery of the ST10. Format the SD card with FAT32 file system. You do not need a large or fast SD card - a cheap card is enough. The SD card can be read via micro USB connector. The telemetry data for copter, ground station and radio connection are stored in file structure called "FlightLog" in different subdirectories. For this application, you need to move or copy the whole "FlightLog" directory with all subdirectories without any changes. For Yuneec Breeze the flight log is stored on the controller by the Pilot App. Breeze has no subdirectories. It seems that data from ST12, ST16 or ST24 do also work with this application. ST10 stands then for all STxx RC-controllers. Example: The screenshot shows a very big amount of flights with Compass Calibration Warnings (orange). Those needs a deeper view. For this, the application can be used as all-in-one solution. Important note: Use this application on your own risk. There is no guaranty for correctness and completeness of the results of the evaluation of flight log data. Because this all was done by own tests and private researches, the interpretation of the data may be wrong. On the other hand, this application is freeware. Q500log2kml, Version 2.8 02//2017 Page 3/17 Features (overview)         Archive: Rename the FlightLog directory by using a time stamp to avoid overwriting older data. This should be the first action if you move the FlightLog data from ST10 to your PC. Convert: Convert telemetry data from copter to KML- or KMZ-files (flight path for Google Earth), GPX for other map services, for import to Dashware in order to get telemetry data in videos or as HTML-Report for documentation. Convert CCC waypoint files either to KML/KMZ or to GPX file format. Overview: Some important information for the flights in a table form (ceiling, max. air speed, max. distance, warnings, etc). Display files: Browse raw data of telemetry files. Elevation histogram: Graphic elevation histogram and voltage curve. Analysis: Analyze a predefined data area to see i.e average speed, climb rate… Settings: A tab sheet where you can enter main settings of the application. CCC Waypoints: Edit, add, delete and convert CCC waypoint files from ST16 of the Yuneec Typhoon H. Installation No installation necessary, simply unzip the downloaded file and store it to a directory where you have write access. This can also be a USB stick or a removable drive. Download updates and user manual from my homepage. To run the application you might have to suppress Microsoft SmartScreen warnings: Click on "more info" and then "run anyway". Detailed description of the features Read data: In the header of the application window are the main input fields and controls. To load data to the application select the main directory (usually \FlightLog) where the FlightLog data are located in three different subdirectories: \Remote, \RemoteGPS and \Telemetry. You can also Drag & Drop the directory from a file manager to the application window. Files will be checked and an overview in table form will be shown at tab sheet “Overview. Flights where error flags appeared will be marked das colored line. Voltage warnings are indicated by a “!“ in the column "Umin". The status bar at the bottom of the application window shows the following context dependent from left to right: - count of files with telemetry data, Q500log2kml, Version 2.8 02//2017 Page 4/17 - count of data points or selected data point in the file, output format for file conversion, state, messages or analysis results. Usually there are for each flight three files in different subdirectories: - Telemetry_*.csv in directory "\Telemetry": contains telemetry data sent by copter (selection: Copter). - RemoteGPS_*.csv in directory "\RemoteGPS": contains GPS data from STxx ground station (Selection: RC). - Remote_*.csv in directory "\Remote": contains the values, that are transmitted over the RC connection (selection: Radio). Stick values greater that neutral (2048) are marked with blue colour, stick values smaller than neutral position are green. You can see those raw data at tab sheet "Display files". Flight modes, Error flags, GPS accuracy and RC signal strength (fsk_rssi) are indicated by different colours. Maximum values for speed (tas) and altitude will be marked as yellow to find it faster. By click on right mouse button, you will get a context menu for following functions: - Show at Google Maps: GPS coordinates of the selected data point will be shown at Google Maps in Hybrid View. - Show at OpenStreetMap: GPS coordinates of the selected data point will be shown at OpenStreetMap. - Go to data point: Scrolls down the table to the selected data point. The selection may come from Elevation histogram if the cursor is switched on. - Data analysis: As at Elevation histogram this performs an analysis for a predefined number of data points, results are in status bar. - Go to error flags: Scrolls down to the next error flags in the table. Double click on a cell shows additional information in the status bar below (explains flight modes, motor status and so on). In column Date/Time cells will be marked with color, if the interval between the time stamps is bigger than expected. This may be normal, but it indicates possibly bad radio conditions or high processor load in flight controller. Good to have an eye on it. Threshold 1: salmon - 600 ms Q500log2kml, Version 2.8 02//2017 Page 5/17 Threshold 2: red - 2 sec A click on the header of a column open another window with statistics or charts. This makes it easier to identify and understand what values there are and how things go in the raw data files. If header of columns with coordinates was clicked then the chart shows the distance from home point. Example: You will see a vertical red line as cursor for the cell that you have clicked in the table of raw data on the position in the timeline of the chart. Or for countable values: Archive: The ST10 saves only 20 flights and deletes older ones. Once deleted it cannot recovered any more. That is why I pull from time to time the FlightLog data from the memory card located in the ST10 and delete the whole directory there. It will be automatically recreated during next flight by the ST10 SW. Because the directory name is then always the same, I rename it to put it into the archive on the PC. This can be done by the button Archive to avoid overwriting older files with newer ones with the same name. This function adds simply a time stamp at the end of the directory name. The format of the directory suffix depends on settings for archiving. Q500log2kml, Version 2.8 02//2017 Page 6/17 Convert data: First intension of this application was to convert flight log data to KML files for Google Earth. For larger files Google recommends the format KMZ, which is nothing else than a zipped KML file. The output format can be defined in settings. Another supported file format is the GPX-format (GPS Exchange Format). This file format can be used to visualize your flight in services like Doarama. Additionally it is now possible to create output files for Dashware (due to missing profile, this function is not available for Yuneec Breeze). The format is the same as "st2dash" from Tami: http://www.drohnen-forum.de/index.php/Thread/12303-ST2Dash-der-Flightlog-Konverter-f%C3%BCrdie-ST10-Q500/ There you can find the related Dashware profile for the Q500 "Yuneec Q500 Dashware Profile v1.5". There will be converted only data from real flight modes. Calibration and initialisation data will be suppressed. This may be then easier to synchronize it with the video. Optional you can create a HTML-report for your flights as base for documentation. The output format can be selected on tab sheet "Settings". The output files will be saved in the selected FlightLog directory. By double click on the directory selection field, you will open the file manager with the directory where the output files are located. Elevation histogram: This tab sheet shows the elevation histogram with different colors depending on flight mode and a curve for the battery voltage of the copter. The elevation histogram is a bar chart with a bar for each data point, which has a colour depending on the flight mode (f_mode): - green: Smart mode (6, 21, 23), - purple: Angle mode (3, 4), - orange: ohne GPS (2, 5, 7, 22, 24), - blue: Stability mode (0, 1), - red: RTH und Agility mode (13, 14, 20), Q500log2kml, Version 2.8 02//2017 Page 7/17 - maroon: Error, Calibrations (9, 10, 11, 12, 17, 18). Because there are different time intervals between the data points, there may be gaps in the histogram between the bars. As overlay, there is a curve for the voltage of the flight battery. The colour of the curve has different meanings: - blue: real flight with GPS support, - red: real flight with GPS switched off, - grey: flight by simulator UAV-Pilot (identified by values in column 'current'). Context menu, called by right mouse button: - Copy to clipboard: Copy the picture of the elevation histogram to clipboard. - Save as picture...: The elevation histogram will be saved as *.png file. - Cursor on/off: Switches on/off a vertical line following the mouse pointer as cursor to navigate in the diagram. With the cursor you can select a data point as start for analysis. - Go to table: Opens the table with raw data and jumps to the selected data point. Data analysis: The analysis functionality is available at tables in "Display files" and at "Elevation histogram". The results will be displayed in the status bar at the bottom of the application window. Analysis at elevation histogram: Setting the cursor to 'on' in context menu (activated by right mouse button) and navigate to desired data point. Start analysis by click on left mouse button. Results will be displayed in status bar at the bottom. If the crtl-key is down when the left mouse button was clicked then the results will be copied to clipboard too. The selected data point will be taken over to the "Data point" field in the header of the application. This is then the start of the interval of data points defined in settings. This point can also be used as start point for analysis in table view (Display files). Following results will be shown: - time interval depending on number of data points for analysis defined in settings, - average climbing or sinking rate if delta in altitude is > 2m inside the interval, - distance between start and end point of the data interval, - length of trip covered by data interval, - average speed in the data interval. Analyse at data table: Start analysis by context menu with right mouse button. Start point is the selected data point in field "Data point". It can be set / changed by click on a cell in the table. The data interval depends on settings (the same as for analysis in elevation histogram). Output for telemetry data (Copter) is the same as described at Analysis at elevation histogram. Analysis of ST10 data (GPS of the ground station) gets the following results: - time interval depending on number of data points for analysis defined in settings, - average altitude over NN from GPS data, - length of trip of the ground station covered by data interval, - average speed of the ground station in the data interval. Analysis of RC connection data (Radio) gets following results: - time interval depending on number of data points for analysis defined in settings, - number of used channels (for ST10 it should be always 10), - number of used frequencies. Q500log2kml, Version 2.8 02//2017 Page 8/17 Settings: On tab sheet "Settings" it is possible to commission different parameter to define how the application works. Output files: All settings for file conversion to flight paths for Google Earth.  Format - .kml ---> Convert creates for each flight a *.kml file, which can be imported to Google Earth and many other map services. The file can be read and edited by any text editor  Format - .kmz ---> same as *.kml, but zipped.  Format - .gpx ---> Convert creates for each flight a *.gpx file, which can be imported to many map services or applications like Doarama. The file can be read and edited by any text editor  Format - dashw.csv ---> Convert creates *.csv files for Dashware import.  Format - .html ---> Convert creates a report file in HTML format documentation purposes. Flight track in KML/KMZ - Color ---> Set colour for the flight track in Google Earth. Flight track in KML/KMZ - Opacity ---> Set opacity for the flight track in Google Earth. Right is full opacity (=default). Flight track in KML/KMZ - Width ---> Set width for the flight track in Google Earth (default 3). Check save status during close? ---> Check if files are converted/saved when close the application or better not (default: no). All to Dashw ---> Export all data to DashWare (initialization, calibration, no GPS), not only from real flight modes (default: no). Q500log2kml, Version 2.8 02//2017 Page 9/17 Example created with settings above: Data analysis: Settings for data analysis in table or elevation histogram.  Speed in - m/s ---> Speed (vertical and horizontal) in meter per second (default).  Speed in - km/h ---> Speed (vertical and horizontal) in kilometres per hour.  Speed in - mph ---> Speed (vertical and horizontal) in miles per hour.  Number of data points for analysis ---> set how many data points (data interval) beginning with the selected start point will be checked. 50 data points are around 15 seconds flight time, but this may vary depending on firmware.  Distance between waypoints ---> sets the minimal distance between two sets of coordinates of flight path, where a new CCC waypoint will be set during conversion of telemetry to CCC waypoint file. Saved models: A string list for different aircrafts that deliver telemetry data. From this list, the related aircraft can be selected for "Copter-ID" to have the right one in the reports for documentation (see HTML report). Archiving: Set the format how the FlightLog directory will be renamed.  Date_Time ---> the suffix appended after "FlightLog" has the format YYYY-MM-DD_hhmmss.  Date ---> the suffix appended after "FlightLog" has the format YYYY-MM-DD.  POSIX time ---> the suffix appended after "FlightLog" is a POSIX time stamp (aka UNIX time – count of seconds since 1.1.1970 00:00h). Q500log2kml, Version 2.8 02//2017 Page 10/17 CCC Waypoints (development discontinued, no support): This tab sheet contains some functions to create, edit, delete and convert CCC Waypoint files. Currently those CCC Waypoints are only supported by Yuneec Typhoon H/ST16. Load WP: Import waypoints from different sources to display a symbolic diagram (this green display field) with those waypoints. Note: The diagram is no map, scale and x/y deformation depends on the imported data. There is also a list of waypoints with the direct distance to the previous waypoint, where you can select/deselect single or a couple of waypoints for operation. Double click on this list toggles the selection. There are three sources for waypoint files:  CCC waypoints from ST16 – previous recorded with your Yuneec Typhoon H and saved as plain text file (Java type C pseudo code).  GPX file, created by a web-based map service like www.geoplaner.com. You can call GeoPlaner with context menu of the green display field (right mouse button).  Telemetry data from a Yuneec copter – you can repeat a former flight, using the telemetry file, which will be converted to CCC waypoint file format. New waypoints will be created when the distance between two coordinates exceeds a predefined threshold. Play around with this threshold to find a good compromise between number of waypoints and accuracy of the flightpath. You can also drag a flight number from the list of telemetry data at the left side to the display field and drop it there to convert it to CCC waypoints. Move WP: The first selected waypoint will be moved to the new position. All following selected waypoints will be moved too, but relative to the first one. Single waypoints can be moved with mouse. To do this, hold CTRL key and left mouse button. With CTRL key and Arrow keys all selected waypoints can be moved stepwise in the related direction. With CTRL key and + or – the altitude of all selected waypoints can be increased/decreased by 1m. Q500log2kml, Version 2.8 02//2017 Page 11/17 Insert WP: A new waypoint will be inserted at the position, given by coordinates in the sequence according its waypoint number. Default is, to insert it at the end. The new waypoint inherits its other parameter from the previous waypoint. The parameter can be set and tuned manually. New coordinates for “Move WP” and “Insert WP” can be grabbed in the following ways:  Mouse click With CTRL key and left mouse button on the green display field.  Get coordinates from OpenStreetMap (set marker on map, copy the link address).  Manual input to „Lon“ and „Lat“. To edit a waypoint, double click with left mouse button on the waypoint on the display field. You can manually edit the parameter of the waypoint. With Delete WP the waypoint and all its parameter will be deleted. OK takes over the settings; Cancel withdraws the setting and keep the old one. Save WP: Edited waypoints will be saved as CCC waypoint file for import to ST16. Per default, the target directory is the same as the source directory. It is also possible to convert CCC waypoint files either to GPX or KML/KMZ file format by button Convert. The target file format is defined in settings. Only coordinates and elevation above ground will be converted, all other parameter will be ignored during conversion. Note: Use the CCC waypoints on your own risk! Planning of a automated flight needs great attention. Especially check values for Altitude carefully. Most of the map services give altitude above sea level but copter needs altitude relative to his start point. Q500log2kml, Version 2.8 02//2017 Page 12/17 Appendix Error Flags (set bitwise): Bit 7 6 5 4 3 2 1 0 Error Flag ERROR_FLAG_AIRPORT_WARNING ERROR_FLAG_FLYAWAY_CHECKER_WARNING ERROR_FLAG_COMPASS_CALIBRATION_WARNING ERROR_FLAG_HIGH_TEMPERATURE_WARNING ERROR_FLAG_COMPLETE_MOTOR_ESC_FAILURE ERROR_FLAG_MOTOR_FAILSAFE_MODE ERROR_FLAG_VOLTAGE_WARNING2 ERROR_FLAG_VOLTAGE_WARNING1 Value * 128 64 32 16 8 4 2 1 * Note: If more than one error flag is set, then the sum of value is displayed in the telemetry data (Example: 33 = ERROR_FLAG_COMPASS_CALIBRATION_WARNING and ERROR_FLAG_VOLTAGE_WARNING1). Vehicle types: Value 1 2 3 4 5 Vehicle Type 1 = Yuneec H920 2 = Yuneec Q500 3 = Blade 350QX 4 = Blade Chroma (380QX) 5 = Yuneec Typhoon H Meaning of the columns in the raw data tables: Column header Telemetry (Copter) Description Unit Status Date / Time Date / time including milliseconds JJJJMMTT hh:mm:ss:zzz checked fsk_rssi Received Signal Strength Indication from copter’s receiver dBm supposed V checked supposed for H920 checked checked checked voltage current altitude latitude longitude Voltage off light accu Current of flight accu, if sensor available (not for Q500 or Typhoon H) Ascent relative to start point Latitude - GPS coordinates of copter Longitude - GPS coordinates of copter dA m decimal degrees decimal degrees tas True Air Speed, Speed of the aircraft, computed from GPS coordinates I guess. So it is m/s groundspeed, not really TAS. gps_used fix_type satellites_num roll yaw pitch GPS usage (true, false) GPS Fix Type Number of detected satellites Roll (see Wiki Roll-Nick-Gier) Gier (see Wiki Roll-Nick-Gier) Nick (see Wiki Roll-Nick-Gier) motor_status Motor Status, bitwise. Motor numbers according bits the picture in the GUI Q500log2kml, Version 2.8 02//2017 boolean ? number ° ° ° checked checked checked supposed supposed supposed supposed Page 13/17 Column header Telemetry (Copter) Description Unit Status imu_status IMU Status (inertial measurement unit – see Wiki) bits supposed gps_status cgps_used press_compass_status f_mode gps_pos_used vehicle_type error_flags1 GPS unit status C-GPS (unknown meaning) Sensor status (Barometer, Magnetometer) Code for different flight modes (see table below) GPS position used (true, false) Copter type Error flags, bitwise bits ? bits code boolean code bits supposed gps_accH Horicontal GPS accuracy. Seems to be HDOP (see Wiki - GPS HDOP) HDOP supposed Date / time including milliseconds JJJJMMTT hh:mm:ss:zzz checked decimal degrees checked decimal degrees checked m ? supposed supposed checked checked checked checked RemoteGPS (STxx) Date / Time lon lat alt accuracy Longitude - GPS coordinates of the ground station Latitude - GPS coordinates of the ground station Height from GPS relative to sea level Accuracy of GPS? speed Speed, unknown source (maybe computed from ? GPS coordinates), unknown unit angle Angel of moving direction to north? ° supposed Remote (Funk) Date / Time Date / time including milliseconds CH0 Channel 1: J1 throttle/ascent (thr) CH1 CH2 CH3 Channel 2: J4 roll (ail) Channel 3: J3 nick (ele) Channel 4: J2 yaw (rud) CH4 Channel 5: S4 Flight mode CH5 Channel 6: A02 - RTH CH6 Channel 7: K2 Camera tilt CH7 CH8 Channel 8: K1 Camera pan Channel 9: S1 Gimbal Tilt Mode CH9 Channel 10: S2 Gimbal Pan Mode CH10 Channel 11: S5 Landegestell CH11 CH12 CH13 CH14 CH15 CH16 CH17 CH18 Channel 12: A08 Channel 13: A09 Channel 14: A10 Channel 15: A11 Channel 16: A12 Channel 17: A13 Channel 18: A14 Channel 19: A15 Q500log2kml, Version 2.8 02//2017 JJJJMMTT hh:mm:ss:zzz 0=Motor start/stop (B3) 2048=neutral 2048=neutral 2048=neutral 2048=neutral 3412=Smart 2048=Angle 683=RTH 2048=neutral 4095=RTH 683=horizontal (0°), 3413=vertical down (-90°) A=2184, V=3412 F=683, Center=1502, G=3412 0.0=up 1.0=down checked checked checked checked checked checked checked checked checked checked supposed checked Page 14/17 Column header Telemetry (Copter) CH19 CH20 CH21 CH22 CH23 Description Unit Status Channel 20: A16 Channel 21: A17 Channel 22: A18 Channel 23: A19 Channel 24: A20 * Note: Channel assignment is only valid for ST with Mode 2, for ST16 assignment can be changed by user. Also the mode of the may be changed by user, which changes assignment to throttle, yaw, roll and pitch accordingly. Yuneec Breeze raw data: Column header FlightLog UTC TimeStamp flightMode distance height loseGPSAct goHomeHeight maxHeight maxDistance maxSpeed alt IMU_Sta lat lon AutoTakeOFF roll pitch yaw motorStatus errorFlags nsat voltage Description Unit Status Timestamp Timestamp number Flight Mode Distance Standard height Fail Save Action RTH hight Geo fence Maximum Hight Geo fence Maximum Distance Maximum Speed Altitude IMU Status Coordinates, Latitude Coordinates, Longitude Flight rule Roll angle Pitch angle Yaw Motor Status Error Flags YYYY-MM-DD hh:mm:ss 53 3 dm dm 1 dm dm dm m/s * 100 cm -17 518800483 63090397 0 308 344 -8495 15 0 Signed decimal + GPS Fix Flag 249 UTC or Time zone? Number satelites, GPS fix LiPo voltage supposed supposed supposed supposed supposed supposed supposed supposed unknown Flight Modes: f_mode class FModeData Q500 / Typhoon H String 0 FMODE_BLUE_SOLID Stability mode (Blue solid) THR 1 FMODE_BLUE_FLASHING Blue flashing THR 2 FMODE_BLUE_WOULD_BE_SOLID_NO_GPS Blue, no GPS THR 3 FMODE_PURPLE_SOLID Angle mode (Purple solid) Angle 4 FMODE_PURPLE_FLASHING Purple flashing Angle 5 FMODE_PURPLE_WOULD_BE_SOLID_NO_GPS Angle mode (Purple solid) - no GPS Angle 6 FMODE_SMART Smart mode Smart 7 FMODE_SMART_BUT_NO_GPS Smart mode - no GPS Angle Q500log2kml, Version 2.8 02//2017 Page 15/17 f_mode class FModeData Q500 / Typhoon H 8 FMODE_MOTORS_STARTING Motor starting String Start 9 FMODE_TEMP_CALIB Temperature calibration 10 FMODE_PRESS_CALIB Pressure calibration Pre Cali Temp 11 FMODE_ACCELBIAS_CALI Accelerator calibration Acc Cali 12 FMODE_EMERGENCY_KILLED Emergency/Killed EMER 13 FMODE_GO_HOME RTH coming Home 14 FMODE_LANDING RTH landing Land 15 FMODE_BINDING Binding 16 FMODE_READY_TO_START Initializing, Ready to start Ready 17 FMODE_WAITING_FOR_RC Waiting for RC No RC 18 FMODE_MAG_CALIB Magnetometer calibration 19 FMODE_UNKNOWN Unknown mode 20 FMODE_RATE Agility mode (Rate) 21 FMODE_FOLLOW Smart mode - Follow me 22 FMODE_FOLLOW_NO_GPS Smart mode - Follow me - no GPS 23 FMODE_CAMERA_TRACKING Smart mode - Camera tracking 24 FMODE_CAMERA_TRACKING_NO_GPS Camera tracking - no GPS 26 FMODE_TASK_CCC Task Curve Cable Cam CCC 27 FMODE_TASK_JOUR Task Journey JOUR 28 FMODE_TASK_POI Task Point of Interest 29 FMODE_TASK_ORBIT Task Orbit 32 ? Indoor Positioning System Bind Mag Cali Rate Follow THR Watch THR POI ORBIT IPS Continuation Flight Modes (Blade 350QX: found by try and error): f_mode Chroma (380QX) String Blade 350QX 0 Stability mode (Blue solid) Stab 1 Blue flashing Stab 2 Blue, no GPS Stab 3 Angle mode (Purple solid) AP Waiting for RC 4 Purple flashing AP Initializing 5 Angle mode (Purple solid) - no GPS AP Motor starting 6 Smart mode 7 Smart mode - no GPS 8 Motor starting Smart AP Start Emergency Temp RTH landing 9 Temperature calibration 10 Pressure calibration Pre Cali Agility - no GPS 11 Accelerator calibration Acc Cali Stability 12 Emergency/Killed EMER Smart Mode 13 RTH coming Home Agility Mode 14 RTH landing Land RTH coming 15 Binding 16 Initializing, Ready to start Ready 17 Waiting for RC No RC 18 Magnetometer calibration 19 Unknown mode 20 Agility mode (Rate) 21 Smart mode - Follow me Follow 22 Smart mode - Follow me - no GPS Follow 23 Smart mode - Camera tracking Track 24 Camera tracking - no GPS Track Q500log2kml, Version 2.8 02//2017 Bind Magnetometer calibration Mag Cali Agil Binding Page 16/17 f_mode Chroma (380QX) String 25 Blade 350QX AP Mode Thresholds / color coding: Meaning Poor Reasonable Good Color Date/time fsk_rssk Red >2s >85 Light red 600ms-2s 70-85 Light green 55-70 Very good Green <55 Maximum values Yellow gps_accH >2,5 1,8-2,5 1-1,8 <1 Short description – Prepare telemetry for Dashware: Step 1: Prepare Dashware (only once the first time): - download and install latest Dashware from http://www.dashware.net/dashware-download/ - download profile "Yuneec Q500 v1.5" from http://www.drohnen-forum.de/index.php/Thread/12303-ST2Dash-der-Flightlog-Konverterf%C3%BCr-die-ST10-Q500/ - unzip "Yuneec Q500 v1.5.xml" and copy it to the Profile directory of Dashware: %HOMEPATH%\Documents\DashWare\DataProfiles\ - restart Dashware. Now the new profile for Yuneec telemetry data from ST2DASH or q500log2kml is available every time you use Dashware. Done. Step 2: Convert telemetry file to Dashware format that fits the profile: - download and install "q500log2kml" from here: http://h-elsner.mooo.com/downloads/q500log2kml_en.zip - read the description (OK, this you have done at this point) - select Data conversion output format "dashw.csv" in tab "Settings" - convert all the telemetry data of real flights in one step to Dashwarefiles by click on Convert Step 3: Use video files and fitting converted Dashwarefile (i.e. Telemetry000xxdashw.csv): - start Dashware - create a new project - add one or more video files (I guess Dashware cannot use 4k videos, it must be downsized) - add converted Dashwarefile (i.e. Telemetry000xxdashw.csv) as data logger file - select "Yuneec Q500 v1.5" as relating profile - synchronize telemetry/video and do all the stuff that you want to do with your project... Q500log2kml, Version 2.8 02//2017 Page 17/17