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
@@ -22,11 +23,7 @@ To get millimeter accuracy we need to provide the RTK unit with correction value
22
23
23
24
These companies set up a large number of reference stations that cover entire regions and countries, but charge a monthly fee. They are often easy to use but can be expensive.
24
25
25
-
-[PointPerfect](https://docs.sparkfun.com/SparkFun_RTK_Everywhere_Firmware/quickstart-torch/#pointperfect-corrections) ($8/month) - US, EU, as well as parts of Australia, Brazil, and South Korea.
26
-
27
-
!!! note
28
-
This is an SSR service.
29
-
26
+
-[PointPerfect](https://docs.sparkfun.com/SparkFun_RTK_Everywhere_Firmware/quickstart-torch/#pointperfect-corrections) ($8/month) - US, EU, as well as parts of Australia, Brazil, and South Korea. Note: This is an [SSR service](https://docs.sparkfun.com/SparkFun_RTK_Everywhere_Firmware/correction_sources/#osr-vs-ssr).
30
27
-[Onocoy](https://console.onocoy.com/explorer) ($25/month) - US, EU, Australia, and many other partial areas
31
28
-[PointOneNav](https://app.pointonenav.com/trial?src=sparkfun) ($50/month) - US, EU, Australia, South Korea
32
29
-[Skylark](https://www.swiftnav.com/skylark) ($29 to $69/month) - US, EU, Japan, Australia
The European Union launched a free correction service called [High Accuracy Service](https://www.gsc-europa.eu/galileo/services/galileo-high-accuracy-service-has) or **HAS** starting in 2023. The service is delivered over the E6 frequency. In general, this service will greatly improve accuracy to receivers but is lower accuracy than an OSR or SSR-based RTK Fix. Additionally, a receiver can take up to 5 minutes to benefit from these corrections (convergence time is larger), as opposed to OSR (seconds) or SSR (~180 seconds) to achieve maximum accuracy. But HAS is free! And available with very little additional configuration.
105
103
106
-
Various SparkFun RTK products support this new GNSS band (E6). In general, the RTK Torch will need UM980 firmware 118333 or newer. See how to [Update the UM980 Firmware](firmware_update.md#updating-um980-firmware) for instructions. HAS/E6 is enabled by default and can be disabled in the [GNSS Menu](menu_gnss.md#galileo-e6-corrections) if desired.
104
+
Various SparkFun RTK products support this new GNSS band (E6).
105
+
* The RTK EVK does not support E6 reception.
106
+
* The RTK Postcard's LG290P GNSS receiver has the ability to receive the E6 signals but as of writing, HAS is not yet implemented in the GNSS location engine.
107
+
* The RTK Torch will need UM980 firmware 118333 or newer. See how to [Update the UM980 Firmware](firmware_update.md#updating-um980-firmware) for instructions. HAS/E6 is enabled by default and can be disabled in the [GNSS Menu](menu_gnss.md#galileo-e6-corrections) if desired.
Copy file name to clipboardExpand all lines: docs/correction_transport.md
+98-34Lines changed: 98 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
# Correction Transport
2
2
3
-
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.
3
+
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 but varies depending on the GNSS receiver and its settings. This section describes the various methods to move correction data from a base to one or more rovers.
4
4
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.
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 around 30 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.
- EVK: [:material-radiobox-blank:{ .support-none }]( title ="Feature Not Supported" )
21
+
- Postcard: [:material-radiobox-blank:{ .support-none }]( title ="Feature Not Supported" )
22
+
- Torch: [:material-radiobox-blank:{ .support-none }]( title ="Feature Not Supported" )
22
23
23
24
</div>
24
25
25
-
<figuremarkdown>
26
-
27
-
<figcaptionmarkdown>
28
-
</figcaption>
29
-
</figure>
30
-
31
-
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.
32
-
33
-
WiFi broadcasting is the most common transport method of getting RTCM correction data to the internet and to rovers via NTRIP Clients.
34
-
35
-
<figuremarkdown>
36
-
37
-
<figcaptionmarkdown>
38
-
RTK product showing corrections being downloaded over WiFi in NTRIP Client mode
39
-
</figcaption>
40
-
</figure>
26
+
The RTK EVK has built-in cellular via a u-blox LARA-R6001D. However, the RTK Everywhere firmware does not yet support cellular. Adding it is on our roadmap. Stay tuned for updates! Meanwhile, we do have a stand-alone EVK code example which will connect to PointPerfect localized distribution via cellular:
41
27
42
-
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.
28
+
-[EVK example 8_5_PointPerfect_MQTT](https://github.com/sparkfun/SparkFun_RTK_EVK/tree/main/Example_Sketches/8_5_PointPerfect_MQTT)
29
+
-[EVK example 8_6_PointPerfect_MQTT_WiFi_ETH_Cellular](https://github.com/sparkfun/SparkFun_RTK_EVK/tree/main/Example_Sketches/8_6_PointPerfect_MQTT_WiFi_ETH_Cellular)
@@ -71,7 +59,7 @@ Shown above are SW Map's NTRIP Client Settings. Nearly all GIS applications have
71
59
72
60
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.
- Postcard: [:material-radiobox-blank:{ .support-none }]( title ="Feature Not Supported" )
87
77
- Torch: [:material-radiobox-blank:{ .support-none }]( title ="Feature Not Supported" )
88
-
- EVK: [:material-radiobox-blank:{ .support-none }]( title ="Feature Not Supported" )
89
78
90
79
</div>
91
80
92
-
The RTK EVK has built-in cellular via a u-blox LARA-R6001D. However, the RTK Everywhere firmware does not yet support cellular. Adding it is on our roadmap. Stay tuned for updates! Meanwhile, we do have a stand-alone EVK code example which will connect to PointPerfect localized distribution via cellular:
81
+
Ethernet-equipped RTK devices send and receive correction data via Ethernet.
82
+
83
+
Please see [Ethernet Menu](menu_ethernet.md) for more details.
- Torch: [:material-radiobox-blank:{ .support-none }]( title ="Feature Supported" )
101
+
102
+
</div>
103
+
104
+
<figuremarkdown>
105
+
106
+
<figcaptionmarkdown>
107
+
</figcaption>
108
+
</figure>
109
+
110
+
All RTK devices have a built-in radio capable of transmitting RTCM from a single base to multiple rovers. The range is not great, but it's free! See [ESP-NOW Configuration](menu_radios.md#esp-now) for more information.
93
111
94
-
-[EVK example 8_5_PointPerfect_MQTT](https://github.com/sparkfun/SparkFun_RTK_EVK/tree/main/Example_Sketches/8_5_PointPerfect_MQTT)
95
-
-[EVK example 8_6_PointPerfect_MQTT_WiFi_ETH_Cellular](https://github.com/sparkfun/SparkFun_RTK_EVK/tree/main/Example_Sketches/8_6_PointPerfect_MQTT_WiFi_ETH_Cellular)
96
112
97
113
## L-Band
98
114
@@ -107,8 +123,9 @@ Compatibility Icons
107
123
108
124
<divclass="grid cards fill"markdown>
109
125
110
-
- Torch: [:material-radiobox-blank:{ .support-none }]( title ="Feature Not Supported" )
- Postcard: :material-radiobox-marked:{ .support-full title="Feature Not Supported" }
128
+
- Torch: [:material-radiobox-blank:{ .support-none }]( title ="Feature Not Supported" )
112
129
113
130
</div>
114
131
@@ -120,7 +137,7 @@ These corrections are not as accurate as a fixed base station, and the correctio
120
137
121
138
L-Band reception requires specialized RF receivers capable of demodulating the satellite transmissions. The RTK EVK has a built-in NEO-D9S corrections receiver. The RTK Everywhere firmware supports this and will tune the NEO-D9S to the correct frequency if you are in the US or EU. The PointPerfect L-Band corrections are encrypted and require a subscription and valid keys in order to work. The EVK comes with a one month free subscription to PointPerfect L-Band + IP, providing built-in support for L-Band corrections and IP corrections via Ethernet or WiFi.
122
139
123
-
## Serial Radios
140
+
## LoRa
124
141
125
142
<!--
126
143
Compatibility Icons
@@ -133,8 +150,38 @@ Compatibility Icons
133
150
134
151
<divclass="grid cards fill"markdown>
135
152
153
+
- EVK: :material-radiobox-marked:{ .support-full title="Feature Not Supported" }
- Torch: [:material-radiobox-blank:{ .support-none }]( title ="Feature Not Supported" )
156
+
157
+
</div>
158
+
159
+
<figuremarkdown>
160
+
161
+
<figcaptionmarkdown>
162
+
Antenna covered removed from the RTK Torch
163
+
</figcaption>
164
+
</figure>
165
+
166
+
167
+
The RTK Torch contains a 1 watt Long Range (LoRa) radio capable of transmitting RTCM from a single base to multiple rovers. See [LoRa Radio Configuration](menu_radios.md#configuration) for more information.
- Torch: [:material-radiobox-blank:{ .support-none }]( title ="Feature Not Supported" )
138
185
139
186
</div>
140
187
@@ -168,7 +215,8 @@ The benefit of a serial telemetry radio link is that you do not need to configur
168
215
169
216
The downside to serial telemetry radios is that they generally have a much shorter range (often slightly more than a 1-kilometer functional range) than a cellular link can provide.
170
217
171
-
## Ethernet
218
+
219
+
## WiFi
172
220
173
221
<!--
174
222
Compatibility Icons
@@ -181,11 +229,27 @@ Compatibility Icons
181
229
182
230
<divclass="grid cards fill"markdown>
183
231
184
-
- Torch: [:material-radiobox-blank:{ .support-none }]( title ="Feature Not Supported" )
Ethernet-equipped RTK devices send and receive correction data via Ethernet.
238
+
<figuremarkdown>
239
+
240
+
<figcaptionmarkdown>
241
+
</figcaption>
242
+
</figure>
190
243
191
-
Please see [Ethernet Menu](menu_ethernet.md) for more details.
244
+
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.
245
+
246
+
WiFi broadcasting is the most common transport method of getting RTCM correction data to the internet and to rovers via NTRIP Clients.
247
+
248
+
<figuremarkdown>
249
+
250
+
<figcaptionmarkdown>
251
+
RTK product showing corrections being downloaded over WiFi in NTRIP Client mode
252
+
</figcaption>
253
+
</figure>
254
+
255
+
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.
0 commit comments