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. It is not tested with ardupilot.
Any feedback, comments and contributions are very welcome.
Development Status: Last updated 24/01/23
- Auto loading of custom keyfigure definition files from a dedicated directory at startup
- Autosave into result directory requests and saves DMESG output
- Multiple videostreams
- Videostream replay (if video found in result directory)
- 3D View reworked
Note: 3D map data can be transferred to MAVGCL using the custom MAVLink message msg_msp_micro_grid - for encoding refer to MAP3DSpacialInfo.java
See MAVGCL some action:
- 3D View: https://youtu.be/9CRZ7D_caTo (2023)
- Video replay: https://www.youtube.com/watch?v=liEKiAzEZ5Y (2022)
- XY View: https://youtu.be/jOWNSIwIA9k (2018)
Features:
- Realtime data acquisition (20ms sampling, 100ms rolling display) based on MAVLink messages or ULOG data over MAVLink
- Timechart annotated by messages (MAVLink and ULog) and parameter changes (MAVLink only)
- XY Analysis for selected key-figures
- FFT for selected keyfigures
- 3D View (vehicle and observer perspective)
- MAVLink inspector (reporting raw MAVlink messages)
- Zooming (Click&Drag), pause / continue rolling update while continue recording in the background
- MAVLinkShell provides NutShell over MAVLink (Console)
- Map viewer of global/local position and raw gps data with option to record path (cached)
- Offline-mode: Import of key-figures from ULog (file or last log from device via WiFi)
- Save and load of collected data
- Key figure conversion based on expressions
- FrSky Taranis USB supported in SITL
- PS4Controller support in OSX
- Low latency MJPEG based video stream display based on uv4l or any other source
- Video stream recorded as H264/MP4 file while collecting data
- Virtual (calculated) key figures added (Example here: default definition file)
- RTCM3 base supported with automatic survey-in for UBlox devices (OS X only)
Note that some features (MSP) are only available if you run a companion on your vehicle using MAVComm .
Requirements:
- requires minimum Java 11 JRE
- A companion running a serial-to-udp-proxy (either MAVComm or MAVROS, not required for PIXRacer)
- Video streaming from the vehicle requires an rtps mjpeg streaming service running on companion
Note: maven building currently requires local mavcom, mavmap, mavbase and mavutils in local repository
Binaries:
Available binaries can be found here.
Screenshots (Light Theme):
Screenshot (Dark Theme):
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)"/>
Limitations:
- Limited to one device (MAVLink-ID '1')
- Default PX4Log/ULog keyfigure mapping still not complete, but you can add your own definition file
Note for developers:
MAVGAnalysis depends on https://github.com/ecmnet/mavcom for MAVLink parsing.
Please note the License terms.