Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 60.1 >
edited by Xiaoling
on 2022/11/17 14:59
To version < 70.5 >
edited by Xiaoling
on 2022/11/18 10:48
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -9,10 +9,12 @@
9 9  
10 10  **Table of Contents：**
11 11  
12 +{{toc/}}
12 12  
13 13  
14 14  
15 15  
17 +
16 16  = 1.  Introduction =
17 17  
18 18  == 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
... ... @@ -129,7 +129,6 @@
129 129  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]]
130 130  
131 131  
132 -
133 133  === 1.7.2  Jumper JP2(Power ON/OFF) ===
134 134  
135 135  
... ... @@ -136,7 +136,6 @@
136 136  Power on Device when putting this jumper.
137 137  
138 138  
139 -
140 140  === 1.7.3  BOOT MODE / SW1 ===
141 141  
142 142  
... ... @@ -145,7 +145,6 @@
145 145  2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
146 146  
147 147  
148 -
149 149  === 1.7.4  Reset Button ===
150 150  
151 151  
... ... @@ -152,7 +152,6 @@
152 152  Press to reboot the device.
153 153  
154 154  
155 -
156 156  === 1.7.5  LED ===
157 157  
158 158  
... ... @@ -163,18 +163,16 @@
163 163  2.  Send an uplink packet
164 164  
165 165  
166 -
167 167  == 1.8  Magnet Distance ==
168 168  
169 169  
170 170  (% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
171 171  
172 -(% style="color:blue" %)**Iron Door:**(%%)**  **30 ~~ 45mm
169 +(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
173 173  
174 174  
172 += 2.  Use NDS03A to communicate with IoT Server =
175 175  
176 -= 2.  Use CPN01 to communicate with IoT Server =
177 -
178 178  == 2.1  How it works ==
179 179  
180 180  
... ... @@ -185,7 +185,6 @@
185 185  [[image:image-20221021110615-5.png]]
186 186  
187 187  
188 -
189 189  == 2.2 ​ Configure NDS03A ==
190 190  
191 191  === 2.2.1 Test Requirement ===
... ... @@ -201,9 +201,7 @@
201 201  
202 202  [[image:image-20221117142300-1.png]]
203 203  
204 - ​
205 205  
206 -
207 207  === 2.2.2 Insert NB-IoT SIM card ===
208 208  
209 209  
... ... @@ -214,7 +214,6 @@
214 214  [[image:image-20221021110745-6.png]] ​
215 215  
216 216  
217 -
218 218  === 2.2.3 Connect USB – TTL to NDS03A and configure it ===
219 219  
220 220  
... ... @@ -258,7 +258,7 @@
258 258  (% 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/]]
259 259  
260 260  
261 -(% style="color:blue" %)**Use below commands in CPN01:**
253 +(% style="color:blue" %)**Use below commands in NDS03A:**
262 262  
263 263  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
264 264  
... ... @@ -271,12 +271,11 @@
271 271  [[image:image-20221021110948-8.png]]
272 272  
273 273  
274 -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.
266 +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.
275 275  
276 -[[image:image-20221021110956-9.png]] ​
268 +[[image:image-20221118103547-9.png||height="605" width="837"]] ​
277 277  
278 278  
279 -
280 280  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
281 281  
282 282  
... ... @@ -295,7 +295,6 @@
295 295  
296 296  ​
297 297  
298 -
299 299  === 2.2.6 Use MQTT protocol to uplink data ===
300 300  
301 301  
... ... @@ -315,10 +315,10 @@
315 315  
316 316  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
317 317  
318 -​ [[image:image-20221021111058-12.png]]
308 +​ [[image:image-20221118103445-7.png]]
319 319  
320 320  
321 -[[image:image-20221021111201-16.png||height="472" width="653"]]
311 +[[image:image-20221118103453-8.png||height="608" width="841"]]
322 322  
323 323  ​
324 324  
... ... @@ -325,7 +325,6 @@
325 325  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.
326 326  
327 327  
328 -
329 329  === 2.2.7 Use TCP protocol to uplink data ===
330 330  
331 331  
... ... @@ -341,7 +341,6 @@
341 341  
342 342  ​
343 343  
344 -
345 345  === 2.2.8 Change Update Interval ===
346 346  
347 347  
... ... @@ -354,63 +354,79 @@
354 354  1.  By default, the device will send an uplink message every 4 hour.
355 355  
356 356  
357 -
358 358  == 2.3  Uplink Payload ==
359 359  
360 360  
361 -The uplink payload includes 123 bytes in total by default.
348 +The uplink payload includes 26 bytes in total by default.
362 362  
363 -Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
350 +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.
364 364  
352 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
365 365  
366 -(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
367 -|=(% 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**
368 -|=(% style="width: 96px;" %)**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" %)[[Contact Status>>||anchor="H2.4.7A0ContactStatus"]]|(% style="width:57px" %)[[Alarm>>||anchor="H2.4.6A0Alarm"]]|(% style="width:91px" %)[[Total pulse>>||anchor="H2.4.8A0Totalpulse"]]
354 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
355 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:30px" %)**2**|(% style="width:30px" %)**2**|(% style="width:70px" %)**1**|(% style="width:30px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**1**|(% style="width:80px" %)**3**|(% style="width:100px" %)**3**
356 +|=(% 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)
369 369  
370 370  (% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
371 -|(% 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**
372 -|(% 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" %)...
359 +|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)(((
360 +**1-32 group**
361 +)))
362 +|(% 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" %)...
373 373  
374 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
375 375  
376 -[[image:image-20221021111201-16.png||height="572" width="792"]]
377 377  
366 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
378 378  
368 +
369 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
370 +|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:66px" %)**8**|(% style="width:40px" %)**2**|(% style="width:46px" %)**2**|(% style="width:70px" %)**1**|(% style="width:54px" %)**1**|(% style="width:55px" %)**1**|(% style="width:57px" %)**1**|(% style="width:86px" %)**3**|(% style="width:82px" %)**3**
371 +|=(% 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)
372 +
373 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
374 +|(% style="width:59px" %)**1**|(% style="width:67px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:66px" %)**1**|(% style="width:92px" %)**3**
375 +|(% 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)
376 +
377 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
378 +|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
379 +**1-32 group**
380 +)))
381 +|(% style="width:102px" %)last open time (pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:88px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
382 +
383 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
384 +
385 +[[image:image-20221117145932-2.png]]
386 +
387 +
379 379  The payload is ASCII string, representative same HEX:
380 380  
381 -**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0c78__(% style="color:#00b0f0" %) __17__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__ (% style="color:#660066" %)__00__ (% style="color:#aaaa40" %)__000009__(% style="color:#663300" %) __000002__ (% style="color:#d60093" %)__6315537b__ (% style="color:#660066" %)__01 00000b 02 0000026 63510fed__ (%%)__0100000e0200000263510f39__ __010000000000000063510e85__ __010000000000000063510d2e__ __010000000000000063510c7a__ __010000000000000063510bc6__ __010000000000000063510954__ __010000000000000063510882 __**
390 +**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 384  
385 385  * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
386 386  
387 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
396 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
388 388  
389 -* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
398 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
390 390  
391 -* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
400 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
392 392  
393 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
402 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
394 394  
395 -* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
404 +* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
396 396  
397 -* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
406 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
398 398  
399 -* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
408 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
400 400  
401 -* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
410 +* (% style="color:#037691" %)**last open time:  **(%%)0x000017 =23
402 402  
403 -* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
412 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
404 404  
405 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
406 406  
407 -* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
408 408  
409 -* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
410 -
411 411  == 2.4  Payload Explanation and Sensor Interface ==
412 412  
413 -
414 414  === 2.4.1  Device ID ===
415 415  
416 416  
... ... @@ -425,20 +425,18 @@
425 425  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
426 426  
427 427  
428 -
429 429  === 2.4.2  Version Info ===
430 430  
431 431  
432 432  Specify the software version: 0x64=100, which means firmware version 1.00.
433 433  
434 -For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
437 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
435 435  
436 436  
437 -
438 438  === 2.4.3  Battery Info ===
439 439  
440 440  
441 -Check the battery voltage for CPN01.
443 +Check the battery voltage for NDS03A.
442 442  
443 443  Ex1: 0x0B45 = 2885mV
444 444  
... ... @@ -445,7 +445,6 @@
445 445  Ex2: 0x0B49 = 2889mV
446 446  
447 447  
448 -
449 449  === 2.4.4  Signal Strength ===
450 450  
451 451  
... ... @@ -464,70 +464,38 @@
464 464  **99**    Not known or not detectable
465 465  
466 466  
468 +=== 2.4.5  Disalarm: (default: 0) ===
467 467  
468 -=== 2.4.5  Calculate Flag ===
469 469  
471 +(% 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.
470 470  
471 -The calculate flag is a user defined field, IoT server can use this filed to handle different meters with different pulse factors. For example, if there are 100 water meters, meter 1~~50 are 1 liter/pulse and meter 51 ~~ 100 has 1.5 liter/pulse.
473 +(% 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.
472 472  
473 -User can set calculate flag to 1 for meter 1~~50 and 2 for meter 51 ~~ 100, So IoT Server can use this field for calculation.
475 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
474 474  
475 -Default value: 0. 
476 476  
477 -Range (6 bits): (b)000000 ~~ (b) 111111
478 +=== 2.4.6  Keep Status & Keep Time ===
478 478  
479 479  
481 +Shows the configure value of Alarm Base on Timeout Feature
480 480  
481 -=== 2.4.6  Alarm ===
482 482  
484 +=== 2.4.7  Timestamp ===
483 483  
484 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
485 485  
487 +Timestamp : 0x6315537b =1662342011
486 486  
487 487  
488 -=== 2.4.7  Contact Status ===
490 +=== 2.4.8  Switch Dual Channel Mode ===
489 489  
490 490  
491 -0: Open
493 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
492 492  
493 -1: Close
494 494  
495 -
496 -
497 -=== 2.4.8  Total pulse ===
498 -
499 -
500 -Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
501 -
502 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
503 -
504 -
505 -
506 -=== 2.4.9  The last open duration ===
507 -
508 -
509 -Dry Contact last open duration.
510 -
511 -Unit: min.
512 -
513 -[[image:image-20221021111346-17.png||height="146" width="770"]]
514 -
515 -
516 -
517 -=== 2.4.10  Timestamp ===
518 -
519 -
520 -Timestamp : 0x6315537b =1662342011
521 -
522 -Convert Unix timestamp to time 2022-9-5 9:40:11.
523 -
524 -**~ **
525 -
526 -
527 527  == 2.5  Downlink Payload ==
528 528  
529 529  
530 -By default, CPN01 prints the downlink payload to console port.
499 +By default, NDS03A prints the downlink payload to console port.
531 531  
532 532  [[image:image-20221021111414-18.png]] ​
533 533  
... ... @@ -544,7 +544,7 @@
544 544  
545 545  * (% style="color:#037691" %)**Reset**
546 546  
547 -If payload = 0x04FF, it will reset the NSE01
516 +If payload = 0x04FF, it will reset the NDS03A
548 548  
549 549  * (% style="color:#037691" %)**INTMOD**
550 550  
... ... @@ -551,20 +551,21 @@
551 551  Downlink Payload: 06000003, Set AT+INTMOD=3
552 552  
553 553  
554 -
555 555  == 2.6  ​LED Indicator ==
556 556  
557 557  
558 -The CPN01 has an internal LED which is to show the status of different states.
526 +The NDS03A has an internal LED which is to show the status of different states.
559 559  
560 560  * When the device starts normally, the LED will light up for 1 second.
561 -* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
529 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
562 562  * For each uplink probe, LED will be on for 500ms.
563 563  
532 +
533 +
564 564  == 2.7  Alarm Base on Timeout ==
565 565  
566 566  
567 -CPN01 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:
537 +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:
568 568  
569 569  
570 570  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -580,17 +580,25 @@
580 580  
581 581  If keep time = 0, Disable Alarm Base on Timeout feature.
582 582  
583 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
553 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
584 584  
585 585  
586 586  (% style="color:blue" %)**AT Command to configure:**
587 587  
588 -(% 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. CPN01 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.
558 +(% style="color:blue" %)**PB14 PIN:**
589 589  
560 +(% 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.
561 +
590 590  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
591 591  
592 592  
565 +(% style="color:blue" %)**PB15 PIN:**
593 593  
567 +(% style="color:#037691" %)**AT+TTRIG2=1,30**
568 +
569 +(% style="color:#037691" %)**AT+TTRIG2=0,0 **
570 +
571 +
594 594  == 2.8  Set debug mode ==
595 595  
596 596  
... ... @@ -612,54 +612,57 @@
612 612  [[image:image-20221021111527-19.png]]
613 613  
614 614  
593 +== 2.10  Count Mod ==
615 615  
616 -== 2.10  Set trigger mode ==
617 617  
596 +(% style="color:blue" %)**AT Command: AT+COUNTMOD**
618 618  
619 -(% style="color:blue" %)**AT Command: AT+TTRMOD**
598 +[[image:image-20221118092935-1.png]]
620 620  
621 -Feature: Set the trigger interrupt mode.
622 622  
623 -[[image:image-20221021111552-20.png]]
601 +== 2.11  Interrupt Pin Channel Mod ==
624 624  
625 625  
604 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
626 626  
627 -== 2.11  Set the calculate flag ==
606 +[[image:image-20221118093144-2.png]]
628 628  
629 629  
630 -Feature: Set the calculate flag
609 +== 2.12 TTRIG1/2 timeout status alarm ==
631 631  
632 -(% style="color:blue" %)**AT Command: AT+CALCFLAG**
633 633  
634 -[[image:image-20221021111711-22.png]]
612 +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.
635 635  
614 +(% style="color:blue" %)**AT Command: AT+TTRALARM**
636 636  
616 +[[image:image-20221118093512-3.png]]
637 637  
638 -== 2.12 Set count number ==
639 639  
619 +== 2.13  Select counting mode ==
640 640  
641 -Feature: Manually set the count number
642 642  
643 -(% style="color:blue" %)**AT Command: AT+SETCNT**
622 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
644 644  
645 -[[image:image-20221021111748-24.png]]
624 +When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
646 646  
626 +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.
647 647  
628 +[[image:image-20221118093658-4.png]]
648 648  
649 -== 2.13  Set the number of data to be uploaded and the recording time ==
650 650  
631 +== 2.14  Set the number of data to be uploaded and the recording time ==
651 651  
633 +
652 652  (% style="color:blue" %)**AT Command:**
653 653  
654 -(% 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)
636 +(% 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)
655 655  
656 -(% style="color:#037691" %)**AT+NOUD=8 ** (%%)~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
638 +(% 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.
657 657  
658 658  
641 +== 2.15  Read or Clear cached data ==
659 659  
660 -== 2.14  Read or Clear cached data ==
661 661  
662 -
663 663  (% style="color:blue" %)**AT Command:**
664 664  
665 665  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -666,27 +666,24 @@
666 666  
667 667  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
668 668  
669 -[[image:image-20221021111810-25.png||height="364" width="797"]]
650 +[[image:image-20221118094227-5.png]]
670 670  
671 671  
653 +== 2.16  ​Firmware Change Log ==
672 672  
673 -== 2.15  ​Firmware Change Log ==
674 674  
656 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
675 675  
676 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
677 -
678 678  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
679 679  
680 680  
661 +== 2.17  ​Battery Analysis ==
681 681  
682 -== 2.16  ​Battery Analysis ==
663 +=== 2.17.1  ​Battery Type ===
683 683  
684 684  
685 -=== 2.16.1  ​Battery Type ===
666 +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.
686 686  
687 -
688 -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.
689 -
690 690  The battery is designed to last for several years depends on the actual use environment and update interval. 
691 691  
692 692  The battery-related documents as below:
... ... @@ -700,10 +700,9 @@
700 700  [[image:image-20221021111911-26.png]] ​
701 701  
702 702  
681 +=== 2.17.2  Power consumption Analyze ===
703 703  
704 -=== 2.16.2  Power consumption Analyze ===
705 705  
706 -
707 707  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.
708 708  
709 709  Instruction to use as below:
... ... @@ -723,21 +723,18 @@
723 723  [[image:1666596205057-567.png]] ​
724 724  
725 725  
703 +=== 2.17.3  ​Battery Note ===
726 726  
727 -=== 2.16.3  ​Battery Note ===
728 728  
729 -
730 730  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.
731 731  
732 732  
709 +=== 2.17.4  Replace the battery ===
733 733  
734 -=== 2.16.4  Replace the battery ===
735 735  
712 +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).
736 736  
737 -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).
738 738  
739 -
740 -
741 741  = 3. ​ Access NB-IoT Module =
742 742  
743 743  
... ... @@ -745,13 +745,11 @@
745 745  
746 746  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/]] 
747 747  
748 -[[image:image-20221021112006-28.png]] ​
722 +[[image:image-20221118094449-6.png]] ​
749 749  
750 750  
751 -
752 752  = 4.  Using the AT Commands =
753 753  
754 -
755 755  == 4.1  Access AT Commands ==
756 756  
757 757  
... ... @@ -798,15 +798,21 @@
798 798  
799 799  AT+ DEBUG   : Enable or Disable debug mode
800 800  
801 -AT+ TTRIG   : Get or Set Alarm Base on Timeout
773 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
802 802  
803 -AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
775 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
804 804  
805 -AT+ CALCFLAG   : Get or Set the calculate flag
777 +AT+COUNTMOD  :  Get or Set the count mode
806 806  
807 -AT+ CLRC   : Clear current door open count
779 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
808 808  
781 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
809 809  
783 +AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
784 +
785 +AT+ CLRC   :  Clear current door open count
786 +
787 +
810 810  (% style="color:blue" %)**COAP Management**      
811 811  
812 812  AT+URI            : Resource parameters
... ... @@ -837,10 +837,8 @@
837 837  AT+PWORD  : Serial Access Password
838 838  
839 839  
840 -
841 841  = ​5.  FAQ =
842 842  
843 -
844 844  == 5.1 ​ How to Upgrade Firmware ==
845 845  
846 846  
... ... @@ -848,13 +848,11 @@
848 848  
849 849  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]]
850 850  
851 -(% 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.**
827 +(% 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.**
852 852  
853 853  
854 -
855 855  = 6.  Trouble Shooting =
856 856  
857 -
858 858  == 6.1  ​Connection problem when uploading firmware ==
859 859  
860 860  
... ... @@ -861,7 +861,6 @@
861 861  (% 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]]
862 862  
863 863  
864 -
865 865  == 6.2  AT Command input doesn't work ==
866 866  
867 867  
... ... @@ -868,26 +868,20 @@
868 868  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.
869 869  
870 870  
871 -
872 872  = 7. ​ Order Info =
873 873  
874 874  
875 -Part Number**:** CPN01
847 +Part Number**:** NDS03A
876 876  
877 877  
878 -
879 879  = 8.  Packing Info =
880 880  
881 881  
882 882  (% style="color:blue" %)**Package Includes**:
883 883  
884 -* CPN01 Open/Close Sensor x 1
885 -* External antenna x 1
855 +* NDS03A Open/Close Door Sensor x 1
886 886  
887 -(% style="color:blue" %)**Dimension and weight**:
888 888  
889 -* Size: 195 x 125 x 55 mm
890 -* Weight:   420g
891 891  
892 892  = 9.  Support =
893 893  
image-20221117150312-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +8.7 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

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0