Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 3 removed)
  • image-20240123182345-1.png
  • image-20240129142110-1.png
  • image-20240129142147-2.png

Details

Page properties

Content

...	...	@@ -4,7 +4,7 @@
4	4
5	5
6	6
7		-= 1. Join process page check =
	7	+= z =
8	8
9	9
10	10	These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
...	...	@@ -26,11 +26,12 @@
26	26
27	27	* What frequency the device is sending?
28	28
29		-[[image:image-20240123182345-1.png||height="605" width="946"]]
	29	+[[image:image-20220526164956-15.png||height="591" width="1153"]]
30	30
31		-Console Output from End device to see the transmit frequency.
	31	+Console Output from End device to see the transmit frequency
32	32
33	33
	34	+
34	34	(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
35	35
36	36	* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
...	...	@@ -42,6 +42,7 @@
42	42	Console Output from Gateway to see packets between end node and server.
43	43
44	44
	46	+
45	45	(% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
46	46
47	47	* Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
...	...	@@ -55,6 +55,7 @@
55	55	The Traffic for the End node in the server, use TTN as example.
56	56
57	57
	60	+
58	58	(% style="color:blue" %)**4. Data Page in LoRaWAN server**
59	59
60	60	* 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.
...	...	@@ -73,17 +73,17 @@
73	73
74	74
75	75	(((
76		-If user has problem to work with LoRaWAN server in band US915/AU915/CN470, he can check:
	79	+If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
77	77	)))
78	78
79	79	* (((
80		-What **sub-band** the server support?
	83	+What **sub-band** the server support ?
81	81	)))
82	82	* (((
83		-What is the **sub-band** the gateway support?
	86	+What is the **sub-band** the gateway support ?
84	84	)))
85	85	* (((
86		-What is the **sub-band** the end node is using?
	89	+What is the **sub-band** the end node is using ?
87	87	)))
88	88
89	89	(((
...	...	@@ -95,7 +95,7 @@
95	95	)))
96	96
97	97	(((
98		-In LoRaWAN protocol, the frequency bands US915, AU915, CN470 each includes at least 72 frequencies. Many gateways support only 8 or 16 frequencies, and server might support 8 frequency only. In this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies, because the end node will send data in many frequency that the gateway or server doesn't support.
	101	+In LoRaWAN protocol, the frequency bands US915, AU915, CN470 each includes at least 72 frequencies. Many gateways support only 8 or 16 frequencies, and server might support 8 frequency only. In this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies, because the end node will send data in many frequency that the gateway or server doesn,t support.
99	99	)))
100	100
101	101	(((
...	...	@@ -103,7 +103,7 @@
103	103	)))
104	104
105	105	(((
106		-Here are the frequency tables for these bands as reference:
	109	+Here are the freuqency tables for these bands as reference:
107	107	)))
108	108
109	109	[[image:image-20220526163801-6.png]]
...	...	@@ -213,6 +213,8 @@
213	213
214	214	* 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.**
215	215
	219	+(% class="wikigeneratedid" %)
	220	+== ==
216	216
217	217	== 5.2 See Debug Info ==
218	218
...	...	@@ -404,7 +404,7 @@
404	404	)))
405	405
406	406
407		-= 8. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
	412	+= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
408	408
409	409
410	410	Since firmware v1.8, LHT65 will send MAC command to request time, in the case if DR only support max 11 bytes, this MAC command will be bundled to a separate uplink payload with 0x00.
...	...	@@ -553,24 +553,24 @@
553	553	= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
554	554
555	555
556		-In US915, AU915 or CN470 frequency band, there are 8 sub-bands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Sub-band 2 in TTN. The gateway also configured to Sub-band 2 and cover eight channels in this sub-band. If the end node transfer data in Sub-band 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other sub-bands, for example sub-band 1, the packet won't arrive both gateway or LoRaWAN server.
	561	+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.
557	557
558	558
559		-In Dragino Sensors old version firmware (before early 2022), the sub-band is fixed the sub-band 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:
	564	+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:
560	560
561		-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 sub-bands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
	566	+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:
562	562
563	563	* (((
564		-Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band.
	569	+Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
565	565	)))
566	566	* (((
567		-Use the Join successful sub-band if the server doesn't include sub-band info in the OTAA Join Accept message (TTN v2 doesn't include).
	572	+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)
568	568	)))
569	569
570		-This change will make the activation time a little longer but make sure the device can be used in any sub-band.
	575	+This change will make the activation time a littler longer but make sure the device can be used in any subband.
571	571
572	572
573		-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 sub-band he uses.
	578	+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.
574	574
575	575
576	576	[[image:image-20221215223215-1.png||height="584" width="1280"]]

image-20240123182345-1.png

Author

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

Size

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

Content

image-20240129142110-1.png

Author

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

Size

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

Content

image-20240129142147-2.png

Author

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

Size

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

Content