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