Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -16,9 +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		-(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
21		-
22	22	* If the device is sending join request to server?
23	23	* What frequency the device is sending?
24	24
...	...	@@ -27,9 +27,8 @@
27	27	Console Output from End device to see the transmit frequency
28	28
29	29
	29	+**2. Gateway packet traffic in gateway web or ssh. we can check:**
30	30
31		-(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
32		-
33	33	* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
34	34	* If the gateway gets the Join Accept message from server and transmit it via LoRa?
35	35
...	...	@@ -38,7 +38,7 @@
38	38	Console Output from Gateway to see packets between end node and server.
39	39
40	40
41		-(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
	39	+**3. Gateway Traffic Page in LoRaWAN Server**
42	42
43	43	* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
44	44	* 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.
...	...	@@ -49,7 +49,7 @@
49	49	The Traffic for the End node in the server, use TTN as example
50	50
51	51
52		-(% style="color:blue" %)**4. Data Page in LoRaWAN server**
	50	+**4. Data Page in LoRaWAN server**
53	53
54	54	* 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.
55	55
...	...	@@ -62,7 +62,6 @@
62	62	Check if OTAA Keys match the keys in device
63	63
64	64
65		-
66	66	= 2. Notice of US915/CN470/AU915 Frequency band =
67	67
68	68
...	...	@@ -134,7 +134,6 @@
134	134	)))
135	135
136	136
137		-
138	138	= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
139	139
140	140
...	...	@@ -157,7 +157,6 @@
157	157	)))
158	158
159	159
160		-
161	161	= 4. Transmision on ABP Mode =
162	162
163	163
...	...	@@ -186,7 +186,6 @@
186	186	Disable Frame Counter Check in ABP Mode
187	187
188	188
189		-
190	190	= 5. Downstream Debug =
191	191
192	192	== 5.1 How it work ==
...	...	@@ -211,8 +211,6 @@
211	211	* This packet must match the frequency of the RX1 or RX2 window.
212	212	* 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.**
213	213
214		-
215		-
216	216	== 5.2 See Debug Info ==
217	217
218	218
...	...	@@ -246,7 +246,6 @@
246	246	)))
247	247
248	248
249		-
250	250	(((
251	251	(% style="color:blue" %)**For LoRaWAN Gateway**
252	252	)))
...	...	@@ -262,7 +262,6 @@
262	262	)))
263	263
264	264
265		-
266	266	(((
267	267	(% style="color:blue" %)**For End Node**
268	268	)))
...	...	@@ -277,7 +277,6 @@
277	277	(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
278	278	(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
279	279
280		-
281	281
282	282	)))
283	283
...	...	@@ -295,8 +295,6 @@
295	295
296	296	(((
297	297
298		-
299		-
300	300	)))
301	301
302	302	(((
...	...	@@ -315,7 +315,6 @@
315	315	1:0012345678}}}
316	316
317	317
318		-
319	319	== 5.3 If problem doesn't solve ==
320	320
321	321
...	...	@@ -354,7 +354,6 @@
354	354	)))
355	355
356	356
357		-
358	358	= 7. Decrypt a LoRaWAN Packet =
359	359
360	360
...	...	@@ -364,11 +364,9 @@
364	364	**Change to fix frequency:  AT+CHS=904900000**
365	365	**Change to fix DR:  AT+DR=0**
366	366
367		-
368	368	[[image:image-20220526165525-16.png]]
369	369
370	370
371		-
372	372	(% style="color:blue" %)**2. In LG02 , configure to receive above message**
373	373
374	374	[[image:image-20220526165612-17.png]]
...	...	@@ -379,7 +379,6 @@
379	379	[[image:image-20220526171112-21.png]]
380	380
381	381
382		-
383	383	(% style="color:blue" %)**3. Decode the info in web**
384	384
385	385	[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
...	...	@@ -402,7 +402,6 @@
402	402	)))
403	403
404	404
405		-
406	406	= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
407	407
408	408
...	...	@@ -409,7 +409,6 @@
409	409	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.
410	410
411	411
412		-
413	413	= 9. Why do I see a "MIC Mismatch" error message from the server? =
414	414
415	415
...	...	@@ -444,18 +444,27 @@
444	444	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
445	445
446	446
447		-* If you are using US915, AU915 or AS923 frequencies.It is possible because: .
	427	+* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
448	448
449		-When using the frequency mentioned above, the server sometimes adjusts the Data Rate (DR) of the node, because the end node has Adaptive Data Rate (ADR) Enabled.
	429	+(((
	430	+When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
	431	+)))
450	450
	433	+(((
451	451	When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node,and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,so it will send a normal uplink packet, and an additional 00 data packet.
	435	+)))
452	452
	437	+* (((
453	453	Solution: Use the decoder to filter out this 00 packet.
454		-
	439	+)))
	440	+* (((
455	455	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]]
456	456
457	457
458	458
	445	+
	446	+)))
	447	+
459	459	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
460	460
461	461
...	...	@@ -517,7 +517,6 @@
517	517	(Any combination of 16 bit codes can be used）
518	518
519	519
520		-
521	521	= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
522	522	)))
523	523