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 < 172.1 >

edited by Dilisi S
on 2024/11/08 06:20

To version < 178.1 >

edited by Dilisi S
on 2024/11/09 02:59

Change comment: Nov 8 edits - part 1

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -33,8 +33,6 @@
  With the LT-22222-L 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.
  )))
--> The LT Series I/O Controllers are designed for easy, low-cost installation on LoRaWAN networks.
--
  (((
  You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways:
@@ -59,7 +59,7 @@
  * SX1276/78 Wireless Chip
  * Power Consumption:
  ** Idle: 4mA@12v
--** 20dB Transmit: 34mA@12v
++** 20dB Transmit: 34mA@12V
  * Operating Temperature: -40 ~~ 85 Degrees, No Dew
  (% style="color:#037691" %)**Interface for Model: LT22222-L:**
@@ -68,7 +68,7 @@
  * 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)
++* 2 x 0~~30V Analog Input (res:0.01V)
  * Power Input 7~~ 24V DC.
  (% style="color:#037691" %)**LoRa Spec:**
@@ -136,10 +136,10 @@
  * 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 bracket for DIN rail 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.
++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 ==
@@ -171,7 +171,7 @@
  == 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.
++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.
  [[image:1653297104069-180.png]]
@@ -183,13 +183,13 @@
  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.
++After powering on, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** the LoRaWAN network. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LE**D will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status.
  In case you can't set the root key and other identifiers in the network server and must use them from the server, you can use [[AT Commands>>||anchor="H4.UseATCommand"]] to configure them on the device.
  == 3.2 Registering with a LoRaWAN network server ==
--The diagram below shows how the LT-22222-L connects to a typical LoRaWAN network.
++The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
  [[image:image-20220523172350-1.png||height="266" width="864"]]
@@ -207,8 +207,11 @@
  * 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: ====
++(% class="wikigeneratedid" %)
++====   ====
++==== 3.2.2.1 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**.
@@ -217,7 +217,8 @@
  [[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
--*
++
++* Page continued...
  ** 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.
@@ -226,8 +226,11 @@
  [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
--==== Entering device information manually: ====
++(% class="wikigeneratedid" %)
++====   ====
++==== 3.2.2.2 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.
@@ -240,26 +240,49 @@
  [[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
--* 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.
++* Page continued...
++** 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.
  [[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
--==== Joining ====
++You will be navigated to the **Device overview** page.
--Click on **Live Data** in the left navigation. Then, power on the device, and it will join The Things Stack Sandbox. You can see the join request, join accept, followed by uplink messages form the device showing in the Live Data panel.
--[[image:1653298044601-602.png||height="405" width="709"]]
++[[image:lt-22222-device-overview.png||height="625" width="1000"]]
++==== 3.2.2.3 Joining ====
++
++Click on **Live data** in the left navigation. The Live data panel for your application will display.
++
++Power on your LT-22222-L. It will begin joining The Things Stack LoRaWAN network server. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. Once successfully joined, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**).
++
++
++[[image:lt-22222-join-network.png||height="625" width="1000"]]
++
++
++By default, you will receive an uplink data message every 10 minutes.
++
++Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the decode_payload {} JSON object.
++
++[[image:lt-22222-ul-payload-decoded.png]]
++
++
++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.
++
++[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
++
++
  == 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.
++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 work 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
@@ -273,11 +273,16 @@
  * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5
++
++The uplink messages are sent over LoRaWAN FPort 2. By default, an uplink message is sent every 10 minutes.
++
  === 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" %)
++This is the default mode.
++The uplink payload is 11 bytes long. (% 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**
  |Value|(((
@@ -324,13 +324,13 @@
  * [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.
++* **[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.
++* **[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+.
@@ -355,7 +355,7 @@
  )))
  (((
--(% 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, FIRST, Reserve, Reserve, DO3, DO2 and DO1, and its size is 1 byte long 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**
@@ -1353,19 +1353,25 @@
  == 3.5 Integrating with ThingsEye.io ==
--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.
++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.
++* 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.
++
  [[image:tts-mqtt-integration.png||height="625" width="1000"]]
  === 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 >>https://thingseye.io]]account.
  * Under the **Integrations center**, click **Integrations**.
  * Click the **Add integration** button (the button with the **+** symbol).
@@ -1375,7 +1375,7 @@
  On the **Add integration** window, 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.
@@ -1388,62 +1388,69 @@
  [[image:thingseye-io-step-2.png||height="625" width="1000"]]
--2. **Uplink data converter:**
++**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 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]].
++* 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]].
  * 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.
--* Paste the downlink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
++* 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.
  [[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 **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
++
++[[image:message-1.png]]
++
++
  * 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 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.
--[[image:thingseye-io-step-6.png||height="625" width="1000"]]
++[[image:thingseye.io_integrationsCenter_integrations.png||height="686" 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.
++**Viewing integration details**:
--[add image here]
++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.
++[[image:integration-details.png||height="686" width="1000"]]
--[add image here]
--Once you have done click on the Apply changes button.
++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.
--Click on the Events tab.
--- Select Debug from the Event type dropdown.
++**Viewing events:**
--- Select the time frame from the time window.
++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.
@@ -1451,9 +1451,9 @@
  [insert image]
--Deleting the integration:
++**Deleting the integration**:
--If you want to delete this integration, click the Delete integration button.
++If you want to delete this integration, click the **Delete integratio**n button.
  == 3.6 Interface Details ==
@@ -1711,7 +1711,7 @@
  (((
--On the PC, the user needs to set the (% style="color:#4f81bd" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) to a baud rate of (% style="color:green" %)**9600**(%%) to access to access serial console of LT-22222-L. The AT commands are disabled by default, and a password (default:(% style="color:green" %)**123456**)(%%) must be entered to active them, as shown below:
++On the PC, the user needs 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. The AT commands are disabled by default, and a password (default:(% style="color:green" %)**123456**)(%%) must be entered to active them, as shown below:
  )))
  [[image:1653358355238-883.png]]
@@ -2056,7 +2056,7 @@
  = 6. FAQ =
--== 6.1 How to upgrade the image? ==
++== 6.1 How to upgrade the firmware 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:
@@ -2065,20 +2065,25 @@
  * Fix bugs.
  * Change LoRaWAN bands.
--Below is the hardware connection setup for uploading an image to the LT:
++Below is the hardware connection setup for uploading an firmware image to the LT-22222-L:
++(% class="box infomessage" %)
++(((
++The latest firmware version available for the LT-22222-L is v1.6.1 at the time of this writing.
++)))
++
  [[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 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]]. (replaced by STM32CubeProgrammer)
  (% 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" %)**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, 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.
  )))

integration-details.png

Author

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

Size

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

Content

thingseye.io_integrationsCenter_integrations-2.png

Author

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

Size

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

Content

thingseye.io_integrationsCenter_integrations.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation