Open ecmnet opened 2 years ago
These are messages coming from the CAN device with node id 125. For the CAN nodes I work with (mainly running PX4) I'm careful to not spam output, but I'm not sure what this is running (hereflow?).
I could add a parameter like UAVCAN_SUB_LOGMSG
so you could have control over the subscription.
Yes, it’s hereflow.
Separately maybe we could ask the manufacturer to add a mechanism on the node to silence this output in the future? @proficnc @bugobliterator
@ecmnet @dagar I have updated the firmware for HereFlow to not publish these messages, please update your hardware with the latest firmware that can be installed using following steps: https://docs.cubepilot.org/user-guides/here-3/here-3-manual#2.-here-3-here-3+-firmware-upgrade the software version that should appear after update is
1.1.9B687E2 |
Thanks @bugobliterator.
On PX4 you can simply place the CAN firmware .bin file on the flight controller SD card and the UAVCAN firmware server will grab it and handle the node upgrade.
@bugobliterator Any direct link to the firmware .bin file?
@bugobliterator Any direct link to the firmware .bin file?
@bugobliterator Thanks a lot for the link. However, either the update did not work (as described above for PX4) or the update worked but did not solve the issue.
@bugobliterator Thanks a lot for the link. However, either the update did not work (as described above for PX4) or the update worked but did not solve the issue.
Can you ensure the firmware version is correct 1.1.9B687E2
Now that I think of I'm not sure if the PX4 UAVCAN firmware server logic that finds the .bin on the SD card works with the ardupilot CAN appdescription.
If I can find some hardware I'll take a look.
As I have no (and cannot install) MissionPlanner, I am limited to the Nutshell console of QGC. UAVCAN status
gives very little information regarding the FW or the update process currently. I also ran UAVCAN update
but got no output.
You can use the Dronecan GUI to install the update as well.
UAVCAN messages spam mavlink shell as well as ULOG messages in 1.13.0: