Wiki source code of LT-22222-LA -- LoRa I/O Controller User Manual

Version 47.1 by Kilight Cao on 2025/07/03 14:42

version	line-number	content
2.3	1	[[image:image-20220523163353-1.jpeg\|\|data-xwiki-image-style-alignment="center" height="604" width="500"]]
	2
	3
	4
	5
	6
	7
	8
	9	Table of Contents:
	10
	11	{{toc/}}
	12
	13
	14
	15
	16
	17	= 1. Introduction =
	18
	19	== 1.1 What is the LT-22222-LA I/O Controller? ==
	20
	21
	22	(((
	23	(((
	24	The Dragino (% style="color:blue" %)LT-22222-LA 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.
	25
	26	The LT-22222-LA 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.
	27	)))
	28	)))
	29
	30	(((
	31	With the LT-22222-LA I/O Controller, users can transmit data over ultra-long distances with low power consumption using LoRa, a spread-spectrum modulation technique derived from chirp spread spectrum (CSS) technology that operates on license-free ISM bands.
	32	)))
	33
	34	(((
	35	You can connect the LT-22222-LA I/O Controller to a LoRaWAN network service provider in several ways:
	36
	37	* 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-LA I/O controller with it.
	38	* 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-LA I/O controller with this network.
	39	* Setup your own private LoRaWAN network.
	40	)))
	41
	42	(((
	43
	44
2.4	45	The network diagram below illustrates how the LT-22222-LA communicates with a typical LoRaWAN network.
2.3	46	)))
	47
	48
	49
	50	== 1.2 Specifications ==
	51
	52
2.5	53	(% style="color:#037691" %)Hardware System:
2.3	54
	55	* Power Consumption:
	56	** Idle: 4mA@12V
	57	** 20dB Transmit: 34mA@12V
	58	* Operating Temperature: -40 ~~ 85 Degrees, No Dew
	59
	60	(% style="color:#037691" %)Interface for Model: LT22222-L:
	61
	62	* 2 x Digital dual direction Input (Detect High/Low signal, Max: 50V, or 220V with optional external resistor)
	63	* 2 x Digital Output (NPN output. Max pull-up voltage 36V,450mA)
	64	* 2 x Relay Output (5A@250VAC / 30VDC)
	65	* 2 x 0~~20mA Analog Input (res:0.01mA)
	66	* 2 x 0~~30V Analog Input (res:0.01V)
	67	* Power Input 7~~ 24V DC.
	68
	69	(% style="color:#037691" %)LoRa Spec:
	70
	71	* Frequency Range:
	72	** Band 1 (HF): 862 ~~ 1020 MHz
	73	** Band 2 (LF): 410 ~~ 528 MHz
	74	* 168 dB maximum link budget.
	75	* +20 dBm - 100 mW constant RF output vs.
	76	* +14 dBm high-efficiency PA.
	77	* Programmable bit rate up to 300 kbps.
	78	* High sensitivity: down to -148 dBm.
	79	* Bullet-proof front end: IIP3 = -12.5 dBm.
	80	* Excellent blocking immunity.
	81	* Low RX current of 10.3 mA, 200 nA register retention.
	82	* Fully integrated synthesizer with a resolution of 61 Hz.
	83	* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
	84	* Built-in bit synchronizer for clock recovery.
	85	* Preamble detection.
	86	* 127 dB Dynamic Range RSSI.
	87	* Automatic RF Sense and CAD with ultra-fast AFC.
	88	* Packet engine up to 256 bytes with CRC.
	89
	90	== 1.3 Features ==
	91
	92
	93	* LoRaWAN Class A & Class C modes
	94	* Optional Customized LoRa Protocol
	95	* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
	96	* AT Commands to change parameters
	97	* Remotely configure parameters via LoRaWAN Downlink
	98	* Firmware upgradable via program port
	99	* Counting
	100
	101	== 1.4 Applications ==
	102
	103
	104	* Smart buildings & home automation
	105	* Logistics and supply chain management
	106	* Smart metering
	107	* Smart agriculture
	108	* Smart cities
	109	* Smart factory
	110
	111	== 1.5 Hardware Variants ==
	112
	113
	114	(% border="1" cellspacing="3" style="width:510px" %)
	115	\|(% style="background-color:#4f81bd; color:white; width:94px" %)Model\|(% style="background-color:#4f81bd; color:white; width:172px" %)Photo\|(% style="background-color:#4f81bd; color:white; width:244px" %)Description
	116	\|(% style="width:94px" %)LT-33222-L\|(% style="width:172px" %)(((
2.6	117
2.3	118	)))\|(% style="width:256px" %)(((
	119	* 3 x Digital Input (Bi-direction)
	120	* 3 x Digital Output
	121	* 2 x Relay Output (5A@250VAC / 30VDC)
	122	* 2 x 0~~20mA Analog Input (res:0.01mA)
	123	* 2 x 0~~30V Analog Input (res:0.01v)
	124	* 1 x Counting Port
	125	)))
	126
	127	= 2. Assembling the device =
	128
	129	== 2.1 Connecting the antenna ==
	130
	131
	132	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.
	133
	134	{{warning}}
	135	Warning! Do not power on the device without connecting the antenna.
	136	{{/warning}}
	137
	138
	139	== 2.2 Terminals ==
	140
	141
	142	The LT-22222-L has two screw terminal blocks. The upper screw terminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals.
	143
	144	Upper screw terminal block (from left to right):
	145
	146	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:381px" %)
	147	\|=(% style="width: 139px;background-color:#4f81bd;color:white" %)Screw Terminal\|=(% style="width: 242px;background-color:#4f81bd;color:white" %)Function
	148	\|(% style="width:139px" %)GND\|(% style="width:242px" %)Ground
	149	\|(% style="width:139px" %)VIN\|(% style="width:242px" %)Input Voltage
	150	\|(% style="width:139px" %)AVI2\|(% style="width:242px" %)Analog Voltage Input Terminal 2
	151	\|(% style="width:139px" %)AVI1\|(% style="width:242px" %)Analog Voltage Input Terminal 1
	152	\|(% style="width:139px" %)ACI2\|(% style="width:242px" %)Analog Current Input Terminal 2
	153	\|(% style="width:139px" %)ACI1\|(% style="width:242px" %)Analog Current Input Terminal 1
	154
	155	Lower screw terminal block (from left to right):
	156
	157	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:253px" %)
	158	\|=(% style="width: 125px;background-color:#4f81bd;color:white" %)Screw Terminal\|=(% style="width: 128px;background-color:#4f81bd;color:white" %)Function
	159	\|(% style="width:125px" %)RO1-2\|(% style="width:128px" %)Relay Output 1
	160	\|(% style="width:125px" %)RO1-1\|(% style="width:128px" %)Relay Output 1
	161	\|(% style="width:125px" %)RO2-2\|(% style="width:128px" %)Relay Output 2
	162	\|(% style="width:125px" %)RO2-1\|(% style="width:128px" %)Relay Output 2
	163	\|(% style="width:125px" %)DI2+\|(% style="width:128px" %)Digital Input 2
	164	\|(% style="width:125px" %)DI2-\|(% style="width:128px" %)Digital Input 2
	165	\|(% style="width:125px" %)DI1+\|(% style="width:128px" %)Digital Input 1
	166	\|(% style="width:125px" %)DI1-\|(% style="width:128px" %)Digital Input 1
	167	\|(% style="width:125px" %)DO2\|(% style="width:128px" %)Digital Output 2
	168	\|(% style="width:125px" %)DO1\|(% style="width:128px" %)Digital Output 1
	169
	170	== 2.3 Connecting LT-22222-L to a Power Source ==
	171
	172
	173	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
	175	{{warning}}
	176	We recommend that you power on the LT-22222-L after adding its registration information to the LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.
	177	{{/warning}}
	178
	179
	180
	181
	182	= 3. Registering LT-22222-L with a LoRaWAN Network Server =
	183
	184
	185	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.
	186
	187
	188	== 3.1 Prerequisites ==
	189
	190
	191	The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey which allows you to register it with a LoRaWAN network. This 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
	193	{{info}}
	194	If you are unable to set the provided root key and other identifiers in the network server, you must generate new keys and identifiers with the network server and configure the device with them using AT commands.
	195	{{/info}}
	196
	197	The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
	198
	199
	200	== 3.2 The Things Stack ==
	201
	202
	203	This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
	204
	205	{{info}}
	206	The Things Stack Sandbox was formally called The Things Stack Community Edition.
	207	{{/info}}
	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\|\|height="374" width="1400"]]
	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.1 Setting up ===
	221
	222
	223	* Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet.
	224	* Log in to your The Things Stack Sandbox account.
	225	* Create an application with The Things Stack if you do not have one yet (E.g., dragino-docs).
	226	* Go to your application's page and click on the End devices in the left menu.
	227	* On the End devices page, click on + Register end device. Two registration options are available:
	228
	229	==== 3.2.1.1 Using the LoRaWAN Device Repository ====
	230
	231
	232	* On the Register end device page:
	233	Select the option Select the end device in the LoRaWAN Device Repository under Input method**.
	234	Select the End device brand, Model, Hardware version, Firmware version, and Profile (Region)** from the respective dropdown lists.
	235	* End device brand**: Dragino Technology Co., Limited
	236	* Model**: LT22222-L I/O Controller
	237	* Hardware ver**: Unknown
	238	* Firmware ver**: 1.6.0
	239	* Profile (Region)**: Select the region that matches your device.
	240	Select the Frequency plan that matches your device from the Frequency plan** dropdown list.
	241
	242
	243
2.6	244
2.3	245	* Register end device page continued...
	246	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'.
	247	In the DevEUI field, enter the DevEUI**.
	248	In the AppKey field, enter the AppKey.**
	249	In the End device ID** field, enter a unique name for your LT-22222-L within this application.
	250	Under After registration, select the View registered end device** option.
	251	Click Register end device** button.
	252
	253
	254
2.7	255
2.3	256	* You will be navigated to the Device overview page.
	257
	258
	259
2.7	260
2.3	261	==== 3.2.1.2 Adding device manually ====
	262
	263
	264	* On the Register end device page:
	265	Select the option Enter end device specifies manually under Input method**.
	266	Select the Frequency plan that matches your device from the Frequency plan** dropdown list.
	267	Select the LoRaWAN version as LoRaWAN Specification 1.0.3**
	268	Select the Regional Parameters version as RP001 Regional Parameters 1.0.3 revision A**
	269	Click Show advanced activation, LoRaWAN class and cluster settings** link to expand the hidden section.
	270	Select the option Over the air activation (OTAA) under the Activation mode.**
	271	Select Class C (Continuous) from the Additional LoRaWAN class capabilities** dropdown list.
	272
	273
	274
2.7	275
2.3	276	* Register end device page continued...
	277	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**//'
	278	In the DevEUI field, enter the DevEUI**.
	279	In the AppKey field, enter the AppKey**.
	280	In the End device ID** field, enter a unique name for your LT-22222-N within this application.
	281	Under After registration, select the View registered end device** option.
	282	Click the Register end device** button.
	283
	284	[[image:lt-22222-l-manually-p2.png]]
	285
	286
	287	You will be navigated to the Device overview page.
	288
	289
	290	[[image:lt-22222-device-overview.png]]
	291
	292
	293	=== 3.2.2 Joining ===
	294
	295
	296	On the end device's page (in this case, lt-22222-l), click on Live data tab. The Live data panel for your device will display. Initially, it is blank.
	297
	298	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.
	299
	300
	301	[[image:lt-22222-l-joining.png]]
	302
	303
	304	=== 3.2.3 Uplinks ===
	305
	306
	307	After successfully joining, the device will send its first uplink data message to The Things Stack application it belongs to (in this example, it is 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.
	308
	309	Click on one of the Forward uplink data messages to see its payload content. The payload content is encapsulated within the decode_payload {} JSON object.
	310
	311	[[image:lt-22222-ul-payload-decoded.png]]
	312
	313
	314	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.
	315
	316	{{info}}
	317	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.
	318	{{/info}}
	319
	320	[[image:lt-22222-ul-payload-fmt.png]]
	321
	322
	323	We have written a payload formatter that resolves some decoding issues present in The Things Stack Device Repository payload formatter. You can add it under the Custom JavaScript formatter. It can be found [[here>>https://github.com/dragino/dragino-end-node-decoder/blob/main/LT22222-L/v1.6_decoder_ttn%20.txt]]:
	324
	325	(% class="wikigeneratedid" %)
	326	[[image:lt-22222-l-js-custom-payload-formatter.png]]
	327
	328
	329	=== 3.2.4 Downlinks ===
	330
	331
	332	When the LT-22222-L receives a downlink message from the LoRaWAN Network Server, the RX LED turns on for 1 second.
	333
	334
	335	== 3.3 Working Modes and Uplink Payload formats ==
	336
	337
	338	The LT-22222-L has 5 working modes. It also has an interrupt/trigger mode for different types of applications that can be used together with any working mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands.
	339
	340	* (% style="color:blue" %)MOD1(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO
	341
	342	* (% style="color:blue" %)MOD2(%%): Double DI Counting + DO + RO
	343
	344	* (% style="color:blue" %)MOD3(%%): Single DI Counting + 2 x ACI + DO + RO
	345
	346	* (% style="color:blue" %)MOD4(%%): Single DI Counting + 1 x Voltage Counting + DO + RO
	347
	348	* (% style="color:blue" %)MOD5(%%): Single DI Counting + 2 x AVI + 1 x ACI + DO + RO
	349
	350	* (% style="color:blue" %)ADDMOD6(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5
	351
	352	The uplink messages are sent over LoRaWAN FPort=2. By default, an uplink message is sent every 10 minutes.
	353
	354
	355	=== 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
	356
	357
	358	(((
	359	This is the default mode.
	360
	361	The uplink payload is 11 bytes long.
	362	(% wfd-invisible="true" style="display:none" %)
	363
	364	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
	365	\|(% style="background-color:#4f81bd; color:white" %)Size(bytes)\|(% style="background-color:#4f81bd; color:white" %)2\|(% style="background-color:#4f81bd; color:white" %)2\|(% style="background-color:#4f81bd; color:white" %)2\|(% style="background-color:#4f81bd; color:white" %)2\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)1
	366	\|Value\|(((
	367	AVI1 voltage
	368	)))\|(((
	369	AVI2 voltage
	370	)))\|(((
	371	ACI1 Current
	372	)))\|(((
	373	ACI2 Current
	374	)))\|DIDORO*\|(((
	375	Reserve
	376	)))\|MOD
	377	)))
	378
	379	(((
	380	(% style="color:#4f81bd" %)* DIDORO(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, and its size is1 byte long as shown below.
	381
	382	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
	383	\|bit 7\|bit 6\|bit 5\|bit 4\|bit 3\|bit 2\|bit 1\|bit 0
	384	\|RO1\|RO2\|--DI3--\|DI2\|DI1\|--DO3--\|DO2\|DO1
	385	)))
	386
	387	* RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN.
	388	* DI is for digital input. DIx=1: HIGH or FLOATING, DIx=0: LOW.
	389	* DO is for reverse digital output. DOx=1: LOW, DOx=0: HIGH or FLOATING.
	390
	391	(% style="color:red" %)Note: DI3 and DO3 bits are not valid for LT-22222-L
	392
	393	For example, if the payload is: [[image:image-20220523175847-2.png]]
	394
	395
	396	The interface values can be calculated as follows:
	397
	398	AVI1 channel voltage is 0x04AB/1000=1195(DEC)/1000=1.195V
	399
	400	AVI2 channel voltage is 0x04AC/1000=1.196V
	401
	402	ACI1 channel current is 0x1310/1000=4.880mA
	403
	404	ACI2 channel current is 0x1300/1000=4.864mA
	405
	406	The last byte 0xAA= 10101010(b) means,
	407
	408	* [1] The RO1 relay channel is CLOSED, and the RO1 LED is ON.
	409	* [0] The RO2 relay channel is OPEN, and the RO2 LED is OFF.
	410	* [1] DI3 - not used for LT-22222-L.
	411	* [0] DI2 channel input is LOW, and the DI2 LED is OFF.
	412	* [1] DI1 channel input state:
	413	** DI1 is FLOATING when no sensor is connected between DI1+ and DI1-.
	414	** DI1 is HIGH when a sensor is connected between DI1- and DI1+ and the sensor is ACTIVE.
	415	** DI1 LED is ON in both cases.
	416	* [0] DO3 - not used for LT-22222-L.
	417	* [1] DO2 channel output is LOW, and the DO2 LED is ON.
	418	* [0] DO1 channel output state:
	419	** DO1 is FLOATING when there is no load between DO1 and V+.
	420	** DO1 is HIGH and there is a load between DO1 and V+.
	421	** DO1 LED is OFF in both cases.
	422
	423	Reserve = 0
	424
	425	MOD = 1
	426
	427
	428	=== 3.3.2 AT+MOD~=2, (Double DI Counting) ===
	429
	430
	431	(((
	432	For LT-22222-L: In this mode, DI1 and DI2 are used as counting pins.
	433	)))
	434
	435	(((
	436	The uplink payload is 11 bytes long.
	437
	438	(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
	439	The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
	440	It starts counting again when it reaches the maximum value.**
	441
	442	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
	443	\|(% style="background-color:#4f81bd; color:white" %)Size(bytes)\|(% style="background-color:#4f81bd; color:white" %)4\|(% style="background-color:#4f81bd; color:white" %)4\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)1
	444	\|Value\|COUNT1\|COUNT2 \|DIDORO*\|(((
	445	Reserve
	446	)))\|MOD
	447	)))
	448
	449	(((
	450	(% style="color:#4f81bd" %)*DIDORO(%%) is a combination of RO1, RO2, FIRST, Reserve, Reserve, DO3, DO2 and DO1, and its size is 1 byte long as shown below.
	451
	452	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
	453	\|bit 7\|bit 6\|bit 5\|bit 4\|bit 3\|bit 2\|bit 1\|bit 0
	454	\|RO1\|RO2\|FIRST\|Reserve\|Reserve\|--DO3--\|DO2\|DO1
	455
	456	* RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN.
	457	)))
	458
	459	* FIRST: Indicates that this is the first packet after joining the network.
	460	* DO is for reverse digital output. DOx=1: LOW, DOx=0: HIGH or FLOATING.
	461
	462	(((
	463	(% style="color:red" %)Note: DO3 bit is not valid for LT-22222-L
	464
	465
	466	)))
	467
	468	(((
	469	To activate this mode, run the following AT commands:
	470	)))
	471
	472	(((
	473	(% class="box infomessage" %)
	474	(((
	475	AT+MOD=2
	476
	477	ATZ
	478	)))
	479	)))
	480
	481	(((
	482
	483
	484	(% style="color:#4f81bd" %)AT Commands for counting:
	485	)))
	486
	487	(((
	488	For LT22222-L:
	489
	490	(% style="color:blue" %)AT+TRIG1=0,100(%%) (sets the DI1 port to trigger on a LOW level. The valid signal duration is 100ms)
	491
	492	(% style="color:blue" %)AT+TRIG1=1,100(%%) (sets the DI1 port to trigger on a HIGH level. The valid signal duration is 100ms)
	493
	494	(% style="color:blue" %)AT+TRIG2=0,100(%%) (sets the DI2 port to trigger on a LOW level. The valid signal duration is 100ms)
	495
	496	(% style="color:blue" %)AT+TRIG2=1,100(%%) (sets the DI2 port to trigger on a HIGH level. The valid signal duration is 100ms)
	497
	498	(% style="color:blue" %)AT+SETCNT=1,60(%%) (sets the COUNT1 value to 60)
	499
	500	(% style="color:blue" %)AT+SETCNT=2,60 (%%)(sets the COUNT2 value to 60)
	501	)))
	502
	503
	504
	505
	506	=== 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI ===
	507
	508
	509	(% style="color:red" %)**Note: The maximum count depends on the bytes it is.
	510	The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
	511	It starts counting again when it reaches the maximum value.**
	512
	513	LT22222-L: In this mode, the DI1 is used as a counting pin.
	514
	515	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
	516	\|(% style="background-color:#4f81bd; color:white" %)Size(bytes)\|(% style="background-color:#4f81bd; color:white" %)4\|(% style="background-color:#4f81bd; color:white" %)2\|(% style="background-color:#4f81bd; color:white" %)2\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)1
	517	\|Value\|COUNT1\|(((
	518	ACI1 Current
	519	)))\|(((
	520	ACI2 Current
	521	)))\|DIDORO*\|Reserve\|MOD
	522
	523	(((
	524	(% style="color:#4f81bd" %)*DIDORO(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
	525
	526	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
	527	\|bit 7\|bit 6\|bit 5\|bit 4\|bit 3\|bit 2\|bit 1\|bit 0
	528	\|RO1\|RO2\|FIRST\|Reserve\|Reserve\|--DO3--\|DO2\|DO1
	529	)))
	530
	531	* RO is for the relay. ROx=1: closed, ROx=0 always open.
	532	* FIRST: Indicates that this is the first packet after joining the network.
	533	* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
	534
	535	(((
	536	(% style="color:red" %)Note: DO3 bit is not valid for LT-22222-L.
	537	)))
	538
	539
	540
	541
	542	(((
	543	To activate this mode, run the following AT commands:
	544	)))
	545
	546	(((
	547	(% class="box infomessage" %)
	548	(((
	549	AT+MOD=3
	550
	551	ATZ
	552	)))
	553	)))
	554
	555	(((
	556	AT Commands for counting:
	557
	558	The AT Commands for counting are similar to the [[MOD2 Counting Command>>\|\|anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
	559	)))
	560
	561
	562	=== 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
	563
	564
	565	(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
	566	The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
	567	It starts counting again when it reaches the maximum value.**
	568
	569
	570	(((
	571	LT22222-L: In this mode, the DI1 is used as a counting pin.
	572	)))
	573
	574	(((
	575	The AVI1 is also used for counting. It monitors the voltage and checks it every 60 seconds. If the voltage is higher or lower than VOLMAX mV, the AVI1 count increases by 1, allowing AVI1 counting to be used to measure a machine's working hours.
	576
	577	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
	578	\|(% style="background-color:#4f81bd; color:white" %)Size(bytes)\|(% style="background-color:#4f81bd; color:white" %)4\|(% style="background-color:#4f81bd; color:white" %)4\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)1
	579	\|Value\|COUNT1\|AVI1 Counting\|DIDORO*\|(((
	580	Reserve
	581	)))\|MOD
	582	)))
	583
	584	(((
	585	(% style="color:#4f81bd" %)DIDORO (%%)is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
	586
	587	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
	588	\|bit 7\|bit 6\|bit 5\|bit 4\|bit 3\|bit 2\|bit 1\|bit 0
	589	\|RO1\|RO2\|FIRST\|Reserve\|Reserve\|--DO3--\|DO2\|DO1
	590	)))
	591
	592	* RO is for the relay. ROx=1: closed, ROx=0 always open.
	593	* FIRST: Indicates that this is the first packet after joining the network.
	594	* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
	595
	596	(((
	597	(% style="color:red" %)Note: DO3 bit is not valid for LT-22222-L.
	598
	599
	600	)))
	601
	602	(((
	603	To activate this mode, run the following AT commands:
	604	)))
	605
	606	(((
	607	(% class="box infomessage" %)
	608	(((
	609	AT+MOD=4
	610
	611	ATZ
	612	)))
	613	)))
	614
	615	(((
	616	AT Commands for counting are similar to the [[MOD2 Counting Command>>\|\|anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
	617	)))
	618
	619	(((
	620	In addition to that, below are the commands for AVI1 Counting:
	621
	622	(% style="color:blue" %)AT+SETCNT=3,60 (%%)(Sets AVI1 Count to 60)
	623
	624	(% style="color:blue" %)AT+VOLMAX=20000 (%%)(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), the counter increases by 1)
	625
	626	(% style="color:blue" %)AT+VOLMAX=20000,0 (%%)(If the AVI1 voltage is lower than VOLMAX (20000mV =20V), counter increases by 1)
	627
	628	(% style="color:blue" %)AT+VOLMAX=20000,1 (%%)(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), counter increases by 1)
	629	)))
	630
	631
	632
	633
	634	=== 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI ===
	635
	636
	637	(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
	638	The maximum count for four bytes is FFFF (hex) = 65535 (dec).
	639	It starts counting again when it reaches the maximum value.**
	640
	641
	642	LT22222-L: In this mode, the DI1 is used as a counting pin.
	643
	644	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
	645	\|(% style="background-color:#4f81bd; color:white" %)Size(bytes)\|(% style="background-color:#4f81bd; color:white" %)2\|(% style="background-color:#4f81bd; color:white" %)2\|(% style="background-color:#4f81bd; color:white" %)2\|(% style="background-color:#4f81bd; color:white" %)2\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)1
	646	\|Value\|(((
	647	AVI1 voltage
	648	)))\|(((
	649	AVI2 voltage
	650	)))\|(((
	651	ACI1 Current
	652	)))\|COUNT1\|DIDORO*\|(((
	653	Reserve
	654	)))\|MOD
	655
	656	(((
	657	(% style="color:#4f81bd" %)DIDORO(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
	658
	659	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
	660	\|bit 7\|bit 6\|bit 5\|bit 4\|bit 3\|bit 2\|bit 1\|bit 0
	661	\|RO1\|RO2\|FIRST\|Reserve\|Reserve\|DO3\|DO2\|DO1
	662	)))
	663
	664	* RO is for the relay. ROx=1: closed, ROx=0 always open.
	665	* FIRST: Indicates that this is the first packet after joining the network.
	666	* (((
	667	DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
	668	)))
	669
	670	(((
	671	(% style="color:red" %)Note: DO3 bit is not valid for LT-22222-L.
	672	)))
	673
	674	(((
	675	To activate this mode, run the following AT commands:
	676	)))
	677
	678	(((
	679	(% class="box infomessage" %)
	680	(((
	681	AT+MOD=5
	682
	683	ATZ
	684	)))
	685	)))
	686
	687	(((
	688	Other AT Commands for counting are similar to the [[MOD2 Counting Command>>\|\|anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
	689	)))
	690
	691
	692
	693
	694	=== 3.3.6 AT+ADDMOD~=6 (Trigger Mode, Optional) ===
	695
	696
	697	(% style="color:#4f81bd" %)This mode is optional and intended for trigger purposes. It can operate __alongside__ with other modes.
	698
	699	For example, if you configure the following commands:
	700
	701	* AT+MOD=1 ~-~-> Sets the default working mode
	702	* AT+ADDMOD6=1 ~-~-> Enables trigger mode
	703
	704	The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. It will send uplink packets in two cases:
	705
	706	1. Periodic uplink: Based on TDC time. The payload is the same as in normal mode (MOD=1 as set above). These are (% style="color:#4f81bd" %)unconfirmed(%%) uplinks.
	707	1. (((
	708	Trigger uplink: sent when a trigger condition is met. In this case, LT will send two packets
	709
	710	* The first uplink uses the payload specified in trigger mode (MOD=6).
	711	* The second packet uses the normal mode payload (MOD=1 as set above). Both are (% style="color:#4f81bd" %)confirmed uplinks.
	712	)))
	713
	714	(% style="color:#037691" %)AT Commands to set Trigger Conditions:
	715
	716	(% style="color:#4f81bd" %)Trigger based on voltage:
	717
	718	Format: AT+AVLIM=<AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH>
	719
	720
	721	Example:
	722
	723	AT+AVLIM=3000,6000,0,2000 (triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V)
	724
	725	AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage is lower than 5V. Use 0 for parameters that are not in use)
	726
	727
	728	(% style="color:#4f81bd" %)Trigger based on current:
	729
	730	Format: AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH>
	731
	732
	733	Example:
	734
	735	AT+ACLIM=10000,15000,0,0 (triggers an uplink if AC1 current is lower than 10mA or higher than 15mA)
	736
	737
	738	(% style="color:#4f81bd" %)Trigger based on DI status:
	739
	740	DI status triggers Flag.
	741
	742	Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >
	743
	744
	745	Example:
	746
	747	AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
	748
	749
	750	(% style="color:#037691" %)LoRaWAN Downlink Commands for Setting the Trigger Conditions:
	751
	752	Type Code: 0xAA. Downlink command same as AT Command AT+AVLIM, AT+ACLIM
	753
	754	Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
	755
	756	AA: Type Code for this downlink Command:
	757
	758	xx: 0: Limit for AV1 and AV2; 1: limit for AC1 and AC2; 2: DI1and DI2 trigger enable/disable.
	759
	760	yy1 yy1: AC1 or AV1 LOW limit or DI1/DI2 trigger status.
	761
	762	yy2 yy2: AC1 or AV1 HIGH limit.
	763
	764	yy3 yy3: AC2 or AV2 LOW limit.
	765
	766	Yy4 yy4: AC2 or AV2 HIGH limit.
	767
	768
	769	Example 1: AA 00 13 88 00 00 00 00 00 00
	770
	771	Same as AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage is lower than 5V. Use 0s for parameters that are not in use)
	772
	773
	774	Example 2: AA 02 01 00
	775
	776	Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
	777
	778
	779	(% style="color:#4f81bd" %)Trigger Settings Payload Explanation:
	780
	781	MOD6 Payload: a total of 11 bytes
	782
	783	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
	784	\|(% style="background-color:#4f81bd; color:white; width:60px" %)Size(bytes)\|(% style="background-color:#4f81bd; color:white; width:69px" %)1\|(% style="background-color:#4f81bd; color:white; width:69px" %)1\|(% style="background-color:#4f81bd; color:white; width:109px" %)1\|(% style="background-color:#4f81bd; color:white; width:49px" %)6\|(% style="background-color:#4f81bd; color:white; width:109px" %)1\|(% style="background-color:#4f81bd; color:white; width:50px" %)1
	785	\|Value\|(((
	786	TRI_A FLAG
	787	)))\|(((
	788	TRI_A Status
	789	)))\|(((
	790	TRI_DI FLAG+STA
	791	)))\|Reserve\|Enable/Disable MOD6\|(((
	792	MOD(6)
	793	)))
	794
	795	(% style="color:#4f81bd" %)TRI FLAG1(%%) is a combination to show if the trigger is set for this part. Total 1 byte as below.
	796
	797	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
	798	\|bit 7\|bit 6\|bit 5\|bit 4\|bit 3\|bit 2\|bit 1\|bit 0
	799	\|(((
	800	AV1_LOW
	801	)))\|(((
	802	AV1_HIGH
	803	)))\|(((
	804	AV2_LOW
	805	)))\|(((
	806	AV2_HIGH
	807	)))\|(((
	808	AC1_LOW
	809	)))\|(((
	810	AC1_HIGH
	811	)))\|(((
	812	AC2_LOW
	813	)))\|(((
	814	AC2_HIGH
	815	)))
	816
	817	* Each bit shows if the corresponding trigger has been configured.
	818
	819	Example:
	820
	821	10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW.
	822
	823
	824	(% style="color:#4f81bd" %)TRI Status1(%%) is a combination to show which condition is triggered. Total 1 byte as below.
	825
	826	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
	827	\|bit 7\|bit 6\|bit 5\|bit 4\|bit 3\|bit 2\|bit 1\|bit 0
	828	\|(((
	829	AV1_LOW
	830	)))\|(((
	831	AV1_HIGH
	832	)))\|(((
	833	AV2_LOW
	834	)))\|(((
	835	AV2_HIGH
	836	)))\|(((
	837	AC1_LOW
	838	)))\|(((
	839	AC1_HIGH
	840	)))\|(((
	841	AC2_LOW
	842	)))\|(((
	843	AC2_HIGH
	844	)))
	845
	846	* Each bit shows which status has been triggered on this uplink.
	847
	848	Example:
	849
	850	10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low.
	851
	852
	853	(% style="color:#4f81bd" %)TRI_DI FLAG+STA (%%)is a combination to show which condition is triggered. Total 1 byte as below.
	854
	855	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
	856	\|(% style="width:50px" %)bit 7\|(% style="width:50px" %)bit 6\|(% style="width:50px" %)bit 5\|(% style="width:50px" %)bit 4\|(% style="width:90px" %)bit 3\|(% style="width:80px" %)bit 2\|(% style="width:90px" %)bit 1\|(% style="width:95px" %)bit 0
	857	\|(% style="width:49px" %)N/A\|(% style="width:53px" %)N/A\|(% style="width:53px" %)N/A\|(% style="width:55px" %)N/A\|(% style="width:99px" %)DI2_STATUS\|(% style="width:83px" %)DI2_FLAG\|(% style="width:98px" %)DI1_STATUS\|(% style="width:85px" %)DI1_FLAG
	858
	859	* Each bit shows which status has been triggered on this uplink.
	860
	861	Example:
	862
	863	00000111: This means both DI1 and DI2 triggers are enabled, and this packet is triggered by DI1.
	864
	865	00000101: This means both DI1 and DI2 triggers are enabled.
	866
	867
	868	(% style="color:#4f81bd" %)Enable/Disable MOD6 (%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled.
	869
	870	Downlink command to poll/request MOD6 status:
	871
	872	AB 06
	873
	874	When the device receives this command, it will send the MOD6 payload.
	875
	876
	877	=== 3.3.7 Payload Decoder ===
	878
	879	(((
	880
	881
	882	Decoder for TTN/loraserver/ChirpStack: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder/tree/main/LT22222-L]]
	883	)))
	884
	885
	886	== 3.4 Configure LT-22222-L via AT Commands or Downlinks ==
	887
	888
	889	(((
	890	You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
	891	)))
	892
	893	(((
	894	(((
	895	There are two types of commands:
	896	)))
	897	)))
	898
	899	* (% style="color:blue" %)Common commands(%%):
	900
	901	* (% style="color:blue" %)Sensor-related commands(%%):
	902
	903	=== 3.4.1 Common commands ===
	904
	905
	906	(((
	907	These are available for each sensor and include actions such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]s.
	908
	909
	910	)))
	911
	912	=== 3.4.2 Sensor-related commands ===
	913
	914
	915	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.
	916
	917
	918	==== 3.4.2.1 Set Transmit/Uplink Interval ====
	919
	920
	921	Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
	922
	923	(% style="color:#037691" %)AT command
	924
	925	(% border="2" style="width:500px" %)
	926	\|Command\|AT+TDC=<time>
	927	\|Parameters\|time : uplink interval in milliseconds
	928	\|Get\|AT+TDC=?
	929	\|Response\|(((
	930	current uplink interval
	931
	932	OK
	933	)))
	934	\|Set\|AT+TDC=<time>
	935	\|Response\|OK
	936	\|Example\|(((
	937	AT+TDC=30000
	938
	939	Sets the uplink interval to 30 seconds (30000 milliseconds)
	940	)))
	941
	942	(% style="color:#037691" %)Downlink payload
	943
	944	(% border="2" style="width:500px" %)
	945	\|Payload\|(((
	946	<prefix><time>
	947	)))
	948	\|Parameters\|(((
	949	prefix : 0x01
	950
	951	time : uplink interval in seconds, represented by 3 bytes in hexadecimal.
	952	)))
	953	\|Example\|(((
	954	01 00 00 1E
	955
	956	Sets the uplink interval to 30 seconds
	957
	958	Conversion: 30 (dec) = 00 00 1E (hex)
	959
	960	See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30]]
	961
	962	[[image:Screenshot 2024-11-23 at 18.27.11.png]]
	963	)))
	964
	965	==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
	966
	967
	968	Sets the working mode.
	969
	970	(% style="color:#037691" %)AT command
	971
	972	(% border="2" style="width:500px" %)
	973	\|(% style="width:97px" %)Command\|(% style="width:413px" %)AT+MOD=<working_mode>
	974	\|(% style="width:97px" %)Parameters\|(% style="width:413px" %)(((
	975	working_mode :
	976
	977	1 = (Default mode/factory set): 2ACI + 2AVI + DI + DO + RO
	978
	979	2 = Double DI Counting + DO + RO
	980
	981	3 = Single DI Counting + 2 x ACI + DO + RO
	982
	983	4 = Single DI Counting + 1 x Voltage Counting + DO + RO
	984
	985	5 = Single DI Counting + 2 x AVI + 1 x ACI + DO + RO
	986
	987	6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5
	988	)))
	989	\|(% style="width:97px" %)Get\|(% style="width:413px" %)AT+MOD=?
	990	\|(% style="width:97px" %)Response\|(% style="width:413px" %)(((
	991	Current working mode
	992
	993	OK
	994	)))
	995	\|(% style="width:97px" %)Set\|(% style="width:413px" %)AT+MOD=<working_mode>
	996	\|(% style="width:97px" %)Response\|(% style="width:413px" %)(((
	997	Attention:Take effect after ATZ
	998
	999	OK
	1000	)))
	1001	\|(% style="width:97px" %)Example\|(% style="width:413px" %)(((
	1002	AT+MOD=2
	1003
	1004	Sets the device to working mode 2 (Double DI Counting + DO + RO)
	1005	)))
	1006
	1007	(% class="wikigeneratedid" %)
	1008	(% style="color:#037691" %)Downlink payload
	1009
	1010	(% border="2" style="width:500px" %)
	1011	\|(% style="width:98px" %)Payload\|(% style="width:400px" %)<prefix><working_mode>
	1012	\|(% style="width:98px" %)Parameters\|(% style="width:400px" %)(((
	1013	prefix : 0x0A
	1014
	1015	working_mode : Working mode, represented by 1 byte in hexadecimal.
	1016	)))
	1017	\|(% style="width:98px" %)Example\|(% style="width:400px" %)(((
	1018	0A 02
	1019
	1020	Sets the device to working mode 2 (Double DI Counting + DO + RO)
	1021	)))
	1022
	1023	==== 3.4.2.3 Request an uplink from the device ====
	1024
	1025
	1026	Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
	1027
	1028	(% style="color:#037691" %)AT command
	1029
	1030	There is no AT Command available for this feature.
	1031
	1032	(% style="color:#037691" %)Downlink payload
	1033
	1034	(% border="2" style="width:500px" %)
	1035	\|(% style="width:101px" %)Payload\|(% style="width:397px" %)<prefix>FF
	1036	\|(% style="width:101px" %)Parameters\|(% style="width:397px" %)prefix : 0x08
	1037	\|(% style="width:101px" %)Example\|(% style="width:397px" %)(((
	1038	08 FF
	1039
	1040	Requests an uplink from LT-22222-L.
	1041	)))
	1042
	1043	==== 3.4.2.4 Enable/Disable Trigger Mode ====
	1044
	1045
	1046	Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>\|\|anchor="H3.3.6AT2BADDMOD3D628TriggerMode2COptional29"]]).
	1047
	1048	(% style="color:#037691" %)AT Command
	1049
	1050	(% border="2" style="width:500px" %)
	1051	\|(% style="width:95px" %)Command\|(% style="width:403px" %)AT+ADDMOD6=<enable/disable trigger_mode>
	1052	\|(% style="width:95px" %)Response\|(% style="width:403px" %)
	1053	\|(% style="width:95px" %)Parameters\|(% style="width:403px" %)(((
	1054	enable/disable trigger_mode :
	1055
	1056	1 = enable trigger mode
	1057
	1058	0 = disable trigger mode
	1059	)))
	1060	\|(% style="width:95px" %)Example\|(% style="width:403px" %)(((
	1061	AT+ADDMOD6=1
	1062
	1063	Enable trigger mode for the current working mode
	1064	)))
	1065
	1066	(% style="color:#037691" %)Downlink payload
	1067
	1068	(% border="2" style="width:500px" %)
	1069	\|(% style="width:97px" %)Payload\|(% style="width:401px" %)<prefix><enable/disable trigger_mode>
	1070	\|(% style="width:97px" %)Parameters\|(% style="width:401px" %)(((
	1071	prefix : 0x0A 06 (two bytes in hexadecimal)
	1072
	1073	enable/disable trigger_mode : enable (1) or disable (0), represented by 1 byte in hexadecimal.
	1074	)))
	1075	\|(% style="width:97px" %)Example\|(% style="width:401px" %)(((
	1076	0A 06 01
	1077
	1078	Enable trigger mode for the current working mode
	1079	)))
	1080
	1081	==== 3.4.2.5 Request trigger settings ====
	1082
	1083
	1084	Requests the trigger settings.
	1085
	1086	(% style="color:#037691" %)AT Command:
	1087
	1088	There is no AT Command available for this feature.
	1089
	1090	(% style="color:#037691" %)Downlink Payload
	1091
	1092	(% border="2" style="width:500px" %)
	1093	\|(% style="width:95px" %)Payload\|(% style="width:403px" %)<prefix>
	1094	\|(% style="width:95px" %)Parameters\|(% style="width:403px" %)prefix : AB 06 (two bytes in hexadecimal)
	1095	\|(% style="width:95px" %)Example\|(% style="width:403px" %)(((
	1096	AB 06
	1097
	1098	Uplink the trigger settings.
	1099	)))
	1100
	1101	==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ====
	1102
	1103
	1104	Enable or disable DI1/DI2/DI3 as a trigger.
	1105
	1106	(% style="color:#037691" %)AT Command
	1107
	1108	(% border="2" style="width:500px" %)
	1109	\|(% style="width:98px" %)Command\|(% style="width:400px" %)AT+DTRI=<DI1_trigger>,<DI2_trigger>
	1110	\|(% style="width:98px" %)Response\|(% style="width:400px" %)
	1111	\|(% style="width:98px" %)Parameters\|(% style="width:400px" %)(((
	1112	DI1_trigger:
	1113
	1114	1 = enable DI1 trigger
	1115
	1116	0 = disable DI1 trigger
	1117
	1118	DI2 _trigger
	1119
	1120	1 = enable DI2 trigger
	1121
	1122	0 = disable DI2 trigger
	1123	)))
	1124	\|(% style="width:98px" %)Example\|(% style="width:400px" %)(((
	1125	AT+DTRI=1,0
	1126
	1127	Enable DI1 trigger, disable DI2 trigger
	1128	)))
	1129
	1130	(% class="wikigeneratedid" %)
	1131	(% style="color:#037691" %)Downlink Payload
	1132
	1133	(% border="2" style="width:500px" %)
	1134	\|(% style="width:101px" %)Payload\|(% style="width:397px" %)<prefix><DI1_trigger><DI2_trigger>
	1135	\|(% style="width:101px" %)Parameters\|(% style="width:397px" %)(((
	1136	prefix : AA 02 (two bytes in hexadecimal)
	1137
	1138	DI1_trigger:
	1139
	1140	1 = enable DI1 trigger, represented by 1 byte in hexadecimal.
	1141
	1142	0 = disable DI1 trigger, represented by 1 byte in hexadecimal.
	1143
	1144	DI2 _trigger
	1145
	1146	1 = enable DI2 trigger, represented by 1 byte in hexadecimal.
	1147
	1148	0 = disable DI2 trigger, represented by 1 byte in hexadecimal.
	1149	)))
	1150	\|(% style="width:101px" %)Example\|(% style="width:397px" %)(((
	1151	AA 02 01 00
	1152
	1153	Enable DI1 trigger, disable DI2 trigger
	1154	)))
	1155
	1156	==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as a trigger ====
	1157
	1158
	1159	Sets DI1 or DI3 (for LT-33222-L) as a trigger.
	1160
	1161	(% style="color:#037691" %)AT Command
	1162
	1163	(% border="2" style="width:500px" %)
	1164	\|(% style="width:101px" %)Command\|(% style="width:397px" %)AT+TRIG1=<interrupt_mode>,<minimum_signal_duration>
	1165	\|(% style="width:101px" %)Response\|(% style="width:397px" %)
	1166	\|(% style="width:101px" %)Parameters\|(% style="width:397px" %)(((
	1167	interrupt_mode : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
	1168
	1169	minimum_signal_duration : the minimum signal duration required for the DI1 port to recognize a valid trigger.
	1170	)))
	1171	\|(% style="width:101px" %)Example\|(% style="width:397px" %)(((
	1172	AT+TRIG1=1,100
	1173
	1174	Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms.
	1175	)))
	1176
	1177	(% class="wikigeneratedid" %)
	1178	(% style="color:#037691" %)Downlink Payload
	1179
	1180	(% border="2" style="width:500px" %)
	1181	\|(% style="width:101px" %)Payload\|(% style="width:397px" %)<prefix><interrupt_mode><minimum_signal_duration>
	1182	\|(% style="width:101px" %)Parameters\|(% style="width:397px" %)(((
	1183	prefix : 09 01 (hexadecimal)
	1184
	1185	interrupt_mode : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal.
	1186
	1187	minimum_signal_duration : in milliseconds, represented two bytes in hexadecimal.
	1188	)))
	1189	\|(% style="width:101px" %)Example\|(% style="width:397px" %)(((
	1190	09 01 01 00 64
	1191
	1192	Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms.
	1193	)))
	1194
	1195	==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
	1196
	1197
	1198	Sets DI2 as a trigger.
	1199
	1200	(% style="color:#037691" %)AT Command
	1201
	1202	(% border="2" style="width:500px" %)
	1203	\|(% style="width:94px" %)Command\|(% style="width:404px" %)AT+TRIG2=<interrupt_mode>,<minimum_signal_duration>
	1204	\|(% style="width:94px" %)Response\|(% style="width:404px" %)
	1205	\|(% style="width:94px" %)Parameters\|(% style="width:404px" %)(((
	1206	interrupt_mode : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
	1207
	1208	minimum_signal_duration : the minimum signal duration required for the DI1 port to recognize a valid trigger.
	1209	)))
	1210	\|(% style="width:94px" %)Example\|(% style="width:404px" %)(((
	1211	AT+TRIG2=0,100
	1212
	1213	Set the DI1 port to trigger on a falling edge; the valid signal duration is 100 ms.
	1214	)))
	1215
	1216	(% style="color:#037691" %)Downlink Payload
	1217
	1218	(% border="2" style="width:500px" %)
	1219	\|(% style="width:96px" %)Payload\|(% style="width:402px" %)<prefix><interrupt_mode><minimum_signal_duration>
	1220	\|(% style="width:96px" %)Parameters\|(% style="width:402px" %)(((
	1221	prefix : 09 02 (hexadecimal)
	1222
	1223	interrupt_mode : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal.
	1224
	1225	minimum_signal_duration : in milliseconds, represented two bytes in hexadecimal
	1226	)))
	1227	\|(% style="width:96px" %)Example\|(% style="width:402px" %)09 02 00 00 64
	1228
	1229	==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
	1230
	1231
	1232	Sets the current trigger based on the AC port. See also [[trigger mode>>\|\|anchor="H3.3.6AT2BADDMOD3D628TriggerMode2COptional29"]]
	1233
	1234	(% style="color:#037691" %)AT Command
	1235
	1236	(% border="2" style="width:500px" %)
	1237	\|(% style="width:104px" %)Command\|(% style="width:394px" %)(((
	1238	AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH>
	1239	)))
	1240	\|(% style="width:104px" %)Response\|(% style="width:394px" %)
	1241	\|(% style="width:104px" %)Parameters\|(% style="width:394px" %)(((
	1242	AC1_LIMIT_LOW : lower limit of the current to be checked
	1243
	1244	AC1_LIMIT_HIGH : higher limit of the current to be checked
	1245
	1246	AC2_LIMIT_HIGH : lower limit of the current to be checked
	1247
	1248	AC2_LIMIT_LOW : higher limit of the current to be checked
	1249	)))
	1250	\|(% style="width:104px" %)Example\|(% style="width:394px" %)(((
	1251	AT+ACLIM=10000,15000,0,0
	1252
	1253	Triggers an uplink if AC1 current is lower than 10mA or higher than 15mA
	1254	)))
	1255	\|(% style="width:104px" %)Note\|(% style="width:394px" %)See also, [[trigger mode>>\|\|anchor="H3.3.6AT2BADDMOD3D628TriggerMode2COptional29"]]
	1256
	1257	(% style="color:#037691" %)Downlink Payload
	1258
	1259	(% border="2" style="width:500px" %)
	1260	\|(% style="width:104px" %)Payload\|(% style="width:394px" %)<prefix><AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH>
	1261	\|(% style="width:104px" %)Parameters\|(% style="width:394px" %)(((
	1262	prefix : AA 01 (hexadecimal)
	1263
	1264	AC1_LIMIT_LOW : lower limit of the current to be checked, two bytes in hexadecimal
	1265
	1266	AC1_LIMIT_HIGH : higher limit of the current to be checked, two bytes in hexadecimal
	1267
	1268	AC2_LIMIT_HIGH : lower limit of the current to be checked, two bytes in hexadecimal
	1269
	1270	AC2_LIMIT_LOW : higher limit of the current to be checked, two bytes in hexadecimal
	1271	)))
	1272	\|(% style="width:104px" %)Example\|(% style="width:394px" %)(((
	1273	AA 01 27 10 3A 98 00 00 00 00
	1274
	1275	Triggers an uplink if AC1 current is lower than 10mA or higher than 15mA. Set all values to zero for AC2 limits because we are only checking AC1 limits.
	1276	)))
	1277	\|(% style="width:104px" %)Note\|(% style="width:394px" %)See also, [[trigger mode>>\|\|anchor="H3.3.6AT2BADDMOD3D628TriggerMode2COptional29"]]
	1278
	1279	==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
	1280
	1281
	1282	Sets the current trigger based on the AV port. See also [[trigger mode>>\|\|anchor="H3.3.6AT2BADDMOD3D628TriggerMode2COptional29"]]
	1283
	1284	(% style="color:#037691" %)AT Command
	1285
	1286	(% border="2" style="width:500px" %)
	1287	\|(% style="width:104px" %)Command\|(% style="width:387px" %)AT+AVLIM= AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH>
	1288	\|(% style="width:104px" %)Response\|(% style="width:387px" %)
	1289	\|(% style="width:104px" %)Parameters\|(% style="width:387px" %)(((
	1290	AC1_LIMIT_LOW : lower limit of the current to be checked
	1291
	1292	AC1_LIMIT_HIGH : higher limit of the current to be checked
	1293
	1294	AC2_LIMIT_HIGH : lower limit of the current to be checked
	1295
	1296	AC2_LIMIT_LOW : higher limit of the current to be checked
	1297	)))
	1298	\|(% style="width:104px" %)Example\|(% style="width:387px" %)(((
	1299	AT+AVLIM=3000,6000,0,2000
	1300
	1301	Triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V
	1302	)))
	1303	\|(% style="width:104px" %)Note\|(% style="width:387px" %)See also, [[trigger mode>>\|\|anchor="H3.3.6AT2BADDMOD3D628TriggerMode2COptional29"]]
	1304
	1305	(% style="color:#037691" %)Downlink Payload
	1306
	1307	(% border="2" style="width:500px" %)
	1308	\|(% style="width:104px" %)Payload\|(% style="width:394px" %)<prefix><AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH>
	1309	\|(% style="width:104px" %)Parameters\|(% style="width:394px" %)(((
	1310	prefix : AA 00 (hexadecimal)
	1311
	1312	AV1_LIMIT_LOW : lower limit of the voltage to be checked, two bytes in hexadecimal
	1313
	1314	AV1_LIMIT_HIGH : higher limit of the voltage to be checked, two bytes in hexadecimal
	1315
	1316	AV2_LIMIT_HIGH : lower limit of the voltage to be checked, two bytes in hexadecimal
	1317
	1318	AV2_LIMIT_LOW : higher limit of the voltage to be checked, two bytes in hexadecimal
	1319	)))
	1320	\|(% style="width:104px" %)Example\|(% style="width:394px" %)(((
	1321	AA 00 0B B8 17 70 00 00 07 D0
	1322
	1323	Triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V.
	1324	)))
	1325	\|(% style="width:104px" %)Note\|(% style="width:394px" %)See also, [[trigger mode>>\|\|anchor="H3.3.6AT2BADDMOD3D628TriggerMode2COptional29"]]
	1326
	1327	==== 3.4.2.11 Trigger – Set the minimum interval ====
	1328
	1329
	1330	Sets the AV and AC trigger minimum interval. The device won't respond to a second trigger within this set time after the first trigger.
	1331
	1332	(% style="color:#037691" %)AT Command
	1333
	1334	(% border="2" style="width:500px" %)
	1335	\|(% style="width:113px" %)Command\|(% style="width:385px" %)AT+ATDC=<time>
	1336	\|(% style="width:113px" %)Response\|(% style="width:385px" %)
	1337	\|(% style="width:113px" %)Parameters\|(% style="width:385px" %)(((
	1338	time : in minutes
	1339	)))
	1340	\|(% style="width:113px" %)Example\|(% style="width:385px" %)(((
	1341	AT+ATDC=5
	1342
	1343	The device won't respond to the second trigger within 5 minutes after the first trigger.
	1344	)))
	1345	\|(% style="width:113px" %)Note\|(% style="width:385px" %)(% style="color:red" %)The time must be greater than 5 minutes.
	1346
	1347	(% style="color:#037691" %)Downlink Payload
	1348
	1349	(% border="2" style="width:500px" %)
	1350	\|(% style="width:112px" %)Payload\|(% style="width:386px" %)<prefix><time>
	1351	\|(% style="width:112px" %)Parameters\|(% style="width:386px" %)(((
	1352	prefix : AC (hexadecimal)
	1353
	1354	time : in minutes (two bytes in hexadecimal)
	1355	)))
	1356	\|(% style="width:112px" %)Example\|(% style="width:386px" %)(((
	1357	AC 00 05
	1358
	1359	The device won't respond to the second trigger within 5 minutes after the first trigger.
	1360	)))
	1361	\|(% style="width:112px" %)Note\|(% style="width:386px" %)(% style="color:red" %)The time must be greater than 5 minutes.
	1362
	1363	==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
	1364
	1365
	1366	Controls the digital outputs DO1, DO2, and DO3
	1367
	1368	(% style="color:#037691" %)AT Command
	1369
	1370	There is no AT Command to control the Digital Output.
	1371
	1372
	1373	(% style="color:#037691" %)Downlink Payload
	1374
	1375	(% border="2" style="width:500px" %)
	1376	\|(% style="width:115px" %)Payload\|(% style="width:383px" %)<prefix><DO1><DO2><DO3>
	1377	\|(% style="width:115px" %)Parameters\|(% style="width:383px" %)(((
	1378	prefix : 02 (hexadecimal)
	1379
	1380	DOI : 01: Low, 00: High, 11: No action (1 byte in hex)
	1381
	1382	DO2 : 01: Low, 00: High, 11: No action (1 byte in hex)
	1383
	1384	DO3 : 01: Low, 00: High, 11: No action (1 byte in hex)
	1385	)))
	1386	\|(% style="width:115px" %)Examples\|(% style="width:383px" %)(((
	1387	02 01 00 01
	1388
	1389	If there is a load between V+ and DOx, it means DO1 is set to low, DO2 is set to high, and DO3 is set to low.
	1390
	1391	More examples:
	1392
	1393	(((
	1394	01: Low, 00: High, 11: No action
	1395
	1396	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:383px" %)
	1397	\|(% style="background-color:#4f81bd; color:white; width:126px" %)Downlink Code\|(% style="background-color:#4f81bd; color:white; width:85px" %)DO1\|(% style="background-color:#4f81bd; color:white; width:86px" %)DO2\|(% style="background-color:#4f81bd; color:white; width:86px" %)DO3
	1398	\|(% style="width:126px" %)02 01 00 11\|(% style="width:85px" %)Low\|(% style="width:86px" %)High\|(% style="width:86px" %)No Action
	1399	\|(% style="width:126px" %)02 00 11 01\|(% style="width:85px" %)High\|(% style="width:86px" %)No Action\|(% style="width:86px" %)Low
	1400	\|(% style="width:126px" %)02 11 01 00\|(% style="width:85px" %)No Action\|(% style="width:86px" %)Low\|(% style="width:86px" %)High
	1401	)))
	1402
	1403	(((
	1404	(((
	1405	(% style="color:red" %)Note: For the LT-22222-L, there is no DO3; the last byte can have any value.
	1406	)))
	1407
	1408	(((
	1409	(% style="color:red" %)The device will upload a packet if downlink code executes successfully.
	1410	)))
	1411	)))
	1412	)))
	1413
	1414	==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
	1415
	1416
	1417	(% style="color:#037691" %)AT command
	1418
	1419	There is no AT command to control the digital output.
	1420
	1421
	1422	(% style="color:#037691" %)Downlink payload
	1423
	1424	(% border="2" style="width:500px" %)
	1425	\|(% style="width:116px" %)Prefix\|(% style="width:382px" %)0xA9
	1426	\|(% style="width:116px" %)Parameters\|(% style="width:382px" %)(((
	1427	inverter_mode: 1 byte in hex.
	1428
	1429	01: DO pins revert to their original state after the timeout.
	1430	00: DO pins switch to an inverted state after the timeout.
	1431
	1432
	1433	DO1_control_method_and_port_status - 1 byte in hex
	1434
	1435	0x01 : DO1 set to low
	1436
	1437	0x00 : DO1 set to high
	1438
	1439	0x11 : DO1 NO action
	1440
	1441
	1442	DO2_control_method_and_port_status - 1 byte in hex
	1443
	1444	0x01 : DO2 set to low
	1445
	1446	0x00 : DO2 set to high
	1447
	1448	0x11 : DO2 NO action
	1449
	1450
	1451	DO3_control_method_and_port_status - 1 byte in hex
	1452
	1453	0x01 : DO3 set to low
	1454
	1455	0x00 : DO3 set to high
	1456
	1457	0x11 : DO3 NO action
	1458
	1459
	1460	latching_time : 4 bytes in hex
	1461
	1462	(% style="color:red" %)Note:
	1463
	1464	Since firmware v1.6.0, the latch time supports 4 bytes or 2 bytes
	1465
	1466	Before firmware v1.6.0, the latch time only supported 2 bytes.
	1467
	1468	(% style="color:red" %)The device will uplink a packet if the downlink code executes successfully.
	1469	)))
	1470	\|(% style="width:116px" %)Payload format\|(% style="width:382px" %)<prefix><inverter_mode><DO1_control_method_and_port_status><DO2_control_method_and_port_status><DO2_control_method_and_port_status><latching_time>
	1471	\|(% style="width:116px" %)Example\|(% style="width:382px" %)(((
	1472	A9 01 01 01 01 07 D0
	1473
	1474	DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state.
	1475
	1476
	1477	A9 01 00 01 11 07 D0
	1478
	1479	DO1 pin is set to high, DO2 pin is set to low, and DO3 pin takes no action. This lasts for 2 seconds and then reverts to the original state.
	1480
	1481
	1482	A9 00 00 00 00 07 D0
	1483
	1484	DO1 pin, DO2 pin, and DO3 pin will be set to high, last for 2 seconds, and then all change to low.
	1485
	1486
	1487	A9 00 11 01 00 07 D0
	1488
	1489	DO1 pin takes no action, DO2 pin is set to low, and DO3 pin is set to high. This lasts for 2 seconds, after which the DO1 pin takes no action, the DO2 pin is set to high, and the DO3 pin is set to low.
	1490	)))
	1491
	1492	==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
	1493
	1494
	1495	(% style="color:#037691" %)AT Command:
	1496
	1497	There is no AT Command to control the Relay Output.
	1498
	1499
	1500	(% style="color:#037691" %)Downlink Payload
	1501
	1502	(% border="2" style="width:500px" %)
	1503	\|(% style="width:113px" %)Prefix\|(% style="width:384px" %)0x03
	1504	\|(% style="width:113px" %)Parameters\|(% style="width:384px" %)(((
	1505	RO1_status : 1 byte in hex
	1506
	1507	00: Open
	1508
	1509	01: Close
	1510
	1511	11: No action
	1512
	1513
	1514	RO2_status : 1 byte in hex
	1515
	1516	00: Open
	1517
	1518	01: Close
	1519
	1520	11: No action
	1521	)))
	1522	\|(% style="width:113px" %)Payload format\|(% style="width:384px" %)<prefix><RO1_status><RO2_status>
	1523	\|(% style="width:113px" %)Example\|(% style="width:384px" %)(((
	1524	(% border="2" %)
	1525	\|=Payload\|=RO1\|=RO2
	1526	\|03 00 11\|Open\|No action
	1527	\|03 01 11\|Close\|No action
	1528	\|03 11 00\|No action\|Open
	1529	\|03 11 01\|No action\|Close
	1530	\|03 00 00\|Open\|Open
	1531	\|03 01 01\|Close\|Close
	1532	\|03 01 00\|Close\|Open
	1533	\|03 00 01\|Open\|Close
	1534
	1535	(% style="color:red" %)The device will transmit an uplink packet if the downlink payload is executed successfully.
	1536	)))
	1537
	1538	==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
	1539
	1540
	1541	Controls the relay output time.
	1542
	1543
	1544	(% style="color:#037691" %)AT Command:
	1545
	1546	There is no AT Command to control the Relay Output
	1547
	1548
	1549	(% style="color:#037691" %)Downlink Payload (prefix 0x05):
	1550
	1551	(% style="color:blue" %)0x05 aa bb cc dd (%%)~/~/ Sets RO1/RO2 relays with time control
	1552
	1553
	1554	This controls the relay output time and includes 4 bytes:
	1555
	1556	(% style="color:#4f81bd" %)First byte (%%): Type code (0x05)
	1557
	1558	(% style="color:#4f81bd" %)Second byte (aa)(%%): Inverter Mode
	1559
	1560	01: Relays will change back to their original state after a timeout.
	1561
	1562	00: Relays will change to the inverter state after a timeout.
	1563
	1564
	1565	(% style="color:#4f81bd" %)Third byte (bb)(%%): Control Method and Ports status:
	1566
	1567	[[image:image-20221008095908-1.png\|\|height="364" width="564"]]
	1568
	1569
	1570	(% style="color:#4f81bd" %)Fourth/Fifth/Sixth/Seventh bytes (cc)(%%): Latching time. Unit: ms
	1571
	1572
	1573	(% style="color:red" %)Note:
	1574
	1575	Since firmware v1.6.0, the latch time supports both 4 bytes and 2 bytes.
	1576
	1577	Before firmware v1.6.0, the latch time only supported 2 bytes.
	1578
	1579
	1580	(% style="color:red" %)The device will uplink a packet if the downlink code executes successfully.
	1581
	1582
	1583	Example payload:
	1584
	1585	~1. 05 01 11 07 D0
	1586
	1587	Relay1 and Relay2 will be set to NC, lasting 2 seconds, then revert to their original state
	1588
	1589	2. 05 01 10 07 D0
	1590
	1591	Relay1 will change to NC, Relay2 will change to NO, lasting 2 seconds, and then both will revert to their original state.
	1592
	1593	3. 05 00 01 07 D0
	1594
	1595	Relay1 will change to NO, Relay2 will change to NC, lasting 2 seconds, then Relay1 will change to NC, and Relay2 will change to NO.
	1596
	1597	4. 05 00 00 07 D0
	1598
	1599	Relay1 and Relay2 will change to NO, lasting 2 seconds, then both will change to NC.
	1600
	1601
	1602
	1603	==== 3.4.2.16 Counting ~-~- Voltage threshold counting ====
	1604
	1605
	1606	When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>\|\|anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
	1607
	1608	(% style="color:#037691" %)AT Command
	1609
	1610	(% border="2" style="width:500px" %)
	1611	\|(% style="width:137px" %)Command\|(% style="width:361px" %)AT+VOLMAX=<voltage>,<logic>
	1612	\|(% style="width:137px" %)Response\|(% style="width:361px" %)
	1613	\|(% style="width:137px" %)Parameters\|(% style="width:361px" %)(((
	1614	voltage : voltage threshold in mV
	1615
	1616	logic:
	1617
	1618	0 : lower than
	1619
	1620	1: higher than
	1621
	1622	if you leave the logic parameter blank, it is considered 0
	1623	)))
	1624	\|(% style="width:137px" %)Examples\|(% style="width:361px" %)(((
	1625	AT+VOLMAX=20000
	1626
	1627	If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
	1628
	1629	AT+VOLMAX=20000,0
	1630
	1631	If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1
	1632
	1633	AT+VOLMAX=20000,1
	1634
	1635	If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
	1636	)))
	1637
	1638	(% style="color:#037691" %)Downlink Payload
	1639
	1640	(% border="2" style="width:500px" %)
	1641	\|(% style="width:140px" %)Payload\|(% style="width:358px" %)<prefix><voltage><logic>
	1642	\|(% style="width:140px" %)Parameters\|(% style="width:358px" %)(((
	1643	prefix : A5 (hex)
	1644
	1645	voltage : voltage threshold in mV (2 bytes in hex)
	1646
	1647	logic: (1 byte in hexadecimal)
	1648
	1649	0 : lower than
	1650
	1651	1: higher than
	1652
	1653	if you leave the logic parameter blank, it is considered 1 (higher than)
	1654	)))
	1655	\|(% style="width:140px" %)Example\|(% style="width:358px" %)(((
	1656	A5 4E 20
	1657
	1658	If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
	1659
	1660	A5 4E 20 00
	1661
	1662	If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1
	1663
	1664	A5 4E 20 01
	1665
	1666	If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
	1667	)))
	1668
	1669	==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ====
	1670
	1671
	1672	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.
	1673
	1674	(% style="color:#037691" %)AT Command
	1675
	1676	(% border="2" style="width:500px" %)
	1677	\|(% style="width:134px" %)Command\|(% style="width:364px" %)AT+SETCNT=<counting_parameter>,<number>
	1678	\|(% style="width:134px" %)Response\|(% style="width:364px" %)
	1679	\|(% style="width:134px" %)Parameters\|(% style="width:364px" %)(((
	1680	counting_parameter :
	1681
	1682	1: COUNT1
	1683
	1684	2: COUNT2
	1685
	1686	3: AVI1 Count
	1687
	1688	number : Start number
	1689	)))
	1690	\|(% style="width:134px" %)Example\|(% style="width:364px" %)(((
	1691	AT+SETCNT=1,10
	1692
	1693	Sets the COUNT1 to 10.
	1694	)))
	1695
	1696	(% style="color:#037691" %)Downlink Payload
	1697
	1698	(% border="2" style="width:500px" %)
	1699	\|(% style="width:135px" %)Payload\|(% style="width:363px" %)<prefix><counting_parameter><number>
	1700	\|(% style="width:135px" %)Parameters\|(% style="width:363px" %)(((
	1701	prefix : A8 (hex)
	1702
	1703	counting_parameter : (1 byte in hexadecimal)
	1704
	1705	1: COUNT1
	1706
	1707	2: COUNT2
	1708
	1709	3: AVI1 Count
	1710
	1711	number : Start number, 4 bytes in hexadecimal
	1712	)))
	1713	\|(% style="width:135px" %)Example\|(% style="width:363px" %)(((
	1714	A8 01 00 00 00 0A
	1715
	1716	Sets the COUNT1 to 10.
	1717	)))
	1718
	1719	==== 3.4.2.18 Counting ~-~- Clear Counting ====
	1720
	1721
	1722	This command clears the counting in counting mode.
	1723
	1724	(% style="color:#037691" %)AT Command
	1725
	1726	(% border="2" style="width:500px" %)
	1727	\|(% style="width:142px" %)Command\|(% style="width:356px" %)AT+CLRCOUNT
	1728	\|(% style="width:142px" %)Response\|(% style="width:356px" %)-
	1729
	1730	(% style="color:#037691" %)Downlink Payload
	1731
	1732	(% border="2" style="width:500px" %)
	1733	\|(% style="width:141px" %)Payload\|(% style="width:357px" %)<prefix><clear?>
	1734	\|(% style="width:141px" %)Parameters\|(% style="width:357px" %)(((
	1735	prefix : A6 (hex)
	1736
	1737	clear? : 01 (hex)
	1738	)))
	1739	\|(% style="width:141px" %)Example\|(% style="width:357px" %)A6 01
	1740
	1741	==== 3.4.2.19 Set the save intervals of the counting results, RO (Relay Output), and DO (Digital Output) states ====
	1742
	1743	This command configures the device to periodically save the counting results, RO (Relay Output), and DO (Digital Output) states to internal flash memory at a user-defined interval. By setting a save interval, the device ensures that critical data (counting values and output states) is preserved in case of power loss.
	1744	The save interval can be adjusted to the user's needs, with a minimum value of (% style="color:blue" %)30(%%) seconds.
	1745	The saved RO/DO states can be restored after a device reset by combining this function with the (% style="color:blue" %)AT+RODORESET(%%) command.
	1746
	1747	(% style="color:#037691" %)AT Command
	1748
	1749	(% border="2" style="width:500px" %)
	1750	\|(% style="width:124px" %)Command\|(% style="width:374px" %)AT+COUTIME=<time>
	1751	\|(% style="width:124px" %)Response\|(% style="width:374px" %)
	1752	\|(% style="width:124px" %)Parameters\|(% style="width:374px" %)time : seconds (0 to 16777215)
	1753	\|(% style="width:124px" %)Example\|(% style="width:374px" %)(((
	1754	AT+COUTIME=60
	1755
	1756	Sets the device to save its counting results, RO and DO states to the memory every 60 seconds.
	1757	)))
	1758
	1759	(% style="color:#037691" %)Downlink Payload
	1760
	1761	(% border="2" style="width:500px" %)
	1762	\|(% style="width:123px" %)Payload\|(% style="width:375px" %)<prefix><time>
	1763	\|(% style="width:123px" %)Parameters\|(% style="width:375px" %)(((
	1764	prefix : A7
	1765
	1766	time : seconds, 3 bytes in hexadecimal
	1767	)))
	1768	\|(% style="width:123px" %)Example\|(% style="width:375px" %)(((
	1769	A7 00 00 3C
	1770
	1771	SSets the device to save its counting results, RO and DO states to the memory every 60 seconds.
	1772	)))
	1773
	1774	==== 3.4.2.20 Reset saved RO and DO states ====
	1775
	1776
	1777	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.
	1778
	1779	(% style="color:#037691" %)AT Command
	1780
	1781	(% border="2" style="width:500px" %)
	1782	\|(% style="width:127px" %)Command\|(% style="width:371px" %)AT+RODORESET=<state>
	1783	\|(% style="width:127px" %)Response\|(% style="width:371px" %)
	1784	\|(% style="width:127px" %)Parameters\|(% style="width:371px" %)(((
	1785	state :
	1786
	1787	0 : RODO will close when the device joins the network. (default)
	1788
	1789	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.
	1790	)))
	1791	\|(% style="width:127px" %)Example\|(% style="width:371px" %)(((
	1792	(% style="color:blue" %)AT+RODORESET=1
	1793
	1794	RODO will close when the device joins the network. (default)
	1795
	1796	(% style="color:blue" %)AT+RODORESET=0
	1797
	1798	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.
	1799	)))
	1800
	1801	(% style="color:#037691" %)Downlink Payload
	1802
	1803	(% border="2" style="width:500px" %)
	1804	\|(% style="width:127px" %)Payload\|(% style="width:371px" %)<prefix><state>
	1805	\|(% style="width:127px" %)Parameters\|(% style="width:371px" %)(((
	1806	prefix : AD
	1807
	1808	state :
	1809
	1810	0 : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal.
	1811
	1812	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
	1813	)))
	1814	\|(% style="width:127px" %)Example\|(% style="width:371px" %)(((
	1815	AD 01
	1816
	1817	RODO will close when the device joins the network. (default)
	1818
	1819	AD 00
	1820
	1821	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.
	1822	)))
	1823
	1824	==== 3.4.2.21 Encrypted payload ====
	1825
	1826
	1827	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.
	1828
	1829	(% style="color:#037691" %)AT Command:
	1830
	1831	(% border="2" style="width:500px" %)
	1832	\|(% style="width:127px" %)Command\|(% style="width:371px" %)AT+DECRYPT=<state>
	1833	\|(% style="width:127px" %)Response\|(% style="width:371px" %)
	1834	\|(% style="width:127px" %)Parameters\|(% style="width:371px" %)(((
	1835	state :
	1836
	1837	1 : The payload is uploaded without encryption
	1838
	1839	0 : The payload is encrypted when uploaded (default)
	1840	)))
	1841	\|(% style="width:127px" %)Example\|(% style="width:371px" %)(((
	1842	AT+DECRYPT=1
	1843
	1844	The payload is uploaded without encryption
	1845
	1846	AT+DECRYPT=0
	1847
	1848	The payload is encrypted when uploaded (default)
	1849	)))
	1850
	1851	There is no downlink payload for this configuration.
	1852
	1853
	1854	==== 3.4.2.22 Get sensor value ====
	1855
	1856
	1857	This command allows you to retrieve and optionally uplink sensor readings through the serial port.
	1858
	1859	(% style="color:#037691" %)AT Command
	1860
	1861	(% border="2" style="width:500px" %)
	1862	\|(% style="width:127px" %)Command\|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
	1863	\|(% style="width:127px" %)Response\|(% style="width:371px" %)
	1864	\|(% style="width:127px" %)Parameters\|(% style="width:371px" %)(((
	1865	state :
	1866
	1867	0 : Retrieves the current sensor reading via the serial port.
	1868
	1869	1 : Retrieves and uploads the current sensor reading via the serial port.
	1870	)))
	1871	\|(% style="width:127px" %)Example\|(% style="width:371px" %)(((
	1872	AT+GETSENSORVALUE=0
	1873
	1874	Retrieves the current sensor reading via the serial port.
	1875
	1876	AT+GETSENSORVALUE=1
	1877
	1878	Retrieves and uplinks the current sensor reading via the serial port.
	1879	)))
	1880
	1881	There is no downlink payload for this configuration.
	1882
	1883
	1884	==== 3.4.2.23 Resetting the downlink packet count ====
	1885
	1886
	1887	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.
	1888
	1889	(% style="color:#037691" %)AT Command
	1890
	1891	(% border="2" style="width:500px" %)
	1892	\|(% style="width:130px" %)Command\|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
	1893	\|(% style="width:130px" %)Response\|(% style="width:368px" %)(((
	1894
	1895	)))
	1896	\|(% style="width:130px" %)Parameters\|(% style="width:368px" %)(((
	1897	state :
	1898
	1899	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).
	1900
	1901
	1902	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.
	1903	)))
	1904	\|(% style="width:130px" %)Example\|(% style="width:368px" %)(((
	1905	AT+DISFCNTCHECK=0
	1906
	1907	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).
	1908
	1909	AT+DISFCNTCHECK=1
	1910
	1911	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.
	1912	)))
	1913
	1914	There is no downlink payload for this configuration.
	1915
	1916
	1917	==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ====
	1918
	1919
	1920	This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceed 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.
	1921
	1922	(% style="color:#037691" %)AT Command
	1923
	1924	(% border="2" style="width:500px" %)
	1925	\|(% style="width:127px" %)Command\|(% style="width:371px" %)AT+DISMACANS=<state>
	1926	\|(% style="width:127px" %)Response\|(% style="width:371px" %)
	1927	\|(% style="width:127px" %)Parameters\|(% style="width:371px" %)(((
	1928	state :
	1929
	1930	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)
	1931
	1932	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.
	1933	)))
	1934	\|(% style="width:127px" %)Example\|(% style="width:371px" %)(((
	1935	AT+DISMACANS=0
	1936
	1937	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)
	1938
	1939	AT+DISMACANS=1
	1940
	1941	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.
	1942	)))
	1943
	1944	(% style="color:#037691" %)Downlink Payload
	1945
	1946	(% border="2" style="width:500px" %)
	1947	\|(% style="width:126px" %)Payload\|(% style="width:372px" %)<prefix><state>
	1948	\|(% style="width:126px" %)Parameters\|(% style="width:372px" %)(((
	1949	prefix : 21
	1950
	1951	state : (2 bytes in hexadecimal)
	1952
	1953	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)
	1954
	1955	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.
	1956	)))
	1957	\|(% style="width:126px" %)Example\|(% style="width:372px" %)(((
	1958	21 00 01
	1959
	1960	Set DISMACANS=1
	1961	)))
	1962
	1963	==== 3.4.2.25 Copy downlink to uplink ====
	1964
	1965
	1966	This command enables the device to immediately uplink the payload of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100.
	1967
	1968	(% style="color:#037691" %)AT Command(%%):
	1969
	1970	(% style="color:blue" %)AT+RPL=5 (%%) ~/~/ After receiving a downlink payload from the server, the device will immediately uplink the payload back to the server using port number 100.
	1971
	1972	Example：aa xx xx xx xx ~/~/ aa indicates whether the configuration has changed: 00 means YES, and 01 means NO. xx xx xx xx are the bytes uplinked back.
	1973
	1974
	1975	[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173747-6.png?width=1124&height=165&rev=1.1\|\|alt="image-20220823173747-6.png"]]
	1976
	1977	For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
	1978
	1979	[[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"]]
	1980
	1981	For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
	1982
	1983
	1984	(% style="color:#037691" %)Downlink Payload(%%):
	1985
	1986	There is no downlink option available for this feature.
	1987
	1988
	1989	==== 3.4.2.26 Query firmware version, frequency band, subband, and TDC time ====
	1990
	1991
	1992	This command is used to query key information about the device, including its firmware version, frequency band, subband, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device.
	1993
	1994	* (((
	1995	(% style="color:#037691" %)Downlink Payload(%%):
	1996
	1997	(% style="color:blue" %)26 01 (%%) ~/~/ The downlink payload 26 01 is used to query the device's firmware version, frequency band, subband, and TDC time.
	1998
	1999
	2000	)))
	2001
	2002	Example：
	2003
	2004	[[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-20220823173929-8.png?width=1205&height=76&rev=1.1\|\|alt="image-20220823173929-8.png"]]
	2005
	2006
	2007	== 3.5 Integrating with ThingsEye.io ==
	2008
	2009
	2010	The Things Stack application supports integration with ThingsEye.io. Once integrated, ThingsEye.io acts as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
	2011
	2012
	2013	=== 3.5.1 Configuring The Things Stack ===
	2014
	2015
	2016	We use The Things Stack Sandbox in this example:
	2017
	2018	* In The Things Stack Sandbox, go to the Application for the LT-22222-L you added.
	2019	* Select MQTT under Integrations in the left menu.
	2020	* In the Connection information section, under Connection credentials, The Things Stack displays an auto-generated username. You can use it or provide a new one.
	2021	* Click the Generate new API key button to generate a password. You can view it by clicking on the visibility toggle/eye icon. The API key works as the password.
	2022
	2023	{{info}}
	2024	The username and password (API key) you created here are required in the next section.
	2025	{{/info}}
	2026
	2027	[[image:tts-mqtt-integration.png]]
	2028
	2029
	2030	=== 3.5.2 Configuring ThingsEye.io ===
	2031
	2032
	2033	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.
	2034
	2035	* Login to your [[ThingsEye.io >>https://thingseye.io]]account.
	2036	* Under the Integrations center, click Integrations.
	2037	* Click the Add integration button (the button with the + symbol).
	2038
	2039	[[image:thingseye-io-step-1.png]]
	2040
	2041
	2042	On the Add integration window, configure the following:
	2043
	2044	Basic settings:
	2045
	2046	* Select The Things Stack Community from the Integration type list.
	2047	* Enter a suitable name for your integration in the Name text box or keep the default name.
	2048	* Ensure the following options are turned on.
	2049	** Enable integration
	2050	** Debug mode
	2051	** Allow creating devices or assets
	2052	* Click the Next button. you will be navigated to the Uplink data converter tab.
	2053
	2054	[[image:thingseye-io-step-2.png]]
	2055
	2056
	2057	Uplink data converter:
	2058
	2059	* Click the Create new button if it is not selected by default.
	2060	* Enter a suitable name for the uplink data converter in the Name text box or keep the default name.
	2061	* Click the JavaScript button.
	2062	* 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]].
	2063	* Click the Next button. You will be navigated to the Downlink data converter tab.
	2064
	2065	[[image:thingseye-io-step-3.png]]
	2066
	2067
	2068	Downlink data converter (this is an optional step):
	2069
	2070	* Click the Create new button if it is not selected by default.
	2071	* Enter a suitable name for the downlink data converter in the Name text box or keep the default name.
	2072	* Click the JavaScript button.
	2073	* 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]].
	2074	* Click the Next button. You will be navigated to the Connection tab.
	2075
	2076	[[image:thingseye-io-step-4.png]]
	2077
	2078
	2079	Connection:
	2080
	2081	* Choose Region from the Host type.
	2082	* 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/...).
	2083	* 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).
	2084	* Click the Check connection button to test the connection. If the connection is successful, you will see the message saying Connected.
	2085
	2086	[[image:message-1.png]]
	2087
	2088
	2089	* Click the Add button.
	2090
	2091	[[image:thingseye-io-step-5.png]]
	2092
	2093
	2094	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.
	2095
	2096	[[image:thingseye.io_integrationsCenter_integrations.png]]
	2097
	2098
	2099	==== 3.5.2.1 Viewing integration details ====
	2100
	2101
	2102	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.
	2103
	2104	[[image:integration-details.png]]
	2105
	2106
	2107	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.
	2108
	2109	{{info}}
	2110	See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
	2111	{{/info}}
	2112
	2113
	2114	==== 3.5.2.2 Viewing events ====
	2115
	2116
	2117	The Events tab displays all the uplink messages from the LT-22222-L.
	2118
	2119	* Select Debug from the Event type dropdown.
	2120	* Select the time frame from the time window.
	2121
	2122	[[image:thingseye-events.png]]
	2123
	2124
	2125	* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
	2126
	2127	[[image:thingseye-json.png]]
	2128
	2129
	2130	==== 3.5.2.3 Deleting an integration ====
	2131
	2132
	2133	If you want to delete an integration, click the Delete integration button on the Integrations page.
	2134
	2135
	2136	==== 3.5.2.4 Viewing sensor data on a dashboard ====
	2137
	2138
	2139	You can create a dashboard with ThingsEye to visualize the sensor data coming from the LT-22222-L. The following image shows a dashboard created for the LT-22222-L. See Creating a dashboard in ThingsEye documentation for more information.
	2140
	2141	[[image:lt-22222-l-dashboard.png]]
	2142
	2143
	2144	== 3.6 Interface Details ==
	2145
	2146	=== 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
	2147
	2148
	2149	Supports NPN-type sensors.
	2150
	2151	[[image:1653356991268-289.png]]
	2152
	2153
	2154	=== 3.6.2 Digital Input Ports: DI1/DI2 ===
	2155
	2156
	2157	(((
	2158	The DI ports of the LT-22222-L can support NPN, PNP, or dry contact output sensors.
	2159	)))
	2160
	2161	(((
	2162	(((
	2163	The part of the internal circuit of the LT-22222-L shown below includes the NEC2501 photocoupler. The active current from NEC2501 pin 1 to pin 2 is 1 mA, with a maximum allowable current of 50 mA. When active current flows from NEC2501 pin 1 to pin 2, the DI becomes active HIGH and the DI LED status changes.
	2164
	2165
	2166	)))
	2167	)))
	2168
	2169	[[image:1653357170703-587.png]]
	2170
	2171	(((
	2172	(((
	2173	(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)When connecting a device to the DI port, both DI1+ and DI1- must be connected.
	2174	)))
	2175	)))
	2176
	2177	(((
	2178
	2179	)))
	2180
	2181	(((
	2182	(% style="color:#0000ff" %)Example 1(%%): Connecting to a low-active sensor.
	2183	)))
	2184
	2185	(((
	2186	This type of sensor outputs a low (GND) signal when active.
	2187	)))
	2188
	2189	* (((
	2190	Connect the sensor's output to DI1-
	2191	)))
	2192	* (((
	2193	Connect the sensor's VCC to DI1+.
	2194	)))
	2195
	2196	(((
	2197	When the sensor is active, the current between NEC2501 pin 1 and pin 2 will be：
	2198	)))
	2199
	2200	(((
	2201	[[image:1653968155772-850.png\|\|height="23" width="19"]]= DI1+ / 1K.
	2202	)))
	2203
	2204	(((
	2205	For example, if DI1+ = 12V, the resulting current is [[image:1653968155772-850.png\|\|height="23" width="19"]]= 12mA. Therefore, the LT-22222-L will be able to detect this active signal.
	2206	)))
	2207
	2208	(((
	2209
	2210	)))
	2211
	2212	(((
	2213	(% style="color:#0000ff" %)Example 2(%%): Connecting to a high-active sensor.
	2214	)))
	2215
	2216	(((
	2217	This type of sensor outputs a high signal (e.g., 24V) when active.
	2218	)))
	2219
	2220	* (((
	2221	Connect the sensor's output to DI1+
	2222	)))
	2223	* (((
	2224	Connect the sensor's GND DI1-.
	2225	)))
	2226
	2227	(((
	2228	When the sensor is active, the current between NEC2501 pin1 and pin2 will be:
	2229	)))
	2230
	2231	(((
	2232	[[image:1653968155772-850.png\|\|height="23" width="19"]]= DI1+ / 1K.
	2233	)))
	2234
	2235	(((
	2236	If DI1+ = 24V, the resulting current[[image:1653968155772-850.png\|\|height="23" width="19"]] is 24mA, Therefore, the LT-22222-L will detect this high-active signal.
	2237	)))
	2238
	2239	(((
	2240
	2241	)))
	2242
	2243	(((
	2244	(% style="color:#0000ff" %)Example 3(%%): Connecting to a 220V high-active sensor.
	2245	)))
	2246
	2247	(((
	2248	Assume that you want to monitor an active signal higher than 220V without damaging the photocoupler
	2249	)))
	2250
	2251	* (((
	2252	Connect the sensor's output to DI1+ with a 50K resistor in series.
	2253	)))
	2254	* (((
	2255	Connect the sensor's GND DI1-.
	2256	)))
	2257
	2258	(((
	2259	When the sensor is active, the current between NEC2501 pin1 and pin2 will be:
	2260	)))
	2261
	2262	(((
	2263	[[image:1653968155772-850.png\|\|height="23" width="19"]]= DI1+ / 51K.
	2264	)))
	2265
	2266	(((
	2267	If the sensor output is 220V, then [[image:1653968155772-850.png\|\|height="23" width="19"]](% wfd-invisible="true" id="cke_bm_243359S" style="display:none" %)[[image:image-20220524095628-8.png]](%%) = DI1+ / 51K = 4.3mA. Therefore, the LT-22222-L will be able to safely detect this high-active signal.
	2268	)))
	2269
	2270
	2271
	2272
	2273	(% style="color:blue" %)Example 4(%%): Connecting to a Dry Contact sensor
	2274
	2275	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.
	2276
	2277	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.
	2278
	2279	[[image:image-20230616235145-1.png]]
	2280
	2281	(% style="color:blue" %)Example 5(%%): Connecting to an Open Collector
	2282
	2283	[[image:image-20240219115718-1.png]]
	2284
	2285
	2286	=== 3.6.3 Digital Output Ports: DO1/DO2 ===
	2287
	2288
	2289	(% style="color:blue" %)NPN output(%%): GND or Float. The maximum voltage that can be applied to the output pin is 36V.
	2290
	2291	(% style="color:red" %)Note: The DO pins will float when the device is powered off.
	2292
	2293	[[image:1653357531600-905.png]]
	2294
	2295
	2296	=== 3.6.4 Analog Input Interfaces ===
	2297
	2298
	2299	The analog input interface is shown below. The LT-22222-L will measure the IN2 voltage to calculate the current passing through the load. The formula is:
	2300
	2301
	2302	(% style="color:blue" %)AC2 = (IN2 voltage )/12
	2303
	2304	[[image:1653357592296-182.png]]
	2305
	2306	Example: Connecting a 4~~20mA sensor
	2307
	2308	We will use the wind speed sensor as an example for reference only.
	2309
	2310
	2311	(% style="color:blue" %)Specifications of the wind speed sensor:
	2312
	2313	(% style="color:red" %)Red: 12~~24V
	2314
	2315	(% style="color:#ffc000" %)Yellow: 4~~20mA
	2316
	2317	Black: GND
	2318
	2319	Connection diagram:
	2320
	2321	[[image:1653357640609-758.png]]
	2322
	2323	[[image:1653357648330-671.png\|\|height="155" width="733"]]
	2324
	2325
	2326	Example: Connecting to a regulated power supply to measure voltage
	2327
	2328	[[image:image-20230608101532-1.png\|\|height="606" width="447"]]
	2329
	2330	[[image:image-20230608101608-2.jpeg\|\|height="379" width="284"]]
	2331
	2332	[[image:image-20230608101722-3.png\|\|height="102" width="1139"]]
	2333
	2334
	2335	(% style="color:blue; font-weight:bold" %)Specifications of the regulated power supply(% style="color:blue" %):
	2336
	2337	(% style="color:red" %)Red: 12~~24v
	2338
	2339	Black: GND
	2340
	2341
	2342	=== 3.6.5 Relay Output ===
	2343
	2344
	2345	(((
	2346	The LT-22222-L has two relay interfaces, RO1 and RO2, each using two pins of the screw terminal (ROx-1 and ROx-2 where x is the port number, 1 or 2). You can connect a device's power line in series with one of the relay interfaces (e.g., RO1-1 and RO1-2 screw terminals). See the example below:
	2347
	2348	(% style="color:red" %)Note:(%%) The ROx pins will be in the Open (NO) state when the LT-22222-L is powered off.
	2349	)))
	2350
	2351	[[image:image-20220524100215-9.png]]
	2352
	2353
	2354	[[image:image-20220524100215-10.png\|\|height="382" width="723"]]
	2355
	2356
	2357	== 3.7 LED Indicators ==
	2358
	2359
	2360	The table below lists the behaviour of LED indicators for each port function.
	2361
	2362	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
	2363	\|(% style="background-color:#4f81bd; color:white; width:50px" %)LEDs\|(% style="background-color:#4f81bd; color:white; width:460px" %)Feature
	2364	\|PWR\|Always on when there is power
	2365	\|TX\|(((
	2366	(((
	2367	Device booting: TX blinks 5 times.
	2368	)))
	2369
	2370	(((
	2371	Successful network joins: TX remains ON for 5 seconds.
	2372	)))
	2373
	2374	(((
	2375	Transmit a LoRa packet: TX blinks once
	2376	)))
	2377	)))
	2378	\|RX\|RX blinks once when a packet is received.
	2379	\|DO1\|For LT-22222-L: ON when DO1 is low, OFF when DO1 is high
	2380	\|DO2\|For LT-22222-L: ON when DO2 is low, OFF when DO2 is high
	2381	\|DI1\|(((
	2382	For LT-22222-L: ON when DI1 is high, OFF when DI1 is low
	2383	)))
	2384	\|DI2\|(((
	2385	For LT-22222-L: ON when DI2 is high, OFF when DI2 is low
	2386	)))
	2387	\|RO1\|For LT-22222-L: ON when RO1 is closed, OFF when RO1 is open
	2388	\|RO2\|For LT-22222-L: ON when RO2 is closed, OFF when RO2 is open
	2389
	2390	= 4. Using AT Commands =
	2391
	2392
	2393	The LT-22222-L supports programming using AT Commands.
	2394
	2395
	2396	== 4.1 Connecting the LT-22222-L to a PC ==
	2397
	2398
	2399	(((
	2400	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.
	2401
	2402	[[image:usb-ttl-audio-jack-connection.jpg]]
	2403
	2404
	2405	)))
	2406
	2407	(((
	2408	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:
	2409	)))
	2410
	2411	[[image:1653358355238-883.png]]
	2412
	2413
	2414	(((
	2415	== 4.2 LT-22222-L related AT commands ==
	2416
	2417
	2418	)))
	2419
	2420	(((
	2421	The following is the list of all the AT commands related to the LT-22222-L, except for those used for switching between working modes.
	2422
	2423	* ##AT##+<CMD>? : Help on <CMD>
	2424	* ##AT##+<CMD> : Run <CMD>
	2425	* ##AT##+<CMD>=<value> : Set the value
	2426	* ##AT##+<CMD>=? : Get the value
	2427	* ##ATZ##: Trigger a reset of the MCU
	2428	* ##AT+FDR##: Reset Parameters to factory default, reserve keys
	2429	* ##AT+DEUI##: Get or set the Device EUI (DevEUI)
	2430	* ##AT+DADDR##: Get or set the Device Address (DevAddr)
	2431	* ##AT+APPKEY##: Get or set the Application Key (AppKey)
	2432	* ##AT+NWKSKEY##: Get or set the Network Session Key (NwkSKey)
	2433	* ##AT+APPSKEY##: Get or set the Application Session Key (AppSKey)
	2434	* ##AT+APPEUI##: Get or set the Application EUI (AppEUI)
	2435	* ##AT+ADR##: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
	2436	* ##AT+TXP##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
	2437	* ##AT+DR##: Get or set the Data Rate. (0-7 corresponding to DR_X)
	2438	* ##AT+DCS##: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
	2439	* ##AT+PNM##: Get or set the public network mode. (0: off, 1: on)
	2440	* ##AT+RX2FQ##: Get or set the Rx2 window frequency
	2441	* ##AT+RX2DR##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
	2442	* ##AT+RX1DL##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
	2443	* ##AT+RX2DL##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
	2444	* ##AT+JN1DL##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
	2445	* ##AT+JN2DL##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
	2446	* ##AT+NJM##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
	2447	* ##AT+NWKID##: Get or set the Network ID
	2448	* ##AT+FCU##: Get or set the Frame Counter Uplink (FCntUp)
	2449	* ##AT+FCD##: Get or set the Frame Counter Downlink (FCntDown)
	2450	* ##AT+CLASS##: Get or set the Device Class
	2451	* ##AT+JOIN##: Join Network
	2452	* ##AT+NJS##: Get OTAA Join Status
	2453	* ##AT+SENDB##: Send hexadecimal data along with the application port
	2454	* ##AT+SEND##: Send text data along with the application port
	2455	* ##AT+RECVB##: Print the last received data in binary format (with hexadecimal values)
	2456	* ##AT+RECV##: Print the last received data in raw format
	2457	* ##AT+VER##: Get the current image version and Frequency Band
	2458	* ##AT+CFM##: Get or Set the confirmation mode (0-1)
	2459	* ##AT+CFS##: Get confirmation status of the last AT+SEND (0-1)
	2460	* ##AT+SNR##: Get the SNR of the last received packet
	2461	* ##AT+RSSI##: Get the RSSI of the last received packet
	2462	* ##AT+TDC##: Get or set the application data transmission interval in ms
	2463	* ##AT+PORT##: Get or set the application port
	2464	* ##AT+DISAT##: Disable AT commands
	2465	* ##AT+PWORD##: Set password, max 9 digits
	2466	* ##AT+CHS##: Get or set the Frequency (Unit: Hz) for Single Channel Mode
	2467	* ##AT+CHE##: Get or set eight channels mode, Only for US915, AU915, CN470
	2468	* ##AT+CFG##: Print all settings
	2469	)))
	2470
	2471
	2472	== 4.2 Common AT Command Sequence ==
	2473
	2474	=== 4.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
	2475
	2476	(((
	2477
	2478
	2479	(((
	2480	(% style="color:blue" %)If the device has not yet joined the network:
	2481	)))
	2482	)))
	2483
	2484	(((
	2485	(% style="background-color:#dcdcdc" %)##123456 ~/~/Enter the password to enable AT command access##
	2486	)))
	2487
	2488	(((
	2489	(% style="background-color:#dcdcdc" %)##AT+FDR ~/~/Reset parameters to factory default, Reserve keys##
	2490	)))
	2491
	2492	(((
	2493	(% style="background-color:#dcdcdc" %)##123456 ~/~/Enter the password to enable AT command access##
	2494	)))
	2495
	2496	(((
	2497	(% style="background-color:#dcdcdc" %)##AT+NJM=0 ~/~/Set to ABP mode##
	2498	)))
	2499
	2500	(((
	2501	(% style="background-color:#dcdcdc" %)##ATZ ~/~/Reset MCU##
	2502	)))
	2503
	2504
	2505	(((
	2506	(% style="color:blue" %)If the device has already joined the network:
	2507	)))
	2508
	2509	(((
	2510	(% style="background-color:#dcdcdc" %)##AT+NJM=0##
	2511	)))
	2512
	2513	(((
	2514	(% style="background-color:#dcdcdc" %)##ATZ##
	2515	)))
	2516
	2517
	2518	=== 4.2.2 Single-channel ABP mode (Use with LG01/LG02) ===
	2519
	2520	(((
	2521
	2522
	2523	(((
	2524	(% style="background-color:#dcdcdc" %)123456(%%) ~/~/ Enter the password to enable AT commands access
	2525	)))
	2526	)))
	2527
	2528	(((
	2529	(% style="background-color:#dcdcdc" %) AT+FDR(%%) ~/~/ Reset parameters to Factory Default, Reserve keys
	2530	)))
	2531
	2532	(((
	2533	(% style="background-color:#dcdcdc" %) 123456(%%) ~/~/ Enter the password to enable AT command access
	2534	)))
	2535
	2536	(((
	2537	(% style="background-color:#dcdcdc" %) AT+CLASS=C(%%) ~/~/ Set to CLASS C mode
	2538	)))
	2539
	2540	(((
	2541	(% style="background-color:#dcdcdc" %) AT+NJM=0(%%) ~/~/ Set to ABP mode
	2542	)))
	2543
	2544	(((
	2545	(% style="background-color:#dcdcdc" %) AT+ADR=0(%%) ~/~/ Set the Adaptive Data Rate Off
	2546	)))
	2547
	2548	(((
	2549	(% style="background-color:#dcdcdc" %) AT+DR=5(%%) ~/~/ Set Data Rate
	2550	)))
	2551
	2552	(((
	2553	(% style="background-color:#dcdcdc" %) AT+TDC=60000(%%) ~/~/ Set transmit interval to 60 seconds
	2554	)))
	2555
	2556	(((
	2557	(% style="background-color:#dcdcdc" %) AT+CHS=868400000(%%) ~/~/ Set transmit frequency to 868.4 MHz
	2558	)))
	2559
	2560	(((
	2561	(% style="background-color:#dcdcdc" %) AT+RX2FQ=868400000(%%) ~/~/ Set RX2 frequency to 868.4 MHz (according to the result from the server)
	2562	)))
	2563
	2564	(((
	2565	(% style="background-color:#dcdcdc" %) AT+RX2DR=5(%%) ~/~/ Set RX2 DR to match the downlink DR from the server. See below.
	2566	)))
	2567
	2568	(((
	2569	(% style="background-color:#dcdcdc" %) AT+DADDR=26 01 1A F1 (%%) ~/~/ Set Device Address. The Device Address can be found in the application on the LoRaWAN NS.
	2570	)))
	2571
	2572	(((
	2573	(% style="background-color:#dcdcdc" %) ATZ (%%) ~/~/ Reset MCU
	2574
	2575
	2576	)))
	2577
	2578	(((
	2579	(% style="color:red" %)Note:
	2580	)))
	2581
	2582	(((
	2583	~1. Ensure that the device is set to ABP mode in the LoRaWAN Network Server.
	2584
	2585	2. Verify that the LG01/02 gateway RX frequency matches the AT+CHS setting exactly.
	2586
	2587	3. Make sure the SF/bandwidth settings in the LG01/LG02 match the settings of AT+DR. Refer to [[this link>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.
	2588
	2589	4. The commands AT+RX2FQ and AT+RX2DR enable downlink functionality. To set the correct parameters, you can check the actual downlink parameters to be used as shown below. Here, RX2FQ should be set to 868400000 and RX2DR should be set to 5.
	2590	)))
	2591
	2592	(((
	2593	[[image:1653359097980-169.png\|\|height="188" width="729"]]
	2594	)))
	2595
	2596
	2597	=== 4.2.3 Change to Class A ===
	2598
	2599
	2600	(((
	2601	(% style="color:blue" %)If the sensor has JOINED:
	2602
	2603	(% style="background-color:#dcdcdc" %)AT+CLASS=A
	2604
	2605	(% style="background-color:#dcdcdc" %)ATZ
	2606	)))
	2607
	2608
	2609	= 5. Case Study =
	2610
	2611	== 5.1 Counting how many objects pass through the flow line ==
	2612
	2613
	2614	See [[How to set up to setup counting for objects passing through the flow line>>How to set up to count objects pass in flow line]].
	2615
	2616
	2617	= 6. FAQ =
	2618
	2619
	2620	This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
	2621
	2622
	2623	== 6.1 How to update the firmware? ==
	2624
	2625
	2626	Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to:
	2627
	2628	* Support new features
	2629	* Fix bugs
	2630	* Change LoRaWAN frequency bands
	2631
	2632	You will need the following things before proceeding:
	2633
	2634	* 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
	2635	* USB to TTL adapter/converter
	2636	* 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)
	2637	* 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.
	2638
	2639	{{info}}
	2640	As of this writing, the latest firmware version available for the LT-22222-L is v1.6.1.
	2641	{{/info}}
	2642
	2643	Below is the hardware setup for uploading a firmware image to the LT-22222-L:
	2644
	2645	[[image:usb-ttl-audio-jack-connection.jpg]]
	2646
	2647
	2648
	2649	Start the STM32 Flash Loader and choose the correct COM port to update.
	2650
	2651	(((
	2652	(((
	2653	(% style="color:blue" %)For LT-22222-L(%%):
	2654
	2655	Hold down the PRO button, then briefly press the RST button. The DO1 LED will change from OFF to ON. When the DO1 LED is ON, it indicates that the device is in firmware download mode.
	2656	)))
	2657
	2658
	2659	)))
	2660
	2661	[[image:image-20220524103407-12.png]]
	2662
	2663
	2664	[[image:image-20220524103429-13.png]]
	2665
	2666
	2667	[[image:image-20220524104033-15.png]]
	2668
	2669
	2670	(% style="color:red" %)Note(%%): If you have lost the programming cable, you can make one from a 3.5 mm cable. The pin mapping is as follows:
	2671
	2672	[[image:1653360054704-518.png\|\|height="186" width="745"]]
	2673
	2674
	2675	(((
	2676	(((
	2677	== 6.2 How to change the LoRaWAN frequency band/region? ==
	2678
	2679
	2680	)))
	2681	)))
	2682
	2683	(((
	2684	You can follow the introductions on [[how to upgrade the image>>\|\|anchor="H6.1Howtoupdatethefirmware3F"]]. When downloading, select the required image file.
	2685	)))
	2686
	2687	(((
	2688
	2689
	2690	== 6.3 How to set up LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
	2691
	2692
	2693	)))
	2694
	2695	(((
	2696	(((
	2697	In this case, you need to set the LT-22222-L to work in ABP mode and transmit on only one frequency.
	2698	)))
	2699	)))
	2700
	2701	(((
	2702	(((
	2703	We assume you have an LG01/LG02 working on the frequency 868400000. Below are the steps.
	2704
	2705
	2706	)))
	2707	)))
	2708
	2709	(((
	2710	(% style="color:#0000ff" %)Step 1(%%): Log in to The Things Stack Sandbox account and create an ABP device in the application. To do this, use the manual registration option as explained in section 3.2.2.2, //Adding a Device Manually//. Select //Activation by Personalization (ABP)// under Activation Mode. Enter the DevEUI exactly as shown on the registration information sticker, then generate the Device Address, Application Session Key (AppSKey), and Network Session Key (NwkSKey).
	2711
	2712	[[image:lt-22222-l-abp.png\|\|height="686" width="1000"]]
	2713	)))
	2714
	2715	(((
	2716
	2717	)))
	2718
	2719	{{warning}}
	2720	Ensure that the Device Address (DevAddr) and the two keys match between the LT-22222-L and The Things Stack. You can modify them either in The Things Stack or on the LT-22222-L to make them align. In The Things Stack, you can configure the NwkSKey and AppSKey on the settings page, but note that the Device Address is generated by The Things Stack.
	2721	{{/warning}}
	2722
	2723
	2724	(((
	2725	(% style="color:blue" %)Step 2(%%): (% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)Run AT commands to configure the LT-22222-L to operate in single-frequency and ABP mode. The AT commands are as follows:
	2726
	2727
	2728	)))
	2729
	2730	(((
	2731	(% style="background-color:#dcdcdc" %)123456 (%%) : Enter the password to enable AT access.
	2732
	2733	(% style="background-color:#dcdcdc" %)AT+FDR(%%) : Reset parameters to factory default, keeping keys reserved.
	2734
	2735	(% style="background-color:#dcdcdc" %)AT+NJM=0 (%%) : Set to ABP mode.
	2736
	2737	(% style="background-color:#dcdcdc" %)AT+ADR=0 (%%) : Disable the Adaptive Data Rate (ADR).
	2738
	2739	(% style="background-color:#dcdcdc" %)AT+DR=5 (%%) : Set Data Rate (Use AT+DR=3 for the 915 MHz band).
	2740
	2741	(% style="background-color:#dcdcdc" %)AT+TDC=60000 (%%) : Set transmit interval to 60 seconds.
	2742
	2743	(% style="background-color:#dcdcdc" %)AT+CHS=868400000(%%) : Set transmit frequency to 868.4 MHz.
	2744
	2745	(% style="background-color:#dcdcdc" %)AT+DADDR=xxxx(%%) : Set the Device Address (DevAddr)
	2746
	2747	(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:700; text-decoration:none; white-space:pre-wrap" %)AT+APPKEY=xxxx(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %): Get or set the Application Key (AppKey)
	2748
	2749	(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)AT+NWKSKEY=xxxx: Get or set the Network Session Key (NwkSKey)
	2750
	2751	(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)AT+APPSKEY=xxxx: Get or set the Application Session Key (AppSKey)
	2752
	2753	(% style="background-color:#dcdcdc" %)ATZ (%%) : Reset MCU.
	2754	)))
	2755
	2756
	2757	(((
	2758	(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)The following figure shows the screenshot of the command set above, issued using a serial tool:
	2759	)))
	2760
	2761	[[image:1653360498588-932.png\|\|height="485" width="726"]]
	2762
	2763
	2764	== 6.4 How to change the uplink interval? ==
	2765
	2766
	2767	Please see this link: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/]]
	2768
	2769
	2770	== 6.5 Can I see the counting event in the serial output? ==
	2771
	2772
	2773	(((
	2774	You can run the AT command AT+DEBUG to view the counting event in the serial output. If the firmware is too old and doesn’t support AT+DEBUG, update to the latest firmware first.
	2775
	2776
	2777	== 6.6 Can I use point-to-point communication with LT-22222-L? ==
	2778
	2779
	2780	Yes, you can. Please refer to the [[Point-to-Point Communication of LT-22222-L>>https://wiki.dragino.com/xwiki/bin/view/Main/%20Point%20to%20Point%20Communication%20of%20LT-22222-L/]] page. The firmware that supports point-to-point communication can be found [[here>>https://github.com/dragino/LT-22222-L/releases]].
	2781
	2782
	2783	)))
	2784
	2785	(((
	2786	== 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
	2787
	2788
	2789	* If the device is not properly shut down and is directly powered off.
	2790	* It will default to a power-off state.
	2791	* In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
	2792	* After a restart, the status before the power failure will be read from Flash.
	2793
	2794	== 6.8 Can I set up LT-22222-L as an NC (Normally Closed) relay? ==
	2795
	2796
	2797	The LT-22222-L's built-in relay is Normally Open (NO). You can use an external relay to achieve a Normally Closed (NC) configuration. The circuit diagram is shown below:
	2798
	2799
	2800	[[image:image-20221006170630-1.png\|\|height="610" width="945"]]
	2801
	2802
	2803	== 6.9 Can the LT-22222-L save the RO state? ==
	2804
	2805
	2806	To enable this feature, the firmware version must be 1.6.0 or higher.
	2807
	2808
	2809	== 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
	2810
	2811
	2812	It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
	2813
	2814
	2815	= 7. Troubleshooting =
	2816
	2817
	2818	This section provides some known troubleshooting tips.
	2819
	2820
	2821	)))
	2822
	2823	(((
	2824	(((
	2825	== 7.1 Downlink isn't working. How can I solve this? ==
	2826
	2827
	2828	)))
	2829	)))
	2830
	2831	(((
	2832	Please refer to this link for debugging instructions: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome\|\|anchor="H5.1Howitwork"]]
	2833	)))
	2834
	2835	(((
	2836
	2837
	2838	== 7.2 Having trouble uploading an image? ==
	2839
	2840
	2841	)))
	2842
	2843	(((
	2844	Please refer to this link for troubleshooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
	2845	)))
	2846
	2847	(((
	2848
	2849
	2850	== 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
	2851
	2852
	2853	)))
	2854
	2855	(((
	2856	It might be related to the channel mapping. [[Please refer to this link for details.>>https://github.com/dragino/LT-22222-L/releases]]
	2857	)))
	2858
	2859
	2860	== 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? ==
	2861
	2862
	2863	The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
	2864	Use this command to synchronize their counts: [[Resets the downlink packet count>>\|\|anchor="H3.4.2.23Resettingthedownlinkpacketcount"]]
	2865
	2866
	2867	= 8. Ordering information =
	2868
	2869
	2870	(% style="color:#4f81bd" %)LT-22222-L-XXX:
	2871
	2872	(% style="color:#4f81bd" %)XXX:
	2873
	2874	* (% style="color:red" %)EU433(%%): LT with frequency bands EU433
	2875	* (% style="color:red" %)EU868(%%): LT with frequency bands EU868
	2876	* (% style="color:red" %)KR920(%%): LT with frequency bands KR920
	2877	* (% style="color:red" %)CN470(%%): LT with frequency bands CN470
	2878	* (% style="color:red" %)AS923(%%): LT with frequency bands AS923
	2879	* (% style="color:red" %)AU915(%%): LT with frequency bands AU915
	2880	* (% style="color:red" %)US915(%%): LT with frequency bands US915
	2881	* (% style="color:red" %)IN865(%%): LT with frequency bands IN865
	2882	* (% style="color:red" %)CN779(%%): LT with frequency bands CN779
	2883
	2884	= 9. Package information =
	2885
	2886
	2887	(% style="color:#037691" %)Package Includes:
	2888
	2889	* 1 x LT-22222-L I/O Controller
	2890	* 1 x LoRa antenna matched to the frequency of the LT-22222-L
	2891	* 1 x bracket for DIN rail mounting
	2892	* 1 x 3.5 mm programming cable
	2893
	2894	(% style="color:#037691" %)Dimension and weight:
	2895
	2896	* Package Size / pcs : 145×80×50 mm
	2897	* Weight / pcs : 180 g
	2898
	2899	= 10. Support =
	2900
	2901
	2902	* (((
	2903	Support is available Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time zones, we cannot offer live support. However, your questions will be answered as soon as possible within the aforementioned schedule.
	2904	)))
	2905	* (((
	2906	Please provide as much information as possible regarding your inquiry (e.g., product models, a detailed description of the problem, steps to replicate it, etc.) and send an email to [[support@dragino.cc>>mailto:support@dragino.cc]]
	2907
	2908
	2909	)))
	2910
	2911	= 11. Reference =
	2912
	2913
	2914	* LT-22222-L: [[http:~~/~~/www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html>>url:http://www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html]]
	2915	* [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]]
	2916	* [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]

Wiki source code of LT-22222-LA -- LoRa I/O Controller User Manual

Applications