Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -11,19 +11,14 @@
11	11	\\**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:**
12	12
13	13	* End node console to show the Join freuqency and DR. (If possible)
14		-
15	15	* Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
16		-
17	17	* Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normaly possible)
18		-
19	19	* End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
20		-
21	21	* 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)
22	22
23	23	(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
24	24
25	25	* If the device is sending join request to server?
26		-
27	27	* What frequency the device is sending?
28	28
29	29	[[image:image-20220526164956-15.png||height="591" width="1153"]]
...	...	@@ -35,7 +35,6 @@
35	35	(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
36	36
37	37	* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
38		-
39	39	* If the gateway gets the Join Accept message from server and transmit it via LoRa?
40	40
41	41	[[image:image-20220526163608-2.png]]
...	...	@@ -47,9 +47,7 @@
47	47	(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
48	48
49	49	* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
50		-
51	51	* 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.
52		-
53	53	* If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
54	54
55	55	[[image:image-20220526163633-3.png]]
...	...	@@ -214,6 +214,8 @@
214	214
215	215	* 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.**
216	216
	209	+
	210	+
217	217	== 5.2 See Debug Info ==
218	218
219	219
...	...	@@ -273,13 +273,13 @@
273	273	)))
274	274
275	275	(((
276		-* (% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
	270	+(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
	271	+(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
	272	+(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
	273	+(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
277	277
278		-* (% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
279	279
280		-* (% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
281		-
282		-* (% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
	276	+
283	283	)))
284	284
285	285	(((
...	...	@@ -322,14 +322,12 @@
322	322	(% 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:**
323	323
324	324	* End node console to show the transmit freuqency and DR.
325		-
326	326	* Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
327		-
328	328	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
329		-
330	330	* End Node traffic (from server UI) to shows end node activity in server.
331	331
332	332
	324	+
333	333	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
334	334
335	335
...	...	@@ -362,9 +362,7 @@
362	362	(% style="color:blue" %)**1. LHT65 End device configure:**
363	363
364	364	**Change to ABP Mode:  AT+NJM=0**
365		-
366	366	**Change to fix frequency:  AT+CHS=904900000**
367		-
368	368	**Change to fix DR:  AT+DR=0**
369	369
370	370
...	...	@@ -436,22 +436,15 @@
436	436
437	437	* (((
438	438	If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
439		-)))
440	440
441		-(% class="wikigeneratedid" %)
442		-3）Wrong Regional Parameters version selected
443		- We generally use versions above 1.0.2
444	444
445		-(% class="wikigeneratedid" %)
446		-[[image:image-20230322163227-1.png]]
	431	+
	432	+)))
447	447
448		-(% class="wikigeneratedid" %)
449		-4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
450		-
451	451	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
452	452
453	453
454		-(% style="color:blue" %)**Why this happen:**
	437	+**Why this happen:**
455	455
456	456	For US915, AU915 or AS923 frequencies.It is possible because: .
457	457
...	...	@@ -460,7 +460,7 @@
460	460	When the server adjusts end node data rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the end 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 following an additional 00 data packet to handle this MAC command response.
461	461
462	462
463		-(% style="color:blue" %)**How to solve:**
	446	+**How to solve:**
464	464
465	465	Solution: Use the decoder to filter out this 0x00 packet.
466	466

image-20230322163227-1.png

Author

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

Size

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

Content