Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 4.6
edited by Xiaoling
on 2022/05/11 14:52
Change comment: There is no comment for this version
To version 4.9
edited by Xiaoling
on 2022/05/11 15:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -244,59 +244,69 @@
244 244  **For End Node**
245 245  )))
246 246  
247 +(((
247 247  we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
249 +)))
248 248  
251 +(((
252 +
253 +)))
254 +
255 +(((
249 249  (% class="box infomessage" %)
250 250  (((
251 - AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
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
252 252  )))
263 +)))
253 253  
254 254  (% class="box infomessage" %)
255 255  (((
256 - AT+RX2DR=3 ~-~--> The RX2 DataRate
267 +AT+RX2DR=3 ~-~--> The RX2 DataRate
257 257  )))
258 258  
259 259  (% class="box infomessage" %)
260 260  (((
261 - AT+RX1DL=1000 ~-~--> Receive Delay 1
272 + AT+RX1DL=1000 ~-~--> Receive Delay 1
262 262  )))
263 263  
264 264  (% class="box infomessage" %)
265 265  (((
266 - AT+RX2DL=2000 ~-~--> Receive Delay 2
277 + AT+RX2DL=2000 ~-~--> Receive Delay 2
267 267  )))
268 268  
269 -**when the device running, we can see below info:**
270 -
271 271  (((
272 -
281 +**when the device running, we can see below info:**
273 273  )))
274 274  
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)}}}
284 +{{{ [12502]***** UpLinkCounter= 0 *****
285 + [12503]TX on freq 868500000 Hz at DR 0
286 + [13992]txDone
287 + [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
288 + [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
289 + [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
290 + [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
282 282  
283 283  (((
284 284  
285 285  )))
286 286  
296 +(((
287 287  **Another message:**
298 +)))
288 288  
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}}}
300 +{{{ [12502]***** UpLinkCounter= 0 *****
301 + [12503]TX on freq 868100000 Hz at DR 0
302 + [13992]txDone
303 + [15022]RX on freq 868100000 Hz at DR 0
304 + [15222]rxTimeOut
305 + [15987]RX on freq 869525000 Hz at DR 3
306 + [16185]rxDone --> We have got the downstream packet.
307 + Rssi= -64
308 + Receive data
309 + 1:0012345678}}}
300 300  
301 301  == 5.3 If problem doesn’t solve ==
302 302  
... ... @@ -321,9 +321,7 @@
321 321  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:
322 322  )))
323 323  
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 -)))
334 +{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
327 327  
328 328  (((
329 329  
... ... @@ -375,7 +375,9 @@
375 375  
376 376  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
377 377  
386 +(((
378 378  [[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]]
388 +)))
379 379  
380 380  [[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
381 381  
... ... @@ -388,32 +388,58 @@
388 388  
389 389  = 9. Why do I see a "MIC Mismatch" error message from the server? =
390 390  
401 +(((
391 391  1)If the user receives a "MIC Mismatch" message after registering the node on the server.
403 +)))
392 392  
405 +(((
393 393  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
407 +)))
394 394  
395 -* Please note the distinction between "APPKEY" and "APPSKEY".
409 +* (((
410 +Please note the distinction between "APPKEY" and "APPSKEY".
411 +)))
396 396  
413 +(((
397 397  2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
415 +)))
398 398  
417 +(((
399 399  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
419 +)))
400 400  
401 -* If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
421 +* (((
422 +If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
423 +)))
402 402  
403 403  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
404 404  
405 -* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
427 +* (((
428 +If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
429 +)))
406 406  
431 +(((
407 407  When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
433 +)))
408 408  
435 +(((
409 409  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,
437 +)))
410 410  
439 +(((
411 411  and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
441 +)))
412 412  
443 +(((
413 413  so it will send a normal uplink packet, and an additional 00 data packet.
445 +)))
414 414  
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
447 +* (((
448 +Solution: Use the decoder to filter out this 00 packet.
449 +)))
450 +* (((
451 +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
452 +)))
417 417  
418 418  (% class="wikigeneratedid" id="H" %)
419 419