Hey Mikhail,
The problem of socat is that for instance multiple GCS applications will be sending commands at the same time confusing each other. Most of the GCS code I have seen does not differentiate by sys_id or component_id.
The possibility to customize the SR_* parameters for each telemtry virtual port is what I am really interest in. Specially for the project i am developing, [the SmartPort to Mavlink converter][1], where a specific set of SR_* parameters configurations optimizes the latency of the updates.
Strangely while testing the above project we found that the communications in the primary telemetry “virtual” port spilled to the secondary one, which led us to work around the issue but left us wondering how a third party in the communication may disrupt our MAVLink transactions.
Paulo Neves
Airborne Projects
[1]: MavLink to FrSky SmartPort Converter - #3 by pneves