Changes for page LT-22222-L -- LoRa I/O Controller User Manual

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 7 added, 0 removed)
  • Screenshot 2024-11-23 at 18.27.11.png
  • dragino-lorawan-nw-lt-22222-n.jpg
  • dragino-ttn-te.jpg
  • lorawan-nw.jpg
  • lt-22222-l-joining.png
  • lt33222-l.jpg
  • usb-ttl-audio-jack-connection.jpg

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.pradeeka
	1	+XWiki.Xiaoling

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 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 end device designed to provide seamless wireless long-range connectivity with various I/O options, including analog current and voltage inputs, digital inputs and outputs, and relay outputs.
31	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,23 +40,24 @@
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 Network), you can select a network and register the LT-22222-L I/O controller with it.
	43	+* If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Stack Community Network), you can select a network and register the LT-22222-L I/O controller with it.
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}}
50	50	)))
51	51
52	52	(((
53		-[[image:1653295757274-912.png]]
54		-
55	55
	50	+
	51	+The network diagram below illustrates how the LT-22222-L communicates with a typical LoRaWAN network.
56	56	)))
57	57
	54	+(% class="wikigeneratedid" %)
	55	+[[image:lorawan-nw.jpg||height="354" width="900"]]
	56	+
	57	+
58	58	== 1.2 Specifications ==
59	59
	60	+
60	60	(% style="color:#037691" %)**Hardware System:**
61	61
62	62	* STM32L072xxxx MCU
...	...	@@ -115,24 +115,41 @@
115	115	* Smart cities
116	116	* Smart factory
117	117
118		-== 2. Assembling the device ==
	119	+== 1.5 Hardware Variants ==
119	119
	121	+
	122	+(% border="1" cellspacing="3" style="width:510px" %)
	123	+|(% style="width:94px" %)**Model**|(% style="width:172px" %)**Photo**|(% style="width:244px" %)**Description**
	124	+|(% style="width:94px" %)**LT-33222-L**|(% style="width:172px" %)(((
	125	+(% style="text-align:center" %)
	126	+[[image:lt33222-l.jpg||height="139" width="120"]]
	127	+)))|(% style="width:256px" %)(((
	128	+* 3 x Digital Input (Bi-direction)
	129	+* 3 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	+
120	120	== 2.1 Connecting the antenna ==
121	121
122	122	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.
123	123
124	124	{{warning}}
125		-Warning! Do not power on the device without connecting the antenna.
	143	+**Warning! Do not power on the device without connecting the antenna.**
126	126	{{/warning}}
127	127
128	128	== 2.2 Terminals ==
129	129
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.
	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.
131	131
132		-Upper screw terminal block (from left to right):
	150	+**Upper screw terminal block (from left to right):**
133	133
134	134	(% style="width:634px" %)
135		-|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function
	153	+|=(% style="width: 295px;" %)Screw Terminal|=(% style="width: 338px;" %)Function
136	136	|(% style="width:295px" %)GND|(% style="width:338px" %)Ground
137	137	|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage
138	138	|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2
...	...	@@ -140,10 +140,10 @@
140	140	|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2
141	141	|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1
142	142
143		-Lower screw terminal block (from left to right):
	161	+**Lower screw terminal block (from left to right):**
144	144
145	145	(% style="width:633px" %)
146		-|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function
	164	+|=(% style="width: 296px;" %)Screw Terminal|=(% style="width: 334px;" %)Function
147	147	|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1
148	148	|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1
149	149	|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2
...	...	@@ -155,14 +155,12 @@
155	155	|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
156	156	|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
157	157
158		-== 2.3 Powering the device ==
	176	+== 2.3 Connecting LT-22222-L to a Power Source ==
159	159
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.
	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.
161	161
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		-
164	164	{{warning}}
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.
	181	+**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.**
166	166	{{/warning}}
167	167
168	168
...	...	@@ -169,36 +169,51 @@
169	169	[[image:1653297104069-180.png]]
170	170
171	171
172		-= 3. Registering with a LoRaWAN Network Server =
	188	+= 3. Registering LT-22222-L with a LoRaWAN Network Server =
173	173
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.
	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.
175	175
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.
177	177
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		-
184	184	=== 3.2.1 Prerequisites ===
185	185
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.
	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.
187	187
188	188	[[image:image-20230425173427-2.png||height="246" width="530"]]
189	189
	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	+
190	190	The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
191	191
192		-=== 3.2.2 The Things Stack Sandbox (TTSS) ===
	205	+=== 3.2.2 The Things Stack ===
193	193
	207	+This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
	208	+
	209	+{{info}}
194	194	The Things Stack Sandbox was formally called The Things Stack Community Edition.
	211	+{{/info}}
195	195
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.
	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.
199	199	* On the End devices page, click on **+ Register end device**. Two registration options are available:
200	200
201		-==== 3.2.2.1 Using the LoRaWAN Device Repository ====
	232	+==== 3.2.2.2 Using the LoRaWAN Device Repository ====
202	202
203	203	* On the **Register end device** page:
204	204	** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
...	...	@@ -210,7 +210,7 @@
210	210	*** **Profile (Region)**: Select the region that matches your device.
211	211	** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
212	212
213		-[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
	244	+[[image:lt-22222-l-dev-repo-reg-p1.png]]
214	214
215	215
216	216	* Register end device page continued...
...	...	@@ -220,11 +220,10 @@
220	220	** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
221	221	** Under **After registration**, select the **View registered end device** option.
222	222
223		-[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
	254	+[[image:lt-22222-l-dev-repo-reg-p2.png]]
224	224
225		-==== ====
226	226
227		-==== 3.2.2.2 Adding device manually ====
	257	+==== 3.2.2.3 Adding device manually ====
228	228
229	229	* On the **Register end device** page:
230	230	** Select the option **Enter end device specifies manually** under **Input method**.
...	...	@@ -235,11 +235,11 @@
235	235	** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
236	236	** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
237	237
238		-[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
	268	+[[image:lt-22222-l-manually-p1.png]]
239	239
240	240
241	241	* Register end device page continued...
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'
	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**//'
243	243	** In the **DevEUI** field, enter the **DevEUI**.
244	244	** In the **AppKey** field, enter the **AppKey**.
245	245	** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
...	...	@@ -246,41 +246,50 @@
246	246	** Under **After registration**, select the **View registered end device** option.
247	247	** Click the **Register end device** button.
248	248
249		-[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
	279	+[[image:lt-22222-l-manually-p2.png]]
250	250
251	251
252	252	You will be navigated to the **Device overview** page.
253	253
254	254
255		-[[image:lt-22222-device-overview.png||height="625" width="1000"]]
	285	+[[image:lt-22222-device-overview.png]]
256	256
257	257
258		-==== 3.2.2.3 Joining ====
	288	+==== 3.2.2.4 Joining ====
259	259
260		-On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
	290	+On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
261	261
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**).
	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.
263	263
264	264
265		-[[image:lt-22222-join-network.png||height="625" width="1000"]]
	295	+[[image:lt-22222-l-joining.png]]
266	266
267	267
268		-By default, you will receive an uplink data message from the device every 10 minutes.
269	269
	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	+
270	270	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.
271	271
272	272	[[image:lt-22222-ul-payload-decoded.png]]
273	273
274	274
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.
	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.
276	276
277	277	{{info}}
278	278	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.
279	279	{{/info}}
280	280
281		-[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
	315	+[[image:lt-22222-ul-payload-fmt.png]]
282	282
283	283
	318	+==== 3.2.2.6 Downlinks ====
	319	+
	320	+When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
	321	+
	322	+
284	284	== 3.3 Working Modes and Uplink Payload formats ==
285	285
286	286
...	...	@@ -556,19 +556,19 @@
556	556	)))
557	557
558	558	(((
559		-Other AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
	598	+AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
560	560	)))
561	561
562	562	(((
563	563	**In addition to that, below are the commands for AVI1 Counting:**
564	564
565		-(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI Count to 60)**
	604	+(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)**
566	566
567		-(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
	606	+(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), the counter increases by 1)**
568	568
569		-(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
	608	+(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If the AVI1 voltage is lower than VOLMAX (20000mV =20V), counter increases by 1)**
570	570
571		-(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
	610	+(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), counter increases by 1)**
572	572	)))
573	573
574	574
...	...	@@ -687,9 +687,9 @@
687	687
688	688	(% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
689	689
690		-Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
	729	+**Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
691	691
692		-Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
	731	+**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
693	693
694	694	AA: Type Code for this downlink Command:
695	695
...	...	@@ -756,7 +756,7 @@
756	756
757	757	**Example:**
758	758
759		-10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
	798	+10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW.
760	760
761	761
762	762	(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
...	...	@@ -785,7 +785,7 @@
785	785
786	786	**Example:**
787	787
788		-10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
	827	+10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low.
789	789
790	790
791	791	(% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
...	...	@@ -794,22 +794,22 @@
794	794	|(% 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**
795	795	|(% 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
796	796
797		-* Each bits shows which status has been triggered on this uplink.
	836	+* Each bit shows which status has been triggered on this uplink.
798	798
799	799	**Example:**
800	800
801		-00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
	840	+00000111: This means both DI1 and DI2 triggers are enabled, and this packet is trigger by DI1.
802	802
803		-00000101: Means both DI1 and DI2 trigger are enabled.
	842	+00000101: This means both DI1 and DI2 triggers are enabled.
804	804
805	805
806		-(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable.
	845	+(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled.
807	807
808		-Downlink command to poll MOD6 status:
	847	+Downlink command to poll/request MOD6 status:
809	809
810	810	**AB 06**
811	811
812		-When device got this command, it will send the MOD6 payload.
	851	+When device receives this command, it will send the MOD6 payload.
813	813
814	814
815	815	=== 3.3.7 Payload Decoder ===
...	...	@@ -848,7 +848,7 @@
848	848	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.
849	849
850	850
851		-==== 3.4.2.1 Set Transmit Interval ====
	890	+==== 3.4.2.1 Set Transmit/Uplink Interval ====
852	852
853	853	Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
854	854
...	...	@@ -857,11 +857,11 @@
857	857	(% border="2" style="width:500px" %)
858	858	|**Command**|AT+TDC=<time>
859	859	|**Response**|
860		-|**Parameters**|**time** : uplink interval is in milliseconds
	899	+|**Parameters**|**time** : uplink interval is in **milliseconds**
861	861	|**Example**|(((
862	862	AT+TDC=30000
863	863
864		-Sets the uplink interval to 30,000 milliseconds (30 seconds)
	903	+Sets the uplink interval to **30 seconds** (30000 milliseconds)
865	865	)))
866	866
867	867	(% style="color:#037691" %)**Downlink payload**
...	...	@@ -873,16 +873,18 @@
873	873	|**Parameters**|(((
874	874	**prefix** : 0x01
875	875
876		-**time** : uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
	915	+**time** : uplink interval is in **seconds**, represented by **3  bytes** in **hexadecimal**.
877	877	)))
878	878	|**Example**|(((
879		-01 **00 75 30**
	918	+01 **00 00 1E**
880	880
881		-Sets the uplink interval to 30,000 milliseconds (30 seconds)
	920	+Sets the uplink interval to **30 seconds**
882	882
883		-Conversion: 30000 (dec) = 00 75 30 (hex)
	922	+Conversion: 30 (dec) = 00 00 1E (hex)
884	884
885		-See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]]
	924	+See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30]]
	925	+
	926	+[[image:Screenshot 2024-11-23 at 18.27.11.png]]
886	886	)))
887	887
888	888	==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
...	...	@@ -931,13 +931,13 @@
931	931	Sets the device to working mode 2 (Double DI Counting + DO + RO)
932	932	)))
933	933
934		-==== 3.4.2.3 Poll an uplink ====
	975	+==== 3.4.2.3 Request an uplink from the device ====
935	935
936		-Requests an uplink from LT-22222-L.
	977	+Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
937	937
938	938	(% style="color:#037691" %)**AT command**
939	939
940		-There is no AT Command to request an uplink from LT-22222-L
	981	+There is no AT Command available for this feature.
941	941
942	942	(% style="color:#037691" %)**Downlink payload**
943	943
...	...	@@ -945,7 +945,7 @@
945	945	|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF
946	946	|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08
947	947	|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
948		-08 FF
	989	+08 **FF**
949	949
950	950	Requests an uplink from LT-22222-L.
951	951	)))
...	...	@@ -979,7 +979,7 @@
979	979	|(% style="width:97px" %)**Parameters**|(% style="width:401px" %)(((
980	980	**prefix** : 0x0A 06 (two bytes in hexadecimal)
981	981
982		-**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
	1023	+**enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
983	983	)))
984	984	|(% style="width:97px" %)**Example**|(% style="width:401px" %)(((
985	985	0A 06 **01**
...	...	@@ -987,13 +987,13 @@
987	987	Enable trigger mode for the current working mode
988	988	)))
989	989
990		-==== 3.4.2.5 Poll trigger settings ====
	1031	+==== 3.4.2.5 Request trigger settings ====
991	991
992		-Polls the trigger settings.
	1033	+Requests the trigger settings.
993	993
994	994	(% style="color:#037691" %)**AT Command:**
995	995
996		-There is no AT Command for this feature.
	1037	+There is no AT Command available for this feature.
997	997
998	998	(% style="color:#037691" %)**Downlink Payload**
999	999
...	...	@@ -1133,9 +1133,6 @@
1133	1133	)))
1134	1134	|(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
1135	1135
1136		-(% class="wikigeneratedid" %)
1137		-==== ====
1138		-
1139	1139	==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1140	1140
1141	1141	Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
...	...	@@ -1210,7 +1210,6 @@
1210	1210	)))
1211	1211	|(% style="width:104px" %)**Note**|(% style="width:387px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1212	1212
1213		-
1214	1214	(% style="color:#037691" %)**Downlink Payload**
1215	1215
1216	1216	(% border="2" style="width:500px" %)
...	...	@@ -1233,7 +1233,6 @@
1233	1233	)))
1234	1234	|(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1235	1235
1236		-
1237	1237	==== 3.4.2.11 Trigger – Set minimum interval ====
1238	1238
1239	1239	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.
...	...	@@ -1269,7 +1269,6 @@
1269	1269	)))
1270	1270	|(% style="width:112px" %)Note|(% style="width:386px" %)(% style="color:red" %)**The time must be greater than 5 minutes.**
1271	1271
1272		-
1273	1273	==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
1274	1274
1275	1275	Controls the digital outputs DO1, DO2, and DO3
...	...	@@ -1320,33 +1320,28 @@
1320	1320	)))
1321	1321	)))
1322	1322
1323		-(% class="wikigeneratedid" %)
1324		-==== ====
1325		-
1326	1326	==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1327	1327
1328	1328
1329	1329	* (% style="color:#037691" %)**AT Command**
1330	1330
1331		-There is no AT Command to control Digital Output
	1363	+There is no AT command to control the digital output.
1332	1332
1333	1333
1334	1334	* (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
1335	1335
1336		-(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Set DO1/DO2/DO3 output with time control
	1368	+(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control
1337	1337
1338		-
1339	1339	This is to control the digital output time of DO pin. Include four bytes:
1340	1340
1341		-(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
	1372	+(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)
1342	1342
1343		-(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
	1374	+(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode
1344	1344
1345		-01: DO pins will change back to original state after timeout.
	1376	+**01:** DO pins revert to their original state after the timeout.
	1377	+**00:** DO pins switch to an inverted state after the timeout.
1346	1346
1347		-00: DO pins will change to an inverter state after timeout
1348	1348
1349		-
1350	1350	(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1351	1351
1352	1352	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
...	...	@@ -1355,7 +1355,7 @@
1355	1355	|0x00|DO1 set to high
1356	1356	|0x11|DO1 NO Action
1357	1357
1358		-(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
	1388	+(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:
1359	1359
1360	1360	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1361	1361	|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
...	...	@@ -1363,7 +1363,7 @@
1363	1363	|0x00|DO2 set to high
1364	1364	|0x11|DO2 NO Action
1365	1365
1366		-(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
	1396	+(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:
1367	1367
1368	1368	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1369	1369	|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
...	...	@@ -1371,7 +1371,7 @@
1371	1371	|0x00|DO3 set to high
1372	1372	|0x11|DO3 NO Action
1373	1373
1374		-(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
	1404	+(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)
1375	1375
1376	1376
1377	1377	(% style="color:red" %)**Note: **
...	...	@@ -1380,7 +1380,7 @@
1380	1380
1381	1381	Before firmware v1.6.0, the latch time only supported 2 bytes.
1382	1382
1383		-(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
	1413	+(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1384	1384
1385	1385
1386	1386	**Example payload:**
...	...	@@ -1407,16 +1407,16 @@
1407	1407
1408	1408	* (% style="color:#037691" %)**AT Command:**
1409	1409
1410		-There is no AT Command to control Relay Output
	1440	+There is no AT Command to control the Relay Output
1411	1411
1412	1412
1413	1413	* (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
1414	1414
1415		-(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
	1445	+(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Sets RO1/RO2 output
1416	1416
1417	1417
1418	1418	(((
1419		-If payload is 0x030100, it means setting RO1 to close and RO2 to open.
	1449	+If the payload is 0x030100, it means setting RO1 to close and RO2 to open.
1420	1420	)))
1421	1421
1422	1422	(((
...	...	@@ -1434,7 +1434,7 @@
1434	1434	|03  00  01|Open|Close
1435	1435	)))
1436	1436
1437		-(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
	1467	+(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1438	1438
1439	1439
1440	1440	==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
...	...	@@ -1443,19 +1443,19 @@
1443	1443
1444	1444	* (% style="color:#037691" %)**AT Command:**
1445	1445
1446		-There is no AT Command to control Relay Output
	1476	+There is no AT Command to control the Relay Output
1447	1447
1448	1448
1449	1449	* (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1450	1450
1451		-(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
	1481	+(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
1452	1452
1453	1453
1454		-This is to control the relay output time. It includes four bytes:
	1484	+This controls the relay output time and includes 4 bytes:
1455	1455
1456		-(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
	1486	+(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
1457	1457
1458		-(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
	1488	+(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
1459	1459
1460	1460	01: Relays will change back to their original state after timeout.
1461	1461
...	...	@@ -1462,12 +1462,12 @@
1462	1462	00: Relays will change to the inverter state after timeout.
1463	1463
1464	1464
1465		-(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
	1495	+(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
1466	1466
1467	1467	[[image:image-20221008095908-1.png||height="364" width="564"]]
1468	1468
1469	1469
1470		-(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
	1500	+(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms
1471	1471
1472	1472
1473	1473	(% style="color:red" %)**Note:**
...	...	@@ -1477,7 +1477,7 @@
1477	1477	Before firmware v1.6.0, the latch time only supported 2 bytes.
1478	1478
1479	1479
1480		-(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
	1510	+(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1481	1481
1482	1482
1483	1483	**Example payload:**
...	...	@@ -1505,131 +1505,356 @@
1505	1505
1506	1506	When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1507	1507
1508		-* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX   ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
	1538	+(% style="color:#037691" %)**AT Command**
1509	1509
1510		-* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):**
	1540	+(% border="2" style="width:500px" %)
	1541	+|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage>,<logic>
	1542	+|(% style="width:137px" %)**Response**|(% style="width:361px" %)
	1543	+|(% style="width:137px" %)**Parameters**|(% style="width:361px" %)(((
	1544	+**voltage** : voltage threshold in mV
1511	1511
1512		-(% style="color:blue" %)**0xA5 aa bb cc   ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc
	1546	+**logic**:
1513	1513
	1548	+**0** : lower than
1514	1514
	1550	+**1**: higher than
1515	1515
	1552	+if you leave logic parameter blank, it is considered 0
	1553	+)))
	1554	+|(% style="width:137px" %)**Examples**|(% style="width:361px" %)(((
	1555	+AT+VOLMAX=20000
	1556	+
	1557	+If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
	1558	+
	1559	+AT+VOLMAX=20000,0
	1560	+
	1561	+If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1
	1562	+
	1563	+AT+VOLMAX=20000,1
	1564	+
	1565	+If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
	1566	+)))
	1567	+
	1568	+(% style="color:#037691" %)**Downlink Payload**
	1569	+
	1570	+(% border="2" style="width:500px" %)
	1571	+|(% style="width:140px" %)**Payload**|(% style="width:358px" %)<prefix><voltage><logic>
	1572	+|(% style="width:140px" %)**Parameters**|(% style="width:358px" %)(((
	1573	+**prefix** : A5 (hex)
	1574	+
	1575	+**voltage** : voltage threshold in mV (2 bytes in hex)
	1576	+
	1577	+**logic**: (1 byte in hexadecimal)
	1578	+
	1579	+**0** : lower than
	1580	+
	1581	+**1**: higher than
	1582	+
	1583	+if you leave logic parameter blank, it is considered 1 (higher than)
	1584	+)))
	1585	+|(% style="width:140px" %)**Example**|(% style="width:358px" %)(((
	1586	+A5 **4E 20**
	1587	+
	1588	+If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
	1589	+
	1590	+A5 **4E 20 00**
	1591	+
	1592	+If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1
	1593	+
	1594	+A5 **4E 20 01**
	1595	+
	1596	+If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
	1597	+)))
	1598	+
1516	1516	==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ====
1517	1517
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.
	1601	+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.
1519	1519
1520		-* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) **
	1603	+(% style="color:#037691" %)**AT Command**
1521	1521
1522		-(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count
	1605	+(% border="2" style="width:500px" %)
	1606	+|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter>,<number>
	1607	+|(% style="width:134px" %)**Response**|(% style="width:364px" %)
	1608	+|(% style="width:134px" %)**Parameters**|(% style="width:364px" %)(((
	1609	+**counting_parameter** :
1523	1523
1524		-(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set
	1611	+1: COUNT1
1525	1525
	1613	+2: COUNT2
1526	1526
1527		-* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):**
	1615	+3: AVI1 Count
1528	1528
1529		-(% style="color:blue" %)**0x A8 aa bb cc dd ee     ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
	1617	+**number** : Start number
	1618	+)))
	1619	+|(% style="width:134px" %)**Example**|(% style="width:364px" %)(((
	1620	+AT+SETCNT=1,10
1530	1530
	1622	+Sets the COUNT1 to 10.
	1623	+)))
1531	1531
	1625	+(% style="color:#037691" %)**Downlink Payload**
1532	1532
	1627	+(% border="2" style="width:500px" %)
	1628	+|(% style="width:135px" %)**Payload**|(% style="width:363px" %)<prefix><counting_parameter><number>
	1629	+|(% style="width:135px" %)**Parameters**|(% style="width:363px" %)(((
	1630	+prefix : A8 (hex)
	1631	+
	1632	+**counting_parameter** : (1 byte in hexadecimal)
	1633	+
	1634	+1: COUNT1
	1635	+
	1636	+2: COUNT2
	1637	+
	1638	+3: AVI1 Count
	1639	+
	1640	+**number** : Start number, 4 bytes in hexadecimal
	1641	+)))
	1642	+|(% style="width:135px" %)**Example**|(% style="width:363px" %)(((
	1643	+A8 **01 00 00 00 0A**
	1644	+
	1645	+Sets the COUNT1 to 10.
	1646	+)))
	1647	+
1533	1533	==== 3.4.2.18 Counting ~-~- Clear Counting ====
1534	1534
1535		-This feature clears the counting in counting mode.
	1650	+This command clears the counting in counting mode.
1536	1536
1537		-* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
	1652	+(% style="color:#037691" %)**AT Command**
1538	1538
1539		-* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
	1654	+(% border="2" style="width:500px" %)
	1655	+|(% style="width:142px" %)**Command**|(% style="width:356px" %)AT+CLRCOUNT
	1656	+|(% style="width:142px" %)**Response**|(% style="width:356px" %)-
1540	1540
1541		-(% style="color:blue" %)**0x A6 01    ** (%%)~/~/ clear all counting
	1658	+(% style="color:#037691" %)**Downlink Payload**
1542	1542
	1660	+(% border="2" style="width:500px" %)
	1661	+|(% style="width:141px" %)**Payload**|(% style="width:357px" %)<prefix><clear?>
	1662	+|(% style="width:141px" %)**Parameters**|(% style="width:357px" %)(((
	1663	+prefix : A6 (hex)
1543	1543
	1665	+clear? : 01 (hex)
	1666	+)))
	1667	+|(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
1544	1544
1545		-==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
	1669	+==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
1546	1546
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.
	1671	+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.
1548	1548
1549		-* (% style="color:#037691" %)**AT Command:**
	1673	+(% style="color:#037691" %)**AT Command**
1550	1550
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)
	1675	+(% border="2" style="width:500px" %)
	1676	+|(% style="width:124px" %)**Command**|(% style="width:374px" %)AT+COUTIME=<time>
	1677	+|(% style="width:124px" %)**Response**|(% style="width:374px" %)
	1678	+|(% style="width:124px" %)**Parameters**|(% style="width:374px" %)time : seconds (0 to 16777215)
	1679	+|(% style="width:124px" %)**Example**|(% style="width:374px" %)(((
	1680	+AT+COUTIME=60
1552	1552
	1682	+Sets the device to save its counting results to the memory every 60 seconds.
	1683	+)))
1553	1553
1554		-* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
	1685	+(% style="color:#037691" %)**Downlink Payload**
1555	1555
1556		-(% style="color:blue" %)**0x A7 aa bb cc     ** (%%)~/~/ same as AT+COUTIME =aa bb cc,
	1687	+(% border="2" style="width:500px" %)
	1688	+|(% style="width:123px" %)**Payload**|(% style="width:375px" %)<prefix><time>
	1689	+|(% style="width:123px" %)**Parameters**|(% style="width:375px" %)(((
	1690	+prefix : A7
1557	1557
1558		-(((
1559		-Range: aa bb cc:0 to 16777215,  (unit: seconds)
	1692	+time : seconds, 3 bytes in hexadecimal
1560	1560	)))
	1694	+|(% style="width:123px" %)**Example**|(% style="width:375px" %)(((
	1695	+A7 **00 00 3C**
1561	1561
	1697	+Sets the device to save its counting results to the memory every 60 seconds.
	1698	+)))
1562	1562
	1700	+==== 3.4.2.20 Reset saved RO and DO states ====
1563	1563
1564		-==== 3.4.2.20 Reset save RO DO state ====
	1702	+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.
1565	1565
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.
	1704	+(% style="color:#037691" %)**AT Command**
1567	1567
1568		-* (% style="color:#037691" %)**AT Command:**
	1706	+(% border="2" style="width:500px" %)
	1707	+|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state>
	1708	+|(% style="width:127px" %)**Response**|(% style="width:371px" %)
	1709	+|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
	1710	+**state** :
1569	1569
1570		-(% style="color:blue" %)**AT+RODORESET=1    **(%%)~/~/ RODO will close when the device joining the network. (default)
	1712	+**0** : RODO will close when the device joins the network. (default)
1571	1571
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.
	1714	+**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.
	1715	+)))
	1716	+|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
	1717	+(% style="color:blue" %)**AT+RODORESET=1 **
1573	1573
	1719	+RODO will close when the device joins the network. (default)
1574	1574
1575		-* (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):**
	1721	+(% style="color:blue" %)**AT+RODORESET=0 **
1576	1576
1577		-(% style="color:blue" %)**0x AD aa      ** (%%)~/~/ same as AT+RODORET =aa
	1723	+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.
	1724	+)))
1578	1578
	1726	+(% style="color:#037691" %)**Downlink Payload**
1579	1579
	1728	+(% border="2" style="width:500px" %)
	1729	+|(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state>
	1730	+|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
	1731	+**prefix** : AD
1580	1580
	1733	+**state** :
	1734	+
	1735	+**0** : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal.
	1736	+
	1737	+**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
	1738	+)))
	1739	+|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
	1740	+AD **01**
	1741	+
	1742	+RODO will close when the device joins the network. (default)
	1743	+
	1744	+AD **00**
	1745	+
	1746	+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.
	1747	+)))
	1748	+
1581	1581	==== 3.4.2.21 Encrypted payload ====
1582	1582
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.
	1751	+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.
1584	1584
1585		-* (% style="color:#037691" %)**AT Command:**
	1753	+(% style="color:#037691" %)**AT Command:**
1586	1586
1587		-(% style="color:blue" %)**AT+DECRYPT=1  ** (%%)~/~/ The payload is uploaded without encryption
	1755	+(% border="2" style="width:500px" %)
	1756	+|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state>
	1757	+|(% style="width:127px" %)**Response**|(% style="width:371px" %)
	1758	+|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
	1759	+**state** :
1588	1588
1589		-(% style="color:blue" %)**AT+DECRYPT=0    **(%%)~/~/  Encrypt when uploading payload (default)
	1761	+**1** : The payload is uploaded without encryption
1590	1590
	1763	+**0** : The payload is encrypted when uploaded (default)
	1764	+)))
	1765	+|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
	1766	+AT+DECRYPT=1
1591	1591
	1768	+The payload is uploaded without encryption
1592	1592
	1770	+AT+DECRYPT=0
	1771	+
	1772	+The payload is encrypted when uploaded (default)
	1773	+)))
	1774	+
	1775	+There is no downlink payload for this configuration.
	1776	+
	1777	+
1593	1593	==== 3.4.2.22 Get sensor value ====
1594	1594
	1780	+This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1595	1595
1596		-* (% style="color:#037691" %)**AT Command:**
	1782	+(% style="color:#037691" %)**AT Command**
1597	1597
1598		-(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port retrieves the reading of the current sensor.
	1784	+(% border="2" style="width:500px" %)
	1785	+|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
	1786	+|(% style="width:127px" %)**Response**|(% style="width:371px" %)
	1787	+|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
	1788	+**state** :
1599	1599
1600		-(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.
	1790	+**0 **: Retrieves the current sensor reading via the serial port.
1601	1601
	1792	+**1 **: Retrieves and uploads the current sensor reading via the serial port.
	1793	+)))
	1794	+|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
	1795	+AT+GETSENSORVALUE=0
1602	1602
	1797	+Retrieves the current sensor reading via the serial port.
1603	1603
1604		-==== 3.4.2.23 Resets the downlink packet count ====
	1799	+AT+GETSENSORVALUE=1
1605	1605
	1801	+Retrieves and uplinks the current sensor reading via the serial port.
	1802	+)))
1606	1606
1607		-* (% style="color:#037691" %)**AT Command:**
	1804	+There is no downlink payload for this configuration.
1608	1608
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)
1610	1610
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.
	1807	+==== 3.4.2.23 Resetting the downlink packet count ====
1612	1612
	1809	+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.
1613	1613
	1811	+(% style="color:#037691" %)**AT Command**
1614	1614
	1813	+(% border="2" style="width:500px" %)
	1814	+|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
	1815	+|(% style="width:130px" %)**Response**|(% style="width:368px" %)(((
	1816	+
	1817	+)))
	1818	+|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)(((
	1819	+**state **:
	1820	+
	1821	+**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).
	1822	+
	1823	+
	1824	+**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.
	1825	+)))
	1826	+|(% style="width:130px" %)**Example**|(% style="width:368px" %)(((
	1827	+AT+DISFCNTCHECK=0
	1828	+
	1829	+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).
	1830	+
	1831	+AT+DISFCNTCHECK=1
	1832	+
	1833	+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.
	1834	+)))
	1835	+
	1836	+There is no downlink payload for this configuration.
	1837	+
	1838	+
1615	1615	==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ====
1616	1616
1617	1617
1618		-* (% style="color:#037691" %)**AT Command:**
	1842	+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.
1619	1619
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)
	1844	+(% style="color:#037691" %)**AT Command**
1621	1621
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.
	1846	+(% border="2" style="width:500px" %)
	1847	+|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state>
	1848	+|(% style="width:127px" %)**Response**|(% style="width:371px" %)
	1849	+|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
	1850	+**state** :
1623	1623
	1852	+**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)
1624	1624
1625		-* (% style="color:#037691" %)**Downlink Payload **(%%)**:**
	1854	+**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.
	1855	+)))
	1856	+|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
	1857	+AT+DISMACANS=0
1626	1626
1627		-(% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set  the DISMACANS=1
	1859	+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)
1628	1628
	1861	+AT+DISMACANS=1
1629	1629
	1863	+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.
	1864	+)))
1630	1630
	1866	+(% style="color:#037691" %)**Downlink Payload**
	1867	+
	1868	+(% border="2" style="width:500px" %)
	1869	+|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state>
	1870	+|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)(((
	1871	+**prefix** : 21
	1872	+
	1873	+**state** : (2 bytes in hexadecimal)
	1874	+
	1875	+**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)
	1876	+
	1877	+**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.
	1878	+)))
	1879	+|(% style="width:126px" %)**Example**|(% style="width:372px" %)(((
	1880	+21 **00 01**
	1881	+
	1882	+Set DISMACANS=1
	1883	+)))
	1884	+
1631	1631	==== 3.4.2.25 Copy downlink to uplink ====
1632	1632
	1887	+This command enables the device to immediately uplink the content of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100.
1633	1633
1634	1634	* (% style="color:#037691" %)**AT Command**(%%)**:**
1635	1635
...	...	@@ -1642,8 +1642,22 @@
1642	1642
1643	1643	For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1644	1644
	1900	+(% border="2" style="width:500px" %)
	1901	+|(% style="width:122px" %)**Command**|(% style="width:376px" %)(((
	1902	+AT+RPL=5
1645	1645
	1904	+After receiving a downlink packet from the server, the node immediately uplinks the content of the packet back to the server using port number 100.
	1905	+)))
	1906	+|(% style="width:122px" %)**Example**|(% style="width:376px" %)(((
	1907	+Downlink:
1646	1646
	1909	+01 00 02 58
	1910	+
	1911	+Uplink:
	1912	+
	1913	+01 01 00 02 58
	1914	+)))
	1915	+
1647	1647	[[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"]]
1648	1648
1649	1649	For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
...	...	@@ -1650,14 +1650,16 @@
1650	1650
1651	1651
1652	1652
1653		-==== 3.4.2.26 Query version number and frequency band 、TDC ====
	1922	+==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
1654	1654
	1924	+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.
1655	1655
1656	1656	* (((
1657	1657	(% style="color:#037691" %)**Downlink Payload**(%%)**:**
1658	1658
1659		-(% style="color:blue" %)**26 01  ** (%%) ~/~/  Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
	1929	+(% 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.
1660	1660
	1931	+
1661	1661
1662	1662	)))
1663	1663
...	...	@@ -1683,15 +1683,17 @@
1683	1683	The username and  password (API key) you created here are required in the next section.
1684	1684	{{/info}}
1685	1685
1686		-[[image:tts-mqtt-integration.png||height="625" width="1000"]]
	1957	+[[image:tts-mqtt-integration.png]]
1687	1687
1688	1688	=== 3.5.2 Configuring ThingsEye.io ===
1689	1689
	1961	+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.
	1962	+
1690	1690	* Login to your [[ThingsEye.io >>https://thingseye.io]]account.
1691	1691	* Under the **Integrations center**, click **Integrations**.
1692	1692	* Click the **Add integration** button (the button with the **+** symbol).
1693	1693
1694		-[[image:thingseye-io-step-1.png||height="625" width="1000"]]
	1967	+[[image:thingseye-io-step-1.png]]
1695	1695
1696	1696
1697	1697	On the **Add integration** window, configure the following:
...	...	@@ -1706,7 +1706,7 @@
1706	1706	** Allow create devices or assets
1707	1707	* Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
1708	1708
1709		-[[image:thingseye-io-step-2.png||height="625" width="1000"]]
	1982	+[[image:thingseye-io-step-2.png]]
1710	1710
1711	1711
1712	1712	**Uplink data converter:**
...	...	@@ -1717,7 +1717,7 @@
1717	1717	* 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]].
1718	1718	* Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
1719	1719
1720		-[[image:thingseye-io-step-3.png||height="625" width="1000"]]
	1993	+[[image:thingseye-io-step-3.png]]
1721	1721
1722	1722
1723	1723	**Downlink data converter (this is an optional step):**
...	...	@@ -1728,7 +1728,7 @@
1728	1728	* 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]].
1729	1729	* Click the **Next** button. You will be navigated to the **Connection** tab.
1730	1730
1731		-[[image:thingseye-io-step-4.png||height="625" width="1000"]]
	2004	+[[image:thingseye-io-step-4.png]]
1732	1732
1733	1733
1734	1734	**Connection:**
...	...	@@ -1735,7 +1735,7 @@
1735	1735
1736	1736	* Choose **Region** from the **Host type**.
1737	1737	* 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/...).
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).
	2011	+* 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**).
1739	1739	* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
1740	1740
1741	1741	[[image:message-1.png]]
...	...	@@ -1743,13 +1743,13 @@
1743	1743
1744	1744	* Click the **Add** button.
1745	1745
1746		-[[image:thingseye-io-step-5.png||height="625" width="1000"]]
	2019	+[[image:thingseye-io-step-5.png]]
1747	1747
1748	1748
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.
	2022	+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.
1750	1750
1751	1751
1752		-[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
	2025	+[[image:thingseye.io_integrationsCenter_integrations.png]]
1753	1753
1754	1754
1755	1755	==== 3.5.2.1 Viewing integration details ====
...	...	@@ -1756,13 +1756,13 @@
1756	1756
1757	1757	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.
1758	1758
1759		-[[image:integration-details.png||height="686" width="1000"]]
	2032	+[[image:integration-details.png]]
1760	1760
1761	1761
1762	1762	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.
1763	1763
1764	1764	{{info}}
1765		-See also ThingsEye documentation.
	2038	+See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
1766	1766	{{/info}}
1767	1767
1768	1768	==== **3.5.2.2 Viewing events** ====
...	...	@@ -1772,12 +1772,12 @@
1772	1772	* Select **Debug **from the **Event type** dropdown.
1773	1773	* Select the** time frame** from the **time window**.
1774	1774
1775		-[[image:thingseye-events.png||height="686" width="1000"]]
	2048	+[[image:thingseye-events.png]]
1776	1776
1777	1777
1778		-* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
	2051	+* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
1779	1779
1780		-[[image:thingseye-json.png||width="1000"]]
	2053	+[[image:thingseye-json.png]]
1781	1781
1782	1782
1783	1783	==== **3.5.2.3 Deleting an integration** ====
...	...	@@ -1785,12 +1785,17 @@
1785	1785	If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
1786	1786
1787	1787
	2061	+==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
	2062	+
	2063	+This will be added soon.
	2064	+
	2065	+
1788	1788	== 3.6 Interface Details ==
1789	1789
1790	1790	=== 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
1791	1791
1792	1792
1793		-Supports NPN-type sensors.
	2071	+Supports** NPN-type **sensors.
1794	1794
1795	1795	[[image:1653356991268-289.png]]
1796	1796
...	...	@@ -1912,15 +1912,15 @@
1912	1912	)))
1913	1913
1914	1914
1915		-(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
	2193	+(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor
1916	1916
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.
	2195	+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.
1918	1918
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.
	2197	+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.
1920	1920
1921	1921	[[image:image-20230616235145-1.png]]
1922	1922
1923		-(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
	2201	+(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector
1924	1924
1925	1925	[[image:image-20240219115718-1.png]]
1926	1926
...	...	@@ -1996,7 +1996,7 @@
1996	1996	[[image:image-20220524100215-10.png||height="382" width="723"]]
1997	1997
1998	1998
1999		-== 3.7 LEDs Indicators ==
	2277	+== 3.7 LED Indicators ==
2000	2000
2001	2001	The table below lists the behavior of LED indicators for each port function.
2002	2002
...	...	@@ -2035,13 +2035,14 @@
2035	2035	== 4.1 Connecting the LT-22222-L to a PC ==
2036	2036
2037	2037	(((
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.
	2316	+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.
2039	2039
2040		-[[image:usb-ttl-programming.png]]
	2318	+[[image:usb-ttl-audio-jack-connection.jpg]]
	2319	+
	2320	+
2041	2041	)))
2042	2042
2043	2043
2044		-
2045	2045	(((
2046	2046	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:
2047	2047	)))
...	...	@@ -2071,39 +2071,39 @@
2071	2071	* **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
2072	2072	* **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
2073	2073	* **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
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
	2353	+* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
	2354	+* **##AT+DR##**:  Get or set the Data Rate. (0-7 corresponding to DR_X)
	2355	+* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
	2356	+* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)
	2357	+* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency
	2358	+* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
	2359	+* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
	2360	+* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
	2361	+* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
	2362	+* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
	2363	+* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
	2364	+* ##**AT+NWKID**##: Get or set the Network ID
	2365	+* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)
	2366	+* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)
	2367	+* ##**AT+CLASS**##: Get or set the Device Class
	2368	+* ##**AT+JOIN**##: Join network
	2369	+* ##**AT+NJS**##: Get OTAA Join Status
	2370	+* ##**AT+SENDB**##: Send hexadecimal data along with the application port
	2371	+* ##**AT+SEND**##: Send text data along with the application port
	2372	+* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)
	2373	+* ##**AT+RECV**##: Print last received data in raw format
	2374	+* ##**AT+VER**##: Get current image version and Frequency Band
	2375	+* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)
	2376	+* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)
	2377	+* ##**AT+SNR**##: Get the SNR of the last received packet
	2378	+* ##**AT+RSSI**##: Get the RSSI of the last received packet
	2379	+* ##**AT+TDC**##: Get or set the application data transmission interval in ms
	2380	+* ##**AT+PORT**##: Get or set the application port
	2381	+* ##**AT+DISAT**##: Disable AT commands
	2382	+* ##**AT+PWORD**##: Set password, max 9 digits
	2383	+* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode
	2384	+* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470
	2385	+* ##**AT+CFG**##: Print all settings
2107	2107	)))
2108	2108
2109	2109
...	...	@@ -2268,7 +2268,7 @@
2268	2268	You will need the following things before proceeding:
2269	2269
2270	2270	* 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2271		-* USB to TTL adapter
	2550	+* USB to TTL adapter/converter
2272	2272	* 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)
2273	2273	* 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.
2274	2274
...	...	@@ -2278,7 +2278,7 @@
2278	2278
2279	2279	Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2280	2280
2281		-[[image:usb-ttl-programming.png]]
	2560	+[[image:usb-ttl-audio-jack-connection.jpg]]
2282	2282
2283	2283
2284	2284

Screenshot 2024-11-23 at 18.27.11.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+143.4 KB

Content

dragino-lorawan-nw-lt-22222-n.jpg

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+267.3 KB

Content

dragino-ttn-te.jpg

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+273.8 KB

Content

lorawan-nw.jpg

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+250.6 KB

Content

lt-22222-l-joining.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+301.9 KB

Content

lt33222-l.jpg

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+31.3 KB

Content

usb-ttl-audio-jack-connection.jpg

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+394.4 KB

Content