Wiki source code of NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | (% style="text-align:center" %) | ||
| 2 | [[image:LMDS200_10.jpg]] | ||
| 3 | |||
| 4 | |||
| 5 | **Table of Contents：** | ||
| 6 | |||
| 7 | |||
| 8 | |||
| 9 | |||
| 10 | |||
| 11 | = 1. Introduction = | ||
| 12 | |||
| 13 | == 1.1 What is NMDS200 NB-IoT Microwave Radar Distance Sensor == | ||
| 14 | |||
| 15 | |||
| 16 | ((( | ||
| 17 | The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor. | ||
| 18 | |||
| 19 | |||
| 20 | The NMDS200 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. | ||
| 21 | |||
| 22 | NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one. | ||
| 23 | |||
| 24 | NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range. | ||
| 25 | |||
| 26 | NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technology**(%%) developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage. | ||
| 27 | |||
| 28 | NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements. | ||
| 29 | |||
| 30 | NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) | ||
| 31 | |||
| 32 | To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection. | ||
| 33 | ))) | ||
| 34 | |||
| 35 | |||
| 36 | |||
| 37 | == 1.2 Features == | ||
| 38 | |||
| 39 | |||
| 40 | * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD | ||
| 41 | * Short uplink interval for Distance Alarm | ||
| 42 | * Monitor Battery Level | ||
| 43 | * Microwave Radar for distance detection | ||
| 44 | * Datalog feature | ||
| 45 | * Uplink periodically | ||
| 46 | * Downlink to change configure | ||
| 47 | * Wall Mountable | ||
| 48 | * Outdoor Use | ||
| 49 | * Ultra-Low Power consumption | ||
| 50 | * AT Commands to change parameters | ||
| 51 | * Micro SIM card slot for NB-IoT SIM | ||
| 52 | * 8500mAh Battery for long-term use | ||
| 53 | |||
| 54 | |||
| 55 | == 1.3 Radar probe specification == | ||
| 56 | |||
| 57 | |||
| 58 | * Measuring Method: FMCW | ||
| 59 | * Frequency: 24.000 24.500 GHz | ||
| 60 | * Measurement output power: 6dBm | ||
| 61 | * Measure range: 0.5 20m | ||
| 62 | * Accuracy: ±0.1m | ||
| 63 | * Resolution: 0.01m | ||
| 64 | * Horizontal Angel: 78° | ||
| 65 | * Vertical Angel: 23° | ||
| 66 | |||
| 67 | |||
| 68 | |||
| 69 | == 1.4 Storage Temperature == | ||
| 70 | |||
| 71 | |||
| 72 | -40°C to +85°C | ||
| 73 | |||
| 74 | |||
| 75 | |||
| 76 | |||
| 77 | |||
| 78 | == 1.5 Applications == | ||
| 79 | |||
| 80 | |||
| 81 | |||
| 82 | * Horizontal distance measurement | ||
| 83 | * Liquid level measurement | ||
| 84 | * Parking management system | ||
| 85 | * Object proximity and presence detection | ||
| 86 | * Intelligent trash can management system | ||
| 87 | * Robot obstacle avoidance | ||
| 88 | * Automatic control | ||
| 89 | * Sewer | ||
| 90 | * Bottom water level monitoring | ||
| 91 | |||
| 92 | |||
| 93 | == 1.6 Specification == | ||
| 94 | |||
| 95 | |||
| 96 | (% style="color:blue" %)**Common DC Characteristics:** | ||
| 97 | |||
| 98 | * Supply Voltage: 2.1v ~~ 3.6v | ||
| 99 | * Operating Temperature: 0 ~~ 70°C | ||
| 100 | |||
| 101 | (% style="color:blue" %)**NB-IoT Spec:** | ||
| 102 | |||
| 103 | * B1 @H-FDD: 2100MHz | ||
| 104 | * B3 @H-FDD: 1800MHz | ||
| 105 | * B8 @H-FDD: 900MHz | ||
| 106 | * B5 @H-FDD: 850MHz | ||
| 107 | * B20 @H-FDD: 800MHz | ||
| 108 | * B28 @H-FDD: 700MHz | ||
| 109 | |||
| 110 | |||
| 111 | == 1.7 Installation == | ||
| 112 | |||
| 113 | |||
| 114 | Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object. | ||
| 115 | |||
| 116 | |||
| 117 | [[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]] | ||
| 118 | |||
| 119 | |||
| 120 | |||
| 121 | == 1.8 Pin Definitions and Switch == | ||
| 122 | |||
| 123 | |||
| 124 | [[image:1670404362039-351.png]] | ||
| 125 | |||
| 126 | |||
| 127 | = 2. Use NMDS200 to communicate with IoT Server = | ||
| 128 | |||
| 129 | == 2.1 How it works == | ||
| 130 | |||
| 131 | |||
| 132 | The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200. | ||
| 133 | |||
| 134 | The diagram below shows the working flow in the default firmware of NMDS200: | ||
| 135 | |||
| 136 | [[image:image-20221021110615-5.png]] | ||
| 137 | |||
| 138 | |||
| 139 | == 2.2 Configure NMDS200 == | ||
| 140 | |||
| 141 | |||
| 142 | To use NMDS200 in your city, make sure to meet below requirements: | ||
| 143 | |||
| 144 | * Your local operator has already distributed an NB-IoT Network. | ||
| 145 | * The local NB-IoT network used the band that NMDS200 supports. | ||
| 146 | * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. | ||
| 147 | |||
| 148 | Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NMDS200 will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server. | ||
| 149 | |||
| 150 | [[image:image-20221207173300-4.png]] | ||
| 151 | |||
| 152 | |||
| 153 | === 2.2.1 Insert NB-IoT SIM card === | ||
| 154 | |||
| 155 | |||
| 156 | Insert the NB-IoT Card get from your provider. | ||
| 157 | |||
| 158 | User needs to take out the NB-IoT module and insert the SIM card like below: | ||
| 159 | |||
| 160 | [[image:image-20221021110745-6.png]] | ||
| 161 | |||
| 162 | |||
| 163 | === 2.2.2 Connect USB – TTL to NMDS200 and configure it === | ||
| 164 | |||
| 165 | |||
| 166 | User need to configure NMDS200 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NMDS200 support AT Commands, user can use a USB to TTL adapter to connect to NMDS200 and use AT Commands to configure it, as below. | ||
| 167 | |||
| 168 | (% style="color:blue" %)**Connection:** | ||
| 169 | |||
| 170 | (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND** | ||
| 171 | |||
| 172 | (% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD** | ||
| 173 | |||
| 174 | (% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD** | ||
| 175 | |||
| 176 | |||
| 177 | In the PC, use below serial tool settings: | ||
| 178 | |||
| 179 | * Baud: (% style="color:red" %)**9600** | ||
| 180 | |||
| 181 | * Data bits:** (% style="color:red" %)8(%%)** | ||
| 182 | |||
| 183 | * Stop bits: (% style="color:red" %)**1** | ||
| 184 | |||
| 185 | * Parity: (% style="color:red" %)**None** | ||
| 186 | |||
| 187 | * Flow Control: (% style="color:red" %)**None** | ||
| 188 | |||
| 189 | Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%). | ||
| 190 | |||
| 191 | [[image:image-20221021110817-7.png]] | ||
| 192 | |||
| 193 | NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input. | ||
| 194 | |||
| 195 | |||
| 196 | (% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]] | ||
| 197 | |||
| 198 | |||
| 199 | |||
| 200 | === 2.2.3 Use CoAP protocol to uplink data === | ||
| 201 | |||
| 202 | |||
| 203 | (% style="color:red" %)**Note: if you don't have a CoAP server, you can refer this link to set up a CoAP server: **(%%)[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] | ||
| 204 | |||
| 205 | |||
| 206 | (% style="color:blue" %)**Use below commands in NDS03A:** | ||
| 207 | |||
| 208 | * (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink | ||
| 209 | |||
| 210 | * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ Set CoAP server address and port | ||
| 211 | |||
| 212 | * (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/ Set CoAP resource path | ||
| 213 | |||
| 214 | For parameter description, please refer to AT command set | ||
| 215 | |||
| 216 | [[image:image-20221021110948-8.png]] | ||
| 217 | |||
| 218 | |||
| 219 | After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server. | ||
| 220 | |||
| 221 | [[image:1670405841875-916.png]] | ||
| 222 | |||
| 223 | |||
| 224 | === 2.2.4 Use UDP protocol to uplink data(Default protocol) === | ||
| 225 | |||
| 226 | |||
| 227 | (% style="color:blue" %)**AT Commands:** | ||
| 228 | |||
| 229 | * (% style="color:#037691" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink | ||
| 230 | |||
| 231 | * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ Set UDP server address and port | ||
| 232 | |||
| 233 | * (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary | ||
| 234 | |||
| 235 | [[image:image-20221021111025-10.png]] | ||
| 236 | |||
| 237 | |||
| 238 | [[image:image-20221021111033-11.png||height="241" width="576"]] | ||
| 239 | |||
| 240 | | ||
| 241 | |||
| 242 | === 2.2.5 Use MQTT protocol to uplink data === | ||
| 243 | |||
| 244 | |||
| 245 | (% style="color:blue" %)**AT Commands:** | ||
| 246 | |||
| 247 | * (% style="color:#037691" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink | ||
| 248 | |||
| 249 | * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port | ||
| 250 | |||
| 251 | * (% style="color:#037691" %)**AT+CLIENT=CLIENT ** (%%) ~/~/ Set up the CLIENT of MQTT | ||
| 252 | |||
| 253 | * (% style="color:#037691" %)**AT+UNAME=UNAME **(%%)** **~/~/ Set the username of MQTT | ||
| 254 | |||
| 255 | * (% style="color:#037691" %)**AT+PWD=PWD **(%%)** **~/~/ Set the password of MQTT | ||
| 256 | |||
| 257 | * (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB **(%%)** **~/~/ Set the sending topic of MQTT | ||
| 258 | |||
| 259 | * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB ** (%%) ~/~/ Set the subscription topic of MQTT | ||
| 260 | |||
| 261 | [[image:image-20221118103445-7.png]] | ||
| 262 | |||
| 263 | |||
| 264 | [[image:1670405928926-116.png]] | ||
| 265 | |||
| 266 | | ||
| 267 | |||
| 268 | MQTT protocol has a much higher power consumption compare with UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. | ||
| 269 | |||
| 270 | |||
| 271 | === 2.2.6 Use TCP protocol to uplink data === | ||
| 272 | |||
| 273 | |||
| 274 | (% style="color:blue" %)**AT Commands:** | ||
| 275 | |||
| 276 | * (% style="color:#037691" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink | ||
| 277 | |||
| 278 | * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ Set TCP server address and port | ||
| 279 | |||
| 280 | [[image:1670406036256-101.png||height="676" width="713"]] | ||
| 281 | |||
| 282 | |||
| 283 | [[image:image-20221021111131-15.png]] | ||
| 284 | |||
| 285 | | ||
| 286 | |||
| 287 | === 2.2.7 Change Update Interval === | ||
| 288 | |||
| 289 | |||
| 290 | User can use below command to change the (% style="color:blue" %)**uplink interval**. | ||
| 291 | |||
| 292 | * (% style="color:#037691" %)**AT+TDC=7200 ** (%%) ~/~/ Set Update Interval to 7200s (4 hours) | ||
| 293 | |||
| 294 | (% style="color:red" %)**NOTE:** | ||
| 295 | |||
| 296 | 1. By default, the device will send an uplink message every 4 hour. | ||
| 297 | |||
| 298 | |||
| 299 | == 2.3 Uplink Payload == | ||
| 300 | |||
| 301 | |||
| 302 | The uplink payload includes 23 bytes in total by default. | ||
| 303 | |||
| 304 | Each time the device uploads a data package. The user can use the AT+NOUD command to upload the recorded data.Up to 32 sets of recorded data can be uploaded. | ||
| 305 | |||
| 306 | |||
| 307 | (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) | ||
| 308 | |=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:90px" %)**2**|(% style="width:100px" %)**2** | ||
| 309 | |=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) Distance 1 |(% style="width:93px" %) Distance 2 | ||
| 310 | |||
| 311 | (% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %) | ||
| 312 | |(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)((( | ||
| 313 | **1-32 group** | ||
| 314 | ))) | ||
| 315 | |(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance 2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)... | ||
| 316 | |||
| 317 | If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data. | ||
| 318 | |||
| 319 | [[image:1670406261143-723.png]] | ||
| 320 | |||
| 321 | |||
| 322 | The payload is ASCII string, representative same HEX: f867787050471071 0064 0cc3 09 01 00 00ef 013d 6390453d | ||
| 323 | |||
| 324 | **0x (% style="color:red" %)__f867787050471071__ (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)** | ||
| 325 | |||
| 326 | **where:** | ||
| 327 | |||
| 328 | * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071 | ||
| 329 | |||
| 330 | * (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 | ||
| 331 | |||
| 332 | * (% style="color:#037691" %)**BAT :**(%%) 0x0cc3 = 3267 mV = 3.267V | ||
| 333 | |||
| 334 | * (% style="color:#037691" %)**Singal: **(%%)0x09 = 9 | ||
| 335 | |||
| 336 | * (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 | ||
| 337 | |||
| 338 | * (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0 | ||
| 339 | |||
| 340 | * (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239 | ||
| 341 | |||
| 342 | * (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317 | ||
| 343 | |||
| 344 | * (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time) | ||
| 345 | |||
| 346 | |||
| 347 | |||
| 348 | == 2.4 Payload Explanation and Sensor Interface == | ||
| 349 | |||
| 350 | === 2.4.1 Device ID === | ||
| 351 | |||
| 352 | |||
| 353 | By default, the Device ID is equal to the last 15 bits of IMEI. | ||
| 354 | |||
| 355 | User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID | ||
| 356 | |||
| 357 | **Example:** | ||
| 358 | |||
| 359 | AT+DEUI=868411056754138 | ||
| 360 | |||
| 361 | The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID. | ||
| 362 | |||
| 363 | |||
| 364 | === 2.4.2 Version Info === | ||
| 365 | |||
| 366 | |||
| 367 | Specify the software version: 0x64=100, which means firmware version 1.00. | ||
| 368 | |||
| 369 | For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0. | ||
| 370 | |||
| 371 | |||
| 372 | === 2.4.3 Battery Info === | ||
| 373 | |||
| 374 | |||
| 375 | Check the battery voltage for NDS03A. | ||
| 376 | |||
| 377 | Ex1: 0x0B45 = 2885mV | ||
| 378 | |||
| 379 | Ex2: 0x0B49 = 2889mV | ||
| 380 | |||
| 381 | |||
| 382 | === 2.4.4 Signal Strength === | ||
| 383 | |||
| 384 | |||
| 385 | NB-IoT Network signal Strength. | ||
| 386 | |||
| 387 | **Ex1: 0x1d = 29** | ||
| 388 | |||
| 389 | **0** -113dBm or less | ||
| 390 | |||
| 391 | **1** -111dBm | ||
| 392 | |||
| 393 | **2...30** -109dBm... -53dBm | ||
| 394 | |||
| 395 | **31** -51dBm or greater | ||
| 396 | |||
| 397 | **99** Not known or not detectable | ||
| 398 | |||
| 399 | |||
| 400 | === 2.4.5 Disalarm: (default: 0) === | ||
| 401 | |||
| 402 | |||
| 403 | (% style="color:blue" %)**If Disalarm = 1**(%%), NDS03A will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many open/close event, and platform only care about the total number of pulse. | ||
| 404 | |||
| 405 | (% style="color:blue" %)**If Disalarm = 0**(%%), NDS03A will send uplink at every TDC periodically and send data on each open/close event. This is useful for the application user need to monitor the open/close event in real-time. | ||
| 406 | |||
| 407 | (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast. | ||
| 408 | |||
| 409 | |||
| 410 | === 2.4.6 Keep Status & Keep Time === | ||
| 411 | |||
| 412 | |||
| 413 | Shows the configure value of Alarm Base on Timeout Feature | ||
| 414 | |||
| 415 | |||
| 416 | === 2.4.7 Timestamp === | ||
| 417 | |||
| 418 | |||
| 419 | Timestamp : 0x6315537b =1662342011 | ||
| 420 | |||
| 421 | |||
| 422 | === 2.4.8 Switch Dual Channel Mode === | ||
| 423 | |||
| 424 | |||
| 425 | NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function. | ||
| 426 | |||
| 427 | |||
| 428 | == 2.5 Downlink Payload == | ||
| 429 | |||
| 430 | |||
| 431 | By default, NDS03A prints the downlink payload to console port. | ||
| 432 | |||
| 433 | [[image:image-20221021111414-18.png]] | ||
| 434 | |||
| 435 | |||
| 436 | **Examples:** | ||
| 437 | |||
| 438 | * (% style="color:#037691" %)**Set TDC** | ||
| 439 | |||
| 440 | If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. | ||
| 441 | |||
| 442 | Payload: 01 00 00 1E TDC=30S | ||
| 443 | |||
| 444 | Payload: 01 00 00 3C TDC=60S | ||
| 445 | |||
| 446 | * (% style="color:#037691" %)**Reset** | ||
| 447 | |||
| 448 | If payload = 0x04FF, it will reset the NDS03A | ||
| 449 | |||
| 450 | * (% style="color:#037691" %)**INTMOD** | ||
| 451 | |||
| 452 | Downlink Payload: 06000003, Set AT+INTMOD=3 | ||
| 453 | |||
| 454 | |||
| 455 | == 2.6 LED Indicator == | ||
| 456 | |||
| 457 | |||
| 458 | The NDS03A has an internal LED which is to show the status of different states. | ||
| 459 | |||
| 460 | * When the device starts normally, the LED will light up for 1 second. | ||
| 461 | * After NDS03A join NB-IoT network. The LED will be ON for 3 seconds. | ||
| 462 | * For each uplink probe, LED will be on for 500ms. | ||
| 463 | |||
| 464 | == 2.7 Alarm Base on Timeout == | ||
| 465 | |||
| 466 | |||
| 467 | NDS03A can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are: | ||
| 468 | |||
| 469 | |||
| 470 | (% style="color:blue" %)**1. Keep Status: Status to be monitor** | ||
| 471 | |||
| 472 | Keep Status = 1: Monitor Close to Open event | ||
| 473 | |||
| 474 | Keep Status = 0: Monitor Open to Close event | ||
| 475 | |||
| 476 | |||
| 477 | (% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm** | ||
| 478 | |||
| 479 | Range 0 ~~ 65535(0xFFFF) seconds. | ||
| 480 | |||
| 481 | If keep time = 0, Disable Alarm Base on Timeout feature. | ||
| 482 | |||
| 483 | If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout. | ||
| 484 | |||
| 485 | |||
| 486 | (% style="color:blue" %)**AT Command to configure:** | ||
| 487 | |||
| 488 | (% style="color:blue" %)**PB14 PIN:** | ||
| 489 | |||
| 490 | (% style="color:#037691" %)**AT+TTRIG=1,30** (%%) **~-~->** When the **Keep Status** change from connected to disconnect, and device remains in disconnect status for more than 30 seconds. NDS03A will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1. | ||
| 491 | |||
| 492 | (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm. | ||
| 493 | |||
| 494 | |||
| 495 | (% style="color:blue" %)**PB15 PIN:** | ||
| 496 | |||
| 497 | (% style="color:#037691" %)**AT+TTRIG2=1,30** | ||
| 498 | |||
| 499 | (% style="color:#037691" %)**AT+TTRIG2=0,0 ** | ||
| 500 | |||
| 501 | |||
| 502 | == 2.8 Set debug mode == | ||
| 503 | |||
| 504 | |||
| 505 | Feature: Enable or Disable debug mode | ||
| 506 | |||
| 507 | (% style="color:blue" %)**AT Command: AT+DEBUG** | ||
| 508 | |||
| 509 | [[image:image-20221021111629-21.png]] | ||
| 510 | |||
| 511 | |||
| 512 | |||
| 513 | == 2.9 Clear Flash Record == | ||
| 514 | |||
| 515 | |||
| 516 | Feature: Clear flash storage for data log feature. | ||
| 517 | |||
| 518 | (% style="color:blue" %)**AT Command: AT+CLRDTA** | ||
| 519 | |||
| 520 | [[image:image-20221021111527-19.png]] | ||
| 521 | |||
| 522 | |||
| 523 | == 2.10 Count Mod == | ||
| 524 | |||
| 525 | |||
| 526 | (% style="color:blue" %)**AT Command: AT+COUNTMOD** | ||
| 527 | |||
| 528 | [[image:image-20221118092935-1.png]] | ||
| 529 | |||
| 530 | |||
| 531 | == 2.11 Interrupt Pin Channel Mod == | ||
| 532 | |||
| 533 | |||
| 534 | (% style="color:blue" %)**AT Command: AT+TTRCHANNEL** | ||
| 535 | |||
| 536 | [[image:image-20221118093144-2.png]] | ||
| 537 | |||
| 538 | |||
| 539 | == 2.12 TTRIG1/2 timeout status alarm == | ||
| 540 | |||
| 541 | |||
| 542 | It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval. | ||
| 543 | |||
| 544 | (% style="color:blue" %)**AT Command: AT+TTRALARM** | ||
| 545 | |||
| 546 | [[image:image-20221118093512-3.png]] | ||
| 547 | |||
| 548 | |||
| 549 | == 2.13 Select counting mode == | ||
| 550 | |||
| 551 | |||
| 552 | (% style="color:blue" %)**AT Command: AT+TTRMODx=a,b** | ||
| 553 | |||
| 554 | When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted. | ||
| 555 | |||
| 556 | When (% style="color:red" %)**b=0**(%%), it is the last door open duration, and when (% style="color:red" %)**b=1**(%%),the last door close duration. | ||
| 557 | |||
| 558 | [[image:image-20221118093658-4.png]] | ||
| 559 | |||
| 560 | |||
| 561 | == 2.14 Set the number of data to be uploaded and the recording time == | ||
| 562 | |||
| 563 | |||
| 564 | (% style="color:blue" %)**AT Command:** | ||
| 565 | |||
| 566 | (% style="color:#037691" %)**AT+TR=900**(%%) ~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds) | ||
| 567 | |||
| 568 | (% style="color:#037691" %)**AT+NOUD=8**(%%)** ** ~/~/ The device uploads 0 sets of recorded data by default. Up to 32 sets of record data can be uploaded. | ||
| 569 | |||
| 570 | |||
| 571 | == 2.15 Read or Clear cached data == | ||
| 572 | |||
| 573 | |||
| 574 | (% style="color:blue" %)**AT Command:** | ||
| 575 | |||
| 576 | (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data | ||
| 577 | |||
| 578 | (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data | ||
| 579 | |||
| 580 | [[image:image-20221118094227-5.png]] | ||
| 581 | |||
| 582 | |||
| 583 | == 2.16 Firmware Change Log == | ||
| 584 | |||
| 585 | |||
| 586 | Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]] | ||
| 587 | |||
| 588 | Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] | ||
| 589 | |||
| 590 | |||
| 591 | == 2.17 Battery Analysis == | ||
| 592 | |||
| 593 | === 2.17.1 Battery Type === | ||
| 594 | |||
| 595 | |||
| 596 | The NDS03A battery is a combination of an 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. | ||
| 597 | |||
| 598 | The battery is designed to last for several years depends on the actual use environment and update interval. | ||
| 599 | |||
| 600 | The battery-related documents as below: | ||
| 601 | |||
| 602 | * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] | ||
| 603 | |||
| 604 | * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] | ||
| 605 | |||
| 606 | * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] | ||
| 607 | |||
| 608 | [[image:image-20221021111911-26.png]] | ||
| 609 | |||
| 610 | |||
| 611 | === 2.17.2 Power consumption Analyze === | ||
| 612 | |||
| 613 | |||
| 614 | Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval. | ||
| 615 | |||
| 616 | Instruction to use as below: | ||
| 617 | |||
| 618 | (% style="color:blue" %)**Step 1: **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]] | ||
| 619 | |||
| 620 | (% style="color:blue" %)**Step 2: **(%%) Open it and choose | ||
| 621 | |||
| 622 | * Product Model | ||
| 623 | |||
| 624 | * Uplink Interval | ||
| 625 | |||
| 626 | * Working Mode | ||
| 627 | |||
| 628 | And the Life expectation in difference case will be shown on the right. | ||
| 629 | |||
| 630 | [[image:1666596205057-567.png]] | ||
| 631 | |||
| 632 | |||
| 633 | === 2.17.3 Battery Note === | ||
| 634 | |||
| 635 | |||
| 636 | The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased. | ||
| 637 | |||
| 638 | |||
| 639 | === 2.17.4 Replace the battery === | ||
| 640 | |||
| 641 | |||
| 642 | The default battery pack of NDS03A 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). | ||
| 643 | |||
| 644 | |||
| 645 | = 3. Access NB-IoT Module = | ||
| 646 | |||
| 647 | |||
| 648 | Users can directly access the AT command set of the NB-IoT module. | ||
| 649 | |||
| 650 | The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] | ||
| 651 | |||
| 652 | |||
| 653 | [[image:image-20221118094449-6.png]] | ||
| 654 | |||
| 655 | |||
| 656 | = 4. Using the AT Commands = | ||
| 657 | |||
| 658 | == 4.1 Access AT Commands == | ||
| 659 | |||
| 660 | |||
| 661 | See this link for detail: [[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]] | ||
| 662 | |||
| 663 | AT+<CMD>? : Help on <CMD> | ||
| 664 | |||
| 665 | AT+<CMD> : Run <CMD> | ||
| 666 | |||
| 667 | AT+<CMD>=<value> : Set the value | ||
| 668 | |||
| 669 | AT+<CMD>=? : Get the value | ||
| 670 | |||
| 671 | |||
| 672 | (% style="color:blue" %)**General Commands** | ||
| 673 | |||
| 674 | AT : Attention | ||
| 675 | |||
| 676 | AT? : Short Help | ||
| 677 | |||
| 678 | ATZ : MCU Reset | ||
| 679 | |||
| 680 | AT+TDC : Application Data Transmission Interval | ||
| 681 | |||
| 682 | AT+CFG : Print all configurations | ||
| 683 | |||
| 684 | AT+CFGMOD : Working mode selection | ||
| 685 | |||
| 686 | AT+INTMOD : Set the trigger interrupt mode | ||
| 687 | |||
| 688 | AT+5VT : Set extend the time of 5V power | ||
| 689 | |||
| 690 | AT+PRO : Choose agreement | ||
| 691 | |||
| 692 | AT+RXDL : Extend the sending and receiving time | ||
| 693 | |||
| 694 | AT+SERVADDR : Server Address | ||
| 695 | |||
| 696 | AT+TR : Get or Set record time | ||
| 697 | |||
| 698 | AT+NOUD : Get or Set the number of data to be uploaded | ||
| 699 | |||
| 700 | AT+CDP : Read or Clear cached data | ||
| 701 | |||
| 702 | AT+ DEBUG : Enable or Disable debug mode | ||
| 703 | |||
| 704 | AT+ TTRIG1 : Get or Set PB14 PIN Alarm Base on Timeout | ||
| 705 | |||
| 706 | AT+ TTRIG2 : Get or Set PB15 PIN Alarm Base on Timeout | ||
| 707 | |||
| 708 | AT+COUNTMOD : Get or Set the count mode | ||
| 709 | |||
| 710 | AT+TTRCHANNEL : Get or Set the number of interrupt channels | ||
| 711 | |||
| 712 | AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute) | ||
| 713 | |||
| 714 | AT+DISALARM : Enable/Disable Alarm for door open/close or water leak event | ||
| 715 | |||
| 716 | AT+ CLRC : Clear current door open count | ||
| 717 | |||
| 718 | |||
| 719 | (% style="color:blue" %)**COAP Management** | ||
| 720 | |||
| 721 | AT+URI : Resource parameters | ||
| 722 | |||
| 723 | |||
| 724 | (% style="color:blue" %)**UDP Management** | ||
| 725 | |||
| 726 | AT+CFM : Upload confirmation mode (only valid for UDP) | ||
| 727 | |||
| 728 | |||
| 729 | (% style="color:blue" %)**MQTT Management** | ||
| 730 | |||
| 731 | AT+CLIENT : Get or Set MQTT client | ||
| 732 | |||
| 733 | AT+UNAME : Get or Set MQTT Username | ||
| 734 | |||
| 735 | AT+PWD : Get or Set MQTT password | ||
| 736 | |||
| 737 | AT+PUBTOPIC : Get or Set MQTT publish topic | ||
| 738 | |||
| 739 | AT+SUBTOPIC : Get or Set MQTT subscription topic | ||
| 740 | |||
| 741 | |||
| 742 | (% style="color:blue" %)**Information** | ||
| 743 | |||
| 744 | AT+FDR : Factory Data Reset | ||
| 745 | |||
| 746 | AT+PWORD : Serial Access Password | ||
| 747 | |||
| 748 | |||
| 749 | = 5. FAQ = | ||
| 750 | |||
| 751 | == 5.1 How to Upgrade Firmware == | ||
| 752 | |||
| 753 | |||
| 754 | User can upgrade the firmware for 1) bug fix, 2) new feature release. | ||
| 755 | |||
| 756 | Please see this link for how to upgrade: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]] | ||
| 757 | |||
| 758 | (% style="color:red" %)**Notice: **(% style="color:blue" %)**NDS03A** (%%)**and (% style="color:blue" %)LDS03A(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.** | ||
| 759 | |||
| 760 | |||
| 761 | = 6. Trouble Shooting = | ||
| 762 | |||
| 763 | == 6.1 Connection problem when uploading firmware == | ||
| 764 | |||
| 765 | |||
| 766 | (% style="color:blue" %)**Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]] | ||
| 767 | |||
| 768 | |||
| 769 | == 6.2 AT Command input doesn't work == | ||
| 770 | |||
| 771 | |||
| 772 | 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. | ||
| 773 | |||
| 774 | |||
| 775 | = 7. Order Info = | ||
| 776 | |||
| 777 | |||
| 778 | Part Number**:** NDS03A | ||
| 779 | |||
| 780 | |||
| 781 | = 8. Packing Info = | ||
| 782 | |||
| 783 | |||
| 784 | (% style="color:blue" %)**Package Includes**: | ||
| 785 | |||
| 786 | * NDS03A Open/Close Door Sensor x 1 | ||
| 787 | |||
| 788 | = 9. Support = | ||
| 789 | |||
| 790 | |||
| 791 | * 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. | ||
| 792 | |||
| 793 | * 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]] | ||
| 794 | |||
| 795 | |