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 (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 21 removed)
- Screenshot 2024-11-23 at 18.27.11.png
- Screenshot 2024-12-08 193946.png
- dragino-lorawan-nw-lt-22222-n.jpg
- 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-joining.png
- lt-22222-l-js-custom-payload-formatter.png
- lt-22222-ul-payload-decoded.png
- lt-22222-ul-payload-fmt.png
- lt33222-l.jpg
- message-1.png
- thingseye-events.png
- thingseye-json.png
- thingseye.io_integrationsCenter_integrations-2.png
- thingseye.io_integrationsCenter_integrations.png
- usb-ttl-audio-jack-connection.jpg
- usb-ttl-programming.png
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -LT-22222-L -- LoRa I /O Controller User Manual1 +LT-22222-L -- LoRa IO Controller User Manual - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.pradeeka - Content
-
... ... @@ -17,19 +17,14 @@ 17 17 18 18 19 19 20 -= 1. 20 += 1.Introduction = 21 21 22 22 == 1.1 What is the LT-22222-L I/O Controller? == 23 23 24 - 25 25 ((( 26 26 ((( 27 -{{info}} 28 -**This manual is also applicable to the LT-33222-L.** 29 -{{/info}} 26 +The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN device designed to provide seamless wireless long-range connectivity with various I/O options, including analog current and voltage inputs, digital inputs and outputs, and relay outputs. 30 30 31 -The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN end device designed to provide seamless wireless long-range connectivity with various I/O options, including analog current and voltage inputs, digital inputs and outputs, and relay outputs. 32 - 33 33 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. 34 34 ))) 35 35 ))) ... ... @@ -38,53 +38,52 @@ 38 38 With the LT-22222-L I/O Controller, users can transmit data over ultra-long distances with low power consumption using LoRa, a spread-spectrum modulation technique derived from chirp spread spectrum (CSS) technology that operates on license-free ISM bands. 39 39 ))) 40 40 36 +> The LT Series I/O Controllers are designed for easy, low-cost installation on LoRaWAN networks. 37 + 41 41 ((( 42 42 You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways: 43 43 44 -* If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Stack CommunityNetwork), you can select a network and register the LT-22222-L I/O controller with it.41 +* 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. 45 45 * 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. 46 46 * Setup your own private LoRaWAN network. 44 + 45 +> You can use the Dragino LG308 gateway to expand or create LoRaWAN coverage in your area. 47 47 ))) 48 48 49 49 ((( 50 - 49 +[[image:1653295757274-912.png]] 51 51 52 - Thenetwork diagram below illustrates how the LT-22222-L communicates with a typical LoRaWAN network.51 + 53 53 ))) 54 54 55 -(% class="wikigeneratedid" %) 56 -[[image:lorawan-nw.jpg||height="354" width="900"]] 57 - 58 - 59 59 == 1.2 Specifications == 60 60 61 - 62 62 (% style="color:#037691" %)**Hardware System:** 63 63 64 64 * STM32L072xxxx MCU 65 65 * SX1276/78 Wireless Chip 66 66 * Power Consumption: 67 -** Idle: 4mA@12 V68 -** 20dB Transmit: 34mA@12 V69 -* Operating Temperature: -40 ~~ 85 Degree s, No Dew61 +** Idle: 4mA@12v 62 +** 20dB Transmit: 34mA@12v 63 +* Operating Temperature: -40 ~~ 85 Degree, No Dew 70 70 71 71 (% style="color:#037691" %)**Interface for Model: LT22222-L:** 72 72 73 -* 2 x Digital dual direction Input (Detect High/Low signal, Max: 50 V, or 220Vwith optional external resistor)74 -* 2 x Digital Output (NPN output. Max pull -up voltage 36V,450mA)67 +* 2 x Digital dual direction Input (Detect High/Low signal, Max: 50v, or 220v with optional external resistor) 68 +* 2 x Digital Output (NPN output. Max pull up voltage 36V,450mA) 75 75 * 2 x Relay Output (5A@250VAC / 30VDC) 76 76 * 2 x 0~~20mA Analog Input (res:0.01mA) 77 -* 2 x 0~~30V Analog Input (res:0.01 V)71 +* 2 x 0~~30V Analog Input (res:0.01v) 78 78 * Power Input 7~~ 24V DC. 79 79 80 80 (% style="color:#037691" %)**LoRa Spec:** 81 81 82 82 * Frequency Range: 83 -** Band 1 (HF): 862 ~~ 1020 M Hz84 -** Band 2 (LF): 410 ~~ 528 M Hz77 +** Band 1 (HF): 862 ~~ 1020 Mhz 78 +** Band 2 (LF): 410 ~~ 528 Mhz 85 85 * 168 dB maximum link budget. 86 86 * +20 dBm - 100 mW constant RF output vs. 87 -* +14 dBm high -efficiency PA.81 +* +14 dBm high efficiency PA. 88 88 * Programmable bit rate up to 300 kbps. 89 89 * High sensitivity: down to -148 dBm. 90 90 * Bullet-proof front end: IIP3 = -12.5 dBm. ... ... @@ -100,34 +100,32 @@ 100 100 101 101 == 1.3 Features == 102 102 103 - 104 -* LoRaWAN Class A & Class C modes 97 +* LoRaWAN Class A & Class C protocol 105 105 * Optional Customized LoRa Protocol 106 106 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869 107 107 * AT Commands to change parameters 108 -* Remote lyconfigure parameters via LoRaWANDownlink101 +* Remote configure parameters via LoRa Downlink 109 109 * Firmware upgradable via program port 110 110 * Counting 111 111 112 112 == 1.4 Applications == 113 113 107 +* Smart Buildings & Home Automation 108 +* Logistics and Supply Chain Management 109 +* Smart Metering 110 +* Smart Agriculture 111 +* Smart Cities 112 +* Smart Factory 114 114 115 -* Smart buildings & home automation 116 -* Logistics and supply chain management 117 -* Smart metering 118 -* Smart agriculture 119 -* Smart cities 120 -* Smart factory 121 - 122 122 == 1.5 Hardware Variants == 123 123 124 124 125 -(% border="1" cellspacing=" 3" style="width:510px" %)126 -|(% style="background-color:#4f81bd; color:white; width: 94px" %)**Model**|(% style="background-color:#4f81bd; color:white; width:172px" %)**Photo**|(% style="background-color:#4f81bd; color:white; width:244px" %)**Description**127 -|(% style="width: 94px" %)**LT-22222-L**|(% style="width:172px" %)(((117 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %) 118 +|(% 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** 119 +|(% style="width:103px" %)**LT22222-L**|(% style="width:131px" %)((( 128 128 (% style="text-align:center" %) 129 -[[image: lt33222-l.jpg||height="110" width="95"]]130 -)))|(% style="width: 256px" %)(((121 +[[image:image-20230424115112-1.png||height="106" width="58"]] 122 +)))|(% style="width:334px" %)((( 131 131 * 2 x Digital Input (Bi-direction) 132 132 * 2 x Digital Output 133 133 * 2 x Relay Output (5A@250VAC / 30VDC) ... ... @@ -136,220 +136,141 @@ 136 136 * 1 x Counting Port 137 137 ))) 138 138 139 -= 2. Assembling the device =131 += 2. Assembling the Device = 140 140 141 -== 2.1 Connectingthe antenna ==133 +== 2.1 What is included in the package? == 142 142 135 +The package includes the following items: 143 143 144 -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. 137 +* 1 x LT-22222-L I/O Controller 138 +* 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L 139 +* 1 x bracket for wall mounting 140 +* 1 x programming cable 145 145 146 -{{warning}} 147 -**Warning! Do not power on the device without connecting the antenna.** 148 -{{/warning}} 142 +Attach the LoRaWAN antenna to the connector labeled **ANT** (located on the top right side of the device, next to the upper terminal block). Secure the antenna by tightening it clockwise. 149 149 150 - 151 151 == 2.2 Terminals == 152 152 146 +Upper screw terminal block (from left to right): 153 153 154 -The LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals. 148 +(% style="width:634px" %) 149 +|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function 150 +|(% style="width:295px" %)GND|(% style="width:338px" %)Ground 151 +|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage 152 +|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2 153 +|(% style="width:295px" %)AVI1|(% style="width:338px" %)Analog Voltage Input Terminal 1 154 +|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2 155 +|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1 155 155 156 - **Upper screw terminal block (from left to right):**157 +Lower screw terminal block (from left to right): 157 157 158 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:381px" %) 159 -|=(% style="width: 139px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 242px;background-color:#4f81bd;color:white" %)Function 160 -|(% style="width:139px" %)GND|(% style="width:242px" %)Ground 161 -|(% style="width:139px" %)VIN|(% style="width:242px" %)Input Voltage 162 -|(% style="width:139px" %)AVI2|(% style="width:242px" %)Analog Voltage Input Terminal 2 163 -|(% style="width:139px" %)AVI1|(% style="width:242px" %)Analog Voltage Input Terminal 1 164 -|(% style="width:139px" %)ACI2|(% style="width:242px" %)Analog Current Input Terminal 2 165 -|(% style="width:139px" %)ACI1|(% style="width:242px" %)Analog Current Input Terminal 1 159 +(% style="width:633px" %) 160 +|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function 161 +|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1 162 +|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1 163 +|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2 164 +|(% style="width:296px" %)RO2-1|(% style="width:334px" %)Relay Output 2 165 +|(% style="width:296px" %)DI2+|(% style="width:334px" %)Digital Input 2 166 +|(% style="width:296px" %)DI2-|(% style="width:334px" %)Digital Input 2 167 +|(% style="width:296px" %)DI1+|(% style="width:334px" %)Digital Input 1 168 +|(% style="width:296px" %)DI1-|(% style="width:334px" %)Digital Input 1 169 +|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2 170 +|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1 166 166 167 - **Lowerscrewterminal block (from left toright):**172 +== 2.3 Powering == 168 168 169 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:253px" %) 170 -|=(% style="width: 125px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 128px;background-color:#4f81bd;color:white" %)Function 171 -|(% style="width:125px" %)RO1-2|(% style="width:128px" %)Relay Output 1 172 -|(% style="width:125px" %)RO1-1|(% style="width:128px" %)Relay Output 1 173 -|(% style="width:125px" %)RO2-2|(% style="width:128px" %)Relay Output 2 174 -|(% style="width:125px" %)RO2-1|(% style="width:128px" %)Relay Output 2 175 -|(% style="width:125px" %)DI2+|(% style="width:128px" %)Digital Input 2 176 -|(% style="width:125px" %)DI2-|(% style="width:128px" %)Digital Input 2 177 -|(% style="width:125px" %)DI1+|(% style="width:128px" %)Digital Input 1 178 -|(% style="width:125px" %)DI1-|(% style="width:128px" %)Digital Input 1 179 -|(% style="width:125px" %)DO2|(% style="width:128px" %)Digital Output 2 180 -|(% style="width:125px" %)DO1|(% style="width:128px" %)Digital Output 1 174 +The LT-22222-L I/O Controller can be powered by a 7–24V DC power source. Connect the power supply’s positive wire to the VIN screw terminal and the negative wire to the GND screw terminal. The power indicator (PWR) LED will turn on when the device is properly powered. 181 181 182 182 183 - == 2.3 ConnectingLT-22222-L to a Power Source ==177 +[[image:1653297104069-180.png]] 184 184 185 185 186 - TheLT-22222-L I/O Controller can be powered by a **7–24V DC** power source.Connect yourpowersupply’s **positive wire** to the **VIN**andthe **negative wire** tothe **GND** screw terminals.The power indicator **(PWR) LED** will turn on whenthe device is properly powered.180 += 3. Operation Mode = 187 187 188 -{{warning}} 189 -**We recommend that you power on the LT-22222-L after adding its registration information to the LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.** 190 -{{/warning}} 182 +== 3.1 How does it work? == 191 191 184 +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. 192 192 193 - [[image:1653297104069-180.png]]186 +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. 194 194 188 +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. 195 195 196 -= 3. Registering LT-22222-Lwith a LoRaWANNetworkServer =190 +== 3.2 Registering with a LoRaWAN network server == 197 197 192 +The diagram below shows how the LT-22222-L connects to a typical LoRaWAN network. 198 198 199 - The LT-22222-L supports both OTAA (Over-the-Air Activation) and ABP (Activation By Personalization)methods toactivatewith a LoRaWAN Network Server. However, OTAA is themost secure method foractivatinga device with a LoRaWAN Network Server. OTAA regenerates session keys upon initial registration and regenerates new session keys after any subsequent reboots. By default, the LT-22222-L is configuredtooperatein LoRaWAN Class C mode.194 +[[image:image-20220523172350-1.png||height="266" width="864"]] 200 200 201 - 202 202 === 3.2.1 Prerequisites === 203 203 198 +Make sure you have the device registration information such as DevEUI, AppEUI, and AppKey with you. The registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference. 204 204 205 -The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey that allows you to register it with a LoRaWAN network. These registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference. 206 - 207 207 [[image:image-20230425173427-2.png||height="246" width="530"]] 208 208 209 -{{info}} 210 -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. 211 -{{/info}} 212 - 213 213 The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers. 214 214 204 +=== 3.2.2 The Things Stack Sandbox (TTSS) === 215 215 216 -=== 3.2.2 The Things Stack === 206 +* Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account. 207 +* Create an application if you do not have one yet. 208 +* Register LT-22222-L with that application. Two registration options available: 217 217 210 +==== Using the LoRaWAN Device Repository: ==== 218 218 219 -This section guides you through how to register your LT-22222-L with The Things Stack Sandbox. 220 - 221 -{{info}} 222 -The Things Stack Sandbox was formally called The Things Stack Community Edition. 223 -{{/info}} 224 - 225 - 226 -The network diagram below illustrates the connection between the LT-22222-L and The Things Stack, as well as how the data can be integrated with the ThingsEye IoT platform. 227 - 228 - 229 -[[image:dragino-lorawan-nw-lt-22222-n.jpg||height="374" width="1400"]] 230 - 231 -{{info}} 232 - You can use a LoRaWAN gateway, such as the [[Dragino LPS8N>>https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], to expand or create LoRaWAN coverage in your area. 233 -{{/info}} 234 - 235 - 236 -==== 3.2.2.1 Setting up ==== 237 - 238 - 239 -* Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet. 240 -* Log in to your The Things Stack Sandbox account. 241 -* Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs). 242 -* Go to your application's page and click on the **End devices** in the left menu. 243 -* On the End devices page, click on **+ Register end device**. Two registration options are available: 244 - 245 - 246 -==== 3.2.2.2 Using the LoRaWAN Device Repository ==== 247 - 248 - 212 +* Go to your application and click on the **Register end device** button. 249 249 * On the **Register end device** page: 250 -** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**. 251 -** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists. 252 -*** **End device brand**: Dragino Technology Co., Limited 253 -*** **Model**: LT22222-L I/O Controller 254 -*** **Hardware ver**: Unknown 255 -*** **Firmware ver**: 1.6.0 256 -*** **Profile (Region)**: Select the region that matches your device. 257 -** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 214 +** Select the option **Select the end device in the LoRaWAN Device Repository**. 215 +** Choose the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)**. 216 +** Select the **Frequency plan** that matches with your device. 258 258 259 -[[image:lt-22222-l-dev-repo-reg-p1.png]] 218 +[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]] 260 260 261 - 262 -* Register end device page continued... 263 -** 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'. 264 -** In the **DevEUI** field, enter the **DevEUI**. 265 -** In the **AppKey** field, enter the **AppKey.** 266 -** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 220 +* 221 +** Enter the **AppEUI** in the **JoinEUI** field and click **Confirm** button. 222 +** Enter the **DevEUI** in the **DevEUI** field. 223 +** Enter the **AppKey** in the **AppKey** field. 224 +** In the **End device ID** field, enter a unique name within this application for your LT-22222-N. 267 267 ** Under **After registration**, select the **View registered end device** option. 268 268 269 -[[image:lt-22222-l-dev-repo-reg-p2.png]] 227 +[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]] 270 270 229 +==== Entering device information manually: ==== 271 271 272 -==== 3.2.2.3 Adding device manually ==== 273 - 274 - 275 275 * On the **Register end device** page: 276 -** Select the option**Enter end device specifies manually**under**Input method**.277 -** Select the **Frequency plan** from the **Frequency plan** dropdown list.278 -** Select the **LoRaWAN version** as **LoRaWAN Specification 1.0.3**279 -** Select the **Regional Parameters version** as** RP001 Regional Parameters 1.0.3 revision A**280 -** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the hiddensection.281 -** Select the option**Over the air activation (OTAA)** underthe**Activation mode.**282 -** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.232 +** Select the **Enter end device specifies manually** option as the input method. 233 +** Select the **Frequency plan** that matches with your device. 234 +** Select the **LoRaWAN version**. 235 +** Select the **Regional Parameters version**. 236 +** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the section. 237 +** Select **Over the air activation (OTAA)** option under **Activation mode** 238 +** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities**. 283 283 284 -[[image:lt-22222-l-manually-p1.png]] 240 +[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]] 285 285 286 286 287 -* Register end device page continued... 288 -** 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**//' 289 -** In the **DevEUI** field, enter the **DevEUI**. 290 -** In the **AppKey** field, enter the **AppKey**. 291 -** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 292 -** Under **After registration**, select the **View registered end device** option. 293 -** Click the **Register end device** button. 243 +* Enter **AppEUI** in the **JoinEUI** field and click **Confirm** button. 244 +* Enter **DevEUI** in the **DevEUI** field. 245 +* Enter **AppKey** in the **AppKey** field. 246 +* In the **End device ID** field, enter a unique name within this application for your LT-22222-N. 247 +* Under **After registration**, select the **View registered end device** option. 294 294 295 -[[image:lt-22222-l-manually-p2.png]] 249 +[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]] 296 296 297 297 298 - Youwill benavigatedto the **Device overview** page.252 +==== Joining ==== 299 299 254 +Click on **Live Data** in the left navigation. Then, power on the device, and it will join The Things Stack Sandbox. You can see the join request, join accept, followed by uplink messages form the device showing in the Live Data panel. 300 300 301 -[[image: lt-22222-device-overview.png]]256 +[[image:1653298044601-602.png||height="405" width="709"]] 302 302 303 303 304 -== ==3.2.2.4 Joining====259 +== 3.3 Uplink Payload formats == 305 305 306 306 307 - On theDevice'spage,clickon**Live data**tab.TheLivedatapanel foryourdevicewilldisplay.262 +The LT-22222-L has 5 working modes. It also has an interrupt/trigger mode for different type applications that can be used together with all the working modes as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands. 308 308 309 - Now power on your LT-22222-L. The**TXLED**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 beonfor **5 seconds**afterjoining thenetwork. In the **Live data** panel,youcanseethe**join-request**and**join-accept**messagesexchangedbetweenthedeviceandthenetwork server.264 +* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2 x ACI + 2AVI + DI + DO + RO 310 310 311 - 312 -[[image:lt-22222-l-joining.png]] 313 - 314 - 315 -==== 3.2.2.5 Uplinks ==== 316 - 317 - 318 -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. 319 - 320 -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. 321 - 322 -[[image:lt-22222-ul-payload-decoded.png]] 323 - 324 - 325 -If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > your application > End devices** > **your end device** > **Payload formatters** > **Uplink**. Then select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes. 326 - 327 -{{info}} 328 -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. 329 -{{/info}} 330 - 331 -[[image:lt-22222-ul-payload-fmt.png]] 332 - 333 - 334 -We also have a payload formatter that resolves some decoding issues present in the Device Repository formatter. You can add it under the Custom JavaScript formatter. It can be found [[here>>https://github.com/dragino/dragino-end-node-decoder/blob/main/LT22222-L/v1.6_decoder_ttn%20.txt]]: 335 - 336 -(% class="wikigeneratedid" %) 337 -[[image:lt-22222-l-js-custom-payload-formatter.png]] 338 - 339 - 340 -==== 3.2.2.6 Downlinks ==== 341 - 342 - 343 -When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**. 344 - 345 - 346 -== 3.3 Working Modes and Uplink Payload formats == 347 - 348 - 349 -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. 350 - 351 -* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO 352 - 353 353 * (% style="color:blue" %)**MOD2**(%%): Double DI Counting + DO + RO 354 354 355 355 * (% style="color:blue" %)**MOD3**(%%): Single DI Counting + 2 x ACI + DO + RO ... ... @@ -360,21 +360,12 @@ 360 360 361 361 * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5 362 362 363 -The uplink messages are sent over LoRaWAN FPort=2. By default, an uplink message is sent every 10 minutes. 364 - 365 - 366 366 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 367 367 368 368 369 369 ((( 370 -This is t he defaultmode.280 +The uplink payload is 11 bytes long. Uplink packets are sent over LoRaWAN FPort=2. By default, one uplink is sent every 10 minutes. (% style="display:none" %) 371 371 372 -The uplink payload is 11 bytes long. 373 - 374 -(% style="color:red" %)**Note:The maximum count depends on the bytes number of bytes. 375 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 376 -It starts counting again when it reaches the maximum value.**(% style="display:none" wfd-invisible="true" %) 377 - 378 378 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 379 379 |(% 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** 380 380 |Value|((( ... ... @@ -385,13 +385,13 @@ 385 385 ACI1 Current 386 386 )))|((( 387 387 ACI2 Current 388 -)))| **DIDORO***|(((292 +)))|DIDORO*|((( 389 389 Reserve 390 390 )))|MOD 391 391 ))) 392 392 393 393 ((( 394 -(% style="color:#4f81bd" %)*** DIDORO**(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, anditssizeis1 bytelongas shown below.298 +(% style="color:#4f81bd" %)*** DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below. 395 395 396 396 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 397 397 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** ... ... @@ -398,9 +398,9 @@ 398 398 |RO1|RO2|--DI3--|DI2|DI1|--DO3--|DO2|DO1 399 399 ))) 400 400 401 -* RO is for therelay. ROx=1:CLOSED, ROx=0 alwaysOPEN.402 -* DI is for digital input. DIx=1: HIGHorFLOATING, DIx=0:LOW.403 -* DO is for reverse digital output. DOx=1: LOW, DOx=0:HIGHorFLOATING.305 +* RO is for relay. ROx=1 : closed, ROx=0 always open. 306 +* DI is for digital input. DIx=1: high or floating, DIx=0: low. 307 +* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating. 404 404 405 405 (% style="color:red" %)**Note: DI3 and DO3 bits are not valid for LT-22222-L** 406 406 ... ... @@ -417,42 +417,36 @@ 417 417 418 418 ACI2 channel current is 0x1300/1000=4.864mA 419 419 420 -The last byte 0xAA= **10101010**(b) means,324 +The last byte 0xAA= 10101010(b) means, 421 421 422 -* [1] TheRO1 relay channel isCLOSED, and the RO1 LED is ON.423 -* [0] TheRO2 relay channel isOPEN, andtheRO2 LED is OFF.424 -* **[1] DI3 - not used for LT-22222-L.**425 -* [0] DI2 channel input is LOW, and the DI2 LED is OFF.326 +* [1] RO1 relay channel is closed, and the RO1 LED is ON. 327 +* [0] RO2 relay channel is open, and RO2 LED is OFF. 328 +* [1] DI3 - not used for LT-22222-L. 329 +* [0] DI2 channel input is low, and the DI2 LED is OFF. 426 426 * [1] DI1 channel input state: 427 -** DI1 is FLOATINGwhenno sensor isconnected between DI1+andDI1-.428 -** DI1 is HIGHwhena sensor isconnected between DI1-andDI1+ and the sensor is ACTIVE.331 +** DI1 is floating when there is no load between DI1 and V+. 332 +** DI1 is high when there is load between DI1 and V+. 429 429 ** DI1 LED is ON in both cases. 430 -* **[0] DO3 - not used for LT-22222-L.** 431 -* [1] DO2 channel output is LOW, and the DO2 LED is ON. 334 +* [0] DO3 channel output state: 335 +** DO3 is float in case no load between DO3 and V+. 336 +** DO3 is high in case there is load between DO3 and V+. 337 +** DO3 LED is OFF in both case 338 +* [1] DO2 channel output is low, and the DO2 LED is ON. 432 432 * [0] DO1 channel output state: 433 -** DO1 is FLOATINGwhen there is no load between DO1 and V+.434 -** DO1 is HIGHandthere isaload between DO1 and V+.435 -** DO1 LED is OFF in both case s.340 +** DO1 is floating when there is no load between DO1 and V+. 341 +** DO1 is high when there is load between DO1 and V+. 342 +** DO1 LED is OFF in both case. 436 436 437 -Reserve = 0 438 - 439 -MOD = 1 440 - 441 - 442 442 === 3.3.2 AT+MOD~=2, (Double DI Counting) === 443 443 444 444 445 445 ((( 446 -**For LT-22222-L**: In this mode, **DI1 and DI2** are used as counting pins. 348 +**For LT-22222-L**: In this mode, the **DI1 and DI2** are used as counting pins. 447 447 ))) 448 448 449 449 ((( 450 450 The uplink payload is 11 bytes long. 451 451 452 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is. 453 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 454 -It starts counting again when it reaches the maximum value.** 455 - 456 456 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 457 457 |(% 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** 458 458 |Value|COUNT1|COUNT2 |DIDORO*|((( ... ... @@ -461,17 +461,17 @@ 461 461 ))) 462 462 463 463 ((( 464 -(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2,FIRST, Reserve, Reserve,DO3, DO2 and DO1, anditssizeis1 bytelongas shown below.362 +(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination for RO1, RO2, DO3, DO2 and DO1, for a total of 1 byte, as shown below. 465 465 466 466 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 467 467 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 468 468 |RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1 469 469 470 -* RO is for therelay. ROx=1:CLOSED, ROx=0 alwaysOPEN.368 +* RO is for relay. ROx=1 : closed, ROx=0 always open. 471 471 ))) 472 472 473 473 * FIRST: Indicates that this is the first packet after joining the network. 474 -* DO is for reverse digital output. DOx=1: LOW, DOx=0:HIGHorFLOATING.372 +* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating. 475 475 476 476 ((( 477 477 (% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L** ... ... @@ -480,7 +480,7 @@ 480 480 ))) 481 481 482 482 ((( 483 -**To activate this mode, run the following AT command s:**381 +**To activate this mode, please run the following AT command:** 484 484 ))) 485 485 486 486 ((( ... ... @@ -501,17 +501,17 @@ 501 501 ((( 502 502 **For LT22222-L:** 503 503 504 -(% style="color:blue" %)**AT+TRIG1=0,100**(%%)** (set sthe DI1 port to trigger on aLOWlevel.The valid signal duration is 100ms) **402 +(% style="color:blue" %)**AT+TRIG1=0,100**(%%)** (set the DI1 port to trigger on a low level, the valid signal duration is 100ms) ** 505 505 506 -(% style="color:blue" %)**AT+TRIG1=1,100**(%%)** (set sthe DI1 port to trigger on aHIGHlevel.The valid signal duration is 100ms) **404 +(% style="color:blue" %)**AT+TRIG1=1,100**(%%)** (set the DI1 port to trigger on a high level, the valid signal duration is 100ms) ** 507 507 508 -(% style="color:blue" %)**AT+TRIG2=0,100**(%%)** (set sthe DI2 port to trigger on aLOWlevel.The valid signal duration is 100ms) **406 +(% style="color:blue" %)**AT+TRIG2=0,100**(%%)** (set the DI2 port to trigger on a low level, the valid signal duration is 100ms) ** 509 509 510 -(% style="color:blue" %)**AT+TRIG2=1,100**(%%)** (set sthe DI2 port to trigger on aHIGHlevel.The valid signal duration is 100ms) **408 +(% style="color:blue" %)**AT+TRIG2=1,100**(%%)** (set the DI2 port to trigger on a high level, the valid signal duration is 100ms) ** 511 511 512 -(% style="color:blue" %)**AT+SETCNT=1,60**(%%)** ( setsthe COUNT1 value to 60)**410 +(% style="color:blue" %)**AT+SETCNT=1,60**(%%)** (Set the COUNT1 value to 60)** 513 513 514 -(% style="color:blue" %)**AT+SETCNT=2,60 setsthe COUNT2 value to 60)**412 +(% style="color:blue" %)**AT+SETCNT=2,60**(%%)** (Set the COUNT2 value to 60)** 515 515 ))) 516 516 517 517 ... ... @@ -518,10 +518,6 @@ 518 518 === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI === 519 519 520 520 521 -(% style="color:red" %)**Note: The maximum count depends on the bytes it is. 522 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 523 -It starts counting again when it reaches the maximum value.** 524 - 525 525 **LT22222-L**: In this mode, the DI1 is used as a counting pin. 526 526 527 527 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) ... ... @@ -533,7 +533,7 @@ 533 533 )))|DIDORO*|Reserve|MOD 534 534 535 535 ((( 536 -(% 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.430 +(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below. 537 537 538 538 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 539 539 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** ... ... @@ -540,17 +540,17 @@ 540 540 |RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1 541 541 ))) 542 542 543 -* RO is for therelay. ROx=1: closed, ROx=0 always open.437 +* RO is for relay. ROx=1 : closed, ROx=0 always open. 544 544 * FIRST: Indicates that this is the first packet after joining the network. 545 545 * DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating. 546 546 547 547 ((( 548 -(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L.**442 +(% style="color:red" %)**Note: DO3 is not valid for LT-22222-L.** 549 549 ))) 550 550 551 551 552 552 ((( 553 -**To activate this mode, run the following AT command s:**447 +**To activate this mode, please run the following AT command:** 554 554 ))) 555 555 556 556 ((( ... ... @@ -565,7 +565,7 @@ 565 565 ((( 566 566 AT Commands for counting: 567 567 568 -The AT Commands for counting are similar to the[[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.462 +The AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]. Use only the commands that match 'DI'. 569 569 ))) 570 570 571 571 ... ... @@ -572,11 +572,6 @@ 572 572 === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting === 573 573 574 574 575 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is. 576 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 577 -It starts counting again when it reaches the maximum value.** 578 - 579 - 580 580 ((( 581 581 **LT22222-L**: In this mode, the DI1 is used as a counting pin. 582 582 ))) ... ... @@ -592,7 +592,7 @@ 592 592 ))) 593 593 594 594 ((( 595 -(% 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.484 +(% style="color:#4f81bd" %)**DIDORO **(%%)is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below. 596 596 597 597 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 598 598 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** ... ... @@ -599,18 +599,18 @@ 599 599 |RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1 600 600 ))) 601 601 602 -* RO is for therelay. ROx=1: closed, ROx=0 always open.491 +* RO is for relay. ROx=1 : closed, ROx=0 always open. 603 603 * FIRST: Indicates that this is the first packet after joining the network. 604 604 * DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating. 605 605 606 606 ((( 607 -(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L.**496 +(% style="color:red" %)**Note: DO3 is not valid for LT-22222-L.** 608 608 609 609 610 610 ))) 611 611 612 612 ((( 613 -**To activate this mode, run the following AT command s:**502 +**To activate this mode, please run the following AT command:** 614 614 ))) 615 615 616 616 ((( ... ... @@ -623,19 +623,19 @@ 623 623 ))) 624 624 625 625 ((( 626 -AT Commands for counting are similar to the[[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.515 +Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]. 627 627 ))) 628 628 629 629 ((( 630 630 **In addition to that, below are the commands for AVI1 Counting:** 631 631 632 -(% style="color:blue" %)**AT+SETCNT=3,60 SetsAVI1Count to 60)**521 +(% style="color:blue" %)**AT+SETCNT=3,60**(%%)** (set AVI Count to 60)** 633 633 634 -(% style="color:blue" %)**AT+VOLMAX=20000 theAVI1 voltageishigher than VOLMAX (20000mV =20V),thecounter increasesby1)**523 +(% style="color:blue" %)**AT+VOLMAX=20000**(%%)** (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 635 635 636 -(% style="color:blue" %)**AT+VOLMAX=20000,0 theAVI1 voltageislower than VOLMAX (20000mV =20V), counter increasesby1)**525 +(% style="color:blue" %)**AT+VOLMAX=20000,0**(%%)** (If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)** 637 637 638 -(% style="color:blue" %)**AT+VOLMAX=20000,1 theAVI1 voltageishigher than VOLMAX (20000mV =20V), counter increasesby1)**527 +(% style="color:blue" %)**AT+VOLMAX=20000,1**(%%)** (If AVI1 voltage higer than VOLMAX (20000mV =20v), counter increase 1)** 639 639 ))) 640 640 641 641 ... ... @@ -642,13 +642,8 @@ 642 642 === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI === 643 643 644 644 645 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is. 646 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 647 -It starts counting again when it reaches the maximum value.** 534 +**LT22222-L**: This mode the DI1 is used as a counting pin. 648 648 649 - 650 -**LT22222-L**: In this mode, the DI1 is used as a counting pin. 651 - 652 652 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 653 653 |(% 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** 654 654 |Value|((( ... ... @@ -662,25 +662,25 @@ 662 662 )))|MOD 663 663 664 664 ((( 665 -(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1,for atotalof1,asshownbelow.549 +(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below 666 666 667 667 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 668 -|**bit 552 +|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 669 669 |RO1|RO2|FIRST|Reserve|Reserve|DO3|DO2|DO1 670 670 ))) 671 671 672 -* RO is for therelay. ROx=1: closed, ROx=0 always open.673 -* FIRST: Indicate sthat this is the first packet after joiningthenetwork.556 +* RO is for relay. ROx=1 : close, ROx=0 always open. 557 +* FIRST: Indicate this is the first packet after join network. 674 674 * ((( 675 -DO is for reverse digital output. DOx=1: output low, DOx=0: high or float ing.559 +DO is for reverse digital output. DOx=1: output low, DOx=0: high or float. 676 676 ))) 677 677 678 678 ((( 679 -(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L.**563 +(% style="color:red" %)**Note: DO3 is not valid for LT-22222-L.** 680 680 ))) 681 681 682 682 ((( 683 -**To activate this mode,run the following AT commands:**567 +**To use this mode, please run:** 684 684 ))) 685 685 686 686 ((( ... ... @@ -693,33 +693,29 @@ 693 693 ))) 694 694 695 695 ((( 696 -Other AT Commands for counting are similar to the[[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.580 +Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]. 697 697 ))) 698 698 699 699 700 -=== 3.3.6 AT+ADDMOD~=6 (Trigger Mode, Optional) === 584 +=== 3.3.6 AT+ADDMOD~=6. (Trigger Mode, Optional) === 701 701 702 702 703 -(% style="color:#4f81bd" %)**This mode is optional andintendedfor trigger purposes. It canoperate__alongside__with other modes.**587 +(% style="color:#4f81bd" %)**This mode is an optional mode for trigger purpose. It can run together with other mode.** 704 704 705 -For example, if you configurethefollowingcommands:589 +For example, if user has configured below commands: 706 706 707 -* **AT+MOD=1 ** **~-~->** Sets thedefaultworking mode708 -* **AT+ADDMOD6=1** **~-~->** Enable striggermode591 +* **AT+MOD=1 ** **~-~->** The normal working mode 592 +* **AT+ADDMOD6=1** **~-~->** Enable trigger 709 709 710 - TheLT-22222-Lwillcontinuouslymonitor AV1,AV2,AC1, andAC2 every 5 seconds.Itwill send uplink packets in two cases:594 +LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases: 711 711 712 -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. 713 -1. ((( 714 -Trigger uplink: sent when a trigger condition is met. In this case, LT will send two packets 596 +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 597 +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.** 715 715 716 -* The first uplink uses the payload specified in trigger mode (MOD=6). 717 -* The second packet uses the normal mode payload (MOD=1 as set above). Both are (% style="color:#4f81bd" %)**confirmed uplinks.** 718 -))) 599 +(% style="color:#037691" %)**AT Command to set Trigger Condition**: 719 719 720 -(% style="color:#037691" %)**AT Commands to set Trigger Conditions**: 721 721 722 -(% style="color:#4f81bd" %)**Trigger base don voltage**:602 +(% style="color:#4f81bd" %)**Trigger base on voltage**: 723 723 724 724 Format: AT+AVLIM=<AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH> 725 725 ... ... @@ -726,25 +726,27 @@ 726 726 727 727 **Example:** 728 728 729 -AT+AVLIM=3000,6000,0,2000 ( triggers an uplink if AVI1 voltageislower than 3Vor higher than 6V,orifAV2 voltage is higher than 2V)609 +AT+AVLIM=3000,6000,0,2000 (If AVI1 voltage lower than 3v or higher than 6v. or AV2 voltage is higher than 2v, LT will trigger Uplink) 730 730 731 -AT+AVLIM=5000,0,0,0 ( triggers an uplink if AVI1 voltage lower than 5V.Use0 forparametersthatarenotinuse)611 +AT+AVLIM=5000,0,0,0 (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore) 732 732 733 733 734 -(% style="color:#4f81bd" %)**Trigger based on current**: 735 735 615 +(% style="color:#4f81bd" %)**Trigger base on current**: 616 + 736 736 Format: AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH> 737 737 738 738 739 739 **Example:** 740 740 741 -AT+ACLIM=10000,15000,0,0 ( triggers an uplink if AC1currentislower than 10mA or higher than 15mA)622 +AT+ACLIM=10000,15000,0,0 (If ACI1 voltage lower than 10mA or higher than 15mA, trigger an uplink) 742 742 743 743 744 -(% style="color:#4f81bd" %)**Trigger based on DI status**: 745 745 746 - DIstatustriggersFlag.626 +(% style="color:#4f81bd" %)**Trigger base on DI status**: 747 747 628 +DI status trigger Flag. 629 + 748 748 Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG > 749 749 750 750 ... ... @@ -753,40 +753,41 @@ 753 753 AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 754 754 755 755 756 -(% style="color:#037691" %)** LoRaWANDownlink CommandsforSettingtheTrigger Conditions:**638 +(% style="color:#037691" %)**Downlink Command to set Trigger Condition:** 757 757 758 - **Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**640 +Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 759 759 760 - **Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4642 +Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 761 761 762 - AA: TypeCode for this downlink Command:644 + AA: Code for this downlink Command: 763 763 764 - xx: **0**: Limit for AV1 and AV2;**1**: limit for AC1 and AC2;**2**:DI1andDI2 trigger enable/disable.646 + xx: 0: Limit for AV1 and AV2; 1: limit for AC1 and AC2 ; 2 DI1, DI2 trigger enable/disable 765 765 766 - yy1 yy1: AC1 or AV1 LOWlimit or DI1/DI2 trigger status.648 + yy1 yy1: AC1 or AV1 low limit or DI1/DI2 trigger status. 767 767 768 - yy2 yy2: AC1 or AV1 HIGHlimit.650 + yy2 yy2: AC1 or AV1 high limit. 769 769 770 - yy3 yy3: AC2 or AV2 LOWlimit.652 + yy3 yy3: AC2 or AV2 low limit. 771 771 772 - Yy4 yy4: AC2 or AV2 HIGHlimit.654 + Yy4 yy4: AC2 or AV2 high limit. 773 773 774 774 775 -**Example 657 +**Example1**: AA 00 13 88 00 00 00 00 00 00 776 776 777 -Same as AT+AVLIM=5000,0,0,0 ( triggers an uplink if AVI1 voltageislower than 5V.Use0s forparametersthatarenotinuse)659 +Same as AT+AVLIM=5000,0,0,0 (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore) 778 778 779 779 780 -**Example 662 +**Example2**: AA 02 01 00 781 781 782 -Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 664 +Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 783 783 784 784 667 + 785 785 (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:** 786 786 787 -MOD6 Payload: total of11 bytes670 +MOD6 Payload : total 11 bytes payload 788 788 789 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)672 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 790 790 |(% 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** 791 791 |Value|((( 792 792 TRI_A FLAG ... ... @@ -798,10 +798,10 @@ 798 798 MOD(6) 799 799 ))) 800 800 801 -(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if t he trigger is set for this part. Totally 1684 +(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if trigger is set for this part. Totally 1byte as below 802 802 803 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)804 -|**bit 686 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 687 +|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 805 805 |((( 806 806 AV1_LOW 807 807 )))|((( ... ... @@ -820,17 +820,17 @@ 820 820 AC2_HIGH 821 821 ))) 822 822 823 -* Each bit shows if the corresponding trigger has been configured. 706 +* Each bits shows if the corresponding trigger has been configured. 824 824 825 825 **Example:** 826 826 827 -10100000: This means the systemis configuredto use the triggersAV1_LOW and AV2_LOW.710 +10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW 828 828 829 829 830 -(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 713 +(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1byte as below 831 831 832 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)833 -|**bit 715 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 716 +|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 834 834 |((( 835 835 AV1_LOW 836 836 )))|((( ... ... @@ -849,35 +849,35 @@ 849 849 AC2_HIGH 850 850 ))) 851 851 852 -* Each bit shows which status has been trigger edon this uplink.735 +* Each bits shows which status has been trigger on this uplink. 853 853 854 854 **Example:** 855 855 856 -10000000: Theuplink is triggeredby AV1_LOW,indicatingthat thevoltageistoo low.739 +10000000: Means this packet is trigger by AC1_LOW. Means voltage too low. 857 857 858 858 859 859 (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below 860 860 861 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)862 -| (% style="width:50px" %)**bit(% style="width:50px" %)**bit(% style="width:50px" %)**bit(% style="width:50px" %)**bit(% style="width:90px" %)**bit(% style="width:80px" %)**bit(% style="width:90px" %)**bit(% style="width:95px" %)**bit863 -| (% style="width:49px" %)N/A|(% style="width:53px" %)N/A|(% style="width:53px" %)N/A|(% style="width:55px" %)N/A|(% style="width:99px" %)DI2_STATUS|(% style="width:83px" %)DI2_FLAG|(% style="width:98px" %)DI1_STATUS|(% style="width:85px" %)DI1_FLAG744 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 745 +|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 746 +|N/A|N/A|N/A|N/A|DI2_STATUS|DI2_FLAG|DI1_STATUS|DI1_FLAG 864 864 865 -* Each bit shows which status has been trigger edon this uplink.748 +* Each bits shows which status has been trigger on this uplink. 866 866 867 867 **Example:** 868 868 869 -00000111: This means both DI1 and DI2 triggersare enabled,and this packet is trigger by DI1.752 +00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1. 870 870 871 -00000101: This means both DI1 and DI2 triggersare enabled.754 +00000101: Means both DI1 and DI2 trigger are enabled. 872 872 873 873 874 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable d. 0x00: MOD6 is disabled.757 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable. 875 875 876 -Downlink command to poll /requestMOD6 status:759 +Downlink command to poll MOD6 status: 877 877 878 878 **AB 06** 879 879 880 -When device receivesthis command, it will send the MOD6 payload.763 +When device got this command, it will send the MOD6 payload. 881 881 882 882 883 883 === 3.3.7 Payload Decoder === ... ... @@ -889,559 +889,274 @@ 889 889 ))) 890 890 891 891 892 -== 3.4 Configure LT -22222-Lvia ATCommands or Downlinks==775 +== 3.4 Configure LT via AT or Downlink == 893 893 894 894 895 895 ((( 896 - Youcan configure LT-22222-LI/O Controller via AT Commands or LoRaWAN Downlinks.779 +User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands 897 897 ))) 898 898 899 899 ((( 900 900 ((( 901 -There are two tytes ofcommands:784 +There are two kinds of Commands: 902 902 ))) 903 903 ))) 904 904 905 -* (% style="color:blue" %)**Common commands**(%%):788 +* (% 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]] 906 906 907 -* (% style="color:blue" %)**Sensor -relatedcommands**(%%):790 +* (% style="color:blue" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L. User can see these commands below: 908 908 792 +=== 3.4.1 Common Commands === 909 909 910 -=== 3.4.1 Common commands === 911 911 912 - 913 913 ((( 914 -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. 915 - 916 - 796 +They should be available for each of Dragino Sensors, 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]] 917 917 ))) 918 918 919 -=== 3.4.2 Sensor-related commands === 920 920 800 +=== 3.4.2 Sensor related commands === 921 921 922 - Thesecommandsarespecially designed fortheLT-22222-L. Commandscanbe sentto thedevice using options suchas an AT command or a LoRaWAN downlinkpayload.802 +==== 3.4.2.1 Set Transmit Interval ==== 923 923 924 924 925 - ==== 3.4.2.1SetTransmit/UplinkInterval====805 +Set device uplink interval. 926 926 807 +* (% style="color:#037691" %)**AT Command:** 927 927 928 - Setsthe uplink interval of the device. The default uplink transmission intervalis 10 minutes.809 +(% style="color:blue" %)**AT+TDC=N ** 929 929 930 -(% style="color:#037691" %)**AT command** 931 931 932 -(% border="2" style="width:500px" %) 933 -|**Command**|AT+TDC=<time> 934 -|**Parameters**|**time **: uplink interval in milliseconds 935 -|**Get**|AT+TDC=? 936 -|**Response**|((( 937 -current uplink interval 812 +**Example: **AT+TDC=30000. Means set interval to 30 seconds 938 938 939 -OK 940 -))) 941 -|**Set**|AT+TDC=<time> 942 -|**Response**|OK 943 -|**Example**|((( 944 -AT+TDC=30000 945 945 946 -Sets the uplink interval to **30 seconds** (30000 milliseconds) 947 -))) 815 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x01):** 948 948 949 -(% style="color: #037691"%)**Downlinkpayload**817 +(% style="color:blue" %)**0x01 aa bb cc **(%%)** ~/~/ Same as AT+TDC=0x(aa bb cc)** 950 950 951 -(% border="2" style="width:500px" %) 952 -|**Payload**|((( 953 -<prefix><time> 954 -))) 955 -|**Parameters**|((( 956 -**prefix** : 0x01 957 957 958 -**time** : uplink interval in **seconds**, represented by **3 bytes** in **hexadecimal**. 959 -))) 960 -|**Example**|((( 961 -01 **00 00 1E** 962 962 963 -Set sthe uplinkintervalto**30 seconds**821 +==== 3.4.2.2 Set Work Mode (AT+MOD) ==== 964 964 965 -Conversion: 30 (dec) = 00 00 1E (hex) 966 966 967 -Se e [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30]]824 +Set work mode. 968 968 969 -[[image:Screenshot 2024-11-23 at 18.27.11.png]] 970 -))) 826 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+MOD=N ** 971 971 972 - ====3.4.2.2Set theWorkingMode(AT+MOD) ====828 +**Example**: AT+MOD=2. Set work mode to Double DI counting mode 973 973 830 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A):** 974 974 975 - Setstheworkingmode.832 +(% style="color:blue" %)**0x0A aa **(%%)** ** ~/~/ Same as AT+MOD=aa 976 976 977 -(% style="color:#037691" %)**AT command** 978 978 979 -(% border="2" style="width:500px" %) 980 -|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MOD=<working_mode> 981 -|(% style="width:97px" %)**Parameters**|(% style="width:413px" %)((( 982 -**working_mode** : 983 983 984 - 1=(Defaultmode/factoryset): 2ACI+ 2AVI + DI + DO + RO836 +==== 3.4.2.3 Poll an uplink ==== 985 985 986 -2 = Double DI Counting + DO + RO 987 987 988 - 3=SingleDICounting+2xACI+DO+ RO839 +* (% style="color:#037691" %)**AT Command:**(%%) There is no AT Command to poll uplink 989 989 990 - 4= Single DI Counting+ 1 x VoltageCounting+ DO + RO841 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x08):** 991 991 992 - 5= SingleDI Counting+ 2xAVI+1xACI+DO+ RO843 +(% style="color:blue" %)**0x08 FF **(%%)** **~/~/ Poll an uplink 993 993 994 -6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5 995 -))) 996 -|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=? 997 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 998 -Current working mode 845 +**Example**: 0x08FF, ask device to send an Uplink 999 999 1000 -OK 1001 -))) 1002 -|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode> 1003 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 1004 -Attention:Take effect after ATZ 1005 1005 1006 -OK 1007 -))) 1008 -|(% style="width:97px" %)**Example**|(% style="width:413px" %)((( 1009 -AT+MOD=2 1010 1010 1011 -Sets the device to working mode 2 (Double DI Counting + DO + RO) 1012 -))) 849 +==== 3.4.2.4 Enable Trigger Mode ==== 1013 1013 1014 -(% class="wikigeneratedid" %) 1015 -(% style="color:#037691" %)**Downlink payload** 1016 1016 1017 -(% border="2" style="width:500px" %) 1018 -|(% style="width:98px" %)**Payload**|(% style="width:400px" %)<prefix><working_mode> 1019 -|(% style="width:98px" %)**Parameters**|(% style="width:400px" %)((( 1020 -**prefix** : 0x0A 852 +Use of trigger mode, please check [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1021 1021 1022 -**working_mode** : Working mode, represented by 1 byte in hexadecimal. 1023 -))) 1024 -|(% style="width:98px" %)**Example**|(% style="width:400px" %)((( 1025 -0A **02** 854 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0** 1026 1026 1027 -Sets the device to working mode 2 (Double DI Counting + DO + RO) 1028 -))) 856 +(% style="color:red" %)**1:** (%%)Enable Trigger Mode 1029 1029 1030 - ====3.4.2.3 Requestan uplinkfrom the device ====858 +(% style="color:red" %)**0: **(%%)Disable Trigger Mode 1031 1031 1032 1032 1033 - Requestsanuplink from LT-22222-L. Thententofthe uplinkpayloadvaries based on the device'scurrentworking mode.861 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):** 1034 1034 1035 -(% style="color: #037691" %)**ATcommand**863 +(% style="color:blue" %)**0x0A 06 aa **(%%) ~/~/ Same as AT+ADDMOD6=aa 1036 1036 1037 -There is no AT Command available for this feature. 1038 1038 1039 -(% style="color:#037691" %)**Downlink payload** 1040 1040 1041 -(% border="2" style="width:500px" %) 1042 -|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF 1043 -|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08 1044 -|(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 1045 -08 **FF** 867 +==== 3.4.2.5 Poll trigger settings ==== 1046 1046 1047 -Requests an uplink from LT-22222-L. 1048 -))) 1049 1049 1050 - ==== 3.4.2.4 Enable/DisableTriggerMode====870 +Poll trigger settings 1051 1051 872 +* (% style="color:#037691" %)**AT Command:** 1052 1052 1053 - Enableordisablethetriggermodefor the current working mode (seealso [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).874 +There is no AT Command for this feature. 1054 1054 1055 -(% style="color:#037691" %)** ATCommand**876 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x AB 06):** 1056 1056 1057 -(% border="2" style="width:500px" %) 1058 -|(% style="width:95px" %)**Command**|(% style="width:403px" %)AT+ADDMOD6=<enable/disable trigger_mode> 1059 -|(% style="width:95px" %)**Response**|(% style="width:403px" %) 1060 -|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)((( 1061 -**enable/disable trigger_mode** : 878 +(% style="color:blue" %)**0xAB 06 ** (%%) ~/~/ Poll trigger settings, device will uplink trigger settings once receive this command 1062 1062 1063 -1 = enable trigger mode 1064 1064 1065 -0 = disable trigger mode 1066 -))) 1067 -|(% style="width:95px" %)**Example**|(% style="width:403px" %)((( 1068 -AT+ADDMOD6=1 1069 1069 1070 -Enable trigger mode for the current working mode 1071 -))) 882 +==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ==== 1072 1072 1073 -(% style="color:#037691" %)**Downlink payload** 1074 1074 1075 -(% border="2" style="width:500px" %) 1076 -|(% style="width:97px" %)**Payload**|(% style="width:401px" %)<prefix><enable/disable trigger_mode> 1077 -|(% style="width:97px" %)**Parameters**|(% style="width:401px" %)((( 1078 -**prefix** : 0x0A 06 (two bytes in hexadecimal) 885 +Enable Disable DI1/DI2/DI2 as trigger, 1079 1079 1080 -**enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal. 1081 -))) 1082 -|(% style="width:97px" %)**Example**|(% style="width:401px" %)((( 1083 -0A 06 **01** 887 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >** 1084 1084 1085 -Enable trigger mode for the current working mode 1086 -))) 889 +**Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 1087 1087 1088 -==== 3.4.2.5 Request trigger settings ==== 1089 1089 892 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):** 1090 1090 1091 - Requeststhetriggersettings.894 +(% style="color:blue" %)**0xAA 02 aa bb ** (%%) ~/~/ Same as AT+DTRI=aa,bb 1092 1092 1093 -(% style="color:#037691" %)**AT Command:** 1094 1094 1095 -There is no AT Command available for this feature. 1096 1096 1097 - (% style="color:#037691"%)**DownlinkPayload**898 +==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger ==== 1098 1098 1099 -(% border="2" style="width:500px" %) 1100 -|(% style="width:95px" %)**Payload**|(% style="width:403px" %)<prefix> 1101 -|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)**prefix **: AB 06 (two bytes in hexadecimal) 1102 -|(% style="width:95px" %)**Example**|(% style="width:403px" %)((( 1103 -AB 06 1104 1104 1105 -Uplinks the trigger settings. 1106 -))) 901 +Set DI1 or DI3(for LT-33222-L) trigger. 1107 1107 1108 - ====3.4.2.6Enable/DisableDI1/DI2/DI3asa trigger ====903 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG1=a,b** 1109 1109 905 +(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1). 1110 1110 1111 - EnableisableDI1/DI2/DI3asatrigger.907 +(% style="color:red" %)**b :** (%%)delay timing. 1112 1112 1113 - (% style="color:#037691" %)**ATCommand**909 +**Example:** AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms ) 1114 1114 1115 -(% border="2" style="width:500px" %) 1116 -|(% style="width:98px" %)**Command**|(% style="width:400px" %)AT+DTRI=<DI1_trigger>,<DI2_trigger> 1117 -|(% style="width:98px" %)**Response**|(% style="width:400px" %) 1118 -|(% style="width:98px" %)**Parameters**|(% style="width:400px" %)((( 1119 -**DI1_trigger:** 1120 1120 1121 - 1=enableDI1trigger912 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 01 ):** 1122 1122 1123 - 0=disableDI1trigger914 +(% style="color:blue" %)**0x09 01 aa bb cc ** (%%) ~/~/ same as AT+TRIG1=aa,0x(bb cc) 1124 1124 1125 -**DI2 _trigger** 1126 1126 1127 -1 = enable DI2 trigger 1128 1128 1129 -0 = disable DI2 trigger 1130 -))) 1131 -|(% style="width:98px" %)**Example**|(% style="width:400px" %)((( 1132 -AT+DTRI=1,0 918 +==== 3.4.2.8 Trigger2 – Set DI2 as trigger ==== 1133 1133 1134 -Enable DI1 trigger, disable DI2 trigger 1135 -))) 1136 1136 1137 -(% class="wikigeneratedid" %) 1138 -(% style="color:#037691" %)**Downlink Payload** 921 +Set DI2 trigger. 1139 1139 1140 -(% border="2" style="width:500px" %) 1141 -|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix><DI1_trigger><DI2_trigger> 1142 -|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)((( 1143 -**prefix :** AA 02 (two bytes in hexadecimal) 923 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b** 1144 1144 1145 -** DI1_trigger:**925 +(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1). 1146 1146 1147 - 1= enableDI1 trigger, represented by1byte in hexadecimal.927 +(% style="color:red" %)**b :** (%%)delay timing. 1148 1148 1149 - 0 = disable DI1 trigger, representedby1 bytein hexadecimal.929 +**Example:** AT+TRIG2=0,100(set DI1 port to trigger on low level, valid signal is 100ms ) 1150 1150 1151 -**DI2 _trigger** 1152 1152 1153 - 1=enable DI2 trigger, representedby1 bytenhexadecimal.932 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):** 1154 1154 1155 -0 = disable DI2 trigger, represented by 1 byte in hexadecimal. 1156 -))) 1157 -|(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 1158 -AA 02 **01 00** 934 +(% style="color:blue" %)**0x09 02 aa bb cc ** (%%)~/~/ same as AT+TRIG2=aa,0x(bb cc) 1159 1159 1160 -Enable DI1 trigger, disable DI2 trigger 1161 -))) 1162 1162 1163 -==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ==== 1164 1164 938 +==== 3.4.2.9 Trigger – Set AC (current) as trigger ==== 1165 1165 1166 -Sets DI1 or DI3 (for LT-33222-L) as a trigger. 1167 1167 1168 - (%style="color:#037691" %)**ATmmand**941 +Set current trigger , base on AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1169 1169 1170 -(% border="2" style="width:500px" %) 1171 -|(% style="width:101px" %)**Command**|(% style="width:397px" %)AT+TRIG1=<interrupt_mode>,<minimum_signal_duration> 1172 -|(% style="width:101px" %)**Response**|(% style="width:397px" %) 1173 -|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)((( 1174 -**interrupt_mode** : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1). 943 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ACLIM** 1175 1175 1176 -**minimum_signal_duration** : the **minimum signal duration** required for the DI1 port to recognize a valid trigger. 1177 -))) 1178 -|(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 1179 -AT+TRIG1=1,100 945 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 01 )** 1180 1180 1181 -Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms. 1182 -))) 947 +(% style="color:blue" %)**0x AA 01 aa bb cc dd ee ff gg hh ** (%%) ~/~/ same as AT+ACLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1183 1183 1184 -(% class="wikigeneratedid" %) 1185 -(% style="color:#037691" %)**Downlink Payload** 1186 1186 1187 -(% border="2" style="width:500px" %) 1188 -|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix><interrupt_mode><minimum_signal_duration> 1189 -|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)((( 1190 -**prefix** : 09 01 (hexadecimal) 1191 1191 1192 -**interrupt_mode** : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal. 1193 - 1194 -**minimum_signal_duration** : in milliseconds, represented two bytes in hexadecimal. 1195 -))) 1196 -|(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 1197 -09 01 **01 00 64** 1198 - 1199 -Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms. 1200 -))) 1201 - 1202 -==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ==== 1203 - 1204 - 1205 -Sets DI2 as a trigger. 1206 - 1207 -(% style="color:#037691" %)**AT Command** 1208 - 1209 -(% border="2" style="width:500px" %) 1210 -|(% style="width:94px" %)**Command**|(% style="width:404px" %)AT+TRIG2=<interrupt_mode>,<minimum_signal_duration> 1211 -|(% style="width:94px" %)**Response**|(% style="width:404px" %) 1212 -|(% style="width:94px" %)**Parameters**|(% style="width:404px" %)((( 1213 -**interrupt_mode **: 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1). 1214 - 1215 -**minimum_signal_duration** : the **minimum signal duration** required for the DI1 port to recognize a valid trigger. 1216 -))) 1217 -|(% style="width:94px" %)**Example**|(% style="width:404px" %)((( 1218 -AT+TRIG2=0,100 1219 - 1220 -Set the DI1 port to trigger on a falling edge; the valid signal duration is 100 ms. 1221 -))) 1222 - 1223 -(% style="color:#037691" %)**Downlink Payload** 1224 - 1225 -(% border="2" style="width:500px" %) 1226 -|(% style="width:96px" %)**Payload**|(% style="width:402px" %)<prefix><interrupt_mode><minimum_signal_duration> 1227 -|(% style="width:96px" %)**Parameters**|(% style="width:402px" %)((( 1228 -**prefix** : 09 02 (hexadecimal) 1229 - 1230 -**interrupt_mode **: 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal. 1231 - 1232 -**minimum_signal_duration** : in milliseconds, represented two bytes in hexadecimal 1233 -))) 1234 -|(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64** 1235 - 1236 -==== 3.4.2.9 Trigger – Set AC (current) as a trigger ==== 1237 - 1238 - 1239 -Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1240 - 1241 -(% style="color:#037691" %)**AT Command** 1242 - 1243 -(% border="2" style="width:500px" %) 1244 -|(% style="width:104px" %)**Command**|(% style="width:394px" %)((( 1245 -AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH> 1246 -))) 1247 -|(% style="width:104px" %)**Response**|(% style="width:394px" %) 1248 -|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)((( 1249 -**AC1_LIMIT_LOW** : lower limit of the current to be checked 1250 - 1251 -**AC1_LIMIT_HIGH **: higher limit of the current to be checked 1252 - 1253 -**AC2_LIMIT_HIGH **: lower limit of the current to be checked 1254 - 1255 -**AC2_LIMIT_LOW** : higher limit of the current to be checked 1256 -))) 1257 -|(% style="width:104px" %)**Example**|(% style="width:394px" %)((( 1258 -AT+ACLIM=10000,15000,0,0 1259 - 1260 -Triggers an uplink if AC1 current is lower than 10mA or higher than 15mA 1261 -))) 1262 -|(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1263 - 1264 -(% style="color:#037691" %)**Downlink Payload** 1265 - 1266 -(% border="2" style="width:500px" %) 1267 -|(% style="width:104px" %)**Payload**|(% style="width:394px" %)<prefix><AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH> 1268 -|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)((( 1269 -**prefix **: AA 01 (hexadecimal) 1270 - 1271 -**AC1_LIMIT_LOW** : lower limit of the current to be checked, two bytes in hexadecimal 1272 - 1273 -**AC1_LIMIT_HIGH **: higher limit of the current to be checked, two bytes in hexadecimal 1274 - 1275 -**AC2_LIMIT_HIGH **: lower limit of the current to be checked, two bytes in hexadecimal 1276 - 1277 -**AC2_LIMIT_LOW** : higher limit of the current to be checked, two bytes in hexadecimal 1278 -))) 1279 -|(% style="width:104px" %)**Example**|(% style="width:394px" %)((( 1280 -AA 01 **27** **10 3A** **98** 00 00 00 00 1281 - 1282 -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. 1283 -))) 1284 -|(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1285 - 1286 1286 ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ==== 1287 1287 1288 1288 1289 -Set sthecurrent trigger basedontheAV port. Seealso[[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]954 +Set current trigger , base on AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1290 1290 1291 -(% style="color:#037691" %)**AT Command** 956 +* (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+AVLIM **(%%)** See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]** 1292 1292 1293 -(% border="2" style="width:500px" %) 1294 -|(% style="width:104px" %)**Command**|(% style="width:387px" %)AT+AVLIM= AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH> 1295 -|(% style="width:104px" %)**Response**|(% style="width:387px" %) 1296 -|(% style="width:104px" %)**Parameters**|(% style="width:387px" %)((( 1297 -**AC1_LIMIT_LOW** : lower limit of the current to be checked 958 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 00 )** 1298 1298 1299 -**A C1_LIMIT_HIGH**:higherlimitof theurrenttobe checked960 +(% style="color:blue" %)**0x AA 00 aa bb cc dd ee ff gg hh ** (%%) ~/~/ same as AT+AVLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1300 1300 1301 -**AC2_LIMIT_HIGH **: lower limit of the current to be checked 1302 1302 1303 -**AC2_LIMIT_LOW** : higher limit of the current to be checked 1304 -))) 1305 -|(% style="width:104px" %)**Example**|(% style="width:387px" %)((( 1306 -AT+AVLIM=3000,6000,0,2000 1307 1307 1308 -Triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V 1309 -))) 1310 -|(% style="width:104px" %)**Note**|(% style="width:387px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1311 - 1312 -(% style="color:#037691" %)**Downlink Payload** 1313 - 1314 -(% border="2" style="width:500px" %) 1315 -|(% style="width:104px" %)**Payload**|(% style="width:394px" %)<prefix><AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH> 1316 -|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)((( 1317 -**prefix **: AA 00 (hexadecimal) 1318 - 1319 -**AV1_LIMIT_LOW** : lower limit of the voltage to be checked, two bytes in hexadecimal 1320 - 1321 -**AV1_LIMIT_HIGH **: higher limit of the voltage to be checked, two bytes in hexadecimal 1322 - 1323 -**AV2_LIMIT_HIGH **: lower limit of the voltage to be checked, two bytes in hexadecimal 1324 - 1325 -**AV2_LIMIT_LOW** : higher limit of the voltage to be checked, two bytes in hexadecimal 1326 -))) 1327 -|(% style="width:104px" %)**Example**|(% style="width:394px" %)((( 1328 -AA 00 **0B B8 17 70 00 00 07 D0** 1329 - 1330 -Triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V. 1331 -))) 1332 -|(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1333 - 1334 1334 ==== 3.4.2.11 Trigger – Set minimum interval ==== 1335 1335 1336 1336 1337 -Set stheAV and AC trigger minimum interval.Thedevicewon't respondtoasecond trigger within this set time after the first trigger.967 +Set AV and AC trigger minimum interval, system won't response to the second trigger within this set time after the first trigger. 1338 1338 1339 -(% style="color:#037691" %)**AT Command** 969 +* (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+ATDC=5 ** ~/~/ (%%)Device won't response the second trigger within 5 minute after the first trigger. 1340 1340 1341 -(% border="2" style="width:500px" %) 1342 -|(% style="width:113px" %)**Command**|(% style="width:385px" %)AT+ATDC=<time> 1343 -|(% style="width:113px" %)**Response**|(% style="width:385px" %) 1344 -|(% style="width:113px" %)**Parameters**|(% style="width:385px" %)((( 1345 -**time** : in minutes 1346 -))) 1347 -|(% style="width:113px" %)**Example**|(% style="width:385px" %)((( 1348 -AT+ATDC=5 971 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAC )** 1349 1349 1350 -The device won't respond to the second trigger within 5 minutes after the first trigger. 1351 -))) 1352 -|(% style="width:113px" %)Note|(% style="width:385px" %)(% style="color:red" %)**The time must be greater than 5 minutes.** 973 +(% style="color:blue" %)**0x AC aa bb **(%%) ~/~/ same as AT+ATDC=0x(aa bb) . Unit (min) 1353 1353 1354 -(% style="color:#037691" %)**Downlink Payload** 1355 - 1356 -(% border="2" style="width:500px" %) 1357 -|(% style="width:112px" %)**Payload**|(% style="width:386px" %)<prefix><time> 1358 -|(% style="width:112px" %)**Parameters**|(% style="width:386px" %)((( 1359 -**prefix** : AC (hexadecimal) 1360 - 1361 -**time **: in minutes (two bytes in hexadecimal) 975 +((( 976 +(% style="color:red" %)**Note: ATDC setting must be more than 5min** 1362 1362 ))) 1363 -|(% style="width:112px" %)**Example**|(% style="width:386px" %)((( 1364 -AC **00 05** 1365 1365 1366 -The device won't respond to the second trigger within 5 minutes after the first trigger. 1367 -))) 1368 -|(% style="width:112px" %)Note|(% style="width:386px" %)(% style="color:red" %)**The time must be greater than 5 minutes.** 1369 1369 980 + 1370 1370 ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ==== 1371 1371 1372 1372 1373 - Controlsthedigitalutputs DO1,DO2,andDO3984 +* (% style="color:#037691" %)**AT Command** 1374 1374 1375 - (%style="color:#037691"%)**AT Command**986 +There is no AT Command to control Digital Output 1376 1376 1377 -There is no AT Command to control the Digital Output. 1378 1378 989 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x02)** 1379 1379 1380 -(% style="color: #037691" %)**DownlinkPayload**991 +(% style="color:blue" %)**0x02 aa bb cc ** (%%)~/~/ Set DO1/DO2/DO3 output 1381 1381 1382 -(% border="2" style="width:500px" %) 1383 -|(% style="width:115px" %)**Payload**|(% style="width:383px" %)<prefix><DO1><DO2><DO3> 1384 -|(% style="width:115px" %)**Parameters**|(% style="width:383px" %)((( 1385 -**prefix** : 02 (hexadecimal) 1386 - 1387 -**DOI** : 01: Low, 00: High, 11: No action (1 byte in hex) 1388 - 1389 -**DO2** : 01: Low, 00: High, 11: No action (1 byte in hex) 1390 - 1391 -**DO3 **: 01: Low, 00: High, 11: No action (1 byte in hex) 993 +((( 994 +If payload = 0x02010001, while there is load between V+ and DOx, it means set DO1 to low, DO2 to high and DO3 to low. 1392 1392 ))) 1393 -|(% style="width:115px" %)**Examples**|(% style="width:383px" %)((( 1394 -02 **01 00 01** 1395 1395 1396 -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. 1397 - 1398 -**More examples:** 1399 - 1400 1400 ((( 1401 -01: Low, 00: High, 11: No action 998 +01: Low, 00: High , 11: No action 1402 1402 1403 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:383px" %)1404 -|(% style="background-color:#4f81bd; color:white ; width:126px" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white; width:85px" %)**DO1**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO2**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO3**1405 -| (% style="width:126px" %)02 01 00 11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action1406 -| (% style="width:126px" %)02 00 11 01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low1407 -| (% style="width:126px" %)02 11 01 00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High1000 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 1001 +|(% 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** 1002 +|02 01 00 11|Low|High|No Action 1003 +|02 00 11 01|High|No Action|Low 1004 +|02 11 01 00|No Action|Low|High 1408 1408 ))) 1409 1409 1410 1410 ((( 1411 -((( 1412 -(% style="color:red" %)**Note: For the LT-22222-L, there is no DO3; the last byte can have any value.** 1008 +(% style="color:red" %)**Note: For LT-22222-L, there is no DO3, the last byte can use any value.** 1413 1413 ))) 1414 1414 1415 1415 ((( 1416 -(% style="color:red" %)** Thedevice will upload a packet if downlink code executes successfully.**1012 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1417 1417 ))) 1418 -))) 1419 -))) 1420 1420 1015 + 1016 + 1421 1421 ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ==== 1422 1422 1423 1423 1424 1424 * (% style="color:#037691" %)**AT Command** 1425 1425 1426 -There is no AT command to controlthe digitaloutput.1022 +There is no AT Command to control Digital Output 1427 1427 1428 1428 1429 1429 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)** 1430 1430 1431 -(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set sDO1/DO2/DO3 outputswith time control1027 +(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set DO1/DO2/DO3 output with time control 1432 1432 1029 + 1433 1433 This is to control the digital output time of DO pin. Include four bytes: 1434 1434 1435 -(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)1032 +(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9) 1436 1436 1437 -(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode1034 +(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode 1438 1438 1439 -**01:** DO pins revert to their original state after the timeout. 1440 -**00:** DO pins switch to an inverted state after the timeout. 1036 +01: DO pins will change back to original state after timeout. 1441 1441 1038 +00: DO pins will change to an inverter state after timeout 1442 1442 1443 -(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status: 1444 1444 1041 +(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Ports status: 1042 + 1445 1445 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1446 1446 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** 1447 1447 |0x01|DO1 set to low ... ... @@ -1448,7 +1448,7 @@ 1448 1448 |0x00|DO1 set to high 1449 1449 |0x11|DO1 NO Action 1450 1450 1451 -(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:1049 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Ports status: 1452 1452 1453 1453 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1454 1454 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1456,7 +1456,7 @@ 1456 1456 |0x00|DO2 set to high 1457 1457 |0x11|DO2 NO Action 1458 1458 1459 -(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:1057 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Ports status: 1460 1460 1461 1461 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1462 1462 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1464,16 +1464,16 @@ 1464 1464 |0x00|DO3 set to high 1465 1465 |0x11|DO3 NO Action 1466 1466 1467 -(% style="color:#4f81bd" %)**Sixth ,Seventh,Eighth,and Ninthbytes**:(%%) Latching time(Unit: ms)1065 +(% style="color:#4f81bd" %)**Sixth and Seventh and Eighth and Ninth Byte**:(%%) Latching time. Unit: ms 1468 1468 1469 1469 1470 1470 (% style="color:red" %)**Note: ** 1471 1471 1472 - Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes1070 + Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes 1473 1473 1474 - Before firmware v1.6.0,the latch time only supported2 bytes.1072 + Before Firmwre v1.6.0 the latch time only suport 2 bytes. 1475 1475 1476 -(% style="color:red" %)** Thedevice will uplinka packet ifthedownlink code executes successfully.**1074 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1477 1477 1478 1478 1479 1479 **Example payload:** ... ... @@ -1480,36 +1480,37 @@ 1480 1480 1481 1481 **~1. A9 01 01 01 01 07 D0** 1482 1482 1483 -DO1 pin ,DO2 pin,andDO3 pin will be set tolow, lastfor2 seconds,andthenreverttotheiroriginal state.1081 +DO1 pin & DO2 pin & DO3 pin will be set to Low, last 2 seconds, then change back to original state. 1484 1484 1485 1485 **2. A9 01 00 01 11 07 D0** 1486 1486 1487 -DO1 pin issettohigh, DO2 pinissettolow,andDO3 pintakesno action.Thislastsfor2 secondsandthenrevertstotheoriginal state.1085 +DO1 pin set high, DO2 pin set low, DO3 pin no action, last 2 seconds, then change back to original state. 1488 1488 1489 1489 **3. A9 00 00 00 00 07 D0** 1490 1490 1491 -DO1 pin ,DO2 pin,andDO3 pin will be set to high, lastfor2 seconds,andthenallchange to low.1089 +DO1 pin & DO2 pin & DO3 pin will be set to high, last 2 seconds, then both change to low. 1492 1492 1493 1493 **4. A9 00 11 01 00 07 D0** 1494 1494 1495 -DO1 pin takesno action, DO2 pinissettolow,andDO3 pinissettohigh.Thislastsfor2 seconds,afterwhichDO1 pintakesno action, DO2 pinissettohigh,andDO3 pinissettolow.1093 +DO1 pin no action, DO2 pin set low, DO3 pin set high, last 2 seconds, then DO1 pin no action, DO2 pin set high, DO3 pin set low 1496 1496 1497 1497 1096 + 1498 1498 ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ==== 1499 1499 1500 1500 1501 1501 * (% style="color:#037691" %)**AT Command:** 1502 1502 1503 -There is no AT Command to control theRelay Output1102 +There is no AT Command to control Relay Output 1504 1504 1505 1505 1506 1506 * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):** 1507 1507 1508 -(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set sRO1/RO2 output1107 +(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set RO1/RO2 output 1509 1509 1510 1510 1511 1511 ((( 1512 -If thepayloadis0x030100, it means settingRO1 to close and RO2 to open.1111 +If payload = 0x030100, it means set RO1 to close and RO2 to open. 1513 1513 ))) 1514 1514 1515 1515 ((( ... ... @@ -1527,51 +1527,50 @@ 1527 1527 |03 00 01|Open|Close 1528 1528 ))) 1529 1529 1530 -(% style="color:red" %)** Thedevice will uplinka packet ifthedownlink code executes successfully.**1129 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1531 1531 1532 1532 1132 + 1533 1533 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== 1534 1534 1535 1535 1536 -Controls the relay output time. 1537 - 1538 1538 * (% style="color:#037691" %)**AT Command:** 1539 1539 1540 -There is no AT Command to control theRelay Output1138 +There is no AT Command to control Relay Output 1541 1541 1542 1542 1543 1543 * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1544 1544 1545 -(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set sRO1/RO2 relayswith time control1143 +(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set RO1/RO2 relay with time control 1546 1546 1547 1547 1548 -This control sthe relay output time andincludes4bytes:1146 +This is to control the relay output time of relay. Include four bytes: 1549 1549 1550 -(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)1148 +(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05) 1551 1551 1552 -(% style="color:#4f81bd" %)**Second byte1150 +(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode 1553 1553 1554 -01: Relays will change back to theiroriginal state after timeout.1152 +01: Relays will change back to original state after timeout. 1555 1555 1556 -00: Relays will change to theinverter state after timeout.1154 +00: Relays will change to an inverter state after timeout 1557 1557 1558 1558 1559 -(% style="color:#4f81bd" %)**Third byte1157 +(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status: 1560 1560 1561 1561 [[image:image-20221008095908-1.png||height="364" width="564"]] 1562 1562 1563 1563 1564 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes1162 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms 1565 1565 1566 1566 1567 1567 (% style="color:red" %)**Note:** 1568 1568 1569 - Since firmware v1.6.0, the latch time supportsboth4 bytes and 2 bytes.1167 + Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes 1570 1570 1571 - Before firmware v1.6.0,the latch time only supported2 bytes.1169 + Before Firmwre v1.6.0 the latch time only suport 2 bytes. 1572 1572 1573 1573 1574 -(% style="color:red" %)** Thedevice will uplinka packet ifthedownlink code executes successfully.**1172 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1575 1575 1576 1576 1577 1577 **Example payload:** ... ... @@ -1578,19 +1578,19 @@ 1578 1578 1579 1579 **~1. 05 01 11 07 D0** 1580 1580 1581 -Relay1 and Relay2 will be set to NC, last ing2 seconds, thenreverttotheiroriginal state1179 +Relay1 and Relay 2 will be set to NC , last 2 seconds, then change back to original state. 1582 1582 1583 1583 **2. 05 01 10 07 D0** 1584 1584 1585 -Relay1 will change to NC, Relay2 will change to NO, last ing2 seconds, then bothwill reverttotheiroriginal state.1183 +Relay1 will change to NC, Relay2 will change to NO, last 2 seconds, then both change back to original state. 1586 1586 1587 1587 **3. 05 00 01 07 D0** 1588 1588 1589 -Relay1 will change to NO, Relay2 will change to NC, last ing2 seconds, thenRelay1willchange to NC,andRelay2willchange to NO.1187 +Relay1 will change to NO, Relay2 will change to NC, last 2 seconds, then relay change to NC,Relay2 change to NO. 1590 1590 1591 1591 **4. 05 00 00 07 D0** 1592 1592 1593 -Relay1 andRelay2 will change to NO, lasting2 seconds, then bothwillchange to NC.1191 +Relay 1 & relay2 will change to NO, last 2 seconds, then both change to NC. 1594 1594 1595 1595 1596 1596 ... ... @@ -1597,397 +1597,158 @@ 1597 1597 ==== 3.4.2.16 Counting ~-~- Voltage threshold counting ==== 1598 1598 1599 1599 1600 -When thevoltage exceedsthe threshold, counting begins. For details,see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]1198 +When voltage exceed the threshold, count. Feature see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1601 1601 1602 -(% style="color:#037691" %)**AT Command** 1200 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1603 1603 1604 -(% border="2" style="width:500px" %) 1605 -|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage>,<logic> 1606 -|(% style="width:137px" %)**Response**|(% style="width:361px" %) 1607 -|(% style="width:137px" %)**Parameters**|(% style="width:361px" %)((( 1608 -**voltage** : voltage threshold in mV 1202 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):** 1609 1609 1610 - **logic**:1204 +(% style="color:blue" %)**0xA5 aa bb cc ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc 1611 1611 1612 -**0** : lower than 1613 1613 1614 -**1**: higher than 1615 1615 1616 -if you leave logic parameter blank, it is considered 0 1617 -))) 1618 -|(% style="width:137px" %)**Examples**|(% style="width:361px" %)((( 1619 -AT+VOLMAX=20000 1620 - 1621 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1622 - 1623 -AT+VOLMAX=20000,0 1624 - 1625 -If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1 1626 - 1627 -AT+VOLMAX=20000,1 1628 - 1629 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1630 -))) 1631 - 1632 -(% style="color:#037691" %)**Downlink Payload** 1633 - 1634 -(% border="2" style="width:500px" %) 1635 -|(% style="width:140px" %)**Payload**|(% style="width:358px" %)<prefix><voltage><logic> 1636 -|(% style="width:140px" %)**Parameters**|(% style="width:358px" %)((( 1637 -**prefix** : A5 (hex) 1638 - 1639 -**voltage** : voltage threshold in mV (2 bytes in hex) 1640 - 1641 -**logic**: (1 byte in hexadecimal) 1642 - 1643 -**0** : lower than 1644 - 1645 -**1**: higher than 1646 - 1647 -if you leave logic parameter blank, it is considered 1 (higher than) 1648 -))) 1649 -|(% style="width:140px" %)**Example**|(% style="width:358px" %)((( 1650 -A5 **4E 20** 1651 - 1652 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1653 - 1654 -A5 **4E 20 00** 1655 - 1656 -If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1 1657 - 1658 -A5 **4E 20 01** 1659 - 1660 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1 1661 -))) 1662 - 1663 1663 ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ==== 1664 1664 1665 -This command allows users to pre-configure specific count numbers for various counting parameters such as Count1, Count2, or AVI1 Count. Use the AT command to set the desired count number for each configuration. 1666 1666 1667 -(% style="color:#037691" %)**AT Command** 1211 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) ** 1668 1668 1669 -(% border="2" style="width:500px" %) 1670 -|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter>,<number> 1671 -|(% style="width:134px" %)**Response**|(% style="width:364px" %) 1672 -|(% style="width:134px" %)**Parameters**|(% style="width:364px" %)((( 1673 -**counting_parameter** : 1213 +(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count 1674 1674 1675 - 1:COUNT11215 +(% style="color:red" %)**bb cc dd ee: **(%%)number to be set 1676 1676 1677 -2: COUNT2 1678 1678 1679 - 3:AVI1Count1218 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):** 1680 1680 1681 -**number** : Start number 1682 -))) 1683 -|(% style="width:134px" %)**Example**|(% style="width:364px" %)((( 1684 -AT+SETCNT=1,10 1220 +(% style="color:blue" %)**0x A8 aa bb cc dd ee ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee) 1685 1685 1686 -Sets the COUNT1 to 10. 1687 -))) 1688 1688 1689 -(% style="color:#037691" %)**Downlink Payload** 1690 1690 1691 -(% border="2" style="width:500px" %) 1692 -|(% style="width:135px" %)**Payload**|(% style="width:363px" %)<prefix><counting_parameter><number> 1693 -|(% style="width:135px" %)**Parameters**|(% style="width:363px" %)((( 1694 -prefix : A8 (hex) 1695 - 1696 -**counting_parameter** : (1 byte in hexadecimal) 1697 - 1698 -1: COUNT1 1699 - 1700 -2: COUNT2 1701 - 1702 -3: AVI1 Count 1703 - 1704 -**number** : Start number, 4 bytes in hexadecimal 1705 -))) 1706 -|(% style="width:135px" %)**Example**|(% style="width:363px" %)((( 1707 -A8 **01 00 00 00 0A** 1708 - 1709 -Sets the COUNT1 to 10. 1710 -))) 1711 - 1712 1712 ==== 3.4.2.18 Counting ~-~- Clear Counting ==== 1713 1713 1714 -This command clears the counting in counting mode. 1715 1715 1716 - (% style="color:#037691"%)**AT Command**1227 +Clear counting for counting mode 1717 1717 1718 -(% border="2" style="width:500px" %) 1719 -|(% style="width:142px" %)**Command**|(% style="width:356px" %)AT+CLRCOUNT 1720 -|(% style="width:142px" %)**Response**|(% style="width:356px" %)- 1229 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT **(%%) ~/~/ clear all counting 1721 1721 1722 -(% style="color:#037691" %)**Downlink Payload** 1231 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):** 1723 1723 1724 -(% border="2" style="width:500px" %) 1725 -|(% style="width:141px" %)**Payload**|(% style="width:357px" %)<prefix><clear?> 1726 -|(% style="width:141px" %)**Parameters**|(% style="width:357px" %)((( 1727 -prefix : A6 (hex) 1233 +(% style="color:blue" %)**0x A6 01 ** (%%)~/~/ clear all counting 1728 1728 1729 -clear? : 01 (hex) 1730 -))) 1731 -|(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01** 1732 1732 1733 -==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ==== 1734 1734 1237 +==== 3.4.2.19 Counting ~-~- Change counting mode save time ==== 1735 1735 1736 -This command allows you to configure the device to save its counting result to internal flash memory at specified intervals. By setting a save time, the device will periodically store the counting data to prevent loss in case of power failure. The save interval can be adjusted to suit your requirements, with a minimum value of 30 seconds. 1737 1737 1738 -(% style="color:#037691" %)**AT Command** 1240 +* (% style="color:#037691" %)**AT Command:** 1739 1739 1740 -(% border="2" style="width:500px" %) 1741 -|(% style="width:124px" %)**Command**|(% style="width:374px" %)AT+COUTIME=<time> 1742 -|(% style="width:124px" %)**Response**|(% style="width:374px" %) 1743 -|(% style="width:124px" %)**Parameters**|(% style="width:374px" %)time : seconds (0 to 16777215) 1744 -|(% style="width:124px" %)**Example**|(% style="width:374px" %)((( 1745 -AT+COUTIME=60 1242 +(% style="color:blue" %)**AT+COUTIME=60 **(%%)~/~/ Set save time to 60 seconds. Device will save the counting result in internal flash every 60 seconds. (min value: 30) 1746 1746 1747 -Sets the device to save its counting results to the memory every 60 seconds. 1748 -))) 1749 1749 1750 -(% style="color:#037691" %)**Downlink Payload** 1245 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):** 1751 1751 1752 -(% border="2" style="width:500px" %) 1753 -|(% style="width:123px" %)**Payload**|(% style="width:375px" %)<prefix><time> 1754 -|(% style="width:123px" %)**Parameters**|(% style="width:375px" %)((( 1755 -prefix : A7 1247 +(% style="color:blue" %)**0x A7 aa bb cc ** (%%)~/~/ same as AT+COUTIME =aa bb cc, 1756 1756 1757 -time : seconds, 3 bytes in hexadecimal 1249 +((( 1250 +range: aa bb cc:0 to 16777215, (unit:second) 1758 1758 ))) 1759 -|(% style="width:123px" %)**Example**|(% style="width:375px" %)((( 1760 -A7 **00 00 3C** 1761 1761 1762 -Sets the device to save its counting results to the memory every 60 seconds. 1763 -))) 1764 1764 1765 -==== 3.4.2.20 Reset saved RO and DO states ==== 1766 1766 1255 +==== 3.4.2.20 Reset save RO DO state ==== 1767 1767 1768 -This command allows you to reset the saved relay output (RO) and digital output (DO) states when the device joins the network. By configuring this setting, you can control whether the device should retain or reset the relay states after a reset and rejoin to the network. 1769 1769 1770 -(% style="color:#037691" %)**AT Command** 1258 +* (% style="color:#037691" %)**AT Command:** 1771 1771 1772 -(% border="2" style="width:500px" %) 1773 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state> 1774 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1775 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1776 -**state** : 1260 +(% style="color:blue" %)**AT+RODORESET=1 **(%%)~/~/ RODO will close when the device joining the network. (default) 1777 1777 1778 -**0** :RODOwillclosewhen the devicejoinsthe network.(default)1262 +(% style="color:blue" %)**AT+RODORESET=0 **(%%)~/~/ After the device is reset, the previously saved RODO state (only MOD2 to MOD5) is read, and its state is not changed when it is reconnected to the network. 1779 1779 1780 -**1**: After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network. 1781 -))) 1782 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1783 -(% style="color:blue" %)**AT+RODORESET=1 ** 1784 1784 1785 - RODOwillclosewhenthe device joinsthe network.(default)1265 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):** 1786 1786 1787 -(% style="color:blue" %)**AT+RODORE SET=0**1267 +(% style="color:blue" %)**0x AD aa ** (%%)~/~/ same as AT+RODORET =aa 1788 1788 1789 -After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network. 1790 -))) 1791 1791 1792 -(% style="color:#037691" %)**Downlink Payload** 1793 1793 1794 -(% border="2" style="width:500px" %) 1795 -|(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state> 1796 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1797 -**prefix** : AD 1798 - 1799 -**state** : 1800 - 1801 -**0** : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal. 1802 - 1803 -**1**: After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network. - represents as 1 byte in hexadecimal 1804 -))) 1805 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1806 -AD **01** 1807 - 1808 -RODO will close when the device joins the network. (default) 1809 - 1810 -AD **00** 1811 - 1812 -After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network. 1813 -))) 1814 - 1815 1815 ==== 3.4.2.21 Encrypted payload ==== 1816 1816 1817 1817 1818 - Thiscommandallowsyouto 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 eitheruploadencrypted dataor transmit it without encryption.1274 +* (% style="color:#037691" %)**AT Command:** 1819 1819 1820 -(% style="color: #037691" %)**ATmmand:**1276 +(% style="color:blue" %)**AT+DECRYPT=1 ** (%%)~/~/ The payload is uploaded without encryption 1821 1821 1822 -(% border="2" style="width:500px" %) 1823 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state> 1824 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1825 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1826 -**state** : 1278 +(% style="color:blue" %)**AT+DECRYPT=0 **(%%)~/~/ Encrypt when uploading payload (default) 1827 1827 1828 -**1** : The payload is uploaded without encryption 1829 1829 1830 -**0** : The payload is encrypted when uploaded (default) 1831 -))) 1832 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1833 -AT+DECRYPT=1 1834 1834 1835 -The payload is uploaded without encryption 1836 - 1837 -AT+DECRYPT=0 1838 - 1839 -The payload is encrypted when uploaded (default) 1840 -))) 1841 - 1842 -There is no downlink payload for this configuration. 1843 - 1844 - 1845 1845 ==== 3.4.2.22 Get sensor value ==== 1846 1846 1847 1847 1848 - Thiscommandallowsyouto retrieve and optionallyuplink sensorreadingsthrough the serial port.1285 +* (% style="color:#037691" %)**AT Command:** 1849 1849 1850 -(% style="color: #037691" %)**ATCommand**1287 +(% style="color:blue" %)**AT+GETSENSORVALUE=0 **(%%)~/~/ The serial port gets the reading of the current sensor 1851 1851 1852 -(% border="2" style="width:500px" %) 1853 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state> 1854 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1855 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1856 -**state** : 1289 +(% style="color:blue" %)**AT+GETSENSORVALUE=1 **(%%)~/~/ The serial port gets the current sensor reading and uploads it. 1857 1857 1858 -**0 **: Retrieves the current sensor reading via the serial port. 1859 1859 1860 -**1 **: Retrieves and uploads the current sensor reading via the serial port. 1861 -))) 1862 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1863 -AT+GETSENSORVALUE=0 1864 1864 1865 -Re trieves thecurrent sensor readingviatheserial port.1293 +==== 3.4.2.23 Resets the downlink packet count ==== 1866 1866 1867 -AT+GETSENSORVALUE=1 1868 1868 1869 -Retrieves and uplinks the current sensor reading via the serial port. 1870 -))) 1296 +* (% style="color:#037691" %)**AT Command:** 1871 1871 1872 -There is no downlink pa yloadfor thisconfiguration.1298 +(% style="color:blue" %)**AT+DISFCNTCHECK=0 **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node will no longer receive downlink packets (default) 1873 1873 1300 +(% style="color:blue" %)**AT+DISFCNTCHECK=1 **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node resets the downlink packet count and keeps it consistent with the server downlink packet count. 1874 1874 1875 -==== 3.4.2.23 Resetting the downlink packet count ==== 1876 1876 1877 1877 1878 -This command manages how the node handles mismatched downlink packet counts. It offers two modes: one disables the reception of further downlink packets if discrepancies occur, while the other resets the downlink packet count to align with the server, ensuring continued communication. 1879 - 1880 -(% style="color:#037691" %)**AT Command** 1881 - 1882 -(% border="2" style="width:500px" %) 1883 -|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state> 1884 -|(% style="width:130px" %)**Response**|(% style="width:368px" %)((( 1885 - 1886 -))) 1887 -|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)((( 1888 -**state **: 1889 - 1890 -**0** : When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node stops receiving further downlink packets (default). 1891 - 1892 - 1893 -**1** : When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node resets its downlink packet count to match the server's, ensuring consistency. 1894 -))) 1895 -|(% style="width:130px" %)**Example**|(% style="width:368px" %)((( 1896 -AT+DISFCNTCHECK=0 1897 - 1898 -When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node stops receiving further downlink packets (default). 1899 - 1900 -AT+DISFCNTCHECK=1 1901 - 1902 -When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node resets its downlink packet count to match the server's, ensuring consistency. 1903 -))) 1904 - 1905 -There is no downlink payload for this configuration. 1906 - 1907 - 1908 1908 ==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ==== 1909 1909 1910 1910 1911 - Thiscommand controls the behavior of the node when the combined size of the MAC commands(MACANS)from theserver andthe payloadexceeds the allowed bytelimit forthe current data rate (DR).Thecommandprovides two modes:one enables splitting the data into batches to ensure compliance with the byte limit, while the other prioritizes the payload and ignores the MACANS in cases of overflow.1307 +* (% style="color:#037691" %)**AT Command:** 1912 1912 1913 -(% style="color: #037691" %)**AT Command**1309 +(% style="color:blue" %)**AT+DISMACANS=0** (%%) ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of 11 bytes (DR0 of US915, DR2 of AS923, DR2 of AU195), the node will send a packet with a payload of 00 and a port of 4. (default) 1914 1914 1915 -(% border="2" style="width:500px" %) 1916 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state> 1917 -|(% style="width:127px" %)**Response**|(% style="width:371px" %) 1918 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1919 -**state** : 1311 +(% style="color:blue" %)**AT+DISMACANS=1** (%%) ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of the DR, the node will ignore the MACANS and not reply, and only upload the payload part. 1920 1920 1921 -**0** : When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default) 1922 1922 1923 -**1** : When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload. 1924 -))) 1925 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1926 -AT+DISMACANS=0 1314 +* (% style="color:#037691" %)**Downlink Payload **(%%)**:** 1927 1927 1928 - Whenthembined sizeof the MACANS from the server and the payloadexceedsthe byte limit (11bytes for DR0of US915,DR2ofAS923,DR2ofAU915),thenodesendsapacketwith a payload of00 anda portof 4. (default)1316 +(% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set the DISMACANS=1 1929 1929 1930 -AT+DISMACANS=1 1931 1931 1932 -When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload. 1933 -))) 1934 1934 1935 -(% style="color:#037691" %)**Downlink Payload** 1936 - 1937 -(% border="2" style="width:500px" %) 1938 -|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state> 1939 -|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)((( 1940 -**prefix** : 21 1941 - 1942 -**state** : (2 bytes in hexadecimal) 1943 - 1944 -**0** : When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default) 1945 - 1946 -**1 **: When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload. 1947 -))) 1948 -|(% style="width:126px" %)**Example**|(% style="width:372px" %)((( 1949 -21 **00 01** 1950 - 1951 -Set DISMACANS=1 1952 -))) 1953 - 1954 1954 ==== 3.4.2.25 Copy downlink to uplink ==== 1955 1955 1956 1956 1957 - Thiscommandenableshe device to immediatelyuplink thepayload of a received downlink packet back tothe server.Thecommandallows for quick data replication from downlink to uplink, with a fixed port number of 100.1323 +* (% style="color:#037691" %)**AT Command**(%%)**:** 1958 1958 1959 -(% style="color: #037691" %)**ATCommand**(%%)**:**1325 +(% style="color:blue" %)**AT+RPL=5** (%%) ~/~/ After receiving the package from the server, it will immediately upload the content of the package to the server, the port number is 100. 1960 1960 1961 - (% style="color:blue" %)**AT+RPL=5**(%%)~/~/Afterreceivingadownlink payloadfromtherver,thedevice will immediately uplinkthe payloadback to the serverusingportnumber100.1327 +Example:**aa xx xx xx xx** ~/~/ aa indicates whether the configuration has changed, 00 is yes, 01 is no; xx xx xx xx are the bytes sent. 1962 1962 1963 -Example:**aa xx xx xx xx** ~/~/ **aa** indicates whether the configuration has changed: **00** means YES, and **01** means NO. **xx xx xx xx** are the bytes uplinked back. 1964 1964 1965 - 1966 1966 [[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-20220823173747-6.png?width=1124&height=165&rev=1.1||alt="image-20220823173747-6.png"]] 1967 1967 1968 1968 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1969 1969 1334 + 1335 + 1970 1970 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]] 1971 1971 1972 1972 For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. 1973 1973 1974 1974 1975 -(% style="color:#037691" %)**Downlink Payload**(%%)**:** 1976 1976 1977 - Thereisno downlinkoptionavailableforthisfeature.1342 +==== 3.4.2.26 Query version number and frequency band 、TDC ==== 1978 1978 1979 1979 1980 -==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ==== 1981 - 1982 - 1983 -This command is used to query key information about the device, including its firmware version, frequency band, sub band, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device. 1984 - 1985 1985 * ((( 1986 1986 (% style="color:#037691" %)**Downlink Payload**(%%)**:** 1987 1987 1988 -(% style="color:blue" %)**26 01 ** (%%) ~/~/ The downlinkpayload26 01isusedtoquerythedevice'sfirmwareversion, frequency band, sub band,andTDC time.1348 +(% style="color:blue" %)**26 01 ** (%%) ~/~/ Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time. 1989 1989 1990 - 1991 1991 1992 1992 ))) 1993 1993 ... ... @@ -1998,151 +1998,80 @@ 1998 1998 1999 1999 == 3.5 Integrating with ThingsEye.io == 2000 2000 1360 +If you are using one of The Things Stack plans, you can integrate ThingsEye.io with your application. Once integrated, ThingsEye.io works as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic. 2001 2001 2002 - TheThings Stack application supports integration with ThingsEye.io.Onceintegrated, ThingsEye.ioacts as an MQTT client for The Things StackMQTT broker,allowing it to subscribe to upstream traffic andpublish downlinktraffic.1362 +=== 3.5.1 Configuring The Things Stack Sandbox === 2003 2003 1364 +* Go to your Application and select MQTT under Integrations. 1365 +* In the Connection credentials section, under Username, The Thins Stack displays an auto-generated username. You can use it or provide a new one. 1366 +* For the Password, click the Generate new API key button to generate a password. You can see it by clicking on the eye button. 2004 2004 2005 - === 3.5.1 ConfiguringTheThings Stack===1368 +[[image:tts-mqtt-integration.png||height="625" width="1000"]] 2006 2006 2007 - 2008 -We use The Things Stack Sandbox in this example: 2009 - 2010 -* In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added. 2011 -* Select **MQTT** under **Integrations** in the left menu. 2012 -* 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. 2013 -* 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. 2014 - 2015 -{{info}} 2016 -The username and password (API key) you created here are required in the next section. 2017 -{{/info}} 2018 - 2019 -[[image:tts-mqtt-integration.png]] 2020 - 2021 - 2022 2022 === 3.5.2 Configuring ThingsEye.io === 2023 2023 1372 +* Login to your thingsEye.io account. 1373 +* Under the Integrations center, click Integrations. 1374 +* Click the Add integration button (the button with the + symbol). 2024 2024 2025 - TheThingsEye.ioIoT platform isnotopen for self-registrationat themoment. If you areinterested in testingthe platform,please send your projectinformation to admin@thingseye.io, and we will create an account for you.1376 +[[image:thingseye-io-step-1.png||height="625" width="1000"]] 2026 2026 2027 -* Login to your [[ThingsEye.io >>https://thingseye.io]]account. 2028 -* Under the **Integrations center**, click **Integrations**. 2029 -* Click the **Add integration** button (the button with the **+** symbol). 2030 2030 2031 - [[image:thingseye-io-step-1.png]]1379 +On the Add integration page configure the following: 2032 2032 1381 +Basic settings: 2033 2033 2034 -On the **Add integration** window, configure the following: 1383 +* Select The Things Stack Community from the Integration type list. 1384 +* Enter a suitable name for your integration in the Name box or keep the default name. 1385 +* Click the Next button. 2035 2035 2036 - **Basic settings:**1387 +[[image:thingseye-io-step-2.png||height="625" width="1000"]] 2037 2037 2038 -* Select **The Things Stack Community** from the **Integration type** list. 2039 -* Enter a suitable name for your integration in the **Name **text** **box or keep the default name. 2040 -* Ensure the following options are turned on. 2041 -** Enable integration 2042 -** Debug mode 2043 -** Allow create devices or assets 2044 -* Click the **Next** button. you will be navigated to the **Uplink data converter** tab. 1389 +Uplink Data converter: 2045 2045 2046 -[[image:thingseye-io-step-2.png]] 1391 +* Click the Create New button if it is not selected by default. 1392 +* Click the JavaScript button. 1393 +* Paste the uplink decoder function into the text area (first, delete the default code). The demo decoder function can be found here. 1394 +* Click the Next button. 2047 2047 1396 +[[image:thingseye-io-step-3.png||height="625" width="1000"]] 2048 2048 2049 - **Uplinkdata converter:**1398 +Downlink Data converter (this is an optional step): 2050 2050 2051 -* Click the **Create new** button if it is not selected by default. 2052 -* Enter a suitable name for the uplink data converter in the **Name **text** **box or keep the default name. 2053 -* Click the **JavaScript** button. 2054 -* 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]]. 2055 -* Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 1400 +* Click the Create new button if it is not selected by default. 1401 +* Click the JavaScript button. 1402 +* Paste the downlink decoder function into the text area (first, delete the default code). The demo decoder function can be found here. 1403 +* Click the Next button. 2056 2056 2057 -[[image:thingseye-io-step- 3.png]]1405 +[[image:thingseye-io-step-4.png||height="625" width="1000"]] 2058 2058 1407 +Connection: 2059 2059 2060 -**Downlink data converter (this is an optional step):** 1409 +* Choose Region from the Host type. 1410 +* Enter the cluster of your The Things Stack in the Region textbox. 1411 +* Enter the Username and Password in the Credentials section. Use the same username and password you created with the MQTT page of The Things Stack. 1412 +* Click Check connection to test the connection. If the connection is successful, you can see the message saying Connected. 1413 +* Click the Add button. 2061 2061 2062 -* Click the **Create new** button if it is not selected by default. 2063 -* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name. 2064 -* Click the **JavaScript** button. 2065 -* 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]]. 2066 -* Click the **Next** button. You will be navigated to the **Connection** tab. 1415 +[[image:thingseye-io-step-5.png||height="625" width="1000"]] 2067 2067 2068 -[[image:thingseye-io-step-4.png]] 2069 2069 1418 +Your integration is added to the integrations list and it will display on the Integrations page. 2070 2070 2071 - **Connection:**1420 +[[image:thingseye-io-step-6.png||height="625" width="1000"]] 2072 2072 2073 -* Choose **Region** from the **Host type**. 2074 -* 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/...). 2075 -* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username **and **password **can be found on the MQTT integration page of your The Things Stack account (see **3.5.1 Configuring The Things Stack**). 2076 -* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**. 2077 2077 2078 -[[image:message-1.png]] 2079 - 2080 - 2081 -* Click the **Add** button. 2082 - 2083 -[[image:thingseye-io-step-5.png]] 2084 - 2085 - 2086 -Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings and correct any errors. 2087 - 2088 - 2089 -[[image:thingseye.io_integrationsCenter_integrations.png]] 2090 - 2091 - 2092 -==== 3.5.2.1 Viewing integration details ==== 2093 - 2094 - 2095 -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. 2096 - 2097 -[[image:integration-details.png]] 2098 - 2099 - 2100 -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. 2101 - 2102 -{{info}} 2103 -See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]]. 2104 -{{/info}} 2105 - 2106 - 2107 -==== 3.5.2.2 Viewing events ==== 2108 - 2109 - 2110 -The **Events **tab displays all the uplink messages from the LT-22222-L. 2111 - 2112 -* Select **Debug **from the **Event type** dropdown. 2113 -* Select the** time frame** from the **time window**. 2114 - 2115 -[[image:thingseye-events.png]] 2116 - 2117 - 2118 -* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message. 2119 - 2120 -[[image:thingseye-json.png]] 2121 - 2122 - 2123 -==== 3.5.2.3 Deleting an integration ==== 2124 - 2125 - 2126 -If you want to delete an integration, click the **Delete integratio**n button on the Integrations page. 2127 - 2128 - 2129 -==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ==== 2130 - 2131 - 2132 -This will be added soon. 2133 - 2134 - 2135 2135 == 3.6 Interface Details == 2136 2136 2137 -=== 3.6.1 Digital Input Port s: DI1/DI2/DI3 (For LT-33222-L,LowActive) ===1425 +=== 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) === 2138 2138 2139 2139 2140 -Support s**NPN-type**sensors.1428 +Support NPN Type sensor 2141 2141 2142 2142 [[image:1653356991268-289.png]] 2143 2143 2144 2144 2145 -=== 3.6.2 Digital Input Ports: DI1/DI2 === 1433 +=== 3.6.2 Digital Input Ports: DI1/DI2 ( For LT-22222-L) === 2146 2146 2147 2147 2148 2148 ((( ... ... @@ -2151,7 +2151,7 @@ 2151 2151 2152 2152 ((( 2153 2153 ((( 2154 -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. 1442 +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. 2155 2155 2156 2156 2157 2157 ))) ... ... @@ -2170,11 +2170,11 @@ 2170 2170 ))) 2171 2171 2172 2172 ((( 2173 -(% style="color: #0000ff" %)**Example1461 +(% style="color:blue" %)**Example1**(%%): Connecting to a low-active sensor. 2174 2174 ))) 2175 2175 2176 2176 ((( 2177 -This type of sensor outputs a low (GND) signal when active. 1465 +This type of sensors outputs a low (GND) signal when active. 2178 2178 ))) 2179 2179 2180 2180 * ((( ... ... @@ -2201,11 +2201,11 @@ 2201 2201 ))) 2202 2202 2203 2203 ((( 2204 -(% style="color: #0000ff" %)**Example1492 +(% style="color:blue" %)**Example2**(%%): Connecting to a high-active sensor. 2205 2205 ))) 2206 2206 2207 2207 ((( 2208 -This type of sensor outputs a high signal (e.g., 24V) when active. 1496 +This type of sensors outputs a high signal (e.g., 24V) when active. 2209 2209 ))) 2210 2210 2211 2211 * ((( ... ... @@ -2224,7 +2224,7 @@ 2224 2224 ))) 2225 2225 2226 2226 ((( 2227 -If **DI1+ = 24V**, the resulting current[[image:1653968155772-850.png||height="23" width="19"]] is24mA, Therefore, the LT-22222-L will detect this high-active signal.1515 +If **DI1+ = 24V**, the resulting current[[image:1653968155772-850.png||height="23" width="19"]] 24mA , Therefore, the LT-22222-L will detect this high-active signal. 2228 2228 ))) 2229 2229 2230 2230 ((( ... ... @@ -2232,7 +2232,7 @@ 2232 2232 ))) 2233 2233 2234 2234 ((( 2235 -(% style="color: #0000ff" %)**Example1523 +(% style="color:blue" %)**Example3**(%%): Connecting to a 220V high-active sensor. 2236 2236 ))) 2237 2237 2238 2238 ((( ... ... @@ -2255,29 +2255,29 @@ 2255 2255 ))) 2256 2256 2257 2257 ((( 2258 -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.1546 +If the sensor output is 220V, then [[image:1653968155772-850.png||height="23" width="19"]](% id="cke_bm_243359S" style="display:none" %)[[image:image-20220524095628-8.png]](%%) = DI1+ / 51K. = 4.3mA. Therefore, the LT-22222-L will be able to safely detect this high-active signal. 2259 2259 ))) 2260 2260 2261 2261 2262 -(% style="color:blue" %)**Example aDry Contact sensor1550 +(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor 2263 2263 2264 -From theDI port circuit above, 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 differenceon its own.1552 +From 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. 2265 2265 2266 -To detect a Dry Contact, you can supply a power source to one of thepinsof the Dry Contact.Areference circuit diagramis shown below.1554 +To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram. 2267 2267 2268 2268 [[image:image-20230616235145-1.png]] 2269 2269 2270 -(% style="color:blue" %)**Example 1558 +(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector 2271 2271 2272 2272 [[image:image-20240219115718-1.png]] 2273 2273 2274 2274 2275 -=== 3.6.3 Digital Output Ports: DO1/DO2 === 1563 +=== 3.6.3 Digital Output Ports: DO1/DO2 /DO3 === 2276 2276 2277 2277 2278 2278 (% style="color:blue" %)**NPN output**(%%): GND or Float. The maximum voltage that can be applied to the output pin is 36V. 2279 2279 2280 -(% style="color:red" %)**Note: The DO pins will float when thedevice is powered off.**1568 +(% style="color:red" %)**Note: The DO pins will float when device is powered off.** 2281 2281 2282 2282 [[image:1653357531600-905.png]] 2283 2283 ... ... @@ -2343,14 +2343,12 @@ 2343 2343 [[image:image-20220524100215-10.png||height="382" width="723"]] 2344 2344 2345 2345 2346 -== 3.7 LED Indicators == 1634 +== 3.7 LEDs Indicators == 2347 2347 2348 2348 2349 -The table below lists the behavior of LED indicators for each port function. 2350 - 2351 2351 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) 2352 2352 |(% style="background-color:#4f81bd; color:white; width:50px" %)**LEDs**|(% style="background-color:#4f81bd; color:white; width:460px" %)**Feature** 2353 -|**PWR**|Always on whenthere is power1639 +|**PWR**|Always on if there is power 2354 2354 |**TX**|((( 2355 2355 ((( 2356 2356 Device boot: TX blinks 5 times. ... ... @@ -2357,7 +2357,7 @@ 2357 2357 ))) 2358 2358 2359 2359 ((( 2360 -Successful network join: TXremainsON for 5 seconds.1646 +Successful join network: TX ON for 5 seconds. 2361 2361 ))) 2362 2362 2363 2363 ((( ... ... @@ -2364,104 +2364,228 @@ 2364 2364 Transmit a LoRa packet: TX blinks once 2365 2365 ))) 2366 2366 ))) 2367 -|**RX**|RX blinks once when a packet is received.2368 -|**DO1**|For LT-22222-L: ON when DO1 is low, O FFwhen DO1 is high2369 -|**DO2**|For LT-22222-L: ON when DO2 is low, O FFwhen DO2 is high1653 +|**RX**|RX blinks once when receive a packet. 1654 +|**DO1**|For LT-22222-L: ON when DO1 is low, LOW when DO1 is high 1655 +|**DO2**|For LT-22222-L: ON when DO2 is low, LOW when DO2 is high 2370 2370 |**DI1**|((( 2371 -For LT-22222-L: ON when DI1 is high, O FFwhen DI1 is low1657 +For LT-22222-L: ON when DI1 is high, LOW when DI1 is low 2372 2372 ))) 2373 2373 |**DI2**|((( 2374 -For LT-22222-L: ON when DI2 is high, O FFwhen DI2 is low1660 +For LT-22222-L: ON when DI2 is high, LOW when DI2 is low 2375 2375 ))) 2376 -|**RO1**|For LT-22222-L: ON when RO1 is closed, O FFwhen RO1 is open2377 -|**RO2**|For LT-22222-L: ON when RO2 is closed, O FFwhen RO2 is open1662 +|**RO1**|For LT-22222-L: ON when RO1 is closed, LOW when RO1 is open 1663 +|**RO2**|For LT-22222-L: ON when RO2 is closed, LOW when RO2 is open 2378 2378 2379 -= 4. Using AT Command s=1665 += 4. Using AT Command = 2380 2380 1667 +== 4.1 Connecting the LT-22222-L to a computer == 2381 2381 2382 -The LT-22222-L supports programming using AT Commands. 2383 2383 1670 +((( 1671 +The LT-22222-L supports programming using AT Commands. You can use a USB-to-TTL adapter along with a 3.5mm Program Cable to connect the LT-22222-L to a computer, as shown below. 1672 +))) 2384 2384 2385 - == 4.1 ConnectingtheLT-22222-L to a PC ==1674 +[[image:1653358238933-385.png]] 2386 2386 2387 2387 2388 2388 ((( 2389 -You can use a USB-to-TTL adapter/converter along with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below. 1678 +On the PC, the user needs to set the (% style="color:#4f81bd" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) to a baud rate of (% style="color:green" %)**9600**(%%) to access to access serial console of LT-22222-L. The AT commands are disabled by default, and a password (default:(% style="color:green" %)**123456**)(%%) must be entered to active them, as shown below: 1679 +))) 2390 2390 2391 -[[image: usb-ttl-audio-jack-connection.jpg]]1681 +[[image:1653358355238-883.png]] 2392 2392 2393 - 1683 + 1684 +((( 1685 +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/]] 2394 2394 ))) 2395 2395 1688 +((( 1689 +The following table lists all the AT commands related to the LT-22222-L, except for those used for switching between modes. 2396 2396 1691 +AT+<CMD>? : Help on <CMD> 1692 +))) 1693 + 2397 2397 ((( 2398 - 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 enteredto enable AT command access, as shown below:1695 +AT+<CMD> : Run <CMD> 2399 2399 ))) 2400 2400 2401 -[[image:1653358355238-883.png]] 1698 +((( 1699 +AT+<CMD>=<value> : Set the value 1700 +))) 2402 2402 1702 +((( 1703 +AT+<CMD>=? : Get the value 1704 +))) 2403 2403 2404 2404 ((( 2405 -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/]] 1707 +ATZ: Trig a reset of the MCU 1708 +))) 2406 2406 1710 +((( 1711 +AT+FDR: Reset Parameters to Factory Default, Keys Reserve 1712 +))) 2407 2407 2408 -== 4.2 LT-22222-L related AT commands == 1714 +((( 1715 +AT+DEUI: Get or Set the Device EUI 1716 +))) 2409 2409 2410 - 1718 +((( 1719 +AT+DADDR: Get or Set the Device Address 2411 2411 ))) 2412 2412 2413 2413 ((( 2414 -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. 1723 +AT+APPKEY: Get or Set the Application Key 1724 +))) 2415 2415 2416 -* **##AT##+<CMD>?** : Help on <CMD> 2417 -* **##AT##+<CMD>** : Run <CMD> 2418 -* **##AT##+<CMD>=<value>** : Set the value 2419 -* **##AT##+<CMD>=?** : Get the value 2420 -* ##**ATZ**##: Trigger a reset of the MCU 2421 -* ##**AT+FDR**##: Reset Parameters to factory default, reserve keys 2422 -* **##AT+DEUI##**: Get or set the Device EUI (DevEUI) 2423 -* **##AT+DADDR##**: Get or set the Device Address (DevAddr) 2424 -* **##AT+APPKEY##**: Get or set the Application Key (AppKey) 2425 -* ##**AT+NWKSKEY**##: Get or set the Network Session Key (NwkSKey) 2426 -* **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey) 2427 -* **##AT+APPEUI##**: Get or set the Application EUI (AppEUI) 2428 -* **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON) 2429 -* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification) 2430 -* **##AT+DR##**: Get or set the Data Rate. (0-7 corresponding to DR_X) 2431 -* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing 2432 -* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on) 2433 -* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency 2434 -* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X) 2435 -* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms 2436 -* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms 2437 -* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms 2438 -* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms 2439 -* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA) 2440 -* ##**AT+NWKID**##: Get or set the Network ID 2441 -* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp) 2442 -* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown) 2443 -* ##**AT+CLASS**##: Get or set the Device Class 2444 -* ##**AT+JOIN**##: Join network 2445 -* ##**AT+NJS**##: Get OTAA Join Status 2446 -* ##**AT+SENDB**##: Send hexadecimal data along with the application port 2447 -* ##**AT+SEND**##: Send text data along with the application port 2448 -* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values) 2449 -* ##**AT+RECV**##: Print last received data in raw format 2450 -* ##**AT+VER**##: Get current image version and Frequency Band 2451 -* ##**AT+CFM**##: Get or Set the confirmation mode (0-1) 2452 -* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1) 2453 -* ##**AT+SNR**##: Get the SNR of the last received packet 2454 -* ##**AT+RSSI**##: Get the RSSI of the last received packet 2455 -* ##**AT+TDC**##: Get or set the application data transmission interval in ms 2456 -* ##**AT+PORT**##: Get or set the application port 2457 -* ##**AT+DISAT**##: Disable AT commands 2458 -* ##**AT+PWORD**##: Set password, max 9 digits 2459 -* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode 2460 -* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470 2461 -* ##**AT+CFG**##: Print all settings 1726 +((( 1727 +AT+NWKSKEY: Get or Set the Network Session Key 2462 2462 ))) 2463 2463 1730 +((( 1731 +AT+APPSKEY: Get or Set the Application Session Key 1732 +))) 2464 2464 1734 +((( 1735 +AT+APPEUI: Get or Set the Application EUI 1736 +))) 1737 + 1738 +((( 1739 +AT+ADR: Get or Set the Adaptive Data Rate setting. (0: off, 1: on) 1740 +))) 1741 + 1742 +((( 1743 +AT+TXP: Get or Set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Spec) 1744 +))) 1745 + 1746 +((( 1747 +AT+DR: Get or Set the Data Rate. (0-7 corresponding to DR_X) 1748 +))) 1749 + 1750 +((( 1751 +AT+DCS: Get or Set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing 1752 +))) 1753 + 1754 +((( 1755 +AT+PNM: Get or Set the public network mode. (0: off, 1: on) 1756 +))) 1757 + 1758 +((( 1759 +AT+RX2FQ: Get or Set the Rx2 window frequency 1760 +))) 1761 + 1762 +((( 1763 +AT+RX2DR: Get or Set the Rx2 window data rate (0-7 corresponding to DR_X) 1764 +))) 1765 + 1766 +((( 1767 +AT+RX1DL: Get or Set the delay between the end of the Tx and the Rx Window 1 in ms 1768 +))) 1769 + 1770 +((( 1771 +AT+RX2DL: Get or Set the delay between the end of the Tx and the Rx Window 2 in ms 1772 +))) 1773 + 1774 +((( 1775 +AT+JN1DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms 1776 +))) 1777 + 1778 +((( 1779 +AT+JN2DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms 1780 +))) 1781 + 1782 +((( 1783 +AT+NJM: Get or Set the Network Join Mode. (0: ABP, 1: OTAA) 1784 +))) 1785 + 1786 +((( 1787 +AT+NWKID: Get or Set the Network ID 1788 +))) 1789 + 1790 +((( 1791 +AT+FCU: Get or Set the Frame Counter Uplink 1792 +))) 1793 + 1794 +((( 1795 +AT+FCD: Get or Set the Frame Counter Downlink 1796 +))) 1797 + 1798 +((( 1799 +AT+CLASS: Get or Set the Device Class 1800 +))) 1801 + 1802 +((( 1803 +AT+JOIN: Join network 1804 +))) 1805 + 1806 +((( 1807 +AT+NJS: Get OTAA Join Status 1808 +))) 1809 + 1810 +((( 1811 +AT+SENDB: Send hexadecimal data along with the application port 1812 +))) 1813 + 1814 +((( 1815 +AT+SEND: Send text data along with the application port 1816 +))) 1817 + 1818 +((( 1819 +AT+RECVB: Print last received data in binary format (with hexadecimal values) 1820 +))) 1821 + 1822 +((( 1823 +AT+RECV: Print last received data in raw format 1824 +))) 1825 + 1826 +((( 1827 +AT+VER: Get current image version and Frequency Band 1828 +))) 1829 + 1830 +((( 1831 +AT+CFM: Get or Set the confirmation mode (0-1) 1832 +))) 1833 + 1834 +((( 1835 +AT+CFS: Get confirmation status of the last AT+SEND (0-1) 1836 +))) 1837 + 1838 +((( 1839 +AT+SNR: Get the SNR of the last received packet 1840 +))) 1841 + 1842 +((( 1843 +AT+RSSI: Get the RSSI of the last received packet 1844 +))) 1845 + 1846 +((( 1847 +AT+TDC: Get or set the application data transmission interval in ms 1848 +))) 1849 + 1850 +((( 1851 +AT+PORT: Get or set the application port 1852 +))) 1853 + 1854 +((( 1855 +AT+DISAT: Disable AT commands 1856 +))) 1857 + 1858 +((( 1859 +AT+PWORD: Set password, max 9 digits 1860 +))) 1861 + 1862 +((( 1863 +AT+CHS: Get or Set Frequency (Unit: Hz) for Single Channel Mode 1864 +))) 1865 + 1866 +((( 1867 +AT+CHE: Get or Set eight channels mode, Only for US915, AU915, CN470 1868 +))) 1869 + 1870 +((( 1871 +AT+CFG: Print all settings 1872 +))) 1873 + 1874 + 2465 2465 == 4.2 Common AT Command Sequence == 2466 2466 2467 2467 === 4.2.1 Multi-channel ABP mode (Use with SX1301/LG308) === ... ... @@ -2470,41 +2470,41 @@ 2470 2470 2471 2471 2472 2472 ((( 2473 -(% style="color:blue" %)**If thedevice has notyetjoinedthenetwork:**1883 +(% style="color:blue" %)**If device has not joined network yet:** 2474 2474 ))) 2475 2475 ))) 2476 2476 2477 2477 ((( 2478 -(% style="background-color:#dcdcdc" %) ##**123456~/~/Enter the password to enable AT commands access**##1888 +(% style="background-color:#dcdcdc" %)**123456** 2479 2479 ))) 2480 2480 2481 2481 ((( 2482 -(% style="background-color:#dcdcdc" %) ##**AT+FDR~/~/Reset parameters to factory default, Reserve keys**##1892 +(% style="background-color:#dcdcdc" %)**AT+FDR** 2483 2483 ))) 2484 2484 2485 2485 ((( 2486 -(% style="background-color:#dcdcdc" %) ##**123456~/~/Enter the password to enable AT commands access**##1896 +(% style="background-color:#dcdcdc" %)**123456** 2487 2487 ))) 2488 2488 2489 2489 ((( 2490 -(% style="background-color:#dcdcdc" %) ##**AT+NJM=0~/~/Set to ABP mode**##1900 +(% style="background-color:#dcdcdc" %)**AT+NJM=0** 2491 2491 ))) 2492 2492 2493 2493 ((( 2494 -(% style="background-color:#dcdcdc" %) ##**ATZ~/~/Reset MCU**##1904 +(% style="background-color:#dcdcdc" %)**ATZ** 2495 2495 ))) 2496 2496 2497 2497 2498 2498 ((( 2499 -(% style="color:blue" %)**If thedevicehas already joinedthenetwork:**1909 +(% style="color:blue" %)**If device already joined network:** 2500 2500 ))) 2501 2501 2502 2502 ((( 2503 -(% style="background-color:#dcdcdc" %) ##**AT+NJM=0**##1913 +(% style="background-color:#dcdcdc" %)**AT+NJM=0** 2504 2504 ))) 2505 2505 2506 2506 ((( 2507 -(% style="background-color:#dcdcdc" %) ##**ATZ**##1917 +(% style="background-color:#dcdcdc" %)**ATZ** 2508 2508 ))) 2509 2509 2510 2510 ... ... @@ -2514,20 +2514,20 @@ 2514 2514 2515 2515 2516 2516 ((( 2517 -(% style="background-color:#dcdcdc" %)**123456**(%%) ~/~/ Enter password toenable ATcommands access1927 +(% style="background-color:#dcdcdc" %)**123456**(%%) ~/~/ Enter Password to have AT access. 2518 2518 ))) 2519 2519 ))) 2520 2520 2521 2521 ((( 2522 -(% style="background-color:#dcdcdc" %)** AT+FDR**(%%) ~/~/ Reset parameters to Factory Default, Reservekeys1932 +(% style="background-color:#dcdcdc" %)** AT+FDR**(%%) ~/~/ Reset Parameters to Factory Default, Keys Reserve 2523 2523 ))) 2524 2524 2525 2525 ((( 2526 -(% style="background-color:#dcdcdc" %)** 123456**(%%) ~/~/ Enter password toenable ATcommands access1936 +(% style="background-color:#dcdcdc" %)** 123456**(%%) ~/~/ Enter Password to have AT access. 2527 2527 ))) 2528 2528 2529 2529 ((( 2530 -(% style="background-color:#dcdcdc" %)** AT+CLASS=C**(%%) ~/~/ Set to CLASS C mode1940 +(% style="background-color:#dcdcdc" %)** AT+CLASS=C**(%%) ~/~/ Set to work in CLASS C 2531 2531 ))) 2532 2532 2533 2533 ((( ... ... @@ -2547,19 +2547,19 @@ 2547 2547 ))) 2548 2548 2549 2549 ((( 2550 -(% style="background-color:#dcdcdc" %)** AT+CHS=868400000**(%%) ~/~/ Set transmit frequency to 868.4 Hz1960 +(% style="background-color:#dcdcdc" %)** AT+CHS=868400000**(%%) ~/~/ Set transmit frequency to 868.4Mhz 2551 2551 ))) 2552 2552 2553 2553 ((( 2554 -(% style="background-color:#dcdcdc" %)** AT+RX2FQ=868400000**(%%) ~/~/ Set RX2 frequency to 868.4Hz (according to the result fromtheserver)1964 +(% style="background-color:#dcdcdc" %)** AT+RX2FQ=868400000**(%%) ~/~/ Set RX2Frequency to 868.4Mhz (according to the result from server) 2555 2555 ))) 2556 2556 2557 2557 ((( 2558 -(% style="background-color:#dcdcdc" %)** AT+RX2DR=5**(%%)** ** ~/~/ Set RX2 theserver.See below.1968 +(% style="background-color:#dcdcdc" %)** AT+RX2DR=5**(%%)** ** ~/~/ Set RX2DR to match the downlink DR from server. see below 2559 2559 ))) 2560 2560 2561 2561 ((( 2562 -(% style="background-color:#dcdcdc" %)** AT+DADDR=26 01 1A F1** (%%) ~/~/ Set Device Address .TheDeviceAddresscan be found in theapplication on theLoRaWANNS.1972 +(% style="background-color:#dcdcdc" %)** AT+DADDR=26 01 1A F1** (%%) ~/~/ Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal. 2563 2563 ))) 2564 2564 2565 2565 ((( ... ... @@ -2573,14 +2573,14 @@ 2573 2573 ))) 2574 2574 2575 2575 ((( 2576 -**~1. Ensure that the device is set to ABP mode in theLoRaWANNetworkServer.**1986 +**~1. Make sure the device is set to ABP mode in the IoT Server.** 2577 2577 2578 -**2. Verifythat the LG01/02 gateway RX frequencymatchesthe AT+CHS settingexactly.**1988 +**2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.** 2579 2579 2580 -**3. Make sure theSF/bandwidth settingsintheLG01/LG02 match the settings of AT+DR.Referto[[this link>>url:http://www.dragino.com/downloads/index.php?1990 +**3. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php? 2581 2581 dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.** 2582 2582 2583 -**4. The command sAT+RX2FQ and AT+RX2DRenable downlinkfunctionality.To set the correct parameters,you can check the actual downlink parameters to be usedasshownbelow.Here,RX2FQ shouldbesetto868400000 and RX2DR should beset to5.**1993 +**4. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5.** 2584 2584 ))) 2585 2585 2586 2586 ((( ... ... @@ -2592,7 +2592,7 @@ 2592 2592 2593 2593 2594 2594 ((( 2595 -(% style="color:blue" %)**If thesensorhasJOINED:**2005 +(% style="color:blue" %)**If sensor JOINED:** 2596 2596 2597 2597 (% style="background-color:#dcdcdc" %)**AT+CLASS=A** 2598 2598 ... ... @@ -2602,51 +2602,37 @@ 2602 2602 2603 2603 = 5. Case Study = 2604 2604 2605 -== 5.1 Counting how many objects pass throughthe flowline ==2015 +== 5.1 Counting how many objects pass in Flow Line == 2606 2606 2607 2607 2608 - Seesetupcountingfor objects passingthrough theflow line>>How to set up to count objects pass in flow line]]?2018 +Reference Link: [[How to set up to count objects pass in flow line>>How to set up to count objects pass in flow line]]? 2609 2609 2610 2610 2611 2611 = 6. FAQ = 2612 2612 2023 +== 6.1 How to upgrade the image? == 2613 2613 2614 -This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly. 2615 2615 2026 +The LT LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to LT to: 2616 2616 2617 -== 6.1 How to update the firmware? == 2618 - 2619 - 2620 -Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to: 2621 - 2622 2622 * Support new features 2623 -* F ixbugs2624 -* Change LoRaWAN frequencybands2029 +* For bug fix 2030 +* Change LoRaWAN bands. 2625 2625 2626 - Youwillneedthefollowingthingsbeforeproceeding:2032 +Below shows the hardware connection for how to upload an image to the LT: 2627 2627 2628 -* 3.5mm programming cable (included with the LT-22222-L as an additional accessory) 2629 -* USB to TTL adapter/converter 2630 -* 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) 2631 -* 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. 2034 +[[image:1653359603330-121.png]] 2632 2632 2633 -{{info}} 2634 -As of this writing, the latest firmware version available for the LT-22222-L is v1.6.1. 2635 -{{/info}} 2636 2636 2637 -Below is the hardware setup for uploading a firmware image to the LT-22222-L: 2037 +((( 2038 +(% 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]]. 2039 +(% 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]]. 2040 +(% style="color:blue" %)**Step3**(%%)**:** Open flashloader; choose the correct COM port to update. 2041 + 2638 2638 2639 -[[image:usb-ttl-audio-jack-connection.jpg]] 2640 - 2641 - 2642 - 2643 -Start the STM32 Flash Loader and choose the correct COM port to update. 2644 - 2645 2645 ((( 2646 -((( 2647 2647 (% style="color:blue" %)**For LT-22222-L**(%%): 2648 - 2649 -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. 2045 +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. 2650 2650 ))) 2651 2651 2652 2652 ... ... @@ -2661,7 +2661,7 @@ 2661 2661 [[image:image-20220524104033-15.png]] 2662 2662 2663 2663 2664 -(% style="color:red" %)**Note**(%%): I fyou havelost the programmingcable,youcan make one from a 3.5as follows:2060 +(% style="color:red" %)**Notice**(%%): In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is: 2665 2665 2666 2666 [[image:1653360054704-518.png||height="186" width="745"]] 2667 2667 ... ... @@ -2668,7 +2668,7 @@ 2668 2668 2669 2669 ((( 2670 2670 ((( 2671 -== 6.2 How to change the LoRa WANfrequencyband/region? ==2067 +== 6.2 How to change the LoRa Frequency Bands/Region? == 2672 2672 2673 2673 2674 2674 ))) ... ... @@ -2675,13 +2675,13 @@ 2675 2675 ))) 2676 2676 2677 2677 ((( 2678 - Youcan follow the introductionson[[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, selectthe required image file.2074 +User can follow the introduction for [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download. 2679 2679 ))) 2680 2680 2681 2681 ((( 2682 2682 2683 2683 2684 -== 6.3 How to setup LT -22222-Lto work withaSingle Channel Gateway,such as LG01/LG02? ==2080 +== 6.3 How to set up LT to work with Single Channel Gateway such as LG01/LG02? == 2685 2685 2686 2686 2687 2687 ))) ... ... @@ -2688,13 +2688,13 @@ 2688 2688 2689 2689 ((( 2690 2690 ((( 2691 -In this case, you need to settheLT-22222-L to work in ABP modeandtransmiton only one frequency.2087 +In this case, users need to set LT-33222-L to work in ABP mode & transmit in only one frequency. 2692 2692 ))) 2693 2693 ))) 2694 2694 2695 2695 ((( 2696 2696 ((( 2697 - We assumeyouhave anLG01/LG02 workingon the frequency 868400000.Belowarethe steps.2093 +Assume we have a LG02 working in the frequency 868400000 now , below is the step. 2698 2698 2699 2699 2700 2700 ))) ... ... @@ -2701,55 +2701,52 @@ 2701 2701 ))) 2702 2702 2703 2703 ((( 2704 -(% style="color: #0000ff" %)**SteptoTheThingsStack Sandbox account and create an ABP device in the application.Todothis,usethemanual registrationoption asxplained insection3.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, ApplicationSessionKey (AppSKey),and Network SessionKey(NwkSKey).2100 +(% style="color:blue" %)**Step1**(%%): Log in TTN, Create an ABP device in the application and input the network session key (NETSKEY), app session key (APPSKEY) from the device. 2705 2705 2706 - [[image:lt-22222-l-abp.png||height="686"width="1000"]]2102 + 2707 2707 ))) 2708 2708 2709 2709 ((( 2106 +[[image:1653360231087-571.png||height="401" width="727"]] 2107 + 2710 2710 2711 2711 ))) 2712 2712 2713 - {{warning}}2714 - Ensure that theDevice Address(DevAddr)andthe two keysmatchbetweentheLT-22222-L and TheThingsStack.Youcanmodify themeither in TheThingsStackoron theLT-22222-Lto make themalign. In TheThingsStack,youcan configurethe NwkSKeyand AppSKeyonthesettingspage, butnote that theDevice Addressis generated by TheThings Stack.2715 - {{/warning}}2111 +((( 2112 +(% style="color:red" %)**Note: user just need to make sure above three keys match, User can change either in TTN or Device to make then match. In TTN, NETSKEY and APPSKEY can be configured by user in setting page, but Device Addr is generated by TTN.** 2113 +))) 2716 2716 2717 2717 2116 + 2718 2718 ((( 2719 -(% style="color:blue" %)**Step (% 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 ATcommandstoconfiguretheLT-22222-Ltooperateinsingle-frequencyandABP mode.The AT commandsare as follows:2118 +(% style="color:blue" %)**Step2**(%%)**: **Run AT Command to make LT work in Single frequency & ABP mode. Below is the AT commands: 2720 2720 2721 2721 2722 2722 ))) 2723 2723 2724 2724 ((( 2725 -(% style="background-color:#dcdcdc" %)**123456** (%%) : Enter the password toenable AT access.2124 +(% style="background-color:#dcdcdc" %)**123456** (%%) : Enter Password to have AT access. 2726 2726 2727 -(% style="background-color:#dcdcdc" %)**AT+FDR**(%%) : Reset parameters tofactorydefault,keeping keysreserved.2126 +(% style="background-color:#dcdcdc" %)**AT+FDR**(%%) : Reset Parameters to Factory Default, Keys Reserve 2728 2728 2729 -(% style="background-color:#dcdcdc" %)**AT+NJM=0** (%%) : Set to ABP mode .2128 +(% style="background-color:#dcdcdc" %)**AT+NJM=0** (%%) : Set to ABP mode 2730 2730 2731 -(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%) : Disable the Adaptive Data Rate(ADR).2130 +(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%) : Set the Adaptive Data Rate Off 2732 2732 2733 -(% style="background-color:#dcdcdc" %)**AT+DR=5** (%%) : Set Data Rate ( Use AT+DR=3 forthe915MHzband).2132 +(% style="background-color:#dcdcdc" %)**AT+DR=5** (%%) : Set Data Rate (Set AT+DR=3 for 915 band) 2734 2734 2735 -(% style="background-color:#dcdcdc" %)**AT+TDC=60000 **(%%) : Set transmit interval to 60 seconds .2134 +(% style="background-color:#dcdcdc" %)**AT+TDC=60000 **(%%) : Set transmit interval to 60 seconds 2736 2736 2737 -(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) : Set transmit frequency to 868.4 Hz.2136 +(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) : Set transmit frequency to 868.4Mhz 2738 2738 2739 -(% style="background-color:#dcdcdc" %)**AT+DADDR= xxxx**(%%) : SettheDevice Address(DevAddr)2138 +(% style="background-color:#dcdcdc" %)**AT+DADDR=26 01 1A F1**(%%) : Set Device Address to 26 01 1A F1 2740 2740 2741 -(% 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) 2742 - 2743 -(% 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) 2744 - 2745 -(% 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) 2746 - 2747 -(% style="background-color:#dcdcdc" %)**ATZ** (%%) : Reset MCU. 2140 +(% style="background-color:#dcdcdc" %)**ATZ** (%%) : Reset MCU 2748 2748 ))) 2749 2749 2750 2750 2751 2751 ((( 2752 - (% 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 followingfigure shows the screenshotof the command set above, issued using a serialtool:2145 +As shown in below: 2753 2753 ))) 2754 2754 2755 2755 [[image:1653360498588-932.png||height="485" width="726"]] ... ... @@ -2761,62 +2761,61 @@ 2761 2761 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/]] 2762 2762 2763 2763 2764 -== 6.5 Can I see thecounting event intheserialoutput? ==2157 +== 6.5 Can I see counting event in Serial? == 2765 2765 2766 2766 2767 2767 ((( 2768 - Youcan runtheAT command**AT+DEBUG**toviewthe counting event intheserialoutput. Ifthefirmwareistoo old and doesn’t support,update tothelatest firmware first.2161 +User can run AT+DEBUG command to see the counting event in serial. If firmware too old and doesn't support AT+DEBUG. User can update to latest firmware first. 2769 2769 2770 2770 2771 -== 6.6 Can Iuse point-to-point communicationwithLT-22222-L? ==2164 +== 6.6 Can i use point to point communication for LT-22222-L? == 2772 2772 2773 2773 2774 -Yes, you can. Please referto the[[Point-to-Point Communicationof LT-22222-L>>https://wiki.dragino.com/xwiki/bin/view/Main/%20Point%20to%20Point%20Communication%20of%20LT-22222-L/]] page.Thefirmware thatsupportspoint-to-point communication can be found [[here>>https://github.com/dragino/LT-22222-L/releases]].2167 +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]]. 2775 2775 2776 2776 2777 2777 ))) 2778 2778 2779 2779 ((( 2780 -== 6.7 Why does the relay output default toan open relay after theLT-22222-Lis powered off? ==2173 +== 6.7 Why does the relay output become the default and open relay after the lt22222 is powered off? == 2781 2781 2782 2782 2783 -* If the device is not properly shut down and is directly powered off. 2784 -* It will default to a power-off state. 2785 -* In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory. 2786 -* After a restart, the status before the power failure will be read from flash. 2176 +If the device is not shut down, but directly powered off. 2787 2787 2788 - ==6.8CanIsetupLT-22222-L as aNC (Normally Closed)relay? ==2178 +It will default that this is a power-off state. 2789 2789 2180 +In modes 2 to 5, DO RO status and pulse count are saved in flash. 2790 2790 2791 - The LT-22222-L's built-in relay is NormallyOpen (NO). You can use an externalrelaytoachieveaNormallyClosed(NC) configuration.Thecircuit diagramisshown below:2182 +After restart, the status before power failure will be read from flash. 2792 2792 2793 2793 2794 - [[image:image-20221006170630-1.png||height="610"width="945"]]2185 +== 6.8 Can i set up LT-22222-L as a NC(Normal Close) Relay? == 2795 2795 2796 2796 2797 - == 6.9 Can theLT-22222-L savetheROstate?==2188 +LT-22222-L built-in relay is NO (Normal Open). User can use an external relay to achieve Normal Close purpose. Diagram as below: 2798 2798 2799 2799 2800 - To enable this feature, the firmwareversion mustbe 1.6.0or higher.2191 +[[image:image-20221006170630-1.png||height="610" width="945"]] 2801 2801 2802 2802 2803 -== 6. 10Whydoes theLT-22222-Lalwaysreport15.585Vwhen measuringtheAVI? ==2194 +== 6.9 Can LT22222-L save RO state? == 2804 2804 2805 2805 2806 - Itis likely that the GND is not connected during themeasurement,or that thewire connected totheGNDisloose.2197 +Firmware version needs to be no less than 1.6.0. 2807 2807 2808 2808 2809 -= 7.Troubleshooting =2200 +== 6.10 Why does the LT22222 always report 15.585V when measuring AVI? == 2810 2810 2811 2811 2812 - Thissectionprovidessomeknowntroubleshootingtips.2203 +It is likely that the GND is not connected during the measurement, or the wire connected to the GND is loose. 2813 2813 2814 - 2205 + 2206 += 7. Trouble Shooting = 2815 2815 ))) 2816 2816 2817 2817 ((( 2818 2818 ((( 2819 -== 7.1 Downlink isn't working.HowcanIsolvethis? ==2211 +== 7.1 Downlink doesn't work, how to solve it? == 2820 2820 2821 2821 2822 2822 ))) ... ... @@ -2823,42 +2823,42 @@ 2823 2823 ))) 2824 2824 2825 2825 ((( 2826 -Please referto this link for debugging instructions: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]2218 +Please see this link for how to debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]] 2827 2827 ))) 2828 2828 2829 2829 ((( 2830 2830 2831 2831 2832 -== 7.2 Hav ingtrouble uploadinganimage?==2224 +== 7.2 Have trouble to upload image. == 2833 2833 2834 2834 2835 2835 ))) 2836 2836 2837 2837 ((( 2838 - Pleasereferto this link for troubleshooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]2230 +See this link for trouble shooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]] 2839 2839 ))) 2840 2840 2841 2841 ((( 2842 2842 2843 2843 2844 -== 7.3 Why can't Ijoin TTN intheUS915 /AU915 bands? ==2236 +== 7.3 Why I can't join TTN in US915 /AU915 bands? == 2845 2845 2846 2846 2847 2847 ))) 2848 2848 2849 2849 ((( 2850 -It might be relatedto the channel mapping. [[Pleasereferto this link for details.>>https://github.com/dragino/LT-22222-L/releases]]2242 +It might be about the channels mapping. [[Please see this link for detail>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]] 2851 2851 ))) 2852 2852 2853 2853 2854 -== 7.4 Why can theLT-22222-Lperformuplink normally, but cannot receivedownlink? ==2246 +== 7.4 Why can LT22222 perform Uplink normally, but cannot receive Downlink? == 2855 2855 2856 2856 2857 -The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue. 2858 -Use this command to synchronizetheir counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]2249 +The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue state. 2250 +Use this command to bring their counts back together: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]] 2859 2859 2860 2860 2861 -= 8. Order inginformation=2253 += 8. Order Info = 2862 2862 2863 2863 2864 2864 (% style="color:#4f81bd" %)**LT-22222-L-XXX:** ... ... @@ -2865,42 +2865,43 @@ 2865 2865 2866 2866 (% style="color:#4f81bd" %)**XXX:** 2867 2867 2868 -* (% style="color:red" %)**EU433**(%%): LT with frequency bands EU433 2869 -* (% style="color:red" %)**EU868**(%%): LT with frequency bands EU868 2870 -* (% style="color:red" %)**KR920**(%%): LT with frequency bands KR920 2871 -* (% style="color:red" %)**CN470**(%%): LT with frequency bands CN470 2872 -* (% style="color:red" %)**AS923**(%%): LT with frequency bands AS923 2873 -* (% style="color:red" %)**AU915**(%%): LT with frequency bands AU915 2874 -* (% style="color:red" %)**US915**(%%): LT with frequency bands US915 2875 -* (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865 2876 -* (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779 2260 +* (% style="color:red" %)**EU433**(%%): LT with frequency bands EU433 2261 +* (% style="color:red" %)**EU868**(%%): LT with frequency bands EU868 2262 +* (% style="color:red" %)**KR920**(%%): LT with frequency bands KR920 2263 +* (% style="color:red" %)**CN470**(%%): LT with frequency bands CN470 2264 +* (% style="color:red" %)**AS923**(%%): LT with frequency bands AS923 2265 +* (% style="color:red" %)**AU915**(%%): LT with frequency bands AU915 2266 +* (% style="color:red" %)**US915**(%%): LT with frequency bands US915 2267 +* (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865 2268 +* (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779 2877 2877 2878 -= 9. Pack ageinformation=2270 += 9. Packing Info = 2879 2879 2880 2880 2881 -**Package includes**:2273 +**Package Includes**: 2882 2882 2883 -* 1 xLT-22222-L I/O Controller2884 -* 1x LoRa antennamatched to thefrequencyoftheLT-22222-L2885 -* 1 x bracket forDIN rail mounting2886 -* 1 x 3.5 mm programmingcable2275 +* LT-22222-L I/O Controller x 1 2276 +* Stick Antenna for LoRa RF part x 1 2277 +* Bracket for controller x1 2278 +* Program cable x 1 2887 2887 2888 2888 **Dimension and weight**: 2889 2889 2890 2890 * Device Size: 13.5 x 7 x 3 cm 2891 -* Device Weight: 105 2283 +* Device Weight: 105g 2892 2892 * Package Size / pcs : 14.5 x 8 x 5 cm 2893 -* Weight / pcs : 170 2285 +* Weight / pcs : 170g 2894 2894 2895 2895 = 10. Support = 2896 2896 2897 2897 2898 2898 * ((( 2899 -Support is available Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time,we cannot offer live support. However, your questions will be answered as soon as possiblewithin theaforementioned schedule.2291 +Support is provided Monday 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 the before-mentioned schedule. 2900 2900 ))) 2901 2901 * ((( 2902 -P lease provide as much information as possible regarding yourinquiry (e.g.,product models, adetaileddescriptionoftheproblem,steps to replicate it,etc.) and send anemail to [[support@dragino.cc>>mailto:support@dragino.cc]]2294 +Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[Support@dragino.cc>>mailto:Support@dragino.cc]] 2903 2903 2296 + 2904 2904 2905 2905 ))) 2906 2906
- Screenshot 2024-11-23 at 18.27.11.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -143.4 KB - Content
- Screenshot 2024-12-08 193946.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -32.4 KB - Content
- dragino-lorawan-nw-lt-22222-n.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -267.3 KB - Content
- dragino-ttn-te.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -273.8 KB - Content
- integration-details.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -463.9 KB - Content
- lorawan-nw.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -250.6 KB - Content
- lt-22222-device-overview.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -497.2 KB - Content
- lt-22222-join-network.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -340.6 KB - Content
- lt-22222-l-abp.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -321.4 KB - Content
- lt-22222-l-joining.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -301.9 KB - Content
- lt-22222-l-js-custom-payload-formatter.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -453.9 KB - Content
- lt-22222-ul-payload-decoded.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -48.7 KB - Content
- lt-22222-ul-payload-fmt.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -438.6 KB - Content
- lt33222-l.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.3 KB - Content
- message-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -20.1 KB - Content
- thingseye-events.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -530.6 KB - Content
- thingseye-json.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -554.8 KB - Content
- thingseye.io_integrationsCenter_integrations-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -469.3 KB - Content
- thingseye.io_integrationsCenter_integrations.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -302.3 KB - Content
- usb-ttl-audio-jack-connection.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -394.4 KB - Content
- usb-ttl-programming.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -462.9 KB - Content