Skip to content

TCP/UDP Menu

Torch: Feature Supported / EVK: Feature Supported

NMEA data is generally consumed by a GIS application or Data Collector. These messages can be transmitted over a variety of transport methods. This section focuses on the delivery of NMEA messages via TCP and UDP.

TCP/UDP Menu showing various TCP/UDP Client and Server options

TCP/UDP Menu showing various Client and Server options

TCP Client and Server

The RTK device supports connection over TCP. The TCP Client sits on top of the network layer (WiFi or Ethernet) and sends position data to one or more computers or cell phones for display. Some Data Collector software (such as Vespucci) requires that the SparkFun RTK device connect as a TCP Client. Other software (such as QGIS) requires that the SparkFun RTK device acts as a TCP Server. Both are supported.

Note: Currently for WiFi: TCP is only supported while connected to local WiFi, not AP mode. This means the device will need to be connected to a WiFi network, such as a mobile hotspot, before TCP connections can occur.

TCP Port Entry

If either Client or Server is enabled, a port can be designated. By default, the port is 2947 (registered as GPS Daemon request/response) but any port 0 to 65535 is supported.

Ethernet TCP Client connection

The above animation was generated using TCP_Server.py.

UDP Server

NMEA messages can also be broadcast via UDP on Ethernet and WiFi, rather than TCP. If enabled, the UDP Server will begin broadcasting NMEA data over the specific port (default 10110).