Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 67.6 >
edited by Xiaoling
on 2022/11/18 10:23
To version < 90.2 >
edited by Xiaoling
on 2022/12/12 17:19
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
1 +NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
Content
... ... @@ -1,12 +1,16 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20221117105556-1.png]]
2 +[[image:LMDS200_10.jpg||height="572" width="572"]]
3 3  
4 4  
5 5  
6 6  
7 7  
8 +(% style="display:none" %) (%%)
8 8  
9 9  
11 +
12 +
13 +
10 10  **Table of Contents：**
11 11  
12 12  {{toc/}}
... ... @@ -15,53 +15,55 @@
15 15  
16 16  
17 17  
22 +
23 +
24 +
25 +
18 18  = 1.  Introduction =
19 19  
20 -== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
28 +== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
21 21  
22 22  
23 23  (((
24 -The Dragino NDS03A is an (% style="color:blue" %)**Open/Close NB-IoT Door Sensor**(%%). It detects door (% style="color:blue" %)**open/close status**(%%) and (% style="color:blue" %)**uplinks**(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server.
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.
25 25  )))
26 26  
27 27  (((
28 -The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically.
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.
29 29  )))
30 30  
31 31  (((
32 -NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT.
40 +NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
33 33  )))
34 34  
35 35  (((
36 -NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time.
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.
37 37  )))
38 38  
39 39  (((
40 -NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
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.
41 41  )))
42 42  
43 43  (((
44 -NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technologyTCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
52 +NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
45 45  )))
46 46  
47 47  (((
48 -NDS03A is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
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)
49 49  )))
50 50  
51 51  (((
52 -To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection.
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.
53 53  )))
54 54  
55 55  
56 -
57 57  == ​1.2  Features ==
58 58  
59 59  
60 60  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
61 -* Open/Close detect
62 -* Open/Close statistics
68 +* Short uplink interval for Distance Alarm
63 63  * Monitor Battery Level
64 -* connect two door sensors
70 +* Microwave Radar for distance detection
65 65  * Datalog feature
66 66  * Uplink periodically
67 67  * Downlink to change configure
... ... @@ -72,29 +72,40 @@
72 72  * Micro SIM card slot for NB-IoT SIM
73 73  * 8500mAh Battery for long-term use
74 74  
75 -== 1.3  Storage & Operation ==
76 76  
77 77  
78 -Temperature -40°C to +85°C
83 +== 1.3 Radar probe specification ==
79 79  
80 80  
81 -== 1.4  Mechanical ==
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°
82 82  
83 83  
84 -[[image:image-20221117114937-4.png]]
85 85  
97 +== 1.4  Storage Temperature ==
86 86  
87 -[[image:image-20221117114949-5.png]]
88 88  
100 + -40°C to +85°C
89 89  
90 -[[image:image-20221117115010-6.png]]
91 91  
92 -
93 -
94 94  == 1.5 ​ Applications ==
95 95  
96 96  
97 -[[image:image-20221117114842-3.png]]
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 98  
99 99  
100 100  
... ... @@ -104,107 +104,66 @@
104 104  (% style="color:blue" %)**Common DC Characteristics:**
105 105  
106 106  * Supply Voltage: 2.1v ~~ 3.6v
107 -* Operating Temperature: -40 ~~ 85°C
124 +* Operating Temperature: 0 ~~ 70°C
108 108  
109 109  (% style="color:blue" %)**NB-IoT Spec:**
110 110  
111 -* - B1 @H-FDD: 2100MHz
112 -* - B3 @H-FDD: 1800MHz
113 -* - B8 @H-FDD: 900MHz
114 -* - B5 @H-FDD: 850MHz
115 -* - B20 @H-FDD: 800MHz
116 -* - B28 @H-FDD: 700MHz
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
117 117  
118 -== 1.7  Pin Definitions and Switch ==
119 119  
120 120  
121 -[[image:image-20221021110429-4.png]]
137 +== 1.7  Installation ==
122 122  
123 123  
124 -=== 1.7.1  Pin Definition ===
140 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
125 125  
126 126  
127 -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]]
143 +[[image:image-20221207170748-1.png]]
128 128  
129 129  
146 + [[image:image-20221207170748-2.png||height="345" width="634"]]
130 130  
131 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
132 132  
149 +== 1.8  Pin Definitions and Switch ==
133 133  
134 -Power on Device when putting this jumper.
135 135  
152 +[[image:1670404362039-351.png]]
136 136  
137 137  
138 -=== 1.7.3  BOOT MODE / SW1 ===
155 += 2.  Use NMDS200 to communicate with IoT Server =
139 139  
140 -
141 -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.
142 -
143 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
144 -
145 -
146 -
147 -=== 1.7.4  Reset Button ===
148 -
149 -
150 -Press to reboot the device.
151 -
152 -
153 -
154 -=== 1.7.5  LED ===
155 -
156 -
157 -The LED will blink when :
158 -
159 -1.  Boot the device in flash mode
160 -
161 -2.  Send an uplink packet
162 -
163 -
164 -
165 -== 1.8  Magnet Distance ==
166 -
167 -
168 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
169 -
170 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
171 -
172 -
173 -
174 -= 2.  Use NDS03A to communicate with IoT Server =
175 -
176 176  == 2.1  How it works ==
177 177  
178 178  
179 -In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.
160 +The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
180 180  
181 -The diagram below shows the working flow in the default firmware of NDS03A:
162 +The diagram below shows the working flow in the default firmware of NMDS200:
182 182  
183 -[[image:image-20221021110615-5.png]]
164 +[[image:image-20221021110615-5.png||height="996" width="492"]]
184 184  
185 185  
167 +== 2.2 ​ Configure NMDS200 ==
186 186  
187 -== 2.2 ​ Configure NDS03A ==
188 188  
189 -=== 2.2.1 Test Requirement ===
170 +To use NMDS200 in your city, make sure to meet below requirements:
190 190  
191 -
192 -To use NDS03A in your city, make sure to meet below requirements:
193 -
194 194  * Your local operator has already distributed an NB-IoT Network.
195 -* The local NB-IoT network used the band that NDS03A supports.
173 +* The local NB-IoT network used the band that NMDS200 supports.
196 196  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
197 197  
198 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDS03A will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
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.
199 199  
200 -[[image:image-20221117142300-1.png]]
178 +[[image:image-20221209090938-1.png]]
201 201  
202 - ​
203 203  
181 +=== 2.2.1 Insert NB-IoT SIM card ===
204 204  
205 -=== 2.2.2 Insert NB-IoT SIM card ===
206 206  
207 -
208 208  Insert the NB-IoT Card get from your provider.
209 209  
210 210  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -212,12 +212,11 @@
212 212  [[image:image-20221021110745-6.png]] ​
213 213  
214 214  
191 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
215 215  
216 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
217 217  
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.
218 218  
219 -User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
220 -
221 221  (% style="color:blue" %)**Connection:**
222 222  
223 223  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -239,24 +239,23 @@
239 239  
240 240  * Flow Control: (% style="color:red" %)**None**
241 241  
242 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
217 +Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
243 243  
244 244  ​[[image:image-20221021110817-7.png]]
245 245  
246 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
221 +NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
247 247  
248 248  
249 249  (% 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]]
250 250  
251 251  
227 +=== 2.2.3 Use CoAP protocol to uplink data ===
252 252  
253 -=== 2.2.4 Use CoAP protocol to uplink data ===
254 254  
255 -
256 256  (% 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/]]
257 257  
258 258  
259 -(% style="color:blue" %)**Use below commands in NDS03A:**
233 +(% style="color:blue" %)**Use below commands in NMDS200:**
260 260  
261 261  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
262 262  
... ... @@ -266,18 +266,17 @@
266 266  
267 267  For parameter description, please refer to AT command set
268 268  
269 -[[image:image-20221021110948-8.png]]
243 +[[image:1670471530120-960.png||height="647" width="674"]]
270 270  
271 271  
272 -After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
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.
273 273  
274 -[[image:image-20221021110956-9.png]] ​
248 +[[image:1670405841875-916.png]] ​
275 275  
276 276  
251 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
277 277  
278 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
279 279  
280 -
281 281  (% style="color:blue" %)**AT Commands:**
282 282  
283 283  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -286,7 +286,7 @@
286 286  
287 287  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
288 288  
289 -​ [[image:image-20221021111025-10.png]]
262 +​ [[image:1670471559211-638.png]]
290 290  
291 291  
292 292  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -293,10 +293,9 @@
293 293  
294 294  ​
295 295  
269 +=== 2.2.5 Use MQTT protocol to uplink data ===
296 296  
297 -=== 2.2.6 Use MQTT protocol to uplink data ===
298 298  
299 -
300 300  (% style="color:blue" %)**AT Commands:**
301 301  
302 302  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -313,10 +313,10 @@
313 313  
314 314  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
315 315  
316 -​ [[image:image-20221021111058-12.png]]
288 +​ [[image:1670471584490-640.png]]
317 317  
318 318  
319 -[[image:image-20221021111201-16.png||height="472" width="653"]]
291 +[[image:1670405928926-116.png]]
320 320  
321 321  ​
322 322  
... ... @@ -323,10 +323,9 @@
323 323  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.
324 324  
325 325  
298 +=== 2.2.6 Use TCP protocol to uplink data ===
326 326  
327 -=== 2.2.7 Use TCP protocol to uplink data ===
328 328  
329 -
330 330  (% style="color:blue" %)**AT Commands:**
331 331  
332 332  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -333,19 +333,19 @@
333 333  
334 334  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
335 335  
336 -​ [[image:image-20221021111125-14.png]]
307 +​ [[image:1670471613823-833.png]]
337 337  
309 +
338 338  [[image:image-20221021111131-15.png]]
339 339  
340 340  ​
341 341  
314 +=== 2.2.7 Change Update Interval ===
342 342  
343 -=== 2.2.8 Change Update Interval ===
344 344  
345 -
346 346  User can use below command to change the (% style="color:blue" %)**uplink interval**.
347 347  
348 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
319 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
349 349  
350 350  (% style="color:red" %)**NOTE:**
351 351  
... ... @@ -352,77 +352,57 @@
352 352  1.  By default, the device will send an uplink message every 4 hour.
353 353  
354 354  
355 -
356 356  == 2.3  Uplink Payload ==
357 357  
358 358  
359 -The uplink payload includes 26 bytes in total by default.
329 +The uplink payload includes 23 bytes in total by default.
360 360  
361 361  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.
362 362  
363 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
364 364  
365 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
366 -|=(% scope="row" style="width: 93px;" %)**Size(bytes)**|(% style="width:67px" %)**8**|(% style="width:40px" %)**2**|(% style="width:45px" %)**2**|(% style="width:75px" %)**1**|(% style="width:54px" %)**1**|(% style="width:62px" %)**1**|(% style="width:60px" %)**1**|(% style="width:94px" %)**3**|(% style="width:93px" %)**3**
367 -|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
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"]]
368 368  
369 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
370 -|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)(((
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" %)(((
371 371  **1-32 group**
372 372  )))
373 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
342 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...
374 374  
375 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
344 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
376 376  
346 +[[image:1670406261143-723.png]]
377 377  
378 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
379 -|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:66px" %)**8**|(% style="width:40px" %)**2**|(% style="width:46px" %)**2**|(% style="width:70px" %)**1**|(% style="width:54px" %)**1**|(% style="width:55px" %)**1**|(% style="width:57px" %)**1**|(% style="width:86px" %)**3**|(% style="width:82px" %)**3**
380 -|=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
381 381  
382 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
383 -|(% style="width:59px" %)**1**|(% style="width:67px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:66px" %)**1**|(% style="width:92px" %)**3**
384 -|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
349 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
385 385  
386 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
387 -|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
388 -**1-32 group**
389 -)))
390 -|(% style="width:102px" %)last open time (pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:88px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
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__(%%)**
391 391  
392 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
393 -
394 -[[image:image-20221117145932-2.png]]
395 -
396 -
397 -The payload is ASCII string, representative same HEX:
398 -
399 -**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)**
400 -
401 401  **where:**
402 402  
403 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
355 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
404 404  
405 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
357 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
406 406  
407 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
359 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
408 408  
409 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
361 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
410 410  
411 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
363 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
412 412  
413 -* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0
365 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
414 414  
415 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
367 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
416 416  
417 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
369 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
418 418  
419 -* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
371 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
420 420  
421 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
422 422  
374 +
423 423  == 2.4  Payload Explanation and Sensor Interface ==
424 424  
425 -
426 426  === 2.4.1  Device ID ===
427 427  
428 428  
... ... @@ -442,13 +442,13 @@
442 442  
443 443  Specify the software version: 0x64=100, which means firmware version 1.00.
444 444  
445 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
396 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
446 446  
447 447  
448 448  === 2.4.3  Battery Info ===
449 449  
450 450  
451 -Check the battery voltage for NDS03A.
402 +Check the battery voltage for NMDS200.
452 452  
453 453  Ex1: 0x0B45 = 2885mV
454 454  
... ... @@ -460,52 +460,49 @@
460 460  
461 461  NB-IoT Network signal Strength.
462 462  
463 -**Ex1: 0x1d = 29**
414 +(% style="color:blue" %)**Ex1: 0x1d = 29**
464 464  
465 -**0**  -113dBm or less
416 +(% style="color:#037691" %)**0** (%%) -113dBm or less
466 466  
467 -**1**  -111dBm
418 +(% style="color:#037691" %)**1**  (%%) -111dBm
468 468  
469 -**2...30** -109dBm... -53dBm
420 +(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
470 470  
471 -**31**   -51dBm or greater
422 +(% style="color:#037691" %)**31** (%%) -51dBm or greater
472 472  
473 -**99**    Not known or not detectable
424 +(% style="color:#037691" %)**99** (%%) Not known or not detectable
474 474  
475 475  
476 -=== 2.4.5  Disalarm: (default: 0) ===
427 +=== 2.4.5  Distance ===
477 477  
478 478  
479 -(% style="color:blue" %)**If Disalarm = 1**(%%), NDS03A will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many open/close event, and platform only care about the total number of pulse.
430 +[[image:1670407401682-959.png]]
480 480  
481 -(% style="color:blue" %)**If Disalarm = 0**(%%), NDS03A will send uplink at every TDC periodically and send data on each open/close event. This is useful for the application user need to monitor the open/close event in real-time.
482 482  
483 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
433 +(% style="color:blue" %)**Object1 Distance:**
484 484  
435 +Distance between sensor probe to the first object. (unit: cm)
485 485  
486 -=== 2.4.6  Keep Status & Keep Time ===
437 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
487 487  
439 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
488 488  
489 -Shows the configure value of Alarm Base on Timeout Feature
490 490  
442 +(% style="color:blue" %)**Object2 Distance:**
491 491  
492 -=== 2.4.7  Timestamp ===
444 +Distance between sensor probe to the second object. (unit: cm)
493 493  
494 494  
495 -Timestamp : 0x6315537b =1662342011
447 +=== 2.4.6  Timestamp ===
496 496  
497 497  
450 +Timestamp : 0x6315537b =1662342011
498 498  
499 -=== 2.4.8  Switch Dual Channel Mode ===
500 500  
501 -
502 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
503 -
504 -
505 505  == 2.5  Downlink Payload ==
506 506  
507 507  
508 -By default, NDS03A prints the downlink payload to console port.
456 +By default, NMDS200 prints the downlink payload to console port.
509 509  
510 510  [[image:image-20221021111414-18.png]] ​
511 511  
... ... @@ -522,7 +522,7 @@
522 522  
523 523  * (% style="color:#037691" %)**Reset**
524 524  
525 -If payload = 0x04FF, it will reset the NDS03A
473 +If payload = 0x04FF, it will reset the NMDS200
526 526  
527 527  * (% style="color:#037691" %)**INTMOD**
528 528  
... ... @@ -529,122 +529,37 @@
529 529  Downlink Payload: 06000003, Set AT+INTMOD=3
530 530  
531 531  
532 -
533 533  == 2.6  ​LED Indicator ==
534 534  
535 535  
536 -The NDS03A has an internal LED which is to show the status of different states.
483 +The NMDS200 has an internal LED which is to show the status of different states.
537 537  
538 538  * When the device starts normally, the LED will light up for 1 second.
539 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
486 +* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
540 540  * For each uplink probe, LED will be on for 500ms.
541 541  
542 -== 2.7  Alarm Base on Timeout ==
543 543  
544 544  
545 -NDS03A can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are:
491 +== 2.7  Distance alarm function ==
546 546  
547 547  
548 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
494 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
549 549  
550 -Keep Status = 1: Monitor Close to Open event
496 +(% style="color:#037691" %)**Example 1:**
551 551  
552 -Keep Status = 0: Monitor Open to Close event
498 +AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
553 553  
500 +AT+ ALARM2 =min,max
554 554  
555 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
556 556  
557 -Range 0 ~~ 65535(0xFFFF) seconds.
503 +(% style="color:#037691" %)**Example 2:**
558 558  
559 -If keep time = 0, Disable Alarm Base on Timeout feature.
505 +AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
560 560  
561 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
562 562  
508 +== 2.8  Set the number of data to be uploaded and the recording time ==
563 563  
564 -(% style="color:blue" %)**AT Command to configure:**
565 565  
566 -(% style="color:blue" %)**PB14 PIN:**
567 -
568 -(% style="color:#037691" %)**AT+TTRIG=1,30** (%%) **~-~->**  When the **Keep Status** change from connected to disconnect, and device remains in disconnect status for more than 30 seconds. NDS03A will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
569 -
570 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
571 -
572 -
573 -(% style="color:blue" %)**PB15 PIN:**
574 -
575 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
576 -
577 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
578 -
579 -
580 -== 2.8  Set debug mode ==
581 -
582 -
583 -Feature: Enable or Disable debug mode
584 -
585 -(% style="color:blue" %)**AT Command: AT+DEBUG**
586 -
587 -[[image:image-20221021111629-21.png]]
588 -
589 -
590 -
591 -== 2.9  Clear Flash Record ==
592 -
593 -
594 -Feature: Clear flash storage for data log feature.
595 -
596 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
597 -
598 -[[image:image-20221021111527-19.png]]
599 -
600 -
601 -
602 -== 2.10  Count Mod ==
603 -
604 -
605 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
606 -
607 -[[image:image-20221118092935-1.png]]
608 -
609 -
610 -
611 -== 2.11  Interrupt Pin Channel Mod ==
612 -
613 -
614 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
615 -
616 -[[image:image-20221118093144-2.png]]
617 -
618 -
619 -
620 -== 2.12 TTRIG1/2 timeout status alarm ==
621 -
622 -
623 -It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval.
624 -
625 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
626 -
627 -[[image:image-20221118093512-3.png]]
628 -
629 -
630 -
631 -== 2.13  Select counting mode ==
632 -
633 -
634 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
635 -
636 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
637 -
638 -When (% style="color:red" %)**b=0**(%%), it is the last door open duration, and when (% style="color:red" %)**b=1**(%%),the last door close duration.
639 -
640 -[[image:image-20221118093658-4.png]]
641 -
642 -
643 -
644 -
645 -== 2.14  Set the number of data to be uploaded and the recording time ==
646 -
647 -
648 648  (% style="color:blue" %)**AT Command:**
649 649  
650 650  (% 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)
... ... @@ -652,7 +652,7 @@
652 652  (% 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.
653 653  
654 654  
655 -== 2.15  Read or Clear cached data ==
518 +== 2.9  Read or Clear cached data ==
656 656  
657 657  
658 658  (% style="color:blue" %)**AT Command:**
... ... @@ -661,27 +661,24 @@
661 661  
662 662  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
663 663  
664 -[[image:image-20221118094227-5.png]]
527 +[[image:1670408172929-569.png]]
665 665  
666 666  
530 +== 2.10  ​Firmware Change Log ==
667 667  
668 -== 2.16  ​Firmware Change Log ==
669 669  
533 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
670 670  
671 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
672 -
673 673  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
674 674  
675 675  
538 +== 2.11  ​Battery Analysis ==
676 676  
677 -== 2.17  ​Battery Analysis ==
540 +=== 2.11.1  ​Battery Type ===
678 678  
679 679  
680 -=== 2.17.1  ​Battery Type ===
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.
681 681  
682 -
683 -The NDS03A battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
684 -
685 685  The battery is designed to last for several years depends on the actual use environment and update interval. 
686 686  
687 687  The battery-related documents as below:
... ... @@ -695,10 +695,9 @@
695 695  [[image:image-20221021111911-26.png]] ​
696 696  
697 697  
558 +=== 2.11.2  Power consumption Analyze ===
698 698  
699 -=== 2.17.2  Power consumption Analyze ===
700 700  
701 -
702 702  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.
703 703  
704 704  Instruction to use as below:
... ... @@ -718,21 +718,18 @@
718 718  [[image:1666596205057-567.png]] ​
719 719  
720 720  
580 +=== 2.11.3  ​Battery Note ===
721 721  
722 -=== 2.17.3  ​Battery Note ===
723 723  
724 -
725 725  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.
726 726  
727 727  
586 +=== 2.11.4  Replace the battery ===
728 728  
729 -=== 2.17.4  Replace the battery ===
730 730  
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).
731 731  
732 -The default battery pack of NDS03A includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
733 733  
734 -
735 -
736 736  = 3. ​ Access NB-IoT Module =
737 737  
738 738  
... ... @@ -740,13 +740,12 @@
740 740  
741 741  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/]] 
742 742  
599 +
743 743  [[image:image-20221118094449-6.png]] ​
744 744  
745 745  
746 -
747 747  = 4.  Using the AT Commands =
748 748  
749 -
750 750  == 4.1  Access AT Commands ==
751 751  
752 752  
... ... @@ -777,71 +777,63 @@
777 777  
778 778  AT+INTMOD            : Set the trigger interrupt mode
779 779  
780 -AT+5VT  : Set extend the time of 5V power  
635 +AT+5VT  : Set extend the time of 5V power  
781 781  
782 -AT+PRO  : Choose agreement
637 +AT+PRO  : Choose agreement
783 783  
784 -AT+RXDL  : Extend the sending and receiving time
639 +AT+RXDL  : Extend the sending and receiving time
785 785  
786 -AT+SERVADDR  : Server Address
641 +AT+SERVADDR  : Server Address
787 787  
788 -AT+TR      :  Get or Set record time
643 +AT+TR      :  Get or Set record time
789 789  
790 -AT+NOUD      : Get or Set the number of data to be uploaded
645 +AT+NOUD :  Get or Set the number of data to be uploaded
791 791  
792 792  AT+CDP     :  Read or Clear cached data
793 793  
794 -AT+ DEBUG   : Enable or Disable debug mode
649 +AT+DEBUG:  Enable or Disable debug mode
795 795  
796 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
651 +AT+ALARM1:  Get or Set alarm of distance1
797 797  
798 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
653 +AT+ALARM2:  Get or Set alarm of distance2
799 799  
800 -AT+COUNTMOD  :  Get or Set the count mode
655 +AT+GETSENSORVALUE :  Returns the current sensor measurement
801 801  
802 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
657 +AT+POWERIC :  Get or set the Power IC flag
803 803  
804 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
805 805  
806 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
807 -
808 -AT+ CLRC   :  Clear current door open count
809 -
810 -
811 811  (% style="color:blue" %)**COAP Management**      
812 812  
813 -AT+URI            : Resource parameters
662 +AT+URI :  Resource parameters
814 814  
815 815  
816 816  (% style="color:blue" %)**UDP Management**
817 817  
818 -AT+CFM          : Upload confirmation mode (only valid for UDP)
667 +AT+CFM :  Upload confirmation mode (only valid for UDP)
819 819  
820 820  
821 821  (% style="color:blue" %)**MQTT Management**
822 822  
823 -AT+CLIENT               : Get or Set MQTT client
672 +AT+CLIENT  : Get or Set MQTT client
824 824  
825 -AT+UNAME  : Get or Set MQTT Username
674 +AT+UNAME : Get or Set MQTT Username
826 826  
827 -AT+PWD                  : Get or Set MQTT password
676 +AT+PWD  :  Get or Set MQTT password
828 828  
829 -AT+PUBTOPIC  : Get or Set MQTT publish topic
678 +AT+PUBTOPIC :  Get or Set MQTT publish topic
830 830  
831 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
680 +AT+SUBTOPIC :  Get or Set MQTT subscription topic
832 832  
833 833  
834 834  (% style="color:blue" %)**Information**          
835 835  
836 -AT+FDR  : Factory Data Reset
685 +AT+FDR :  Factory Data Reset
837 837  
838 -AT+PWORD  : Serial Access Password
687 +AT+PWORD :  Serial Access Password
839 839  
840 840  
841 -
842 842  = ​5.  FAQ =
843 843  
844 -
845 845  == 5.1 ​ How to Upgrade Firmware ==
846 846  
847 847  
... ... @@ -849,13 +849,11 @@
849 849  
850 850  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]]
851 851  
852 -(% style="color:red" %)**Notice: **(% style="color:blue" %)**NDS03A** (%%)**and (% style="color:blue" %)LDS03A(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
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.**
853 853  
854 854  
855 -
856 856  = 6.  Trouble Shooting =
857 857  
858 -
859 859  == 6.1  ​Connection problem when uploading firmware ==
860 860  
861 861  
... ... @@ -862,7 +862,6 @@
862 862  (% 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]]
863 863  
864 864  
865 -
866 866  == 6.2  AT Command input doesn't work ==
867 867  
868 868  
... ... @@ -869,21 +869,21 @@
869 869  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.
870 870  
871 871  
872 -
873 873  = 7. ​ Order Info =
874 874  
875 875  
876 -Part Number**:** NDS03A
719 +Part Number:(% style="color:blue" %)** NMDS200**
877 877  
878 878  
879 -
880 880  = 8.  Packing Info =
881 881  
882 882  
883 883  (% style="color:blue" %)**Package Includes**:
884 884  
885 -* NDS03A Open/Close Door Sensor x 1
727 +* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
886 886  
729 +
730 +
887 887  = 9.  Support =
888 888  
889 889  
1670404362039-351.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +492.6 KB
Content
1670405841875-916.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +181.0 KB
Content
1670406261143-723.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.9 KB
Content
1670407401682-959.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +23.7 KB
Content
1670408172929-569.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +211.8 KB
Content
1670471530120-960.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +67.6 KB
Content
1670471559211-638.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +170.6 KB
Content
1670471584490-640.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +91.1 KB
Content
1670471613823-833.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +181.0 KB
Content
LMDS200_10.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
image-20221118103445-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +43.5 KB
Content
image-20221207170748-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.1 KB
Content
image-20221207170748-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +29.9 KB
Content
image-20221207173200-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.7 KB
Content
image-20221207173300-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.0 KB
Content
image-20221208090742-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +79.7 KB
Content
image-20221209090938-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +121.9 KB
Content
image-20221212171610-1.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +756.0 KB
Content

Applications

Navigation

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