Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -151,7 +151,7 @@
151	151	== 2.1 How it works ==
152	152
153	153
154		-The SN50v3-LB is configured as (% style="color:#037691" %)**LoRaWAN OTAA Class A**(%%) mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and press the button to activate the S31x-LB. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes.
	154	+The SN50v3-LB is configured as (% style="color:#037691" %)**LoRaWAN OTAA Class A**(%%) mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and press the button to activate the SN50v3-LB. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes.
155	155
156	156
157	157	== 2.2 ​Quick guide to connect to LoRaWAN server (OTAA) ==
...	...	@@ -159,7 +159,7 @@
159	159
160	160	Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LPS8v2>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/228-lps8v2.html]] as a LoRaWAN gateway in this example.
161	161
162		-The LPS8V2 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server.
	162	+The LPS8v2 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server.
163	163
164	164
165	165	(% style="color:blue" %)**Step 1:**(%%) Create a device in TTN with the OTAA keys from SN50v3-LB.
...	...	@@ -208,7 +208,7 @@
208	208	=== 2.3.1 Device Status, FPORT~=5 ===
209	209
210	210
211		-Users can use the downlink command(**0x26 01**) to ask SN50v3 to send device configure detail, include device configure status. SN50v3 will uplink a payload via FPort=5 to server.
	211	+Users can use the downlink command(**0x26 01**) to ask SN50v3-LB to send device configure detail, include device configure status. SN50v3-LB will uplink a payload via FPort=5 to server.
212	212
213	213	The Payload format is as below.
214	214
...	...	@@ -221,7 +221,7 @@
221	221	Example parse in TTNv3
222	222
223	223
224		-(% style="color:#037691" %)**Sensor Model**(%%): For SN50v3, this value is 0x1C
	224	+(% style="color:#037691" %)**Sensor Model**(%%): For SN50v3-LB, this value is 0x1C
225	225
226	226	(% style="color:#037691" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version
227	227
...	...	@@ -286,7 +286,7 @@
286	286
287	287	(% style="color:red" %) **Important Notice:**
288	288
289		-~1. Some working modes has payload more than 12 bytes, The US915/AU915/AS923 frequency bands' definition has maximum 11 bytes in (% style="color:blue" %)**DR0**(%%). Server sides will see NULL payload while SN50v3 transmit in DR0 with 12 bytes payload.
	289	+~1. Some working modes has payload more than 12 bytes, The US915/AU915/AS923 frequency bands' definition has maximum 11 bytes in (% style="color:blue" %)**DR0**(%%). Server sides will see NULL payload while SN50v3-LB transmit in DR0 with 12 bytes payload.
290	290
291	291	2. All modes share the same Payload Explanation from HERE.
292	292