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,7 @@
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	+
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
	41	+
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
	53	+
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
	62	+
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
	110	+
106	106	[[image:image-20220526163926-7.png]]
107	107
108	108	AU915 Channels
...	...	@@ -441,6 +441,8 @@
441	441	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
442	442
443	443
	449	+**Why this happen:**
	450	+
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
	458	+**How to solve:**
	459	+
	460	+Solution: Use the decoder to filter out this 0x00 packet.
	461	+
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
...	...	@@ -522,6 +522,30 @@
522	522	Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
523	523
524	524
	535	+= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
525	525
	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	+
526	526	(% class="wikigeneratedid" %)
527	527

image-20221215223215-1.png

Author

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

Size

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

Content