Table of Contents:

1. Introduction

1.1 What is NB-IoT Leaf Moisture Sensor

The Dragino LMS01-NB is a NB-IoT Leaf Moisture Sensor for IoT of Agriculture. It is designed to measure the leaf moisture and temperature, so to send to the platform to analyze the leaf status such as : watering, moisturizing, dew, frozen. The probe is IP67 waterproof.

LMS01-NB detects leaf's moisture and temperature use FDR method, it senses the dielectric constant cause by liquid over the leaf surface, and cover the value to leaf moisture. The probe is design in a leaf shape to best simulate the real leaf characterizes. The probe has as density as 15 leaf vein lines per centimeter which make it can senses small drop and more accuracy.

LMS01-NB supports different uplink methods including MQTT, MQTTs, UDP & TCP for different application requirement, and support uplinks to various IoT Servers.

LMS01-NB supports BLE configure and OTA update which make user easy to use.

LMS01-NB is powered by 8500mAh Li-SOCI2 battery, it is designed for long-term use up to several years.

LMS01-NB has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration.

​ 

1.2 ​Features

• NB-IoT Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 @H-FDD
• Ultra-low power consumption
• Monitor Leaf moisture
• Monitor Leaf temperature
• Multiply Sampling and one uplink
• Support Bluetooth v5.1 remote configure and update firmware
• Uplink on periodically
• Downlink to change configure
• IP66 Waterproof Enclosure
• IP67 rate for the Sensor Probe
• 8500mAh Battery for long term use
• Nano SIM card slot for NB-IoT SIM

1.3 Specification

Common DC Characteristics:

• Supply Voltage: 2.5v ~ 3.6v
• Operating Temperature: -40 ~ 85°C

Leaf Moisture: percentage of water drop over total leaf surface

• Range: 0~100%
• Resolution: 0.1%
• Accuracy: ±3%(0 ~ 50%); ±6%(>50%)
• IP67 Protection
• Length: 3.5 meters

Leaf Temperature:

• Range: -50 ~ 80°C
• Resolution: 0.1°C
• Accuracy: <±0.5°C(-10°C ~ 70°C),<±1.0°C (others)
• IP67 Protection
• Length: 3.5 meters

NB-IoT Spec:

NB-IoT Module: BC660K-GL

Support Bands:

• B1 @H-FDD: 2100MHz
• B2 @H-FDD: 1900MHz
• B3 @H-FDD: 1800MHz
• B4 @H-FDD: 2100MHz
• B5 @H-FDD: 860MHz
• B8 @H-FDD: 900MHz
• B12 @H-FDD: 720MHz
• B13 @H-FDD: 740MHz
• B17 @H-FDD: 730MHz
• B18 @H-FDD: 870MHz
• B19 @H-FDD: 870MHz
• B20 @H-FDD: 790MHz
• B25 @H-FDD: 1900MHz
• B28 @H-FDD: 750MHz
• B66 @H-FDD: 2000MHz
• B70 @H-FDD: 2000MHz
• B85 @H-FDD: 700MHz

Battery:

• Li/SOCI2 un-chargeable battery
• Capacity: 8500mAh
• Self Discharge: <1% / Year @ 25°C
• Max continuously current: 130mA
• Max boost current: 2A, 1 second

Power Consumption

• STOP Mode: 10uA @ 3.3v
• Max transmit power: 350mA@3.3v

1.4 Applications

• Smart Agriculture

1.5 Mechanical

​

​

​

1.6 Sleep mode and working mode

Deep Sleep Mode: Sensor doesn't have any NB-IoT activate. This mode is used for storage and shipping to save battery life.

Working Mode: In this mode, Sensor will work as NB-IoT Sensor to Join NB-IoT network and send out sensor data to server. Between each sampling/tx/rx periodically, sensor will be in IDLE mode), in IDLE mode, sensor has the same power consumption as Deep Sleep mode.

1.7 Button & LEDs

​

Note: When the device is executing a program, the buttons may become invalid. It is best to press the buttons after the device has completed the program execution.

1.8 BLE connection

LMS01-NB support BLE remote configure and firmware update.

BLE can be used to configure the parameter of sensor or see the console output from sensor. BLE will be only activate on below case:

• Press button to send an uplink
• Press button to active device.
• Device Power on or reset.

If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode.

1.9 Pin Definitions , Switch & SIM Direction

​

1.9.1 Jumper JP2

Power on Device when put this jumper.

1.9.2 BOOT MODE / SW1

1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.

2) Flash: work mode, device starts to work and send out console output for further debug

1.9.3 Reset Button

Press to reboot the device.

1.9.4 SIM Card Direction

See this link. How to insert SIM Card.

2. Use LMS01-NB to communicate with IoT Server

2.1 Send data to IoT server via NB-IoT network

The LMS01-NB is equipped with a NB-IoT module, the pre-loaded firmware in LMS01-NB will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by LMS01-NB.

Below shows the network structure:

​

There are two version: -GE and -1D version of LMS01-NB.

GE Version: This version doesn't include SIM card or point to any IoT server. User needs to use AT Commands to configure below two steps to set LMS01-NB send data to IoT server.

• Install NB-IoT SIM card and configure APN. See instruction of Attach Network.

• Set up sensor to point to IoT Server. See instruction of Configure to Connect Different Servers.  

Below shows result of different server as a glance.

1D Version: This version has 1NCE SIM card pre-installed and configure to send value to DataCake. User Just need to select the sensor type in DataCake and Activate LMS01-NB and user will be able to see data in DataCake. See here for DataCake Config Instruction.

2.2 ​Payload Types

To meet different server requirement, LMS01-NB supports different payload type.

Includes:

• General JSON format payload. (Type=5)

• HEX format Payload. (Type=0)

• ThingSpeak Format. (Type=1)

• ThingsBoard Format. (Type=3)

User can specify the payload type when choose the connection protocol. Example:

AT+PRO=2,0            // Use UDP Connection & hex Payload

AT+PRO=2,5            // Use UDP Connection & Json Payload

AT+PRO=3,5            // Use MQTT Connection & Json Payload

2.2.1 General Json Format(Type=5)

This is the General Json Format. As below:

{"IMEI":"863663062798914","Model":"LMS01-NB","humidity":1.2,"temperature":24.6,"interrupt":0,"interrupt_level":0,"battery":3.38,"signal":15,"1":[24.6,1.2,"2024/05/27 08:55:44"],"2":[24.9,1.2,"2024/05/27 08:40:44"],"3":[25.1,1.2,"2024/05/27 08:25:44"],"4":[24.5,1.2,"2024/05/27 08:10:44"],"5":[24.6,1.2,"2024/05/27 07:55:44"],"6":[24.3,63.8,"2024/05/27 06:24:12"],"7":[24.6,63.4,"2024/05/27 06:21:12"],"8":[24.4,62.6,"2024/05/27 06:18:12"]}

​

Notice, from above payload:

• Humidity,Temperature ,Interrupt, Interrupt_level, Battery & Signal are the value at uplink time.

• Json entry 1 ~ 8 are the last 1 ~ 8 sampling data as specify by AT+CLOCKLOG=1,65535,15,8  Command. Each entry includes (from left to right): Leaf Moisture, Leaf Temperature & Sampling time.

2.2.2 HEX format Payload(Type=0)

This is the HEX Format. As below:

f863663062798914077b0d2f13010000000c00f766544e3500f6000c66544a9000f9000c6654470c00fb000c6654438800f5000c6654400400f6000c66543c8000f3027e6654270c00f6027a6654265800f40272665425a4

​

If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.

​

Version:

These bytes include the hardware and software version.

Higher byte: Specify Sensor Model: 0x07 for LMS01-NB

Lower byte: Specify the software version: 0x7b=123, means firmware version 1.2.3

BAT (Battery Info):

Ex1: 0x0CC6 = 3270mV

Signal Strength:

NB-IoT Network signal Strength.

Ex1: 0x18 = 24

0        -113dBm or less

1        -111dBm

2...30 -109dBm... -53dBm

31      -51dBm or greater

99      Not known or not detectable

 DS18B20 Temperature sensor

This is optional, user can connect external DS18B20 sensor to the +3.3v, one-wire and GND pin . and this field will report temperature.

Example:

If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree

If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.

Leaf Moisture

Range: 0 ~ 100%

Example:

0x0015(H) = 21(D) /10= 2.1%

Leaf Temperature

Get Leaf Temperature  

Example:

If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree

If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.

Interrupt:

This data field shows if this packet is generated by interrupt or not. 

Example:

0x00: Normal uplink packet.

0x01: Interrupt Uplink Packet.

Interrupt_level:

This byte shows whether the interrupt is triggered by a high or low level.

Ex1: 0x00  Interrupt triggered by falling edge (low level)

Ex2: 0x01  Interrupt triggered by rising edge (high level)

TimeStamp:   

Unit TimeStamp Example: 64d49439(H) = 1691653177(D)

Put the decimal value into this link(https://www.epochconverter.com)) to get the time.

2.2.3 ThingsBoard Payload(Type=3)

Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard.

 {
    "topic": "2276492",
    "payload": {
        "IMEI": "863663062798914",
        "Model": "LMS01-NB",
        "humidity": 1.2,
        "temperature": 24.6,
        "interrupt": 0,
        "interrupt_level": 0,
        "battery": 3.38,
        "signal": 17,
        "1": [24.6, 1.2, "2024/05/27 08:55:44"],
        "2": [24.9, 1.2, "2024/05/27 08:40:44"],
        "3": [25.1, 1.2, "2024/05/27 08:25:44"],
        "4": [24.5, 1.2, "2024/05/27 08:10:44"],
        "5": [24.6, 1.2, "2024/05/27 07:55:44"],
        "6": [24.3, 63.8, "2024/05/27 06:24:12"],
        "7": [24.6, 63.4, "2024/05/27 06:21:12"],
        "8": [24.4, 62.6, "2024/05/27 06:18:12"]
    }
}

​

2.2.4 ThingSpeak Payload(Type=1)

This payload meets ThingSpeak platform requirement. It includes only four fields. Form 1~4 are:

Humidity,Temperature ,Battery & Signal. This payload type only valid for ThingsSpeak Platform.

As below:

field1=Humidity value&field2=Temperature value&field3=Battery value&field4=Signal value

​

2.3 Test Uplink and Change Update Interval

By default, Sensor will send uplinks every 2 hours & AT+NOUD=8

User can use below commands to change the uplink interval.

AT+TDC=7200        // Set Update Interval to 7200s

User can also push the button for more than 1 seconds to activate an uplink.

2.4 Multi-Samplings and One uplink

Notice: The AT+NOUD feature is upgraded to Clock Logging, please refer Clock Logging Feature.

To save battery life, LMS01-NB will sample temperature & humidity data every 15 minutes and send one uplink every 2 hours. So each uplink it will include 8 stored data + 1 real-time data. They are defined by:

• AT+TR=900        // The unit is seconds, and the default is to record data once every 900 seconds (15 minutes, the minimum can be set to 180 seconds)

• AT+NOUD=8     //  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.

The diagram below explains the relationship between TR, NOUD, and TDC more clearly:

​

2.5 Trggier an uplink by external interrupt

LMS01-NB has an external trigger interrupt function. Users can use the GPIO_EXTI pin to trigger the upload of data packets.

AT command:

• AT+INTMOD         // Set the trigger interrupt mode

• AT+INTMOD=0    // Disable Interrupt

• AT+INTMOD=1    // Trigger by rising and falling edge

• AT+INTMOD=2    // Trigger by falling edge

• AT+INTMOD=3    // Trigger by rising edge

2.6 Installation

LMS01-NB probe has two sides. The side without words are the sense side. Please be ware when install the sensor.

​ ​

2.7 Clock logging (Since firmware version v1.2.1)

Sometimes when we deploy lots of end nodes in field. We want all sensors sample data at the same time, and upload these data together for analyze. In such case, we can use clock loging feature.

We can use this command to set the start time of data recording and the time interval to meet the requirements of the specific collection time of data.

• AT command: AT+CLOCKLOG=a,b,c,d

a: 0: Disable Clock logging.   1: Enable Clock Logging

b: Specify First sampling start second: range (0 ~ 3599, 65535)         // Note: If parameter b is set to 65535, the log period starts after the node accesses the network and sends packets.

c: Specify the sampling interval: range (0 ~ 255 minutes)

d: How many entries should be uplink on every TDC (max 32)

Note: To disable clock recording, set the following parameters: AT+CLOCKLOG=1,65535,0,0

Example:

AT+CLOCKLOG=1,65535,1,5

After the node sends the first packet, data is recorded to the memory at intervals of 1 minute. For each TDC uplink, the uplink load will include: battery information + the last 5 memory records (payload + timestamp).

Note: Users need to synchronize the server time before configuring this command. If the server time is not synchronized before this command is configured, the command takes effect only after the node is reset.

• Downlink command:  0x0A

Format: Command Code (0x0A) followed by 5 bytes.

• Example 1: Downlink Payload: 0A01FFFF0F08             // Set SHT record time: AT+CLOCKLOG=1,65535,15,8
• Example 1: Downlink Payload: 0A0104B00F08             // Set SHT record time: AT+CLOCKLOG=1,1200,15,8

Note: When entering the downlink payload, there must be no Spaces between bytes.

2.8 Humidity and Temperature alarm function

On each sampling define by AT+TR ( default 900s or 15 minutes), when the value exceed the range, it will trigger an Alarm and immediately sends a uplink. 

AT command: 

AT+ SHHUM=min,max

Example: AT+ SHHUM=50,80     // Alarm when humidity lower than 50 or higher than 80.

AT+ SHTEMP=min,max

Example: AT+ SHTEMP=20,30   // Alarm when temperature lower than 20 or higher than 30

Notice:

• To disable Alarm, user can set min and max to same value , such as AT+ SHTEMP=0,0.

• If user only want to send only min or max, user can set the alarm to a value that device won’t reach. For example: AT+ SHTEMP=-80,0.

2.9 Example Query saved historical records

• AT command: AT+CDP

This command can be used to search the saved history, recording up to 32 groups of data, each group of historical data contains a maximum of 100 bytes.

2.10 Uplink log query

• AT command: AT+GETLOG

This command can be used to query upstream logs of data packets.

2.11 Scheduled domain name resolution

This command is used to set up scheduled domain name resolution.

AT command:

• AT+DNSTIMER=XX   // Unit: hour

After setting this command, domain name resolution will be performed regularly.

2.12 Set the QoS level

This command is used to set the QoS level of MQTT.

AT command:

• AT+MQOS=xx   // 0~2

Downlink command:  0x07

Format: Command Code (0x07) followed by 1 byte.

Ex1: Downlink payload: 0x0700   //AT+MQOS=0

Ex2: Downlink payload: 0x0701   //AT+MQOS=1

3. Configure LMS01-NB

3.1 Configure Methods

LMS01-NB supports below configure method:

• AT Command via Bluetooth Connection (Recommended): BLE Configure Instruction.

• AT Command via UART Connection : See UART Connection.

3.2  Serial Access Password

After the Bluetooth or UART connection is successful, use the Serial Access Password to enter the AT command window.

The label on the box of the node will print the initial password: AT+PIN=xxxxxx, and directly use the six-digit password to access the AT instruction window.

If you need to change the password, use AT+PWORD=xxxxxx (6 characters), NB nodes only support lowercase letters.

Note: After entering the command, you need to add a line break, and you can also set automatic line breaks in the Bluetooth tool or UART connection tool.

3.3 AT Commands Set

AT+<CMD>?           : Help on <CMD>

AT+<CMD>                      : Run <CMD>

AT+<CMD>=<value>      : Set the value

AT+<CMD>=?          : Get the value

General Commands       

AT                    : Attention        

AT?                  : Short Help      

ATZ                 : MCU Reset     

AT+TDC          : Application Data Transmission Interval

AT+CFG          : Print all configurations

AT+CFGMOD           : Working mode selection

AT+DEUI                  : Get or set the Device ID

AT+INTMOD            : Set the trigger interrupt mode

AT+5VT           : Set extend the time of 5V power   

AT+PRO          : Choose agreement

AT+RXDL        : Extend the sending and receiving time

AT+DNSCFG   : Get or Set DNS Server

AT+GETSENSORVALUE   : Returns the current sensor measurement

AT+NOUD  : Get or Set the number of data to be uploaded

AT+CDP     : Read or Clear cached data

AT+SHTEMP:   Get or Set alarm of temp

AT+SHHUM:   Get or Set alarm of moisture

AT+SERVADDR :   Server Address

MQTT Management

AT+CLIENT               : Get or Set MQTT client

AT+UNAME              : Get or Set MQTT Username

AT+PWD                  : Get or Set MQTT password

AT+PUBTOPIC          : Get or Set MQTT publish topic

AT+SUBTOPIC          : Get or Set MQTT subscription topic

Information           

AT+FDR              : Factory Data Reset

AT+PWORD        : Serial Access Password

AT+LDATA           : Get the last upload data

AT+CDP               : Read or Clear cached data

4. Battery & Power Consumption

LMS01-NB use ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.

Battery Info & Power Consumption Analyze .

5. Firmware update

User can change device firmware to::

• Update with new features.

• Fix bugs. 

Firmware and changelog can be downloaded from : Firmware download link

Methods to Update Firmware:

• (Recommended way) OTA firmware update via BLE: Instruction.

• Update through UART TTL interface : Instruction.

6. FAQ

6.1 How can I access t BC660K-GL AT Commands?

User can access to BC660K-GL directly and send AT Commands.

See BC660K-GL AT Command set

7. Order Info

Part Number: LMS01-NB-XX

XX: 

• GE: General version ( Exclude SIM card)

• 1T: with 1NCE * 10 years 500MB SIM card and Pre-configure to ThingsEye server

8. ​Packing Info

Package Includes:

• LMS01-NB NB-IoT Leaf Moisture Sensor x 1

• External antenna x 1

Dimension and weight:

• Device Size: cm

• Device Weight: g

• Package Size / pcs : cm

• Weight / pcs : g

9. Support

• Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.

• Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to Support@dragino.cc.