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

Last modified by Mengting Qiu on 2025/06/04 18:42

From 77.58 to 77.57 From 77.87 to 77.86

From version 77.86

edited by Xiaoling
on 2022/06/10 09:27

Change comment: There is no comment for this version

To version 77.58

edited by Xiaoling
on 2022/06/10 09:11

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -325,11 +325,8 @@
  ** DO1 is high in case there is load between DO1 and V+.
  ** DO1 LED is off in both case
--
--
  === 3.3.2 AT+MOD~=2, (Double DI Counting) ===
--
  **For LT-22222-L**: this mode the **DI1 and DI2** are used as counting pins.
  (((
@@ -338,7 +338,6 @@
  [[image:image-20220523180452-3.png]]
--
  (((
  (% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DO3, DO2 and DO1. Totally 1bytes as below
  )))
@@ -354,8 +354,6 @@
  )))
  (((
--
--
  **To use counting mode, please run:**
  )))
@@ -374,8 +374,6 @@
  )))
  (((
--
--
  (% style="color:#4f81bd" %)**AT Commands for counting:**
  )))
@@ -472,9 +472,9 @@
  )))
++
  === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
--
  **LT22222-L**: This mode the DI1 is used as a counting pin.
  The AVI1 is also used for counting. AVI1 is used to monitor the voltage. It will check the voltage **every 60s**, if voltage is higher or lower than VOLMAX mV, the AVI1 Counting increase 1, so AVI1 counting can be used to measure a machine working hour.
@@ -481,7 +481,6 @@
  [[image:image-20220523181903-8.png]]
--
  (((
  (% style="color:#4f81bd" %)**DIDORO **(%%)is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below
  )))
@@ -497,8 +497,6 @@
  )))
  (((
--
--
  **To use this mode, please run:**
  )))
@@ -525,8 +525,6 @@
  )))
  (((
--
--
  **Plus below command for AVI1 Counting:**
  )))
@@ -562,14 +562,11 @@
  === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI ===
--
  **LT22222-L**: This mode the DI1 is used as a counting pin.
  [[image:image-20220523182334-9.png]]
  (((
--
--
  (% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below
  )))
@@ -584,8 +584,6 @@
  )))
  (((
--
--
  **To use this mode, please run:**
  )))
@@ -605,6 +605,8 @@
  (((
  Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]].
++
++
  )))
@@ -611,7 +611,6 @@
  === 3.3.6 AT+ADDMOD~=6. (Trigger Mode, Optional) ===
--
  (% style="color:#4f81bd" %)**This mode is an optional mode for trigger purpose. It can run together with other mode.**
  For example, if user has configured below commands:
@@ -619,13 +619,11 @@
  * **AT+MOD=1 **  **~-~->** The normal working mode
  * **AT+ADDMOD6=1**   **~-~->** Enable trigger
--
  LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases:
 . Periodically uplink (Base on TDC time). Payload is same as the normal MOD (MOD 1 for above command). This uplink uses LoRaWAN (% style="color:#4f81bd" %)**unconfirmed**(%%) data type
 . Trigger uplink when meet the trigger condition. LT will sent two packets in this case, the first uplink use payload specify in this mod (mod=6), the second packets use the normal mod payload(MOD=1 for above settings). Both Uplinks use LoRaWAN (% style="color:#4f81bd" %)**CONFIRMED data type.**
--
  **AT Command to set Trigger Condition**:
  (% style="color:#4f81bd" %)**Trigger base on voltage**:
@@ -677,17 +677,14 @@
    Yy4 yy4: AC2 or AV2 high limit.
--
  **Example1**: AA 00 13 88 00 00 00 00 00 00
  Same as AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
--
  **Example2**: AA 02 01 00
  Same as AT+ DTRI =1,0  (Enable DI1 trigger / disable DI2 trigger)
--
  (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:**
  MOD6 Payload : total 11 bytes payload
@@ -694,7 +694,6 @@
  [[image:image-20220524085923-1.png]]
--
  (% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if trigger is set for this part. Totally 1byte as below
  [[image:image-20220524090106-2.png]]
@@ -701,7 +701,6 @@
  * Each bits shows if the corresponding trigger has been configured.
--
  **Example:**
  10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW
@@ -713,7 +713,6 @@
  * Each bits shows which status has been trigger on this uplink.
--
  **Example:**
  10000000: Means this packet is trigger by AC1_LOW. Means voltage too low.
@@ -725,7 +725,6 @@
  * Each bits shows which status has been trigger on this uplink.
--
  **Example:**
  00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
@@ -746,8 +746,6 @@
  === 3.3.7 Payload Decoder ===
  (((
--
--
  **Decoder for TTN/loraserver/ChirpStack**: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/Payload_decoder/>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/Payload_decoder/]]
@@ -767,8 +767,6 @@
  * (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L.  User can see these commands below:
--
--
  === 3.4.1 Common Commands ===
  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]]
@@ -790,7 +790,6 @@
  **Example: **AT+TDC=30000. Means set interval to 30 seconds
--
  * Downlink Payload (prefix 0x01):
  (% class="box infomessage" %)
@@ -813,7 +813,6 @@
  **Example**: AT+MOD=2. Set work mode to Double DI counting mode
--
  * Downlink Payload (prefix 0x0A):
  (% class="box infomessage" %)
@@ -829,7 +829,6 @@
  There is no AT Command to poll uplink
--
  * Downlink Payload (prefix 0x08):
  (% class="box infomessage" %)
@@ -856,7 +856,6 @@
 : Disable Trigger Mode
--
  * Downlink Payload (prefix 0x0A 06):
  (% class="box infomessage" %)
@@ -874,7 +874,6 @@
  There is no AT Command for this feature.
--
  * Downlink Payload (prefix 0x AB 06):
  (% class="box infomessage" %)
@@ -895,7 +895,6 @@
  **Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
  )))
--
  **Example:**
  AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
@@ -924,12 +924,10 @@
  b : delay timing.
--
  **Example:**
  AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms )
--
  * Downlink Payload (prefix 0x09 01 ):
  (% class="box infomessage" %)
@@ -954,12 +954,10 @@
  b : delay timing.
--
  **Example:**
  AT+TRIG2=0,100(set DI1 port to trigger on low level, valid signal is 100ms )
--
  * Downlink Payload (prefix 0x09 02 ):
  (% class="box infomessage" %)
@@ -980,7 +980,6 @@
  **AT+ACLIM. **
  )))
--
  * Downlink Payload (prefix 0xAA 01 ):
  (% class="box infomessage" %)
@@ -1001,7 +1001,6 @@
  **AT+AVLIM. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
  )))
--
  * Downlink Payload (prefix 0xAA 00 ):
  (% class="box infomessage" %)
@@ -1022,7 +1022,6 @@
  **AT+ATDC=5. Device won’t response the second trigger within 5 minute after the first trigger.**
  )))
--
  * Downlink Payload (prefix 0xAC ):
  (% class="box infomessage" %)
@@ -1038,7 +1038,6 @@
  There is no AT Command to control Digital Output
--
  * Downlink Payload (prefix 0x02):
  (% class="box infomessage" %)
@@ -1072,7 +1072,6 @@
  There is no AT Command to control Digital Output
--
  * Downlink Payload (prefix 0xA9):
  (% class="box infomessage" %)
@@ -1092,22 +1092,18 @@
 : DO pins will change to an inverter state after timeout
--
  (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Ports status:
  [[image:image-20220524093238-6.png]]
--
  (% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Ports status:
  [[image:image-20220524093328-7.png]]
--
  (% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Ports status:
  [[image:image-20220524093351-8.png]]
--
  (% style="color:#4f81bd" %)**Sixth and Seventh Byte**:
           Latching time. Unit: ms
@@ -1114,7 +1114,6 @@
  Device will upload a packet if downlink code executes successfully.
--
  **Example payload:**
  **~1. A9 01 01 01 01 07 D0**
@@ -1135,13 +1135,12 @@
--==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
++=== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ===
  * AT Command:
  There is no AT Command to control Relay Output
--
  * Downlink Payload (prefix 0x03):
  (% class="box infomessage" %)
@@ -1171,7 +1171,6 @@
  There is no AT Command to control Relay Output
--
  * Downlink Payload (prefix 0x05):
  (% class="box infomessage" %)
@@ -1189,17 +1189,14 @@
 : Relays will change to an inverter state after timeout
--
  (% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
  [[image:image-20220524093831-10.png]]
--
  (% style="color:#4f81bd" %)**Fourth/Fifth Bytes(cc)**(%%): Latching time. Unit: ms
  Device will upload a packet if downlink code executes successfully.
--
  **Example payload:**
  **~1. 05 01 11 07 D0**
@@ -1231,7 +1231,6 @@
  **AT+VOLMAX    ~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]**
  )))
--
  * Downlink Payload (prefix 0xA5):
  (% class="box infomessage" %)
@@ -1258,7 +1258,6 @@
  Bb cc dd ee: number to be set
--
  * Downlink Payload (prefix 0xA8):
  (% class="box infomessage" %)
@@ -1311,16 +1311,17 @@
  )))
++
  == 3.5 Integrate with Mydevice ==
  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:
  (((
--(% style="color:blue" %)**Step 1**(%%): Be sure that your device is programmed and properly connected to the network at this time.
++**Step 1**: Be sure that your device is programmed and properly connected to the network at this time.
  )))
  (((
--(% 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:
++**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:
  )))
  [[image:1653356737703-362.png||height="232" width="732"]]
@@ -1327,13 +1327,12 @@
  [[image:image-20220524094641-11.png||height="390" width="723"]]
--
  [[image:image-20220524094641-12.png||height="402" width="718"]]
--(% style="color:blue" %)**Step 3**(%%): Create an account or log in Mydevices.
++**Step 3**: Create an account or log in Mydevices.
--(% style="color:blue" %)**Step 4**(%%): Search LT-22222-L(for both LT-22222-L / LT-33222-L) and add DevEUI.(% style="display:none" %)
++**Step 4**: Search LT-22222-L(for both LT-22222-L / LT-33222-L) and add DevEUI.(% style="display:none" %)
  Search under The things network
@@ -1340,21 +1340,16 @@
  [[image:1653356838789-523.png||height="337" width="740"]]
--
  After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
  [[image:image-20220524094909-1.png||height="335" width="729"]]
--
  [[image:image-20220524094909-2.png||height="337" width="729"]]
--
  [[image:image-20220524094909-3.png||height="338" width="727"]]
--
  [[image:image-20220524094909-4.png||height="339" width="728"]](% style="display:none" %)
--
  [[image:image-20220524094909-5.png||height="341" width="734"]]

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

Summary

Details

Applications

Navigation