Table of Contents:

• 1. Introduction
  • 1.1 What is LDS40-NB NB-IoT LiDAR ToF Distance Sensor
  • 1.2 ​Features
  • 1.3 Specification
  • 1.4 Applications
  • 1.5 Sleep mode and working mode
  • 1.6 Button & LEDs
  • 1.7 BLE connection
  • 1.8 Pin Definitions , Switch & SIM Direction
    • 1.8.1 Jumper JP2
    • 1.8.2 BOOT MODE / SW1
    • 1.8.3 Reset Button
    • 1.8.4 SIM Card Direction
  • 1.9 Mechanical
• 2. Use LDS40-NB to communicate with IoT Server
  • 2.1 Send data to IoT server via NB-IoT network
  • 2.2 ​Payload Types
    • 2.2.1 General Json Format(Type=5)
    • 2.2.2 HEX format Payload(Type=0)
    • 2.2.3 ThingsBoard Payload(Type=3)
    • 2.2.4 ThingSpeak Payload(Type=1)
  • 2.3 Test Uplink and Change Update Interval
  • 2.4 Multi-Samplings and One uplink
  • 2.5 Trggier an uplink by external interrupt
  • 2.6 LiDAR ToF Measurement
    • 2.6.1 Principle of Distance Measurement
    • 2.6.2 Distance Measurement Characteristics
    • 2.6.3 Notice of usage
    • 2.6.4 Reflectivity of different objects
  • 2.7 Set Transmit Interval Time
  • 2.8 Clock logging (Since firmware version v1.2.1)
  • 2.9 Example Query saved historical records
• 3. Configure LDS40-NB
  • 3.1 Configure Methods
  • 3.2 AT Commands Set
• 4. Battery & Power Consumption
• 5. Firmware update
• 6. FAQ
  • 6.1 How can I access t BC660K-GL AT Commands?
• 7. Trouble Shooting
  • 7.1 Significant error between the output distant value of LiDAR and actual distance
• 8. Order Info
• 9. ​Packing Info
• 10. Support

1. Introduction

1.1 What is LDS40-NB NB-IoT LiDAR ToF Distance Sensor

The Dragino LDS40-NB is a NB-IoT LiDAR ToF (Time of Flight) Distance Sensor for Internet of Things solution.  It is capable of measuring the distance to objects as close as 0m to 40m. The LiDAR probe uses laser induction technology for distance measurement.

The LDS40-NB can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.

It detects the distance between the measured object and the sensor, and uploads the value via wireless to NB-IoT IoT Server.

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

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

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

LDS40-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
• Laser technology for distance detection
• Measure Distance: 0.1m ~ 40m @ 90% Reflectivity; 0.1m ~ 13.5m @ 10% Reflectivity
• Distance resolution: 1cm
• Multiply Sampling and one uplink
• Support Bluetooth v5.1 remote configure and update firmware
• Uplink on periodically
• Downlink to change configure
• IP65 Waterproof Enclosure
• 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

Probe Specification:

• Storage temperature：-30°C~80°C
• Operating temperature: -20°C~60°C
• Measure Distance:
  • 0.1m ~ 40m @ 90% Reflectivity
  • 0.1m ~ 13.5m @ 10% Reflectivity
• Distance resolution: 1cm
• Ambient light immunity: 100klux
• Enclosure rating : IP65
• Light source : VCSEL
• Central wavelength : 850nm
• FOV : 3°
• Material of enclosure : ABS+PC
• Wire length : 75cm

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

• Horizontal distance measurement
• Parking management system
• Object proximity and presence detection
• Intelligent trash can management system
• Robot obstacle avoidance
• Automatic control
• Sewer

1.5 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.6 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.7 BLE connection

LDS40-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.8 Pin Definitions , Switch & SIM Direction

1.8.1 Jumper JP2

Power on Device when put this jumper.

1.8.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.8.3 Reset Button

Press to reboot the device.

1.8.4 SIM Card Direction

See this link. How to insert SIM Card.

1.9 Mechanical

Probe Mechanical:

2. Use LDS40-NB to communicate with IoT Server

2.1 Send data to IoT server via NB-IoT network

The LDS40-NB is equipped with a NB-IoT module, the pre-loaded firmware in LDS40-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 LDS40-NB.

Below shows the network structure:

There are two version: -GE and -1D version of LDS40-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 LDS12-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 LDS40-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, LDS40-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":"866207052559857","Model":"LDS40-NB","ds18b20_temperature":-0.1,"distance":357,"distance_signal_strength":1285,"temperature":29,"battery":3.51,"signal":22,"1":{358,1301,27,2023/11/06 10:01:07},"2":{357,1293,27,2023/11/06 09:46:07},"3":{67,3047,27,2023/11/06 08:56:32},"4":{12,1262,27,2023/11/06 08:21:48},"5":{10,5873,29,2023/11/06 07:52:21},"6":{2175,736,46,2023/11/06 07:05:43},"7":{2204,843,51,2023/11/06 06:42:58},"8":{2252,995,58,2023/11/06 06:27:58}}

Notice, from above payload:

• DS18b20_temperature, Distance, Distance signal strength, Temperature, Battery & Signal are the value at uplink time.

• Json entry 1 ~ 8 are the last 1 ~ 8 sampling data as specify by AT+NOUD=8  Command. Each entry includes (from left to right): Distance, Distance signal strength, LIDAR Temperature, Sampling time.

2.2.2 HEX format Payload(Type=0)

This is the HEX Format. As below:

f86620705255985710640dba1a01000000000b04e3001c65489ec5000a16f1001d65489b35087f02e0002e65489047089c034b003365488af208cc03e3003a6548876e08bb018c001e6548806a08cb018f001e654879d308cf018d001e6548764e08d60189001d654872ca

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: 0x10 for LDS40-NB

Lower byte: Specify the software version: 0x64=100, means firmware version 1.0.0

BAT (Battery Info):

Ex1: 0x0DB4 = 3508mV

DS18B20 Temperature sensor:

This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-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.

Distance:

Represents the distance value of the measurement output, the default unit is cm, and the value range parsed as a decimal number is 0-4000. In actual use, when the signal strength value Strength.

Example:

If the data you get from the register is 0x0B 0xEA, the distance between the sensor and the measured object is 0BEA(H) = 3050 (D)/10 = 305cm.

Distance signal strength:

Refers to the signal strength, the default output value will be between 0-65535. When the ranging gear is fixed, the farther the ranging, the lower the signal strength.

In actual use, when the signal strength value Strength≤60, the measured value of Dist is considered unreliable, and the default output is 4500. When the signal strength is greater than 60 and the actual distance is and the actual distance is 45~60m, the output value of Dist is 4500. When the signal strength is greater than 60 and the actual distance is more than 60m, there will be over-period data appearing as 0 or other abnormal values.

Example:

If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.

Customers can judge whether they need to adjust the environment based on the signal strength.

Interrupt Pin & Interrupt Level:

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

Note: The Internet Pin is a separate pin in the screw terminal. 

Example:

If byte[0]&0x01=0x00 : Normal uplink packet.

If byte[0]&0x01=0x01 : Interrupt Uplink Packet.

LiDAR temp:

Characterize the internal temperature value of the sensor.

Example: 

If payload is: 001C(H) <<24>>24=28(D), LiDAR temp=28°C.

If payload is: FFF2(H) <<24>>24=-14(D), LiDAR temp=-14°C.

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.

 { "IMEI": "866207052559857",
        "Model": "LDS40-NB",
        "ds18b20_temperature": -0.1,
        "distance": 356,
        "distance_signal_strength": 1298,
        "temperature": 28,
        "battery": 3.49,
        "signal": 22
    }

2.2.4 ThingSpeak Payload(Type=1)

This payload meets ThingSpeak platform requirement. It includes six fields. Form 1~6 are:

DS18b20_temperature, Distance, Distance signal strength, Temperature, Battery & Signal. This payload type only valid for ThingsSpeak Platform.

As below:

field1=Distance value&field2=Distance signal strength value&field3=Temperature value&field4=Battery value&field5=Signal value&field6=DS18B20_temperature 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=600        // Set Update Interval to 600s

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

2.4 Multi-Samplings and One uplink

To save battery life, LDS40-NB will sample distance 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

LDS40-NB has an external trigger interrupt function. Users can use the PB15 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 LiDAR ToF Measurement

2.6.1 Principle of Distance Measurement

The LiDAR probe is based on TOF, namely, Time of Flight principle. To be specific, the product emits modulation wave of near infrared ray on a periodic basis, which will be reflected after contacting object. The product obtains the time of flight by measuring round-trip phase difference and then calculates relative range between the product and the detection object, as shown below.

2.6.2 Distance Measurement Characteristics

The detection angle of the LDS40-NB is 3 degrees, and the size of the light spot at different distances is the side length of the detection range. The size of the light spot at different distances is the side length of the detection range. The side length of the detection range (the shape is square), as shown.

Note that generally, the side length of the detected target object should be greater than the side length of the detection range of the LDS40-NB; when the detected object is smaller than the detection range side length; when the detected object is smaller than the detection range side length, the effective range of the radar will be reduced.

2.6.3 Notice of usage

Possible invalid /wrong reading for LiDAR ToF tech:

• Measure high reflectivity object such as: Mirror, Smooth ceramic tile, static milk surface, will have possible wrong readings.

• While there is transparent object such as glass, water drop between the measured object and the LiDAR sensor, the reading might be wrong.

• The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.

• The sensor window is made by Acrylic. Don't touch it with alcohol material. This will destroy the sensor window.

2.6.4 Reflectivity of different objects

2.7 Set Transmit Interval Time

• Example 1: Downlink Payload: 0100001E       // Set Transmit Interval (TDC) = 30 seconds

• Example 2: Downlink Payload: 0100003C      // Set Transmit Interval (TDC) = 60 seconds  

2.8 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)

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.

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.

3. Configure LDS40-NB

3.1 Configure Methods

LDS40-NB supports below configure method:

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

• AT Command via UART Connection : See UART Connection.

3.2 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+ALARM:      Get or Set alarm of distance

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

LDS40-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. Trouble Shooting

7.1 Significant error between the output distant value of LiDAR and actual distance

8. Order Info

Part Number: LDS40-NB-XX

XX: 

• GE: General version ( Exclude SIM card)

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

1NCE SIM Card NB-IoT network coverage: Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands

9. ​Packing Info

Package Includes:

• LDS40-NB NB-IoT LiDAR ToF Distance sensor x 1

• External antenna x 1

Dimension and weight:

• Device Size: 13.0 x 5 x 4.5 cm

• Device Weight: 150g

• Package Size / pcs : 14.0 x 8x 5 cm

• Weight / pcs : 180g

10. 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.