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
...	...	@@ -210,6 +210,7 @@
210	210	* This packet must match the frequency of the RX1 or RX2 window.
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
	218	+
213	213	== 5.2 See Debug Info ==
214	214
215	215
...	...	@@ -323,6 +323,7 @@
323	323	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
324	324	* End Node traffic (from server UI) to shows end node activity in server.
325	325
	332	+
326	326	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
327	327
328	328
...	...	@@ -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