Wiki source code of LMDS200 - LoRaWAN Microwave Radar Distance Sensor User Manual
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | (% style="text-align:center" %) | ||
| 2 | [[image:image-20220615144725-2.jpeg]] | ||
| 3 | |||
| 4 | **Table of Contents:** | ||
| 5 | |||
| 6 | |||
| 7 | |||
| 8 | |||
| 9 | |||
| 10 | |||
| 11 | |||
| 12 | = 1. Introduction = | ||
| 13 | |||
| 14 | == 1.1 What is LMDS200 Microwave Radar DistanceSensor == | ||
| 15 | |||
| 16 | ((( | ||
| 17 | |||
| 18 | |||
| 19 | ((( | ||
| 20 | ((( | ||
| 21 | ((( | ||
| 22 | ((( | ||
| 23 | The Dragino LMDS200 is a (% style="color:#4472c4" %)**LoRaWAN Microwave Radar distance sensor**(%%). It uses (% style="color:#4472c4" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:#4472c4" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor. | ||
| 24 | ))) | ||
| 25 | |||
| 26 | ((( | ||
| 27 | |||
| 28 | ))) | ||
| 29 | |||
| 30 | ((( | ||
| 31 | The LMDS200 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 | |||
| 34 | ((( | ||
| 35 | |||
| 36 | ))) | ||
| 37 | |||
| 38 | ((( | ||
| 39 | LMDS200 can (% style="color:#4472c4" %)**measure two distances**(%%): the closest object and next object behind the closest one. | ||
| 40 | ))) | ||
| 41 | |||
| 42 | ((( | ||
| 43 | |||
| 44 | ))) | ||
| 45 | |||
| 46 | ((( | ||
| 47 | LMDS200 supports (% style="color:#4472c4" %)**Alarm Feature**(%%), user can set the LMDS200 to uplink data in a short interval when the distance is out of configured range. | ||
| 48 | ))) | ||
| 49 | |||
| 50 | ((( | ||
| 51 | |||
| 52 | ))) | ||
| 53 | |||
| 54 | ((( | ||
| 55 | The LoRa wireless technology used in LMDS200 allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. | ||
| 56 | ))) | ||
| 57 | |||
| 58 | ((( | ||
| 59 | |||
| 60 | ))) | ||
| 61 | |||
| 62 | ((( | ||
| 63 | LMDS200 is powered by 8500mAh Li-SOCI2 battery, it is designed for long term use up to 5 years. | ||
| 64 | ))) | ||
| 65 | |||
| 66 | ((( | ||
| 67 | |||
| 68 | ))) | ||
| 69 | |||
| 70 | ((( | ||
| 71 | Each LMDS200 is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect after power on. | ||
| 72 | ))) | ||
| 73 | |||
| 74 | ((( | ||
| 75 | |||
| 76 | ))) | ||
| 77 | |||
| 78 | ((( | ||
| 79 | *Battery life depends on how often to send data, please see [[battery analyzer>>||anchor="H4. Battery & how to replace"]]. | ||
| 80 | ))) | ||
| 81 | ))) | ||
| 82 | ))) | ||
| 83 | ))) | ||
| 84 | ))) | ||
| 85 | |||
| 86 | |||
| 87 | [[image:1655277036890-950.png]] | ||
| 88 | |||
| 89 | |||
| 90 | |||
| 91 | == 1.2 Features == | ||
| 92 | |||
| 93 | * LoRaWAN 1.0.3 Class A | ||
| 94 | * Ultra-low power consumption | ||
| 95 | * Microwave Radar for distance detection | ||
| 96 | * Short uplink interval for Distance Alarm | ||
| 97 | * Monitor Battery Level | ||
| 98 | * Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865 | ||
| 99 | * AT Commands to change parameters | ||
| 100 | * Uplink on periodically | ||
| 101 | * Downlink to change configure | ||
| 102 | * 8500mAh Battery for long term use | ||
| 103 | * Wall Mountable | ||
| 104 | * Outdoor Use | ||
| 105 | |||
| 106 | == 1.3 Radar probe specification == | ||
| 107 | |||
| 108 | * Measuring Method: FMCW | ||
| 109 | * Frequency: 24.000 ~~ 24.500 GHz | ||
| 110 | * Measurement output power: 6dBm | ||
| 111 | * Measure range: 0.5 ~~ 20m | ||
| 112 | * Accuracy: ±0.1m | ||
| 113 | * Resolution: 0.01m | ||
| 114 | * Horizontal Angel: 78° | ||
| 115 | * Vertical Angel: 23° | ||
| 116 | |||
| 117 | == 1.4 Storage & Operation Temperature == | ||
| 118 | |||
| 119 | -20°C to +85°C | ||
| 120 | |||
| 121 | |||
| 122 | |||
| 123 | == 1.5 Applications == | ||
| 124 | |||
| 125 | * Horizontal distance measurement | ||
| 126 | * Liquid level measurement | ||
| 127 | * Parking management system | ||
| 128 | * Object proximity and presence detection | ||
| 129 | * Intelligent trash can management system | ||
| 130 | * Robot obstacle avoidance | ||
| 131 | * Automatic control | ||
| 132 | * Sewer | ||
| 133 | * Bottom water level monitoring | ||
| 134 | |||
| 135 | == 1.6 Installation == | ||
| 136 | |||
| 137 | Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object. | ||
| 138 | |||
| 139 | [[image:image-20220615152454-3.png]] | ||
| 140 | |||
| 141 | |||
| 142 | [[image:image-20220615152454-4.png]] | ||
| 143 | |||
| 144 | |||
| 145 | |||
| 146 | |||
| 147 | == 1.7 Pin mapping and power on == | ||
| 148 | |||
| 149 | |||
| 150 | [[image:1655257026882-201.png]] | ||
| 151 | |||
| 152 | |||
| 153 | |||
| 154 | = 2. Operation Mode = | ||
| 155 | |||
| 156 | |||
| 157 | == 2.1 How it works == | ||
| 158 | |||
| 159 | ((( | ||
| 160 | Each LMDS200 is shipped with a worldwide unique set of OTAA keys. To use LMDS200 in a LoRaWAN network, user needs to input the OTAA keys in the LoRaWAN network server. So LMDS200 can join the LoRaWAN network and start to transmit sensor data. | ||
| 161 | ))) | ||
| 162 | |||
| 163 | |||
| 164 | |||
| 165 | == 2.2 Example to use for LoRaWAN network == | ||
| 166 | |||
| 167 | ((( | ||
| 168 | Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LG308>>url:http://www.dragino.com/products/lora/item/140-lg308.html]] as a LoRaWAN gateway in this example. | ||
| 169 | ))) | ||
| 170 | |||
| 171 | ((( | ||
| 172 | [[image:1655278047781-517.png]] | ||
| 173 | |||
| 174 | * In this user case, the LMDS200 is installed on top of river to detect the water level and send the level info to the LoRaWAN server. The LMDS200 will uplink different types of messages to the LoRaWAN server. See [[Uplink payload>>path:#Uplink_Payload]] for detail. | ||
| 175 | ))) | ||
| 176 | |||
| 177 | ((( | ||
| 178 | Assume the LoRaWAN Gateway DLOS8 is already set to connect to the [[TTN V3 network >>url:https://eu1.cloud.thethings.network]]. We need to add the LMDS200 device in TTN V3: | ||
| 179 | ))) | ||
| 180 | |||
| 181 | ((( | ||
| 182 | ((( | ||
| 183 | |||
| 184 | ))) | ||
| 185 | |||
| 186 | ((( | ||
| 187 | (% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LMDS200. | ||
| 188 | ))) | ||
| 189 | ))) | ||
| 190 | |||
| 191 | ((( | ||
| 192 | ((( | ||
| 193 | Each LMDS200 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below. | ||
| 194 | |||
| 195 | [[image:1655278302970-688.png]] | ||
| 196 | |||
| 197 | |||
| 198 | |||
| 199 | ))) | ||
| 200 | ))) | ||
| 201 | |||
| 202 | Users can enter these keys in the LoRaWAN Server portal. Below is the TTN V3 screenshot: | ||
| 203 | |||
| 204 | __**Add APP EUI**__ in the application. | ||
| 205 | |||
| 206 | |||
| 207 | [[image:image-20220610161353-4.png]] | ||
| 208 | |||
| 209 | [[image:image-20220610161353-5.png]] | ||
| 210 | |||
| 211 | [[image:image-20220610161353-6.png]] | ||
| 212 | |||
| 213 | |||
| 214 | [[image:image-20220610161353-7.png]] | ||
| 215 | |||
| 216 | |||
| 217 | |||
| 218 | You can also choose to create the device manually. | ||
| 219 | |||
| 220 | [[image:image-20220610161538-8.png]] | ||
| 221 | |||
| 222 | |||
| 223 | |||
| 224 | **Add APP KEY and DEV EUI** | ||
| 225 | |||
| 226 | [[image:1655278497961-944.png]] | ||
| 227 | |||
| 228 | |||
| 229 | |||
| 230 | (% style="color:blue" %)**Step 2**(%%): Power on LMDS200 | ||
| 231 | |||
| 232 | |||
| 233 | Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position). | ||
| 234 | |||
| 235 | [[image:1655278589727-228.png]] | ||
| 236 | |||
| 237 | Put the jumper to power on LMDS200 and it will auto-join to the TTN V3 network. After join success, it will start to upload sensor data to TTN V3 and the user can see it in the panel. | ||
| 238 | |||
| 239 | |||
| 240 | |||
| 241 | == 2.3 Uplink Payload == | ||
| 242 | |||
| 243 | Uplink payloads have two types: | ||
| 244 | |||
| 245 | * Distance Value: Use FPORT=2 | ||
| 246 | * Other control commands: Use other FPORT fields. | ||
| 247 | |||
| 248 | The application server should parse the correct value based on FPORT settings. | ||
| 249 | |||
| 250 | ((( | ||
| 251 | ((( | ||
| 252 | ((( | ||
| 253 | |||
| 254 | |||
| 255 | |||
| 256 | ))) | ||
| 257 | ))) | ||
| 258 | ))) | ||
| 259 | |||
| 260 | === 2.3.1 Device Status, FPORT~=5 === | ||
| 261 | |||
| 262 | Include device configure status. Once LMDS200 Joined the network, it will uplink this message to the server. | ||
| 263 | |||
| 264 | Users can also use the downlink command (0x26 01) to ask LMDS200 to resend Device Status. | ||
| 265 | |||
| 266 | [[image:image-20220615154327-2.png]] | ||
| 267 | |||
| 268 | |||
| 269 | [[image:image-20220615154022-1.png]](% style="display:none" %) | ||
| 270 | |||
| 271 | |||
| 272 | * (% style="color:#037691" %)**Sensor Model**(%%)**:** For LMDS200, this value is 0x0C | ||
| 273 | |||
| 274 | * (% style="color:#037691" %)**Firmware Version**(%%)**:** 0x0100, Means: v1.0.0 version | ||
| 275 | |||
| 276 | * (% style="color:#037691" %)**Frequency Band**(%%)**:** | ||
| 277 | |||
| 278 | *0x01: EU868 | ||
| 279 | |||
| 280 | *0x02: US915 | ||
| 281 | |||
| 282 | *0x03: IN865 | ||
| 283 | |||
| 284 | *0x04: AU915 | ||
| 285 | |||
| 286 | *0x05: KZ865 | ||
| 287 | |||
| 288 | *0x06: RU864 | ||
| 289 | |||
| 290 | *0x07: AS923 | ||
| 291 | |||
| 292 | *0x08: AS923-1 | ||
| 293 | |||
| 294 | *0x09: AS923-2 | ||
| 295 | |||
| 296 | *0x0a: AS923-3 | ||
| 297 | |||
| 298 | *0x0b: CN470 | ||
| 299 | |||
| 300 | *0x0c: EU433 | ||
| 301 | |||
| 302 | *0x0d: KR920 | ||
| 303 | |||
| 304 | *0x0e: MA869 | ||
| 305 | |||
| 306 | |||
| 307 | * (% style="color:#037691" %)**Sub-Band**(%%)**:** | ||
| 308 | ** AU915 and US915:value 0x00 ~~ 0x08 | ||
| 309 | ** CN470: value 0x0B ~~ 0x0C | ||
| 310 | ** Other Bands: Always 0x00 | ||
| 311 | |||
| 312 | * (% style="color:#037691" %)**Battery Info:** | ||
| 313 | |||
| 314 | Check the battery voltage. | ||
| 315 | |||
| 316 | Ex1: 0x0B45 = 2885mV | ||
| 317 | |||
| 318 | Ex2: 0x0B49 = 2889mV | ||
| 319 | |||
| 320 | |||
| 321 | |||
| 322 | === 2.3.2 Sensor Configuration, FPORT~=4 === | ||
| 323 | |||
| 324 | ((( | ||
| 325 | LMDS200 will only send this command after getting the downlink command (0x26 02) from the server. | ||
| 326 | |||
| 327 | (% border="1" cellspacing="10" style="background-color:#ffffcc; width:494px" %) | ||
| 328 | |(% colspan="5" style="width:491px" %)**Sensor Configuration FPORT=4** | ||
| 329 | |**Size (bytes)**|(% style="width:84px" %)**3**|(% style="width:73px" %)**1**|(% style="width:117px" %)**4**|(% style="width:136px" %)**1** | ||
| 330 | |**Value**|(% style="width:84px" %)((( | ||
| 331 | [[TDC (unit:sec)>>||anchor="H"]] | ||
| 332 | )))|(% style="width:73px" %)((( | ||
| 333 | [[ATDC (unit:min)>>||anchor="H"]] | ||
| 334 | )))|(% style="width:117px" %)[[Alarm Settings>>||anchor="H"]]|(% style="width:136px" %)[[Interrupt Settings>>||anchor="H"]] | ||
| 335 | ))) | ||
| 336 | |||
| 337 | [[image:1655279779620-413.png]] | ||
| 338 | |||
| 339 | |||
| 340 | === 2.3.3 Distance, Uplink FPORT~=2 === | ||
| 341 | |||
| 342 | LMDS200 will send this uplink **after** Device Status once join the LoRaWAN network successfully. And LMDS200 will: | ||
| 343 | |||
| 344 | 1. | ||
| 345 | 11. periodically send this uplink every 1 hour (TDC time), this interval [[can be changed>>path:#Uplink_Interval]]. | ||
| 346 | 11. periodically send this uplink every 1 minute in Alarm Mode. | ||
| 347 | 11. send this uplink while there is [[interrupt event>>path:#Int_mod]]. | ||
| 348 | |||
| 349 | |||
| 350 | Uplink Payload totals 11 bytes. | ||
| 351 | |||
| 352 | |||
| 353 | |(% colspan="5" %)**Distance Value, FPORT=2** | ||
| 354 | |**Size (bytes)**|**2**|**2**|**2**|**1** | ||
| 355 | |**Value**|[[BAT>>path:#bat]]|Object1 Distance|Object2 Distance|Status & [[Alarm>>path:#Alarm_Timeout]] | ||
| 356 | |||
| 357 | |||
| 358 | |||
| 359 | |||
| 360 | |||
| 361 | |||
| 362 | |(% colspan="4" %)**Status & Alarm field** | ||
| 363 | |**Size (bit)**|**6**|**1**|**1** | ||
| 364 | |**Value**|DALARM Counter|((( | ||
| 365 | Distance Alarm | ||
| 366 | 0: Normal Value | ||
| 367 | |||
| 368 | 1: Distance Alarm | ||
| 369 | )))|((( | ||
| 370 | Interrupt Alarm | ||
| 371 | 0: No Alarm | ||
| 372 | |||
| 373 | 1: external Interrupt Alarm | ||
| 374 | ))) | ||
| 375 | |||
| 376 | |||
| 377 | |||
| 378 | |||
| 379 | |||
| 380 | |||
| 381 | |||
| 382 | |||
| 383 | [[image:image-20220615160828-3.png]] | ||
| 384 | |||
| 385 | **Object1 Distance:** | ||
| 386 | |||
| 387 | Distance between sensor probe to the first object. (unit: cm) | ||
| 388 | |||
| 389 | For example, if the data you get from the register is 0x00 0x73, the distance between the sensor and the measured object is | ||
| 390 | |||
| 391 | **0073(H) = 115 (D) = 115 cm.** | ||
| 392 | |||
| 393 | Notice: There are two special values for object 1 distance: | ||
| 394 | |||
| 395 | * **0x0001**: Probe not detected | ||
| 396 | * **0x0002**: Reading Invalid (exceed the valid range of the probe) | ||
| 397 | |||
| 398 | |||
| 399 | **Object2 Distance:** | ||
| 400 | |||
| 401 | Distance between sensor probe to the second object. (unit: cm) | ||
| 402 | |||
| 403 | DALARM Counter : Alarm Counter. | ||
| 404 | |||
| 405 | [[image:image-20220615160828-4.png]] | ||
| 406 | |||
| 407 | |||
| 408 | |||
| 409 | === 2.3.4 DS18B20 Temperature sensor === | ||
| 410 | |||
| 411 | This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature. | ||
| 412 | |||
| 413 | **Example**: | ||
| 414 | |||
| 415 | If payload is: 0105H: (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree | ||
| 416 | |||
| 417 | If payload is: FF3FH : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. | ||
| 418 | |||
| 419 | (% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021. | ||
| 420 | |||
| 421 | |||
| 422 | |||
| 423 | === 2.3.5 Sensor Flag === | ||
| 424 | |||
| 425 | ((( | ||
| 426 | 0x01: Detect Ultrasonic Sensor | ||
| 427 | ))) | ||
| 428 | |||
| 429 | ((( | ||
| 430 | 0x00: No Ultrasonic Sensor | ||
| 431 | ))) | ||
| 432 | |||
| 433 | |||
| 434 | |||
| 435 | === 2.3.6 Decode payload in The Things Network === | ||
| 436 | |||
| 437 | While using TTN network, you can add the payload format to decode the payload. | ||
| 438 | |||
| 439 | |||
| 440 | [[image:1655261164557-670.png]] | ||
| 441 | |||
| 442 | ((( | ||
| 443 | The payload decoder function for TTN V3 is here: | ||
| 444 | ))) | ||
| 445 | |||
| 446 | ((( | ||
| 447 | ((( | ||
| 448 | LDDS20 TTN V3 Payload Decoder: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LDDS20/Payload_Decoder/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Payload_Decoder/]] | ||
| 449 | ))) | ||
| 450 | ))) | ||
| 451 | |||
| 452 | |||
| 453 | |||
| 454 | == 2.4 Downlink Payload == | ||
| 455 | |||
| 456 | By default, LDDS20 prints the downlink payload to console port. | ||
| 457 | |||
| 458 | [[image:image-20220615100930-15.png]] | ||
| 459 | |||
| 460 | |||
| 461 | **Examples:** | ||
| 462 | |||
| 463 | |||
| 464 | * (% style="color:blue" %)**Set TDC** | ||
| 465 | |||
| 466 | If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. | ||
| 467 | |||
| 468 | Payload: 01 00 00 1E TDC=30S | ||
| 469 | |||
| 470 | Payload: 01 00 00 3C TDC=60S | ||
| 471 | |||
| 472 | |||
| 473 | * (% style="color:blue" %)**Reset** | ||
| 474 | |||
| 475 | If payload = 0x04FF, it will reset the LDDS20 | ||
| 476 | |||
| 477 | |||
| 478 | * (% style="color:blue" %)**CFM** | ||
| 479 | |||
| 480 | Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0 | ||
| 481 | |||
| 482 | |||
| 483 | |||
| 484 | == 2.5 Show Data in DataCake IoT Server == | ||
| 485 | |||
| 486 | ((( | ||
| 487 | [[DATACAKE>>url:https://datacake.co/]] provides a human friendly interface to show the sensor data, once we have data in TTN, we can use [[DATACAKE>>url:https://datacake.co/]] to connect to TTN and see the data in DATACAKE. Below are the steps: | ||
| 488 | ))) | ||
| 489 | |||
| 490 | ((( | ||
| 491 | |||
| 492 | ))) | ||
| 493 | |||
| 494 | ((( | ||
| 495 | (% style="color:blue" %)**Step 1**(%%)**: Be sure that your device is programmed and properly connected to the network at this time.** | ||
| 496 | ))) | ||
| 497 | |||
| 498 | ((( | ||
| 499 | (% style="color:blue" %)**Step 2**(%%)**: To configure the Application to forward data to DATACAKE you will need to add integration. To add the DATACAKE integration, perform the following steps:** | ||
| 500 | ))) | ||
| 501 | |||
| 502 | |||
| 503 | [[image:1654592790040-760.png]] | ||
| 504 | |||
| 505 | |||
| 506 | [[image:1654592800389-571.png]] | ||
| 507 | |||
| 508 | |||
| 509 | (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.** | ||
| 510 | |||
| 511 | (% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.(% style="color:red" %)(Note: LDDS20 use same payload as LDDS75)(%%)** | ||
| 512 | |||
| 513 | [[image:1654851029373-510.png]] | ||
| 514 | |||
| 515 | |||
| 516 | After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake. | ||
| 517 | |||
| 518 | [[image:image-20220610165129-11.png||height="595" width="1088"]] | ||
| 519 | |||
| 520 | |||
| 521 | == 2.6 LED Indicator == | ||
| 522 | |||
| 523 | The LDDS20 has an internal LED which is to show the status of different state. | ||
| 524 | |||
| 525 | |||
| 526 | * Blink once when device power on. | ||
| 527 | * The device detects the sensor and flashes 5 times. | ||
| 528 | * Solid ON for 5 seconds once device successful Join the network. | ||
| 529 | * Blink once when device transmit a packet. | ||
| 530 | |||
| 531 | == 2.7 Firmware Change Log == | ||
| 532 | |||
| 533 | |||
| 534 | ((( | ||
| 535 | **Firmware download link: **[[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/]] | ||
| 536 | ))) | ||
| 537 | |||
| 538 | ((( | ||
| 539 | |||
| 540 | ))) | ||
| 541 | |||
| 542 | ((( | ||
| 543 | **Firmware Upgrade Method: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]** | ||
| 544 | ))) | ||
| 545 | |||
| 546 | |||
| 547 | |||
| 548 | == 2.8 Battery Analysis == | ||
| 549 | |||
| 550 | |||
| 551 | === 2.8.1 Battery Type === | ||
| 552 | |||
| 553 | ((( | ||
| 554 | The LDDS20 battery is a combination of a 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. | ||
| 555 | ))) | ||
| 556 | |||
| 557 | ((( | ||
| 558 | |||
| 559 | ))) | ||
| 560 | |||
| 561 | ((( | ||
| 562 | The battery related documents as below: | ||
| 563 | ))) | ||
| 564 | |||
| 565 | * ((( | ||
| 566 | ((( | ||
| 567 | [[Battery Dimension>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]], | ||
| 568 | ))) | ||
| 569 | ))) | ||
| 570 | * ((( | ||
| 571 | ((( | ||
| 572 | [[Lithium-Thionyl Chloride Battery datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]], | ||
| 573 | ))) | ||
| 574 | ))) | ||
| 575 | * ((( | ||
| 576 | ((( | ||
| 577 | [[Lithium-ion Battery-Capacitor datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] | ||
| 578 | ))) | ||
| 579 | ))) | ||
| 580 | |||
| 581 | [[image:image-20220615111024-1.png]] | ||
| 582 | |||
| 583 | |||
| 584 | |||
| 585 | === 2.8.2 Battery Note === | ||
| 586 | |||
| 587 | The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to uplink data, then the battery life may be decreased. | ||
| 588 | |||
| 589 | |||
| 590 | |||
| 591 | === 2.8.3 Replace the battery === | ||
| 592 | |||
| 593 | ((( | ||
| 594 | ((( | ||
| 595 | You can change the battery in the NBSN95.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won’t be voltage drop between battery and main board. | ||
| 596 | ))) | ||
| 597 | |||
| 598 | ((( | ||
| 599 | |||
| 600 | ))) | ||
| 601 | |||
| 602 | ((( | ||
| 603 | The default battery pack of NBSN95 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes) | ||
| 604 | ))) | ||
| 605 | ))) | ||
| 606 | |||
| 607 | |||
| 608 | |||
| 609 | === 2.8.4 Battery Life Analyze === | ||
| 610 | |||
| 611 | ((( | ||
| 612 | Dragino battery powered products are all run in Low Power mode. User can check the guideline from this link to calculate the estimate battery life: | ||
| 613 | ))) | ||
| 614 | |||
| 615 | ((( | ||
| 616 | [[https:~~/~~/www.dragino.com/downloads/downloads/LoRa_End_Node/Battery_Analyze/DRAGINO_Battery_Life_Guide.pdf>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/Battery_Analyze/DRAGINO_Battery_Life_Guide.pdf]] | ||
| 617 | ))) | ||
| 618 | |||
| 619 | |||
| 620 | |||
| 621 | = 3. Using the AT Commands = | ||
| 622 | |||
| 623 | ((( | ||
| 624 | ((( | ||
| 625 | |||
| 626 | ))) | ||
| 627 | ))) | ||
| 628 | |||
| 629 | == 3.1 Access AT Commands == | ||
| 630 | |||
| 631 | LDDS20 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LDDS20 for using AT command, as below. | ||
| 632 | |||
| 633 | |||
| 634 | [[image:image-20220610172924-4.png||height="483" width="988"]] | ||
| 635 | |||
| 636 | |||
| 637 | Or if you have below board, use below connection: | ||
| 638 | |||
| 639 | |||
| 640 | [[image:image-20220610172924-5.png]] | ||
| 641 | |||
| 642 | |||
| 643 | ((( | ||
| 644 | In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LDDS20. LDDS20 will output system info once power on as below: | ||
| 645 | ))) | ||
| 646 | |||
| 647 | |||
| 648 | [[image:image-20220610172924-6.png||height="601" width="860"]] | ||
| 649 | |||
| 650 | Below are the available commands, a more detailed AT Command manual can be found at [[AT Command Manual>>https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/]]. | ||
| 651 | |||
| 652 | |||
| 653 | AT+<CMD>? : Help on <CMD> | ||
| 654 | |||
| 655 | AT+<CMD> : Run <CMD> | ||
| 656 | |||
| 657 | AT+<CMD>=<value> : Set the value | ||
| 658 | |||
| 659 | AT+<CMD>=? : Get the value | ||
| 660 | |||
| 661 | |||
| 662 | (% style="color:#037691" %)** General Commands :** | ||
| 663 | |||
| 664 | AT : Attention | ||
| 665 | |||
| 666 | AT? : Short Help | ||
| 667 | |||
| 668 | ATZ : MCU Reset | ||
| 669 | |||
| 670 | AT+TDC : Application Data Transmission Interval | ||
| 671 | |||
| 672 | |||
| 673 | (% style="color:#037691" %)** Keys, IDs and EUIs management :** | ||
| 674 | |||
| 675 | AT+APPEUI : Application EUI | ||
| 676 | |||
| 677 | AT+APPKEY : Application Key | ||
| 678 | |||
| 679 | AT+APPSKEY : Application Session Key | ||
| 680 | |||
| 681 | AT+DADDR : Device Address | ||
| 682 | |||
| 683 | AT+DEUI : Device EUI | ||
| 684 | |||
| 685 | AT+NWKID : Network ID (You can enter this command change only after successful network connection) | ||
| 686 | |||
| 687 | AT+NWKSKEY : Network Session Key Joining and sending date on LoRa network | ||
| 688 | |||
| 689 | AT+CFM : Confirm Mode | ||
| 690 | |||
| 691 | AT+CFS : Confirm Status | ||
| 692 | |||
| 693 | AT+JOIN : Join LoRa? Network | ||
| 694 | |||
| 695 | AT+NJM : LoRa? Network Join Mode | ||
| 696 | |||
| 697 | AT+NJS : LoRa? Network Join Status | ||
| 698 | |||
| 699 | AT+RECV : Print Last Received Data in Raw Format | ||
| 700 | |||
| 701 | AT+RECVB : Print Last Received Data in Binary Format | ||
| 702 | |||
| 703 | AT+SEND : Send Text Data | ||
| 704 | |||
| 705 | AT+SENB : Send Hexadecimal Data | ||
| 706 | |||
| 707 | |||
| 708 | (% style="color:#037691" %)** LoRa Network Management :** | ||
| 709 | |||
| 710 | AT+ADR : Adaptive Rate | ||
| 711 | |||
| 712 | AT+CLASS : LoRa Class(Currently only support class A | ||
| 713 | |||
| 714 | AT+DCS : Duty Cycle Setting | ||
| 715 | |||
| 716 | AT+DR : Data Rate (Can Only be Modified after ADR=0) | ||
| 717 | |||
| 718 | AT+FCD : Frame Counter Downlink | ||
| 719 | |||
| 720 | AT+FCU : Frame Counter Uplink | ||
| 721 | |||
| 722 | AT+JN1DL : Join Accept Delay1 | ||
| 723 | |||
| 724 | AT+JN2DL : Join Accept Delay2 | ||
| 725 | |||
| 726 | AT+PNM : Public Network Mode | ||
| 727 | |||
| 728 | AT+RX1DL : Receive Delay1 | ||
| 729 | |||
| 730 | AT+RX2DL : Receive Delay2 | ||
| 731 | |||
| 732 | AT+RX2DR : Rx2 Window Data Rate | ||
| 733 | |||
| 734 | AT+RX2FQ : Rx2 Window Frequency | ||
| 735 | |||
| 736 | AT+TXP : Transmit Power | ||
| 737 | |||
| 738 | |||
| 739 | (% style="color:#037691" %)** Information :** | ||
| 740 | |||
| 741 | AT+RSSI : RSSI of the Last Received Packet | ||
| 742 | |||
| 743 | AT+SNR : SNR of the Last Received Packet | ||
| 744 | |||
| 745 | AT+VER : Image Version and Frequency Band | ||
| 746 | |||
| 747 | AT+FDR : Factory Data Reset | ||
| 748 | |||
| 749 | AT+PORT : Application Port | ||
| 750 | |||
| 751 | AT+CHS : Get or Set Frequency (Unit: Hz) for Single Channel Mode | ||
| 752 | |||
| 753 | AT+CHE : Get or Set eight channels mode, Only for US915, AU915, CN470 | ||
| 754 | |||
| 755 | |||
| 756 | |||
| 757 | == 3.2 Set Interrupt Mode == | ||
| 758 | |||
| 759 | Feature, Set Interrupt mode for GPIO_EXIT. | ||
| 760 | |||
| 761 | (% style="color:#037691" %)**Downlink Command: AT+INTMOD** | ||
| 762 | |||
| 763 | [[image:image-20220610174917-9.png]] | ||
| 764 | |||
| 765 | |||
| 766 | ((( | ||
| 767 | (% style="color:#037691" %)**Downlink Command: 0x06** | ||
| 768 | ))) | ||
| 769 | |||
| 770 | ((( | ||
| 771 | Format: Command Code (0x06) followed by 3 bytes. | ||
| 772 | ))) | ||
| 773 | |||
| 774 | ((( | ||
| 775 | ((( | ||
| 776 | This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06. | ||
| 777 | ))) | ||
| 778 | ))) | ||
| 779 | |||
| 780 | * ((( | ||
| 781 | Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode | ||
| 782 | ))) | ||
| 783 | * ((( | ||
| 784 | Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger | ||
| 785 | ))) | ||
| 786 | |||
| 787 | ((( | ||
| 788 | |||
| 789 | ))) | ||
| 790 | |||
| 791 | ((( | ||
| 792 | |||
| 793 | ))) | ||
| 794 | |||
| 795 | = 4. FAQ = | ||
| 796 | |||
| 797 | == 4.1 What is the frequency plan for LDDS20? == | ||
| 798 | |||
| 799 | LDDS20 use the same frequency as other Dragino products. User can see the detail from this link: [[Introduction>>doc:Main.End Device Frequency Band.WebHome||anchor="H1.Introduction"]] | ||
| 800 | |||
| 801 | |||
| 802 | |||
| 803 | == 4.2 How to change the LoRa Frequency Bands/Region == | ||
| 804 | |||
| 805 | You can follow the instructions for [[how to upgrade image>>||anchor="H2.7A0200BFirmwareChangeLog"]]. | ||
| 806 | When downloading the images, choose the required image file for download. | ||
| 807 | |||
| 808 | |||
| 809 | |||
| 810 | = 5. Trouble Shooting = | ||
| 811 | |||
| 812 | == 5.1 Why I can't join TTN V3 in US915 / AU915 bands? == | ||
| 813 | |||
| 814 | It is due to channel mapping. Please see below link: [[Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]] | ||
| 815 | |||
| 816 | |||
| 817 | == 5.2 AT Command input doesn't work == | ||
| 818 | |||
| 819 | In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string. | ||
| 820 | |||
| 821 | ((( | ||
| 822 | |||
| 823 | ))) | ||
| 824 | |||
| 825 | |||
| 826 | = 6. Order Info = | ||
| 827 | |||
| 828 | |||
| 829 | Part Number **:** (% style="color:blue" %)**LDDS20-XX** | ||
| 830 | |||
| 831 | |||
| 832 | (% style="color:blue" %)**XX**(%%)**: **The default frequency band | ||
| 833 | |||
| 834 | * (% style="color:red" %)**AS923 **(%%)**:** LoRaWAN AS923 band | ||
| 835 | * (% style="color:red" %)**AU915 **(%%)**:** LoRaWAN AU915 band | ||
| 836 | * (% style="color:red" %)**EU433 **(%%)**:** LoRaWAN EU433 band | ||
| 837 | * (% style="color:red" %)**EU868 **(%%)**:** LoRaWAN EU868 band | ||
| 838 | * (% style="color:red" %)**KR920 **(%%)**:** LoRaWAN KR920 band | ||
| 839 | * (% style="color:red" %)**US915 **(%%)**:** LoRaWAN US915 band | ||
| 840 | * (% style="color:red" %)**IN865 **(%%)**:** LoRaWAN IN865 band | ||
| 841 | * (% style="color:red" %)**CN470 **(%%)**:** LoRaWAN CN470 band | ||
| 842 | |||
| 843 | = 7. Packing Info = | ||
| 844 | |||
| 845 | |||
| 846 | ((( | ||
| 847 | **Package Includes**: | ||
| 848 | ))) | ||
| 849 | |||
| 850 | * ((( | ||
| 851 | LDDS20 LoRaWAN Liquid Level Sensor x 1 | ||
| 852 | ))) | ||
| 853 | |||
| 854 | ((( | ||
| 855 | (% style="color:red" %)**Note:** | ||
| 856 | ))) | ||
| 857 | |||
| 858 | ((( | ||
| 859 | ((( | ||
| 860 | (% style="color:red" %)**Ultrasonic coupling paste**(%%) and(% style="color:red" %)** Eproxy AB glue**(%%) are subjected in most shipping way. So the default package doesn't include it and user needs to purchase locally. | ||
| 861 | ))) | ||
| 862 | ))) | ||
| 863 | |||
| 864 | ((( | ||
| 865 | |||
| 866 | ))) | ||
| 867 | |||
| 868 | ((( | ||
| 869 | **Dimension and weight**: | ||
| 870 | ))) | ||
| 871 | |||
| 872 | * ((( | ||
| 873 | Device Size: cm | ||
| 874 | ))) | ||
| 875 | * ((( | ||
| 876 | Device Weight: g | ||
| 877 | ))) | ||
| 878 | * ((( | ||
| 879 | Package Size / pcs : cm | ||
| 880 | ))) | ||
| 881 | * ((( | ||
| 882 | Weight / pcs : g | ||
| 883 | |||
| 884 | |||
| 885 | |||
| 886 | ))) | ||
| 887 | |||
| 888 | = 8. Support = | ||
| 889 | |||
| 890 | * 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. | ||
| 891 | * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]. |