Update UDP Port for the voxl-mavlink-server

ashwin

I’m currently working on a solution to connect a fleet of drones simultaneously to our home-grown Ground Control Station (GCS). Until now, we’ve been differentiating drones using unique IP and port combinations. However, this approach is not feasible with VOXL, as it transmits data to a fixed GCS IP and a hard-coded port via voxl-mavlink-server.

I came across a related topic where modifying the port was discussed. I’d like to know if there’s a supported method to configure or override the default port settings in voxl-mavlink-server, so we can enable multiple drone connections without conflict.

Any guidance or suggestions on this would be greatly appreciated.

Eric Katzfey

@ashwin Can you differentiate each drone based on the drone's IP address? Those will be unique.

ashwin

@Eric-Katzfey Hi Eric thank you for the reply, we didn't exactly try using because of the mavlinks limitation in the working and handling of UDP connection as it sends data to localhost Port 14550 so all of the drones would be sending their data to 127.0.0.1 14550 port and this would create problem for handling multiple drone with same port.

Eric Katzfey

@ashwin I'm not really understanding the issue. Mavlink has no limitation to send packets to a localhost address. On VOXL 2 we configure voxl-px4 to send to localhost but that is because voxl-mavlink-server is the application that actually sends the data to the GCS. At the GCS you will see each connection with a unique IP address.