-
Notifications
You must be signed in to change notification settings - Fork 14.6k
uavcan: add node status logging to uORB #23890
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
5f7c105
to
d9d936e
Compare
@vertiq-jordan let me know what you think |
Looks good on my end! Here's a couple of quick captures of one of our nodes going through the different health cases: Here's a sanity check that everyone is reporting the correct Node ID/they're being logged: I'll get on the Extended ESC Status PR shortly, thank you! |
I do quite like this, we just need to make it fit. |
d9d936e
to
339824f
Compare
This pull request has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there: |
Co-authored-by: Jordan Leiber <jordan.leiber@vertiq.co>
339824f
to
5ec1274
Compare
Rebasing, we will check back once the FLASH report is done. |
@mrpollo flash report is failing. Does it only work with branches from this repo? |
It's running so often that it's reaching max usage limits for the GitHub api, same is happening with the container action. I think we are going to have to stop auto comments until we figure out a solution. |
I'm worried this 700B is going to push px4_fmu-v6x over the edge.. |
Might I suggest that we kill the vertiq_io module from the board defaults? I believe that right now the v6x defaults file is the only one that has our module enabled. We have fairly detailed documentation on our end for building from scratch with our stuff enabled for any board, so I'd be ok killing it as a default option. Should save a couple K. |
Looks like it's the 6c that has the vertiq module, so that won't help unfortunately. @mrpollo does anyone "own" V6X? It would be nice to have an owner of the target who can keep the flash usage under control and make the executive decisions about which modules to support. |
FMUv5X
FMUv6X
|
@dakejahl For the common px4/fmuv_5x and px4/fmu_v6x targets we don't have owners but the devs who have been helping out and are most interested in keeping them sane are @niklaut @davids5 @dagar and myself. I think flash wise we should so far we have been dealing with issues when they come and disabling modules based on what seems right at the moment, once we move to a per vehicle type build we shouldn't be running into this anymore, but until then, we should look into how to improve this ad-hoc process. |
Initial implementation taken from #23882 but reimplemented using the existing interface. This adds ~700B to flash for the extra data in

NodeStatus
but I think it's worth it