ardupilot/libraries/AP_DroneCAN
Thomas Watson aca624486d AP_DroneCAN: DNAServer: don't "allocate" broadcast ID
While technically legal, it's unlikely to have been tested and an
allocatee might do silly things. Also makes the logic a bit more clear
and improves the failure message.
2024-09-10 12:35:04 +10:00
..
canard
dsdl
examples/DroneCAN_sniffer AP_DroneCAN: use NEW_NOTHROW for new(std::nothrow) 2024-06-04 09:20:21 +10:00
AP_Canard_iface.cpp AP_DroneCAN: use NEW_NOTHROW for new(std::nothrow) 2024-06-04 09:20:21 +10:00
AP_Canard_iface.h AP_DroneCAN: reimplement with BinarySemaphore 2024-01-03 07:37:05 +11:00
AP_DroneCAN.cpp AP_DroneCAN: register handle_actuator_status_Volz callback and fix logging 2024-08-27 11:18:18 +10:00
AP_DroneCAN.h AP_DroneCAN: register handle_actuator_status_Volz callback and fix logging 2024-08-27 11:18:18 +10:00
AP_DroneCAN_DNA_Server.cpp AP_DroneCAN: DNAServer: don't "allocate" broadcast ID 2024-09-10 12:35:04 +10:00
AP_DroneCAN_DNA_Server.h AP_DroneCAN: DNAServer: clean up and optimize allocation 2024-09-10 12:35:04 +10:00
AP_DroneCAN_serial.cpp AP_DroneCAN: set protocol in tunnel.Targetted message according to protocol parameter 2024-09-10 11:41:59 +10:00
AP_DroneCAN_serial.h AP_DroneCAN: support CAN serial ports 2023-11-22 17:19:12 +11:00