LDS25-NB -- NB-IoT LiDAR ToF Distance Auto-Clean Sensor

The Dragino LDS25-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 (+/- 6cm up to 6m) and as far as 25 meters (+/-1% starting at 6m). The LiDAR probe uses laser induction technology for distance measurement.

25

26

It has a unique dust removal brush structure built in, and the radar drives the dust removal brush to complete the optical mirror dust removal operation, and the user can customize the dust removal confguration.

27

28

The LDS25-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

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

33

34

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

35

36

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

37

38

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

== 1.2 Features ==

* NB-IoT Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 @H-FDD

45

* Ultra-low power consumption

46

* Laser technology for distance detection

47

* Self-contained Auto-clean function

48

* Measure Distance: 0.1m~~25m

49

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

50

* Resolution : 1cm

51

* FOV : 3°

52

* Monitor Battery Level

53

* Multiply Sampling and one uplink

54

* Uplink via MQTT, MQTTs, TCP, UDP or CoAP

55

* Support Bluetooth v5.1 remote configure and update firmware

56

* Uplink on periodically

57

* Downlink to change configure

58

* IP65 Waterproof Enclosure

59

* 8500mAh Battery for long term use

60

* Nano SIM card slot for NB-IoT SIM

61

62

== 1.3 Specification ==

63

64

65

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

66

67

* Supply Voltage: 2.6v ~~ 3.6v

68

* Operating Temperature: -40 ~~ 85°C

69

70

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

71

72

* Storage temperature: -30°C~~80°C

73

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

74

* Measure Distance:

75

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

76

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

77

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

78

* Distance resolution: 1cm

79

* Ambient light immunity: 100klux

80

* Enclosure rating : IP5X

81

* Light source : VCSEL

82

* Central wavelength : 850nm

83

* FOV : 3°

84

* Material of enclosure : ABS+PC

85

* Wire length : 120cm

86

87

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

88

89

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

90

91

(% 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

106

* B28 @H-FDD: 750MHz

107

* B66 @H-FDD: 2000MHz

108

* B70 @H-FDD: 2000MHz

109

* B85 @H-FDD: 700MHz

110

111

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

112

113

* Li/SOCI2 un-chargeable battery

114

* Capacity: 8500mAh

115

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

116

* Max continuously current: 130mA

117

* Max boost current: 2A, 1 second

118

119

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

120

121

* STOP Mode: 10uA @ 3.3v

122

* Max transmit power: 350mA@3.3v

123

124

== 1.4 Applications ==

125

126

127

* Horizontal distance measurement

128

* Parking management system

129

* Object proximity and presence detection

130

* Intelligent trash can management system

131

* Robot obstacle avoidance

* Automatic control

* Sewer

== 1.5 Sleep mode and working mode ==

136

137

138

(% 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.

139

140

(% 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.

141

142

143

== 1.6 Button & LEDs ==

144

145

146

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

147

148

149

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

150

|=(% 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**

151

|[[image:1749542488522-909.png]] 1~~3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)(((

152

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

153

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

154

)))

155

|[[image:1749542491854-716.png]] >3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)(((

156

(% 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.

157

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.

158

)))

159

|[[image:1749542532300-379.png]] x5|(% 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.

160

161

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

162

163

164

== 1.7 BLE connection ==

165

166

167

LDS25-NB support BLE remote configure and firmware update.

168

169

170

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:

171

172

* Press button to send an uplink

173

* Press button to active device.

174

* Device Power on or reset.

175

176

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

177

178

179

== 1.8 Pin Definitions , Switch & SIM Direction ==

180

181

182

[[image:image-20250218144357-1.jpeg||height="357" width="779"]]

183

184

185

=== 1.8.1 Jumper JP2 ===

186

187

188

Power on Device when put this jumper.

189

190

191

=== 1.8.2 BOOT MODE / SW1 ===

192

193

194

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

195

196

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

197

198

199

=== 1.8.3 Reset Button ===

200

201

202

Press to reboot the device.

203

204

205

=== 1.8.4 SIM Card Direction ===

206

207

208

See this link. [[How to insert SIM Card>>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]].

== 1.9 Mechanical ==

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

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

219

220

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

221

222

223

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

224

225

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

226

227

228

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

229

230

Below shows the network structure:

231

232

[[image:image-20241205173131-1.png]]

233

234

235

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

236

237

(% 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 LDS25-NB send data to IoT server.

238

239

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

240

241

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

242

243

Below shows result of different server as a glance.

244

245

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

246

|(% 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**

247

|(% 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" %)(((

248

[[image:image-20230819113244-8.png||data-xwiki-image-style-alignment="center" height="183" width="367"]]

249

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

250

|(% 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" %)(((

251

[[image:image-20230819113244-9.png||data-xwiki-image-style-alignment="center" height="119" width="367"]]

252

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

253

|(% 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" %)

254

|(% 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" %)

255

|(% 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" %)

256

|(% 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" %)(((

257

[[image:image-20230819113244-10.png||data-xwiki-image-style-alignment="center" height="104" width="367"]]

258

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

259

|(% 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" %)(((

260

[[image:image-20230819113244-11.png||data-xwiki-image-style-alignment="center" height="141" width="367"]]

261

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

262

263

(% style="color:blue" %)**1T Version**(%%): This version has 1NCE SIM card pre-installed and configure to send value to ThingsEye. User Just need to select the sensor type in ThingsEyeand Activate LDS25-NB and user will be able to see data in ThingsEye. See here for [[ThingsEye Config Instruction>>https://wiki.thingseye.io/xwiki/bin/view/Main/ ]].

264

265

266

== 2.2 Payload Types ==

267

268

269

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

**Includes:**

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

274

275

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

276

277

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

278

279

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

280

281

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

282

283

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

284

285

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

286

287

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

288

289

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

290

291

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

292

293

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

294

295

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

296

297

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

298

299

300

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

301

302

303

This is the General Json Format. As below:

304

305

(% style="color:#4472c4" %)**{"IMEI":"863663062798914","IMSI":"460083513507314","Model":"LDS25-NB","distance":325,"distance_signal_strength":148,"lidar_temp":25,"battery":3.271,"signal":16,"time":"2024/12/07 07:42:13","1":[324,137,25,"2024/12/07 07:36:22"],"2":[330,140,25,"2024/12/07 07:21:22"],"3":[324,139,24,"2024/12/07 07:06:22"],"4":[324,138,24,"2024/12/07 06:51:22"],"5":[326,141,25,"2024/12/07 06:36:22"],"6":[327,135,25,"2024/12/07 06:21:22"],"7":[348,136,25,"2024/12/07 06:06:22"],"8":[324,130,24,"2024/12/07 05:46:38"]}**

306

307

[[image:image-20241217114628-1.png]]

308

309

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

310

311

* Distance, Distance signal strength, LIDAR Temperature, Battery, Signal & time are the value at uplink time.

312

313

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

314

315

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

316

317

318

This is the HEX Format. As below:

319

320

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

321

322

[[image:image-20250321104452-1.png]]

323

324

325

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

326

327

[[image:image-20241217135710-1.png]]

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: 0x3f for LDS25-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: 0x0D37 = 3383mV

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

344

345

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

**Example**:

If the data you get from the register is __**0x00 0xA5**__, the distance between the sensor and the measured object is **00A5(H) = 165 (D) = 165cm**.

350

351

352

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

353

354

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

355

356

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

**Example**:

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

361

362

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

363

364

365

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

366

367

Characterize the internal temperature value of the sensor.

**Example: **

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

372

373

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

374

375

376

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

377

378

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

**Example:**

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

383

384

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

385

386

387

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

388

389

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

390

391

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

392

393

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

394

395

396

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

397

398

Unit TimeStamp Example: 672b2846(H) = 1730881606(D)

399

400

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

401

402

403

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

404

405

406

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

407

408

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

409

"topic": "004_NB",

410

"payload": {

411

"IMEI": "863663062798914",

412

"IMSI": "460083513507314",

413

"Model": "LDS25-NB",

414

"distance": 326,

415

"distance_signal_strength": 148,

"lidar_temp": 25,

"battery": 3.263,

"signal": 16,

"time": "2024/12/07 07:51:09",

420

"1": [324, 137, 25, "2024/12/07 07:36:22"],

421

"2": [330, 140, 25, "2024/12/07 07:21:22"],

422

"3": [324, 139, 24, "2024/12/07 07:06:22"],

423

"4": [324, 138, 24, "2024/12/07 06:51:22"],

424

"5": [326, 141, 25, "2024/12/07 06:36:22"],

425

"6": [327, 135, 25, "2024/12/07 06:21:22"],

426

"7": [348, 136, 25, "2024/12/07 06:06:22"],

427

"8": [324, 130, 24, "2024/12/07 05:46:38"]

}

}**

[[image:image-20241217140124-2.png||height="576" width="1285"]]

433

434

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

435

436

437

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

438

439

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

As below:

(% style="color:#4472c4" %)**field1=Distance value&field2=Distance signal strength value&field3=Temperature value&field4=Battery value&field5=Signal value&field6=Interrupt value&field7=Interrupt level value**

== 2.3 Test Uplink and Change Update Interval ==

448

449

450

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

451

452

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

453

454

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

455

456

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

457

458

459

== 2.4 Trggier an uplink by external interrupt ==

460

461

462

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

463

464

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

465

466

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

467

468

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

469

470

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

471

472

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

473

474

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

475

476

== 2.5 LiDAR ToF Measurement ==

477

478

=== 2.5.1 Principle of Distance Measurement ===

479

480

481

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.

482

483

[[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"]]

484

485

486

=== 2.6.2 Distance Measurement Characteristics ===

487

488

489

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.

490

491

TF02-Pro-W Detection Angle Diagram:

492

493

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

(((

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:

498

)))

499

500

[[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"]]

501

502

(((

503

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°. Correspondence between the diameter of light spot and detecting range is given in Table below.

504

)))

505

506

[[image:image-20241106144717-5.png]]

507

508

(((

509

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.6.3 Notice of usage ===

514

515

516

Possible invalid /wrong reading for LiDAR ToF tech:

517

518

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

519

520

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

521

522

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

523

524

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

525

526

=== 2.6.4 Reflectivity of different objects ===

527

528

529

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

530

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

531

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

532

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

533

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

534

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

535

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

536

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

537

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

538

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

539

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

540

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

541

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

542

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

543

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

544

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

545

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

546

Unpolished white metal surface

547

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

548

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

549

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

550

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

551

552

== 2.7 Clock logging (Since firmware version v1.2.1) ==

553

554

555

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

556

557

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

558

559

* (% style="color:blue" %)**AT Command: AT+CLOCKLOG=a,b,c,d**

560

561

(% style="color:blue" %)**a:**(%%)** 0:** Disable Clock logging. ** 1: **Enable Clock Logging

562

563

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

564

565

(% style="color:blue" %)**c:**(%%)** **Specify the sampling interval: range **(0 ~~ 255 minutes)**

566

567

(% style="color:blue" %)**d:**(%%)** **How many entries should be uplink on every TDC **(max 32)**

568

569

(% style="color:red" %)**Note: To disable clock recording, set the following parameters: AT+CLOCKLOG=1,65535,0,0**

570

571

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SPH01-NB_NB-IoT_Soil_pH_Sensor_User_Manual/WebHome/image-20240315141254-1.png?rev=1.1||alt="image-20240315141254-1.png"]]

**Example:**

**AT+CLOCKLOG=1,65535,1,5**

576

577

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

578

579

(% class="wikigeneratedid" %)

580

[[image:image-20240316092934-1.png||height="481" width="1159"]]

581

582

(% class="wikigeneratedid" %)

583

(% style="color:red" %)**Note: Users need to synchronize the server time before configuring this command. If the server time is not synchronized before this command is configured, the command takes effect only after the node is reset.**

584

585

* (% style="color:blue" %)**Downlink Command: 0x0A**

586

587

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

588

589

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

590

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

591

592

(% style="color:red" %)**Note: When entering the downlink payload, there must be no Spaces between bytes.**

== 2.8 Example Query saved historical records ==

597

598

599

* (% style="color:blue" %)**AT Command: AT+CDP**

600

601

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

602

603

(% class="wikigeneratedid" %)

604

[[image:image-20241106173632-12.png]]

605

606

607

== 2.9 Uplink log query ==

608

609

610

* (% style="color:blue" %)**AT Command: AT+GETLOG**

611

612

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

613

614

[[image:image-20241106173655-13.png]]

615

616

617

== 2.10 Scheduled domain name resolution ==

618

619

620

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

621

622

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

623

624

* (% style="color:#037691" %)**AT+DNSTIMER=XX **(%%)~/~/ Unit: hour

625

626

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

627

628

629

== 2.11 Set the QoS level ==

630

631

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

632

633

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

634

635

* (% style="color:#037691" %)**AT+MQOS=xx**(%%)** **~/~/ 0~~2

636

637

(% style="color:blue" %)**Downlink Command: 0x07**

638

639

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

640

641

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

642

643

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

644

645

646

== 2.12 Get or set the automatic cleaning interval ==

647

648

649

Function: It can be set to auto-clean once before each uplink packet or set to auto-clean at regular intervals. (Unit: minute)

650

651

(% style="color:red" %)**Note:If you set it to automatically clean once per uplink packet, it will shorten the length of time that the silicone on the wipers that the sensors can be used to clean is available, so it is recommended to use wipers that are activated once a day. (The factory default is to activate every 1440min)**

652

653

(% style="color:blue" %)**AT Command: AT+REMODUST**

654

655

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

656

|=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 217px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 129px; background-color: rgb(79, 129, 189); color: white;" %)**Response**

657

|(% style="width:154px" %)AT+REMODUST=?|(% style="width:217px" %)Get automatic cleaning interval|(% style="width:129px" %)(((

1,1,1440

OK

)))

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

663

AT+REMODUST=1,1,720

664

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

665

Setting the cleaning function to start every 12 hours

666

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

OK

)))

|(% style="width:154px" %)AT+REMODUST=2,1,0|(% style="width:217px" %)Start the cleaning function once before each packet sending|(% style="width:129px" %)(((

OK

)))

|(% style="width:154px" %)AT+REMODUST=2,2,0|(% style="width:217px" %)Start the cleaning function twice before each packet sending|(% style="width:129px" %)(((

OK

)))

|(% style="width:154px" %)AT+REMODUST|(% style="width:217px" %)Starts the cleaning function once immediately.|(% style="width:129px" %)(((

OK

)))

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

688

|=(% style="width: 155px; background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 112px; background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 242px; background-color:#4F81BD;color:white" %)**parameters**

689

|(% colspan="1" rowspan="3" style="width:155px" %)(((

AT+REMODUST=aa,bb,cc

)))|(% colspan="1" rowspan="3" style="width:112px" %)(((

694

Get or set the automatic cleaning interval

(((

)))

(((

)))

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

704

**aa:**

705

706

1: Timed start (parameter cc controls the interval);

707

708

2: start the cleaning function once before each packet sending

709

710

(When set to 2, the CC parameter is invalid (needs to be set to 0))

711

)))

712

|(% style="width:242px" %)**bb:** how many cleanings per start

713

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

714

**cc: **how often to start at intervals(Unit: min)

715

)))

716

717

(% style="color:blue" %)**Downlink Command: 0x08 02**

718

719

Format: Command Code (0x08 02) followed by 4 bytes.

720

721

* Example 1: Downlink Payload: 08 02 01 01 05 A0 **~-~-->** AT+REMODUST=1,1,1440

722

* Example 2: Downlink Payload: 08 02 01 01 02 D0 **~-~-->** AT+REMODUST=1,1,720

723

* Example 3: Downlink Payload: 08 02 02 01 00 00 **~-~-->** AT+REMODUST=2,1,0

724

* Example 4: Downlink Payload: 08 02 02 02 00 00 **~-~-->** AT+REMODUST=2,2,0

725

* Example 5: Downlink Payload: 08 01 **~-~-->** AT+REMODUST

726

727

== 2.13 Set the downlink debugging mode(Since firmware v1.0.0) ==

728

729

730

Feature: Set the conversion between the standard version and 1T version downlinks.

731

732

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

733

734

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

735

|=(% style="width: 138px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 143px; background-color: rgb(79, 129, 189); color: white;" %)**Function/Parameters**|=(% style="width: 229px; background-color: rgb(79, 129, 189); color: white;" %)**Response/Explanation**

736

|(% style="width:134px" %)AT+DOWNTE=?|(% style="width:143px" %)Get current Settings|(% style="width:229px" %)(((

0,0 (default)

OK

)))

|(% colspan="1" rowspan="2" style="width:134px" %)(((

AT+DOWNTE=a,b

)))|(% style="width:143px" %)**a**: Set the conversion between the downlink of the standard version and 1T version|(% style="width:229px" %)(((

747

**0**: Set the downlink of the standard version.

748

**1**: Set the downlink of the 1T version(ThingsEye platform)

749

)))

750

|(% style="width:143px" %)**b**: Enable/Disable downlink debugging|(% style="width:229px" %)(((

751

**0**: Disable downlink debugging mode.

752

**1**: Enable downlink debugging mode, users can see the original downlink reception.

)))

**Example:**

* AT+DOWNTE=0,1 ~/~/ Set to standard version downlink, and enable downlink debugging.

758

* AT+DOWNTE=1,1 ~/~/ Set to 1T version downlink, and enable downlink debugging.

759

760

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

761

762

No downlink commands for feature

763

764

765

== 2.14 Domain name resolution settings(Since firmware v1.0.0) ==

766

767

768

Feature: Set dynamic domain name resolution IP.

769

770

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

771

772

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

773

|=(% style="width: 138px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 143px; background-color: rgb(79, 129, 189); color: white;" %)**Function/Parameters**|=(% style="width: 229px; background-color: rgb(79, 129, 189); color: white;" %)**Response/Explanation**

774

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

775

AT+BKDNS=?

776

)))|(% style="width:143px" %)Get current Settings|(% style="width:606px" %)(((

0,0,NULL (default)

OK

)))

|(% colspan="1" rowspan="3" style="width:134px" %)(((

AT+BKDNS=a,b,c

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

794

**a**: Enable/Disable dynamic domain name resolution.

795

)))|(% style="width:606px" %)**1**: Disable dynamic domain name update. The ip address will be saved after the domain name is resolved, if the next domain name resolution fails, the last saved ip address will be used.

796

**2**: Enable dynamic domain name update. The ip address will be saved after domain name resolution, if the next domain name resolution fails, the last saved ip address will be used, and the domain name resolution will be updated regularly according to the time set by the customer.

797

|(% style="width:143px" %)**b**: Set the time to update the domain name resolution at regular intervals.|(% style="width:606px" %)(((

798

Unit: hour

799

)))

800

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

801

**c**: Set the IP address manually.

802

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

803

The format is the same as AT+SERVADDR.

804

If domain name resolution fails, this ip address will be used directly, if domain name resolution succeeds, parameter c will be updated to the successfully resolved IP address.

)))

**Example:**

* AT+BKDNS=1,0 ~/~/ Dynamic domain name resolution is disabled.

810

* AT+BKDNS=2,1 ~/~/ The dynamic domain name resolution function is enabled and the automatic update time is set to 1 hour.

811

* AT+BKDNS=2,4,3.69.98.183,1883 ~/~/ The dynamic domain name resolution function is enabled and the automatic update time is set to 4 hour, and manually set the ip address, if the domain name failed to resolve, it will directly use this ip to communicate. When the next domain name resolution is successful, it will be updated to the ip address of the successful resolution.

812

813

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

814

815

No downlink commands for feature

816

817

818

== 2.12 Set CoAP option ==

819

820

821

This command sets the connection parameters of the COAP.

822

823

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

824

825

* AT+URI1 ~/~/ CoAP option name, CoAP option length, "CoAP option value"

826

* AT+URI2 ~/~/ CoAP option name, CoAP option length, "CoAP option value"

827

* AT+URI3 ~/~/ CoAP option name, CoAP option length, "CoAP option value"

828

* AT+URI4 ~/~/ CoAP option name, CoAP option length, "CoAP option value"

**Example:**

* AT+URI1=11,38,"i/faaa241f-af4a-b780-4468-c671bb574858"

833

834

= 3. Configure LDS25-NB =

835

836

== 3.1 Configure Methods ==

837

838

839

LDS25-NB supports below configure method:

840

841

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

842

843

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

844

845

== 3.2 Serial Access Password ==

846

847

848

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

849

850

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

851

852

[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/RS485-NB%2C-NS_RS485%2CUART_to_NB-IoT_Converter_User_Manual/WebHome/image-20250226165815-1.png?rev=1.1||alt="image-20250226165815-1.png"]]

853

854

855

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

856

857

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

858

859

860

(% style="color:red" %)**Note: After entering the command, you need to add a line break, and you can also set automatic line breaks in the Bluetooth tool or UART connection tool.**

861

862

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

== 3.3 AT Commands Set ==

867

868

869

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

AT+<CMD> : Run <CMD>

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

874

875

AT+<CMD>=? : Get the value

876

877

878

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

AT : Attention

AT? : Short Help

AT+MODEL : Get module information

885

886

AT+DEUI : Get or set the Device ID

887

888

AT+SLEEP : Get or set the sleep status

889

890

AT+DEBUG : Set more info output

891

892

AT+SERVADDR : Get or Set the Server address

893

894

AT+TDC : Get or set the application data transmission interval in s

895

896

AT+APN : Get or set the APN

897

898

AT+RXDL : Get or Set the receiving time

899

900

AT+GETSENSORVALUE : Returns the current sensor measurement

901

902

AT+CSQTIME : Get or Set the time to join the network

903

904

AT+DNSTIMER : Get or Set the NDS timer

905

906

AT+PRO : Get or Set usage agreement (1:COAP,2:UDP,3:MQTT,4:TCP)

907

908

AT+3V3T : Get or Set extend the time of 3V3 power

909

910

AT+INTMOD : Get or Set the trigger interrupt mode (0:input,1:falling or rising,2:falling,3:rising)

911

912

AT+TIMESTAMP : Get or Set UNIX timestamp in second

913

914

915

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

916

917

AT+CLIENT : Get or Set the MQTT clientID

918

919

AT+UNAME : Get or Set the MQTT Username

920

921

AT+PWD : Get or Set the MQTT password

922

923

AT+PUBTOPIC : Get or set MQTT publishing topic

924

925

AT+SUBTOPIC : Get or set MQTT subscription topic

926

927

AT+TLSMOD : Get or Set the TLS mode

928

929

AT+MQOS : Set the QoS level of MQTT

930

931

932

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

933

934

AT+FDR1 : Reset parameters to factory default values except for passwords

935

936

AT+FDR : Reset Parameters to Factory Default

937

938

AT+PWORD : Get or set the System password

939

940

AT+LDATA : Get the last upload data

941

942

AT+CDP : Read or Clear cached data

943

944

AT+CFG : Print all settings

945

946

AT+GETLOG : Print serial port logs

947

948

AT+LDATA : Get the last upload data

949

950

AT+CDP : Read or Clear cached data

951

952

ATZ : Trig a reset of the MCU

953

954

AT+DNSCFG : Get or Set DNS Server

955

956

AT+REMODUST : Get or set the number of dust removal mode

957

958

AT+CLOCKLOG : Enable or Disable Clock Logging

959

960

961

(% style="color:blue" %)**COAP Configuration Instructions**

962

963

AT+URI1 : Get or set CoAP option 1

964

965

AT+URI2 : Get or set CoAP option 2

966

967

AT+URI3 : Get or set CoAP option 3

968

969

AT+URI4 : Get or set CoAP option 4

970

971

972

= 4. Battery & Power Consumption =

973

974

975

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

976

977

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

978

979

980

= 5. Firmware update =

981

982

983

User can change device firmware to:

984

985

* Update with new features.

* Fix bugs.

Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/scl/fo/s434scql3wo9sbx3tjiv9/AH1QGENNlajMpXBQp2jONG0?rlkey=plzrydsp2jy0ufumsk1vl57ob&st=idsqf1ri&dl=0]]**

990

991

Methods to Update Firmware:

992

993

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

994

995

* Update through UART TTL interface : **[[Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.

= 6. FAQ =

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

1000

1001

1002

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

1003

1004

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

1005

1006

1007

== 6.2 How to configure the certificate? ==

1008

1009

1010

an can refer to this [[description>>url:http://wiki.dragino.com/xwiki/bin/view/How%20to%20configure%20the%20certificate%3F/]] to configure the certificate.

1011

1012

1013

= 7. Trouble Shooting =

1014

1015

== 7.1 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.)

)))

(((

(% style="color:red" %)**Troubleshooting**(%%): Please avoid use of this product under such circumstance in practice.

)))

(((

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

)))

(((

(% style="color:red" %)**Troubleshooting**(%%): please use dry dust-free cloth to gently remove the foreign matter.

)))

= 8. Order Info =

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

1040

1041

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

1042

1043

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

1044

1045

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

= 9. Packing Info =

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

1051

1052

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

1053

1054

* External antenna x 1

1055

1056

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

1057

1058

* Device Size: 13.0 x 5 x 4.5 cm

1059

1060

* Device Weight: 150g

1061

1062

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

1063

1064

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

1070

1071

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

1072

1073

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

Wiki source code of LDS25-NB -- NB-IoT LiDAR ToF Distance Auto-Clean Sensor

Applications

Navigation