Closed varunvp closed 6 years ago
The UUID is generated here: https://github.com/PX4/Firmware/blob/master/platforms/posix/include/system_config.h
using UUID method have some problem. stm32 has 92bit UUID, but mavlink has only 64bit uuid. Therefore, some FC has same UUID.
@Seunghwan17 correct, we should switch DroneCore from 64bit to 92bit. Mavlink2 actually has the 92bit UUID in the uid2
field.
We discussed this on the dev call and decided that the best way would be to do the existing UUID + mavlink system ID.
I guess this is also applicable to MAVROS.
Great! So how exactly should I use this to connect to new drones now?
@varunvp what exactly do you want to do? I don't have context for what you're trying to do.
I would like to control drone swarms.
@varunvp this should work now, please make a new issue in Dronecode/DronecodeSDK if you still can't connect to multiple drones at once.
Feature Request I wanted to simulate the offboard control of multiple PX4's using DroneCode. Unfortunately, it so happens that DroneCore distinguishes between PX4's using UUIDs, and all PX4 instances start with the same UUID. It does have another feature where if there is no UUID is available, it will fallback to using the system IDs. So it would be useful if we had the option to declare the UUIDs for each drone, let PX4 set different UUIDs for each vehicle or disable them completely.
Here is the link of the issue I raised in DroneCore : https://github.com/dronecore/DroneCore/issues/353