Is there any desire to have a simple CAN output whereby the user chooses a CAN ID to start at and then each of the Servo/ESC signals are output as two bytes. Thus for each 8 byte CAN frame there could be a maximum of 4 Servos/ESCs per message. So with a maximum of 16 servos there would be a maximum of 4 CAN frames. This would allow far easier integration than complicated UAVCAN/ToshibaCAN/KDECAN.
Hi! Ive been doing some testing with uavcan to output to vesc. It is working fine, except that the motor spins as soon as I connect the vesc to the pixhawk and pixhawk not even armed(throttle on zero, but should make no difference). I Ive search through most of the documentation, but cant find what parameter to adjust.
anyone who can tell me which parameter to adjust?
anyone used CANBUS or UAVCAN under SITL? i saw a pr for it from the GSoC 2018 , but it doesn't seem to ahve been merged. ArduPilot/ardupilot#8509 thoughts ?
I seem to be having issues enabling the parameter CAN_P1_DEBUG ( https://ardupilot.org/copter/docs/parameters.html#can-p1-debug-level-of-debug-for-can-devices ) ... as it doesn't seem to exist in any binary I tried. such as copter4.0.4 or copter 'latest' as of 5 minutes ago.... is there something I need to do to unhide this param, or compile my own version..?
mavproxy "param show *CAN*" doesn't show even though the other CAN params are showing
I'm experiencing some issues with SLCAN on CubeOrange. When on the full carrier board, I can successfully discover an mRo F303 node when connected to the CAN 2 port, but not when connected to CAN 1. On the mini carrier board, I can't discover it connected to CAN 2. However, I have successfully set it up with a MS4525D0 airspeed sensor and that works in all cases
Same result with UAVCAN Gui Tool
I'm using the latest ArduPlane beta
question about CAN_P1_DRIVER Vs CAN_P2_DRIVER that the documentation doesn't make clear... in the case where the two physical ports are both on UAVCAN, but on different CAN bus's, should it be CAN_P2_DRIVER=1 or CAN_P2_DRIVER=2 ? https://ardupilot.org/copter/docs/common-canbus-setup-advanced.html#common-canbus-setup-advanced
it seems most people set both of them to '1' and most also want both can ports 'on the same bus', but i'm not 'most'.
I am running arduplane 4.0.5 and trying to use UAVCAN with a vesc 6 plus. when I set the output for channel it just spins up to maximum and isnt responding to the throttle. (It worked on an earlier ardupilot version, but that version didnt seem to have uavcan telemetry support)
was something changed within the UAVCAN protocol which wasnt updated on vesc?
@davidbuzz I apologize for the delayed response but I am appreciative of the time you took to address my situation. My focus will be more on this project for the next couple of months than it has been. Our system is more like the complete end-to-end system you described, with a "master" controller that addresses other devices using j1939. We also do have access to documentation for the specific bits and bytes of every packet in the bus. With this in mind, we will likely attempt to add the pixhawk to the existing bus. Would the "capturing" described and the software logic to read and write commands/instructions be implemented in its own "AP_J1939" library in the codebase? Thanks!
we could add that if there is need for it
Hi all, I have tried my hand at writing a libcanard based test program that sends a NodeStatus message every 750ms and can also respond to a GetNodeInfo message. I tested it with UAVCAN GUI tool and it works nicely so far. To make it do something more interesting I added the transmission of uavcan.equipment.power.BatteryInfo and then just hard-coded some fake battery voltage and current readings. Also tested this with UAVCAN GUI and it works.
Problem is that when I hookup my node to my FC with fw 4.0.4 and set battery type to UAVCAN it does not seem to work. To try and debug I toggled a led on my node when it receives NodeStatus from the FC. After power-up it seems like it receives about 5 to 10 messages (flashes) and then nothing more. When I use SLCAN on Mission Planner then I can see my Node and the led keeps flashing (receiving NodeStatus) until I disconnect it.
I know it's hard to say without seeing the code but maybe anybody have some advice were the issue could possibly be?
Problem is that when I hookup my node to my FC with fw 4.0.4 and set battery type to UAVCAN it does not seem to work. To try and debug I toggled a led on my node when it receives NodeStatus from the FC. After power-up it seems like it receives about 5 to 10 messages (flashes) and then nothing more. When I use SLCAN on Mission Planner then I can see my Node and the led keeps flashing (receiving NodeStatus) until I disconnect it.
I know it's hard to say without seeing the code but maybe anybody have some advice were the issue could possibly be?
I've just gotten a KDE-UAS125UVC ESC that I'm having weird issues with when trying to set up. Having enabled UAVCAN on can1 and KDECAN on can2 on a BlackCube, once I plug the ESC into can2, can1 stops working and the Here2 GPS fails. When snooping traffic via SLCAN on can1, all UAVCAN activity stop immediately, only to start working again after disconnecting the ESC from can2. Any advice?
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
A snippet of the output from the
UAVCAN_sniffer exampleUAVCAN: init done
2016508
3016393
Successfully mounted SDCard (slowdown=0)
4016395
5016648
6016455
7016806
8016589
You know cubeblack has can1 and can2 swapped on carrier labels?
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.
My goal is to utilize something like a pixracer to run the
UAVCAN_sniffer example.
Okay - so this is interesting.
I went from running
I went from running
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?
hello. Tell me how to properly flash the processor f303. I tried and st-flash write build/f303-Universal/bin/AP_Bootloader.bin bold0x8000000
st-flash write build/f303-Universal/bin/AP_Periph.bin bold0x801000 , but the processor does not come out of the bootloader. There were no problems with f103.
st-flash write build/f303-Universal/bin/AP_Periph.bin bold0x801000 , but the processor does not come out of the bootloader. There were no problems with f103.
Hi there, more and more discussion is moving to discord so you are all invited to join us over there! https://ardupilot.org/discord