Skip to content

Commit 85e09b0

Browse files
PaulZCPaulZC
committed
Correct bold and indentation
1 parent 854079f commit 85e09b0

File tree

4 files changed

+18
-18
lines changed

4 files changed

+18
-18
lines changed

‎README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ SparkFun RTK Firmware
3434
</tr>
3535
</table>
3636

37-
The [SparkFun RTK Surveyor](https://www.sparkfun.com/products/18443), [SparkFun RTK Express](https://www.sparkfun.com/products/18442), [SparkFun RTK Express Plus](https://www.sparkfun.com/products/18590), [SparkFun RTK Facet](https://www.sparkfun.com/products/19029), and [SparkFun RTK Facet L-Band](https://www.sparkfun.com/products/20000) are centimeter-level GNSS receivers. With RTK enabled, these devices can output your location with 14mm horizontal and vertical [*accuracy*](https://docs.sparkfun.com/SparkFun_RTK_Firmware/accuracy_verification/) at up to 20Hz!
37+
The [SparkFun RTK Surveyor](https://www.sparkfun.com/products/18443), [SparkFun RTK Express](https://www.sparkfun.com/products/18442), [SparkFun RTK Express Plus](https://www.sparkfun.com/products/18590), [SparkFun RTK Facet](https://www.sparkfun.com/products/19029), [SparkFun RTK Facet L-Band](https://www.sparkfun.com/products/20000) and [SparkFun RTK Reference Station](https://www.sparkfun.com/products/22429) are centimeter-level GNSS receivers. With RTK enabled, these devices can output your location with 14mm horizontal and vertical [*accuracy*](https://docs.sparkfun.com/SparkFun_RTK_Firmware/accuracy_verification/) at up to 20Hz!
3838

3939
This repo houses the [RTK Product Manual](https://docs.sparkfun.com/SparkFun_RTK_Firmware/intro/) and the firmware that runs on the SparkFun RTK product line including:
4040

‎docs/menu_ethernet.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,9 @@ By default, the Reference Station will use DHCP to request an IP Address from th
99

1010
![Reference Station in DHCP mode](img/Ethernet_DHCP.png)
1111

12-
**The Reference Station Ethernet menu - with DHCP selected**
12+
*The Reference Station Ethernet menu - with DHCP selected*
1313

1414
![Reference Station in fixed IP address mode](img/Ethernet_Fixed_IP.png)
1515

16-
**The Reference Station Ethernet menu - with a fixed IP address selected**
16+
*The Reference Station Ethernet menu - with a fixed IP address selected*
1717

‎docs/ntp.md‎

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,13 @@ The Reference Station can act as an Ethernet Network Time Protocol (NTP) server.
77
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:
88

99
* A client sends a NTP request (packet) to the chosen or designated server
10-
* The request contains the client's current clock time - for identification
10+
* The request contains the client's current clock time - for identification
1111

1212
* The server logs the time the client's request arrived and then sends a reply containing:
13-
* The client's clock time - for identification
14-
* The server's clock time - when the request arrived at the server
15-
* The server's clock time - when the reply is sent
16-
* The time the server's clock was last synchronized - providing the age of the synchronization
13+
* The client's clock time - for identification
14+
* The server's clock time - when the request arrived at the server
15+
* The server's clock time - when the reply is sent
16+
* The time the server's clock was last synchronized - providing the age of the synchronization
1717

1818
* The client logs the time the reply is received - using its own clock
1919

@@ -31,9 +31,9 @@ Having your own NTP server on your network allows tighter clock synchronization
3131

3232
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.
3333

34-
![Animation of selecting NTP mode](https://cdn.sparkfun.com/assets/learn_tutorials/3/2/1/0/NTP.gif)](https://cdn.sparkfun.com/assets/learn_tutorials/3/2/1/0/NTP.gif)
34+
[![Animation of selecting NTP mode](https://cdn.sparkfun.com/assets/learn_tutorials/3/2/1/0/NTP.gif)](https://cdn.sparkfun.com/assets/learn_tutorials/3/2/1/0/NTP.gif)
3535

36-
**Selecting NTP mode**
36+
*Selecting NTP mode*
3737

3838
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 connect 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.
3939

@@ -43,17 +43,17 @@ The Reference Station will respond to each NTP request within a few 10's of mill
4343

4444
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.
4545

46-
![The system debug menu showing how to enable the NTP diagnostics](https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/3/2/1/0/NTP_Diagnostics.png)](https://cdn.sparkfun.com/assets/learn_tutorials/3/2/1/0/NTP_Diagnostics.png)
46+
[![The system debug menu showing how to enable the NTP diagnostics](https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/3/2/1/0/NTP_Diagnostics.png)](https://cdn.sparkfun.com/assets/learn_tutorials/3/2/1/0/NTP_Diagnostics.png)
4747

48-
**System Debug Menu - NTP Diagnostics (Click for a closer look)**
48+
*System Debug Menu - NTP Diagnostics (Click for a closer look)*
4949

5050
![The logging menu showing how to log the NTP requests](https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/3/2/1/0/NTP_Logging.png)](https://cdn.sparkfun.com/assets/learn_tutorials/3/2/1/0/NTP_Logging.png)
5151

52-
**Logging Menu - Log NTP Requests**
52+
*Logging Menu - Log NTP Requests*
5353

54-
![NTP requests log](https://cdn.sparkfun.com/assets/learn_tutorials/3/2/1/0/NTP_Log.png)](https://cdn.sparkfun.com/assets/learn_tutorials/3/2/1/0/NTP_Log.png)
54+
[![NTP requests log](https://cdn.sparkfun.com/assets/learn_tutorials/3/2/1/0/NTP_Log.png)](https://cdn.sparkfun.com/assets/learn_tutorials/3/2/1/0/NTP_Log.png)
5555

56-
**Logged NTP Requests**
56+
*Logged NTP Requests*
5757

5858
NTP uses its own epoch - midnight January 1st 1900. This is different to the standard Unix epoch - midnight January 1st 1970 - and the GPS epoch - midnight January 6th 1980. The times shown in the log and diagnostic messages use the NTP epoch. You can use online calculators to convert between the different epochs:
5959

‎docs/repair.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -194,11 +194,11 @@ Taking the Reference Station apart is really easy:
194194
* Disconnect all cables
195195

196196
* Unplug the green 10-way 3.5mm I/O connector
197-
* This makes it easy to remove the main PCB from the enclosure
198-
* The connector is a firm fit. You may need to rock it from side to side as you unplug it
197+
* This makes it easy to remove the main PCB from the enclosure
198+
* The connector is a firm fit. You may need to rock it from side to side as you unplug it
199199

200200
* Unscrew the four screws holding the front panel in place
201-
* We recommend removing the front panel first, so you can unplug the OLED display
201+
* We recommend removing the front panel first, so you can unplug the OLED display
202202

203203
* Remove the front panel
204204

0 commit comments

Comments
 (0)