Summary

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

Details

Page properties

Content

...	...	@@ -16,6 +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	+
	20	+
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?
...	...	@@ -37,6 +37,7 @@
37	37	Console Output from Gateway to see packets between end node and server.
38	38
39	39
	42	+
40	40	(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
41	41
42	42	* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
...	...	@@ -48,6 +48,7 @@
48	48	The Traffic for the End node in the server, use TTN as example
49	49
50	50
	54	+
51	51	(% style="color:blue" %)**4. Data Page in LoRaWAN server**
52	52
53	53	* 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,6 +56,7 @@
56	56
57	57	The data for the end device set in server
58	58
	63	+
59	59	[[image:image-20220526163732-5.png]]
60	60
61	61	Check if OTAA Keys match the keys in device
...	...	@@ -103,6 +103,7 @@
103	103
104	104	US915 Channels
105	105
	111	+
106	106	[[image:image-20220526163926-7.png]]
107	107
108	108	AU915 Channels
...	...	@@ -211,6 +211,7 @@
211	211	* 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.**
212	212
213	213
	220	+
214	214	== 5.2 See Debug Info ==
215	215
216	216
...	...	@@ -325,6 +325,7 @@
325	325	* End Node traffic (from server UI) to shows end node activity in server.
326	326
327	327
	335	+
328	328	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
329	329
330	330
...	...	@@ -441,6 +441,8 @@
441	441	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
442	442
443	443
	452	+**Why this happen:**
	453	+
444	444	For US915, AU915 or AS923 frequencies.It is possible because: .
445	445
446	446	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.
...	...	@@ -447,8 +447,11 @@
447	447
448	448	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.
449	449
450		-Solution: Use the decoder to filter out this 00 packet.
451	451
	461	+**How to solve:**
	462	+
	463	+Solution: Use the decoder to filter out this 0x00 packet.
	464	+
452	452	Some node decoders may not have the filter function, or you need decoders of other servers and formats. Please send an email to [[support@dragino.com>>mailto:support@dragino.com]]
453	453
454	454

image-20221215223215-1.png

Author

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

Size

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

Content