Skip to content
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

[DO NOT MERGE] CI test for UAVCAN SensorBridge Improvements #14424

Closed
wants to merge 10 commits into from

Conversation

MaEtUgR
Copy link
Member

@MaEtUgR MaEtUgR commented Mar 19, 2020

Describe problem solved by this pull request
Just trying to run CI with a rebased version of #14345

Describe possible alternatives
I tried just creating a branch prepending pr- but it only runs two tests and seems to try and fetch the branch that was pushed before the one it should be testing...

JacobCrabill and others added 10 commits March 19, 2020 09:32
UavcanGnssBridge did not support more than 1 GNSS callback/publisher.
This has now been fixed; it works the same as the baro, mag, and flow
sensor bridges.  The EKF2 still doesn't support more than 2 GPS
publishers, however.
Can now see proper UAVCAN bus and unique device ID for barometer
instances; optical flow will also have the UAVCAN node ID assigned as
sensor ID.
Supposedly multiple sensor callbacks were supported; in reality, this
was not the case, and additionally what is there is not well
implemented.

This work is still WIP but appears to allow calibration of multiple
compasses connected via UAVCAN.
For print_status() purposes only.
+ Fixed baro bridge's use of /dev/baro for driver registration; named it
/dev/uavcan/baro instead
+ Other cleanup
Use absolute-zero constant instead of 273.15f

Co-Authored-By: Daniel Agar <daniel@agar.ca>
Also add new 'generic' device types for UAVCAN sensors
@MaEtUgR MaEtUgR closed this Mar 19, 2020
@dagar dagar deleted the pr-can-sensors2 branch April 7, 2020 04:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants