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
Copy file name to clipboardExpand all lines: docs/firmware_update.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ The device has two primary firmwares:
9
9
10
10
The device firmware is displayed in a variety of places:
11
11
12
-
* Power On
12
+
* Power On (if a display is supported)
13
13
* Serial Config Menu
14
14
* WiFi Config
15
15
@@ -44,6 +44,7 @@ The OTA method is generally recommended. For more information see [here](firmwar
44
44
Remember, all SparkFun RTK devices are open source hardware meaning you have total access to the [firmware](https://github.com/sparkfun/SparkFun_RTK_Everywhere_Firmware) and [hardware](https://github.com/sparkfun/SparkFun_RTK_Facet). Be sure to check out each repo for the latest firmware and hardware information.
45
45
46
46
## Updating Firmware Over-The-Air
47
+
47
48
48
49
49
50
*Updating the firmware via WiFi config page*
@@ -52,13 +53,13 @@ Remember, all SparkFun RTK devices are open source hardware meaning you have tot
52
53
53
54
*Updating the firmware via Firmware serial menu*
54
55
55
-
Introduced with version 3.0, firmware can be updated by pressing a button in the System Configuration section of the WiFi Config page, or over the Firmware menu of the serial interface. This makes checking and upgrading a unit very easy.
56
+
Firmware can be updated in the System Configuration section of the WiFi Config page, or over the Firmware menu of the serial interface. This makes checking and upgrading a unit very easy.
56
57
57
-
Additionally, users may opt into checking for Beta firmware. This is the latest firmware that may have new features and is meant for testing. Beta firmware is not recommended for units deployed into the field as it may not be stable.
58
+
Additionally, users may opt to check for Beta firmware. This is the latest firmware that may have new features and is meant for testing. Beta firmware is not recommended for units deployed into the field as it may not be stable.
58
59
59
60
If you have a device with firmware lower than v3.0, you will need to use the [GUI](firmware_update.md#updating-firmware-using-the-uploader-gui) or a method listed below to get to v3.x.
60
61
61
-
With version 3.10 automatic release firmware update is supported over WiFi. Enabling this feature is done using the serial firmware menu. The polling period is speified in minutes and defaults to once a day. The automatic firmware update only checks for and installs the current SparkFun released firmware versions over top of any:
62
+
Automatic release firmware update is supported over WiFi. Enabling this feature is done using the serial firmware menu. The polling period is specified in minutes and defaults to once a day. The automatic firmware update only checks for and installs the current SparkFun released firmware versions over top of any:
62
63
63
64
* Older released versions (continual upgrade)
64
65
* Beta firmware versions (newer or older, restore to released version)
Please see the System Menu [WiFi Interface](menu_system.md#wifi-interface).
8
-
9
-
## Serial Interface
5
+
**Note:** Not all devices support external SD (ie, RTK Torch). This section applies only to devices that support an external SD card, and have one inserted.
10
6
11
7
Torch: 
4
4
5
-
5
+
6
6
7
7
*Setting the baud rates of the two available external ports*
8
8
9
-
9
+
10
10
11
11
*Baud rate configuration of Radio and Data ports*
12
12
@@ -36,15 +36,9 @@ If you must run the data port at lower than 460800bps, and you need to enable a
36
36
37
37
Most applications do not need to plug anything into the **Data** port. Most users will get their NMEA position data over Bluetooth. However, this port can be useful for sending position data to an embedded microcontroller or single-board computer. The pinout is 3.3V / TX / RX / GND. **3.3V** is provided by this connector to power a remote device if needed. While the port is capable of sourcing up to 600mA, we do not recommend more than 300mA. This port should not be connected to a power source.
38
38
39
-
### Wheel Ticks
40
-
41
-
42
-
43
-
*On the RTK Express Plus only.* This dropdown is made available if users wish to connect wheel ticks and a direction encoder as inputs to the ZED-F9R. This aids the Sensor Fusion engine for IMU based location fixes when installed in an automobile. Signals must be limited to 3.3V.
44
-
45
39
### Pulse Per Second
46
40
47
-
41
+
48
42
49
43
*Configuring the External Pulse and External Events over WiFi*
50
44
@@ -67,56 +61,3 @@ For PPS, only the Black and Green wires are needed. If you need to provide 3.3V
67
61
68
62
Similarly, the RX pin of the DATA port can be used for event logging. See [External Event Logging](menu_ports.md#external-event-logging) for more information.
69
63
70
-
### External Event Logging
71
-
72
-
73
-
74
-
*Three RTK Expresses wired with external microphones*
75
-
76
-
The external triggering system is a powerful feature enabling a variety of scientific applications. Above is three RTK Expresses wired with external microphones used in a 'popped balloon' audio triangulation experiment.
77
-
78
-
The ZED-F9P has the ability to mark a detected event with +/-30 *nanosecond accuracy*. When enabled, an event on the RX pin (a low-to-high or high-to-low transition) on the DATA port, will trigger a message in the log with a very accurate timestamp.
79
-
80
-
***Red** - 3.3V
81
-
***Green** - TX (output from the RTK device)
82
-
***Orange** - RX (input into the RTK device)
83
-
***Black** - GND
84
-
85
-
86
-
87
-
For event logging, only the Black and Orange wires are needed. If you need to provide 3.3V to your system, the red wire can supply up to 600mA but we do not recommend sourcing more than 300mA.
88
-
89
-
90
-
91
-
*Configuring the External Pulse and External Events over WiFi*
92
-
93
-
Be sure to select 'Enable External Event Logging' through the ports menu.
* 02: sentenceType - Externally triggered events are type 0x02
109
-
* 5: triggerCount
110
-
* 494326906: towMsR - Time Of Week of rising edge (ms)
111
-
* 136292: towSubMsR - Millisecond fraction of Time Of Week of rising edge (ns)
112
-
* 31: accEst - Accuracy estimate (ns)
113
-
* 74: NMEA CRC
114
-
115
-
The event timestamps can be analyzed to precisely coordinate or triangulate a past event. In the case of the three RTK Expresses with microphones, the three units' locations were known with RTK 14mm accuracy. The air temperature was taken to obtain the speed of sound. From these data points, we can solve for the location of a sound such as a popped balloon.
116
-
117
-
## Surveyor Data Port
118
-
119
-
By default, the Data port is set to 460800bps and can be configured from 4800bps to 921600bps.
120
-
121
-
Note: The Data port does not output NMEA by default. The unit must be opened and the *Serial NMEA Connection* switch must be moved to 'Ext Connector'. See [Hardware Overview - Advanced Features](https://learn.sparkfun.com/tutorials/sparkfun-rtk-surveyor-hookup-guide/all#hardware-overview---advanced-features) for the location of the switch.
Copy file name to clipboardExpand all lines: docs/menu_system.md
-21Lines changed: 0 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,27 +90,6 @@ The device can be in Rover, Base, or WiFi Config mode. The selected mode will be
90
90
91
91
**Note:** Bluetooth SPP cannot operate concurrently with ESP-Now radio transmissions. Therefore, if you plan to use the ESP-Now radio system to connect RTK products, the BLE protocol must be used to communicate over Bluetooth to data collectors. Alternatively, ESP-Now works concurrently with WiFi so connecting to a data collector over WiFi can be used.
92
92
93
-
94
-
## SD Settings
95
-
96
-
On devices that have an SD socket, additional options will be shown to control logging.
97
-
98
-
### Log to SD
99
-
100
-
If a microSD card is detected, all messages will be logged.
101
-
102
-
### Max Log Time
103
-
104
-
Once the max log time is achieved, logging will cease. This is useful for limiting long-term, overnight, static surveys to a certain length of time. Default: 1440 minutes (24 hours). Limit: 1 to 2880 minutes.
105
-
106
-
### Max Log Length
107
-
108
-
Every 'max long length' amount of time the current log will be closed and a new log will be started. This is known as cyclic logging and is convenient on *very* long surveys (ie, months or years) to prevent logs from getting too unwieldy and helps limit the risk of log corruption. This will continue until the unit is powered down or the *max logging time* is reached.
109
-
110
-
### Start New Log
111
-
112
-
Pressing the 'Start New Log' button will close the current log. A new log will be opened immediately and the file name will be shown. This can be helpful in the field when a certain set of coordinates or feature marks need to be recorded in close proximity to one another. By dividing up the logs, the work can be more easily identified.
113
-
114
93
## Factory Reset
115
94
116
95
If a device gets into an unknown state it can be returned to default settings using the WiFi or Serial interfaces.
0 commit comments