Changes for page LT-22222-L -- LoRa I/O Controller User Manual
Last modified by Saxer Lin on 2025/04/15 17:24
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Content
-
... ... @@ -23,10 +23,6 @@ 23 23 24 24 ((( 25 25 ((( 26 -{{info}} 27 -**This manual is also applicable to the LT-33222-L.** 28 -{{/info}} 29 - 30 30 The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN device designed to provide seamless wireless long-range connectivity with various I/O options, including analog current and voltage inputs, digital inputs and outputs, and relay outputs. 31 31 32 32 The LT-22222-L I/O Controller simplifies and enhances I/O monitoring and controlling. It is ideal for professional applications in wireless sensor networks, including irrigation systems, smart metering, smart cities, building automation, and more. These controllers are designed for easy, cost-effective deployment using LoRa wireless technology. ... ... @@ -40,7 +40,7 @@ 40 40 ((( 41 41 You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways: 42 42 43 -* If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Stack CommunityNetwork), you can select a network and register the LT-22222-L I/O controller with it.39 +* If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Network), you can select a network and register the LT-22222-L I/O controller with it. 44 44 * If there is no public LoRaWAN coverage in your area, you can set up a LoRaWAN gateway, or multiple gateways, and connect them to a LoRaWAN network server to create adequate coverage. Then, register the LT-22222-L I/O controller with this network. 45 45 * Setup your own private LoRaWAN network. 46 46 ... ... @@ -50,14 +50,11 @@ 50 50 ))) 51 51 52 52 ((( 53 - 49 +[[image:1653295757274-912.png]] 54 54 55 - Thenetwork diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.51 + 56 56 ))) 57 57 58 -(% class="wikigeneratedid" %) 59 -[[image:lorawan-nw.jpg||height="354" width="900"]] 60 - 61 61 == 1.2 Specifications == 62 62 63 63 (% style="color:#037691" %)**Hardware System:** ... ... @@ -118,24 +118,8 @@ 118 118 * Smart cities 119 119 * Smart factory 120 120 121 -= =1.5HardwareVariants==114 += 2. Assembling the device = 122 122 123 -(% style="width:524px" %) 124 -|(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description** 125 -|(% style="width:94px" %)**LT33222-L**|(% style="width:98px" %)((( 126 - 127 -)))|(% style="width:329px" %)((( 128 -* 2 x Digital Input (Bi-direction) 129 -* 2 x Digital Output 130 -* 2 x Relay Output (5A@250VAC / 30VDC) 131 -* 2 x 0~~20mA Analog Input (res:0.01mA) 132 -* 2 x 0~~30V Analog Input (res:0.01v) 133 -* 1 x Counting Port 134 -))) 135 - 136 - 137 -== 2. Assembling the device == 138 - 139 139 == 2.1 Connecting the antenna == 140 140 141 141 Connect the LoRa antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper screw terminal block. Secure the antenna by tightening it clockwise. ... ... @@ -174,11 +174,11 @@ 174 174 |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2 175 175 |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1 176 176 177 -== 2.3 ConnectingLT-22222-Lto a PowerSource ==154 +== 2.3 Powering the device == 178 178 179 -The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s **positive wire**to the**VIN**and the**negative wire**to the**GND**screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered.156 +The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s positive wire to the VIN and the negative wire to the GND screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered. 180 180 181 -Once powered, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** with the NetworkServer.158 +Once powered, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** The Things Stack. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status. 182 182 183 183 {{warning}} 184 184 We recommend that you power on the LT-22222-L after configuring its registration information with a LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail. ... ... @@ -188,45 +188,35 @@ 188 188 [[image:1653297104069-180.png]] 189 189 190 190 191 -= 3. Registering LT-22222-Lwith a LoRaWAN Network Server =168 += 3. Registering with a LoRaWAN Network Server = 192 192 193 -By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. It supports bothOTAA (Over-the-Air Activation)and ABP (ActivationBy Personalization)methodsto activate with a LoRaWANNetworkServer.However,OTAAis themost securemethodforctivatingadevice with a LoRaWANNetworkServer.170 +By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. It supports OTAA (Over-the-Air Activation), the most secure method for activating a device with a LoRaWAN network server. The LT-22222-L comes with device registration information that allows you to register it with a LoRaWAN network, enabling the device to perform OTAA activation with the network server upon initial power-up and after any subsequent reboots. 194 194 172 +After powering on, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** the LoRaWAN network. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status. 195 195 174 +In case you can't set the root key and other identifiers in the network server and must use them from the server, you can use [[AT Commands>>||anchor="H4.UseATCommand"]] to configure them on the device. 196 196 197 - ===3.2.1Prerequisites===176 +The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network. 198 198 199 - TheLT-22222-L comes with device registrationinformation that allows you to register it witha LoRaWAN network, enablingthe devicetoperform OTAA activationwith the network server upon initial power-up andafter any subsequent reboots.178 +[[image:image-20220523172350-1.png||height="266" width="864"]] 200 200 201 - Makesure you have the device registration information such as DevEUI, AppEUI, and AppKey with you.Theseregistration information can befound on a sticker that can be found insidethepackage. Pleasekeep the **registration information** sticker in a safe place for future reference.180 +=== 3.2.1 Prerequisites === 202 202 182 +Make sure you have the device registration information such as DevEUI, AppEUI, and AppKey with you. The registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference. 183 + 203 203 [[image:image-20230425173427-2.png||height="246" width="530"]] 204 204 205 -{{info}} 206 -In case you can't set the root key and other identifiers in the network server and must use them from the server, you can use [[AT Commands>>||anchor="H4.UseATCommand"]] to configure them on the device. 207 -{{/info}} 208 - 209 209 The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers. 210 210 211 -=== 3.2.2 Registering withThe Things Stack ===188 +=== 3.2.2 The Things Stack Sandbox (TTSS) === 212 212 213 -{{info}} 214 214 The Things Stack Sandbox was formally called The Things Stack Community Edition. 215 -{{/info}} 216 216 217 - 218 -The network diagram below shows how the LT-22222-L is connected to The Things Stack and integrates its data with the ThingsEye IoT platform. 219 - 220 -[[image:dragino-ttn-te.jpg]] 221 - 222 - 223 -* Create a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have a one yet. 224 -* Log in to your The Things Stack Sandbox account. 192 +* Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account. 225 225 * Create an application with The Things Stack if you do not have one yet. 226 226 * Go to your application page and click on the **End devices** in the left menu. 227 227 * On the End devices page, click on **+ Register end device**. Two registration options are available: 228 228 229 - 230 230 ==== 3.2.2.1 Using the LoRaWAN Device Repository ==== 231 231 232 232 * On the **Register end device** page: ... ... @@ -239,7 +239,6 @@ 239 239 *** **Profile (Region)**: Select the region that matches your device. 240 240 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 241 241 242 - 243 243 [[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]] 244 244 245 245 ... ... @@ -289,17 +289,14 @@ 289 289 290 290 On the Device overview page, click on **Live data** tab. The Live data panel for your device will display. 291 291 292 -Now power on your LT-22222-L. The**TX LED**will**fast-blink 5 times** which meansthe LT-22222-L will enter the **work mode** and start to **join**The Things Stacknetwork server.The **TX LED** will be on for **5 seconds** after joining the network.In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server.258 +Now power on your LT-22222-L. It will begin joining The Things Stack. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. Once successfully joined, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**). 293 293 294 294 295 295 [[image:lt-22222-join-network.png||height="625" width="1000"]] 296 296 297 297 298 - ====3.2.2.4Uplinks====264 +By default, you will receive an uplink data message from the device every 10 minutes. 299 299 300 - 301 -After successfully joining, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes. 302 - 303 303 Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the decode_payload {} JSON object. 304 304 305 305 [[image:lt-22222-ul-payload-decoded.png]] ... ... @@ -314,16 +314,11 @@ 314 314 [[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]] 315 315 316 316 317 -== ==3.2.2.4Uplinks ====280 +== 3.3 Work Modes and Uplink Payload formats == 318 318 319 -When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**. 320 320 283 +The LT-22222-L has 5 **work modes**. It also has an interrupt/trigger mode for different types of applications that can be used together with any work mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands. 321 321 322 -== 3.3 Working Modes and Uplink Payload formats == 323 - 324 - 325 -The LT-22222-L has 5 **working modes**. It also has an interrupt/trigger mode for different types of applications that can be used together with any working mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands. 326 - 327 327 * (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO 328 328 329 329 * (% style="color:blue" %)**MOD2**(%%): Double DI Counting + DO + RO ... ... @@ -336,7 +336,7 @@ 336 336 337 337 * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5 338 338 339 -The uplink messages are sent over LoRaWAN FPort =2. By default, an uplink message is sent every 10 minutes.297 +The uplink messages are sent over LoRaWAN FPort 2. By default, an uplink message is sent every 10 minutes. 340 340 341 341 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 342 342 ... ... @@ -345,7 +345,7 @@ 345 345 346 346 The uplink payload is 11 bytes long. 347 347 348 -(% style="color:red" %)**Note:The maximum count depends on the bytes number of bytes.306 +(% style="color:red" %)**Note:The maximum count depends on the bytes it is. 349 349 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 350 350 It starts counting again when it reaches the maximum value.**(% style="display:none" wfd-invisible="true" %) 351 351 ... ... @@ -405,13 +405,9 @@ 405 405 * [1] DO2 channel output is LOW, and the DO2 LED is ON. 406 406 * [0] DO1 channel output state: 407 407 ** DO1 is FLOATING when there is no load between DO1 and V+. 408 -** DO1 is HIGH andthere is a load between DO1 and V+.366 +** DO1 is HIGH when there is a load between DO1 and V+. 409 409 ** DO1 LED is OFF in both cases. 410 410 411 -Reserve = 0 412 - 413 -MOD = 1 414 - 415 415 === 3.3.2 AT+MOD~=2, (Double DI Counting) === 416 416 417 417 ... ... @@ -594,13 +594,13 @@ 594 594 ))) 595 595 596 596 ((( 597 -AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s. 551 +Other AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s. 598 598 ))) 599 599 600 600 ((( 601 601 **In addition to that, below are the commands for AVI1 Counting:** 602 602 603 -(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI 1Count to 60)**557 +(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI Count to 60)** 604 604 605 605 (% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 606 606 ... ... @@ -667,27 +667,24 @@ 667 667 ))) 668 668 669 669 670 -=== 3.3.6 AT+ADDMOD~=6 (Trigger Mode, Optional) === 624 +=== 3.3.6 AT+ADDMOD~=6. (Trigger Mode, Optional) === 671 671 672 672 673 -(% style="color:#4f81bd" %)**This mode is optional and intended for trigger purposes. It can operate __alongside__with other modes.**627 +(% style="color:#4f81bd" %)**This mode is optional and intended for trigger purposes. It can operate together with other modes.** 674 674 675 -For example, if you configure the following commands: 629 +For example, if you configured the following commands: 676 676 677 -* **AT+MOD=1 ** **~-~->** Sets the default workingmode678 -* **AT+ADDMOD6=1** **~-~->** Enable strigger mode631 +* **AT+MOD=1 ** **~-~->** The default work mode 632 +* **AT+ADDMOD6=1** **~-~->** Enable trigger mode 679 679 680 -The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. Itwill send uplink packets in two cases:634 +The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. LT will send uplink packets in two cases: 681 681 682 -1. Periodic uplink :Based on TDC time.setabove). These are (% style="color:#4f81bd" %)**unconfirmed**(%%) uplinks.636 +1. Periodically uplink (Based on TDC time). The payload is the same as in normal mode (MOD=1 for the commands above). These are (% style="color:#4f81bd" %)**unconfirmed**(%%) uplinks. 683 683 1. ((( 684 -Trigger uplink: sent when a trigger condition is met. In this case, LT will send two packets 685 - 686 -* The first uplink uses the payload specified in trigger mode (MOD=6). 687 -* The second packet uses the normal mode payload (MOD=1 as set above). Both are (% style="color:#4f81bd" %)**confirmed uplinks.** 638 +Trigger uplink when the trigger condition is met. LT will send two packets in this case. The first uplink uses the payload specified in trigger mode (MOD=6). The second packet uses the normal mode payload (MOD=1 as set above). Both are (% style="color:#4f81bd" %)**confirmed uplinks.** 688 688 ))) 689 689 690 -(% style="color:#037691" %)**AT Commands to set Trigger Condition s**:641 +(% style="color:#037691" %)**AT Commands to set Trigger Condition**: 691 691 692 692 (% style="color:#4f81bd" %)**Trigger based on voltage**: 693 693 ... ... @@ -696,9 +696,9 @@ 696 696 697 697 **Example:** 698 698 699 -AT+AVLIM=3000,6000,0,2000 (triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V) 650 +AT+AVLIM=3000,6000,0,2000 (triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V) 700 700 701 -AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage lower than 5V. Use 0 for parameters that are not in use) 652 +AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage lower than 5V. Use 0 for parameters that are not in use) 702 702 703 703 704 704 (% style="color:#4f81bd" %)**Trigger based on current**: ... ... @@ -708,7 +708,7 @@ 708 708 709 709 **Example:** 710 710 711 -AT+ACLIM=10000,15000,0,0 (triggers an uplink if AC1 current is lower than 10mA or higher than 15mA)662 +AT+ACLIM=10000,15000,0,0 (triggers an uplink if ACI1 voltage is lower than 10mA or higher than 15mA) 712 712 713 713 714 714 (% style="color:#4f81bd" %)**Trigger based on DI status**: ... ... @@ -828,9 +828,9 @@ 828 828 829 829 (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below 830 830 831 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width: 674px" %)832 -| (% style="width:64px" %)**bit(% style="width:68px" %)**bit(% style="width:63px" %)**bit(% style="width:66px" %)**bit(% style="width:109px" %)**bit(% style="width:93px" %)**bit(% style="width:109px" %)**bit(% style="width:99px" %)**bit833 -| (% style="width:64px" %)N/A|(% style="width:68px" %)N/A|(% style="width:63px" %)N/A|(% style="width:66px" %)N/A|(% style="width:109px" %)DI2_STATUS|(% style="width:93px" %)DI2_FLAG|(% style="width:109px" %)DI1_STATUS|(% style="width:99px" %)DI1_FLAG782 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 783 +|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 784 +|N/A|N/A|N/A|N/A|DI2_STATUS|DI2_FLAG|DI1_STATUS|DI1_FLAG 834 834 835 835 * Each bits shows which status has been triggered on this uplink. 836 836 ... ... @@ -892,10 +892,10 @@ 892 892 893 893 (% style="color:#037691" %)**AT command** 894 894 895 -(% border="2"style="width:500px" %)896 -|**Command**|AT+TDC =<time>846 +(% style="width:500px" %) 847 +|**Command**|AT+TDC<time> 897 897 |**Response**| 898 -|**Parameters**| **time**: uplink interval is in milliseconds849 +|**Parameters**|time : uplink interval is in milliseconds 899 899 |**Example**|((( 900 900 AT+TDC=30000 901 901 ... ... @@ -904,14 +904,14 @@ 904 904 905 905 (% style="color:#037691" %)**Downlink payload** 906 906 907 -(% border="2"style="width:500px" %)858 +(% style="width:500px" %) 908 908 |**Payload**|((( 909 909 <prefix><time> 910 910 ))) 911 911 |**Parameters**|((( 912 - **prefix**: 0x01863 +prefix : 0x01 913 913 914 - **time**: uplink interval is in milliseconds, represented by 3 bytes in hexadecimal.865 +time : uplink interval is in milliseconds, represented by 3 bytes in hexadecimal. 915 915 ))) 916 916 |**Example**|((( 917 917 01 **00 75 30** ... ... @@ -923,6 +923,7 @@ 923 923 See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]] 924 924 ))) 925 925 877 + 926 926 ==== 3.4.2.2 Set the Working Mode (AT+MOD) ==== 927 927 928 928 Sets the working mode. ... ... @@ -929,11 +929,11 @@ 929 929 930 930 (% style="color:#037691" %)**AT command** 931 931 932 -(% border="2"style="width:500px" %)933 -|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE =<working_mode>884 +(% style="width:500px" %) 885 +|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE<working_mode> 934 934 |(% style="width:97px" %)**Response**|(% style="width:413px" %) 935 935 |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)((( 936 - **working_mode**:888 +working_mode : 937 937 938 938 1 = (Default mode/factory set): 2ACI + 2AVI + DI + DO + RO 939 939 ... ... @@ -953,15 +953,16 @@ 953 953 Sets the device to working mode 2 (Double DI Counting + DO + RO) 954 954 ))) 955 955 908 + 956 956 (% class="wikigeneratedid" %) 957 957 (% style="color:#037691" %)**Downlink payload** 958 958 959 -(% border="2"style="width:500px" %)912 +(% style="width:500px" %) 960 960 |(% style="width:98px" %)**Payload**|(% style="width:400px" %)<prefix><working_mode> 961 961 |(% style="width:98px" %)**Parameters**|(% style="width:400px" %)((( 962 - **prefix**: 0x0A915 +prefix : 0x0A 963 963 964 - **working_mode**: Working mode, represented by 1 byte in hexadecimal.917 +working_mode : Working mode, represented by 1 byte in hexadecimal. 965 965 ))) 966 966 |(% style="width:98px" %)**Example**|(% style="width:400px" %)((( 967 967 0A **02** ... ... @@ -969,6 +969,7 @@ 969 969 Sets the device to working mode 2 (Double DI Counting + DO + RO) 970 970 ))) 971 971 925 + 972 972 ==== 3.4.2.3 Poll an uplink ==== 973 973 974 974 Requests an uplink from LT-22222-L. ... ... @@ -979,9 +979,9 @@ 979 979 980 980 (% style="color:#037691" %)**Downlink payload** 981 981 982 -(% border="2"style="width:500px" %)936 +(% style="width:500px" %) 983 983 |(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF 984 -|(% style="width:101px" %)**Parameters**|(% style="width:397px" %) **prefix**: 0x08938 +|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)prefix : 0x08 985 985 |(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 986 986 08 FF 987 987 ... ... @@ -988,6 +988,7 @@ 988 988 Requests an uplink from LT-22222-L. 989 989 ))) 990 990 945 + 991 991 ==== 3.4.2.4 Enable/Disable Trigger Mode ==== 992 992 993 993 Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]). ... ... @@ -994,11 +994,11 @@ 994 994 995 995 (% style="color:#037691" %)**AT Command** 996 996 997 -(% border="2"style="width:500px" %)952 +(% style="width:500px" %) 998 998 |(% style="width:95px" %)**Command**|(% style="width:403px" %)AT+ADDMOD6=<enable/disable trigger_mode> 999 999 |(% style="width:95px" %)**Response**|(% style="width:403px" %) 1000 1000 |(% style="width:95px" %)**Parameters**|(% style="width:403px" %)((( 1001 - **enable/disable trigger_mode**:956 +enable/disable trigger_mode : 1002 1002 1003 1003 1 = enable trigger mode 1004 1004 ... ... @@ -1012,12 +1012,12 @@ 1012 1012 1013 1013 (% style="color:#037691" %)**Downlink payload** 1014 1014 1015 -(% border="2"style="width:500px" %)970 +(% style="width:500px" %) 1016 1016 |(% style="width:97px" %)**Payload**|(% style="width:401px" %)<prefix><enable/disable trigger_mode> 1017 1017 |(% style="width:97px" %)**Parameters**|(% style="width:401px" %)((( 1018 - **prefix**: 0x0A 06(two bytes in hexadecimal)973 +prefix : 0x0A 06 1019 1019 1020 - **working mode**: enable (1) or disable (0), represented by 1 byte in hexadecimal.975 +working mode : enable (1) or disable (0), represented by 1 byte in hexadecimal. 1021 1021 ))) 1022 1022 |(% style="width:97px" %)**Example**|(% style="width:401px" %)((( 1023 1023 0A 06 **01** ... ... @@ -1025,316 +1025,153 @@ 1025 1025 Enable trigger mode for the current working mode 1026 1026 ))) 1027 1027 983 + 1028 1028 ==== 3.4.2.5 Poll trigger settings ==== 1029 1029 1030 1030 Polls the trigger settings. 1031 1031 1032 -(% style="color:#037691" %)**AT Command:** 988 +* (% style="color:#037691" %)**AT Command:** 1033 1033 1034 1034 There is no AT Command for this feature. 1035 1035 1036 -(% style="color:#037691" %)**Downlink Payload** 992 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x AB 06):** 1037 1037 1038 -(% border="2" style="width:500px" %) 1039 -|(% style="width:95px" %)**Payload**|(% style="width:403px" %)<prefix> 1040 -|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)**prefix **: AB 06 (two bytes in hexadecimal) 1041 -|(% style="width:95px" %)**Example**|(% style="width:403px" %)((( 1042 -AB 06 994 +(% style="color:blue" %)**0xAB 06 ** (%%) ~/~/ Poll the trigger settings. Device will uplink trigger settings once receive this command 1043 1043 1044 -Uplinks the trigger settings. 1045 -))) 1046 1046 1047 -==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ==== 997 +(% style="width:500px" %) 998 +|(% style="width:95px" %)**Payload**|(% style="width:403px" %)<prefix> 999 +|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)prefix : AB 06 1000 +|(% style="width:95px" %)**Example**|(% style="width:403px" %)AB 06 1048 1048 1049 -Enable or disable DI1/DI2/DI3 as a trigger. 1050 1050 1051 - (%style="color:#037691"%)**ATCommand**1003 +==== 3.4.2.6 Enable / Disable DI1/DI2 as a trigger ==== 1052 1052 1053 -(% border="2" style="width:500px" %) 1054 -|(% style="width:98px" %)**Command**|(% style="width:400px" %)AT+DTRI=<DI1_trigger>,<DI2_trigger> 1055 -|(% style="width:98px" %)**Response**|(% style="width:400px" %) 1056 -|(% style="width:98px" %)**Parameters**|(% style="width:400px" %)((( 1057 -**DI1_trigger:** 1005 +Enable or disable DI1/DI2 as a trigger. 1058 1058 1059 - 1=enable DI1trigger1007 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >** 1060 1060 1061 - 0= disable DI1trigger1009 +**Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 1062 1062 1063 -**DI2 _trigger** 1064 1064 1065 - 1=enable DI2trigger1012 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):** 1066 1066 1067 -0 = disable DI2 trigger 1068 -))) 1069 -|(% style="width:98px" %)**Example**|(% style="width:400px" %)((( 1070 -AT+DTRI=1,0 1014 +(% style="color:blue" %)**0xAA 02 aa bb ** (%%) ~/~/ Same as AT+DTRI=aa,bb 1071 1071 1072 -Enable DI1 trigger, disable DI2 trigger 1073 -))) 1074 1074 1075 -(% class="wikigeneratedid" %) 1076 -(% style="color:#037691" %)**Downlink Payload** 1017 +(% style="width:500px" %) 1018 +|(% style="width:98px" %)Command|(% style="width:400px" %)AT+DTRI=<DI1_trigger><DI2_trigger> 1019 +|(% style="width:98px" %)Response|(% style="width:400px" %) 1020 +|(% style="width:98px" %)Parameters|(% style="width:400px" %)((( 1021 +DI1_trigger: 1077 1077 1078 -(% border="2" style="width:500px" %) 1079 -|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix><DI1_trigger><DI2_trigger> 1080 -|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)((( 1081 -**prefix :** AA 02 (two bytes in hexadecimal) 1023 +1 = enable DI_1 trigger 1082 1082 1083 - **DI1_trigger:**1025 +0 = disable DI_1 trigger 1084 1084 1085 - 1 = enableDI1trigger, represented by 1 byte in hexadecimal.1027 +DI2 _trigger 1086 1086 1087 - 0=disable DI1 trigger, represented by 1 byte in hexadecimal.1029 +1 = enable D2_1 trigger 1088 1088 1089 -**DI2 _trigger** 1090 - 1091 -1 = enable DI2 trigger, represented by 1 byte in hexadecimal. 1092 - 1093 -0 = disable DI2 trigger, represented by 1 byte in hexadecimal. 1031 +0 = disable D2_1 trigger 1094 1094 ))) 1095 -|(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 1096 -AA 02 **01 00** 1033 +|(% style="width:98px" %)Example|(% style="width:400px" %) 1097 1097 1098 -Enable DI1 trigger, disable DI2 trigger 1099 -))) 1100 1100 1101 1101 ==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ==== 1102 1102 1103 1103 Sets DI1 or DI3 (for LT-33222-L) as a trigger. 1104 1104 1040 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG1=a,b** 1105 1105 1106 -(% style="color: #037691" %)**ATCommand**1042 +(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1). 1107 1107 1108 -(% border="2" style="width:500px" %) 1109 -|(% style="width:101px" %)**Command**|(% style="width:397px" %)AT+TRIG1=<interrupt_mode>,<minimum_signal_duration> 1110 -|(% style="width:101px" %)**Response**|(% style="width:397px" %) 1111 -|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)((( 1112 -**interrupt_mode** : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1). 1044 +(% style="color:red" %)**b :** (%%)delay timing. 1113 1113 1114 -**minimum_signal_duration** : the **minimum signal duration** required for the DI1 port to recognize a valid trigger. 1115 -))) 1116 -|(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 1117 -AT+TRIG1=1,100 1046 +**Example:** AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms ) 1118 1118 1119 -Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms. 1120 -))) 1121 1121 1122 -(% class="wikigeneratedid" %) 1123 -(% style="color:#037691" %)**Downlink Payload** 1049 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 01 ):** 1124 1124 1125 -(% border="2" style="width:500px" %) 1126 -|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix><interrupt_mode><minimum_signal_duration> 1127 -|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)((( 1128 -**prefix** : 09 01 (hexadecimal) 1051 +(% style="color:blue" %)**0x09 01 aa bb cc ** (%%) ~/~/ same as AT+TRIG1=aa,0x(bb cc) 1129 1129 1130 -**interrupt_mode** : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal. 1131 1131 1132 -**minimum_signal_duration** : in milliseconds, represented two bytes in hexadecimal. 1133 -))) 1134 -|(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 1135 -09 01 **01 00 64** 1136 - 1137 -Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms. 1138 -))) 1139 - 1140 1140 ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ==== 1141 1141 1142 1142 Sets DI2 as a trigger. 1143 1143 1058 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b** 1144 1144 1145 -(% style="color: #037691" %)**ATCommand**1060 +(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1). 1146 1146 1147 -(% border="2" style="width:500px" %) 1148 -|(% style="width:94px" %)**Command**|(% style="width:404px" %)AT+TRIG2=<interrupt_mode>,<minimum_signal_duration> 1149 -|(% style="width:94px" %)**Response**|(% style="width:404px" %) 1150 -|(% style="width:94px" %)**Parameters**|(% style="width:404px" %)((( 1151 -**interrupt_mode **: 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1). 1062 +(% style="color:red" %)**b :** (%%)delay timing. 1152 1152 1153 -**minimum_signal_duration** : the **minimum signal duration** required for the DI1 port to recognize a valid trigger. 1154 -))) 1155 -|(% style="width:94px" %)**Example**|(% style="width:404px" %)((( 1156 -AT+TRIG2=0,100 1064 +**Example:** AT+TRIG2=0,100 (set DI1 port to trigger on low level, valid signal is 100ms ) 1157 1157 1158 -Set the DI1 port to trigger on a falling edge; the valid signal duration is 100 ms. 1159 -))) 1160 1160 1161 -(% style="color:#037691" %)**Downlink Payload** 1067 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):** 1162 1162 1163 -(% border="2" style="width:500px" %) 1164 -|(% style="width:96px" %)**Payload**|(% style="width:402px" %)<prefix><interrupt_mode><minimum_signal_duration> 1165 -|(% style="width:96px" %)**Parameters**|(% style="width:402px" %)((( 1166 -**prefix** : 09 02 (hexadecimal) 1069 +(% style="color:blue" %)**0x09 02 aa bb cc ** (%%)~/~/ same as AT+TRIG2=aa,0x(bb cc) 1167 1167 1168 -**interrupt_mode **: 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal. 1169 1169 1170 -**minimum_signal_duration** : in milliseconds, represented two bytes in hexadecimal 1171 -))) 1172 -|(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64** 1173 - 1174 -==== ==== 1175 - 1176 1176 ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ==== 1177 1177 1178 -Sets the current trigger based on the AC port. See also[[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]1074 +Sets the current trigger based on the AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1179 1179 1180 -(% style="color:#037691" %)**AT Command** 1076 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ACLIM** 1181 1181 1182 -(% border="2" style="width:500px" %) 1183 -|(% style="width:104px" %)**Command**|(% style="width:394px" %)((( 1184 -AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH> 1185 -))) 1186 -|(% style="width:104px" %)**Response**|(% style="width:394px" %) 1187 -|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)((( 1188 -**AC1_LIMIT_LOW** : lower limit of the current to be checked 1078 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 01 )** 1189 1189 1190 -**A C1_LIMIT_HIGH**:higherlimitofthecurrenttobecked1080 +(% style="color:blue" %)**0x AA 01 aa bb cc dd ee ff gg hh ** (%%) ~/~/ same as AT+ACLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1191 1191 1192 -**AC2_LIMIT_HIGH **: lower limit of the current to be checked 1193 1193 1194 -**AC2_LIMIT_LOW** : higher limit of the current to be checked 1195 -))) 1196 -|(% style="width:104px" %)**Example**|(% style="width:394px" %)((( 1197 -AT+ACLIM=10000,15000,0,0 1198 1198 1199 -Triggers an uplink if AC1 current is lower than 10mA or higher than 15mA 1200 -))) 1201 -|(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1202 - 1203 -(% style="color:#037691" %)**Downlink Payload** 1204 - 1205 -(% border="2" style="width:500px" %) 1206 -|(% style="width:104px" %)**Payload**|(% style="width:394px" %)<prefix><AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH> 1207 -|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)((( 1208 -**prefix **: AA 01 (hexadecimal) 1209 - 1210 -**AC1_LIMIT_LOW** : lower limit of the current to be checked, two bytes in hexadecimal 1211 - 1212 -**AC1_LIMIT_HIGH **: higher limit of the current to be checked, two bytes in hexadecimal 1213 - 1214 -**AC2_LIMIT_HIGH **: lower limit of the current to be checked, two bytes in hexadecimal 1215 - 1216 -**AC2_LIMIT_LOW** : higher limit of the current to be checked, two bytes in hexadecimal 1217 -))) 1218 -|(% style="width:104px" %)**Example**|(% style="width:394px" %)((( 1219 -AA 01 **27** **10 3A** **98** 00 00 00 00 1220 - 1221 -Triggers an uplink if AC1 current is lower than 10mA or higher than 15mA. Set all values to zero for AC2 limits because we are only checking AC1 limits. 1222 -))) 1223 -|(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1224 - 1225 1225 ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ==== 1226 1226 1227 -Sets the current trigger based on the AV port. See also[[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]1086 +Sets the current trigger based on the AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1228 1228 1229 -(% style="color:#037691" %)**AT Command** 1088 +* (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+AVLIM **(%%)** See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]** 1230 1230 1231 -(% border="2" style="width:500px" %) 1232 -|(% style="width:104px" %)**Command**|(% style="width:387px" %)AT+AVLIM= AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH> 1233 -|(% style="width:104px" %)**Response**|(% style="width:387px" %) 1234 -|(% style="width:104px" %)**Parameters**|(% style="width:387px" %)((( 1235 -**AC1_LIMIT_LOW** : lower limit of the current to be checked 1090 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 00 )** 1236 1236 1237 -**A C1_LIMIT_HIGH**:higherlimitof theurrenttobe checked1092 +(% style="color:blue" %)**0x AA 00 aa bb cc dd ee ff gg hh ** (%%) ~/~/ same as AT+AVLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1238 1238 1239 -**AC2_LIMIT_HIGH **: lower limit of the current to be checked 1240 1240 1241 -**AC2_LIMIT_LOW** : higher limit of the current to be checked 1242 -))) 1243 -|(% style="width:104px" %)**Example**|(% style="width:387px" %)((( 1244 -AT+AVLIM=3000,6000,0,2000 1245 - 1246 -Triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V 1247 -))) 1248 -|(% style="width:104px" %)**Note**|(% style="width:387px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1249 - 1250 -(% style="color:#037691" %)**Downlink Payload** 1251 - 1252 -(% border="2" style="width:500px" %) 1253 -|(% style="width:104px" %)**Payload**|(% style="width:394px" %)<prefix><AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH> 1254 -|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)((( 1255 -**prefix **: AA 00 (hexadecimal) 1256 - 1257 -**AV1_LIMIT_LOW** : lower limit of the voltage to be checked, two bytes in hexadecimal 1258 - 1259 -**AV1_LIMIT_HIGH **: higher limit of the voltage to be checked, two bytes in hexadecimal 1260 - 1261 -**AV2_LIMIT_HIGH **: lower limit of the voltage to be checked, two bytes in hexadecimal 1262 - 1263 -**AV2_LIMIT_LOW** : higher limit of the voltage to be checked, two bytes in hexadecimal 1264 -))) 1265 -|(% style="width:104px" %)**Example**|(% style="width:394px" %)((( 1266 -AA 00 **0B B8 17 70 00 00 07 D0** 1267 - 1268 -Triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V. 1269 -))) 1270 -|(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1271 - 1272 1272 ==== 3.4.2.11 Trigger – Set minimum interval ==== 1273 1273 1274 -Sets theAV and AC trigger minimum interval.Thedevice won't respondtoasecond trigger within this set time after the first trigger.1097 +Sets AV and AC trigger minimum interval. Device won't response to the second trigger within this set time after the first trigger. 1275 1275 1276 -(% style="color:#037691" %)**AT Command** 1099 +* (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+ATDC=5 ** ~/~/ (%%)Device won't response the second trigger within 5 minute after the first trigger. 1277 1277 1278 -(% border="2" style="width:500px" %) 1279 -|(% style="width:113px" %)**Command**|(% style="width:385px" %)AT+ATDC=<time> 1280 -|(% style="width:113px" %)**Response**|(% style="width:385px" %) 1281 -|(% style="width:113px" %)**Parameters**|(% style="width:385px" %)((( 1282 -**time** : in minutes 1283 -))) 1284 -|(% style="width:113px" %)**Example**|(% style="width:385px" %)((( 1285 -AT+ATDC=5 1101 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAC )** 1286 1286 1287 -The device won't respond to the second trigger within 5 minutes after the first trigger. 1288 -))) 1289 -|(% style="width:113px" %)Note|(% style="width:385px" %)(% style="color:red" %)**The time must be greater than 5 minutes.** 1103 +(% style="color:blue" %)**0x AC aa bb **(%%) ~/~/ same as AT+ATDC=0x(aa bb) . Unit (min) 1290 1290 1291 -(% style="color:#037691" %)**Downlink Payload** 1292 - 1293 -(% border="2" style="width:500px" %) 1294 -|(% style="width:112px" %)**Payload**|(% style="width:386px" %)<prefix><time> 1295 -|(% style="width:112px" %)**Parameters**|(% style="width:386px" %)((( 1296 -**prefix** : AC (hexadecimal) 1297 - 1298 -**time **: in minutes (two bytes in hexadecimal) 1105 +((( 1106 +(% style="color:red" %)**Note: ATDC setting must be more than 5min** 1299 1299 ))) 1300 -|(% style="width:112px" %)**Example**|(% style="width:386px" %)((( 1301 -AC **00 05** 1302 1302 1303 -The device won't respond to the second trigger within 5 minutes after the first trigger. 1304 -))) 1305 -|(% style="width:112px" %)Note|(% style="width:386px" %)(% style="color:red" %)**The time must be greater than 5 minutes.** 1306 1306 1110 + 1307 1307 ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ==== 1308 1308 1309 1309 Controls the digital outputs DO1, DO2, and DO3 1310 1310 1311 -(% style="color:#037691" %)**AT Command** 1115 +* (% style="color:#037691" %)**AT Command** 1312 1312 1313 -There is no AT Command to control theDigital Output.1117 +There is no AT Command to control Digital Output 1314 1314 1315 1315 1316 -(% style="color:#037691" %)**Downlink Payload** 1120 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x02)** 1317 1317 1318 -(% border="2" style="width:500px" %) 1319 -|(% style="width:115px" %)**Payload**|(% style="width:383px" %)<prefix><DO1><DO2><DO3> 1320 -|(% style="width:115px" %)**Parameters**|(% style="width:383px" %)((( 1321 -**prefix** : 02 (hexadecimal) 1122 +(% style="color:blue" %)**0x02 aa bb cc ** (%%)~/~/ Set DO1/DO2/DO3 output 1322 1322 1323 -**DOI** : 01: Low, 00: High, 11: No action (1 byte in hex) 1324 - 1325 -**DO2** : 01: Low, 00: High, 11: No action (1 byte in hex) 1326 - 1327 -**DO3 **: 01: Low, 00: High, 11: No action (1 byte in hex) 1124 +((( 1125 +If payload = 0x02010001, while there is load between V+ and DOx, it means set DO1 to low, DO2 to high and DO3 to low. 1328 1328 ))) 1329 -|(% style="width:115px" %)**Examples**|(% style="width:383px" %)((( 1330 -02 **01 00 01** 1331 1331 1332 -If there is a load between V+ and DOx, it means DO1 is set to low, DO2 is set to high, and DO3 is set to low. 1333 - 1334 -**More examples:** 1335 - 1336 1336 ((( 1337 -01: Low, 00: High, 11: No action 1129 +01: Low, 00: High , 11: No action 1338 1338 1339 1339 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 1340 1340 |(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**DO1**|(% style="background-color:#4f81bd; color:white" %)**DO2**|(% style="background-color:#4f81bd; color:white" %)**DO3** ... ... @@ -1344,18 +1344,15 @@ 1344 1344 ))) 1345 1345 1346 1346 ((( 1347 -((( 1348 -(% style="color:red" %)**Note: For the LT-22222-L, there is no DO3; the last byte can have any value.** 1139 +(% style="color:red" %)**Note: For LT-22222-L, there is no DO3, the last byte can use any value.** 1349 1349 ))) 1350 1350 1351 1351 ((( 1352 -(% style="color:red" %)** Thedevice will upload a packet if downlink code executes successfully.**1143 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1353 1353 ))) 1354 -))) 1355 -))) 1356 1356 1357 -==== ==== 1358 1358 1147 + 1359 1359 ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ==== 1360 1360 1361 1361 ... ... @@ -1380,7 +1380,7 @@ 1380 1380 00: DO pins will change to an inverter state after timeout 1381 1381 1382 1382 1383 -(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status: 1172 +(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Ports status: 1384 1384 1385 1385 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1386 1386 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1388,7 +1388,7 @@ 1388 1388 |0x00|DO1 set to high 1389 1389 |0x11|DO1 NO Action 1390 1390 1391 -(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status: 1180 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Ports status: 1392 1392 1393 1393 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1394 1394 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1396,7 +1396,7 @@ 1396 1396 |0x00|DO2 set to high 1397 1397 |0x11|DO2 NO Action 1398 1398 1399 -(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status: 1188 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Ports status: 1400 1400 1401 1401 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1402 1402 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1404,16 +1404,16 @@ 1404 1404 |0x00|DO3 set to high 1405 1405 |0x11|DO3 NO Action 1406 1406 1407 -(% style="color:#4f81bd" %)**Sixth ,Seventh,Eighth,and Ninth Bytes**:(%%) Latching time(Unit: ms)1196 +(% style="color:#4f81bd" %)**Sixth and Seventh and Eighth and Ninth Byte**:(%%) Latching time. Unit: ms 1408 1408 1409 1409 1410 1410 (% style="color:red" %)**Note: ** 1411 1411 1412 - Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes1201 + Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes 1413 1413 1414 - Before firmware v1.6.0,the latch time only supported2 bytes.1203 + Before Firmwre v1.6.0 the latch time only suport 2 bytes. 1415 1415 1416 -(% style="color:red" %)**Device will upload a packet if thedownlink code executes successfully.**1205 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1417 1417 1418 1418 1419 1419 **Example payload:** ... ... @@ -1420,21 +1420,22 @@ 1420 1420 1421 1421 **~1. A9 01 01 01 01 07 D0** 1422 1422 1423 -DO1 pin ,DO2 pin,andDO3 pin will be set tolow, lastfor2 seconds,andthenreverttotheiroriginal state.1212 +DO1 pin & DO2 pin & DO3 pin will be set to Low, last 2 seconds, then change back to original state. 1424 1424 1425 1425 **2. A9 01 00 01 11 07 D0** 1426 1426 1427 -DO1 pin issettohigh, DO2 pinissettolow,andDO3 pintakesno action.Thislastsfor2 secondsandthenrevertstotheoriginal state.1216 +DO1 pin set high, DO2 pin set low, DO3 pin no action, last 2 seconds, then change back to original state. 1428 1428 1429 1429 **3. A9 00 00 00 00 07 D0** 1430 1430 1431 -DO1 pin ,DO2 pin,andDO3 pin will be set to high, lastfor2 seconds,andthenallchange to low.1220 +DO1 pin & DO2 pin & DO3 pin will be set to high, last 2 seconds, then both change to low. 1432 1432 1433 1433 **4. A9 00 11 01 00 07 D0** 1434 1434 1435 -DO1 pin takesno action, DO2 pinissettolow,andDO3 pinissettohigh.Thislastsfor2 seconds,afterwhichDO1 pintakesno action, DO2 pinissettohigh,andDO3 pinissettolow.1224 +DO1 pin no action, DO2 pin set low, DO3 pin set high, last 2 seconds, then DO1 pin no action, DO2 pin set high, DO3 pin set low 1436 1436 1437 1437 1227 + 1438 1438 ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ==== 1439 1439 1440 1440 ... ... @@ -1449,11 +1449,11 @@ 1449 1449 1450 1450 1451 1451 ((( 1452 -If payload is0x030100, it means settingRO1 to close and RO2 to open.1242 +If payload = 0x030100, it means set RO1 to close and RO2 to open. 1453 1453 ))) 1454 1454 1455 1455 ((( 1456 -00: Close , 01: Open , 11: No action 1246 +00: Closed , 01: Open , 11: No action 1457 1457 1458 1458 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %) 1459 1459 |(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2** ... ... @@ -1470,9 +1470,9 @@ 1470 1470 (% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1471 1471 1472 1472 1263 + 1473 1473 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== 1474 1474 1475 -Controls the relay output time. 1476 1476 1477 1477 * (% style="color:#037691" %)**AT Command:** 1478 1478 ... ... @@ -1484,15 +1484,15 @@ 1484 1484 (% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set RO1/RO2 relay with time control 1485 1485 1486 1486 1487 -This is to control the relay output time. I t includesfour bytes:1277 +This is to control the relay output time of relay. Include four bytes: 1488 1488 1489 1489 (% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05) 1490 1490 1491 1491 (% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode 1492 1492 1493 -01: Relays will change back to theiroriginal state after timeout.1283 +01: Relays will change back to original state after timeout. 1494 1494 1495 -00: Relays will change to theinverter state after timeout.1285 +00: Relays will change to an inverter state after timeout 1496 1496 1497 1497 1498 1498 (% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status: ... ... @@ -1505,12 +1505,12 @@ 1505 1505 1506 1506 (% style="color:red" %)**Note:** 1507 1507 1508 - Since firmware v1.6.0, the latch time supportsboth4 bytes and 2 bytes.1298 + Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes 1509 1509 1510 - Before firmware v1.6.0,the latch time only supported2 bytes.1300 + Before Firmwre v1.6.0 the latch time only suport 2 bytes. 1511 1511 1512 1512 1513 -(% style="color:red" %)**Device will upload a packet if thedownlink code executes successfully.**1303 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1514 1514 1515 1515 1516 1516 **Example payload:** ... ... @@ -1517,19 +1517,19 @@ 1517 1517 1518 1518 **~1. 05 01 11 07 D0** 1519 1519 1520 -Relay1 and Relay2 will be set to NC, last ing2 seconds, thenreverttotheiroriginal state1310 +Relay1 and Relay 2 will be set to NC , last 2 seconds, then change back to original state. 1521 1521 1522 1522 **2. 05 01 10 07 D0** 1523 1523 1524 -Relay1 will change to NC, Relay2 will change to NO, last ing2 seconds, then bothwill reverttotheiroriginal state.1314 +Relay1 will change to NC, Relay2 will change to NO, last 2 seconds, then both change back to original state. 1525 1525 1526 1526 **3. 05 00 01 07 D0** 1527 1527 1528 -Relay1 will change to NO, Relay2 will change to NC, last ing2 seconds, thenRelay1willchange to NC,andRelay2willchange to NO.1318 +Relay1 will change to NO, Relay2 will change to NC, last 2 seconds, then relay change to NC,Relay2 change to NO. 1529 1529 1530 1530 **4. 05 00 00 07 D0** 1531 1531 1532 -Relay1 andRelay2 will change to NO, lasting2 seconds, then bothwillchange to NC.1322 +Relay 1 & relay2 will change to NO, last 2 seconds, then both change to NC. 1533 1533 1534 1534 1535 1535 ... ... @@ -1536,7 +1536,7 @@ 1536 1536 ==== 3.4.2.16 Counting ~-~- Voltage threshold counting ==== 1537 1537 1538 1538 1539 -When thevoltage exceedsthe threshold, counting begins. For details,see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]1329 +When voltage exceed the threshold, count. Feature see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1540 1540 1541 1541 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1542 1542 ... ... @@ -1545,76 +1545,15 @@ 1545 1545 (% style="color:blue" %)**0xA5 aa bb cc ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc 1546 1546 1547 1547 1548 -(% style="color:#037691" %)**AT Command** 1549 1549 1550 -(% border="2" style="width:500px" %) 1551 -|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage><logic> 1552 -|(% style="width:137px" %)**Response**|(% style="width:361px" %) 1553 -|(% style="width:137px" %)**Parameters**|(% style="width:361px" %)((( 1554 -**voltage** : voltage threshold in mV 1555 - 1556 -**logic**: 1557 - 1558 -0 : lower than 1559 - 1560 -1: higher than 1561 - 1562 -if you leave logic parameter blank, it is considered 0 1563 -))) 1564 -|(% style="width:137px" %)**Examples**|(% style="width:361px" %)((( 1565 -AT+VOLMAX=20000 1566 - 1567 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1568 - 1569 -AT+VOLMAX=20000,0 1570 - 1571 -If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1 1572 - 1573 -AT+VOLMAX=20000,1 1574 - 1575 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1576 -))) 1577 - 1578 -(% style="color:#037691" %)**Downlink Payload** 1579 - 1580 -(% border="2" style="width:500px" %) 1581 -|(% style="width:140px" %)**Payload**|(% style="width:358px" %)<prefix><voltage><logic> 1582 -|(% style="width:140px" %)**Parameters**|(% style="width:358px" %)((( 1583 -**prefix** : A5 (hex) 1584 - 1585 -**voltage** : voltage threshold in mV (2 bytes in hex) 1586 - 1587 -**logic**: (1 byte in hexadecimal) 1588 - 1589 -0 : lower than 1590 - 1591 -1: higher than 1592 - 1593 -if you leave logic parameter blank, it is considered 1 (higher than) 1594 -))) 1595 -|(% style="width:140px" %)**Example**|(% style="width:358px" %)((( 1596 -A5 **4E 20** 1597 - 1598 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1599 - 1600 -A5 **4E 20 00** 1601 - 1602 -If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1 1603 - 1604 -A5 **4E 20 01** 1605 - 1606 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1607 -))) 1608 - 1609 1609 ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ==== 1610 1610 1611 -This feature allows users to pre-configure specific count numbers for various counting parameters such as Count1, Count2, or AVI1 Count. Use the AT command to set the desired count number for each configuration. 1612 1612 1613 1613 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) ** 1614 1614 1615 1615 (% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count 1616 1616 1617 -(% style="color:red" %)**bb cc dd ee: **(%%) Thenumber to be set1346 +(% style="color:red" %)**bb cc dd ee: **(%%)number to be set 1618 1618 1619 1619 1620 1620 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):** ... ... @@ -1622,55 +1622,12 @@ 1622 1622 (% style="color:blue" %)**0x A8 aa bb cc dd ee ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee) 1623 1623 1624 1624 1625 -(% style="color:#037691" %)**AT Command** 1626 1626 1627 -(% border="2" style="width:500px" %) 1628 -|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter><number> 1629 -|(% style="width:134px" %)**Response**|(% style="width:364px" %) 1630 -|(% style="width:134px" %)**Parameters**|(% style="width:364px" %)((( 1631 -**counting_parameter** : 1632 - 1633 -1: COUNT1 1634 - 1635 -2: COUNT2 1636 - 1637 -3: AVI1 Count 1638 - 1639 -**number** : Start number 1640 -))) 1641 -|(% style="width:134px" %)**Example**|(% style="width:364px" %)((( 1642 -AT+SETCNT=1,10 1643 - 1644 -Sets the COUNT1 to 10. 1645 -))) 1646 - 1647 -(% style="color:#037691" %)**Downlink Payload** 1648 - 1649 -(% border="2" style="width:500px" %) 1650 -|(% style="width:135px" %)**Payload**|(% style="width:363px" %)<prefix><counting_parameter><number> 1651 -|(% style="width:135px" %)**Parameters**|(% style="width:363px" %)((( 1652 -prefix : A8 (hex) 1653 - 1654 -**counting_parameter** : (1 byte in hexadecimal) 1655 - 1656 -1: COUNT1 1657 - 1658 -2: COUNT2 1659 - 1660 -3: AVI1 Count 1661 - 1662 -**number** : Start number, 4 bytes in hexadecimal 1663 -))) 1664 -|(% style="width:135px" %)**Example**|(% style="width:363px" %)((( 1665 -A8 **01 00 00 00 0A** 1666 - 1667 -Sets the COUNT1 to 10. 1668 -))) 1669 - 1670 1670 ==== 3.4.2.18 Counting ~-~- Clear Counting ==== 1671 1671 1672 -This feature clears the counting in counting mode. 1673 1673 1358 +Clear counting for counting mode 1359 + 1674 1674 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT **(%%) ~/~/ clear all counting 1675 1675 1676 1676 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):** ... ... @@ -1677,30 +1677,14 @@ 1677 1677 1678 1678 (% style="color:blue" %)**0x A6 01 ** (%%)~/~/ clear all counting 1679 1679 1680 -(% style="color:#037691" %)**AT Command** 1681 1681 1682 -(% border="2" style="width:500px" %) 1683 -|(% style="width:142px" %)**Command**|(% style="width:356px" %)AT+CLRCOUNT 1684 -|(% style="width:142px" %)**Response**|(% style="width:356px" %)- 1685 1685 1686 -(% style="color:#037691" %)**Downlink Payload** 1687 - 1688 -(% border="2" style="width:500px" %) 1689 -|(% style="width:141px" %)**Payload**|(% style="width:357px" %)<prefix><clear?> 1690 -|(% style="width:141px" %)**Parameters**|(% style="width:357px" %)((( 1691 -prefix : A6 (hex) 1692 - 1693 -clear? : 01 (hex) 1694 -))) 1695 -|(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01** 1696 - 1697 1697 ==== 3.4.2.19 Counting ~-~- Change counting mode to save time ==== 1698 1698 1699 -This feature allows you to configure the device to save its counting result to internal flash memory at specified intervals. By setting a save time, the device will periodically store the counting data to prevent loss in case of power failure. The save interval can be adjusted to suit your requirements, with a minimum value of 30 seconds. 1700 1700 1701 1701 * (% style="color:#037691" %)**AT Command:** 1702 1702 1703 -(% style="color:blue" %)**AT+COUTIME=60 **(%%)~/~/ sthesave time to 60 seconds.Thedevice will save the counting result in internal flash every 60 seconds. (Min value: 30seconds)1373 +(% style="color:blue" %)**AT+COUTIME=60 **(%%)~/~/ Set save time to 60 seconds. Device will save the counting result in internal flash every 60 seconds. (min value: 30) 1704 1704 1705 1705 1706 1706 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):** ... ... @@ -1708,7 +1708,7 @@ 1708 1708 (% style="color:blue" %)**0x A7 aa bb cc ** (%%)~/~/ same as AT+COUTIME =aa bb cc, 1709 1709 1710 1710 ((( 1711 - Range: aa bb cc:0 to 16777215, (unit:s)1381 +range: aa bb cc:0 to 16777215, (unit:second) 1712 1712 ))) 1713 1713 1714 1714 ... ... @@ -1715,13 +1715,12 @@ 1715 1715 1716 1716 ==== 3.4.2.20 Reset save RO DO state ==== 1717 1717 1718 -This feature allows you to reset the saved relay output (RO) and digital output (DO) states when the device joins the network. By configuring this setting, you can control whether the device should retain or reset the relay states after a reset and rejoin to the network. 1719 1719 1720 1720 * (% style="color:#037691" %)**AT Command:** 1721 1721 1722 1722 (% style="color:blue" %)**AT+RODORESET=1 **(%%)~/~/ RODO will close when the device joining the network. (default) 1723 1723 1724 -(% style="color:blue" %)**AT+RODORESET=0 **(%%)~/~/ After the device is reset, the previously saved RODO state (only MOD2 to MOD5) is read, and its state willnot change when thedevicereconnectsto the network.1393 +(% style="color:blue" %)**AT+RODORESET=0 **(%%)~/~/ After the device is reset, the previously saved RODO state (only MOD2 to MOD5) is read, and its state is not changed when it is reconnected to the network. 1725 1725 1726 1726 1727 1727 * (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):** ... ... @@ -1732,7 +1732,6 @@ 1732 1732 1733 1733 ==== 3.4.2.21 Encrypted payload ==== 1734 1734 1735 -This feature allows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption. 1736 1736 1737 1737 * (% style="color:#037691" %)**AT Command:** 1738 1738 ... ... @@ -1747,9 +1747,9 @@ 1747 1747 1748 1748 * (% style="color:#037691" %)**AT Command:** 1749 1749 1750 -(% style="color:blue" %)**AT+GETSENSORVALUE=0 **(%%)~/~/ The serial port retrieves the reading of the current sensor.1418 +(% style="color:blue" %)**AT+GETSENSORVALUE=0 **(%%)~/~/ The serial port gets the reading of the current sensor 1751 1751 1752 -(% style="color:blue" %)**AT+GETSENSORVALUE=1 **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.1420 +(% style="color:blue" %)**AT+GETSENSORVALUE=1 **(%%)~/~/ The serial port gets the current sensor reading and uploads it. 1753 1753 1754 1754 1755 1755 ... ... @@ -1939,10 +1939,10 @@ 1939 1939 1940 1940 == 3.6 Interface Details == 1941 1941 1942 -=== 3.6.1 Digital Input Port s: DI1/DI2/DI3 (For LT-33222-L,LowActive) ===1610 +=== 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) === 1943 1943 1944 1944 1945 -Support sNPN-type sensors.1613 +Support NPN-type sensor 1946 1946 1947 1947 [[image:1653356991268-289.png]] 1948 1948
- dragino-ttn-te.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -273.8 KB - Content
- lorawan-nw.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -250.6 KB - Content