Summary

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

Details

Page properties

Content

...	...	@@ -16,10 +16,8 @@
16	16	* End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
17	17	* 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)
18	18
	19	+**~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		-
23	23	* If the device is sending join request to server?
24	24	* What frequency the device is sending?
25	25
...	...	@@ -28,9 +28,8 @@
28	28	Console Output from End device to see the transmit frequency
29	29
30	30
	29	+**2. Gateway packet traffic in gateway web or ssh. we can check:**
31	31
32		-(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
33		-
34	34	* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
35	35	* If the gateway gets the Join Accept message from server and transmit it via LoRa?
36	36
...	...	@@ -39,7 +39,7 @@
39	39	Console Output from Gateway to see packets between end node and server.
40	40
41	41
42		-(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
	39	+**3. Gateway Traffic Page in LoRaWAN Server**
43	43
44	44	* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
45	45	* 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.
...	...	@@ -50,7 +50,7 @@
50	50	The Traffic for the End node in the server, use TTN as example
51	51
52	52
53		-(% style="color:blue" %)**4. Data Page in LoRaWAN server**
	50	+**4. Data Page in LoRaWAN server**
54	54
55	55	* 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.
56	56
...	...	@@ -63,7 +63,6 @@
63	63	Check if OTAA Keys match the keys in device
64	64
65	65
66		-
67	67	= 2. Notice of US915/CN470/AU915 Frequency band =
68	68
69	69
...	...	@@ -135,7 +135,6 @@
135	135	)))
136	136
137	137
138		-
139	139	= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
140	140
141	141
...	...	@@ -158,7 +158,6 @@
158	158	)))
159	159
160	160
161		-
162	162	= 4. Transmision on ABP Mode =
163	163
164	164
...	...	@@ -187,7 +187,6 @@
187	187	Disable Frame Counter Check in ABP Mode
188	188
189	189
190		-
191	191	= 5. Downstream Debug =
192	192
193	193	== 5.1 How it work ==
...	...	@@ -212,9 +212,6 @@
212	212	* This packet must match the frequency of the RX1 or RX2 window.
213	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.**
214	214
215		-
216		-
217		-
218	218	== 5.2 See Debug Info ==
219	219
220	220
...	...	@@ -248,7 +248,6 @@
248	248	)))
249	249
250	250
251		-
252	252	(((
253	253	(% style="color:blue" %)**For LoRaWAN Gateway**
254	254	)))
...	...	@@ -264,7 +264,6 @@
264	264	)))
265	265
266	266
267		-
268	268	(((
269	269	(% style="color:blue" %)**For End Node**
270	270	)))
...	...	@@ -279,7 +279,6 @@
279	279	(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
280	280	(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
281	281
282		-
283	283
284	284	)))
285	285
...	...	@@ -297,8 +297,6 @@
297	297
298	298	(((
299	299
300		-
301		-
302	302	)))
303	303
304	304	(((
...	...	@@ -317,7 +317,6 @@
317	317	1:0012345678}}}
318	318
319	319
320		-
321	321	== 5.3 If problem doesn't solve ==
322	322
323	323
...	...	@@ -330,7 +330,6 @@
330	330
331	331
332	332
333		-
334	334	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
335	335
336	336
...	...	@@ -357,7 +357,6 @@
357	357	)))
358	358
359	359
360		-
361	361	= 7. Decrypt a LoRaWAN Packet =
362	362
363	363
...	...	@@ -367,11 +367,9 @@
367	367	**Change to fix frequency:  AT+CHS=904900000**
368	368	**Change to fix DR:  AT+DR=0**
369	369
370		-
371	371	[[image:image-20220526165525-16.png]]
372	372
373	373
374		-
375	375	(% style="color:blue" %)**2. In LG02 , configure to receive above message**
376	376
377	377	[[image:image-20220526165612-17.png]]
...	...	@@ -382,7 +382,6 @@
382	382	[[image:image-20220526171112-21.png]]
383	383
384	384
385		-
386	386	(% style="color:blue" %)**3. Decode the info in web**
387	387
388	388	[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
...	...	@@ -395,7 +395,6 @@
395	395
396	396	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
397	397
398		-
399	399	[[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]]
400	400
401	401	[[image:image-20220526171029-20.png]]
...	...	@@ -405,19 +405,15 @@
405	405	)))
406	406
407	407
408		-
409	409	= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
410	410
411		-
412	412	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.
413	413
414	414
415		-
416	416	= 9. Why do I see a "MIC Mismatch" error message from the server? =
417	417
418		-
419	419	(((
420		-1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
	394	+1)If the user receives a "MIC Mismatch" message after registering the node on the server.
421	421	)))
422	422
423	423	(((
...	...	@@ -439,14 +439,11 @@
439	439	* (((
440	440	If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
441	441
442		-
443		-
444	444
445	445	)))
446	446
447	447	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
448	448
449		-
450	450	* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
451	451
452	452	(((
...	...	@@ -463,14 +463,11 @@
463	463	* (((
464	464	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]]
465	465
466		-
467		-
468	468
469	469	)))
470	470
471	471	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
472	472
473		-
474	474	(((
475	475	It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
476	476	)))
...	...	@@ -501,8 +501,6 @@
501	501
502	502	(((
503	503	You can rewrites the keys by running commands in AT Console
504		-
505		-
506	506	)))
507	507
508	508	(((
...	...	@@ -529,7 +529,6 @@
529	529	(Any combination of 16 bit codes can be used）
530	530
531	531
532		-
533	533	= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
534	534	)))
535	535