Summary

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

Details

Page properties

Content

...	...	@@ -11,14 +11,19 @@
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	+
14	14	* Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
	16	+
15	15	* Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normaly possible)
	18	+
16	16	* End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
	20	+
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	19	(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
20	20
21	21	* If the device is sending join request to server?
	26	+
22	22	* What frequency the device is sending?
23	23
24	24	[[image:image-20220526164956-15.png||height="591" width="1153"]]
...	...	@@ -30,6 +30,7 @@
30	30	(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
31	31
32	32	* 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	+
33	33	* If the gateway gets the Join Accept message from server and transmit it via LoRa?
34	34
35	35	[[image:image-20220526163608-2.png]]
...	...	@@ -41,7 +41,9 @@
41	41	(% style="color:blue" %)**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.
	50	+
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.
	52	+
45	45	* 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.
46	46
47	47	[[image:image-20220526163633-3.png]]
...	...	@@ -267,13 +267,13 @@
267	267	)))
268	268
269	269	(((
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
	278	+* (% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
274	274
	280	+* (% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
275	275
276		-
	282	+* (% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
	283	+
	284	+* (% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
277	277	)))
278	278
279	279	(((
...	...	@@ -316,12 +316,13 @@
316	316	(% 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:**
317	317
318	318	* End node console to show the transmit freuqency and DR.
	327	+
319	319	* Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
	329	+
320	320	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
	331	+
321	321	* End Node traffic (from server UI) to shows end node activity in server.
322	322
323		-
324		-
325	325	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
326	326
327	327
...	...	@@ -354,7 +354,9 @@
354	354	(% style="color:blue" %)**1. LHT65 End device configure:**
355	355
356	356	**Change to ABP Mode:  AT+NJM=0**
	366	+
357	357	**Change to fix frequency:  AT+CHS=904900000**
	368	+
358	358	**Change to fix DR:  AT+DR=0**
359	359
360	360
...	...	@@ -434,7 +434,7 @@
434	434	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
435	435
436	436
437		-**Why this happen:**
	448	+(% style="color:blue" %)**Why this happen:**
438	438
439	439	For US915, AU915 or AS923 frequencies.It is possible because: .
440	440
...	...	@@ -443,7 +443,7 @@
443	443	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.
444	444
445	445
446		-**How to solve:**
	457	+(% style="color:blue" %)**How to solve:**
447	447
448	448	Solution: Use the decoder to filter out this 0x00 packet.
449	449