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, 4 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -169,7 +169,7 @@ 169 169 |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2 170 170 |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1 171 171 172 -== 2.3 Powering the LT-22222-L 172 +== 2.3 Powering the LT-22222-L == 173 173 174 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 and the negative wire to the GND screw terminals. The power indicator (PWR) LED will turn on when the device is properly powered. 175 175 ... ... @@ -256,12 +256,12 @@ 256 256 [[image:1653298044601-602.png||height="405" width="709"]] 257 257 258 258 259 -== 3.3 259 +== 3.3 Work Modes and their Uplink Payload formats == 260 260 261 261 262 -The LT-22222-L has 5 work ingmodes. 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.262 +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. 263 263 264 -* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2 xACI + 2AVI + DI + DO + RO264 +* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO 265 265 266 266 * (% style="color:blue" %)**MOD2**(%%): Double DI Counting + DO + RO 267 267 ... ... @@ -275,9 +275,8 @@ 275 275 276 276 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 277 277 278 - 279 279 ((( 280 -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" %)279 +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" %) 281 281 282 282 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 283 283 |(% 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** ... ... @@ -289,13 +289,13 @@ 289 289 ACI1 Current 290 290 )))|((( 291 291 ACI2 Current 292 -)))|DIDORO*|((( 291 +)))|**DIDORO***|((( 293 293 Reserve 294 294 )))|MOD 295 295 ))) 296 296 297 297 ((( 298 -(% style="color:#4f81bd" %)*** DIDORO**(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, fora totalof1 byte,as shown below.297 +(% 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. 299 299 300 300 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 301 301 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** ... ... @@ -302,9 +302,9 @@ 302 302 |RO1|RO2|--DI3--|DI2|DI1|--DO3--|DO2|DO1 303 303 ))) 304 304 305 -* RO is for the relay. ROx=1: closed, ROx=0 alwaysopen.306 -* DI is for digital input. DIx=1: highorfloating, DIx=0:low.307 -* DO is for reverse digital output. DOx=1: output low, DOx=0:highorfloating.304 +* RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN. 305 +* DI is for digital input. DIx=1: HIGH or FLOATING, DIx=0: LOW. 306 +* DO is for reverse digital output. DOx=1: LOW, DOx=0: HIGH or FLOATING. 308 308 309 309 (% style="color:red" %)**Note: DI3 and DO3 bits are not valid for LT-22222-L** 310 310 ... ... @@ -342,7 +342,7 @@ 342 342 343 343 344 344 ((( 345 -**For LT-22222-L**: In this mode, the**DI1 and DI2** are used as counting pins.344 +**For LT-22222-L**: In this mode, **DI1 and DI2** are used as counting pins. 346 346 ))) 347 347 348 348 ((( ... ... @@ -356,17 +356,17 @@ 356 356 ))) 357 357 358 358 ((( 359 -(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, DO3, DO2 and DO1, fora totalof1 byte,as shown below.358 +(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, DO3, DO2 and DO1, and its size is 1 byte long as shown below. 360 360 361 361 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 362 362 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 363 363 |RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1 364 364 365 -* RO is for the relay. ROx=1: closed, ROx=0 alwaysopen.364 +* RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN. 366 366 ))) 367 367 368 368 * FIRST: Indicates that this is the first packet after joining the network. 369 -* DO is for reverse digital output. DOx=1: output low, DOx=0:highorfloating.368 +* DO is for reverse digital output. DOx=1: LOW, DOx=0: HIGH or FLOATING. 370 370 371 371 ((( 372 372 (% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L** ... ... @@ -602,9 +602,9 @@ 602 602 603 603 **Example:** 604 604 605 -AT+AVLIM=3000,6000,0,2000 ( If AVI1 voltage lower than 3vor higher than 6v.v, LT will trigger Uplink)604 +AT+AVLIM=3000,6000,0,2000 (triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V) 606 606 607 -AT+AVLIM=5000,0,0,0 ( If AVI1 voltage lower than 5V, triggeruplink,0 meansignore)606 +AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage lower than 5V. Use 0 for parameters that are not in use) 608 608 609 609 610 610 (% style="color:#4f81bd" %)**Trigger based on current**: ... ... @@ -614,7 +614,7 @@ 614 614 615 615 **Example:** 616 616 617 -AT+ACLIM=10000,15000,0,0 ( If ACI1 voltage lower than 10mA or higher than 15mA, trigger an uplink)616 +AT+ACLIM=10000,15000,0,0 (triggers an uplink if ACI1 voltage is lower than 10mA or higher than 15mA) 618 618 619 619 620 620 (% style="color:#4f81bd" %)**Trigger based on DI status**: ... ... @@ -629,39 +629,38 @@ 629 629 AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 630 630 631 631 632 -(% style="color:#037691" %)**Downlink Command toset Trigger Condition:**631 +(% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:** 633 633 634 634 Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 635 635 636 636 Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 637 637 638 - AA: Code for this downlink Command: 637 + AA: Type Code for this downlink Command: 639 639 640 - xx: 0: Limit for AV1 and AV2; ,DI2 trigger enable/disable639 + xx: **0**: Limit for AV1 and AV2; **1**: limit for AC1 and AC2; **2**: DI1and DI2 trigger enable/disable. 641 641 642 - yy1 yy1: AC1 or AV1 lowlimit or DI1/DI2 trigger status.641 + yy1 yy1: AC1 or AV1 LOW limit or DI1/DI2 trigger status. 643 643 644 - yy2 yy2: AC1 or AV1 highlimit.643 + yy2 yy2: AC1 or AV1 HIGH limit. 645 645 646 - yy3 yy3: AC2 or AV2 lowlimit.645 + yy3 yy3: AC2 or AV2 LOW limit. 647 647 648 - Yy4 yy4: AC2 or AV2 highlimit.647 + Yy4 yy4: AC2 or AV2 HIGH limit. 649 649 650 650 651 -**Example1**: AA 00 13 88 00 00 00 00 00 00 650 +**Example 1**: AA 00 13 88 00 00 00 00 00 00 652 652 653 -Same as AT+AVLIM=5000,0,0,0 If AVI1 voltage lower than 5V, triggeruplink,0 meansignore)652 +Same as AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage is lower than 5V. Use 0s for parameters that are not in use) 654 654 655 655 656 -**Example2**: AA 02 01 00 655 +**Example 2**: AA 02 01 00 657 657 658 -Same as AT+ DTRI =1,0 657 +Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 659 659 660 660 661 - 662 662 (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:** 663 663 664 -MOD6 Payload: total 11 bytes payload662 +MOD6 Payload: total of 11 bytes 665 665 666 666 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 667 667 |(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:49px" %)**6**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1** ... ... @@ -675,10 +675,10 @@ 675 675 MOD(6) 676 676 ))) 677 677 678 -(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1byte as below 676 +(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below 679 679 680 680 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 681 -|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 679 +|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 682 682 |((( 683 683 AV1_LOW 684 684 )))|((( ... ... @@ -697,17 +697,17 @@ 697 697 AC2_HIGH 698 698 ))) 699 699 700 -* Each bit sshows if the corresponding trigger has been configured.698 +* Each bit shows if the corresponding trigger has been configured. 701 701 702 702 **Example:** 703 703 704 -10100000: Means the system has configure to use the trigger: A C1_LOW and AV2_LOW702 +10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW 705 705 706 706 707 -(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1byte as below 705 +(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below 708 708 709 709 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 710 -|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 708 +|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 711 711 |((( 712 712 AV1_LOW 713 713 )))|((( ... ... @@ -726,11 +726,11 @@ 726 726 AC2_HIGH 727 727 ))) 728 728 729 -* Each bit sshows which status has been trigger on this uplink.727 +* Each bit shows which status has been triggered on this uplink. 730 730 731 731 **Example:** 732 732 733 -10000000: Means this p acketis trigger by AC1_LOW.Means voltage too low.731 +10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low. 734 734 735 735 736 736 (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below ... ... @@ -739,7 +739,7 @@ 739 739 |**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0** 740 740 |N/A|N/A|N/A|N/A|DI2_STATUS|DI2_FLAG|DI1_STATUS|DI1_FLAG 741 741 742 -* Each bits shows which status has been trigger on this uplink. 740 +* Each bits shows which status has been triggered on this uplink. 743 743 744 744 **Example:** 745 745 ... ... @@ -766,11 +766,11 @@ 766 766 ))) 767 767 768 768 769 -== 3.4 Configure LT via AT or Downlink == 767 +== 3.4 Configure LT via AT Commands or Downlinks == 770 770 771 771 772 772 ((( 773 -User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands771 +User can configure LT I/O Controller via AT Commands or LoRaWAN Downlinks. 774 774 ))) 775 775 776 776 ((( ... ... @@ -785,9 +785,8 @@ 785 785 786 786 === 3.4.1 Common Commands === 787 787 788 - 789 789 ((( 790 -The yshould be available foreachofDraginoSensors, such as:change uplink interval,reset device. For firmware v1.5.4, usercan findwhat common commandsit supports:[[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]787 +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]]. 791 791 ))) 792 792 793 793 ... ... @@ -795,34 +795,37 @@ 795 795 796 796 ==== 3.4.2.1 Set Transmit Interval ==== 797 797 795 +Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes. 798 798 799 - Setdeviceuplink interval.797 +* (% style="color:#037691" %)**AT command:** 800 800 801 - *(% style="color:#037691" %)**ATommand:**799 +(% style="color:blue" %)**AT+TDC=N** 802 802 803 - (%style="color:blue"%)**AT+TDC=N**801 +where N is the time in milliseconds. 804 804 803 +**Example: **AT+TDC=30000. This will set the uplink interval to 30 seconds 805 805 806 -**Example: **AT+TDC=30000. Means set interval to 30 seconds 807 807 806 +* (% style="color:#037691" %)**Downlink payload (prefix 0x01):** 808 808 809 -* (% style="color:#037691" %)**Downlink Payload (prefix 0x01):** 810 - 811 811 (% style="color:blue" %)**0x01 aa bb cc **(%%)** ~/~/ Same as AT+TDC=0x(aa bb cc)** 812 812 813 813 814 814 815 -==== 3.4.2.2 Set Work Mode (AT+MOD) ==== 812 +==== 3.4.2.2 Set the Work Mode (AT+MOD) ==== 816 816 817 817 818 -Set work mode. 815 +Sets the work mode. 819 819 820 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+MOD=N **817 +* (% style="color:#037691" %)**AT command:**(%%) (% style="color:blue" %)**AT+MOD=N ** 821 821 822 - **Example**:AT+MOD=2.Set work modeto Double DI counting mode819 +Where N is the work mode. 823 823 824 -* (%style="color:#037691"%)**DownlinkPayload(prefix 0x0A):**821 +**Example**: AT+MOD=2. This will set the work mode to Double DI counting mode. 825 825 823 + 824 +* (% style="color:#037691" %)**Downlink payload (prefix 0x0A):** 825 + 826 826 (% style="color:blue" %)**0x0A aa **(%%)** ** ~/~/ Same as AT+MOD=aa 827 827 828 828 ... ... @@ -830,10 +830,12 @@ 830 830 ==== 3.4.2.3 Poll an uplink ==== 831 831 832 832 833 - * (%style="color:#037691"%)**AT Command:**(%%) ThereisnoAT Commandto polluplink833 +Asks the device to send an uplink. 834 834 835 -* (% style="color:#037691" %)** DownlinkPayload(prefix0x08):**835 +* (% style="color:#037691" %)**AT command:**(%%) There is no AT Command to poll uplink 836 836 837 +* (% style="color:#037691" %)**Downlink payload (prefix 0x08):** 838 + 837 837 (% style="color:blue" %)**0x08 FF **(%%)** **~/~/ Poll an uplink 838 838 839 839 **Example**: 0x08FF, ask device to send an Uplink ... ... @@ -840,16 +840,16 @@ 840 840 841 841 842 842 843 -==== 3.4.2.4 Enable Trigger Mode ==== 845 +==== 3.4.2.4 Enable/Disable Trigger Mode ==== 844 844 845 845 846 - Use oftrigger mode,pleasecheck[[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]848 +Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]). 847 847 848 848 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0** 849 849 850 -(% style="color:red" %)**1:** (%%)Enable TriggerMode852 +(% style="color:red" %)**1:** (%%)Enable the trigger mode 851 851 852 -(% style="color:red" %)**0: **(%%)Disable TriggerMode854 +(% style="color:red" %)**0: **(%%)Disable the trigger mode 853 853 854 854 855 855 * (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):** ... ... @@ -861,7 +861,7 @@ 861 861 ==== 3.4.2.5 Poll trigger settings ==== 862 862 863 863 864 -Poll trigger settings 866 +Polls the trigger settings 865 865 866 866 * (% style="color:#037691" %)**AT Command:** 867 867 ... ... @@ -869,7 +869,7 @@ 869 869 870 870 * (% style="color:#037691" %)**Downlink Payload (prefix 0x AB 06):** 871 871 872 -(% style="color:blue" %)**0xAB 06 ** (%%) ~/~/ Poll trigger settings ,device will uplink trigger settings once receive this command874 +(% style="color:blue" %)**0xAB 06 ** (%%) ~/~/ Poll the trigger settings. Device will uplink trigger settings once receive this command 873 873 874 874 875 875 ... ... @@ -876,11 +876,11 @@ 876 876 ==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ==== 877 877 878 878 879 -Enable Disable DI1/DI2/DI2 as trigger, 881 +Enable or Disable DI1/DI2/DI2 as trigger, 880 880 881 881 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >** 882 882 883 -**Example:** AT+ DTRI =1,0 885 +**Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 884 884 885 885 886 886 * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):** ... ... @@ -912,15 +912,15 @@ 912 912 ==== 3.4.2.8 Trigger2 – Set DI2 as trigger ==== 913 913 914 914 915 -Set DI2 trigger. 917 +Sets DI2 trigger. 916 916 917 917 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b** 918 918 919 -(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1). 921 +(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1). 920 920 921 921 (% style="color:red" %)**b :** (%%)delay timing. 922 922 923 -**Example:** AT+TRIG2=0,100(set DI1 port to trigger on low level, valid signal is 100ms ) 925 +**Example:** AT+TRIG2=0,100 (set DI1 port to trigger on low level, valid signal is 100ms ) 924 924 925 925 926 926 * (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):** ... ... @@ -958,7 +958,7 @@ 958 958 ==== 3.4.2.11 Trigger – Set minimum interval ==== 959 959 960 960 961 -Set AV and AC trigger minimum interval ,systemwon't response to the second trigger within this set time after the first trigger.963 +Sets AV and AC trigger minimum interval. Device won't response to the second trigger within this set time after the first trigger. 962 962 963 963 * (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+ATDC=5 ** ~/~/ (%%)Device won't response the second trigger within 5 minute after the first trigger. 964 964 ... ... @@ -1353,67 +1353,107 @@ 1353 1353 1354 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. 1355 1355 1356 -=== 3.5.1 Configuring The Things Stack Sandbox === 1358 +=== 3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox === 1357 1357 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. 1360 +* In **The Things Stack Sandbox**, select your application under **Applications**. 1361 +* Select **MQTT** under **Integrations**. 1362 +* In the **Connection information **section, for **Username**, The Things Stack displays an auto-generated username. You can use it or provide a new one. 1363 +* For the **Password**, click the **Generate new API key** button to generate a password. You can see it by clicking on the **eye** button. 1361 1361 1362 1362 [[image:tts-mqtt-integration.png||height="625" width="1000"]] 1363 1363 1364 1364 === 3.5.2 Configuring ThingsEye.io === 1365 1365 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). 1369 +* Login to your [[ThingsEye.io >>https://thingseye.io]]account. 1370 +* Under the **Integrations center**, click **Integrations**. 1371 +* Click the **Add integration** button (the button with the **+** symbol). 1369 1369 1370 1370 [[image:thingseye-io-step-1.png||height="625" width="1000"]] 1371 1371 1372 1372 1373 -On the Add integration pageconfigure the following:1376 +On the **Add integration** window, configure the following: 1374 1374 1375 -Basic settings: 1378 +~1. **Basic settings:** 1376 1376 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. 1380 +* Select **The Things Stack Community** from the **Integration type** list. 1381 +* Enter a suitable name for your integration in the **Name **text** **box or keep the default name. 1382 +* Ensure the following options are turned on. 1383 +** Enable integration 1384 +** Debug mode 1385 +** Allow create devices or assets 1386 +* Click the **Next** button. you will be navigated to the **Uplink data converter** tab. 1380 1380 1381 1381 [[image:thingseye-io-step-2.png||height="625" width="1000"]] 1382 1382 1383 -Uplink Data converter: 1384 1384 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. 1391 +2. **Uplink data converter:** 1389 1389 1393 +* Click the **Create new** button if it is not selected by default. 1394 +* Enter a suitable name for the uplink data converter in the **Name **text** **box or keep the default name. 1395 +* Click the **JavaScript** button. 1396 +* 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]]. 1397 +* Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 1398 + 1390 1390 [[image:thingseye-io-step-3.png||height="625" width="1000"]] 1391 1391 1392 -Downlink Data converter (this is an optional step):1401 +3.** Downlink data converter (this is an optional step):** 1393 1393 1394 -* Click the Create new button if it is not selected by default. 1395 -* Click the JavaScript button. 1403 +* Click the **Create new** button if it is not selected by default. 1404 +* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name 1405 +* Click the **JavaScript** button. 1396 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. 1407 +* Click the **Next** button. You will be navigated to the **Connection** tab. 1398 1398 1399 1399 [[image:thingseye-io-step-4.png||height="625" width="1000"]] 1400 1400 1401 -Connection: 1411 +4. **Connection:** 1402 1402 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 thesameusername and passwordyoucreatedwiththe 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. 1413 +* Choose **Region** from the **Host type**. 1414 +* 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/...). 1415 +* 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). 1416 +* Click the **Check connection** button to test the connection. If the connection is successful, you can see the message saying **Connected**. 1417 +* Click the **Add** button. 1408 1408 1409 1409 [[image:thingseye-io-step-5.png||height="625" width="1000"]] 1410 1410 1411 1411 1412 -Your integration is added to the integrations list and it will display on the Integrations page.1422 +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. 1413 1413 1414 1414 [[image:thingseye-io-step-6.png||height="625" width="1000"]] 1415 1415 1416 1416 1427 +Viewing integration details: 1428 + 1429 +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. 1430 + 1431 +[add image here] 1432 + 1433 +If you want to edit the settings you have provided, click on the Toggle edit mode button. 1434 + 1435 +[add image here] 1436 + 1437 +Once you have done click on the Apply changes button. 1438 + 1439 +Note: See also ThingsEye documentation. 1440 + 1441 +Click on the Events tab. 1442 + 1443 +- Select Debug from the Event type dropdown. 1444 + 1445 +- Select the time frame from the time window. 1446 + 1447 +[insert image] 1448 + 1449 +- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message. 1450 + 1451 +[insert image] 1452 + 1453 + 1454 +Deleting the integration: 1455 + 1456 +If you want to delete this integration, click the Delete integration button. 1457 + 1458 + 1417 1417 == 3.6 Interface Details == 1418 1418 1419 1419 === 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
- lt-22222-device-overview.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +497.2 KB - Content
- lt-22222-join-network.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +340.6 KB - Content
- lt-22222-ul-payload-decoded.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +48.7 KB - Content
- lt-22222-ul-payload-fmt.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +438.6 KB - Content