You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hello!
I have a pixhawk cube and a motor and motion controller which communicate via can open.
I want to connect the to the pixhawk but i know that pixhawk supports only uavcan.
tried to find any documantation on the internet but couldnt find somthing good.
I was wondering if there is a way to convert uavcan to can open so the pixhawk could communicate withe the motion controller and the motor.
Thanks!
The text was updated successfully, but these errors were encountered:
Can you share specifics about the particular motor? Are interface details publicly available?
I'm very much in favor of making it easier to use the system with multiple different CAN protocols. We're looking at moving most of the system over to SocketCAN so that the CAN driver isn't so tightly integrated with UAVCAN. For now there are simple examples like https://github.com/PX4/PX4-Autopilot/blob/master/src/drivers/tattu_can/TattuCan.cpp that show how to use the NuttX CAN driver directly (you have to manually disable UAVCAN first).
I dont have any specifices on the motor and the motion controller.
I tought about the option to combine between motors with can open and pixhawk.
I saw on the internet some kinds of brushless dc motors that operate withe can open/
It's definitely possible, just don't expect it to be plug and play. Often those CAN messages are vendor proprietary so we'll have to take a closer look.
hello!
I have a pixhawk cube and a motor and motion controller which communicate via can open.
I want to connect the to the pixhawk but i know that pixhawk supports only uavcan.
tried to find any documantation on the internet but couldnt find somthing good.
I was wondering if there is a way to convert uavcan to can open so the pixhawk could communicate withe the motion controller and the motor.
Thanks!
The text was updated successfully, but these errors were encountered: