Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 70.21 >
edited by Xiaoling
on 2022/11/18 11:23
To version < 52.3 >
edited by Xiaoling
on 2022/10/25 15:49
>
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,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,43 +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) technologyTCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
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 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)
49 -)))
43 +​
50 50  
51 -(((
52 -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.
53 -)))
54 54  
55 -
56 -
57 57  == ​1.2  Features ==
58 58  
59 59  
... ... @@ -61,7 +61,7 @@
61 61  * Open/Close detect
62 62  * Open/Close statistics
63 63  * Monitor Battery Level
64 -* connect two door sensors
53 +* Uplink on periodically and open/close event
65 65  * Datalog feature
66 66  * Uplink periodically
67 67  * Downlink to change configure
... ... @@ -73,50 +73,54 @@
73 73  * 8500mAh Battery for long-term use
74 74  
75 75  
76 -== 1.3  Storage & Operation ==
77 77  
66 +== 1.3  Specification ==
78 78  
79 -Temperature -40°C to +85°C
80 80  
69 +(% style="color:blue" %)**Common DC Characteristics:**
81 81  
82 -== 1.4  Mechanical ==
71 +* Supply Voltage: 2.1v ~~ 3.6v
72 +* Operating Temperature: -40 ~~ 85°C
83 83  
74 +(% style="color:blue" %)**NB-IoT Spec:**
84 84  
85 -[[image:image-20221117114937-4.png]]
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
86 86  
87 87  
88 -[[image:image-20221117114949-5.png]]
89 89  
85 +== 1.4  Installation ==
90 90  
91 -[[image:image-20221117115010-6.png]]
92 92  
88 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
93 93  
90 +[[image:image-20221021110329-1.png]]
94 94  
95 -== 1.5 ​ Applications ==
96 96  
93 +[[image:image-20221022234602-2.png||height="288" width="922"]]
97 97  
98 -[[image:image-20221117114842-3.png]]
99 99  
100 100  
97 +== 1.5 ​ Applications ==
101 101  
102 -== 1.6  Specification ==
103 103  
100 +* Open/Close Detection
101 +* Pulse meter application
102 +* Dry Contact Detection
104 104  
105 -(% style="color:blue" %)**Common DC Characteristics:**
106 106  
107 -* Supply Voltage: 2.1v ~~ 3.6v
108 -* Operating Temperature: -40 ~~ 85°C
109 109  
110 -(% style="color:blue" %)**NB-IoT Spec:**
106 +== 1.6  Mechanical ==
111 111  
112 -* - B1 @H-FDD: 2100MHz
113 -* - B3 @H-FDD: 1800MHz
114 -* - B8 @H-FDD: 900MHz
115 -* - B5 @H-FDD: 850MHz
116 -* - B20 @H-FDD: 800MHz
117 -* - B28 @H-FDD: 700MHz
118 118  
109 +​[[image:image-20221021110415-3.png]]
119 119  
111 +
112 +
120 120  == 1.7  Pin Definitions and Switch ==
121 121  
122 122  
... ... @@ -126,9 +126,10 @@
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]]
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]]**.
130 130  
131 131  
125 +
132 132  === 1.7.2  Jumper JP2(Power ON/OFF) ===
133 133  
134 134  
... ... @@ -135,6 +135,7 @@
135 135  Power on Device when putting this jumper.
136 136  
137 137  
132 +
138 138  === 1.7.3  BOOT MODE / SW1 ===
139 139  
140 140  
... ... @@ -143,6 +143,7 @@
143 143  2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
144 144  
145 145  
141 +
146 146  === 1.7.4  Reset Button ===
147 147  
148 148  
... ... @@ -149,6 +149,7 @@
149 149  Press to reboot the device.
150 150  
151 151  
148 +
152 152  === 1.7.5  LED ===
153 153  
154 154  
... ... @@ -159,42 +159,40 @@
159 159  2.  Send an uplink packet
160 160  
161 161  
162 -== 1.8  Magnet Distance ==
163 163  
160 += 2.  Use CPN01 to communicate with IoT Server =
164 164  
165 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
166 166  
167 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
168 -
169 -
170 -= 2.  Use NDS03A to communicate with IoT Server =
171 -
172 172  == 2.1  How it works ==
173 173  
174 174  
175 -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.
176 176  
177 -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:
178 178  
179 179  [[image:image-20221021110615-5.png]]
180 180  
181 181  
182 -== 2.2 ​ Configure NDS03A ==
183 183  
174 +== 2.2 ​ Configure CPN01 ==
175 +
176 +
184 184  === 2.2.1 Test Requirement ===
185 185  
186 186  
187 -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:
188 188  
189 189  * Your local operator has already distributed an NB-IoT Network.
190 -* The local NB-IoT network used the band that NDS03A supports.
183 +* The local NB-IoT network used the band that CPN01 supports.
191 191  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
192 192  
193 -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.
194 194  
195 -[[image:image-20221117142300-1.png]]
188 +[[image:image-20221023000439-3.png]]
196 196  
190 + ​
197 197  
192 +
198 198  === 2.2.2 Insert NB-IoT SIM card ===
199 199  
200 200  
... ... @@ -205,11 +205,12 @@
205 205  [[image:image-20221021110745-6.png]] ​
206 206  
207 207  
208 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
209 209  
204 +=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
210 210  
211 -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.
212 212  
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 +
213 213  (% style="color:blue" %)**Connection:**
214 214  
215 215  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -231,11 +231,11 @@
231 231  
232 232  * Flow Control: (% style="color:red" %)**None**
233 233  
234 -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**(%%).
235 235  
236 236  ​[[image:image-20221021110817-7.png]]
237 237  
238 -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.
239 239  
240 240  
241 241  (% 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]]
... ... @@ -248,7 +248,7 @@
248 248  (% 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/]]
249 249  
250 250  
251 -(% style="color:blue" %)**Use below commands in NDS03A:**
247 +(% style="color:blue" %)**Use below commands in CPN01:**
252 252  
253 253  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
254 254  
... ... @@ -261,11 +261,12 @@
261 261  [[image:image-20221021110948-8.png]]
262 262  
263 263  
264 -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.
265 265  
266 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
262 +[[image:image-20221021110956-9.png]] ​
267 267  
268 268  
265 +
269 269  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
270 270  
271 271  
... ... @@ -284,6 +284,7 @@
284 284  
285 285  ​
286 286  
284 +
287 287  === 2.2.6 Use MQTT protocol to uplink data ===
288 288  
289 289  
... ... @@ -303,10 +303,10 @@
303 303  
304 304  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
305 305  
306 -​ [[image:image-20221118103445-7.png]]
304 +​ [[image:image-20221021111058-12.png]]
307 307  
308 308  
309 -[[image:image-20221118103453-8.png||height="608" width="841"]]
307 +[[image:image-20221021111201-16.png||height="472" width="653"]]
310 310  
311 311  ​
312 312  
... ... @@ -313,6 +313,7 @@
313 313  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.
314 314  
315 315  
314 +
316 316  === 2.2.7 Use TCP protocol to uplink data ===
317 317  
318 318  
... ... @@ -328,89 +328,78 @@
328 328  
329 329  ​
330 330  
330 +
331 331  === 2.2.8 Change Update Interval ===
332 332  
333 333  
334 334  User can use below command to change the (% style="color:blue" %)**uplink interval**.
335 335  
336 -* (% 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)
337 337  
338 338  (% style="color:red" %)**NOTE:**
339 339  
340 -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.
341 341  
342 342  
343 +
343 343  == 2.3  Uplink Payload ==
344 344  
345 345  
346 -The uplink payload includes 26 bytes in total by default.
347 +The uplink payload includes 123 bytes in total by default.
347 347  
348 -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.
349 349  
350 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
351 351  
352 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
353 -|=(% 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**
354 -|=(% 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: 96px;" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:40px" %)**2**|(% style="width:44px" %)**2**|(% style="width:121px" %)**1**|(% style="width:52px" %)**1**|(% style="width:84px" %)**1**|(% style="width:116px" %)**1**|(% style="width:57px" %)**1**|(% style="width:91px" %)**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"]]
355 355  
356 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
357 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
358 -**1-32 group**
359 -)))
360 -|(% 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:176px" %)**3**|(% style="width:98px" %)**4**|(% style="width:115px" %)**1**|(% style="width:92px" %)**3**|(% style="width:169px" %)**3**|(% style="width:97px" %)4|(% style="width:74px" %)**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" %)...
361 361  
360 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
362 362  
363 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
362 +[[image:image-20221021111201-16.png||height="572" width="792"]]
364 364  
365 365  
366 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
367 -|=(% 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**
368 -|=(% 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)
365 +The payload is ASCII string, representative same HEX:
369 369  
370 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
371 -|(% 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**
372 -|(% 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)
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 __**
373 373  
374 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
375 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
376 -**1-32 group**
377 -)))
378 -|(% 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" %)......
369 +**where:**
379 379  
380 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
371 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
381 381  
382 -[[image:image-20221117145932-2.png]]
373 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
383 383  
375 +* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
384 384  
385 -The payload is ASCII string, representative same HEX:
377 +* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
386 386  
387 -**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__(%%)**
379 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
388 388  
389 -**where:**
381 +* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
390 390  
391 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
383 +* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
392 392  
393 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
385 +* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
394 394  
395 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
387 +* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
396 396  
397 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
389 +* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
398 398  
399 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
391 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
400 400  
401 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
393 +* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
402 402  
403 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
395 +* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
404 404  
405 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
406 406  
407 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
408 408  
409 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
410 -
411 -
412 412  == 2.4  Payload Explanation and Sensor Interface ==
413 413  
401 +
414 414  === 2.4.1  Device ID ===
415 415  
416 416  
... ... @@ -425,18 +425,20 @@
425 425  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
426 426  
427 427  
416 +
428 428  === 2.4.2  Version Info ===
429 429  
430 430  
431 431  Specify the software version: 0x64=100, which means firmware version 1.00.
432 432  
433 -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.
434 434  
435 435  
425 +
436 436  === 2.4.3  Battery Info ===
437 437  
438 438  
439 -Check the battery voltage for NDS03A.
429 +Check the battery voltage for CPN01.
440 440  
441 441  Ex1: 0x0B45 = 2885mV
442 442  
... ... @@ -443,6 +443,7 @@
443 443  Ex2: 0x0B49 = 2889mV
444 444  
445 445  
436 +
446 446  === 2.4.4  Signal Strength ===
447 447  
448 448  
... ... @@ -461,38 +461,70 @@
461 461  **99**    Not known or not detectable
462 462  
463 463  
464 -=== 2.4.5  Disalarm: (default: 0) ===
465 465  
456 +=== 2.4.5  Calculate Flag ===
466 466  
467 -(% 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.
468 468  
469 -(% 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.
470 470  
471 - (% 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.
472 472  
463 +Default value: 0. 
473 473  
474 -=== 2.4.6  Keep Status & Keep Time ===
465 +Range (6 bits): (b)000000 ~~ (b) 111111
475 475  
476 476  
477 -Shows the configure value of Alarm Base on Timeout Feature
478 478  
469 +=== 2.4.6  Alarm ===
479 479  
480 -=== 2.4.7  Timestamp ===
481 481  
472 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
482 482  
483 -Timestamp : 0x6315537b =1662342011
484 484  
485 485  
486 -=== 2.4.8  Switch Dual Channel Mode ===
476 +=== 2.4.7  Contact Status ===
487 487  
488 488  
489 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
479 +0: Open
490 490  
481 +1: Close
491 491  
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 +
492 492  == 2.5  Downlink Payload ==
493 493  
494 494  
495 -By default, NDS03A prints the downlink payload to console port.
518 +By default, CPN01 prints the downlink payload to console port.
496 496  
497 497  [[image:image-20221021111414-18.png]] ​
498 498  
... ... @@ -509,7 +509,7 @@
509 509  
510 510  * (% style="color:#037691" %)**Reset**
511 511  
512 -If payload = 0x04FF, it will reset the NDS03A
535 +If payload = 0x04FF, it will reset the NSE01
513 513  
514 514  * (% style="color:#037691" %)**INTMOD**
515 515  
... ... @@ -516,20 +516,22 @@
516 516  Downlink Payload: 06000003, Set AT+INTMOD=3
517 517  
518 518  
542 +
519 519  == 2.6  ​LED Indicator ==
520 520  
521 521  
522 -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.
523 523  
524 524  * When the device starts normally, the LED will light up for 1 second.
525 -* 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.
526 526  * For each uplink probe, LED will be on for 500ms.
527 527  
528 528  
553 +
529 529  == 2.7  Alarm Base on Timeout ==
530 530  
531 531  
532 -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:
533 533  
534 534  
535 535  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -545,25 +545,17 @@
545 545  
546 546  If keep time = 0, Disable Alarm Base on Timeout feature.
547 547  
548 -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.
549 549  
550 550  
551 551  (% style="color:blue" %)**AT Command to configure:**
552 552  
553 -(% 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.
554 554  
555 -(% 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.
556 -
557 557  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
558 558  
559 559  
560 -(% style="color:blue" %)**PB15 PIN:**
561 561  
562 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
563 -
564 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
565 -
566 -
567 567  == 2.8  Set debug mode ==
568 568  
569 569  
... ... @@ -585,57 +585,54 @@
585 585  [[image:image-20221021111527-19.png]]
586 586  
587 587  
588 -== 2.10  Count Mod ==
589 589  
606 +== 2.10  Set trigger mode ==
590 590  
591 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
592 592  
593 -[[image:image-20221118092935-1.png]]
609 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
594 594  
611 +Feature: Set the trigger interrupt mode.
595 595  
596 -== 2.11  Interrupt Pin Channel Mod ==
613 +[[image:image-20221021111552-20.png]]
597 597  
598 598  
599 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
600 600  
601 -[[image:image-20221118093144-2.png]]
617 +== 2.11  Set the calculate flag ==
602 602  
603 603  
604 -== 2.12 TTRIG1/2 timeout status alarm ==
620 +Feature: Set the calculate flag
605 605  
622 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
606 606  
607 -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]]
608 608  
609 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
610 610  
611 -[[image:image-20221118093512-3.png]]
612 612  
628 +== 2.12 Set count number ==
613 613  
614 -== 2.13  Select counting mode ==
615 615  
631 +Feature: Manually set the count number
616 616  
617 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
633 +(% style="color:blue" %)**AT Command: AT+SETCNT**
618 618  
619 -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]]
620 620  
621 -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.
622 622  
623 -[[image:image-20221118093658-4.png]]
624 624  
639 +== 2.13  Set the number of data to be uploaded and the recording time ==
625 625  
626 -== 2.14  Set the number of data to be uploaded and the recording time ==
627 627  
628 -
629 629  (% style="color:blue" %)**AT Command:**
630 630  
631 -(% 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)
632 632  
633 -(% 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.
634 634  
635 635  
636 -== 2.15  Read or Clear cached data ==
637 637  
650 +== 2.14  Read or Clear cached data ==
638 638  
652 +
639 639  (% style="color:blue" %)**AT Command:**
640 640  
641 641  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -642,24 +642,27 @@
642 642  
643 643  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
644 644  
645 -[[image:image-20221118094227-5.png]]
659 +[[image:image-20221021111810-25.png||height="364" width="797"]]
646 646  
647 647  
648 -== 2.16  ​Firmware Change Log ==
649 649  
663 +== 2.15  ​Firmware Change Log ==
650 650  
651 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
652 652  
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 +
653 653  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
654 654  
655 655  
656 -== 2.17  ​Battery Analysis ==
657 657  
658 -=== 2.17.1  ​Battery Type ===
672 +== 2.16  ​Battery Analysis ==
659 659  
660 660  
661 -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 ===
662 662  
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 +
663 663  The battery is designed to last for several years depends on the actual use environment and update interval. 
664 664  
665 665  The battery-related documents as below:
... ... @@ -673,9 +673,10 @@
673 673  [[image:image-20221021111911-26.png]] ​
674 674  
675 675  
676 -=== 2.17.2  Power consumption Analyze ===
677 677  
694 +=== 2.16.2  Power consumption Analyze ===
678 678  
696 +
679 679  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.
680 680  
681 681  Instruction to use as below:
... ... @@ -695,18 +695,21 @@
695 695  [[image:1666596205057-567.png]] ​
696 696  
697 697  
698 -=== 2.17.3  ​Battery Note ===
699 699  
717 +=== 2.16.3  ​Battery Note ===
700 700  
719 +
701 701  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.
702 702  
703 703  
704 -=== 2.17.4  Replace the battery ===
705 705  
724 +=== 2.16.4  Replace the battery ===
706 706  
707 -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).
708 708  
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).
709 709  
729 +
730 +
710 710  = 3. ​ Access NB-IoT Module =
711 711  
712 712  
... ... @@ -714,11 +714,13 @@
714 714  
715 715  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/]] 
716 716  
717 -[[image:image-20221118094449-6.png]] ​
738 +[[image:image-20221021112006-28.png]] ​
718 718  
719 719  
741 +
720 720  = 4.  Using the AT Commands =
721 721  
744 +
722 722  == 4.1  Access AT Commands ==
723 723  
724 724  
... ... @@ -765,21 +765,15 @@
765 765  
766 766  AT+ DEBUG   : Enable or Disable debug mode
767 767  
768 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
791 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
769 769  
770 -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)
771 771  
772 -AT+COUNTMOD  :  Get or Set the count mode
795 +AT+ CALCFLAG   : Get or Set the calculate flag
773 773  
774 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
797 +AT+ CLRC   : Clear current door open count
775 775  
776 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
777 777  
778 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
779 -
780 -AT+ CLRC   :  Clear current door open count
781 -
782 -
783 783  (% style="color:blue" %)**COAP Management**      
784 784  
785 785  AT+URI            : Resource parameters
... ... @@ -810,8 +810,10 @@
810 810  AT+PWORD  : Serial Access Password
811 811  
812 812  
830 +
813 813  = ​5.  FAQ =
814 814  
833 +
815 815  == 5.1 ​ How to Upgrade Firmware ==
816 816  
817 817  
... ... @@ -819,11 +819,13 @@
819 819  
820 820  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]]
821 821  
822 -(% 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.**
823 823  
824 824  
844 +
825 825  = 6.  Trouble Shooting =
826 826  
847 +
827 827  == 6.1  ​Connection problem when uploading firmware ==
828 828  
829 829  
... ... @@ -830,6 +830,7 @@
830 830  (% 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]]
831 831  
832 832  
854 +
833 833  == 6.2  AT Command input doesn't work ==
834 834  
835 835  
... ... @@ -836,20 +836,29 @@
836 836  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.
837 837  
838 838  
861 +
839 839  = 7. ​ Order Info =
840 840  
841 841  
842 -Part Number**:** NDS03A
865 +Part Number**:** CPN01
843 843  
844 844  
868 +
845 845  = 8.  Packing Info =
846 846  
847 847  
848 848  (% style="color:blue" %)**Package Includes**:
849 849  
850 -* NDS03A Open/Close Door Sensor x 1
874 +* CPN01 Open/Close Sensor x 1
875 +* External antenna x 1
851 851  
877 +(% style="color:blue" %)**Dimension and weight**:
852 852  
879 +* Size: 195 x 125 x 55 mm
880 +* Weight:   420g
881 +
882 +
883 +
853 853  = 9.  Support =
854 854  
855 855  
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