Last modified by Saxer Lin on 2025/04/15 17:24
<
From version < 137.2 >
edited by Dilisi S
on 2024/10/30 02:28
To version < 159.1 >
edited by Bei Jinggeng
on 2024/11/01 14:02
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.pradeeka
1 +XWiki.Bei
Content
... ... @@ -19,15 +19,13 @@
19 19  
20 20  = 1.Introduction =
21 21  
22 -== 1.1 What is LT Series I/O Controller ==
22 +== 1.1 What is the LT-22222-L I/O Controller? ==
23 23  
24 24  (((
25 -
26 -
27 27  (((
28 -(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN device designed to provide seamless wireless long-range connectivity with various I/O options, including analog current and voltage inputs, digital inputs and outputs, and relay outputs. The LT-22222-L simplifies and enhances I/O monitoring and controlling.
26 +The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN device designed to provide seamless wireless long-range connectivity with various I/O options, including analog current and voltage inputs, digital inputs and outputs, and relay outputs.
29 29  
30 -The Dragino LT-22222-L I/O Controller is ideal for professional applications in wireless sensor networks, including irrigation systems, smart metering, smart cities, building automation, and more. These controllers are designed for easy, cost-effective deployment using LoRa wireless technology.
28 +The LT-22222-L I/O Controller simplifies and enhances I/O monitoring and controlling. It is ideal for professional applications in wireless sensor networks, including irrigation systems, smart metering, smart cities, building automation, and more. These controllers are designed for easy, cost-effective deployment using LoRa wireless technology.
31 31  )))
32 32  )))
33 33  
... ... @@ -35,18 +35,16 @@
35 35  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.
36 36  )))
37 37  
38 -(((
39 -(% style="line-height:1.38; margin-top:16px; margin-bottom:16px" %)
40 -The LT Series I/O Controllers are designed for easy, low-cost installation on LoRaWAN networks.
41 -)))
36 +> The LT Series I/O Controllers are designed for easy, low-cost installation on LoRaWAN networks.
42 42  
43 43  (((
44 -(% style="line-height:1.38; margin-top:16px; margin-bottom:16px" %)
45 -(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways:
39 +You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways:
46 46  
47 -* (% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)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.
48 -* (% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)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.
49 -* (% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)Setup your own private LoRaWAN network.
41 +* 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.
42 +* 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.
43 +* Setup your own private LoRaWAN network.
44 +
45 +> You can use the Dragino LG308 gateway to expand or create LoRaWAN coverage in your area.
50 50  )))
51 51  
52 52  (((
... ... @@ -132,85 +132,140 @@
132 132  * 1 x Counting Port
133 133  )))
134 134  
135 -= 2. Power ON Device =
131 += 2. Assembling the Device =
136 136  
137 -The LT controller can be powered by 7 ~~ 24V DC power source. Connect VIN to Power Input V+ and GND to power input V- to power the LT controller.
133 +== 2.1 What is included in the package? ==
138 138  
139 -PWR will on when device is properly powered.
135 +The package includes the following items:
140 140  
137 +* 1 x LT-22222-L I/O Controller
138 +* 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L
139 +* 1 x bracket for wall mounting
140 +* 1 x programming cable
141 +
142 +Attach the LoRaWAN antenna to the connector labeled **ANT** (located on the top right side of the device, next to the upper terminal block). Secure the antenna by tightening it clockwise.
143 +
144 +== 2.2 Terminals ==
145 +
146 +Upper screw terminal block (from left to right):
147 +
148 +(% style="width:634px" %)
149 +|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function
150 +|(% style="width:295px" %)GND|(% style="width:338px" %)Ground
151 +|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage
152 +|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2
153 +|(% style="width:295px" %)AVI1|(% style="width:338px" %)Analog Voltage Input Terminal 1
154 +|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2
155 +|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1
156 +
157 +Lower screw terminal block (from left to right):
158 +
159 +(% style="width:633px" %)
160 +|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function
161 +|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1
162 +|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1
163 +|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2
164 +|(% style="width:296px" %)RO2-1|(% style="width:334px" %)Relay Output 2
165 +|(% style="width:296px" %)DI2+|(% style="width:334px" %)Digital Input 2
166 +|(% style="width:296px" %)DI2-|(% style="width:334px" %)Digital Input 2
167 +|(% style="width:296px" %)DI1+|(% style="width:334px" %)Digital Input 1
168 +|(% style="width:296px" %)DI1-|(% style="width:334px" %)Digital Input 1
169 +|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
170 +|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
171 +
172 +== 2.3 Powering ==
173 +
174 +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 screw terminal and the negative wire to the GND screw terminal. The power indicator (PWR) LED will turn on when the device is properly powered.
175 +
176 +
141 141  [[image:1653297104069-180.png]]
142 142  
143 143  
144 144  = 3. Operation Mode =
145 145  
146 -== 3.1 How it works? ==
182 +== 3.1 How does it work? ==
147 147  
184 +The LT-22222-L is configured to operate in LoRaWAN Class C mode by default. It supports OTAA (Over-the-Air Activation), which is 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.
148 148  
149 -(((
150 -The LT is configured as LoRaWAN OTAA Class C mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the LT. It will auto join the network via OTAA. For LT-22222-L, the LED will show the Join status: After power on (% style="color:green" %)**TX LED**(%%) will fast blink 5 times, LT-22222-L will enter working mode and start to JOIN LoRaWAN network. (% style="color:green" %)**TX LED**(%%) will be on for 5 seconds after joined in network. When there is message from server, the RX LED will be on for 1 second. 
151 -)))
186 +For LT-22222-L, the LED will show the Join status: After power on (% style="color:green" %)**TX LED**(%%) will fast blink 5 times, LT-22222-L will enter working mode and start to JOIN LoRaWAN network. (% style="color:green" %)**TX LED**(%%) will be on for 5 seconds after joined in network. When there is message from server, the RX LED will be on for 1 second. 
152 152  
153 -(((
154 -In case user can't set the OTAA keys in the network server and has to use the existing keys from server. User can [[use AT Command>>||anchor="H4.UseATCommand"]] to set the keys in the devices.
155 -)))
188 +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.
156 156  
190 +== 3.2 Registering with a LoRaWAN network server ==
157 157  
158 -== 3.2 Example to join LoRaWAN network ==
192 +The diagram below shows how the LT-22222-L connects to a typical LoRaWAN network.
159 159  
194 +[[image:image-20220523172350-1.png||height="266" width="864"]]
160 160  
161 -(((
162 -This chapter shows an example for how to join the TTN LoRaWAN Network. Below is the network structure, we use our LG308 as LoRaWAN gateway here. 
196 +=== 3.2.1 Prerequisites ===
163 163  
164 -
165 -)))
198 +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.
166 166  
167 -[[image:image-20220523172350-1.png||height="266" width="864"]]
200 +[[image:image-20230425173427-2.png||height="246" width="530"]]
168 168  
202 +The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
169 169  
170 -(((
171 -The LG308 is already set to connect to [[TTN network >>url:https://www.thethingsnetwork.org/]]. So what we need to do now is only configure register this device to TTN:
204 +=== 3.2.2 The Things Stack Sandbox (TTSS) ===
172 172  
173 -
174 -)))
206 +* Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
207 +* Create an application if you do not have one yet.
208 +* Register LT-22222-L with that application. Two registration options available:
175 175  
176 -(((
177 -(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LT IO controller.
178 -)))
210 +==== Using the LoRaWAN Device Repository: ====
179 179  
180 -(((
181 -Each LT is shipped with a sticker with the default device EUI as below:
182 -)))
212 +* Go to your application and click on the **Register end device** button.
213 +* On the **Register end device** page:
214 +** Select the option **Select the end device in the LoRaWAN Device Repository**.
215 +** Choose the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)**.
216 +** Select the **Frequency plan** that matches with your device.
183 183  
184 -[[image:image-20230425173427-2.png||height="246" width="530"]]
218 +[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
185 185  
220 +*
221 +** Enter the **AppEUI** in the **JoinEUI** field and click **Confirm** button.
222 +** Enter the **DevEUI** in the **DevEUI** field.
223 +** Enter the **AppKey** in the **AppKey** field.
224 +** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
225 +** Under **After registration**, select the **View registered end device** option.
186 186  
187 -Input these keys in the LoRaWAN Server portal. Below is TTN screen shot:
227 +[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
188 188  
189 -**Add APP EUI in the application.**
229 +==== Entering device information manually: ====
190 190  
191 -[[image:1653297955910-247.png||height="321" width="716"]]
231 +* On the **Register end device** page:
232 +** Select the **Enter end device specifies manually** option as the input method.
233 +** Select the **Frequency plan** that matches with your device.
234 +** Select the **LoRaWAN version**.
235 +** Select the **Regional Parameters version**.
236 +** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the section.
237 +** Select **Over the air activation (OTAA)** option under **Activation mode**
238 +** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities**.
192 192  
240 +[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
193 193  
194 -**Add APP KEY and DEV EUI**
195 195  
196 -[[image:1653298023685-319.png]]
243 +* Enter **AppEUI** in the **JoinEUI** field and click **Confirm** button.
244 +* Enter **DevEUI** in the **DevEUI** field.
245 +* Enter **AppKey** in the **AppKey** field.
246 +* In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
247 +* Under **After registration**, select the **View registered end device** option.
197 197  
249 +[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
198 198  
199 -(((
200 -(% style="color:blue" %)**Step 2**(%%): Power on LT and it will auto join to the TTN network. After join success, it will start to upload message to TTN and user can see in the panel.
201 201  
202 -
203 -)))
252 +==== Joining ====
204 204  
254 +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.
255 +
205 205  [[image:1653298044601-602.png||height="405" width="709"]]
206 206  
207 207  
208 -== 3.3 Uplink Payload ==
259 +== 3.3 Uplink Payload formats ==
209 209  
210 210  
211 -There are five working modes + one interrupt mode on LT for different type application:
262 +The LT-22222-L has 5 working modes. It also has an interrupt/trigger mode for different type applications that can be used together with all the working modes as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands.
212 212  
213 -* (% style="color:blue" %)**MOD1**(%%): (default setting): 2 x ACI + 2AVI + DI + DO + RO
264 +* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2 x ACI + 2AVI + DI + DO + RO
214 214  
215 215  * (% style="color:blue" %)**MOD2**(%%): Double DI Counting + DO + RO
216 216  
... ... @@ -226,7 +226,7 @@
226 226  
227 227  
228 228  (((
229 -The uplink payload includes totally 9 bytes. Uplink packets use FPORT=2 and every 10 minutes send one uplink by default. (% style="display:none" %)
280 +In working mode MOD1, the uplink payload includes a total of 11 bytes. Uplink packets are sent over LoRaWAN FPort=2. By default, one uplink is sent every 10 minutes. (% style="display:none" %)
230 230  
231 231  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
232 232  |(% 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**
... ... @@ -244,23 +244,23 @@
244 244  )))
245 245  
246 246  (((
247 -(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below
298 +(% style="color:#4f81bd" %)*** DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte ,as shown below
248 248  
249 249  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
250 -|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
251 -|RO1|RO2|DI3|DI2|DI1|DO3|DO2|DO1
301 +|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
302 +|RO1|RO2|--DI3--|DI2|DI1|--DO3--|DO2|DO1
252 252  )))
253 253  
254 -* RO is for relay. ROx=1 : close, ROx=0 always open.
255 -* DI is for digital input. DIx=1: high or float, DIx=0: low.
256 -* DO is for reverse digital output. DOx=1: output low, DOx=0: high or float.
305 +* RO is for relay. ROx=1 : closed, ROx=0 always open.
306 +* DI is for digital input. DIx=1: high or floating, DIx=0: low.
307 +* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
257 257  
258 -(% style="color:red" %)**Note: DI3 and DO3 bit are not valid for LT-22222-L**
309 +(% style="color:red" %)**Note: DI3 and DO3 bits are not valid for LT-22222-L**
259 259  
260 -For example if payload is: [[image:image-20220523175847-2.png]]
311 +For example, if the payload is: [[image:image-20220523175847-2.png]]
261 261  
262 262  
263 -**The value for the interface is:  **
314 +**The interface values can be calculated as follows:  **
264 264  
265 265  AVI1 channel voltage is 0x04AB/1000=1195(DEC)/1000=1.195V
266 266  
... ... @@ -272,23 +272,19 @@
272 272  
273 273  The last byte 0xAA= 10101010(B) means
274 274  
275 -* [1] RO1 relay channel is close and the RO1 LED is ON.
276 -* [0] RO2 relay channel is open and RO2 LED is OFF;
277 -
278 -**LT22222-L:**
279 -
280 -* [1] DI2 channel is high input and DI2 LED is ON;
281 -* [0] DI1 channel is low input;
282 -
326 +* [1] RO1 relay channel is closed, and the RO1 LED is ON.
327 +* [0] RO2 relay channel is open, and RO2 LED is OFF.
328 +* [1] DI2 channel is high input and DI2 LED is ON.
329 +* [0] DI1 channel is low input.
283 283  * [0] DO3 channel output state
284 -** DO3 is float in case no load between DO3 and V+.;
331 +** DO3 is float in case no load between DO3 and V+.
285 285  ** DO3 is high in case there is load between DO3 and V+.
286 286  ** DO3 LED is off in both case
287 287  * [1] DO2 channel output is low and DO2 LED is ON.
288 288  * [0] DO1 channel output state
289 -** DO1 is float in case no load between DO1 and V+.;
336 +** DO1 is float in case no load between DO1 and V+.
290 290  ** DO1 is high in case there is load between DO1 and V+.
291 -** DO1 LED is off in both case
338 +** DO1 LED is off in both case.
292 292  
293 293  === 3.3.2 AT+MOD~=2, (Double DI Counting) ===
294 294  
... ... @@ -1302,54 +1302,71 @@
1302 1302  [[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-20220823173929-8.png?width=1205&height=76&rev=1.1||alt="image-20220823173929-8.png"]]
1303 1303  
1304 1304  
1305 -== 3.5 Integrate with Mydevice ==
1352 +== 3.5 Integrating with ThingsEye.io ==
1306 1306  
1354 +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.
1307 1307  
1308 -Mydevices provides a human friendly interface to show the sensor data, once we have data in TTN, we can use Mydevices to connect to TTN and see the data in Mydevices. Below are the steps:
1356 +=== 3.5.1 Configuring The Things Stack Sandbox ===
1309 1309  
1310 -(((
1311 -(% style="color:blue" %)**Step 1**(%%): Be sure that your device is programmed and properly connected to the network at this time.
1312 -)))
1358 +* Go to your Application and select MQTT under Integrations.
1359 +* In the Connection credentials section, under Username, The Thins Stack displays an auto-generated username. You can use it or provide a new one.
1360 +* For the Password, click the Generate new API key button to generate a password. You can see it by clicking on the eye button.
1313 1313  
1314 -(((
1315 -(% style="color:blue" %)**Step 2**(%%): To configure the Application to forward data to Mydevices you will need to add integration. To add the Mydevices integration, perform the following steps:
1362 +[[image:tts-mqtt-integration.png||height="625" width="1000"]]
1316 1316  
1317 -
1318 -)))
1364 +=== 3.5.2 Configuring ThingsEye.io ===
1319 1319  
1320 -[[image:image-20220719105525-1.png||height="377" width="677"]]
1366 +* Login to your thingsEye.io account.
1367 +* Under the Integrations center, click Integrations.
1368 +* Click the Add integration button (the button with the + symbol).
1321 1321  
1370 +[[image:thingseye-io-step-1.png||height="625" width="1000"]]
1322 1322  
1323 1323  
1324 -[[image:image-20220719110247-2.png||height="388" width="683"]]
1373 +On the Add integration page configure the following:
1325 1325  
1375 +Basic settings:
1326 1326  
1327 -(% style="color:blue" %)**Step 3**(%%): Create an account or log in Mydevices.
1377 +* Select The Things Stack Community from the Integration type list.
1378 +* Enter a suitable name for your integration in the Name box or keep the default name.
1379 +* Click the Next button.
1328 1328  
1329 -(% style="color:blue" %)**Step 4**(%%): Search LT-22222-L(for both LT-22222-L) and add DevEUI.(% style="display:none" %)
1381 +[[image:thingseye-io-step-2.png||height="625" width="1000"]]
1330 1330  
1331 -Search under The things network
1383 +Uplink Data converter:
1332 1332  
1333 -[[image:1653356838789-523.png||height="337" width="740"]]
1385 +* Click the Create New button if it is not selected by default.
1386 +* Click the JavaScript button.
1387 +* Paste the uplink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
1388 +* Click the Next button.
1334 1334  
1390 +[[image:thingseye-io-step-3.png||height="625" width="1000"]]
1335 1335  
1336 -After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
1392 +Downlink Data converter (this is an optional step):
1337 1337  
1338 -[[image:image-20220524094909-1.png||height="335" width="729"]]
1394 +* Click the Create new button if it is not selected by default.
1395 +* Click the JavaScript button.
1396 +* Paste the downlink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
1397 +* Click the Next button.
1339 1339  
1399 +[[image:thingseye-io-step-4.png||height="625" width="1000"]]
1340 1340  
1341 -[[image:image-20220524094909-2.png||height="337" width="729"]]
1401 +Connection:
1342 1342  
1403 +* Choose Region from the Host type.
1404 +* Enter the cluster of your The Things Stack in the Region textbox.
1405 +* 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.
1406 +* Click Check connection to test the connection. If the connection is successful, you can see the message saying Connected.
1407 +* Click the Add button.
1343 1343  
1344 -[[image:image-20220524094909-3.png||height="338" width="727"]]
1409 +[[image:thingseye-io-step-5.png||height="625" width="1000"]]
1345 1345  
1346 1346  
1347 -[[image:image-20220524094909-4.png||height="339" width="728"]](% style="display:none" %)
1412 +Your integration is added to the integrations list and it will display on the Integrations page.
1348 1348  
1414 +[[image:thingseye-io-step-6.png||height="625" width="1000"]]
1349 1349  
1350 -[[image:image-20220524094909-5.png||height="341" width="734"]]
1351 1351  
1352 -
1353 1353  == 3.6 Interface Detail ==
1354 1354  
1355 1355  === 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
lt-22222-l-dev-repo-p1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +391.8 KB
Content
lt-22222-l-dev-repo-reg-p1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +391.7 KB
Content
lt-22222-l-dev-repo-reg-p2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +319.1 KB
Content
lt-22222-l-manually-p1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +306.6 KB
Content
lt-22222-l-manually-p2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +279.1 KB
Content
thingseye-io-step-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +191.8 KB
Content
thingseye-io-step-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +260.3 KB
Content
thingseye-io-step-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +336.6 KB
Content
thingseye-io-step-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +361.1 KB
Content
thingseye-io-step-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +292.1 KB
Content
thingseye-io-step-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +203.8 KB
Content
tts-mqtt-integration.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +306.4 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0