image-20230614153353-1.png

Table of Contents:

1. Introduction

1.1 What is LoRaWAN LiDAR ToF Distance Sensor

The Dragino LDS12-LB is a LoRaWAN LiDAR ToF (Time of Flight) Distance Sensor for Internet of Things solution. It is capable to measure the distance to an object as close as 10 centimeters (+/- 5cm up to 6m) and as far as 12 meters (+/-1% starting at 6m)!. The LiDAR probe uses laser induction technology for distance measurement.

The LDS12-LB 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 LoRaWAN IoT Server.

The LoRa wireless technology used in LDS12-LB allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption.

LDS12-LB supports BLE configure and wireless OTA update which make user easy to use.

LDS12-LB is powered by 8500mAh Li-SOCI2 battery, it is designed for long term use up to 5 years.

Each LDS12-LB is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect after power on.

image-20230615152941-1.png

1.2 ​Features

  • LoRaWAN 1.0.3 Class A
  • Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
  • Ultra-low power consumption
  • Laser technology for distance detection
  • Measure Distance: 0.1m~12m
  • Accuracy :  ±5cm@(0.1-5m), ±1%@(5m-12m)
  • Monitor Battery Level
  • Support Bluetooth v5.1 and LoRaWAN remote configure
  • Support wireless OTA update firmware
  • AT Commands to change parameters
  • Downlink to change configure
  • 8500mAh Battery for long term use

1.3 Specification

Common DC Characteristics:

  • Supply Voltage: built in 8500mAh Li-SOCI2 battery , 2.5v ~ 3.6v
  • Operating Temperature: -40 ~ 85°C

Probe Specification:

  • Storage temperature:-20℃~75℃
  • Operating temperature : -20℃~60℃
  • Measure Distance:
    • 0.1m ~ 12m @ 90% Reflectivity
    • 0.1m ~ 4m @ 10% Reflectivity
  • Accuracy : ±5cm@(0.1-5m), ±1%@(5m-12m)
  • Distance resolution : 1cm
  • Ambient light immunity : 70klux
  • Enclosure rating : IP65
  • Light source : LED
  • Central wavelength : 850nm
  • FOV : 3.6°
  • Material of enclosure : ABS+PC
  • Wire length : 25cm

LoRa Spec:

  • Frequency Range,  Band 1 (HF): 862 ~ 1020 Mhz
  • Max +22 dBm constant RF output vs.
  • RX sensitivity: down to -139 dBm.
  • Excellent blocking immunity

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

  • Sleep Mode: 5uA @ 3.3v
  • LoRa Transmit Mode: 125mA @ 20dBm, 82mA @ 14dBm

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 LoRaWAN activate. This mode is used for storage and shipping to save battery life.

Working Mode: In this mode, Sensor will work as LoRaWAN Sensor to Join LoRaWAN 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

1675071855856-879.png

Behavior on ACTFunctionAction
Pressing ACT between 1s < time < 3sSend an uplink

If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, blue led will blink once.
Meanwhile, BLE module will be active and user can connect via BLE to configure device.

Pressing ACT for more than 3sActive Device

Green led will fast blink 5 times, device will enter OTA mode for 3 seconds. And then start to JOIN LoRaWAN network.
Green led will solidly turn on for 5 seconds after joined in network.
Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device join or not join LoRaWAN network.

Fast press ACT 5 times.Deactivate DeviceRed led will solid on for 5 seconds. Means device is in Deep Sleep Mode.

1.7 BLE connection

LDS12-LB support BLE remote configure.

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

image-20230805144259-1.png

1.9 Mechanical

1675143884058-338.png

1675143899218-599.png

1675143909447-639.png

Probe Mechanical:

1654827224480-952.png

2. Configure LDS12-LB to connect to LoRaWAN network

2.1 How it works

The LDS12-LB is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and press the button to activate the LDS12-LB. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes.

  

2.2 ​Quick guide to connect to LoRaWAN server (OTAA)

Following is an example for how to join the TTN v3 LoRaWAN Network. Below is the network structure; we use the LPS8v2  as a LoRaWAN gateway in this example. 

The LPS8v2 is already set to connected to TTN network , so what we need to now is configure the TTN server.

image-20230615153004-2.png 

Step 1: Create a device in TTN with the OTAA keys from LDS12-LB.

Each LDS12-LB is shipped with a sticker with the default device EUI as below:

图片-20230426084152-1.png

You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:

Register the device

1654935135620-998.png

Add APP EUI and DEV EUI

图片-20220611161308-4.png

Add APP EUI in the application

图片-20220611161308-5.png

Add APP KEY

图片-20220611161308-6.png

Step 2: Activate on LDS12-LB

Press the button for 5 seconds to activate the LDS12-LB.

Green led will fast blink 5 times, device will enter OTA mode for 3 seconds. And then start to JOIN LoRaWAN network. Green led will solidly turn on for 5 seconds after joined in network.

After join success, it will start to upload messages to TTN and you can see the messages in the panel.

2.3 ​Uplink Payload

2.3.1 Device Status, FPORT=5

Users can use the downlink command(0x26 01) to ask LDS12-LB to send device configure detail, include device configure status. LDS12-LB will uplink a payload via FPort=5 to server.

The Payload format is as below.

Size(bytes)

12112
ValueSensor ModelFirmware VersionFrequency BandSub-bandBAT

Example parse in TTNv3

image-20230805103904-1.png

Sensor Model: For LDS12-LB, this value is 0x24

Firmware Version: 0x0100, Means: v1.0.0 version

Frequency Band:

0x01: EU868

0x02: US915

0x03: IN865

0x04: AU915

0x05: KZ865

0x06: RU864

0x07: AS923

0x08: AS923-1

0x09: AS923-2

0x0a: AS923-3

0x0b: CN470

0x0c: EU433

0x0d: KR920

0x0e: MA869

Sub-Band:

AU915 and US915:value 0x00 ~ 0x08

CN470: value 0x0B ~ 0x0C

Other Bands: Always 0x00

Battery Info:

Check the battery voltage.

Ex1: 0x0B45 = 2885mV

Ex2: 0x0B49 = 2889mV

2.3.2 Uplink Payload, FPORT=2

LDS12-LB will send this uplink after Device Status once join the LoRaWAN network successfully. And LDS12-LB will:

periodically send this uplink every 20 minutes, this interval can be changed.

Uplink Payload totals 11 bytes.

Size(bytes)

2222111
ValueBATDistanceDistance signal strengthLiDAR temp

image-20230805104104-2.png

Battery Info

Check the battery voltage for LDS12-LB.

Ex1: 0x0B45 = 2885mV

Ex2: 0x0B49 = 2889mV

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-1200. 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 distance measurement gear is fixed, the farther the distance measurement is, the lower the signal strength; the lower the target reflectivity, the lower the signal strength. When Strength is greater than 100 and not equal to 65535, the measured value of Dist is considered credible.

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.

1) When the sensor detects valid data:

image-20230805155335-1.png

2) When the sensor detects invalid data:

image-20230805155428-2.png

3) When the sensor is not connected:

image-20230805155515-3.png

Interrupt Pin & Interrupt Level

This data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.

Note: The Internet Pin is a separate pin in the screw terminal. See pin mapping of GPIO_EXTI .

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: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.

Message Type

For a normal uplink payload, the message type is always 0x01.

Valid Message Type:

Message Type CodeDescriptionPayload
0x01Normal UplinkNormal Uplink Payload
0x02Reply configures infoConfigure Info Payload

image-20230805150315-4.png

2.3.3 Historical measuring distance, FPORT=3

LDS12-LB stores sensor values and users can retrieve these history values via the downlink command.

The historical payload includes one or multiplies entries and every entry has the same payload as Real-Time measuring distance.

Size(bytes)

112214
ValueInterrupt flag & Interrupt_level

Reserve(0xFF)

DistanceDistance signal strength

LiDAR temp

Unix TimeStamp

Interrupt flag & Interrupt level:

Size(bit)

bit7bit6[bit5:bit2]bit1bit0
ValueNo ACK messagePoll Message FlagReserveInterrupt level

Interrupt flag

  • Each data entry is 11 bytes and has the same structure as Uplink Payload, to save airtime and battery, LDS12-LB will send max bytes according to the current DR and Frequency bands.

For example, in the US915 band, the max payload for different DR is:

a) DR0: max is 11 bytes so one entry of data

b) DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)

c) DR2: total payload includes 11 entries of data

d) DR3: total payload includes 22 entries of data.

If LDS12-LB doesn't have any data in the polling time. It will uplink 11 bytes of 0

Downlink:

0x31 64 CC 68 0C 64 CC 69 74 05

image-20230805144936-2.png

Uplink:

43 FF 0E 10 00 B0 1E 64 CC 68 0C 40 FF 0D DE 00 A8 1E 64 CC 68 29 40 FF 09 92 00 D3 1E 64 CC 68 65 40 FF 02 3A 02 BC 1E 64 CC 68 A1 41 FF 0E 1A 00 A4 1E 64 CC 68 C0 40 FF 0D 2A 00 B8 1E 64 CC 68 E8 40 FF 00 C8 11 6A 1E 64 CC 69 24 40 FF 0E 24 00 AD 1E 64 CC 69 6D

Parsed Value:

[DISTANCE , DISTANCE_SIGNAL_STRENGTH,LIDAR_TEMP,EXTI_STATUS , EXTI_FLAG , TIME]

[360,176,30,High,True,2023-08-04 02:53:00],

[355,168,30,Low,False,2023-08-04 02:53:29],

[245,211,30,Low,False,2023-08-04 02:54:29],

[57,700,30,Low,False,2023-08-04 02:55:29],

[361,164,30,Low,True,2023-08-04 02:56:00],

[337,184,30,Low,False,2023-08-04 02:56:40],

[20,4458,30,Low,False,2023-08-04 02:57:40],

[362,173,30,Low,False,2023-08-04 02:58:53],

History read from serial port:

image-20230805145056-3.png

2.3.4 Decode payload in The Things Network

While using TTN network, you can add the payload format to decode the payload.

1654592762713-715.png

The payload decoder function for TTN is here:

2.4 ​Show Data in DataCake IoT Server

DATACAKE provides a human friendly interface to show the sensor data, once we have data in TTN, we can use DATACAKE to connect to TTN and see the data in DATACAKE. Below are the steps:

Step 1: Be sure that your device is programmed and properly connected to the network at this time.

Step 2: To configure the Application to forward data to DATACAKE you will need to add integration. To add the DATACAKE integration, perform the following steps:

1654592790040-760.png

1654592800389-571.png

Step 3: Create an account or log in Datacake.

Step 4: Search the LDS12-LB and add DevEUI.

1654851029373-510.png

After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.

image-20220610165129-11.png

2.5 Datalog Feature

Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, LDS12-LB will store the reading for future retrieving purposes.

2.5.1 Ways to get datalog via LoRaWAN

Set PNACKMD=1, LDS12-LB will wait for ACK for every uplink, when there is no LoRaWAN network,LDS12-LB will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.

  • a) LDS12-LB will do an ACK check for data records sending to make sure every data arrive server.

  • b) LDS12-LB will send data in CONFIRMED Mode when PNACKMD=1, but LDS12-LB won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink if LDS12-LB gets a ACK, LDS12-LB will consider there is a network connection and resend all NONE-ACK messages. 

Below is the typical case for the auto-update datalog feature (Set PNACKMD=1)

图片-20220703111700-2.png

2.5.2 Unix TimeStamp

LDS12-LB uses Unix TimeStamp format based on

图片-20220523001219-11.png

User can get this time from link:  https://www.epochconverter.com/ :

Below is the converter example

图片-20220523001219-12.png

So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan -- 29 Friday 03:03:25

2.5.3 Set Device Time

User need to set SYNCMOD=1 to enable sync time via MAC command.

Once LDS12-LB Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to LDS12-LB. If LDS12-LB fails to get the time from the server, LDS12-LB will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).

Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn't support. If server doesn't support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1.

2.5.4 Poll sensor value

Users can poll sensor values based on timestamps. Below is the downlink command.

Downlink Command to poll Open/Close status (0x31)
1byte4bytes4bytes1byte
31Timestamp startTimestamp endUplink Interval

Timestamp start and Timestamp end-use Unix TimeStamp format as mentioned above. Devices will reply with all data logs during this period, using the uplink interval.

For example, downlink command image-20220518162852-1.png 

Is to check 2021/11/12 12:00:00 to 2021/11/12 15:00:00's data

Uplink Internal =5s,means LDS12-LB will send one packet every 5s. range 5~255s.

2.6 Frequency Plans

The LDS12-LB uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets.

http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/

2.7 LiDAR ToF Measurement

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

1654831757579-263.png

2.7.2 Distance Measurement Characteristics

With optimization of light path and algorithm, The LiDAR probe has minimized influence from external environment on distance measurement performance. Despite that, the range of distance measurement may still be affected by the environment illumination intensity and the reflectivity of detection object. As shown in below:

1654831774373-275.png

① Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.

② Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.

③ Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m.

Vertical Coordinates: Represents the radius of light spot for The LiDAR probe at different distances. The diameter of light spot depends on the FOV of The LiDAR probe (the term of FOV generally refers to the smaller value between the receiving angle and the transmitting angle), which is calculated as follows:

1654831797521-720.png

In the formula above, d is the diameter of light spot; D is detecting range; β is the value of the receiving angle of The LiDAR probe, 3.6°. Correspondence between the diameter of light spot and detecting range is given in Table below.

1654831810009-716.png

If the light spot reaches two objects with different distances, as shown in Figure 3, the output distance value will be a value between the actual distance values of the two objects. For a high accuracy requirement in practice, the above situation should be noticed to avoid the measurement error.

2.7.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.7.4  Reflectivity of different objects

ItemMaterialRelectivity
1Black foam rubber2.4%
2Black fabric3%
3Black rubber4%
4Coal (different types of coal)4~8%
5Black car paint5%
6Black Jam10%
7Opaque black plastic14%
8Clean rough board20%
9Translucent plastic bottle62%
10Carton cardboard68%
11Clean pine70%
12Opaque white plastic87%
13White Jam90%
14Kodak Standard Whiteboard100%
15

Unpolished white metal surface

130%
16Glossy light metal surface150%
17stainless steel200%
18Reflector plate, reflective tape>300%

3. Configure LDS12-LB

3.1 Configure Methods

LDS12-LB supports below configure method:

3.2 General Commands

These commands are to configure:

  • General system settings like: uplink interval.
  • LoRaWAN protocol & radio related command.

They are same for all Dragino Devices which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki:

http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/

3.3 Commands special design for LDS12-LB

These commands only valid for LDS12-LB, as below:

3.3.1 Set Transmit Interval Time

Feature: Change LoRaWAN End Node Transmit Interval.

AT Command: AT+TDC

Command ExampleFunctionResponse
AT+TDC=?Show current transmit Interval

30000
OK
the interval is 30000ms = 30s

AT+TDC=60000Set 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  

     

3.3.2 Set Interrupt Mode

Feature, Set Interrupt mode for pin of GPIO_EXTI.

When AT+INTMOD=0 is set, GPIO_EXTI is used as a digital input port.

AT Command: AT+INTMOD

Command ExampleFunctionResponse
AT+INTMOD=?Show current interrupt mode

0
OK
the mode is 0 =Disable Interrupt

AT+INTMOD=2

(default)

Set Transmit Interval
0. (Disable Interrupt),
1. (Trigger by rising and falling edge)
2. (Trigger by falling edge)
3. (Trigger by rising edge)

OK

Downlink Command: 0x06

Format: Command Code (0x06) followed by 3 bytes.

This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.

  • Example 1: Downlink Payload: 06000000       //  Turn off interrupt mode
  • Example 2: Downlink Payload: 06000003      //   Set the interrupt mode to rising edge trigger

3.3.3  Set Power Output Duration

Control the output duration 3V3(pin of VBAT_OUT) . Before each sampling, device will

1. first enable the power output to external sensor,

2. keep it on as per duration, read sensor value and construct uplink payload

3. final, close the power output.

AT Command: AT+3V3T

Command ExampleFunctionResponse
AT+3V3T=?Show 3V3 open time.0 (default)
OK
AT+3V3T=1000Close after a delay of 1000 milliseconds.OK
AT+3V3T=0Always turn on the power supply of 3V3 pin.OK
AT+3V3T=65535Always turn off the power supply of 3V3 pin.OK

Downlink Command: 0x07
Format: Command Code (0x07) followed by 3 bytes.

The first byte is 01,the second and third bytes are the time to turn on.

  • Example 1: Downlink Payload: 07 01 00 00     --->   AT+3V3T=0
  • Example 2: Downlink Payload: 07 01 01 F4      --->  AT+3V3T=500
  • Example 3: Downlink Payload: 07 01 FF FF      --->  AT+3V3T=65535

4. Battery & Power Consumption

LDS12-LB 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. OTA Firmware update

User can change firmware LDS12-LB 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:

6. FAQ

6.1 What is the frequency plan for LDS12-LB?

LDS12-LB use the same frequency as other Dragino products. User can see the detail from this link:  Introduction

7. Trouble Shooting

7.1 AT Command input doesn't work

In the case if user can see the console output but can't type input to the device. Please check if you already include the ENTER while sending out the command. Some serial tool doesn't send ENTER while press the send key, user need to add ENTER in their string. 

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

Cause ①Due to the physical principles of The LiDAR probe, the above phenomenon is likely to occur if the detection object is the material with high reflectivity (such as mirror, smooth floor tile, etc.) or transparent substance. (such as glass and water, etc.)

Troubleshooting: Please avoid use of this product under such circumstance in practice.

Cause ②The IR-pass filters are blocked.

Troubleshooting: please use dry dust-free cloth to gently remove the foreign matter.

8. Order Info

Part Number: LDS12-LB-XXX

XXX: 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

9. ​Packing Info

Package Includes:

  • LDS12-LB LoRaWAN LiDAR ToF Distance Sensor x 1

Dimension and weight:

  • Device Size: cm
  • Device Weight: g
  • Package Size / pcs : cm
  • Weight / pcs : g

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.
Tags:
    
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0