LLDS12-LoRaWAN LiDAR ToF Distance Sensor User Manual

The Dragino LLDS12 is a (% style="color:blue" %)**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.

21

22

The LLDS12 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.

23

24

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

25

26

The LoRa wireless technology used in LLDS12 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.

27

28

LLDS12 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use up to 5 years.

29

30

Each LLDS12 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:1654826306458-414.png]]

== 1.2 Features ==

* LoRaWAN 1.0.3 Class A

41

* Ultra-low power consumption

42

* Laser technology for distance detection

43

* Operating Range - 0.1m~~12m①

44

* Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)

45

* Monitor Battery Level

46

* Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865

47

* AT Commands to change parameters

48

* Uplink on periodically

49

* Downlink to change configure

50

* 8500mAh Battery for long term use

51

52

== 1.3 Probe Specification ==

53

54

* Storage temperature ：-20℃~~75℃

55

* Operating temperature - -20℃~~60℃

56

* Operating Range - 0.1m~~12m①

57

* Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)

58

* Distance resolution - 5mm

59

* Ambient light immunity - 70klux

60

* Enclosure rating - IP65

61

* Light source - LED

62

* Central wavelength - 850nm

63

* FOV - 3.6°

64

* Material of enclosure - ABS+PC

65

* Wire length - 25cm

66

67

== 1.4 Probe Dimension ==

68

69

70

[[image:1654827224480-952.png]]

== 1.5 Applications ==

75

76

* Horizontal distance measurement

77

* Parking management system

78

* Object proximity and presence detection

79

* Intelligent trash can management system

80

* Robot obstacle avoidance

* Automatic control

* Sewer

== 1.6 Pin mapping and power on ==

85

86

87

[[image:1654827332142-133.png]]

= 2. Configure LLDS12 to connect to LoRaWAN network =

92

93

== 2.1 How it works ==

94

95

(((

96

The LLDS12 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 power on the LLDS12. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes.

)))

(((

In case you can’t set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H6.UseATCommand"]]to set the keys in the LLDS12.

)))

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

105

106

(((

107

Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LG308>>url:http://www.dragino.com/products/lora/item/140-lg308.html]] as a LoRaWAN gateway in this example.

)))

(((

[[image:1654827857527-556.png]]

)))

(((

The LG308 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server.

)))

(((

(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LSPH01.

)))

(((

Each LSPH01 is shipped with a sticker with the default device EUI as below:

124

)))

125

126

[[image:image-20220607170145-1.jpeg]]

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

131

132

133

**Register the device**

134

135

136

[[image:1654592600093-601.png]]

137

138

139

**Add APP EUI and DEV EUI**

140

141

[[image:1654592619856-881.png]]

142

143

144

**Add APP EUI in the application**

145

146

[[image:1654592632656-512.png]]

**Add APP KEY**

[[image:1654592653453-934.png]]

153

154

155

(% style="color:blue" %)**Step 2**(%%): Power on LSPH01

156

157

158

Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).

159

160

[[image:image-20220607170442-2.png]]

(((

(% style="color:blue" %)**Step 3**(%%)**:** The LSPH01 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel.

165

)))

166

167

[[image:1654592697690-910.png]]

== 2.3 Uplink Payload ==

172

173

(((

174

LSPH01 will uplink payload via LoRaWAN with below payload format:

)))

(((

Uplink payload includes in total 11 bytes.

)))

(((

Normal uplink payload:

183

)))

184

185

(% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)

186

|=(% style="width: 62.5px;" %)(((

187

**Size (bytes)**

188

)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1**

189

|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1BatteryInfo"]]|(% style="width:62.5px" %)(((

190

[[Temperature>>||anchor="H2.3.2DS18B20Temperaturesensor"]]

191

192

[[(Optional)>>||anchor="H2.3.2DS18B20Temperaturesensor"]]

193

)))|[[Soil pH>>||anchor="H2.3.3SoilpH"]]|[[Soil Temperature>>||anchor="H2.3.4SoilTemperature"]]|(((

194

[[Digital Interrupt (Optional)>>||anchor="H2.3.5InterruptPin"]]

195

)))|Reserve|(((

196

[[Message Type>>||anchor="H2.3.6MessageType"]]

197

)))

198

199

[[image:1654592721645-318.png]]

=== 2.3.1 Battery Info ===

204

205

206

Check the battery voltage for LSPH01.

Ex1: 0x0B45 = 2885mV

Ex2: 0x0B49 = 2889mV

=== 2.3.2 DS18B20 Temperature sensor ===

215

216

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

222

223

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

=== 2.3.3 Soil pH ===

Range: 0 ~~ 14 pH

**Example:**

(% style="color:#037691" %)** 0x02B7(H) = 695(D) = 6.95pH**

=== 2.3.4 Soil Temperature ===

Get Soil Temperature

**Example**:

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

245

246

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

=== 2.3.5 Interrupt Pin ===

251

252

This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H3.2SetInterruptMode"]] for the hardware and software set up.

**Example:**

0x00: Normal uplink packet.

258

259

0x01: Interrupt Uplink Packet.

=== 2.3.6 Message Type ===

264

265

(((

266

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

)))

(((

Valid Message Type:

)))

(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)

275

|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**

276

|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]]

277

|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.4GetFirmwareVersionInfo"]]

278

|(% style="width:160px" %)0x03|(% style="width:163px" %)Reply Calibration Info|(% style="width:173px" %)[[Calibration Payload>>||anchor="H2.7Calibration"]]

279

280

=== 2.3.7 Decode payload in The Things Network ===

281

282

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

283

284

285

[[image:1654592762713-715.png]]

286

287

(((

288

The payload decoder function for TTN is here:

)))

(((

LSPH01 TTN Payload Decoder: [[https:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/LSPH01/Decoder/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSNPK01/Decoder/]]

)))

== 2.4 Uplink Interval ==

298

299

The LSPH01 by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]]

== 2.5 Show Data in DataCake IoT Server ==

304

305

(((

306

[[DATACAKE>>url:https://datacake.co/]] provides a human friendly interface to show the sensor data, once we have data in TTN, we can use [[DATACAKE>>url:https://datacake.co/]] to connect to TTN and see the data in DATACAKE. 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.**

)))

(((

(% style="color:blue" %)**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:**

)))

[[image:1654592790040-760.png]]

323

324

325

[[image:1654592800389-571.png]]

326

327

328

(% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**

329

330

(% style="color:blue" %)**Step 4**(%%)**: Create LSPH01 product.**

331

332

[[image:1654592819047-535.png]]

[[image:1654592833877-762.png]]

337

338

339

[[image:1654592856403-259.png]]

(((

(% style="color:blue" %)**Step 5**(%%)**: add payload decode**

)))

(((

Download Datacake decoder from: [[https:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/LSPH01/Decoder/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSNPK01/Decoder/]]

)))

[[image:1654592878525-845.png]]

352

353

[[image:1654592892967-474.png]]

354

355

356

[[image:1654592905354-123.png]]

357

358

359

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

360

361

362

[[image:1654592917530-261.png]]

== 2.6 Installation and Maintain ==

367

368

=== 2.6.1 Before measurement ===

(((

(((

If the LSPH01 has more than 7 days not use or just clean the pH probe. User should put the probe inside pure water for more than 24 hours for activation. If no put in water, user need to put inside soil for more than 24 hours to ensure the measurement accuracy.

)))

)))

=== 2.6.2 Measurement ===

(((

(% style="color:#4f81bd" %)**Measurement the soil surface:**

)))

(((

[[image:1654592946732-634.png]]

)))

(((

Choose the proper measuring position. Split the surface soil according to the measured deep.

)))

(((

Put pure water, or rainwater to make the soil of measurement point to moist mud. Remove rocks or hard things.

)))

(((

Slowly insert the probe to the measure point. Don’t use large force which will break the probe. Make sure not shake when inserting.

)))

(((

Put soil over the probe after insert. And start to measure.

)))

(((

)))

(((

(% style="color:#4f81bd" %)**Measurement inside soil:**

)))

(((

Dig a hole with diameter > 20CM.

)))

(((

Insert the probe inside, method like measure the surface.

)))

=== 2.6.3 Maintain Probe ===

424

425

1. (((

426

pH probe electrode is fragile and no strong. User must avoid strong force or hitting it.

427

)))

428

1. (((

429

After long time use (3~~ 6 months). The probe electrode needs to be clean; user can use high grade sandpaper to polish it or put in 5% hydrochloric acid for several minutes. After the metal probe looks like new, user can use pure water to wash it.

430

)))

431

1. (((

432

Probe reference electrode is also no strong, need to avoid strong force or hitting.

433

)))

434

1. (((

435

User should keep reference electrode wet while not use.

436

)))

437

1. (((

438

Avoid the probes to touch oily matter. Which will cause issue in accuracy.

439

)))

440

1. (((

441

The probe is IP68 can be put in water.

)))

== 2.7 Calibration ==

448

449

(((

450

User can do calibration for the probe. It is limited to use below pH buffer solution to calibrate: 4.00, 6.86, 9.18. When calibration, user need to clean the electrode and put the probe in the pH buffer solution to wait the value stable ( a new clean electrode might need max 24 hours to be stable).

)))

(((

After stable, user can use below command to calibrate.

455

)))

456

457

[[image:image-20220607171149-4.png]]

458

459

460

(% style="color:#037691" %)**Calibration Payload**

461

462

(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)

463

|=(% style="width: 62.5px;" %)(((

**Size (bytes)**

|**Value**|(((

PH4

Calibrate value

)))|PH6.86 Calibrate value|(((

PH9.18

Calibrate value

)))|Reserve|(((

[[Message Type>>||anchor="H2.3.6MessageType"]]

Always 0x03

)))

User can also send 0x14 downlink command to poll the current calibration payload.

481

482

[[image:image-20220607171416-7.jpeg]]

483

484

485

* Reply to the confirmation package: 14 01

486

* Reply to non-confirmed packet: 14 00

487

488

== 2.8 Frequency Plans ==

489

490

(((

491

The LSPH01 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.

)))

=== 2.8.1 EU863-870 (EU868) ===

496

497

(((

498

(% style="color:blue" %)**Uplink:**

)))

(((

868.1 - SF7BW125 to SF12BW125

)))

(((

868.3 - SF7BW125 to SF12BW125 and SF7BW250

)))

(((

868.5 - SF7BW125 to SF12BW125

)))

(((

867.1 - SF7BW125 to SF12BW125

)))

(((

867.3 - SF7BW125 to SF12BW125

)))

(((

867.5 - SF7BW125 to SF12BW125

)))

(((

867.7 - SF7BW125 to SF12BW125

)))

(((

867.9 - SF7BW125 to SF12BW125

)))

(((

868.8 - FSK

)))

(((

)))

(((

(% style="color:blue" %)**Downlink:**

)))

(((

Uplink channels 1-9 (RX1)

)))

(((

869.525 - SF9BW125 (RX2 downlink only)

)))

=== 2.8.2 US902-928(US915) ===

556

557

(((

558

Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.

)))

(((

To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join.

)))

(((

After Join success, the end node will switch to the correct sub band by:

567

)))

568

569

* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band

570

* Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)

571

572

=== 2.8.3 CN470-510 (CN470) ===

573

574

(((

575

Used in China, Default use CHE=1

)))

(((

(% style="color:blue" %)**Uplink:**

)))

(((

486.3 - SF7BW125 to SF12BW125

)))

(((

486.5 - SF7BW125 to SF12BW125

)))

(((

486.7 - SF7BW125 to SF12BW125

)))

(((

486.9 - SF7BW125 to SF12BW125

)))

(((

487.1 - SF7BW125 to SF12BW125

)))

(((

487.3 - SF7BW125 to SF12BW125

)))

(((

487.5 - SF7BW125 to SF12BW125

)))

(((

487.7 - SF7BW125 to SF12BW125

)))

(((

)))

(((

(% style="color:blue" %)**Downlink:**

)))

(((

506.7 - SF7BW125 to SF12BW125

)))

(((

506.9 - SF7BW125 to SF12BW125

)))

(((

507.1 - SF7BW125 to SF12BW125

)))

(((

507.3 - SF7BW125 to SF12BW125

)))

(((

507.5 - SF7BW125 to SF12BW125

)))

(((

507.7 - SF7BW125 to SF12BW125

)))

(((

507.9 - SF7BW125 to SF12BW125

)))

(((

508.1 - SF7BW125 to SF12BW125

)))

(((

505.3 - SF12BW125 (RX2 downlink only)

)))

=== 2.8.4 AU915-928(AU915) ===

661

662

(((

663

Frequency band as per definition in LoRaWAN 1.0.3 Regional document.

)))

(((

To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join.

)))

(((

)))

(((

After Join success, the end node will switch to the correct sub band by:

676

)))

677

678

* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band

679

* Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)

680

681

=== 2.8.5 AS920-923 & AS923-925 (AS923) ===

682

683

(((

684

(% style="color:blue" %)**Default Uplink channel:**

)))

(((

923.2 - SF7BW125 to SF10BW125

)))

(((

923.4 - SF7BW125 to SF10BW125

)))

(((

)))

(((

(% style="color:blue" %)**Additional Uplink Channel**:

)))

(((

(OTAA mode, channel added by JoinAccept message)

)))

(((

)))

(((

(% style="color:blue" %)**AS920~~AS923 for Japan, Malaysia, Singapore**:

)))

(((

922.2 - SF7BW125 to SF10BW125

)))

(((

922.4 - SF7BW125 to SF10BW125

)))

(((

922.6 - SF7BW125 to SF10BW125

)))

(((

922.8 - SF7BW125 to SF10BW125

)))

(((

923.0 - SF7BW125 to SF10BW125

)))

(((

922.0 - SF7BW125 to SF10BW125

)))

(((

)))

(((

(% style="color:blue" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**:

)))

(((

923.6 - SF7BW125 to SF10BW125

)))

(((

923.8 - SF7BW125 to SF10BW125

)))

(((

924.0 - SF7BW125 to SF10BW125

)))

(((

924.2 - SF7BW125 to SF10BW125

)))

(((

924.4 - SF7BW125 to SF10BW125

)))

(((

924.6 - SF7BW125 to SF10BW125

)))

(((

)))

(((

(% style="color:blue" %)**Downlink:**

)))

(((

Uplink channels 1-8 (RX1)

)))

(((

923.2 - SF10BW125 (RX2)

)))

=== 2.8.6 KR920-923 (KR920) ===

790

791

(((

792

(% style="color:blue" %)**Default channel:**

)))

(((

922.1 - SF7BW125 to SF12BW125

)))

(((

922.3 - SF7BW125 to SF12BW125

)))

(((

922.5 - SF7BW125 to SF12BW125

)))

(((

)))

(((

(% style="color:blue" %)**Uplink: (OTAA mode, channel added by JoinAccept message)**

)))

(((

922.1 - SF7BW125 to SF12BW125

)))

(((

922.3 - SF7BW125 to SF12BW125

)))

(((

922.5 - SF7BW125 to SF12BW125

)))

(((

922.7 - SF7BW125 to SF12BW125

)))

(((

922.9 - SF7BW125 to SF12BW125

)))

(((

923.1 - SF7BW125 to SF12BW125

)))

(((

923.3 - SF7BW125 to SF12BW125

)))

(((

)))

(((

(% style="color:blue" %)**Downlink:**

)))

(((

Uplink channels 1-7(RX1)

)))

(((

921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)

)))

=== 2.8.7 IN865-867 (IN865) ===

862

863

(((

864

(% style="color:blue" %)**Uplink:**

)))

(((

865.0625 - SF7BW125 to SF12BW125

)))

(((

865.4025 - SF7BW125 to SF12BW125

)))

(((

865.9850 - SF7BW125 to SF12BW125

)))

(((

)))

(((

(% style="color:blue" %)**Downlink:**

)))

(((

Uplink channels 1-3 (RX1)

)))

(((

866.550 - SF10BW125 (RX2)

)))

== 2.9 LED Indicator ==

898

899

The LSPH01 has an internal LED which is to show the status of different state.

900

901

* The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.

902

* Blink once when device transmit a packet.

903

904

== 2.10 Firmware Change Log ==

905

906

907

**Firmware download link:**

908

909

[[http:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/LSPH01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/]]

910

911

912

**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>path:/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/]]

913

914

915

= 3. LiDAR ToF Measurement =

916

917

== 3.1 Principle of Distance Measurement ==

918

919

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.

920

921

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]

== 3.2 Distance Measurement Characteristics ==

926

927

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:

928

929

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]]

930

931

932

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

933

934

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

935

936

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

937

938

939

Vertical Coordinates: Represents the radius of light spot for The LiDAR probe at the 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:

940

941

942

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]]

943

944

945

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.

946

947

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]]

948

949

950

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.

== 3.3 Notice of usage: ==

955

956

Possible invalid /wrong reading for LiDAR ToF tech:

957

958

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

959

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

960

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

961

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

= 4. Configure LLDS12 via AT Command or LoRaWAN Downlink =

966

967

(((

968

Use can configure LLDS12 via AT Command or LoRaWAN Downlink.

)))

* (((

AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].

973

)))

974

* (((

975

LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>path:/xwiki/bin/view/Main/]]

)))

(((

There are two kinds of commands to configure LLDS12, they are:

)))

* (((

(% style="color:#4f81bd" %)** General Commands**.

)))

(((

These commands are to configure:

)))

* (((

General system settings like: uplink interval.

994

)))

995

* (((

996

LoRaWAN protocol & radio related command.

)))

(((

They are same for all Dragino Device which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki: [[End Device AT Commands and Downlink Command>>path:/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]

)))

(((

)))

* (((

(% style="color:#4f81bd" %)** Commands special design for LLDS12**

)))

(((

These commands only valid for LLDS12, as below:

)))

== 4.1 Set Transmit Interval Time ==

1018

1019

Feature: Change LoRaWAN End Node Transmit Interval.

1020

1021

(% style="color:#037691" %)**AT Command: AT+TDC**

1022

1023

[[image:image-20220607171554-8.png]]

(((

(% style="color:#037691" %)**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

1041

)))

1042

* (((

1043

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

)))

== 4.2 Set Interrupt Mode ==

1050

1051

Feature, Set Interrupt mode for GPIO_EXIT.

1052

1053

(% style="color:#037691" %)**AT Command: AT+INTMOD**

1054

1055

[[image:image-20220610105806-2.png]]

(((

(% style="color:#037691" %)**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

1074

)))

1075

* (((

1076

Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger

)))

== 4.3 Get Firmware Version Info ==

1082

1083

Feature: use downlink to get firmware version.

1084

1085

(% style="color:#037691" %)**Downlink Command: 0x26**

1086

1087

[[image:image-20220607171917-10.png]]

1088

1089

* Reply to the confirmation package: 26 01

1090

* Reply to non-confirmed packet: 26 00

1091

1092

1093

Device will send an uplink after got this downlink command. With below payload:

1094

1095

Configures info payload:

1096

1097

(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)

1098

|=(((

1099

**Size(bytes)**

1100

)))|=**1**|=**1**|=**1**|=**1**|=**1**|=**5**|=**1**

1101

|**Value**|Software Type|(((

Frequency

Band

)))|Sub-band|(((

Firmware

Version

)))|Sensor Type|Reserve|(((

1110

[[Message Type>>||anchor="H2.3.6MessageType"]]

Always 0x02

)))

**Software Type**: Always 0x03 for LLDS12

**Frequency Band**:

*0x01: EU868

*0x02: US915

*0x03: IN865

*0x04: AU915

*0x05: KZ865

*0x06: RU864

*0x07: AS923

*0x08: AS923-1

*0x09: AS923-2

*0xa0: AS923-3

**Sub-Band**: value 0x00 ~~ 0x08

1141

1142

1143

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

**Sensor Type**:

0x01: LSE01

0x02: LDDS75

0x03: LDDS20

0x04: LLMS01

0x05: LSPH01

0x06: LSNPK01

0x07: LLDS12

= 5. Battery & How to replace =

1165

1166

== 5.1 Battery Type ==

1167

1168

(((

1169

LLDS12 is equipped with a [[8500mAH ER26500 Li-SOCI2 battery>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]. The battery is un-rechargeable battery with low discharge rate targeting for 8~~10 years use. This type of battery is commonly used in IoT target for long-term running, such as water meter.

)))

(((

The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.

1174

)))

1175

1176

[[image:1654593587246-335.png]]

1177

1178

1179

Minimum Working Voltage for the LLDS12:

1180

1181

LLDS12: 2.45v ~~ 3.6v

== 5.2 Replace Battery ==

1186

1187

(((

1188

Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.

)))

(((

And make sure the positive and negative pins match.

)))

== 5.3 Power Consumption Analyze ==

1198

1199

(((

1200

Dragino Battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.

)))

(((

Instruction to use as below:

)))

**Step 1**: Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:

1209

1210

[[https:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]

1211

1212

1213

**Step 2**: Open it and choose

* Product Model

* Uplink Interval

* Working Mode

And the Life expectation in difference case will be shown on the right.

1220

1221

[[image:1654593605679-189.png]]

1222

1223

1224

The battery related documents as below:

1225

1226

* (((

1227

[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],

1228

)))

1229

* (((

1230

[[Lithium-Thionyl Chloride Battery datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],

1231

)))

1232

* (((

1233

[[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC_1520_datasheet.jpg]], [[Tech Spec>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC1520%20Technical%20Specification20171123.pdf]]

1234

)))

1235

1236

[[image:image-20220607172042-11.png]]

=== 5.3.1 Battery Note ===

1241

1242

(((

1243

The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.

)))

=== 5.3.2 Replace the battery ===

1249

1250

(((

1251

You can change the battery in the LLDS12.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won’t be voltage drop between battery and main board.

)))

(((

The default battery pack of LLDS12 includes a ER26500 plus super capacitor. If user can’t find this pack locally, they can find ER26500 or equivalence, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes)

)))

= 6. Use AT Command =

1261

1262

== 6.1 Access AT Commands ==

1263

1264

LLDS12 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LLDS12 for using AT command, as below.

1265

1266

[[image:1654593668970-604.png]]

**Connection:**

(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**

1271

1272

(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD**

1273

1274

(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD**

(((

In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LSPH01. LSPH01 will output system info once power on as below:

)))

[[image:1654593712276-618.png]]

1283

1284

Valid AT Command please check [[Configure Device>>||anchor="H3.ConfigureLSPH01viaATCommandorLoRaWANDownlink"]].

= 7. FAQ =

== 7.1 How to change the LoRa Frequency Bands/Region ==

1290

1291

You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]].

1292

When downloading the images, choose the required image file for download.

1293

1294

1295

= 8. Trouble Shooting =

1296

1297

== 8.1 AT Commands input doesn’t work ==

1298

1299

1300

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 (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn’t send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.

1301

1302

1303

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

(((

(% style="color:blue" %)**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.

)))

(((

)))

(((

(% style="color:blue" %)**Cause ②**(%%)**: **The IR-pass filters are blocked.

)))

(((

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

)))

= 9. Order Info =

Part Number: (% style="color:blue" %)**LLDS12-XX**

1332

1333

1334

(% style="color:blue" %)**XX**(%%): The default frequency band

1335

1336

* (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band

1337

* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band

1338

* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band

1339

* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band

1340

* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band

1341

* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band

1342

* (% style="color:red" %)**IN865**(%%): LoRaWAN IN865 band

1343

* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band

= 10. Packing Info =

**Package Includes**:

1350

1351

* LLDS12 LoRaWAN LiDAR Distance Sensor x 1

1352

1353

**Dimension and weight**:

* Device Size: cm

* Device Weight: g

* Package Size / pcs : cm

* Weight / pcs : g

= 11. 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.

1364

* 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.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]].

1365

1366

Wiki source code of LLDS12-LoRaWAN LiDAR ToF Distance Sensor User Manual

Applications

Navigation