LHT65N-VIB LoRaWAN Vibration Sensor Manual
Table of Contents:
- 1. Introduction
- 2. Connect LHT65N-VIB to IoT Server
- 4. Configure LHT65N-VIB via AT command or LoRaWAN downlink
- 4.1 Set Transmit Interval Time
- 4.2 Set Vibration Sensor Mode
- 4.3 Vibration sensitivity setting
- 4.4 Set Password
- 4.5 Quit AT Command
- 4.6 Set to sleep mode
- 4.7 Set system time
- 4.8 Set Time Sync Mode
- 4.9 Set Time Sync Interval
- 4.10 Get data
- 4.11 Print data entries base on page
- 4.12 Print last few data entries
- 4.13 Clear Flash Record
- 4.14 Auto Send None-ACK messages
- 5. Battery & How to replace
- 6. FAQ
- 7. Order Info
- 8. Packing Info
- 9. Reference material
- 10. FCC Warning
1. Introduction
1.1 What is LHT65N-VIB LoRaWAN Vibration Sensor
The Dragino LHT65N-VIB LoRaWAN Vibration Sensor is designed to detect and measure vibrations, shocks, or accelerations of an object. By analyze the motion of the object, LHT65N-VIB can send meaningful resulte such as: Alarm, device runtime, counting, vibration strenght to IoT platform for further analyze.
It targets professional wireless sensor network applications such as monitoring equipment status, water leakage alarm, usage statistics, vibration intensity detection, etc.
LHT65N-VIB supports Datalog Feature. It will record the data when there is no network coverage and users can retrieve the sensor value later to ensure no miss for every sensor reading.
The LHT65N-VIB allows users to send data and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption.
LHT65N-VIB has a built-in 2400mAh non-chargeable battery which can be used for up to 3 years*.
LHT65N-VIB is full compatible with LoRaWAN v1.0.3 Class A protocol, it can work with a standard LoRaWAN gateway.
*The actual battery life depends on how often to send data, please see the battery analyzer chapter.
1.2 Features
- LoRaWAN v1.0.3 Class A protocol
- Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915
- Detecting object vibration status
- Detect vibration alarm
- 3-axis accelerator for x,y,z
- Calcula device runtime
- Built-in 2400mAh battery for long time use
- Built-in Temperature & Humidity sensor
- Tri-color LED to indicate working status
- Datalog feature (Max 3328 records)
- AT Commands to change parameters
- Remote configure parameters via LoRaWAN Downlink
- Firmware upgradeable via program port
1.3 Specification
Built-in Temperature Sensor:
- Resolution: 0.01 °C
- Accuracy Tolerance : Typ ±0.3 °C
- Long Term Drift: < 0.02 °C/yr
- Operating Range: -40 ~ 85 °C
Built-in Humidity Sensor:
- Resolution: 0.04 %RH
- Accuracy Tolerance : Typ ±3 %RH
- Long Term Drift: < 0.25 RH/yr
- Operating Range: 0 ~ 96 %RH
External Vibration Sensor:
- Detecting object vibration status
- accelerator for x,y,z
- Small size for easy installation
- Acceleration: ±2g,±4g,±8g;±16g
- Frequency: 25Hz,50Hz,100Hz,200Hz,400Hz
2. Connect LHT65N-VIB to IoT Server
2.1 How does LHT65N-VIB work?
LHT65N-VIB is configured as LoRaWAN OTAA Class A mode by default. Each LHT65N-VIB is shipped with a worldwide unique set of OTAA keys. To use LHT65N-VIB in a LoRaWAN network, first, we need to put the OTAA keys in LoRaWAN Network Server and then activate LHT65N-VIB.
If LHT65N-VIB is under the coverage of this LoRaWAN network. LHT65N-VIB can join the LoRaWAN network automatically. After successfully joining, LHT65N-VIB will start to measure environment temperature and humidity, and start to transmit sensor data to the LoRaWAN server. The default period for each uplink is 20 minutes.
2.2 How to Activate LHT65N-VIB?
The LHT65N-VIB has two working modes:
Deep Sleep Mode: LHT65N-VIB doesn't have any LoRaWAN activation. This mode is used for storage and shipping to save battery life.
Working Mode: In this mode, LHT65N-VIB works as LoRaWAN Sensor mode to Join LoRaWAN network and send out the sensor data to the server. Between each sampling/tx/rx periodically, LHT65N-VIB will be in STOP mode (IDLE mode), in STOP mode, LHT65N has the same power consumption as Deep Sleep mode.
The LHT65N-VIB is set in deep sleep mode by default; The ACT button on the front is to switch to different modes:
| Behavior on ACT | Function | Action |
|---|---|---|
| Pressing ACT between 1s < time < 3s | Test uplink status | If LHT65N-VIB is already Joined to rhe LoRaWAN network, LHT65N will send an uplink packet, if LHT65N has external sensor connected,Blue led will blink once. If LHT65N-VIB has not external sensor, Red led will blink once. |
| Pressing ACT for more than 3s | Active Device | Green led will fast blink 5 times, LHT65N-VIB will enter working mode and start to JOIN LoRaWAN network. |
| Fast press ACT 5 times. | Deactivate Device | Red led will solid on for 5 seconds. Means LHT65N-VIB is in Deep Sleep Mode. |
2.3 Example to join LoRaWAN network
This section shows an example of how to join the TTN V3 LoRaWAN IoT server. Use with other LoRaWAN IoT servers is of a similar procedure.
Assume the LPS8v2 is already set to connect to TTN V3 network, So it provides network coverage for LHT65N-VIB. Next we need to add the LHT65N-VIB device in TTN V3:
2.3.1 Step 1: Create Device on TTN
Create a device in TTN V3 with the OTAA keys from LHT65N-VIB.
Each LHT65N-VIB is shipped with a sticker with its device EUI, APP Key and APP EUI as below:
User can enter these keys in the LoRaWAN Server portal. Below is TTN V3 screenshot:
Add APP EUI in the application.
1. Create application
Add APP EUI and DEV EUI
Add APP EUI in the application
Add APP KEY
2.3.2 Step 2: Activate LHT65N-VIB by pressing the ACT button for more than 5 seconds.
Use ACT button to activate LHT65N-VIB and it will auto-join to the TTN V3 network. After join success, it will start to upload sensor data to TTN V3 and user can see in the panel.
2.3.3 Decoder in TTN V3
When the uplink payload arrives TTNv3, it shows HEX format and not friendly to read. We can add LHT65N-VIB decoder in TTNv3 for friendly reading.
Below is the position to put the decoder and LHT65N-VIB decoder can be download from here: https://github.com/dragino/dragino-end-node-decoder
2.4 Uplink Payload (Fport=2)
The uplink payload includes totally 11 bytes. Uplink packets use FPORT=2 and every 20 minutes send one uplink by default.
After each uplink, the BLUE LED will blink once.
There are four different working modes:
VIBMOD=1 vib count, work min
VIBMOD=2 TempC_SHT, Hum_SHT, vib count
VIBMOD=3 TempC_SHT, Hum_SHT, vib min
VIBMOD=4 X, Y, Z
2.4.1 VIBMOD=1
Size(bytes) | 2 | 1 | 4 | 4 |
|---|---|---|---|---|
Value | BAT | MOD Alarm TDC | vib_count | work_min |
2.4.1.1 BAT-Battery Info
These two bytes of BAT include the actually voltage
Check the battery voltage for LHT65N-VIB.
- 0x0BF2/1000=3.058V
2.4.1.2 VIBMOD and Alarm and TDC
bytes[2]=0x06=0000 0110
Current working mode=(bytes[2]>>2)&0x07=1
Current alarm situation= (bytes[2] & 0x01)? "TRUE":"FALSE";=0=FALSE
Whether the current data occurs is TDC (the data will be uploaded by the alarm)= (bytes[2] & 0x02)? "YES":"NO";=00000010 (non -zero value)=YES
2.4.1.3 vib_count
vib_count it means how many vibration events have been recorded
- 0x00000007=7
2.4.1.4 work_min
It means how long the current vibration sensor has worked in the latest triggering.
- 0x00000000=0
0 means that the current vibration sensor is not triggered.
2.4.2 VIBMOD=2
Size(bytes) | 2 | 1 | 4 | 2 | 2 |
|---|---|---|---|---|---|
Value | BAT | MOD Alarm TDC | vib_count | TempC_SHT | Hum_SHT |
2.4.2.1 BAT-Battery Info
These two bytes of BAT include the actually voltage
Check the battery voltage for LHT65N-VIB.
- 0x0BC6/1000=3.014V
2.4.2.2 VIBMOD and Alarm and TDC
bytes[2]=0x0A=0000 0101
Current working mode=(bytes[2]>>2)&0x07=2
Current alarm situation= (bytes[2] & 0x01)? "TRUE":"FALSE";=0=FALSE
Whether the current data occurs is TDC (the data will be uploaded by the alarm)= (bytes[2] & 0x02)? "YES":"NO";=00000010 (non -zero value)=YES
2.4.2.3 vib_count
vib_count it means how many vibration events have been recorded
- 0x00000000=0
2.4.2.4 TempC_SHT
The temperature detected by the built-in temperature sensor SHT31.
- 0x0B22/100=28.5
2.4.2.5 Hum_SHT
The temperature detected by the built-in humidity sensor SHT31.
- 0x0212/10=53
2.4.3 VIBMOD=3
Size(bytes) | 2 | 1 | 2 | 2 | 4 |
|---|---|---|---|---|---|
Value | BAT | MOD Alarm TDC | TempC_SHT | Hum_SHT | work_min |
2.4.3.1 BAT-Battery Info
These two bytes of BAT include the actually voltage
Check the battery voltage for LHT65N-VIB.
- 0x0BC2/1000=3.01V
2.4.3.2 VIBMOD and Alarm and TDC
bytes[2]=0x0A=0000 1110
Current working mode=(bytes[2]>>2)&0x07=3
Current alarm situation= (bytes[2] & 0x01)? "TRUE":"FALSE";=0=FALSE
Whether the current data occurs is TDC (the data will be uploaded by the alarm)= (bytes[2] & 0x02)? "YES":"NO";=00000010 (non -zero value)=YES
2.4.3.3 TempC_SHT
The temperature detected by the built-in temperature sensor SHT31.
- 0x0B21/100=28.49
2.4.3.4 Hum_SHT
The temperature detected by the built-in humidity sensor SHT31.
- 0x0213/10=53.1
2.4.3.5 work_min
It means how long the current vibration sensor has worked in the latest triggering.
- 0x00000000=0
0 means that the current vibration sensor is not triggered.
2.4.4 VIBMOD=4(FPORT=7)
Size(bytes) | 2 | 2 | 2 | 2 | 2 |
|---|---|---|---|---|---|
Value | BAT | X | Y | Z | ...... |
X=0xFC50 In binary, it is represented as 1111110000110111, the highest bit is 1, indicating a negative number, and its complement is -977
Y=0x0014=20
Z=0x00F6=246
2.5 Show data on Datacake
Datacake IoT platform provides a human-friendly interface to show the sensor data, once we have sensor data in TTN V3, we can use Datacake to connect to TTN V3 and see the data in Datacake. Below are the steps:
Step 1: Be sure that your device is programmed and properly connected to the LoRaWAN network.
Step 2: Configure your Application to forward data to Datacake you will need to add integration. Go to TTN V3 Console --> Applications --> Integrations --> Add Integrations.
Add Datacake:
Select default key as Access Key:
In Datacake console (https://datacake.co/) , add LHT65 device.
2.8 LED Indicator
The LHT65 has a triple color LED which for easy showing different stage .
While user press ACT button, the LED will work as per LED status with ACT button.
In a normal working state:
- For each uplink, the BLUE LED or RED LED will blink once.
BLUE LED when external sensor is connected. - RED LED when external sensor is not connected
- For each success downlink, the PURPLE LED will blink once
2.9 installation
4. Configure LHT65N-VIB via AT command or LoRaWAN downlink
Use can configure LHT65N-VIB via AT Command or LoRaWAN Downlink.
AT Command Connection: See FAQ.
LoRaWAN Downlink instruction for different platforms: IoT LoRaWAN Server
There are two kinds of commands to configure LHT65N-VIB, they are:
General Commands.
These commands are to configure:
General system settings like: uplink interval.
LoRaWAN protocol & radio-related commands.
They are the same for all Dragino Devices which supports DLWS-005 LoRaWAN Stack(Note**). These commands can be found on the wiki: End Device Downlink Command
Commands special design for LHT65N-VIB
These commands are only valid for LHT65N-VIB, as below:
4.1 Set Transmit Interval Time
Feature: Change LoRaWAN End Node Transmit Interval.
AT Command: AT+TDC
| Command Example | Function | Response |
| AT+TDC=? | Show current transmit Interval | 30000 OK the interval is 30000ms = 30s |
| AT+TDC=60000 | Set Transmit Interval | OK Set transmit interval to 60000ms = 60 seconds |
Downlink Command: 0x01
Format: Command Code (0x01) followed by 3 bytes time value.
If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01.
- Example 1: Downlink Payload: 0100001E // Set Transmit Interval (TDC) = 30 seconds
- Example 2: Downlink Payload: 0100003C // Set Transmit Interval (TDC) = 60 seconds
4.2 Set Vibration Sensor Mode
Feature: Change Vibration Sensor Mode.
AT Command: AT+VIBMOD
| Command Example | Function | Response |
| AT+VIBMOD=MOD,AlarmTime,StopDurationTime | MOD:1,2,3 AlarmTime:Set the duration of continuous operation to trigger the alarm (unit: seconds)( Set AlarmTimeout to 0 disable Alarm) StopDurationTime:After the interval time is exceeded, it will be counted as a trigger | OK |
| AT+VIBMOD=4,Collectioninterval,groups | 4:MOD=4 Collection:Collection interval(unit: seconds) groups:Number of collection groups | OK |
Example:AT+VIBMOD=1,60,10
Mode 1 will display vib_count and work_min without temperature and humidity. If the vibration stops for more than 60 seconds, an alarm message will be generated.
If the vibration stops for more than 10 seconds, vib_count will increase by one and work_min will be reset to zero.
Downlink Command:
Example:
- AT+VIBMOD=1,60,10=0x0A01003c000A
Example:AT+VIBMOD=4,1,10
MOD4 sets the collection interval to 10 second and collects 1 sets of data in total.
Downlink Command:
Example:
- AT+VIBMOD=4,1,10=0x0A0400010A
4.3 Vibration sensitivity setting
Feature: Users can adjust the sensitivity settings according to different usage scenarios.
AT Command:
| Command Example | Function | Response |
| AT+VIBSET=acceleration,frequency,threshold, duration | Acceleration: 0:±2g,1:±4g,2:±8g;3:±16g Frequency: 0:25Hz,1:50Hz,2:100Hz,3:200Hz,4:400Hz Threshold: interrupt threshold Duration: Interrupt detection duration(unit ms) | OK |
Example:AT+VIBSET=0,4,10,12
The acceleration is set to ±2g and the frequency is 400Hz. The Threshold is set to 10*16mg. This means that the change difference between 158-162 can be detected.
I want to detect an event that lasts at least 30 milliseconds, so I set the register to 30/2.5=12 counts. When the time difference between consecutive readings exceeds 12 duration LSBs, an interrupt will be triggered. See the figure below for specific values.
Downlink Command:
- AT+VIBSET=0,4,10,12=0x0900040A0C
4.4 Set Password
Feature: Set device password, max 9 digits
AT Command: AT+PWORD
| Command Example | Function | Response |
| AT+PWORD=? | Show password | 123456 OK |
| AT+PWORD=999999 | Set password | OK |
Downlink Command:
No downlink command for this feature.
4.5 Quit AT Command
Feature: Quit AT Command mode, so user needs to input password again before use AT Commands.
AT Command: AT+DISAT
| Command Example | Function | Response |
| AT+DISAT | Quit AT Commands mode | OK |
Downlink Command:
No downlink command for this feature.
4.6 Set to sleep mode
Feature: Set device to sleep mode
- AT+Sleep=0 : Normal working mode, device will sleep and use lower power when there is no LoRa message
- AT+Sleep=1 : Device is in deep sleep mode, no LoRa activation happen, used for storage or shipping.
AT Command: AT+SLEEP
| Command Example | Function | Response |
| AT+SLEEP | Set to sleep mode | Clear all stored sensor data… OK |
Downlink Command:
- There is no downlink command to set to Sleep mode.
4.7 Set system time
Feature: Set system time, unix format. See here for format detail.
AT Command:
| Command Example | Function |
| AT+TIMESTAMP=1611104352 | OK Set System time to 2021-01-20 00:59:12 |
Downlink Command:
0x306007806000 // Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352
4.8 Set Time Sync Mode
Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply this command.
SYNCMOD is set to 1 by default. If user want to set a different time from LoRaWAN server, user need to set this to 0.
AT Command:
| Command Example | Function |
| AT+SYNCMOD=1 | Enable Sync system time via LoRaWAN MAC Command (DeviceTimeReq) |
Downlink Command:
0x28 01 // Same As AT+SYNCMOD=1
0x28 00 // Same As AT+SYNCMOD=0
4.9 Set Time Sync Interval
Feature: Define System time sync interval. SYNCTDC default value: 10 days.
AT Command:
| Command Example | Function |
| AT+SYNCTDC=0x0A | Set SYNCTDC to 10 (0x0A), so the sync time is 10 days. |
Downlink Command:
0x29 0A // Same as AT+SYNCTDC=0x0A
4.10 Get data
Feature: Get the current sensor data.
AT Command:
- AT+GETSENSORVALUE=0 // The serial port gets the reading of the current sensor
- AT+GETSENSORVALUE=1 // The serial port gets the current sensor reading and uploads it.
4.11 Print data entries base on page
Feature: Print the sector data from start page to stop page (max is 416 pages).
AT Command: AT+PDTA
| Command Example | Function |
AT+PDTA=1,3 | Stop Tx events when read sensor data 8031000 2024/10/12 08:26:16 1 2807 tdc:yes alarm:false event_count:0 work_min:0 8031010 2024/10/12 08:26:40 1 2804 tdc:no alarm:false event_count:0 work_min:0 8031020 1970/1/1 00:00:10 1 2806 tdc:yes alarm:false event_count:0 work_min:0 8031030 2024/10/12 08:28:18 1 2805 tdc:yes alarm:false event_count:0 work_min:0 8031040 2024/10/12 08:29:18 1 2804 tdc:yes alarm:false event_count:0 work_min:0 8031050 2024/10/12 08:30:18 1 2806 tdc:yes alarm:false event_count:1 work_min:0 8031060 2024/10/12 08:30:27 1 2806 tdc:no alarm:true event_count:2 work_min:0 8031070 2024/10/12 08:31:18 1 2806 tdc:yes alarm:false event_count:3 work_min:1 [Rx][16:33:25.888] 8031080 2024/10/12 08:32:18 1 2806 tdc:yes alarm:false event_count:3 work_min:1 8031090 2024/10/12 08:33:18 1 2807 tdc:yes alarm:false event_count:3 work_min:1 80310A0 80310B0 80310C0 80310D0 80310E0 80310F0 8031100 8031110 8031120 8031130 8031140 8031150 8031160 8031170 Start Tx events OK |
Downlink Command:
No downlink commands for feature
4.12 Print last few data entries
Feature: Print the last few data entries
AT Command: AT+PLDTA
| Command Example | Function |
AT+PLDTA=5 | Stop Tx events when read sensor data 0001 2024/10/12 08:33:18 1 2807 tdc:yes alarm:false event_count:3 work_min:1 0002 2024/10/12 08:34:50 1 2808 tdc:yes alarm:false event_count:3 work_min:1 0003 2024/10/12 08:35:50 1 2808 tdc:yes alarm:false event_count:3 work_min:1 0004 2024/10/12 08:36:50 1 2809 tdc:yes alarm:false event_count:3 work_min:1 0005 2024/10/12 08:37:50 1 2810 tdc:yes alarm:false event_count:3 work_min:1 |
Downlink Command:
No downlink commands for feature
4.13 Clear Flash Record
Feature: Clear flash storage for data log feature.
AT Command: AT+CLRDTA
| Command Example | Function | Response |
| AT+CLRDTA | Clear date record | Clear all stored sensor data… OK |
Downlink Command: 0xA3
- Example: 0xA301 // Same as AT+CLRDTA
4.14 Auto Send None-ACK messages
Feature: LHT65N-VIB will wait for ACK for each uplink, If LHT65N-VIB doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. LHT65N-VIB keeps sending messages in normal periodically. Once LHT65N-VIB gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
AT Command: AT+PNACKMD
The default factory setting is 0
| Command Example | Function | Response |
|---|---|---|
| AT+PNACKMD=1 | Poll None-ACK message | OK |
Downlink Command: 0x34
- Example: 0x3401 // Same as AT+PNACKMD=1
5. Battery & How to replace
5.1 Battery Type
LHT65N-VIB is equipped with a 2400mAH Li-MnO2 (CR17505) battery . The battery is an un-rechargeable battery with low discharge rate targeting for up to 8~10 years use. This type of battery is commonly used in IoT devices for long-term running, such as water meters.
The discharge curve is not linear so can't simply use percentage to show the battery level. Below is the battery performance.
The minimum Working Voltage for the LHT65N-VIB is ~ 2.5v. When battery is lower than 2.6v, it is time to change the battery.
5.2 Replace Battery
LHT65N-VIB has two screws on the back, Unscrew them, and changing the battery inside is ok. The battery is a general CR17450 battery. Any brand should be ok.
5.3 Battery Life Analyze
Dragino battery-powered products are all run in Low Power mode. User can check the guideline from this link to calculate the estimated battery life:
https://www.dragino.com/downloads/downloads/LoRa_End_Node/Battery_Analyze/DRAGINO_Battery_Life_Guide.pdf
A full detail test report for LHT65N-VIB on different frequency can be found at : https://www.dropbox.com/sh/r2i3zlhsyrpavla/AAB1sZw3mdT0K7XjpHCITt13a?dl=0
6. FAQ
6.1 How to connect to LHT65N-VIB UART interface?
The LHT65N-VIB has the UART interface in its Type-C. The UART Interface can be used for
- Send AT Commands, and get output from LHT65N-VIB
- Upgrade firmwre of LHT65N-VIB.
The hardware connection is: PC <--> USB to TTL Adapter <--> Jump wires <--> Type-C Adapter <--> LHT65N-VIB
Option of USB TTL adapter:
- CP2101 USB TTL Adapter
- CH340 USB TTL Adapter
- FT232 USB TTL Adapter
Option of Type-C Adapter:
Connection:
- USB to TTL GND <--> LHT65N GND
- USB to TTL RXD <--> LHT65N TXD
- USB to TTL TXD <--> LHT65N RXD
Connection Example:
6.2 How to use AT Commands?
First, Connect PC and LHT65N-VIB via USB TTL adapter as FAQ 6.1
In PC, User needs to set serial tool(such as putty, SecureCRT) baud rate to 9600 to access to access serial console for LHT65N-VIB. The AT commands are disable by default and need to enter password (default:123456) to active it. Timeout to input AT Command is 5 min, after 5-minute, user need to input password again. User can use AT+DISAT command to disable AT command before timeout.
Input password and ATZ to activate LHT65N,As shown below:
AT Command List is as below:
AT+<CMD>? : Help on <CMD>
AT+<CMD> : Run <CMD>
AT+<CMD>=<value> : Set the value
AT+<CMD>=? : Get the value
AT+DEBUG: Set more info output
ATZ: Trig a reset of the MCU
AT+FDR: Reset Parameters to Factory Default, Keys Reserve
AT+DEUI: Get or Set the Device EUI
AT+DADDR: Get or Set the Device Address
AT+APPKEY: Get or Set the Application Key
AT+NWKSKEY: Get or Set the Network Session Key
AT+APPSKEY: Get or Set the Application Session Key
AT+APPEUI: Get or Set the Application EUI
AT+ADR: Get or Set the Adaptive Data Rate setting. (0: off, 1: on)
AT+TXP: Get or Set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Spec)
AT+DR: Get or Set the Data Rate. (0-7 corresponding to DR_X)
AT+DCS: Get or Set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
AT+PNM: Get or Set the public network mode. (0: off, 1: on)
AT+RX2FQ: Get or Set the Rx2 window frequency
AT+RX2DR: Get or Set the Rx2 window data rate (0-7 corresponding to DR_X)
AT+RX1DL: Get or Set the delay between the end of the Tx and the Rx Window 1 in ms
AT+RX2DL: Get or Set the delay between the end of the Tx and the Rx Window 2 in ms
AT+JN1DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
AT+JN2DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
AT+NJM: Get or Set the Network Join Mode. (0: ABP, 1: OTAA)
AT+NWKID: Get or Set the Network ID
AT+FCU: Get or Set the Frame Counter Uplink
AT+FCD: Get or Set the Frame Counter Downlink
AT+CLASS: Get or Set the Device Class
AT+JOIN: Join network
AT+NJS: Get the join status
AT+SENDB: Send hexadecimal data along with the application port
AT+SEND: Send text data along with the application port
AT+RECVB: Print last received data in binary format (with hexadecimal values)
AT+RECV: Print last received data in raw format
AT+VER: Get current image version and Frequency Band
AT+CFM: Get or Set the confirmation mode (0-1)
AT+SNR: Get the SNR of the last received packet
AT+RSSI: Get the RSSI of the last received packet
AT+TDC: Get or set the application data transmission interval in ms
AT+PORT: Get or set the application port
AT+DISAT: Disable AT commands
AT+PWORD: Set password, max 9 digits
AT+CHS: Get or Set Frequency (Unit: Hz) for Single Channel Mode
AT+CHE: Get or Set eight channels mode,Only for US915,AU915,CN470
AT+PDTA: Print the sector data from start page to stop page
AT+PLDTA: Print the last few sets of data
AT+CLRDTA: Clear the storage, record position back to 1st
AT+SLEEP: Set sleep mode
AT+BAT: Get the current battery voltage in mV
AT+CFG: Print all configurations
AT+WMOD: Get or Set Work Mode
AT+ARTEMP: Get or set the internal Temperature sensor alarm range
AT+CITEMP: Get or set the internal Temperature sensor collection interval in min
AT+SETCNT: Set the count at present
AT+RJTDC: Get or set the ReJoin data transmission interval in min
AT+RPL: Get or set response level
AT+TIMESTAMP: Get or Set UNIX timestamp in second
AT+LEAPSEC: Get or Set Leap Second
AT+SYNCMOD: Get or Set time synchronization method
AT+SYNCTDC: Get or set time synchronization interval in day
AT+PID: Get or set the PID
6.3 How to use Downlink commands?
Downlink commands:
TTN:
Helium:
Chirpstack: The downlink window will not be displayed until the network is accessed
AWS-IOT :
6.4 How to change the uplink interval?
Please see this link: http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/
6.5 How to upgrade firmware?
User can change firmware LHT65N-PIR to:
- Change Frequency band/ region.
- Update with new features.
- Fix bugs.
Firmware and changelog can be downloaded from : Firmware download link
Methods to Update Firmware:
- (Recommanded way) OTA firmware update via wireless: http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/
- Update through UART TTL interface. Instruction.
6.6 Why can't I see the datalog information
1. The time is not aligned, and the correct query command is not used.
2. Decoder error, did not parse the datalog data, the data was filtered.
6.7 How can i read sensor data without LoRaWAN? For Calibration Purpose
Some clients need to calibrate the sensor value in calibration Lab. In such case, Reading the data without LoRaWAN network is more convinient. To achieve this, use can use a USB Type-C Breakout board to expose the UART pins while still have the probe connected. See below. Detail Pin out please refer the FAQ of how to connect UART
After there is UART Connectio, run below commands:
1. AT+NJM=0 // Set Device to ABP mode , so can works without join to LoRaWAN server.
2. AT+GETSENSORVALUE=0 //The serial port gets the reading of the current sensor.
Example output:
7. Order Info
Part Number: LHT65N-XX
XX : The default frequency band
- AS923: LoRaWAN AS923 band
- AU915: LoRaWAN AU915 band
- EU433: LoRaWAN EU433 band
- EU868: LoRaWAN EU868 band
- KR920: LoRaWAN KR920 band
- US915: LoRaWAN US915 band
- IN865: LoRaWAN IN865 band
- CN470: LoRaWAN CN470 band
8. Packing Info
Package Includes:
- LHT65N-VIB LoRaWAN Vibration Sensor x 1
9. Reference material
10. FCC Warning
This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
(1) This device may not cause harmful interference;
(2) this device must accept any interference received, including interference that may cause undesired operation.