You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once a [correction source](correction_sources.md) is chosen, the correction data must be transported from the base to the rover. The RTCM serial data is approximately 530 bytes per second. This section describes the various methods to move correction data from a base to one or more rovers.
4
4
5
-
Once a [correction source](correction_sources.md) is chosen, the correction data must be transported from the base to the rover. The RTCM serial data is approximately 530 bytes per second and is transmitted at 57600bps out of the **RADIO** port on a SparkFun RTK device.
6
-
7
-
There are a variety of ways to move data from a base to a rover. We will cover the most common below.
8
-
9
-
Note: RTK calculations require RTCM data to be delivered approximately once per second. If RTCM data is lost or not received by a rover, RTK Fix can still be maintained for many seconds before the device will enter RTK Float mode. This is beneficial where devices like Serial Radios may drop packets due to RF congestion.
10
-
11
-
**Note:** The RTK Facet L-Band is capable of receiving RTCM corrections from a terrestrial source but because it has a built-in L-Band receiver, we recommend using the satellite-based corrections.
5
+
RTK calculations require RTCM data to be delivered approximately once per second. If RTCM data is lost or not received by a rover, RTK Fix can still be maintained for many seconds before the device will enter RTK Float mode. If a transport method experiences congestion (ie, cellular latency, Serial Radios dropping packets, etc) the rover(s) can continue in RTK Fix mode even if correction data is not available for multiple seconds.
12
6
13
7
## WiFi
14
8
15
-


16
12
17
13
Any SparkFun RTK device can be set up as an [NTRIP Server](menu_base.md#ntrip-server). This means the device will connect to local WiFi and broadcast its correction data to the internet. The data is delivered to something called an NTRIP Caster. Any number of rovers can then access this data using something called an NTRIP Client. Nearly *every* GIS application has an NTRIP Client built into it so this makes it very handy.
18
14
19
15
WiFi broadcasting is the most common transport method of getting RTCM correction data to the internet and to rovers via NTRIP Clients.
20
16
21
17

22
18
23
-
Similarly, any SparkFun RTK device can be set up as an [NTRIP Client](menu_gnss.md#ntrip-client). The RTK device will connect to the local WiFi and begin downloading the RTCM data from the given NTRIP Caster and RTK Fix will be achieved. This is useful only if the Rover remains in RF range of the WiFi access point. Because of the limited range, we recommend using a cellphone rather than WiFi for NTRIP Clients.
19
+
*RTK product showing corrections being downloaded over WiFi in NTRIP Client mode*
20
+
21
+
Similarly, any SparkFun RTK device can be set up as an [NTRIP Client](menu_gnss.md#ntrip-client). The RTK device will connect to the local WiFi and begin downloading the RTCM data from the given NTRIP Caster and RTK Fix will be achieved. This is useful only if the Rover remains in RF range of a WiFi access point. Because of the limited range, we recommend using a cell phone's hotspot feature rather than a stationary WiFi access point for NTRIP Clients.
Using a cellphone is the most common way of transporting correction data from the internet to a rover. This method uses the cell phone's built-in internet connection to obtain data from an NTRIP Caster and then pass those corrections over Bluetooth to the RTK device.
29
+
Using a cell phone is the most common way of transporting correction data from the internet to a rover. This method uses the cell phone's built-in internet connection to obtain data from an NTRIP Caster and then pass those corrections over Bluetooth to the RTK device.
30
30
31
31
Shown above are SW Map's NTRIP Client Settings. Nearly all GIS applications have an NTRIP Client built in so we recommend leveraging the device you already own to save money. Additionally, a cell phone gives your rover incredible range: a rover can obtain RTCM corrections anywhere there is cellular coverage.
32
32
33
33
Cellular can even be used in Base mode. We have seen some very inventive users use an old cell phone as a WiFi access point. The base unit is configured as an NTRIP Server with the cellphone's WiFi AP credentials. The base performs a survey-in, connects to the WiFi, and the RTCM data is pushed over WiFi, over cellular, to an NTRIP Caster.
34
34
35
35
## L-Band
36
36
37
+
Torch: 
38
+
37
39
What if you are in the field, far away from WiFi, cellular, radio, or any other data connection? Look to the sky!
38
40
39
41
A variety of companies provide GNSS RTK corrections broadcast from satellites over a spectrum called L-Band. [L-Band](https://en.wikipedia.org/wiki/L_band) is any frequency from 1 to 2 GHz. These frequencies have the ability to penetrate clouds, fog, and other natural weather phenomena making them particularly useful for location applications.
@@ -44,13 +46,15 @@ L-Band reception requires specialized RF receivers capable of demodulating the s
44
46
45
47
## Serial Radios
46
48
49
+
Torch: 
50
+
47
51

48
52
49
53
Serial radios, sometimes called telemetry radios, provide what is essentially a serial cable between the base and rover devices. Transmission distance, frequency, maximum data rate, configurability, and price vary widely, but all behave functionally the same. SparkFun recommends the [HolyBro 100mW](https://www.sparkfun.com/products/19032) and the [SparkFun LoRaSerial 1W](https://www.sparkfun.com/products/19311) radios for RTK use.
50
54
51
55

52
56
53
-
All SparkFun RTK products include a [4-pin to 6-pin cable](https://www.sparkfun.com/products/17239) that will allow you to connect the HolyBro branded radio or the SparkFun LoRaSerial radios to a base and rover RTK device.
57
+
On SparkFun RTK products that have an external radio port, a [4-pin to 6-pin cable](https://www.sparkfun.com/products/17239) is included that will allow you to connect the HolyBro branded radio or the SparkFun LoRaSerial radios to a base and rover RTK device.
54
58
55
59

56
60
@@ -62,6 +66,8 @@ The downside to serial telemetry radios is that they generally have a much short
62
66
63
67
## Ethernet
64
68
65
-
The Reference Station send and receive correction data via Ethernet. (Note: it cannot currently send or receive correction data via WiFi)
69
+
Torch: 
70
+
71
+
Ethernet-equipped RTK devices send and receive correction data via Ethernet.
66
72
67
73
Please see [Ethernet Menu](menu_ethernet.md) for more details.
Copy file name to clipboardExpand all lines: docs/menu_ethernet.md
+6-23Lines changed: 6 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,39 +1,22 @@
1
1
# Ethernet Menu
2
2
3
-
## TCP Client and Server
3
+
Torch: 
4
4
5
-
The RTK device supports connection over TCP. Some Data Collector software (such as [Vespucci](gis_software.md#vespucci)) requires that the SparkFun RTK device connect as a TCP Client. Other software (such as [QGIS](gis_software.md#qgis)) requires that the SparkFun RTK device acts as a TCP Server. Both are supported.
5
+
An Ethernet-equipped RTK device sends and receives NTRIP correction data via Ethernet. It can also send NMEA and RTCM navigation messages to an external TCP Server via Ethernet. It also has a dedicated Configure-Via-Ethernet (*Cfg Eth*) mode which is accessed via the MODE button and OLED display.
6
6
7
-
**Note:** Currently 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.
7
+
By default, the RTK device will use DHCP to request an IP Address from the network Gateway. But you can optionally configure it with a fixed IP Address.
8
8
9
-

10
-
11
-
If either Client or Server is enabled, a port can be designated. By default, the port is 2947 (registered as [*GPS Daemon request/response*](https://en.wikipedia.org/wiki/Gpsd)) but any port 0 to 65535 is supported.
12
-
13
-
14
-
15
-
Surveyor:  / Express:  / Express Plus:  / Facet:  / Facet L-Band:  / Reference Station: 
16
-
17
-
The Reference Station sends and receives NTRIP correction data via Ethernet. It can also send NMEA and RTCM navigation messages to an external TCP Server via Ethernet.
18
-
It also has a dedicated Configure-Via-Ethernet (*Cfg Eth*) mode which is accessed via the MODE button and OLED display.
19
-
20
-
By default, the Reference Station will use DHCP to request an IP Address from the network Gateway. But you can optionally configure it with a fixed IP Address.
21
-
22
-

9
+

23
10
24
11
*The Reference Station Ethernet menu - with DHCP selected*
25
12
26
13

27
14
28
15
*The Reference Station Ethernet menu - with a fixed IP address selected*
29
16
30
-
### Ethernet TCP Client
31
-
32
-
The Reference Station can act as an Ethernet TCP Client, sending NMEA and / or UBX data to a remote TCP Server.
33
-
34
-
This is similar to the WiFi TCP Client mode on our other RTK products, but the data can be sent to any server based on its IP Address or URL.
17
+
## Ethernet TCP Client
35
18
36
-
E.g. to connect to a local machine via its IP Address, select option "c" and then enter the IP Address using option "h"
19
+
Ethernet-equipped RTK devices can act as an Ethernet TCP Client, sending NMEA and / or UBX data to a remote TCP Server. This is similar to the WiFi TCP Client mode on our other RTK products, but the data can be sent to any server based on its IP Address or URL. E.g. to connect to a local machine via its IP Address, select option "c" and then enter the IP Address using option "h"
Copy file name to clipboardExpand all lines: docs/menu_ntp.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
1
# Network Time Protocol Menu
2
2
3
-
Surveyor: / Express:  / Express Plus:  / Facet:  / Facet L-Band:  / Reference Station: 
3
+
Torch: 
4
4
5
-
The Reference Station can act as an Ethernet Network Time Protocol (NTP) server.
5
+
Ethernet-equipped RTK devices can act as an Ethernet Network Time Protocol (NTP) server.
6
6
7
7
Network Time Protocol has been around since 1985. It is a simple way for computers to synchronize their clocks with each other, allowing the network latency (delay) to be subtracted:
8
8
9
-
* A client sends a NTP request (packet) to the chosen or designated server
9
+
* A client sends an NTP request (packet) to the chosen or designated server
10
10
* The request contains the client's current clock time - for identification
11
11
12
12
* The server logs the time the client's request arrived and then sends a reply containing:
@@ -29,17 +29,17 @@ This exchange is repeated typically five times, before the client synchronizes i
29
29
30
30
Having your own NTP server on your network allows tighter clock synchronization as the network latency is minimized.
31
31
32
-
The Reference Station can be placed into its dedicated NTP mode, by pressing the **MODE** button until NTP is highlighted in the display and pausing there.
32
+
Ethernet-equipped RTK devices can be placed into dedicated NTP mode, by pressing the **MODE** button until NTP is highlighted in the display and pausing there.
33
33
34
-

34
+

35
35
36
36
*Selecting NTP mode*
37
37
38
-
The Reference Station will first synchronize its Real Time Clock (RTC) using the very accurate time provided by the u-blox GNSS module. The module's Time Pulse (Pulse-Per-Second) signal is connected to the ESP32 as an interrupt. The ESP32's RTC is synchronized to Universal Time Coordinate (UTC) on the rising edge of the TP signal using the time contained in the UBX-TIM-TP message.
38
+
Ethernet-equipped RTK devices will first synchronize its Real Time Clock (RTC) using the very accurate time provided by the u-blox GNSS module. The module's Time Pulse (Pulse-Per-Second) signal is connected to the ESP32 as an interrupt. The ESP32's RTC is synchronized to Universal Time Coordinate (UTC) on the rising edge of the TP signal using the time contained in the UBX-TIM-TP message.
39
39
40
40
The WIZnet W5500 interrupt signal is also connected to the ESP32, allowing the ESP32 to accurately log when each NTP request arrives.
41
41
42
-
The Reference Station will respond to each NTP request within a few 10s of milliseconds.
42
+
The RTK device will respond to each NTP request within a few 10s of milliseconds.
43
43
44
44
If desired, you can log all NTP requests to a file on the microSD card, and/or print them as diagnostic messages. The log and messages contain the NTP timing information and the IP Address and port of the Client.
45
45
@@ -65,7 +65,7 @@ NTP uses its own epoch - midnight January 1st, 1900. This is different than the
65
65
66
66
### NTP on Windows
67
67
68
-
If you want to synchronize your Windows PC to a Reference Station NTP Server, here's how to do it:
68
+
If you want to synchronize your Windows PC to a RTK device running as an NTP Server, here's how to do it:
69
69
70
70
* Install [Meinberg NTP](https://www.meinbergglobal.com/english/sw/ntp.htm) - this replaces the Windows built-in Time Service
71
71
@@ -83,7 +83,7 @@ If you want to synchronize your Windows PC to a Reference Station NTP Server, he
* Comment the lines in *ntp.conf* which name the pool.ntp servers
86
-
* Add an extra *server* line and include the IP Address for your Reference Station. It helps to give your Reference Station a fixed IP Address first - see [Menu Ethernet](menu_ethernet.md)
86
+
* Add an extra *server* line and include the IP Address for your RTK device. It helps to give your RTK device a fixed IP Address first - see [Menu Ethernet](menu_ethernet.md)
0 commit comments