Summary

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

Details

Page properties

Content

...	...	@@ -38,6 +38,7 @@
38	38	Console Output from Gateway to see packets between end node and server.
39	39
40	40
	41	+
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.
...	...	@@ -49,6 +49,7 @@
49	49	The Traffic for the End node in the server, use TTN as example
50	50
51	51
	53	+
52	52	(% style="color:blue" %)**4. Data Page in LoRaWAN server**
53	53
54	54	* 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.
...	...	@@ -57,6 +57,7 @@
57	57
58	58	The data for the end device set in server
59	59
	62	+
60	60	[[image:image-20220526163732-5.png]]
61	61
62	62	Check if OTAA Keys match the keys in device
...	...	@@ -104,6 +104,7 @@
104	104
105	105	US915 Channels
106	106
	110	+
107	107	[[image:image-20220526163926-7.png]]
108	108
109	109	AU915 Channels
...	...	@@ -212,7 +212,6 @@
212	212	* 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.**
213	213
214	214
215		-
216	216	== 5.2 See Debug Info ==
217	217
218	218
...	...	@@ -327,7 +327,6 @@
327	327	* End Node traffic (from server UI) to shows end node activity in server.
328	328
329	329
330		-
331	331	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
332	332
333	333
...	...	@@ -444,18 +444,23 @@
444	444	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
445	445
446	446
447		-* If you are using US915, AU915 or AS923 frequencies.It is possible because: .
	449	+**Why this happen:**
448	448
	451	+For US915, AU915 or AS923 frequencies.It is possible because: .
	452	+
449	449	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.
450	450
451		-When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the 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 an additional 00 data packet.
	455	+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.
452	452
453		-Solution: Use the decoder to filter out this 00 packet.
454	454
455		-Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to [[david.huang@dragino.cc>>mailto:david.huang@dragino.cc]]
	458	+**How to solve:**
456	456
	460	+Solution: Use the decoder to filter out this 0x00 packet.
457	457
	462	+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]]
458	458
	464	+
	465	+
459	459	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
460	460
461	461
...	...	@@ -525,6 +525,30 @@
525	525	Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
526	526
527	527
	535	+= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
528	528
	537	+
	538	+In US915, AU915 or CN470 frequency band, there are 8 subbands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Subband 2 in TTN. The gateway also configured to Subband 2 and cover eight channels in this subband. If the end node transfer data in Subband 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other subbands, for example subband 1, the packet won't arrive both gateway or LoRaWAN server.
	539	+
	540	+
	541	+In Dragino Sensors old version firmware (before early 2022), the subband is fixed the subband to 2 , but this cause a problem, the end node is hard to use in other subband and need program. So the new logic is as below:
	542	+
	543	+We have improved this, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join, In this case, In this case, the end node can support LoRaWAN servers with different subbands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
	544	+
	545	+* (((
	546	+Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
	547	+)))
	548	+* (((
	549	+Use the Join successful sub-band if the server doesn't include subband info in the OTAA Join Accept message ( TTN v2 doesn't include)
	550	+)))
	551	+
	552	+This change will make the activation time a littler longer but make sure the device can be used in any subband.
	553	+
	554	+
	555	+Below is a photo to show why it takes longer time for OTAA Join. We can see in 72 channels mode, why it takes more time to join success. If users want to have faster OTAA Join success, he can change default CHE to the subband he use.
	556	+
	557	+
	558	+[[image:image-20221215223215-1.png||height="584" width="1280"]]
	559	+
529	529	(% class="wikigeneratedid" %)
530	530

image-20221215223215-1.png

Author

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

Size

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

Content