Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 58.4 >
edited by Xiaoling
on 2022/11/17 14:02
To version < 66.2 >
edited by Xiaoling
on 2022/11/18 09:43
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -15,7 +15,6 @@
15 15  
16 16  = 1.  Introduction =
17 17  
18 -
19 19  == 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
20 20  
21 21  
... ... @@ -71,8 +71,6 @@
71 71  * Micro SIM card slot for NB-IoT SIM
72 72  * 8500mAh Battery for long-term use
73 73  
74 -
75 -
76 76  == 1.3  Storage & Operation ==
77 77  
78 78  
... ... @@ -116,8 +116,6 @@
116 116  * - B20 @H-FDD: 800MHz
117 117  * - B28 @H-FDD: 700MHz
118 118  
119 -
120 -
121 121  == 1.7  Pin Definitions and Switch ==
122 122  
123 123  
... ... @@ -170,39 +170,37 @@
170 170  
171 171  (% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
172 172  
173 -(% style="color:blue" %)**Iron Door:**(%%)**  **30 ~~ 45mm
168 +(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
174 174  
175 175  
176 176  
177 177  = 2.  Use CPN01 to communicate with IoT Server =
178 178  
179 -
180 180  == 2.1  How it works ==
181 181  
182 182  
183 -The CPN01 is equipped with an NB-IoT module, the pre-loaded firmware in CPN01 will get (% style="color:blue" %)**Open/Close Event or Count**(%%) from sensor and send the value to the NB-IoT network. The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01.
177 +In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.
184 184  
185 -The diagram below shows the working flow in the default firmware of CPN01:
179 +The diagram below shows the working flow in the default firmware of NDS03A:
186 186  
187 187  [[image:image-20221021110615-5.png]]
188 188  
189 189  
190 190  
191 -== 2.2 ​ Configure CPN01 ==
185 +== 2.2 ​ Configure NDS03A ==
192 192  
193 -
194 194  === 2.2.1 Test Requirement ===
195 195  
196 196  
197 -To use CPN01 in your city, make sure to meet below requirements:
190 +To use NDS03A in your city, make sure to meet below requirements:
198 198  
199 199  * Your local operator has already distributed an NB-IoT Network.
200 -* The local NB-IoT network used the band that CPN01 supports.
193 +* The local NB-IoT network used the band that NDS03A supports.
201 201  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
202 202  
203 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The CPN01 will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
196 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDS03A will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
204 204  
205 -[[image:image-20221023000439-3.png]]
198 +[[image:image-20221117142300-1.png]]
206 206  
207 207   ​
208 208  
... ... @@ -218,10 +218,10 @@
218 218  
219 219  
220 220  
221 -=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
214 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
222 222  
223 223  
224 -User need to configure CPN01 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. CPN01 support AT Commands, user can use a USB to TTL adapter to connect to CPN01 and use AT Commands to configure it, as below.
217 +User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
225 225  
226 226  (% style="color:blue" %)**Connection:**
227 227  
... ... @@ -244,11 +244,11 @@
244 244  
245 245  * Flow Control: (% style="color:red" %)**None**
246 246  
247 -Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
240 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
248 248  
249 249  ​[[image:image-20221021110817-7.png]]
250 250  
251 -CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
244 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
252 252  
253 253  
254 254  (% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
... ... @@ -274,7 +274,7 @@
274 274  [[image:image-20221021110948-8.png]]
275 275  
276 276  
277 -After configuring the server address and (% style="color:green" %)**reset CPN01**(%%) (via AT+ATZ ), CPN01 will start to uplink sensor values to the CoAP server.
270 +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.
278 278  
279 279  [[image:image-20221021110956-9.png]] ​
280 280  
... ... @@ -350,11 +350,11 @@
350 350  
351 351  User can use below command to change the (% style="color:blue" %)**uplink interval**.
352 352  
353 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
346 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
354 354  
355 355  (% style="color:red" %)**NOTE:**
356 356  
357 -1.  By default, the device will send an uplink message every 1 hour.
350 +1.  By default, the device will send an uplink message every 4 hour.
358 358  
359 359  
360 360  
... ... @@ -361,27 +361,47 @@
361 361  == 2.3  Uplink Payload ==
362 362  
363 363  
364 -The uplink payload includes 123 bytes in total by default.
357 +The uplink payload includes 26 bytes in total by default.
365 365  
366 -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.
359 +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.
367 367  
361 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
368 368  
369 -(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
370 -|=(% 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**
371 -|=(% 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"]]
363 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
364 +|=(% scope="row" style="width: 93px;" %)**Size(bytes)**|(% style="width:67px" %)**8**|(% style="width:40px" %)**2**|(% style="width:45px" %)**2**|(% style="width:75px" %)**1**|(% style="width:54px" %)**1**|(% style="width:62px" %)**1**|(% style="width:60px" %)**1**|(% style="width:94px" %)**3**|(% style="width:93px" %)**3**
365 +|=(% 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.4.6A0Alarm"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
372 372  
373 373  (% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
374 -|(% 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**
375 -|(% 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" %)...
368 +|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)(((
369 +**1-32 group**
370 +)))
371 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% 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" %)...
376 376  
377 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
373 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
378 378  
379 -[[image:image-20221021111201-16.png||height="572" width="792"]]
380 380  
376 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
377 +|=(% 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**
378 +|=(% 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|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.4.6A0Alarm"]]|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
381 381  
380 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
381 +|(% 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**
382 +|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPN01-%20NB-IoT%20Outdoor%20OpenClose%20Dry%20Contact%20Sensor%C2%A0User%20Manual/#H2.4.7A0ContactStatus]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)Time stamp|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
383 +
384 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
385 +|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
386 +**1-32 group**
387 +)))
388 +|(% 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|(% style="width:87px" %)...
389 +
390 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
391 +
392 +[[image:image-20221117145932-2.png]]
393 +
394 +
382 382  The payload is ASCII string, representative same HEX:
383 383  
384 -**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 __**
397 +**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__(%%)**
385 385  
386 386  **where:**
387 387  
... ... @@ -389,28 +389,22 @@
389 389  
390 390  * (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
391 391  
392 -* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
405 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
393 393  
394 -* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
407 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
395 395  
396 396  * (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
397 397  
398 -* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
411 +* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0
399 399  
400 -* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
413 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
401 401  
402 -* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
415 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
403 403  
404 -* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
417 +* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
405 405  
406 -* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
419 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
407 407  
408 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
409 -
410 -* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
411 -
412 -* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
413 -
414 414  == 2.4  Payload Explanation and Sensor Interface ==
415 415  
416 416  
... ... @@ -428,20 +428,18 @@
428 428  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
429 429  
430 430  
431 -
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 CPN01 with firmware version 1.0.0.
443 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
438 438  
439 439  
440 -
441 441  === 2.4.3  Battery Info ===
442 442  
443 443  
444 -Check the battery voltage for CPN01.
449 +Check the battery voltage for NDS03A.
445 445  
446 446  Ex1: 0x0B45 = 2885mV
447 447  
... ... @@ -448,7 +448,6 @@
448 448  Ex2: 0x0B49 = 2889mV
449 449  
450 450  
451 -
452 452  === 2.4.4  Signal Strength ===
453 453  
454 454  
... ... @@ -467,70 +467,39 @@
467 467  **99**    Not known or not detectable
468 468  
469 469  
474 +=== 2.4.5  Disalarm: (default: 0) ===
470 470  
471 -=== 2.4.5  Calculate Flag ===
472 472  
477 +(% 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.
473 473  
474 -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.
479 +(% 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.
475 475  
476 -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.
481 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
477 477  
478 -Default value: 0. 
479 479  
480 -Range (6 bits): (b)000000 ~~ (b) 111111
484 +=== 2.4.6  Keep Status & Keep Time ===
481 481  
482 482  
487 +Shows the configure value of Alarm Base on Timeout Feature
483 483  
484 -=== 2.4.6  Alarm ===
485 485  
490 +=== 2.4.7  Timestamp ===
486 486  
487 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
488 488  
493 +Timestamp : 0x6315537b =1662342011
489 489  
490 490  
491 -=== 2.4.7  Contact Status ===
492 492  
497 +=== 2.4.8  Switch Dual Channel Mode ===
493 493  
494 -0: Open
495 495  
496 -1: Close
500 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
497 497  
498 498  
499 -
500 -=== 2.4.8  Total pulse ===
501 -
502 -
503 -Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
504 -
505 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
506 -
507 -
508 -
509 -=== 2.4.9  The last open duration ===
510 -
511 -
512 -Dry Contact last open duration.
513 -
514 -Unit: min.
515 -
516 -[[image:image-20221021111346-17.png||height="146" width="770"]]
517 -
518 -
519 -
520 -=== 2.4.10  Timestamp ===
521 -
522 -
523 -Timestamp : 0x6315537b =1662342011
524 -
525 -Convert Unix timestamp to time 2022-9-5 9:40:11.
526 -
527 -**~ **
528 -
529 -
530 530  == 2.5  Downlink Payload ==
531 531  
532 532  
533 -By default, CPN01 prints the downlink payload to console port.
506 +By default, NDS03A prints the downlink payload to console port.
534 534  
535 535  [[image:image-20221021111414-18.png]] ​
536 536  
... ... @@ -547,7 +547,7 @@
547 547  
548 548  * (% style="color:#037691" %)**Reset**
549 549  
550 -If payload = 0x04FF, it will reset the NSE01
523 +If payload = 0x04FF, it will reset the NDS03A
551 551  
552 552  * (% style="color:#037691" %)**INTMOD**
553 553  
... ... @@ -558,16 +558,17 @@
558 558  == 2.6  ​LED Indicator ==
559 559  
560 560  
561 -The CPN01 has an internal LED which is to show the status of different states.
534 +The NDS03A has an internal LED which is to show the status of different states.
562 562  
563 563  * When the device starts normally, the LED will light up for 1 second.
564 564  * After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
565 565  * For each uplink probe, LED will be on for 500ms.
566 566  
540 +
567 567  == 2.7  Alarm Base on Timeout ==
568 568  
569 569  
570 -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:
544 +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:
571 571  
572 572  
573 573  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -583,17 +583,25 @@
583 583  
584 584  If keep time = 0, Disable Alarm Base on Timeout feature.
585 585  
586 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
560 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
587 587  
588 588  
589 589  (% style="color:blue" %)**AT Command to configure:**
590 590  
565 +(% style="color:blue" %)**PB14 PIN:**
566 +
591 591  (% 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.
592 592  
593 593  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
594 594  
595 595  
572 +(% style="color:blue" %)**PB15 PIN:**
596 596  
574 +(% style="color:#037691" %)**AT+TTRIG2=1,30**
575 +
576 +(% style="color:#037691" %)**AT+TTRIG2=0,0 **
577 +
578 +
597 597  == 2.8  Set debug mode ==
598 598  
599 599  
... ... @@ -616,64 +616,73 @@
616 616  
617 617  
618 618  
619 -== 2.10  Set trigger mode ==
601 +== 2.10  Count Mod ==
620 620  
621 621  
622 -(% style="color:blue" %)**AT Command: AT+TTRMOD**
604 +(% style="color:blue" %)**AT Command: AT+COUNTMOD**
623 623  
624 -Feature: Set the trigger interrupt mode.
606 +[[image:image-20221118092935-1.png]]
625 625  
626 -[[image:image-20221021111552-20.png]]
627 627  
628 628  
610 +== 2.11  Interrupt Pin Channel Mod ==
629 629  
630 -== 2.11  Set the calculate flag ==
631 631  
613 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
632 632  
633 -Feature: Set the calculate flag
615 +[[image:image-20221118093144-2.png]]
634 634  
635 -(% style="color:blue" %)**AT Command: AT+CALCFLAG**
636 636  
637 -[[image:image-20221021111711-22.png]]
638 638  
619 +== 2.12 TTRIG1/2 timeout status alarm ==
639 639  
640 640  
641 -== 2.12 Set count number ==
622 +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.
642 642  
624 +(% style="color:blue" %)**AT Command: AT+TTRALARM**
643 643  
644 -Feature: Manually set the count number
626 +[[image:image-20221118093512-3.png]]
645 645  
646 -(% style="color:blue" %)**AT Command: AT+SETCNT**
647 647  
648 -[[image:image-20221021111748-24.png]]
649 649  
630 +== 2.13  Select counting mode ==
650 650  
651 651  
652 -== 2.13  Set the number of data to be uploaded and the recording time ==
633 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
653 653  
635 +When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
654 654  
655 -(% style="color:blue" %)**AT Command:**
637 +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.
656 656  
657 -(% 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)
639 +[[image:image-20221118093658-4.png]]
658 658  
659 -(% 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.
660 660  
661 661  
662 662  
663 -== 2.14  Read or Clear cached data ==
644 +== 2.14  Set the number of data to be uploaded and the recording time ==
664 664  
665 665  
666 666  (% style="color:blue" %)**AT Command:**
667 667  
649 +(% 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)
650 +
651 +(% 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.
652 +
653 +
654 +== 2.15  Read or Clear cached data ==
655 +
656 +
657 +(% style="color:blue" %)**AT Command:**
658 +
668 668  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
669 669  
670 670  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
671 671  
672 -[[image:image-20221021111810-25.png||height="364" width="797"]]
663 +[[image:image-20221118094227-5.png]]
673 673  
674 674  
675 675  
676 -== 2.15  ​Firmware Change Log ==
667 +== 2.16  ​Firmware Change Log ==
677 677  
678 678  
679 679  Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
image-20221117142300-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +51.9 KB
Content
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

Applications

Navigation

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