Hi @andrewkwolek -
PingViewer would not be possible to run onboard the vehicle, so is not likely a good approach for anything but logging data on a connected topside computer. This specific example should have the bones of what you need to ingest the data into your extension! Ping-python can be used separate from BlueOS, but no reason it can’t be used running within an extension onboard - that’s kind of the whole idea! There have been quite a few posts on the forum working thru parsing the ping360 data if you get stuck.
A good check for parameters is to navigate to Available Services, and checkout the link to Mavlink2Rest as mentioned previously. Scaled_IMU2 seems to only hold x,y,z magnetometer data. It’s likely best to use AHRS2 as this contains the already filtered/ processed orientation data, rather than the raw values.
If you’re running BlueOS beta, you can switch to MavlinkServer (under Mavlink Endpoints, at the top) and have a much more powerful view of data:
