kenyuneec / mavgcl

In-Flight Analysis for PX4

MAVGAnalysis

In-Flight/PX4Log/ULog Analyzer for PX4

This JavaFx based tool enables PX4 Users to record and analyse data published via UDP during flight or offline based on PX4Logs or ULogs. It is not intended to replace the QGC.

Any feedback, comments and contributions are very welcome.

Development Status: Last updated 30/10/2016

• Available as pre-release
• MAVLink 2.0 compatibility
• UDP MAVLink logging: in progress
• UDP connection reliability and performance improved
• Performance optimizations

Note, that developer builds require MAVLink 2.0 protocol without signing

Features:

• Realtime data acquisition (50ms sampling) based on MAVLink messages
• Timechart annotated by messages (MAVLink and ULog) and parameter changes (MAVLink only)
• Trigger recording manually or by selectable flight-mode/state changes with adjustable stop-recording delay
• Display of key-figures during and after recording (with 'Replay')
• XY Analysis for selected key-figures
• MAVLink inspector (reporting raw MAVlink messages)
• MAVLinkShell provides NutShell over MAVLink (Console)
• Easy to use parameter editor and In-Flight-Tuning-Widget
• Map viewer of global position and raw gps data with option to record path (cached)
• Offline-mode: Import of key-figures from PX4Log/ULog (file or last log from device via WiFi)
• Save and load of collected data
• Import of Custom KeyFigureMetaDataFiles allows to define use-case specific collections of key-figures.
• Key figure conversion based on expressions
• FrSky Taranis USB supported in SITL
• Low latency MJPEG based video stream display based on uv4l or any other source
• Virtual (calculated) key figures added (Example here: default definition file)

Requirements:

• requires Java 8 JRE
• A companion running a serial-to-udp-proxy (either MAVComm or MAVROS, not required for PIXRacer)
• Video streaming from the vehicle requires an mjpeg streaming service (e.g. uv4l) running on companion

Binaries:

Binaries can be found here.

Screenshots:

How to build on OSX (other platforms may need adjustments in build.xml):

• Clone repository
• Goto main directory cd MAVGCL-master/MAVGCL
• Run ant all

How to start after build (all platforms):

• Goto directory /dist

• Start with java -jar MAVGAnalysis.jar

• Set IP address and port in File->Preferences and restart (For local SITL use 127.0.0.1:14556 or start with java -jar MAVGAnalysis.jar --SITL=true)

• Open demo_data.mgc, import PX4Log file or collect data directly from your vehicle

• For video (mjpeg), setup uv4l at port 8080 on your companion with : ​ uv4l --auto-video_nr --sched-rr --mem-lock --driver uvc --server-option '--port=8080'

  Set video URL in File->Preferences: e.g. http://127.0.0.1:8080/stream/video.mjpeg

  or

  run MAVSlam vision based on Intel® RealSense™ R200 on your companion and point video to port 8080 of your companion.

  ​

How to deploy on OSX:

• Run ant_deploy

How to define custom key-figure metadata files:

• Refer to example file or default definition file
• Conversion based on expressions ( exp4j ). Example: <Converter class="ExpressionConverter" expression="1.5 * sin(val)"/>

How to map custom MAVLink messages to key figures

Currently a direct mapping of MAVLink messages to keyfigures is not possible. Instead you have to generate the java class of the message and map it to the key figure:

1. Clone https://github.com/ecmnet/MAVComm and add the MAVLink definition in https://github.com/ecmnet/MAVComm/blob/master/MAVComm/mavlink/lquac.xml

   This creates the java class of the custom message and adds it to mavcomm.jar

2. Build mavcomm.jar with ant build_mavcomm and replace the one used by MAVGCL

3. Map a keyfigure definition to the created java class in the default definition file like this

 <KeyFigure desc="MAVLINK Test" uom="" mask="#0.0" key="MAVLINK">
		<MAVLinkSource class="msg_altitude" field="altitude_amsl"/>
		<Validity min="0.1" max="1000.0"/>
		<Groups>
			<Group>Custom mavlink messages</Group>
		</Groups>
  </KeyFigure>

Limitations:

• Limited to one device (MAVLink-ID '1')
• Currently does not support USB or any serial connection (should be easy to add, so feel free to implement it). Note: Serial via radio might be too slow.
• Default PX4Log/ULog keyfigure mapping still not complete, but you can add your own definition file

Note for developers:

MAVGAnalysis depends heavily on https://github.com/ecmnet/MAVComm for MAVLink parsing.

Please note the License terms.