Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 49.1 >
edited by Mengting Qiu
on 2024/01/23 16:37
To version < 68.1 >
edited by Mengting Qiu
on 2024/01/29 16:43
>
Change comment: Uploaded new attachment "image-20240129164326-5.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 5  
6 6  
7 -= z =
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,12 +38,11 @@
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  
46 -
47 47  (% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
48 48  
49 49  * Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
... ... @@ -52,22 +52,21 @@
52 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 57  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-20240123150720-1.png||height="459" width="1182"]]
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-20240123150943-2.png||height="556" width="1179"]]
67 +[[image:image-20240129142631-4.png||height="637" width="1256"]]
71 71  
72 72  Check if OTAA Keys match the keys in device.
73 73  
... ... @@ -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]]
... ... @@ -216,9 +216,6 @@
216 216  
217 217  * 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.**
218 218  
219 -(% class="wikigeneratedid" %)
220 -== ==
221 -
222 222  == 5.2 See Debug Info ==
223 223  
224 224  
... ... @@ -232,23 +232,26 @@
232 232  
233 233  (((
234 234  Configure a downlink to the end device
229 +
230 +[[image:image-20240129152412-8.png||height="486" width="1206"]]
235 235  )))
236 236  
237 -[[image:image-20240123163307-7.png||height="330" width="1125"]]
238 238  
239 239  (((
240 240  Set a downstream in TTN and see it is sent
241 241  )))
242 242  
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.**
243 243  
240 +
244 244  (((
245 -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.
246 246  )))
247 247  
248 -[[image:image-20220526164650-13.png]]
245 +[[image:image-20240129152049-7.png||height="463" width="1166"]]
249 249  
250 250  (((
251 -Gateway Traffic can see this downstream info
248 +Gateway Traffic can see this downlink info
252 252  )))
253 253  
254 254  
... ... @@ -258,10 +258,10 @@
258 258  )))
259 259  
260 260  (((
261 -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:
262 262  )))
263 263  
264 -[[image:image-20220526164734-14.png]]
261 +[[image:image-20240129154321-9.png]]
265 265  
266 266  (((
267 267  Gateway Sent out this packet
... ... @@ -338,7 +338,7 @@
338 338  
339 339  
340 340  (((
341 -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.
342 342  )))
343 343  
344 344  (((
... ... @@ -409,7 +409,7 @@
409 409  )))
410 410  
411 411  
412 -= 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 =
413 413  
414 414  
415 415  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.
... ... @@ -453,7 +453,7 @@
453 453  4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
454 454  
455 455  
456 -= 10. Why i got the payload only with "0x00" or "AA~=~="? =
453 += 10. Why I got the payload only with "0x00" or "AA~=~="? =
457 457  
458 458  
459 459  (% style="color:blue" %)**Why sensor sends 0x00?**
... ... @@ -548,7 +548,7 @@
548 548  (Any combination of 16 bit codes can be used）
549 549  
550 550  
551 -= 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? =
552 552  )))
553 553  
554 554  
... ... @@ -558,27 +558,25 @@
558 558  = 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
559 559  
560 560  
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.
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.
562 562  
563 563  
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:
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:
565 565  
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:
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:
567 567  
568 568  * (((
569 -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.
570 570  )))
571 571  * (((
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)
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).
573 573  )))
574 574  
575 -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.
576 576  
577 577  
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.
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.
579 579  
580 580  
581 581  [[image:image-20221215223215-1.png||height="584" width="1280"]]
582 582  
583 -(% class="wikigeneratedid" %)
584 -
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
image-20240129163533-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +23.0 KB
Content
image-20240129163714-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.2 KB
Content
image-20240129163741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +36.5 KB
Content
image-20240129164219-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +30.3 KB
Content
image-20240129164326-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +80.8 KB
Content

Applications

Navigation

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