Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 70.25 >
edited by Xiaoling
on 2022/12/07 16:40
To version < 52.6 >
edited by Xiaoling
on 2022/10/25 16:00
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
1 +CPN01- NB-IoT Outdoor Open/Close Dry Contact Sensor User Manual
Content
... ... @@ -1,12 +1,8 @@
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  
12 12  {{toc/}}
... ... @@ -17,47 +17,36 @@
17 17  
18 18  = 1.  Introduction =
19 19  
20 -== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
21 21  
17 +== 1.1 ​ What is CPN01 NB-IoT Pulse/Contact Sensor ==
22 22  
23 -(((
24 -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.
25 -)))
26 26  
27 27  (((
28 -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.
21 +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.
29 29  )))
30 30  
31 31  (((
32 -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.
25 +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.
33 33  )))
34 34  
35 35  (((
36 -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.
29 +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.
37 37  )))
38 38  
39 39  (((
40 -NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
33 +CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures.
41 41  )))
42 42  
43 43  (((
44 -NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**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.
37 +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.
38 +\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
39 +\\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)
40 +\\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.
45 45  )))
46 46  
47 -(((
48 -NDS03A supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
49 -)))
43 +​
50 50  
51 -(((
52 -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)
53 -)))
54 54  
55 -(((
56 -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.
57 -)))
58 -
59 -
60 -
61 61  == ​1.2  Features ==
62 62  
63 63  
... ... @@ -65,7 +65,7 @@
65 65  * Open/Close detect
66 66  * Open/Close statistics
67 67  * Monitor Battery Level
68 -* connect two door sensors
53 +* Uplink on periodically and open/close event
69 69  * Datalog feature
70 70  * Uplink periodically
71 71  * Downlink to change configure
... ... @@ -78,48 +78,50 @@
78 78  
79 79  
80 80  
81 -== 1.3  Storage & Operation ==
66 +== 1.3  Specification ==
82 82  
83 83  
84 -Temperature -40°C to +85°C
69 +(% style="color:blue" %)**Common DC Characteristics:**
85 85  
71 +* Supply Voltage: 2.1v ~~ 3.6v
72 +* Operating Temperature: -40 ~~ 85°C
86 86  
87 -== 1.4  Mechanical ==
74 +(% style="color:blue" %)**NB-IoT Spec:**
88 88  
76 +* - B1 @H-FDD: 2100MHz
77 +* - B3 @H-FDD: 1800MHz
78 +* - B8 @H-FDD: 900MHz
79 +* - B5 @H-FDD: 850MHz
80 +* - B20 @H-FDD: 800MHz
81 +* - B28 @H-FDD: 700MHz
89 89  
90 -[[image:image-20221117114937-4.png]]
91 91  
92 92  
93 -[[image:image-20221117114949-5.png]]
85 +== 1.4  Installation ==
94 94  
95 95  
96 -[[image:image-20221117115010-6.png]]
88 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
97 97  
90 +[[image:image-20221021110329-1.png]]
98 98  
99 99  
100 -== 1.5 ​ Applications ==
93 +[[image:image-20221022234602-2.png||height="288" width="922"]]
101 101  
102 102  
103 -[[image:image-20221117114842-3.png]]
104 104  
97 +== 1.5 ​ Applications ==
105 105  
106 106  
107 -== 1.6  Specification ==
100 +* Open/Close Detection
101 +* Pulse meter application
102 +* Dry Contact Detection
108 108  
109 109  
110 -(% style="color:blue" %)**Common DC Characteristics:**
111 111  
112 -* Supply Voltage: 2.1v ~~ 3.6v
113 -* Operating Temperature: -40 ~~ 85°C
106 +== 1.6  Mechanical ==
114 114  
115 -(% style="color:blue" %)**NB-IoT Spec:**
116 116  
117 -* B1 @H-FDD: 2100MHz
118 -* B3 @H-FDD: 1800MHz
119 -* B8 @H-FDD: 900MHz
120 -* B5 @H-FDD: 850MHz
121 -* B20 @H-FDD: 800MHz
122 -* B28 @H-FDD: 700MHz
109 +​[[image:image-20221021110415-3.png]]
123 123  
124 124  
125 125  
... ... @@ -132,9 +132,10 @@
132 132  === 1.7.1  Pin Definition ===
133 133  
134 134  
135 -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]]
122 +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]]**.
136 136  
137 137  
125 +
138 138  === 1.7.2  Jumper JP2(Power ON/OFF) ===
139 139  
140 140  
... ... @@ -141,6 +141,7 @@
141 141  Power on Device when putting this jumper.
142 142  
143 143  
132 +
144 144  === 1.7.3  BOOT MODE / SW1 ===
145 145  
146 146  
... ... @@ -149,6 +149,7 @@
149 149  2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
150 150  
151 151  
141 +
152 152  === 1.7.4  Reset Button ===
153 153  
154 154  
... ... @@ -155,6 +155,7 @@
155 155  Press to reboot the device.
156 156  
157 157  
148 +
158 158  === 1.7.5  LED ===
159 159  
160 160  
... ... @@ -165,42 +165,40 @@
165 165  2.  Send an uplink packet
166 166  
167 167  
168 -== 1.8  Magnet Distance ==
169 169  
160 += 2.  Use CPN01 to communicate with IoT Server =
170 170  
171 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
172 172  
173 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
174 -
175 -
176 -= 2.  Use NDS03A to communicate with IoT Server =
177 -
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.
166 +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:
168 +The diagram below shows the working flow in the default firmware of CPN01:
184 184  
185 185  [[image:image-20221021110615-5.png]]
186 186  
187 187  
188 -== 2.2 ​ Configure NDS03A ==
189 189  
174 +== 2.2 ​ Configure CPN01 ==
175 +
176 +
190 190  === 2.2.1 Test Requirement ===
191 191  
192 192  
193 -To use NDS03A in your city, make sure to meet below requirements:
180 +To use CPN01 in your city, make sure to meet below requirements:
194 194  
195 195  * Your local operator has already distributed an NB-IoT Network.
196 -* The local NB-IoT network used the band that NDS03A supports.
183 +* The local NB-IoT network used the band that CPN01 supports.
197 197  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
198 198  
199 -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.
186 +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 200  
201 -[[image:image-20221117142300-1.png]]
188 +[[image:image-20221023000439-3.png]]
202 202  
190 + ​
203 203  
192 +
204 204  === 2.2.2 Insert NB-IoT SIM card ===
205 205  
206 206  
... ... @@ -211,11 +211,12 @@
211 211  [[image:image-20221021110745-6.png]] ​
212 212  
213 213  
214 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
215 215  
204 +=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
216 216  
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.
218 218  
207 +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.
208 +
219 219  (% style="color:blue" %)**Connection:**
220 220  
221 221  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -237,11 +237,11 @@
237 237  
238 238  * Flow Control: (% style="color:red" %)**None**
239 239  
240 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
230 +Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
241 241  
242 242  ​[[image:image-20221021110817-7.png]]
243 243  
244 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
234 +CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
245 245  
246 246  
247 247  (% 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]]
... ... @@ -254,7 +254,7 @@
254 254  (% style="color:red" %)**Note: if you don't have a CoAP server, you can refer this link to set up a CoAP server: **(%%)[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
255 255  
256 256  
257 -(% style="color:blue" %)**Use below commands in NDS03A:**
247 +(% style="color:blue" %)**Use below commands in CPN01:**
258 258  
259 259  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
260 260  
... ... @@ -267,11 +267,12 @@
267 267  [[image:image-20221021110948-8.png]]
268 268  
269 269  
270 -After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
260 +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.
271 271  
272 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
262 +[[image:image-20221021110956-9.png]] ​
273 273  
274 274  
265 +
275 275  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
276 276  
277 277  
... ... @@ -290,6 +290,7 @@
290 290  
291 291  ​
292 292  
284 +
293 293  === 2.2.6 Use MQTT protocol to uplink data ===
294 294  
295 295  
... ... @@ -309,10 +309,10 @@
309 309  
310 310  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
311 311  
312 -​ [[image:image-20221118103445-7.png]]
304 +​ [[image:image-20221021111058-12.png]]
313 313  
314 314  
315 -[[image:image-20221118103453-8.png||height="608" width="841"]]
307 +[[image:image-20221021111201-16.png||height="472" width="653"]]
316 316  
317 317  ​
318 318  
... ... @@ -319,6 +319,7 @@
319 319  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.
320 320  
321 321  
314 +
322 322  === 2.2.7 Use TCP protocol to uplink data ===
323 323  
324 324  
... ... @@ -334,89 +334,78 @@
334 334  
335 335  ​
336 336  
330 +
337 337  === 2.2.8 Change Update Interval ===
338 338  
339 339  
340 340  User can use below command to change the (% style="color:blue" %)**uplink interval**.
341 341  
342 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
336 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
343 343  
344 344  (% style="color:red" %)**NOTE:**
345 345  
346 -1.  By default, the device will send an uplink message every 4 hour.
340 +1.  By default, the device will send an uplink message every 1 hour.
347 347  
348 348  
343 +
349 349  == 2.3  Uplink Payload ==
350 350  
351 351  
352 -The uplink payload includes 26 bytes in total by default.
347 +The uplink payload includes 123 bytes in total by default.
353 353  
354 -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.
349 +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.
355 355  
356 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
357 357  
358 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
359 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**1**|(% style="width:90px" %)**3**|(% style="width:100px" %)**3**
360 -|=(% 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.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
352 +(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
353 +|=(% 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**
354 +|=(% 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"]]
361 361  
362 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
363 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
364 -**1-32 group**
365 -)))
366 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% 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" %)...
356 +(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
357 +|(% 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**
358 +|(% 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" %)...
367 367  
368 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
360 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
369 369  
362 +[[image:image-20221021111201-16.png||height="572" width="792"]]
370 370  
371 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
372 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:45px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:60px" %)**1**|(% style="width:60px" %)**1**|(% style="width:87px" %)**3**|(% style="width:80px" %)**3**
373 -|=(% 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(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
374 374  
375 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
376 -|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:75px" %)**1**|(% style="width:75px" %)**3**
377 -|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
378 -
379 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
380 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
381 -**1-32 group**
382 -)))
383 -|(% style="width:102px" %)last open time(pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:100px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
384 -
385 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
386 -
387 -[[image:image-20221117145932-2.png]]
388 -
389 -
390 390  The payload is ASCII string, representative same HEX:
391 391  
392 -**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__(%%)**
367 +**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 __**
393 393  
394 394  **where:**
395 395  
396 396  * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
397 397  
398 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
373 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
399 399  
400 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
375 +* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
401 401  
402 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
377 +* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
403 403  
404 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
379 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
405 405  
406 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
381 +* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
407 407  
408 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
383 +* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
409 409  
410 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
385 +* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
411 411  
412 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
387 +* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
413 413  
414 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
389 +* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
415 415  
391 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
416 416  
393 +* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
417 417  
395 +* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
396 +
397 +
398 +
418 418  == 2.4  Payload Explanation and Sensor Interface ==
419 419  
401 +
420 420  === 2.4.1  Device ID ===
421 421  
422 422  
... ... @@ -431,18 +431,20 @@
431 431  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
432 432  
433 433  
416 +
434 434  === 2.4.2  Version Info ===
435 435  
436 436  
437 437  Specify the software version: 0x64=100, which means firmware version 1.00.
438 438  
439 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
422 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
440 440  
441 441  
425 +
442 442  === 2.4.3  Battery Info ===
443 443  
444 444  
445 -Check the battery voltage for NDS03A.
429 +Check the battery voltage for CPN01.
446 446  
447 447  Ex1: 0x0B45 = 2885mV
448 448  
... ... @@ -449,6 +449,7 @@
449 449  Ex2: 0x0B49 = 2889mV
450 450  
451 451  
436 +
452 452  === 2.4.4  Signal Strength ===
453 453  
454 454  
... ... @@ -467,38 +467,70 @@
467 467  **99**    Not known or not detectable
468 468  
469 469  
470 -=== 2.4.5  Disalarm: (default: 0) ===
471 471  
456 +=== 2.4.5  Calculate Flag ===
472 472  
473 -(% 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.
474 474  
475 -(% 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.
459 +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.
476 476  
477 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
461 +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.
478 478  
463 +Default value: 0. 
479 479  
480 -=== 2.4.6  Keep Status & Keep Time ===
465 +Range (6 bits): (b)000000 ~~ (b) 111111
481 481  
482 482  
483 -Shows the configure value of Alarm Base on Timeout Feature
484 484  
469 +=== 2.4.6  Alarm ===
485 485  
486 -=== 2.4.7  Timestamp ===
487 487  
472 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
488 488  
489 -Timestamp : 0x6315537b =1662342011
490 490  
491 491  
492 -=== 2.4.8  Switch Dual Channel Mode ===
476 +=== 2.4.7  Contact Status ===
493 493  
494 494  
495 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
479 +0: Open
496 496  
481 +1: Close
497 497  
483 +
484 +
485 +=== 2.4.8  Total pulse ===
486 +
487 +
488 +Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
489 +
490 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
491 +
492 +
493 +
494 +=== 2.4.9  The last open duration ===
495 +
496 +
497 +Dry Contact last open duration.
498 +
499 +Unit: min.
500 +
501 +[[image:image-20221021111346-17.png||height="146" width="770"]]
502 +
503 +
504 +
505 +=== 2.4.10  Timestamp ===
506 +
507 +
508 +Timestamp : 0x6315537b =1662342011
509 +
510 +Convert Unix timestamp to time 2022-9-5 9:40:11.
511 +
512 +**~ **
513 +
514 +
498 498  == 2.5  Downlink Payload ==
499 499  
500 500  
501 -By default, NDS03A prints the downlink payload to console port.
518 +By default, CPN01 prints the downlink payload to console port.
502 502  
503 503  [[image:image-20221021111414-18.png]] ​
504 504  
... ... @@ -515,7 +515,7 @@
515 515  
516 516  * (% style="color:#037691" %)**Reset**
517 517  
518 -If payload = 0x04FF, it will reset the NDS03A
535 +If payload = 0x04FF, it will reset the NSE01
519 519  
520 520  * (% style="color:#037691" %)**INTMOD**
521 521  
... ... @@ -522,13 +522,14 @@
522 522  Downlink Payload: 06000003, Set AT+INTMOD=3
523 523  
524 524  
542 +
525 525  == 2.6  ​LED Indicator ==
526 526  
527 527  
528 -The NDS03A has an internal LED which is to show the status of different states.
546 +The CPN01 has an internal LED which is to show the status of different states.
529 529  
530 530  * When the device starts normally, the LED will light up for 1 second.
531 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
549 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
532 532  * For each uplink probe, LED will be on for 500ms.
533 533  
534 534  
... ... @@ -536,7 +536,7 @@
536 536  == 2.7  Alarm Base on Timeout ==
537 537  
538 538  
539 -NDS03A can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are:
557 +CPN01 can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are:
540 540  
541 541  
542 542  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -552,25 +552,17 @@
552 552  
553 553  If keep time = 0, Disable Alarm Base on Timeout feature.
554 554  
555 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
573 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
556 556  
557 557  
558 558  (% style="color:blue" %)**AT Command to configure:**
559 559  
560 -(% style="color:blue" %)**PB14 PIN:**
578 +(% style="color:#037691" %)**AT+TTRIG=1,30** (%%) **~-~->**  When the **Keep Status** change from connected to disconnect, and device remains in disconnect status for more than 30 seconds. CPN01 will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
561 561  
562 -(% style="color:#037691" %)**AT+TTRIG=1,30** (%%) **~-~->**  When the **Keep Status** change from connected to disconnect, and device remains in disconnect status for more than 30 seconds. NDS03A will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
563 -
564 564  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
565 565  
566 566  
567 -(% style="color:blue" %)**PB15 PIN:**
568 568  
569 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
570 -
571 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
572 -
573 -
574 574  == 2.8  Set debug mode ==
575 575  
576 576  
... ... @@ -592,57 +592,54 @@
592 592  [[image:image-20221021111527-19.png]]
593 593  
594 594  
595 -== 2.10  Count Mod ==
596 596  
606 +== 2.10  Set trigger mode ==
597 597  
598 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
599 599  
600 -[[image:image-20221118092935-1.png]]
609 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
601 601  
611 +Feature: Set the trigger interrupt mode.
602 602  
603 -== 2.11  Interrupt Pin Channel Mod ==
613 +[[image:image-20221021111552-20.png]]
604 604  
605 605  
606 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
607 607  
608 -[[image:image-20221118093144-2.png]]
617 +== 2.11  Set the calculate flag ==
609 609  
610 610  
611 -== 2.12 TTRIG1/2 timeout status alarm ==
620 +Feature: Set the calculate flag
612 612  
622 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
613 613  
614 -It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval.
624 +[[image:image-20221021111711-22.png]]
615 615  
616 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
617 617  
618 -[[image:image-20221118093512-3.png]]
619 619  
628 +== 2.12 Set count number ==
620 620  
621 -== 2.13  Select counting mode ==
622 622  
631 +Feature: Manually set the count number
623 623  
624 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
633 +(% style="color:blue" %)**AT Command: AT+SETCNT**
625 625  
626 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
635 +[[image:image-20221021111748-24.png]]
627 627  
628 -When (% style="color:red" %)**b=0**(%%), it is the last door open duration, and when (% style="color:red" %)**b=1**(%%),the last door close duration.
629 629  
630 -[[image:image-20221118093658-4.png]]
631 631  
639 +== 2.13  Set the number of data to be uploaded and the recording time ==
632 632  
633 -== 2.14  Set the number of data to be uploaded and the recording time ==
634 634  
635 -
636 636  (% style="color:blue" %)**AT Command:**
637 637  
638 -(% style="color:#037691" %)**AT+TR=900**(%%)  ~/~/  The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
644 +(% style="color:#037691" %)**AT+TR=900**        (%%)~/~/  The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
639 639  
640 -(% style="color:#037691" %)**AT+NOUD=8**(%%)** ** ~/~/  The device uploads 0 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
646 +(% style="color:#037691" %)**AT+NOUD=8 ** (%%)~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
641 641  
642 642  
643 -== 2.15  Read or Clear cached data ==
644 644  
650 +== 2.14  Read or Clear cached data ==
645 645  
652 +
646 646  (% style="color:blue" %)**AT Command:**
647 647  
648 648  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -649,24 +649,27 @@
649 649  
650 650  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
651 651  
652 -[[image:image-20221118094227-5.png]]
659 +[[image:image-20221021111810-25.png||height="364" width="797"]]
653 653  
654 654  
655 -== 2.16  ​Firmware Change Log ==
656 656  
663 +== 2.15  ​Firmware Change Log ==
657 657  
658 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
659 659  
666 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
667 +
660 660  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
661 661  
662 662  
663 -== 2.17  ​Battery Analysis ==
664 664  
665 -=== 2.17.1  ​Battery Type ===
672 +== 2.16  ​Battery Analysis ==
666 666  
667 667  
668 -The NDS03A battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
675 +=== 2.16.1  ​Battery Type ===
669 669  
677 +
678 +The CPN01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
679 +
670 670  The battery is designed to last for several years depends on the actual use environment and update interval. 
671 671  
672 672  The battery-related documents as below:
... ... @@ -680,9 +680,10 @@
680 680  [[image:image-20221021111911-26.png]] ​
681 681  
682 682  
683 -=== 2.17.2  Power consumption Analyze ===
684 684  
694 +=== 2.16.2  Power consumption Analyze ===
685 685  
696 +
686 686  Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
687 687  
688 688  Instruction to use as below:
... ... @@ -702,18 +702,21 @@
702 702  [[image:1666596205057-567.png]] ​
703 703  
704 704  
705 -=== 2.17.3  ​Battery Note ===
706 706  
717 +=== 2.16.3  ​Battery Note ===
707 707  
719 +
708 708  The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
709 709  
710 710  
711 -=== 2.17.4  Replace the battery ===
712 712  
724 +=== 2.16.4  Replace the battery ===
713 713  
714 -The default battery pack of NDS03A includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
715 715  
727 +The default battery pack of CPN01 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
716 716  
729 +
730 +
717 717  = 3. ​ Access NB-IoT Module =
718 718  
719 719  
... ... @@ -721,12 +721,13 @@
721 721  
722 722  The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
723 723  
738 +[[image:image-20221021112006-28.png]] ​
724 724  
725 -[[image:image-20221118094449-6.png]] ​
726 726  
727 727  
728 728  = 4.  Using the AT Commands =
729 729  
744 +
730 730  == 4.1  Access AT Commands ==
731 731  
732 732  
... ... @@ -773,21 +773,15 @@
773 773  
774 774  AT+ DEBUG   : Enable or Disable debug mode
775 775  
776 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
791 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
777 777  
778 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
793 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
779 779  
780 -AT+COUNTMOD  :  Get or Set the count mode
795 +AT+ CALCFLAG   : Get or Set the calculate flag
781 781  
782 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
797 +AT+ CLRC   : Clear current door open count
783 783  
784 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
785 785  
786 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
787 -
788 -AT+ CLRC   :  Clear current door open count
789 -
790 -
791 791  (% style="color:blue" %)**COAP Management**      
792 792  
793 793  AT+URI            : Resource parameters
... ... @@ -818,8 +818,10 @@
818 818  AT+PWORD  : Serial Access Password
819 819  
820 820  
830 +
821 821  = ​5.  FAQ =
822 822  
833 +
823 823  == 5.1 ​ How to Upgrade Firmware ==
824 824  
825 825  
... ... @@ -827,11 +827,13 @@
827 827  
828 828  Please see this link for how to upgrade:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
829 829  
830 -(% style="color:red" %)**Notice: **(% style="color:blue" %)**NDS03A** (%%)**and (% style="color:blue" %)LDS03A(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
841 +(% style="color:red" %)**Notice: **(% style="color:blue" %)**CPN01** (%%)**and (% style="color:blue" %)CPL01(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
831 831  
832 832  
844 +
833 833  = 6.  Trouble Shooting =
834 834  
847 +
835 835  == 6.1  ​Connection problem when uploading firmware ==
836 836  
837 837  
... ... @@ -838,6 +838,7 @@
838 838  (% style="color:blue" %)**Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
839 839  
840 840  
854 +
841 841  == 6.2  AT Command input doesn't work ==
842 842  
843 843  
... ... @@ -844,21 +844,29 @@
844 844  In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER** (%%)while press the send key, user need to add ENTER in their string.
845 845  
846 846  
861 +
847 847  = 7. ​ Order Info =
848 848  
849 849  
850 -Part Number**:** NDS03A
865 +Part Number**:** CPN01
851 851  
852 852  
868 +
853 853  = 8.  Packing Info =
854 854  
855 855  
856 856  (% style="color:blue" %)**Package Includes**:
857 857  
858 -* NDS03A Open/Close Door Sensor x 1
874 +* CPN01 Open/Close Sensor x 1
875 +* External antenna x 1
859 859  
877 +(% style="color:blue" %)**Dimension and weight**:
860 860  
879 +* Size: 195 x 125 x 55 mm
880 +* Weight:   420g
861 861  
882 +
883 +
862 862  = 9.  Support =
863 863  
864 864  
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
image-20221118092935-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.5 KB
Content
image-20221118093658-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -12.7 KB
Content
image-20221118094227-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.2 KB
Content
image-20221118094449-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.5 KB
Content
image-20221118103445-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.5 KB
Content

Applications

Navigation

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