Skip to content

Commit 7278efc

Browse files
committed
Docs: Update LED states. Update mkdocs config.
1 parent 1700e72 commit 7278efc

File tree

6 files changed

+54
-134
lines changed

6 files changed

+54
-134
lines changed

docs/hardware_overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ For security reasons, the radios are both set to the lowest transmission power t
112112

113113
The firmware on the LoRaSerial can be upgraded from a computer without ever having to open the unit. In the rare case that the SAMD21 needs to be forced into bootloader mode the reset button should be quickly double-tapped. The unit will then enter bootloader mode and wait for new firmware or for a reset event (button is pressed or power is cycled).
114114

115-
Please see [Updating LoRaSerial Firmware](docs\firmware_update.md) for more information.
115+
Please see [Updating LoRaSerial Firmware](http://docs.sparkfun.com/SparkFun_LoRaSerial/firmware_update/) for more information.
116116

117117
### GPIO
118118

-828 Bytes
Loading

docs/index.md

Lines changed: 0 additions & 18 deletions
This file was deleted.

docs/led_states.md

Lines changed: 37 additions & 104 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ A variety of LEDs are visible on the LoRaSerial radio to give the user feedback
66

77
*LEDs on the LoRaSerial*
88

9-
First lets define the LEDs on the LoRaSerial device. The following diagram shows the various LEDs:
9+
The following diagram shows the various LEDs on the LoRaSerial device:
1010

1111
Antenna Qwiic
1212
+---------------------------+
@@ -22,86 +22,15 @@ First lets define the LEDs on the LoRaSerial device. The following diagram show
2222
+---------------------------+
2323
USB Serial
2424

25-
The red LED is the power indicator. G1 through G4 in the diagram above are all green LEDs.
25+
The red LED is the power indicator. G1 through G4 in the diagram above are all green LEDs.
2626

27-
The LED behavior may be changed by using the AT-SelectLedUse command and setting the value to one of the mode numbers described in the sections below. As an example, if the radio is in multipoint mode the following serial data sequence causes the LEDs to display more information about the radio behavior.
27+
## Radio Reset
2828

29-
+++
30-
AT-SelectLedUse=0
31-
ATO
32-
33-
## LED Mode 0 (LEDS_MULTIPOINT)
34-
35-
When the radio is in multipoint mode, selecting this mode for the LEDs provides additional insight into the radio's behavior.
36-
37-
* The G4 LED pulses when the radio transmits a frame.
38-
* The G3 LED is pulse width modulated to indicate the last received RSSI level.
39-
* The G2 LED turns on when the link is up (data can pass).
40-
* The G1 LED pulses when the radio successfully receives a frame.
41-
* The blue LED pulses on the server radio when the server transmits a HEARTBEAT frame. The blue LED pulses on the client radio when the client successfully receives a HEARTBEAT frame from the server.
42-
* The yellow LED pulses each time a channel hop (frequency change) occurs.
43-
44-
## LED Mode 1 (Default: LEDS_P2P)
45-
46-
When the radio is in point-to-point mode, selecting this mode for the LEDs provides additional insight into the radio's behavior.
47-
48-
* The G4 LED pulses when the radio transmits a frame.
49-
* The G3 LED is pulse width modulated to indicate the last received RSSI level.
50-
* The G2 LED is off.
51-
* The G1 LED pulses when the radio successfully receives a frame.
52-
* The blue LED pulses on the radio successfully receives a HEARTBEAT frame.
53-
* The yellow LED pulses each time a channel hop (frequency change) occurs.
54-
55-
## LED Mode 2 (LEDS_VC)
56-
57-
When the radio is in virtual-circuit mode, selecting this mode for the LEDs provides additional insight into the radio's behavior.
58-
59-
* The G4 LED pulses when the radio transmits a frame.
60-
* The G3 LED is pulse width modulated to indicate the last received RSSI level.
61-
* The G2 LED pulses when serial data is received.
62-
* The G1 LED pulses when the radio successfully receives a frame.
63-
* The blue LED pulses on the server radio when the server transmits a HEARTBEAT frame. The blue LED pulses on the client radio when the client successfully receives a HEARTBEAT frame from the server.
64-
* The yellow LED pulses each time a channel hop (frequency change) occurs.
65-
66-
## LED Mode 3 (LEDS_RADIO_USE)
67-
68-
This mode is useful for users who want additional LED feedback about the RF link.
69-
70-
* The G4 LED pulses when the radio transmits a frame.
71-
* The G3 LED is pulse width modulated to indicate the last received RSSI level.
72-
* The G2 LED turns on when the link is up (data can pass).
73-
* The G1 LED pulses when the radio successfully receives a frame.
74-
* The blue LED will blink when the radio receives a bad frame.
75-
* The yellow LED will blink when the radio receives a duplicate frame or receives frame where the software CRC does not match.
76-
77-
## LED Mode 4 (Default: LEDS_RSSI)
78-
79-
In the Received Signal Strength Indicator (RSSI) mode uses the green LEDs to indicate ranges of signal strengths:
80-
81-
* The RSSI LEDs indicate the signal strength of the last received packet:
82-
* -70 < RSSI: All green LEDs lit (strong)
83-
* -100 < RSSI <= -70: G3, G2, G1 LEDs lit, G4 off
84-
* -120 < RSSI <= -100: G2, G1 LEDs lit, G4 and G3 off
85-
* -150 < RSSI <= -120: G1 LED lit, all G4, G3 and G2 off (weak)
86-
* RSSI <= -150: <= All green LEDs off
87-
* The blue TX LED indicates when serial data is received over the radio and sent to the host, either over USB or hardware serial.
88-
* The yellow RX LED indicates when serial data is received from the host and sent over the radio.
89-
90-
## LED Mode 5 (LEDS_BUTTON_PRESS)
91-
92-
The button press mode is an internal mode used to indicate the state of the button press. The green LEDs are counting seconds. The following blue and yellow LED behavior occurs:
93-
94-
* Press time < 4 seconds: Blue LED is off and if in command mode or not performing training the yellow LED is off. Otherewise if not in command mode and performing training the yellow LED is flashing and upon button release the radio exits training.
95-
96-
* 4 seconds <= button press time < 8 seconds: Yellow LED is off and if in command mode or not performing training the blue LED is off. Otherewise if not in command mode and performing training the blue LED is flashing and upon button release the radio enters training in client mode.
97-
98-
* 8 seconds <= button press time < 16 seconds: If in command mode or not performing training both LEDs are off. Otherewise if not in command mode and performing training the both LEDs are flashing and upon button release the radio enters training in server mode.
29+
When the device is first powered on or is reset, all LEDs will blink quickly three times indicating system reset.
9930

100-
* 16 seconds <= button press time: Reset pattern caused by a system reset
31+
## Training
10132

102-
## LED Mode 7 (LEDS_CYLON)
103-
104-
The cylon eye pattern in green is typically used to indicate radio training. One green LED is lit at a time and the lit LED moves from side to side.
33+
During Training, the green RSSI LEDs will cylon back and forth. One green LED is lit at a time and the lit LED moves from side to side.
10534

10635
G4 G3 G2 G1
10736
X
@@ -114,41 +43,45 @@ The cylon eye pattern in green is typically used to indicate radio training. On
11443
X
11544
...
11645

117-
* The blue LED will blink when the radio transmits a frame.
118-
* The yellow LED will blink when the radio successfully receives a frame.
119-
120-
## LED Mode 8 (LEDS_ALL_OFF)
121-
122-
This is a testing pattern with all LEDs off.
123-
124-
## LED Mode 9 (LEDS_BLUE_ON)
125-
126-
This is a testing pattern with only the blue LED on.
46+
Once training is complete, the radio will reset causing all LEDS to blink.
12747

128-
## LED Mode 10 (LEDS_YELLOW_ON)
48+
## LED Mode - LEDS_RSSI (4)
12949

130-
This is a testing pattern with only the yellow LED on.
50+
This is the default mode. The RSSI LEDs will indicate the link's signal strength.
13151

132-
## LED Mode 11 (LEDS_GREEN_1_ON)
52+
The LED behavior may be changed by using the **AT-SelectLedUse** command and setting the value to one of the mode numbers described in the sections below. As an example, the following commands cause the LEDs to display different information about the radio's behavior.
13353

134-
This is a testing pattern with only the G1 LED on.
135-
136-
## LED Mode 12 (LEDS_GREEN_2_ON)
137-
138-
This is a testing pattern with only the G2 LED on.
139-
140-
## LED Mode 13 (LEDS_GREEN_3_ON)
54+
+++
55+
AT-SelectLedUse=4
56+
ATO
14157

142-
This is a testing pattern with only the G3 LED on.
58+
* The RSSI LEDs indicate the signal strength of the last received packet:
59+
* -70 < RSSI: All green LEDs lit (strong)
60+
* -100 < RSSI <= -70: G3, G2, G1 LEDs lit, G4 off
61+
* -120 < RSSI <= -100: G2, G1 LEDs lit, G4 and G3 off
62+
* -150 < RSSI <= -120: G1 LED lit, all G4, G3 and G2 off (weak)
63+
* RSSI <= -150: <= All green LEDs off
64+
* The blue TX LED indicates when serial data is received over the radio and sent to the host, either over USB or hardware serial.
65+
* The yellow RX LED indicates when serial data is received from the host and sent over the radio.
14366

144-
## LED Mode 14 (LEDS_GREEN_4_ON)
67+
## LED Mode - LEDS_MULTIPOINT (0)
14568

146-
This is a testing pattern with only the G4 LED on.
69+
This mode gives the user insight into when the link is hopping and when a heartbeat is transmitted/received.
14770

148-
## LED Mode 15 (LEDS_ALL_OFF)
71+
* The G4 LED pulses when the radio transmits a frame.
72+
* The G3 LED is pulse width modulated to indicate the last received RSSI level.
73+
* The G2 LED turns on when the link is up (data can pass).
74+
* The G1 LED pulses when the radio successfully receives a frame.
75+
* The blue LED pulses on the server radio when the server transmits a HEARTBEAT frame. The blue LED pulses on the client radio when the client successfully receives a HEARTBEAT frame from the server.
76+
* The yellow LED pulses each time a channel hop (frequency change) occurs.
14977

150-
This is a testing pattern with all LEDs on.
78+
## LED Mode - LEDS_RADIO_USE (3)
15179

152-
## Other LED modes
80+
This mode gives the user insight into when a bad or duplicate frame is detected.
15381

154-
Undefined LED modes display the RSSI pattern (mode 4).
82+
* The G4 LED pulses when the radio transmits a frame.
83+
* The G3 LED is pulse width modulated to indicate the last received RSSI level.
84+
* The G2 LED turns on when the link is up (data can pass).
85+
* The G1 LED pulses when the radio successfully receives a frame.
86+
* The blue LED will blink when the radio receives a bad frame.
87+
* The yellow LED will blink when the radio receives a duplicate frame or receives a frame where the software CRC does not match.

docs/training.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,20 @@
22

33
Training is the process of passing a radio's set of parameters to other radios so that they can successfully communicate.
44

5-
There are two ways to initiate training:
6-
75
![Training button on LoRaSerial](Original/SparkFun_LoRaSerial_-_Train.png)
86

7+
*The train button on the LoRaSerial*
8+
9+
There are two ways to initiate training:
10+
911
* Pressing the **Train** button on the end of the LoRaSerial device
1012
* Entering the **ATT** command
1113

1214
Training is performed by a server radio sending parameters to the client radio. Upon reception, the client radio saves the parameters in non-volatile memory and then reboots with the new parameters.
1315

14-
Pressing and releasing the training button for different lengths of time initiates the following behaviors:
16+
Pressing and releasing the training button for different lengths of time initiates the following behaviors.
17+
18+
A ball-point pen is best for pressing the training button. *Be gentle.* The training button can be damaged with too much force.
1519

1620
## Training as Client
1721

mkdocs.yml

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,8 @@ site_name: SparkFun LoRaSerial Product Manual
33
site_description: A guide to the SparkFun LoRaSerial hardware, firmware, and features
44
site_url: https://sparkfun.github.io/SparkFun_LoRaSerial
55

6+
repo_name: sparkfun/SparkFun_LoRaSerial
7+
repo_url: https://github.com/sparkfun/SparkFun_LoRaSerial
68
edit_uri: edit/main/docs/
79

810
theme:
@@ -16,9 +18,9 @@ theme:
1618
code: Roboto Mono
1719
features:
1820
- content.code.annotate
19-
- navigation.tracking
20-
- navigation.tabs.sticky
21-
- navigation.tabs
21+
# - navigation.tracking
22+
# - navigation.tabs.sticky
23+
# - navigation.tabs
2224

2325
icon:
2426
repo: fontawesome/brands/github
@@ -40,9 +42,6 @@ plugins:
4042
- search
4143
- monorepo
4244

43-
repo_url: https://github.com/sparkfun/SparkFun_LoRaSerial
44-
repo_name: sparkfun/SparkFun_LoRaSerial
45-
4645
copyright: Copyright 2023 SparkFun Electronics (6333 Dry Creek Parkway, Niwot, Colorado 80503)
4746

4847
markdown_extensions:
@@ -74,8 +73,7 @@ extra:
7473
link: https://twitter.com/sparkfun
7574

7675
nav:
77-
- Software Specifics:
78-
- intro.md
76+
- Introduction: intro.md
7977
- quick_start.md
8078
- at_commands.md
8179
- led_states.md
@@ -84,3 +82,6 @@ nav:
8482
- firmware_update.md
8583
- hardware_overview.md
8684

85+
extra:
86+
version:
87+
provider: mike

0 commit comments

Comments
 (0)