ArduPilot / MAVProxy

MAVLink proxy and command line ground station
GNU General Public License v3.0
455 stars 675 forks source link

MAVProxy hold on to TCP port after port is removed or disconnected (Windows) #472

Open pkvaloy opened 6 years ago

pkvaloy commented 6 years ago

We use MAVProxy to multiplex telemetry data from a 433MHz link (COM) and a 5,8GHz link (TCP). If the TCP link goes down there is no way of reconnecting other than to restart MAVProxy. When MAVProxy is restarted we have to reconnect MissionPlanner and reload all parameters. This takes time and leaves us with no link while restarting. Flight data is also reset.

There should be a way to reconnect TCP links without restarting MAVProxy. MAVProxys process holds on to the TCP port even if the link is down, and is unable to reconnect. Running on Windows 10.

peterbarker commented 6 years ago

On Wed, 13 Dec 2017, Pål Kvaløy wrote:

We use MAVProxy to multiplex telemetry data from a 433MHz link (COM) and a 5,8GHz link (TCP). If the TCP link goes down there is no way of reconnecting other than to restart MAVProxy. When MAVProxy is restarted we have to reconnect MissionPlanner and reload all parameters. This takes time and leaves us with no link while restarting. Flight data is also reset.

There should be a way to reconnect TCP links without restarting MAVProxy. MAVProxys process holds on to the TCP port even if the link is down, and is unable to reconnect. Running on Windows 10.

Not to say we shouldn't fix the TCP problem, but...

Why are you using TCP rather than UDP? What does TCP give you that UDP doesn't. If you're thinking "guaranteed delivery", then you might like to think about that for a moment....

pkvaloy commented 6 years ago

Hi. I agree that UDP is the preferred protocol. In our planes we have routers that at the moment cannot run UDP. We are working on a fix for that, but I think that MAVProxy should be able to reconnect a TCP link anyway.....