DroneCAN Startup Conflict Between Here3 GPS and Holybro DLVR Pitot

ArduPlane Plane 4.5
1

Cube Orange - Arduplane 4.5.7

DroneCAN bus on [can2]: 3× CAN servos, Here3 , Holybro DLVR pitot (DLVR-F50D)

When the Here3 and the Holybro DLVR pitot are powered up together on the same bus, they consistently fail to initialize properly.
Their Node ID’s are configured for there to be no conflicts. Most of the bus comes up fine, but between these two devices something goes wrong, usually the pitot’s node ID appears, it struggles to communicate on the bus (uptime getting stuck). After boot, if I disconnect one of the two and reconnect it, both work fine and everything gets sorted.

  • For some reason this only happens at baudrates below 1 Mbps. At 1M they start normally, but I don’t want to configure the bus to that speed. This doesn’t happen with Mateksys’ pitot instead of Holybro’s.

What could be the cause and how can I make them initialize properly?

2 Likes
2

That’s weird, it looks like one of the devices somehow gets wrong bus rate or something like that. If the device has an available USB or serial port you could try connecting to the node directly using MAVLink (after configuring the serial port for it).

3

I’m not sure that’s it, because each device separately communicates with the bus just fine on the baudrate I’ve configured for it - 250k. Something about these two devices together leads to problems even though they have different node id’s.

4

Have you try CAN_D2_OPTION first and secound bit ?

5

Yes, I’ve tried each bit and both together, doesn’t affect the problem.