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

edited by Dilisi S
on 2024/11/06 22:47

Change comment: some minor edits on 6th nov. as part 1

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -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**
@@ -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,8 +792,9 @@
  ==== 3.4.2.1 Set Transmit Interval ====
--Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
++Sets the uplink interval of the device.
++
  * (% style="color:#037691" %)**AT command:**
  (% style="color:blue" %)**AT+TDC=N**
@@ -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 ) ===

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

Summary

Details

Applications

Navigation