Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 90.3 >
edited by Xiaoling
on 2022/12/13 11:28
To version < 58.4 >
edited by Xiaoling
on 2022/11/17 14:02
>
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,73 +1,66 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg||height="572" width="572"]]
2 +[[image:image-20221117105556-1.png]]
3 3  
4 4  
5 5  
6 6  
7 7  
8 -(% style="display:none" %) (%%)
9 9  
10 10  
11 -
12 -
13 -
14 14  **Table of Contents：**
15 15  
16 -{{toc/}}
17 17  
18 18  
19 19  
20 20  
21 -
22 -
23 -
24 -
25 -
26 26  = 1.  Introduction =
27 27  
28 -== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
29 29  
19 +== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
30 30  
21 +
31 31  (((
32 -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.
23 +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.
33 33  )))
34 34  
35 35  (((
36 -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.
27 +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.
37 37  )))
38 38  
39 39  (((
40 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
31 +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.
41 41  )))
42 42  
43 43  (((
44 -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.
35 +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.
45 45  )))
46 46  
47 47  (((
48 -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.
39 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
49 49  )))
50 50  
51 51  (((
52 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
43 +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.
53 53  )))
54 54  
55 55  (((
56 -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)
47 +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)
57 57  )))
58 58  
59 59  (((
60 -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.
51 +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.
61 61  )))
62 62  
63 63  
55 +
64 64  == ​1.2  Features ==
65 65  
66 66  
67 67  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
68 -* Short uplink interval for Distance Alarm
60 +* Open/Close detect
61 +* Open/Close statistics
69 69  * Monitor Battery Level
70 -* Microwave Radar for distance detection
63 +* connect two door sensors
71 71  * Datalog feature
72 72  * Uplink periodically
73 73  * Downlink to change configure
... ... @@ -80,38 +80,29 @@
80 80  
81 81  
82 82  
83 -== 1.3 Radar probe specification ==
76 +== 1.3  Storage & Operation ==
84 84  
85 85  
86 -* Measuring Method: FMCW
87 -* Frequency: 24.000 ~~ 24.500 GHz
88 -* Measurement output power: 6dBm
89 -* Measure range: 0.5 ~~ 20m
90 -* Accuracy: ±0.1m
91 -* Resolution: 0.01m
92 -* Horizontal Angel: 78°
93 -* Vertical Angel: 23°
79 +Temperature -40°C to +85°C
94 94  
95 95  
82 +== 1.4  Mechanical ==
96 96  
97 -== 1.4  Storage Temperature ==
98 98  
85 +[[image:image-20221117114937-4.png]]
99 99  
100 - -40°C to +85°C
101 101  
88 +[[image:image-20221117114949-5.png]]
102 102  
90 +
91 +[[image:image-20221117115010-6.png]]
92 +
93 +
94 +
103 103  == 1.5 ​ Applications ==
104 104  
105 105  
106 -* Horizontal distance measurement
107 -* Liquid level measurement
108 -* Parking management system
109 -* Object proximity and presence detection
110 -* Intelligent trash can management system
111 -* Robot obstacle avoidance
112 -* Automatic control
113 -* Sewer
114 -* Bottom water level monitoring
98 +[[image:image-20221117114842-3.png]]
115 115  
116 116  
117 117  
... ... @@ -121,66 +121,111 @@
121 121  (% style="color:blue" %)**Common DC Characteristics:**
122 122  
123 123  * Supply Voltage: 2.1v ~~ 3.6v
124 -* Operating Temperature: 0 ~~ 70°C
108 +* Operating Temperature: -40 ~~ 85°C
125 125  
126 126  (% style="color:blue" %)**NB-IoT Spec:**
127 127  
128 -* B1 @H-FDD: 2100MHz
129 -* B3 @H-FDD: 1800MHz
130 -* B8 @H-FDD: 900MHz
131 -* B5 @H-FDD: 850MHz
132 -* B20 @H-FDD: 800MHz
133 -* B28 @H-FDD: 700MHz
112 +* - B1 @H-FDD: 2100MHz
113 +* - B3 @H-FDD: 1800MHz
114 +* - B8 @H-FDD: 900MHz
115 +* - B5 @H-FDD: 850MHz
116 +* - B20 @H-FDD: 800MHz
117 +* - B28 @H-FDD: 700MHz
134 134  
135 135  
136 136  
137 -== 1.7  Installation ==
121 +== 1.7  Pin Definitions and Switch ==
138 138  
139 139  
140 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
124 +[[image:image-20221021110429-4.png]]
141 141  
142 142  
143 -[[image:image-20221207170748-1.png]]
127 +=== 1.7.1  Pin Definition ===
144 144  
145 145  
146 - [[image:image-20221207170748-2.png||height="345" width="634"]]
130 +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]]
147 147  
148 148  
149 -== 1.8  Pin Definitions and Switch ==
150 150  
134 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
151 151  
152 -[[image:1670404362039-351.png]]
153 153  
137 +Power on Device when putting this jumper.
154 154  
155 -= 2.  Use NMDS200 to communicate with IoT Server =
156 156  
140 +
141 +=== 1.7.3  BOOT MODE / SW1 ===
142 +
143 +
144 +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.
145 +
146 +2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
147 +
148 +
149 +
150 +=== 1.7.4  Reset Button ===
151 +
152 +
153 +Press to reboot the device.
154 +
155 +
156 +
157 +=== 1.7.5  LED ===
158 +
159 +
160 +The LED will blink when :
161 +
162 +1.  Boot the device in flash mode
163 +
164 +2.  Send an uplink packet
165 +
166 +
167 +
168 +== 1.8  Magnet Distance ==
169 +
170 +
171 +(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
172 +
173 +(% style="color:blue" %)**Iron Door:**(%%)**  **30 ~~ 45mm
174 +
175 +
176 +
177 += 2.  Use CPN01 to communicate with IoT Server =
178 +
179 +
157 157  == 2.1  How it works ==
158 158  
159 159  
160 -The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
183 +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.
161 161  
162 -The diagram below shows the working flow in the default firmware of NMDS200:
185 +The diagram below shows the working flow in the default firmware of CPN01:
163 163  
164 -[[image:image-20221021110615-5.png||height="996" width="492"]]
187 +[[image:image-20221021110615-5.png]]
165 165  
166 166  
167 -== 2.2 ​ Configure NMDS200 ==
168 168  
191 +== 2.2 ​ Configure CPN01 ==
169 169  
170 -To use NMDS200 in your city, make sure to meet below requirements:
171 171  
194 +=== 2.2.1 Test Requirement ===
195 +
196 +
197 +To use CPN01 in your city, make sure to meet below requirements:
198 +
172 172  * Your local operator has already distributed an NB-IoT Network.
173 -* The local NB-IoT network used the band that NMDS200 supports.
200 +* The local NB-IoT network used the band that CPN01 supports.
174 174  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
175 175  
176 -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.
203 +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.
177 177  
178 -[[image:image-20221209090938-1.png]]
205 +[[image:image-20221023000439-3.png]]
179 179  
207 + ​
180 180  
181 -=== 2.2.1 Insert NB-IoT SIM card ===
182 182  
210 +=== 2.2.2 Insert NB-IoT SIM card ===
183 183  
212 +
184 184  Insert the NB-IoT Card get from your provider.
185 185  
186 186  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -188,11 +188,12 @@
188 188  [[image:image-20221021110745-6.png]] ​
189 189  
190 190  
191 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
192 192  
221 +=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
193 193  
194 -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.
195 195  
224 +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.
225 +
196 196  (% style="color:blue" %)**Connection:**
197 197  
198 198  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -214,23 +214,24 @@
214 214  
215 215  * Flow Control: (% style="color:red" %)**None**
216 216  
217 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
247 +Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
218 218  
219 219  ​[[image:image-20221021110817-7.png]]
220 220  
221 -NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
251 +CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
222 222  
223 223  
224 224  (% 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]]
225 225  
226 226  
227 -=== 2.2.3 Use CoAP protocol to uplink data ===
228 228  
258 +=== 2.2.4 Use CoAP protocol to uplink data ===
229 229  
260 +
230 230  (% 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/]]
231 231  
232 232  
233 -(% style="color:blue" %)**Use below commands in NMDS200:**
264 +(% style="color:blue" %)**Use below commands in CPN01:**
234 234  
235 235  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
236 236  
... ... @@ -240,17 +240,18 @@
240 240  
241 241  For parameter description, please refer to AT command set
242 242  
243 -[[image:1670471530120-960.png||height="647" width="674"]]
274 +[[image:image-20221021110948-8.png]]
244 244  
245 245  
246 -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.
277 +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.
247 247  
248 -[[image:1670405841875-916.png]] ​
279 +[[image:image-20221021110956-9.png]] ​
249 249  
250 250  
251 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
252 252  
283 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
253 253  
285 +
254 254  (% style="color:blue" %)**AT Commands:**
255 255  
256 256  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -259,7 +259,7 @@
259 259  
260 260  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
261 261  
262 -​ [[image:1670471559211-638.png]]
294 +​ [[image:image-20221021111025-10.png]]
263 263  
264 264  
265 265  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -266,9 +266,10 @@
266 266  
267 267  ​
268 268  
269 -=== 2.2.5 Use MQTT protocol to uplink data ===
270 270  
302 +=== 2.2.6 Use MQTT protocol to uplink data ===
271 271  
304 +
272 272  (% style="color:blue" %)**AT Commands:**
273 273  
274 274  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -285,10 +285,10 @@
285 285  
286 286  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
287 287  
288 -​ [[image:1670471584490-640.png]]
321 +​ [[image:image-20221021111058-12.png]]
289 289  
290 290  
291 -[[image:1670405928926-116.png]]
324 +[[image:image-20221021111201-16.png||height="472" width="653"]]
292 292  
293 293  ​
294 294  
... ... @@ -295,9 +295,10 @@
295 295  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.
296 296  
297 297  
298 -=== 2.2.6 Use TCP protocol to uplink data ===
299 299  
332 +=== 2.2.7 Use TCP protocol to uplink data ===
300 300  
334 +
301 301  (% style="color:blue" %)**AT Commands:**
302 302  
303 303  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -304,76 +304,82 @@
304 304  
305 305  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
306 306  
307 -​ [[image:1670471613823-833.png]]
341 +​ [[image:image-20221021111125-14.png]]
308 308  
309 -
310 310  [[image:image-20221021111131-15.png]]
311 311  
312 312  ​
313 313  
314 -=== 2.2.7 Change Update Interval ===
315 315  
348 +=== 2.2.8 Change Update Interval ===
316 316  
350 +
317 317  User can use below command to change the (% style="color:blue" %)**uplink interval**.
318 318  
319 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
353 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
320 320  
321 321  (% style="color:red" %)**NOTE:**
322 322  
323 -1.  By default, the device will send an uplink message every 4 hour.
357 +1.  By default, the device will send an uplink message every 1 hour.
324 324  
325 325  
360 +
326 326  == 2.3  Uplink Payload ==
327 327  
328 328  
329 -The uplink payload includes 23 bytes in total by default.
364 +The uplink payload includes 123 bytes in total by default.
330 330  
331 -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.
366 +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.
332 332  
333 333  
334 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %)
335 -|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:30px" %)**2**|(% style="width:30px" %)**2**|(% style="width:75px" %)**1**|(% style="width:30px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**
336 -|=(% 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" %)Exit flag|(% style="width:94px" %) [[Distance 1>>||anchor="H2.4.5A0Distance"]] |(% style="width:93px" %) [[Distance 2>>||anchor="H2.4.5A0Distance"]]
369 +(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
370 +|=(% 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**
371 +|=(% 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"]]
337 337  
338 -(% border="1" style="background-color:#ffffcc; color:green; width:429px" %)
339 -|(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((
340 -**1-32 group**
341 -)))
342 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...
373 +(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
374 +|(% 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**
375 +|(% 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" %)...
343 343  
344 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
377 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
345 345  
346 -[[image:1670406261143-723.png]]
379 +[[image:image-20221021111201-16.png||height="572" width="792"]]
347 347  
348 348  
349 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
382 +The payload is ASCII string, representative same HEX:
350 350  
351 -**0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
384 +**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 __**
352 352  
353 353  **where:**
354 354  
355 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
388 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
356 356  
357 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
390 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
358 358  
359 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
392 +* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
360 360  
361 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
394 +* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
362 362  
363 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
396 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
364 364  
365 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
398 +* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
366 366  
367 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
400 +* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
368 368  
369 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
402 +* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
370 370  
371 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
404 +* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
372 372  
406 +* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
373 373  
408 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
374 374  
410 +* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
411 +
412 +* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
413 +
375 375  == 2.4  Payload Explanation and Sensor Interface ==
376 376  
416 +
377 377  === 2.4.1  Device ID ===
378 378  
379 379  
... ... @@ -388,18 +388,20 @@
388 388  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
389 389  
390 390  
431 +
391 391  === 2.4.2  Version Info ===
392 392  
393 393  
394 394  Specify the software version: 0x64=100, which means firmware version 1.00.
395 395  
396 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
437 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
397 397  
398 398  
440 +
399 399  === 2.4.3  Battery Info ===
400 400  
401 401  
402 -Check the battery voltage for NMDS200.
444 +Check the battery voltage for CPN01.
403 403  
404 404  Ex1: 0x0B45 = 2885mV
405 405  
... ... @@ -406,54 +406,89 @@
406 406  Ex2: 0x0B49 = 2889mV
407 407  
408 408  
451 +
409 409  === 2.4.4  Signal Strength ===
410 410  
411 411  
412 412  NB-IoT Network signal Strength.
413 413  
414 -(% style="color:blue" %)**Ex1: 0x1d = 29**
457 +**Ex1: 0x1d = 29**
415 415  
416 -(% style="color:#037691" %)**0** (%%) -113dBm or less
459 +**0**  -113dBm or less
417 417  
418 -(% style="color:#037691" %)**1**  (%%) -111dBm
461 +**1**  -111dBm
419 419  
420 -(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
463 +**2...30** -109dBm... -53dBm
421 421  
422 -(% style="color:#037691" %)**31** (%%) -51dBm or greater
465 +**31**   -51dBm or greater
423 423  
424 -(% style="color:#037691" %)**99** (%%) Not known or not detectable
467 +**99**    Not known or not detectable
425 425  
426 426  
427 -=== 2.4.5  Distance ===
428 428  
471 +=== 2.4.5  Calculate Flag ===
429 429  
430 -[[image:1670407401682-959.png]]
431 431  
474 +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.
432 432  
433 -(% style="color:blue" %)**Object1 Distance:**
476 +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.
434 434  
435 -Distance between sensor probe to the first object. (unit: cm)
478 +Default value: 0. 
436 436  
437 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
480 +Range (6 bits): (b)000000 ~~ (b) 111111
438 438  
439 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
440 440  
441 441  
442 -(% style="color:blue" %)**Object2 Distance:**
484 +=== 2.4.6  Alarm ===
443 443  
444 -Distance between sensor probe to the second object. (unit: cm)
445 445  
487 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
446 446  
447 -=== 2.4.6  Timestamp ===
448 448  
449 449  
491 +=== 2.4.7  Contact Status ===
492 +
493 +
494 +0: Open
495 +
496 +1: Close
497 +
498 +
499 +
500 +=== 2.4.8  Total pulse ===
501 +
502 +
503 +Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
504 +
505 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
506 +
507 +
508 +
509 +=== 2.4.9  The last open duration ===
510 +
511 +
512 +Dry Contact last open duration.
513 +
514 +Unit: min.
515 +
516 +[[image:image-20221021111346-17.png||height="146" width="770"]]
517 +
518 +
519 +
520 +=== 2.4.10  Timestamp ===
521 +
522 +
450 450  Timestamp : 0x6315537b =1662342011
451 451  
525 +Convert Unix timestamp to time 2022-9-5 9:40:11.
452 452  
527 +**~ **
528 +
529 +
453 453  == 2.5  Downlink Payload ==
454 454  
455 455  
456 -By default, NMDS200 prints the downlink payload to console port.
533 +By default, CPN01 prints the downlink payload to console port.
457 457  
458 458  [[image:image-20221021111414-18.png]] ​
459 459  
... ... @@ -470,7 +470,7 @@
470 470  
471 471  * (% style="color:#037691" %)**Reset**
472 472  
473 -If payload = 0x04FF, it will reset the NMDS200
550 +If payload = 0x04FF, it will reset the NSE01
474 474  
475 475  * (% style="color:#037691" %)**INTMOD**
476 476  
... ... @@ -477,47 +477,115 @@
477 477  Downlink Payload: 06000003, Set AT+INTMOD=3
478 478  
479 479  
557 +
480 480  == 2.6  ​LED Indicator ==
481 481  
482 482  
483 -The NMDS200 has an internal LED which is to show the status of different states.
561 +The CPN01 has an internal LED which is to show the status of different states.
484 484  
485 485  * When the device starts normally, the LED will light up for 1 second.
486 -* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
564 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
487 487  * For each uplink probe, LED will be on for 500ms.
488 488  
567 +== 2.7  Alarm Base on Timeout ==
489 489  
490 490  
491 -== 2.7  Distance alarm function ==
570 +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:
492 492  
493 493  
494 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
573 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
495 495  
496 -(% style="color:#037691" %)**Example 1:**
575 +Keep Status = 1: Monitor Close to Open event
497 497  
498 -AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
577 +Keep Status = 0: Monitor Open to Close event
499 499  
500 -AT+ ALARM2 =min,max
501 501  
580 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
502 502  
503 -(% style="color:#037691" %)**Example 2:**
582 +Range 0 ~~ 65535(0xFFFF) seconds.
504 504  
505 -AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
584 +If keep time = 0, Disable Alarm Base on Timeout feature.
506 506  
586 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
507 507  
508 -== 2.8  Set the number of data to be uploaded and the recording time ==
509 509  
589 +(% style="color:blue" %)**AT Command to configure:**
510 510  
591 +(% 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.
592 +
593 +(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
594 +
595 +
596 +
597 +== 2.8  Set debug mode ==
598 +
599 +
600 +Feature: Enable or Disable debug mode
601 +
602 +(% style="color:blue" %)**AT Command: AT+DEBUG**
603 +
604 +[[image:image-20221021111629-21.png]]
605 +
606 +
607 +
608 +== 2.9  Clear Flash Record ==
609 +
610 +
611 +Feature: Clear flash storage for data log feature.
612 +
613 +(% style="color:blue" %)**AT Command: AT+CLRDTA**
614 +
615 +[[image:image-20221021111527-19.png]]
616 +
617 +
618 +
619 +== 2.10  Set trigger mode ==
620 +
621 +
622 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
623 +
624 +Feature: Set the trigger interrupt mode.
625 +
626 +[[image:image-20221021111552-20.png]]
627 +
628 +
629 +
630 +== 2.11  Set the calculate flag ==
631 +
632 +
633 +Feature: Set the calculate flag
634 +
635 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
636 +
637 +[[image:image-20221021111711-22.png]]
638 +
639 +
640 +
641 +== 2.12 Set count number ==
642 +
643 +
644 +Feature: Manually set the count number
645 +
646 +(% style="color:blue" %)**AT Command: AT+SETCNT**
647 +
648 +[[image:image-20221021111748-24.png]]
649 +
650 +
651 +
652 +== 2.13  Set the number of data to be uploaded and the recording time ==
653 +
654 +
511 511  (% style="color:blue" %)**AT Command:**
512 512  
513 -(% 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)
657 +(% 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)
514 514  
515 -(% 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.
659 +(% 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.
516 516  
517 517  
518 -== 2.9  Read or Clear cached data ==
519 519  
663 +== 2.14  Read or Clear cached data ==
520 520  
665 +
521 521  (% style="color:blue" %)**AT Command:**
522 522  
523 523  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -524,24 +524,27 @@
524 524  
525 525  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
526 526  
527 -[[image:1670408172929-569.png]]
672 +[[image:image-20221021111810-25.png||height="364" width="797"]]
528 528  
529 529  
530 -== 2.10  ​Firmware Change Log ==
531 531  
676 +== 2.15  ​Firmware Change Log ==
532 532  
533 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]
534 534  
679 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
680 +
535 535  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
536 536  
537 537  
538 -== 2.11  ​Battery Analysis ==
539 539  
540 -=== 2.11.1  ​Battery Type ===
685 +== 2.16  ​Battery Analysis ==
541 541  
542 542  
543 -The NMDS200 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.
688 +=== 2.16.1  ​Battery Type ===
544 544  
690 +
691 +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.
692 +
545 545  The battery is designed to last for several years depends on the actual use environment and update interval. 
546 546  
547 547  The battery-related documents as below:
... ... @@ -555,9 +555,10 @@
555 555  [[image:image-20221021111911-26.png]] ​
556 556  
557 557  
558 -=== 2.11.2  Power consumption Analyze ===
559 559  
707 +=== 2.16.2  Power consumption Analyze ===
560 560  
709 +
561 561  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.
562 562  
563 563  Instruction to use as below:
... ... @@ -577,18 +577,21 @@
577 577  [[image:1666596205057-567.png]] ​
578 578  
579 579  
580 -=== 2.11.3  ​Battery Note ===
581 581  
730 +=== 2.16.3  ​Battery Note ===
582 582  
732 +
583 583  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.
584 584  
585 585  
586 -=== 2.11.4  Replace the battery ===
587 587  
737 +=== 2.16.4  Replace the battery ===
588 588  
589 -The default battery pack of NMDS200 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).
590 590  
740 +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).
591 591  
742 +
743 +
592 592  = 3. ​ Access NB-IoT Module =
593 593  
594 594  
... ... @@ -596,12 +596,13 @@
596 596  
597 597  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/]] 
598 598  
751 +[[image:image-20221021112006-28.png]] ​
599 599  
600 -[[image:image-20221118094449-6.png]] ​
601 601  
602 602  
603 603  = 4.  Using the AT Commands =
604 604  
757 +
605 605  == 4.1  Access AT Commands ==
606 606  
607 607  
... ... @@ -632,63 +632,65 @@
632 632  
633 633  AT+INTMOD            : Set the trigger interrupt mode
634 634  
635 -AT+5VT  : Set extend the time of 5V power  
788 +AT+5VT  : Set extend the time of 5V power  
636 636  
637 -AT+PRO  : Choose agreement
790 +AT+PRO  : Choose agreement
638 638  
639 -AT+RXDL  : Extend the sending and receiving time
792 +AT+RXDL  : Extend the sending and receiving time
640 640  
641 -AT+SERVADDR  : Server Address
794 +AT+SERVADDR  : Server Address
642 642  
643 -AT+TR      :  Get or Set record time
796 +AT+TR      :  Get or Set record time
644 644  
645 -AT+NOUD :  Get or Set the number of data to be uploaded
798 +AT+NOUD      : Get or Set the number of data to be uploaded
646 646  
647 647  AT+CDP     :  Read or Clear cached data
648 648  
649 -AT+DEBUG:  Enable or Disable debug mode
802 +AT+ DEBUG   : Enable or Disable debug mode
650 650  
651 -AT+ALARM1:  Get or Set alarm of distance1
804 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
652 652  
653 -AT+ALARM2:  Get or Set alarm of distance2
806 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
654 654  
655 -AT+GETSENSORVALUE :  Returns the current sensor measurement
808 +AT+ CALCFLAG   : Get or Set the calculate flag
656 656  
657 -AT+POWERIC :  Get or set the Power IC flag
810 +AT+ CLRC   : Clear current door open count
658 658  
659 659  
660 660  (% style="color:blue" %)**COAP Management**      
661 661  
662 -AT+URI :  Resource parameters
815 +AT+URI            : Resource parameters
663 663  
664 664  
665 665  (% style="color:blue" %)**UDP Management**
666 666  
667 -AT+CFM :  Upload confirmation mode (only valid for UDP)
820 +AT+CFM          : Upload confirmation mode (only valid for UDP)
668 668  
669 669  
670 670  (% style="color:blue" %)**MQTT Management**
671 671  
672 -AT+CLIENT  : Get or Set MQTT client
825 +AT+CLIENT               : Get or Set MQTT client
673 673  
674 -AT+UNAME : Get or Set MQTT Username
827 +AT+UNAME  : Get or Set MQTT Username
675 675  
676 -AT+PWD  :  Get or Set MQTT password
829 +AT+PWD                  : Get or Set MQTT password
677 677  
678 -AT+PUBTOPIC :  Get or Set MQTT publish topic
831 +AT+PUBTOPIC  : Get or Set MQTT publish topic
679 679  
680 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
833 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
681 681  
682 682  
683 683  (% style="color:blue" %)**Information**          
684 684  
685 -AT+FDR :  Factory Data Reset
838 +AT+FDR  : Factory Data Reset
686 686  
687 -AT+PWORD :  Serial Access Password
840 +AT+PWORD  : Serial Access Password
688 688  
689 689  
843 +
690 690  = ​5.  FAQ =
691 691  
846 +
692 692  == 5.1 ​ How to Upgrade Firmware ==
693 693  
694 694  
... ... @@ -696,11 +696,13 @@
696 696  
697 697  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]]
698 698  
699 -(% style="color:red" %)**Notice: **(% style="color:blue" %)**NMDS200** (%%)**and (% style="color:blue" %)LMDS200(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
854 +(% 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.**
700 700  
701 701  
857 +
702 702  = 6.  Trouble Shooting =
703 703  
860 +
704 704  == 6.1  ​Connection problem when uploading firmware ==
705 705  
706 706  
... ... @@ -707,6 +707,7 @@
707 707  (% 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]]
708 708  
709 709  
867 +
710 710  == 6.2  AT Command input doesn't work ==
711 711  
712 712  
... ... @@ -713,20 +713,26 @@
713 713  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.
714 714  
715 715  
874 +
716 716  = 7. ​ Order Info =
717 717  
718 718  
719 -Part Number:(% style="color:blue" %)** NMDS200**
878 +Part Number**:** CPN01
720 720  
721 721  
881 +
722 722  = 8.  Packing Info =
723 723  
724 724  
725 725  (% style="color:blue" %)**Package Includes**:
726 726  
727 -* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
887 +* CPN01 Open/Close Sensor x 1
888 +* External antenna x 1
728 728  
890 +(% style="color:blue" %)**Dimension and weight**:
729 729  
892 +* Size: 195 x 125 x 55 mm
893 +* Weight:   420g
730 730  
731 731  = 9.  Support =
732 732  
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
1670406261143-723.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content
1670407401682-959.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -23.7 KB
Content
1670408172929-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -211.8 KB
Content
1670471530120-960.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -67.6 KB
Content
1670471559211-638.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -170.6 KB
Content
1670471584490-640.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.1 KB
Content
1670471613823-833.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-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
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
image-20221208090742-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.7 KB
Content
image-20221209090938-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -121.9 KB
Content
image-20221212171610-1.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -756.0 KB
Content

Applications

Navigation

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