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

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 3 added, 0 removed)
  • Screenshot 2024-11-23 at 18.27.11.png
  • dragino-lorawan-nw-lt-22222-n.jpg
  • lorawan-nw.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 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,21 +40,20 @@
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	+
58	58	== 1.2 Specifications ==
59	59
60	60	(% style="color:#037691" %)**Hardware System:**
...	...	@@ -120,7 +120,7 @@
120	120	(% style="width:524px" %)
121	121	|(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description**
122	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"]]
	122	+
124	124	)))|(% style="width:329px" %)(((
125	125	* 2 x Digital Input (Bi-direction)
126	126	* 2 x Digital Output
...	...	@@ -130,26 +130,24 @@
130	130	* 1 x Counting Port
131	131	)))
132	132
	132	+= 2. Assembling the device =
133	133
134		-
135		-== 2. Assembling the device ==
136		-
137	137	== 2.1 Connecting the antenna ==
138	138
139	139	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.
140	140
141	141	{{warning}}
142		-Warning! Do not power on the device without connecting the antenna.
	139	+**Warning! Do not power on the device without connecting the antenna.**
143	143	{{/warning}}
144	144
145	145	== 2.2 Terminals ==
146	146
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.
	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.
148	148
149		-Upper screw terminal block (from left to right):
	146	+**Upper screw terminal block (from left to right):**
150	150
151	151	(% style="width:634px" %)
152		-|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function
	149	+|=(% style="width: 295px;" %)Screw Terminal|=(% style="width: 338px;" %)Function
153	153	|(% style="width:295px" %)GND|(% style="width:338px" %)Ground
154	154	|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage
155	155	|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2
...	...	@@ -157,10 +157,10 @@
157	157	|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2
158	158	|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1
159	159
160		-Lower screw terminal block (from left to right):
	157	+**Lower screw terminal block (from left to right):**
161	161
162	162	(% style="width:633px" %)
163		-|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function
	160	+|=(% style="width: 296px;" %)Screw Terminal|=(% style="width: 334px;" %)Function
164	164	|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1
165	165	|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1
166	166	|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2
...	...	@@ -172,14 +172,12 @@
172	172	|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
173	173	|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
174	174
175		-== 2.3 Powering the device ==
	172	+== 2.3 Connecting LT-22222-L to a Power Source ==
176	176
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.
	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.
178	178
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		-
181	181	{{warning}}
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.
	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.**
183	183	{{/warning}}
184	184
185	185
...	...	@@ -186,36 +186,51 @@
186	186	[[image:1653297104069-180.png]]
187	187
188	188
189		-= 3. Registering with a LoRaWAN Network Server =
	184	+= 3. Registering LT-22222-L with a LoRaWAN Network Server =
190	190
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.
	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.
192	192
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.
194	194
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		-
201	201	=== 3.2.1 Prerequisites ===
202	202
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.
	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.
204	204
205	205	[[image:image-20230425173427-2.png||height="246" width="530"]]
206	206
	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	+
207	207	The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
208	208
209		-=== 3.2.2 The Things Stack Sandbox (TTSS) ===
	201	+=== 3.2.2 The Things Stack ===
210	210
	203	+This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
	204	+
	205	+{{info}}
211	211	The Things Stack Sandbox was formally called The Things Stack Community Edition.
	207	+{{/info}}
212	212
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.
	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.
216	216	* On the End devices page, click on **+ Register end device**. Two registration options are available:
217	217
218		-==== 3.2.2.1 Using the LoRaWAN Device Repository ====
	228	+==== 3.2.2.2 Using the LoRaWAN Device Repository ====
219	219
220	220	* On the **Register end device** page:
221	221	** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
...	...	@@ -239,9 +239,8 @@
239	239
240	240	[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
241	241
242		-==== ====
243	243
244		-==== 3.2.2.2 Adding device manually ====
	253	+==== 3.2.2.3 Adding device manually ====
245	245
246	246	* On the **Register end device** page:
247	247	** Select the option **Enter end device specifies manually** under **Input method**.
...	...	@@ -256,7 +256,7 @@
256	256
257	257
258	258	* Register end device page continued...
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'
	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**//'
260	260	** In the **DevEUI** field, enter the **DevEUI**.
261	261	** In the **AppKey** field, enter the **AppKey**.
262	262	** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
...	...	@@ -272,24 +272,27 @@
272	272	[[image:lt-22222-device-overview.png||height="625" width="1000"]]
273	273
274	274
275		-==== 3.2.2.3 Joining ====
	284	+==== 3.2.2.4 Joining ====
276	276
277		-On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
	286	+On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
278	278
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**).
	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.
280	280
281	281
282	282	[[image:lt-22222-join-network.png||height="625" width="1000"]]
283	283
284	284
285		-By default, you will receive an uplink data message from the device every 10 minutes.
	294	+==== 3.2.2.5 Uplinks ====
286	286
	296	+
	297	+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.
	298	+
287	287	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.
288	288
289	289	[[image:lt-22222-ul-payload-decoded.png]]
290	290
291	291
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.
	304	+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.
293	293
294	294	{{info}}
295	295	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.
...	...	@@ -298,6 +298,11 @@
298	298	[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
299	299
300	300
	313	+==== 3.2.2.6 Downlinks ====
	314	+
	315	+When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
	316	+
	317	+
301	301	== 3.3 Working Modes and Uplink Payload formats ==
302	302
303	303
...	...	@@ -865,7 +865,7 @@
865	865	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.
866	866
867	867
868		-==== 3.4.2.1 Set Transmit Interval ====
	885	+==== 3.4.2.1 Set Transmit/Uplink Interval ====
869	869
870	870	Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
871	871
...	...	@@ -874,11 +874,11 @@
874	874	(% border="2" style="width:500px" %)
875	875	|**Command**|AT+TDC=<time>
876	876	|**Response**|
877		-|**Parameters**|**time** : uplink interval is in milliseconds
	894	+|**Parameters**|**time** : uplink interval is in **milliseconds**
878	878	|**Example**|(((
879	879	AT+TDC=30000
880	880
881		-Sets the uplink interval to 30,000 milliseconds (30 seconds)
	898	+Sets the uplink interval to **30 seconds** (30000 milliseconds)
882	882	)))
883	883
884	884	(% style="color:#037691" %)**Downlink payload**
...	...	@@ -890,16 +890,18 @@
890	890	|**Parameters**|(((
891	891	**prefix** : 0x01
892	892
893		-**time** : uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
	910	+**time** : uplink interval is in **seconds**, represented by **3  bytes** in **hexadecimal**.
894	894	)))
895	895	|**Example**|(((
896		-01 **00 75 30**
	913	+01 **00 00 1E**
897	897
898		-Sets the uplink interval to 30,000 milliseconds (30 seconds)
	915	+Sets the uplink interval to **30 seconds**
899	899
900		-Conversion: 30000 (dec) = 00 75 30 (hex)
	917	+Conversion: 30 (dec) = 00 00 1E (hex)
901	901
902		-See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]]
	919	+See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30]]
	920	+
	921	+[[image:Screenshot 2024-11-23 at 18.27.11.png]]
903	903	)))
904	904
905	905	==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
...	...	@@ -950,11 +950,11 @@
950	950
951	951	==== 3.4.2.3 Poll an uplink ====
952	952
953		-Requests an uplink from LT-22222-L.
	972	+Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
954	954
955	955	(% style="color:#037691" %)**AT command**
956	956
957		-There is no AT Command to request an uplink from LT-22222-L
	976	+There is no AT Command available for this feature.
958	958
959	959	(% style="color:#037691" %)**Downlink payload**
960	960
...	...	@@ -962,7 +962,7 @@
962	962	|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF
963	963	|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08
964	964	|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
965		-08 FF
	984	+08 **FF**
966	966
967	967	Requests an uplink from LT-22222-L.
968	968	)))
...	...	@@ -996,7 +996,7 @@
996	996	|(% style="width:97px" %)**Parameters**|(% style="width:401px" %)(((
997	997	**prefix** : 0x0A 06 (two bytes in hexadecimal)
998	998
999		-**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
	1018	+**enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
1000	1000	)))
1001	1001	|(% style="width:97px" %)**Example**|(% style="width:401px" %)(((
1002	1002	0A 06 **01**
...	...	@@ -1010,7 +1010,7 @@
1010	1010
1011	1011	(% style="color:#037691" %)**AT Command:**
1012	1012
1013		-There is no AT Command for this feature.
	1032	+There is no AT Command available for this feature.
1014	1014
1015	1015	(% style="color:#037691" %)**Downlink Payload**
1016	1016
...	...	@@ -1150,8 +1150,6 @@
1150	1150	)))
1151	1151	|(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
1152	1152
1153		-==== ====
1154		-
1155	1155	==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1156	1156
1157	1157	Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
...	...	@@ -1333,8 +1333,6 @@
1333	1333	)))
1334	1334	)))
1335	1335
1336		-==== ====
1337		-
1338	1338	==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1339	1339
1340	1340
...	...	@@ -1517,17 +1517,10 @@
1517	1517
1518	1518	When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1519	1519
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		-
1527	1527	(% style="color:#037691" %)**AT Command**
1528	1528
1529	1529	(% border="2" style="width:500px" %)
1530		-|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage><logic>
	1538	+|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage>,<logic>
1531	1531	|(% style="width:137px" %)**Response**|(% style="width:361px" %)
1532	1532	|(% style="width:137px" %)**Parameters**|(% style="width:361px" %)(((
1533	1533	**voltage** : voltage threshold in mV
...	...	@@ -1534,9 +1534,9 @@
1534	1534
1535	1535	**logic**:
1536	1536
1537		-0 : lower than
	1545	+**0** : lower than
1538	1538
1539		-1: higher than
	1547	+**1**: higher than
1540	1540
1541	1541	if you leave logic parameter blank, it is considered 0
1542	1542	)))
...	...	@@ -1565,9 +1565,9 @@
1565	1565
1566	1566	**logic**: (1 byte in hexadecimal)
1567	1567
1568		-0 : lower than
	1576	+**0** : lower than
1569	1569
1570		-1: higher than
	1578	+**1**: higher than
1571	1571
1572	1572	if you leave logic parameter blank, it is considered 1 (higher than)
1573	1573	)))
...	...	@@ -1587,24 +1587,12 @@
1587	1587
1588	1588	==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ====
1589	1589
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	+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.
1591	1591
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		-
1604	1604	(% style="color:#037691" %)**AT Command**
1605	1605
1606	1606	(% border="2" style="width:500px" %)
1607		-|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter><number>
	1603	+|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter>,<number>
1608	1608	|(% style="width:134px" %)**Response**|(% style="width:364px" %)
1609	1609	|(% style="width:134px" %)**Parameters**|(% style="width:364px" %)(((
1610	1610	**counting_parameter** :
...	...	@@ -1648,14 +1648,8 @@
1648	1648
1649	1649	==== 3.4.2.18 Counting ~-~- Clear Counting ====
1650	1650
1651		-This feature clears the counting in counting mode.
	1647	+This command clears the counting in counting mode.
1652	1652
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		-
1659	1659	(% style="color:#037691" %)**AT Command**
1660	1660
1661	1661	(% border="2" style="width:500px" %)
...	...	@@ -1675,92 +1675,224 @@
1675	1675
1676	1676	==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1677	1677
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	+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.
1679	1679
1680		-* (% style="color:#037691" %)**AT Command:**
	1670	+(% style="color:#037691" %)**AT Command**
1681	1681
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)
	1672	+(% border="2" style="width:500px" %)
	1673	+|(% style="width:124px" %)**Command**|(% style="width:374px" %)AT+COUTIME=<time>
	1674	+|(% style="width:124px" %)**Response**|(% style="width:374px" %)
	1675	+|(% style="width:124px" %)**Parameters**|(% style="width:374px" %)time : seconds (0 to 16777215)
	1676	+|(% style="width:124px" %)**Example**|(% style="width:374px" %)(((
	1677	+AT+COUTIME=60
1683	1683
	1679	+Sets the device to save its counting results to the memory every 60 seconds.
	1680	+)))
1684	1684
1685		-* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
	1682	+(% style="color:#037691" %)**Downlink Payload**
1686	1686
1687		-(% style="color:blue" %)**0x A7 aa bb cc     ** (%%)~/~/ same as AT+COUTIME =aa bb cc,
	1684	+(% border="2" style="width:500px" %)
	1685	+|(% style="width:123px" %)**Payload**|(% style="width:375px" %)<prefix><time>
	1686	+|(% style="width:123px" %)**Parameters**|(% style="width:375px" %)(((
	1687	+prefix : A7
1688	1688
1689		-(((
1690		-Range: aa bb cc:0 to 16777215,  (unit: seconds)
	1689	+time : seconds, 3 bytes in hexadecimal
1691	1691	)))
	1691	+|(% style="width:123px" %)**Example**|(% style="width:375px" %)(((
	1692	+A7 **00 00 3C**
1692	1692
	1694	+Sets the device to save its counting results to the memory every 60 seconds.
	1695	+)))
1693	1693
1694		-
1695	1695	==== 3.4.2.20 Reset save RO DO state ====
1696	1696
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.
	1699	+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.
1698	1698
1699		-* (% style="color:#037691" %)**AT Command:**
	1701	+(% style="color:#037691" %)**AT Command**
1700	1700
1701		-(% style="color:blue" %)**AT+RODORESET=1    **(%%)~/~/ RODO will close when the device joining the network. (default)
	1703	+(% border="2" style="width:500px" %)
	1704	+|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state>
	1705	+|(% style="width:127px" %)**Response**|(% style="width:371px" %)
	1706	+|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
	1707	+**state** :
1702	1702
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.
	1709	+**0** : RODO will close when the device joins the network. (default)
1704	1704
	1711	+**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.
	1712	+)))
	1713	+|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
	1714	+(% style="color:blue" %)**AT+RODORESET=1 **
1705	1705
1706		-* (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):**
	1716	+RODO will close when the device joins the network. (default)
1707	1707
1708		-(% style="color:blue" %)**0x AD aa      ** (%%)~/~/ same as AT+RODORET =aa
	1718	+(% style="color:blue" %)**AT+RODORESET=0 **
1709	1709
	1720	+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.
	1721	+)))
1710	1710
1711	1711
	1724	+(% style="color:#037691" %)**Downlink Payload**
	1725	+
	1726	+(% border="2" style="width:500px" %)
	1727	+|(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state>
	1728	+|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
	1729	+**prefix** : AD
	1730	+
	1731	+**state** :
	1732	+
	1733	+**0** : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal.
	1734	+
	1735	+**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
	1736	+)))
	1737	+|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
	1738	+AD **01**
	1739	+
	1740	+RODO will close when the device joins the network. (default)
	1741	+
	1742	+AD **00**
	1743	+
	1744	+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.
	1745	+)))
	1746	+
1712	1712	==== 3.4.2.21 Encrypted payload ====
1713	1713
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.
	1749	+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.
1715	1715
1716		-* (% style="color:#037691" %)**AT Command:**
	1751	+(% style="color:#037691" %)**AT Command:**
1717	1717
1718		-(% style="color:blue" %)**AT+DECRYPT=1  ** (%%)~/~/ The payload is uploaded without encryption
	1753	+(% border="2" style="width:500px" %)
	1754	+|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state>
	1755	+|(% style="width:127px" %)**Response**|(% style="width:371px" %)
	1756	+|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
	1757	+**state** :
1719	1719
1720		-(% style="color:blue" %)**AT+DECRYPT=0    **(%%)~/~/  Encrypt when uploading payload (default)
	1759	+**1** : The payload is uploaded without encryption
1721	1721
	1761	+**0** : The payload is encrypted when uploaded (default)
	1762	+)))
	1763	+|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
	1764	+AT+DECRYPT=1
1722	1722
	1766	+The payload is uploaded without encryption
1723	1723
	1768	+AT+DECRYPT=0
	1769	+
	1770	+The payload is encrypted when uploaded (default)
	1771	+)))
	1772	+
	1773	+There is no downlink payload for this configuration.
	1774	+
	1775	+
1724	1724	==== 3.4.2.22 Get sensor value ====
1725	1725
	1778	+This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1726	1726
1727		-* (% style="color:#037691" %)**AT Command:**
	1780	+(% style="color:#037691" %)**AT Command**
1728	1728
1729		-(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port retrieves the reading of the current sensor.
	1782	+(% border="2" style="width:500px" %)
	1783	+|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
	1784	+|(% style="width:127px" %)**Response**|(% style="width:371px" %)
	1785	+|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
	1786	+**state** :
1730	1730
1731		-(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.
	1788	+**0 **: Retrieves the current sensor reading via the serial port.
1732	1732
	1790	+**1 **: Retrieves and uploads the current sensor reading via the serial port.
	1791	+)))
	1792	+|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
	1793	+AT+GETSENSORVALUE=0
1733	1733
	1795	+Retrieves the current sensor reading via the serial port.
1734	1734
1735		-==== 3.4.2.23 Resets the downlink packet count ====
	1797	+AT+GETSENSORVALUE=1
1736	1736
	1799	+Retrieves and uplinks the current sensor reading via the serial port.
	1800	+)))
1737	1737
1738		-* (% style="color:#037691" %)**AT Command:**
	1802	+There is no downlink payload for this configuration.
1739	1739
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)
1741	1741
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.
	1805	+==== 3.4.2.23 Resetting the downlink packet count ====
1743	1743
	1807	+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.
1744	1744
	1809	+(% style="color:#037691" %)**AT Command**
1745	1745
	1811	+(% border="2" style="width:500px" %)
	1812	+|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
	1813	+|(% style="width:130px" %)**Response**|(% style="width:368px" %)(((
	1814	+
	1815	+)))
	1816	+|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)(((
	1817	+**state **:
	1818	+
	1819	+**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).
	1820	+
	1821	+
	1822	+**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.
	1823	+)))
	1824	+|(% style="width:130px" %)**Example**|(% style="width:368px" %)(((
	1825	+AT+DISFCNTCHECK=0
	1826	+
	1827	+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).
	1828	+
	1829	+AT+DISFCNTCHECK=1
	1830	+
	1831	+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.
	1832	+)))
	1833	+
	1834	+There is no downlink payload for this configuration.
	1835	+
	1836	+
1746	1746	==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ====
1747	1747
1748	1748
1749		-* (% style="color:#037691" %)**AT Command:**
	1840	+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.
1750	1750
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)
	1842	+(% style="color:#037691" %)**AT Command**
1752	1752
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.
	1844	+(% border="2" style="width:500px" %)
	1845	+|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state>
	1846	+|(% style="width:127px" %)**Response**|(% style="width:371px" %)
	1847	+|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
	1848	+**state** :
1754	1754
	1850	+**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)
1755	1755
1756		-* (% style="color:#037691" %)**Downlink Payload **(%%)**:**
	1852	+**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.
	1853	+)))
	1854	+|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
	1855	+AT+DISMACANS=0
1757	1757
1758		-(% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set  the DISMACANS=1
	1857	+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)
1759	1759
	1859	+AT+DISMACANS=1
1760	1760
	1861	+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.
	1862	+)))
1761	1761
	1864	+(% style="color:#037691" %)**Downlink Payload**
	1865	+
	1866	+(% border="2" style="width:500px" %)
	1867	+|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state>
	1868	+|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)(((
	1869	+**prefix** : 21
	1870	+
	1871	+**state** : (2 bytes in hexadecimal)
	1872	+
	1873	+**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)
	1874	+
	1875	+**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.
	1876	+)))
	1877	+|(% style="width:126px" %)**Example**|(% style="width:372px" %)(((
	1878	+21 **00 01**
	1879	+
	1880	+Set DISMACANS=1
	1881	+)))
	1882	+
1762	1762	==== 3.4.2.25 Copy downlink to uplink ====
1763	1763
	1885	+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.
1764	1764
1765	1765	* (% style="color:#037691" %)**AT Command**(%%)**:**
1766	1766
...	...	@@ -1773,8 +1773,22 @@
1773	1773
1774	1774	For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1775	1775
	1898	+(% border="2" style="width:500px" %)
	1899	+|(% style="width:122px" %)**Command**|(% style="width:376px" %)(((
	1900	+AT+RPL=5
1776	1776
	1902	+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.
	1903	+)))
	1904	+|(% style="width:122px" %)**Example**|(% style="width:376px" %)(((
	1905	+Downlink:
1777	1777
	1907	+01 00 02 58
	1908	+
	1909	+Uplink:
	1910	+
	1911	+01 01 00 02 58
	1912	+)))
	1913	+
1778	1778	[[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"]]
1779	1779
1780	1780	For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
...	...	@@ -1781,14 +1781,16 @@
1781	1781
1782	1782
1783	1783
1784		-==== 3.4.2.26 Query version number and frequency band 、TDC ====
	1920	+==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
1785	1785
	1922	+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.
1786	1786
1787	1787	* (((
1788	1788	(% style="color:#037691" %)**Downlink Payload**(%%)**:**
1789	1789
1790		-(% style="color:blue" %)**26 01  ** (%%) ~/~/  Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
	1927	+(% 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.
1791	1791
	1929	+
1792	1792
1793	1793	)))
1794	1794
...	...	@@ -1818,6 +1818,8 @@
1818	1818
1819	1819	=== 3.5.2 Configuring ThingsEye.io ===
1820	1820
	1959	+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.
	1960	+
1821	1821	* Login to your [[ThingsEye.io >>https://thingseye.io]]account.
1822	1822	* Under the **Integrations center**, click **Integrations**.
1823	1823	* Click the **Add integration** button (the button with the **+** symbol).
...	...	@@ -1866,7 +1866,7 @@
1866	1866
1867	1867	* Choose **Region** from the **Host type**.
1868	1868	* 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/...).
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).
	2009	+* 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**).
1870	1870	* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
1871	1871
1872	1872	[[image:message-1.png]]
...	...	@@ -1877,7 +1877,7 @@
1877	1877	[[image:thingseye-io-step-5.png||height="625" width="1000"]]
1878	1878
1879	1879
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.
	2020	+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.
1881	1881
1882	1882
1883	1883	[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
...	...	@@ -1893,7 +1893,7 @@
1893	1893	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.
1894	1894
1895	1895	{{info}}
1896		-See also ThingsEye documentation.
	2036	+See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
1897	1897	{{/info}}
1898	1898
1899	1899	==== **3.5.2.2 Viewing events** ====
...	...	@@ -1906,7 +1906,7 @@
1906	1906	[[image:thingseye-events.png||height="686" width="1000"]]
1907	1907
1908	1908
1909		-* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
	2049	+* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
1910	1910
1911	1911	[[image:thingseye-json.png||width="1000"]]
1912	1912
...	...	@@ -1916,6 +1916,11 @@
1916	1916	If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
1917	1917
1918	1918
	2059	+==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
	2060	+
	2061	+This will be added soon.
	2062	+
	2063	+
1919	1919	== 3.6 Interface Details ==
1920	1920
1921	1921	=== 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===

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

lorawan-nw.jpg

Author

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

Size

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

Content