Wiki source code of LDS25-CB -- NB-IoT/LTE-M LiDAR ToF Distance Auto-Clean Sensor
Version 169.1 by Mengting Qiu on 2024/11/05 19:47
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 | (% style="text-align:center" %) | ||
| 4 | [[image:image-20231017170656-1.png||height="454" width="660"]] | ||
| 5 | |||
| 6 | |||
| 7 | |||
| 8 | |||
| 9 | |||
| 10 | |||
| 11 | |||
| 12 | |||
| 13 | **Table of Contents:** | ||
| 14 | |||
| 15 | {{toc/}} | ||
| 16 | |||
| 17 | |||
| 18 | |||
| 19 | |||
| 20 | |||
| 21 | |||
| 22 | = 1. Introduction = | ||
| 23 | |||
| 24 | == 1.1 What is LDS25-CB NB-IoT/LTE-M LiDAR Distance Auto-Clean Sensor == | ||
| 25 | |||
| 26 | |||
| 27 | The Dragino LDS25-CB is a (% style="color:blue" %)**NB-IoT/LTE-M LiDAR ToF (Time of Flight) Distance Auto-Clean 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 25m)!. The LiDAR probe uses laser induction technology for distance measurement. | ||
| 28 | |||
| 29 | 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. | ||
| 30 | |||
| 31 | The LDS25-CB 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. | ||
| 32 | |||
| 33 | It detects the distance between the measured object and the sensor, and uploads the value via wireless to NB-IoT/CAT-M1 IoT Server. | ||
| 34 | |||
| 35 | LDS25-CB 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. | ||
| 36 | |||
| 37 | LDS25-CB (% style="color:blue" %)**supports BLE configure **(%%)and(% style="color:blue" %)** OTA update**(%%) which make user easy to use. | ||
| 38 | |||
| 39 | LDS25-CB is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long-term use up to several years. | ||
| 40 | |||
| 41 | LDS25-CB has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration. | ||
| 42 | |||
| 43 | |||
| 44 | == 1.2 Features == | ||
| 45 | |||
| 46 | |||
| 47 | * For -NB Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 | ||
| 48 | * For -CB Bands: B1/B2/B3/B4/B5/B8/B12/B13~/~/B18/B19/B20/B25/B28/B66/B71/B85 | ||
| 49 | * CAT-M1 / LTE-M Bands: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 | ||
| 50 | * Ultra-low power consumption | ||
| 51 | * Laser technology for distance detection | ||
| 52 | * Self-contained Auto-clean function | ||
| 53 | * Measure Distance: 0.1m~~25m | ||
| 54 | * Accuracy : ±6cm@(0.1m-6m), ±1%@(6m-25m) | ||
| 55 | * Resolution : 1cm | ||
| 56 | * FOV : 3° | ||
| 57 | * Monitor Battery Level | ||
| 58 | * Multiply Sampling and one uplink | ||
| 59 | * Uplink via MQTT, MQTTs, TCP, UDP or CoAP | ||
| 60 | * GNSS for Location Report | ||
| 61 | * Support Bluetooth v5.1 remote configure and update firmware | ||
| 62 | * Uplink on periodically | ||
| 63 | * Downlink to change configure | ||
| 64 | * IP65 Waterproof Enclosure | ||
| 65 | * 8500mAh Battery for long term use | ||
| 66 | * Nano SIM card slot for NB-IoT SIM | ||
| 67 | |||
| 68 | == 1.3 Specification == | ||
| 69 | |||
| 70 | |||
| 71 | (% style="color:blue" %)**Common DC Characteristics:** | ||
| 72 | |||
| 73 | * Supply Voltage: 2.6v ~~ 3.6v | ||
| 74 | * Operating Temperature: -40 ~~ 85°C | ||
| 75 | |||
| 76 | (% style="color:blue" %)**Probe Specification:** | ||
| 77 | |||
| 78 | * Storage temperature：-30°C~~80°C | ||
| 79 | * Operating temperature: -20°C~~60°C | ||
| 80 | * Measure Distance: | ||
| 81 | ** 0.1m ~~ 25m @ 90% Reflectivity | ||
| 82 | ** 0.1m ~~ 12m @ 10% Reflectivity | ||
| 83 | * Accuracy : ±6cm@(0.1m-6m), ±1%@(6m-25m) | ||
| 84 | * Distance resolution : 1cm | ||
| 85 | * Ambient light immunity : 100klux | ||
| 86 | * Enclosure rating : IP5X | ||
| 87 | * Light source : VCSEL | ||
| 88 | * Central wavelength : 850nm | ||
| 89 | * FOV : 3° | ||
| 90 | * Material of enclosure : ABS+PC | ||
| 91 | * Wire length : 120cm | ||
| 92 | |||
| 93 | (% style="color:blue" %)**NB-IoT Spec:** | ||
| 94 | |||
| 95 | (% style="color:#037691" %)**NB-IoT Module: BG95-NGFF** | ||
| 96 | |||
| 97 | (% style="color:#037691" %)**Support Bands:** | ||
| 98 | |||
| 99 | * B1 @H-FDD: 2100MHz | ||
| 100 | * B2 @H-FDD: 1900MHz | ||
| 101 | * B3 @H-FDD: 1800MHz | ||
| 102 | * B4 @H-FDD: 2100MHz | ||
| 103 | * B5 @H-FDD: 860MHz | ||
| 104 | * B8 @H-FDD: 900MHz | ||
| 105 | * B12 @H-FDD: 720MHz | ||
| 106 | * B13 @H-FDD: 740MHz | ||
| 107 | * B17 @H-FDD: 730MHz | ||
| 108 | * B18 @H-FDD: 870MHz | ||
| 109 | * B19 @H-FDD: 870MHz | ||
| 110 | * B20 @H-FDD: 790MHz | ||
| 111 | * B25 @H-FDD: 1900MHz | ||
| 112 | * B28 @H-FDD: 750MHz | ||
| 113 | * B66 @H-FDD: 2000MHz | ||
| 114 | * B70 @H-FDD: 2000MHz | ||
| 115 | * B85 @H-FDD: 700MHz | ||
| 116 | |||
| 117 | (% style="color:blue" %)**Battery:** | ||
| 118 | |||
| 119 | * Li/SOCI2 un-chargeable battery | ||
| 120 | * Capacity: 8500mAh | ||
| 121 | * Self Discharge: <1% / Year @ 25°C | ||
| 122 | * Max continuously current: 130mA | ||
| 123 | * Max boost current: 2A, 1 second | ||
| 124 | |||
| 125 | (% style="color:blue" %)**Power Consumption** | ||
| 126 | |||
| 127 | * STOP Mode: 10uA @ 3.3v | ||
| 128 | * Max transmit power: 350mA@3.3v | ||
| 129 | |||
| 130 | == 1.4 Applications == | ||
| 131 | |||
| 132 | |||
| 133 | * Horizontal distance measurement | ||
| 134 | * Parking management system | ||
| 135 | * Object proximity and presence detection | ||
| 136 | * Intelligent trash can management system | ||
| 137 | * Robot obstacle avoidance | ||
| 138 | * Automatic control | ||
| 139 | * Sewer | ||
| 140 | |||
| 141 | == 1.5 Sleep mode and working mode == | ||
| 142 | |||
| 143 | |||
| 144 | (% 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. | ||
| 145 | |||
| 146 | (% 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. | ||
| 147 | |||
| 148 | |||
| 149 | == 1.6 Button & LEDs == | ||
| 150 | |||
| 151 | |||
| 152 | [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]] | ||
| 153 | |||
| 154 | |||
| 155 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
| 156 | |=(% 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** | ||
| 157 | |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)((( | ||
| 158 | If sensor has already attached to NB-IoT network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once. | ||
| 159 | Meanwhile, BLE module will be active and user can connect via BLE to configure device. | ||
| 160 | ))) | ||
| 161 | |(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)((( | ||
| 162 | (% 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. | ||
| 163 | (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
| 164 | 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. | ||
| 165 | ))) | ||
| 166 | |(% 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. | ||
| 167 | |||
| 168 | (% 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.** | ||
| 169 | |||
| 170 | |||
| 171 | == 1.7 BLE connection == | ||
| 172 | |||
| 173 | |||
| 174 | LDS25-CB support BLE remote configure and firmware update. | ||
| 175 | |||
| 176 | |||
| 177 | 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: | ||
| 178 | |||
| 179 | * Press button to send an uplink | ||
| 180 | * Press button to active device. | ||
| 181 | * Device Power on or reset. | ||
| 182 | |||
| 183 | If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode. | ||
| 184 | |||
| 185 | |||
| 186 | == 1.8 Pin Definitions , Switch & SIM Direction == | ||
| 187 | |||
| 188 | |||
| 189 | [[image:image-20241031173444-1.jpeg||height="442" width="721"]] | ||
| 190 | |||
| 191 | |||
| 192 | === 1.8.1 Jumper JP2 === | ||
| 193 | |||
| 194 | |||
| 195 | Power on Device when put this jumper. | ||
| 196 | |||
| 197 | |||
| 198 | === 1.8.2 BOOT MODE / SW1 === | ||
| 199 | |||
| 200 | |||
| 201 | **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. | ||
| 202 | |||
| 203 | **2)** (% style="color:blue" %)**Flash**(%%): work mode, device starts to work and send out console output for further debug | ||
| 204 | |||
| 205 | |||
| 206 | === 1.8.3 Reset Button === | ||
| 207 | |||
| 208 | |||
| 209 | Press to reboot the device. | ||
| 210 | |||
| 211 | |||
| 212 | === 1.8.4 SIM Card Direction === | ||
| 213 | |||
| 214 | |||
| 215 | 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]]. | ||
| 216 | |||
| 217 | |||
| 218 | == 1.9 Mechanical == | ||
| 219 | |||
| 220 | [[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"]] | ||
| 221 | |||
| 222 | [[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"]] | ||
| 223 | |||
| 224 | [[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"]] | ||
| 225 | |||
| 226 | |||
| 227 | (% style="color:blue" %)**Probe Mechanical:** | ||
| 228 | |||
| 229 | |||
| 230 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS40-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1666948963951-832.png?rev=1.1||alt="1666948963951-832.png"]] | ||
| 231 | |||
| 232 | |||
| 233 | = 2. Use LDS25-CB to communicate with IoT Server = | ||
| 234 | |||
| 235 | == 2.1 Send data to IoT server via NB-IoT/CAT-M1 network == | ||
| 236 | |||
| 237 | |||
| 238 | The LDS25-CB is equipped with a NB-IoT module, the pre-loaded firmware in LDS25-CB 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-CB. | ||
| 239 | |||
| 240 | Below shows the network structure: | ||
| 241 | |||
| 242 | [[image:image-20240722101715-1.jpeg]] | ||
| 243 | |||
| 244 | |||
| 245 | There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1T**(%%) version of LDS25-CB. | ||
| 246 | |||
| 247 | |||
| 248 | (% 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-CB send data to IoT server. | ||
| 249 | |||
| 250 | * 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]]. | ||
| 251 | |||
| 252 | * 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]]. | ||
| 253 | |||
| 254 | Below shows result of different server as a glance. | ||
| 255 | |||
| 256 | (% border="1" cellspacing="4" style="width:515px" %) | ||
| 257 | |(% 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** | ||
| 258 | |(% 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" %)((( | ||
| 259 | (% style="text-align:center" %) | ||
| 260 | [[image:image-20230819113244-8.png||height="183" width="367"]] | ||
| 261 | )))|(% style="width:170px" %) | ||
| 262 | |(% 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" %)((( | ||
| 263 | (% style="text-align:center" %) | ||
| 264 | [[image:image-20230819113244-9.png||height="119" width="367"]] | ||
| 265 | )))|(% style="width:170px" %) | ||
| 266 | |(% 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" %) | ||
| 267 | |(% 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" %) | ||
| 268 | |(% 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" %) | ||
| 269 | |(% 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" %)((( | ||
| 270 | (% style="text-align:center" %) | ||
| 271 | [[image:image-20230819113244-10.png||height="104" width="367"]] | ||
| 272 | )))|(% style="width:170px" %) | ||
| 273 | |(% 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" %)((( | ||
| 274 | (% style="text-align:center" %) | ||
| 275 | [[image:image-20230819113244-11.png||height="141" width="367"]] | ||
| 276 | )))|(% style="width:170px" %) | ||
| 277 | |||
| 278 | (% style="color:blue" %)**1T 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 LDS25-CB 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]]. | ||
| 279 | |||
| 280 | |||
| 281 | == 2.2 Payload Types == | ||
| 282 | |||
| 283 | |||
| 284 | To meet different server requirement, LDS25-CB supports different payload type. | ||
| 285 | |||
| 286 | **Includes:** | ||
| 287 | |||
| 288 | * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5) | ||
| 289 | |||
| 290 | * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0) | ||
| 291 | |||
| 292 | * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1) | ||
| 293 | |||
| 294 | * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3) | ||
| 295 | |||
| 296 | User can specify the payload type when choose the connection protocol. Example: | ||
| 297 | |||
| 298 | (% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Use UDP Connection & hex Payload | ||
| 299 | |||
| 300 | (% style="color:#037691" %)**AT+PRO=2,5** (%%) ~/~/ Use UDP Connection & Json Payload | ||
| 301 | |||
| 302 | (% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload | ||
| 303 | |||
| 304 | |||
| 305 | === 2.2.1 General Json Format(Type~=5) === | ||
| 306 | |||
| 307 | |||
| 308 | This is the General Json Format. As below: | ||
| 309 | |||
| 310 | (% style="color:#4472c4" %)**{"IMEI":"868508065601703","Model":"LDS25-CB","distance":342,"distance_signal_strength":0,"lidar_temp":0,"battery":3.392,"signal":23,"latitude":0.000000,"longitude":0.000000,"gps_time":"2024-11-01T09:53:00Z","1":[0,65534,"2024-11-01T08:59:38Z"],"2":[0,65534,"2024-11-01T08:44:38Z"],"3":[0,65534,"2024-11-01T08:29:38Z"],"4":[0,65534,"2024-11-01T08:14:38Z"],"5":[0,65534,"2024-11-01T07:59:38Z"],"6":[0,65534,"2024-11-01T07:44:38Z"],"7":[0,65534,"2024-11-01T07:29:38Z"],"8":[0,65534,"2024-11-01T07:14:38Z"]}** | ||
| 311 | |||
| 312 | [[image:image-20241101175702-1.png||height="699" width="818"]] | ||
| 313 | |||
| 314 | |||
| 315 | (% style="color:red" %)**Notice, from above payload:** | ||
| 316 | |||
| 317 | * DS18b20_temperature, Distance, Distance signal strength, Temperature, Interrupt, Interrupt_level, Battery & Signal are the value at uplink time. | ||
| 318 | |||
| 319 | * 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. | ||
| 320 | |||
| 321 | === 2.2.2 HEX format Payload(Type~=0) === | ||
| 322 | |||
| 323 | |||
| 324 | This is the HEX Format. As below: | ||
| 325 | |||
| 326 | (% style="color:#4472c4" %)**f8685080656017036f640d3c12000000000000000000006724a64e000000fffe6724a64e0000fffe6724987a0000fffe672494f60000fffe672491720000fffe67248dee0000fffe67248a6a0000fffe672486e60000fffe672483620000fffe67247fde** | ||
| 327 | |||
| 328 | [[image:image-20240528155734-2.png||height="156" width="940"]] | ||
| 329 | |||
| 330 | |||
| 331 | If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. | ||
| 332 | |||
| 333 | [[image:image-20241101180302-2.png||height="724" width="842"]] | ||
| 334 | |||
| 335 | (% style="color:blue" %)**Version:** | ||
| 336 | |||
| 337 | These bytes include the hardware and software version. | ||
| 338 | |||
| 339 | (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x10 for LDS25-CB | ||
| 340 | |||
| 341 | (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x7b=123, means firmware version 1.2.3 | ||
| 342 | |||
| 343 | |||
| 344 | (% style="color:blue" %)**BAT (Battery Info):** | ||
| 345 | |||
| 346 | Ex1: 0x0DB4 = 3508mV | ||
| 347 | |||
| 348 | |||
| 349 | (% style="color:blue" %)**DS18B20 Temperature sensor:** | ||
| 350 | |||
| 351 | This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature. | ||
| 352 | |||
| 353 | **Example**: | ||
| 354 | |||
| 355 | If payload is: 0105H: (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree | ||
| 356 | |||
| 357 | If payload is: FF3FH : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. | ||
| 358 | |||
| 359 | |||
| 360 | (% style="color:blue" %)**Distance:** | ||
| 361 | |||
| 362 | 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. | ||
| 363 | |||
| 364 | **Example**: | ||
| 365 | |||
| 366 | 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**. | ||
| 367 | |||
| 368 | |||
| 369 | (% style="color:blue" %)**Distance signal strength:** | ||
| 370 | |||
| 371 | 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. | ||
| 372 | |||
| 373 | 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. | ||
| 374 | |||
| 375 | **Example**: | ||
| 376 | |||
| 377 | If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible. | ||
| 378 | |||
| 379 | Customers can judge whether they need to adjust the environment based on the signal strength. | ||
| 380 | |||
| 381 | |||
| 382 | (% style="color:blue" %)**Interrupt:** | ||
| 383 | |||
| 384 | This data field shows if this packet is generated by interrupt or not. | ||
| 385 | |||
| 386 | **Example:** | ||
| 387 | |||
| 388 | If byte[0]&0x01=0x00 : Normal uplink packet. | ||
| 389 | |||
| 390 | If byte[0]&0x01=0x01 : Interrupt Uplink Packet. | ||
| 391 | |||
| 392 | |||
| 393 | |||
| 394 | (% style="color:blue" %)**Interrupt Level:** | ||
| 395 | |||
| 396 | This byte shows whether the interrupt is triggered by a high or low level. | ||
| 397 | |||
| 398 | **Ex1:** 0x00 Interrupt triggered by falling edge (low level) | ||
| 399 | |||
| 400 | **Ex2: **0x01 Interrupt triggered by rising edge (high level) | ||
| 401 | |||
| 402 | |||
| 403 | |||
| 404 | (% style="color:blue" %)**LiDAR temp:** | ||
| 405 | |||
| 406 | Characterize the internal temperature value of the sensor. | ||
| 407 | |||
| 408 | **Example: ** | ||
| 409 | |||
| 410 | If payload is: 001C(H) <<24>>24=28(D), LiDAR temp=28°C. | ||
| 411 | |||
| 412 | If payload is: FFF2(H) <<24>>24=-14(D), LiDAR temp=-14°C. | ||
| 413 | |||
| 414 | |||
| 415 | (% style="color:blue" %)**TimeStamp: ** | ||
| 416 | |||
| 417 | Unit TimeStamp Example: 64d49439(H) = 1691653177(D) | ||
| 418 | |||
| 419 | Put the decimal value into this link([[https:~~/~~/www.epochconverter.com)>>https://www.epochconverter.com]]) to get the time. | ||
| 420 | |||
| 421 | |||
| 422 | === 2.2.3 ThingsBoard Payload(Type~=3) === | ||
| 423 | |||
| 424 | |||
| 425 | Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard. | ||
| 426 | |||
| 427 | (% style="color:#4472c4" %)**{ | ||
| 428 | "topic": "CB_PUB", | ||
| 429 | "payload": { | ||
| 430 | "IMEI": "864370064394515", | ||
| 431 | "Model": "LDS25-CB", | ||
| 432 | "ds18b20_temperature": -0.1, | ||
| 433 | "distance": 354, | ||
| 434 | "distance_signal_strength": 1506, | ||
| 435 | "temperature": 29, | ||
| 436 | "interrupt": 0, | ||
| 437 | "interrupt_level": 0, | ||
| 438 | "battery": 3.27, | ||
| 439 | "signal": 29, | ||
| 440 | "latitude": 0.0, | ||
| 441 | "longitude": 0.0, | ||
| 442 | "gps_time": "1970-01-01T00:00:00Z", | ||
| 443 | "1": [0, 65534, 0, "2024-07-20T07:12:43Z"], | ||
| 444 | "2": [0, 65534, 0, "2024-07-20T06:54:03Z"], | ||
| 445 | "3": [0, 0, 0, "2024-07-20T06:22:00Z"], | ||
| 446 | "4": [0, 0, 0, "2024-07-20T05:39:40Z"], | ||
| 447 | "5": [0, 0, 0, "2024-07-20T05:24:40Z"], | ||
| 448 | "6": [0, 0, 0, "2024-07-20T05:09:40Z"], | ||
| 449 | "7": [0, 0, 0, "2024-07-20T04:54:40Z"], | ||
| 450 | "8": [0, 0, 0, "2024-07-20T04:39:40Z"] | ||
| 451 | } | ||
| 452 | }** | ||
| 453 | |||
| 454 | [[image:image-20240722105208-2.png||height="570" width="1154"]] | ||
| 455 | |||
| 456 | |||
| 457 | === 2.2.4 ThingSpeak Payload(Type~=1) === | ||
| 458 | |||
| 459 | |||
| 460 | This payload meets ThingSpeak platform requirement. It includes six fields. Form 1~~8 are: | ||
| 461 | |||
| 462 | DS18b20_temperature, Distance, Distance signal strength, Temperature, Battery & Signal. This payload type only valid for ThingsSpeak Platform. | ||
| 463 | |||
| 464 | As below: | ||
| 465 | |||
| 466 | (% style="color:#4472c4" %)**field1=Distance value&field2=Distance signal strength value&field3=Temperature value&field4=Battery value&field5=Signal value&field6=DS18B20_temperature value&field7=Interrupt value&field8=Interrupt level value** | ||
| 467 | |||
| 468 | [[image:image-20240722105833-5.png||height="572" width="907"]] | ||
| 469 | |||
| 470 | [[image:image-20240722105844-6.png]] | ||
| 471 | |||
| 472 | |||
| 473 | == 2.6 LiDAR ToF Measurement == | ||
| 474 | |||
| 475 | === 2.6.1 Principle of Distance Measurement === | ||
| 476 | |||
| 477 | |||
| 478 | 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. | ||
| 479 | |||
| 480 | [[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"]] | ||
| 481 | |||
| 482 | |||
| 483 | === 2.6.2 Distance Measurement Characteristics === | ||
| 484 | |||
| 485 | |||
| 486 | The detection angle of the LDS25-CB is 3 degrees, and the size of the light spot at different distances is the side length of the detection range. The size of the light spot at different distances is the side length of the detection range. The side length of the detection range (the shape is square), as shown. | ||
| 487 | |||
| 488 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %) | ||
| 489 | |(% style="width:240px" %)**Distance(m)**|(% style="width:26px" %)1|(% style="width:35px" %)2|(% style="width:36px" %)3|(% style="width:32px" %)5|(% style="width:33px" %)7|(% style="width:34px" %)10|(% style="width:43px" %)20|(% style="width:41px" %)30|(% style="width:41px" %)40 | ||
| 490 | |(% style="width:240px" %)**Detection range side length (cm)**|(% style="width:26px" %)5|(% style="width:35px" %)10|(% style="width:36px" %)16|(% style="width:32px" %)26|(% style="width:33px" %)37|(% style="width:34px" %)52|(% style="width:43px" %)105|(% style="width:41px" %)156|(% style="width:41px" %)208 | ||
| 491 | |||
| 492 | Note that generally, the side length of the detected target object should be greater than the side length of the detection range of the LDS25-CB; when the detected object is smaller than the detection range side length; when the detected object is smaller than the detection range side length, the effective range of the radar will be reduced. | ||
| 493 | |||
| 494 | |||
| 495 | === 2.6.3 Notice of usage === | ||
| 496 | |||
| 497 | |||
| 498 | Possible invalid /wrong reading for LiDAR ToF tech: | ||
| 499 | |||
| 500 | * Measure high reflectivity object such as: Mirror, Smooth ceramic tile, static milk surface, will have possible wrong readings. | ||
| 501 | |||
| 502 | * While there is transparent object such as glass, water drop between the measured object and the LiDAR sensor, the reading might be wrong. | ||
| 503 | |||
| 504 | * The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe. | ||
| 505 | |||
| 506 | * The sensor window is made by Acrylic. Don't touch it with alcohol material. This will destroy the sensor window. | ||
| 507 | |||
| 508 | === 2.6.4 Reflectivity of different objects === | ||
| 509 | |||
| 510 | |||
| 511 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:379px" %) | ||
| 512 | |=(% 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 | ||
| 513 | |(% style="width:53px" %)1|(% style="width:229px" %)Black foam rubber|(% style="width:93px" %)2.4% | ||
| 514 | |(% style="width:53px" %)2|(% style="width:229px" %)Black fabric|(% style="width:93px" %)3% | ||
| 515 | |(% style="width:53px" %)3|(% style="width:229px" %)Black rubber|(% style="width:93px" %)4% | ||
| 516 | |(% style="width:53px" %)4|(% style="width:229px" %)Coal (different types of coal)|(% style="width:93px" %)4~~8% | ||
| 517 | |(% style="width:53px" %)5|(% style="width:229px" %)Black car paint|(% style="width:93px" %)5% | ||
| 518 | |(% style="width:53px" %)6|(% style="width:229px" %)Black Jam|(% style="width:93px" %)10% | ||
| 519 | |(% style="width:53px" %)7|(% style="width:229px" %)Opaque black plastic|(% style="width:93px" %)14% | ||
| 520 | |(% style="width:53px" %)8|(% style="width:229px" %)Clean rough board|(% style="width:93px" %)20% | ||
| 521 | |(% style="width:53px" %)9|(% style="width:229px" %)Translucent plastic bottle|(% style="width:93px" %)62% | ||
| 522 | |(% style="width:53px" %)10|(% style="width:229px" %)Carton cardboard|(% style="width:93px" %)68% | ||
| 523 | |(% style="width:53px" %)11|(% style="width:229px" %)Clean pine|(% style="width:93px" %)70% | ||
| 524 | |(% style="width:53px" %)12|(% style="width:229px" %)Opaque white plastic|(% style="width:93px" %)87% | ||
| 525 | |(% style="width:53px" %)13|(% style="width:229px" %)White Jam|(% style="width:93px" %)90% | ||
| 526 | |(% style="width:53px" %)14|(% style="width:229px" %)Kodak Standard Whiteboard|(% style="width:93px" %)100% | ||
| 527 | |(% style="width:53px" %)15|(% style="width:229px" %)((( | ||
| 528 | Unpolished white metal surface | ||
| 529 | )))|(% style="width:93px" %)130% | ||
| 530 | |(% style="width:53px" %)16|(% style="width:229px" %)Glossy light metal surface|(% style="width:93px" %)150% | ||
| 531 | |(% style="width:53px" %)17|(% style="width:229px" %)stainless steel|(% style="width:93px" %)200% | ||
| 532 | |(% style="width:53px" %)18|(% style="width:229px" %)Reflector plate, reflective tape|(% style="width:93px" %)>300% | ||
| 533 | |||
| 534 | = 3. Configure DDS45-CB = | ||
| 535 | |||
| 536 | == 3.1 Configure Methods == | ||
| 537 | |||
| 538 | |||
| 539 | DDS45-CB supports below configure method: | ||
| 540 | |||
| 541 | * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]. | ||
| 542 | |||
| 543 | * 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]]. | ||
| 544 | |||
| 545 | == 3.2 Serial Access Password == | ||
| 546 | |||
| 547 | |||
| 548 | After the Bluetooth or UART connection is successful, use the Serial Access Password to enter the AT command window. | ||
| 549 | |||
| 550 | 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. | ||
| 551 | |||
| 552 | [[image:image-20240826184824-1.png]] | ||
| 553 | |||
| 554 | |||
| 555 | If you need to change the password, use **AT+PWORD=**xxxxxx (6 characters), -CB nodes only support lowercase letters. | ||
| 556 | |||
| 557 | [[image:image-20240826184830-2.png]] | ||
| 558 | |||
| 559 | |||
| 560 | (% 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.** | ||
| 561 | |||
| 562 | [[image:image-20240826184838-3.png]] | ||
| 563 | |||
| 564 | |||
| 565 | == (% data-sider-select-id="1e751b55-39cf-4950-96a9-a2a7be8c4dd3" %)3.3 AT Commands Set(%%) == | ||
| 566 | |||
| 567 | |||
| 568 | AT+<CMD>? : Help on <CMD> | ||
| 569 | |||
| 570 | AT+<CMD> : Run <CMD> | ||
| 571 | |||
| 572 | AT+<CMD>=<value> : Set the value | ||
| 573 | |||
| 574 | AT+<CMD>=? : Get the value | ||
| 575 | |||
| 576 | |||
| 577 | (% style="color:blue" %)**General Commands** | ||
| 578 | |||
| 579 | AT : Attention | ||
| 580 | |||
| 581 | AT? : Short Help | ||
| 582 | |||
| 583 | AT+MODEL : Get module information | ||
| 584 | |||
| 585 | ATZ : Trig a reset of the MCU | ||
| 586 | |||
| 587 | AT+CFGMOD : Working mode selection | ||
| 588 | |||
| 589 | AT+DEUI : Get or set the Device ID | ||
| 590 | |||
| 591 | AT+CFG : Print all settings | ||
| 592 | |||
| 593 | AT+SERVADDR: Get or Set the Server address | ||
| 594 | |||
| 595 | AT+TDC : Get or set the application data transmission interval in s | ||
| 596 | |||
| 597 | AT+INTMOD : Get or Set the trigger interrupt mode (0:input,1:falling or rising,2:falling,3:rising) | ||
| 598 | |||
| 599 | AT+APN : Get or set the APN | ||
| 600 | |||
| 601 | AT+5VT : Get or Set extend the time of 5V power | ||
| 602 | |||
| 603 | AT+PRO : Get or Set usage agreement (1:COAP,2:UDP,3:MQTT,4:TCP) | ||
| 604 | |||
| 605 | AT+RXDL : Get or Set the receiving time | ||
| 606 | |||
| 607 | AT+ALARM:Get or Set alarm of distance | ||
| 608 | |||
| 609 | AT+GETSENSORVALUE : Returns the current sensor measurement | ||
| 610 | |||
| 611 | AT+DNSCFG : Get or Set DNS Server | ||
| 612 | |||
| 613 | AT+CSQTIME : Get or Set the time to join the network | ||
| 614 | |||
| 615 | AT+GDNS : Get or Set the DNS | ||
| 616 | |||
| 617 | AT+TLSMOD : Get or Set the TLS mode | ||
| 618 | |||
| 619 | AT+SLEEP : Get or Set the sleep mode | ||
| 620 | |||
| 621 | AT+DEBUG : Entering/exiting debugging mode | ||
| 622 | |||
| 623 | AT+MQOS : Set the QoS level of MQTT | ||
| 624 | |||
| 625 | AT+IPTYPE : Set the IPv4 or IPv6 | ||
| 626 | |||
| 627 | AT+QSW : Power on and power off BG95 module | ||
| 628 | |||
| 629 | AT+GETLOG : Print serial port logs | ||
| 630 | |||
| 631 | AT+CLOCKLOG: Get or set SHT record time | ||
| 632 | |||
| 633 | AT+QBAND: Get or set Frequency Band | ||
| 634 | |||
| 635 | AT+IOTMOD: Configure Network Category to be Searched for under LTE RAT | ||
| 636 | |||
| 637 | |||
| 638 | (% style="color:blue" %)**MQTT Management** | ||
| 639 | |||
| 640 | AT+CLIENT : Get or Set the MQTT clientID | ||
| 641 | |||
| 642 | AT+UNAME : Get or Set the MQTT Username | ||
| 643 | |||
| 644 | AT+PWD : Get or Set the MQTT password | ||
| 645 | |||
| 646 | AT+PUBTOPIC: Get or set MQTT publishing topic | ||
| 647 | |||
| 648 | AT+SUBTOPIC: Get or set MQTT subscription topic | ||
| 649 | |||
| 650 | |||
| 651 | (% style="color:blue" %)**Coap Management** | ||
| 652 | |||
| 653 | AT+URI1: Get or set CoAP option 1 | ||
| 654 | |||
| 655 | AT+URI2: Get or set CoAP option 2 | ||
| 656 | |||
| 657 | AT+URI3: Get or set CoAP option 3 | ||
| 658 | |||
| 659 | AT+URI4: Get or set CoAP option 4 | ||
| 660 | |||
| 661 | AT+URI5: Get or set CoAP option 5 | ||
| 662 | |||
| 663 | AT+URI6: Get or set CoAP option 6 | ||
| 664 | |||
| 665 | AT+URI7: Get or set CoAP option 7 | ||
| 666 | |||
| 667 | AT+URI8: Get or set CoAP option 8 | ||
| 668 | |||
| 669 | |||
| 670 | (% style="color:blue" %)**GPS** | ||
| 671 | |||
| 672 | AT+GNSST : Extend the time to turn on GNSS | ||
| 673 | |||
| 674 | AT+GPS : Turn off and on GPS | ||
| 675 | |||
| 676 | AT+GTDC : Get or set GPS positioning interval in units of h | ||
| 677 | |||
| 678 | |||
| 679 | (% style="color:blue" %)**Information** | ||
| 680 | |||
| 681 | AT+CDP : Read or Clear cached data | ||
| 682 | |||
| 683 | AT+LDATA : Get the last upload data | ||
| 684 | |||
| 685 | AT+PWORD : Get or set the System password | ||
| 686 | |||
| 687 | AT+FDR1 : Reset parameters to factory default values except for passwords | ||
| 688 | |||
| 689 | AT+FDR : Reset Parameters to Factory Default | ||
| 690 | |||
| 691 | |||
| 692 | == 3.4 Test Uplink and Change Update Interval == | ||
| 693 | |||
| 694 | |||
| 695 | By default, Sensor will send uplinks **every 2 hours.** | ||
| 696 | |||
| 697 | User can use below commands to change the uplink interval. | ||
| 698 | |||
| 699 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+TDC** (%%) | ||
| 700 | |||
| 701 | Example: AT+TDC=7200 ~/~/ Set Update Interval to 7200 seconds | ||
| 702 | |||
| 703 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x01** | ||
| 704 | |||
| 705 | Format: Command Code (0x01) followed by 3 bytes. | ||
| 706 | |||
| 707 | Example: 12 hours= 43200 seconds 43200(D)=0xA8C0(H) | ||
| 708 | |||
| 709 | Downlink Payload: **01 00 A8 C0** ~/~/ AT+TDC=43200, Set Update Interval to 12 hours. | ||
| 710 | |||
| 711 | (% style="color:red" %)**Note: User can also push the button for more than 1 seconds to activate an uplink.** | ||
| 712 | |||
| 713 | |||
| 714 | == 3.5 Set the working mode == | ||
| 715 | |||
| 716 | |||
| 717 | Feature: Working mode selection | ||
| 718 | |||
| 719 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+CFGMOD** | ||
| 720 | |||
| 721 | Example: AT+CFGMOD=1 ~/~/ Set the working mode to 2(Only default mode 1 is available). | ||
| 722 | |||
| 723 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x02** | ||
| 724 | |||
| 725 | Format: Command Code (0x02) followed by 1 byte. | ||
| 726 | |||
| 727 | Example: Downlink Payload: **02 01 **~/~/ AT+CFGMOD=1 | ||
| 728 | |||
| 729 | |||
| 730 | == 3.6 Set the receiving time == | ||
| 731 | |||
| 732 | |||
| 733 | Feature: Extend the receiving time | ||
| 734 | |||
| 735 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+RXDL** | ||
| 736 | |||
| 737 | Example: AT+RXDL=1000 ~/~/ Set the receiving time delay to 1000ms | ||
| 738 | |||
| 739 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x03** | ||
| 740 | |||
| 741 | Format: Command Code (0x03) followed by 3 bytes. | ||
| 742 | |||
| 743 | Example: Downlink Payload: **03 00 03 E8 **~/~/ AT+RXDL=1000 | ||
| 744 | |||
| 745 | |||
| 746 | == 3.7 Reset == | ||
| 747 | |||
| 748 | |||
| 749 | Feature: Trig a reset of the MCU. | ||
| 750 | |||
| 751 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**ATZ** | ||
| 752 | |||
| 753 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x04FF** | ||
| 754 | |||
| 755 | |||
| 756 | == 3.8 +5V == | ||
| 757 | |||
| 758 | |||
| 759 | Feature: Set extend the time of 5V power. | ||
| 760 | |||
| 761 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+5VT** | ||
| 762 | |||
| 763 | Example: AT+5VT=2000 ~/~/ Set extend the time of 5V power to 2000 ms | ||
| 764 | |||
| 765 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x05** | ||
| 766 | |||
| 767 | Format: Command Code (0x05) followed by 3 bytes. | ||
| 768 | |||
| 769 | Example: Downlink Payload: **05 00 07 D0 **~/~/ AT+5VT=2000 | ||
| 770 | |||
| 771 | |||
| 772 | == 3.9 Trigger an uplink by external interrupt == | ||
| 773 | |||
| 774 | |||
| 775 | LDS25-CB has an external trigger interrupt function. Users can use the GPIO_EXTI pin to trigger the upload of data packets. | ||
| 776 | |||
| 777 | (% style="color:blue" %)**AT command:** | ||
| 778 | |||
| 779 | * (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode | ||
| 780 | |||
| 781 | * (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt | ||
| 782 | |||
| 783 | * (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge | ||
| 784 | |||
| 785 | * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge | ||
| 786 | |||
| 787 | * (% style="color:#037691" %)**AT+INTMOD=3 **(%%) ~/~/ Trigger by rising edge | ||
| 788 | |||
| 789 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x06** | ||
| 790 | |||
| 791 | Format: Command Code (0x06) followed by 3 bytes. | ||
| 792 | |||
| 793 | Example1: Downlink Payload: **06 00 00 01 **~/~/ AT+INTMOD=1 | ||
| 794 | |||
| 795 | Example2: Downlink Payload: **06 00 00 03 **~/~/ AT+INTMOD=3 | ||
| 796 | |||
| 797 | |||
| 798 | == 3.10 Set the QoS level == | ||
| 799 | |||
| 800 | |||
| 801 | This command is used to set the QoS level of **MQTT**. | ||
| 802 | |||
| 803 | (% style="color:blue" %)**AT command:** | ||
| 804 | |||
| 805 | * (% style="color:#037691" %)**AT+MQOS=xx**(%%)** **~/~/ 0~~2 | ||
| 806 | |||
| 807 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x07(%%)** | ||
| 808 | |||
| 809 | Format: Command Code (0x07) followed by 1 byte. | ||
| 810 | |||
| 811 | **Ex1:** Downlink payload: **0x0700** ~/~/ AT+MQOS=0 | ||
| 812 | |||
| 813 | **Ex2:** Downlink payload: **0x0701** ~/~/ AT+MQOS=1 | ||
| 814 | |||
| 815 | |||
| 816 | == 3.11 Clock logging == | ||
| 817 | |||
| 818 | |||
| 819 | 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. | ||
| 820 | |||
| 821 | 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. | ||
| 822 | |||
| 823 | (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CLOCKLOG=a,b,c,d(%%)** | ||
| 824 | |||
| 825 | (% style="color:#037691" %)**a: **(%%)**0:** Disable Clock logging. ** 1: **Enable Clock Logging | ||
| 826 | |||
| 827 | (% style="color:#037691" %)**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. | ||
| 828 | |||
| 829 | (% style="color:#037691" %)**c: **(%%)Specify the sampling interval: range **(0 ~~ 255 minutes)** | ||
| 830 | |||
| 831 | (% style="color:#037691" %)**d:**(%%)** **How many entries should be uplink on every TDC **(max 32)** | ||
| 832 | |||
| 833 | (% style="color:red" %)**Note: To disable clock recording, set the following parameters: AT+CLOCKLOG=1,65535,0,0** | ||
| 834 | |||
| 835 | [[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"]] | ||
| 836 | |||
| 837 | **Example:** | ||
| 838 | |||
| 839 | **AT+CLOCKLOG=1,65535,1,5** | ||
| 840 | |||
| 841 | 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). | ||
| 842 | |||
| 843 | [[image:image-20240722111707-8.png||height="554" width="1069"]] | ||
| 844 | |||
| 845 | |||
| 846 | (% class="wikigeneratedid" %) | ||
| 847 | (% 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.** | ||
| 848 | |||
| 849 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x08(%%)** | ||
| 850 | |||
| 851 | Format: Command Code (0x08) followed by 5 bytes. | ||
| 852 | |||
| 853 | * **Example 1**: Downlink Payload:** 08 01 FFFF 0F 08** ~/~/ Set SHT record time: AT+CLOCKLOG=1,65535,15,8 | ||
| 854 | * **Example 2**: Downlink Payload:** 08 01 04B0 0F 08** ~/~/ Set SHT record time: AT+CLOCKLOG=1,1200,15,8 | ||
| 855 | |||
| 856 | (% style="color:red" %)**Note: When entering the downlink payload, there must be no Spaces between bytes.** | ||
| 857 | |||
| 858 | |||
| 859 | == 3.12 Set the TLS mode == | ||
| 860 | |||
| 861 | |||
| 862 | Refer to this link ([[MQTT Connection to send data to Tago.io>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Manual%20for%20-CB%20%2C%20-CS%20models/#H3.7Tago.io28viaMQTT29]])to use the TLS mode. | ||
| 863 | |||
| 864 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+TLSMOD** | ||
| 865 | |||
| 866 | **Example 1: ** AT+TLSMOD=0,0 ~/~/ Disable TLS Mode. | ||
| 867 | |||
| 868 | **Example 2:** AT+TLSMOD=1,0 ~/~/ No authentication | ||
| 869 | |||
| 870 | AT+TLSMOD=1,1 ~/~/ Perform server authentication | ||
| 871 | |||
| 872 | AT+TLSMOD=1,2 ~/~/ Perform server and client authentication if requested by the remote server | ||
| 873 | |||
| 874 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x09(%%)** | ||
| 875 | |||
| 876 | Format: Command Code (0x09) followed by 2 bytes. | ||
| 877 | |||
| 878 | Example1: Downlink Payload: **09 00 00 **~/~/AT+TLSMOD=0,0 | ||
| 879 | |||
| 880 | Example2: Downlink Payload: **09 01 02 **~/~/AT+TLSMOD=1,2 | ||
| 881 | |||
| 882 | |||
| 883 | == 3.13 Set GNSS open time == | ||
| 884 | |||
| 885 | |||
| 886 | Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated. | ||
| 887 | |||
| 888 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GNSST** | ||
| 889 | |||
| 890 | Example: AT+GNSST=30 ~/~/ Set the GPS positioning time to 30 seconds | ||
| 891 | |||
| 892 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x10(%%)** | ||
| 893 | |||
| 894 | Format: Command Code (0x10) followed by 2 bytes. | ||
| 895 | |||
| 896 | Example: Downlink Payload: **10 00 1E **~/~/ AT+GNSST=30 | ||
| 897 | |||
| 898 | |||
| 899 | == 3.14 Turn on/off GPS == | ||
| 900 | |||
| 901 | |||
| 902 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GPS ** | ||
| 903 | |||
| 904 | **Ex1: **AT+GPS=0 ~/~/ Turn off GPS | ||
| 905 | |||
| 906 | **Ex2: **AT+GPS=1 ~/~/ Turn on GPS | ||
| 907 | |||
| 908 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x11(%%)** | ||
| 909 | |||
| 910 | Format: Command Code (0x11) followed by 1 byte. | ||
| 911 | |||
| 912 | Example: Downlink Payload: **11 01 **~/~/ AT+GPS=1 | ||
| 913 | |||
| 914 | |||
| 915 | == 3.15 Set GPS positioning interval == | ||
| 916 | |||
| 917 | |||
| 918 | Feature: Set GPS positioning interval (unit: hour). | ||
| 919 | |||
| 920 | When GPS is enabled, the node automatically locates and uplinks each time it passes **GTDC time** after activation. | ||
| 921 | |||
| 922 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GTDC** | ||
| 923 | |||
| 924 | Example: AT+GTDC=24 ~/~/ Set the GPS positioning interval to 24h. | ||
| 925 | |||
| 926 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x12(%%)** | ||
| 927 | |||
| 928 | Format: Command Code (0x12) followed by 3 bytes. | ||
| 929 | |||
| 930 | Example: 24 hours: 24(D)=0x18(H) | ||
| 931 | |||
| 932 | Downlink Payload: **12 00 00 18 **~/~/ AT+GTDC=24 | ||
| 933 | |||
| 934 | |||
| 935 | == 3.16 Set the search network time == | ||
| 936 | |||
| 937 | |||
| 938 | Feature: Get or Set the time to join the network(unit: minutes). | ||
| 939 | |||
| 940 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+CSQTIME** | ||
| 941 | |||
| 942 | Example: AT+CSQTIME=10 ~/~/ Set the search time to 10 minutes. | ||
| 943 | |||
| 944 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x13(%%)** | ||
| 945 | |||
| 946 | Format: Command Code (0x13) followed by 1 byte. | ||
| 947 | |||
| 948 | Example: Downlink Payload: **13 0A **~/~/ AT+CSQTIME=10 | ||
| 949 | |||
| 950 | |||
| 951 | == 3.17 Distance Alarm == | ||
| 952 | |||
| 953 | |||
| 954 | Feature: Set alarm of distance. | ||
| 955 | |||
| 956 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+ALARM**(%%)** ** (Range: 10cm~~4000cm) | ||
| 957 | |||
| 958 | Example: AT+ALARM=100,500 ~/~/ Set the alarm threshold | ||
| 959 | |||
| 960 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x0A(%%)** | ||
| 961 | |||
| 962 | Format: Command Code (0x0A) followed by 4 bytes. | ||
| 963 | |||
| 964 | Example: Downlink Payload: ** 0A 00 64 01 F4 **~/~/ AT+ALARM=100,500 | ||
| 965 | |||
| 966 | |||
| 967 | == 3.18 Set the IPv4 or IPv6 == | ||
| 968 | |||
| 969 | |||
| 970 | This command is used to set IP version. | ||
| 971 | |||
| 972 | (% style="color:blue" %)**AT command:** | ||
| 973 | |||
| 974 | * (% style="color:#037691; font-weight:bold" %)**AT+IPTYPE**(% style="color:#037691" %)**=1**(%%)** **~/~/ IPv4 | ||
| 975 | * (% style="color:#037691; font-weight:bold" %)**AT+IPTYPE**(% style="color:#037691" %)**=2**(%%)** **~/~/ IPv6 | ||
| 976 | |||
| 977 | == 3.19 Configure Network Category to be Searched for under LTE RAT. == | ||
| 978 | |||
| 979 | |||
| 980 | (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+IOTMOD=xx(%%)** | ||
| 981 | |||
| 982 | (% style="color:#037691" %)**xx:**(%%) **0:** eMTC | ||
| 983 | |||
| 984 | **1:** NB-IoT | ||
| 985 | |||
| 986 | **2:** eMTC and NB-IoT | ||
| 987 | |||
| 988 | |||
| 989 | == 3.20 Factory data reset == | ||
| 990 | |||
| 991 | |||
| 992 | Two different restore factory Settings configurations. | ||
| 993 | |||
| 994 | (% style="color:blue" %)**AT command:** | ||
| 995 | |||
| 996 | * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)** **~/~/ Reset Parameters to Factory Default. | ||
| 997 | * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)** **~/~/ Reset parameters to factory default values **except for passwords**. | ||
| 998 | |||
| 999 | == 3.21 Set CoAP option == | ||
| 1000 | |||
| 1001 | |||
| 1002 | Feature: Set CoAP option, follow this link to set up the CoaP protocol. | ||
| 1003 | |||
| 1004 | (% style="color:blue" %)**AT command: **(% style="color:#037691; font-weight:bold" %)**AT+URI1~~AT+URI8** | ||
| 1005 | |||
| 1006 | (% style="color:#037691; font-weight:bold" %)**AT+URI1=11,CoAP endpoint URl length,"CoAP endpoint URl" **(%%)~/~/ 11 is a fixed parameter. | ||
| 1007 | |||
| 1008 | Example: AT+URI1=11,38,"i/13a35fbe-9515-6e55-36e8-081fb6aacf86" | ||
| 1009 | |||
| 1010 | |||
| 1011 | == 3.22 Power on / power off BG95 module == | ||
| 1012 | |||
| 1013 | |||
| 1014 | This command is used to power on and power off BG95 module. | ||
| 1015 | |||
| 1016 | * (% style="color:blue" %)**AT command: **(% style="color:#037691" %)**AT+QSW** | ||
| 1017 | |||
| 1018 | The module is powered on after the command is sent for the first time, and powered off after the command is sent again. | ||
| 1019 | |||
| 1020 | [[image:image-20240722112048-11.png||height="730" width="849"]] | ||
| 1021 | |||
| 1022 | |||
| 1023 | == 3.23 Example Query saved historical records == | ||
| 1024 | |||
| 1025 | |||
| 1026 | * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CDP(%%)** | ||
| 1027 | |||
| 1028 | 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. | ||
| 1029 | |||
| 1030 | (% class="wikigeneratedid" %) | ||
| 1031 | [[image:image-20240722111743-9.png||height="714" width="842"]] | ||
| 1032 | |||
| 1033 | |||
| 1034 | == 3.24 Uplink log query == | ||
| 1035 | |||
| 1036 | |||
| 1037 | * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+GETLOG(%%)** | ||
| 1038 | |||
| 1039 | This command can be used to query upstream logs of data packets. | ||
| 1040 | |||
| 1041 | [[image:image-20240722111825-10.png||height="721" width="847"]] | ||
| 1042 | |||
| 1043 | |||
| 1044 | = 4. Battery & Power Consumption = | ||
| 1045 | |||
| 1046 | |||
| 1047 | LDS25-CB use ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. | ||
| 1048 | |||
| 1049 | [[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . | ||
| 1050 | |||
| 1051 | |||
| 1052 | = 5. Firmware update = | ||
| 1053 | |||
| 1054 | |||
| 1055 | User can change device firmware to:: | ||
| 1056 | |||
| 1057 | * Update with new features. | ||
| 1058 | |||
| 1059 | * Fix bugs. | ||
| 1060 | |||
| 1061 | Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/scl/fo/1mzflb9p9kx15btnc11gr/AO34owuuOSiRjP_LJCYziZ8/LDS40-CB?dl=0&rlkey=ku98jt8u30coqy66saebai2co&subfolder_nav_tracking=1]]** | ||
| 1062 | |||
| 1063 | Methods to Update Firmware: | ||
| 1064 | |||
| 1065 | * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]]. | ||
| 1066 | |||
| 1067 | * Update through UART TTL interface : **[[Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**. | ||
| 1068 | |||
| 1069 | = 6. FAQ = | ||
| 1070 | |||
| 1071 | == 6.1 How can I access the BG95-NGFF AT Commands? == | ||
| 1072 | |||
| 1073 | |||
| 1074 | User can access to BG95-NGFF directly and send AT Commands. | ||
| 1075 | |||
| 1076 | [[See BG95-NGFF AT Command set>>https://www.dropbox.com/scl/fo/1mzflb9p9kx15btnc11gr/ALDWTvDjuVoXvDJuYWCRh5U/Vendor%20Datasheet/BG95?dl=0&rlkey=ku98jt8u30coqy66saebai2co&subfolder_nav_tracking=1]] | ||
| 1077 | |||
| 1078 | |||
| 1079 | == 6.2 General Manual for -CB , -CS models == | ||
| 1080 | |||
| 1081 | |||
| 1082 | Users can follow the instructions in this [[link>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Manual%20for%20-CB%20%2C%20-CS%20models/]] to see how to configure to connect to different servers. | ||
| 1083 | |||
| 1084 | |||
| 1085 | = 7. Trouble Shooting = | ||
| 1086 | |||
| 1087 | == 7.1 Significant error between the output distant value of LiDAR and actual distance == | ||
| 1088 | |||
| 1089 | |||
| 1090 | ((( | ||
| 1091 | (% 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.) | ||
| 1092 | ))) | ||
| 1093 | |||
| 1094 | ((( | ||
| 1095 | (% style="color:red" %)**Troubleshooting**(%%): Please avoid use of this product under such circumstance in practice. | ||
| 1096 | ))) | ||
| 1097 | |||
| 1098 | |||
| 1099 | ((( | ||
| 1100 | (% style="color:blue" %)**Cause ②**(%%)**: **The IR-pass filters are blocked. | ||
| 1101 | ))) | ||
| 1102 | |||
| 1103 | ((( | ||
| 1104 | (% style="color:red" %)**Troubleshooting**(%%): please use dry dust-free cloth to gently remove the foreign matter. | ||
| 1105 | ))) | ||
| 1106 | |||
| 1107 | |||
| 1108 | = 8. Order Info = | ||
| 1109 | |||
| 1110 | |||
| 1111 | Part Number: (% style="color:blue" %)**LDS25-CB-XX** | ||
| 1112 | |||
| 1113 | (% style="color:red" %)**XX**(%%): | ||
| 1114 | |||
| 1115 | * (% style="color:#037691" %)**GE**(%%): General version ( Exclude SIM card) | ||
| 1116 | |||
| 1117 | * (% style="color:#037691" %)**1T**(%%) with 1NCE* 10 years 500MB SIM card and Pre-configure to ThingsEye server | ||
| 1118 | |||
| 1119 | = 9. Packing Info = | ||
| 1120 | |||
| 1121 | |||
| 1122 | (% style="color:#037691" %)**Package Includes**: | ||
| 1123 | |||
| 1124 | * LDS25-CB NB-IoT/LTE-M LiDAR ToF Distance sensor x 1 | ||
| 1125 | |||
| 1126 | * External antenna x 1 | ||
| 1127 | |||
| 1128 | (% style="color:#037691" %)**Dimension and weight**: | ||
| 1129 | |||
| 1130 | * Device Size: 13.0 x 5 x 4.5 cm | ||
| 1131 | |||
| 1132 | * Device Weight: 150g | ||
| 1133 | |||
| 1134 | * Package Size / pcs : 14.0 x 8x 5 cm | ||
| 1135 | |||
| 1136 | * Weight / pcs : 180g | ||
| 1137 | |||
| 1138 | = 10. Support = | ||
| 1139 | |||
| 1140 | |||
| 1141 | * 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. | ||
| 1142 | |||
| 1143 | * 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]]. | ||
| 1144 | |||
| 1145 | (% style="display:none" %) (%%) |