Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 50.1 >
edited by David Huang
on 2022/10/25 08:56
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
Title
... ... @@ -1,1 +1,1 @@
1 -CPN01- NB-IoT Outdoor Open/Close Dry Contact Sensor User Manual
1 +NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.David
1 +XWiki.Xiaoling
Content
... ... @@ -1,38 +1,57 @@
1 1  (% style="text-align:center" %)
2 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/WebHome/1652856952171-363.png?rev=1.1||alt="1652856952171-363.png" height="578" width="588"]]
2 +[[image:image-20221117105556-1.png]]
3 3  
4 4  
5 5  
6 -**Table of Contents：**
7 7  
8 -{{toc/}}
9 9  
10 10  
11 11  
10 +**Table of Contents：**
12 12  
13 13  
13 +
14 +
15 +
14 14  = 1.  Introduction =
15 15  
18 +== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
16 16  
17 -== 1.1 ​ What is CPN01 NB-IoT Pulse/Contact Sensor ==
18 18  
21 +(((
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 +)))
19 19  
20 -The Dragino CPN01 is an (% style="color:blue" %)**NB-IoT Dry Contact Sensor**(%%). It detects open/close status and uplinks the info to IoT server via NB-IoT network. User can see the (% style="color:blue" %)**dry contact status, open time, and open counts**(%%) in the IoT Server.
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 +)))
21 21  
22 -The CPN01 will send periodically data every day as well as for each dry contact action. It also counts the contact open times and calculates the last open duration. Users can also disable the uplink for each Open/Close event, instead, device can count each open event and uplink periodically.
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 +)))
23 23  
24 -CPN01 has** (% style="color:blue" %)Open-Alarm feature(%%)**, user can set this feature so CPN01 will send an alarm if the contact has been open exceeds 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 +)))
25 25  
26 -CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures.
37 +(((
38 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
39 +)))
27 27  
28 -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.
29 -\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
30 -\\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)
31 -\\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.
41 +(((
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.
43 +)))
32 32  
33 -​
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 +)))
34 34  
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 +)))
35 35  
53 +
54 +
36 36  == ​1.2  Features ==
37 37  
38 38  
... ... @@ -40,7 +40,7 @@
40 40  * Open/Close detect
41 41  * Open/Close statistics
42 42  * Monitor Battery Level
43 -* Uplink on periodically and open/close event
62 +* connect two door sensors
44 44  * Datalog feature
45 45  * Uplink periodically
46 46  * Downlink to change configure
... ... @@ -51,31 +51,22 @@
51 51  * Micro SIM card slot for NB-IoT SIM
52 52  * 8500mAh Battery for long-term use
53 53  
54 -== 1.3  Specification ==
73 +== 1.3  Storage & Operation ==
55 55  
56 56  
57 -(% style="color:blue" %)**Common DC Characteristics:**
76 +Temperature -40°C to +85°C
58 58  
59 -* Supply Voltage: 2.1v ~~ 3.6v
60 -* Operating Temperature: -40 ~~ 85°C
61 61  
62 -(% style="color:blue" %)**NB-IoT Spec:**
79 +== 1.4  Mechanical ==
63 63  
64 -* - B1 @H-FDD: 2100MHz
65 -* - B3 @H-FDD: 1800MHz
66 -* - B8 @H-FDD: 900MHz
67 -* - B5 @H-FDD: 850MHz
68 -* - B20 @H-FDD: 800MHz
69 -* - B28 @H-FDD: 700MHz
70 70  
71 -== 1.4  Installation ==
82 +[[image:image-20221117114937-4.png]]
72 72  
73 73  
74 -Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
85 +[[image:image-20221117114949-5.png]]
75 75  
76 -[[image:image-20221021110329-1.png]]
77 77  
78 -[[image:image-20221022234602-2.png||height="288" width="922"]]
88 +[[image:image-20221117115010-6.png]]
79 79  
80 80  
81 81  
... ... @@ -82,19 +82,30 @@
82 82  == 1.5 ​ Applications ==
83 83  
84 84  
85 -* Open/Close Detection
86 -* Pulse meter application
87 -* Dry Contact Detection
95 +[[image:image-20221117114842-3.png]]
88 88  
89 -== 1.6  Mechanical ==
90 90  
91 91  
92 -​[[image:image-20221021110415-3.png]]
99 +== 1.6  Specification ==
93 93  
94 94  
102 +(% style="color:blue" %)**Common DC Characteristics:**
95 95  
104 +* Supply Voltage: 2.1v ~~ 3.6v
105 +* Operating Temperature: -40 ~~ 85°C
106 +
107 +(% style="color:blue" %)**NB-IoT Spec:**
108 +
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
115 +
96 96  == 1.7  Pin Definitions and Switch ==
97 97  
118 +
98 98  [[image:image-20221021110429-4.png]]
99 99  
100 100  
... ... @@ -101,7 +101,7 @@
101 101  === 1.7.1  Pin Definition ===
102 102  
103 103  
104 -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]]
105 105  
106 106  
107 107  
... ... @@ -139,35 +139,42 @@
139 139  
140 140  
141 141  
142 -= 2.  Use CPN01 to communicate with IoT Server =
163 +== 1.8  Magnet Distance ==
143 143  
144 144  
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 +
145 145  == 2.1  How it works ==
146 146  
147 147  
148 -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.
149 149  
150 -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:
151 151  
152 152  [[image:image-20221021110615-5.png]]
153 153  
154 154  
155 155  
156 -== 2.2 ​ Configure CPN01 ==
185 +== 2.2 ​ Configure NDS03A ==
157 157  
158 -
159 159  === 2.2.1 Test Requirement ===
160 160  
161 161  
162 -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:
163 163  
164 164  * Your local operator has already distributed an NB-IoT Network.
165 -* The local NB-IoT network used the band that CPN01 supports.
193 +* The local NB-IoT network used the band that NDS03A supports.
166 166  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
167 167  
168 -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.
169 169  
170 -[[image:image-20221023000439-3.png]]
198 +[[image:image-20221117142300-1.png]]
171 171  
172 172   ​
173 173  
... ... @@ -183,10 +183,10 @@
183 183  
184 184  
185 185  
186 -=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
214 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
187 187  
188 188  
189 -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.
190 190  
191 191  (% style="color:blue" %)**Connection:**
192 192  
... ... @@ -209,11 +209,11 @@
209 209  
210 210  * Flow Control: (% style="color:red" %)**None**
211 211  
212 -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**(%%).
213 213  
214 214  ​[[image:image-20221021110817-7.png]]
215 215  
216 -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.
217 217  
218 218  
219 219  (% 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]]
... ... @@ -239,7 +239,7 @@
239 239  [[image:image-20221021110948-8.png]]
240 240  
241 241  
242 -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.
243 243  
244 244  [[image:image-20221021110956-9.png]] ​
245 245  
... ... @@ -315,11 +315,11 @@
315 315  
316 316  User can use below command to change the (% style="color:blue" %)**uplink interval**.
317 317  
318 -* (% 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)
319 319  
320 320  (% style="color:red" %)**NOTE:**
321 321  
322 -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.
323 323  
324 324  
325 325  
... ... @@ -326,27 +326,47 @@
326 326  == 2.3  Uplink Payload ==
327 327  
328 328  
329 -The uplink payload includes 123 bytes in total by default.
357 +The uplink payload includes 26 bytes in total by default.
330 330  
331 -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.
332 332  
361 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
333 333  
334 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:510px" %)
335 -|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:40px" %)**2**|(% style="width:44px" %)**2**|(% style="width:121px" %)**1**|(% style="width:52px" %)**1**|(% style="width:84px" %)**1**|(% style="width:116px" %)**1**|(% style="width:57px" %)**1**|(% style="width:91px" %)**3**
336 -|=(% 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)
337 337  
338 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:490px" %)
339 -|(% style="width:176px" %)**3**|(% style="width:98px" %)**4**|(% style="width:115px" %)**1**|(% style="width:92px" %)**3**|(% style="width:169px" %)**3**|(% style="width:97px" %)4|(% style="width:74px" %)**8 group**|(% style="width:1px" %)
340 -|(% 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" %)...|(% style="width:1px" %)
367 +(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
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" %)...
341 341  
342 -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:**
343 343  
344 -[[image:image-20221021111201-16.png||height="572" width="792"]]
345 345  
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)
346 346  
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 +
347 347  The payload is ASCII string, representative same HEX:
348 348  
349 -**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" %)__09__(% style="color:#663300" %) __02__ (% 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__(%%)**
350 350  
351 351  **where:**
352 352  
... ... @@ -354,28 +354,22 @@
354 354  
355 355  * (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
356 356  
357 -* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
405 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
358 358  
359 -* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
407 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
360 360  
361 361  * (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
362 362  
363 -* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
411 +* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0
364 364  
365 -* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
413 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
366 366  
367 -* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
415 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
368 368  
369 -* (% style="color:#037691" %)**Total pulse: **(%%)0x09 =0
417 +* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
370 370  
371 -* (% style="color:#037691" %)**The last open duration: **(%%)0x02 =2
419 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
372 372  
373 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
374 -
375 -* (% style="color:#037691" %)**Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 01  00000b  02  000026  63510fed
376 -
377 -* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
378 -
379 379  == 2.4  Payload Explanation and Sensor Interface ==
380 380  
381 381  
... ... @@ -393,20 +393,18 @@
393 393  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
394 394  
395 395  
396 -
397 397  === 2.4.2  Version Info ===
398 398  
399 399  
400 400  Specify the software version: 0x64=100, which means firmware version 1.00.
401 401  
402 -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.
403 403  
404 404  
405 -
406 406  === 2.4.3  Battery Info ===
407 407  
408 408  
409 -Check the battery voltage for CPN01.
449 +Check the battery voltage for NDS03A.
410 410  
411 411  Ex1: 0x0B45 = 2885mV
412 412  
... ... @@ -413,7 +413,6 @@
413 413  Ex2: 0x0B49 = 2889mV
414 414  
415 415  
416 -
417 417  === 2.4.4  Signal Strength ===
418 418  
419 419  
... ... @@ -432,70 +432,39 @@
432 432  **99**    Not known or not detectable
433 433  
434 434  
474 +=== 2.4.5  Disalarm: (default: 0) ===
435 435  
436 -=== 2.4.5  Calculate Flag ===
437 437  
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.
438 438  
439 -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.
440 440  
441 -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.
442 442  
443 -Default value: 0. 
444 444  
445 -Range (6 bits): (b)000000 ~~ (b) 111111
484 +=== 2.4.6  Keep Status & Keep Time ===
446 446  
447 447  
487 +Shows the configure value of Alarm Base on Timeout Feature
448 448  
449 -=== 2.4.6  Alarm ===
450 450  
490 +=== 2.4.7  Timestamp ===
451 451  
452 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
453 453  
493 +Timestamp : 0x6315537b =1662342011
454 454  
455 455  
456 -=== 2.4.7  Contact Status ===
457 457  
497 +=== 2.4.8  Switch Dual Channel Mode ===
458 458  
459 -0: Open
460 460  
461 -1: Close
500 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
462 462  
463 463  
464 -
465 -=== 2.4.8  Total pulse ===
466 -
467 -
468 -Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
469 -
470 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
471 -
472 -
473 -
474 -=== 2.4.9  The last open duration ===
475 -
476 -
477 -Dry Contact last open duration.
478 -
479 -Unit: min.
480 -
481 -[[image:image-20221021111346-17.png||height="146" width="770"]]
482 -
483 -
484 -
485 -=== 2.4.10  Timestamp ===
486 -
487 -
488 -Timestamp : 0x6315537b =1662342011
489 -
490 -Convert Unix timestamp to time 2022-9-5 9:40:11.
491 -
492 -**~ **
493 -
494 -
495 495  == 2.5  Downlink Payload ==
496 496  
497 497  
498 -By default, CPN01 prints the downlink payload to console port.
506 +By default, NDS03A prints the downlink payload to console port.
499 499  
500 500  [[image:image-20221021111414-18.png]] ​
501 501  
... ... @@ -512,7 +512,7 @@
512 512  
513 513  * (% style="color:#037691" %)**Reset**
514 514  
515 -If payload = 0x04FF, it will reset the NSE01
523 +If payload = 0x04FF, it will reset the NDS03A
516 516  
517 517  * (% style="color:#037691" %)**INTMOD**
518 518  
... ... @@ -523,16 +523,17 @@
523 523  == 2.6  ​LED Indicator ==
524 524  
525 525  
526 -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.
527 527  
528 528  * When the device starts normally, the LED will light up for 1 second.
529 529  * 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  
540 +
532 532  == 2.7  Alarm Base on Timeout ==
533 533  
534 534  
535 -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:
536 536  
537 537  
538 538  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -548,17 +548,25 @@
548 548  
549 549  If keep time = 0, Disable Alarm Base on Timeout feature.
550 550  
551 -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.
552 552  
553 553  
554 554  (% style="color:blue" %)**AT Command to configure:**
555 555  
565 +(% style="color:blue" %)**PB14 PIN:**
566 +
556 556  (% 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.
557 557  
558 558  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
559 559  
560 560  
572 +(% style="color:blue" %)**PB15 PIN:**
561 561  
574 +(% style="color:#037691" %)**AT+TTRIG2=1,30**
575 +
576 +(% style="color:#037691" %)**AT+TTRIG2=0,0 **
577 +
578 +
562 562  == 2.8  Set debug mode ==
563 563  
564 564  
... ... @@ -581,64 +581,73 @@
581 581  
582 582  
583 583  
584 -== 2.10  Set trigger mode ==
601 +== 2.10  Count Mod ==
585 585  
586 586  
587 -(% style="color:blue" %)**AT Command: AT+TTRMOD**
604 +(% style="color:blue" %)**AT Command: AT+COUNTMOD**
588 588  
589 -Feature: Set the trigger interrupt mode.
606 +[[image:image-20221118092935-1.png]]
590 590  
591 -[[image:image-20221021111552-20.png]]
592 592  
593 593  
610 +== 2.11  Interrupt Pin Channel Mod ==
594 594  
595 -== 2.11  Set the calculate flag ==
596 596  
613 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
597 597  
598 -Feature: Set the calculate flag
615 +[[image:image-20221118093144-2.png]]
599 599  
600 -(% style="color:blue" %)**AT Command: AT+CALCFLAG**
601 601  
602 -[[image:image-20221021111711-22.png]]
603 603  
619 +== 2.12 TTRIG1/2 timeout status alarm ==
604 604  
605 605  
606 -== 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.
607 607  
624 +(% style="color:blue" %)**AT Command: AT+TTRALARM**
608 608  
609 -Feature: Manually set the count number
626 +[[image:image-20221118093512-3.png]]
610 610  
611 -(% style="color:blue" %)**AT Command: AT+SETCNT**
612 612  
613 -[[image:image-20221021111748-24.png]]
614 614  
630 +== 2.13  Select counting mode ==
615 615  
616 616  
617 -== 2.13  Set the number of data to be uploaded and the recording time ==
633 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
618 618  
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.
619 619  
620 -(% 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.
621 621  
622 -(% 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]]
623 623  
624 -(% 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.
625 625  
626 626  
627 627  
628 -== 2.14  Read or Clear cached data ==
644 +== 2.14  Set the number of data to be uploaded and the recording time ==
629 629  
630 630  
631 631  (% style="color:blue" %)**AT Command:**
632 632  
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 +
633 633  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
634 634  
635 635  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
636 636  
637 -[[image:image-20221021111810-25.png||height="364" width="797"]]
663 +[[image:image-20221118094227-5.png]]
638 638  
639 639  
640 640  
641 -== 2.15  ​Firmware Change Log ==
667 +== 2.16  ​Firmware Change Log ==
642 642  
643 643  
644 644  Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
... ... @@ -647,13 +647,13 @@
647 647  
648 648  
649 649  
650 -== 2.16  ​Battery Analysis ==
676 +== 2.17  ​Battery Analysis ==
651 651  
652 652  
653 -=== 2.16.1  ​Battery Type ===
679 +=== 2.17.1  ​Battery Type ===
654 654  
655 655  
656 -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.
657 657  
658 658  The battery is designed to last for several years depends on the actual use environment and update interval. 
659 659  
... ... @@ -669,7 +669,7 @@
669 669  
670 670  
671 671  
672 -=== 2.16.2  Power consumption Analyze ===
698 +=== 2.17.2  Power consumption Analyze ===
673 673  
674 674  
675 675  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.
... ... @@ -692,7 +692,7 @@
692 692  
693 693  
694 694  
695 -=== 2.16.3  ​Battery Note ===
721 +=== 2.17.3  ​Battery Note ===
696 696  
697 697  
698 698  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.
... ... @@ -699,7 +699,7 @@
699 699  
700 700  
701 701  
702 -=== 2.16.4  Replace the battery ===
728 +=== 2.17.4  Replace the battery ===
703 703  
704 704  
705 705  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).
... ... @@ -713,7 +713,7 @@
713 713  
714 714  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/]] 
715 715  
716 -[[image:image-20221021112006-28.png]] ​
742 +[[image:image-20221118094449-6.png]] ​
717 717  
718 718  
719 719  
... ... @@ -766,15 +766,21 @@
766 766  
767 767  AT+ DEBUG   : Enable or Disable debug mode
768 768  
769 -AT+ TTRIG   : Get or Set Alarm Base on Timeout
795 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
770 770  
771 -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
772 772  
773 -AT+ CALCFLAG   : Get or Set the calculate flag
799 +AT+COUNTMOD  :  Get or Set the count mode
774 774  
775 -AT+ CLRC   : Clear current door open count
801 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
776 776  
803 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
777 777  
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 +
778 778  (% style="color:blue" %)**COAP Management**      
779 779  
780 780  AT+URI            : Resource parameters
... ... @@ -816,7 +816,7 @@
816 816  
817 817  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]]
818 818  
819 -(% 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.**
820 820  
821 821  
822 822  
... ... @@ -840,7 +840,7 @@
840 840  = 7. ​ Order Info =
841 841  
842 842  
843 -Part Number**:** CPN01
875 +Part Number**:** NDS03A
844 844  
845 845  
846 846  
... ... @@ -849,7 +849,7 @@
849 849  
850 850  (% style="color:blue" %)**Package Includes**:
851 851  
852 -* CPN01 Open/Close Sensor x 1
884 +* NDS03A Open/Close Door Sensor x 1
853 853  * External antenna x 1
854 854  
855 855  (% style="color:blue" %)**Dimension and weight**:
image-20221117105556-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +133.3 KB
Content
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-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0