PX4 / PX4-Autopilot

PX4 Autopilot Software
https://px4.io
BSD 3-Clause "New" or "Revised" License
8.17k stars 13.36k forks source link

UAVCAN v0 Node Issue Tracker and Discussion #16942

Open mrpollo opened 3 years ago

mrpollo commented 3 years ago

The following Issue is an effort to continue tracking the discussions and progress of the UAVCAN v0 Node.

The CAN Node for v0 support has been in the codebase for a while, without much use until now, the developer team has put an extra effort to bring it back to full support, and is currently testing it with hardware from different vendors Including CUAV, Holybro, and NXP, all of which will be releasing hardware in the near future with UAVCAN v0 support using the PX4 CAN Node

The project is being led by @davids5 and @LorenzMeier, with the help from @dagar

Progress Tracking

Hardware Support

Manufacturer Type Hardware Build Name Bootloader Apps Status Contributors
CUAV Peripheral NEO v3 PRO cuav_can-gps-v1 Verified running, needs testing from manufacturer @davids5
Holybro Peripheral Unreleased holybro_can-gps-v1 Verified running, needs testing from manufacturer @davids5
NXP Peripheral UCANS32K146 nxp_ucans32k146 ✅* Runs uavcannode_gps_demo, Testing with FMUK66, testing GPS and PNP automatic @davids5 & @PetervdPerk-NXP
Holybro Peripheral Pixhawk 4 px4_fmu-v5_uavcanv0periph TODO @davids5
mRo Peripheral Pixracer TODO TODO @JacobCrabill

* Runs uavcannode_gps_demo

Relevant PRs

The PX4 cannode bootloader resurrection (Merged) https://github.com/PX4/PX4-Autopilot/pull/16554

UAVCAN Node Register/Parameter Server (Merged) https://github.com/PX4/PX4-Autopilot/pull/16649 https://github.com/PX4/PX4-Autopilot/pull/16595

S32K can bootloader (Merged) https://github.com/PX4/PX4-Autopilot/pull/16879

NOTE: This Issue is superseding the project card previously found on the Roadmap Project Tracker for the PX4 Autopilot.

igalloway commented 3 years ago

@mrpollo - what do you mean by Hardware Support - "working" The UCANS32K146 software is working well. It was just the bootloader(s) left to do. The CAN bootloader has a PR now (as you have noticed.

mrpollo commented 3 years ago

hey @igalloway It was a reference to the bootloader PR from @davids5, we got it merged :)

igalloway commented 3 years ago

Super! Thanks

On Wed, Feb 24, 2021, 2:21 PM Ramon Roche notifications@github.com wrote:

hey @igalloway https://github.com/igalloway It was a reference to the bootloader PR from @davids5 https://github.com/davids5, we got it merged :)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/PX4/PX4-Autopilot/issues/16942#issuecomment-785277358, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACQFV7SXUICITHJKQBX7PN3TAU7UNANCNFSM4YD2J6SA .

mzahana commented 3 years ago

@mrpollo I faced this issue (https://github.com/PX4/PX4-Autopilot/issues/17004) And I thought it's related. I hope to get some help on that.

Thanks!

mrpollo commented 3 years ago

Thanks for the report @mzahana, I replied to your issue, it seems unrelated.

ghost commented 3 years ago

Which release/commit introduced RGB-LED support?

mrpollo commented 3 years ago

@fnax8902 LED support was added to the CUAV Neo v3 PRO through various commits, but the gist of it is on this commit https://github.com/PX4/PX4-Autopilot/pull/16554/commits/a96fafffd8b3ee8116d46cb488cf7ce0429fa1be

davids5 commented 3 years ago

That is just the original bootloader one and it was replaced, with https://github.com/PX4/PX4-Autopilot/pull/16619

ghost commented 3 years ago

RGB LED is working with the Here 3 GPS using current master, thank you!

mzahana commented 3 years ago

@fnax8902 Which autopilot hardware did you use? Would it work on the Orange Cube?

ghost commented 3 years ago

I do have a holybro pix32 and according to the ulg-file I'm using "PX4_FMU_V3 (V2)".

julianoes commented 1 year ago

I would assume this can now be closed?

dk7xe commented 1 year ago

I would assume this can now be closed?

What about the uORB messages?

julianoes commented 1 year ago

@dk7xe what exactly is to do there, is there a use case that requires it? I feel like it would have been implemented if it was important, right?