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