LDS12-NB_NB-IoT_LiDAR_ToF_Distance_Sensor_User_Manual

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

27

28

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

29

30

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

31

32

LDS12-NB supports different uplink methods including (% style="color:blue" %)**MQTT, MQTTs, UDP & TCP**(%%) for different application requirement, and support uplinks to various IoT Servers.

33

34

LDS12-NB (% style="color:blue" %)**supports BLE configure **(%%)and(% style="color:blue" %)** OTA update**(%%) which make user easy to use.

35

36

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

37

38

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

39

40

[[image:image-20231017101030-1.png||height="317" width="898"]]

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

47

* Ultra-low power consumption

48

* Laser technology for distance detection

49

* Measure Distance: 0.1m~~12m @ 90% Reflectivity

50

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

51

* Multiply Sampling and one uplink

52

* Support Bluetooth v5.1 remote configure and update firmware

53

* Uplink on periodically

54

* Downlink to change configure

55

* IP66 Waterproof Enclosure

56

* 8500mAh Battery for long term use

57

* Nano SIM card slot for NB-IoT SIM

58

59

== 1.3 Specification ==

60

61

62

(% style="color:blue" %)**Common DC Characteristics:**

63

64

* Supply Voltage: 2.5v ~~ 3.6v

65

* Operating Temperature: -40 ~~ 85°C

66

67

(% style="color:blue" %)**Probe Specification:**

68

69

* Storage temperature：-20°C ~~ 75°C

70

* Operating temperature : -20°C ~~ 60°C

71

* Measure Distance:

72

** 0.1m ~~ 12m @ 90% Reflectivity

73

** 0.1m ~~ 4m @ 10% Reflectivity

74

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

75

* Distance resolution : 5mm

76

* Ambient light immunity : 70klux

77

* Enclosure rating : IP65

78

* Light source : LED

79

* Central wavelength : 850nm

80

* FOV : 3.6°

81

* Material of enclosure : ABS+PC

82

* Wire length : 25cm

83

84

(% style="color:blue" %)**NB-IoT Spec:**

85

86

(% style="color:#037691" %)**NB-IoT Module: BC660K-GL**

87

88

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

103

* B28 @H-FDD: 750MHz

104

* B66 @H-FDD: 2000MHz

105

* B70 @H-FDD: 2000MHz

106

* B85 @H-FDD: 700MHz

107

108

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

109

110

* Li/SOCI2 un-chargeable battery

111

* Capacity: 8500mAh

112

* Self Discharge: <1% / Year @ 25°C

113

* Max continuously current: 130mA

114

* Max boost current: 2A, 1 second

115

116

(% style="color:blue" %)**Power Consumption**

117

118

* STOP Mode: 10uA @ 3.3v

119

* Max transmit power: 350mA@3.3v

120

121

122

== 1.4 Applications ==

123

124

125

* Horizontal distance measurement

126

* Parking management system

127

* Object proximity and presence detection

128

* Intelligent trash can management system

129

* Robot obstacle avoidance

* Automatic control

* Sewer

== 1.5 Sleep mode and working mode ==

134

135

136

(% style="color:blue" %)**Deep Sleep Mode: **(%%)Sensor doesn't have any NB-IoT activate. This mode is used for storage and shipping to save battery life.

137

138

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

139

140

141

== 1.6 Button & LEDs ==

142

143

144

[[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]]

145

146

147

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

148

|=(% style="width: 167px;background-color:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width:225px;background-color:#4F81BD;color:white" %)**Action**

149

|(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)(((

150

If sensor has already attached to NB-IoT network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once.

151

Meanwhile, BLE module will be active and user can connect via BLE to configure device.

152

)))

153

|(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)(((

154

(% style="color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:#037691" %)**OTA mode**(%%) for 3 seconds. And then start to attach NB-IoT network.

155

(% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network.

156

Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device attach NB-IoT network or not.

157

)))

158

|(% style="width:167px" %)Fast press ACT 5 times.|(% style="width:117px" %)Deactivate Device|(% style="width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means device is in Deep Sleep Mode.

159

160

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

161

162

163

== 1.7 BLE connection ==

164

165

166

LDS12-NB support BLE remote configure and firmware update.

167

168

169

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:

170

171

* Press button to send an uplink

172

* Press button to active device.

173

* Device Power on or reset.

174

175

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

176

177

178

== 1.8 Pin Definitions & Switch ==

179

180

181

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS12-LB_LoRaWAN_LiDAR_ToF_Distance_Sensor_User_Manual/WebHome/image-20230805144259-1.png?width=741&height=413&rev=1.1||alt="image-20230805144259-1.png"]]

182

183

184

=== 1.8.1 Jumper JP2 ===

185

186

187

Power on Device when put this jumper.

188

189

190

=== 1.8.2 BOOT MODE / SW1 ===

191

192

193

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

194

195

**2)** (% style="color:blue" %)**Flash**(%%): work mode, device starts to work and send out console output for further debug

196

197

198

=== 1.8.3 Reset Button ===

199

200

201

Press to reboot the device.

202

203

(% style="display:none" %)

== 1.9 Mechanical ==

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/1675143884058-338.png?rev=1.1||alt="1675143884058-338.png"]]

209

210

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/1675143899218-599.png?rev=1.1||alt="1675143899218-599.png"]]

211

212

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/1675143909447-639.png?rev=1.1||alt="1675143909447-639.png"]]

213

214

215

(% style="color:blue" %)**Probe Mechanical:**

216

217

218

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654827224480-952.png?rev=1.1||alt="1654827224480-952.png"]]

= 2. Use LDS12-NB to communicate with IoT Server =

224

225

== 2.1 Send data to IoT server via NB-IoT network ==

226

227

228

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

229

230

Below shows the network structure:

231

232

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS12-NB_NB-IoT_LiDAR_ToF_Distance_Sensor_User_Manual/WebHome/image-20231017101030-1.png?width=898&height=317&rev=1.1||alt="image-20231017101030-1.png"]]

233

234

235

There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1D**(%%) version of LDS12-NB.

236

237

238

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

239

240

* Install NB-IoT SIM card and configure APN. See instruction of [[Attach Network>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.AttachNetwork]].

241

242

* Set up sensor to point to IoT Server. See instruction of [[Configure to Connect Different Servers>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.Configuretoconnecttodifferentservers]].

243

244

Below shows result of different server as a glance.

245

246

(% border="1" cellspacing="4" style="width:515px" %)

247

|(% style="background-color:#4f81bd; color:white; width:100px" %)**Servers**|(% style="background-color:#4f81bd; color:white; width:300px" %)**Dash Board**|(% style="background-color:#4f81bd; color:white; width:115px" %)**Comments**

248

|(% style="width:127px" %)[[Node-Red>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.5A0Node-RedA028viaA0MQTT29]]|(% style="width:385px" %)(((

249

(% style="text-align:center" %)

250

[[image:image-20230819113244-8.png||height="183" width="367"]]

251

)))|(% style="width:170px" %)

252

|(% style="width:127px" %)[[DataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.4Datacake]]|(% style="width:385px" %)(((

253

(% style="text-align:center" %)

254

[[image:image-20230819113244-9.png||height="119" width="367"]]

255

)))|(% style="width:170px" %)

256

|(% style="width:127px" %)[[Tago.IO>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.7A0Tago.ioA028viaA0MQTT29]]|(% style="width:385px" %) |(% style="width:170px" %)

257

|(% style="width:127px" %)[[General UDP>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.1GeneralA0UDPA0Connection]]|(% style="width:385px" %)Raw Payload. Need Developer to design Dash Board|(% style="width:170px" %)

258

|(% style="width:127px" %)[[General MQTT>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.2GeneralA0MQTTA0Connection]]|(% style="width:385px" %)Raw Payload. Need Developer to design Dash Board|(% style="width:170px" %)

259

|(% style="width:127px" %)[[ThingSpeak>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.3A0ThingSpeakA028viaA0MQTT29]]|(% style="width:385px" %)(((

260

(% style="text-align:center" %)

261

[[image:image-20230819113244-10.png||height="104" width="367"]]

262

)))|(% style="width:170px" %)

263

|(% style="width:127px" %)[[ThingsBoard>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.6A0ThingsBoard.CloudA028viaA0MQTT29]]|(% style="width:385px" %)(((

264

(% style="text-align:center" %)

265

[[image:image-20230819113244-11.png||height="141" width="367"]]

266

)))|(% style="width:170px" %)

267

268

(% style="color:blue" %)**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 LDS12-NB and user will be able to see data in DataCake. See here for [[DataCake Config Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.4Datacake]].

269

270

271

== 2.2 Payload Types ==

272

273

274

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

**Includes:**

* [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5)

279

280

* [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0)

281

282

* [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1)

283

284

* [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3)

285

286

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

287

288

(% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Use UDP Connection & hex Payload

289

290

(% style="color:#037691" %)**AT+PRO=2,5** (%%) ~/~/ Use UDP Connection & Json Payload

291

292

(% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload

293

294

295

=== 2.2.1 General Json Format(Type~=5) ===

296

297

298

This is the General Json Format. As below:

299

300

(% style="color:#4472c4" %)**{"IMEI":"866207058378443","Model":"LDS12-NB","distance":396,"battery":3.50,"signal":22,"1":{748,2023/09/21 08:36:55},"2":{911,2023/09/21 07:44:35},"3":{702,2023/09/21 07:07:19},"4":{705,2023/09/21 06:52:19},"5":{705,2023/09/21 06:37:19},"6":{705,2023/09/21 06:20:49},"7":{256,2023/09/21 02:49:51},"8":{221,2023/09/20 09:47:01}}**

301

302

303

[[image:image-20230921173213-4.png||height="590" width="858"]]

304

305

306

(% style="color:red" %)**Notice, from above payload:**

307

308

* Distance , Battery & Signal are the value at uplink time.

309

310

* Json entry 1 ~~ 8 are the last 1 ~~ 8 sampling data as specify by (% style="color:#037691" %)**AT+NOUD=8 ** (%%)Command. Each entry includes (from left to right): Temperature, Humidity, Sampling time.

=== 2.2.2 HEX format Payload(Type~=0) ===

315

316

317

This is the HEX Format. As below:

318

319

(% style="color:#4472c4" %)**f86620705837844309640db41201000159650c02e702ec650c00a7038f650bf46302be650beba702c1650be82302c1650be49f02c1650be0c10100650baf4f00dd650abf95**

320

321

[[image:image-20230921165015-2.png||height="195" width="965"]]

322

323

324

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

325

326

327

[[image:image-20230921165050-3.png||height="621" width="905"]]

328

329

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

330

331

These bytes include the hardware and software version.

332

333

(% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x0F for LDS12-NB

334

335

(% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x64=100, means firmware version 1.0.0

336

337

338

(% style="color:blue" %)**BAT (Battery Info):**

Ex1: 0x0DB4 = 3508mV

(% style="color:blue" %)**DS18B20 Temperature sensor:**

344

345

346

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

352

353

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

354

355

356

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

357

358

359

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.

365

366

367

(% style="color:blue" %)**Distance signal strength:**

368

369

370

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.

376

377

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

378

379

380

**1) When the sensor detects valid data:**

381

382

[[image:image-20230805155335-1.png||height="145" width="724"]]

383

384

385

**2) When the sensor detects invalid data:**

386

387

[[image:image-20230805155428-2.png||height="139" width="726"]]

388

389

390

**3) When the sensor is not connected:**

391

392

[[image:image-20230805155515-3.png||height="143" width="725"]]

393

394

395

(% style="color:blue" %)**Interrupt Pin & Interrupt Level:**

396

397

398

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

399

400

(% style="color:red" %)Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.8PinDefinitions"]] of GPIO_EXTI .

**Example:**

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

405

406

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

407

408

409

(% style="color:blue" %)**LiDAR temp:**

410

411

Characterize the internal temperature value of the sensor.

**Example: **

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

416

417

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

418

419

420

=== 2.2.3 ThingsBoard Payload(Type~=3) ===

421

422

423

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

424

425

(% style="color:#4472c4" %)** {"IMEI": "866207058378443","Model": "LDS12-NB", "distance": 491,"battery": 3.57,"signal": 22}**

426

427

[[image:image-20230922091736-3.png||height="517" width="845"]]

428

429

430

=== 2.2.4 ThingSpeak Payload(Type~=1) ===

431

432

433

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

434

435

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

As below:

(% style="color:#4472c4" %)**field1=Distance value&field2=Battery value&field3=Singal value**

440

441

[[image:image-20230921174457-5.png||height="556" width="849"]]

442

443

444

== 2.3 Uplink Payload ==

445

446

447

=== 2.3.1 Uplink Payload, FPORT~=2 ===

(((

LDS12-NB will send this uplink **after** Device Status once join the NB-IoT network successfully. And LDS12-NB will:

452

453

periodically send this uplink every 20 minutes, this interval [[can be changed>>||anchor="H3.3.1SetTransmitIntervalTime"]].

454

455

Uplink Payload totals 11 bytes.

456

)))

457

458

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

459

|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((

460

**Size(bytes)**

461

)))|=(% style="width: 30px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 50px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 70px;background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white; width: 80px;" %)**1**|=(% style="background-color: #4F81BD;color:white; width: 70px;" %)**1**|=(% style="background-color: #4F81BD;color:white; width: 70px;" %)**1**

462

|(% style="width:62.5px" %)Value|(% style="width:62.5px" %)[[BAT>>||anchor="HBatteryInfo"]]|(% style="width:62.5px" %)(((

463

[[Temperature DS18B20>>||anchor="HDS18B20Temperaturesensor"]]

464

)))|[[Distance>>||anchor="HDistance"]]|[[Distance signal strength>>||anchor="HDistancesignalstrength"]]|(% style="width:122px" %)(((

465

[[Interrupt flag & Interrupt_level>>||anchor="HInterruptPin26A0InterruptLevel"]]

466

)))|(% style="width:54px" %)[[LiDAR temp>>||anchor="HLiDARtemp"]]|(% style="width:96px" %)(((

467

[[Message Type>>||anchor="HMessageType"]]

468

)))

469

470

[[image:image-20230805104104-2.png||height="136" width="754"]]

471

472

473

==== (% style="color:blue" %)**Battery Info**(%%) ====

474

475

476

Check the battery voltage for LDS12-NB.

Ex1: 0x0B45 = 2885mV

Ex2: 0x0B49 = 2889mV

==== (% style="color:blue" %)**DS18B20 Temperature sensor**(%%) ====

484

485

486

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

492

493

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

494

495

496

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

497

498

499

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.

505

506

507

==== (% style="color:blue" %)**Distance signal strength**(%%) ====

508

509

510

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.

516

517

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

518

519

520

**1) When the sensor detects valid data:**

521

522

[[image:image-20230805155335-1.png||height="145" width="724"]]

523

524

525

**2) When the sensor detects invalid data:**

526

527

[[image:image-20230805155428-2.png||height="139" width="726"]]

528

529

530

**3) When the sensor is not connected:**

531

532

[[image:image-20230805155515-3.png||height="143" width="725"]]

533

534

535

==== (% style="color:blue" %)**Interrupt Pin & Interrupt Level**(%%) ====

536

537

538

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

539

540

Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.8PinDefinitions"]] of GPIO_EXTI .

**Example:**

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

545

546

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

547

548

549

==== (% style="color:blue" %)**LiDAR temp**(%%) ====

550

551

552

Characterize the internal temperature value of the sensor.

553

554

**Example: **

555

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

556

If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.

557

558

559

==== (% style="color:blue" %)**Message Type**(%%) ====

(((

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

)))

(((

Valid Message Type:

)))

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

571

|=(% style="width: 161px;background-color:#4F81BD;color:white" %)**Message Type Code**|=(% style="width: 164px;background-color:#4F81BD;color:white" %)**Description**|=(% style="width: 174px;background-color:#4F81BD;color:white" %)**Payload**

572

|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)Normal Uplink Payload

573

|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)Configure Info Payload

574

575

[[image:image-20230805150315-4.png||height="233" width="723"]]

576

577

578

=== 2.3.2 Historical measuring distance, FPORT~=3 ===

579

580

581

LDS12-NB stores sensor values and users can retrieve these history values via the [[downlink command>>||anchor="H2.5.4Pollsensorvalue"]].

582

583

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

584

585

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

586

|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((

587

**Size(bytes)**

588

)))|=(% style="width: 80px;background-color:#4F81BD;color:white" %)1|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 50px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 70px;background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD; color: white; width: 85px;" %)**1**|=(% style="background-color: #4F81BD; color: white; width: 85px;" %)4

589

|(% style="width:62.5px" %)Value|(% style="width:62.5px" %)Interrupt flag & Interrupt_level|(% style="width:62.5px" %)(((

590

Reserve(0xFF)

591

)))|Distance|Distance signal strength|(% style="width:88px" %)(((

592

LiDAR temp

593

)))|(% style="width:85px" %)Unix TimeStamp

594

595

**Interrupt flag & Interrupt level:**

596

597

(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:480px" %)

598

|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((

599

**Size(bit)**

600

)))|=(% style="width: 90px;background-color:#4F81BD;color:white" %)**bit7**|=(% style="width: 90px;background-color:#4F81BD;color:white" %)**bit6**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**[bit5:bit2]**|=(% style="width: 90px; background-color: #4F81BD; color: white;" %)**bit1**|=(% style="background-color: #4F81BD; color: white; width: 90px;" %)**bit0**

Interrupt flag

)))

* (((

Each data entry is 11 bytes and has the same structure as [[Uplink Payload>>||anchor="H2.3.2UplinkPayload2CFPORT3D2"]], to save airtime and battery, LDS12-NB will send max bytes according to the current DR and Frequency bands.

607

)))

608

609

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

610

611

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

612

613

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

614

615

**c) DR2:** total payload includes 11 entries of data

616

617

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

618

619

If LDS12-NB 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

625

626

[[image:image-20230805144936-2.png||height="113" width="746"]]

**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]

636

637

638

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

639

640

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

641

642

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

643

644

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

645

646

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

647

648

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

649

650

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

651

652

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

653

654

655

**History read from serial port：**

656

657

[[image:image-20230805145056-3.png]]

658

659

660

== 2.4 Test Uplink and Change Update Interval ==

661

662

663

By default, Sensor will send uplinks (% style="color:blue" %)**every 2 hours**(%%) & AT+NOUD=8

664

665

User can use below commands to change the (% style="color:blue" %)**uplink interval**.

666

667

(% style="color:#037691" %)**AT+TDC=600 ** (%%) ~/~/ Set Update Interval to 600s

668

669

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

670

671

672

== 2.5 Multi-Samplings and One uplink ==

673

674

675

To save battery life, LDS12-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:

676

677

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

678

679

* (% style="color:#037691" %)**AT+NOUD=8** (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.

680

681

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

682

683

[[image:1692424376354-959.png]]

684

685

686

== 2.6 Trggier an uplink by external interrupt ==

687

688

689

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

690

691

(% style="color:blue" %)**AT command:**

692

693

* (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode

694

695

* (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt

696

697

* (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge

698

699

* (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge

700

701

* (% style="color:#037691" %)**AT+INTMOD=3 **(%%) ~/~/ Trigger by rising edge

702

703

704

== 2.7 LiDAR ToF Measurement ==

705

706

=== 2.7.1 Principle of Distance Measurement ===

707

708

709

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.

710

711

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654831757579-263.png?rev=1.1||alt="1654831757579-263.png"]]

712

713

714

=== 2.7.2 Distance Measurement Characteristics ===

715

716

717

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:

718

719

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654831774373-275.png?rev=1.1||alt="1654831774373-275.png"]]

(((

(% style="color:blue" %)**① **(%%)Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.

)))

(((

(% style="color:blue" %)**② **(%%)Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.

)))

(((

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

737

)))

738

739

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654831797521-720.png?rev=1.1||alt="1654831797521-720.png"]]

740

741

(((

742

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.

743

)))

744

745

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654831810009-716.png?rev=1.1||alt="1654831810009-716.png"]]

746

747

(((

748

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

753

754

755

Possible invalid /wrong reading for LiDAR ToF tech:

756

757

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

758

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

759

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

760

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

761

762

763

=== 2.7.4 Reflectivity of different objects ===

764

765

766

(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:379px" %)

767

|=(% style="width: 54px;background-color:#4F81BD;color:white" %)Item|=(% style="width: 231px;background-color:#4F81BD;color:white" %)Material|=(% style="width: 94px;background-color:#4F81BD;color:white" %)Relectivity

768

|(% style="width:53px" %)1|(% style="width:229px" %)Black foam rubber|(% style="width:93px" %)2.4%

769

|(% style="width:53px" %)2|(% style="width:229px" %)Black fabric|(% style="width:93px" %)3%

770

|(% style="width:53px" %)3|(% style="width:229px" %)Black rubber|(% style="width:93px" %)4%

771

|(% style="width:53px" %)4|(% style="width:229px" %)Coal (different types of coal)|(% style="width:93px" %)4~~8%

772

|(% style="width:53px" %)5|(% style="width:229px" %)Black car paint|(% style="width:93px" %)5%

773

|(% style="width:53px" %)6|(% style="width:229px" %)Black Jam|(% style="width:93px" %)10%

774

|(% style="width:53px" %)7|(% style="width:229px" %)Opaque black plastic|(% style="width:93px" %)14%

775

|(% style="width:53px" %)8|(% style="width:229px" %)Clean rough board|(% style="width:93px" %)20%

776

|(% style="width:53px" %)9|(% style="width:229px" %)Translucent plastic bottle|(% style="width:93px" %)62%

777

|(% style="width:53px" %)10|(% style="width:229px" %)Carton cardboard|(% style="width:93px" %)68%

778

|(% style="width:53px" %)11|(% style="width:229px" %)Clean pine|(% style="width:93px" %)70%

779

|(% style="width:53px" %)12|(% style="width:229px" %)Opaque white plastic|(% style="width:93px" %)87%

780

|(% style="width:53px" %)13|(% style="width:229px" %)White Jam|(% style="width:93px" %)90%

781

|(% style="width:53px" %)14|(% style="width:229px" %)Kodak Standard Whiteboard|(% style="width:93px" %)100%

782

|(% style="width:53px" %)15|(% style="width:229px" %)(((

783

Unpolished white metal surface

784

)))|(% style="width:93px" %)130%

785

|(% style="width:53px" %)16|(% style="width:229px" %)Glossy light metal surface|(% style="width:93px" %)150%

786

|(% style="width:53px" %)17|(% style="width:229px" %)stainless steel|(% style="width:93px" %)200%

787

|(% style="width:53px" %)18|(% style="width:229px" %)Reflector plate, reflective tape|(% style="width:93px" %)>300%

= 3. Configure LDS12-NB =

793

794

== 3.1 Configure Methods ==

795

796

797

LDS12-NB supports below configure method:

798

799

* AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]].

800

801

* AT Command via UART Connection : See [[UART Connection>>http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]].

802

803

== 3.2 AT Commands Set ==

804

805

806

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

AT+<CMD> : Run <CMD>

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

811

812

AT+<CMD>=? : Get the value

813

814

815

(% style="color:blue" %)**General Commands**

AT : Attention

AT? : Short Help

ATZ : MCU Reset

AT+TDC : Application Data Transmission Interval

824

825

AT+CFG : Print all configurations

826

827

AT+CFGMOD : Working mode selection

828

829

AT+DEUI : Get or set the Device ID

830

831

AT+INTMOD : Set the trigger interrupt mode

832

833

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

834

835

AT+PRO : Choose agreement

836

837

AT+RXDL : Extend the sending and receiving time

838

839

AT+DNSCFG : Get or Set DNS Server

840

841

AT+GETSENSORVALUE : Returns the current sensor measurement

842

843

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

844

845

AT+CDP : Read or Clear cached data

846

847

AT+SHTEMP: Get or Set alarm of temp

848

849

AT+SHHUM: Get or Set alarm of moisture

850

851

AT+SERVADDR : Server Address

852

853

854

(% style="color:blue" %)**UDP Management**

855

856

AT+CFM : Upload confirmation mode (only valid for UDP)

857

858

859

(% style="color:blue" %)**MQTT Management**

860

861

AT+CLIENT : Get or Set MQTT client

862

863

AT+UNAME : Get or Set MQTT Username

864

865

AT+PWD : Get or Set MQTT password

866

867

AT+PUBTOPIC : Get or Set MQTT publish topic

868

869

AT+SUBTOPIC : Get or Set MQTT subscription topic

870

871

872

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

873

874

AT+FDR : Factory Data Reset

875

876

AT+PWORD : Serial Access Password

877

878

AT+LDATA : Get the last upload data

879

880

AT+CDP : Read or Clear cached data

881

882

883

= 4. Battery & Power Consumption =

884

885

886

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

887

888

[[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .

889

890

891

= 5. Firmware update =

892

893

894

User can change device firmware to::

895

896

* Update with new features.

* Fix bugs.

Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/sh/spr33jrw3x45qnm/AADljOsDG-DesaL2WwTWSV55a?dl=0]]**

901

902

Methods to Update Firmware:

903

904

* (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]].

905

906

* Update through UART TTL interface : **[[Instruction>>url:http://8.211.40.43/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H4.2.FirmwareupgradeusingSTM32Cubeprogramer]]**.

= 6. FAQ =

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

911

912

913

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

914

915

[[See BC660K-GL AT Command set>>url:https://www.dropbox.com/sh/5f6ssda5fum8rvs/AABT68l8ZzWOvZ5eg2qwOoFda?dl=0]]

916

917

918

== 6.2 Can I use LDS12-NB in condensation environment? ==

919

920

921

LDS12-NB is not suitable to be used in condensation environment. Condensation on the LDS12-NB probe will affect the reading and always got 0.

922

923

924

= 7. Trouble Shooting =

925

926

== 7.1 Why does the sensor reading show 0 or "No sensor" ==

927

928

929

~1. The measurement object is very close to the sensor, but in the blind spot of the sensor.

930

931

2. Sensor wiring is disconnected

932

933

3. Not using the correct decoder

934

935

936

== 7.2 Abnormal readings The gap between multiple readings is too large or the gap between the readings and the actual value is too large ==

937

938

939

1) Please check if there is something on the probe affecting its measurement (condensed water, volatile oil, etc.)

940

941

2) Does it change with temperature, temperature will affect its measurement

942

943

3) If abnormal data occurs, you can turn on DEBUG mode, Please use downlink or AT COMMAN to enter DEBUG mode.

944

945

downlink command: (% style="color:blue" %)**F1 01**(%%), AT command: (% style="color:blue" %)**AT+DDEBUG=1**

946

947

4) After entering the debug mode, it will send 20 pieces of data at a time, and you can send its uplink to us for analysis

948

949

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDDS75%20-%20LoRaWAN%20Distance%20Detection%20Sensor%20User%20Manual/WebHome/image-20230113135125-2.png?width=1057&height=136&rev=1.1||alt="image-20230113135125-2.png"]]

950

951

952

Its original payload will be longer than other data. Even though it is being parsed, it can be seen that it is abnormal data.

953

954

Please send the data to us for check.

= 8. Order Info =

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

961

962

(% style="color:red" %)**XX**(%%):

963

964

* (% style="color:#037691" %)**GE**(%%): General version ( Exclude SIM card)

965

966

* (% style="color:#037691" %)**1D**(%%): with 1NCE* 10 years 500MB SIM card and Pre-configure to DataCake server

967

968

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

(% style="color:#037691" %)**Package Includes**:

975

976

* LDS12-NB NB-IoT LiDAR ToF Distance sensor x 1

977

978

* External antenna x 1

979

980

(% style="color:#037691" %)**Dimension and weight**:

981

982

* Device Size: 13.0 x 5 x 4.5 cm

983

984

* Device Weight: 150g

985

986

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

987

988

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

994

995

* 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>>mailto:Support@dragino.cc]].

996

997

(% style="display:none" %) (%%)

Wiki source code of LDS12-NB_NB-IoT_LiDAR_ToF_Distance_Sensor_User_Manual

Applications

Navigation