<
From version < 110.2 >
edited by Xiaoling
on 2024/01/15 17:05
To version < 120.1 >
edited by Mengting Qiu
on 2024/09/25 16:11
>
Change comment: Uploaded new attachment "image-20240925161141-1.jpeg", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.ting
Content
... ... @@ -135,7 +135,8 @@
135 135  v1.0: Release
136 136  )))
137 137  
138 -
138 +
139 +== 1.7 Pin definition ==
139 139  )))
140 140  )))
141 141  
... ... @@ -571,10 +571,10 @@
571 571  == 3.4 Uplink Payload ==
572 572  
573 573  
574 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
575 -|(% style="background-color:#d9e2f3; color:#0070c0; width:70px" %)(((
575 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
576 +|(% style="background-color:#4f81bd; color:white; width:70px" %)(((
576 576  **Size(bytes)**
577 -)))|(% style="background-color:#d9e2f3; color:#0070c0; width:80px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:360px" %)(((
578 +)))|(% style="background-color:#4f81bd; color:white; width:80px" %)**1**|(% style="background-color:#4f81bd; color:white; width:360px" %)(((
578 578  **Length depends on the return from the commands**
579 579  )))
580 580  |(% style="width:90px" %)(((
... ... @@ -736,31 +736,21 @@
736 736  )))
737 737  
738 738  (((
739 -(% style="color:blue" %)**Example 2:**  (%%) ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
740 +(% style="color:blue" %)**Example 2:**  (%%)
740 740  )))
741 741  
742 742  (((
743 -User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
744 +Check TTL Sensor return:
744 744  )))
745 745  
746 746  (((
747 -
748 -)))
749 -
750 750  (((
751 -(((
752 -RS485-LN got this downlink command and send (% style="color:#4f81bd" %)**0A 08 00 04 00 01 **(%%)to Modbus network. One of the RS485 sensor in the network send back Modbus reply **0A 08 00 04 00 00**. RS485-LN get this reply and combine with the original downlink command and uplink. The uplink message is:  **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
749 +[[image:http://8.211.40.43/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/test/WebHome/1654132684752-193.png?rev=1.1||alt="1654132684752-193.png"]](% title="Click and drag to resize" %)​
753 753  )))
754 -
755 -
756 756  )))
757 757  
758 -(((
759 - (% aria-label="1654159460680-153.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654159460680-153.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
760 -)))
761 761  
762 762  
763 -
764 764  ==== (% style="color:blue" %)**Set Payload version**(%%) ====
765 765  
766 766  
... ... @@ -1694,7 +1694,7 @@
1694 1694  1. Check if Modbus-MTU return back the expected result to RS485-LN.
1695 1695  1. If both b) and c) has issue, we can compare PC’s output and RS485-LN output.
1696 1696  
1697 -[[image:image-20221130104310-1.png||height="380" width="680"]]
1688 +[[image:image-20240816112950-1.png||height="382" width="731"]]
1698 1698  
1699 1699  
1700 1700  Example Connection:
... ... @@ -1816,12 +1816,36 @@
1816 1816  Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
1817 1817  
1818 1818  
1819 -== 7.2 Why I can't join TTN V3 in US915 /AU915 bands? ==
1810 +== 7.2 Why customers can't join TTN V3 in US915 /AU915 bands? ==
1820 1820  
1821 1821  
1822 1822  It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1823 1823  
1824 1824  
1816 +== 7.3 Why can't customers see the device's data in the server when the data is too long? ==
1817 +
1818 +This is due to the limitation of the lorawan protocol, and the fixed DR needs to be adjusted to improve this problem.
1819 +
1820 +Please refer to the following link for the number of bytes limited by different frequencies and different DRs in the lorawan protocol
1821 +
1822 +[[lora-alliance.org/wp-content/uploads/2021/05/RP002-1.0.3-FINAL-1.pdf>>url:https://lora-alliance.org/wp-content/uploads/2021/05/RP002-1.0.3-FINAL-1.pdf]]
1823 +
1824 +Example:
1825 +
1826 +[[image:image-20240620145456-1.png]]
1827 +
1828 +Please refer to the following command to fix DR
1829 +
1830 +AT+ADR=0
1831 +
1832 +AT+DR=3
1833 +
1834 +Downlink command:
1835 +
1836 +[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate]]
1837 +
1838 +
1839 +
1825 1825  = 8. Order Info =
1826 1826  
1827 1827  
image-20240620145456-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +50.3 KB
Content
image-20240816112950-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.karry
Size
... ... @@ -1,0 +1,1 @@
1 +230.3 KB
Content
image-20240925144019-1.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +1.6 MB
Content
image-20240925145611-2.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +606.6 KB
Content
image-20240925161141-1.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +1.6 MB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0