tridge on master
protocol: replace unsupported %… (compare)
tridge on master
Add override keyword to those m… (compare)
peterbarker on override-keywords
Add override keyword to those m… (compare)
tridge on pr-header-conflict-ch
tridge on master
marshal: fixed header conflict … (compare)
OXINARF on fix-python-37
OXINARF on pr-STM32H7-support
OXINARF on master
stm32: support ChibiOS kernel m… dsdl_compiler: add missing sheb… dsdl_compiler: remove trailing … and 1 more (compare)
OXINARF on fix-python-37
dsdl_compiler: add missing sheb… dsdl_compiler: remove trailing … dsdl_compiler: check for StopIt… (compare)
tridge on pr-STM32H7-support
stm32: support ChibiOS kernel m… (compare)
OXINARF on ardupilot-2018-06-09
OXINARF on pr-chibios-update
OXINARF on allow-can2-without-can1
Hi All, I have a question re. examples/UAVCAN_sniffer...
I currently have access to a a cube, which is able to run uavcan_gui_tool
bus monitor and dump the traffic that way. But I was hoping to run UAVCAN_sniffer, which appears to be able to produce a serial stream of message names and counts.
Strangely, all I appear to see is the system time being printed.
Have I misunderstood the purpose of UAVCAN_sniffer? or am I using it incorrectly?
Thanks
UAVCAN_sniffer
exampleUAVCAN: init done
2016508
3016393
Successfully mounted SDCard (slowdown=0)
4016395
5016648
6016455
7016806
8016589
That's odd - the uavcan_gui_tool
image (above) is from the same cube connected to the same CAN network above - so I know there is messages on the network.
I wasn't aware the cube black has the labels swapped. I've got a cube orange - I haven't seen the swapped labels in any cubepilot documentation for the orange.
I just tried UAVCAN_sniffer
again, checking connection on both CAN labels, and still only have the system time being printed. Swapping back to running plane
on the cube orange, and checking uavcan_gui_tool
I can still see the can node.
UAVCAN_sniffer
example.
plane
where uavcan_tool_gui
was working, then flashing UAVCAN_sniffer
without unplugging the cube, and it had messages coming in, in a format I was expecting.
Ahh, the peripheral was 'initialized' and setup for UAVCAN when running plane
, and when I reflash to the sniffer, the network is already set up. If I unplug/replug the peripheral, the light constantly flashes, which is searching for network, or network not available, or the like.
Is the sniffer not able to start the network? or is there an extra step there I'm missing?