Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 70.11 >
edited by Xiaoling
on 2022/11/18 11:09
To version < 61.1 >
edited by Xiaoling
on 2022/11/17 15:03
>
Change comment: Uploaded new attachment "image-20221117150312-3.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -9,12 +9,10 @@
9 9  
10 10  **Table of Contents：**
11 11  
12 -{{toc/}}
13 13  
14 14  
15 15  
16 16  
17 -
18 18  = 1.  Introduction =
19 19  
20 20  == 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
... ... @@ -131,6 +131,7 @@
131 131  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]]
132 132  
133 133  
132 +
134 134  === 1.7.2  Jumper JP2(Power ON/OFF) ===
135 135  
136 136  
... ... @@ -137,6 +137,7 @@
137 137  Power on Device when putting this jumper.
138 138  
139 139  
139 +
140 140  === 1.7.3  BOOT MODE / SW1 ===
141 141  
142 142  
... ... @@ -145,6 +145,7 @@
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 +
148 148  === 1.7.4  Reset Button ===
149 149  
150 150  
... ... @@ -151,6 +151,7 @@
151 151  Press to reboot the device.
152 152  
153 153  
155 +
154 154  === 1.7.5  LED ===
155 155  
156 156  
... ... @@ -161,16 +161,18 @@
161 161  2.  Send an uplink packet
162 162  
163 163  
166 +
164 164  == 1.8  Magnet Distance ==
165 165  
166 166  
167 167  (% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
168 168  
169 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
172 +(% style="color:blue" %)**Iron Door:**(%%)**  **30 ~~ 45mm
170 170  
171 171  
172 -= 2.  Use NDS03A to communicate with IoT Server =
173 173  
176 += 2.  Use CPN01 to communicate with IoT Server =
177 +
174 174  == 2.1  How it works ==
175 175  
176 176  
... ... @@ -181,6 +181,7 @@
181 181  [[image:image-20221021110615-5.png]]
182 182  
183 183  
188 +
184 184  == 2.2 ​ Configure NDS03A ==
185 185  
186 186  === 2.2.1 Test Requirement ===
... ... @@ -196,7 +196,9 @@
196 196  
197 197  [[image:image-20221117142300-1.png]]
198 198  
204 + ​
199 199  
206 +
200 200  === 2.2.2 Insert NB-IoT SIM card ===
201 201  
202 202  
... ... @@ -207,6 +207,7 @@
207 207  [[image:image-20221021110745-6.png]] ​
208 208  
209 209  
217 +
210 210  === 2.2.3 Connect USB – TTL to NDS03A and configure it ===
211 211  
212 212  
... ... @@ -250,7 +250,7 @@
250 250  (% 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/]]
251 251  
252 252  
253 -(% style="color:blue" %)**Use below commands in NDS03A:**
261 +(% style="color:blue" %)**Use below commands in CPN01:**
254 254  
255 255  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
256 256  
... ... @@ -263,11 +263,12 @@
263 263  [[image:image-20221021110948-8.png]]
264 264  
265 265  
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.
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.
267 267  
268 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
276 +[[image:image-20221021110956-9.png]] ​
269 269  
270 270  
279 +
271 271  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
272 272  
273 273  
... ... @@ -286,6 +286,7 @@
286 286  
287 287  ​
288 288  
298 +
289 289  === 2.2.6 Use MQTT protocol to uplink data ===
290 290  
291 291  
... ... @@ -305,10 +305,10 @@
305 305  
306 306  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
307 307  
308 -​ [[image:image-20221118103445-7.png]]
318 +​ [[image:image-20221021111058-12.png]]
309 309  
310 310  
311 -[[image:image-20221118103453-8.png||height="608" width="841"]]
321 +[[image:image-20221021111201-16.png||height="472" width="653"]]
312 312  
313 313  ​
314 314  
... ... @@ -315,6 +315,7 @@
315 315  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.
316 316  
317 317  
328 +
318 318  === 2.2.7 Use TCP protocol to uplink data ===
319 319  
320 320  
... ... @@ -330,6 +330,7 @@
330 330  
331 331  ​
332 332  
344 +
333 333  === 2.2.8 Change Update Interval ===
334 334  
335 335  
... ... @@ -342,79 +342,63 @@
342 342  1.  By default, the device will send an uplink message every 4 hour.
343 343  
344 344  
357 +
345 345  == 2.3  Uplink Payload ==
346 346  
347 347  
348 -The uplink payload includes 26 bytes in total by default.
361 +The uplink payload includes 123 bytes in total by default.
349 349  
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.
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.
351 351  
352 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
353 353  
354 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
355 -|=(% 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**
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)
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"]]
357 357  
358 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
359 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)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" %)...
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" %)...
363 363  
374 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
364 364  
376 +[[image:image-20221021111201-16.png||height="572" width="792"]]
365 365  
366 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
367 367  
368 -
369 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
370 -|=(% 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**
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:510px" %)
374 -|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:80px" %)**1**|(% style="width:80px" %)**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:90px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
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:100px" %)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 -
388 388  The payload is ASCII string, representative same HEX:
389 389  
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__(%%)**
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 __**
391 391  
392 392  **where:**
393 393  
394 394  * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
395 395  
396 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
387 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
397 397  
398 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
389 +* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
399 399  
400 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
391 +* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
401 401  
402 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
393 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
403 403  
404 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
395 +* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
405 405  
406 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
397 +* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
407 407  
408 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
399 +* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
409 409  
410 -* (% style="color:#037691" %)**last open time:  **(%%)0x000017 =23
401 +* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
411 411  
412 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
403 +* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
413 413  
405 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
414 414  
407 +* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
415 415  
409 +* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
410 +
416 416  == 2.4  Payload Explanation and Sensor Interface ==
417 417  
413 +
418 418  === 2.4.1  Device ID ===
419 419  
420 420  
... ... @@ -429,18 +429,20 @@
429 429  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
430 430  
431 431  
428 +
432 432  === 2.4.2  Version Info ===
433 433  
434 434  
435 435  Specify the software version: 0x64=100, which means firmware version 1.00.
436 436  
437 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
434 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
438 438  
439 439  
437 +
440 440  === 2.4.3  Battery Info ===
441 441  
442 442  
443 -Check the battery voltage for NDS03A.
441 +Check the battery voltage for CPN01.
444 444  
445 445  Ex1: 0x0B45 = 2885mV
446 446  
... ... @@ -447,6 +447,7 @@
447 447  Ex2: 0x0B49 = 2889mV
448 448  
449 449  
448 +
450 450  === 2.4.4  Signal Strength ===
451 451  
452 452  
... ... @@ -465,38 +465,70 @@
465 465  **99**    Not known or not detectable
466 466  
467 467  
468 -=== 2.4.5  Disalarm: (default: 0) ===
469 469  
468 +=== 2.4.5  Calculate Flag ===
470 470  
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.
472 472  
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.
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.
474 474  
475 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
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.
476 476  
475 +Default value: 0. 
477 477  
478 -=== 2.4.6  Keep Status & Keep Time ===
477 +Range (6 bits): (b)000000 ~~ (b) 111111
479 479  
480 480  
481 -Shows the configure value of Alarm Base on Timeout Feature
482 482  
481 +=== 2.4.6  Alarm ===
483 483  
484 -=== 2.4.7  Timestamp ===
485 485  
484 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
486 486  
487 -Timestamp : 0x6315537b =1662342011
488 488  
489 489  
490 -=== 2.4.8  Switch Dual Channel Mode ===
488 +=== 2.4.7  Contact Status ===
491 491  
492 492  
493 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
491 +0: Open
494 494  
493 +1: Close
495 495  
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 +
496 496  == 2.5  Downlink Payload ==
497 497  
498 498  
499 -By default, NDS03A prints the downlink payload to console port.
530 +By default, CPN01 prints the downlink payload to console port.
500 500  
501 501  [[image:image-20221021111414-18.png]] ​
502 502  
... ... @@ -513,7 +513,7 @@
513 513  
514 514  * (% style="color:#037691" %)**Reset**
515 515  
516 -If payload = 0x04FF, it will reset the NDS03A
547 +If payload = 0x04FF, it will reset the NSE01
517 517  
518 518  * (% style="color:#037691" %)**INTMOD**
519 519  
... ... @@ -520,21 +520,20 @@
520 520  Downlink Payload: 06000003, Set AT+INTMOD=3
521 521  
522 522  
554 +
523 523  == 2.6  ​LED Indicator ==
524 524  
525 525  
526 -The NDS03A has an internal LED which is to show the status of different states.
558 +The CPN01 has an internal LED which is to show the status of different states.
527 527  
528 528  * When the device starts normally, the LED will light up for 1 second.
529 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
561 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
530 530  * For each uplink probe, LED will be on for 500ms.
531 531  
532 -
533 -
534 534  == 2.7  Alarm Base on Timeout ==
535 535  
536 536  
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:
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:
538 538  
539 539  
540 540  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -550,25 +550,17 @@
550 550  
551 551  If keep time = 0, Disable Alarm Base on Timeout feature.
552 552  
553 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
583 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
554 554  
555 555  
556 556  (% style="color:blue" %)**AT Command to configure:**
557 557  
558 -(% style="color:blue" %)**PB14 PIN:**
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.
559 559  
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 -
562 562  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
563 563  
564 564  
565 -(% style="color:blue" %)**PB15 PIN:**
566 566  
567 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
568 -
569 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
570 -
571 -
572 572  == 2.8  Set debug mode ==
573 573  
574 574  
... ... @@ -590,57 +590,54 @@
590 590  [[image:image-20221021111527-19.png]]
591 591  
592 592  
593 -== 2.10  Count Mod ==
594 594  
616 +== 2.10  Set trigger mode ==
595 595  
596 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
597 597  
598 -[[image:image-20221118092935-1.png]]
619 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
599 599  
621 +Feature: Set the trigger interrupt mode.
600 600  
601 -== 2.11  Interrupt Pin Channel Mod ==
623 +[[image:image-20221021111552-20.png]]
602 602  
603 603  
604 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
605 605  
606 -[[image:image-20221118093144-2.png]]
627 +== 2.11  Set the calculate flag ==
607 607  
608 608  
609 -== 2.12 TTRIG1/2 timeout status alarm ==
630 +Feature: Set the calculate flag
610 610  
632 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
611 611  
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.
634 +[[image:image-20221021111711-22.png]]
613 613  
614 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
615 615  
616 -[[image:image-20221118093512-3.png]]
617 617  
638 +== 2.12 Set count number ==
618 618  
619 -== 2.13  Select counting mode ==
620 620  
641 +Feature: Manually set the count number
621 621  
622 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
643 +(% style="color:blue" %)**AT Command: AT+SETCNT**
623 623  
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.
645 +[[image:image-20221021111748-24.png]]
625 625  
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.
627 627  
628 -[[image:image-20221118093658-4.png]]
629 629  
649 +== 2.13  Set the number of data to be uploaded and the recording time ==
630 630  
631 -== 2.14  Set the number of data to be uploaded and the recording time ==
632 632  
633 -
634 634  (% style="color:blue" %)**AT Command:**
635 635  
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)
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)
637 637  
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.
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.
639 639  
640 640  
641 -== 2.15  Read or Clear cached data ==
642 642  
660 +== 2.14  Read or Clear cached data ==
643 643  
662 +
644 644  (% style="color:blue" %)**AT Command:**
645 645  
646 646  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -647,24 +647,27 @@
647 647  
648 648  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
649 649  
650 -[[image:image-20221118094227-5.png]]
669 +[[image:image-20221021111810-25.png||height="364" width="797"]]
651 651  
652 652  
653 -== 2.16  ​Firmware Change Log ==
654 654  
673 +== 2.15  ​Firmware Change Log ==
655 655  
656 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
657 657  
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 +
658 658  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
659 659  
660 660  
661 -== 2.17  ​Battery Analysis ==
662 662  
663 -=== 2.17.1  ​Battery Type ===
682 +== 2.16  ​Battery Analysis ==
664 664  
665 665  
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.
685 +=== 2.16.1  ​Battery Type ===
667 667  
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 +
668 668  The battery is designed to last for several years depends on the actual use environment and update interval. 
669 669  
670 670  The battery-related documents as below:
... ... @@ -678,9 +678,10 @@
678 678  [[image:image-20221021111911-26.png]] ​
679 679  
680 680  
681 -=== 2.17.2  Power consumption Analyze ===
682 682  
704 +=== 2.16.2  Power consumption Analyze ===
683 683  
706 +
684 684  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.
685 685  
686 686  Instruction to use as below:
... ... @@ -700,18 +700,21 @@
700 700  [[image:1666596205057-567.png]] ​
701 701  
702 702  
703 -=== 2.17.3  ​Battery Note ===
704 704  
727 +=== 2.16.3  ​Battery Note ===
705 705  
729 +
706 706  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.
707 707  
708 708  
709 -=== 2.17.4  Replace the battery ===
710 710  
734 +=== 2.16.4  Replace the battery ===
711 711  
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).
713 713  
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).
714 714  
739 +
740 +
715 715  = 3. ​ Access NB-IoT Module =
716 716  
717 717  
... ... @@ -719,11 +719,13 @@
719 719  
720 720  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/]] 
721 721  
722 -[[image:image-20221118094449-6.png]] ​
748 +[[image:image-20221021112006-28.png]] ​
723 723  
724 724  
751 +
725 725  = 4.  Using the AT Commands =
726 726  
754 +
727 727  == 4.1  Access AT Commands ==
728 728  
729 729  
... ... @@ -770,21 +770,15 @@
770 770  
771 771  AT+ DEBUG   : Enable or Disable debug mode
772 772  
773 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
801 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
774 774  
775 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
803 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
776 776  
777 -AT+COUNTMOD  :  Get or Set the count mode
805 +AT+ CALCFLAG   : Get or Set the calculate flag
778 778  
779 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
807 +AT+ CLRC   : Clear current door open count
780 780  
781 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
782 782  
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 -
788 788  (% style="color:blue" %)**COAP Management**      
789 789  
790 790  AT+URI            : Resource parameters
... ... @@ -815,8 +815,10 @@
815 815  AT+PWORD  : Serial Access Password
816 816  
817 817  
840 +
818 818  = ​5.  FAQ =
819 819  
843 +
820 820  == 5.1 ​ How to Upgrade Firmware ==
821 821  
822 822  
... ... @@ -824,11 +824,13 @@
824 824  
825 825  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]]
826 826  
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.**
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.**
828 828  
829 829  
854 +
830 830  = 6.  Trouble Shooting =
831 831  
857 +
832 832  == 6.1  ​Connection problem when uploading firmware ==
833 833  
834 834  
... ... @@ -835,6 +835,7 @@
835 835  (% 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]]
836 836  
837 837  
864 +
838 838  == 6.2  AT Command input doesn't work ==
839 839  
840 840  
... ... @@ -841,20 +841,26 @@
841 841  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.
842 842  
843 843  
871 +
844 844  = 7. ​ Order Info =
845 845  
846 846  
847 -Part Number**:** NDS03A
875 +Part Number**:** CPN01
848 848  
849 849  
878 +
850 850  = 8.  Packing Info =
851 851  
852 852  
853 853  (% style="color:blue" %)**Package Includes**:
854 854  
855 -* NDS03A Open/Close Door Sensor x 1
884 +* CPN01 Open/Close Sensor x 1
885 +* External antenna x 1
856 856  
887 +(% style="color:blue" %)**Dimension and weight**:
857 857  
889 +* Size: 195 x 125 x 55 mm
890 +* Weight:   420g
858 858  
859 859  = 9.  Support =
860 860  
image-20221118092935-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.5 KB
Content
image-20221118093658-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -12.7 KB
Content
image-20221118094227-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.2 KB
Content
image-20221118094449-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.5 KB
Content
image-20221118103445-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.5 KB
Content

Applications

Navigation

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