Configuring VOXL 2 with a new UDP port

Gary Holmgren

Hello, I am wokring with MAVSDK on VOXL2 and I have made a script that runs on port 14551 successfully, but if I want to make a separate script or application that also communicates via mavlink how would I configure VOXL 2 to have a new UDP port since one port can only be used by a single instance.

Would it be as simple as modifying the vision hub config to include the following? Also what about adding a third?

{
    "en_localhost_mavlink_udp": true,
    "localhost_udp_port_number": 14551,
    "secondary_ip": "127.0.0.1",
    "secondary_port": 14552
}

such that my seperate MAVSDK script could be ran using: udpin:0.0.0.0:14552

I guess I am a little lost from how this works in MPA. I guess a little more clarity on how new UDP ports can be opened in addition to this documentation would be helpful.

Eric Katzfey

@Gary-Holmgren Depending on what your needs are you can also connect to px4 directly through voxl-mavlink-server. It listens on port 14550 for incoming "GCS" connections and can support multiple endpoints.

Gary Holmgren

@Eric-Katzfey Trying to run a MAVSDK example that changes some params and controls actuator outputs. So I would basically be able to let my MAVSDK scripts use 14550 just by running udpin:0.0.0.0:14550?

Eric Katzfey

@Gary-Holmgren Can you try it?

Gary Holmgren

@Eric-Katzfey Yes I did run that and it output an error that stated the port was already bound to another process.

Eric Katzfey

@Gary-Holmgren No, what I meant was that it shouldn't matter what port MAVSDK uses, but it should try to connect to port 14550 on voxl-mavlink-server.

Gary Holmgren

@Eric-Katzfey My apologies I guess I am confused what you mean. I tried using MAVSDK with 14550 but it wouldn't let me connect. Also, I have QGC connected using 14550 if that matters.

Eric Katzfey

@Gary-Holmgren Yes, only one thing can be using port 14550 on the VOXL 2. So that is voxl-mavlink-server. So, if you have another application (Something using MAVSDK) then you choose some other unused port for it and tell it to connect to port 14550. Basically voxl-mavlink-server is the server and your MAVSDK application is the client.

Gary Holmgren

@Eric-Katzfey Ahh that makes more sense, thankyou for explaining!