Additional UDP Port Setting

voxltester

Hi,
I would like to have one more additional port to communicate VOXL2 from my laptop.
This is the current voxl-mavlink-server.conf

{
	"primary_static_gcs_ip":	"10.223.0.4",
	"primary_static_gcs_ip_port":	14550,
	"secondary_static_gcs_ip":	"10.223.0.4",
	"secondary_static_gcs_ip_port":	14600,
	"onboard_port_to_autopilot":	14556,
	"onboard_port_from_autopilot":	14557,
	"gcs_port_to_autopilot":	14558,
	"gcs_port_from_autopilot":	14559,
	"en_external_uart_ap":	false,
	"autopilot_uart_bus":	1,
	"autopilot_uart_baudrate":	921600,
	"autopilot_mission_delay_start":	-1,
	"autopilot_mission_delay_sound":	false,
	"autopilot_mission_force_restart":	0,
	"autopilot_mission_notif_dur":	0.1,
	"en_external_ap_timesync":	1,
	"en_external_ap_heartbeat":	1,
	"udp_mtu":	512,
	"gcs_timeout_s":	4.5
}

I am using 14550 for QGC and 14600 for MAVROS.
Is it possible to have one more UDP port for MAVSDK? I would like to run mavsdk from my laptop by running await drone.connect(system_address="udp://:14xxx")

Please let me know.
I would like to know if the following explanation is true;
Up to 16 simultaneous external UDP connections can be established with voxl-mavlink-server. These can be connections to qGroundControl, MAVROS, MAVSDK, or any custom software on the same network as VOXL.
in https://docs.modalai.com/mavlink/#mavlink-routing-on-voxl

Eric Katzfey

@voxltester The primary and secondary ip / port configurations are for destinations. voxl-mavlink-server will initiate connections to those. For incoming connections just send to port 14550. voxl-mavlink-server is listening on that port. When an incoming message from a new ip / port combo comes in it will store that and consider that a new connection. If you use drone.connect it is waiting for voxl-mavlink-server to connect to it rather than attempting to connect to voxl-mavlink-server on it's own.