Changes for page NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 17:03
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 12 added, 0 removed)
- LMDS200_10.jpg
- image-20221118092935-1.png
- image-20221118093144-2.png
- image-20221118093512-3.png
- image-20221118093658-4.png
- image-20221118094227-5.png
- image-20221118094449-6.png
- image-20221118103445-7.png
- image-20221118103453-8.png
- image-20221118103547-9.png
- image-20221207170748-1.png
- image-20221207170748-2.png
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -NDS0 3A-OutdoorNB-IoTOpen/CloseDoor Sensor User Manual1 +NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual - Content
-
... ... @@ -1,12 +1,7 @@ 1 1 (% style="text-align:center" %) 2 -[[image: image-20221117105556-1.png]]2 +[[image:LMDS200_10.jpg]] 3 3 4 4 5 - 6 - 7 - 8 - 9 - 10 10 **Table of Contents:** 11 11 12 12 ... ... @@ -15,7 +15,7 @@ 15 15 16 16 = 1. Introduction = 17 17 18 -== 1.1 What is NDS0 3ANB-IoTOpen/CloseDoor Sensor ==13 +== 1.1 What is NMDS200 NB-IoT Microwave Radar Distance Sensor == 19 19 20 20 21 21 ((( ... ... @@ -39,10 +39,14 @@ 39 39 ))) 40 40 41 41 ((( 42 -NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technology TCP, MQTT, UDP, and CoAP**(%%)for differentapplication requirements.37 +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. 43 43 ))) 44 44 45 45 ((( 41 +NDS03A supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements. 42 +))) 43 + 44 +((( 46 46 NDS03A 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) 47 47 ))) 48 48 ... ... @@ -107,12 +107,12 @@ 107 107 108 108 (% style="color:blue" %)**NB-IoT Spec:** 109 109 110 -* -B1 @H-FDD: 2100MHz111 -* -B3 @H-FDD: 1800MHz112 -* -B8 @H-FDD: 900MHz113 -* -B5 @H-FDD: 850MHz114 -* -B20 @H-FDD: 800MHz115 -* -B28 @H-FDD: 700MHz109 +* B1 @H-FDD: 2100MHz 110 +* B3 @H-FDD: 1800MHz 111 +* B8 @H-FDD: 900MHz 112 +* B5 @H-FDD: 850MHz 113 +* B20 @H-FDD: 800MHz 114 +* B28 @H-FDD: 700MHz 116 116 117 117 118 118 == 1.7 Pin Definitions and Switch == ... ... @@ -127,7 +127,6 @@ 127 127 The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at: [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]] 128 128 129 129 130 - 131 131 === 1.7.2 Jumper JP2(Power ON/OFF) === 132 132 133 133 ... ... @@ -134,7 +134,6 @@ 134 134 Power on Device when putting this jumper. 135 135 136 136 137 - 138 138 === 1.7.3 BOOT MODE / SW1 === 139 139 140 140 ... ... @@ -143,7 +143,6 @@ 143 143 2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging. 144 144 145 145 146 - 147 147 === 1.7.4 Reset Button === 148 148 149 149 ... ... @@ -150,7 +150,6 @@ 150 150 Press to reboot the device. 151 151 152 152 153 - 154 154 === 1.7.5 LED === 155 155 156 156 ... ... @@ -161,7 +161,6 @@ 161 161 2. Send an uplink packet 162 162 163 163 164 - 165 165 == 1.8 Magnet Distance == 166 166 167 167 ... ... @@ -170,9 +170,8 @@ 170 170 (% style="color:blue" %)**Iron Door:**(%%)** **30 ~~ 45mm 171 171 172 172 167 += 2. Use NDS03A to communicate with IoT Server = 173 173 174 -= 2. Use CPN01 to communicate with IoT Server = 175 - 176 176 == 2.1 How it works == 177 177 178 178 ... ... @@ -183,7 +183,6 @@ 183 183 [[image:image-20221021110615-5.png]] 184 184 185 185 186 - 187 187 == 2.2 Configure NDS03A == 188 188 189 189 === 2.2.1 Test Requirement === ... ... @@ -199,9 +199,7 @@ 199 199 200 200 [[image:image-20221117142300-1.png]] 201 201 202 - 203 203 204 - 205 205 === 2.2.2 Insert NB-IoT SIM card === 206 206 207 207 ... ... @@ -212,7 +212,6 @@ 212 212 [[image:image-20221021110745-6.png]] 213 213 214 214 215 - 216 216 === 2.2.3 Connect USB – TTL to NDS03A and configure it === 217 217 218 218 ... ... @@ -256,7 +256,7 @@ 256 256 (% 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/]] 257 257 258 258 259 -(% style="color:blue" %)**Use below commands in CPN01:**248 +(% style="color:blue" %)**Use below commands in NDS03A:** 260 260 261 261 * (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 262 262 ... ... @@ -269,12 +269,11 @@ 269 269 [[image:image-20221021110948-8.png]] 270 270 271 271 272 -After configuring the server address and (% style="color:green" %)**reset CPN01**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.261 +After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server. 273 273 274 -[[image:image-20221 021110956-9.png]] 263 +[[image:image-20221118103547-9.png||height="605" width="837"]] 275 275 276 276 277 - 278 278 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 279 279 280 280 ... ... @@ -293,7 +293,6 @@ 293 293 294 294 295 295 296 - 297 297 === 2.2.6 Use MQTT protocol to uplink data === 298 298 299 299 ... ... @@ -313,10 +313,10 @@ 313 313 314 314 * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB ** (%%) ~/~/ Set the subscription topic of MQTT 315 315 316 - [[image:image-20221 021111058-12.png]]303 + [[image:image-20221118103445-7.png]] 317 317 318 318 319 -[[image:image-20221 021111201-16.png||height="472" width="653"]]306 +[[image:image-20221118103453-8.png||height="608" width="841"]] 320 320 321 321 322 322 ... ... @@ -323,7 +323,6 @@ 323 323 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. 324 324 325 325 326 - 327 327 === 2.2.7 Use TCP protocol to uplink data === 328 328 329 329 ... ... @@ -339,7 +339,6 @@ 339 339 340 340 341 341 342 - 343 343 === 2.2.8 Change Update Interval === 344 344 345 345 ... ... @@ -352,23 +352,42 @@ 352 352 1. By default, the device will send an uplink message every 4 hour. 353 353 354 354 355 - 356 356 == 2.3 Uplink Payload == 357 357 358 358 359 -The uplink payload includes 123bytes in total by default.343 +The uplink payload includes 26 bytes in total by default. 360 360 361 -Each time the device uploads a data package ,8sets ofrecorded datawill be attached.345 +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. 362 362 347 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:** 363 363 364 -(% border="1 .5" style="background-color:#ffffcc; color:green; width:510px" %)365 -|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:60px" %)**3**366 -|=(% style="width: 9 6px;" %)**Value**|(% style="width:84px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:44px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:121px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:52px" %)MOD|(% style="width:84px" %)[[ Calculate Flag>>||anchor="H2.4.5A0CalculateFlag"]]|(% style="width:116px" %)[[ContactStatus>>||anchor="H2.4.7A0ContactStatus"]]|(% style="width:57px" %)[[Alarm>>||anchor="H2.4.6A0Alarm"]]|(% style="width:91px" %)[[Total pulse>>||anchor="H2.4.8A0Totalpulse"]]349 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 350 +|=(% 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:60px" %)**1**|(% style="width:90px" %)**3**|(% style="width:100px" %)**3** 351 +|=(% 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" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14) 367 367 368 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %) 369 -|(% style="width:100px" %)**3**|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:100px" %)**3**|(% style="width:80px" %)4|(% style="width:50px" %)**8 group** 370 -|(% style="width:176px" %)[[The last open duration>>||anchor="H2.4.9A0Thelastopenduration"]]|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% style="width:115px" %)Contact Status|(% style="width:92px" %)Total pulse|(% style="width:169px" %)The last open duration|(% style="width:97px" %)Time stamp|(% style="width:74px" %)... 353 +(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %) 354 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)((( 355 +**1-32 group** 356 +))) 357 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)... 371 371 359 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:** 360 + 361 + 362 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 363 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:45px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:60px" %)**1**|(% style="width:60px" %)**1**|(% style="width:87px" %)**3**|(% style="width:80px" %)**3** 364 +|=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14) 365 + 366 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 367 +|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:75px" %)**1**|(% style="width:75px" %)**3** 368 +|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14) 369 + 370 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 371 +|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)((( 372 +**1-32 group** 373 +))) 374 +|(% style="width:102px" %)last open time(pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:100px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)...... 375 + 372 372 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data. 373 373 374 374 [[image:image-20221117145932-2.png]] ... ... @@ -376,8 +376,6 @@ 376 376 377 377 The payload is ASCII string, representative same HEX: 378 378 379 -**0x **f867787050213317 0064 0ccf 19 01 00 00 000016 000017 637590df 380 - 381 381 **0x (% style="color:red" %)__f867787050213317__ (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)** 382 382 383 383 **where:** ... ... @@ -384,29 +384,27 @@ 384 384 385 385 * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317 386 386 387 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 389 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 388 388 389 389 * (% style="color:#037691" %)**BAT :**(%%) 0x0ccf = 3279 mV = 3.279V 390 390 391 391 * (% style="color:#037691" %)**Singal: **(%%)0x19 = 25 392 392 393 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 395 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 394 394 395 -* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0 397 +* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0 396 396 397 397 * (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0 398 398 399 399 * (% style="color:#037691" %)**door open num: **(%%)0x000016 =22 400 400 401 -* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23 403 +* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23 402 402 403 403 * (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time) 404 404 405 405 406 - 407 407 == 2.4 Payload Explanation and Sensor Interface == 408 408 409 - 410 410 === 2.4.1 Device ID === 411 411 412 412 ... ... @@ -421,20 +421,18 @@ 421 421 The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID. 422 422 423 423 424 - 425 425 === 2.4.2 Version Info === 426 426 427 427 428 428 Specify the software version: 0x64=100, which means firmware version 1.00. 429 429 430 -For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.429 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0. 431 431 432 432 433 - 434 434 === 2.4.3 Battery Info === 435 435 436 436 437 -Check the battery voltage for CPN01.435 +Check the battery voltage for NDS03A. 438 438 439 439 Ex1: 0x0B45 = 2885mV 440 440 ... ... @@ -441,7 +441,6 @@ 441 441 Ex2: 0x0B49 = 2889mV 442 442 443 443 444 - 445 445 === 2.4.4 Signal Strength === 446 446 447 447 ... ... @@ -460,70 +460,38 @@ 460 460 **99** Not known or not detectable 461 461 462 462 460 +=== 2.4.5 Disalarm: (default: 0) === 463 463 464 -=== 2.4.5 Calculate Flag === 465 465 463 +(% 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. 466 466 467 - Thecalculate flagisuserdefinedfield,IoTserver canusethis filed tohandledifferentmeterswithdifferent pulse factors.Forexample,ifthereare100 watermeters,meter1~~50 are1 liter/pulseand meter51~~ 100 has 1.5liter/pulse.465 +(% 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. 468 468 469 - Usercansetcalculateflag to1foreter 1~~50 and2formeter51 ~~ 100, SoIoTServercanuse this fieldforcalculation.467 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast. 470 470 471 -Default value: 0. 472 472 473 - Range(6bits):(b)000000~~(b)111111470 +=== 2.4.6 Keep Status & Keep Time === 474 474 475 475 473 +Shows the configure value of Alarm Base on Timeout Feature 476 476 477 -=== 2.4.6 Alarm === 478 478 476 +=== 2.4.7 Timestamp === 479 479 480 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]] 481 481 479 +Timestamp : 0x6315537b =1662342011 482 482 483 483 484 -=== 2.4. 7ContactStatus===482 +=== 2.4.8 Switch Dual Channel Mode === 485 485 486 486 487 -0 :Open485 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function. 488 488 489 -1: Close 490 490 491 - 492 - 493 -=== 2.4.8 Total pulse === 494 - 495 - 496 -Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]] 497 - 498 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215 499 - 500 - 501 - 502 -=== 2.4.9 The last open duration === 503 - 504 - 505 -Dry Contact last open duration. 506 - 507 -Unit: min. 508 - 509 -[[image:image-20221021111346-17.png||height="146" width="770"]] 510 - 511 - 512 - 513 -=== 2.4.10 Timestamp === 514 - 515 - 516 -Timestamp : 0x6315537b =1662342011 517 - 518 -Convert Unix timestamp to time 2022-9-5 9:40:11. 519 - 520 -**~ ** 521 - 522 - 523 523 == 2.5 Downlink Payload == 524 524 525 525 526 -By default, CPN01prints the downlink payload to console port.491 +By default, NDS03A prints the downlink payload to console port. 527 527 528 528 [[image:image-20221021111414-18.png]] 529 529 ... ... @@ -540,7 +540,7 @@ 540 540 541 541 * (% style="color:#037691" %)**Reset** 542 542 543 -If payload = 0x04FF, it will reset the NS E01508 +If payload = 0x04FF, it will reset the NDS03A 544 544 545 545 * (% style="color:#037691" %)**INTMOD** 546 546 ... ... @@ -547,20 +547,20 @@ 547 547 Downlink Payload: 06000003, Set AT+INTMOD=3 548 548 549 549 550 - 551 551 == 2.6 LED Indicator == 552 552 553 553 554 -The CPN01has an internal LED which is to show the status of different states.518 +The NDS03A has an internal LED which is to show the status of different states. 555 555 556 556 * When the device starts normally, the LED will light up for 1 second. 557 -* After CPN01join NB-IoT network. The LED will be ON for 3 seconds.521 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds. 558 558 * For each uplink probe, LED will be on for 500ms. 559 559 524 + 560 560 == 2.7 Alarm Base on Timeout == 561 561 562 562 563 - CPN01can 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:528 +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: 564 564 565 565 566 566 (% style="color:blue" %)**1. Keep Status: Status to be monitor** ... ... @@ -576,17 +576,25 @@ 576 576 577 577 If keep time = 0, Disable Alarm Base on Timeout feature. 578 578 579 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn ’t change after timeout.544 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout. 580 580 581 581 582 582 (% style="color:blue" %)**AT Command to configure:** 583 583 584 -(% 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. CPN01will 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.549 +(% style="color:blue" %)**PB14 PIN:** 585 585 551 +(% 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. 552 + 586 586 (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm. 587 587 588 588 556 +(% style="color:blue" %)**PB15 PIN:** 589 589 558 +(% style="color:#037691" %)**AT+TTRIG2=1,30** 559 + 560 +(% style="color:#037691" %)**AT+TTRIG2=0,0 ** 561 + 562 + 590 590 == 2.8 Set debug mode == 591 591 592 592 ... ... @@ -608,54 +608,57 @@ 608 608 [[image:image-20221021111527-19.png]] 609 609 610 610 584 +== 2.10 Count Mod == 611 611 612 -== 2.10 Set trigger mode == 613 613 587 +(% style="color:blue" %)**AT Command: AT+COUNTMOD** 614 614 615 - (% style="color:blue" %)**AT Command: AT+TTRMOD**589 +[[image:image-20221118092935-1.png]] 616 616 617 -Feature: Set the trigger interrupt mode. 618 618 619 - [[image:image-20221021111552-20.png]]592 +== 2.11 Interrupt Pin Channel Mod == 620 620 621 621 595 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL** 622 622 623 - == 2.11 Set the calculateflag==597 +[[image:image-20221118093144-2.png]] 624 624 625 625 626 - Feature:Setthecalculateflag600 +== 2.12 TTRIG1/2 timeout status alarm == 627 627 628 -(% style="color:blue" %)**AT Command: AT+CALCFLAG** 629 629 630 - [[image:image-20221021111711-22.png]]603 +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. 631 631 605 +(% style="color:blue" %)**AT Command: AT+TTRALARM** 632 632 607 +[[image:image-20221118093512-3.png]] 633 633 634 -== 2.12 Set count number == 635 635 610 +== 2.13 Select counting mode == 636 636 637 -Feature: Manually set the count number 638 638 639 -(% style="color:blue" %)**AT Command: AT+ SETCNT**613 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b** 640 640 641 - [[image:image-20221021111748-24.png]]615 +When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted. 642 642 617 +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. 643 643 619 +[[image:image-20221118093658-4.png]] 644 644 645 -== 2.13 Set the number of data to be uploaded and the recording time == 646 646 622 +== 2.14 Set the number of data to be uploaded and the recording time == 647 647 624 + 648 648 (% style="color:blue" %)**AT Command:** 649 649 650 -(% style="color:#037691" %)**AT+TR=900** 627 +(% 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) 651 651 652 -(% style="color:#037691" %)**AT+NOUD=8 ** (%%)~/~/ The device uploads8sets of recorded data by default. Up to 32 sets of record data can be uploaded.629 +(% 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. 653 653 654 654 632 +== 2.15 Read or Clear cached data == 655 655 656 -== 2.14 Read or Clear cached data == 657 657 658 - 659 659 (% style="color:blue" %)**AT Command:** 660 660 661 661 (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data ... ... @@ -662,27 +662,24 @@ 662 662 663 663 (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 664 664 665 -[[image:image-20221 021111810-25.png||height="364" width="797"]]641 +[[image:image-20221118094227-5.png]] 666 666 667 667 644 +== 2.16 Firmware Change Log == 668 668 669 -== 2.15 Firmware Change Log == 670 670 647 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]] 671 671 672 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]] 673 - 674 674 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 675 675 676 676 652 +== 2.17 Battery Analysis == 677 677 678 -== 2.1 6BatteryAnalysis==654 +=== 2.17.1 Battery Type === 679 679 680 680 681 - ===2.16.1Battery Type===657 +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. 682 682 683 - 684 -The CPN01 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. 685 - 686 686 The battery is designed to last for several years depends on the actual use environment and update interval. 687 687 688 688 The battery-related documents as below: ... ... @@ -696,10 +696,9 @@ 696 696 [[image:image-20221021111911-26.png]] 697 697 698 698 672 +=== 2.17.2 Power consumption Analyze === 699 699 700 -=== 2.16.2 Power consumption Analyze === 701 701 702 - 703 703 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. 704 704 705 705 Instruction to use as below: ... ... @@ -719,21 +719,18 @@ 719 719 [[image:1666596205057-567.png]] 720 720 721 721 694 +=== 2.17.3 Battery Note === 722 722 723 -=== 2.16.3 Battery Note === 724 724 725 - 726 726 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. 727 727 728 728 700 +=== 2.17.4 Replace the battery === 729 729 730 -=== 2.16.4 Replace the battery === 731 731 703 +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). 732 732 733 -The default battery pack of CPN01 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). 734 734 735 - 736 - 737 737 = 3. Access NB-IoT Module = 738 738 739 739 ... ... @@ -741,13 +741,12 @@ 741 741 742 742 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/]] 743 743 744 -[[image:image-20221021112006-28.png]] 745 745 714 +[[image:image-20221118094449-6.png]] 746 746 747 747 748 748 = 4. Using the AT Commands = 749 749 750 - 751 751 == 4.1 Access AT Commands == 752 752 753 753 ... ... @@ -794,15 +794,21 @@ 794 794 795 795 AT+ DEBUG : Enable or Disable debug mode 796 796 797 -AT+ TTRIG : Get or Set Alarm Base on Timeout 765 +AT+ TTRIG1 : Get or Set PB14 PIN Alarm Base on Timeout 798 798 799 -AT+ TTR MOD: Get or Setthetriggerinterruptmode(0:falling,1:rising)767 +AT+ TTRIG2 : Get or Set PB15 PIN Alarm Base on Timeout 800 800 801 -AT+ ALCFLAGalculateflag769 +AT+COUNTMOD : Get or Set the count mode 802 802 803 -AT+ CLRCClearcurrentdoor open count771 +AT+TTRCHANNEL : Get or Set the number of interrupt channels 804 804 773 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute) 805 805 775 +AT+DISALARM : Enable/Disable Alarm for door open/close or water leak event 776 + 777 +AT+ CLRC : Clear current door open count 778 + 779 + 806 806 (% style="color:blue" %)**COAP Management** 807 807 808 808 AT+URI : Resource parameters ... ... @@ -833,10 +833,8 @@ 833 833 AT+PWORD : Serial Access Password 834 834 835 835 836 - 837 837 = 5. FAQ = 838 838 839 - 840 840 == 5.1 How to Upgrade Firmware == 841 841 842 842 ... ... @@ -844,13 +844,11 @@ 844 844 845 845 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]] 846 846 847 -(% style="color:red" %)**Notice: **(% style="color:blue" %)** CPN01** (%%)**and (% style="color:blue" %)CPL01(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**819 +(% 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.** 848 848 849 849 850 - 851 851 = 6. Trouble Shooting = 852 852 853 - 854 854 == 6.1 Connection problem when uploading firmware == 855 855 856 856 ... ... @@ -857,7 +857,6 @@ 857 857 (% 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]] 858 858 859 859 860 - 861 861 == 6.2 AT Command input doesn't work == 862 862 863 863 ... ... @@ -864,27 +864,20 @@ 864 864 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. 865 865 866 866 867 - 868 868 = 7. Order Info = 869 869 870 870 871 -Part Number**:** CPN01839 +Part Number**:** NDS03A 872 872 873 873 874 - 875 875 = 8. Packing Info = 876 876 877 877 878 878 (% style="color:blue" %)**Package Includes**: 879 879 880 -* CPN01 Open/Close Sensor x 1 881 -* External antenna x 1 847 +* NDS03A Open/Close Door Sensor x 1 882 882 883 -(% style="color:blue" %)**Dimension and weight**: 884 884 885 -* Size: 195 x 125 x 55 mm 886 -* Weight: 420g 887 - 888 888 = 9. Support = 889 889 890 890
- LMDS200_10.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +39.9 KB - Content
- image-20221118092935-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +13.1 KB - Content
- image-20221118093144-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +11.7 KB - Content
- image-20221118093512-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +9.5 KB - Content
- image-20221118093658-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +12.7 KB - Content
- image-20221118094227-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +29.2 KB - Content
- image-20221118094449-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +76.5 KB - Content
- image-20221118103445-7.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +20.4 KB - Content
- image-20221118103453-8.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +46.2 KB - Content
- image-20221118103547-9.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +43.5 KB - Content
- image-20221207170748-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +26.1 KB - Content
- image-20221207170748-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +29.9 KB - Content