Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 4.17 >
edited by Xiaoling
on 2022/05/11 15:34
To version < 13.2 >
edited by Xiaoling
on 2022/05/26 16:37
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,9 @@
1 1  **~ Contents:**
2 2  
3 +(((
4 +
5 +)))
6 +
3 3  {{toc/}}
4 4  
5 5  
... ... @@ -19,7 +19,7 @@
19 19  * If the device is sending join request to server?
20 20  * What frequency the device is sending?
21 21  
22 -[[image:https://wiki.dragino.com/images/thumb/0/0f/OTAA_Join-1.jpg/600px-OTAA_Join-1.jpg||height="316" width="600"]]
26 +[[image:image-20220526163523-1.png]]
23 23  
24 24  Console Output from End device to see the transmit frequency
25 25  
... ... @@ -29,7 +29,7 @@
29 29  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
30 30  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
31 31  
32 -[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
36 +[[image:image-20220526163608-2.png]]
33 33  
34 34  Console Output from Gateway to see packets between end node and server.
35 35  
... ... @@ -40,7 +40,7 @@
40 40  * If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
41 41  * If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
42 42  
43 -[[image:https://wiki.dragino.com/images/thumb/5/5c/OTAA_Join-3.png/600px-OTAA_Join-3.png||height="301" width="600"]]
47 +[[image:image-20220526163633-3.png]]
44 44  
45 45  The Traffic for the End node in the server, use TTN as example
46 46  
... ... @@ -49,11 +49,11 @@
49 49  
50 50  * If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
51 51  
52 -[[image:https://wiki.dragino.com/images/thumb/e/ec/OTAA_Join-4.png/600px-OTAA_Join-4.png||height="181" width="600"]]
56 +[[image:image-20220526163704-4.png]]
53 53  
54 54  The data for the end device set in server
55 55  
56 -[[image:https://wiki.dragino.com/images/thumb/b/b1/OTAA_Join-5.png/600px-OTAA_Join-5.png||height="166" width="600"]]
60 +[[image:image-20220526163732-5.png]]
57 57  
58 58  Check if OTAA Keys match the keys in device
59 59  
... ... @@ -405,6 +405,8 @@
405 405  
406 406  * (((
407 407  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
412 +
413 +
408 408  )))
409 409  
410 410  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
... ... @@ -412,27 +412,50 @@
412 412  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
413 413  
414 414  (((
415 - When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
421 +When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
416 416  )))
417 417  
418 418  (((
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,
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.
420 420  )))
421 421  
422 -(((
423 - 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
424 -)))
425 -
426 -(((
427 - uplink packet, and an additional 00 data packet.
428 -)))
429 -
430 430  * (((
431 431  Solution: Use the decoder to filter out this 00 packet.
432 432  )))
433 433  * (((
434 -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
435 -)))
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]]
436 436  
437 -(% class="wikigeneratedid" id="H" %)
434 +
438 438  
436 +)))
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 +
image-20220526163523-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +633.8 KB
Content
image-20220526163608-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +116.4 KB
Content
image-20220526163633-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +65.6 KB
Content
image-20220526163704-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.8 KB
Content
image-20220526163732-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +18.5 KB
Content

Applications

Navigation

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