Table of Contents:

• 1. Introduction
  • 1.1 What is the LT-22222-L I/O Controller?
  • 1.2 Specifications
  • 1.3 Features
  • 1.4 Applications
  • 1.5 Hardware Variants
• 2. Assembling the Device
  • 2.1 What is included in the package?
  • 2.2 Terminals
  • 2.3 Powering the LT-22222-L
• 3. Operation Mode
  • 3.1 How does it work?
  • 3.2 Registering with a LoRaWAN network server
    • 3.2.1 Prerequisites
    • 3.2.2 The Things Stack Sandbox (TTSS)
      • Using the LoRaWAN Device Repository:
      • Entering device information manually:
      • Joining
  • 3.3 Work Modes and their Uplink Payload formats
    • 3.3.1 AT+MOD=1, 2ACI+2AVI
    • 3.3.2 AT+MOD=2, (Double DI Counting)
    • 3.3.3 AT+MOD=3, Single DI Counting + 2 x ACI
    • 3.3.4 AT+MOD=4, Single DI Counting + 1 x Voltage Counting
    • 3.3.5 AT+MOD=5, Single DI Counting + 2 x AVI + 1 x ACI
    • 3.3.6 AT+ADDMOD=6. (Trigger Mode, Optional)
    • 3.3.7 Payload Decoder
  • 3.4 ​Configure LT via AT Commands or Downlinks
    • 3.4.1 Common Commands
    • 3.4.2 Sensor related commands
      • 3.4.2.1 Set Transmit Interval
      • 3.4.2.2 Set the Work Mode (AT+MOD)
      • 3.4.2.3 Poll an uplink
      • 3.4.2.4 Enable/Disable Trigger Mode
      • 3.4.2.5 Poll trigger settings
      • 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger
      • 3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger
      • 3.4.2.8 Trigger2 – Set DI2 as trigger
      • 3.4.2.9 Trigger – Set AC (current) as trigger
      • 3.4.2.10 Trigger – Set AV (voltage) as trigger
      • 3.4.2.11 Trigger – Set minimum interval
      • 3.4.2.12 DO -- Control Digital Output DO1/DO2/DO3
      • 3.4.2.13 DO -- Control Digital Output DO1/DO2/DO3 with time control
      • 3.4.2.14 Relay -- Control Relay Output RO1/RO2
      • 3.4.2.15 Relay -- Control Relay Output RO1/RO2 with time control
      • 3.4.2.16 Counting -- Voltage threshold counting
      • 3.4.2.17 Counting -- Pre-configure the Count Number
      • 3.4.2.18 Counting -- Clear Counting
      • 3.4.2.19 Counting -- Change counting mode to save time
      • 3.4.2.20 Reset save RO DO state
      • 3.4.2.21 Encrypted payload
      • 3.4.2.22 Get sensor value
      • 3.4.2.23 Resets the downlink packet count
      • 3.4.2.24 When the limit bytes are exceeded, upload in batches
      • 3.4.2.25 Copy downlink to uplink
      • 3.4.2.26 Query version number and frequency band 、TDC
  • 3.5 Integrating with ThingsEye.io
    • 3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox
    • 3.5.2 Configuring ThingsEye.io
  • 3.6 Interface Details
    • 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active )
    • 3.6.2 Digital Input Ports: DI1/DI2 ( For LT-22222-L)
    • 3.6.3 Digital Output Ports: DO1/DO2 /DO3
    • 3.6.4 Analog Input Interfaces
    • 3.6.5 Relay Output
  • 3.7 LEDs Indicators
• 4. Using AT Command
  • 4.1 Connecting the LT-22222-L to a computer
  • 4.2 Common AT Command Sequence
    • 4.2.1 Multi-channel ABP mode (Use with SX1301/LG308)
    • 4.2.2 Single-channel ABP mode (Use with LG01/LG02)
    • 4.2.3 Change to Class A
• 5. Case Study
  • 5.1 Counting how many objects pass through the flow Line
• 6. FAQ
  • 6.1 How to upgrade the image?
  • 6.2 How to change the LoRa Frequency Bands/Region?
  • 6.3 How to set up LT to work with a Single Channel Gateway, such as LG01/LG02?
  • 6.4 How to change the uplink interval?
  • 6.5 Can I see the counting event in Serial?
  • 6.6 Can I use point-to-point communication with LT-22222-L?
  • 6.7 Why does the relay output become the default and open relay after the lt22222 is powered off?
  • 6.8 Can i set up LT-22222-L as a NC(Normal Close) Relay?
  • 6.9 Can LT22222-L save RO state?
  • 6.10 Why does the LT22222 always report 15.585V when measuring AVI?
• 7. Trouble Shooting
  • 7.1 Downlink doesn't work, how to solve it?
  • 7.2 Have trouble to upload image.
  • 7.3 Why I can't join TTN in US915 /AU915 bands?
  • 7.4 Why can LT22222 perform Uplink normally, but cannot receive Downlink?
• 8. Order Info
• 9. Packing Info
• 10. Support
• 11. Reference​​​​​

1. Introduction

1.1 What is the LT-22222-L I/O Controller?

 The LT Series I/O Controllers are designed for easy, low-cost installation on LoRaWAN networks.

1.2 Specifications

Hardware System:

• STM32L072xxxx MCU
• SX1276/78 Wireless Chip  
• Power Consumption:
  • Idle: 4mA@12v
  • 20dB Transmit: 34mA@12v
• Operating Temperature: -40 ~ 85 Degrees, No Dew

Interface for Model: LT22222-L:

• 2 x Digital dual direction Input (Detect High/Low signal, Max: 50v, or 220v with optional external resistor)
• 2 x Digital Output (NPN output. Max pull-up voltage 36V,450mA)
• 2 x Relay Output (5A@250VAC / 30VDC)
• 2 x 0~20mA Analog Input (res:0.01mA)
• 2 x 0~30V Analog Input (res:0.01v)
• Power Input 7~ 24V DC.  

LoRa Spec:

• Frequency Range:
  • Band 1 (HF): 862 ~ 1020 Mhz
  • Band 2 (LF): 410 ~ 528 Mhz
• 168 dB maximum link budget.
• +20 dBm - 100 mW constant RF output vs.
• +14 dBm high-efficiency PA.
• Programmable bit rate up to 300 kbps.
• High sensitivity: down to -148 dBm.
• Bullet-proof front end: IIP3 = -12.5 dBm.
• Excellent blocking immunity.
• Low RX current of 10.3 mA, 200 nA register retention.
• Fully integrated synthesizer with a resolution of 61 Hz.
• FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
• Built-in bit synchronizer for clock recovery.
• Preamble detection.
• 127 dB Dynamic Range RSSI.
• Automatic RF Sense and CAD with ultra-fast AFC.
• Packet engine up to 256 bytes with CRC.

1.3 Features

• LoRaWAN Class A & Class C protocol
• Optional Customized LoRa Protocol
• Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
• AT Commands to change parameters
• Remotely configure parameters via LoRaWAN Downlink
• Firmware upgradable via program port
• Counting

1.4 Applications

• Smart Buildings & Home Automation
• Logistics and Supply Chain Management
• Smart Metering
• Smart Agriculture
• Smart Cities
• Smart Factory

1.5 Hardware Variants

2. Assembling the Device

2.1 What is included in the package?

The package includes the following items:

• 1 x LT-22222-L I/O Controller
• 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L
• 1 x bracket for wall mounting
• 1 x programming cable

Attach the LoRaWAN antenna to the antenna connector, ANT, located on the top right side of the device, next to the upper terminal block. Secure the antenna by tightening it clockwise.

2.2 Terminals

Upper screw terminal block (from left to right):

Lower screw terminal block (from left to right):

2.3 Powering the LT-22222-L

The LT-22222-L I/O Controller can be powered by a 7–24V DC power source. Connect the 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.

3. Operation Mode

3.1 How does it work?

By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. It supports OTAA (Over-the-Air Activation), the most secure method for activating a device with a LoRaWAN network server. The LT-22222-L comes with device registration information that allows you to register it with a LoRaWAN network, enabling the device to perform OTAA activation with the network server upon initial power-up and after any subsequent reboots.

For LT-22222-L, the LED will show the Join status: After powering on, the TX LED will fast-blink 5 times which means the LT-22222-L will enter the working mode and start to JOIN the LoRaWAN network. The TX LED will be on for 5 seconds after joining the network. When there is a message from the server, the RX LED will be on for 1 second.  

In case you can't set the root key and other identifiers in the network server and must use them from the server, you can use AT Commands to configure them on the device.

3.2 Registering with a LoRaWAN network server

The diagram below shows how the LT-22222-L connects to a typical LoRaWAN network.

3.2.1 Prerequisites

Make sure you have the device registration information such as DevEUI, AppEUI, and AppKey with you. The registration information can be found on a sticker that can be found inside the package. Please keep the registration information sticker in a safe place for future reference.

The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.

3.2.2 The Things Stack Sandbox (TTSS)

• Log in to your The Things Stack Sandbox account.
• Create an application if you do not have one yet.
• Register LT-22222-L with that application. Two registration options are available:

Using the LoRaWAN Device Repository:

• Go to your application and click on the Register end device button.
• On the Register end device page:
  • Select the option Select the end device in the LoRaWAN Device Repository.
  • Choose the End device brand, Model, Hardware version, Firmware version, and Profile (Region).
  • Select the Frequency plan that matches your device.

•  
  • Enter the AppEUI in the JoinEUI field and click the Confirm button.
  • Enter the DevEUI in the DevEUI field.
  • Enter the AppKey in the AppKey field.
  • In the End device ID field, enter a unique name within this application for your LT-22222-N.
  • Under After registration, select the View registered end device option.

Entering device information manually:

• On the Register end device page:
  • Select the Enter end device specifies manually option as the input method.
  • Select the Frequency plan that matches your device.
  • Select the LoRaWAN version.
  • Select the Regional Parameters version.
  • Click Show advanced activation, LoRaWAN class and cluster settings link to expand the section.
  • Select Over the air activation (OTAA) option under the Activation mode
  • Select Class C (Continuous) from the Additional LoRaWAN class capabilities.

• Enter AppEUI in the JoinEUI field and click the Confirm button.
• Enter DevEUI in the DevEUI field.
• Enter AppKey in the AppKey field.
• In the End device ID field, enter a unique name within this application for your LT-22222-N.
• Under After registration, select the View registered end device option.
• Click the Register end device button.

You will be navigated to the Device overview page.

Joining

Click on Live data in the left navigation. Then, power on LT-22222-L. It will join The Things Stack LoRaWAN network server. You can see the join request, join accept, followed by uplink data messages form the device showing in the Live data panel.

Click on a message with the messge type, Forward uplink data message. You can see the  decoded uplink payload as shown below.

If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select End devices > LT-22222-L > Payload formatters > Uplink. Then  select Use Device repository formatters for the Formatter type dropdown. Click the Save changes button to apply the changes.

3.3 Work Modes and their Uplink Payload formats

The LT-22222-L has 5 work 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.

• MOD1: (default mode/factory set): 2ACI + 2AVI + DI + DO + RO

• MOD2: Double DI Counting + DO + RO

• MOD3: Single DI Counting + 2 x ACI + DO + RO

• MOD4: Single DI Counting + 1 x Voltage Counting + DO + RO

• MOD5: Single DI Counting + 2 x AVI + 1 x ACI + DO + RO

• ADDMOD6: Trigger Mode, Optional, used together with MOD1 ~ MOD5

3.3.1 AT+MOD=1, 2ACI+2AVI

• RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN.
• DI is for digital input. DIx=1: HIGH or FLOATING, DIx=0: LOW.
• DO is for reverse digital output. DOx=1: LOW, DOx=0: HIGH or FLOATING.

Note: DI3 and DO3 bits are not valid for LT-22222-L

For example, if the payload is: 

The interface values can be calculated as follows:  

AVI1 channel voltage is 0x04AB/1000=1195(DEC)/1000=1.195V

AVI2 channel voltage is 0x04AC/1000=1.196V

ACI1 channel current is 0x1310/1000=4.880mA

ACI2 channel current is 0x1300/1000=4.864mA

The last byte 0xAA= 10101010(b) means,

• [1] The RO1 relay channel is CLOSED, and the RO1 LED is ON.
• [0] The RO2 relay channel is OPEN, and the RO2 LED is OFF.
• [1] DI3 - not used for LT-22222-L.
• [0] DI2 channel input is LOW, and the DI2 LED is OFF.
• [1] DI1 channel input state:
  • DI1 is FLOATING when no sensor is connected between DI1+ and DI1-.
  • DI1 is HIGH when a sensor is connected between DI1- and DI1+ and the sensor is ACTIVE.
  • DI1 LED is ON in both cases.
• [0] DO3 - not used for LT-22222-L.
• [1] DO2 channel output is LOW, and the DO2 LED is ON.
• [0] DO1 channel output state:
  • DO1 is FLOATING when there is no load between DO1 and V+.
  • DO1 is HIGH when there is a load between DO1 and V+.
  • DO1 LED is OFF in both cases.

3.3.2 AT+MOD=2, (Double DI Counting)

• FIRST: Indicates that this is the first packet after joining the network.
• DO is for reverse digital output. DOx=1: LOW, DOx=0: HIGH or FLOATING.

3.3.3 AT+MOD=3, Single DI Counting + 2 x ACI

LT22222-L: In this mode, the DI1 is used as a counting pin.

• RO is for the relay. ROx=1: closed, ROx=0 always open.
• FIRST: Indicates that this is the first packet after joining the network.
• DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.

3.3.4 AT+MOD=4, Single DI Counting + 1 x Voltage Counting

• RO is for the relay. ROx=1: closed, ROx=0 always open.
• FIRST: Indicates that this is the first packet after joining the network.
• DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.

3.3.5 AT+MOD=5, Single DI Counting + 2 x AVI + 1 x ACI

LT22222-L: In this mode, the DI1 is used as a counting pin.

• RO is for the relay. ROx=1: closed, ROx=0 always open.
• FIRST: Indicates that this is the first packet after joining the network.

• DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.

3.3.6 AT+ADDMOD=6. (Trigger Mode, Optional)

This mode is optional and intended for trigger purposes. It can operate together with other modes.

For example, if you configured the following commands:

• AT+MOD=1             -->   The normal working mode
• AT+ADDMOD6=1   -->   Enable trigger mode

The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. LT will send uplink packets in two cases:

1. Periodically uplink (Based on TDC time). The payload is the same as in normal mode (MOD=1 for the commands above). These are unconfirmed uplinks.
2. Trigger uplink when the trigger condition is met. LT will send two packets in this case. The first uplink uses the payload specified in trigger mode (MOD=6). The second packet uses the normal mode payload (MOD=1 as set above). Both are CONFIRMED uplinks.

AT Command to set Trigger Condition:

Trigger based on voltage:

Format: AT+AVLIM=<AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH>

Example:

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)

AT+AVLIM=5000,0,0,0   (triggers an uplink if AVI1 voltage lower than 5V. Use 0 for parameters that are not in use)

Trigger based on current:

Format: AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH>

Example:

AT+ACLIM=10000,15000,0,0   (triggers an uplink if ACI1 voltage is lower than 10mA or higher than 15mA)

Trigger based on DI status:

DI status triggers Flag.

Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >

Example:

AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)

LoRaWAN Downlink Commands for Setting the Trigger Conditions:

Type Code: 0xAA. Downlink command same as AT Command AT+AVLIM, AT+ACLIM

Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4

  AA: Type Code for this downlink Command:

  xx: 0: Limit for AV1 and AV2; 1: limit for AC1 and AC2; 2: DI1and DI2 trigger enable/disable.

  yy1 yy1: AC1 or AV1 LOW limit or DI1/DI2 trigger status.

  yy2 yy2: AC1 or AV1 HIGH limit.

  yy3 yy3: AC2 or AV2 LOW limit.

  Yy4 yy4: AC2 or AV2 HIGH limit.

Example 1: AA 00 13 88 00 00 00 00 00 00

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)

Example 2: AA 02 01 00

Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)

Trigger Settings Payload Explanation:

MOD6 Payload: total of 11 bytes

TRI FLAG1 is a combination to show if the trigger is set for this part. Totally 1 byte as below

• Each bit shows if the corresponding trigger has been configured.

Example:

10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW

TRI Status1 is a combination to show which condition is trigger. Totally 1 byte as below

• Each bit shows which status has been triggered on this uplink.

Example:

10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.

TRI_DI FLAG+STA is a combination to show which condition is trigger. Totally 1byte as below

• Each bits shows which status has been triggered on this uplink.

Example:

00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.

00000101: Means both DI1 and DI2 trigger are enabled.

Enable/Disable MOD6 : 0x01: MOD6 is enable. 0x00: MOD6 is disable.

Downlink command to poll MOD6 status:

AB 06

When device got this command, it will send the MOD6 payload.

3.3.7 Payload Decoder

3.4 ​Configure LT via AT Commands or Downlinks

• Common Commands: They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.5.4, user can find what common commands it supports: End Device AT Commands and Downlink Command

• Sensor Related Commands: These commands are special designed for LT-22222-L.  User can see these commands below:

3.4.1 Common Commands

3.4.2 Sensor related commands

3.4.2.1 Set Transmit Interval

Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.

• AT command:

AT+TDC=N

where N is the time in milliseconds.

Example: AT+TDC=30000. This will set the uplink interval to 30 seconds

• Downlink payload (prefix 0x01):

0x01 aa bb cc     // Same as AT+TDC=0x(aa bb cc)

3.4.2.2 Set the Work Mode (AT+MOD)

Sets the work mode.

• AT command: AT+MOD=N  

Where N is the work mode.

Example: AT+MOD=2. This will set the work mode to Double DI counting mode.

• Downlink payload (prefix 0x0A):

0x0A aa     // Same as AT+MOD=aa

3.4.2.3 Poll an uplink

Asks the device to send an uplink.

• AT command: There is no AT Command to poll uplink

• Downlink payload (prefix 0x08):

0x08 FF     // Poll an uplink

Example: 0x08FF, ask device to send an Uplink

3.4.2.4 Enable/Disable Trigger Mode

Enable or disable the trigger mode (see also ADDMOD6).

• AT Command: AT+ADDMOD6=1 or 0

1: Enable the trigger mode

0: Disable the trigger mode

• Downlink Payload (prefix 0x0A 06):

0x0A 06 aa        // Same as AT+ADDMOD6=aa

3.4.2.5 Poll trigger settings

Polls the trigger settings

• AT Command:

There is no AT Command for this feature.

• Downlink Payload (prefix 0x AB 06):

0xAB 06       // Poll the trigger settings. Device will uplink trigger settings once receive this command

3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger

Enable or Disable DI1/DI2/DI2 as trigger,

• AT Command: Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >

Example: AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)

• Downlink Payload (prefix 0xAA 02):

0xAA 02 aa bb      // Same as AT+DTRI=aa,bb

3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger

Set DI1 or DI3(for LT-33222-L) trigger.

• AT Command: AT+TRIG1=a,b

a : Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).

b : delay timing.

Example: AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms ) 

• Downlink Payload (prefix 0x09 01 ):

0x09 01 aa bb cc         // same as AT+TRIG1=aa,0x(bb cc)

3.4.2.8 Trigger2 – Set DI2 as trigger

Sets DI2 trigger.

• AT Command: AT+TRIG2=a,b

a : Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).

b : delay timing.

Example: AT+TRIG2=0,100 (set DI1 port to trigger on low level, valid signal is 100ms ) 

• Downlink Payload (prefix 0x09 02 ):

0x09 02 aa bb cc     // same as AT+TRIG2=aa,0x(bb cc)

3.4.2.9 Trigger – Set AC (current) as trigger

Set current trigger , base on AC port. See trigger mode

• AT Command: AT+ACLIM

• Downlink Payload (prefix 0xAA 01 )

0x AA 01 aa bb cc dd ee ff gg hh           // same as AT+ACLIM See trigger mode

3.4.2.10 Trigger – Set AV (voltage) as trigger

Set current trigger , base on AV port. See trigger mode

• AT Command: AT+AVLIM            See trigger mode

• Downlink Payload (prefix 0xAA 00 )

0x AA 00 aa bb cc dd ee ff gg hh      // same as AT+AVLIM See trigger mode 

3.4.2.11 Trigger – Set minimum interval

Sets AV and AC trigger minimum interval.  Device won't response to the second trigger within this set time after the first trigger.

• AT Command: AT+ATDC=5         // Device won't response the second trigger within 5 minute after the first trigger.

• Downlink Payload (prefix 0xAC )

0x AC aa bb    // same as AT+ATDC=0x(aa bb)   . Unit (min)

3.4.2.12 DO -- Control Digital Output DO1/DO2/DO3

• AT Command

There is no AT Command to control Digital Output

• Downlink Payload (prefix 0x02)

0x02 aa bb cc      // Set DO1/DO2/DO3 output

3.4.2.13 DO -- Control Digital Output DO1/DO2/DO3 with time control

• AT Command

There is no AT Command to control Digital Output

• Downlink Payload (prefix 0xA9)

0xA9 aa bb cc      // Set DO1/DO2/DO3 output with time control

This is to control the digital output time of DO pin. Include four bytes:

First Byte: Type code (0xA9)

Second Byte: Inverter Mode

01: DO pins will change back to original state after timeout. 

00: DO pins will change to an inverter state after timeout  

Third Byte: Control Method and Ports status:

Fourth Byte: Control Method and Ports status:

Fifth Byte: Control Method and Ports status:

Sixth and Seventh and Eighth and Ninth Byte: Latching time. Unit: ms

Note: 

   Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes

   Before Firmwre v1.6.0 the latch time only suport 2 bytes.

Device will upload a packet if downlink code executes successfully.

Example payload:

1. A9 01 01 01 01 07 D0

DO1 pin & DO2 pin & DO3 pin will be set to Low, last 2 seconds, then change back to original state.

2. A9 01 00 01 11 07 D0

DO1 pin set high, DO2 pin set low, DO3 pin no action, last 2 seconds, then change back to original state.

3. A9 00 00 00 00 07 D0

DO1 pin & DO2 pin & DO3 pin will be set to high, last 2 seconds, then both change to low.

4. A9 00 11 01 00 07 D0

DO1 pin no action, DO2 pin set low, DO3 pin set high, last 2 seconds, then DO1 pin no action, DO2 pin set high, DO3 pin set low

3.4.2.14 Relay -- Control Relay Output RO1/RO2

• AT Command:

There is no AT Command to control Relay Output

• Downlink Payload (prefix 0x03):

0x03 aa bb      // Set RO1/RO2 output

Device will upload a packet if downlink code executes successfully.

3.4.2.15 Relay -- Control Relay Output RO1/RO2 with time control

• AT Command:

There is no AT Command to control Relay Output

• Downlink Payload (prefix 0x05):

0x05 aa bb cc dd      // Set RO1/RO2 relay with time control

This is to control the relay output time of relay. Include four bytes:

First Byte : Type code (0x05)

Second Byte(aa): Inverter Mode

01: Relays will change back to original state after timeout.

00: Relays will change to an inverter state after timeout

Third Byte(bb): Control Method and Ports status:

Fourth/Fifth/Sixth/Seventh Bytes(cc): Latching time. Unit: ms

Note:

   Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes

   Before Firmwre v1.6.0 the latch time only suport 2 bytes.

Device will upload a packet if downlink code executes successfully.

Example payload:

1. 05 01 11 07 D0

Relay1 and Relay 2 will be set to NC , last 2 seconds, then change back to original state.

2. 05 01 10 07 D0

Relay1 will change to NC, Relay2 will change to NO, last 2 seconds, then both change back to original state.

3. 05 00 01 07 D0

Relay1 will change to NO, Relay2 will change to NC, last 2 seconds, then relay change to NC,Relay2 change to NO.

4. 05 00 00 07 D0

Relay 1 & relay2 will change to NO, last 2 seconds, then both change to NC.

3.4.2.16 Counting -- Voltage threshold counting

When voltage exceed the threshold, count. Feature see MOD4

• AT Command: AT+VOLMAX    // See MOD4

• Downlink Payload (prefix 0xA5):

0xA5 aa bb cc    // Same as AT+VOLMAX=(aa bb),cc

3.4.2.17 Counting -- Pre-configure the Count Number

• AT Command: AT+SETCNT=aa,(bb cc dd ee) 

aa: 1: Set count1; 2: Set count2; 3: Set AV1 count

bb cc dd ee: number to be set

• Downlink Payload (prefix 0xA8):

0x A8 aa bb cc dd ee      // same as AT+SETCNT=aa,(bb cc dd ee)

3.4.2.18 Counting -- Clear Counting

Clear counting for counting mode

• AT Command: AT+CLRCOUNT          // clear all counting

• Downlink Payload (prefix 0xA6):

0x A6 01     // clear all counting

3.4.2.19 Counting -- Change counting mode to save time

• AT Command:

AT+COUTIME=60  // Set save time to 60 seconds. Device will save the counting result in internal flash every 60 seconds. (min value: 30)

• Downlink Payload (prefix 0xA7):

0x A7 aa bb cc      // same as AT+COUTIME =aa bb cc,

3.4.2.20 Reset save RO DO state

• AT Command:

AT+RODORESET=1    // RODO will close when the device joining the network. (default)

AT+RODORESET=0    // After the device is reset, the previously saved RODO state (only MOD2 to MOD5) is read, and its state is not changed when it is reconnected to the network. 

• Downlink Payload (prefix 0xAD):

0x AD aa       // same as AT+RODORET =aa

3.4.2.21 Encrypted payload

• AT Command:

AT+DECRYPT=1     // The payload is uploaded without encryption

AT+DECRYPT=0    //  Encrypt when uploading payload (default)

3.4.2.22 Get sensor value

• AT Command:

AT+GETSENSORVALUE=0    // The serial port gets the reading of the current sensor

AT+GETSENSORVALUE=1    // The serial port gets the current sensor reading and uploads it.

3.4.2.23 Resets the downlink packet count

• AT Command:

AT+DISFCNTCHECK=0   // When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node will no longer receive downlink packets (default)

AT+DISFCNTCHECK=1   // When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node resets the downlink packet count and keeps it consistent with the server downlink packet count.

3.4.2.24 When the limit bytes are exceeded, upload in batches

• AT Command:

AT+DISMACANS=0     // When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of 11 bytes (DR0 of US915, DR2 of AS923, DR2 of AU195), the node will send a packet with a payload of 00 and a port of 4. (default)

AT+DISMACANS=1      // When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of the DR, the node will ignore the MACANS and not reply, and only upload the payload part.

• Downlink Payload :

0x21 00 01          // Set  the DISMACANS=1

3.4.2.25 Copy downlink to uplink

• AT Command:

AT+RPL=5     // After receiving the package from the server, it will immediately upload the content of the package to the server, the port number is 100.

Example：aa xx xx xx xx         // aa indicates whether the configuration has changed, 00 is yes, 01 is no; xx xx xx xx are the bytes sent.

For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.

For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.

3.4.2.26 Query version number and frequency band 、TDC

• Downlink Payload:

  26 01     //  Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.

   

Example：

3.5 Integrating with ThingsEye.io

The Things Stack applications can be integrated with ThingsEye.io. Once integrated, ThingsEye.io works as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.

3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox

We use The Things Stack Sandbox for demonstating the configuration but  other 

• In The Things Stack Sandbox, select your application under Applications.
• Select MQTT under Integrations.
• In the Connection information section, for Username, The Things Stack displays an auto-generated username. You can use it or provide a new one.
• For the Password, click the Generate new API key button to generate a password. You can see it by clicking on the eye button. The API key works as the password.

NOTE. The username and  password (API key) you created here are required in the next section.

3.5.2 Configuring ThingsEye.io

This section guides you on how to create an integration in ThingsEye to connect with The Things Stack MQTT server. 

• Login to your ThingsEye.io account.
• Under the Integrations center, click Integrations.
• Click the Add integration button (the button with the + symbol).

On the Add integration window, configure the following:

Basic settings:

• Select The Things Stack Community from the Integration type list.
• Enter a suitable name for your integration in the Name text box or keep the default name.
• Ensure the following options are turned on.
  • Enable integration
  • Debug mode
  • Allow create devices or assets
• Click the Next button. you will be navigated to the Uplink data converter tab.

Uplink data converter:

• Click the Create new button if it is not selected by default.
• Enter a suitable name for the uplink data converter in the Name text box or keep the default name.
• Click the JavaScript button.
• Paste the uplink decoder function into the text area (first, delete the default code). The demo uplink decoder function can be found here.
• Click the Next button. You will be navigated to the Downlink data converter tab.

Downlink data converter (this is an optional step):

• Click the Create new button if it is not selected by default.
• Enter a suitable name for the downlink data converter in the Name text box or keep the default name
• Click the JavaScript button.
• Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found here.
• Click the Next button. You will be navigated to the Connection tab.

Connection:

• Choose Region from the Host type.
• 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/...).
• Enter the Username and Password of the MQTT integration in the Credentials section. The username and password can be found on the MQTT integration page of your The Things Stack account (see Configuring MQTT Connection information with The Things Stack Sandbox).
• Click the Check connection button to test the connection. If the connection is successful, you will see the message saying Connected.

• Click the Add button.

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.

Viewing integration details:

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.

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.

Note: See also ThingsEye documentation.

Viewing events:

This tab  displays all the uplink messages from the LT-22222-L.

• Click on the Events tab.
• Select Debug from the Event type dropdown.
• Select the time frame from the time window.

[insert image]

- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.

[insert image]

Deleting the integration:

If you want to delete this integration, click the Delete integration button.

3.6 Interface Details

3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active )

Support NPN-type sensor

3.6.2 Digital Input Ports: DI1/DI2 ( For LT-22222-L)

• Connect the sensor's output to DI1-

• Connect the sensor's VCC to DI1+.

• Connect the sensor's output to DI1+

• Connect the sensor's GND DI1-.

• Connect the sensor's output to DI1+ with a 50K resistor in series.

• Connect the sensor's GND DI1-.

Example4: Connecting to Dry Contact sensor

From the DI port circuit above, you can see that activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference.

To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.

Example5: Connecting to an Open Collector

3.6.3 Digital Output Ports: DO1/DO2 /DO3

NPN output: GND or Float. The maximum voltage that can be applied to the output pin is 36V.

Note: The DO pins will float when the device is powered off.

3.6.4 Analog Input Interfaces

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:

AC2 = (IN2 voltage )/12

Example:  Connecting a 4~20mA sensor

We will use the wind speed sensor as an example for reference only.

Specifications of the wind speed sensor:

Red:      12~24V

Yellow:  4~20mA

Black:   GND

Connection diagram:

Example: Connecting to a regulated power supply to measure voltage

Specifications of the regulated power supply:

Red:      12~24v

Black:   GND

3.6.5 Relay Output

3.7 LEDs Indicators

4. Using AT Command

4.1 Connecting the LT-22222-L to a computer

4.2 Common AT Command Sequence

4.2.1 Multi-channel ABP mode (Use with SX1301/LG308)

4.2.2 Single-channel ABP mode (Use with LG01/LG02)

4.2.3 Change to Class A

5. Case Study

5.1 Counting how many objects pass through the flow Line

Reference Link: How to set up to setup counting for objects passing through the flow line?

6. FAQ

6.1 How to upgrade the image?

The LT-22222-L I/O Controller is shipped with a 3.5mm cable, which is used to upload an image to LT in order to:

• Support new features.
• Fix bugs.
• Change LoRaWAN bands.

Below is the hardware connection setup for uploading an image to the LT:

Note: If you have lost the programming cable, you can make one from a 3.5mm cable. The pin mapping is as follows:

6.4 How to change the uplink interval?

Please see this link: http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/ 

6.5 Can I see the counting event in Serial?

7.4 Why can LT22222 perform Uplink normally, but cannot receive Downlink?

The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue state.
Use this command to bring their counts back together: Resets the downlink packet count

8. Order Info

LT-22222-L-XXX:

XXX:

• EU433:   LT with frequency bands EU433
• EU868:   LT with frequency bands EU868
• KR920:   LT with frequency bands KR920
• CN470:  LT with frequency bands CN470
• AS923:   LT with frequency bands AS923
• AU915:  LT with frequency bands AU915
• US915:  LT with frequency bands US915
• IN865:   LT with frequency bands IN865
• CN779:  LT with frequency bands CN779

9. Packing Info

Package Includes:

• LT-22222-L I/O Controller x 1
• Stick Antenna for LoRa RF part x 1
• Bracket for controller x1
• Program cable x 1

Dimension and weight:

• Device Size: 13.5 x 7 x 3 cm
• Device Weight: 105g
• Package Size / pcs : 14.5 x 8 x 5 cm
• Weight / pcs : 170g

10. Support

• Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.

• Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to Support@dragino.cc

   

11. Reference​​​​​

• LT-22222-L: http://www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html
• Datasheet, Document Base
• Hardware Source