Step 1
Identify the source
Start with the receiver, INS, or vessel system that produces the position stream.
How to route GNSS data to multiple applications
A single GNSS receiver often needs to feed several operational systems. This workflow shows how Data Mirror sits between the source and downstream applications.
UDP TCP Serial
Step 2
Mirror the feed
Route the incoming serial, TCP, UDP, ASCII, or binary stream through Data Mirror instead of rewiring the source.
Step 3
Create downstream outputs
Send the same data to survey, acquisition, navigation, logging, and display applications.
Step 4
Monitor and command devices
Use the UDP, TCP, and serial console views to check live traffic, send supported commands to devices, log evidence, and diagnose connection issues.
Inspect traffic, send supported commands, and keep operational logs
UDP terminal and logging
View UDP packets in a live terminal, send test commands or configuration messages where the device supports them, and keep logs for troubleshooting survey or vessel telemetry feeds.
TCP console and diagnostics
Inspect TCP streams from networked marine systems, send console commands to connected devices, and route the same feed to downstream applications.
Serial terminal for RS232 feeds
Use Data Mirror as a serial terminal for RS232-style data, including command entry, NMEA inspection, and custom ASCII stream logging.
Operational route logs
Capture routing evidence during mobilisation, integration, and offshore fault-finding without adding separate terminal tools.
Binary protocol routing
Route binary data protocols and proprietary sensor streams over UDP, TCP, or serial links without converting them to text first.
When this workflow matters
Survey vessels, ROV teams, and ocean science crews often need the same position or attitude stream in several applications at once. Data Mirror gives those teams a routing, terminal, command, and logging layer for live offshore data workflows.