Changes for page LT-22222-L -- LoRa I/O Controller User Manual
Last modified by Saxer Lin on 2025/04/15 17:24
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 8 removed)
Details
- Page properties
-
- Content
-
... ... @@ -245,40 +245,24 @@ 245 245 * Enter **AppKey** in the **AppKey** field. 246 246 * In the **End device ID** field, enter a unique name within this application for your LT-22222-N. 247 247 * Under **After registration**, select the **View registered end device** option. 248 -* Click the **Register end device** button. 249 249 250 250 [[image:lt-22222-l-manually-p2.png||height="625" width="1000"]] 251 251 252 252 253 -You will be navigated to the **Device overview** page. 254 - 255 -[[image:lt-22222-device-overview.png||height="625" width="1000"]] 256 - 257 - 258 258 ==== Joining ==== 259 259 260 -Click on **Live data** in the left navigation. Then, power onLT-22222-L.It will join The Things StackLoRaWANnetwork server. You can see the**join request**,**join accept**, followed by**uplinkdatamessages**form the device showing in the**Livedata**panel.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. 261 261 262 -[[image: lt-22222-join-network.png||height="625" width="1000"]]256 +[[image:1653298044601-602.png||height="405" width="709"]] 263 263 264 264 265 - Clickon a message with the messge type, **Forward uplink data message**.You can see thedecoded uplinkpayload asshown below.259 +== 3.3 Uplink Payload formats == 266 266 267 -[[image:lt-22222-ul-payload-decoded.png]] 268 268 262 +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. 269 269 270 - Ifyoucan'tseethedecoded payload, it isbecauseyouhaven't added the uplinkformatter code. To add theuplink formattercode, select **End devices** > **LT-22222-L** > **Payloadformatters** > **Uplink**. Then select**Use Device repositoryformatters** for the**Formattertype**dropdown.Clickthe**Savechanges** buttontoapplythechanges.264 +* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2 x ACI + 2AVI + DI + DO + RO 271 271 272 -[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]] 273 - 274 - 275 -== 3.3 Work Modes and their Uplink Payload formats == 276 - 277 - 278 -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. 279 - 280 -* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO 281 - 282 282 * (% style="color:blue" %)**MOD2**(%%): Double DI Counting + DO + RO 283 283 284 284 * (% style="color:blue" %)**MOD3**(%%): Single DI Counting + 2 x ACI + DO + RO ... ... @@ -291,8 +291,9 @@ 291 291 292 292 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 293 293 278 + 294 294 ((( 295 -The uplink payload is 11 bytes long. Uplink messages are sent over LoRaWAN FPort280 +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" %) 296 296 297 297 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 298 298 |(% 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** ... ... @@ -304,13 +304,13 @@ 304 304 ACI1 Current 305 305 )))|((( 306 306 ACI2 Current 307 -)))| **DIDORO***|(((292 +)))|DIDORO*|((( 308 308 Reserve 309 309 )))|MOD 310 310 ))) 311 311 312 312 ((( 313 -(% style="color:#4f81bd" %)*** DIDORO**(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, a nditssizeis1 bytelongas shown below.298 +(% 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. 314 314 315 315 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 316 316 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** ... ... @@ -317,9 +317,9 @@ 317 317 |RO1|RO2|--DI3--|DI2|DI1|--DO3--|DO2|DO1 318 318 ))) 319 319 320 -* RO is for the relay. ROx=1: CLOSED, ROx=0 alwaysOPEN.321 -* DI is for digital input. DIx=1: HIGHorFLOATING, DIx=0:LOW.322 -* DO is for reverse digital output. DOx=1: LOW, DOx=0:HIGHorFLOATING.305 +* RO is for the 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. 323 323 324 324 (% style="color:red" %)**Note: DI3 and DO3 bits are not valid for LT-22222-L** 325 325 ... ... @@ -357,7 +357,7 @@ 357 357 358 358 359 359 ((( 360 -**For LT-22222-L**: In this mode, **DI1 and DI2** are used as counting pins. 345 +**For LT-22222-L**: In this mode, the **DI1 and DI2** are used as counting pins. 361 361 ))) 362 362 363 363 ((( ... ... @@ -371,17 +371,17 @@ 371 371 ))) 372 372 373 373 ((( 374 -(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, DO3, DO2 and DO1, a nditssizeis1 bytelongas shown below.359 +(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, DO3, DO2 and DO1, for a total of 1 byte, as shown below. 375 375 376 376 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 377 377 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 378 378 |RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1 379 379 380 -* RO is for the relay. ROx=1: CLOSED, ROx=0 alwaysOPEN.365 +* RO is for the relay. ROx=1: closed, ROx=0 always open. 381 381 ))) 382 382 383 383 * FIRST: Indicates that this is the first packet after joining the network. 384 -* DO is for reverse digital output. DOx=1: LOW, DOx=0:HIGHorFLOATING.369 +* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating. 385 385 386 386 ((( 387 387 (% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L** ... ... @@ -780,11 +780,11 @@ 780 780 ))) 781 781 782 782 783 -== 3.4 Configure LT via AT Commands or Downlinks==768 +== 3.4 Configure LT via AT or Downlink == 784 784 785 785 786 786 ((( 787 -User can configure LT I/O Controller via AT Commands or LoRaWAN Downlinks .772 +User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands 788 788 ))) 789 789 790 790 ((( ... ... @@ -799,8 +799,9 @@ 799 799 800 800 === 3.4.1 Common Commands === 801 801 787 + 802 802 ((( 803 -The secommandsshould be available for allDraginosensors, such as changing the uplink intervalorresettingthedevice. For firmware v1.5.4,you can findthe supportedcommon commands under [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]].789 +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]] 804 804 ))) 805 805 806 806 ... ... @@ -808,8 +808,9 @@ 808 808 809 809 ==== 3.4.2.1 Set Transmit Interval ==== 810 810 811 -Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes. 812 812 798 +Sets the uplink interval of the device. 799 + 813 813 * (% style="color:#037691" %)**AT command:** 814 814 815 815 (% style="color:blue" %)**AT+TDC=N** ... ... @@ -1369,122 +1369,69 @@ 1369 1369 1370 1370 == 3.5 Integrating with ThingsEye.io == 1371 1371 1372 -The Things Stack applications canbeintegratedwithThingsEye.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.1359 +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. 1373 1373 1374 -=== 3.5.1 Configuring MQTT Connection Information withThe Things Stack Sandbox ===1361 +=== 3.5.1 Configuring The Things Stack Sandbox === 1375 1375 1376 -We use The Things Stack Sandbox for demonstating the configuration but other 1363 +* Go to your Application and select MQTT under Integrations. 1364 +* In the Connection credentials section, under Username, The Thins Stack displays an auto-generated username. You can use it or provide a new one. 1365 +* For the Password, click the Generate new API key button to generate a password. You can see it by clicking on the eye button. 1377 1377 1378 -* In **The Things Stack Sandbox**, select your application under **Applications**. 1379 -* Select **MQTT** under **Integrations**. 1380 -* In the **Connection information **section, for **Username**, The Things Stack displays an auto-generated username. You can use it or provide a new one. 1381 -* 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. 1382 - 1383 -NOTE. The username and password (API key) you created here are required in the next section. 1384 - 1385 1385 [[image:tts-mqtt-integration.png||height="625" width="1000"]] 1386 1386 1387 1387 === 3.5.2 Configuring ThingsEye.io === 1388 1388 1389 -This section guides you on how to create an integration in ThingsEye to connect with The Things Stack MQTT server. 1371 +* Login to your thingsEye.io account. 1372 +* Under the Integrations center, click Integrations. 1373 +* Click the Add integration button (the button with the + symbol). 1390 1390 1391 -* Login to your [[ThingsEye.io >>https://thingseye.io]]account. 1392 -* Under the **Integrations center**, click **Integrations**. 1393 -* Click the **Add integration** button (the button with the **+** symbol). 1394 - 1395 1395 [[image:thingseye-io-step-1.png||height="625" width="1000"]] 1396 1396 1397 1397 1398 -On the **Add integration** window,configure the following:1378 +On the Add integration page configure the following: 1399 1399 1400 - **Basic settings:**1380 +Basic settings: 1401 1401 1402 -* Select **The Things Stack Community** from the **Integration type** list. 1403 -* Enter a suitable name for your integration in the **Name **text** **box or keep the default name. 1404 -* Ensure the following options are turned on. 1405 -** Enable integration 1406 -** Debug mode 1407 -** Allow create devices or assets 1408 -* Click the **Next** button. you will be navigated to the **Uplink data converter** tab. 1382 +* Select The Things Stack Community from the Integration type list. 1383 +* Enter a suitable name for your integration in the Name box or keep the default name. 1384 +* Click the Next button. 1409 1409 1410 1410 [[image:thingseye-io-step-2.png||height="625" width="1000"]] 1411 1411 1388 +Uplink Data converter: 1412 1412 1413 -**Uplink data converter:** 1390 +* Click the Create New button if it is not selected by default. 1391 +* Click the JavaScript button. 1392 +* Paste the uplink decoder function into the text area (first, delete the default code). The demo decoder function can be found here. 1393 +* Click the Next button. 1414 1414 1415 -* Click the **Create new** button if it is not selected by default. 1416 -* Enter a suitable name for the uplink data converter in the **Name **text** **box or keep the default name. 1417 -* Click the **JavaScript** button. 1418 -* 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]]. 1419 -* Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 1420 - 1421 1421 [[image:thingseye-io-step-3.png||height="625" width="1000"]] 1422 1422 1397 +Downlink Data converter (this is an optional step): 1423 1423 1424 -**Downlink data converter (this is an optional step):** 1399 +* Click the Create new button if it is not selected by default. 1400 +* Click the JavaScript button. 1401 +* Paste the downlink decoder function into the text area (first, delete the default code). The demo decoder function can be found here. 1402 +* Click the Next button. 1425 1425 1426 -* Click the **Create new** button if it is not selected by default. 1427 -* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name 1428 -* Click the **JavaScript** button. 1429 -* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found here. 1430 -* Click the **Next** button. You will be navigated to the **Connection** tab. 1431 - 1432 1432 [[image:thingseye-io-step-4.png||height="625" width="1000"]] 1433 1433 1406 +Connection: 1434 1434 1435 -**Connection:** 1408 +* Choose Region from the Host type. 1409 +* Enter the cluster of your The Things Stack in the Region textbox. 1410 +* 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. 1411 +* Click Check connection to test the connection. If the connection is successful, you can see the message saying Connected. 1412 +* Click the Add button. 1436 1436 1437 -* Choose **Region** from the **Host type**. 1438 -* 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/...). 1439 -* 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). 1440 -* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**. 1441 - 1442 -[[image:message-1.png]] 1443 - 1444 - 1445 -* Click the **Add** button. 1446 - 1447 1447 [[image:thingseye-io-step-5.png||height="625" width="1000"]] 1448 1448 1449 1449 1450 -Your integration hasbeenadded to the** Integrations**list and willbedisplayedon the**Integrations**page.Check whether the status is shown as **Active**. If not, review your configuration settings.1417 +Your integration is added to the integrations list and it will display on the Integrations page. 1451 1451 1419 +[[image:thingseye-io-step-6.png||height="625" width="1000"]] 1452 1452 1453 -[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]] 1454 1454 1455 - 1456 -**Viewing integration details**: 1457 - 1458 -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. 1459 - 1460 -[[image:integration-details.png||height="686" width="1000"]] 1461 - 1462 - 1463 -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. 1464 - 1465 -Note: See also ThingsEye documentation. 1466 - 1467 - 1468 -**Viewing events:** 1469 - 1470 -This tab displays all the uplink messages from the LT-22222-L. 1471 - 1472 -* Click on the **Events **tab. 1473 -* Select **Debug **from the **Event type** dropdown. 1474 -* Select the** time frame** from the **time window**. 1475 - 1476 -[insert image] 1477 - 1478 -- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message. 1479 - 1480 -[insert image] 1481 - 1482 - 1483 -**Deleting the integration**: 1484 - 1485 -If you want to delete this integration, click the **Delete integratio**n button. 1486 - 1487 - 1488 1488 == 3.6 Interface Details == 1489 1489 1490 1490 === 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
- integration-details.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -463.9 KB - Content
- lt-22222-device-overview.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -497.2 KB - Content
- lt-22222-join-network.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -340.6 KB - Content
- lt-22222-ul-payload-decoded.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -48.7 KB - Content
- lt-22222-ul-payload-fmt.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -438.6 KB - Content
- message-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -20.1 KB - Content
- thingseye.io_integrationsCenter_integrations-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -469.3 KB - Content
- thingseye.io_integrationsCenter_integrations.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -302.3 KB - Content