Changes for page LoRaWAN Communication Debug
Last modified by Edwin Chen on 2025/01/29 20:30
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,14 +1,12 @@ 1 -**~ Contents:** 1 +**~ Table of Contents:** 2 2 3 -((( 4 - 5 -))) 6 - 7 7 {{toc/}} 8 8 9 9 6 + 10 10 = 1. OTAA Join Process Debug = 11 11 9 + 12 12 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. 13 13 \\**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:** 14 14 ... ... @@ -64,6 +64,7 @@ 64 64 65 65 = 2. Notice of US915/CN470/AU915 Frequency band = 66 66 65 + 67 67 ((( 68 68 If user has problem to work with lorawan server in band US915/AU915/CN470, he can check: 69 69 ))) ... ... @@ -106,10 +106,13 @@ 106 106 107 107 AU915 Channels 108 108 108 + 109 109 [[image:image-20220526163941-8.png]] 110 110 111 111 ((( 112 112 CN470 Channels 113 + 114 + 113 113 ))) 114 114 115 115 ((( ... ... @@ -120,6 +120,8 @@ 120 120 121 121 ((( 122 122 TTN FREQUENCY PLAN 125 + 126 + 123 123 ))) 124 124 125 125 ((( ... ... @@ -129,6 +129,7 @@ 129 129 130 130 = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good = 131 131 136 + 132 132 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: 133 133 134 134 * **End node** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors. ... ... @@ -150,6 +150,7 @@ 150 150 151 151 = 4. Transmision on ABP Mode = 152 152 158 + 153 153 ((( 154 154 In ABP mode, there is a Frame Counter Checks. With this check enabled, the server will only accept the frame with a higher counter. If you reboot the device in ABP mode, the device will start from count 0, so you won't be able to see the frame update in server. 155 155 ))) ... ... @@ -179,6 +179,7 @@ 179 179 180 180 == 5.1 How it work == 181 181 188 + 182 182 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. 183 183 184 184 ((( ... ... @@ -185,10 +185,11 @@ 185 185 Depends on Class A or Class C, the receive windows will be a little difference, 186 186 ))) 187 187 188 -[[image:image-202205 26164547-11.png]]195 +[[image:image-20220531161828-1.png]] 189 189 190 190 receive windows for Class A and Class C 191 191 199 + 192 192 Below are the requirement for the End Device to receive the packets. 193 193 194 194 * The End Device must open the receive windows: RX1 or RX2 ... ... @@ -195,12 +195,14 @@ 195 195 * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node. 196 196 * This downstream packet must arrive to the end node while RX1 or RX2 is open. 197 197 * This packet must match the frequency of the RX1 or RX2 window. 198 -* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). **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.** 206 +* 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.** 199 199 208 + 200 200 == 5.2 See Debug Info == 201 201 211 + 202 202 ((( 203 -**For LoRaWAN Server** 213 +(% style="color:blue" %)**For LoRaWAN Server** 204 204 ))) 205 205 206 206 ((( ... ... @@ -230,7 +230,7 @@ 230 230 231 231 232 232 ((( 233 -**For LoRaWAN Gateway** 243 +(% style="color:blue" %)**For LoRaWAN Gateway** 234 234 ))) 235 235 236 236 ((( ... ... @@ -245,7 +245,7 @@ 245 245 246 246 247 247 ((( 248 -**For End Node** 258 +(% style="color:blue" %)**For End Node** 249 249 ))) 250 250 251 251 ((( ... ... @@ -267,7 +267,7 @@ 267 267 ))) 268 268 269 269 ((( 270 -**when the device running, we can see below info:** 280 +(% style="color:blue" %)**when the device running, we can see below info:** 271 271 ))) 272 272 273 273 {{{ [12502]***** UpLinkCounter= 0 ***** ... ... @@ -283,7 +283,7 @@ 283 283 ))) 284 284 285 285 ((( 286 -**Another message:** 296 +(% style="color:blue" %)**Another message:** 287 287 ))) 288 288 289 289 {{{ [12502]***** UpLinkCounter= 0 ***** ... ... @@ -339,15 +339,7 @@ 339 339 (% class="box infomessage" %) 340 340 ((( 341 341 **Change to ABP Mode: AT+NJM=0** 342 -))) 343 - 344 -(% class="box infomessage" %) 345 -((( 346 346 **Change to fix frequency: AT+CHS=904900000** 347 -))) 348 - 349 -(% class="box infomessage" %) 350 -((( 351 351 **Change to fix DR: AT+DR=0** 352 352 ))) 353 353 ... ... @@ -436,39 +436,74 @@ 436 436 * ((( 437 437 Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to [[david.huang@dragino.cc>>mailto:david.huang@dragino.cc]] 438 438 439 - 440 440 441 441 ))) 442 442 443 443 = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? = 444 444 446 +((( 445 445 It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG 448 +))) 446 446 450 +((( 447 447 AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 452 +))) 448 448 454 +((( 449 449 AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 456 +))) 450 450 458 +((( 451 451 AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 460 +))) 452 452 462 +((( 453 453 AT+APPEUI=00 00 00 00 00 00 00 00 464 +))) 454 454 466 +((( 467 + 468 +))) 455 455 470 +((( 456 456 You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number. 472 +))) 457 457 474 +((( 458 458 You can rewrites the keys by running commands in AT Console 476 +))) 459 459 460 -For example: 478 +((( 479 +**For example:** 480 +))) 461 461 482 +((( 462 462 AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE 484 +))) 463 463 486 +((( 464 464 AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11 488 +))) 465 465 490 +((( 466 466 AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10 492 +))) 467 467 494 +((( 468 468 AT+APPEUI=2C 45 47 E3 24 12 23 24 496 +))) 469 469 498 +((( 470 470 (Any combination of 16 bit codes can be used) 471 471 472 472 502 += 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? = 503 +))) 504 + 505 + 506 +Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode. 507 + 508 + 509 + 473 473 (% class="wikigeneratedid" %) 474 474
- image-20220531161828-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +98.6 KB - Content