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 < 61.5 >
edited by Xiaoling
on 2022/11/17 16:45
>
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  
... ... @@ -412,7 +412,7 @@
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.
444 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
416 416  
417 417  
418 418  
... ... @@ -419,7 +419,7 @@
419 419  === 2.4.3  Battery Info ===
420 420  
421 421  
422 -Check the battery voltage for CPN01.
451 +Check the battery voltage for NDS03A.
423 423  
424 424  Ex1: 0x0B45 = 2885mV
425 425  
... ... @@ -446,19 +446,17 @@
446 446  
447 447  
448 448  
449 -=== 2.4.5  Calculate Flag ===
478 +=== 2.4.5  Disalarm: (default: 0) ===
450 450  
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.
481 +(% 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.
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.
483 +(% 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.
455 455  
456 -Default value: 0. 
485 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
457 457  
458 -Range (6 bits): (b)000000 ~~ (b) 111111
459 459  
460 460  
461 -
462 462  === 2.4.6  Alarm ===
463 463  
464 464  
... ... @@ -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

Applications

Navigation

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