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

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 7 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

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,20 +40,21 @@
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	57	== 1.2 Specifications ==
58	58
59	59	(% style="color:#037691" %)**Hardware System:**
...	...	@@ -116,13 +116,13 @@
116	116
117	117	== 1.5 Hardware Variants ==
118	118
119		-(% style="width:650px" %)
120		-|(% style="width:94px" %)**Model**|(% style="width:172px" %)**Photo**|(% style="width:256px" %)**Description**
121		-|(% style="width:94px" %)**LT-33222-L**|(% style="width:172px" %)(((
122		-[[image:lt33222-l.jpg]]
123		-)))|(% style="width:256px" %)(((
124		-* 3 x Digital Input (Bi-direction)
125		-* 3 x Digital Output
	120	+(% style="width:524px" %)
	121	+|(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description**
	122	+|(% style="width:94px" %)**LT33222-L**|(% style="width:98px" %)(((
	123	+[[image:/xwiki/bin/downloadrev/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LT-22222-L/WebHome/image-20230424115112-1.png?rev=1.1&width=58&height=106||alt="image-20230424115112-1.png" height="106" width="58"]]
	124	+)))|(% style="width:329px" %)(((
	125	+* 2 x Digital Input (Bi-direction)
	126	+* 2 x Digital Output
126	126	* 2 x Relay Output (5A@250VAC / 30VDC)
127	127	* 2 x 0~~20mA Analog Input (res:0.01mA)
128	128	* 2 x 0~~30V Analog Input (res:0.01v)
...	...	@@ -129,24 +129,26 @@
129	129	* 1 x Counting Port
130	130	)))
131	131
132		-= 2. Assembling the device =
133	133
	134	+
	135	+== 2. Assembling the device ==
	136	+
134	134	== 2.1 Connecting the antenna ==
135	135
136	136	Connect the LoRa antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper screw terminal block. Secure the antenna by tightening it clockwise.
137	137
138	138	{{warning}}
139		-**Warning! Do not power on the device without connecting the antenna.**
	142	+Warning! Do not power on the device without connecting the antenna.
140	140	{{/warning}}
141	141
142	142	== 2.2 Terminals ==
143	143
144		-The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals.
	147	+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.
145	145
146		-**Upper screw terminal block (from left to right):**
	149	+Upper screw terminal block (from left to right):
147	147
148	148	(% style="width:634px" %)
149		-|=(% style="width: 295px;" %)Screw Terminal|=(% style="width: 338px;" %)Function
	152	+|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function
150	150	|(% style="width:295px" %)GND|(% style="width:338px" %)Ground
151	151	|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage
152	152	|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2
...	...	@@ -154,10 +154,10 @@
154	154	|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2
155	155	|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1
156	156
157		-**Lower screw terminal block (from left to right):**
	160	+Lower screw terminal block (from left to right):
158	158
159	159	(% style="width:633px" %)
160		-|=(% style="width: 296px;" %)Screw Terminal|=(% style="width: 334px;" %)Function
	163	+|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function
161	161	|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1
162	162	|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1
163	163	|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2
...	...	@@ -169,12 +169,14 @@
169	169	|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
170	170	|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
171	171
172		-== 2.3 Connecting LT-22222-L to a Power Source ==
	175	+== 2.3 Powering the device ==
173	173
174		-The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s **positive wire** to the **VIN** and the **negative wire** to the **GND** screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered.
	177	+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.
175	175
	179	+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.
	180	+
176	176	{{warning}}
177		-**We recommend that you power on the LT-22222-L after configuring its registration information with a LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.**
	182	+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.
178	178	{{/warning}}
179	179
180	180
...	...	@@ -181,51 +181,36 @@
181	181	[[image:1653297104069-180.png]]
182	182
183	183
184		-= 3. Registering LT-22222-L with a LoRaWAN Network Server =
	189	+= 3. Registering with a LoRaWAN Network Server =
185	185
186		-The LT-22222-L supports both OTAA (Over-the-Air Activation) and ABP (Activation By Personalization) methods to activate with a LoRaWAN Network Server. However, OTAA is the most secure method for activating a device with a LoRaWAN Network Server. OTAA regenerates session keys upon initial registration and regenerates new session keys after any subsequent reboots. By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode.
	191	+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.
187	187
	193	+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.
188	188
	195	+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.
	196	+
	197	+The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
	198	+
	199	+[[image:image-20220523172350-1.png||height="266" width="864"]]
	200	+
189	189	=== 3.2.1 Prerequisites ===
190	190
191		-The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey that allows you to register it with a LoRaWAN network. These registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference.
	203	+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.
192	192
193	193	[[image:image-20230425173427-2.png||height="246" width="530"]]
194	194
195		-{{info}}
196		-In case you can't set the root key and other identifiers in the network server and must use them from the server, you can use [[AT Commands>>||anchor="H4.UseATCommand"]] to configure them on the device.
197		-{{/info}}
198		-
199	199	The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
200	200
201		-=== 3.2.2 The Things Stack ===
	209	+=== 3.2.2 The Things Stack Sandbox (TTSS) ===
202	202
203		-This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
204		-
205		-{{info}}
206	206	The Things Stack Sandbox was formally called The Things Stack Community Edition.
207		-{{/info}}
208	208
209		-
210		-The network diagram below illustrates the connection between the LT-22222-L and The Things Stack, as well as how the data can be integrated with the ThingsEye IoT platform.
211		-
212		-
213		-[[image:dragino-lorawan-nw-lt-22222-n.jpg]]
214		-
215		-{{info}}
216		- You can use a LoRaWAN gateway, such as the [[Dragino LPS8N>>https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], to expand or create LoRaWAN coverage in your area.
217		-{{/info}}
218		-
219		-
220		-==== 3.2.2.1 Setting up ====
221		-
222		-* Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet.
223		-* Log in to your The Things Stack Sandbox account.
224		-* Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs).
225		-* Go to your application's page and click on the **End devices** in the left menu.
	213	+* Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
	214	+* Create an application with The Things Stack if you do not have one yet.
	215	+* Go to your application page and click on the **End devices** in the left menu.
226	226	* On the End devices page, click on **+ Register end device**. Two registration options are available:
227	227
228		-==== 3.2.2.2 Using the LoRaWAN Device Repository ====
	218	+==== 3.2.2.1 Using the LoRaWAN Device Repository ====
229	229
230	230	* On the **Register end device** page:
231	231	** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
...	...	@@ -237,7 +237,7 @@
237	237	*** **Profile (Region)**: Select the region that matches your device.
238	238	** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
239	239
240		-[[image:lt-22222-l-dev-repo-reg-p1.png]]
	230	+[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
241	241
242	242
243	243	* Register end device page continued...
...	...	@@ -247,10 +247,11 @@
247	247	** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
248	248	** Under **After registration**, select the **View registered end device** option.
249	249
250		-[[image:lt-22222-l-dev-repo-reg-p2.png]]
	240	+[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
251	251
	242	+==== ====
252	252
253		-==== 3.2.2.3 Adding device manually ====
	244	+==== 3.2.2.2 Adding device manually ====
254	254
255	255	* On the **Register end device** page:
256	256	** Select the option **Enter end device specifies manually** under **Input method**.
...	...	@@ -261,11 +261,11 @@
261	261	** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
262	262	** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
263	263
264		-[[image:lt-22222-l-manually-p1.png]]
	255	+[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
265	265
266	266
267	267	* Register end device page continued...
268		-** 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**//'
	259	+** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'
269	269	** In the **DevEUI** field, enter the **DevEUI**.
270	270	** In the **AppKey** field, enter the **AppKey**.
271	271	** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
...	...	@@ -272,50 +272,41 @@
272	272	** Under **After registration**, select the **View registered end device** option.
273	273	** Click the **Register end device** button.
274	274
275		-[[image:lt-22222-l-manually-p2.png]]
	266	+[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
276	276
277	277
278	278	You will be navigated to the **Device overview** page.
279	279
280	280
281		-[[image:lt-22222-device-overview.png]]
	272	+[[image:lt-22222-device-overview.png||height="625" width="1000"]]
282	282
283	283
284		-==== 3.2.2.4 Joining ====
	275	+==== 3.2.2.3 Joining ====
285	285
286		-On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
	277	+On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
287	287
288		-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.
	279	+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**).
289	289
290	290
291		-[[image:lt-22222-l-joining.png]]
	282	+[[image:lt-22222-join-network.png||height="625" width="1000"]]
292	292
293	293
	285	+By default, you will receive an uplink data message from the device every 10 minutes.
294	294
295		-==== 3.2.2.5 Uplinks ====
296		-
297		-
298		-After successfully joining, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes.
299		-
300	300	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.
301	301
302	302	[[image:lt-22222-ul-payload-decoded.png]]
303	303
304	304
305		-If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > your application > End devices** > **your end device** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
	292	+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.
306	306
307	307	{{info}}
308	308	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.
309	309	{{/info}}
310	310
311		-[[image:lt-22222-ul-payload-fmt.png]]
	298	+[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
312	312
313	313
314		-==== 3.2.2.6 Downlinks ====
315		-
316		-When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
317		-
318		-
319	319	== 3.3 Working Modes and Uplink Payload formats ==
320	320
321	321
...	...	@@ -599,11 +599,11 @@
599	599
600	600	(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)**
601	601
602		-(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), the counter increases by 1)**
	584	+(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
603	603
604		-(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If the AVI1 voltage is lower than VOLMAX (20000mV =20V), counter increases by 1)**
	586	+(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
605	605
606		-(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), counter increases by 1)**
	588	+(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
607	607	)))
608	608
609	609
...	...	@@ -722,9 +722,9 @@
722	722
723	723	(% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
724	724
725		-**Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
	707	+Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
726	726
727		-**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
	709	+Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
728	728
729	729	AA: Type Code for this downlink Command:
730	730
...	...	@@ -791,7 +791,7 @@
791	791
792	792	**Example:**
793	793
794		-10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW.
	776	+10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
795	795
796	796
797	797	(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
...	...	@@ -820,7 +820,7 @@
820	820
821	821	**Example:**
822	822
823		-10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low.
	805	+10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
824	824
825	825
826	826	(% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
...	...	@@ -829,22 +829,22 @@
829	829	|(% style="width:64px" %)**bit 7**|(% style="width:68px" %)**bit 6**|(% style="width:63px" %)**bit 5**|(% style="width:66px" %)**bit 4**|(% style="width:109px" %)**bit 3**|(% style="width:93px" %)**bit 2**|(% style="width:109px" %)**bit 1**|(% style="width:99px" %)**bit 0**
830	830	|(% style="width:64px" %)N/A|(% style="width:68px" %)N/A|(% style="width:63px" %)N/A|(% style="width:66px" %)N/A|(% style="width:109px" %)DI2_STATUS|(% style="width:93px" %)DI2_FLAG|(% style="width:109px" %)DI1_STATUS|(% style="width:99px" %)DI1_FLAG
831	831
832		-* Each bit shows which status has been triggered on this uplink.
	814	+* Each bits shows which status has been triggered on this uplink.
833	833
834	834	**Example:**
835	835
836		-00000111: This means both DI1 and DI2 triggers are enabled, and this packet is trigger by DI1.
	818	+00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
837	837
838		-00000101: This means both DI1 and DI2 triggers are enabled.
	820	+00000101: Means both DI1 and DI2 trigger are enabled.
839	839
840	840
841		-(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled.
	823	+(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable.
842	842
843		-Downlink command to poll/request MOD6 status:
	825	+Downlink command to poll MOD6 status:
844	844
845	845	**AB 06**
846	846
847		-When device receives this command, it will send the MOD6 payload.
	829	+When device got this command, it will send the MOD6 payload.
848	848
849	849
850	850	=== 3.3.7 Payload Decoder ===
...	...	@@ -883,7 +883,7 @@
883	883	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.
884	884
885	885
886		-==== 3.4.2.1 Set Transmit/Uplink Interval ====
	868	+==== 3.4.2.1 Set Transmit Interval ====
887	887
888	888	Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
889	889
...	...	@@ -892,11 +892,11 @@
892	892	(% border="2" style="width:500px" %)
893	893	|**Command**|AT+TDC=<time>
894	894	|**Response**|
895		-|**Parameters**|**time** : uplink interval is in **milliseconds**
	877	+|**Parameters**|**time** : uplink interval is in milliseconds
896	896	|**Example**|(((
897	897	AT+TDC=30000
898	898
899		-Sets the uplink interval to **30 seconds** (30000 milliseconds)
	881	+Sets the uplink interval to 30,000 milliseconds (30 seconds)
900	900	)))
901	901
902	902	(% style="color:#037691" %)**Downlink payload**
...	...	@@ -908,18 +908,16 @@
908	908	|**Parameters**|(((
909	909	**prefix** : 0x01
910	910
911		-**time** : uplink interval is in **seconds**, represented by **3  bytes** in **hexadecimal**.
	893	+**time** : uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
912	912	)))
913	913	|**Example**|(((
914		-01 **00 00 1E**
	896	+01 **00 75 30**
915	915
916		-Sets the uplink interval to **30 seconds**
	898	+Sets the uplink interval to 30,000 milliseconds (30 seconds)
917	917
918		-Conversion: 30 (dec) = 00 00 1E (hex)
	900	+Conversion: 30000 (dec) = 00 75 30 (hex)
919	919
920		-See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30]]
921		-
922		-[[image:Screenshot 2024-11-23 at 18.27.11.png]]
	902	+See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]]
923	923	)))
924	924
925	925	==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
...	...	@@ -968,13 +968,13 @@
968	968	Sets the device to working mode 2 (Double DI Counting + DO + RO)
969	969	)))
970	970
971		-==== 3.4.2.3 Request an uplink from the device ====
	951	+==== 3.4.2.3 Poll an uplink ====
972	972
973		-Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
	953	+Requests an uplink from LT-22222-L.
974	974
975	975	(% style="color:#037691" %)**AT command**
976	976
977		-There is no AT Command available for this feature.
	957	+There is no AT Command to request an uplink from LT-22222-L
978	978
979	979	(% style="color:#037691" %)**Downlink payload**
980	980
...	...	@@ -982,7 +982,7 @@
982	982	|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF
983	983	|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08
984	984	|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
985		-08 **FF**
	965	+08 FF
986	986
987	987	Requests an uplink from LT-22222-L.
988	988	)))
...	...	@@ -1016,7 +1016,7 @@
1016	1016	|(% style="width:97px" %)**Parameters**|(% style="width:401px" %)(((
1017	1017	**prefix** : 0x0A 06 (two bytes in hexadecimal)
1018	1018
1019		-**enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
	999	+**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
1020	1020	)))
1021	1021	|(% style="width:97px" %)**Example**|(% style="width:401px" %)(((
1022	1022	0A 06 **01**
...	...	@@ -1024,13 +1024,13 @@
1024	1024	Enable trigger mode for the current working mode
1025	1025	)))
1026	1026
1027		-==== 3.4.2.5 Request trigger settings ====
	1007	+==== 3.4.2.5 Poll trigger settings ====
1028	1028
1029		-Requests the trigger settings.
	1009	+Polls the trigger settings.
1030	1030
1031	1031	(% style="color:#037691" %)**AT Command:**
1032	1032
1033		-There is no AT Command available for this feature.
	1013	+There is no AT Command for this feature.
1034	1034
1035	1035	(% style="color:#037691" %)**Downlink Payload**
1036	1036
...	...	@@ -1170,6 +1170,8 @@
1170	1170	)))
1171	1171	|(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
1172	1172
	1153	+==== ====
	1154	+
1173	1173	==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1174	1174
1175	1175	Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
...	...	@@ -1351,28 +1351,32 @@
1351	1351	)))
1352	1352	)))
1353	1353
	1336	+==== ====
	1337	+
1354	1354	==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1355	1355
1356	1356
1357	1357	* (% style="color:#037691" %)**AT Command**
1358	1358
1359		-There is no AT command to control the digital output.
	1343	+There is no AT Command to control Digital Output
1360	1360
1361	1361
1362	1362	* (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
1363	1363
1364		-(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control
	1348	+(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Set DO1/DO2/DO3 output with time control
1365	1365
	1350	+
1366	1366	This is to control the digital output time of DO pin. Include four bytes:
1367	1367
1368		-(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)
	1353	+(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
1369	1369
1370		-(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode
	1355	+(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
1371	1371
1372		-**01:** DO pins revert to their original state after the timeout.
1373		-**00:** DO pins switch to an inverted state after the timeout.
	1357	+01: DO pins will change back to original state after timeout.
1374	1374
	1359	+00: DO pins will change to an inverter state after timeout
1375	1375
	1361	+
1376	1376	(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1377	1377
1378	1378	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
...	...	@@ -1381,7 +1381,7 @@
1381	1381	|0x00|DO1 set to high
1382	1382	|0x11|DO1 NO Action
1383	1383
1384		-(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:
	1370	+(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
1385	1385
1386	1386	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1387	1387	|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
...	...	@@ -1389,7 +1389,7 @@
1389	1389	|0x00|DO2 set to high
1390	1390	|0x11|DO2 NO Action
1391	1391
1392		-(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:
	1378	+(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
1393	1393
1394	1394	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1395	1395	|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
...	...	@@ -1397,7 +1397,7 @@
1397	1397	|0x00|DO3 set to high
1398	1398	|0x11|DO3 NO Action
1399	1399
1400		-(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)
	1386	+(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
1401	1401
1402	1402
1403	1403	(% style="color:red" %)**Note: **
...	...	@@ -1406,7 +1406,7 @@
1406	1406
1407	1407	Before firmware v1.6.0, the latch time only supported 2 bytes.
1408	1408
1409		-(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
	1395	+(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1410	1410
1411	1411
1412	1412	**Example payload:**
...	...	@@ -1433,16 +1433,16 @@
1433	1433
1434	1434	* (% style="color:#037691" %)**AT Command:**
1435	1435
1436		-There is no AT Command to control the Relay Output
	1422	+There is no AT Command to control Relay Output
1437	1437
1438	1438
1439	1439	* (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
1440	1440
1441		-(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Sets RO1/RO2 output
	1427	+(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
1442	1442
1443	1443
1444	1444	(((
1445		-If the payload is 0x030100, it means setting RO1 to close and RO2 to open.
	1431	+If payload is 0x030100, it means setting RO1 to close and RO2 to open.
1446	1446	)))
1447	1447
1448	1448	(((
...	...	@@ -1460,7 +1460,7 @@
1460	1460	|03  00  01|Open|Close
1461	1461	)))
1462	1462
1463		-(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
	1449	+(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
1464	1464
1465	1465
1466	1466	==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
...	...	@@ -1469,19 +1469,19 @@
1469	1469
1470	1470	* (% style="color:#037691" %)**AT Command:**
1471	1471
1472		-There is no AT Command to control the Relay Output
	1458	+There is no AT Command to control Relay Output
1473	1473
1474	1474
1475	1475	* (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1476	1476
1477		-(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
	1463	+(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
1478	1478
1479	1479
1480		-This controls the relay output time and includes 4 bytes:
	1466	+This is to control the relay output time. It includes four bytes:
1481	1481
1482		-(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
	1468	+(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
1483	1483
1484		-(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
	1470	+(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
1485	1485
1486	1486	01: Relays will change back to their original state after timeout.
1487	1487
...	...	@@ -1488,12 +1488,12 @@
1488	1488	00: Relays will change to the inverter state after timeout.
1489	1489
1490	1490
1491		-(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
	1477	+(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
1492	1492
1493	1493	[[image:image-20221008095908-1.png||height="364" width="564"]]
1494	1494
1495	1495
1496		-(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms
	1482	+(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
1497	1497
1498	1498
1499	1499	(% style="color:red" %)**Note:**
...	...	@@ -1503,7 +1503,7 @@
1503	1503	Before firmware v1.6.0, the latch time only supported 2 bytes.
1504	1504
1505	1505
1506		-(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
	1492	+(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1507	1507
1508	1508
1509	1509	**Example payload:**
...	...	@@ -1531,10 +1531,17 @@
1531	1531
1532	1532	When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1533	1533
	1520	+* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX   ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
	1521	+
	1522	+* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):**
	1523	+
	1524	+(% style="color:blue" %)**0xA5 aa bb cc   ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc
	1525	+
	1526	+
1534	1534	(% style="color:#037691" %)**AT Command**
1535	1535
1536	1536	(% border="2" style="width:500px" %)
1537		-|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage>,<logic>
	1530	+|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage><logic>
1538	1538	|(% style="width:137px" %)**Response**|(% style="width:361px" %)
1539	1539	|(% style="width:137px" %)**Parameters**|(% style="width:361px" %)(((
1540	1540	**voltage** : voltage threshold in mV
...	...	@@ -1541,9 +1541,9 @@
1541	1541
1542	1542	**logic**:
1543	1543
1544		-**0** : lower than
	1537	+0 : lower than
1545	1545
1546		-**1**: higher than
	1539	+1: higher than
1547	1547
1548	1548	if you leave logic parameter blank, it is considered 0
1549	1549	)))
...	...	@@ -1572,9 +1572,9 @@
1572	1572
1573	1573	**logic**: (1 byte in hexadecimal)
1574	1574
1575		-**0** : lower than
	1568	+0 : lower than
1576	1576
1577		-**1**: higher than
	1570	+1: higher than
1578	1578
1579	1579	if you leave logic parameter blank, it is considered 1 (higher than)
1580	1580	)))
...	...	@@ -1594,12 +1594,24 @@
1594	1594
1595	1595	==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ====
1596	1596
1597		-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.
	1590	+This feature allows users to pre-configure specific count numbers for various counting parameters such as Count1, Count2, or AVI1 Count. Use the AT command to set the desired count number for each configuration.
1598	1598
	1592	+* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) **
	1593	+
	1594	+(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count
	1595	+
	1596	+(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set
	1597	+
	1598	+
	1599	+* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):**
	1600	+
	1601	+(% style="color:blue" %)**0x A8 aa bb cc dd ee     ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
	1602	+
	1603	+
1599	1599	(% style="color:#037691" %)**AT Command**
1600	1600
1601	1601	(% border="2" style="width:500px" %)
1602		-|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter>,<number>
	1607	+|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter><number>
1603	1603	|(% style="width:134px" %)**Response**|(% style="width:364px" %)
1604	1604	|(% style="width:134px" %)**Parameters**|(% style="width:364px" %)(((
1605	1605	**counting_parameter** :
...	...	@@ -1643,8 +1643,14 @@
1643	1643
1644	1644	==== 3.4.2.18 Counting ~-~- Clear Counting ====
1645	1645
1646		-This command clears the counting in counting mode.
	1651	+This feature clears the counting in counting mode.
1647	1647
	1653	+* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
	1654	+
	1655	+* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
	1656	+
	1657	+(% style="color:blue" %)**0x A6 01    ** (%%)~/~/ clear all counting
	1658	+
1648	1648	(% style="color:#037691" %)**AT Command**
1649	1649
1650	1650	(% border="2" style="width:500px" %)
...	...	@@ -1662,225 +1662,94 @@
1662	1662	)))
1663	1663	|(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
1664	1664
1665		-==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
	1676	+==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1666	1666
1667		-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.
	1678	+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.
1668	1668
1669		-(% style="color:#037691" %)**AT Command**
	1680	+* (% style="color:#037691" %)**AT Command:**
1670	1670
1671		-(% border="2" style="width:500px" %)
1672		-|(% style="width:124px" %)**Command**|(% style="width:374px" %)AT+COUTIME=<time>
1673		-|(% style="width:124px" %)**Response**|(% style="width:374px" %)
1674		-|(% style="width:124px" %)**Parameters**|(% style="width:374px" %)time : seconds (0 to 16777215)
1675		-|(% style="width:124px" %)**Example**|(% style="width:374px" %)(((
1676		-AT+COUTIME=60
	1682	+(% 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)
1677	1677
1678		-Sets the device to save its counting results to the memory every 60 seconds.
1679		-)))
1680	1680
1681		-(% style="color:#037691" %)**Downlink Payload**
	1685	+* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
1682	1682
1683		-(% border="2" style="width:500px" %)
1684		-|(% style="width:123px" %)**Payload**|(% style="width:375px" %)<prefix><time>
1685		-|(% style="width:123px" %)**Parameters**|(% style="width:375px" %)(((
1686		-prefix : A7
	1687	+(% style="color:blue" %)**0x A7 aa bb cc     ** (%%)~/~/ same as AT+COUTIME =aa bb cc,
1687	1687
1688		-time : seconds, 3 bytes in hexadecimal
	1689	+(((
	1690	+Range: aa bb cc:0 to 16777215,  (unit: seconds)
1689	1689	)))
1690		-|(% style="width:123px" %)**Example**|(% style="width:375px" %)(((
1691		-A7 **00 00 3C**
1692	1692
1693		-Sets the device to save its counting results to the memory every 60 seconds.
1694		-)))
1695	1695
1696		-==== 3.4.2.20 Reset saved RO and DO states ====
1697	1697
1698		-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.
	1695	+==== 3.4.2.20 Reset save RO DO state ====
1699	1699
1700		-(% style="color:#037691" %)**AT Command**
	1697	+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.
1701	1701
1702		-(% border="2" style="width:500px" %)
1703		-|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state>
1704		-|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1705		-|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1706		-**state** :
	1699	+* (% style="color:#037691" %)**AT Command:**
1707	1707
1708		-**0** : RODO will close when the device joins the network. (default)
	1701	+(% style="color:blue" %)**AT+RODORESET=1    **(%%)~/~/ RODO will close when the device joining the network. (default)
1709	1709
1710		-**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.
1711		-)))
1712		-|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1713		-(% style="color:blue" %)**AT+RODORESET=1 **
	1703	+(% 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	1714
1715		-RODO will close when the device joins the network. (default)
1716	1716
1717		-(% style="color:blue" %)**AT+RODORESET=0 **
	1706	+* (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):**
1718	1718
1719		-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.
1720		-)))
	1708	+(% style="color:blue" %)**0x AD aa      ** (%%)~/~/ same as AT+RODORET =aa
1721	1721
1722		-(% style="color:#037691" %)**Downlink Payload**
1723	1723
1724		-(% border="2" style="width:500px" %)
1725		-|(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state>
1726		-|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1727		-**prefix** : AD
1728	1728
1729		-**state** :
1730		-
1731		-**0** : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal.
1732		-
1733		-**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
1734		-)))
1735		-|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1736		-AD **01**
1737		-
1738		-RODO will close when the device joins the network. (default)
1739		-
1740		-AD **00**
1741		-
1742		-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.
1743		-)))
1744		-
1745	1745	==== 3.4.2.21 Encrypted payload ====
1746	1746
1747		-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.
	1714	+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.
1748	1748
1749		-(% style="color:#037691" %)**AT Command:**
	1716	+* (% style="color:#037691" %)**AT Command:**
1750	1750
1751		-(% border="2" style="width:500px" %)
1752		-|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state>
1753		-|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1754		-|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1755		-**state** :
	1718	+(% style="color:blue" %)**AT+DECRYPT=1  ** (%%)~/~/ The payload is uploaded without encryption
1756	1756
1757		-**1** : The payload is uploaded without encryption
	1720	+(% style="color:blue" %)**AT+DECRYPT=0    **(%%)~/~/  Encrypt when uploading payload (default)
1758	1758
1759		-**0** : The payload is encrypted when uploaded (default)
1760		-)))
1761		-|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1762		-AT+DECRYPT=1
1763	1763
1764		-The payload is uploaded without encryption
1765	1765
1766		-AT+DECRYPT=0
1767		-
1768		-The payload is encrypted when uploaded (default)
1769		-)))
1770		-
1771		-There is no downlink payload for this configuration.
1772		-
1773		-
1774	1774	==== 3.4.2.22 Get sensor value ====
1775	1775
1776		-This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1777	1777
1778		-(% style="color:#037691" %)**AT Command**
	1727	+* (% style="color:#037691" %)**AT Command:**
1779	1779
1780		-(% border="2" style="width:500px" %)
1781		-|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
1782		-|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1783		-|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1784		-**state** :
	1729	+(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port retrieves the reading of the current sensor.
1785	1785
1786		-**0 **: Retrieves the current sensor reading via the serial port.
	1731	+(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.
1787	1787
1788		-**1 **: Retrieves and uploads the current sensor reading via the serial port.
1789		-)))
1790		-|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1791		-AT+GETSENSORVALUE=0
1792	1792
1793		-Retrieves the current sensor reading via the serial port.
1794	1794
1795		-AT+GETSENSORVALUE=1
	1735	+==== 3.4.2.23 Resets the downlink packet count ====
1796	1796
1797		-Retrieves and uplinks the current sensor reading via the serial port.
1798		-)))
1799	1799
1800		-There is no downlink payload for this configuration.
	1738	+* (% style="color:#037691" %)**AT Command:**
1801	1801
	1740	+(% 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)
1802	1802
1803		-==== 3.4.2.23 Resetting the downlink packet count ====
	1742	+(% 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.
1804	1804
1805		-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.
1806	1806
1807		-(% style="color:#037691" %)**AT Command**
1808	1808
1809		-(% border="2" style="width:500px" %)
1810		-|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
1811		-|(% style="width:130px" %)**Response**|(% style="width:368px" %)(((
1812		-
1813		-)))
1814		-|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)(((
1815		-**state **:
1816		-
1817		-**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).
1818		-
1819		-
1820		-**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.
1821		-)))
1822		-|(% style="width:130px" %)**Example**|(% style="width:368px" %)(((
1823		-AT+DISFCNTCHECK=0
1824		-
1825		-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).
1826		-
1827		-AT+DISFCNTCHECK=1
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 resets its downlink packet count to match the server's, ensuring consistency.
1830		-)))
1831		-
1832		-There is no downlink payload for this configuration.
1833		-
1834		-
1835	1835	==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ====
1836	1836
1837	1837
1838		-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.
	1749	+* (% style="color:#037691" %)**AT Command:**
1839	1839
1840		-(% style="color:#037691" %)**AT Command**
	1751	+(% 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)
1841	1841
1842		-(% border="2" style="width:500px" %)
1843		-|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state>
1844		-|(% style="width:127px" %)**Response**|(% style="width:371px" %)
1845		-|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1846		-**state** :
	1753	+(% 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.
1847	1847
1848		-**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)
1849	1849
1850		-**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.
1851		-)))
1852		-|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1853		-AT+DISMACANS=0
	1756	+* (% style="color:#037691" %)**Downlink Payload **(%%)**:**
1854	1854
1855		-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)
	1758	+(% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set  the DISMACANS=1
1856	1856
1857		-AT+DISMACANS=1
1858	1858
1859		-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.
1860		-)))
1861	1861
1862		-(% style="color:#037691" %)**Downlink Payload**
1863		-
1864		-(% border="2" style="width:500px" %)
1865		-|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state>
1866		-|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)(((
1867		-**prefix** : 21
1868		-
1869		-**state** : (2 bytes in hexadecimal)
1870		-
1871		-**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)
1872		-
1873		-**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.
1874		-)))
1875		-|(% style="width:126px" %)**Example**|(% style="width:372px" %)(((
1876		-21 **00 01**
1877		-
1878		-Set DISMACANS=1
1879		-)))
1880		-
1881	1881	==== 3.4.2.25 Copy downlink to uplink ====
1882	1882
1883		-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.
1884	1884
1885	1885	* (% style="color:#037691" %)**AT Command**(%%)**:**
1886	1886
...	...	@@ -1893,22 +1893,8 @@
1893	1893
1894	1894	For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1895	1895
1896		-(% border="2" style="width:500px" %)
1897		-|(% style="width:122px" %)**Command**|(% style="width:376px" %)(((
1898		-AT+RPL=5
1899	1899
1900		-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.
1901		-)))
1902		-|(% style="width:122px" %)**Example**|(% style="width:376px" %)(((
1903		-Downlink:
1904	1904
1905		-01 00 02 58
1906		-
1907		-Uplink:
1908		-
1909		-01 01 00 02 58
1910		-)))
1911		-
1912	1912	[[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"]]
1913	1913
1914	1914	For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
...	...	@@ -1915,16 +1915,14 @@
1915	1915
1916	1916
1917	1917
1918		-==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
	1784	+==== 3.4.2.26 Query version number and frequency band 、TDC ====
1919	1919
1920		-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.
1921	1921
1922	1922	* (((
1923	1923	(% style="color:#037691" %)**Downlink Payload**(%%)**:**
1924	1924
1925		-(% 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.
	1790	+(% style="color:blue" %)**26 01  ** (%%) ~/~/  Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
1926	1926
1927		-
1928	1928
1929	1929	)))
1930	1930
...	...	@@ -1950,17 +1950,15 @@
1950	1950	The username and  password (API key) you created here are required in the next section.
1951	1951	{{/info}}
1952	1952
1953		-[[image:tts-mqtt-integration.png]]
	1817	+[[image:tts-mqtt-integration.png||height="625" width="1000"]]
1954	1954
1955	1955	=== 3.5.2 Configuring ThingsEye.io ===
1956	1956
1957		-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.
1958		-
1959	1959	* Login to your [[ThingsEye.io >>https://thingseye.io]]account.
1960	1960	* Under the **Integrations center**, click **Integrations**.
1961	1961	* Click the **Add integration** button (the button with the **+** symbol).
1962	1962
1963		-[[image:thingseye-io-step-1.png]]
	1825	+[[image:thingseye-io-step-1.png||height="625" width="1000"]]
1964	1964
1965	1965
1966	1966	On the **Add integration** window, configure the following:
...	...	@@ -1975,7 +1975,7 @@
1975	1975	** Allow create devices or assets
1976	1976	* Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
1977	1977
1978		-[[image:thingseye-io-step-2.png]]
	1840	+[[image:thingseye-io-step-2.png||height="625" width="1000"]]
1979	1979
1980	1980
1981	1981	**Uplink data converter:**
...	...	@@ -1986,7 +1986,7 @@
1986	1986	* 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]].
1987	1987	* Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
1988	1988
1989		-[[image:thingseye-io-step-3.png]]
	1851	+[[image:thingseye-io-step-3.png||height="625" width="1000"]]
1990	1990
1991	1991
1992	1992	**Downlink data converter (this is an optional step):**
...	...	@@ -1997,7 +1997,7 @@
1997	1997	* 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]].
1998	1998	* Click the **Next** button. You will be navigated to the **Connection** tab.
1999	1999
2000		-[[image:thingseye-io-step-4.png]]
	1862	+[[image:thingseye-io-step-4.png||height="625" width="1000"]]
2001	2001
2002	2002
2003	2003	**Connection:**
...	...	@@ -2004,7 +2004,7 @@
2004	2004
2005	2005	* Choose **Region** from the **Host type**.
2006	2006	* 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/...).
2007		-* 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**).
	1869	+* 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).
2008	2008	* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
2009	2009
2010	2010	[[image:message-1.png]]
...	...	@@ -2012,13 +2012,13 @@
2012	2012
2013	2013	* Click the **Add** button.
2014	2014
2015		-[[image:thingseye-io-step-5.png]]
	1877	+[[image:thingseye-io-step-5.png||height="625" width="1000"]]
2016	2016
2017	2017
2018		-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.
	1880	+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.
2019	2019
2020	2020
2021		-[[image:thingseye.io_integrationsCenter_integrations.png]]
	1883	+[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
2022	2022
2023	2023
2024	2024	==== 3.5.2.1 Viewing integration details ====
...	...	@@ -2025,13 +2025,13 @@
2025	2025
2026	2026	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.
2027	2027
2028		-[[image:integration-details.png]]
	1890	+[[image:integration-details.png||height="686" width="1000"]]
2029	2029
2030	2030
2031	2031	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.
2032	2032
2033	2033	{{info}}
2034		-See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
	1896	+See also ThingsEye documentation.
2035	2035	{{/info}}
2036	2036
2037	2037	==== **3.5.2.2 Viewing events** ====
...	...	@@ -2041,12 +2041,12 @@
2041	2041	* Select **Debug **from the **Event type** dropdown.
2042	2042	* Select the** time frame** from the **time window**.
2043	2043
2044		-[[image:thingseye-events.png]]
	1906	+[[image:thingseye-events.png||height="686" width="1000"]]
2045	2045
2046	2046
2047		-* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
	1909	+* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
2048	2048
2049		-[[image:thingseye-json.png]]
	1911	+[[image:thingseye-json.png||width="1000"]]
2050	2050
2051	2051
2052	2052	==== **3.5.2.3 Deleting an integration** ====
...	...	@@ -2054,17 +2054,12 @@
2054	2054	If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
2055	2055
2056	2056
2057		-==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
2058		-
2059		-This will be added soon.
2060		-
2061		-
2062	2062	== 3.6 Interface Details ==
2063	2063
2064	2064	=== 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
2065	2065
2066	2066
2067		-Supports** NPN-type **sensors.
	1924	+Supports NPN-type sensors.
2068	2068
2069	2069	[[image:1653356991268-289.png]]
2070	2070
...	...	@@ -2186,15 +2186,15 @@
2186	2186	)))
2187	2187
2188	2188
2189		-(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor
	2046	+(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
2190	2190
2191		-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.
	2048	+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.
2192	2192
2193		-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.
	2050	+To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.
2194	2194
2195	2195	[[image:image-20230616235145-1.png]]
2196	2196
2197		-(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector
	2054	+(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
2198	2198
2199	2199	[[image:image-20240219115718-1.png]]
2200	2200
...	...	@@ -2270,7 +2270,7 @@
2270	2270	[[image:image-20220524100215-10.png||height="382" width="723"]]
2271	2271
2272	2272
2273		-== 3.7 LED Indicators ==
	2130	+== 3.7 LEDs Indicators ==
2274	2274
2275	2275	The table below lists the behavior of LED indicators for each port function.
2276	2276
...	...	@@ -2309,14 +2309,13 @@
2309	2309	== 4.1 Connecting the LT-22222-L to a PC ==
2310	2310
2311	2311	(((
2312		-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.
	2169	+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.
2313	2313
2314		-[[image:usb-ttl-audio-jack-connection.jpg]]
2315		-
2316		-
	2171	+[[image:usb-ttl-programming.png]]
2317	2317	)))
2318	2318
2319	2319
	2175	+
2320	2320	(((
2321	2321	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:
2322	2322	)))
...	...	@@ -2346,39 +2346,39 @@
2346	2346	* **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
2347	2347	* **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
2348	2348	* **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
2349		-* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2350		-* **##AT+DR##**:  Get or set the Data Rate. (0-7 corresponding to DR_X)
2351		-* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2352		-* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)
2353		-* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency
2354		-* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2355		-* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2356		-* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2357		-* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2358		-* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2359		-* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2360		-* ##**AT+NWKID**##: Get or set the Network ID
2361		-* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)
2362		-* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)
2363		-* ##**AT+CLASS**##: Get or set the Device Class
2364		-* ##**AT+JOIN**##: Join network
2365		-* ##**AT+NJS**##: Get OTAA Join Status
2366		-* ##**AT+SENDB**##: Send hexadecimal data along with the application port
2367		-* ##**AT+SEND**##: Send text data along with the application port
2368		-* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)
2369		-* ##**AT+RECV**##: Print last received data in raw format
2370		-* ##**AT+VER**##: Get current image version and Frequency Band
2371		-* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)
2372		-* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)
2373		-* ##**AT+SNR**##: Get the SNR of the last received packet
2374		-* ##**AT+RSSI**##: Get the RSSI of the last received packet
2375		-* ##**AT+TDC**##: Get or set the application data transmission interval in ms
2376		-* ##**AT+PORT**##: Get or set the application port
2377		-* ##**AT+DISAT**##: Disable AT commands
2378		-* ##**AT+PWORD**##: Set password, max 9 digits
2379		-* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2380		-* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470
2381		-* ##**AT+CFG**##: Print all settings
	2205	+* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
	2206	+* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)
	2207	+* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
	2208	+* AT+PNM: Get or set the public network mode. (0: off, 1: on)
	2209	+* AT+RX2FQ: Get or set the Rx2 window frequency
	2210	+* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
	2211	+* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
	2212	+* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
	2213	+* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
	2214	+* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
	2215	+* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
	2216	+* AT+NWKID: Get or set the Network ID
	2217	+* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
	2218	+* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
	2219	+* AT+CLASS: Get or set the Device Class
	2220	+* AT+JOIN: Join network
	2221	+* AT+NJS: Get OTAA Join Status
	2222	+* AT+SENDB: Send hexadecimal data along with the application port
	2223	+* AT+SEND: Send text data along with the application port
	2224	+* AT+RECVB: Print last received data in binary format (with hexadecimal values)
	2225	+* AT+RECV: Print last received data in raw format
	2226	+* AT+VER: Get current image version and Frequency Band
	2227	+* AT+CFM: Get or Set the confirmation mode (0-1)
	2228	+* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
	2229	+* AT+SNR: Get the SNR of the last received packet
	2230	+* AT+RSSI: Get the RSSI of the last received packet
	2231	+* AT+TDC: Get or set the application data transmission interval in ms
	2232	+* AT+PORT: Get or set the application port
	2233	+* AT+DISAT: Disable AT commands
	2234	+* AT+PWORD: Set password, max 9 digits
	2235	+* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
	2236	+* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
	2237	+* AT+CFG: Print all settings
2382	2382	)))
2383	2383
2384	2384
...	...	@@ -2543,7 +2543,7 @@
2543	2543	You will need the following things before proceeding:
2544	2544
2545	2545	* 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2546		-* USB to TTL adapter/converter
	2402	+* USB to TTL adapter
2547	2547	* 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)
2548	2548	* 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.
2549	2549
...	...	@@ -2553,7 +2553,7 @@
2553	2553
2554	2554	Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2555	2555
2556		-[[image:usb-ttl-audio-jack-connection.jpg]]
	2412	+[[image:usb-ttl-programming.png]]
2557	2557
2558	2558
2559	2559

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

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

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