Changes for page LT-22222-L -- LoRa I/O Controller User Manual
Last modified by Mengting Qiu on 2025/06/04 18:42
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 3 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -23,8 +23,12 @@ 23 23 24 24 ((( 25 25 ((( 26 -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. 26 +{{info}} 27 +**This manual is also applicable to the LT-33222-L.** 28 +{{/info}} 27 27 30 +The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN end 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 + 28 28 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. 29 29 ))) 30 30 ))) ... ... @@ -36,21 +36,20 @@ 36 36 ((( 37 37 You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways: 38 38 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. 43 +* If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Stack Community Network), you can select a network and register the LT-22222-L I/O controller with it. 40 40 * 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. 41 41 * Setup your own private LoRaWAN network. 42 - 43 -{{info}} 44 - You can use a LoRaWAN gateway, such as the [[Dragino LG308>>https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], to expand or create LoRaWAN coverage in your area. 45 -{{/info}} 46 46 ))) 47 47 48 48 ((( 49 -[[image:1653295757274-912.png]] 50 - 51 51 50 + 51 +The network diagram below illustrates how the LT-22222-L communicates with a typical LoRaWAN network. 52 52 ))) 53 53 54 +(% class="wikigeneratedid" %) 55 +[[image:lorawan-nw.jpg||height="354" width="900"]] 56 + 54 54 == 1.2 Specifications == 55 55 56 56 (% style="color:#037691" %)**Hardware System:** ... ... @@ -111,24 +111,39 @@ 111 111 * Smart cities 112 112 * Smart factory 113 113 114 -= 2.Assemblingthedevice=117 +== 1.5 Hardware Variants == 115 115 119 +(% style="width:524px" %) 120 +|(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description** 121 +|(% style="width:94px" %)**LT33222-L**|(% style="width:98px" %)((( 122 + 123 +)))|(% style="width:329px" %)((( 124 +* 2 x Digital Input (Bi-direction) 125 +* 2 x Digital Output 126 +* 2 x Relay Output (5A@250VAC / 30VDC) 127 +* 2 x 0~~20mA Analog Input (res:0.01mA) 128 +* 2 x 0~~30V Analog Input (res:0.01v) 129 +* 1 x Counting Port 130 +))) 131 + 132 +== 2. Assembling the device == 133 + 116 116 == 2.1 Connecting the antenna == 117 117 118 118 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. 119 119 120 120 {{warning}} 121 -Warning! Do not power on the device without connecting the antenna. 139 +**Warning! Do not power on the device without connecting the antenna.** 122 122 {{/warning}} 123 123 124 124 == 2.2 Terminals == 125 125 126 -The LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 terminals and the lower screw terminal block has 10 terminals. 144 +The LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals. 127 127 128 -Upper screw terminal block (from left to right): 146 +**Upper screw terminal block (from left to right):** 129 129 130 130 (% style="width:634px" %) 131 -|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function 149 +|=(% style="width: 295px;" %)Screw Terminal|=(% style="width: 338px;" %)Function 132 132 |(% style="width:295px" %)GND|(% style="width:338px" %)Ground 133 133 |(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage 134 134 |(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2 ... ... @@ -136,10 +136,10 @@ 136 136 |(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2 137 137 |(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1 138 138 139 -Lower screw terminal block (from left to right): 157 +**Lower screw terminal block (from left to right):** 140 140 141 141 (% style="width:633px" %) 142 -|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function 160 +|=(% style="width: 296px;" %)Screw Terminal|=(% style="width: 334px;" %)Function 143 143 |(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1 144 144 |(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1 145 145 |(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2 ... ... @@ -151,14 +151,12 @@ 151 151 |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2 152 152 |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1 153 153 154 -== 2.3 Powering thedevice ==172 +== 2.3 Connecting LT-22222-L to a Power Source == 155 155 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. 174 +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. 157 157 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. 159 - 160 160 {{warning}} 161 -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. 177 +**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.** 162 162 {{/warning}} 163 163 164 164 ... ... @@ -165,36 +165,51 @@ 165 165 [[image:1653297104069-180.png]] 166 166 167 167 168 -= 3. Registering with a LoRaWAN Network Server = 184 += 3. Registering LT-22222-L with a LoRaWAN Network Server = 169 169 170 - By default, the LT-22222-Lisconfigured to operate in LoRaWAN ClassC mode. ItsupportsOTAA (Over-the-Air Activation),themostsecuremethodforactivating a devicewith a LoRaWANnetworkserver.TheLT-22222-Lcomeswithdeviceregistrationinformation that allowsyou to registeritwith a LoRaWANnetwork,enabling the deviceto performOTAA activation with thenetworkserverupon initialpower-upand after any subsequent reboots.186 +The LT-22222-L supports both OTAA (Over-the-Air Activation) and ABP (Activation By Personalization) methods to activate with a LoRaWAN Network Server. However, OTAA is the most secure method for activating a device with a LoRaWAN Network Server. OTAA regenerates session keys upon initial registration and regenerates new session keys after any subsequent reboots. By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. 171 171 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. 173 173 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. 175 - 176 -The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network. 177 - 178 -[[image:image-20220523172350-1.png||height="266" width="864"]] 179 - 180 180 === 3.2.1 Prerequisites === 181 181 182 - Makesureyou have thedevice registration information such as DevEUI, AppEUI, and AppKeywith 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.191 +The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey that allows you to register it with a LoRaWAN network. These 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 183 184 184 [[image:image-20230425173427-2.png||height="246" width="530"]] 185 185 195 +{{info}} 196 +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. 197 +{{/info}} 198 + 186 186 The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers. 187 187 188 -=== 3.2.2 The Things Stack Sandbox (TTSS)===201 +=== 3.2.2 The Things Stack === 189 189 203 +This section guides you through how to register your LT-22222-L with The Things Stack Sandbox. 204 + 205 +{{info}} 190 190 The Things Stack Sandbox was formally called The Things Stack Community Edition. 207 +{{/info}} 191 191 192 -* Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account. 193 -* Create an application with The Things Stack if you do not have one yet. 194 -* Go to your application page and click on the **End devices** in the left menu. 209 + 210 +The network diagram below illustrates the connection between the LT-22222-L and The Things Stack, as well as how the data can be integrated with the ThingsEye IoT platform. 211 + 212 + 213 +[[image:dragino-lorawan-nw-lt-22222-n.jpg]] 214 + 215 +{{info}} 216 + You can use a LoRaWAN gateway, such as the [[Dragino LPS8N>>https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], to expand or create LoRaWAN coverage in your area. 217 +{{/info}} 218 + 219 + 220 +==== 3.2.2.1 Setting up ==== 221 + 222 +* Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet. 223 +* Log in to your The Things Stack Sandbox account. 224 +* Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs). 225 +* Go to your application's page and click on the **End devices** in the left menu. 195 195 * On the End devices page, click on **+ Register end device**. Two registration options are available: 196 196 197 -==== 3.2.2. 1Using the LoRaWAN Device Repository ====228 +==== 3.2.2.2 Using the LoRaWAN Device Repository ==== 198 198 199 199 * On the **Register end device** page: 200 200 ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**. ... ... @@ -220,7 +220,7 @@ 220 220 221 221 ==== ==== 222 222 223 -==== 3.2.2. 2Adding device manually ====254 +==== 3.2.2.3 Adding device manually ==== 224 224 225 225 * On the **Register end device** page: 226 226 ** Select the option **Enter end device specifies manually** under **Input method**. ... ... @@ -235,7 +235,7 @@ 235 235 236 236 237 237 * Register end device page continued... 238 -** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network' 269 +** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message '//**This end device can be registered on the network**//' 239 239 ** In the **DevEUI** field, enter the **DevEUI**. 240 240 ** In the **AppKey** field, enter the **AppKey**. 241 241 ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. ... ... @@ -251,24 +251,27 @@ 251 251 [[image:lt-22222-device-overview.png||height="625" width="1000"]] 252 252 253 253 254 -==== 3.2.2. 3Joining ====285 +==== 3.2.2.4 Joining ==== 255 255 256 -On the Device overviewpage, click on **Live data** tab. The Live data panel for your device will display.287 +On the Device's page, click on **Live data** tab. The Live data panel for your device will display. 257 257 258 -Now power on your LT-22222-L. Itwill beginjoiningThe 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**).289 +Now power on your LT-22222-L. 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 network 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. 259 259 260 260 261 261 [[image:lt-22222-join-network.png||height="625" width="1000"]] 262 262 263 263 264 - Bydefault,you will receive an uplinkdata messagefrom the device every 10 minutes.295 +==== 3.2.2.5 Uplinks ==== 265 265 297 + 298 +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. 299 + 266 266 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. 267 267 268 268 [[image:lt-22222-ul-payload-decoded.png]] 269 269 270 270 271 -If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **End devices** > ** LT-22222-L**305 +If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > your application > End devices** > **your end device** > **Payload formatters** > **Uplink**. Then select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes. 272 272 273 273 {{info}} 274 274 The Things Stack provides two levels of payload formatters: application level and device level. The device-level payload formatters **override **the application-level payload formatters. ... ... @@ -277,6 +277,11 @@ 277 277 [[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]] 278 278 279 279 314 +==== 3.2.2.6 Downlinks ==== 315 + 316 +When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**. 317 + 318 + 280 280 == 3.3 Working Modes and Uplink Payload formats == 281 281 282 282 ... ... @@ -552,13 +552,13 @@ 552 552 ))) 553 553 554 554 ((( 555 - OtherAT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.594 +AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s. 556 556 ))) 557 557 558 558 ((( 559 559 **In addition to that, below are the commands for AVI1 Counting:** 560 560 561 -(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI Count to 60)** 600 +(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)** 562 562 563 563 (% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 564 564 ... ... @@ -786,9 +786,9 @@ 786 786 787 787 (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below 788 788 789 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width: 515px" %)790 -|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 791 -|N/A|N/A|N/A|N/A|DI2_STATUS|DI2_FLAG|DI1_STATUS|DI1_FLAG 828 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:674px" %) 829 +|(% style="width:64px" %)**bit 7**|(% style="width:68px" %)**bit 6**|(% style="width:63px" %)**bit 5**|(% style="width:66px" %)**bit 4**|(% style="width:109px" %)**bit 3**|(% style="width:93px" %)**bit 2**|(% style="width:109px" %)**bit 1**|(% style="width:99px" %)**bit 0** 830 +|(% 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_FLAG 792 792 793 793 * Each bits shows which status has been triggered on this uplink. 794 794 ... ... @@ -850,10 +850,10 @@ 850 850 851 851 (% style="color:#037691" %)**AT command** 852 852 853 -(% style="width:500px" %) 854 -|**Command**|AT+TDC<time> 892 +(% border="2" style="width:500px" %) 893 +|**Command**|AT+TDC=<time> 855 855 |**Response**| 856 -|**Parameters**|time : uplink interval is in milliseconds 895 +|**Parameters**|**time** : uplink interval is in milliseconds 857 857 |**Example**|((( 858 858 AT+TDC=30000 859 859 ... ... @@ -862,14 +862,14 @@ 862 862 863 863 (% style="color:#037691" %)**Downlink payload** 864 864 865 -(% style="width:500px" %) 904 +(% border="2" style="width:500px" %) 866 866 |**Payload**|((( 867 867 <prefix><time> 868 868 ))) 869 869 |**Parameters**|((( 870 -prefix : 0x01 909 +**prefix** : 0x01 871 871 872 -time : uplink interval is in milliseconds, represented by 3 bytes in hexadecimal. 911 +**time** : uplink interval is in milliseconds, represented by 3 bytes in hexadecimal. 873 873 ))) 874 874 |**Example**|((( 875 875 01 **00 75 30** ... ... @@ -887,11 +887,11 @@ 887 887 888 888 (% style="color:#037691" %)**AT command** 889 889 890 -(% style="width:500px" %) 891 -|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE<working_mode> 929 +(% border="2" style="width:500px" %) 930 +|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE=<working_mode> 892 892 |(% style="width:97px" %)**Response**|(% style="width:413px" %) 893 893 |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)((( 894 -working_mode : 933 +**working_mode** : 895 895 896 896 1 = (Default mode/factory set): 2ACI + 2AVI + DI + DO + RO 897 897 ... ... @@ -914,12 +914,12 @@ 914 914 (% class="wikigeneratedid" %) 915 915 (% style="color:#037691" %)**Downlink payload** 916 916 917 -(% style="width:500px" %) 956 +(% border="2" style="width:500px" %) 918 918 |(% style="width:98px" %)**Payload**|(% style="width:400px" %)<prefix><working_mode> 919 919 |(% style="width:98px" %)**Parameters**|(% style="width:400px" %)((( 920 -prefix : 0x0A 959 +**prefix** : 0x0A 921 921 922 -working_mode : Working mode, represented by 1 byte in hexadecimal. 961 +**working_mode** : Working mode, represented by 1 byte in hexadecimal. 923 923 ))) 924 924 |(% style="width:98px" %)**Example**|(% style="width:400px" %)((( 925 925 0A **02** ... ... @@ -937,9 +937,9 @@ 937 937 938 938 (% style="color:#037691" %)**Downlink payload** 939 939 940 -(% style="width:500px" %) 979 +(% border="2" style="width:500px" %) 941 941 |(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF 942 -|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)prefix : 0x08 981 +|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08 943 943 |(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 944 944 08 FF 945 945 ... ... @@ -952,11 +952,11 @@ 952 952 953 953 (% style="color:#037691" %)**AT Command** 954 954 955 -(% style="width:500px" %) 994 +(% border="2" style="width:500px" %) 956 956 |(% style="width:95px" %)**Command**|(% style="width:403px" %)AT+ADDMOD6=<enable/disable trigger_mode> 957 957 |(% style="width:95px" %)**Response**|(% style="width:403px" %) 958 958 |(% style="width:95px" %)**Parameters**|(% style="width:403px" %)((( 959 -enable/disable trigger_mode : 998 +**enable/disable trigger_mode** : 960 960 961 961 1 = enable trigger mode 962 962 ... ... @@ -970,12 +970,12 @@ 970 970 971 971 (% style="color:#037691" %)**Downlink payload** 972 972 973 -(% style="width:500px" %) 1012 +(% border="2" style="width:500px" %) 974 974 |(% style="width:97px" %)**Payload**|(% style="width:401px" %)<prefix><enable/disable trigger_mode> 975 975 |(% style="width:97px" %)**Parameters**|(% style="width:401px" %)((( 976 -prefix : 0x0A 06 1015 +**prefix** : 0x0A 06 (two bytes in hexadecimal) 977 977 978 -working mode : enable (1) or disable (0), represented by 1 byte in hexadecimal. 1017 +**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal. 979 979 ))) 980 980 |(% style="width:97px" %)**Example**|(% style="width:401px" %)((( 981 981 0A 06 **01** ... ... @@ -993,9 +993,9 @@ 993 993 994 994 (% style="color:#037691" %)**Downlink Payload** 995 995 996 -(% style="width:500px" %) 1035 +(% border="2" style="width:500px" %) 997 997 |(% style="width:95px" %)**Payload**|(% style="width:403px" %)<prefix> 998 -|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)prefix : AB 06 1037 +|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)**prefix **: AB 06 (two bytes in hexadecimal) 999 999 |(% style="width:95px" %)**Example**|(% style="width:403px" %)((( 1000 1000 AB 06 1001 1001 ... ... @@ -1002,29 +1002,29 @@ 1002 1002 Uplinks the trigger settings. 1003 1003 ))) 1004 1004 1005 -==== 3.4.2.6 Enable/Disable DI1/DI2 as a trigger ==== 1044 +==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ==== 1006 1006 1007 -Enable or disable DI1/DI2 as a trigger. 1046 +Enable or disable DI1/DI2/DI3 as a trigger. 1008 1008 1009 1009 (% style="color:#037691" %)**AT Command** 1010 1010 1011 -(% style="width:500px" %) 1012 -|(% style="width:98px" %)Command|(% style="width:400px" %)AT+DTRI=<DI1_trigger><DI2_trigger> 1013 -|(% style="width:98px" %)Response|(% style="width:400px" %) 1014 -|(% style="width:98px" %)Parameters|(% style="width:400px" %)((( 1015 -DI1_trigger: 1050 +(% border="2" style="width:500px" %) 1051 +|(% style="width:98px" %)**Command**|(% style="width:400px" %)AT+DTRI=<DI1_trigger>,<DI2_trigger> 1052 +|(% style="width:98px" %)**Response**|(% style="width:400px" %) 1053 +|(% style="width:98px" %)**Parameters**|(% style="width:400px" %)((( 1054 +**DI1_trigger:** 1016 1016 1017 1017 1 = enable DI1 trigger 1018 1018 1019 1019 0 = disable DI1 trigger 1020 1020 1021 -DI2 _trigger 1060 +**DI2 _trigger** 1022 1022 1023 1023 1 = enable DI2 trigger 1024 1024 1025 1025 0 = disable DI2 trigger 1026 1026 ))) 1027 -|(% style="width:98px" %)Example|(% style="width:400px" %)((( 1066 +|(% style="width:98px" %)**Example**|(% style="width:400px" %)((( 1028 1028 AT+DTRI=1,0 1029 1029 1030 1030 Enable DI1 trigger, disable DI2 trigger ... ... @@ -1033,24 +1033,24 @@ 1033 1033 (% class="wikigeneratedid" %) 1034 1034 (% style="color:#037691" %)**Downlink Payload** 1035 1035 1036 -(% style="width:500px" %) 1037 -|(% style="width:101px" %)Payload|(% style="width:397px" %)<prefix><DI1_trigger><DI2_trigger> 1038 -|(% style="width:101px" %)Parameters|(% style="width:397px" %)((( 1039 -prefix : AA 02 1075 +(% border="2" style="width:500px" %) 1076 +|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix><DI1_trigger><DI2_trigger> 1077 +|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)((( 1078 +**prefix :** AA 02 (two bytes in hexadecimal) 1040 1040 1041 -DI1_trigger: 1080 +**DI1_trigger:** 1042 1042 1043 1043 1 = enable DI1 trigger, represented by 1 byte in hexadecimal. 1044 1044 1045 1045 0 = disable DI1 trigger, represented by 1 byte in hexadecimal. 1046 1046 1047 -DI2 _trigger 1086 +**DI2 _trigger** 1048 1048 1049 1049 1 = enable DI2 trigger, represented by 1 byte in hexadecimal. 1050 1050 1051 1051 0 = disable DI2 trigger, represented by 1 byte in hexadecimal. 1052 1052 ))) 1053 -|(% style="width:101px" %)Example|(% style="width:397px" %)((( 1092 +|(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 1054 1054 AA 02 **01 00** 1055 1055 1056 1056 Enable DI1 trigger, disable DI2 trigger ... ... @@ -1060,145 +1060,239 @@ 1060 1060 1061 1061 Sets DI1 or DI3 (for LT-33222-L) as a trigger. 1062 1062 1063 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG1=a,b** 1064 1064 1065 -(% style="color: red" %)**a:** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).1103 +(% style="color:#037691" %)**AT Command** 1066 1066 1067 -(% style="color:red" %)**b :** (%%)delay timing. 1105 +(% border="2" style="width:500px" %) 1106 +|(% style="width:101px" %)**Command**|(% style="width:397px" %)AT+TRIG1=<interrupt_mode>,<minimum_signal_duration> 1107 +|(% style="width:101px" %)**Response**|(% style="width:397px" %) 1108 +|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)((( 1109 +**interrupt_mode** : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1). 1068 1068 1069 -**Example:** AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms ) 1111 +**minimum_signal_duration** : the **minimum signal duration** required for the DI1 port to recognize a valid trigger. 1112 +))) 1113 +|(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 1114 +AT+TRIG1=1,100 1070 1070 1116 +Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms. 1117 +))) 1071 1071 1072 -* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 01 ):** 1119 +(% class="wikigeneratedid" %) 1120 +(% style="color:#037691" %)**Downlink Payload** 1073 1073 1074 -(% style="color:blue" %)**0x09 01 aa bb cc ** (%%) ~/~/ same as AT+TRIG1=aa,0x(bb cc) 1122 +(% border="2" style="width:500px" %) 1123 +|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix><interrupt_mode><minimum_signal_duration> 1124 +|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)((( 1125 +**prefix** : 09 01 (hexadecimal) 1075 1075 1127 +**interrupt_mode** : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal. 1076 1076 1077 -(% style="width:500px" %) 1078 -|(% style="width:101px" %)Command|(% style="width:397px" %) 1079 -|(% style="width:101px" %)Response|(% style="width:397px" %) 1080 -|(% style="width:101px" %)Parameters|(% style="width:397px" %) 1081 -|(% style="width:101px" %)Example|(% style="width:397px" %) 1129 +**minimum_signal_duration** : in milliseconds, represented two bytes in hexadecimal. 1130 +))) 1131 +|(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 1132 +09 01 **01 00 64** 1082 1082 1134 +Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms. 1135 +))) 1083 1083 1084 1084 ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ==== 1085 1085 1086 1086 Sets DI2 as a trigger. 1087 1087 1088 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b** 1089 1089 1090 -(% style="color: red" %)**a:** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).1142 +(% style="color:#037691" %)**AT Command** 1091 1091 1092 -(% style="color:red" %)**b :** (%%)delay timing. 1144 +(% border="2" style="width:500px" %) 1145 +|(% style="width:94px" %)**Command**|(% style="width:404px" %)AT+TRIG2=<interrupt_mode>,<minimum_signal_duration> 1146 +|(% style="width:94px" %)**Response**|(% style="width:404px" %) 1147 +|(% style="width:94px" %)**Parameters**|(% style="width:404px" %)((( 1148 +**interrupt_mode **: 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1). 1093 1093 1094 -**Example:** AT+TRIG2=0,100 (Set the DI1 port to trigger on a falling edge; the valid signal duration is 100 ms) 1150 +**minimum_signal_duration** : the **minimum signal duration** required for the DI1 port to recognize a valid trigger. 1151 +))) 1152 +|(% style="width:94px" %)**Example**|(% style="width:404px" %)((( 1153 +AT+TRIG2=0,100 1095 1095 1155 +Set the DI1 port to trigger on a falling edge; the valid signal duration is 100 ms. 1156 +))) 1096 1096 1097 - *(% style="color:#037691" %)**Downlink Payload(prefix 0x09 02 ):**1158 +(% style="color:#037691" %)**Downlink Payload** 1098 1098 1099 -(% style="color:blue" %)**0x09 02 aa bb cc ** (%%)~/~/ same as AT+TRIG2=aa,0x(bb cc) 1160 +(% border="2" style="width:500px" %) 1161 +|(% style="width:96px" %)**Payload**|(% style="width:402px" %)<prefix><interrupt_mode><minimum_signal_duration> 1162 +|(% style="width:96px" %)**Parameters**|(% style="width:402px" %)((( 1163 +**prefix** : 09 02 (hexadecimal) 1100 1100 1165 +**interrupt_mode **: 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal. 1101 1101 1167 +**minimum_signal_duration** : in milliseconds, represented two bytes in hexadecimal 1168 +))) 1169 +|(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64** 1170 + 1171 +==== ==== 1172 + 1173 +==== 3.4.2.9 Trigger – Set AC (current) as a trigger ==== 1174 + 1175 +Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1176 + 1102 1102 (% style="color:#037691" %)**AT Command** 1103 1103 1104 -(% style="width:500px" %) 1105 -|(% style="width:94px" %)Command|(% style="width:404px" %)AT+TRIG=<interrupt_mode><minimum_signal_duration> 1106 -|(% style="width:94px" %)Response|(% style="width:404px" %) 1107 -|(% style="width:94px" %)Parameters|(% style="width:404px" %)((( 1108 -interrupt_mode : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1). 1179 +(% border="2" style="width:500px" %) 1180 +|(% style="width:104px" %)**Command**|(% style="width:394px" %)((( 1181 +AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH> 1182 +))) 1183 +|(% style="width:104px" %)**Response**|(% style="width:394px" %) 1184 +|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)((( 1185 +**AC1_LIMIT_LOW** : lower limit of the current to be checked 1109 1109 1110 -minimum_signal_duration : the **minimum signal duration** required for the DI1 port to recognize a valid trigger. 1187 +**AC1_LIMIT_HIGH **: higher limit of the current to be checked 1188 + 1189 +**AC2_LIMIT_HIGH **: lower limit of the current to be checked 1190 + 1191 +**AC2_LIMIT_LOW** : higher limit of the current to be checked 1111 1111 ))) 1112 -|(% style="width: 94px" %)Example|(% style="width:404px" %)(((1113 -AT+ TRIG2=0,1001193 +|(% style="width:104px" %)**Example**|(% style="width:394px" %)((( 1194 +AT+ACLIM=10000,15000,0,0 1114 1114 1115 - Set the DI1 port to triggerona fallingedge;the validsignal durationis100ms.1196 +Triggers an uplink if AC1 current is lower than 10mA or higher than 15mA 1116 1116 ))) 1198 +|(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1117 1117 1118 1118 (% style="color:#037691" %)**Downlink Payload** 1119 1119 1120 -(% style="width:500px" %) 1121 -|(% style="width: 96px" %)Payload|(% style="width:402px" %)<prefix><interrupt_mode><minimum_signal_duration>1122 -|(% style="width: 96px" %)Parameters|(% style="width:402px" %)(((1123 -prefix : 09021202 +(% border="2" style="width:500px" %) 1203 +|(% style="width:104px" %)**Payload**|(% style="width:394px" %)<prefix><AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH> 1204 +|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)((( 1205 +**prefix **: AA 01 (hexadecimal) 1124 1124 1125 - interrupt_mode:0:fallingedge; 1:risingedge, 2:fallingandraisingedge (forMOD=1), representedby1byte in hexadecimal.1207 +**AC1_LIMIT_LOW** : lower limit of the current to be checked, two bytes in hexadecimal 1126 1126 1127 -<minimum_signal_duration>, represented two bytes in hexadecimal 1128 -))) 1129 -|(% style="width:96px" %)Example|(% style="width:402px" %)09 02 **00 00 64** 1209 +**AC1_LIMIT_HIGH **: higher limit of the current to be checked, two bytes in hexadecimal 1130 1130 1131 - ==== 3.4.2.9Trigger– SetAC(current)asatrigger====1211 +**AC2_LIMIT_HIGH **: lower limit of the current to be checked, two bytes in hexadecimal 1132 1132 1133 -Sets the current trigger based on the AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1213 +**AC2_LIMIT_LOW** : higher limit of the current to be checked, two bytes in hexadecimal 1214 +))) 1215 +|(% style="width:104px" %)**Example**|(% style="width:394px" %)((( 1216 +AA 01 **27** **10 3A** **98** 00 00 00 00 1134 1134 1135 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ACLIM** 1218 +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. 1219 +))) 1220 +|(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1136 1136 1137 - *(%style="color:#037691"%)**DownlinkPayload(prefix0xAA 01 )**1222 +==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ==== 1138 1138 1139 - (%style="color:blue"%)**0xAA 01 aabb ccddeeff gghh ** (%%) ~/~/ sameasAT+ACLIMSee [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]1224 +Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1140 1140 1226 +(% style="color:#037691" %)**AT Command** 1141 1141 1142 -(% style="width:500px" %) 1143 -|(% style="width:104px" %)Command|(% style="width:3 94px" %)AT+ACLIM1144 -|(% style="width:104px" %)Response|(% style="width:3 94px" %)1145 -|(% style="width:104px" %)Parameters|(% style="width:3 94px" %)-1146 - |(%style="width:104px"%)Example|(%style="width:394px"%)AT+ACLIM1228 +(% border="2" style="width:500px" %) 1229 +|(% style="width:104px" %)**Command**|(% style="width:387px" %)AT+AVLIM= AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH> 1230 +|(% style="width:104px" %)**Response**|(% style="width:387px" %) 1231 +|(% style="width:104px" %)**Parameters**|(% style="width:387px" %)((( 1232 +**AC1_LIMIT_LOW** : lower limit of the current to be checked 1147 1147 1234 +**AC1_LIMIT_HIGH **: higher limit of the current to be checked 1148 1148 1236 +**AC2_LIMIT_HIGH **: lower limit of the current to be checked 1149 1149 1150 - (%style="width:500px"%)1151 - |(% style="width:104px" %)Payload|(% style="width:394px" %)<prefix>1152 -|(% style="width:104px" %) Parameters|(% style="width:394px" %)prefix : AA 011153 - |(% style="width:104px" %)Example|(% style="width:394px" %)AA1 aa bb cc dd ee ff gg hh1238 +**AC2_LIMIT_LOW** : higher limit of the current to be checked 1239 +))) 1240 +|(% style="width:104px" %)**Example**|(% style="width:387px" %)((( 1241 +AT+AVLIM=3000,6000,0,2000 1154 1154 1243 +Triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V 1244 +))) 1245 +|(% style="width:104px" %)**Note**|(% style="width:387px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1155 1155 1156 - ====3.4.2.10Trigger – Set AV (voltage) as trigger====1247 +(% style="color:#037691" %)**Downlink Payload** 1157 1157 1158 -Sets the current trigger based on the AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1249 +(% border="2" style="width:500px" %) 1250 +|(% style="width:104px" %)**Payload**|(% style="width:394px" %)<prefix><AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH> 1251 +|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)((( 1252 +**prefix **: AA 00 (hexadecimal) 1159 1159 1160 -* (% style="color:#037691" %)**ATCommand**(%%):(%style="color:blue"%)**AT+AVLIM**(%%)** See [[triggermode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**1254 +**AV1_LIMIT_LOW** : lower limit of the voltage to be checked, two bytes in hexadecimal 1161 1161 1162 -* (%style="color:#037691"%)**DownlinkPayload(prefix0xAA 00 )**1256 +**AV1_LIMIT_HIGH **: higher limit of the voltage to be checked, two bytes in hexadecimal 1163 1163 1164 - (% style="color:blue" %)**0xAA00 aa bb cc ddeeffgghh** (%%) ~/~/ sameasAT+AVLIMSee[[triggermode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]1258 +**AV2_LIMIT_HIGH **: lower limit of the voltage to be checked, two bytes in hexadecimal 1165 1165 1260 +**AV2_LIMIT_LOW** : higher limit of the voltage to be checked, two bytes in hexadecimal 1261 +))) 1262 +|(% style="width:104px" %)**Example**|(% style="width:394px" %)((( 1263 +AA 00 **0B B8 17 70 00 00 07 D0** 1166 1166 1265 +Triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V. 1266 +))) 1267 +|(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1268 + 1167 1167 ==== 3.4.2.11 Trigger – Set minimum interval ==== 1168 1168 1169 -Sets AV and AC trigger minimum interval. Device won't responsetothesecond trigger within this set time after the first trigger.1271 +Sets the AV and AC trigger minimum interval. The device won't respond to a second trigger within this set time after the first trigger. 1170 1170 1171 - *(% 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.1273 +(% style="color:#037691" %)**AT Command** 1172 1172 1173 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xAC )** 1275 +(% border="2" style="width:500px" %) 1276 +|(% style="width:113px" %)**Command**|(% style="width:385px" %)AT+ATDC=<time> 1277 +|(% style="width:113px" %)**Response**|(% style="width:385px" %) 1278 +|(% style="width:113px" %)**Parameters**|(% style="width:385px" %)((( 1279 +**time** : in minutes 1280 +))) 1281 +|(% style="width:113px" %)**Example**|(% style="width:385px" %)((( 1282 +AT+ATDC=5 1174 1174 1175 -(% style="color:blue" %)**0x AC aa bb **(%%) ~/~/ same as AT+ATDC=0x(aa bb) . Unit (min) 1176 - 1177 -((( 1178 -(% style="color:red" %)**Note: ATDC setting must be more than 5min** 1284 +The device won't respond to the second trigger within 5 minutes after the first trigger. 1179 1179 ))) 1286 +|(% style="width:113px" %)Note|(% style="width:385px" %)(% style="color:red" %)**The time must be greater than 5 minutes.** 1180 1180 1288 +(% style="color:#037691" %)**Downlink Payload** 1181 1181 1290 +(% border="2" style="width:500px" %) 1291 +|(% style="width:112px" %)**Payload**|(% style="width:386px" %)<prefix><time> 1292 +|(% style="width:112px" %)**Parameters**|(% style="width:386px" %)((( 1293 +**prefix** : AC (hexadecimal) 1182 1182 1295 +**time **: in minutes (two bytes in hexadecimal) 1296 +))) 1297 +|(% style="width:112px" %)**Example**|(% style="width:386px" %)((( 1298 +AC **00 05** 1299 + 1300 +The device won't respond to the second trigger within 5 minutes after the first trigger. 1301 +))) 1302 +|(% style="width:112px" %)Note|(% style="width:386px" %)(% style="color:red" %)**The time must be greater than 5 minutes.** 1303 + 1183 1183 ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ==== 1184 1184 1185 1185 Controls the digital outputs DO1, DO2, and DO3 1186 1186 1187 - *(% style="color:#037691" %)**AT Command**1308 +(% style="color:#037691" %)**AT Command** 1188 1188 1189 -There is no AT Command to control Digital Output 1310 +There is no AT Command to control the Digital Output. 1190 1190 1191 1191 1192 - *(% style="color:#037691" %)**Downlink Payload(prefix 0x02)**1313 +(% style="color:#037691" %)**Downlink Payload** 1193 1193 1194 -(% style="color:blue" %)**0x02 aa bb cc ** (%%)~/~/ Set DO1/DO2/DO3 output 1315 +(% border="2" style="width:500px" %) 1316 +|(% style="width:115px" %)**Payload**|(% style="width:383px" %)<prefix><DO1><DO2><DO3> 1317 +|(% style="width:115px" %)**Parameters**|(% style="width:383px" %)((( 1318 +**prefix** : 02 (hexadecimal) 1195 1195 1196 -((( 1197 -If payload = 0x02010001, while there is load between V+ and DOx, it means set DO1 to low, DO2 to high and DO3 to low. 1320 +**DOI** : 01: Low, 00: High, 11: No action (1 byte in hex) 1321 + 1322 +**DO2** : 01: Low, 00: High, 11: No action (1 byte in hex) 1323 + 1324 +**DO3 **: 01: Low, 00: High, 11: No action (1 byte in hex) 1198 1198 ))) 1326 +|(% style="width:115px" %)**Examples**|(% style="width:383px" %)((( 1327 +02 **01 00 01** 1199 1199 1329 +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. 1330 + 1331 +**More examples:** 1332 + 1200 1200 ((( 1201 -01: Low, 00: High 1334 +01: Low, 00: High, 11: No action 1202 1202 1203 1203 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 1204 1204 |(% 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** ... ... @@ -1208,15 +1208,18 @@ 1208 1208 ))) 1209 1209 1210 1210 ((( 1211 -(% style="color:red" %)**Note: For LT-22222-L, there is no DO3, the last byte can use any value.** 1344 +((( 1345 +(% style="color:red" %)**Note: For the LT-22222-L, there is no DO3; the last byte can have any value.** 1212 1212 ))) 1213 1213 1214 1214 ((( 1215 -(% style="color:red" %)** Device will upload a packet if downlink code executes successfully.**1349 +(% style="color:red" %)**The device will upload a packet if downlink code executes successfully.** 1216 1216 ))) 1351 +))) 1352 +))) 1217 1217 1354 +==== ==== 1218 1218 1219 - 1220 1220 ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ==== 1221 1221 1222 1222 ... ... @@ -1241,7 +1241,7 @@ 1241 1241 00: DO pins will change to an inverter state after timeout 1242 1242 1243 1243 1244 -(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port sstatus:1380 +(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status: 1245 1245 1246 1246 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1247 1247 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1249,7 +1249,7 @@ 1249 1249 |0x00|DO1 set to high 1250 1250 |0x11|DO1 NO Action 1251 1251 1252 -(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port sstatus:1388 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status: 1253 1253 1254 1254 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1255 1255 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1257,7 +1257,7 @@ 1257 1257 |0x00|DO2 set to high 1258 1258 |0x11|DO2 NO Action 1259 1259 1260 -(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port sstatus:1396 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status: 1261 1261 1262 1262 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1263 1263 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1265,16 +1265,16 @@ 1265 1265 |0x00|DO3 set to high 1266 1266 |0x11|DO3 NO Action 1267 1267 1268 -(% style="color:#4f81bd" %)**Sixth andSeventhandEighth and Ninth Byte**:(%%) Latching time.Unit: ms1404 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms) 1269 1269 1270 1270 1271 1271 (% style="color:red" %)**Note: ** 1272 1272 1273 - Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes1409 + Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes 1274 1274 1275 - Before Firmwre v1.6.0 the latch time only suport 2 bytes.1411 + Before firmware v1.6.0, the latch time only supported 2 bytes. 1276 1276 1277 -(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1413 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.** 1278 1278 1279 1279 1280 1280 **Example payload:** ... ... @@ -1281,22 +1281,21 @@ 1281 1281 1282 1282 **~1. A9 01 01 01 01 07 D0** 1283 1283 1284 -DO1 pin &DO2 pin&DO3 pin will be set toLow, last 2 seconds, thenchangebackto original state.1420 +DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state. 1285 1285 1286 1286 **2. A9 01 00 01 11 07 D0** 1287 1287 1288 -DO1 pin set high, DO2 pin set low, DO3 pin no action ,last 2 seconds,thenchangebackto original state.1424 +DO1 pin is set to high, DO2 pin is set to low, and DO3 pin takes no action. This lasts for 2 seconds and then reverts to the original state. 1289 1289 1290 1290 **3. A9 00 00 00 00 07 D0** 1291 1291 1292 -DO1 pin &DO2 pin&DO3 pin will be set to high, last 2 seconds, thenbothchange to low.1428 +DO1 pin, DO2 pin, and DO3 pin will be set to high, last for 2 seconds, and then all change to low. 1293 1293 1294 1294 **4. A9 00 11 01 00 07 D0** 1295 1295 1296 -DO1 pin no action, DO2 pin set low, DO3 pin set high ,last 2 seconds, thenDO1 pin no action, DO2 pin set high, DO3 pin set low1432 +DO1 pin takes no action, DO2 pin is set to low, and DO3 pin is set to high. This lasts for 2 seconds, after which DO1 pin takes no action, DO2 pin is set to high, and DO3 pin is set to low. 1297 1297 1298 1298 1299 - 1300 1300 ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ==== 1301 1301 1302 1302 ... ... @@ -1311,11 +1311,11 @@ 1311 1311 1312 1312 1313 1313 ((( 1314 -If payload =0x030100, it means set RO1 to close and RO2 to open.1449 +If payload is 0x030100, it means setting RO1 to close and RO2 to open. 1315 1315 ))) 1316 1316 1317 1317 ((( 1318 -00: Close d, 01: Open , 11: No action1453 +00: Close , 01: Open , 11: No action 1319 1319 1320 1320 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %) 1321 1321 |(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2** ... ... @@ -1332,9 +1332,9 @@ 1332 1332 (% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1333 1333 1334 1334 1335 - 1336 1336 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== 1337 1337 1472 +Controls the relay output time. 1338 1338 1339 1339 * (% style="color:#037691" %)**AT Command:** 1340 1340 ... ... @@ -1346,15 +1346,15 @@ 1346 1346 (% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set RO1/RO2 relay with time control 1347 1347 1348 1348 1349 -This is to control the relay output time of relay. Include four bytes:1484 +This is to control the relay output time. It includes four bytes: 1350 1350 1351 1351 (% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05) 1352 1352 1353 1353 (% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode 1354 1354 1355 -01: Relays will change back to original state after timeout. 1490 +01: Relays will change back to their original state after timeout. 1356 1356 1357 -00: Relays will change to aninverter state after timeout1492 +00: Relays will change to the inverter state after timeout. 1358 1358 1359 1359 1360 1360 (% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status: ... ... @@ -1367,12 +1367,12 @@ 1367 1367 1368 1368 (% style="color:red" %)**Note:** 1369 1369 1370 - Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes1505 + Since firmware v1.6.0, the latch time supports both 4 bytes and 2 bytes. 1371 1371 1372 - Before Firmwre v1.6.0 the latch time only suport 2 bytes.1507 + Before firmware v1.6.0, the latch time only supported 2 bytes. 1373 1373 1374 1374 1375 -(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1510 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.** 1376 1376 1377 1377 1378 1378 **Example payload:** ... ... @@ -1379,19 +1379,19 @@ 1379 1379 1380 1380 **~1. 05 01 11 07 D0** 1381 1381 1382 -Relay1 and Relay changebackto original state.1517 +Relay1 and Relay2 will be set to NC, lasting 2 seconds, then revert to their original state 1383 1383 1384 1384 **2. 05 01 10 07 D0** 1385 1385 1386 -Relay1 will change to NC, Relay2 will change to NO, last 2 seconds, then both changebackto original state.1521 +Relay1 will change to NC, Relay2 will change to NO, lasting 2 seconds, then both will revert to their original state. 1387 1387 1388 1388 **3. 05 00 01 07 D0** 1389 1389 1390 -Relay1 will change to NO, Relay2 will change to NC, last 2 seconds, then relay change to NC,Relay2 change to NO.1525 +Relay1 will change to NO, Relay2 will change to NC, lasting 2 seconds, then Relay1 will change to NC, and Relay2 will change to NO. 1391 1391 1392 1392 **4. 05 00 00 07 D0** 1393 1393 1394 -Relay &relay2 will change to NO, last 2 seconds, then both change to NC.1529 +Relay1 and Relay2 will change to NO, lasting 2 seconds, then both will change to NC. 1395 1395 1396 1396 1397 1397 ... ... @@ -1398,7 +1398,7 @@ 1398 1398 ==== 3.4.2.16 Counting ~-~- Voltage threshold counting ==== 1399 1399 1400 1400 1401 -When voltage exceed the threshold, count. F eature see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]1536 +When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1402 1402 1403 1403 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1404 1404 ... ... @@ -1407,15 +1407,76 @@ 1407 1407 (% style="color:blue" %)**0xA5 aa bb cc ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc 1408 1408 1409 1409 1545 +(% style="color:#037691" %)**AT Command** 1410 1410 1547 +(% border="2" style="width:500px" %) 1548 +|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage><logic> 1549 +|(% style="width:137px" %)**Response**|(% style="width:361px" %) 1550 +|(% style="width:137px" %)**Parameters**|(% style="width:361px" %)((( 1551 +**voltage** : voltage threshold in mV 1552 + 1553 +**logic**: 1554 + 1555 +0 : lower than 1556 + 1557 +1: higher than 1558 + 1559 +if you leave logic parameter blank, it is considered 0 1560 +))) 1561 +|(% style="width:137px" %)**Examples**|(% style="width:361px" %)((( 1562 +AT+VOLMAX=20000 1563 + 1564 +If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1565 + 1566 +AT+VOLMAX=20000,0 1567 + 1568 +If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1 1569 + 1570 +AT+VOLMAX=20000,1 1571 + 1572 +If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1573 +))) 1574 + 1575 +(% style="color:#037691" %)**Downlink Payload** 1576 + 1577 +(% border="2" style="width:500px" %) 1578 +|(% style="width:140px" %)**Payload**|(% style="width:358px" %)<prefix><voltage><logic> 1579 +|(% style="width:140px" %)**Parameters**|(% style="width:358px" %)((( 1580 +**prefix** : A5 (hex) 1581 + 1582 +**voltage** : voltage threshold in mV (2 bytes in hex) 1583 + 1584 +**logic**: (1 byte in hexadecimal) 1585 + 1586 +0 : lower than 1587 + 1588 +1: higher than 1589 + 1590 +if you leave logic parameter blank, it is considered 1 (higher than) 1591 +))) 1592 +|(% style="width:140px" %)**Example**|(% style="width:358px" %)((( 1593 +A5 **4E 20** 1594 + 1595 +If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1596 + 1597 +A5 **4E 20 00** 1598 + 1599 +If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1 1600 + 1601 +A5 **4E 20 01** 1602 + 1603 +If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1604 +))) 1605 + 1411 1411 ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ==== 1412 1412 1608 +This command 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. 1413 1413 1414 1414 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) ** 1415 1415 1416 1416 (% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count 1417 1417 1418 -(% style="color:red" %)**bb cc dd ee: **(%%)number to be set 1614 +(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set 1419 1419 1420 1420 1421 1421 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):** ... ... @@ -1423,12 +1423,55 @@ 1423 1423 (% style="color:blue" %)**0x A8 aa bb cc dd ee ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee) 1424 1424 1425 1425 1622 +(% style="color:#037691" %)**AT Command** 1426 1426 1427 -==== 3.4.2.18 Counting ~-~- Clear Counting ==== 1624 +(% border="2" style="width:500px" %) 1625 +|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter><number> 1626 +|(% style="width:134px" %)**Response**|(% style="width:364px" %) 1627 +|(% style="width:134px" %)**Parameters**|(% style="width:364px" %)((( 1628 +**counting_parameter** : 1428 1428 1630 +1: COUNT1 1429 1429 1430 - Clearcounting for counting mode1632 +2: COUNT2 1431 1431 1634 +3: AVI1 Count 1635 + 1636 +**number** : Start number 1637 +))) 1638 +|(% style="width:134px" %)**Example**|(% style="width:364px" %)((( 1639 +AT+SETCNT=1,10 1640 + 1641 +Sets the COUNT1 to 10. 1642 +))) 1643 + 1644 +(% style="color:#037691" %)**Downlink Payload** 1645 + 1646 +(% border="2" style="width:500px" %) 1647 +|(% style="width:135px" %)**Payload**|(% style="width:363px" %)<prefix><counting_parameter><number> 1648 +|(% style="width:135px" %)**Parameters**|(% style="width:363px" %)((( 1649 +prefix : A8 (hex) 1650 + 1651 +**counting_parameter** : (1 byte in hexadecimal) 1652 + 1653 +1: COUNT1 1654 + 1655 +2: COUNT2 1656 + 1657 +3: AVI1 Count 1658 + 1659 +**number** : Start number, 4 bytes in hexadecimal 1660 +))) 1661 +|(% style="width:135px" %)**Example**|(% style="width:363px" %)((( 1662 +A8 **01 00 00 00 0A** 1663 + 1664 +Sets the COUNT1 to 10. 1665 +))) 1666 + 1667 +==== 3.4.2.18 Counting ~-~- Clear Counting ==== 1668 + 1669 +This command clears the counting in counting mode. 1670 + 1432 1432 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT **(%%) ~/~/ clear all counting 1433 1433 1434 1434 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):** ... ... @@ -1435,14 +1435,30 @@ 1435 1435 1436 1436 (% style="color:blue" %)**0x A6 01 ** (%%)~/~/ clear all counting 1437 1437 1677 +(% style="color:#037691" %)**AT Command** 1438 1438 1679 +(% border="2" style="width:500px" %) 1680 +|(% style="width:142px" %)**Command**|(% style="width:356px" %)AT+CLRCOUNT 1681 +|(% style="width:142px" %)**Response**|(% style="width:356px" %)- 1439 1439 1683 +(% style="color:#037691" %)**Downlink Payload** 1684 + 1685 +(% border="2" style="width:500px" %) 1686 +|(% style="width:141px" %)**Payload**|(% style="width:357px" %)<prefix><clear?> 1687 +|(% style="width:141px" %)**Parameters**|(% style="width:357px" %)((( 1688 +prefix : A6 (hex) 1689 + 1690 +clear? : 01 (hex) 1691 +))) 1692 +|(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01** 1693 + 1440 1440 ==== 3.4.2.19 Counting ~-~- Change counting mode to save time ==== 1441 1441 1696 +This command 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. 1442 1442 1443 1443 * (% style="color:#037691" %)**AT Command:** 1444 1444 1445 -(% style="color:blue" %)**AT+COUTIME=60 **(%%)~/~/ Device will save the counting result in internal flash every 60 seconds. (min value: 30)1700 +(% style="color:blue" %)**AT+COUTIME=60 **(%%)~/~/ Sets the save time to 60 seconds. The device will save the counting result in internal flash every 60 seconds. (Min value: 30 seconds) 1446 1446 1447 1447 1448 1448 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):** ... ... @@ -1450,19 +1450,46 @@ 1450 1450 (% style="color:blue" %)**0x A7 aa bb cc ** (%%)~/~/ same as AT+COUTIME =aa bb cc, 1451 1451 1452 1452 ((( 1453 - range: aa bb cc:0 to 16777215, (unit:second)1708 +Range: aa bb cc:0 to 16777215, (unit: seconds) 1454 1454 ))) 1455 1455 1456 1456 1712 +(% style="color:#037691" %)**AT Command** 1457 1457 1714 +(% border="2" style="width:500px" %) 1715 +|(% style="width:124px" %)**Command**|(% style="width:374px" %)AT+COUTIME=<time> 1716 +|(% style="width:124px" %)**Response**|(% style="width:374px" %) 1717 +|(% style="width:124px" %)**Parameters**|(% style="width:374px" %)time : seconds (0 to 16777215) 1718 +|(% style="width:124px" %)**Example**|(% style="width:374px" %)((( 1719 +AT+COUTIME=60 1720 + 1721 +Sets the device to save its counting results to the memory every 60 seconds. 1722 +))) 1723 + 1724 +(% style="color:#037691" %)**Downlink Payload** 1725 + 1726 +(% border="2" style="width:500px" %) 1727 +|(% style="width:123px" %)**Payload**|(% style="width:375px" %)<prefix><time> 1728 +|(% style="width:123px" %)**Parameters**|(% style="width:375px" %)((( 1729 +prefix : A7 1730 + 1731 +time : seconds, 3 bytes in hexadecimal 1732 +))) 1733 +|(% style="width:123px" %)**Example**|(% style="width:375px" %)((( 1734 +A7 **00 00 3C** 1735 + 1736 +Sets the device to save its counting results to the memory every 60 seconds. 1737 +))) 1738 + 1458 1458 ==== 3.4.2.20 Reset save RO DO state ==== 1459 1459 1741 +This command 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. 1460 1460 1461 1461 * (% style="color:#037691" %)**AT Command:** 1462 1462 1463 1463 (% style="color:blue" %)**AT+RODORESET=1 **(%%)~/~/ RODO will close when the device joining the network. (default) 1464 1464 1465 -(% 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 i snot changedwhenit isreconnectedto the network.1747 +(% 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 will not change when the device reconnects to the network. 1466 1466 1467 1467 1468 1468 * (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):** ... ... @@ -1470,9 +1470,50 @@ 1470 1470 (% style="color:blue" %)**0x AD aa ** (%%)~/~/ same as AT+RODORET =aa 1471 1471 1472 1472 1755 +(% border="2" style="width:500px" %) 1756 +|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state> 1757 +|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1758 +|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1759 +**state** : 1473 1473 1761 +**0** : RODO will close when the device joins the network. (default) 1762 + 1763 +**1**: After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network. 1764 +))) 1765 +|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1766 +(% style="color:blue" %)**AT+RODORESET=1 ** 1767 + 1768 +RODO will close when the device joins the network. (default) 1769 + 1770 +(% style="color:blue" %)**AT+RODORESET=0 ** 1771 + 1772 +After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network. 1773 +))) 1774 + 1775 +(% border="2" style="width:500px" %) 1776 +|(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state> 1777 +|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1778 +**prefix** : AD 1779 + 1780 +**state** : 1781 + 1782 +**0** : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal. 1783 + 1784 +**1**: After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network. - represents as 1 byte in hexadecimal 1785 +))) 1786 +|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1787 +AD **01** 1788 + 1789 +RODO will close when the device joins the network. (default) 1790 + 1791 +AD **00** 1792 + 1793 +After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network. 1794 +))) 1795 + 1474 1474 ==== 3.4.2.21 Encrypted payload ==== 1475 1475 1798 +This command 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. 1476 1476 1477 1477 * (% style="color:#037691" %)**AT Command:** 1478 1478 ... ... @@ -1481,21 +1481,67 @@ 1481 1481 (% style="color:blue" %)**AT+DECRYPT=0 **(%%)~/~/ Encrypt when uploading payload (default) 1482 1482 1483 1483 1807 +(% border="2" style="width:500px" %) 1808 +|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state> 1809 +|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1810 +|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1811 +state : 1484 1484 1813 +1 : The payload is uploaded without encryption 1814 + 1815 +0 : The payload is encrypted when uploaded (default) 1816 +))) 1817 +|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1818 +AT+DECRYPT=1 1819 + 1820 +The payload is uploaded without encryption 1821 + 1822 +AT+DECRYPT=0 1823 + 1824 +The payload is encrypted when uploaded (default) 1825 +))) 1826 + 1827 +There is no downlink payload for this configuration. 1828 + 1829 + 1485 1485 ==== 3.4.2.22 Get sensor value ==== 1486 1486 1832 +This command allows you to retrieve and optionally uplink sensor readings through the serial port. 1487 1487 1488 1488 * (% style="color:#037691" %)**AT Command:** 1489 1489 1490 -(% style="color:blue" %)**AT+GETSENSORVALUE=0 **(%%)~/~/ The serial port gets the reading of the current sensor1836 +(% style="color:blue" %)**AT+GETSENSORVALUE=0 **(%%)~/~/ The serial port retrieves the reading of the current sensor. 1491 1491 1492 -(% style="color:blue" %)**AT+GETSENSORVALUE=1 **(%%)~/~/ The serial port gets the current sensor reading and uploads it.1838 +(% style="color:blue" %)**AT+GETSENSORVALUE=1 **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it. 1493 1493 1494 1494 1841 +(% border="2" style="width:500px" %) 1842 +|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state> 1843 +|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1844 +|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1845 +**state** : 1495 1495 1496 - ====3.4.2.23Resets thedownlinkpacketcount====1847 +**0 **: Retrieves the current sensor reading via the serial port. 1497 1497 1849 +**1 **: Retrieves and uploads the current sensor reading via the serial port. 1850 +))) 1851 +|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1852 +AT+GETSENSORVALUE=0 1498 1498 1854 +Retrieves the current sensor reading via the serial port. 1855 + 1856 +AT+GETSENSORVALUE=1 1857 + 1858 +Retrieves and uplinks the current sensor reading via the serial port. 1859 +))) 1860 + 1861 +There is no downlink payload for this configuration. 1862 + 1863 + 1864 +==== 3.4.2.23 Resetting the downlink packet count ==== 1865 + 1866 +This command manages how the node handles mismatched downlink packet counts. It offers two modes: one disables the reception of further downlink packets if discrepancies occur, while the other resets the downlink packet count to align with the server, ensuring continued communication. 1867 + 1499 1499 * (% style="color:#037691" %)**AT Command:** 1500 1500 1501 1501 (% style="color:blue" %)**AT+DISFCNTCHECK=0 **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node will no longer receive downlink packets (default) ... ... @@ -1503,10 +1503,37 @@ 1503 1503 (% style="color:blue" %)**AT+DISFCNTCHECK=1 **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node resets the downlink packet count and keeps it consistent with the server downlink packet count. 1504 1504 1505 1505 1875 +(% border="2" style="width:500px" %) 1876 +|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state> 1877 +|(% style="width:130px" %)**Response**|(% style="width:368px" %)((( 1878 + 1879 +))) 1880 +|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)((( 1881 +**state **: 1506 1506 1883 +**0** : When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node stops receiving further downlink packets (default). 1884 + 1885 + 1886 +**1** : When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node resets its downlink packet count to match the server's, ensuring consistency. 1887 +))) 1888 +|(% style="width:130px" %)**Example**|(% style="width:368px" %)((( 1889 +AT+DISFCNTCHECK=0 1890 + 1891 +When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node stops receiving further downlink packets (default). 1892 + 1893 +AT+DISFCNTCHECK=1 1894 + 1895 +When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node resets its downlink packet count to match the server's, ensuring consistency. 1896 +))) 1897 + 1898 +There is no downlink payload for this configuration. 1899 + 1900 + 1507 1507 ==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ==== 1508 1508 1509 1509 1904 +This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceeds the allowed byte limit for the current data rate (DR). The command provides two modes: one enables splitting the data into batches to ensure compliance with the byte limit, while the other prioritizes the payload and ignores the MACANS in cases of overflow. 1905 + 1510 1510 * (% style="color:#037691" %)**AT Command:** 1511 1511 1512 1512 (% style="color:blue" %)**AT+DISMACANS=0** (%%) ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of 11 bytes (DR0 of US915, DR2 of AS923, DR2 of AU195), the node will send a packet with a payload of 00 and a port of 4. (default) ... ... @@ -1518,10 +1518,50 @@ 1518 1518 1519 1519 (% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set the DISMACANS=1 1520 1520 1917 +(% style="color:#037691" %)**AT Command** 1521 1521 1919 +(% border="2" style="width:500px" %) 1920 +|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state> 1921 +|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1922 +|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1923 +**state** : 1522 1522 1925 +**0** : When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default) 1926 + 1927 +**1** : When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload. 1928 +))) 1929 +|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1930 +AT+DISMACANS=0 1931 + 1932 +When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default) 1933 + 1934 +AT+DISMACANS=1 1935 + 1936 +When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload. 1937 +))) 1938 + 1939 +(% style="color:#037691" %)**Downlink Payload** 1940 + 1941 +(% border="2" style="width:500px" %) 1942 +|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state> 1943 +|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)((( 1944 +**prefix** : 21 1945 + 1946 +**state** : (2 bytes in hexadecimal) 1947 + 1948 +**0** : When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default) 1949 + 1950 +**1 **: When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload. 1951 +))) 1952 +|(% style="width:126px" %)**Example**|(% style="width:372px" %)((( 1953 +21 **00 01** 1954 + 1955 +Set DISMACANS=1 1956 +))) 1957 + 1523 1523 ==== 3.4.2.25 Copy downlink to uplink ==== 1524 1524 1960 +This command enables the device to immediately uplink the content of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100. 1525 1525 1526 1526 * (% style="color:#037691" %)**AT Command**(%%)**:** 1527 1527 ... ... @@ -1534,8 +1534,22 @@ 1534 1534 1535 1535 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1536 1536 1973 +(% border="2" style="width:500px" %) 1974 +|(% style="width:122px" %)**Command**|(% style="width:376px" %)((( 1975 +AT+RPL=5 1537 1537 1977 +After receiving a downlink packet from the server, the node immediately uplinks the content of the packet back to the server using port number 100. 1978 +))) 1979 +|(% style="width:122px" %)**Example**|(% style="width:376px" %)((( 1980 +Downlink: 1538 1538 1982 +01 00 02 58 1983 + 1984 +Uplink: 1985 + 1986 +01 01 00 02 58 1987 +))) 1988 + 1539 1539 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]] 1540 1540 1541 1541 For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. ... ... @@ -1542,14 +1542,16 @@ 1542 1542 1543 1543 1544 1544 1545 -==== 3.4.2.26 Query version number andfrequency band、TDC ====1995 +==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ==== 1546 1546 1997 +This command is used to query key information about the device, including its firmware version, frequency band, sub band, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device. 1547 1547 1548 1548 * ((( 1549 1549 (% style="color:#037691" %)**Downlink Payload**(%%)**:** 1550 1550 1551 -(% style="color:blue" %)**26 01 ** (%%) ~/~/ Downlink 26 01canquery deviceuploadfrequency, frequency band, softwareversion number,TDC time.2002 +(% style="color:blue" %)**26 01 ** (%%) ~/~/ The downlink payload 26 01 is used to query the device's firmware version, frequency band, sub band, and TDC time. 1552 1552 2004 + 1553 1553 1554 1554 ))) 1555 1555 ... ... @@ -1579,6 +1579,8 @@ 1579 1579 1580 1580 === 3.5.2 Configuring ThingsEye.io === 1581 1581 2034 +The ThingsEye.io IoT platform is not open for self-registration at the moment. If you are interested in testing the platform, please send your project information to admin@thingseye.io, and we will create an account for you. 2035 + 1582 1582 * Login to your [[ThingsEye.io >>https://thingseye.io]]account. 1583 1583 * Under the **Integrations center**, click **Integrations**. 1584 1584 * Click the **Add integration** button (the button with the **+** symbol). ... ... @@ -1627,7 +1627,7 @@ 1627 1627 1628 1628 * Choose **Region** from the **Host type**. 1629 1629 * Enter the **cluster** of your **The Things Stack** in the **Region** textbox. You can find the cluster in the url (e.g., https:~/~/**eu1**.cloud.thethings.network/...). 1630 -* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username **and **password **can be found on the MQTT integration page of your The Things Stack account (see Configuring The Things Stack). 2084 +* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username **and **password **can be found on the MQTT integration page of your The Things Stack account (see **3.5.1 Configuring The Things Stack**). 1631 1631 * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**. 1632 1632 1633 1633 [[image:message-1.png]] ... ... @@ -1638,7 +1638,7 @@ 1638 1638 [[image:thingseye-io-step-5.png||height="625" width="1000"]] 1639 1639 1640 1640 1641 -Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings. 2095 +Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings and correct any errors. 1642 1642 1643 1643 1644 1644 [[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]] ... ... @@ -1654,7 +1654,7 @@ 1654 1654 If you want to edit the settings you have provided, click on the **Toggle edit mode** button. Once you have done click on the **Apply changes **button. 1655 1655 1656 1656 {{info}} 1657 -See also ThingsEye documentation. 2111 +See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]]. 1658 1658 {{/info}} 1659 1659 1660 1660 ==== **3.5.2.2 Viewing events** ==== ... ... @@ -1667,7 +1667,7 @@ 1667 1667 [[image:thingseye-events.png||height="686" width="1000"]] 1668 1668 1669 1669 1670 -* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message. 2124 +* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message. 1671 1671 1672 1672 [[image:thingseye-json.png||width="1000"]] 1673 1673 ... ... @@ -1677,12 +1677,17 @@ 1677 1677 If you want to delete an integration, click the **Delete integratio**n button on the Integrations page. 1678 1678 1679 1679 2134 +==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ==== 2135 + 2136 +This will be added soon. 2137 + 2138 + 1680 1680 == 3.6 Interface Details == 1681 1681 1682 -=== 3.6.1 Digital Input Port: DI1/DI2 lowactive2141 +=== 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) === 1683 1683 1684 1684 1685 -Support NPN-type sensor 2144 +Supports NPN-type sensors. 1686 1686 1687 1687 [[image:1653356991268-289.png]] 1688 1688
- dragino-lorawan-nw-lt-22222-n.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +267.3 KB - Content
- dragino-ttn-te.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +273.8 KB - Content
- lorawan-nw.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +250.6 KB - Content