Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 0 removed)
  • image-20220531161828-1.png

Details

Page properties

Content

...	...	@@ -1,4 +1,4 @@
1		-**~ Contents:**
	1	+**~ Table of Contents:**
2	2
3	3	{{toc/}}
4	4
...	...	@@ -6,6 +6,7 @@
6	6
7	7	= 1. OTAA Join Process Debug =
8	8
	9	+
9	9	These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
10	10	\\**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
11	11
...	...	@@ -15,8 +15,10 @@
15	15	* End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
16	16	* End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
17	17
18		-**~1. End Device Join Screen shot, we can check:**
19	19
	20	+
	21	+(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
	22	+
20	20	* If the device is sending join request to server?
21	21	* What frequency the device is sending?
22	22
...	...	@@ -25,8 +25,9 @@
25	25	Console Output from End device to see the transmit frequency
26	26
27	27
28		-**2. Gateway packet traffic in gateway web or ssh. we can check:**
29	29
	32	+(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
	33	+
30	30	* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
31	31	* If the gateway gets the Join Accept message from server and transmit it via LoRa?
32	32
...	...	@@ -35,7 +35,7 @@
35	35	Console Output from Gateway to see packets between end node and server.
36	36
37	37
38		-**3. Gateway Traffic Page in LoRaWAN Server**
	42	+(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
39	39
40	40	* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
41	41	* If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
...	...	@@ -46,7 +46,7 @@
46	46	The Traffic for the End node in the server, use TTN as example
47	47
48	48
49		-**4. Data Page in LoRaWAN server**
	53	+(% style="color:blue" %)**4. Data Page in LoRaWAN server**
50	50
51	51	* If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
52	52
...	...	@@ -59,8 +59,10 @@
59	59	Check if OTAA Keys match the keys in device
60	60
61	61
	66	+
62	62	= 2. Notice of US915/CN470/AU915 Frequency band =
63	63
	69	+
64	64	(((
65	65	If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
66	66	)))
...	...	@@ -103,10 +103,13 @@
103	103
104	104	AU915 Channels
105	105
	112	+
106	106	[[image:image-20220526163941-8.png]]
107	107
108	108	(((
109	109	CN470 Channels
	117	+
	118	+
110	110	)))
111	111
112	112	(((
...	...	@@ -117,6 +117,8 @@
117	117
118	118	(((
119	119	TTN FREQUENCY PLAN
	129	+
	130	+
120	120	)))
121	121
122	122	(((
...	...	@@ -124,8 +124,10 @@
124	124	)))
125	125
126	126
	138	+
127	127	= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
128	128
	141	+
129	129	In this case, we can check if the frequency band matches in End Node, Gateway and LoRaWAN server. A typical case is using US915 in ChirpStack server as below:
130	130
131	131	* **End node** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
...	...	@@ -145,8 +145,10 @@
145	145	)))
146	146
147	147
	161	+
148	148	= 4. Transmision on ABP Mode =
149	149
	164	+
150	150	(((
151	151	In ABP mode, there is a Frame Counter Checks. With this check enabled, the server will only accept the frame with a higher counter. If you reboot the device in ABP mode, the device will start from count 0, so you won't be able to see the frame update in server.
152	152	)))
...	...	@@ -172,10 +172,12 @@
172	172	Disable Frame Counter Check in ABP Mode
173	173
174	174
	190	+
175	175	= 5. Downstream Debug =
176	176
177	177	== 5.1 How it work ==
178	178
	195	+
179	179	LoRaWAN End node will open two receive windows to receive the downstream data. If the downstream packets arrive the end node at these receive windows, the end node will be able to get this packet and process it.
180	180
181	181	(((
...	...	@@ -182,10 +182,11 @@
182	182	Depends on Class A or Class C, the receive windows will be a little difference,
183	183	)))
184	184
185		-[[image:image-20220526164547-11.png]]
	202	+[[image:image-20220531161828-1.png]]
186	186
187	187	receive windows for Class A and Class C
188	188
	206	+
189	189	Below are the requirement for the End Device to receive the packets.
190	190
191	191	* The End Device must open the receive windows: RX1 or RX2
...	...	@@ -192,14 +192,16 @@
192	192	* The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
193	193	* This downstream packet must arrive to the end node while RX1 or RX2 is open.
194	194	* This packet must match the frequency of the RX1 or RX2 window.
195		-* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). **This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.**
	213	+* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). (% style="color:red" %)**This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.**
196	196
197	197
198	198
	217	+
199	199	== 5.2 See Debug Info ==
200	200
	220	+
201	201	(((
202		-**For LoRaWAN Server**
	222	+(% style="color:blue" %)**For LoRaWAN Server**
203	203	)))
204	204
205	205	(((
...	...	@@ -228,8 +228,9 @@
228	228	)))
229	229
230	230
	251	+
231	231	(((
232		-**For LoRaWAN Gateway**
	253	+(% style="color:blue" %)**For LoRaWAN Gateway**
233	233	)))
234	234
235	235	(((
...	...	@@ -243,8 +243,9 @@
243	243	)))
244	244
245	245
	267	+
246	246	(((
247		-**For End Node**
	269	+(% style="color:blue" %)**For End Node**
248	248	)))
249	249
250	250	(((
...	...	@@ -252,23 +252,19 @@
252	252	)))
253	253
254	254	(((
	277	+(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
	278	+(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
	279	+(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
	280	+(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
	281	+
	282	+
255	255
256	256	)))
257	257
258	258	(((
259		-(% class="box infomessage" %)
260		-(((
261		-AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
262		-AT+RX2DR=3      ~-~--> The RX2 DataRate
263		-AT+RX1DL=1000   ~-~--> Receive Delay 1
264		-AT+RX2DL=2000   ~-~--> Receive Delay 2
	287	+(% style="color:blue" %)**when the device running, we can see below info:**
265	265	)))
266		-)))
267	267
268		-(((
269		-**when the device running, we can see below info:**
270		-)))
271		-
272	272	{{{ [12502]***** UpLinkCounter= 0 *****
273	273	[12503]TX on freq 868500000 Hz at DR 0
274	274	[13992]txDone
...	...	@@ -279,10 +279,12 @@
279	279
280	280	(((
281	281
	300	+
	301	+
282	282	)))
283	283
284	284	(((
285		-**Another message:**
	305	+(% style="color:blue" %)**Another message:**
286	286	)))
287	287
288	288	{{{ [12502]***** UpLinkCounter= 0 *****
...	...	@@ -297,8 +297,10 @@
297	297	1:0012345678}}}
298	298
299	299
300		-== 5.3 If problem doesn’t solve ==
301	301
	321	+== 5.3 If problem doesn't solve ==
	322	+
	323	+
302	302	(% style="color:red" %)**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
303	303
304	304	* End node console to show the transmit freuqency and DR.
...	...	@@ -308,8 +308,10 @@
308	308
309	309
310	310
	333	+
311	311	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
312	312
	336	+
313	313	(((
314	314	In LoRaWAN, the gatewat will use the frequency specify by the server to transmit a packet as downlink purpose. Each Frequency band has different downlink frequency. and the gateway has a frequency range limited to transmit downlink.
315	315	)))
...	...	@@ -333,30 +333,23 @@
333	333	)))
334	334
335	335
	360	+
336	336	= 7. Decrypt a LoRaWAN Packet =
337	337
338		-~1. LHT65 End device configure:
339	339
340		-(% class="box infomessage" %)
341		-(((
342		-**Change to ABP Mode: AT+NJM=0**
343		-)))
	364	+(% style="color:blue" %)**1. LHT65 End device configure:**
344	344
345		-(% class="box infomessage" %)
346		-(((
347		-**Change to fix frequency: AT+CHS=904900000**
348		-)))
	366	+**Change to ABP Mode:  AT+NJM=0**
	367	+**Change to fix frequency:  AT+CHS=904900000**
	368	+**Change to fix DR:  AT+DR=0**
349	349
350		-(% class="box infomessage" %)
351		-(((
352		-**Change to fix DR: AT+DR=0**
353		-)))
354	354
355	355	[[image:image-20220526165525-16.png]]
356	356
357	357
358		-2. In LG02 , configure to receive above message
359	359
	375	+(% style="color:blue" %)**2. In LG02 , configure to receive above message**
	376	+
360	360	[[image:image-20220526165612-17.png]]
361	361
362	362
...	...	@@ -365,8 +365,9 @@
365	365	[[image:image-20220526171112-21.png]]
366	366
367	367
368		-3. Decode the info in web
369	369
	386	+(% style="color:blue" %)**3. Decode the info in web**
	387	+
370	370	[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
371	371
372	372	Need these three fields:
...	...	@@ -377,6 +377,7 @@
377	377
378	378	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
379	379
	398	+
380	380	[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111]]
381	381
382	382	[[image:image-20220526171029-20.png]]
...	...	@@ -386,15 +386,19 @@
386	386	)))
387	387
388	388
	408	+
389	389	= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
390	390
	411	+
391	391	Since firmware v1.8, LHT65 will send MAC command to request time, in the case if DR only support max 11 bytes, this MAC command will be bundled to a separate uplink payload with 0x00.
392	392
393	393
	415	+
394	394	= 9. Why do I see a "MIC Mismatch" error message from the server? =
395	395
	418	+
396	396	(((
397		-1)If the user receives a "MIC Mismatch" message after registering the node on the server.
	420	+1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
398	398	)))
399	399
400	400	(((
...	...	@@ -416,11 +416,14 @@
416	416	* (((
417	417	If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
418	418
	442	+
	443	+
419	419
420	420	)))
421	421
422	422	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
423	423
	449	+
424	424	* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
425	425
426	426	(((
...	...	@@ -438,11 +438,13 @@
438	438	Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to [[david.huang@dragino.cc>>mailto:david.huang@dragino.cc]]
439	439
440	440
	467	+
441	441
442	442	)))
443	443
444	444	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
445	445
	473	+
446	446	(((
447	447	It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
448	448	)))
...	...	@@ -473,6 +473,8 @@
473	473
474	474	(((
475	475	You can rewrites the keys by running commands in AT Console
	504	+
	505	+
476	476	)))
477	477
478	478	(((
...	...	@@ -497,8 +497,16 @@
497	497
498	498	(((
499	499	(Any combination of 16 bit codes can be used）
	530	+
	531	+
	532	+
	533	+= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
500	500	)))
501	501
502	502
	537	+Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
	538	+
	539	+
	540	+
503	503	(% class="wikigeneratedid" %)
504	504

image-20220531161828-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+98.6 KB

Content