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

Last modified by Saxer Lin on 2025/04/15 17:24

From version < 167.1 >

edited by Dilisi S
on 2024/11/07 23:09

To version < 163.1 >

edited by Dilisi S
on 2024/11/06 04:29

Change comment: minor edits set 1

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -40,7 +40,7 @@
  * If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Network), you can select a network and register the LT-22222-L I/O controller with it.
  * If there is no public LoRaWAN coverage in your area, you can set up a LoRaWAN gateway, or multiple gateways, and connect them to a LoRaWAN network server to create adequate coverage. Then, register the LT-22222-L I/O controller with this network.
--* Setup your own private LoRaWAN network.
++* Set up your own private LoRaWAN network.
  > You can use a LoRaWAN gateway, such as the Dragino LG308, to expand or create LoRaWAN coverage in your area.
  )))
@@ -169,7 +169,7 @@
  |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
  |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
--== 2.3 Powering the LT-22222-L ==
++== 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.
@@ -256,12 +256,12 @@
  [[image:1653298044601-602.png||height="405" width="709"]]
--== 3.3 Work Modes and their Uplink Payload formats ==
++== 3.3 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.
++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.
--* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO
++* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2 x ACI + 2AVI + DI + DO + RO
  * (% style="color:blue" %)**MOD2**(%%): Double DI Counting + DO + RO
@@ -275,8 +275,9 @@
  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
++
  (((
--The uplink payload is 11 bytes long. Uplink messages are sent over LoRaWAN FPort 2. By default, one uplink is sent every 10 minutes. (% style="display:none" wfd-invisible="true" %)
++The uplink payload is 11 bytes long. Uplink packets are sent over LoRaWAN FPort=2. By default, one uplink is sent every 10 minutes. (% style="display:none" wfd-invisible="true" %)
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
  |(% 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**
@@ -288,13 +288,13 @@
  ACI1 Current
  )))|(((
  ACI2 Current
--)))|**DIDORO***|(((
++)))|DIDORO*|(((
  Reserve
  )))|MOD
  )))
  (((
--(% 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.
++(% 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.
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
@@ -301,9 +301,9 @@
  |RO1|RO2|--DI3--|DI2|DI1|--DO3--|DO2|DO1
  )))
--* 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.
++* 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: output low, DOx=0: high or floating.
  (% style="color:red" %)**Note: DI3 and DO3 bits are not valid for LT-22222-L**
@@ -341,7 +341,7 @@
  (((
--**For LT-22222-L**: In this mode, **DI1 and DI2** are used as counting pins.
++**For LT-22222-L**: In this mode, the **DI1 and DI2** are used as counting pins.
  )))
  (((
@@ -355,17 +355,17 @@
  )))
  (((
--(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, DO3, DO2 and DO1, and its size is 1 byte long as shown below.
++(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
  |RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1
--* RO is for the relay. ROx=1: CLOSED,  ROx=0 always OPEN.
++* 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: LOW, DOx=0: HIGH or FLOATING.
++* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
  (((
  (% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L**
@@ -592,6 +592,7 @@
 . Periodically uplink (Based on TDC time). The payload is the same as in normal mode (MOD=1 for the commands above). These are (% style="color:#4f81bd" %)**unconfirmed**(%%) uplinks.
 . 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 (% style="color:#4f81bd" %)**CONFIRMED uplinks.**
++
  (% style="color:#037691" %)**AT Command to set Trigger Condition**:
  (% style="color:#4f81bd" %)**Trigger based on voltage**:
@@ -601,9 +601,9 @@
  **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=3000,6000,0,2000   (If AVI1 voltage lower than 3v or higher than 6v.  or AV2 voltage is higher than 2v, LT will trigger Uplink)
--AT+AVLIM=5000,0,0,0   (triggers an uplink if AVI1 voltage lower than 5V. Use 0 for parameters that are not in use)
++AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
  (% style="color:#4f81bd" %)**Trigger based on current**:
@@ -613,12 +613,12 @@
  **Example:**
--AT+ACLIM=10000,15000,0,0   (triggers an uplink if ACI1 voltage is lower than 10mA or higher than 15mA)
++AT+ACLIM=10000,15000,0,0   (If ACI1 voltage lower than 10mA or higher than 15mA, trigger an uplink)
--(% style="color:#4f81bd" %)**Trigger based on DI status**:
++(% style="color:#4f81bd" %)**Trigger base on DI status**:
--DI status triggers Flag.
++DI status trigger Flag.
  Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >
@@ -628,38 +628,39 @@
  AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
--(% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
++(% style="color:#037691" %)**Downlink Command to set Trigger Condition:**
  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:
++  AA: Code for this downlink Command:
--  xx: **0**: Limit for AV1 and AV2; **1**: limit for AC1 and AC2; **2**: DI1and DI2 trigger enable/disable.
++  xx: 0: Limit for AV1 and AV2;  1: limit for AC1 and AC2 ; 2 DI1, DI2 trigger enable/disable
--  yy1 yy1: AC1 or AV1 LOW limit or DI1/DI2 trigger status.
++  yy1 yy1: AC1 or AV1 low limit or DI1/DI2 trigger status.
--  yy2 yy2: AC1 or AV1 HIGH limit.
++  yy2 yy2: AC1 or AV1 high limit.
--  yy3 yy3: AC2 or AV2 LOW limit.
++  yy3 yy3: AC2 or AV2 low limit.
--  Yy4 yy4: AC2 or AV2 HIGH limit.
++  Yy4 yy4: AC2 or AV2 high limit.
--**Example 1**: AA 00 13 88 00 00 00 00 00 00
++**Example1**: 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)
++Same as AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
--**Example 2**: AA 02 01 00
++**Example2**: AA 02 01 00
--Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
++Same as AT+ DTRI =1,0  (Enable DI1 trigger / disable DI2 trigger)
++
  (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:**
--MOD6 Payload: total of 11 bytes
++MOD6 Payload : total 11 bytes payload
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
  |(% 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**
@@ -673,10 +673,10 @@
  MOD(6)
  )))
--(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
++(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if trigger is set for this part. Totally 1byte as below
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
--|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
++|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
  |(((
  AV1_LOW
  )))|(((
@@ -695,17 +695,17 @@
  AC2_HIGH
  )))
--* Each bit shows if the corresponding trigger has been configured.
++* Each bits shows if the corresponding trigger has been configured.
  **Example:**
--10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
++10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW
--(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
++(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1byte as below
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
--|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
++|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
  |(((
  AV1_LOW
  )))|(((
@@ -724,11 +724,11 @@
  AC2_HIGH
  )))
--* Each bit shows which status has been triggered on this uplink.
++* Each bits shows which status has been trigger on this uplink.
  **Example:**
--10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
++10000000: Means this packet is trigger by AC1_LOW. Means voltage too low.
  (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
@@ -737,7 +737,7 @@
  |**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
  |N/A|N/A|N/A|N/A|DI2_STATUS|DI2_FLAG|DI1_STATUS|DI1_FLAG
--* Each bits shows which status has been triggered on this uplink.
++* Each bits shows which status has been trigger on this uplink.
  **Example:**
@@ -764,11 +764,11 @@
  )))
--== 3.4 Configure LT via AT Commands or Downlinks ==
++== 3.4 Configure LT via AT or Downlink ==
  (((
--User can configure LT I/O Controller via AT Commands or LoRaWAN Downlinks.
++User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands
  )))
  (((
@@ -783,8 +783,9 @@
  === 3.4.1 Common Commands ===
++
  (((
--These commands should be available for all Dragino sensors, 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]].
++They should be available for each of Dragino Sensors, 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>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
  )))
@@ -792,37 +792,34 @@
  ==== 3.4.2.1 Set Transmit Interval ====
--Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
--* (% style="color:#037691" %)**AT command:**
++Set device uplink interval.
--(% style="color:blue" %)**AT+TDC=N**
++* (% style="color:#037691" %)**AT Command:**
--where N is the time in milliseconds.
++(% style="color:blue" %)**AT+TDC=N **
--**Example: **AT+TDC=30000. This will set the uplink interval to 30 seconds
++**Example: **AT+TDC=30000. Means set interval to 30 seconds
--* (% style="color:#037691" %)**Downlink payload (prefix 0x01):**
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x01):**
++
  (% style="color:blue" %)**0x01 aa bb cc  **(%%)**   ~/~/ Same as AT+TDC=0x(aa bb cc)**
--==== 3.4.2.2 Set the Work Mode (AT+MOD) ====
++==== 3.4.2.2 Set Work Mode (AT+MOD) ====
--Sets the work mode.
++Set work mode.
--* (% style="color:#037691" %)**AT command:**(%%) (% style="color:blue" %)**AT+MOD=N  **
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+MOD=N  **
--Where N is the work mode.
++**Example**: AT+MOD=2. Set work mode to Double DI counting mode
--**Example**: AT+MOD=2. This will set the work mode to Double DI counting mode.
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A):**
--
--* (% style="color:#037691" %)**Downlink payload (prefix 0x0A):**
--
  (% style="color:blue" %)**0x0A aa  **(%%)**  ** ~/~/ Same as AT+MOD=aa
@@ -830,12 +830,10 @@
  ==== 3.4.2.3 Poll an uplink ====
--Asks the device to send an uplink.
++* (% style="color:#037691" %)**AT Command:**(%%) There is no AT Command to poll uplink
--* (% style="color:#037691" %)**AT command:**(%%) There is no AT Command to poll uplink
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x08):**
--* (% style="color:#037691" %)**Downlink payload (prefix 0x08):**
--
  (% style="color:blue" %)**0x08 FF  **(%%)**   **~/~/ Poll an uplink
  **Example**: 0x08FF, ask device to send an Uplink
@@ -842,16 +842,16 @@
--==== 3.4.2.4 Enable/Disable Trigger Mode ====
++==== 3.4.2.4 Enable Trigger Mode ====
--Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
++Use of trigger mode, please check [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0**
--(% style="color:red" %)**1:** (%%)Enable the trigger mode
++(% style="color:red" %)**1:** (%%)Enable Trigger Mode
--(% style="color:red" %)**0: **(%%)Disable the trigger mode
++(% style="color:red" %)**0: **(%%)Disable Trigger Mode
  * (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):**
@@ -863,7 +863,7 @@
  ==== 3.4.2.5 Poll trigger settings ====
--Polls the trigger settings
++Poll trigger settings
  * (% style="color:#037691" %)**AT Command:**
@@ -871,7 +871,7 @@
  * (% style="color:#037691" %)**Downlink Payload (prefix 0x AB 06):**
--(% style="color:blue" %)**0xAB 06  **  (%%)   ~/~/ Poll the trigger settings. Device will uplink trigger settings once receive this command
++(% style="color:blue" %)**0xAB 06  **  (%%)   ~/~/ Poll trigger settings, device will uplink trigger settings once receive this command
@@ -878,11 +878,11 @@
  ==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ====
--Enable or Disable DI1/DI2/DI2 as trigger,
++Enable Disable DI1/DI2/DI2 as trigger,
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
--**Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
++**Example:** AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):**
@@ -914,15 +914,15 @@
  ==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
--Sets DI2 trigger.
++Set DI2 trigger.
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
--(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
++(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
  (% style="color:red" %)**b :** (%%)delay timing.
--**Example:** AT+TRIG2=0,100 (set DI1 port to trigger on low level, valid signal is 100ms )
++**Example:** AT+TRIG2=0,100(set DI1 port to trigger on low level, valid signal is 100ms )
  * (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):**
@@ -960,7 +960,7 @@
  ==== 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.
++Set AV and AC trigger minimum interval, system won't response to the second trigger within this set time after the first trigger.
  * (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+ATDC=5        ** ~/~/ (%%)Device won't response the second trigger within 5 minute after the first trigger.
@@ -1108,7 +1108,7 @@
  )))
  (((
--00: Closed ,  01: Open , 11: No action
++00: Close ,  01: Open , 11: No action
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
  |(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2**
@@ -1230,7 +1230,7 @@
--==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
++==== 3.4.2.19 Counting ~-~- Change counting mode save time ====
  * (% style="color:#037691" %)**AT Command:**
@@ -1355,107 +1355,67 @@
  If you are using one of The Things Stack plans, you can integrate ThingsEye.io with your application. 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 ===
++=== 3.5.1 Configuring The Things Stack Sandbox ===
--* 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.
++* Go to your Application and select MQTT under Integrations.
++* In the Connection credentials section, under Username, The Thins 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.
  [[image:tts-mqtt-integration.png||height="625" width="1000"]]
  === 3.5.2 Configuring ThingsEye.io ===
--* Login to your [[ThingsEye.io >>https://thingseye.io]]account.
--* Under the **Integrations center**, click **Integrations**.
--* Click the **Add integration** button (the button with the **+** symbol).
++* Login to your thingsEye.io account.
++* Under the Integrations center, click Integrations.
++* Click the Add integration button (the button with the + symbol).
  [[image:thingseye-io-step-1.png||height="625" width="1000"]]
--On the **Add integration** window, configure the following:
++On the Add integration page configure the following:
--~1. **Basic settings:**
++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.
++* Select The Things Stack Community from the Integration type list.
++* Enter a suitable name for your integration in the Name box or keep the default name.
++* Click the Next button.
  [[image:thingseye-io-step-2.png||height="625" width="1000"]]
++Uplink Data converter:
--2. **Uplink data converter:**
++* Click the Create New button if it is not selected by default.
++* Click the JavaScript button.
++* Paste the uplink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
++* Click the Next button.
--* 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 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]].
--* Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
--
  [[image:thingseye-io-step-3.png||height="625" width="1000"]]
--3.** Downlink data converter (this is an optional step):**
++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.
++* Click the Create new button if it is not selected by default.
++* Click the JavaScript button.
  * Paste the downlink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
--* Click the **Next** button. You will be navigated to the **Connection** tab.
++* Click the Next button.
  [[image:thingseye-io-step-4.png||height="625" width="1000"]]
--4. **Connection:**
++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 can see the message saying **Connected**.
--* Click the **Add** button.
++* Choose Region from the Host type.
++* Enter the cluster of your The Things Stack in the Region textbox.
++* Enter the Username and Password in the Credentials section. Use the same username and password you created with the MQTT page of The Things Stack.
++* Click Check connection to test the connection. If the connection is successful, you can see the message saying Connected.
++* Click the Add button.
  [[image:thingseye-io-step-5.png||height="625" width="1000"]]
--Your integration is added to the** Integrations** list and it will display on the **Integrations** page. Check whether the status is showing as 'Active'. if not, check your configuration settings again.
++Your integration is added to the integrations list and it will display on the Integrations page.
  [[image:thingseye-io-step-6.png||height="625" width="1000"]]
--Viewing integration details:
--
--Click on the 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.
--
--[add image here]
--
--If you want to edit the settings you have provided, click on the Toggle edit mode button.
--
--[add image here]
--
--Once you have done click on the Apply changes button.
--
--Note: See also ThingsEye documentation.
--
--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 ) ===
@@ -2048,10 +2048,10 @@
  = 5. Case Study =
--== 5.1 Counting how many objects pass through the flow Line ==
++== 5.1 Counting how many objects pass in Flow Line ==
--Reference Link: [[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]]?
++Reference Link: [[How to set up to count objects pass in flow line>>How to set up to count objects pass in flow line]]?
  = 6. FAQ =
@@ -2059,26 +2059,26 @@
  == 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:
++The LT LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to LT to:
--* Support new features.
--* Fix bugs.
++* Support new features
++* For bug fix
  * Change LoRaWAN bands.
--Below is the hardware connection setup for uploading an image to the LT:
++Below is the hardware connection for how to upload an image to the LT:
  [[image:1653359603330-121.png]]
  (((
--(% style="color:#0000ff" %)**Step 1**(%%)**:** Download the F[[lash 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]].
--(% style="color:#0000ff" %)**Step 2**(%%)**:** Download the [[LT Image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]].
--(% style="color:#0000ff" %)**Step 3**(%%)**:** Open the Flash Loader and choose the correct COM port to update.
++(% style="color:blue" %)**Step1**(%%)**:** Download [[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]].
++(% style="color:blue" %)**Step2**(%%)**:** Download the [[LT Image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]].
++(% style="color:blue" %)**Step3**(%%)**:** Open flashloader; choose the correct COM port to update.
  (((
  (% style="color:blue" %)**For LT-22222-L**(%%):
--Hold down the PRO button, then momentarily press the RST reset button. The (% style="color:red" %)**DO1 LED**(%%) will change from OFF to ON. When the (% style="color:red" %)**DO1 LED**(%%) is ON, it indicates that the device is in download mode.
++Hold down the PRO button and then momentarily press the RST reset button and the (% style="color:red" %)**DO1 led**(%%) will change from OFF to ON. When (% style="color:red" %)**DO1 LED**(%%) is on, it means the device is in download mode.
  )))
@@ -2093,7 +2093,7 @@
  [[image:image-20220524104033-15.png]]
--(% style="color:red" %)**Note**(%%): If you have lost the programming cable, you can make one from a 3.5mm cable. The pin mapping is as follows:
++(% style="color:red" %)**Notice**(%%): In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
  [[image:1653360054704-518.png||height="186" width="745"]]
@@ -2107,13 +2107,13 @@
  )))
  (((
--You can follow the introductions on [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file.
++User can follow the introduction for [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
  )))
  (((
--== 6.3 How to set up LT to work with a Single Channel Gateway, such as LG01/LG02? ==
++== 6.3 How to set up LT to work with Single Channel Gateway such as LG01/LG02? ==
  )))
@@ -2120,13 +2120,13 @@
  (((
  (((
--In this case, you need to set the LT-33222-L to work in ABP mode and transmit on only one frequency.
++In this case, users need to set LT-33222-L to work in ABP mode & transmit in only one frequency.
  )))
  )))
  (((
  (((
--Assume you have an LG02 working on the frequency 868400000. Below are the steps.
++Assume we have a LG02 working in the frequency 868400000 now , below is the step.
  )))
@@ -2133,7 +2133,7 @@
  )))
  (((
--(% style="color:#0000ff" %)**Step 1**(%%):  Log in to The Things Stack SANDBOX, create an ABP device in the application, and input the Network Session key (NwkSKey), App session key (AppSKey) of the device.
++(% style="color:blue" %)**Step1**(%%):  Log in TTN, Create an ABP device in the application and input the network session key (NETSKEY), app session key (APPSKEY) from the device.
  )))
@@ -2190,7 +2190,7 @@
  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/]]
--== 6.5 Can I see the counting event in Serial? ==
++== 6.5 Can I see counting event in Serial? ==
  (((
@@ -2197,10 +2197,10 @@
  User can run AT+DEBUG command to see the counting event in serial. If firmware too old and doesn't support AT+DEBUG. User can update to latest firmware first.
--== 6.6 Can I use point-to-point communication with LT-22222-L? ==
++== 6.6 Can i use point to point communication for LT-22222-L? ==
--Yes, please refer [[Point to Point Communication>>doc:Main. Point to Point Communication of LT-22222-L.WebHome]]. this is [[firmware>>https://github.com/dragino/LT-22222-L/releases]].
++Yes, please refer [[Point to Point Communication>>doc:Main. Point to Point Communication of LT-22222-L.WebHome]]  ，this is [[firmware>>https://github.com/dragino/LT-22222-L/releases]].
  )))

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

Summary

Details

Applications

Navigation