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

edited by Dilisi S
on 2024/11/22 04:26

To version < 210.1 >

edited by Dilisi S
on 2024/11/24 00:36

Change comment: fix toc

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -43,16 +43,12 @@
  * If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Stack Community Network), you can select a network and register the LT-22222-L I/O controller with it.
  * 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.
--
--{{info}}
-- You can use a LoRaWAN gateway, such as the [[Dragino LG308>>https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], to expand or create LoRaWAN coverage in your area.
--{{/info}}
  )))
  (((
--The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
++The network diagram below illustrates how the LT-22222-L communicates with a typical LoRaWAN network.
  )))
  (% class="wikigeneratedid" %)
@@ -140,17 +140,17 @@
  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.
  {{warning}}
--Warning! Do not power on the device without connecting the antenna.
++**Warning! Do not power on the device without connecting the antenna.**
  {{/warning}}
  == 2.2 Terminals ==
--The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 terminals and the lower screw terminal block has 10 terminals.
++The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals.
--Upper screw terminal block (from left to right):
++**Upper screw terminal block (from left to right):**
  (% style="width:634px" %)
--|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function
++|=(% style="width: 295px;" %)Screw Terminal|=(% style="width: 338px;" %)Function
  |(% style="width:295px" %)GND|(% style="width:338px" %)Ground
  |(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage
  |(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2
@@ -158,10 +158,10 @@
  |(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2
  |(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1
--Lower screw terminal block (from left to right):
++**Lower screw terminal block (from left to right):**
  (% style="width:633px" %)
--|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function
++|=(% style="width: 296px;" %)Screw Terminal|=(% style="width: 334px;" %)Function
  |(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1
  |(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1
  |(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2
@@ -213,10 +213,14 @@
  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.
--[[image:dragino-ttn-te.jpg]]
++[[image:dragino-lorawan-nw-lt-22222-n.jpg]]
++{{info}}
++ 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.
++{{/info}}
++
  ==== 3.2.2.1 Setting up ====
  * Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet.
@@ -225,7 +225,6 @@
  * Go to your application's page and click on the **End devices** in the left menu.
  * On the End devices page, click on **+ Register end device**. Two registration options are available:
--
  ==== 3.2.2.2 Using the LoRaWAN Device Repository ====
  * On the **Register end device** page:
@@ -250,7 +250,6 @@
  [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
--====   ====
  ==== 3.2.2.3 Adding device manually ====
@@ -285,7 +285,7 @@
  ==== 3.2.2.4 Joining ====
--On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
++On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
  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.
@@ -303,7 +303,7 @@
  [[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.
++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.
  {{info}}
  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.
@@ -1169,8 +1169,8 @@
  )))
  |(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
--====   ====
++
  ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
  Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
@@ -1352,8 +1352,8 @@
  )))
  )))
--====   ====
++
  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
@@ -1606,7 +1606,7 @@
  ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ====
--This feature allows users to pre-configure specific count numbers for various counting parameters such as Count1, Count2, or AVI1 Count. Use the AT command to set the desired count number for each configuration.
++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.
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) **
@@ -1667,7 +1667,7 @@
  ==== 3.4.2.18 Counting ~-~- Clear Counting ====
--This feature clears the counting in counting mode.
++This command clears the counting in counting mode.
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
@@ -1694,7 +1694,7 @@
  ==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
--This feature allows you to configure the device to save its counting result to internal flash memory at specified intervals. By setting a save time, the device will periodically store the counting data to prevent loss in case of power failure. The save interval can be adjusted to suit your requirements, with a minimum value of 30 seconds.
++This command allows you to configure the device to save its counting result to internal flash memory at specified intervals. By setting a save time, the device will periodically store the counting data to prevent loss in case of power failure. The save interval can be adjusted to suit your requirements, with a minimum value of 30 seconds.
  * (% style="color:#037691" %)**AT Command:**
@@ -1737,10 +1737,9 @@
  Sets the device to save its counting results to the memory every 60 seconds.
  )))
--
  ==== 3.4.2.20 Reset save RO DO state ====
--This feature allows you to reset the saved relay output (RO) and digital output (DO) states when the device joins the network. By configuring this setting, you can control whether the device should retain or reset the relay states after a reset and rejoin to the network.
++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.
  * (% style="color:#037691" %)**AT Command:**
@@ -1758,11 +1758,11 @@
  |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state>
  |(% style="width:127px" %)**Response**|(% style="width:371px" %)
  |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
--state :
++**state** :
--0 : RODO will close when the device joins the network. (default)
++**0** : RODO will close when the device joins the network. (default)
--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.
++**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.
  )))
  |(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
  (% style="color:blue" %)**AT+RODORESET=1 **
@@ -1774,17 +1774,16 @@
  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.
  )))
--
  (% border="2" style="width:500px" %)
  |(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state>
  |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
--prefix : AD
++**prefix** : AD
--state :
++**state** :
--0 : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal.
++**0** : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal.
--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
++**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
  )))
  |(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
  AD **01**
@@ -1796,10 +1796,9 @@
  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.
  )))
--
  ==== 3.4.2.21 Encrypted payload ====
--This feature allows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption.
++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.
  * (% style="color:#037691" %)**AT Command:**
@@ -1808,9 +1808,32 @@
  (% style="color:blue" %)**AT+DECRYPT=0    **(%%)~/~/  Encrypt when uploading payload (default)
++(% border="2" style="width:500px" %)
++|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state>
++|(% style="width:127px" %)**Response**|(% style="width:371px" %)
++|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
++state :
++1 : The payload is uploaded without encryption
++
++0 : The payload is encrypted when uploaded (default)
++)))
++|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
++AT+DECRYPT=1
++
++The payload is uploaded without encryption
++
++AT+DECRYPT=0
++
++The payload is encrypted when uploaded (default)
++)))
++
++There is no downlink payload for this configuration.
++
++
  ==== 3.4.2.22 Get sensor value ====
++This command allows you to retrieve and optionally uplink sensor readings through the serial port.
  * (% style="color:#037691" %)**AT Command:**
@@ -1819,10 +1819,33 @@
  (% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.
++(% border="2" style="width:500px" %)
++|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
++|(% style="width:127px" %)**Response**|(% style="width:371px" %)
++|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
++**state** :
--==== 3.4.2.23 Resets the downlink packet count ====
++**0 **: Retrieves the current sensor reading via the serial port.
++**1 **: Retrieves and uploads the current sensor reading via the serial port.
++)))
++|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
++AT+GETSENSORVALUE=0
++Retrieves the current sensor reading via the serial port.
++
++AT+GETSENSORVALUE=1
++
++Retrieves and uplinks the current sensor reading via the serial port.
++)))
++
++There is no downlink payload for this configuration.
++
++
++==== 3.4.2.23 Resetting the downlink packet count ====
++
++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.
++
  * (% style="color:#037691" %)**AT Command:**
  (% style="color:blue" %)**AT+DISFCNTCHECK=0   **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node will no longer receive downlink packets (default)
@@ -1830,10 +1830,37 @@
  (% style="color:blue" %)**AT+DISFCNTCHECK=1   **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node resets the downlink packet count and keeps it consistent with the server downlink packet count.
++(% border="2" style="width:500px" %)
++|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
++|(% style="width:130px" %)**Response**|(% style="width:368px" %)(((
++
++)))
++|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)(((
++**state **:
++**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).
++
++
++**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.
++)))
++|(% style="width:130px" %)**Example**|(% style="width:368px" %)(((
++AT+DISFCNTCHECK=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).
++
++AT+DISFCNTCHECK=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.
++)))
++
++There is no downlink payload for this configuration.
++
++
  ==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ====
++This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceeds the allowed byte limit for the current data rate (DR). The command provides two modes: one enables splitting the data into batches to ensure compliance with the byte limit, while the other prioritizes the payload and ignores the MACANS in cases of overflow.
++
  * (% style="color:#037691" %)**AT Command:**
  (% style="color:blue" %)**AT+DISMACANS=0**   (%%)  ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of 11 bytes (DR0 of US915, DR2 of AS923, DR2 of AU195), the node will send a packet with a payload of 00 and a port of 4. (default)
@@ -1845,10 +1845,50 @@
  (% style="color:blue" %)**0x21 00 01 **   (%%)      ~/~/ Set  the DISMACANS=1
++(% style="color:#037691" %)**AT Command**
++(% border="2" style="width:500px" %)
++|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state>
++|(% style="width:127px" %)**Response**|(% style="width:371px" %)
++|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
++**state** :
++**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)
++
++**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.
++)))
++|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
++AT+DISMACANS=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)
++
++AT+DISMACANS=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.
++)))
++
++(% style="color:#037691" %)**Downlink Payload**
++
++(% border="2" style="width:500px" %)
++|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state>
++|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)(((
++**prefix** : 21
++
++**state** : (2 bytes in hexadecimal)
++
++**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)
++
++**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.
++)))
++|(% style="width:126px" %)**Example**|(% style="width:372px" %)(((
++21 **00 01**
++
++Set DISMACANS=1
++)))
++
  ==== 3.4.2.25 Copy downlink to uplink ====
++This command enables the device to immediately uplink the content of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100.
  * (% style="color:#037691" %)**AT Command**(%%)**:**
@@ -1861,8 +1861,22 @@
  For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
++(% border="2" style="width:500px" %)
++|(% style="width:122px" %)**Command**|(% style="width:376px" %)(((
++AT+RPL=5
++After receiving a downlink packet from the server, the node immediately uplinks the content of the packet back to the server using port number 100.
++)))
++|(% style="width:122px" %)**Example**|(% style="width:376px" %)(((
++Downlink:
++01 00 02 58
++
++Uplink:
++
++01 01 00 02 58
++)))
++
  [[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"]]
  For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
@@ -1869,14 +1869,16 @@
--==== 3.4.2.26 Query version number and frequency band 、TDC ====
++==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
++This command is used to query key information about the device, including its firmware version, frequency band, sub band, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device.
  * (((
  (% style="color:#037691" %)**Downlink Payload**(%%)**:**
--(% style="color:blue" %)**26 01  ** (%%)  ~/~/  Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
++(% style="color:blue" %)**26 01  ** (%%)  ~/~/  The downlink payload 26 01 is used to query the device's firmware version, frequency band, sub band, and TDC time.
++
  )))
@@ -1906,6 +1906,8 @@
  === 3.5.2 Configuring ThingsEye.io ===
++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.
++
  * 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).
@@ -1954,7 +1954,7 @@
  * 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 The Things Stack).
++* 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**).
  * 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]]
@@ -1965,7 +1965,7 @@
  [[image:thingseye-io-step-5.png||height="625" width="1000"]]
--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.
++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.
  [[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
@@ -1981,7 +1981,7 @@
  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.
  {{info}}
--See also ThingsEye documentation.
++See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
  {{/info}}
  ==== **3.5.2.2 Viewing events** ====
@@ -1994,7 +1994,7 @@
  [[image:thingseye-events.png||height="686" width="1000"]]
--* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
++* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
  [[image:thingseye-json.png||width="1000"]]
@@ -2004,6 +2004,11 @@
  If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
++==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
++
++This will be added soon.
++
++
  == 3.6 Interface Details ==
  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===

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

Summary

Details

Applications

Navigation