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
-
... ... @@ -244,64 +244,59 @@ 244 244 **For End Node** 245 245 ))) 246 246 247 -((( 248 248 we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below: 249 -))) 250 250 251 251 (% class="box infomessage" %) 252 252 ((( 253 -AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency 251 + AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency 254 254 ))) 255 255 256 256 (% class="box infomessage" %) 257 257 ((( 258 -AT+RX2DR=3 ~-~--> The RX2 DataRate 256 + AT+RX2DR=3 ~-~--> The RX2 DataRate 259 259 ))) 260 260 261 261 (% class="box infomessage" %) 262 262 ((( 263 - AT+RX1DL=1000 ~-~--> Receive Delay 1 261 + AT+RX1DL=1000 ~-~--> Receive Delay 1 264 264 ))) 265 265 266 266 (% class="box infomessage" %) 267 267 ((( 268 - AT+RX2DL=2000 ~-~--> Receive Delay 2 266 + AT+RX2DL=2000 ~-~--> Receive Delay 2 269 269 ))) 270 270 271 -((( 272 272 **when the device running, we can see below info:** 273 -))) 274 274 275 275 ((( 276 276 277 277 ))) 278 278 279 -{{{ [12502]***** UpLinkCounter= 0 ***** 280 - [12503]TX on freq 868500000 Hz at DR 0 281 - [13992]txDone 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)}}} 275 +{{{ [12502]***** UpLinkCounter= 0 ***** 276 + [12503]TX on freq 868500000 Hz at DR 0 277 + [13992]txDone 278 + [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone 279 + [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms) 280 + [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone 281 + [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}} 286 286 287 287 ((( 288 288 289 289 ))) 290 290 291 -((( 292 292 **Another message:** 293 -))) 294 294 295 -{{{ [12502]***** UpLinkCounter= 0 ***** 296 - [12503]TX on freq 868100000 Hz at DR 0 297 - [13992]txDone 298 - [15022]RX on freq 868100000 Hz at DR 0 299 - [15222]rxTimeOut 300 - [15987]RX on freq 869525000 Hz at DR 3 301 - [16185]rxDone --> We have got the downstream packet. 302 - Rssi= -64 303 - Receive data 304 - 1:0012345678}}} 289 +{{{ 290 + [12502]***** UpLinkCounter= 0 ***** 291 + [12503]TX on freq 868100000 Hz at DR 0 292 + [13992]txDone 293 + [15022]RX on freq 868100000 Hz at DR 0 294 + [15222]rxTimeOut 295 + [15987]RX on freq 869525000 Hz at DR 3 296 + [16185]rxDone --> We have got the downstream packet. 297 + Rssi= -64 298 + Receive data 299 + 1:0012345678}}} 305 305 306 306 == 5.3 If problem doesn’t solve == 307 307 ... ... @@ -326,7 +326,9 @@ 326 326 So if the LoRaWAN server is an AS923 server which ask the gateway to transmit at 923.2Mhz frequency, but the gateway is IN868 frequency band (support 865~~867Mhz to transmit). In the gateway log it will show something like below: 327 327 ))) 328 328 329 -{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}} 324 +((( 325 +Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000) 326 +))) 330 330 331 331 ((( 332 332 ... ... @@ -378,9 +378,7 @@ 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 ... ... @@ -393,58 +393,32 @@ 393 393 394 394 = 9. Why do I see a "MIC Mismatch" error message from the server? = 395 395 396 -((( 397 397 1)If the user receives a "MIC Mismatch" message after registering the node on the server. 398 -))) 399 399 400 -((( 401 401 It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY". 402 -))) 403 403 404 -* ((( 405 -Please note the distinction between "APPKEY" and "APPSKEY". 406 -))) 395 +* Please note the distinction between "APPKEY" and "APPSKEY". 407 407 408 -((( 409 409 2)If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message. 410 -))) 411 411 412 -((( 413 413 The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY. 414 -))) 415 415 416 -* ((( 417 -If a node is registered with multiple servers, it may also cause the "mic mismatch" error. 418 -))) 401 +* If a node is registered with multiple servers, it may also cause the "mic mismatch" error. 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 -))) 405 +* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon. 425 425 426 -((( 427 427 When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate. 428 -))) 429 429 430 -((( 431 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, 432 -))) 433 433 434 -((( 435 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 437 438 -((( 439 439 so it will send a normal uplink packet, and an additional 00 data packet. 440 -))) 441 441 442 -* ((( 443 -Solution: Use the decoder to filter out this 00 packet. 444 -))) 445 -* ((( 446 -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 447 -))) 415 +* Solution: Use the decoder to filter out this 00 packet. 416 +* 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 448 448 449 449 (% class="wikigeneratedid" id="H" %) 450 450