Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 61.2 >
edited by Xiaoling
on 2022/11/17 15:08
To version < 48.2 >
edited by Xiaoling
on 2022/10/24 15:43
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
1 +CPN01- NB-IoT Outdoor Open/Close Dry Contact Sensor User Manual
Content
... ... @@ -1,57 +1,38 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20221117105556-1.png]]
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"]]
3 3  
4 4  
5 5  
6 -
7 -
8 -
9 -
10 10  **Table of Contents：**
11 11  
8 +{{toc/}}
12 12  
13 13  
14 14  
15 15  
13 +
16 16  = 1.  Introduction =
17 17  
18 -== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
19 19  
17 +== 1.1 ​ What is CPN01 NB-IoT Pulse/Contact Sensor ==
20 20  
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 -)))
24 24  
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 -)))
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.
28 28  
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 -)))
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.
32 32  
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 -)))
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.
36 36  
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 -)))
26 +CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures.
40 40  
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 -)))
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.
44 44  
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 -)))
33 +​
48 48  
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 -)))
52 52  
53 -
54 -
55 55  == ​1.2  Features ==
56 56  
57 57  
... ... @@ -59,7 +59,7 @@
59 59  * Open/Close detect
60 60  * Open/Close statistics
61 61  * Monitor Battery Level
62 -* connect two door sensors
43 +* Uplink on periodically and open/close event
63 63  * Datalog feature
64 64  * Uplink periodically
65 65  * Downlink to change configure
... ... @@ -70,54 +70,50 @@
70 70  * Micro SIM card slot for NB-IoT SIM
71 71  * 8500mAh Battery for long-term use
72 72  
54 +== 1.3  Specification ==
73 73  
74 -== 1.3  Storage & Operation ==
75 75  
57 +(% style="color:blue" %)**Common DC Characteristics:**
76 76  
77 -Temperature -40°C to +85°C
59 +* Supply Voltage: 2.1v ~~ 3.6v
60 +* Operating Temperature: -40 ~~ 85°C
78 78  
62 +(% style="color:blue" %)**NB-IoT Spec:**
79 79  
80 -== 1.4  Mechanical ==
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
81 81  
71 +== 1.4  Installation ==
82 82  
83 -[[image:image-20221117114937-4.png]]
84 84  
74 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
85 85  
86 -[[image:image-20221117114949-5.png]]
76 +[[image:image-20221021110329-1.png]]
87 87  
78 +[[image:image-20221022234602-2.png||height="288" width="922"]]
88 88  
89 -[[image:image-20221117115010-6.png]]
90 90  
91 91  
92 -
93 93  == 1.5 ​ Applications ==
94 94  
95 95  
96 -[[image:image-20221117114842-3.png]]
85 +* Open/Close Detection
86 +* Pulse meter application
87 +* Dry Contact Detection
97 97  
89 +== 1.6  Mechanical ==
98 98  
99 99  
100 -== 1.6  Specification ==
92 +​[[image:image-20221021110415-3.png]]
101 101  
102 102  
103 -(% style="color:blue" %)**Common DC Characteristics:**
104 104  
105 -* Supply Voltage: 2.1v ~~ 3.6v
106 -* Operating Temperature: -40 ~~ 85°C
107 -
108 -(% style="color:blue" %)**NB-IoT Spec:**
109 -
110 -* - B1 @H-FDD: 2100MHz
111 -* - B3 @H-FDD: 1800MHz
112 -* - B8 @H-FDD: 900MHz
113 -* - B5 @H-FDD: 850MHz
114 -* - B20 @H-FDD: 800MHz
115 -* - B28 @H-FDD: 700MHz
116 -
117 -
118 118  == 1.7  Pin Definitions and Switch ==
119 119  
120 -
121 121  [[image:image-20221021110429-4.png]]
122 122  
123 123  
... ... @@ -124,7 +124,7 @@
124 124  === 1.7.1  Pin Definition ===
125 125  
126 126  
127 -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]]
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]]**.
128 128  
129 129  
130 130  
... ... @@ -138,9 +138,9 @@
138 138  === 1.7.3  BOOT MODE / SW1 ===
139 139  
140 140  
141 -1)  ISP:  upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run.
118 +1) ISP:  upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run.
142 142  
143 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
120 +2) Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
144 144  
145 145  
146 146  
... ... @@ -162,42 +162,35 @@
162 162  
163 163  
164 164  
165 -== 1.8  Magnet Distance ==
166 -
167 -
168 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
169 -
170 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
171 -
172 -
173 -
174 174  = 2.  Use CPN01 to communicate with IoT Server =
175 175  
144 +
176 176  == 2.1  How it works ==
177 177  
178 178  
179 -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.
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.
180 180  
181 -The diagram below shows the working flow in the default firmware of NDS03A:
150 +The diagram below shows the working flow in the default firmware of CPN01:
182 182  
183 183  [[image:image-20221021110615-5.png]]
184 184  
185 185  
186 186  
187 -== 2.2 ​ Configure NDS03A ==
156 +== 2.2 ​ Configure CPN01 ==
188 188  
158 +
189 189  === 2.2.1 Test Requirement ===
190 190  
191 191  
192 -To use NDS03A in your city, make sure to meet below requirements:
162 +To use CPN01 in your city, make sure to meet below requirements:
193 193  
194 194  * Your local operator has already distributed an NB-IoT Network.
195 -* The local NB-IoT network used the band that NDS03A supports.
165 +* The local NB-IoT network used the band that CPN01 supports.
196 196  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
197 197  
198 -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.
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.
199 199  
200 -[[image:image-20221117142300-1.png]]
170 +[[image:image-20221023000439-3.png]]
201 201  
202 202   ​
203 203  
... ... @@ -213,10 +213,10 @@
213 213  
214 214  
215 215  
216 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
186 +=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
217 217  
218 218  
219 -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.
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.
220 220  
221 221  (% style="color:blue" %)**Connection:**
222 222  
... ... @@ -239,11 +239,11 @@
239 239  
240 240  * Flow Control: (% style="color:red" %)**None**
241 241  
242 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
212 +Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
243 243  
244 244  ​[[image:image-20221021110817-7.png]]
245 245  
246 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
216 +CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
247 247  
248 248  
249 249  (% 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]]
... ... @@ -258,18 +258,19 @@
258 258  
259 259  (% style="color:blue" %)**Use below commands in CPN01:**
260 260  
261 -* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
231 +(% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
262 262  
263 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
233 +(% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
264 264  
265 -* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
235 +(% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
266 266  
237 +
267 267  For parameter description, please refer to AT command set
268 268  
269 269  [[image:image-20221021110948-8.png]]
270 270  
271 271  
272 -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 +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.
273 273  
274 274  [[image:image-20221021110956-9.png]] ​
275 275  
... ... @@ -280,15 +280,14 @@
280 280  
281 281  (% style="color:blue" %)**AT Commands:**
282 282  
283 -* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
254 +* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
284 284  
285 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  Set UDP server address and port
256 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ Set UDP server address and port
286 286  
287 -* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
258 +* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
288 288  
289 289  ​ [[image:image-20221021111025-10.png]]
290 290  
291 -
292 292  [[image:image-20221021111033-11.png||height="241" width="576"]]
293 293  
294 294  ​
... ... @@ -299,23 +299,22 @@
299 299  
300 300  (% style="color:blue" %)**AT Commands:**
301 301  
302 -* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
272 +* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
303 303  
304 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
274 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
305 305  
306 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
276 +* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/Set up the CLIENT of MQTT
307 307  
308 -* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
278 +* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/Set the username of MQTT
309 309  
310 -* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
280 +* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/Set the password of MQTT
311 311  
312 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/  Set the sending topic of MQTT
282 +* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/Set the sending topic of MQTT
313 313  
314 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
284 +* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/Set the subscription topic of MQTT
315 315  
316 316  ​ [[image:image-20221021111058-12.png]]
317 317  
318 -
319 319  [[image:image-20221021111201-16.png||height="472" width="653"]]
320 320  
321 321  ​
... ... @@ -323,15 +323,14 @@
323 323  MQTT protocol has a much higher power consumption compare with UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
324 324  
325 325  
326 -
327 327  === 2.2.7 Use TCP protocol to uplink data ===
328 328  
329 329  
330 -(% style="color:blue" %)**AT Commands:**
298 +(% style="color:blue" %)**AT Commands**
331 331  
332 -* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
300 +* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
333 333  
334 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
302 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/ Set TCP server address and port
335 335  
336 336  ​ [[image:image-20221021111125-14.png]]
337 337  
... ... @@ -339,20 +339,19 @@
339 339  
340 340  ​
341 341  
342 -
343 343  === 2.2.8 Change Update Interval ===
344 344  
345 345  
346 346  User can use below command to change the (% style="color:blue" %)**uplink interval**.
347 347  
348 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
315 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
349 349  
350 350  (% style="color:red" %)**NOTE:**
351 351  
352 -1.  By default, the device will send an uplink message every 4 hour.
319 +*
320 +**
321 +**1. By default, the device will send an uplink message every 1 hour.
353 353  
354 -
355 -
356 356  == 2.3  Uplink Payload ==
357 357  
358 358  
... ... @@ -360,47 +360,48 @@
360 360  
361 361  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.
362 362  
330 +|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**1**|**1**|**3**
331 +|**Value**|[[Device ID>>path:#H2.4.1A0A0DeviceID]]|[[Ver>>path:#H2.4.2A0VersionInfo]]|[[BAT>>path:#H2.4.3A0BatteryInfo]]|[[Signal Strength>>path:#H2.4.4A0SignalStrength]]|MOD|[[ Calculate Flag>>path:#H2.4.8A0DigitalInterrupt]]|Contact Status|Alarm|Total pulse
363 363  
364 -(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
365 -|=(% 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**
366 -|=(% 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"]]
333 +(% style="width:1201px" %)
334 +|**3**|**4**|**1**|**3**|**1**|**3**|4|**8 group**|(% style="width:1px" %)
335 +|The last open duration|Time stamp|Contact Status|Total pulse|Calculate Flag|The last open duration|Time stamp|...|(% style="width:1px" %)
367 367  
368 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
369 -|(% 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**
370 -|(% 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" %)...
337 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
371 371  
372 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
339 +[[image:image-20221021111201-16.png||height="572" width="792"]]
373 373  
374 -[[image:image-20221117145932-2.png]]
341 +The payload is ASCII string, representative same HEX:
375 375  
343 +**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 __**
376 376  
377 -The payload is ASCII string, representative same HEX:
345 +**where:**
378 378  
379 -**0x **f867787050213317  0064  0ccf 19 01 00 00 000016 000017 637590df
347 +(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
380 380  
381 -**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__(%%)**
349 +(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
382 382  
383 -**where:**
351 +(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
384 384  
385 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
353 +(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
386 386  
387 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
355 +(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
388 388  
389 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
357 +(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00=0
390 390  
391 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
359 +(% style="color:#037691" %) **Contact Status:**(%%) 0x00=0
392 392  
393 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
361 +(% style="color:#037691" %) **Alarm: **(%%)0x00 =0
394 394  
395 -* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0
363 +(% style="color:#037691" %) **Total pulse: **(%%)0x09 =0
396 396  
397 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
365 +(% style="color:#037691" %) **The last open duration: **(%%)0x02 =2
398 398  
399 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
367 +(% style="color:#037691" %)** Time stamp :**(%%) 0x6315537b =1662342011 (Unix Time)
400 400  
401 -* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
369 +(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 01  00000b  02  000026  63510fed
402 402  
403 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
371 +(% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
404 404  
405 405  
406 406  
... ... @@ -477,7 +477,7 @@
477 477  === 2.4.6  Alarm ===
478 478  
479 479  
480 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
448 +See [[Alarm Base on Timeout>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H3.5AlarmBaseonTimeout]]
481 481  
482 482  
483 483  
... ... @@ -493,7 +493,7 @@
493 493  === 2.4.8  Total pulse ===
494 494  
495 495  
496 -Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
464 +Total pulse/counting based on dry [[contact trigger event>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.2SensorConfiguration2CFPORT3D4]]
497 497  
498 498  Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
499 499  
... ... @@ -669,9 +669,9 @@
669 669  == 2.15  ​Firmware Change Log ==
670 670  
671 671  
672 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
640 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
673 673  
674 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
642 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
675 675  
676 676  
677 677  
image-20221117105556-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -133.3 KB
Content
image-20221117114459-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20221117114842-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -964.1 KB
Content
image-20221117114937-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.1 KB
Content
image-20221117114949-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -33.4 KB
Content
image-20221117115010-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -40.4 KB
Content
image-20221117142300-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -51.9 KB
Content
image-20221117150312-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.7 KB
Content

Applications

Navigation

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