Summary

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

Details

Page properties

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]]
...	...	@@ -275,13 +275,13 @@
275	275	)))
276	276
277	277	(((
278		-* (% 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
279	279
280		-* (% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
281	281
282		-* (% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
283		-
284		-* (% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
	276	+
285	285	)))
286	286
287	287	(((
...	...	@@ -324,13 +324,12 @@
324	324	(% 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:**
325	325
326	326	* End node console to show the transmit freuqency and DR.
327		-
328	328	* Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
329		-
330	330	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
331		-
332	332	* End Node traffic (from server UI) to shows end node activity in server.
333	333
	323	+
	324	+
334	334	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
335	335
336	336
...	...	@@ -363,9 +363,7 @@
363	363	(% style="color:blue" %)**1. LHT65 End device configure:**
364	364
365	365	**Change to ABP Mode:  AT+NJM=0**
366		-
367	367	**Change to fix frequency:  AT+CHS=904900000**
368		-
369	369	**Change to fix DR:  AT+DR=0**
370	370
371	371
...	...	@@ -445,7 +445,7 @@
445	445	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
446	446
447	447
448		-(% style="color:blue" %)**Why this happen:**
	437	+**Why this happen:**
449	449
450	450	For US915, AU915 or AS923 frequencies.It is possible because: .
451	451
...	...	@@ -454,7 +454,7 @@
454	454	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.
455	455
456	456
457		-(% style="color:blue" %)**How to solve:**
	446	+**How to solve:**
458	458
459	459	Solution: Use the decoder to filter out this 0x00 packet.
460	460