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
-
... ... @@ -248,18 +248,24 @@ 248 248 we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below: 249 249 ))) 250 250 251 +(% class="box infomessage" %) 251 251 ((( 252 - 253 +AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency 253 253 ))) 254 254 256 +(% class="box infomessage" %) 255 255 ((( 258 +AT+RX2DR=3 ~-~--> The RX2 DataRate 259 +))) 260 + 256 256 (% class="box infomessage" %) 257 257 ((( 258 -AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency 259 -AT+RX2DR=3 ~-~--> The RX2 DataRate 260 -AT+RX1DL=1000 ~-~--> Receive Delay 1 261 -AT+RX2DL=2000 ~-~--> Receive Delay 2 263 + AT+RX1DL=1000 ~-~--> Receive Delay 1 262 262 ))) 265 + 266 +(% class="box infomessage" %) 267 +((( 268 + AT+RX2DL=2000 ~-~--> Receive Delay 2 263 263 ))) 264 264 265 265 ((( ... ... @@ -266,13 +266,17 @@ 266 266 **when the device running, we can see below info:** 267 267 ))) 268 268 275 +((( 276 + 277 +))) 278 + 269 269 {{{ [12502]***** UpLinkCounter= 0 ***** 270 270 [12503]TX on freq 868500000 Hz at DR 0 271 271 [13992]txDone 272 - [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone 273 - [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms) 274 - [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone 275 - [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}} 282 + [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone 283 + [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms) 284 + [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone 285 + [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}} 276 276 277 277 ((( 278 278 ... ... @@ -288,7 +288,7 @@ 288 288 [15022]RX on freq 868100000 Hz at DR 0 289 289 [15222]rxTimeOut 290 290 [15987]RX on freq 869525000 Hz at DR 3 291 - [16185]rxDone --> We have got the downstream packet. 301 + [16185]rxDone --> We have got the downstream packet. 292 292 Rssi= -64 293 293 Receive data 294 294 1:0012345678}}} ... ... @@ -368,13 +368,13 @@ 368 368 369 369 AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key) 370 370 381 +((( 371 371 [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111]] 383 +))) 372 372 373 373 [[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]] 374 374 375 -((( 376 - The FRMPayload is the device payload. 377 -))) 387 +The FRMPayload is the device payload. 378 378 379 379 380 380 = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware = ... ... @@ -409,7 +409,9 @@ 409 409 410 410 = 10. Why i got the payload only with "0x00" or "AA~=~="? = 411 411 412 -* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon. 422 +* ((( 423 +If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon. 424 +))) 413 413 414 414 ((( 415 415 When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate. ... ... @@ -416,9 +416,17 @@ 416 416 ))) 417 417 418 418 ((( 419 -When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node, and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,so it will send a normal uplink packet, and an additional 00 data packet.431 +When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node, 420 420 ))) 421 421 434 +((( 435 +and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit, 436 +))) 437 + 438 +((( 439 +so it will send a normal uplink packet, and an additional 00 data packet. 440 +))) 441 + 422 422 * ((( 423 423 Solution: Use the decoder to filter out this 00 packet. 424 424 )))