Summary

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

Details

Page properties

Content

...	...	@@ -16,8 +16,6 @@
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		-
21	21	(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
22	22
23	23	* If the device is sending join request to server?
...	...	@@ -39,7 +39,6 @@
39	39	Console Output from Gateway to see packets between end node and server.
40	40
41	41
42		-
43	43	(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
44	44
45	45	* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
...	...	@@ -51,7 +51,6 @@
51	51	The Traffic for the End node in the server, use TTN as example
52	52
53	53
54		-
55	55	(% style="color:blue" %)**4. Data Page in LoRaWAN server**
56	56
57	57	* 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.
...	...	@@ -60,7 +60,6 @@
60	60
61	61	The data for the end device set in server
62	62
63		-
64	64	[[image:image-20220526163732-5.png]]
65	65
66	66	Check if OTAA Keys match the keys in device
...	...	@@ -108,7 +108,6 @@
108	108
109	109	US915 Channels
110	110
111		-
112	112	[[image:image-20220526163926-7.png]]
113	113
114	114	AU915 Channels
...	...	@@ -217,7 +217,6 @@
217	217	* 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.**
218	218
219	219
220		-
221	221	== 5.2 See Debug Info ==
222	222
223	223
...	...	@@ -332,7 +332,6 @@
332	332	* End Node traffic (from server UI) to shows end node activity in server.
333	333
334	334
335		-
336	336	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
337	337
338	338
...	...	@@ -449,8 +449,6 @@
449	449	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
450	450
451	451
452		-**Why this happen:**
453		-
454	454	For US915, AU915 or AS923 frequencies.It is possible because: .
455	455
456	456	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.
...	...	@@ -457,11 +457,8 @@
457	457
458	458	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.
459	459
	450	+Solution: Use the decoder to filter out this 00 packet.
460	460
461		-**How to solve:**
462		-
463		-Solution: Use the decoder to filter out this 0x00 packet.
464		-
465	465	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]]
466	466
467	467

image-20221215223215-1.png

Author

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

Size

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

Content