dvl-a50: mavlink2resthelper: fix incorrect IDs #31
Conversation
- `system_id` set to match the vehicle ID, since they should be part of the same system - `component_id` set to 197 (`MAV_COMP_ID_VISUAL_INERTIAL_ODOMETRY`)
|
@ES-Alexander I will work on testing this in-water over the next few weeks. |
|
@clydemcqueen did you ever get around to testing this? :-) |
|
@ES-Alexander Sadly, we did not. I'll see if I can schedule some test time w/ a DVL-rigged ROV. |
|
@ES-Alexander -- sorry, testing this (and PR 34) is just not making it to the top of the queue. We have limited time to run these sorts of tests on real hardware, and the test process is cumbersome (creating a docker image per PR, installing them, etc.) Are there plans to create BETA and DEV tracks for extensions? We always run the latest ArduSub BETA on production dives (to get surftrak and other nifty features). I think it would be straightforward to switch to the BETA track of this extension, if such a thing existed. |
system_idset to match the vehicle ID, since they should be part of the same systemcomponent_idset to 197 (MAV_COMP_ID_VISUAL_INERTIAL_ODOMETRY)Fixes #30
Untested, so probably good if someone can try it before it gets merged.