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)
Details
- Page properties
-
- Content
-
... ... @@ -28,6 +28,7 @@ 28 28 Console Output from End device to see the transmit frequency 29 29 30 30 31 + 31 31 (% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:** 32 32 33 33 * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency) ... ... @@ -62,6 +62,7 @@ 62 62 Check if OTAA Keys match the keys in device 63 63 64 64 66 + 65 65 = 2. Notice of US915/CN470/AU915 Frequency band = 66 66 67 67 ... ... @@ -133,6 +133,7 @@ 133 133 ))) 134 134 135 135 138 + 136 136 = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good = 137 137 138 138 ... ... @@ -155,6 +155,7 @@ 155 155 ))) 156 156 157 157 161 + 158 158 = 4. Transmision on ABP Mode = 159 159 160 160 ... ... @@ -183,6 +183,7 @@ 183 183 Disable Frame Counter Check in ABP Mode 184 184 185 185 190 + 186 186 = 5. Downstream Debug = 187 187 188 188 == 5.1 How it work == ... ... @@ -243,6 +243,7 @@ 243 243 ))) 244 244 245 245 251 + 246 246 ((( 247 247 (% style="color:blue" %)**For LoRaWAN Gateway** 248 248 ))) ... ... @@ -258,6 +258,7 @@ 258 258 ))) 259 259 260 260 267 + 261 261 ((( 262 262 (% style="color:blue" %)**For End Node** 263 263 ))) ... ... @@ -272,6 +272,7 @@ 272 272 (% style="color:#037691" %)**AT+RX1DL=1000** (%%) ** ~-~-->** Receive Delay 1 273 273 (% style="color:#037691" %)**AT+RX2DL=2000** (%%) **~-~--> ** Receive Delay 2 274 274 282 + 275 275 276 276 ))) 277 277 ... ... @@ -289,6 +289,8 @@ 289 289 290 290 ((( 291 291 300 + 301 + 292 292 ))) 293 293 294 294 ((( ... ... @@ -307,6 +307,7 @@ 307 307 1:0012345678}}} 308 308 309 309 320 + 310 310 == 5.3 If problem doesn't solve == 311 311 312 312 ... ... @@ -319,6 +319,7 @@ 319 319 320 320 321 321 333 + 322 322 = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency = 323 323 324 324 ... ... @@ -345,6 +345,7 @@ 345 345 ))) 346 346 347 347 360 + 348 348 = 7. Decrypt a LoRaWAN Packet = 349 349 350 350 ... ... @@ -358,6 +358,7 @@ 358 358 [[image:image-20220526165525-16.png]] 359 359 360 360 374 + 361 361 (% style="color:blue" %)**2. In LG02 , configure to receive above message** 362 362 363 363 [[image:image-20220526165612-17.png]] ... ... @@ -368,6 +368,7 @@ 368 368 [[image:image-20220526171112-21.png]] 369 369 370 370 385 + 371 371 (% style="color:blue" %)**3. Decode the info in web** 372 372 373 373 [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]] ... ... @@ -390,6 +390,7 @@ 390 390 ))) 391 391 392 392 408 + 393 393 = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware = 394 394 395 395 ... ... @@ -396,6 +396,7 @@ 396 396 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. 397 397 398 398 415 + 399 399 = 9. Why do I see a "MIC Mismatch" error message from the server? = 400 400 401 401 ... ... @@ -512,6 +512,7 @@ 512 512 (Any combination of 16 bit codes can be used) 513 513 514 514 532 + 515 515 = 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? = 516 516 ))) 517 517