Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 59.2 >
edited by Xiaoling
on 2022/11/17 14:23
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,56 +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 74  
75 -== 1.3  Storage & Operation ==
57 +(% style="color:blue" %)**Common DC Characteristics:**
76 76  
59 +* Supply Voltage: 2.1v ~~ 3.6v
60 +* Operating Temperature: -40 ~~ 85°C
77 77  
78 -Temperature -40°C to +85°C
62 +(% style="color:blue" %)**NB-IoT Spec:**
79 79  
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
80 80  
81 -== 1.4  Mechanical ==
71 +== 1.4  Installation ==
82 82  
83 83  
84 -[[image:image-20221117114937-4.png]]
74 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
85 85  
76 +[[image:image-20221021110329-1.png]]
86 86  
87 -[[image:image-20221117114949-5.png]]
78 +[[image:image-20221022234602-2.png||height="288" width="922"]]
88 88  
89 89  
90 -[[image:image-20221117115010-6.png]]
91 91  
92 -
93 -
94 94  == 1.5 ​ Applications ==
95 95  
96 96  
97 -[[image:image-20221117114842-3.png]]
85 +* Open/Close Detection
86 +* Pulse meter application
87 +* Dry Contact Detection
98 98  
89 +== 1.6  Mechanical ==
99 99  
100 100  
101 -== 1.6  Specification ==
92 +​[[image:image-20221021110415-3.png]]
102 102  
103 103  
104 -(% style="color:blue" %)**Common DC Characteristics:**
105 105  
106 -* Supply Voltage: 2.1v ~~ 3.6v
107 -* Operating Temperature: -40 ~~ 85°C
108 -
109 -(% style="color:blue" %)**NB-IoT Spec:**
110 -
111 -* - B1 @H-FDD: 2100MHz
112 -* - B3 @H-FDD: 1800MHz
113 -* - B8 @H-FDD: 900MHz
114 -* - B5 @H-FDD: 850MHz
115 -* - B20 @H-FDD: 800MHz
116 -* - B28 @H-FDD: 700MHz
117 -
118 -
119 -
120 120  == 1.7  Pin Definitions and Switch ==
121 121  
122 -
123 123  [[image:image-20221021110429-4.png]]
124 124  
125 125  
... ... @@ -126,7 +126,7 @@
126 126  === 1.7.1  Pin Definition ===
127 127  
128 128  
129 -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]]**.
130 130  
131 131  
132 132  
... ... @@ -140,9 +140,9 @@
140 140  === 1.7.3  BOOT MODE / SW1 ===
141 141  
142 142  
143 -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.
144 144  
145 -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.
146 146  
147 147  
148 148  
... ... @@ -164,23 +164,15 @@
164 164  
165 165  
166 166  
167 -== 1.8  Magnet Distance ==
168 -
169 -
170 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
171 -
172 -(% style="color:blue" %)**Iron Door:**(%%)**  **30 ~~ 45mm
173 -
174 -
175 -
176 176  = 2.  Use CPN01 to communicate with IoT Server =
177 177  
144 +
178 178  == 2.1  How it works ==
179 179  
180 180  
181 -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.
182 182  
183 -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:
184 184  
185 185  [[image:image-20221021110615-5.png]]
186 186  
... ... @@ -188,18 +188,19 @@
188 188  
189 189  == 2.2 ​ Configure CPN01 ==
190 190  
158 +
191 191  === 2.2.1 Test Requirement ===
192 192  
193 193  
194 -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:
195 195  
196 196  * Your local operator has already distributed an NB-IoT Network.
197 197  * The local NB-IoT network used the band that CPN01 supports.
198 198  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
199 199  
200 -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.
201 201  
202 -[[image:image-20221117142300-1.png]]
170 +[[image:image-20221023000439-3.png]]
203 203  
204 204   ​
205 205  
... ... @@ -260,12 +260,13 @@
260 260  
261 261  (% style="color:blue" %)**Use below commands in CPN01:**
262 262  
263 -* (% 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
264 264  
265 -* (% 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
266 266  
267 -* (% 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
268 268  
237 +
269 269  For parameter description, please refer to AT command set
270 270  
271 271  [[image:image-20221021110948-8.png]]
... ... @@ -282,15 +282,14 @@
282 282  
283 283  (% style="color:blue" %)**AT Commands:**
284 284  
285 -* (% 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
286 286  
287 -* (% 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
288 288  
289 -* (% 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
290 290  
291 291  ​ [[image:image-20221021111025-10.png]]
292 292  
293 -
294 294  [[image:image-20221021111033-11.png||height="241" width="576"]]
295 295  
296 296  ​
... ... @@ -301,23 +301,22 @@
301 301  
302 302  (% style="color:blue" %)**AT Commands:**
303 303  
304 -* (% 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
305 305  
306 -* (% 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
307 307  
308 -* (% 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
309 309  
310 -* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
278 +* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/Set the username of MQTT
311 311  
312 -* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
280 +* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/Set the password of MQTT
313 313  
314 -* (% 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
315 315  
316 -* (% 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
317 317  
318 318  ​ [[image:image-20221021111058-12.png]]
319 319  
320 -
321 321  [[image:image-20221021111201-16.png||height="472" width="653"]]
322 322  
323 323  ​
... ... @@ -325,15 +325,14 @@
325 325  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.
326 326  
327 327  
328 -
329 329  === 2.2.7 Use TCP protocol to uplink data ===
330 330  
331 331  
332 -(% style="color:blue" %)**AT Commands:**
298 +(% style="color:blue" %)**AT Commands**
333 333  
334 -* (% 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
335 335  
336 -* (% 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
337 337  
338 338  ​ [[image:image-20221021111125-14.png]]
339 339  
... ... @@ -341,7 +341,6 @@
341 341  
342 342  ​
343 343  
344 -
345 345  === 2.2.8 Change Update Interval ===
346 346  
347 347  
... ... @@ -351,10 +351,10 @@
351 351  
352 352  (% style="color:red" %)**NOTE:**
353 353  
354 -1.  By default, the device will send an uplink message every 1 hour.
319 +*
320 +**
321 +**1. By default, the device will send an uplink message every 1 hour.
355 355  
356 -
357 -
358 358  == 2.3  Uplink Payload ==
359 359  
360 360  
... ... @@ -362,52 +362,51 @@
362 362  
363 363  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.
364 364  
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
365 365  
366 -(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
367 -|=(% 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**
368 -|=(% 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" %)
369 369  
370 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
371 -|(% 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**
372 -|(% 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" %)...
373 -
374 374  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
375 375  
376 376  [[image:image-20221021111201-16.png||height="572" width="792"]]
377 377  
378 -
379 379  The payload is ASCII string, representative same HEX:
380 380  
381 -**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 __**
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 __**
382 382  
383 383  **where:**
384 384  
385 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
347 +(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
386 386  
387 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
349 +(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
388 388  
389 -* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
351 +(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
390 390  
391 -* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
353 +(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
392 392  
393 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
355 +(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
394 394  
395 -* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
357 +(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00=0
396 396  
397 -* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
359 +(% style="color:#037691" %) **Contact Status:**(%%) 0x00=0
398 398  
399 -* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
361 +(% style="color:#037691" %) **Alarm: **(%%)0x00 =0
400 400  
401 -* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
363 +(% style="color:#037691" %) **Total pulse: **(%%)0x09 =0
402 402  
403 -* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
365 +(% style="color:#037691" %) **The last open duration: **(%%)0x02 =2
404 404  
405 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
367 +(% style="color:#037691" %)** Time stamp :**(%%) 0x6315537b =1662342011 (Unix Time)
406 406  
407 -* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
369 +(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 01  00000b  02  000026  63510fed
408 408  
409 -* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
371 +(% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
410 410  
373 +
374 +
411 411  == 2.4  Payload Explanation and Sensor Interface ==
412 412  
413 413  
... ... @@ -481,7 +481,7 @@
481 481  === 2.4.6  Alarm ===
482 482  
483 483  
484 -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]]
485 485  
486 486  
487 487  
... ... @@ -497,7 +497,7 @@
497 497  === 2.4.8  Total pulse ===
498 498  
499 499  
500 -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]]
501 501  
502 502  Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
503 503  
... ... @@ -673,9 +673,9 @@
673 673  == 2.15  ​Firmware Change Log ==
674 674  
675 675  
676 -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]]
677 677  
678 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
642 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
679 679  
680 680  
681 681  
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

Applications

Navigation

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