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 (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 26 added, 0 removed)
- dragino-ttn-te.jpg
- integration-details.png
- lorawan-nw.jpg
- lt-22222-device-overview.png
- lt-22222-join-network.png
- lt-22222-l-abp.png
- lt-22222-l-dev-repo-p1.png
- lt-22222-l-dev-repo-reg-p1.png
- lt-22222-l-dev-repo-reg-p2.png
- lt-22222-l-manually-p1.png
- lt-22222-l-manually-p2.png
- lt-22222-ul-payload-decoded.png
- lt-22222-ul-payload-fmt.png
- message-1.png
- thingseye-events.png
- thingseye-io-step-1.png
- thingseye-io-step-2.png
- thingseye-io-step-3.png
- thingseye-io-step-4.png
- thingseye-io-step-5.png
- thingseye-io-step-6.png
- thingseye-json.png
- thingseye.io_integrationsCenter_integrations-2.png
- thingseye.io_integrationsCenter_integrations.png
- tts-mqtt-integration.png
- usb-ttl-programming.png
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -LT-22222-L -- LoRa IO Controller User Manual 1 +LT-22222-L -- LoRa I/O Controller User Manual - Content
-
... ... @@ -17,14 +17,18 @@ 17 17 18 18 19 19 20 -= 1.Introduction = 20 += 1. Introduction = 21 21 22 22 == 1.1 What is the LT-22222-L I/O Controller? == 23 23 24 24 ((( 25 25 ((( 26 -(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)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 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 ))) ... ... @@ -34,25 +34,26 @@ 34 34 ))) 35 35 36 36 ((( 37 -(% style="line-height:1.38; margin-top:16px; margin-bottom:16px" %) 38 -The LT Series I/O Controllers are designed for easy, low-cost installation on LoRaWAN networks. 39 -))) 41 +You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways: 40 40 41 -( ((42 - (%style="line-height:1.38;margin-top:16px;margin-bottom:16px"%)43 - (%style="color:#000000; font-family:Arial,sans-serif; font-size:11pt;font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-position:normal; font-weight:400; text-decoration:none;white-space:pre-wrap" %)You can connect theLT-22222-L I/O Controller to a LoRaWAN networkservice provider in several ways: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. 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 +* Setup your own private LoRaWAN network. 44 44 45 - * (% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)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.46 - *(% style="color:#000000;font-family:Arial,sans-serif;font-size:11pt;font-style:normal;font-variant-alternates:normal;font-variant-east-asian:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)If there is nopublicLoRaWAN coverage in yourrea, you canset up a LoRaWANgateway, ormultiplegateways, andconnectthemto aLoRaWANnetwork server tocreate adequate coverage.Then,register the LT-22222-L I/O controllerwith this network.47 - * (% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)Setup your own private LoRaWAN network.47 +{{info}} 48 + 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. 49 +{{/info}} 48 48 ))) 49 49 50 50 ((( 51 -[[image:1653295757274-912.png]] 52 - 53 53 54 + 55 +The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network. 54 54 ))) 55 55 58 +(% class="wikigeneratedid" %) 59 +[[image:lorawan-nw.jpg||height="354" width="900"]] 60 + 56 56 == 1.2 Specifications == 57 57 58 58 (% style="color:#037691" %)**Hardware System:** ... ... @@ -60,27 +60,27 @@ 60 60 * STM32L072xxxx MCU 61 61 * SX1276/78 Wireless Chip 62 62 * Power Consumption: 63 -** Idle: 4mA@12 v64 -** 20dB Transmit: 34mA@12 v65 -* Operating Temperature: -40 ~~ 85 Degree, No Dew 68 +** Idle: 4mA@12V 69 +** 20dB Transmit: 34mA@12V 70 +* Operating Temperature: -40 ~~ 85 Degrees, No Dew 66 66 67 67 (% style="color:#037691" %)**Interface for Model: LT22222-L:** 68 68 69 -* 2 x Digital dual direction Input (Detect High/Low signal, Max: 50 v, or 220vwith optional external resistor)70 -* 2 x Digital Output (NPN output. Max pull 74 +* 2 x Digital dual direction Input (Detect High/Low signal, Max: 50V, or 220V with optional external resistor) 75 +* 2 x Digital Output (NPN output. Max pull-up voltage 36V,450mA) 71 71 * 2 x Relay Output (5A@250VAC / 30VDC) 72 72 * 2 x 0~~20mA Analog Input (res:0.01mA) 73 -* 2 x 0~~30V Analog Input (res:0.01 v)78 +* 2 x 0~~30V Analog Input (res:0.01V) 74 74 * Power Input 7~~ 24V DC. 75 75 76 76 (% style="color:#037691" %)**LoRa Spec:** 77 77 78 78 * Frequency Range: 79 -** Band 1 (HF): 862 ~~ 1020 M hz80 -** Band 2 (LF): 410 ~~ 528 M hz84 +** Band 1 (HF): 862 ~~ 1020 MHz 85 +** Band 2 (LF): 410 ~~ 528 MHz 81 81 * 168 dB maximum link budget. 82 82 * +20 dBm - 100 mW constant RF output vs. 83 -* +14 dBm high 88 +* +14 dBm high-efficiency PA. 84 84 * Programmable bit rate up to 300 kbps. 85 85 * High sensitivity: down to -148 dBm. 86 86 * Bullet-proof front end: IIP3 = -12.5 dBm. ... ... @@ -96,32 +96,30 @@ 96 96 97 97 == 1.3 Features == 98 98 99 -* LoRaWAN Class A & Class C protocol104 +* LoRaWAN Class A & Class C modes 100 100 * Optional Customized LoRa Protocol 101 101 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869 102 102 * AT Commands to change parameters 103 -* Remote configure parameters via LoRa Downlink 108 +* Remotely configure parameters via LoRaWAN Downlink 104 104 * Firmware upgradable via program port 105 105 * Counting 106 106 107 107 == 1.4 Applications == 108 108 109 -* Smart Buildings &HomeAutomation110 -* Logistics and SupplyChainManagement111 -* Smart Metering112 -* Smart Agriculture113 -* Smart Cities114 -* Smart Factory114 +* Smart buildings & home automation 115 +* Logistics and supply chain management 116 +* Smart metering 117 +* Smart agriculture 118 +* Smart cities 119 +* Smart factory 115 115 116 116 == 1.5 Hardware Variants == 117 117 118 - 119 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %) 120 -|(% style="background-color:#4f81bd; color:white; width:103px" %)**Model**|(% style="background-color:#4f81bd; color:white; width:131px" %)**Photo**|(% style="background-color:#4f81bd; color:white; width:266px" %)**Description** 121 -|(% style="width:103px" %)**LT22222-L**|(% style="width:131px" %)((( 122 -(% style="text-align:center" %) 123 -[[image:image-20230424115112-1.png||height="106" width="58"]] 124 -)))|(% style="width:334px" %)((( 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" %)((( 125 125 * 2 x Digital Input (Bi-direction) 126 126 * 2 x Digital Output 127 127 * 2 x Relay Output (5A@250VAC / 30VDC) ... ... @@ -130,92 +130,199 @@ 130 130 * 1 x Counting Port 131 131 ))) 132 132 133 -= 2. Powering ON the Device = 134 134 135 -(% style="line-height:1.38" %) 136 -(% style="font-size: 11pt; font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; white-space: pre-wrap; font-family: Arial, sans-serif; color: rgb(0, 0, 0); font-weight: 400; font-style: normal; text-decoration: none" %)The LT-22222-L controller can be powered by a 7–24V DC power source. 137 +== 2. Assembling the device == 137 137 138 -* (% style="font-size: 11pt; font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; white-space: pre-wrap; font-family: Arial, sans-serif; color: rgb(0, 0, 0); font-weight: 400; font-style: normal; text-decoration: none" %)Connect VIN to Power Input V+ and GND to Power Input V- to power the LT-22222-L controller. 139 -* (% style="font-size: 11pt; font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; white-space: pre-wrap; font-family: Arial, sans-serif; color: rgb(0, 0, 0); font-weight: 400; font-style: normal; text-decoration: none" %)Connect the positive wire of the power supply to the VIN screw terminal and the negative wire to the GND screw terminal. 139 +== 2.1 Connecting the antenna == 140 140 141 - (% style="font-size: 11pt;font-variant-alternates:normal;font-variant-east-asian:normal;font-variant-ligatures:normal;font-variant-numeric: normal;font-variant-position:normal; white-space:pre-wrap; font-family:Arial, sans-serif;color:rgb(0, 0, 0); font-weight:400; font-style:normal;text-decoration:none"%)The powerindicator(PWR) LEDwillturn onwhenthedevice isproperly powered.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. 142 142 143 +{{warning}} 144 +Warning! Do not power on the device without connecting the antenna. 145 +{{/warning}} 143 143 147 +== 2.2 Terminals == 148 + 149 +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. 150 + 151 +Upper screw terminal block (from left to right): 152 + 153 +(% style="width:634px" %) 154 +|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function 155 +|(% style="width:295px" %)GND|(% style="width:338px" %)Ground 156 +|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage 157 +|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2 158 +|(% style="width:295px" %)AVI1|(% style="width:338px" %)Analog Voltage Input Terminal 1 159 +|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2 160 +|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1 161 + 162 +Lower screw terminal block (from left to right): 163 + 164 +(% style="width:633px" %) 165 +|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function 166 +|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1 167 +|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1 168 +|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2 169 +|(% style="width:296px" %)RO2-1|(% style="width:334px" %)Relay Output 2 170 +|(% style="width:296px" %)DI2+|(% style="width:334px" %)Digital Input 2 171 +|(% style="width:296px" %)DI2-|(% style="width:334px" %)Digital Input 2 172 +|(% style="width:296px" %)DI1+|(% style="width:334px" %)Digital Input 1 173 +|(% style="width:296px" %)DI1-|(% style="width:334px" %)Digital Input 1 174 +|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2 175 +|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1 176 + 177 +== 2.3 Connecting LT-22222-L to a Power Source == 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. 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 Network Server. 182 + 183 +{{warning}} 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. 185 +{{/warning}} 186 + 187 + 144 144 [[image:1653297104069-180.png]] 145 145 146 146 147 -= 3. OperationMode =191 += 3. Registering LT-22222-L with a LoRaWAN Network Server = 148 148 149 - ==3.1How doesit work?==193 +By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. It 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. 150 150 151 -((( 152 -The LT-22222-L is configured to operate in LoRaWAN Class C mode by default. It supports OTAA (Over-the-Air Activation), which is 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. 153 153 154 -For LT-22222-L, the LED will show the Join status: After power on (% style="color:green" %)**TX LED**(%%) will fast blink 5 times, LT-22222-L will enter working mode and start to JOIN LoRaWAN network. (% style="color:green" %)**TX LED**(%%) will be on for 5 seconds after joined in network. When there is message from server, the RX LED will be on for 1 second. 155 -))) 156 156 157 -((( 197 +=== 3.2.1 Prerequisites === 198 + 199 +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. 200 + 201 +Make sure you have the device registration information such as DevEUI, AppEUI, and AppKey with you. 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. 202 + 203 +[[image:image-20230425173427-2.png||height="246" width="530"]] 204 + 205 +{{info}} 158 158 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. 159 - )))207 +{{/info}} 160 160 209 +The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers. 161 161 162 -== 3.2 Exampleo joinLoRaWANnetwork ==211 +=== 3.2.2 Registering with The Things Stack === 163 163 213 +{{info}} 214 +The Things Stack Sandbox was formally called The Things Stack Community Edition. 215 +{{/info}} 164 164 165 -((( 166 -This chapter shows an example for how to join the TTN LoRaWAN Network. Below is the network structure, we use our LG308 as LoRaWAN gateway here. 167 167 168 - 169 -))) 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. 170 170 171 -[[image: image-20220523172350-1.png||height="266" width="864"]]220 +[[image:dragino-ttn-te.jpg]] 172 172 173 173 174 -((( 175 -The LG308 is already set to connect to [[TTN network >>url:https://www.thethingsnetwork.org/]]. So what we need to do now is only configure register this device to TTN: 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. 225 +* Create an application with The Things Stack if you do not have one yet. 226 +* Go to your application page and click on the **End devices** in the left menu. 227 +* On the End devices page, click on **+ Register end device**. Two registration options are available: 176 176 177 - 178 -))) 179 179 180 -((( 181 -(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LT IO controller. 182 -))) 230 +==== 3.2.2.1 Using the LoRaWAN Device Repository ==== 183 183 184 -((( 185 -Each LT is shipped with a sticker with the default device EUI as below: 186 -))) 232 +* On the **Register end device** page: 233 +** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**. 234 +** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists. 235 +*** **End device brand**: Dragino Technology Co., Limited 236 +*** **Model**: LT22222-L I/O Controller 237 +*** **Hardware ver**: Unknown 238 +*** **Firmware ver**: 1.6.0 239 +*** **Profile (Region)**: Select the region that matches your device. 240 +** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 187 187 188 -[[image:image-20230425173427-2.png||height="246" width="530"]] 189 189 243 +[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]] 190 190 191 -Input these keys in the LoRaWAN Server portal. Below is TTN screen shot: 192 192 193 -**Add APP EUI in the application.** 246 +* Register end device page continued... 247 +** 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'. 248 +** In the **DevEUI** field, enter the **DevEUI**. 249 +** In the **AppKey** field, enter the **AppKey.** 250 +** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 251 +** Under **After registration**, select the **View registered end device** option. 194 194 195 -[[image: 1653297955910-247.png||height="321" width="716"]]253 +[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]] 196 196 255 +==== ==== 197 197 198 - **AddAPPKEYandDEV EUI**257 +==== 3.2.2.2 Adding device manually ==== 199 199 200 -[[image:1653298023685-319.png]] 259 +* On the **Register end device** page: 260 +** Select the option **Enter end device specifies manually** under **Input method**. 261 +** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 262 +** Select the **LoRaWAN version** as **LoRaWAN Specification 1.0.3** 263 +** Select the **Regional Parameters version** as** RP001 Regional Parameters 1.0.3 revision A** 264 +** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the hidden section. 265 +** Select the option **Over the air activation (OTAA)** under the **Activation mode.** 266 +** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list. 201 201 268 +[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]] 202 202 203 -((( 204 -(% style="color:blue" %)**Step 2**(%%): Power on LT and it will auto join to the TTN network. After join success, it will start to upload message to TTN and user can see in the panel. 205 205 206 - 207 -))) 271 +* Register end device page continued... 272 +** 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' 273 +** In the **DevEUI** field, enter the **DevEUI**. 274 +** In the **AppKey** field, enter the **AppKey**. 275 +** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 276 +** Under **After registration**, select the **View registered end device** option. 277 +** Click the **Register end device** button. 208 208 209 -[[image: 1653298044601-602.png||height="405" width="709"]]279 +[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]] 210 210 211 211 212 - ==3.3 UplinkPayload==282 +You will be navigated to the **Device overview** page. 213 213 214 214 215 - There are five workingmodes + oneinterrupt modeon LT fordifferent typeapplication:285 +[[image:lt-22222-device-overview.png||height="625" width="1000"]] 216 216 217 -* (% style="color:blue" %)**MOD1**(%%): (default setting): 2 x ACI + 2AVI + DI + DO + RO 218 218 288 +==== 3.2.2.3 Joining ==== 289 + 290 +On the Device overview page, click on **Live data** tab. The Live data panel for your device will display. 291 + 292 +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. 293 + 294 + 295 +[[image:lt-22222-join-network.png||height="625" width="1000"]] 296 + 297 + 298 +==== 3.2.2.4 Uplinks ==== 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 +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 + 305 +[[image:lt-22222-ul-payload-decoded.png]] 306 + 307 + 308 +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** > **Payload formatters** > **Uplink**. Then select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes. 309 + 310 +{{info}} 311 +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. 312 +{{/info}} 313 + 314 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]] 315 + 316 + 317 +==== 3.2.2.4 Uplinks ==== 318 + 319 +When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**. 320 + 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 +* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO 328 + 219 219 * (% style="color:blue" %)**MOD2**(%%): Double DI Counting + DO + RO 220 220 221 221 * (% style="color:blue" %)**MOD3**(%%): Single DI Counting + 2 x ACI + DO + RO ... ... @@ -226,12 +226,19 @@ 226 226 227 227 * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5 228 228 339 +The uplink messages are sent over LoRaWAN FPort=2. By default, an uplink message is sent every 10 minutes. 340 + 229 229 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 230 230 231 - 232 232 ((( 233 -Th e uplink payload includestotally 9 bytes. Uplink packetsuse FPORT=2 and every 10 minutessendoneuplink by default. (%style="display:none" %)344 +This is the default mode. 234 234 346 +The uplink payload is 11 bytes long. 347 + 348 +(% style="color:red" %)**Note:The maximum count depends on the bytes number of bytes. 349 +The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 350 +It starts counting again when it reaches the maximum value.**(% style="display:none" wfd-invisible="true" %) 351 + 235 235 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 236 236 |(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1** 237 237 |Value|((( ... ... @@ -242,29 +242,29 @@ 242 242 ACI1 Current 243 243 )))|((( 244 244 ACI2 Current 245 -)))|DIDORO*|((( 362 +)))|**DIDORO***|((( 246 246 Reserve 247 247 )))|MOD 248 248 ))) 249 249 250 250 ((( 251 -(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination forRO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1.Totally1bytesas below368 +(% style="color:#4f81bd" %)*** DIDORO**(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, and its size is1 byte long as shown below. 252 252 253 253 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 254 -|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 255 -|RO1|RO2|DI3|DI2|DI1|DO3|DO2|DO1 371 +|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 372 +|RO1|RO2|--DI3--|DI2|DI1|--DO3--|DO2|DO1 256 256 ))) 257 257 258 -* RO is for relay. ROx=1 close, ROx=0 alwaysopen.259 -* DI is for digital input. DIx=1: highorfloat, DIx=0:low.260 -* DO is for reverse digital output. DOx=1: output low, DOx=0:highorfloat.375 +* RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN. 376 +* DI is for digital input. DIx=1: HIGH or FLOATING, DIx=0: LOW. 377 +* DO is for reverse digital output. DOx=1: LOW, DOx=0: HIGH or FLOATING. 261 261 262 -(% style="color:red" %)**Note: DI3 and DO3 bit are not valid for LT-22222-L** 379 +(% style="color:red" %)**Note: DI3 and DO3 bits are not valid for LT-22222-L** 263 263 264 -For example if payload is: [[image:image-20220523175847-2.png]] 381 +For example, if the payload is: [[image:image-20220523175847-2.png]] 265 265 266 266 267 -**The value fortheinterfaceis: **384 +**The interface values can be calculated as follows: ** 268 268 269 269 AVI1 channel voltage is 0x04AB/1000=1195(DEC)/1000=1.195V 270 270 ... ... @@ -274,36 +274,41 @@ 274 274 275 275 ACI2 channel current is 0x1300/1000=4.864mA 276 276 277 -The last byte 0xAA= 10101010( B) means394 +The last byte 0xAA= **10101010**(b) means, 278 278 279 -* [1] RO1 relay channel is close and the RO1 LED is ON. 280 -* [0] RO2 relay channel is open and RO2 LED is OFF; 396 +* [1] The RO1 relay channel is CLOSED, and the RO1 LED is ON. 397 +* [0] The RO2 relay channel is OPEN, and the RO2 LED is OFF. 398 +* **[1] DI3 - not used for LT-22222-L.** 399 +* [0] DI2 channel input is LOW, and the DI2 LED is OFF. 400 +* [1] DI1 channel input state: 401 +** DI1 is FLOATING when no sensor is connected between DI1+ and DI1-. 402 +** DI1 is HIGH when a sensor is connected between DI1- and DI1+ and the sensor is ACTIVE. 403 +** DI1 LED is ON in both cases. 404 +* **[0] DO3 - not used for LT-22222-L.** 405 +* [1] DO2 channel output is LOW, and the DO2 LED is ON. 406 +* [0] DO1 channel output state: 407 +** DO1 is FLOATING when there is no load between DO1 and V+. 408 +** DO1 is HIGH and there is a load between DO1 and V+. 409 +** DO1 LED is OFF in both cases. 281 281 282 - **LT22222-L:**411 +Reserve = 0 283 283 284 -* [1] DI2 channel is high input and DI2 LED is ON; 285 -* [0] DI1 channel is low input; 413 +MOD = 1 286 286 287 -* [0] DO3 channel output state 288 -** DO3 is float in case no load between DO3 and V+.; 289 -** DO3 is high in case there is load between DO3 and V+. 290 -** DO3 LED is off in both case 291 -* [1] DO2 channel output is low and DO2 LED is ON. 292 -* [0] DO1 channel output state 293 -** DO1 is float in case no load between DO1 and V+.; 294 -** DO1 is high in case there is load between DO1 and V+. 295 -** DO1 LED is off in both case 296 - 297 297 === 3.3.2 AT+MOD~=2, (Double DI Counting) === 298 298 299 299 300 300 ((( 301 -**For LT-22222-L**: this mode the**DI1 and DI2** are used as counting pins.419 +**For LT-22222-L**: In this mode, **DI1 and DI2** are used as counting pins. 302 302 ))) 303 303 304 304 ((( 305 -T otal:11 bytespayload423 +The uplink payload is 11 bytes long. 306 306 425 +(% style="color:red" %)**Note:The maximum count depends on the bytes it is. 426 +The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 427 +It starts counting again when it reaches the maximum value.** 428 + 307 307 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 308 308 |(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1** 309 309 |Value|COUNT1|COUNT2 |DIDORO*|((( ... ... @@ -312,26 +312,26 @@ 312 312 ))) 313 313 314 314 ((( 315 -(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination forRO1, RO2, DO3, DO2 and DO1.Totally1bytesas below437 +(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, FIRST, Reserve, Reserve, DO3, DO2 and DO1, and its size is 1 byte long as shown below. 316 316 317 317 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 318 -|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 319 -|RO1|RO2|FIRST|Reserve|Reserve|DO3|DO2|DO1 440 +|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 441 +|RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1 320 320 321 -RO is for relay. ROx=1 close, ROx=0 alwaysopen.443 +* RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN. 322 322 ))) 323 323 324 -* FIRST: Indicate this is the first packet after join network. 325 -* DO is for reverse digital output. DOx=1: output low, DOx=0:highorfloat.446 +* FIRST: Indicates that this is the first packet after joining the network. 447 +* DO is for reverse digital output. DOx=1: LOW, DOx=0: HIGH or FLOATING. 326 326 327 327 ((( 328 -(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L .**450 +(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L** 329 329 330 330 331 331 ))) 332 332 333 333 ((( 334 -**To usecountingmode,pleaserun:**456 +**To activate this mode, run the following AT commands:** 335 335 ))) 336 336 337 337 ((( ... ... @@ -352,24 +352,27 @@ 352 352 ((( 353 353 **For LT22222-L:** 354 354 355 -(% style="color:blue" %)**AT+TRIG1=0,100**(%%)** lowlevel,valid signal is 100ms) **477 +(% style="color:blue" %)**AT+TRIG1=0,100**(%%)** (sets the DI1 port to trigger on a LOW level. The valid signal duration is 100ms) ** 356 356 357 -(% style="color:blue" %)**AT+TRIG1=1,100**(%%)** highlevel,valid signal is 100ms479 +(% style="color:blue" %)**AT+TRIG1=1,100**(%%)** (sets the DI1 port to trigger on a HIGH level. The valid signal duration is 100ms) ** 358 358 359 -(% style="color:blue" %)**AT+TRIG2=0,100**(%%)** lowlevel,valid signal is 100ms) **481 +(% style="color:blue" %)**AT+TRIG2=0,100**(%%)** (sets the DI2 port to trigger on a LOW level. The valid signal duration is 100ms) ** 360 360 361 -(% style="color:blue" %)**AT+TRIG2=1,100**(%%)** highlevel,valid signal is 100ms483 +(% style="color:blue" %)**AT+TRIG2=1,100**(%%)** (sets the DI2 port to trigger on a HIGH level. The valid signal duration is 100ms) ** 362 362 363 -(% style="color:blue" %)**AT+SETCNT=1,60**(%%)** Set COUNT1 value to 60)**485 +(% style="color:blue" %)**AT+SETCNT=1,60**(%%)** (sets the COUNT1 value to 60)** 364 364 365 -(% style="color:blue" %)**AT+SETCNT=2,60**(%%)** Set COUNT2 value to 60)**487 +(% style="color:blue" %)**AT+SETCNT=2,60 **(%%)**(sets the COUNT2 value to 60)** 366 366 ))) 367 367 368 368 369 369 === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI === 370 370 493 +(% style="color:red" %)**Note: The maximum count depends on the bytes it is. 494 +The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 495 +It starts counting again when it reaches the maximum value.** 371 371 372 -**LT22222-L**: This mode the DI1 is used as a counting pin.497 +**LT22222-L**: In this mode, the DI1 is used as a counting pin. 373 373 374 374 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 375 375 |(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1** ... ... @@ -380,24 +380,24 @@ 380 380 )))|DIDORO*|Reserve|MOD 381 381 382 382 ((( 383 -(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination forRO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1.Totally1bytesas below508 +(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below. 384 384 385 385 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 386 -|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 387 -|RO1|RO2|FIRST|Reserve|Reserve|DO3|DO2|DO1 511 +|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 512 +|RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1 388 388 ))) 389 389 390 -* RO is for relay. ROx=1 391 -* FIRST: Indicate this is the first packet after join network. 392 -* DO is for reverse digital output. DOx=1: output low, DOx=0: high or float. 515 +* RO is for the relay. ROx=1: closed, ROx=0 always open. 516 +* FIRST: Indicates that this is the first packet after joining the network. 517 +* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating. 393 393 394 394 ((( 395 -(% style="color:red" %)**Note: DO3 is not valid for LT-22222-L.** 520 +(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L.** 396 396 ))) 397 397 398 398 399 399 ((( 400 -**To usecountingmode,pleaserun:**525 +**To activate this mode, run the following AT commands:** 401 401 ))) 402 402 403 403 ((( ... ... @@ -410,19 +410,25 @@ 410 410 ))) 411 411 412 412 ((( 413 -Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]. 538 +AT Commands for counting: 539 + 540 +The AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s. 414 414 ))) 415 415 416 416 417 417 === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting === 418 418 546 +(% style="color:red" %)**Note:The maximum count depends on the bytes it is. 547 +The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 548 +It starts counting again when it reaches the maximum value.** 419 419 550 + 420 420 ((( 421 -**LT22222-L**: This mode the DI1 is used as a counting pin.552 +**LT22222-L**: In this mode, the DI1 is used as a counting pin. 422 422 ))) 423 423 424 424 ((( 425 -The AVI1 is also used for counting. AVI1 is usedtomonitor the voltage.Itwillcheck thevoltage**every 60s**,if voltage is higher or lower than VOLMAX mV, the AVI1Countingincrease 1,so AVI1 countingcanbe used to measure a machine working hour.556 +The AVI1 is also used for counting. It monitors the voltage and checks it every **60 seconds**. If the voltage is higher or lower than VOLMAX mV, the AVI1 count increases by 1, allowing AVI1 counting to be used to measure a machine's working hours. 426 426 427 427 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 428 428 |(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1** ... ... @@ -432,25 +432,25 @@ 432 432 ))) 433 433 434 434 ((( 435 -(% style="color:#4f81bd" %)**DIDORO **(%%)is a combination forRO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1.Totally1bytesas below566 +(% style="color:#4f81bd" %)**DIDORO **(%%)is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below. 436 436 437 437 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 438 -|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 439 -|RO1|RO2|FIRST|Reserve|Reserve|DO3|DO2|DO1 569 +|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 570 +|RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1 440 440 ))) 441 441 442 -* RO is for relay. ROx=1 443 -* FIRST: Indicate this is the first packet after join network. 444 -* DO is for reverse digital output. DOx=1: output low, DOx=0: high or float. 573 +* RO is for the relay. ROx=1: closed, ROx=0 always open. 574 +* FIRST: Indicates that this is the first packet after joining the network. 575 +* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating. 445 445 446 446 ((( 447 -(% style="color:red" %)**Note: DO3 is not valid for LT-22222-L.** 578 +(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L.** 448 448 449 449 450 450 ))) 451 451 452 452 ((( 453 -**To use this mode,pleaserun:**584 +**To activate this mode, run the following AT commands:** 454 454 ))) 455 455 456 456 ((( ... ... @@ -463,27 +463,31 @@ 463 463 ))) 464 464 465 465 ((( 466 - OtherAT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]].597 +AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s. 467 467 ))) 468 468 469 469 ((( 470 -** Plusbelow command for AVI1 Counting:**601 +**In addition to that, below are the commands for AVI1 Counting:** 471 471 472 -(% style="color:blue" %)**AT+SETCNT=3,60**(%%)** set AVI Count to 60)**603 +(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)** 473 473 474 -(% style="color:blue" %)**AT+VOLMAX=20000**(%%)** 605 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 475 475 476 -(% style="color:blue" %)**AT+VOLMAX=20000,0**(%%)** 607 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)** 477 477 478 -(% style="color:blue" %)**AT+VOLMAX=20000,1**(%%)** 609 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 479 479 ))) 480 480 481 481 482 482 === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI === 483 483 615 +(% style="color:red" %)**Note:The maximum count depends on the bytes it is. 616 +The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 617 +It starts counting again when it reaches the maximum value.** 484 484 485 -**LT22222-L**: This mode the DI1 is used as a counting pin. 486 486 620 +**LT22222-L**: In this mode, the DI1 is used as a counting pin. 621 + 487 487 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 488 488 |(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1** 489 489 |Value|((( ... ... @@ -497,25 +497,25 @@ 497 497 )))|MOD 498 498 499 499 ((( 500 -(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination forRO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1.Totally1bytesas below635 +(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below. 501 501 502 502 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 503 -|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 638 +|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 504 504 |RO1|RO2|FIRST|Reserve|Reserve|DO3|DO2|DO1 505 505 ))) 506 506 507 -* RO is for relay. ROx=1 508 -* FIRST: Indicate this is the first packet after join network. 642 +* RO is for the relay. ROx=1: closed, ROx=0 always open. 643 +* FIRST: Indicates that this is the first packet after joining the network. 509 509 * ((( 510 -DO is for reverse digital output. DOx=1: output low, DOx=0: high or float. 645 +DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating. 511 511 ))) 512 512 513 513 ((( 514 -(% style="color:red" %)**Note: DO3 is not valid for LT-22222-L.** 649 +(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L.** 515 515 ))) 516 516 517 517 ((( 518 -**To use this mode,pleaserun:**653 +**To activate this mode, run the following AT commands:** 519 519 ))) 520 520 521 521 ((( ... ... @@ -528,29 +528,33 @@ 528 528 ))) 529 529 530 530 ((( 531 -Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]. 666 +Other AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s. 532 532 ))) 533 533 534 534 535 -=== 3.3.6 AT+ADDMOD~=6 .(Trigger Mode, Optional) ===670 +=== 3.3.6 AT+ADDMOD~=6 (Trigger Mode, Optional) === 536 536 537 537 538 -(% style="color:#4f81bd" %)**This mode is anoptionalmode for trigger purpose. It can runtogetherwith other mode.**673 +(% style="color:#4f81bd" %)**This mode is optional and intended for trigger purposes. It can operate __alongside__ with other modes.** 539 539 540 -For example, if u serhasconfiguredbelow commands:675 +For example, if you configure the following commands: 541 541 542 -* **AT+MOD=1 ** **~-~->** Thenormal working mode543 -* **AT+ADDMOD6=1** **~-~->** Enable trigger 677 +* **AT+MOD=1 ** **~-~->** Sets the default working mode 678 +* **AT+ADDMOD6=1** **~-~->** Enables trigger mode 544 544 545 -LT will keepmonitoringAV1/AV2/AC1/AC2 every 5 seconds;LTwill send uplink packets in two cases:680 +The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. It will send uplink packets in two cases: 546 546 547 -1. Periodically uplink (Base on TDC time). Payload is same as the normal MOD (MOD 1 for above command). This uplink uses LoRaWAN (% style="color:#4f81bd" %)**unconfirmed**(%%) data type 548 -1. Trigger uplink when meet the trigger condition. LT will sent two packets in this case, the first uplink use payload specify in this mod (mod=6), the second packets use the normal mod payload(MOD=1 for above settings). Both Uplinks use LoRaWAN (% style="color:#4f81bd" %)**CONFIRMED data type.** 682 +1. Periodic uplink: Based on TDC time. The payload is the same as in normal mode (MOD=1 as set above). These are (% style="color:#4f81bd" %)**unconfirmed**(%%) uplinks. 683 +1. ((( 684 +Trigger uplink: sent when a trigger condition is met. In this case, LT will send two packets 549 549 550 -(% style="color:#037691" %)**AT Command to set Trigger Condition**: 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.** 688 +))) 551 551 690 +(% style="color:#037691" %)**AT Commands to set Trigger Conditions**: 552 552 553 -(% style="color:#4f81bd" %)**Trigger base on voltage**: 692 +(% style="color:#4f81bd" %)**Trigger based on voltage**: 554 554 555 555 Format: AT+AVLIM=<AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH> 556 556 ... ... @@ -557,27 +557,25 @@ 557 557 558 558 **Example:** 559 559 560 -AT+AVLIM=3000,6000,0,2000 If AVI1 voltage lower than 3vor higher than 6v.v, LT will trigger Uplink)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) 561 561 562 -AT+AVLIM=5000,0,0,0 If AVI1 voltage lower than 5V, triggeruplink,0 meansignore)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) 563 563 564 564 704 +(% style="color:#4f81bd" %)**Trigger based on current**: 565 565 566 -(% style="color:#4f81bd" %)**Trigger base on current**: 567 - 568 568 Format: AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH> 569 569 570 570 571 571 **Example:** 572 572 573 -AT+ACLIM=10000,15000,0,0 If ACI1voltage lower than 10mA or higher than 15mA, trigger an uplink)711 +AT+ACLIM=10000,15000,0,0 (triggers an uplink if AC1 current is lower than 10mA or higher than 15mA) 574 574 575 575 714 +(% style="color:#4f81bd" %)**Trigger based on DI status**: 576 576 577 - (%style="color:#4f81bd"%)**Triggerbaseon DI status**:716 +DI status triggers Flag. 578 578 579 -DI status trigger Flag. 580 - 581 581 Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG > 582 582 583 583 ... ... @@ -586,39 +586,38 @@ 586 586 AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 587 587 588 588 589 -(% style="color:#037691" %)**Downlink Command toset Trigger Condition:**726 +(% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:** 590 590 591 591 Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 592 592 593 593 Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 594 594 595 - AA: Code for this downlink Command: 732 + AA: Type Code for this downlink Command: 596 596 597 - xx: 0: Limit for AV1 and AV2; ,DI2 trigger enable/disable734 + xx: **0**: Limit for AV1 and AV2; **1**: limit for AC1 and AC2; **2**: DI1and DI2 trigger enable/disable. 598 598 599 - yy1 yy1: AC1 or AV1 lowlimit or DI1/DI2 trigger status.736 + yy1 yy1: AC1 or AV1 LOW limit or DI1/DI2 trigger status. 600 600 601 - yy2 yy2: AC1 or AV1 highlimit.738 + yy2 yy2: AC1 or AV1 HIGH limit. 602 602 603 - yy3 yy3: AC2 or AV2 lowlimit.740 + yy3 yy3: AC2 or AV2 LOW limit. 604 604 605 - Yy4 yy4: AC2 or AV2 highlimit.742 + Yy4 yy4: AC2 or AV2 HIGH limit. 606 606 607 607 608 -**Example1**: AA 00 13 88 00 00 00 00 00 00 745 +**Example 1**: AA 00 13 88 00 00 00 00 00 00 609 609 610 -Same as AT+AVLIM=5000,0,0,0 If AVI1 voltage lower than 5V, triggeruplink,0 meansignore)747 +Same as AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage is lower than 5V. Use 0s for parameters that are not in use) 611 611 612 612 613 -**Example2**: AA 02 01 00 750 +**Example 2**: AA 02 01 00 614 614 615 -Same as AT+ DTRI =1,0 752 +Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 616 616 617 617 618 - 619 619 (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:** 620 620 621 -MOD6 Payload payload757 +MOD6 Payload: total of 11 bytes 622 622 623 623 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 624 624 |(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:49px" %)**6**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1** ... ... @@ -632,10 +632,10 @@ 632 632 MOD(6) 633 633 ))) 634 634 635 -(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if trigger is set for this part. Totally 1byte as below 771 +(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below 636 636 637 637 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 638 -|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 774 +|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 639 639 |((( 640 640 AV1_LOW 641 641 )))|((( ... ... @@ -654,17 +654,17 @@ 654 654 AC2_HIGH 655 655 ))) 656 656 657 -* Each bit sshows if the corresponding trigger has been configured.793 +* Each bit shows if the corresponding trigger has been configured. 658 658 659 659 **Example:** 660 660 661 -10100000: Means the system has configure to use the trigger: A C1_LOW and AV2_LOW797 +10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW 662 662 663 663 664 -(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1byte as below 800 +(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below 665 665 666 666 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 667 -|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 803 +|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 668 668 |((( 669 669 AV1_LOW 670 670 )))|((( ... ... @@ -683,20 +683,20 @@ 683 683 AC2_HIGH 684 684 ))) 685 685 686 -* Each bit sshows which status has been trigger on this uplink.822 +* Each bit shows which status has been triggered on this uplink. 687 687 688 688 **Example:** 689 689 690 -10000000: Means this p acketis trigger by AC1_LOW.Means voltage too low.826 +10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low. 691 691 692 692 693 693 (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below 694 694 695 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width: 515px" %)696 -|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 697 -|N/A|N/A|N/A|N/A|DI2_STATUS|DI2_FLAG|DI1_STATUS|DI1_FLAG 831 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:674px" %) 832 +|(% 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** 833 +|(% 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 698 698 699 -* Each bits shows which status has been trigger on this uplink. 835 +* Each bits shows which status has been triggered on this uplink. 700 700 701 701 **Example:** 702 702 ... ... @@ -723,230 +723,482 @@ 723 723 ))) 724 724 725 725 726 -== 3.4 Configure LT via AT or Downlink == 862 +== 3.4 Configure LT-22222-L via AT Commands or Downlinks == 727 727 728 - 729 729 ((( 730 - Usercan configure LT I/O Controller via AT Commands or LoRaWAN DownlinkCommands865 +You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks. 731 731 ))) 732 732 733 733 ((( 734 734 ((( 735 -There are two kinds ofCommands:870 +There are two tytes of commands: 736 736 ))) 737 737 ))) 738 738 739 -* (% style="color:blue" %)**Common Commands**(%%):They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.5.4, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]874 +* (% style="color:blue" %)**Common commands**(%%): 740 740 741 -* (% style="color:blue" %)**Sensor RelatedCommands**(%%):These commands are special designed for LT-22222-L. User can see these commands below:876 +* (% style="color:blue" %)**Sensor-related commands**(%%): 742 742 743 -=== 3.4.1 Common Commands ===878 +=== 3.4.1 Common commands === 744 744 745 - 746 746 ((( 747 -The yshouldbe available for each of DraginoSensors,such as:changeuplink interval,reset device. For firmware v1.5.4, usercan findwhat common commandsit supports:881 +These are available for each sensors and include actions such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]s. 748 748 ))) 749 749 884 +=== 3.4.2 Sensor-related commands === 750 750 751 - ===3.4.2Sensorrelated commands===886 +These commands are specially designed for the LT-22222-L. Commands can be sent to the device using options such as an AT command or a LoRaWAN downlink payload. 752 752 888 + 753 753 ==== 3.4.2.1 Set Transmit Interval ==== 754 754 891 +Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes. 755 755 756 - Setdevice uplink interval.893 +(% style="color:#037691" %)**AT command** 757 757 758 -* (% style="color:#037691" %)**AT Command:** 895 +(% border="2" style="width:500px" %) 896 +|**Command**|AT+TDC=<time> 897 +|**Response**| 898 +|**Parameters**|**time** : uplink interval is in milliseconds 899 +|**Example**|((( 900 +AT+TDC=30000 759 759 760 -(% style="color:blue" %)**AT+TDC=N ** 902 +Sets the uplink interval to 30,000 milliseconds (30 seconds) 903 +))) 761 761 905 +(% style="color:#037691" %)**Downlink payload** 762 762 763 -**Example: **AT+TDC=30000. Means set interval to 30 seconds 907 +(% border="2" style="width:500px" %) 908 +|**Payload**|((( 909 +<prefix><time> 910 +))) 911 +|**Parameters**|((( 912 +**prefix** : 0x01 764 764 914 +**time** : uplink interval is in milliseconds, represented by 3 bytes in hexadecimal. 915 +))) 916 +|**Example**|((( 917 +01 **00 75 30** 765 765 766 - * (%style="color:#037691"%)**DownlinkPayload(prefix0x01):**919 +Sets the uplink interval to 30,000 milliseconds (30 seconds) 767 767 768 - (% style="color:blue"%)**0x01aa bb cc **(%%)**~/~/Same as AT+TDC=0x(aabb cc)**921 +Conversion: 30000 (dec) = 00 75 30 (hex) 769 769 923 +See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]] 924 +))) 770 770 926 +==== 3.4.2.2 Set the Working Mode (AT+MOD) ==== 771 771 772 - ==== 3.4.2.2SetWorkMode(AT+MOD) ====928 +Sets the working mode. 773 773 930 +(% style="color:#037691" %)**AT command** 774 774 775 -Set work mode. 932 +(% border="2" style="width:500px" %) 933 +|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE=<working_mode> 934 +|(% style="width:97px" %)**Response**|(% style="width:413px" %) 935 +|(% style="width:97px" %)**Parameters**|(% style="width:413px" %)((( 936 +**working_mode** : 776 776 777 - *(%style="color:#037691"%)**AT Command:**(%%) (% style="color:blue"%)**AT+MOD=N**938 +1 = (Default mode/factory set): 2ACI + 2AVI + DI + DO + RO 778 778 779 - **Example**:AT+MOD=2.Set work mode toDouble DIcountingmode940 +2 = Double DI Counting + DO + RO 780 780 781 - *(%style="color:#037691"%)**DownlinkPayload(prefix0x0A):**942 +3 = Single DI Counting + 2 x ACI + DO + RO 782 782 783 - (%style="color:blue"%)**0x0Aaa**(%%)****~/~/ SameasAT+MOD=aa944 +4 = Single DI Counting + 1 x Voltage Counting + DO + RO 784 784 946 +5 = Single DI Counting + 2 x AVI + 1 x ACI + DO + RO 785 785 948 +6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5 949 +))) 950 +|(% style="width:97px" %)**Example**|(% style="width:413px" %)((( 951 +AT+MOD=2 786 786 787 -==== 3.4.2.3 Poll an uplink ==== 953 +Sets the device to working mode 2 (Double DI Counting + DO + RO) 954 +))) 788 788 956 +(% class="wikigeneratedid" %) 957 +(% style="color:#037691" %)**Downlink payload** 789 789 790 -* (% style="color:#037691" %)**AT Command:**(%%) There is no AT Command to poll uplink 959 +(% border="2" style="width:500px" %) 960 +|(% style="width:98px" %)**Payload**|(% style="width:400px" %)<prefix><working_mode> 961 +|(% style="width:98px" %)**Parameters**|(% style="width:400px" %)((( 962 +**prefix** : 0x0A 791 791 792 -* (% style="color:#037691" %)**Downlink Payload (prefix 0x08):** 964 +**working_mode** : Working mode, represented by 1 byte in hexadecimal. 965 +))) 966 +|(% style="width:98px" %)**Example**|(% style="width:400px" %)((( 967 +0A **02** 793 793 794 -(% style="color:blue" %)**0x08 FF **(%%)** **~/~/ Poll an uplink 969 +Sets the device to working mode 2 (Double DI Counting + DO + RO) 970 +))) 795 795 796 - **Example**:0x08FF,ask device tosendanUplink972 +==== 3.4.2.3 Poll an uplink ==== 797 797 974 +Requests an uplink from LT-22222-L. 798 798 976 +(% style="color:#037691" %)**AT command** 799 799 800 - ====3.4.2.4EnableTriggerMode====978 +There is no AT Command to request an uplink from LT-22222-L 801 801 980 +(% style="color:#037691" %)**Downlink payload** 802 802 803 -Use of trigger mode, please check [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 982 +(% border="2" style="width:500px" %) 983 +|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF 984 +|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08 985 +|(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 986 +08 FF 804 804 805 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0** 988 +Requests an uplink from LT-22222-L. 989 +))) 806 806 807 - (% style="color:red"%)**1:**(%%)Enable Trigger Mode991 +==== 3.4.2.4 Enable/Disable Trigger Mode ==== 808 808 809 - (%style="color:red"%)**0:**(%%)Disable Trigger993 +Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]). 810 810 995 +(% style="color:#037691" %)**AT Command** 811 811 812 -* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):** 997 +(% border="2" style="width:500px" %) 998 +|(% style="width:95px" %)**Command**|(% style="width:403px" %)AT+ADDMOD6=<enable/disable trigger_mode> 999 +|(% style="width:95px" %)**Response**|(% style="width:403px" %) 1000 +|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)((( 1001 +**enable/disable trigger_mode** : 813 813 814 - (%style="color:blue"%)**0x0A06 aa **(%%) ~/~/ Sameas AT+ADDMOD6=aa1003 +1 = enable trigger mode 815 815 1005 +0 = disable trigger mode 1006 +))) 1007 +|(% style="width:95px" %)**Example**|(% style="width:403px" %)((( 1008 +AT+ADDMOD6=1 816 816 1010 +Enable trigger mode for the current working mode 1011 +))) 817 817 818 - ====3.4.2.5Poll trigger settings====1013 +(% style="color:#037691" %)**Downlink payload** 819 819 1015 +(% border="2" style="width:500px" %) 1016 +|(% style="width:97px" %)**Payload**|(% style="width:401px" %)<prefix><enable/disable trigger_mode> 1017 +|(% style="width:97px" %)**Parameters**|(% style="width:401px" %)((( 1018 +**prefix** : 0x0A 06 (two bytes in hexadecimal) 820 820 821 -Poll trigger settings 1020 +**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal. 1021 +))) 1022 +|(% style="width:97px" %)**Example**|(% style="width:401px" %)((( 1023 +0A 06 **01** 822 822 823 -* (% style="color:#037691" %)**AT Command:** 1025 +Enable trigger mode for the current working mode 1026 +))) 824 824 1028 +==== 3.4.2.5 Poll trigger settings ==== 1029 + 1030 +Polls the trigger settings. 1031 + 1032 +(% style="color:#037691" %)**AT Command:** 1033 + 825 825 There is no AT Command for this feature. 826 826 827 - *(% style="color:#037691" %)**Downlink Payload(prefix 0x AB 06):**1036 +(% style="color:#037691" %)**Downlink Payload** 828 828 829 -(% style="color:blue" %)**0xAB 06 ** (%%) ~/~/ Poll trigger settings, device will uplink trigger settings once receive this command 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 830 830 1044 +Uplinks the trigger settings. 1045 +))) 831 831 1047 +==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ==== 832 832 833 - ==== 3.4.2.6Enable/Disable DI1/DI2/DI3 as trigger====1049 +Enable or disable DI1/DI2/DI3 as a trigger. 834 834 1051 +(% style="color:#037691" %)**AT Command** 835 835 836 -Enable Disable DI1/DI2/DI2 as trigger, 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:** 837 837 838 - *(% style="color:#037691"%)**AT Command:**(%%) (% style="color:blue"%)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,<DI2_TIRGGER_FlAG >**1059 +1 = enable DI1 trigger 839 839 840 - **Example:** AT+DTRI=1,0(Enable DI1 trigger /disable DI2trigger)1061 +0 = disable DI1 trigger 841 841 1063 +**DI2 _trigger** 842 842 843 - *(% style="color:#037691"%)**Downlink Payload (prefix0xAA 02):**1065 +1 = enable DI2 trigger 844 844 845 -(% style="color:blue" %)**0xAA 02 aa bb ** (%%) ~/~/ Same as AT+DTRI=aa,bb 1067 +0 = disable DI2 trigger 1068 +))) 1069 +|(% style="width:98px" %)**Example**|(% style="width:400px" %)((( 1070 +AT+DTRI=1,0 846 846 1072 +Enable DI1 trigger, disable DI2 trigger 1073 +))) 847 847 1075 +(% class="wikigeneratedid" %) 1076 +(% style="color:#037691" %)**Downlink Payload** 848 848 849 -==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger ==== 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) 850 850 1083 +**DI1_trigger:** 851 851 852 - SetDI1or DI3(for LT-33222-L)trigger.1085 +1 = enable DI1 trigger, represented by 1 byte in hexadecimal. 853 853 854 - *(%style="color:#037691"%)**AT Command:**(%%)(%style="color:blue"%)**AT+TRIG1=a,b**1087 +0 = disable DI1 trigger, represented by 1 byte in hexadecimal. 855 855 856 - (% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge,2:falling andraisingedge(forMOD=1).1089 +**DI2 _trigger** 857 857 858 - (%style="color:red"%)**b:**(%%)delayming.1091 +1 = enable DI2 trigger, represented by 1 byte in hexadecimal. 859 859 860 -**Example:** AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms ) 1093 +0 = disable DI2 trigger, represented by 1 byte in hexadecimal. 1094 +))) 1095 +|(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 1096 +AA 02 **01 00** 861 861 1098 +Enable DI1 trigger, disable DI2 trigger 1099 +))) 862 862 863 - *(%style="color:#037691"%)**DownlinkPayload(prefix0x09 01 ):**1101 +==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ==== 864 864 865 - (% style="color:blue"%)**0x09 01aabbcc **(%%)~/~/ same asAT+TRIG1=aa,0x(bbcc)1103 +Sets DI1 or DI3 (for LT-33222-L) as a trigger. 866 866 867 867 1106 +(% style="color:#037691" %)**AT Command** 868 868 869 -==== 3.4.2.8 Trigger2 – Set DI2 as trigger ==== 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). 870 870 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 871 871 872 -Set DI2 trigger. 1119 +Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms. 1120 +))) 873 873 874 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b** 1122 +(% class="wikigeneratedid" %) 1123 +(% style="color:#037691" %)**Downlink Payload** 875 875 876 -(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1). 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) 877 877 878 - (% style="color:red" %)**b:**(%%)delaytiming.1130 +**interrupt_mode** : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal. 879 879 880 -**Example:** AT+TRIG2=0,100(set DI1 port to trigger on low level, valid signal is 100ms ) 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** 881 881 1137 +Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms. 1138 +))) 882 882 883 - *(%style="color:#037691"%)**DownlinkPayload(prefix0x09 02 ):**1140 +==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ==== 884 884 885 - (% style="color:blue"%)**0x09 02 aa bb cc ** (%%)~/~/sameasAT+TRIG2=aa,0x(bb cc)1142 +Sets DI2 as a trigger. 886 886 887 887 1145 +(% style="color:#037691" %)**AT Command** 888 888 889 -==== 3.4.2.9 Trigger – Set AC (current) as trigger ==== 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). 890 890 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 891 891 892 -Set current trigger , base on AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1158 +Set the DI1 port to trigger on a falling edge; the valid signal duration is 100 ms. 1159 +))) 893 893 894 - *(% style="color:#037691" %)**AT Command:**(%%) (%style="color:blue" %)**AT+ACLIM**1161 +(% style="color:#037691" %)**Downlink Payload** 895 895 896 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 01 )** 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) 897 897 898 - (% style="color:blue"%)**0xAA 01aabbccddeeffgghh ** (%%) ~/~/ sameasAT+ACLIM See [[triggermode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]1168 +**interrupt_mode **: 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal. 899 899 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** 900 900 1174 +==== ==== 901 901 1176 +==== 3.4.2.9 Trigger – Set AC (current) as a trigger ==== 1177 + 1178 +Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1179 + 1180 +(% style="color:#037691" %)**AT Command** 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 1189 + 1190 +**AC1_LIMIT_HIGH **: higher limit of the current to be checked 1191 + 1192 +**AC2_LIMIT_HIGH **: lower limit of the current to be checked 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 + 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 + 902 902 ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ==== 903 903 1227 +Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 904 904 905 - Setcurrent trigger , base on AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]1229 +(% style="color:#037691" %)**AT Command** 906 906 907 -* (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+AVLIM **(%%)** See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]** 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 908 908 909 -* (%style="color:#037691"%)**DownlinkPayload(prefix0xAA00)**1237 +**AC1_LIMIT_HIGH **: higher limit of the current to be checked 910 910 911 - (% style="color:blue" %)**0xAA00 aa bb cc dd ee ff gg hh**(%%) ~/~/ sameasAT+AVLIM See[[triggermode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]1239 +**AC2_LIMIT_HIGH **: lower limit of the current to be checked 912 912 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 913 913 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"]] 914 914 915 - ====3.4.2.11Trigger – Set minimum interval====1250 +(% style="color:#037691" %)**Downlink Payload** 916 916 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) 917 917 918 - SetAVandAC triggerminimuminterval,systemwon'tresponsetothesecond triggerwithinthisset timeafter thefirst trigger.1257 +**AV1_LIMIT_LOW** : lower limit of the voltage to be checked, two bytes in hexadecimal 919 919 920 -* (% style="color:#037691" %)**ATCommand**(%%):(%style="color:blue"%)**AT+ATDC=5 ** ~/~/ (%%)Device won'tresponsethesecondtriggerwithin5 minuteafterthefirsttrigger.1259 +**AV1_LIMIT_HIGH **: higher limit of the voltage to be checked, two bytes in hexadecimal 921 921 922 -* (% style="color:#037691" %)**DownlinkPayload(prefix0xAC )**1261 +**AV2_LIMIT_HIGH **: lower limit of the voltage to be checked, two bytes in hexadecimal 923 923 924 -(% style="color:blue" %)**0x AC aa bb **(%%) ~/~/ same as AT+ATDC=0x(aa bb) . Unit (min) 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** 925 925 926 -((( 927 -(% style="color:red" %)**Note: ATDC setting must be more than 5min** 1268 +Triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V. 928 928 ))) 1270 +|(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 929 929 1272 +==== 3.4.2.11 Trigger – Set minimum interval ==== 930 930 1274 +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. 931 931 1276 +(% style="color:#037691" %)**AT Command** 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 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.** 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) 1299 +))) 1300 +|(% style="width:112px" %)**Example**|(% style="width:386px" %)((( 1301 +AC **00 05** 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 + 932 932 ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ==== 933 933 1309 +Controls the digital outputs DO1, DO2, and DO3 934 934 935 - *(% style="color:#037691" %)**AT Command**1311 +(% style="color:#037691" %)**AT Command** 936 936 937 -There is no AT Command to control Digital Output 1313 +There is no AT Command to control the Digital Output. 938 938 939 939 940 - *(% style="color:#037691" %)**Downlink Payload(prefix 0x02)**1316 +(% style="color:#037691" %)**Downlink Payload** 941 941 942 -(% style="color:blue" %)**0x02 aa bb cc ** (%%)~/~/ Set DO1/DO2/DO3 output 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) 943 943 944 -((( 945 -If payload = 0x02010001, while there is load between V+ and DOx, it means set DO1 to low, DO2 to high and DO3 to low. 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) 946 946 ))) 1329 +|(% style="width:115px" %)**Examples**|(% style="width:383px" %)((( 1330 +02 **01 00 01** 947 947 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 + 948 948 ((( 949 -01: Low, 00: High 1337 +01: Low, 00: High, 11: No action 950 950 951 951 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 952 952 |(% 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** ... ... @@ -956,15 +956,18 @@ 956 956 ))) 957 957 958 958 ((( 959 -(% style="color:red" %)**Note: For LT-22222-L, there is no DO3, the last byte can use any value.** 1347 +((( 1348 +(% style="color:red" %)**Note: For the LT-22222-L, there is no DO3; the last byte can have any value.** 960 960 ))) 961 961 962 962 ((( 963 -(% style="color:red" %)** Device will upload a packet if downlink code executes successfully.**1352 +(% style="color:red" %)**The device will upload a packet if downlink code executes successfully.** 964 964 ))) 1354 +))) 1355 +))) 965 965 1357 +==== ==== 966 966 967 - 968 968 ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ==== 969 969 970 970 ... ... @@ -989,7 +989,7 @@ 989 989 00: DO pins will change to an inverter state after timeout 990 990 991 991 992 -(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port sstatus:1383 +(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status: 993 993 994 994 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 995 995 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -997,7 +997,7 @@ 997 997 |0x00|DO1 set to high 998 998 |0x11|DO1 NO Action 999 999 1000 -(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port sstatus:1391 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status: 1001 1001 1002 1002 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1003 1003 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1005,7 +1005,7 @@ 1005 1005 |0x00|DO2 set to high 1006 1006 |0x11|DO2 NO Action 1007 1007 1008 -(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port sstatus:1399 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status: 1009 1009 1010 1010 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1011 1011 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1013,16 +1013,16 @@ 1013 1013 |0x00|DO3 set to high 1014 1014 |0x11|DO3 NO Action 1015 1015 1016 -(% style="color:#4f81bd" %)**Sixth andSeventhandEighth and Ninth Byte**:(%%) Latching time.Unit: ms1407 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms) 1017 1017 1018 1018 1019 1019 (% style="color:red" %)**Note: ** 1020 1020 1021 - Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes1412 + Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes 1022 1022 1023 - Before Firmwre v1.6.0 the latch time only suport 2 bytes.1414 + Before firmware v1.6.0, the latch time only supported 2 bytes. 1024 1024 1025 -(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1416 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.** 1026 1026 1027 1027 1028 1028 **Example payload:** ... ... @@ -1029,22 +1029,21 @@ 1029 1029 1030 1030 **~1. A9 01 01 01 01 07 D0** 1031 1031 1032 -DO1 pin &DO2 pin&DO3 pin will be set toLow, last 2 seconds, thenchangebackto original state.1423 +DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state. 1033 1033 1034 1034 **2. A9 01 00 01 11 07 D0** 1035 1035 1036 -DO1 pin set high, DO2 pin set low, DO3 pin no action ,last 2 seconds,thenchangebackto original state.1427 +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. 1037 1037 1038 1038 **3. A9 00 00 00 00 07 D0** 1039 1039 1040 -DO1 pin &DO2 pin&DO3 pin will be set to high, last 2 seconds, thenbothchange to low.1431 +DO1 pin, DO2 pin, and DO3 pin will be set to high, last for 2 seconds, and then all change to low. 1041 1041 1042 1042 **4. A9 00 11 01 00 07 D0** 1043 1043 1044 -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 low1435 +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. 1045 1045 1046 1046 1047 - 1048 1048 ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ==== 1049 1049 1050 1050 ... ... @@ -1059,7 +1059,7 @@ 1059 1059 1060 1060 1061 1061 ((( 1062 -If payload =0x030100, it means set RO1 to close and RO2 to open.1452 +If payload is 0x030100, it means setting RO1 to close and RO2 to open. 1063 1063 ))) 1064 1064 1065 1065 ((( ... ... @@ -1080,9 +1080,9 @@ 1080 1080 (% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1081 1081 1082 1082 1083 - 1084 1084 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== 1085 1085 1475 +Controls the relay output time. 1086 1086 1087 1087 * (% style="color:#037691" %)**AT Command:** 1088 1088 ... ... @@ -1094,15 +1094,15 @@ 1094 1094 (% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set RO1/RO2 relay with time control 1095 1095 1096 1096 1097 -This is to control the relay output time of relay. Include four bytes:1487 +This is to control the relay output time. It includes four bytes: 1098 1098 1099 1099 (% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05) 1100 1100 1101 1101 (% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode 1102 1102 1103 -01: Relays will change back to original state after timeout. 1493 +01: Relays will change back to their original state after timeout. 1104 1104 1105 -00: Relays will change to aninverter state after timeout1495 +00: Relays will change to the inverter state after timeout. 1106 1106 1107 1107 1108 1108 (% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status: ... ... @@ -1115,12 +1115,12 @@ 1115 1115 1116 1116 (% style="color:red" %)**Note:** 1117 1117 1118 - Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes1508 + Since firmware v1.6.0, the latch time supports both 4 bytes and 2 bytes. 1119 1119 1120 - Before Firmwre v1.6.0 the latch time only suport 2 bytes.1510 + Before firmware v1.6.0, the latch time only supported 2 bytes. 1121 1121 1122 1122 1123 -(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1513 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.** 1124 1124 1125 1125 1126 1126 **Example payload:** ... ... @@ -1127,19 +1127,19 @@ 1127 1127 1128 1128 **~1. 05 01 11 07 D0** 1129 1129 1130 -Relay1 and Relay changebackto original state.1520 +Relay1 and Relay2 will be set to NC, lasting 2 seconds, then revert to their original state 1131 1131 1132 1132 **2. 05 01 10 07 D0** 1133 1133 1134 -Relay1 will change to NC, Relay2 will change to NO, last 2 seconds, then both changebackto original state.1524 +Relay1 will change to NC, Relay2 will change to NO, lasting 2 seconds, then both will revert to their original state. 1135 1135 1136 1136 **3. 05 00 01 07 D0** 1137 1137 1138 -Relay1 will change to NO, Relay2 will change to NC, last 2 seconds, then relay change to NC,Relay2 change to NO.1528 +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. 1139 1139 1140 1140 **4. 05 00 00 07 D0** 1141 1141 1142 -Relay &relay2 will change to NO, last 2 seconds, then both change to NC.1532 +Relay1 and Relay2 will change to NO, lasting 2 seconds, then both will change to NC. 1143 1143 1144 1144 1145 1145 ... ... @@ -1146,7 +1146,7 @@ 1146 1146 ==== 3.4.2.16 Counting ~-~- Voltage threshold counting ==== 1147 1147 1148 1148 1149 -When voltage exceed the threshold, count. F eature see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]1539 +When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1150 1150 1151 1151 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1152 1152 ... ... @@ -1155,15 +1155,76 @@ 1155 1155 (% style="color:blue" %)**0xA5 aa bb cc ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc 1156 1156 1157 1157 1548 +(% style="color:#037691" %)**AT Command** 1158 1158 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 + 1159 1159 ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ==== 1160 1160 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. 1161 1161 1162 1162 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) ** 1163 1163 1164 1164 (% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count 1165 1165 1166 -(% style="color:red" %)**bb cc dd ee: **(%%)number to be set 1617 +(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set 1167 1167 1168 1168 1169 1169 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):** ... ... @@ -1171,12 +1171,55 @@ 1171 1171 (% style="color:blue" %)**0x A8 aa bb cc dd ee ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee) 1172 1172 1173 1173 1625 +(% style="color:#037691" %)**AT Command** 1174 1174 1175 -==== 3.4.2.18 Counting ~-~- Clear Counting ==== 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** : 1176 1176 1633 +1: COUNT1 1177 1177 1178 - Clearcounting for counting mode1635 +2: COUNT2 1179 1179 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 +==== 3.4.2.18 Counting ~-~- Clear Counting ==== 1671 + 1672 +This feature clears the counting in counting mode. 1673 + 1180 1180 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT **(%%) ~/~/ clear all counting 1181 1181 1182 1182 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):** ... ... @@ -1183,14 +1183,30 @@ 1183 1183 1184 1184 (% style="color:blue" %)**0x A6 01 ** (%%)~/~/ clear all counting 1185 1185 1680 +(% style="color:#037691" %)**AT Command** 1186 1186 1682 +(% border="2" style="width:500px" %) 1683 +|(% style="width:142px" %)**Command**|(% style="width:356px" %)AT+CLRCOUNT 1684 +|(% style="width:142px" %)**Response**|(% style="width:356px" %)- 1187 1187 1188 - ====3.4.2.19Counting~-~- Change counting mode save time ====1686 +(% style="color:#037691" %)**Downlink Payload** 1189 1189 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) 1190 1190 1693 +clear? : 01 (hex) 1694 +))) 1695 +|(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01** 1696 + 1697 +==== 3.4.2.19 Counting ~-~- Change counting mode to save time ==== 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 + 1191 1191 * (% style="color:#037691" %)**AT Command:** 1192 1192 1193 -(% style="color:blue" %)**AT+COUTIME=60 **(%%)~/~/ Device will save the counting result in internal flash every 60 seconds. (min value: 30)1703 +(% 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) 1194 1194 1195 1195 1196 1196 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):** ... ... @@ -1198,7 +1198,7 @@ 1198 1198 (% style="color:blue" %)**0x A7 aa bb cc ** (%%)~/~/ same as AT+COUTIME =aa bb cc, 1199 1199 1200 1200 ((( 1201 - range: aa bb cc:0 to 16777215, (unit:second)1711 +Range: aa bb cc:0 to 16777215, (unit: seconds) 1202 1202 ))) 1203 1203 1204 1204 ... ... @@ -1205,12 +1205,13 @@ 1205 1205 1206 1206 ==== 3.4.2.20 Reset save RO DO state ==== 1207 1207 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. 1208 1208 1209 1209 * (% style="color:#037691" %)**AT Command:** 1210 1210 1211 1211 (% style="color:blue" %)**AT+RODORESET=1 **(%%)~/~/ RODO will close when the device joining the network. (default) 1212 1212 1213 -(% 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.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 will not change when the device reconnects to the network. 1214 1214 1215 1215 1216 1216 * (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):** ... ... @@ -1221,6 +1221,7 @@ 1221 1221 1222 1222 ==== 3.4.2.21 Encrypted payload ==== 1223 1223 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. 1224 1224 1225 1225 * (% style="color:#037691" %)**AT Command:** 1226 1226 ... ... @@ -1235,9 +1235,9 @@ 1235 1235 1236 1236 * (% style="color:#037691" %)**AT Command:** 1237 1237 1238 -(% style="color:blue" %)**AT+GETSENSORVALUE=0 **(%%)~/~/ The serial port gets the reading of the current sensor1750 +(% style="color:blue" %)**AT+GETSENSORVALUE=0 **(%%)~/~/ The serial port retrieves the reading of the current sensor. 1239 1239 1240 -(% style="color:blue" %)**AT+GETSENSORVALUE=1 **(%%)~/~/ The serial port gets the current sensor reading and uploads it.1752 +(% style="color:blue" %)**AT+GETSENSORVALUE=1 **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it. 1241 1241 1242 1242 1243 1243 ... ... @@ -1306,74 +1306,145 @@ 1306 1306 [[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-20220823173929-8.png?width=1205&height=76&rev=1.1||alt="image-20220823173929-8.png"]] 1307 1307 1308 1308 1309 -== 3.5 Integrat ewithMydevice==1821 +== 3.5 Integrating with ThingsEye.io == 1310 1310 1823 +The Things Stack application supports integration with ThingsEye.io. Once integrated, ThingsEye.io acts as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic. 1311 1311 1312 - Mydevicesprovidesa humanendlyinterface to show thesensor data, once wehave datainTTN, we can useMydevicesto connect to TTNand see the data in Mydevices.Below are the steps:1825 +=== 3.5.1 Configuring The Things Stack === 1313 1313 1314 -((( 1315 -(% style="color:blue" %)**Step 1**(%%): Be sure that your device is programmed and properly connected to the network at this time. 1316 -))) 1827 +We use The Things Stack Sandbox in this example: 1317 1317 1318 -((( 1319 -(% style="color:blue" %)**Step 2**(%%): To configure the Application to forward data to Mydevices you will need to add integration. To add the Mydevices integration, perform the following steps: 1829 +* In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added. 1830 +* Select **MQTT** under **Integrations** in the left menu. 1831 +* In the **Connection information **section, under **Connection credentials**, The Things Stack displays an auto-generated **username**. You can use it or provide a new one. 1832 +* Click the **Generate new API key** button to generate a password. You can view it by clicking on the **visibility toggle/eye** icon. The API key works as the password. 1320 1320 1321 - 1322 -))) 1834 +{{info}} 1835 +The username and password (API key) you created here are required in the next section. 1836 +{{/info}} 1323 1323 1324 -[[image: image-20220719105525-1.png||height="377" width="677"]]1838 +[[image:tts-mqtt-integration.png||height="625" width="1000"]] 1325 1325 1840 +=== 3.5.2 Configuring ThingsEye.io === 1326 1326 1842 +* Login to your [[ThingsEye.io >>https://thingseye.io]]account. 1843 +* Under the **Integrations center**, click **Integrations**. 1844 +* Click the **Add integration** button (the button with the **+** symbol). 1327 1327 1328 -[[image:i mage-20220719110247-2.png||height="388" width="683"]]1846 +[[image:thingseye-io-step-1.png||height="625" width="1000"]] 1329 1329 1330 1330 1331 - (%style="color:blue"%)**Step 3**(%%): Create anaccount orloginMydevices.1849 +On the **Add integration** window, configure the following: 1332 1332 1333 - (% style="color:blue" %)**Step 4**(%%): SearchLT-22222-L(for both LT-22222-L) and add DevEUI.(%style="display:none" %)1851 +**Basic settings:** 1334 1334 1335 -Search under The things network 1853 +* Select **The Things Stack Community** from the **Integration type** list. 1854 +* Enter a suitable name for your integration in the **Name **text** **box or keep the default name. 1855 +* Ensure the following options are turned on. 1856 +** Enable integration 1857 +** Debug mode 1858 +** Allow create devices or assets 1859 +* Click the **Next** button. you will be navigated to the **Uplink data converter** tab. 1336 1336 1337 -[[image: 1653356838789-523.png||height="337" width="740"]]1861 +[[image:thingseye-io-step-2.png||height="625" width="1000"]] 1338 1338 1339 1339 1340 - After added, the sensordataarrive TTN, it will alsoarrive and show in Mydevices.1864 +**Uplink data converter:** 1341 1341 1342 -[[image:image-20220524094909-1.png||height="335" width="729"]] 1866 +* Click the **Create new** button if it is not selected by default. 1867 +* Enter a suitable name for the uplink data converter in the **Name **text** **box or keep the default name. 1868 +* Click the **JavaScript** button. 1869 +* Paste the uplink decoder function into the text area (first, delete the default code). The demo uplink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Uplink_Converter.js]]. 1870 +* Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 1343 1343 1872 +[[image:thingseye-io-step-3.png||height="625" width="1000"]] 1344 1344 1345 -[[image:image-20220524094909-2.png||height="337" width="729"]] 1346 1346 1875 +**Downlink data converter (this is an optional step):** 1347 1347 1348 -[[image:image-20220524094909-3.png||height="338" width="727"]] 1877 +* Click the **Create new** button if it is not selected by default. 1878 +* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name. 1879 +* Click the **JavaScript** button. 1880 +* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Downlink_Converter.js]]. 1881 +* Click the **Next** button. You will be navigated to the **Connection** tab. 1349 1349 1883 +[[image:thingseye-io-step-4.png||height="625" width="1000"]] 1350 1350 1351 -[[image:image-20220524094909-4.png||height="339" width="728"]](% style="display:none" %) 1352 1352 1886 +**Connection:** 1353 1353 1354 -[[image:image-20220524094909-5.png||height="341" width="734"]] 1888 +* Choose **Region** from the **Host type**. 1889 +* 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/...). 1890 +* 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). 1891 +* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**. 1355 1355 1893 +[[image:message-1.png]] 1356 1356 1357 -== 3.6 Interface Detail == 1358 1358 1359 - ===3.6.1 DigitalInputPort: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===1896 +* Click the **Add** button. 1360 1360 1898 +[[image:thingseye-io-step-5.png||height="625" width="1000"]] 1361 1361 1362 -Support NPN Type sensor 1363 1363 1901 +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. 1902 + 1903 + 1904 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]] 1905 + 1906 + 1907 +==== 3.5.2.1 Viewing integration details ==== 1908 + 1909 +Click on your integration from the list. The **Integration details** window will appear with the **Details **tab selected. The **Details **tab shows all the settings you have provided for this integration. 1910 + 1911 +[[image:integration-details.png||height="686" width="1000"]] 1912 + 1913 + 1914 +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. 1915 + 1916 +{{info}} 1917 +See also ThingsEye documentation. 1918 +{{/info}} 1919 + 1920 +==== **3.5.2.2 Viewing events** ==== 1921 + 1922 +The **Events **tab displays all the uplink messages from the LT-22222-L. 1923 + 1924 +* Select **Debug **from the **Event type** dropdown. 1925 +* Select the** time frame** from the **time window**. 1926 + 1927 +[[image:thingseye-events.png||height="686" width="1000"]] 1928 + 1929 + 1930 +* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message. 1931 + 1932 +[[image:thingseye-json.png||width="1000"]] 1933 + 1934 + 1935 +==== **3.5.2.3 Deleting an integration** ==== 1936 + 1937 +If you want to delete an integration, click the **Delete integratio**n button on the Integrations page. 1938 + 1939 + 1940 +== 3.6 Interface Details == 1941 + 1942 +=== 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) === 1943 + 1944 + 1945 +Supports NPN-type sensors. 1946 + 1364 1364 [[image:1653356991268-289.png]] 1365 1365 1366 1366 1367 -=== 3.6.2 Digital Input Port: DI1/DI2 ( For LT-22222-L)===1950 +=== 3.6.2 Digital Input Ports: DI1/DI2 === 1368 1368 1369 1369 1370 1370 ((( 1371 -The DI port of LT-22222-L can support **NPN** or**PNP** or **DryContact** output sensor.1954 +The DI ports of the LT-22222-L can support **NPN**, **PNP**, or **dry contact** output sensors. 1372 1372 ))) 1373 1373 1374 1374 ((( 1375 1375 ((( 1376 - Internal circuitas below,the NEC2501is aphotocoupler,theActive current(from NEC2501 pin 1 to pin 2 is 1maandthemax currentis50mA).(% class="mark" %)Whenthere isactive currentpassNEC2501 pin1 to pin2.The DIwillbe activehighand DI LED statuswillchange.1959 +The part of the internal circuit of the LT-22222-L shown below includes the NEC2501 photocoupler. The active current from NEC2501 pin 1 to pin 2 is 1 mA, with a maximum allowable current of 50 mA. When active current flows from NEC2501 pin 1 to pin 2, the DI becomes active HIGH and the DI LED status changes. 1377 1377 1378 1378 1379 1379 ))) ... ... @@ -1383,7 +1383,7 @@ 1383 1383 1384 1384 ((( 1385 1385 ((( 1386 - When use need1969 +(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)When connecting a device to the DI port, both DI1+ and DI1- must be connected. 1387 1387 ))) 1388 1388 ))) 1389 1389 ... ... @@ -1392,22 +1392,22 @@ 1392 1392 ))) 1393 1393 1394 1394 ((( 1395 -(% style="color: blue" %)**Example1**(%%): Connect to aLow1978 +(% style="color:#0000ff" %)**Example 1**(%%): Connecting to a low-active sensor. 1396 1396 ))) 1397 1397 1398 1398 ((( 1399 -This type of sensor willoutput a low signalGNDwhen active.1982 +This type of sensor outputs a low (GND) signal when active. 1400 1400 ))) 1401 1401 1402 1402 * ((( 1403 -Connect sensor's output to DI1- 1986 +Connect the sensor's output to DI1- 1404 1404 ))) 1405 1405 * ((( 1406 -Connect sensor's VCC to DI1+. 1989 +Connect the sensor's VCC to DI1+. 1407 1407 ))) 1408 1408 1409 1409 ((( 1410 - So when sensor active, the current between NEC2501 pin1 and pin2 is:1993 +When the sensor is active, the current between NEC2501 pin 1 and pin 2 will be: 1411 1411 ))) 1412 1412 1413 1413 ((( ... ... @@ -1415,7 +1415,7 @@ 1415 1415 ))) 1416 1416 1417 1417 ((( 1418 - If** DI1+ **= **12v**, the [[image:1653968155772-850.png||height="23" width="19"]]= 12mA ,Sothe LT-22222-L will be able to detect this active signal.2001 +For example, if** DI1+ **= **12V**, the resulting current is [[image:1653968155772-850.png||height="23" width="19"]]= 12mA. Therefore, the LT-22222-L will be able to detect this active signal. 1419 1419 ))) 1420 1420 1421 1421 ((( ... ... @@ -1423,22 +1423,22 @@ 1423 1423 ))) 1424 1424 1425 1425 ((( 1426 -(% style="color: blue" %)**Example2**(%%): Connect to aHigh2009 +(% style="color:#0000ff" %)**Example 2**(%%): Connecting to a high-active sensor. 1427 1427 ))) 1428 1428 1429 1429 ((( 1430 -This type of sensor willoutput a high signal (example24v) when active.2013 +This type of sensor outputs a high signal (e.g., 24V) when active. 1431 1431 ))) 1432 1432 1433 1433 * ((( 1434 -Connect sensor's output to DI1+ 2017 +Connect the sensor's output to DI1+ 1435 1435 ))) 1436 1436 * ((( 1437 -Connect sensor's GND DI1-. 2020 +Connect the sensor's GND DI1-. 1438 1438 ))) 1439 1439 1440 1440 ((( 1441 - So when sensor active, the current between NEC2501 pin1 and pin2 is:2024 +When the sensor is active, the current between NEC2501 pin1 and pin2 will be: 1442 1442 ))) 1443 1443 1444 1444 ((( ... ... @@ -1446,7 +1446,7 @@ 1446 1446 ))) 1447 1447 1448 1448 ((( 1449 -If **DI1+ = 24 v**, the[[image:1653968155772-850.png||height="23" width="19"]] 24mASo the LT-22222-L willbe able todetect this high2032 +If **DI1+ = 24V**, the resulting current[[image:1653968155772-850.png||height="23" width="19"]] is 24mA, Therefore, the LT-22222-L will detect this high-active signal. 1450 1450 ))) 1451 1451 1452 1452 ((( ... ... @@ -1454,22 +1454,22 @@ 1454 1454 ))) 1455 1455 1456 1456 ((( 1457 -(% style="color: blue" %)**Example3**(%%): Connect to a 220vhigh2040 +(% style="color:#0000ff" %)**Example 3**(%%): Connecting to a 220V high-active sensor. 1458 1458 ))) 1459 1459 1460 1460 ((( 1461 -Assume u serwant to monitor an active signal higher than 220v,to make surenotburnthe photocoupler2044 +Assume that you want to monitor an active signal higher than 220V without damaging the photocoupler 1462 1462 ))) 1463 1463 1464 1464 * ((( 1465 -Connect sensor's output to DI1+ with a serial50K resistor2048 +Connect the sensor's output to DI1+ with a 50K resistor in series. 1466 1466 ))) 1467 1467 * ((( 1468 -Connect sensor's GND DI1-. 2051 +Connect the sensor's GND DI1-. 1469 1469 ))) 1470 1470 1471 1471 ((( 1472 - So when sensor active, the current between NEC2501 pin1 and pin2 is:2055 +When the sensor is active, the current between NEC2501 pin1 and pin2 will be: 1473 1473 ))) 1474 1474 1475 1475 ((( ... ... @@ -1477,37 +1477,37 @@ 1477 1477 ))) 1478 1478 1479 1479 ((( 1480 -If sensor output is 220 v, the.= 4.3mA ,Sothe LT-22222-L will be able to detect this highsafely.2063 +If the sensor output is 220V, then [[image:1653968155772-850.png||height="23" width="19"]](% id="cke_bm_243359S" style="display:none" wfd-invisible="true" %)[[image:image-20220524095628-8.png]](%%) = DI1+ / 51K = 4.3mA. Therefore, the LT-22222-L will be able to safely detect this high-active signal. 1481 1481 ))) 1482 1482 1483 1483 1484 -(% style="color:blue" %)**Example4**(%%): Connect to Dry Contact sensor 2067 +(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor 1485 1485 1486 -From above DI portscircuit,we can see that activethe photocouplerwill needto haveavoltage difference between DI+ and DI- port.While the Dry Contact sensor is a passive componentwhichcan't provide this voltage difference.2069 +From the DI port circuit above, you can see that activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference. 1487 1487 1488 -To detect a Dry Contact, wecan providea power source to one pin of the Dry Contact. Below is a reference connection.2071 +To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram. 1489 1489 1490 1490 [[image:image-20230616235145-1.png]] 1491 1491 1492 -(% style="color:blue" %)**Example5**(%%): Connect to Open Colle actor2075 +(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector 1493 1493 1494 1494 [[image:image-20240219115718-1.png]] 1495 1495 1496 1496 1497 -=== 3.6.3 Digital Output Port: DO1/DO2 /DO3===2080 +=== 3.6.3 Digital Output Ports: DO1/DO2 === 1498 1498 1499 1499 1500 -(% style="color:blue" %)**NPN output**(%%): GND or Float. Max voltage can applyto output pin is 36v.2083 +(% style="color:blue" %)**NPN output**(%%): GND or Float. The maximum voltage that can be applied to the output pin is 36V. 1501 1501 1502 -(% style="color:red" %)**Note: DO pins gotofloat when device is power off.**2085 +(% style="color:red" %)**Note: The DO pins will float when the device is powered off.** 1503 1503 1504 1504 [[image:1653357531600-905.png]] 1505 1505 1506 1506 1507 -=== 3.6.4 Analog Input Interface === 2090 +=== 3.6.4 Analog Input Interfaces === 1508 1508 1509 1509 1510 -The analog input interface is as below. The LT will measure the IN2 voltagesoto calculate the current pass theLoad. The formula is:2093 +The analog input interface is shown below. The LT-22222-L will measure the IN2 voltage to calculate the current passing through the load. The formula is: 1511 1511 1512 1512 1513 1513 (% style="color:blue" %)**AC2 = (IN2 voltage )/12** ... ... @@ -1514,14 +1514,14 @@ 1514 1514 1515 1515 [[image:1653357592296-182.png]] 1516 1516 1517 -Example toconnect a 4~~20mA sensor2100 +Example: Connecting a 4~~20mA sensor 1518 1518 1519 -We take the wind speed sensor as an example for reference only.2102 +We will use the wind speed sensor as an example for reference only. 1520 1520 1521 1521 1522 1522 (% style="color:blue" %)**Specifications of the wind speed sensor:** 1523 1523 1524 -(% style="color:red" %)**Red: 12~~24 v**2107 +(% style="color:red" %)**Red: 12~~24V** 1525 1525 1526 1526 (% style="color:#ffc000" %)**Yellow: 4~~20mA** 1527 1527 ... ... @@ -1534,7 +1534,7 @@ 1534 1534 [[image:1653357648330-671.png||height="155" width="733"]] 1535 1535 1536 1536 1537 -Example connectedto a regulated power supply to measure voltage2120 +Example: Connecting to a regulated power supply to measure voltage 1538 1538 1539 1539 [[image:image-20230608101532-1.png||height="606" width="447"]] 1540 1540 ... ... @@ -1543,7 +1543,7 @@ 1543 1543 [[image:image-20230608101722-3.png||height="102" width="1139"]] 1544 1544 1545 1545 1546 -(% style="color:blue; font-weight:bold" %)**Specifications of the regulated power**(% %) (%style="color:blue" %)**:**2129 +(% style="color:blue; font-weight:bold" %)**Specifications of the regulated power supply**(% style="color:blue" %)**:** 1547 1547 1548 1548 (% style="color:red" %)**Red: 12~~24v** 1549 1549 ... ... @@ -1554,9 +1554,9 @@ 1554 1554 1555 1555 1556 1556 ((( 1557 -The LT serial controllerhas two relay interfaces;eachinterfaceusestwo pins of the screw terminal.User can connectotherdevice'sPowerLinetoin serialof RO1_1 and RO_2. Such asbelow:2140 +The LT-22222-L has two relay interfaces, RO1 and RO2, each using two pins of the screw terminal (ROx-1 and ROx-2 where x is the port number, 1 or 2). You can connect a device's power line in series with one of the relay interfaces (e.g., RO1-1 and RO1-2 screw terminals). See the example below: 1558 1558 1559 -**Note**: RO pins gotoOpen(NO) whendeviceis power off.2142 +**Note**: The ROx pins will be in the Open (NO) state when the LT-22222-L is powered off. 1560 1560 ))) 1561 1561 1562 1562 [[image:image-20220524100215-9.png]] ... ... @@ -1567,10 +1567,11 @@ 1567 1567 1568 1568 == 3.7 LEDs Indicators == 1569 1569 2153 +The table below lists the behavior of LED indicators for each port function. 1570 1570 1571 1571 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) 1572 1572 |(% style="background-color:#4f81bd; color:white; width:50px" %)**LEDs**|(% style="background-color:#4f81bd; color:white; width:460px" %)**Feature** 1573 -|**PWR**|Always on ifthere is power2157 +|**PWR**|Always on when there is power 1574 1574 |**TX**|((( 1575 1575 ((( 1576 1576 Device boot: TX blinks 5 times. ... ... @@ -1577,7 +1577,7 @@ 1577 1577 ))) 1578 1578 1579 1579 ((( 1580 -Successful joinnetwork: TX ON for 5 seconds.2164 +Successful network join: TX remains ON for 5 seconds. 1581 1581 ))) 1582 1582 1583 1583 ((( ... ... @@ -1584,32 +1584,34 @@ 1584 1584 Transmit a LoRa packet: TX blinks once 1585 1585 ))) 1586 1586 ))) 1587 -|**RX**|RX blinks once when receivea packet.1588 -|**DO1**|For LT-22222-L: ON when DO1 is low, LOWwhen DO1 is high1589 -|**DO2**|For LT-22222-L: ON when DO2 is low, LOWwhen DO2 is high2171 +|**RX**|RX blinks once when a packet is received. 2172 +|**DO1**|For LT-22222-L: ON when DO1 is low, OFF when DO1 is high 2173 +|**DO2**|For LT-22222-L: ON when DO2 is low, OFF when DO2 is high 1590 1590 |**DI1**|((( 1591 -For LT-22222-L: ON when DI1 is high, LOWwhen DI1 is low2175 +For LT-22222-L: ON when DI1 is high, OFF when DI1 is low 1592 1592 ))) 1593 1593 |**DI2**|((( 1594 -For LT-22222-L: ON when DI2 is high, LOWwhen DI2 is low2178 +For LT-22222-L: ON when DI2 is high, OFF when DI2 is low 1595 1595 ))) 1596 -|**RO1**|For LT-22222-L: ON when RO1 is closed, LOWwhen RO1 is open1597 -|**RO2**|For LT-22222-L: ON when RO2 is closed, LOWwhen RO2 is open2180 +|**RO1**|For LT-22222-L: ON when RO1 is closed, OFF when RO1 is open 2181 +|**RO2**|For LT-22222-L: ON when RO2 is closed, OFF when RO2 is open 1598 1598 1599 -= 4. Us eAT Command =2183 += 4. Using AT Commands = 1600 1600 1601 - ==4.1Access AT Command==2185 +The LT-22222-L supports programming using AT Commands. 1602 1602 2187 +== 4.1 Connecting the LT-22222-L to a PC == 1603 1603 1604 1604 ((( 1605 -LT supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to LT for using AT command, as below. 2190 +You can use a USB-to-TTL adapter along with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below. 2191 + 2192 +[[image:usb-ttl-programming.png]] 1606 1606 ))) 1607 1607 1608 -[[image:1653358238933-385.png]] 1609 1609 1610 1610 1611 1611 ((( 1612 - In PC,Userneedsto set (% style="color:#4f81bd" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]],SecureCRT) baud ratetoo accessserial consoleforLT.The AT commandsaredisable by default andneedto enterpassword (default:(% style="color:green" %)**123456**)(%%)oactiveit.As shown below:2198 +On the PC, you need to set the (% style="color:#4f81bd" %)**serial tool **(%%)(such as [[PuTTY>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]] or [[SecureCRT>>https://www.vandyke.com/cgi-bin/releases.php?product=securecrt]]) to a baud rate of (% style="color:green" %)**9600**(%%) to access the serial console of LT-22222-L. Access to AT commands is disabled by default, and a password (default: (% style="color:green" %)**123456**)(%%) must be entered to enable AT command access, as shown below: 1613 1613 ))) 1614 1614 1615 1615 [[image:1653358355238-883.png]] ... ... @@ -1616,194 +1616,63 @@ 1616 1616 1617 1617 1618 1618 ((( 1619 -More detail AT Command manual can be found at [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]] 1620 -))) 2205 +You can find more details in the [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]] 1621 1621 1622 -((( 1623 -AT+<CMD>? : Help on <CMD> 2207 +== 4.2 LT-22222-L related AT commands == 1624 1624 ))) 1625 1625 1626 1626 ((( 1627 -AT+<CMD> : Run <CMD> 1628 -))) 2211 +The following is the list of all the AT commands related to the LT-22222-L, except for those used for switching between working modes. 1629 1629 1630 -((( 1631 -AT+<CMD>=<value> : Set the value 2213 +* **##AT##+<CMD>?** : Help on <CMD> 2214 +* **##AT##+<CMD>** : Run <CMD> 2215 +* **##AT##+<CMD>=<value>** : Set the value 2216 +* **##AT##+<CMD>=?** : Get the value 2217 +* ##**ATZ**##: Trigger a reset of the MCU 2218 +* ##**AT+FDR**##: Reset Parameters to factory default, reserve keys 2219 +* **##AT+DEUI##**: Get or set the Device EUI (DevEUI) 2220 +* **##AT+DADDR##**: Get or set the Device Address (DevAddr) 2221 +* **##AT+APPKEY##**: Get or set the Application Key (AppKey) 2222 +* ##**AT+NWKSKEY**##: Get or set the Network Session Key (NwkSKey) 2223 +* **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey) 2224 +* **##AT+APPEUI##**: Get or set the Application EUI (AppEUI) 2225 +* **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON) 2226 +* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification) 2227 +* AT+DR: Get or set the Data Rate. (0-7 corresponding to DR_X) 2228 +* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing 2229 +* AT+PNM: Get or set the public network mode. (0: off, 1: on) 2230 +* AT+RX2FQ: Get or set the Rx2 window frequency 2231 +* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X) 2232 +* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms 2233 +* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms 2234 +* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms 2235 +* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms 2236 +* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA) 2237 +* AT+NWKID: Get or set the Network ID 2238 +* AT+FCU: Get or set the Frame Counter Uplink (FCntUp) 2239 +* AT+FCD: Get or set the Frame Counter Downlink (FCntDown) 2240 +* AT+CLASS: Get or set the Device Class 2241 +* AT+JOIN: Join network 2242 +* AT+NJS: Get OTAA Join Status 2243 +* AT+SENDB: Send hexadecimal data along with the application port 2244 +* AT+SEND: Send text data along with the application port 2245 +* AT+RECVB: Print last received data in binary format (with hexadecimal values) 2246 +* AT+RECV: Print last received data in raw format 2247 +* AT+VER: Get current image version and Frequency Band 2248 +* AT+CFM: Get or Set the confirmation mode (0-1) 2249 +* AT+CFS: Get confirmation status of the last AT+SEND (0-1) 2250 +* AT+SNR: Get the SNR of the last received packet 2251 +* AT+RSSI: Get the RSSI of the last received packet 2252 +* AT+TDC: Get or set the application data transmission interval in ms 2253 +* AT+PORT: Get or set the application port 2254 +* AT+DISAT: Disable AT commands 2255 +* AT+PWORD: Set password, max 9 digits 2256 +* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode 2257 +* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470 2258 +* AT+CFG: Print all settings 1632 1632 ))) 1633 1633 1634 -((( 1635 -AT+<CMD>=? : Get the value 1636 -))) 1637 1637 1638 -((( 1639 -ATZ: Trig a reset of the MCU 1640 -))) 1641 - 1642 -((( 1643 -AT+FDR: Reset Parameters to Factory Default, Keys Reserve 1644 -))) 1645 - 1646 -((( 1647 -AT+DEUI: Get or Set the Device EUI 1648 -))) 1649 - 1650 -((( 1651 -AT+DADDR: Get or Set the Device Address 1652 -))) 1653 - 1654 -((( 1655 -AT+APPKEY: Get or Set the Application Key 1656 -))) 1657 - 1658 -((( 1659 -AT+NWKSKEY: Get or Set the Network Session Key 1660 -))) 1661 - 1662 -((( 1663 -AT+APPSKEY: Get or Set the Application Session Key 1664 -))) 1665 - 1666 -((( 1667 -AT+APPEUI: Get or Set the Application EUI 1668 -))) 1669 - 1670 -((( 1671 -AT+ADR: Get or Set the Adaptive Data Rate setting. (0: off, 1: on) 1672 -))) 1673 - 1674 -((( 1675 -AT+TXP: Get or Set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Spec) 1676 -))) 1677 - 1678 -((( 1679 -AT+DR: Get or Set the Data Rate. (0-7 corresponding to DR_X) 1680 -))) 1681 - 1682 -((( 1683 -AT+DCS: Get or Set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing 1684 -))) 1685 - 1686 -((( 1687 -AT+PNM: Get or Set the public network mode. (0: off, 1: on) 1688 -))) 1689 - 1690 -((( 1691 -AT+RX2FQ: Get or Set the Rx2 window frequency 1692 -))) 1693 - 1694 -((( 1695 -AT+RX2DR: Get or Set the Rx2 window data rate (0-7 corresponding to DR_X) 1696 -))) 1697 - 1698 -((( 1699 -AT+RX1DL: Get or Set the delay between the end of the Tx and the Rx Window 1 in ms 1700 -))) 1701 - 1702 -((( 1703 -AT+RX2DL: Get or Set the delay between the end of the Tx and the Rx Window 2 in ms 1704 -))) 1705 - 1706 -((( 1707 -AT+JN1DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms 1708 -))) 1709 - 1710 -((( 1711 -AT+JN2DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms 1712 -))) 1713 - 1714 -((( 1715 -AT+NJM: Get or Set the Network Join Mode. (0: ABP, 1: OTAA) 1716 -))) 1717 - 1718 -((( 1719 -AT+NWKID: Get or Set the Network ID 1720 -))) 1721 - 1722 -((( 1723 -AT+FCU: Get or Set the Frame Counter Uplink 1724 -))) 1725 - 1726 -((( 1727 -AT+FCD: Get or Set the Frame Counter Downlink 1728 -))) 1729 - 1730 -((( 1731 -AT+CLASS: Get or Set the Device Class 1732 -))) 1733 - 1734 -((( 1735 -AT+JOIN: Join network 1736 -))) 1737 - 1738 -((( 1739 -AT+NJS: Get OTAA Join Status 1740 -))) 1741 - 1742 -((( 1743 -AT+SENDB: Send hexadecimal data along with the application port 1744 -))) 1745 - 1746 -((( 1747 -AT+SEND: Send text data along with the application port 1748 -))) 1749 - 1750 -((( 1751 -AT+RECVB: Print last received data in binary format (with hexadecimal values) 1752 -))) 1753 - 1754 -((( 1755 -AT+RECV: Print last received data in raw format 1756 -))) 1757 - 1758 -((( 1759 -AT+VER: Get current image version and Frequency Band 1760 -))) 1761 - 1762 -((( 1763 -AT+CFM: Get or Set the confirmation mode (0-1) 1764 -))) 1765 - 1766 -((( 1767 -AT+CFS: Get confirmation status of the last AT+SEND (0-1) 1768 -))) 1769 - 1770 -((( 1771 -AT+SNR: Get the SNR of the last received packet 1772 -))) 1773 - 1774 -((( 1775 -AT+RSSI: Get the RSSI of the last received packet 1776 -))) 1777 - 1778 -((( 1779 -AT+TDC: Get or set the application data transmission interval in ms 1780 -))) 1781 - 1782 -((( 1783 -AT+PORT: Get or set the application port 1784 -))) 1785 - 1786 -((( 1787 -AT+DISAT: Disable AT commands 1788 -))) 1789 - 1790 -((( 1791 -AT+PWORD: Set password, max 9 digits 1792 -))) 1793 - 1794 -((( 1795 -AT+CHS: Get or Set Frequency (Unit: Hz) for Single Channel Mode 1796 -))) 1797 - 1798 -((( 1799 -AT+CHE: Get or Set eight channels mode, Only for US915, AU915, CN470 1800 -))) 1801 - 1802 -((( 1803 -AT+CFG: Print all settings 1804 -))) 1805 - 1806 - 1807 1807 == 4.2 Common AT Command Sequence == 1808 1808 1809 1809 === 4.2.1 Multi-channel ABP mode (Use with SX1301/LG308) === ... ... @@ -1812,41 +1812,41 @@ 1812 1812 1813 1813 1814 1814 ((( 1815 -(% style="color:blue" %)**If device has not joined network yet:**2270 +(% style="color:blue" %)**If the device has not yet joined the network:** 1816 1816 ))) 1817 1817 ))) 1818 1818 1819 1819 ((( 1820 -(% style="background-color:#dcdcdc" %)**123456** 2275 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**## 1821 1821 ))) 1822 1822 1823 1823 ((( 1824 -(% style="background-color:#dcdcdc" %)**AT+FDR** 2279 +(% style="background-color:#dcdcdc" %)##**AT+FDR ~/~/Reset parameters to factory default, Reserve keys**## 1825 1825 ))) 1826 1826 1827 1827 ((( 1828 -(% style="background-color:#dcdcdc" %)**123456** 2283 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**## 1829 1829 ))) 1830 1830 1831 1831 ((( 1832 -(% style="background-color:#dcdcdc" %)**AT+NJM=0** 2287 +(% style="background-color:#dcdcdc" %)##**AT+NJM=0 ~/~/Set to ABP mode**## 1833 1833 ))) 1834 1834 1835 1835 ((( 1836 -(% style="background-color:#dcdcdc" %)**ATZ** 2291 +(% style="background-color:#dcdcdc" %)##**ATZ ~/~/Reset MCU**## 1837 1837 ))) 1838 1838 1839 1839 1840 1840 ((( 1841 -(% style="color:blue" %)**If device already joined network:** 2296 +(% style="color:blue" %)**If the device has already joined the network:** 1842 1842 ))) 1843 1843 1844 1844 ((( 1845 -(% style="background-color:#dcdcdc" %)**AT+NJM=0** 2300 +(% style="background-color:#dcdcdc" %)##**AT+NJM=0**## 1846 1846 ))) 1847 1847 1848 1848 ((( 1849 -(% style="background-color:#dcdcdc" %)**ATZ** 2304 +(% style="background-color:#dcdcdc" %)##**ATZ**## 1850 1850 ))) 1851 1851 1852 1852 ... ... @@ -1856,20 +1856,20 @@ 1856 1856 1857 1857 1858 1858 ((( 1859 -(% style="background-color:#dcdcdc" %)**123456**(%%) ~/~/ Enter Password tohave AT access.2314 +(% style="background-color:#dcdcdc" %)**123456**(%%) ~/~/ Enter password to enable AT commands access 1860 1860 ))) 1861 1861 ))) 1862 1862 1863 1863 ((( 1864 -(% style="background-color:#dcdcdc" %)** AT+FDR**(%%) ~/~/ Reset Parameters to Factory Default,KeysReserve2319 +(% style="background-color:#dcdcdc" %)** AT+FDR**(%%) ~/~/ Reset parameters to Factory Default, Reserve keys 1865 1865 ))) 1866 1866 1867 1867 ((( 1868 -(% style="background-color:#dcdcdc" %)** 123456**(%%) ~/~/ Enter Password tohave AT access.2323 +(% style="background-color:#dcdcdc" %)** 123456**(%%) ~/~/ Enter password to enable AT commands access 1869 1869 ))) 1870 1870 1871 1871 ((( 1872 -(% style="background-color:#dcdcdc" %)** AT+CLASS=C**(%%) ~/~/ Set to work inCLASS C2327 +(% style="background-color:#dcdcdc" %)** AT+CLASS=C**(%%) ~/~/ Set to CLASS C mode 1873 1873 ))) 1874 1874 1875 1875 ((( ... ... @@ -1889,19 +1889,19 @@ 1889 1889 ))) 1890 1890 1891 1891 ((( 1892 -(% style="background-color:#dcdcdc" %)** AT+CHS=868400000**(%%) ~/~/ Set transmit frequency to 868.4M hz2347 +(% style="background-color:#dcdcdc" %)** AT+CHS=868400000**(%%) ~/~/ Set transmit frequency to 868.4 MHz 1893 1893 ))) 1894 1894 1895 1895 ((( 1896 -(% style="background-color:#dcdcdc" %)** AT+RX2FQ=868400000**(%%) ~/~/ Set RX2 Frequency to 868.4Mhz (according to the result from server)2351 +(% style="background-color:#dcdcdc" %)** AT+RX2FQ=868400000**(%%) ~/~/ Set RX2 frequency to 868.4 MHz (according to the result from the server) 1897 1897 ))) 1898 1898 1899 1899 ((( 1900 -(% style="background-color:#dcdcdc" %)** AT+RX2DR=5**(%%)** ** ~/~/ Set RX2DR to match the downlink DR from server. see below2355 +(% style="background-color:#dcdcdc" %)** AT+RX2DR=5**(%%)** ** ~/~/ Set RX2 DR to match the downlink DR from the server. See below. 1901 1901 ))) 1902 1902 1903 1903 ((( 1904 -(% style="background-color:#dcdcdc" %)** AT+DADDR=26 01 1A F1** (%%) ~/~/ Set Device Address to2601 1AF1, thisIDcan be found in theLoRaServerportal.2359 +(% style="background-color:#dcdcdc" %)** AT+DADDR=26 01 1A F1** (%%) ~/~/ Set Device Address. The Device Address can be found in the application on the LoRaWAN NS. 1905 1905 ))) 1906 1906 1907 1907 ((( ... ... @@ -1915,14 +1915,14 @@ 1915 1915 ))) 1916 1916 1917 1917 ((( 1918 -**~1. Makesure the device is set to ABP mode in theIoTServer.**2373 +**~1. Ensure that the device is set to ABP mode in the LoRaWAN Network Server.** 1919 1919 1920 -**2. Makesurethe LG01/02 gateway RX frequencyis exactlythesame asAT+CHS setting.**2375 +**2. Verify that the LG01/02 gateway RX frequency matches the AT+CHS setting exactly.** 1921 1921 1922 -**3. Make sure SF refer [[this link>>url:http://www.dragino.com/downloads/index.php?2377 +**3. Make sure the SF/bandwidth settings in the LG01/LG02 match the settings of AT+DR. Refer to [[this link>>url:http://www.dragino.com/downloads/index.php? 1923 1923 dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.** 1924 1924 1925 -**4. The command AT+RX2FQ and AT+RX2DR is toletdownlinkwork.to set the correct parameters, usercan check the actuallydownlink parameters to be used.As below.Which shows the RX2FQ shoulduse 868400000 and RX2DR should be 5.**2380 +**4. The commands AT+RX2FQ and AT+RX2DR enable downlink functionality. To set the correct parameters, you can check the actual downlink parameters to be used as shown below. Here, RX2FQ should be set to 868400000 and RX2DR should be set to 5.** 1926 1926 ))) 1927 1927 1928 1928 ((( ... ... @@ -1934,7 +1934,7 @@ 1934 1934 1935 1935 1936 1936 ((( 1937 -(% style="color:blue" %)**If sensor JOINED:** 2392 +(% style="color:blue" %)**If the sensor has JOINED:** 1938 1938 1939 1939 (% style="background-color:#dcdcdc" %)**AT+CLASS=A** 1940 1940 ... ... @@ -1944,37 +1944,48 @@ 1944 1944 1945 1945 = 5. Case Study = 1946 1946 1947 -== 5.1 Counting how many objects pass inFlowLine ==2402 +== 5.1 Counting how many objects pass through the flow line == 1948 1948 2404 +See [[How to set up to setup counting for objects passing through the flow line>>How to set up to count objects pass in flow line]]? 1949 1949 1950 -Reference Link: [[How to set up to count objects pass in flow line>>How to set up to count objects pass in flow line]]? 1951 1951 1952 - 1953 1953 = 6. FAQ = 1954 1954 1955 - ==6.1 Howtoupgrade theimage?==2409 +This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly. 1956 1956 1957 1957 1958 - TheLTLoRaWANControlleris shippedwitha3.5mm cable,thecableis used to upload imageto LT to:2412 +== 6.1 How to update the firmware? == 1959 1959 2414 +Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to: 2415 + 1960 1960 * Support new features 1961 -* F orbugfix1962 -* Change LoRaWAN bands .2417 +* Fix bugs 2418 +* Change LoRaWAN frequency bands 1963 1963 1964 - Belowshowsthe hardwareconnection forhow to uploadanimage to the LT:2420 +You will need the following things before proceeding: 1965 1965 1966 -[[image:1653359603330-121.png]] 2422 +* 3.5mm programming cable (included with the LT-22222-L as an additional accessory) 2423 +* USB to TTL adapter 2424 +* Download and install the [[STM32 Flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]]. (replaced by STM32CubeProgrammer) 2425 +* Download the latest firmware image from [[LT-22222-L firmware image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]]. Check the file name of the firmware to find the correct region. 1967 1967 2427 +{{info}} 2428 +As of this writing, the latest firmware version available for the LT-22222-L is v1.6.1. 2429 +{{/info}} 1968 1968 1969 -((( 1970 -(% style="color:blue" %)**Step1**(%%)**:** Download [[flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]]. 1971 -(% style="color:blue" %)**Step2**(%%)**:** Download the [[LT Image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]]. 1972 -(% style="color:blue" %)**Step3**(%%)**:** Open flashloader; choose the correct COM port to update. 1973 - 2431 +Below is the hardware setup for uploading a firmware image to the LT-22222-L: 1974 1974 2433 +[[image:usb-ttl-programming.png]] 2434 + 2435 + 2436 + 2437 +Start the STM32 Flash Loader and choose the correct COM port to update. 2438 + 1975 1975 ((( 2440 +((( 1976 1976 (% style="color:blue" %)**For LT-22222-L**(%%): 1977 -Hold down the PRO button and then momentarily press the RST reset button and the (% style="color:red" %)**DO1 led**(%%) will change from OFF to ON. When (% style="color:red" %)**DO1 LED**(%%) is on, it means the device is in download mode. 2442 + 2443 +Hold down the **PRO** button, then briefly press the **RST** button. The **DO1** LED will change from OFF to ON. When the **DO1** LED is ON, it indicates that the device is in firmware download mode. 1978 1978 ))) 1979 1979 1980 1980 ... ... @@ -1989,7 +1989,7 @@ 1989 1989 [[image:image-20220524104033-15.png]] 1990 1990 1991 1991 1992 -(% style="color:red" %)**Not ice**(%%): Incaseuserhaslost the program cable.Usercanhandmade one from a 3.5mm cable. The pin mapping is:2458 +(% style="color:red" %)**Note**(%%): If you have lost the programming cable, you can make one from a 3.5 mm cable. The pin mapping is as follows: 1993 1993 1994 1994 [[image:1653360054704-518.png||height="186" width="745"]] 1995 1995 ... ... @@ -1996,33 +1996,29 @@ 1996 1996 1997 1997 ((( 1998 1998 ((( 1999 -== 6.2 How to change the LoRa Frequency Bands/Region? == 2000 - 2001 - 2465 +== 6.2 How to change the LoRaWAN frequency band/region? == 2002 2002 ))) 2003 2003 ))) 2004 2004 2005 2005 ((( 2006 - Usercan follow the introductionfor[[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloadtheimages,choose the required image filefor download.2470 +You can follow the introductions on [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file. 2007 2007 ))) 2008 2008 2009 2009 ((( 2010 2010 2011 2011 2012 -== 6.3 How to set up LT to work with Single Channel Gateway such as LG01/LG02? == 2013 - 2014 - 2476 +== 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? == 2015 2015 ))) 2016 2016 2017 2017 ((( 2018 2018 ((( 2019 -In this case, u sersneed to set LT-33222-L to work in ABP mode&transmitin only one frequency.2481 +In this case, you need to set the LT-22222-L to work in ABP mode and transmit on only one frequency. 2020 2020 ))) 2021 2021 ))) 2022 2022 2023 2023 ((( 2024 2024 ((( 2025 - Assumewehave a LG02 workingin the frequency 868400000now , belowisthe step.2487 +We assume you have an LG01/LG02 working on the frequency 868400000. Below are the steps. 2026 2026 2027 2027 2028 2028 ))) ... ... @@ -2029,52 +2029,55 @@ 2029 2029 ))) 2030 2030 2031 2031 ((( 2032 -(% style="color: blue" %)**Step1**(%%):N,Create an ABP device in the applicationand inputthe networksessionkey (NETSKEY), appsessionkey (APPSKEY)fromthedevice.2494 +(% style="color:#0000ff" %)**Step 1**(%%): Log in to The Things Stack Sandbox account and create an ABP device in the application. To do this, use the manual registration option as explained in section 3.2.2.2, //Adding a Device Manually//. Select //Activation by Personalization (ABP)// under Activation Mode. Enter the DevEUI exactly as shown on the registration information sticker, then generate the Device Address, Application Session Key (AppSKey), and Network Session Key (NwkSKey). 2033 2033 2034 - 2496 +[[image:lt-22222-l-abp.png||height="686" width="1000"]] 2035 2035 ))) 2036 2036 2037 2037 ((( 2038 -[[image:1653360231087-571.png||height="401" width="727"]] 2039 - 2040 2040 2041 2041 ))) 2042 2042 2043 - (((2044 - (%style="color:red"%)**Note:userjustneed tomakeureabove threekeysmatch,Usercanchange either in TTNorDeviceto make thenmatch. In TTN,NETSKEY andAPPSKEYcanbeconfiguredbyuserin setting page, but Device Addr is generated by TTN.**2045 - )))2503 +{{warning}} 2504 +Ensure that the Device Address (DevAddr) and the two keys match between the LT-22222-L and The Things Stack. You can modify them either in The Things Stack or on the LT-22222-L to make them align. In The Things Stack, you can configure the NwkSKey and AppSKey on the settings page, but note that the Device Address is generated by The Things Stack. 2505 +{{/warning}} 2046 2046 2047 2047 2048 - 2049 2049 ((( 2050 -(% style="color:blue" %)**Step2**(%%)**: **Run AT Command tomake LTworkinSingle&ABP mode.Below is the AT commands:2509 +(% style="color:blue" %)**Step 2**(%%)**: **(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)Run AT commands to configure the LT-22222-L to operate in single-frequency and ABP mode. The AT commands are as follows: 2051 2051 2052 2052 2053 2053 ))) 2054 2054 2055 2055 ((( 2056 -(% style="background-color:#dcdcdc" %)**123456** (%%) Password tohave AT access.2515 +(% style="background-color:#dcdcdc" %)**123456** (%%) : Enter the password to enable AT access. 2057 2057 2058 -(% style="background-color:#dcdcdc" %)**AT+FDR**(%%) Parameters toFactoryDefault,KeysReserve2517 +(% style="background-color:#dcdcdc" %)**AT+FDR**(%%) : Reset parameters to factory default, keeping keys reserved. 2059 2059 2060 -(% style="background-color:#dcdcdc" %)**AT+NJM=0** (%%) : 2519 +(% style="background-color:#dcdcdc" %)**AT+NJM=0** (%%) : Set to ABP mode. 2061 2061 2062 -(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%) Setthe Adaptive Data RateOff2521 +(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%) : Disable the Adaptive Data Rate (ADR). 2063 2063 2064 -(% style="background-color:#dcdcdc" %)**AT+DR=5** (%%) SetAT+DR=3 for 915 band)2523 +(% style="background-color:#dcdcdc" %)**AT+DR=5** (%%) : Set Data Rate (Use AT+DR=3 for the 915 MHz band). 2065 2065 2066 -(% style="background-color:#dcdcdc" %)**AT+TDC=60000 **(%%) 2525 +(% style="background-color:#dcdcdc" %)**AT+TDC=60000 **(%%) : Set transmit interval to 60 seconds. 2067 2067 2068 -(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) : Set transmit frequency to 868.4M hz2527 +(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) : Set transmit frequency to 868.4 MHz. 2069 2069 2070 -(% style="background-color:#dcdcdc" %)**AT+DADDR= 26 01 1A F1**(%%)to 26 01 1AF12529 +(% style="background-color:#dcdcdc" %)**AT+DADDR=xxxx**(%%) : Set the Device Address (DevAddr) 2071 2071 2072 -(% style="background-color:#dcdcdc" %)**ATZ** (%%) : Reset MCU 2531 +(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:700; text-decoration:none; white-space:pre-wrap" %)**AT+APPKEY=xxxx**(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %): Get or set the Application Key (AppKey) 2532 + 2533 +(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)**AT+NWKSKEY=xxxx**: Get or set the Network Session Key (NwkSKey) 2534 + 2535 +(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)**AT+APPSKEY=xxxx**: Get or set the Application Session Key (AppSKey) 2536 + 2537 +(% style="background-color:#dcdcdc" %)**ATZ** (%%) : Reset MCU. 2073 2073 ))) 2074 2074 2075 2075 2076 2076 ((( 2077 -As shown in belo w:2542 +(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)The following figure shows the screenshot of the command set above, issued using a serial tool: 2078 2078 ))) 2079 2079 2080 2080 [[image:1653360498588-932.png||height="485" width="726"]] ... ... @@ -2082,156 +2082,137 @@ 2082 2082 2083 2083 == 6.4 How to change the uplink interval? == 2084 2084 2085 - 2086 2086 Please see this link: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/]] 2087 2087 2088 2088 2089 -== 6.5 Can I see counting event in Serial? ==2553 +== 6.5 Can I see the counting event in the serial output? == 2090 2090 2091 - 2092 2092 ((( 2093 - Usercan run AT+DEBUGcommandseethe counting event in serial. If firmware too old and doesn't support.User canupdate to latest firmware first.2556 +You can run the AT command **AT+DEBUG** to view the counting event in the serial output. If the firmware is too old and doesn’t support AT+DEBUG, update to the latest firmware first. 2094 2094 2095 2095 2096 -== 6.6 Can iuse pointforLT-22222-L? ==2559 +== 6.6 Can I use point-to-point communication with LT-22222-L? == 2097 2097 2561 +Yes, you can. Please refer to the [[Point-to-Point Communication of LT-22222-L>>https://wiki.dragino.com/xwiki/bin/view/Main/%20Point%20to%20Point%20Communication%20of%20LT-22222-L/]] page. The firmware that supports point-to-point communication can be found [[here>>https://github.com/dragino/LT-22222-L/releases]]. 2098 2098 2099 -Yes, please refer [[Point to Point Communication>>doc:Main. Point to Point Communication of LT-22222-L.WebHome]] ,this is [[firmware>>https://github.com/dragino/LT-22222-L/releases]]. 2100 - 2101 2101 2102 2102 ))) 2103 2103 2104 2104 ((( 2105 -== 6.7 Why does the relay output become thedefault andopen relay after thelt22222 is powered off? ==2567 +== 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? == 2106 2106 2569 +* If the device is not properly shut down and is directly powered off. 2570 +* It will default to a power-off state. 2571 +* In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory. 2572 +* After a restart, the status before the power failure will be read from flash. 2107 2107 2108 - Ifthedeviceisnot shutdown,butdirectlypoweredoff.2574 +== 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? == 2109 2109 2110 - Itwilldefaultthat thisisapower-offstate.2576 +The LT-22222-L's built-in relay is Normally Open (NO). You can use an external relay to achieve a Normally Closed (NC) configuration. The circuit diagram is shown below: 2111 2111 2112 -In modes 2 to 5, DO RO status and pulse count are saved in flash. 2113 2113 2114 -After restart, the status before power failure will be read from flash. 2115 - 2116 - 2117 -== 6.8 Can i set up LT-22222-L as a NC(Normal Close) Relay? == 2118 - 2119 - 2120 -LT-22222-L built-in relay is NO (Normal Open). User can use an external relay to achieve Normal Close purpose. Diagram as below: 2121 - 2122 - 2123 2123 [[image:image-20221006170630-1.png||height="610" width="945"]] 2124 2124 2125 2125 2126 -== 6.9 Can LT22222-L save RO state? == 2582 +== 6.9 Can the LT-22222-L save the RO state? == 2127 2127 2584 +To enable this feature, the firmware version must be 1.6.0 or higher. 2128 2128 2129 -Firmware version needs to be no less than 1.6.0. 2130 2130 2587 +== 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? == 2131 2131 2132 - ==6.10WhydoestheLT22222alwaysreport15.585VwhenmeasuringAVI?==2589 +It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose. 2133 2133 2134 2134 2135 - Itislikely that the GND isnot connected duringthe measurement, or the wire connected to the GND is loose.2592 += 7. Troubleshooting = 2136 2136 2594 +This section provides some known troubleshooting tips. 2137 2137 2138 - =7. Trouble Shooting =2596 + 2139 2139 ))) 2140 2140 2141 2141 ((( 2142 2142 ((( 2143 -== 7.1 Downlink doesn't work, how to solve it? == 2144 - 2145 - 2601 +== 7.1 Downlink isn't working. How can I solve this? == 2146 2146 ))) 2147 2147 ))) 2148 2148 2149 2149 ((( 2150 -Please see this link forhow todebug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]2606 +Please refer to this link for debugging instructions: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]] 2151 2151 ))) 2152 2152 2153 2153 ((( 2154 2154 2155 2155 2156 -== 7.2 Have trouble to upload image. == 2157 - 2158 - 2612 +== 7.2 Having trouble uploading an image? == 2159 2159 ))) 2160 2160 2161 2161 ((( 2162 - See this link for trouble2616 +Please refer to this link for troubleshooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]] 2163 2163 ))) 2164 2164 2165 2165 ((( 2166 2166 2167 2167 2168 -== 7.3 Why I can't join TTN in US915 /AU915 bands? == 2169 - 2170 - 2622 +== 7.3 Why can't I join TTN in the US915 /AU915 bands? == 2171 2171 ))) 2172 2172 2173 2173 ((( 2174 -It might be a bout the channelsmapping. [[Pleasesee this link for detail>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]2626 +It might be related to the channel mapping. [[Please refer to this link for details.>>https://github.com/dragino/LT-22222-L/releases]] 2175 2175 ))) 2176 2176 2177 2177 2178 -== 7.4 Why can LT22222 perform Uplink normally, but cannot receiveDownlink? ==2630 +== 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? == 2179 2179 2632 +The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue. 2633 +Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]] 2180 2180 2181 -The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue state. 2182 -Use this command to bring their counts back together: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]] 2183 2183 2636 += 8. Ordering information = 2184 2184 2185 -= 8. Order Info = 2186 - 2187 - 2188 2188 (% style="color:#4f81bd" %)**LT-22222-L-XXX:** 2189 2189 2190 2190 (% style="color:#4f81bd" %)**XXX:** 2191 2191 2192 -* (% style="color:red" %)**EU433**(%%): 2193 -* (% style="color:red" %)**EU868**(%%): 2194 -* (% style="color:red" %)**KR920**(%%): 2195 -* (% style="color:red" %)**CN470**(%%): 2196 -* (% style="color:red" %)**AS923**(%%): 2197 -* (% style="color:red" %)**AU915**(%%): 2198 -* (% style="color:red" %)**US915**(%%): 2199 -* (% style="color:red" %)**IN865**(%%): 2200 -* (% style="color:red" %)**CN779**(%%): 2642 +* (% style="color:red" %)**EU433**(%%): LT with frequency bands EU433 2643 +* (% style="color:red" %)**EU868**(%%): LT with frequency bands EU868 2644 +* (% style="color:red" %)**KR920**(%%): LT with frequency bands KR920 2645 +* (% style="color:red" %)**CN470**(%%): LT with frequency bands CN470 2646 +* (% style="color:red" %)**AS923**(%%): LT with frequency bands AS923 2647 +* (% style="color:red" %)**AU915**(%%): LT with frequency bands AU915 2648 +* (% style="color:red" %)**US915**(%%): LT with frequency bands US915 2649 +* (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865 2650 +* (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779 2201 2201 2202 -= 9. Pack ingInfo =2652 += 9. Package information = 2203 2203 2654 +**Package includes**: 2204 2204 2205 -**Package Includes**: 2656 +* 1 x LT-22222-L I/O Controller 2657 +* 1 x LoRa antenna matched to the frequency of the LT-22222-L 2658 +* 1 x bracket for DIN rail mounting 2659 +* 1 x 3.5 mm programming cable 2206 2206 2207 -* LT-22222-L I/O Controller x 1 2208 -* Stick Antenna for LoRa RF part x 1 2209 -* Bracket for controller x1 2210 -* Program cable x 1 2211 - 2212 2212 **Dimension and weight**: 2213 2213 2214 2214 * Device Size: 13.5 x 7 x 3 cm 2215 -* Device Weight: 105g 2664 +* Device Weight: 105 g 2216 2216 * Package Size / pcs : 14.5 x 8 x 5 cm 2217 -* Weight / pcs : 170g 2666 +* Weight / pcs : 170 g 2218 2218 2219 2219 = 10. Support = 2220 2220 2221 - 2222 2222 * ((( 2223 -Support is providedMonday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in thebefore-mentioned schedule.2671 +Support is available Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time zones, we cannot offer live support. However, your questions will be answered as soon as possible within the aforementioned schedule. 2224 2224 ))) 2225 2225 * ((( 2226 -Provide as much information as possible regarding your enquiry (product models, accuratelydescribeyourproblemandsteps to replicate it etc) and send a mail to [[Support@dragino.cc>>mailto:Support@dragino.cc]]2674 +Please provide as much information as possible regarding your inquiry (e.g., product models, a detailed description of the problem, steps to replicate it, etc.) and send an email to [[support@dragino.cc>>mailto:support@dragino.cc]] 2227 2227 2228 - 2229 2229 2230 2230 ))) 2231 2231 2232 2232 = 11. Reference = 2233 2233 2234 - 2235 2235 * LT-22222-L: [[http:~~/~~/www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html>>url:http://www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html]] 2236 2236 * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]] 2237 2237 * [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]
- dragino-ttn-te.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +273.8 KB - Content
- integration-details.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +463.9 KB - Content
- lorawan-nw.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +250.6 KB - Content
- lt-22222-device-overview.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +497.2 KB - Content
- lt-22222-join-network.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +340.6 KB - Content
- lt-22222-l-abp.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +321.4 KB - Content
- lt-22222-l-dev-repo-p1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +391.8 KB - Content
- lt-22222-l-dev-repo-reg-p1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +391.7 KB - Content
- lt-22222-l-dev-repo-reg-p2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +319.1 KB - Content
- lt-22222-l-manually-p1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +306.6 KB - Content
- lt-22222-l-manually-p2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +279.1 KB - Content
- lt-22222-ul-payload-decoded.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +48.7 KB - Content
- lt-22222-ul-payload-fmt.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +438.6 KB - Content
- message-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +20.1 KB - Content
- thingseye-events.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +530.6 KB - Content
- thingseye-io-step-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +191.8 KB - Content
- thingseye-io-step-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +260.3 KB - Content
- thingseye-io-step-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +336.6 KB - Content
- thingseye-io-step-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +361.1 KB - Content
- thingseye-io-step-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +292.1 KB - Content
- thingseye-io-step-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +203.8 KB - Content
- thingseye-json.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +554.8 KB - Content
- thingseye.io_integrationsCenter_integrations-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +469.3 KB - Content
- thingseye.io_integrationsCenter_integrations.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +302.3 KB - Content
- tts-mqtt-integration.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +306.4 KB - Content
- usb-ttl-programming.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +462.9 KB - Content