Skip to Content
Last modified by Mengting Qiu on 2025/06/04 18:42
From version 230.1
edited by Dilisi S
on 2024/12/09 02:51
Change comment: Dec 8 edits - add some details to AT commands
To version 200.1
edited by Dilisi S
on 2024/11/18 04:06
Change comment: Nov 17 - AT Commands edit - part 3

Summary

Details

Page properties
Content
... ... @@ -27,7 +27,7 @@
27 27  **This manual is also applicable to the LT-33222-L.**
28 28  {{/info}}
29 29  
30 -The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN end device designed to provide seamless wireless long-range connectivity with various I/O options, including analog current and voltage inputs, digital inputs and outputs, and relay outputs.
30 +The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN device designed to provide seamless wireless long-range connectivity with various I/O options, including analog current and voltage inputs, digital inputs and outputs, and relay outputs.
31 31  
32 32  The LT-22222-L I/O Controller simplifies and enhances I/O monitoring and controlling. It is ideal for professional applications in wireless sensor networks, including irrigation systems, smart metering, smart cities, building automation, and more. These controllers are designed for easy, cost-effective deployment using LoRa wireless technology.
33 33  )))
... ... @@ -40,24 +40,23 @@
40 40  (((
41 41  You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways:
42 42  
43 -* If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Stack Community Network), you can select a network and register the LT-22222-L I/O controller with it.
43 +* If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Network), you can select a network and register the LT-22222-L I/O controller with it.
44 44  * If there is no public LoRaWAN coverage in your area, you can set up a LoRaWAN gateway, or multiple gateways, and connect them to a LoRaWAN network server to create adequate coverage. Then, register the LT-22222-L I/O controller with this network.
45 45  * Setup your own private LoRaWAN network.
46 +
47 +{{info}}
48 + You can use a LoRaWAN gateway, such as the [[Dragino LG308>>https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], to expand or create LoRaWAN coverage in your area.
49 +{{/info}}
46 46  )))
47 47  
48 48  (((
49 -
53 +[[image:1653295757274-912.png]]
50 50  
51 -The network diagram below illustrates how the LT-22222-L communicates with a typical LoRaWAN network.
55 +
52 52  )))
53 53  
54 -(% class="wikigeneratedid" %)
55 -[[image:lorawan-nw.jpg||height="354" width="900"]]
56 -
57 -
58 58  == 1.2 Specifications ==
59 59  
60 -
61 61  (% style="color:#037691" %)**Hardware System:**
62 62  
63 63  * STM32L072xxxx MCU
... ... @@ -116,41 +116,24 @@
116 116  * Smart cities
117 117  * Smart factory
118 118  
119 -== 1.5 Hardware Variants ==
118 +== 2. Assembling the device ==
120 120  
121 -
122 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
123 -|(% 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**
124 -|(% style="width:94px" %)**LT-22222-L**|(% style="width:172px" %)(((
125 -(% style="text-align:center" %)
126 -[[image:lt33222-l.jpg||height="116" width="100"]]
127 -)))|(% style="width:256px" %)(((
128 -* 2 x Digital Input (Bi-direction)
129 -* 2 x Digital Output
130 -* 2 x Relay Output (5A@250VAC / 30VDC)
131 -* 2 x 0~~20mA Analog Input (res:0.01mA)
132 -* 2 x 0~~30V Analog Input (res:0.01v)
133 -* 1 x Counting Port
134 -)))
135 -
136 -= 2. Assembling the device =
137 -
138 138  == 2.1 Connecting the antenna ==
139 139  
140 140  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.
141 141  
142 142  {{warning}}
143 -**Warning! Do not power on the device without connecting the antenna.**
125 +Warning! Do not power on the device without connecting the antenna.
144 144  {{/warning}}
145 145  
146 146  == 2.2 Terminals ==
147 147  
148 -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.
130 +The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 terminals and the lower screw terminal block has 10 terminals.
149 149  
150 -**Upper screw terminal block (from left to right):**
132 +Upper screw terminal block (from left to right):
151 151  
152 152  (% style="width:634px" %)
153 -|=(% style="width: 295px;" %)Screw Terminal|=(% style="width: 338px;" %)Function
135 +|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function
154 154  |(% style="width:295px" %)GND|(% style="width:338px" %)Ground
155 155  |(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage
156 156  |(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2
... ... @@ -158,10 +158,10 @@
158 158  |(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2
159 159  |(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1
160 160  
161 -**Lower screw terminal block (from left to right):**
143 +Lower screw terminal block (from left to right):
162 162  
163 163  (% style="width:633px" %)
164 -|=(% style="width: 296px;" %)Screw Terminal|=(% style="width: 334px;" %)Function
146 +|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function
165 165  |(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1
166 166  |(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1
167 167  |(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2
... ... @@ -173,12 +173,14 @@
173 173  |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
174 174  |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
175 175  
176 -== 2.3 Connecting LT-22222-L to a Power Source ==
158 +== 2.3 Powering the device ==
177 177  
178 -The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s **positive wire** to the **VIN** and the **negative wire** to the **GND** screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered.
160 +The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s positive wire to the VIN and the negative wire to the GND screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered.
179 179  
162 +Once powered, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** The Things Stack. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status.
163 +
180 180  {{warning}}
181 -**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.**
165 +We recommend that you power on the LT-22222-L after configuring its registration information with a LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.
182 182  {{/warning}}
183 183  
184 184  
... ... @@ -185,51 +185,36 @@
185 185  [[image:1653297104069-180.png]]
186 186  
187 187  
188 -= 3. Registering LT-22222-L with a LoRaWAN Network Server =
172 += 3. Registering with a LoRaWAN Network Server =
189 189  
190 -The LT-22222-L supports both OTAA (Over-the-Air Activation) and ABP (Activation By Personalization) methods to activate with a LoRaWAN Network Server. However, OTAA is the most secure method for activating a device with a LoRaWAN Network Server. OTAA regenerates session keys upon initial registration and regenerates new session keys after any subsequent reboots. By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode.
174 +By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. It supports OTAA (Over-the-Air Activation), the most secure method for activating a device with a LoRaWAN network server. The LT-22222-L comes with device registration information that allows you to register it with a LoRaWAN network, enabling the device to perform OTAA activation with the network server upon initial power-up and after any subsequent reboots.
191 191  
176 +After powering on, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** the LoRaWAN network. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status.
192 192  
178 +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.
179 +
180 +The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
181 +
182 +[[image:image-20220523172350-1.png||height="266" width="864"]]
183 +
193 193  === 3.2.1 Prerequisites ===
194 194  
195 -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.
186 +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.
196 196  
197 197  [[image:image-20230425173427-2.png||height="246" width="530"]]
198 198  
199 -{{info}}
200 -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.
201 -{{/info}}
202 -
203 203  The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
204 204  
205 -=== 3.2.2 The Things Stack ===
192 +=== 3.2.2 The Things Stack Sandbox (TTSS) ===
206 206  
207 -This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
208 -
209 -{{info}}
210 210  The Things Stack Sandbox was formally called The Things Stack Community Edition.
211 -{{/info}}
212 212  
213 -
214 -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.
215 -
216 -
217 -[[image:dragino-lorawan-nw-lt-22222-n.jpg]]
218 -
219 -{{info}}
220 - 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.
221 -{{/info}}
222 -
223 -
224 -==== 3.2.2.1 Setting up ====
225 -
226 -* Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet.
227 -* Log in to your The Things Stack Sandbox account.
228 -* Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs).
229 -* Go to your application's page and click on the **End devices** in the left menu.
196 +* Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
197 +* Create an application with The Things Stack if you do not have one yet.
198 +* Go to your application page and click on the **End devices** in the left menu.
230 230  * On the End devices page, click on **+ Register end device**. Two registration options are available:
231 231  
232 -==== 3.2.2.2 Using the LoRaWAN Device Repository ====
201 +==== 3.2.2.1 Using the LoRaWAN Device Repository ====
233 233  
234 234  * On the **Register end device** page:
235 235  ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
... ... @@ -241,7 +241,7 @@
241 241  *** **Profile (Region)**: Select the region that matches your device.
242 242  ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
243 243  
244 -[[image:lt-22222-l-dev-repo-reg-p1.png]]
213 +[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
245 245  
246 246  
247 247  * Register end device page continued...
... ... @@ -251,10 +251,11 @@
251 251  ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
252 252  ** Under **After registration**, select the **View registered end device** option.
253 253  
254 -[[image:lt-22222-l-dev-repo-reg-p2.png]]
223 +[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
255 255  
225 +==== ====
256 256  
257 -==== 3.2.2.3 Adding device manually ====
227 +==== 3.2.2.2 Adding device manually ====
258 258  
259 259  * On the **Register end device** page:
260 260  ** Select the option **Enter end device specifies manually** under **Input method**.
... ... @@ -265,11 +265,11 @@
265 265  ** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
266 266  ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
267 267  
268 -[[image:lt-22222-l-manually-p1.png]]
238 +[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
269 269  
270 270  
271 271  * Register end device page continued...
272 -** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message '//**This end device can be registered on the network**//'
242 +** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'
273 273  ** In the **DevEUI** field, enter the **DevEUI**.
274 274  ** In the **AppKey** field, enter the **AppKey**.
275 275  ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
... ... @@ -276,56 +276,41 @@
276 276  ** Under **After registration**, select the **View registered end device** option.
277 277  ** Click the **Register end device** button.
278 278  
279 -[[image:lt-22222-l-manually-p2.png]]
249 +[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
280 280  
281 281  
282 282  You will be navigated to the **Device overview** page.
283 283  
284 284  
285 -[[image:lt-22222-device-overview.png]]
255 +[[image:lt-22222-device-overview.png||height="625" width="1000"]]
286 286  
287 287  
288 -==== 3.2.2.4 Joining ====
258 +==== 3.2.2.3 Joining ====
289 289  
290 -On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
260 +On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
291 291  
292 -Now power on your LT-22222-L. The **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** The Things Stack network server. The **TX LED** will be on for **5 seconds** after joining the network. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server.
262 +Now power on your LT-22222-L. It will begin joining The Things Stack. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. Once successfully joined, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**).
293 293  
294 294  
295 -[[image:lt-22222-l-joining.png]]
265 +[[image:lt-22222-join-network.png||height="625" width="1000"]]
296 296  
297 297  
268 +By default, you will receive an uplink data message from the device every 10 minutes.
298 298  
299 -==== 3.2.2.5 Uplinks ====
300 -
301 -
302 -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.
303 -
304 304  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.
305 305  
306 306  [[image:lt-22222-ul-payload-decoded.png]]
307 307  
308 308  
309 -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.
275 +If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **End devices** > **LT-22222-L** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
310 310  
311 311  {{info}}
312 312  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.
313 313  {{/info}}
314 314  
315 -[[image:lt-22222-ul-payload-fmt.png]]
281 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
316 316  
317 317  
318 -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]]:
319 -
320 -(% class="wikigeneratedid" %)
321 -[[image:lt-22222-l-js-custom-payload-formatter.png]]
322 -
323 -
324 -==== 3.2.2.6 Downlinks ====
325 -
326 -When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
327 -
328 -
329 329  == 3.3 Working Modes and Uplink Payload formats ==
330 330  
331 331  
... ... @@ -601,19 +601,19 @@
601 601  )))
602 602  
603 603  (((
604 -AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
559 +Other AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
605 605  )))
606 606  
607 607  (((
608 608  **In addition to that, below are the commands for AVI1 Counting:**
609 609  
610 -(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)**
565 +(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI Count to 60)**
611 611  
612 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), the counter increases by 1)**
567 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
613 613  
614 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If the AVI1 voltage is lower than VOLMAX (20000mV =20V), counter increases by 1)**
569 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
615 615  
616 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), counter increases by 1)**
571 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
617 617  )))
618 618  
619 619  
... ... @@ -732,9 +732,9 @@
732 732  
733 733  (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
734 734  
735 -**Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
690 +Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
736 736  
737 -**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
692 +Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
738 738  
739 739   AA: Type Code for this downlink Command:
740 740  
... ... @@ -801,7 +801,7 @@
801 801  
802 802  **Example:**
803 803  
804 -10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW.
759 +10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
805 805  
806 806  
807 807  (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
... ... @@ -830,7 +830,7 @@
830 830  
831 831  **Example:**
832 832  
833 -10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low.
788 +10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
834 834  
835 835  
836 836  (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
... ... @@ -839,22 +839,22 @@
839 839  |(% style="width:64px" %)**bit 7**|(% style="width:68px" %)**bit 6**|(% style="width:63px" %)**bit 5**|(% style="width:66px" %)**bit 4**|(% style="width:109px" %)**bit 3**|(% style="width:93px" %)**bit 2**|(% style="width:109px" %)**bit 1**|(% style="width:99px" %)**bit 0**
840 840  |(% style="width:64px" %)N/A|(% style="width:68px" %)N/A|(% style="width:63px" %)N/A|(% style="width:66px" %)N/A|(% style="width:109px" %)DI2_STATUS|(% style="width:93px" %)DI2_FLAG|(% style="width:109px" %)DI1_STATUS|(% style="width:99px" %)DI1_FLAG
841 841  
842 -* Each bit shows which status has been triggered on this uplink.
797 +* Each bits shows which status has been triggered on this uplink.
843 843  
844 844  **Example:**
845 845  
846 -00000111: This means both DI1 and DI2 triggers are enabled, and this packet is trigger by DI1.
801 +00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
847 847  
848 -00000101: This means both DI1 and DI2 triggers are enabled.
803 +00000101: Means both DI1 and DI2 trigger are enabled.
849 849  
850 850  
851 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled.
806 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable.
852 852  
853 -Downlink command to poll/request MOD6 status:
808 +Downlink command to poll MOD6 status:
854 854  
855 855  **AB 06**
856 856  
857 -When device receives this command, it will send the MOD6 payload.
812 +When device got this command, it will send the MOD6 payload.
858 858  
859 859  
860 860  === 3.3.7 Payload Decoder ===
... ... @@ -893,7 +893,7 @@
893 893  These commands are specially designed for the LT-22222-L. Commands can be sent to the device using options such as an AT command or a LoRaWAN downlink payload.
894 894  
895 895  
896 -==== 3.4.2.1 Set Transmit/Uplink Interval ====
851 +==== 3.4.2.1 Set Transmit Interval ====
897 897  
898 898  Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
899 899  
... ... @@ -901,19 +901,12 @@
901 901  
902 902  (% border="2" style="width:500px" %)
903 903  |**Command**|AT+TDC=<time>
904 -|**Parameters**|**time **: uplink interval in milliseconds
905 -|**Get**|AT+TDC=?
906 -|**Response**|(((
907 -current uplink interval
908 -
909 -OK
910 -)))
911 -|**Set**|AT+TDC=<time>
912 -|**Response**|OK
859 +|**Response**|
860 +|**Parameters**|**time** : uplink interval is in milliseconds
913 913  |**Example**|(((
914 914  AT+TDC=30000
915 915  
916 -Sets the uplink interval to **30 seconds** (30000 milliseconds)
864 +Sets the uplink interval to 30,000 milliseconds (30 seconds)
917 917  )))
918 918  
919 919  (% style="color:#037691" %)**Downlink payload**
... ... @@ -925,18 +925,16 @@
925 925  |**Parameters**|(((
926 926  **prefix** : 0x01
927 927  
928 -**time** : uplink interval in **seconds**, represented by **3  bytes** in **hexadecimal**.
876 +**time** : uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
929 929  )))
930 930  |**Example**|(((
931 -01 **00 00 1E**
879 +01 **00 75 30**
932 932  
933 -Sets the uplink interval to **30 seconds**
881 +Sets the uplink interval to 30,000 milliseconds (30 seconds)
934 934  
935 -Conversion: 30 (dec) = 00 00 1E (hex)
883 +Conversion: 30000 (dec) = 00 75 30 (hex)
936 936  
937 -See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30]]
938 -
939 -[[image:Screenshot 2024-11-23 at 18.27.11.png]]
885 +See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]]
940 940  )))
941 941  
942 942  ==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
... ... @@ -946,7 +946,8 @@
946 946  (% style="color:#037691" %)**AT command**
947 947  
948 948  (% border="2" style="width:500px" %)
949 -|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MOD=<working_mode>
895 +|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE=<working_mode>
896 +|(% style="width:97px" %)**Response**|(% style="width:413px" %)
950 950  |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)(((
951 951  **working_mode** :
952 952  
... ... @@ -962,18 +962,6 @@
962 962  
963 963  6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5
964 964  )))
965 -|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=?
966 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
967 -Current working mode
968 -
969 -OK
970 -)))
971 -|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode>
972 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
973 -Attention:Take effect after ATZ
974 -
975 -OK
976 -)))
977 977  |(% style="width:97px" %)**Example**|(% style="width:413px" %)(((
978 978  AT+MOD=2
979 979  
... ... @@ -996,13 +996,13 @@
996 996  Sets the device to working mode 2 (Double DI Counting + DO + RO)
997 997  )))
998 998  
999 -==== 3.4.2.3 Request an uplink from the device ====
934 +==== 3.4.2.3 Poll an uplink ====
1000 1000  
1001 -Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
936 +Requests an uplink from LT-22222-L.
1002 1002  
1003 1003  (% style="color:#037691" %)**AT command**
1004 1004  
1005 -There is no AT Command available for this feature.
940 +There is no AT Command to request an uplink from LT-22222-L
1006 1006  
1007 1007  (% style="color:#037691" %)**Downlink payload**
1008 1008  
... ... @@ -1010,7 +1010,7 @@
1010 1010  |(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF
1011 1011  |(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08
1012 1012  |(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
1013 -08 **FF**
948 +08 FF
1014 1014  
1015 1015  Requests an uplink from LT-22222-L.
1016 1016  )))
... ... @@ -1044,7 +1044,7 @@
1044 1044  |(% style="width:97px" %)**Parameters**|(% style="width:401px" %)(((
1045 1045  **prefix** : 0x0A 06 (two bytes in hexadecimal)
1046 1046  
1047 -**enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
982 +**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
1048 1048  )))
1049 1049  |(% style="width:97px" %)**Example**|(% style="width:401px" %)(((
1050 1050  0A 06 **01**
... ... @@ -1052,13 +1052,13 @@
1052 1052  Enable trigger mode for the current working mode
1053 1053  )))
1054 1054  
1055 -==== 3.4.2.5 Request trigger settings ====
990 +==== 3.4.2.5 Poll trigger settings ====
1056 1056  
1057 -Requests the trigger settings.
992 +Polls the trigger settings.
1058 1058  
1059 1059  (% style="color:#037691" %)**AT Command:**
1060 1060  
1061 -There is no AT Command available for this feature.
996 +There is no AT Command for this feature.
1062 1062  
1063 1063  (% style="color:#037691" %)**Downlink Payload**
1064 1064  
... ... @@ -1198,6 +1198,9 @@
1198 1198  )))
1199 1199  |(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
1200 1200  
1136 +(% class="wikigeneratedid" %)
1137 +==== ====
1138 +
1201 1201  ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1202 1202  
1203 1203  Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
... ... @@ -1272,6 +1272,7 @@
1272 1272  )))
1273 1273  |(% style="width:104px" %)**Note**|(% style="width:387px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1274 1274  
1213 +
1275 1275  (% style="color:#037691" %)**Downlink Payload**
1276 1276  
1277 1277  (% border="2" style="width:500px" %)
... ... @@ -1294,6 +1294,7 @@
1294 1294  )))
1295 1295  |(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1296 1296  
1236 +
1297 1297  ==== 3.4.2.11 Trigger – Set minimum interval ====
1298 1298  
1299 1299  Sets the AV and AC trigger minimum interval. The device won't respond to a second trigger within this set time after the first trigger.
... ... @@ -1329,6 +1329,7 @@
1329 1329  )))
1330 1330  |(% style="width:112px" %)Note|(% style="width:386px" %)(% style="color:red" %)**The time must be greater than 5 minutes.**
1331 1331  
1272 +
1332 1332  ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
1333 1333  
1334 1334  Controls the digital outputs DO1, DO2, and DO3
... ... @@ -1361,11 +1361,11 @@
1361 1361  (((
1362 1362  01: Low,  00: High,  11: No action
1363 1363  
1364 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:383px" %)
1365 -|(% 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**
1366 -|(% style="width:126px" %)02  01  00  11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action
1367 -|(% style="width:126px" %)02  00  11  01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low
1368 -|(% style="width:126px" %)02  11  01  00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High
1305 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
1306 +|(% 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**
1307 +|02  01  00  11|Low|High|No Action
1308 +|02  00  11  01|High|No Action|Low
1309 +|02  11  01  00|No Action|Low|High
1369 1369  )))
1370 1370  
1371 1371  (((
... ... @@ -1379,28 +1379,33 @@
1379 1379  )))
1380 1380  )))
1381 1381  
1323 +(% class="wikigeneratedid" %)
1324 +==== ====
1325 +
1382 1382  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1383 1383  
1384 1384  
1385 1385  * (% style="color:#037691" %)**AT Command**
1386 1386  
1387 -There is no AT command to control the digital output.
1331 +There is no AT Command to control Digital Output
1388 1388  
1389 1389  
1390 1390  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
1391 1391  
1392 -(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control
1336 +(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Set DO1/DO2/DO3 output with time control
1393 1393  
1338 +
1394 1394  This is to control the digital output time of DO pin. Include four bytes:
1395 1395  
1396 -(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)
1341 +(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
1397 1397  
1398 -(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode
1343 +(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
1399 1399  
1400 -**01:** DO pins revert to their original state after the timeout.
1401 -**00:** DO pins switch to an inverted state after the timeout.
1345 +01: DO pins will change back to original state after timeout.
1402 1402  
1347 +00: DO pins will change to an inverter state after timeout 
1403 1403  
1349 +
1404 1404  (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1405 1405  
1406 1406  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
... ... @@ -1409,7 +1409,7 @@
1409 1409  |0x00|DO1 set to high
1410 1410  |0x11|DO1 NO Action
1411 1411  
1412 -(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:
1358 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
1413 1413  
1414 1414  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1415 1415  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
... ... @@ -1417,7 +1417,7 @@
1417 1417  |0x00|DO2 set to high
1418 1418  |0x11|DO2 NO Action
1419 1419  
1420 -(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:
1366 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
1421 1421  
1422 1422  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1423 1423  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
... ... @@ -1425,7 +1425,7 @@
1425 1425  |0x00|DO3 set to high
1426 1426  |0x11|DO3 NO Action
1427 1427  
1428 -(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)
1374 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
1429 1429  
1430 1430  
1431 1431  (% style="color:red" %)**Note: **
... ... @@ -1434,7 +1434,7 @@
1434 1434  
1435 1435   Before firmware v1.6.0, the latch time only supported 2 bytes.
1436 1436  
1437 -(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1383 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1438 1438  
1439 1439  
1440 1440  **Example payload:**
... ... @@ -1461,16 +1461,16 @@
1461 1461  
1462 1462  * (% style="color:#037691" %)**AT Command:**
1463 1463  
1464 -There is no AT Command to control the Relay Output
1410 +There is no AT Command to control Relay Output
1465 1465  
1466 1466  
1467 1467  * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
1468 1468  
1469 -(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Sets RO1/RO2 output
1415 +(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
1470 1470  
1471 1471  
1472 1472  (((
1473 -If the payload is 0x030100, it means setting RO1 to close and RO2 to open.
1419 +If payload is 0x030100, it means setting RO1 to close and RO2 to open.
1474 1474  )))
1475 1475  
1476 1476  (((
... ... @@ -1488,7 +1488,7 @@
1488 1488  |03  00  01|Open|Close
1489 1489  )))
1490 1490  
1491 -(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1437 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
1492 1492  
1493 1493  
1494 1494  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
... ... @@ -1497,19 +1497,19 @@
1497 1497  
1498 1498  * (% style="color:#037691" %)**AT Command:**
1499 1499  
1500 -There is no AT Command to control the Relay Output
1446 +There is no AT Command to control Relay Output
1501 1501  
1502 1502  
1503 1503  * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1504 1504  
1505 -(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
1451 +(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
1506 1506  
1507 1507  
1508 -This controls the relay output time and includes 4 bytes:
1454 +This is to control the relay output time. It includes four bytes:
1509 1509  
1510 -(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
1456 +(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
1511 1511  
1512 -(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
1458 +(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
1513 1513  
1514 1514  01: Relays will change back to their original state after timeout.
1515 1515  
... ... @@ -1516,12 +1516,12 @@
1516 1516  00: Relays will change to the inverter state after timeout.
1517 1517  
1518 1518  
1519 -(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
1465 +(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
1520 1520  
1521 1521  [[image:image-20221008095908-1.png||height="364" width="564"]]
1522 1522  
1523 1523  
1524 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms
1470 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
1525 1525  
1526 1526  
1527 1527  (% style="color:red" %)**Note:**
... ... @@ -1531,7 +1531,7 @@
1531 1531   Before firmware v1.6.0, the latch time only supported 2 bytes.
1532 1532  
1533 1533  
1534 -(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1480 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1535 1535  
1536 1536  
1537 1537  **Example payload:**
... ... @@ -1559,362 +1559,137 @@
1559 1559  
1560 1560  When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1561 1561  
1562 -(% style="color:#037691" %)**AT Command**
1508 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX   ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1563 1563  
1564 -(% border="2" style="width:500px" %)
1565 -|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage>,<logic>
1566 -|(% style="width:137px" %)**Response**|(% style="width:361px" %)
1567 -|(% style="width:137px" %)**Parameters**|(% style="width:361px" %)(((
1568 -**voltage** : voltage threshold in mV
1510 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):**
1569 1569  
1570 -**logic**:
1512 +(% style="color:blue" %)**0xA5 aa bb cc   ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc
1571 1571  
1572 -**0** : lower than
1573 1573  
1574 -**1**: higher than
1575 1575  
1576 -if you leave logic parameter blank, it is considered 0
1577 -)))
1578 -|(% style="width:137px" %)**Examples**|(% style="width:361px" %)(((
1579 -AT+VOLMAX=20000
1580 -
1581 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
1582 -
1583 -AT+VOLMAX=20000,0
1584 -
1585 -If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1
1586 -
1587 -AT+VOLMAX=20000,1
1588 -
1589 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
1590 -)))
1591 -
1592 -(% style="color:#037691" %)**Downlink Payload**
1593 -
1594 -(% border="2" style="width:500px" %)
1595 -|(% style="width:140px" %)**Payload**|(% style="width:358px" %)<prefix><voltage><logic>
1596 -|(% style="width:140px" %)**Parameters**|(% style="width:358px" %)(((
1597 -**prefix** : A5 (hex)
1598 -
1599 -**voltage** : voltage threshold in mV (2 bytes in hex)
1600 -
1601 -**logic**: (1 byte in hexadecimal)
1602 -
1603 -**0** : lower than
1604 -
1605 -**1**: higher than
1606 -
1607 -if you leave logic parameter blank, it is considered 1 (higher than)
1608 -)))
1609 -|(% style="width:140px" %)**Example**|(% style="width:358px" %)(((
1610 -A5 **4E 20**
1611 -
1612 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
1613 -
1614 -A5 **4E 20 00**
1615 -
1616 -If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1
1617 -
1618 -A5 **4E 20 01**
1619 -
1620 -If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
1621 -)))
1622 -
1623 1623  ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ====
1624 1624  
1625 -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.
1518 +This feature allows users to pre-configure specific count numbers for various counting parameters such as count1, count2, or AV1 count. Use the AT command to set the desired count number for each configuration.
1626 1626  
1627 -(% style="color:#037691" %)**AT Command**
1520 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) **
1628 1628  
1629 -(% border="2" style="width:500px" %)
1630 -|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter>,<number>
1631 -|(% style="width:134px" %)**Response**|(% style="width:364px" %)
1632 -|(% style="width:134px" %)**Parameters**|(% style="width:364px" %)(((
1633 -**counting_parameter** :
1522 +(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count
1634 1634  
1635 -1: COUNT1
1524 +(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set
1636 1636  
1637 -2: COUNT2
1638 1638  
1639 -3: AVI1 Count
1527 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):**
1640 1640  
1641 -**number** : Start number
1642 -)))
1643 -|(% style="width:134px" %)**Example**|(% style="width:364px" %)(((
1644 -AT+SETCNT=1,10
1529 +(% style="color:blue" %)**0x A8 aa bb cc dd ee     ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
1645 1645  
1646 -Sets the COUNT1 to 10.
1647 -)))
1648 1648  
1649 -(% style="color:#037691" %)**Downlink Payload**
1650 1650  
1651 -(% border="2" style="width:500px" %)
1652 -|(% style="width:135px" %)**Payload**|(% style="width:363px" %)<prefix><counting_parameter><number>
1653 -|(% style="width:135px" %)**Parameters**|(% style="width:363px" %)(((
1654 -prefix : A8 (hex)
1655 -
1656 -**counting_parameter** : (1 byte in hexadecimal)
1657 -
1658 -1: COUNT1
1659 -
1660 -2: COUNT2
1661 -
1662 -3: AVI1 Count
1663 -
1664 -**number** : Start number, 4 bytes in hexadecimal
1665 -)))
1666 -|(% style="width:135px" %)**Example**|(% style="width:363px" %)(((
1667 -A8 **01 00 00 00 0A**
1668 -
1669 -Sets the COUNT1 to 10.
1670 -)))
1671 -
1672 1672  ==== 3.4.2.18 Counting ~-~- Clear Counting ====
1673 1673  
1674 -This command clears the counting in counting mode.
1535 +This feature clears the counting in counting mode.
1675 1675  
1676 -(% style="color:#037691" %)**AT Command**
1537 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
1677 1677  
1678 -(% border="2" style="width:500px" %)
1679 -|(% style="width:142px" %)**Command**|(% style="width:356px" %)AT+CLRCOUNT
1680 -|(% style="width:142px" %)**Response**|(% style="width:356px" %)-
1539 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
1681 1681  
1682 -(% style="color:#037691" %)**Downlink Payload**
1541 +(% style="color:blue" %)**0x A6 01    ** (%%)~/~/ clear all counting
1683 1683  
1684 -(% border="2" style="width:500px" %)
1685 -|(% style="width:141px" %)**Payload**|(% style="width:357px" %)<prefix><clear?>
1686 -|(% style="width:141px" %)**Parameters**|(% style="width:357px" %)(((
1687 -prefix : A6 (hex)
1688 1688  
1689 -clear? : 01 (hex)
1690 -)))
1691 -|(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
1692 1692  
1693 -==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
1545 +==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1694 1694  
1695 -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.
1547 +This feature allows you to configure the device to save its counting result to internal flash memory at specified intervals. By setting a save time, the device will periodically store the counting data to prevent loss in case of power failure. The save interval can be adjusted to suit your requirements, with a minimum value of 30 seconds.
1696 1696  
1697 -(% style="color:#037691" %)**AT Command**
1549 +* (% style="color:#037691" %)**AT Command:**
1698 1698  
1699 -(% border="2" style="width:500px" %)
1700 -|(% style="width:124px" %)**Command**|(% style="width:374px" %)AT+COUTIME=<time>
1701 -|(% style="width:124px" %)**Response**|(% style="width:374px" %)
1702 -|(% style="width:124px" %)**Parameters**|(% style="width:374px" %)time : seconds (0 to 16777215)
1703 -|(% style="width:124px" %)**Example**|(% style="width:374px" %)(((
1704 -AT+COUTIME=60
1551 +(% style="color:blue" %)**AT+COUTIME=60  **(%%)~/~/ Sets the save time to 60 seconds. The device will save the counting result in internal flash every 60 seconds. (Min value: 30 seconds)
1705 1705  
1706 -Sets the device to save its counting results to the memory every 60 seconds.
1707 -)))
1708 1708  
1709 -(% style="color:#037691" %)**Downlink Payload**
1554 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
1710 1710  
1711 -(% border="2" style="width:500px" %)
1712 -|(% style="width:123px" %)**Payload**|(% style="width:375px" %)<prefix><time>
1713 -|(% style="width:123px" %)**Parameters**|(% style="width:375px" %)(((
1714 -prefix : A7
1556 +(% style="color:blue" %)**0x A7 aa bb cc     ** (%%)~/~/ same as AT+COUTIME =aa bb cc,
1715 1715  
1716 -time : seconds, 3 bytes in hexadecimal
1558 +(((
1559 +Range: aa bb cc:0 to 16777215,  (unit: seconds)
1717 1717  )))
1718 -|(% style="width:123px" %)**Example**|(% style="width:375px" %)(((
1719 -A7 **00 00 3C**
1720 1720  
1721 -Sets the device to save its counting results to the memory every 60 seconds.
1722 -)))
1723 1723  
1724 -==== 3.4.2.20 Reset saved RO and DO states ====
1725 1725  
1726 -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.
1564 +==== 3.4.2.20 Reset save RO DO state ====
1727 1727  
1728 -(% style="color:#037691" %)**AT Command**
1566 +This feature allows you to reset the saved relay output (RO) and digital output (DO) states when the device joins the network. By configuring this setting, you can control whether the device should retain or reset the relay states after a reset and rejoin to the network.
1729 1729  
1730 -(% border="2" style="width:500px" %)
1731 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state>
1732 -|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1733 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1734 -**state** :
1568 +* (% style="color:#037691" %)**AT Command:**
1735 1735  
1736 -**0** : RODO will close when the device joins the network. (default)
1570 +(% style="color:blue" %)**AT+RODORESET=1    **(%%)~/~/ RODO will close when the device joining the network. (default)
1737 1737  
1738 -**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.
1739 -)))
1740 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1741 -(% style="color:blue" %)**AT+RODORESET=1 **
1572 +(% style="color:blue" %)**AT+RODORESET=0    **(%%)~/~/ After the device is reset, the previously saved RODO state (only MOD2 to MOD5) is read, and its state will not change when the device reconnects to the network.
1742 1742  
1743 -RODO will close when the device joins the network. (default)
1744 1744  
1745 -(% style="color:blue" %)**AT+RODORESET=0 **
1575 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):**
1746 1746  
1747 -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.
1748 -)))
1577 +(% style="color:blue" %)**0x AD aa      ** (%%)~/~/ same as AT+RODORET =aa
1749 1749  
1750 -(% style="color:#037691" %)**Downlink Payload**
1751 1751  
1752 -(% border="2" style="width:500px" %)
1753 -|(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state>
1754 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1755 -**prefix** : AD
1756 1756  
1757 -**state** :
1758 -
1759 -**0** : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal.
1760 -
1761 -**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
1762 -)))
1763 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1764 -AD **01**
1765 -
1766 -RODO will close when the device joins the network. (default)
1767 -
1768 -AD **00**
1769 -
1770 -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.
1771 -)))
1772 -
1773 1773  ==== 3.4.2.21 Encrypted payload ====
1774 1774  
1775 -This command allows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption.
1583 +This feature allows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption.
1776 1776  
1777 -(% style="color:#037691" %)**AT Command:**
1585 +* (% style="color:#037691" %)**AT Command:**
1778 1778  
1779 -(% border="2" style="width:500px" %)
1780 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state>
1781 -|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1782 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1783 -**state** :
1587 +(% style="color:blue" %)**AT+DECRYPT=1  ** (%%)~/~/ The payload is uploaded without encryption
1784 1784  
1785 -**1** : The payload is uploaded without encryption
1589 +(% style="color:blue" %)**AT+DECRYPT=0    **(%%)~/~/  Encrypt when uploading payload (default)
1786 1786  
1787 -**0** : The payload is encrypted when uploaded (default)
1788 -)))
1789 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1790 -AT+DECRYPT=1
1791 1791  
1792 -The payload is uploaded without encryption
1793 1793  
1794 -AT+DECRYPT=0
1795 -
1796 -The payload is encrypted when uploaded (default)
1797 -)))
1798 -
1799 -There is no downlink payload for this configuration.
1800 -
1801 -
1802 1802  ==== 3.4.2.22 Get sensor value ====
1803 1803  
1804 -This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1805 1805  
1806 -(% style="color:#037691" %)**AT Command**
1596 +* (% style="color:#037691" %)**AT Command:**
1807 1807  
1808 -(% border="2" style="width:500px" %)
1809 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
1810 -|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1811 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1812 -**state** :
1598 +(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port retrieves the reading of the current sensor.
1813 1813  
1814 -**0 **: Retrieves the current sensor reading via the serial port.
1600 +(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.
1815 1815  
1816 -**1 **: Retrieves and uploads the current sensor reading via the serial port.
1817 -)))
1818 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1819 -AT+GETSENSORVALUE=0
1820 1820  
1821 -Retrieves the current sensor reading via the serial port.
1822 1822  
1823 -AT+GETSENSORVALUE=1
1604 +==== 3.4.2.23 Resets the downlink packet count ====
1824 1824  
1825 -Retrieves and uplinks the current sensor reading via the serial port.
1826 -)))
1827 1827  
1828 -There is no downlink payload for this configuration.
1607 +* (% style="color:#037691" %)**AT Command:**
1829 1829  
1609 +(% 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)
1830 1830  
1831 -==== 3.4.2.23 Resetting the downlink packet count ====
1611 +(% 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.
1832 1832  
1833 -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.
1834 1834  
1835 -(% style="color:#037691" %)**AT Command**
1836 1836  
1837 -(% border="2" style="width:500px" %)
1838 -|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
1839 -|(% style="width:130px" %)**Response**|(% style="width:368px" %)(((
1840 -
1841 -)))
1842 -|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)(((
1843 -**state **:
1844 -
1845 -**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).
1846 -
1847 -
1848 -**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.
1849 -)))
1850 -|(% style="width:130px" %)**Example**|(% style="width:368px" %)(((
1851 -AT+DISFCNTCHECK=0
1852 -
1853 -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).
1854 -
1855 -AT+DISFCNTCHECK=1
1856 -
1857 -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.
1858 -)))
1859 -
1860 -There is no downlink payload for this configuration.
1861 -
1862 -
1863 1863  ==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ====
1864 1864  
1865 1865  
1866 -This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceeds the allowed byte limit for the current data rate (DR). The command provides two modes: one enables splitting the data into batches to ensure compliance with the byte limit, while the other prioritizes the payload and ignores the MACANS in cases of overflow.
1618 +* (% style="color:#037691" %)**AT Command:**
1867 1867  
1868 -(% style="color:#037691" %)**AT Command**
1620 +(% 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)
1869 1869  
1870 -(% border="2" style="width:500px" %)
1871 -|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state>
1872 -|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1873 -|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1874 -**state** :
1622 +(% 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.
1875 1875  
1876 -**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)
1877 1877  
1878 -**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.
1879 -)))
1880 -|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1881 -AT+DISMACANS=0
1625 +* (% style="color:#037691" %)**Downlink Payload **(%%)**:**
1882 1882  
1883 -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)
1627 +(% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set  the DISMACANS=1
1884 1884  
1885 -AT+DISMACANS=1
1886 1886  
1887 -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.
1888 -)))
1889 1889  
1890 -(% style="color:#037691" %)**Downlink Payload**
1891 -
1892 -(% border="2" style="width:500px" %)
1893 -|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state>
1894 -|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)(((
1895 -**prefix** : 21
1896 -
1897 -**state** : (2 bytes in hexadecimal)
1898 -
1899 -**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)
1900 -
1901 -**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.
1902 -)))
1903 -|(% style="width:126px" %)**Example**|(% style="width:372px" %)(((
1904 -21 **00 01**
1905 -
1906 -Set DISMACANS=1
1907 -)))
1908 -
1909 1909  ==== 3.4.2.25 Copy downlink to uplink ====
1910 1910  
1911 -This command enables the device to immediately uplink the payload of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100.
1912 1912  
1913 -(% style="color:#037691" %)**AT Command**(%%)**:**
1634 +* (% style="color:#037691" %)**AT Command**(%%)**:**
1914 1914  
1915 -(% style="color:blue" %)**AT+RPL=5**   (%%) ~/~/ After receiving a downlink payload from the server, the device will immediately uplink the payload back to the server using port number 100.
1636 +(% 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.
1916 1916  
1917 -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.
1638 +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.
1918 1918  
1919 1919  
1920 1920  [[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"]]
... ... @@ -1921,26 +1921,22 @@
1921 1921  
1922 1922  For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1923 1923  
1645 +
1646 +
1924 1924  [[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"]]
1925 1925  
1926 1926  For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
1927 1927  
1928 1928  
1929 -(% style="color:#037691" %)**Downlink Payload**(%%)**:**
1930 1930  
1931 -There is no downlink option available for this feature.
1653 +==== 3.4.2.26 Query version number and frequency band 、TDC ====
1932 1932  
1933 1933  
1934 -==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
1935 -
1936 -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.
1937 -
1938 1938  * (((
1939 1939  (% style="color:#037691" %)**Downlink Payload**(%%)**:**
1940 1940  
1941 -(% style="color:blue" %)**26 01  ** (%%) ~/~/  The downlink payload 26 01 is used to query the device's firmware version, frequency band, sub band, and TDC time.
1659 +(% style="color:blue" %)**26 01  ** (%%) ~/~/  Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
1942 1942  
1943 -
1944 1944  
1945 1945  )))
1946 1946  
... ... @@ -1966,17 +1966,15 @@
1966 1966  The username and  password (API key) you created here are required in the next section.
1967 1967  {{/info}}
1968 1968  
1969 -[[image:tts-mqtt-integration.png]]
1686 +[[image:tts-mqtt-integration.png||height="625" width="1000"]]
1970 1970  
1971 1971  === 3.5.2 Configuring ThingsEye.io ===
1972 1972  
1973 -The ThingsEye.io IoT platform is not open for self-registration at the moment. If you are interested in testing the platform, please send your project information to admin@thingseye.io, and we will create an account for you.
1974 -
1975 1975  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
1976 1976  * Under the **Integrations center**, click **Integrations**.
1977 1977  * Click the **Add integration** button (the button with the **+** symbol).
1978 1978  
1979 -[[image:thingseye-io-step-1.png]]
1694 +[[image:thingseye-io-step-1.png||height="625" width="1000"]]
1980 1980  
1981 1981  
1982 1982  On the **Add integration** window, configure the following:
... ... @@ -1991,7 +1991,7 @@
1991 1991  ** Allow create devices or assets
1992 1992  * Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
1993 1993  
1994 -[[image:thingseye-io-step-2.png]]
1709 +[[image:thingseye-io-step-2.png||height="625" width="1000"]]
1995 1995  
1996 1996  
1997 1997  **Uplink data converter:**
... ... @@ -2002,7 +2002,7 @@
2002 2002  * 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]].
2003 2003  * Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
2004 2004  
2005 -[[image:thingseye-io-step-3.png]]
1720 +[[image:thingseye-io-step-3.png||height="625" width="1000"]]
2006 2006  
2007 2007  
2008 2008  **Downlink data converter (this is an optional step):**
... ... @@ -2013,7 +2013,7 @@
2013 2013  * 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]].
2014 2014  * Click the **Next** button. You will be navigated to the **Connection** tab.
2015 2015  
2016 -[[image:thingseye-io-step-4.png]]
1731 +[[image:thingseye-io-step-4.png||height="625" width="1000"]]
2017 2017  
2018 2018  
2019 2019  **Connection:**
... ... @@ -2020,7 +2020,7 @@
2020 2020  
2021 2021  * Choose **Region** from the **Host type**.
2022 2022  * 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/...).
2023 -* 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**).
1738 +* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username **and **password **can be found on the MQTT integration page of your The Things Stack account (see Configuring The Things Stack).
2024 2024  * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
2025 2025  
2026 2026  [[image:message-1.png]]
... ... @@ -2028,13 +2028,13 @@
2028 2028  
2029 2029  * Click the **Add** button.
2030 2030  
2031 -[[image:thingseye-io-step-5.png]]
1746 +[[image:thingseye-io-step-5.png||height="625" width="1000"]]
2032 2032  
2033 2033  
2034 -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.
1749 +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.
2035 2035  
2036 2036  
2037 -[[image:thingseye.io_integrationsCenter_integrations.png]]
1752 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
2038 2038  
2039 2039  
2040 2040  ==== 3.5.2.1 Viewing integration details ====
... ... @@ -2041,13 +2041,13 @@
2041 2041  
2042 2042  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.
2043 2043  
2044 -[[image:integration-details.png]]
1759 +[[image:integration-details.png||height="686" width="1000"]]
2045 2045  
2046 2046  
2047 2047  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.
2048 2048  
2049 2049  {{info}}
2050 -See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
1765 +See also ThingsEye documentation.
2051 2051  {{/info}}
2052 2052  
2053 2053  ==== **3.5.2.2 Viewing events** ====
... ... @@ -2057,12 +2057,12 @@
2057 2057  * Select **Debug **from the **Event type** dropdown.
2058 2058  * Select the** time frame** from the **time window**.
2059 2059  
2060 -[[image:thingseye-events.png]]
1775 +[[image:thingseye-events.png||height="686" width="1000"]]
2061 2061  
2062 2062  
2063 -* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
1778 +* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
2064 2064  
2065 -[[image:thingseye-json.png]]
1780 +[[image:thingseye-json.png||width="1000"]]
2066 2066  
2067 2067  
2068 2068  ==== **3.5.2.3 Deleting an integration** ====
... ... @@ -2070,17 +2070,12 @@
2070 2070  If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
2071 2071  
2072 2072  
2073 -==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
2074 -
2075 -This will be added soon.
2076 -
2077 -
2078 2078  == 3.6 Interface Details ==
2079 2079  
2080 2080  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
2081 2081  
2082 2082  
2083 -Supports** NPN-type **sensors.
1793 +Supports NPN-type sensors.
2084 2084  
2085 2085  [[image:1653356991268-289.png]]
2086 2086  
... ... @@ -2202,15 +2202,15 @@
2202 2202  )))
2203 2203  
2204 2204  
2205 -(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor
1915 +(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
2206 2206  
2207 -From the DI 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 difference on its own.
1917 +From the DI port circuit above, you can see that activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference.
2208 2208  
2209 -To detect a Dry Contact, you can supply a power source to one of the pins of the Dry Contact. A reference circuit diagram is shown below.
1919 +To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.
2210 2210  
2211 2211  [[image:image-20230616235145-1.png]]
2212 2212  
2213 -(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector
1923 +(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
2214 2214  
2215 2215  [[image:image-20240219115718-1.png]]
2216 2216  
... ... @@ -2286,7 +2286,7 @@
2286 2286  [[image:image-20220524100215-10.png||height="382" width="723"]]
2287 2287  
2288 2288  
2289 -== 3.7 LED Indicators ==
1999 +== 3.7 LEDs Indicators ==
2290 2290  
2291 2291  The table below lists the behavior of LED indicators for each port function.
2292 2292  
... ... @@ -2325,14 +2325,13 @@
2325 2325  == 4.1 Connecting the LT-22222-L to a PC ==
2326 2326  
2327 2327  (((
2328 -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.
2038 +You can use a USB-to-TTL adapter along with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below.
2329 2329  
2330 -[[image:usb-ttl-audio-jack-connection.jpg]]
2331 -
2332 -
2040 +[[image:usb-ttl-programming.png]]
2333 2333  )))
2334 2334  
2335 2335  
2044 +
2336 2336  (((
2337 2337  On the PC, you need to set the (% style="color:#4f81bd" %)**serial tool **(%%)(such as [[PuTTY>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]] or [[SecureCRT>>https://www.vandyke.com/cgi-bin/releases.php?product=securecrt]]) to a baud rate of (% style="color:green" %)**9600**(%%) to access the serial console of LT-22222-L. Access to AT commands is disabled by default, and a password (default: (% style="color:green" %)**123456**)(%%) must be entered to enable AT command access, as shown below:
2338 2338  )))
... ... @@ -2362,39 +2362,39 @@
2362 2362  * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
2363 2363  * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
2364 2364  * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
2365 -* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2366 -* **##AT+DR##**:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
2367 -* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2368 -* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)
2369 -* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency
2370 -* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2371 -* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2372 -* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2373 -* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2374 -* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2375 -* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2376 -* ##**AT+NWKID**##: Get or set the Network ID
2377 -* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)
2378 -* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)
2379 -* ##**AT+CLASS**##: Get or set the Device Class
2380 -* ##**AT+JOIN**##: Join network
2381 -* ##**AT+NJS**##: Get OTAA Join Status
2382 -* ##**AT+SENDB**##: Send hexadecimal data along with the application port
2383 -* ##**AT+SEND**##: Send text data along with the application port
2384 -* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)
2385 -* ##**AT+RECV**##: Print last received data in raw format
2386 -* ##**AT+VER**##: Get current image version and Frequency Band
2387 -* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)
2388 -* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)
2389 -* ##**AT+SNR**##: Get the SNR of the last received packet
2390 -* ##**AT+RSSI**##: Get the RSSI of the last received packet
2391 -* ##**AT+TDC**##: Get or set the application data transmission interval in ms
2392 -* ##**AT+PORT**##: Get or set the application port
2393 -* ##**AT+DISAT**##: Disable AT commands
2394 -* ##**AT+PWORD**##: Set password, max 9 digits
2395 -* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2396 -* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470
2397 -* ##**AT+CFG**##: Print all settings
2074 +* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2075 +* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
2076 +* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2077 +* AT+PNM: Get or set the public network mode. (0: off, 1: on)
2078 +* AT+RX2FQ: Get or set the Rx2 window frequency
2079 +* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2080 +* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2081 +* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2082 +* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2083 +* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2084 +* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2085 +* AT+NWKID: Get or set the Network ID
2086 +* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
2087 +* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
2088 +* AT+CLASS: Get or set the Device Class
2089 +* AT+JOIN: Join network
2090 +* AT+NJS: Get OTAA Join Status
2091 +* AT+SENDB: Send hexadecimal data along with the application port
2092 +* AT+SEND: Send text data along with the application port
2093 +* AT+RECVB: Print last received data in binary format (with hexadecimal values)
2094 +* AT+RECV: Print last received data in raw format
2095 +* AT+VER: Get current image version and Frequency Band
2096 +* AT+CFM: Get or Set the confirmation mode (0-1)
2097 +* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
2098 +* AT+SNR: Get the SNR of the last received packet
2099 +* AT+RSSI: Get the RSSI of the last received packet
2100 +* AT+TDC: Get or set the application data transmission interval in ms
2101 +* AT+PORT: Get or set the application port
2102 +* AT+DISAT: Disable AT commands
2103 +* AT+PWORD: Set password, max 9 digits
2104 +* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2105 +* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
2106 +* AT+CFG: Print all settings
2398 2398  )))
2399 2399  
2400 2400  
... ... @@ -2559,7 +2559,7 @@
2559 2559  You will need the following things before proceeding:
2560 2560  
2561 2561  * 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2562 -* USB to TTL adapter/converter
2271 +* USB to TTL adapter
2563 2563  * 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)
2564 2564  * 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.
2565 2565  
... ... @@ -2569,7 +2569,7 @@
2569 2569  
2570 2570  Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2571 2571  
2572 -[[image:usb-ttl-audio-jack-connection.jpg]]
2281 +[[image:usb-ttl-programming.png]]
2573 2573  
2574 2574  
2575 2575  
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
lorawan-nw.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -250.6 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
lt33222-l.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -31.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