Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 48.2 >
edited by Xiaoling
on 2022/10/24 15:43
To version < 61.1 >
edited by Xiaoling
on 2022/11/17 15:03
>
Change comment: Uploaded new attachment "image-20221117150312-3.png", version {1}

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
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,50 +51,56 @@
51 51  * Micro SIM card slot for NB-IoT SIM
52 52  * 8500mAh Battery for long-term use
53 53  
54 -== 1.3  Specification ==
55 55  
56 56  
57 -(% style="color:blue" %)**Common DC Characteristics:**
75 +== 1.3  Storage & Operation ==
58 58  
59 -* Supply Voltage: 2.1v ~~ 3.6v
60 -* Operating Temperature: -40 ~~ 85°C
61 61  
62 -(% style="color:blue" %)**NB-IoT Spec:**
78 +Temperature -40°C to +85°C
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 ==
81 +== 1.4  Mechanical ==
72 72  
73 73  
74 -Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
84 +[[image:image-20221117114937-4.png]]
75 75  
76 -[[image:image-20221021110329-1.png]]
77 77  
78 -[[image:image-20221022234602-2.png||height="288" width="922"]]
87 +[[image:image-20221117114949-5.png]]
79 79  
80 80  
90 +[[image:image-20221117115010-6.png]]
81 81  
92 +
93 +
82 82  == 1.5 ​ Applications ==
83 83  
84 84  
85 -* Open/Close Detection
86 -* Pulse meter application
87 -* Dry Contact Detection
97 +[[image:image-20221117114842-3.png]]
88 88  
89 -== 1.6  Mechanical ==
90 90  
91 91  
92 -​[[image:image-20221021110415-3.png]]
101 +== 1.6  Specification ==
93 93  
94 94  
104 +(% style="color:blue" %)**Common DC Characteristics:**
95 95  
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 +
96 96  == 1.7  Pin Definitions and Switch ==
97 97  
122 +
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]]**.
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]]
105 105  
106 106  
107 107  
... ... @@ -115,9 +115,9 @@
115 115  === 1.7.3  BOOT MODE / SW1 ===
116 116  
117 117  
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.
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.
119 119  
120 -2) Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
145 +2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
121 121  
122 122  
123 123  
... ... @@ -139,35 +139,42 @@
139 139  
140 140  
141 141  
142 -= 2.  Use CPN01 to communicate with IoT Server =
167 +== 1.8  Magnet Distance ==
143 143  
144 144  
170 +(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
171 +
172 +(% style="color:blue" %)**Iron Door:**(%%)**  **30 ~~ 45mm
173 +
174 +
175 +
176 += 2.  Use CPN01 to communicate with IoT Server =
177 +
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.
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.
149 149  
150 -The diagram below shows the working flow in the default firmware of CPN01:
183 +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 ==
189 +== 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:
194 +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.
197 +* 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.
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.
169 169  
170 -[[image:image-20221023000439-3.png]]
202 +[[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 ===
218 +=== 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.
221 +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**(%%).
244 +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.
248 +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]]
... ... @@ -228,19 +228,18 @@
228 228  
229 229  (% style="color:blue" %)**Use below commands in CPN01:**
230 230  
231 -(% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
263 +* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
232 232  
233 -(% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
265 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
234 234  
235 -(% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
267 +* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
236 236  
237 -
238 238  For parameter description, please refer to AT command set
239 239  
240 240  [[image:image-20221021110948-8.png]]
241 241  
242 242  
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.
274 +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.
244 244  
245 245  [[image:image-20221021110956-9.png]] ​
246 246  
... ... @@ -251,14 +251,15 @@
251 251  
252 252  (% style="color:blue" %)**AT Commands:**
253 253  
254 -* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
285 +* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
255 255  
256 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ Set UDP server address and port
287 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  Set UDP server address and port
257 257  
258 -* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
289 +* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
259 259  
260 260  ​ [[image:image-20221021111025-10.png]]
261 261  
293 +
262 262  [[image:image-20221021111033-11.png||height="241" width="576"]]
263 263  
264 264  ​
... ... @@ -269,22 +269,23 @@
269 269  
270 270  (% style="color:blue" %)**AT Commands:**
271 271  
272 -* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
304 +* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
273 273  
274 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
306 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
275 275  
276 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/Set up the CLIENT of MQTT
308 +* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
277 277  
278 -* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/Set the username of MQTT
310 +* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
279 279  
280 -* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/Set the password of MQTT
312 +* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
281 281  
282 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/Set the sending topic of MQTT
314 +* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/  Set the sending topic of MQTT
283 283  
284 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/Set the subscription topic of MQTT
316 +* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
285 285  
286 286  ​ [[image:image-20221021111058-12.png]]
287 287  
320 +
288 288  [[image:image-20221021111201-16.png||height="472" width="653"]]
289 289  
290 290  ​
... ... @@ -292,14 +292,15 @@
292 292  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.
293 293  
294 294  
328 +
295 295  === 2.2.7 Use TCP protocol to uplink data ===
296 296  
297 297  
298 -(% style="color:blue" %)**AT Commands**
332 +(% style="color:blue" %)**AT Commands:**
299 299  
300 -* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
334 +* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
301 301  
302 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/ Set TCP server address and port
336 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
303 303  
304 304  ​ [[image:image-20221021111125-14.png]]
305 305  
... ... @@ -307,19 +307,20 @@
307 307  
308 308  ​
309 309  
344 +
310 310  === 2.2.8 Change Update Interval ===
311 311  
312 312  
313 313  User can use below command to change the (% style="color:blue" %)**uplink interval**.
314 314  
315 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
350 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
316 316  
317 317  (% style="color:red" %)**NOTE:**
318 318  
319 -*
320 -**
321 -**1. By default, the device will send an uplink message every 1 hour.
354 +1.  By default, the device will send an uplink message every 4 hour.
322 322  
356 +
357 +
323 323  == 2.3  Uplink Payload ==
324 324  
325 325  
... ... @@ -327,51 +327,52 @@
327 327  
328 328  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.
329 329  
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
332 332  
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" %)
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"]]
336 336  
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 +
337 337  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
338 338  
339 339  [[image:image-20221021111201-16.png||height="572" width="792"]]
340 340  
378 +
341 341  The payload is ASCII string, representative same HEX:
342 342  
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 __**
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 __**
344 344  
345 345  **where:**
346 346  
347 -(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
385 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
348 348  
349 -(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
387 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
350 350  
351 -(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
389 +* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
352 352  
353 -(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
391 +* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
354 354  
355 -(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
393 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
356 356  
357 -(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00=0
395 +* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
358 358  
359 -(% style="color:#037691" %) **Contact Status:**(%%) 0x00=0
397 +* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
360 360  
361 -(% style="color:#037691" %) **Alarm: **(%%)0x00 =0
399 +* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
362 362  
363 -(% style="color:#037691" %) **Total pulse: **(%%)0x09 =0
401 +* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
364 364  
365 -(% style="color:#037691" %) **The last open duration: **(%%)0x02 =2
403 +* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
366 366  
367 -(% style="color:#037691" %)** Time stamp :**(%%) 0x6315537b =1662342011 (Unix Time)
405 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
368 368  
369 -(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 01  00000b  02  000026  63510fed
407 +* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
370 370  
371 -(% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
409 +* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
372 372  
373 -
374 -
375 375  == 2.4  Payload Explanation and Sensor Interface ==
376 376  
377 377  
... ... @@ -445,7 +445,7 @@
445 445  === 2.4.6  Alarm ===
446 446  
447 447  
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]]
484 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
449 449  
450 450  
451 451  
... ... @@ -461,7 +461,7 @@
461 461  === 2.4.8  Total pulse ===
462 462  
463 463  
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]]
500 +Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
465 465  
466 466  Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
467 467  
... ... @@ -637,9 +637,9 @@
637 637  == 2.15  ​Firmware Change Log ==
638 638  
639 639  
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]]
676 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
641 641  
642 -Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
678 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
643 643  
644 644  
645 645  
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

Applications

Navigation

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