Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 10.2 >
edited by Xiaoling
on 2022/05/26 16:36
To version < 4.6 >
edited by Xiaoling
on 2022/05/11 14:52
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,9 +1,5 @@
1 1  **~ Contents:**
2 2  
3 -(((
4 -
5 -)))
6 -
7 7  {{toc/}}
8 8  
9 9  
... ... @@ -23,7 +23,7 @@
23 23  * If the device is sending join request to server?
24 24  * What frequency the device is sending?
25 25  
26 -[[image:image-20220526163523-1.png]]
22 +[[image:https://wiki.dragino.com/images/thumb/0/0f/OTAA_Join-1.jpg/600px-OTAA_Join-1.jpg||height="316" width="600"]]
27 27  
28 28  Console Output from End device to see the transmit frequency
29 29  
... ... @@ -33,7 +33,7 @@
33 33  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
34 34  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
35 35  
36 -[[image:image-20220526163608-2.png]]
32 +[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
37 37  
38 38  Console Output from Gateway to see packets between end node and server.
39 39  
... ... @@ -248,55 +248,60 @@
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:
253 -)))
254 254  
249 +(% class="box infomessage" %)
255 255  (((
256 -
251 + AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
257 257  )))
258 258  
254 +(% class="box infomessage" %)
259 259  (((
256 + AT+RX2DR=3 ~-~--> The RX2 DataRate
257 +)))
258 +
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
261 + AT+RX1DL=1000 ~-~--> Receive Delay 1
266 266  )))
267 -)))
268 268  
264 +(% class="box infomessage" %)
269 269  (((
270 -**when the device running, we can see below info:**
266 + AT+RX2DL=2000 ~-~--> Receive Delay 2
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)}}}
269 +**when the device running, we can see below info:**
280 280  
281 281  (((
282 282  
283 283  )))
284 284  
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)}}}
282 +
285 285  (((
286 -**Another message:**
284 +
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}}}
287 +**Another message:**
299 299  
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 +
300 300  == 5.3 If problem doesn’t solve ==
301 301  
302 302  **If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
... ... @@ -320,7 +320,9 @@
320 320  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:
321 321  )))
322 322  
323 -{{{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 +)))
324 324  
325 325  (((
326 326  
... ... @@ -376,9 +376,7 @@
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 -)))
382 +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 =
... ... @@ -387,81 +387,32 @@
387 387  
388 388  = 9. Why do I see a "MIC Mismatch" error message from the server? =
389 389  
390 -(((
391 391  1)If the user receives a "MIC Mismatch" message after registering the node on the server.
392 -)))
393 393  
394 -(((
395 395  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
396 -)))
397 397  
398 -* (((
399 -Please note the distinction between "APPKEY" and "APPSKEY".
400 -)))
395 +* Please note the distinction between "APPKEY" and "APPSKEY".
401 401  
402 -(((
403 403  2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
404 -)))
405 405  
406 -(((
407 407  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
408 -)))
409 409  
410 -* (((
411 -If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
401 +* If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
412 412  
413 -
414 -)))
415 -
416 416  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
417 417  
418 418  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
419 419  
420 -(((
421 421  When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
422 -)))
423 423  
424 -(((
425 -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.
426 -)))
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,
427 427  
428 -* (((
429 -Solution: Use the decoder to filter out this 00 packet.
430 -)))
431 -* (((
432 -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>>mailto:david.huang@dragino.cc]]
411 +and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
433 433  
413 +so it will send a normal uplink packet, and an additional 00 data packet.
434 434  
435 -
436 -)))
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
437 437  
438 -= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
439 -
440 -It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
441 -
442 -AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
443 -
444 -AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
445 -
446 -AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
447 -
448 -AT+APPEUI=00 00 00 00 00 00 00 00
449 -
450 -
451 -You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
452 -
453 -You can rewrites the keys by running commands in AT Console
454 -
455 -For example：
456 -
457 -AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
458 -
459 -AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
460 -
461 -AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
462 -
463 -AT+APPEUI=2C 45 47 E3 24 12 23 24
464 -
465 -(Any combination of 16 bit codes can be used）
466 -
467 -
418 +(% class="wikigeneratedid" id="H" %)
419 +
image-20220526163523-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -633.8 KB
Content
image-20220526163608-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -116.4 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0