Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 90.7 >
edited by Xiaoling
on 2023/04/04 14:55
To version < 53.2 >
edited by Xiaoling
on 2022/11/17 11:08
>
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,64 +1,44 @@
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  
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.
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.
37 -)))
23 +The Dragino NDS03A is an Open/Close NB-IoT Door Sensor. It detects door open/close status and 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.
38 38  
39 -(((
40 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
41 -)))
25 +The NDS03A will send periodically data 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.
42 42  
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.
45 -)))
27 +NDS03A has a Datalog feature, it will record the open/close event and the user can retrieve the history from NB-IoT.
46 46  
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.
49 -)))
29 +NDS03A has the 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.
50 50  
51 -(((
52 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
31 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
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)
35 +NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
36 +\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
37 +\\CPN01 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
38 +\\To use CPN01, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that CPN01 supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into CPN01 to get NB-IoT network connection.
57 57  )))
58 58  
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.
61 -)))
41 +​
62 62  
63 63  
64 64  == ​1.2  Features ==
... ... @@ -65,9 +65,10 @@
65 65  
66 66  
67 67  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
68 -* Short uplink interval for Distance Alarm
48 +* Open/Close detect
49 +* Open/Close statistics
69 69  * Monitor Battery Level
70 -* Microwave Radar for distance detection
51 +* Uplink on periodically and open/close event
71 71  * Datalog feature
72 72  * Uplink periodically
73 73  * Downlink to change configure
... ... @@ -79,108 +79,134 @@
79 79  * 8500mAh Battery for long-term use
80 80  
81 81  
63 +== 1.3  Specification ==
82 82  
83 -== 1.3 Radar probe specification ==
84 84  
66 +(% style="color:blue" %)**Common DC Characteristics:**
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°
68 +* Supply Voltage: 2.1v ~~ 3.6v
69 +* Operating Temperature: -40 ~~ 85°C
94 94  
71 +(% style="color:blue" %)**NB-IoT Spec:**
95 95  
73 +* - B1 @H-FDD: 2100MHz
74 +* - B3 @H-FDD: 1800MHz
75 +* - B8 @H-FDD: 900MHz
76 +* - B5 @H-FDD: 850MHz
77 +* - B20 @H-FDD: 800MHz
78 +* - B28 @H-FDD: 700MHz
96 96  
97 -== 1.4  Storage Temperature ==
98 98  
81 +== 1.4  Installation ==
99 99  
100 - -40°C to +85°C
101 101  
84 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
102 102  
86 +[[image:image-20221021110329-1.png]]
87 +
88 +
89 +[[image:image-20221022234602-2.png||height="288" width="922"]]
90 +
91 +
92 +
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
96 +* Open/Close Detection
97 +* Pulse meter application
98 +* Dry Contact Detection
115 115  
116 116  
101 +== 1.6  Mechanical ==
117 117  
118 -== 1.6  Specification ==
119 119  
104 +​[[image:image-20221021110415-3.png]]
120 120  
121 -(% style="color:blue" %)**Common DC Characteristics:**
122 122  
123 -* Supply Voltage: 2.1v ~~ 3.6v
124 -* Operating Temperature: 0 ~~ 70°C
125 125  
126 -(% style="color:blue" %)**NB-IoT Spec:**
108 +== 1.7  Pin Definitions and Switch ==
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
134 134  
111 +[[image:image-20221021110429-4.png]]
135 135  
136 136  
137 -== 1.7  Installation ==
114 +=== 1.7.1  Pin Definition ===
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.
117 +CPN01 is pre-configured to connect to two external wires. The other pins are not used. If user wants to know more about other pins, please refer to the **[[LSN50v2 User Manual>>doc:Main.User Manual for LoRaWAN End Nodes.LSN50 & LSN50-V2 - LoRaWAN Sensor Node User Manual.WebHome]]**.
141 141  
142 142  
143 -[[image:image-20221207170748-1.png]]
144 144  
121 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
145 145  
146 - [[image:image-20221207170748-2.png||height="345" width="634"]]
147 147  
124 +Power on Device when putting this jumper.
148 148  
149 -== 1.8  Pin Definitions and Switch ==
150 150  
151 151  
152 -[[image:1670404362039-351.png]]
128 +=== 1.7.3  BOOT MODE / SW1 ===
153 153  
154 154  
155 -= 2.  Use NMDS200 to communicate with IoT Server =
131 +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.
156 156  
133 +2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
134 +
135 +
136 +
137 +=== 1.7.4  Reset Button ===
138 +
139 +
140 +Press to reboot the device.
141 +
142 +
143 +
144 +=== 1.7.5  LED ===
145 +
146 +
147 +The LED will blink when :
148 +
149 +1.  Boot the device in flash mode
150 +
151 +2.  Send an uplink packet
152 +
153 +
154 +
155 += 2.  Use CPN01 to communicate with IoT Server =
156 +
157 +
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.
161 +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:
163 +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"]]
165 +[[image:image-20221021110615-5.png]]
165 165  
166 166  
167 -== 2.2 ​ Configure NMDS200 ==
168 168  
169 +== 2.2 ​ Configure CPN01 ==
169 169  
170 -To use NMDS200 in your city, make sure to meet below requirements:
171 171  
172 +=== 2.2.1 Test Requirement ===
173 +
174 +
175 +To use CPN01 in your city, make sure to meet below requirements:
176 +
172 172  * Your local operator has already distributed an NB-IoT Network.
173 -* The local NB-IoT network used the band that NMDS200 supports.
178 +* 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.
181 +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]]
183 +[[image:image-20221023000439-3.png]]
179 179  
185 + ​
180 180  
181 -=== 2.2.1 Insert NB-IoT SIM card ===
182 182  
188 +=== 2.2.2 Insert NB-IoT SIM card ===
183 183  
190 +
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  
199 +=== 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  
202 +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.
203 +
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**(%%).
225 +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.
229 +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  
236 +=== 2.2.4 Use CoAP protocol to uplink data ===
229 229  
238 +
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:**
242 +(% 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"]]
252 +[[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.
255 +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]] ​
257 +[[image:image-20221021110956-9.png]] ​
249 249  
250 250  
251 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
252 252  
261 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
253 253  
263 +
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]]
272 +​ [[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  
280 +=== 2.2.6 Use MQTT protocol to uplink data ===
271 271  
282 +
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]]
299 +​ [[image:image-20221021111058-12.png]]
289 289  
290 290  
291 -[[image:1670405928926-116.png]]
302 +[[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  
310 +=== 2.2.7 Use TCP protocol to uplink data ===
300 300  
312 +
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,74 +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]]
319 +​ [[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  
326 +=== 2.2.8 Change Update Interval ===
316 316  
328 +
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)
331 +* (% 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.
335 +1.  By default, the device will send an uplink message every 1 hour.
324 324  
325 325  
338 +
326 326  == 2.3  Uplink Payload ==
327 327  
328 328  
329 -The uplink payload includes 23 bytes in total by default.
342 +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.
344 +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"]]
347 +(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
348 +|=(% 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**
349 +|=(% 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" %)...
351 +(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
352 +|(% 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**
353 +|(% 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.
355 +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]]
357 +[[image:image-20221021111201-16.png||height="572" width="792"]]
347 347  
348 348  
349 -The payload is ASCII string, representative same HEX: **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__(%%)**
360 +The payload is ASCII string, representative same HEX:
350 350  
362 +**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 __**
363 +
351 351  **where:**
352 352  
353 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
366 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
354 354  
355 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
368 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
356 356  
357 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
370 +* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
358 358  
359 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
372 +* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
360 360  
361 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
374 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
362 362  
363 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
376 +* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
364 364  
365 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
378 +* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
366 366  
367 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
380 +* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
368 368  
369 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
382 +* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
370 370  
384 +* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
371 371  
386 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
372 372  
388 +* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
389 +
390 +* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
391 +
373 373  == 2.4  Payload Explanation and Sensor Interface ==
374 374  
394 +
375 375  === 2.4.1  Device ID ===
376 376  
377 377  
... ... @@ -386,18 +386,20 @@
386 386  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
387 387  
388 388  
409 +
389 389  === 2.4.2  Version Info ===
390 390  
391 391  
392 392  Specify the software version: 0x64=100, which means firmware version 1.00.
393 393  
394 -For example 0x00 64 : This device is NMDS200 with firmware version 1.0.0.
415 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
395 395  
396 396  
418 +
397 397  === 2.4.3  Battery Info ===
398 398  
399 399  
400 -Check the battery voltage for NMDS200.
422 +Check the battery voltage for CPN01.
401 401  
402 402  Ex1: 0x0B45 = 2885mV
403 403  
... ... @@ -404,54 +404,89 @@
404 404  Ex2: 0x0B49 = 2889mV
405 405  
406 406  
429 +
407 407  === 2.4.4  Signal Strength ===
408 408  
409 409  
410 410  NB-IoT Network signal Strength.
411 411  
412 -(% style="color:blue" %)**Ex1: 0x1d = 29**
435 +**Ex1: 0x1d = 29**
413 413  
414 -(% style="color:#037691" %)**0** (%%) -113dBm or less
437 +**0**  -113dBm or less
415 415  
416 -(% style="color:#037691" %)**1**  (%%) -111dBm
439 +**1**  -111dBm
417 417  
418 -(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
441 +**2...30** -109dBm... -53dBm
419 419  
420 -(% style="color:#037691" %)**31** (%%) -51dBm or greater
443 +**31**   -51dBm or greater
421 421  
422 -(% style="color:#037691" %)**99** (%%) Not known or not detectable
445 +**99**    Not known or not detectable
423 423  
424 424  
425 -=== 2.4.5  Distance ===
426 426  
449 +=== 2.4.5  Calculate Flag ===
427 427  
428 -[[image:1670407401682-959.png]]
429 429  
452 +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.
430 430  
431 -(% style="color:blue" %)**Object1 Distance:**
454 +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.
432 432  
433 -Distance between sensor probe to the first object. (unit: cm)
456 +Default value: 0. 
434 434  
435 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
458 +Range (6 bits): (b)000000 ~~ (b) 111111
436 436  
437 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
438 438  
439 439  
440 -(% style="color:blue" %)**Object2 Distance:**
462 +=== 2.4.6  Alarm ===
441 441  
442 -Distance between sensor probe to the second object. (unit: cm)
443 443  
465 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
444 444  
445 -=== 2.4.6  Timestamp ===
446 446  
447 447  
469 +=== 2.4.7  Contact Status ===
470 +
471 +
472 +0: Open
473 +
474 +1: Close
475 +
476 +
477 +
478 +=== 2.4.8  Total pulse ===
479 +
480 +
481 +Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
482 +
483 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
484 +
485 +
486 +
487 +=== 2.4.9  The last open duration ===
488 +
489 +
490 +Dry Contact last open duration.
491 +
492 +Unit: min.
493 +
494 +[[image:image-20221021111346-17.png||height="146" width="770"]]
495 +
496 +
497 +
498 +=== 2.4.10  Timestamp ===
499 +
500 +
448 448  Timestamp : 0x6315537b =1662342011
449 449  
503 +Convert Unix timestamp to time 2022-9-5 9:40:11.
450 450  
505 +**~ **
506 +
507 +
451 451  == 2.5  Downlink Payload ==
452 452  
453 453  
454 -By default, NMDS200 prints the downlink payload to console port.
511 +By default, CPN01 prints the downlink payload to console port.
455 455  
456 456  [[image:image-20221021111414-18.png]] ​
457 457  
... ... @@ -468,7 +468,7 @@
468 468  
469 469  * (% style="color:#037691" %)**Reset**
470 470  
471 -If payload = 0x04FF, it will reset the NMDS200
528 +If payload = 0x04FF, it will reset the NSE01
472 472  
473 473  * (% style="color:#037691" %)**INTMOD**
474 474  
... ... @@ -475,47 +475,115 @@
475 475  Downlink Payload: 06000003, Set AT+INTMOD=3
476 476  
477 477  
535 +
478 478  == 2.6  ​LED Indicator ==
479 479  
480 480  
481 -The NMDS200 has an internal LED which is to show the status of different states.
539 +The CPN01 has an internal LED which is to show the status of different states.
482 482  
483 483  * When the device starts normally, the LED will light up for 1 second.
484 -* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
542 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
485 485  * For each uplink probe, LED will be on for 500ms.
486 486  
545 +== 2.7  Alarm Base on Timeout ==
487 487  
488 488  
489 -== 2.7  Distance alarm function ==
548 +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 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
551 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
493 493  
494 -(% style="color:#037691" %)**Example 1:**
553 +Keep Status = 1: Monitor Close to Open event
495 495  
496 -AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
555 +Keep Status = 0: Monitor Open to Close event
497 497  
498 -AT+ ALARM2 =min,max
499 499  
558 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
500 500  
501 -(% style="color:#037691" %)**Example 2:**
560 +Range 0 ~~ 65535(0xFFFF) seconds.
502 502  
503 -AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
562 +If keep time = 0, Disable Alarm Base on Timeout feature.
504 504  
564 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
505 505  
506 -== 2.8  Set the number of data to be uploaded and the recording time ==
507 507  
567 +(% style="color:blue" %)**AT Command to configure:**
508 508  
569 +(% 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.
570 +
571 +(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
572 +
573 +
574 +
575 +== 2.8  Set debug mode ==
576 +
577 +
578 +Feature: Enable or Disable debug mode
579 +
580 +(% style="color:blue" %)**AT Command: AT+DEBUG**
581 +
582 +[[image:image-20221021111629-21.png]]
583 +
584 +
585 +
586 +== 2.9  Clear Flash Record ==
587 +
588 +
589 +Feature: Clear flash storage for data log feature.
590 +
591 +(% style="color:blue" %)**AT Command: AT+CLRDTA**
592 +
593 +[[image:image-20221021111527-19.png]]
594 +
595 +
596 +
597 +== 2.10  Set trigger mode ==
598 +
599 +
600 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
601 +
602 +Feature: Set the trigger interrupt mode.
603 +
604 +[[image:image-20221021111552-20.png]]
605 +
606 +
607 +
608 +== 2.11  Set the calculate flag ==
609 +
610 +
611 +Feature: Set the calculate flag
612 +
613 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
614 +
615 +[[image:image-20221021111711-22.png]]
616 +
617 +
618 +
619 +== 2.12 Set count number ==
620 +
621 +
622 +Feature: Manually set the count number
623 +
624 +(% style="color:blue" %)**AT Command: AT+SETCNT**
625 +
626 +[[image:image-20221021111748-24.png]]
627 +
628 +
629 +
630 +== 2.13  Set the number of data to be uploaded and the recording time ==
631 +
632 +
509 509  (% style="color:blue" %)**AT Command:**
510 510  
511 -(% 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)
635 +(% 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)
512 512  
513 -(% 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.
637 +(% 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.
514 514  
515 515  
516 -== 2.9  Read or Clear cached data ==
517 517  
641 +== 2.14  Read or Clear cached data ==
518 518  
643 +
519 519  (% style="color:blue" %)**AT Command:**
520 520  
521 521  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -522,25 +522,78 @@
522 522  
523 523  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
524 524  
525 -[[image:1670408172929-569.png]]
650 +[[image:image-20221021111810-25.png||height="364" width="797"]]
526 526  
527 527  
528 -== 2.10  ​Firmware Change Log ==
529 529  
654 +== 2.15  ​Firmware Change Log ==
530 530  
531 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]
532 532  
657 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
658 +
533 533  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
534 534  
535 535  
536 -== 2.11 Battery & Power Consumption ==
537 537  
663 +== 2.16  ​Battery Analysis ==
538 538  
539 -NMDS200 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
540 540  
541 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
666 +=== 2.16.1  ​Battery Type ===
542 542  
543 543  
669 +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.
670 +
671 +The battery is designed to last for several years depends on the actual use environment and update interval. 
672 +
673 +The battery-related documents as below:
674 +
675 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
676 +
677 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
678 +
679 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
680 +
681 +[[image:image-20221021111911-26.png]] ​
682 +
683 +
684 +
685 +=== 2.16.2  Power consumption Analyze ===
686 +
687 +
688 +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.
689 +
690 +Instruction to use as below:
691 +
692 +(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
693 +
694 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
695 +
696 +* Product Model
697 +
698 +* Uplink Interval
699 +
700 +* Working Mode
701 +
702 +And the Life expectation in difference case will be shown on the right.
703 +
704 +[[image:1666596205057-567.png]] ​
705 +
706 +
707 +
708 +=== 2.16.3  ​Battery Note ===
709 +
710 +
711 +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.
712 +
713 +
714 +
715 +=== 2.16.4  Replace the battery ===
716 +
717 +
718 +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).
719 +
720 +
721 +
544 544  = 3. ​ Access NB-IoT Module =
545 545  
546 546  
... ... @@ -548,12 +548,13 @@
548 548  
549 549  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/]] 
550 550  
729 +[[image:image-20221021112006-28.png]] ​
551 551  
552 -[[image:image-20221118094449-6.png]] ​
553 553  
554 554  
555 555  = 4.  Using the AT Commands =
556 556  
735 +
557 557  == 4.1  Access AT Commands ==
558 558  
559 559  
... ... @@ -584,63 +584,65 @@
584 584  
585 585  AT+INTMOD            : Set the trigger interrupt mode
586 586  
587 -AT+5VT  : Set extend the time of 5V power  
766 +AT+5VT  : Set extend the time of 5V power  
588 588  
589 -AT+PRO  : Choose agreement
768 +AT+PRO  : Choose agreement
590 590  
591 -AT+RXDL  : Extend the sending and receiving time
770 +AT+RXDL  : Extend the sending and receiving time
592 592  
593 -AT+SERVADDR  : Server Address
772 +AT+SERVADDR  : Server Address
594 594  
595 -AT+TR      :  Get or Set record time
774 +AT+TR      :  Get or Set record time
596 596  
597 -AT+NOUD :  Get or Set the number of data to be uploaded
776 +AT+NOUD      : Get or Set the number of data to be uploaded
598 598  
599 599  AT+CDP     :  Read or Clear cached data
600 600  
601 -AT+DEBUG:  Enable or Disable debug mode
780 +AT+ DEBUG   : Enable or Disable debug mode
602 602  
603 -AT+ALARM1:  Get or Set alarm of distance1
782 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
604 604  
605 -AT+ALARM2:  Get or Set alarm of distance2
784 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
606 606  
607 -AT+GETSENSORVALUE :  Returns the current sensor measurement
786 +AT+ CALCFLAG   : Get or Set the calculate flag
608 608  
609 -AT+POWERIC :  Get or set the Power IC flag
788 +AT+ CLRC   : Clear current door open count
610 610  
611 611  
612 612  (% style="color:blue" %)**COAP Management**      
613 613  
614 -AT+URI :  Resource parameters
793 +AT+URI            : Resource parameters
615 615  
616 616  
617 617  (% style="color:blue" %)**UDP Management**
618 618  
619 -AT+CFM :  Upload confirmation mode (only valid for UDP)
798 +AT+CFM          : Upload confirmation mode (only valid for UDP)
620 620  
621 621  
622 622  (% style="color:blue" %)**MQTT Management**
623 623  
624 -AT+CLIENT  : Get or Set MQTT client
803 +AT+CLIENT               : Get or Set MQTT client
625 625  
626 -AT+UNAME : Get or Set MQTT Username
805 +AT+UNAME  : Get or Set MQTT Username
627 627  
628 -AT+PWD  :  Get or Set MQTT password
807 +AT+PWD                  : Get or Set MQTT password
629 629  
630 -AT+PUBTOPIC :  Get or Set MQTT publish topic
809 +AT+PUBTOPIC  : Get or Set MQTT publish topic
631 631  
632 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
811 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
633 633  
634 634  
635 635  (% style="color:blue" %)**Information**          
636 636  
637 -AT+FDR :  Factory Data Reset
816 +AT+FDR  : Factory Data Reset
638 638  
639 -AT+PWORD :  Serial Access Password
818 +AT+PWORD  : Serial Access Password
640 640  
641 641  
821 +
642 642  = ​5.  FAQ =
643 643  
824 +
644 644  == 5.1 ​ How to Upgrade Firmware ==
645 645  
646 646  
... ... @@ -648,11 +648,13 @@
648 648  
649 649  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]]
650 650  
651 -(% 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.**
832 +(% 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.**
652 652  
653 653  
835 +
654 654  = 6.  Trouble Shooting =
655 655  
838 +
656 656  == 6.1  ​Connection problem when uploading firmware ==
657 657  
658 658  
... ... @@ -659,6 +659,7 @@
659 659  (% 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]]
660 660  
661 661  
845 +
662 662  == 6.2  AT Command input doesn't work ==
663 663  
664 664  
... ... @@ -665,21 +665,28 @@
665 665  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.
666 666  
667 667  
852 +
668 668  = 7. ​ Order Info =
669 669  
670 670  
671 -Part Number:(% style="color:blue" %)** NMDS200**
856 +Part Number**:** CPN01
672 672  
673 673  
859 +
674 674  = 8.  Packing Info =
675 675  
676 676  
677 677  (% style="color:blue" %)**Package Includes**:
678 678  
679 -* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
865 +* CPN01 Open/Close Sensor x 1
866 +* External antenna x 1
680 680  
868 +(% style="color:blue" %)**Dimension and weight**:
681 681  
870 +* Size: 195 x 125 x 55 mm
871 +* Weight:   420g
682 682  
873 +
683 683  = 9.  Support =
684 684  
685 685  
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-20221117114459-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20221117114842-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -964.1 KB
Content
image-20221117114937-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.1 KB
Content
image-20221117114949-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -33.4 KB
Content
image-20221117115010-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -40.4 KB
Content
image-20221117142300-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -51.9 KB
Content
image-20221117150312-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.7 KB
Content
image-20221118092935-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.5 KB
Content
image-20221118093658-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -12.7 KB
Content
image-20221118094227-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.2 KB
Content
image-20221118094449-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.5 KB
Content
image-20221118103445-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.5 KB
Content
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