Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 79.2 >
edited by Xiaoling
on 2022/12/07 17:41
To version < 59.3 >
edited by Xiaoling
on 2022/11/17 14:34
>
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 +NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
Content
... ... @@ -1,7 +1,12 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg]]
2 +[[image:image-20221117105556-1.png]]
3 3  
4 4  
5 +
6 +
7 +
8 +
9 +
5 5  **Table of Contents：**
6 6  
7 7  
... ... @@ -10,26 +10,39 @@
10 10  
11 11  = 1.  Introduction =
12 12  
13 -== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
18 +== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
14 14  
15 15  
16 16  (((
17 -The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor.
22 +The Dragino NDS03A is an (% style="color:blue" %)**Open/Close NB-IoT Door Sensor**(%%). It detects door (% style="color:blue" %)**open/close status**(%%) and (% style="color:blue" %)**uplinks**(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server.
23 +)))
18 18  
25 +(((
26 +The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically.
27 +)))
19 19  
20 -The NMDS200 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
29 +(((
30 +NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT.
31 +)))
21 21  
22 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
33 +(((
34 +NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time.
35 +)))
23 23  
24 -NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range.
37 +(((
38 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
39 +)))
25 25  
26 -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.
41 +(((
42 +NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technologyTCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
43 +)))
27 27  
28 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
45 +(((
46 +NDS03A is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
47 +)))
29 29  
30 -NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
31 -
32 -To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection.
49 +(((
50 +To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection.
33 33  )))
34 34  
35 35  
... ... @@ -38,9 +38,10 @@
38 38  
39 39  
40 40  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
41 -* Short uplink interval for Distance Alarm
59 +* Open/Close detect
60 +* Open/Close statistics
42 42  * Monitor Battery Level
43 -* Microwave Radar for distance detection
62 +* connect two door sensors
44 44  * Datalog feature
45 45  * Uplink periodically
46 46  * Downlink to change configure
... ... @@ -53,27 +53,22 @@
53 53  
54 54  
55 55  
56 -== 1.3 Radar probe specification ==
75 +== 1.3  Storage & Operation ==
57 57  
58 58  
59 -* Measuring Method: FMCW
60 -* Frequency: 24.000 24.500 GHz
61 -* Measurement output power: 6dBm
62 -* Measure range: 0.5 20m
63 -* Accuracy: ±0.1m
64 -* Resolution: 0.01m
65 -* Horizontal Angel: 78°
66 -* Vertical Angel: 23°
78 +Temperature -40°C to +85°C
67 67  
68 68  
81 +== 1.4  Mechanical ==
69 69  
70 70  
71 -== 1.4  Storage Temperature ==
84 +[[image:image-20221117114937-4.png]]
72 72  
73 73  
74 - -40°C to +85°C
87 +[[image:image-20221117114949-5.png]]
75 75  
76 76  
90 +[[image:image-20221117115010-6.png]]
77 77  
78 78  
79 79  
... ... @@ -80,19 +80,10 @@
80 80  == 1.5 ​ Applications ==
81 81  
82 82  
97 +[[image:image-20221117114842-3.png]]
83 83  
84 -* Horizontal distance measurement
85 -* Liquid level measurement
86 -* Parking management system
87 -* Object proximity and presence detection
88 -* Intelligent trash can management system
89 -* Robot obstacle avoidance
90 -* Automatic control
91 -* Sewer
92 -* Bottom water level monitoring
93 93  
94 94  
95 -
96 96  == 1.6  Specification ==
97 97  
98 98  
... ... @@ -99,64 +99,109 @@
99 99  (% style="color:blue" %)**Common DC Characteristics:**
100 100  
101 101  * Supply Voltage: 2.1v ~~ 3.6v
102 -* Operating Temperature: 0 ~~ 70°C
107 +* Operating Temperature: -40 ~~ 85°C
103 103  
104 104  (% style="color:blue" %)**NB-IoT Spec:**
105 105  
106 -* B1 @H-FDD: 2100MHz
107 -* B3 @H-FDD: 1800MHz
108 -* B8 @H-FDD: 900MHz
109 -* B5 @H-FDD: 850MHz
110 -* B20 @H-FDD: 800MHz
111 -* B28 @H-FDD: 700MHz
111 +* - B1 @H-FDD: 2100MHz
112 +* - B3 @H-FDD: 1800MHz
113 +* - B8 @H-FDD: 900MHz
114 +* - B5 @H-FDD: 850MHz
115 +* - B20 @H-FDD: 800MHz
116 +* - B28 @H-FDD: 700MHz
112 112  
113 113  
114 114  
115 -== 1.7  Installation ==
120 +== 1.7  Pin Definitions and Switch ==
116 116  
117 117  
118 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
123 +[[image:image-20221021110429-4.png]]
119 119  
120 120  
121 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
126 +=== 1.7.1  Pin Definition ===
122 122  
123 123  
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]]
124 124  
125 -== 1.8  Pin Definitions and Switch ==
126 126  
127 127  
128 -[[image:1670404362039-351.png]]
133 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
129 129  
130 130  
131 -= 2.  Use NMDS200 to communicate with IoT Server =
136 +Power on Device when putting this jumper.
132 132  
138 +
139 +
140 +=== 1.7.3  BOOT MODE / SW1 ===
141 +
142 +
143 +1)  ISP:  upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run.
144 +
145 +2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
146 +
147 +
148 +
149 +=== 1.7.4  Reset Button ===
150 +
151 +
152 +Press to reboot the device.
153 +
154 +
155 +
156 +=== 1.7.5  LED ===
157 +
158 +
159 +The LED will blink when :
160 +
161 +1.  Boot the device in flash mode
162 +
163 +2.  Send an uplink packet
164 +
165 +
166 +
167 +== 1.8  Magnet Distance ==
168 +
169 +
170 +(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
171 +
172 +(% style="color:blue" %)**Iron Door:**(%%)**  **30 ~~ 45mm
173 +
174 +
175 +
176 += 2.  Use CPN01 to communicate with IoT Server =
177 +
133 133  == 2.1  How it works ==
134 134  
135 135  
136 -The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
181 +In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.
137 137  
138 -The diagram below shows the working flow in the default firmware of NMDS200:
183 +The diagram below shows the working flow in the default firmware of NDS03A:
139 139  
140 140  [[image:image-20221021110615-5.png]]
141 141  
142 142  
143 -== 2.2 ​ Configure NMDS200 ==
144 144  
189 +== 2.2 ​ Configure NDS03A ==
145 145  
146 -To use NMDS200 in your city, make sure to meet below requirements:
191 +=== 2.2.1 Test Requirement ===
147 147  
193 +
194 +To use NDS03A in your city, make sure to meet below requirements:
195 +
148 148  * Your local operator has already distributed an NB-IoT Network.
149 -* The local NB-IoT network used the band that NMDS200 supports.
197 +* The local NB-IoT network used the band that NDS03A supports.
150 150  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
151 151  
152 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NMDS200 will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
200 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDS03A will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
153 153  
154 -[[image:image-20221207173300-4.png]]
202 +[[image:image-20221117142300-1.png]]
155 155  
204 + ​
156 156  
157 -=== 2.2.1 Insert NB-IoT SIM card ===
158 158  
207 +=== 2.2.2 Insert NB-IoT SIM card ===
159 159  
209 +
160 160  Insert the NB-IoT Card get from your provider.
161 161  
162 162  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -164,11 +164,12 @@
164 164  [[image:image-20221021110745-6.png]] ​
165 165  
166 166  
167 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
168 168  
218 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
169 169  
170 -User need to configure NMDS200 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NMDS200 support AT Commands, user can use a USB to TTL adapter to connect to NMDS200 and use AT Commands to configure it, as below.
171 171  
221 +User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
222 +
172 172  (% style="color:blue" %)**Connection:**
173 173  
174 174  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -190,11 +190,11 @@
190 190  
191 191  * Flow Control: (% style="color:red" %)**None**
192 192  
193 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
244 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
194 194  
195 195  ​[[image:image-20221021110817-7.png]]
196 196  
197 -NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
248 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
198 198  
199 199  
200 200  (% 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]]
... ... @@ -201,13 +201,13 @@
201 201  
202 202  
203 203  
204 -=== 2.2.3 Use CoAP protocol to uplink data ===
255 +=== 2.2.4 Use CoAP protocol to uplink data ===
205 205  
206 206  
207 207  (% 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/]]
208 208  
209 209  
210 -(% style="color:blue" %)**Use below commands in NDS03A:**
261 +(% style="color:blue" %)**Use below commands in CPN01:**
211 211  
212 212  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
213 213  
... ... @@ -220,14 +220,15 @@
220 220  [[image:image-20221021110948-8.png]]
221 221  
222 222  
223 -After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server.
274 +After configuring the server address and (% style="color:green" %)**reset CPN01**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
224 224  
225 -[[image:1670405841875-916.png]] ​
276 +[[image:image-20221021110956-9.png]] ​
226 226  
227 227  
228 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
229 229  
280 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
230 230  
282 +
231 231  (% style="color:blue" %)**AT Commands:**
232 232  
233 233  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -243,9 +243,10 @@
243 243  
244 244  ​
245 245  
246 -=== 2.2.5 Use MQTT protocol to uplink data ===
247 247  
299 +=== 2.2.6 Use MQTT protocol to uplink data ===
248 248  
301 +
249 249  (% style="color:blue" %)**AT Commands:**
250 250  
251 251  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -262,10 +262,10 @@
262 262  
263 263  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
264 264  
265 -​ [[image:image-20221118103445-7.png]]
318 +​ [[image:image-20221021111058-12.png]]
266 266  
267 267  
268 -[[image:1670405928926-116.png]]
321 +[[image:image-20221021111201-16.png||height="472" width="653"]]
269 269  
270 270  ​
271 271  
... ... @@ -272,9 +272,10 @@
272 272  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.
273 273  
274 274  
275 -=== 2.2.6 Use TCP protocol to uplink data ===
276 276  
329 +=== 2.2.7 Use TCP protocol to uplink data ===
277 277  
331 +
278 278  (% style="color:blue" %)**AT Commands:**
279 279  
280 280  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -281,19 +281,19 @@
281 281  
282 282  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
283 283  
284 -​ [[image:1670406036256-101.png||height="676" width="713"]]
338 +​ [[image:image-20221021111125-14.png]]
285 285  
286 -
287 287  [[image:image-20221021111131-15.png]]
288 288  
289 289  ​
290 290  
291 -=== 2.2.7 Change Update Interval ===
292 292  
345 +=== 2.2.8 Change Update Interval ===
293 293  
347 +
294 294  User can use below command to change the (% style="color:blue" %)**uplink interval**.
295 295  
296 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
350 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
297 297  
298 298  (% style="color:red" %)**NOTE:**
299 299  
... ... @@ -300,75 +300,63 @@
300 300  1.  By default, the device will send an uplink message every 4 hour.
301 301  
302 302  
357 +
303 303  == 2.3  Uplink Payload ==
304 304  
305 305  
306 -The uplink payload includes 26 bytes in total by default.
361 +The uplink payload includes 123 bytes in total by default.
307 307  
308 -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.
363 +Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
309 309  
310 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
311 311  
312 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
313 -|=(% 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**
314 -|=(% 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)
366 +(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
367 +|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:60px" %)**3**
368 +|=(% style="width: 96px;" %)**Value**|(% style="width:84px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:44px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:121px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:52px" %)MOD|(% style="width:84px" %)[[ Calculate Flag>>||anchor="H2.4.5A0CalculateFlag"]]|(% style="width:116px" %)[[Contact Status>>||anchor="H2.4.7A0ContactStatus"]]|(% style="width:57px" %)[[Alarm>>||anchor="H2.4.6A0Alarm"]]|(% style="width:91px" %)[[Total pulse>>||anchor="H2.4.8A0Totalpulse"]]
315 315  
316 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
317 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
318 -**1-32 group**
319 -)))
320 -|(% 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" %)...
370 +(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
371 +|(% style="width:100px" %)**3**|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:100px" %)**3**|(% style="width:80px" %)4|(% style="width:50px" %)**8 group**
372 +|(% style="width:176px" %)[[The last open duration>>||anchor="H2.4.9A0Thelastopenduration"]]|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% style="width:115px" %)Contact Status|(% style="width:92px" %)Total pulse|(% style="width:169px" %)The last open duration|(% style="width:97px" %)Time stamp|(% style="width:74px" %)...
321 321  
322 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
374 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
323 323  
376 +[[image:image-20221021111201-16.png||height="572" width="792"]]
324 324  
325 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
326 -|=(% 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**
327 -|=(% 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)
328 328  
329 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
330 -|(% 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**
331 -|(% 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)
332 -
333 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
334 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
335 -**1-32 group**
336 -)))
337 -|(% 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" %)......
338 -
339 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
340 -
341 -[[image:image-20221117145932-2.png]]
342 -
343 -
344 344  The payload is ASCII string, representative same HEX:
345 345  
346 -**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__(%%)**
381 +**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0c78__(% style="color:#00b0f0" %) __17__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__ (% style="color:#660066" %)__00__ (% style="color:#aaaa40" %)__000009__(% style="color:#663300" %) __000002__ (% style="color:#d60093" %)__6315537b__ (% style="color:#660066" %)__01 00000b 02 0000026 63510fed__ (%%)__0100000e0200000263510f39__ __010000000000000063510e85__ __010000000000000063510d2e__ __010000000000000063510c7a__ __010000000000000063510bc6__ __010000000000000063510954__ __010000000000000063510882 __**
347 347  
348 348  **where:**
349 349  
350 350  * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
351 351  
352 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
387 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
353 353  
354 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
389 +* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
355 355  
356 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
391 +* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
357 357  
358 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
393 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
359 359  
360 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
395 +* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
361 361  
362 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
397 +* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
363 363  
364 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
399 +* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
365 365  
366 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
401 +* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
367 367  
368 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
403 +* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
369 369  
405 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
406 +
407 +* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
408 +
409 +* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
410 +
370 370  == 2.4  Payload Explanation and Sensor Interface ==
371 371  
413 +
372 372  === 2.4.1  Device ID ===
373 373  
374 374  
... ... @@ -383,18 +383,20 @@
383 383  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
384 384  
385 385  
428 +
386 386  === 2.4.2  Version Info ===
387 387  
388 388  
389 389  Specify the software version: 0x64=100, which means firmware version 1.00.
390 390  
391 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
434 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
392 392  
393 393  
437 +
394 394  === 2.4.3  Battery Info ===
395 395  
396 396  
397 -Check the battery voltage for NDS03A.
441 +Check the battery voltage for CPN01.
398 398  
399 399  Ex1: 0x0B45 = 2885mV
400 400  
... ... @@ -401,6 +401,7 @@
401 401  Ex2: 0x0B49 = 2889mV
402 402  
403 403  
448 +
404 404  === 2.4.4  Signal Strength ===
405 405  
406 406  
... ... @@ -419,38 +419,70 @@
419 419  **99**    Not known or not detectable
420 420  
421 421  
422 -=== 2.4.5  Disalarm: (default: 0) ===
423 423  
468 +=== 2.4.5  Calculate Flag ===
424 424  
425 -(% 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.
426 426  
427 -(% 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.
471 +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.
428 428  
429 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
473 +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.
430 430  
475 +Default value: 0. 
431 431  
432 -=== 2.4.6  Keep Status & Keep Time ===
477 +Range (6 bits): (b)000000 ~~ (b) 111111
433 433  
434 434  
435 -Shows the configure value of Alarm Base on Timeout Feature
436 436  
481 +=== 2.4.6  Alarm ===
437 437  
438 -=== 2.4.7  Timestamp ===
439 439  
484 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
440 440  
441 -Timestamp : 0x6315537b =1662342011
442 442  
443 443  
444 -=== 2.4.8  Switch Dual Channel Mode ===
488 +=== 2.4.7  Contact Status ===
445 445  
446 446  
447 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
491 +0: Open
448 448  
493 +1: Close
449 449  
495 +
496 +
497 +=== 2.4.8  Total pulse ===
498 +
499 +
500 +Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
501 +
502 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
503 +
504 +
505 +
506 +=== 2.4.9  The last open duration ===
507 +
508 +
509 +Dry Contact last open duration.
510 +
511 +Unit: min.
512 +
513 +[[image:image-20221021111346-17.png||height="146" width="770"]]
514 +
515 +
516 +
517 +=== 2.4.10  Timestamp ===
518 +
519 +
520 +Timestamp : 0x6315537b =1662342011
521 +
522 +Convert Unix timestamp to time 2022-9-5 9:40:11.
523 +
524 +**~ **
525 +
526 +
450 450  == 2.5  Downlink Payload ==
451 451  
452 452  
453 -By default, NDS03A prints the downlink payload to console port.
530 +By default, CPN01 prints the downlink payload to console port.
454 454  
455 455  [[image:image-20221021111414-18.png]] ​
456 456  
... ... @@ -467,7 +467,7 @@
467 467  
468 468  * (% style="color:#037691" %)**Reset**
469 469  
470 -If payload = 0x04FF, it will reset the NDS03A
547 +If payload = 0x04FF, it will reset the NSE01
471 471  
472 472  * (% style="color:#037691" %)**INTMOD**
473 473  
... ... @@ -474,19 +474,20 @@
474 474  Downlink Payload: 06000003, Set AT+INTMOD=3
475 475  
476 476  
554 +
477 477  == 2.6  ​LED Indicator ==
478 478  
479 479  
480 -The NDS03A has an internal LED which is to show the status of different states.
558 +The CPN01 has an internal LED which is to show the status of different states.
481 481  
482 482  * When the device starts normally, the LED will light up for 1 second.
483 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
561 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
484 484  * For each uplink probe, LED will be on for 500ms.
485 485  
486 486  == 2.7  Alarm Base on Timeout ==
487 487  
488 488  
489 -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:
567 +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:
490 490  
491 491  
492 492  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -502,25 +502,17 @@
502 502  
503 503  If keep time = 0, Disable Alarm Base on Timeout feature.
504 504  
505 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
583 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
506 506  
507 507  
508 508  (% style="color:blue" %)**AT Command to configure:**
509 509  
510 -(% style="color:blue" %)**PB14 PIN:**
588 +(% 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.
511 511  
512 -(% 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.
513 -
514 514  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
515 515  
516 516  
517 -(% style="color:blue" %)**PB15 PIN:**
518 518  
519 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
520 -
521 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
522 -
523 -
524 524  == 2.8  Set debug mode ==
525 525  
526 526  
... ... @@ -542,57 +542,54 @@
542 542  [[image:image-20221021111527-19.png]]
543 543  
544 544  
545 -== 2.10  Count Mod ==
546 546  
616 +== 2.10  Set trigger mode ==
547 547  
548 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
549 549  
550 -[[image:image-20221118092935-1.png]]
619 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
551 551  
621 +Feature: Set the trigger interrupt mode.
552 552  
553 -== 2.11  Interrupt Pin Channel Mod ==
623 +[[image:image-20221021111552-20.png]]
554 554  
555 555  
556 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
557 557  
558 -[[image:image-20221118093144-2.png]]
627 +== 2.11  Set the calculate flag ==
559 559  
560 560  
561 -== 2.12 TTRIG1/2 timeout status alarm ==
630 +Feature: Set the calculate flag
562 562  
632 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
563 563  
564 -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.
634 +[[image:image-20221021111711-22.png]]
565 565  
566 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
567 567  
568 -[[image:image-20221118093512-3.png]]
569 569  
638 +== 2.12 Set count number ==
570 570  
571 -== 2.13  Select counting mode ==
572 572  
641 +Feature: Manually set the count number
573 573  
574 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
643 +(% style="color:blue" %)**AT Command: AT+SETCNT**
575 575  
576 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
645 +[[image:image-20221021111748-24.png]]
577 577  
578 -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.
579 579  
580 -[[image:image-20221118093658-4.png]]
581 581  
649 +== 2.13  Set the number of data to be uploaded and the recording time ==
582 582  
583 -== 2.14  Set the number of data to be uploaded and the recording time ==
584 584  
585 -
586 586  (% style="color:blue" %)**AT Command:**
587 587  
588 -(% 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)
654 +(% 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)
589 589  
590 -(% 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.
656 +(% 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.
591 591  
592 592  
593 -== 2.15  Read or Clear cached data ==
594 594  
660 +== 2.14  Read or Clear cached data ==
595 595  
662 +
596 596  (% style="color:blue" %)**AT Command:**
597 597  
598 598  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -599,24 +599,27 @@
599 599  
600 600  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
601 601  
602 -[[image:image-20221118094227-5.png]]
669 +[[image:image-20221021111810-25.png||height="364" width="797"]]
603 603  
604 604  
605 -== 2.16  ​Firmware Change Log ==
606 606  
673 +== 2.15  ​Firmware Change Log ==
607 607  
608 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
609 609  
676 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
677 +
610 610  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
611 611  
612 612  
613 -== 2.17  ​Battery Analysis ==
614 614  
615 -=== 2.17.1  ​Battery Type ===
682 +== 2.16  ​Battery Analysis ==
616 616  
617 617  
618 -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.
685 +=== 2.16.1  ​Battery Type ===
619 619  
687 +
688 +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.
689 +
620 620  The battery is designed to last for several years depends on the actual use environment and update interval. 
621 621  
622 622  The battery-related documents as below:
... ... @@ -630,9 +630,10 @@
630 630  [[image:image-20221021111911-26.png]] ​
631 631  
632 632  
633 -=== 2.17.2  Power consumption Analyze ===
634 634  
704 +=== 2.16.2  Power consumption Analyze ===
635 635  
706 +
636 636  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.
637 637  
638 638  Instruction to use as below:
... ... @@ -652,18 +652,21 @@
652 652  [[image:1666596205057-567.png]] ​
653 653  
654 654  
655 -=== 2.17.3  ​Battery Note ===
656 656  
727 +=== 2.16.3  ​Battery Note ===
657 657  
729 +
658 658  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.
659 659  
660 660  
661 -=== 2.17.4  Replace the battery ===
662 662  
734 +=== 2.16.4  Replace the battery ===
663 663  
664 -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).
665 665  
737 +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).
666 666  
739 +
740 +
667 667  = 3. ​ Access NB-IoT Module =
668 668  
669 669  
... ... @@ -671,12 +671,13 @@
671 671  
672 672  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/]] 
673 673  
748 +[[image:image-20221021112006-28.png]] ​
674 674  
675 -[[image:image-20221118094449-6.png]] ​
676 676  
677 677  
678 678  = 4.  Using the AT Commands =
679 679  
754 +
680 680  == 4.1  Access AT Commands ==
681 681  
682 682  
... ... @@ -723,21 +723,15 @@
723 723  
724 724  AT+ DEBUG   : Enable or Disable debug mode
725 725  
726 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
801 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
727 727  
728 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
803 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
729 729  
730 -AT+COUNTMOD  :  Get or Set the count mode
805 +AT+ CALCFLAG   : Get or Set the calculate flag
731 731  
732 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
807 +AT+ CLRC   : Clear current door open count
733 733  
734 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
735 735  
736 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
737 -
738 -AT+ CLRC   :  Clear current door open count
739 -
740 -
741 741  (% style="color:blue" %)**COAP Management**      
742 742  
743 743  AT+URI            : Resource parameters
... ... @@ -768,8 +768,10 @@
768 768  AT+PWORD  : Serial Access Password
769 769  
770 770  
840 +
771 771  = ​5.  FAQ =
772 772  
843 +
773 773  == 5.1 ​ How to Upgrade Firmware ==
774 774  
775 775  
... ... @@ -777,11 +777,13 @@
777 777  
778 778  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]]
779 779  
780 -(% 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.**
851 +(% 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.**
781 781  
782 782  
854 +
783 783  = 6.  Trouble Shooting =
784 784  
857 +
785 785  == 6.1  ​Connection problem when uploading firmware ==
786 786  
787 787  
... ... @@ -788,6 +788,7 @@
788 788  (% 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]]
789 789  
790 790  
864 +
791 791  == 6.2  AT Command input doesn't work ==
792 792  
793 793  
... ... @@ -794,19 +794,27 @@
794 794  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.
795 795  
796 796  
871 +
797 797  = 7. ​ Order Info =
798 798  
799 799  
800 -Part Number**:** NDS03A
875 +Part Number**:** CPN01
801 801  
802 802  
878 +
803 803  = 8.  Packing Info =
804 804  
805 805  
806 806  (% style="color:blue" %)**Package Includes**:
807 807  
808 -* NDS03A Open/Close Door Sensor x 1
884 +* CPN01 Open/Close Sensor x 1
885 +* External antenna x 1
809 809  
887 +(% style="color:blue" %)**Dimension and weight**:
888 +
889 +* Size: 195 x 125 x 55 mm
890 +* Weight:   420g
891 +
810 810  = 9.  Support =
811 811  
812 812  
1670404362039-351.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -492.6 KB
Content
1670405841875-916.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.0 KB
Content
LMDS200_10.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 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
image-20221207170748-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.1 KB
Content
image-20221207170748-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.9 KB
Content
image-20221207173200-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
image-20221207173300-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.0 KB
Content

Applications

Navigation

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