Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 45.1 >
edited by Mengting Qiu
on 2024/01/23 16:17
To version < 63.1 >
edited by Mengting Qiu
on 2024/01/29 15:50
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 5  
6 6  
7 -= 1.(% style="display:none" %) (%%) OTAA Join Process Debug =
7 += 1. Join process page check =
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,12 +26,11 @@
26 26  
27 27  * What frequency the device is sending?
28 28  
29 -[[image:image-20220526164956-15.png||height="591" width="1153"]]
29 +[[image:image-20240129142147-2.png||height="736" width="964"]]
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 -
35 35  (% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
36 36  
37 37  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
... ... @@ -38,38 +38,36 @@
38 38  
39 39  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
40 40  
41 -[[image:image-20220526163608-2.png]]
40 +[[image:image-20240129151608-6.jpeg||height="725" width="1256"]]
42 42  
43 43  Console Output from Gateway to see packets between end node and server.
44 44  
45 45  
45 +(% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
46 46  
47 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
47 +* Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
48 48  
49 -* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
49 +* Does the server send back a Join Accept for the Join Request? If not, check that the key from the device matches the key you put into the server, or try to choose a different server route for that end device.
50 50  
51 -* If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
52 -
53 53  * If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
54 54  
55 -[[image:image-20220526163633-3.png]]
53 +[[image:image-20240129150821-5.jpeg||height="522" width="1264"]]
56 56  
57 -The Traffic for the End node in the server, use TTN as example
55 +The Traffic for the End node in the server, use TTN as example.
58 58  
59 59  
60 -
61 61  (% style="color:blue" %)**4. Data Page in LoRaWAN server**
62 62  
63 63  * 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.
64 64  
65 -[[image:image-20220526163704-4.png]]
62 +[[image:image-20240129142557-3.png||height="488" width="1267"]]
66 66  
67 67  The data for the end device set in server
68 68  
69 69  
70 -[[image:image-20220526163732-5.png]]
67 +[[image:image-20240129142631-4.png||height="637" width="1256"]]
71 71  
72 -Check if OTAA Keys match the keys in device
69 +Check if OTAA Keys match the keys in device.
73 73  
74 74  
75 75  = 2. Notice of US915/CN470/AU915 Frequency band =
... ... @@ -76,17 +76,17 @@
76 76  
77 77  
78 78  (((
79 -If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
76 +If user has problem to work with LoRaWAN server in band US915/AU915/CN470, he can check:
80 80  )))
81 81  
82 82  * (((
83 -What **sub-band** the server support ?
80 +What **sub-band** the server support?
84 84  )))
85 85  * (((
86 -What is the **sub-band** the gateway support ?
83 +What is the **sub-band** the gateway support?
87 87  )))
88 88  * (((
89 -What is the **sub-band** the end node is using ?
86 +What is the **sub-band** the end node is using?
90 90  )))
91 91  
92 92  (((
... ... @@ -98,7 +98,7 @@
98 98  )))
99 99  
100 100  (((
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.
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.
102 102  )))
103 103  
104 104  (((
... ... @@ -106,7 +106,7 @@
106 106  )))
107 107  
108 108  (((
109 -Here are the freuqency tables for these bands as reference:
106 +Here are the frequency tables for these bands as reference:
110 110  )))
111 111  
112 112  [[image:image-20220526163801-6.png]]
... ... @@ -131,7 +131,7 @@
131 131  If we look at the [[TTN network server frequency plan>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]], we can see the US915 frequency band use the channel 8~~15.So the End Node must work at the same frequency in US915 8~~15 channels for TTN server.
132 132  )))
133 133  
134 -[[image:image-20220526164052-9.png]]
131 +[[image:image-20240123151225-3.png||height="434" width="902"]]
135 135  
136 136  (((
137 137  TTN FREQUENCY PLAN
... ... @@ -145,7 +145,7 @@
145 145  
146 146  (% style="display:none" %) (%%)
147 147  
148 -= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
145 += 3. Why I see data lost/ is not periodically uplink？ Even the signal strength is good =
149 149  
150 150  
151 151  In this case, we can check if the frequency band matches in End Node, Gateway and LoRaWAN server. A typical case is using US915 in ChirpStack server as below:
... ... @@ -179,9 +179,11 @@
179 179  
180 180  (((
181 181  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
179 +
180 +[[image:image-20240123161737-4.png||height="395" width="763"]]
182 182  )))
183 183  
184 -[[image:image-20220526164508-10.png]]
183 +[[image:image-20240123161853-6.png||height="599" width="771"]]
185 185  
186 186  Disable Frame Counter Check in ABP Mode
187 187  
... ... @@ -194,7 +194,7 @@
194 194  LoRaWAN End node will open two receive windows to receive the downstream data. If the downstream packets arrive the end node at these receive windows, the end node will be able to get this packet and process it.
195 195  
196 196  (((
197 -Depends on Class A or Class C, the receive windows will be a little difference,
196 +Depends on Class A or Class C, the receive windows will be a little difference.
198 198  )))
199 199  
200 200  [[image:image-20220531161828-1.png]]
... ... @@ -226,24 +226,27 @@
226 226  )))
227 227  
228 228  (((
229 -Configure a downstream to the end device
228 +Configure a downlink to the end device
229 +
230 +[[image:image-20240129152412-8.png||height="486" width="1206"]]
230 230  )))
231 231  
232 -[[image:image-20220526164623-12.png]]
233 233  
234 234  (((
235 235  Set a downstream in TTN and see it is sent
236 236  )))
237 237  
238 +(% style="color:red" %)**Note: After the downlink command is successfully sent from the platform to the node, the downlink command is executed only after the platform receives the next uplink package from the node.**
238 238  
240 +
239 239  (((
240 -This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
242 +This downlink info will then pass to the gateway downlink list. and the DR which is used (SF7BW500) in US915 is DR5.
241 241  )))
242 242  
243 -[[image:image-20220526164650-13.png]]
245 +[[image:image-20240129152049-7.png||height="463" width="1166"]]
244 244  
245 245  (((
246 -Gateway Traffic can see this downstream info
248 +Gateway Traffic can see this downlink info
247 247  )))
248 248  
249 249  
... ... @@ -253,10 +253,10 @@
253 253  )))
254 254  
255 255  (((
256 -When the downstream packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragion Gateway, this can be checked by runinng "logread -f" in the SSH console. and see below:
258 +When the downlink packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragino Gateway, this can be checked by running "logread -f" in the SSH console. and see below:
257 257  )))
258 258  
259 -[[image:image-20220526164734-14.png]]
261 +[[image:image-20240129154321-9.png]]
260 260  
261 261  (((
262 262  Gateway Sent out this packet
... ... @@ -333,7 +333,7 @@
333 333  
334 334  
335 335  (((
336 -In LoRaWAN, the gatewat will use the frequency specify by the server to transmit a packet as downlink purpose. Each Frequency band has different downlink frequency. and the gateway has a frequency range limited to transmit downlink.
338 +In LoRaWAN, the gateway will use the frequency specify by the server to transmit a packet as downlink purpose. Each Frequency band has different downlink frequency. and the gateway has a frequency range limited to transmit downlink.
337 337  )))
338 338  
339 339  (((
... ... @@ -404,7 +404,7 @@
404 404  )))
405 405  
406 406  
407 -= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
409 += 8. Why I see uplink 0x00 periodically 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.
... ... @@ -448,7 +448,7 @@
448 448  4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
449 449  
450 450  
451 -= 10. Why i got the payload only with "0x00" or "AA~=~="? =
453 += 10. Why I got the payload only with "0x00" or "AA~=~="? =
452 452  
453 453  
454 454  (% style="color:blue" %)**Why sensor sends 0x00?**
... ... @@ -543,7 +543,7 @@
543 543  (Any combination of 16 bit codes can be used）
544 544  
545 545  
546 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
548 += 12. I set my device is LoRaWAN Class C mode, why I still see Class A after boot? =
547 547  )))
548 548  
549 549  
... ... @@ -553,27 +553,25 @@
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 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.
558 +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.
557 557  
558 558  
559 -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:
561 +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:
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 subbands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
563 +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:
562 562  
563 563  * (((
564 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
566 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band.
565 565  )))
566 566  * (((
567 -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)
569 +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).
568 568  )))
569 569  
570 -This change will make the activation time a littler longer but make sure the device can be used in any subband.
572 +This change will make the activation time a little longer but make sure the device can be used in any sub-band.
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 subband he use.
575 +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.
574 574  
575 575  
576 576  [[image:image-20221215223215-1.png||height="584" width="1280"]]
577 577  
578 -(% class="wikigeneratedid" %)
579 -
image-20240123161806-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +71.5 KB
Content
image-20240123161853-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +60.6 KB
Content
image-20240123163307-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +123.3 KB
Content
image-20240123182345-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +108.0 KB
Content
image-20240129142110-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +126.9 KB
Content
image-20240129142147-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +116.1 KB
Content
image-20240129142557-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +125.7 KB
Content
image-20240129142631-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +189.0 KB
Content
image-20240129150821-5.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +129.2 KB
Content
image-20240129151608-6.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +318.1 KB
Content
image-20240129152049-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +148.3 KB
Content
image-20240129152412-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +133.6 KB
Content
image-20240129154321-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +99.5 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0