Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 53.2 >
edited by Xiaoling
on 2022/11/17 11:08
To version < 67.2 >
edited by Xiaoling
on 2022/11/18 09:51
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -15,32 +15,43 @@
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  
22 22  (((
23 -The Dragino NDS03A is an Open/Close NB-IoT Door Sensor. It detects door open/close status and uplinks to IoT server via NB-IoT network. NDS03A can connect two door sensors.user can see the door status, open duration, open counts in the IoT Server.
22 +The Dragino NDS03A is an (% style="color:blue" %)**Open/Close NB-IoT Door Sensor**(%%). It detects door (% style="color:blue" %)**open/close status**(%%) and (% style="color:blue" %)**uplinks**(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server.
23 +)))
24 24  
25 -The NDS03A will send periodically data every 4 hours as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically.
25 +(((
26 +The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically.
27 +)))
26 26  
27 -NDS03A has a Datalog feature, it will record the open/close event and the user can retrieve the history from NB-IoT.
29 +(((
30 +NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT.
31 +)))
28 28  
29 -NDS03A has the open alarm feature, user can set this feature so the device will send an alarm if the door has been open for a certain time.
33 +(((
34 +NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time.
35 +)))
30 30  
37 +(((
31 31  NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
32 32  )))
33 33  
34 34  (((
35 -NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
36 -\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
37 -\\CPN01 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
38 -\\To use CPN01, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that CPN01 supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into CPN01 to get NB-IoT network connection.
42 +NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technologyTCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
39 39  )))
40 40  
41 -​
45 +(((
46 +NDS03A is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
47 +)))
42 42  
49 +(((
50 +To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection.
51 +)))
43 43  
53 +
54 +
44 44  == ​1.2  Features ==
45 45  
46 46  
... ... @@ -48,7 +48,7 @@
48 48  * Open/Close detect
49 49  * Open/Close statistics
50 50  * Monitor Battery Level
51 -* Uplink on periodically and open/close event
62 +* connect two door sensors
52 52  * Datalog feature
53 53  * Uplink periodically
54 54  * Downlink to change configure
... ... @@ -59,52 +59,49 @@
59 59  * Micro SIM card slot for NB-IoT SIM
60 60  * 8500mAh Battery for long-term use
61 61  
73 +== 1.3  Storage & Operation ==
62 62  
63 -== 1.3  Specification ==
64 64  
76 +Temperature -40°C to +85°C
65 65  
66 -(% style="color:blue" %)**Common DC Characteristics:**
67 67  
68 -* Supply Voltage: 2.1v ~~ 3.6v
69 -* Operating Temperature: -40 ~~ 85°C
79 +== 1.4  Mechanical ==
70 70  
71 -(% style="color:blue" %)**NB-IoT Spec:**
72 72  
73 -* - B1 @H-FDD: 2100MHz
74 -* - B3 @H-FDD: 1800MHz
75 -* - B8 @H-FDD: 900MHz
76 -* - B5 @H-FDD: 850MHz
77 -* - B20 @H-FDD: 800MHz
78 -* - B28 @H-FDD: 700MHz
82 +[[image:image-20221117114937-4.png]]
79 79  
80 80  
81 -== 1.4  Installation ==
85 +[[image:image-20221117114949-5.png]]
82 82  
83 83  
84 -Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
88 +[[image:image-20221117115010-6.png]]
85 85  
86 -[[image:image-20221021110329-1.png]]
87 87  
88 88  
89 -[[image:image-20221022234602-2.png||height="288" width="922"]]
92 +== 1.5 ​ Applications ==
90 90  
91 91  
95 +[[image:image-20221117114842-3.png]]
92 92  
93 -== 1.5 ​ Applications ==
94 94  
95 95  
96 -* Open/Close Detection
97 -* Pulse meter application
98 -* Dry Contact Detection
99 +== 1.6  Specification ==
99 99  
100 100  
101 -== 1.6  Mechanical ==
102 +(% style="color:blue" %)**Common DC Characteristics:**
102 102  
104 +* Supply Voltage: 2.1v ~~ 3.6v
105 +* Operating Temperature: -40 ~~ 85°C
103 103  
104 -​[[image:image-20221021110415-3.png]]
107 +(% style="color:blue" %)**NB-IoT Spec:**
105 105  
109 +* - B1 @H-FDD: 2100MHz
110 +* - B3 @H-FDD: 1800MHz
111 +* - B8 @H-FDD: 900MHz
112 +* - B5 @H-FDD: 850MHz
113 +* - B20 @H-FDD: 800MHz
114 +* - B28 @H-FDD: 700MHz
106 106  
107 -
108 108  == 1.7  Pin Definitions and Switch ==
109 109  
110 110  
... ... @@ -114,7 +114,7 @@
114 114  === 1.7.1  Pin Definition ===
115 115  
116 116  
117 -CPN01 is pre-configured to connect to two external wires. The other pins are not used. If user wants to know more about other pins, please refer to the **[[LSN50v2 User Manual>>doc:Main.User Manual for LoRaWAN End Nodes.LSN50 & LSN50-V2 - LoRaWAN Sensor Node User Manual.WebHome]]**.
125 +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]]
118 118  
119 119  
120 120  
... ... @@ -152,35 +152,42 @@
152 152  
153 153  
154 154  
155 -= 2.  Use CPN01 to communicate with IoT Server =
163 +== 1.8  Magnet Distance ==
156 156  
157 157  
166 +(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
167 +
168 +(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
169 +
170 +
171 +
172 += 2.  Use CPN01 to communicate with IoT Server =
173 +
158 158  == 2.1  How it works ==
159 159  
160 160  
161 -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.
162 162  
163 -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:
164 164  
165 165  [[image:image-20221021110615-5.png]]
166 166  
167 167  
168 168  
169 -== 2.2 ​ Configure CPN01 ==
185 +== 2.2 ​ Configure NDS03A ==
170 170  
171 -
172 172  === 2.2.1 Test Requirement ===
173 173  
174 174  
175 -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:
176 176  
177 177  * Your local operator has already distributed an NB-IoT Network.
178 -* The local NB-IoT network used the band that CPN01 supports.
193 +* The local NB-IoT network used the band that NDS03A supports.
179 179  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
180 180  
181 -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.
182 182  
183 -[[image:image-20221023000439-3.png]]
198 +[[image:image-20221117142300-1.png]]
184 184  
185 185   ​
186 186  
... ... @@ -196,10 +196,10 @@
196 196  
197 197  
198 198  
199 -=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
214 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
200 200  
201 201  
202 -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.
203 203  
204 204  (% style="color:blue" %)**Connection:**
205 205  
... ... @@ -222,11 +222,11 @@
222 222  
223 223  * Flow Control: (% style="color:red" %)**None**
224 224  
225 -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**(%%).
226 226  
227 227  ​[[image:image-20221021110817-7.png]]
228 228  
229 -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.
230 230  
231 231  
232 232  (% 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]]
... ... @@ -252,7 +252,7 @@
252 252  [[image:image-20221021110948-8.png]]
253 253  
254 254  
255 -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.
256 256  
257 257  [[image:image-20221021110956-9.png]] ​
258 258  
... ... @@ -328,11 +328,11 @@
328 328  
329 329  User can use below command to change the (% style="color:blue" %)**uplink interval**.
330 330  
331 -* (% 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)
332 332  
333 333  (% style="color:red" %)**NOTE:**
334 334  
335 -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.
336 336  
337 337  
338 338  
... ... @@ -339,27 +339,47 @@
339 339  == 2.3  Uplink Payload ==
340 340  
341 341  
342 -The uplink payload includes 123 bytes in total by default.
357 +The uplink payload includes 26 bytes in total by default.
343 343  
344 -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.
345 345  
361 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
346 346  
347 -(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
348 -|=(% 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**
349 -|=(% 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)
350 350  
351 351  (% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
352 -|(% 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**
353 -|(% 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" %)...
354 354  
355 -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:**
356 356  
357 -[[image:image-20221021111201-16.png||height="572" width="792"]]
358 358  
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)
359 359  
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 +
360 360  The payload is ASCII string, representative same HEX:
361 361  
362 -**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__(%%)**
363 363  
364 364  **where:**
365 365  
... ... @@ -367,28 +367,22 @@
367 367  
368 368  * (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
369 369  
370 -* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
405 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
371 371  
372 -* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
407 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
373 373  
374 374  * (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
375 375  
376 -* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
411 +* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0
377 377  
378 -* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
413 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
379 379  
380 -* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
415 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
381 381  
382 -* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
417 +* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
383 383  
384 -* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
419 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
385 385  
386 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
387 -
388 -* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
389 -
390 -* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
391 -
392 392  == 2.4  Payload Explanation and Sensor Interface ==
393 393  
394 394  
... ... @@ -406,20 +406,18 @@
406 406  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
407 407  
408 408  
409 -
410 410  === 2.4.2  Version Info ===
411 411  
412 412  
413 413  Specify the software version: 0x64=100, which means firmware version 1.00.
414 414  
415 -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.
416 416  
417 417  
418 -
419 419  === 2.4.3  Battery Info ===
420 420  
421 421  
422 -Check the battery voltage for CPN01.
449 +Check the battery voltage for NDS03A.
423 423  
424 424  Ex1: 0x0B45 = 2885mV
425 425  
... ... @@ -426,7 +426,6 @@
426 426  Ex2: 0x0B49 = 2889mV
427 427  
428 428  
429 -
430 430  === 2.4.4  Signal Strength ===
431 431  
432 432  
... ... @@ -445,70 +445,39 @@
445 445  **99**    Not known or not detectable
446 446  
447 447  
474 +=== 2.4.5  Disalarm: (default: 0) ===
448 448  
449 -=== 2.4.5  Calculate Flag ===
450 450  
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.
451 451  
452 -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.
453 453  
454 -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.
455 455  
456 -Default value: 0. 
457 457  
458 -Range (6 bits): (b)000000 ~~ (b) 111111
484 +=== 2.4.6  Keep Status & Keep Time ===
459 459  
460 460  
487 +Shows the configure value of Alarm Base on Timeout Feature
461 461  
462 -=== 2.4.6  Alarm ===
463 463  
490 +=== 2.4.7  Timestamp ===
464 464  
465 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
466 466  
493 +Timestamp : 0x6315537b =1662342011
467 467  
468 468  
469 -=== 2.4.7  Contact Status ===
470 470  
497 +=== 2.4.8  Switch Dual Channel Mode ===
471 471  
472 -0: Open
473 473  
474 -1: Close
500 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
475 475  
476 476  
477 -
478 -=== 2.4.8  Total pulse ===
479 -
480 -
481 -Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
482 -
483 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
484 -
485 -
486 -
487 -=== 2.4.9  The last open duration ===
488 -
489 -
490 -Dry Contact last open duration.
491 -
492 -Unit: min.
493 -
494 -[[image:image-20221021111346-17.png||height="146" width="770"]]
495 -
496 -
497 -
498 -=== 2.4.10  Timestamp ===
499 -
500 -
501 -Timestamp : 0x6315537b =1662342011
502 -
503 -Convert Unix timestamp to time 2022-9-5 9:40:11.
504 -
505 -**~ **
506 -
507 -
508 508  == 2.5  Downlink Payload ==
509 509  
510 510  
511 -By default, CPN01 prints the downlink payload to console port.
506 +By default, NDS03A prints the downlink payload to console port.
512 512  
513 513  [[image:image-20221021111414-18.png]] ​
514 514  
... ... @@ -525,7 +525,7 @@
525 525  
526 526  * (% style="color:#037691" %)**Reset**
527 527  
528 -If payload = 0x04FF, it will reset the NSE01
523 +If payload = 0x04FF, it will reset the NDS03A
529 529  
530 530  * (% style="color:#037691" %)**INTMOD**
531 531  
... ... @@ -536,16 +536,17 @@
536 536  == 2.6  ​LED Indicator ==
537 537  
538 538  
539 -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.
540 540  
541 541  * When the device starts normally, the LED will light up for 1 second.
542 542  * After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
543 543  * For each uplink probe, LED will be on for 500ms.
544 544  
540 +
545 545  == 2.7  Alarm Base on Timeout ==
546 546  
547 547  
548 -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:
549 549  
550 550  
551 551  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -561,17 +561,25 @@
561 561  
562 562  If keep time = 0, Disable Alarm Base on Timeout feature.
563 563  
564 -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.
565 565  
566 566  
567 567  (% style="color:blue" %)**AT Command to configure:**
568 568  
565 +(% style="color:blue" %)**PB14 PIN:**
566 +
569 569  (% 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.
570 570  
571 571  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
572 572  
573 573  
572 +(% style="color:blue" %)**PB15 PIN:**
574 574  
574 +(% style="color:#037691" %)**AT+TTRIG2=1,30**
575 +
576 +(% style="color:#037691" %)**AT+TTRIG2=0,0 **
577 +
578 +
575 575  == 2.8  Set debug mode ==
576 576  
577 577  
... ... @@ -594,64 +594,73 @@
594 594  
595 595  
596 596  
597 -== 2.10  Set trigger mode ==
601 +== 2.10  Count Mod ==
598 598  
599 599  
600 -(% style="color:blue" %)**AT Command: AT+TTRMOD**
604 +(% style="color:blue" %)**AT Command: AT+COUNTMOD**
601 601  
602 -Feature: Set the trigger interrupt mode.
606 +[[image:image-20221118092935-1.png]]
603 603  
604 -[[image:image-20221021111552-20.png]]
605 605  
606 606  
610 +== 2.11  Interrupt Pin Channel Mod ==
607 607  
608 -== 2.11  Set the calculate flag ==
609 609  
613 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
610 610  
611 -Feature: Set the calculate flag
615 +[[image:image-20221118093144-2.png]]
612 612  
613 -(% style="color:blue" %)**AT Command: AT+CALCFLAG**
614 614  
615 -[[image:image-20221021111711-22.png]]
616 616  
619 +== 2.12 TTRIG1/2 timeout status alarm ==
617 617  
618 618  
619 -== 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.
620 620  
624 +(% style="color:blue" %)**AT Command: AT+TTRALARM**
621 621  
622 -Feature: Manually set the count number
626 +[[image:image-20221118093512-3.png]]
623 623  
624 -(% style="color:blue" %)**AT Command: AT+SETCNT**
625 625  
626 -[[image:image-20221021111748-24.png]]
627 627  
630 +== 2.13  Select counting mode ==
628 628  
629 629  
630 -== 2.13  Set the number of data to be uploaded and the recording time ==
633 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
631 631  
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.
632 632  
633 -(% 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.
634 634  
635 -(% 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]]
636 636  
637 -(% 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 638  
639 639  
640 640  
641 -== 2.14  Read or Clear cached data ==
644 +== 2.14  Set the number of data to be uploaded and the recording time ==
642 642  
643 643  
644 644  (% style="color:blue" %)**AT Command:**
645 645  
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 +
646 646  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
647 647  
648 648  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
649 649  
650 -[[image:image-20221021111810-25.png||height="364" width="797"]]
663 +[[image:image-20221118094227-5.png]]
651 651  
652 652  
653 653  
654 -== 2.15  ​Firmware Change Log ==
667 +== 2.16  ​Firmware Change Log ==
655 655  
656 656  
657 657  Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
... ... @@ -660,13 +660,13 @@
660 660  
661 661  
662 662  
663 -== 2.16  ​Battery Analysis ==
676 +== 2.17  ​Battery Analysis ==
664 664  
665 665  
666 -=== 2.16.1  ​Battery Type ===
679 +=== 2.17.1  ​Battery Type ===
667 667  
668 668  
669 -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.
682 +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.
670 670  
671 671  The battery is designed to last for several years depends on the actual use environment and update interval. 
672 672  
... ... @@ -682,7 +682,7 @@
682 682  
683 683  
684 684  
685 -=== 2.16.2  Power consumption Analyze ===
698 +=== 2.17.2  Power consumption Analyze ===
686 686  
687 687  
688 688  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.
... ... @@ -705,7 +705,7 @@
705 705  
706 706  
707 707  
708 -=== 2.16.3  ​Battery Note ===
721 +=== 2.17.3  ​Battery Note ===
709 709  
710 710  
711 711  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.
... ... @@ -712,7 +712,7 @@
712 712  
713 713  
714 714  
715 -=== 2.16.4  Replace the battery ===
728 +=== 2.17.4  Replace the battery ===
716 716  
717 717  
718 718  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).
... ... @@ -726,7 +726,7 @@
726 726  
727 727  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/]] 
728 728  
729 -[[image:image-20221021112006-28.png]] ​
742 +[[image:image-20221118094449-6.png]] ​
730 730  
731 731  
732 732  
... ... @@ -779,15 +779,21 @@
779 779  
780 780  AT+ DEBUG   : Enable or Disable debug mode
781 781  
782 -AT+ TTRIG   : Get or Set Alarm Base on Timeout
795 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
783 783  
784 -AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
797 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
785 785  
786 -AT+ CALCFLAG   : Get or Set the calculate flag
799 +AT+COUNTMOD  :  Get or Set the count mode
787 787  
788 -AT+ CLRC   : Clear current door open count
801 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
789 789  
803 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
790 790  
805 +AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
806 +
807 +AT+ CLRC   :  Clear current door open count
808 +
809 +
791 791  (% style="color:blue" %)**COAP Management**      
792 792  
793 793  AT+URI            : Resource parameters
... ... @@ -829,7 +829,7 @@
829 829  
830 830  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]]
831 831  
832 -(% 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.**
851 +(% 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.**
833 833  
834 834  
835 835  
... ... @@ -853,7 +853,7 @@
853 853  = 7. ​ Order Info =
854 854  
855 855  
856 -Part Number**:** CPN01
875 +Part Number**:** NDS03A
857 857  
858 858  
859 859  
... ... @@ -862,7 +862,7 @@
862 862  
863 863  (% style="color:blue" %)**Package Includes**:
864 864  
865 -* CPN01 Open/Close Sensor x 1
884 +* NDS03A Open/Close Door Sensor x 1
866 866  * External antenna x 1
867 867  
868 868  (% style="color:blue" %)**Dimension and weight**:
... ... @@ -870,7 +870,6 @@
870 870  * Size: 195 x 125 x 55 mm
871 871  * Weight:   420g
872 872  
873 -
874 874  = 9.  Support =
875 875  
876 876  
image-20221117114459-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +14.9 KB
Content
image-20221117114842-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +964.1 KB
Content
image-20221117114937-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +79.1 KB
Content
image-20221117114949-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +33.4 KB
Content
image-20221117115010-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +40.4 KB
Content
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
image-20221118094449-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.5 KB
Content

Applications

Navigation

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