Closed JacobCrabill closed 4 years ago
Can you describe your test setup? I just tested this on a Pixracer with a GPS attached and everything works as expected.
Hmm. Using commit 2b82b471? I'll give that another try.
Yup whatever the latest commit is
Still doesn't work for me; I just get this in the UAVCAN GUI when connected to a Babel:
It stays in the "INITIALIZATION" mode for a second or two then goes away. And now after a few minutes, it's no longer rebooting itself at all is doesn't appear on the CAN bus at all.
Using an mRobotics Pixracer; brand-new purchase from last week.
Oh, interesting. I removed the micro-USB cable, replug the CAN cable, and now it works 🤔
Somewhere the handling of USB power on this must have changed. All of my prior testing has been with just leaving the USB cord plugged in.
At any rate, it's looking good now!
Do you have a FTDI to hook into the console? The USB cable being plugged in should make no difference, I've got mine plugged in with a USB as well.
I do; which connector/pins expose the console on the Pixracer?
It's part of the pixhawk debug port https://dev.px4.io/v1.9.0/en/debug/system_console.html
Ah, I see it. I have a DroneCode Probe; I'll give that a try later when I have time.
Well I rebased @dakejahl's airspeed branch on top of master (actually this branch here: https://github.com/volans-i/Firmware/tree/pr-uavcan-airspeed) and it all works now 🤷♂️
Sometime recently the cannode build target for the Pixracer (fmu-v4) was broken. It will boot, but upon connecting a Zubax Babel board to the CAN port, the Babel will show that the cannode gets stuck in an infinite reboot loop. It will briefly show up as initializing, then power off and disappear from the UAVCAN GUI, show up again as initializing, etc.
This commit still works: pull/14444/d14fc944
But as of last Friday at least (and I tried yesterday as well) master does not work.
@dakejahl