RTK Express - WiFi TCP Client use

I am having trouble understanding the use case for “WiFi TCP Client”.

I know that if I want to access the data from the RTK Express from my phone or PC, I need to enable the “WiFi TCP Server”.

When would I want to enable the “WiFi TCP Client” and can the “WiFi TCP Client” and “WiFi TCP Server” both be active at the same time?

I suspect that the “WiFi TCP Client” may come into play when the RTK Express has the “NTRIP Client” enabled.

Menu: Main

  1. Configure WiFi

Menu: WiFi Networks

c) WiFi TCP Client (connect to phone): Enabled

s) WiFi TCP Server: Enabled

p) WiFi TCP Port: 2947

TCP Client is largely available for data collection software such as Vespucci (https://docs.sparkfun.com/SparkFun_RTK_ … /#vespucci) that needs to obtain the NMEA data over TCP.

TCP Server is generally more common.

Just to add a little more detail:

Please have a look at these sections in the Manual:

QGIS can connect to the RTK as a TCP Client only. The RTK acts as the TCP Server:

https://docs.sparkfun.com/SparkFun_RTK_ … ware/#qgis

Vespucci can connect as a TCP Client, or can also be a TCP Server where the RTK connects as a client:

https://docs.sparkfun.com/SparkFun_RTK_ … /#vespucci

The RTK firmware allows you to set both to enabled at the same time, but, in reality, you can only have one or the other enabled. Enabling both actually prevents both from working. I need to fix that - or at least pop up a warning if you do have both enabled.

Note: TCP Client / Server is different to and independent from NTRIP Client / Server. There you can have both enabled - e.g. to do an NTRIP-assisted Base which sends NTRIP to a different Caster. You might want to and can have the RTK receiving NTRIP from (e.g.) Skylark - as a Client - while sending NTRIP to (e.g.) rtk2go - as a Server…

I hope this helps,

Paul