Forward serial telemetry over UDP

Scenario 4: send serial telemetry as UDP datagrams

Use this for NMEA, sensor telemetry and LAN collectors.

1. Configure endpoint A as serial and endpoint B as UDP, then create an A → B bridge. Make it bidirectional only when network commands must return to the device.
2. Choose the UDP target: Reply to the last sender when a peer sends first, Fixed destination for a known collector, or All known peers for every discovered receiver.
3. Match framing to the protocol: line-oriented data can use delimiter 0A (LF) or 0D0A (CRLF); protocols such as Modbus RTU can use Cut on idle gap; fixed-size packets can use Fixed length.
4. Use a packet capture to confirm that one application message becomes one UDP datagram, and watch the bridge manager's dropped counters.

UDP has no retransmission or back pressure. Congestion, an offline destination or an input rate above capacity can only result in dropped data, so Slow the sender down is not a reliability guarantee for UDP. Prefer TCP when delivery and ordering matter.

Common checks after creating a bridge

• Both endpoint panes are open and show bridge badges. The manager should report Active rather than Degraded or Suspended.
• The direction matches the topology. A one-way bridge does not return responses automatically.
• Dropped counters should remain zero. A non-zero value means the sink is too slow, the buffer is too small or the source cannot be throttled. Fix the cause before merely increasing the buffer.
• Keep One client at a time for TCP servers by default. If several request/response clients must share the device, use Take turns together with idle-gap, delimiter or fixed-length framing. All clients share the port can interleave requests on the serial wire.
• Save the endpoints and bridge together in a .spu project for repeated use, and re-check the physical port assignments after loading it.