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,24 +248,18 @@ 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" %) 252 252 ((( 253 - AT+RX2FQ=869525000~-~--> The RX2 Window frequency252 + 254 254 ))) 255 255 256 -(% class="box infomessage" %) 257 257 ((( 258 -AT+RX2DR=3 ~-~--> The RX2 DataRate 259 -))) 260 - 261 261 (% class="box infomessage" %) 262 262 ((( 263 - AT+RX1DL=1000 ~-~--> Receive Delay 1 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 264 264 ))) 265 - 266 -(% class="box infomessage" %) 267 -((( 268 - AT+RX2DL=2000 ~-~--> Receive Delay 2 269 269 ))) 270 270 271 271 ((( ... ... @@ -272,10 +272,6 @@ 272 272 **when the device running, we can see below info:** 273 273 ))) 274 274 275 -((( 276 - 277 -))) 278 - 279 279 {{{ [12502]***** UpLinkCounter= 0 ***** 280 280 [12503]TX on freq 868500000 Hz at DR 0 281 281 [13992]txDone ... ... @@ -378,13 +378,13 @@ 378 378 379 379 AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key) 380 380 381 -((( 382 382 [[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 -))) 384 384 385 385 [[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]] 386 386 387 -The FRMPayload is the device payload. 375 +((( 376 + The FRMPayload is the device payload. 377 +))) 388 388 389 389 390 390 = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware = ... ... @@ -419,24 +419,22 @@ 419 419 420 420 = 10. Why i got the payload only with "0x00" or "AA~=~="? = 421 421 422 -* ((( 423 -If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon. 424 -))) 412 +* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon. 425 425 426 426 ((( 427 -When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate. 415 + When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate. 428 428 ))) 429 429 430 430 ((( 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, 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, 432 432 ))) 433 433 434 434 ((( 435 -and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit, 423 + and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit, 436 436 ))) 437 437 438 438 ((( 439 -so it will send a normal uplink packet, and an additional 00 data packet. 427 + so it will send a normal uplink packet, and an additional 00 data packet. 440 440 ))) 441 441 442 442 * (((