Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 70.1 >
edited by Xiaoling
on 2022/11/18 10:35
To version < 83.3 >
edited by Xiaoling
on 2022/12/08 09:33
>
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,67 +1,44 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20221117105556-1.png]]
2 +[[image:LMDS200_10.jpg]]
3 3  
4 4  
5 -
6 -
7 -
8 -
9 -
10 10  **Table of Contents：**
11 11  
12 -{{toc/}}
13 13  
14 14  
15 15  
16 16  
17 -
18 18  = 1.  Introduction =
19 19  
20 -== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
13 +== 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.
25 -)))
17 +The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor.
26 26  
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.
29 -)))
19 +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.
30 30  
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.
33 -)))
21 +NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
34 34  
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.
37 -)))
23 +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.
38 38  
39 -(((
40 -NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
41 -)))
25 +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.
42 42  
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.
45 -)))
27 +NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
46 46  
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)
49 -)))
29 +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)
50 50  
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.
31 +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
39 +* Short uplink interval for Distance Alarm
63 63  * Monitor Battery Level
64 -* connect two door sensors
41 +* Microwave Radar for distance detection
65 65  * Datalog feature
66 66  * Uplink periodically
67 67  * Downlink to change configure
... ... @@ -72,32 +72,37 @@
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 ==
52 +== 1.3 Radar probe specification ==
76 76  
77 77  
78 -Temperature -40°C to +85°C
55 +* Measuring Method: FMCW
56 +* Frequency: 24.000 24.500 GHz
57 +* Measurement output power: 6dBm
58 +* Measure range: 0.5 20m
59 +* Accuracy: ±0.1m
60 +* Resolution: 0.01m
61 +* Horizontal Angel: 78°
62 +* Vertical Angel: 23°
79 79  
64 +== 1.4  Storage Temperature ==
80 80  
81 -== 1.4  Mechanical ==
82 82  
67 + -40°C to +85°C
83 83  
84 -[[image:image-20221117114937-4.png]]
85 85  
86 -
87 -[[image:image-20221117114949-5.png]]
88 -
89 -
90 -[[image:image-20221117115010-6.png]]
91 -
92 -
93 -
94 94  == 1.5 ​ Applications ==
95 95  
96 96  
97 -[[image:image-20221117114842-3.png]]
73 +* Horizontal distance measurement
74 +* Liquid level measurement
75 +* Parking management system
76 +* Object proximity and presence detection
77 +* Intelligent trash can management system
78 +* Robot obstacle avoidance
79 +* Automatic control
80 +* Sewer
81 +* Bottom water level monitoring
98 98  
99 -
100 -
101 101  == 1.6  Specification ==
102 102  
103 103  
... ... @@ -104,107 +104,62 @@
104 104  (% style="color:blue" %)**Common DC Characteristics:**
105 105  
106 106  * Supply Voltage: 2.1v ~~ 3.6v
107 -* Operating Temperature: -40 ~~ 85°C
89 +* 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
93 +* B1 @H-FDD: 2100MHz
94 +* B3 @H-FDD: 1800MHz
95 +* B8 @H-FDD: 900MHz
96 +* B5 @H-FDD: 850MHz
97 +* B20 @H-FDD: 800MHz
98 +* B28 @H-FDD: 700MHz
117 117  
118 -== 1.7  Pin Definitions and Switch ==
100 +== 1.7  Installation ==
119 119  
120 120  
121 -[[image:image-20221021110429-4.png]]
103 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
122 122  
123 123  
124 -=== 1.7.1  Pin Definition ===
106 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
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]]
128 128  
110 +== 1.8  Pin Definitions and Switch ==
129 129  
130 130  
131 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
113 +[[image:1670404362039-351.png]]
132 132  
133 133  
134 -Power on Device when putting this jumper.
116 += 2.  Use NMDS200 to communicate with IoT Server =
135 135  
136 -
137 -
138 -=== 1.7.3  BOOT MODE / SW1 ===
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.
121 +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:
123 +The diagram below shows the working flow in the default firmware of NMDS200:
182 182  
183 183  [[image:image-20221021110615-5.png]]
184 184  
185 185  
128 +== 2.2 ​ Configure NMDS200 ==
186 186  
187 -== 2.2 ​ Configure NDS03A ==
188 188  
189 -=== 2.2.1 Test Requirement ===
131 +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.
134 +* 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.
137 +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]]
139 +[[image:image-20221208090742-1.png]]
201 201  
202 - ​
203 203  
142 +=== 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  
152 +=== 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  
155 +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,11 +239,11 @@
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**(%%).
178 +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.
182 +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,13 +250,13 @@
250 250  
251 251  
252 252  
253 -=== 2.2.4 Use CoAP protocol to uplink data ===
189 +=== 2.2.3 Use CoAP protocol to uplink data ===
254 254  
255 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:**
195 +(% 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  
... ... @@ -269,15 +269,14 @@
269 269  [[image:image-20221021110948-8.png]]
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.
208 +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]] ​
210 +[[image:1670405841875-916.png]] ​
275 275  
276 276  
213 +=== 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
... ... @@ -293,10 +293,9 @@
293 293  
294 294  ​
295 295  
231 +=== 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]]
250 +​ [[image:image-20221118103445-7.png]]
317 317  
318 318  
319 -[[image:image-20221021111201-16.png||height="472" width="653"]]
253 +[[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  
260 +=== 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]]
269 +​ [[image:1670406036256-101.png||height="676" width="713"]]
337 337  
271 +
338 338  [[image:image-20221021111131-15.png]]
339 339  
340 340  ​
341 341  
276 +=== 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)
281 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
349 349  
350 350  (% style="color:red" %)**NOTE:**
351 351  
... ... @@ -352,74 +352,56 @@
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.
291 +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)
296 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
297 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:90px" %)**2**|(% style="width:100px" %)**2**
298 +|=(% 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.5A0A0Distance"]] |(% style="width:93px" %) [[Distance  2>>||anchor="H2.4.5A0A0Distance"]]
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" %)(((
300 +(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
301 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
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" %)...
304 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
374 374  
375 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
306 +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  
308 +[[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)
311 +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" %)......
313 +**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.
315 +**where:**
393 393  
394 -[[image:image-20221117145932-2.png]]
317 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
395 395  
319 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
396 396  
397 -The payload is ASCII string, representative same HEX:
321 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
398 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__(%%)**
323 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
400 400  
401 -**where:**
325 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
402 402  
403 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
327 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
404 404  
405 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
329 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
406 406  
407 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
331 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
408 408  
409 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
333 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
410 410  
411 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
412 412  
413 -* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0
414 414  
415 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
416 416  
417 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
418 -
419 -* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
420 -
421 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
422 -
423 423  == 2.4  Payload Explanation and Sensor Interface ==
424 424  
425 425  === 2.4.1  Device ID ===
... ... @@ -441,13 +441,13 @@
441 441  
442 442  Specify the software version: 0x64=100, which means firmware version 1.00.
443 443  
444 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
359 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
445 445  
446 446  
447 447  === 2.4.3  Battery Info ===
448 448  
449 449  
450 -Check the battery voltage for NDS03A.
365 +Check the battery voltage for NMDS200.
451 451  
452 452  Ex1: 0x0B45 = 2885mV
453 453  
... ... @@ -459,52 +459,49 @@
459 459  
460 460  NB-IoT Network signal Strength.
461 461  
462 -**Ex1: 0x1d = 29**
377 +**(% style="color:blue" %)Ex1: 0x1d = 29**
463 463  
464 -**0**  -113dBm or less
379 +**(% style="color:#037691" %)0** (%%) -113dBm or less
465 465  
466 -**1**  -111dBm
381 +**(% style="color:#037691" %)1**  (%%) -111dBm
467 467  
468 -**2...30** -109dBm... -53dBm
383 +**(% style="color:#037691" %)2...30** (%%) -109dBm... -53dBm
469 469  
470 -**31**   -51dBm or greater
385 +**(% style="color:#037691" %)31** (%%)  -51dBm or greater
471 471  
472 -**99**    Not known or not detectable
387 +**(% style="color:#037691" %)99** (%%)   Not known or not detectable
473 473  
474 474  
475 -=== 2.4.5  Disalarm: (default: 0) ===
390 +=== 2.4.5  Distance ===
476 476  
477 477  
478 -(% 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.
393 +[[image:1670407401682-959.png]]
479 479  
480 -(% 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.
481 481  
482 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
396 +(% style="color:blue" %)**Object1 Distance:**
483 483  
398 +Distance between sensor probe to the first object. (unit: cm)
484 484  
485 -=== 2.4.6  Keep Status & Keep Time ===
400 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
486 486  
402 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
487 487  
488 -Shows the configure value of Alarm Base on Timeout Feature
489 489  
405 +(% style="color:blue" %)**Object2 Distance:**
490 490  
491 -=== 2.4.7  Timestamp ===
407 +Distance between sensor probe to the second object. (unit: cm)
492 492  
493 493  
494 -Timestamp : 0x6315537b =1662342011
410 +=== 2.4.6  Timestamp ===
495 495  
496 496  
413 +Timestamp : 0x6315537b =1662342011
497 497  
498 -=== 2.4.8  Switch Dual Channel Mode ===
499 499  
500 -
501 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
502 -
503 -
504 504  == 2.5  Downlink Payload ==
505 505  
506 506  
507 -By default, NDS03A prints the downlink payload to console port.
419 +By default, NMDS200 prints the downlink payload to console port.
508 508  
509 509  [[image:image-20221021111414-18.png]] ​
510 510  
... ... @@ -521,7 +521,7 @@
521 521  
522 522  * (% style="color:#037691" %)**Reset**
523 523  
524 -If payload = 0x04FF, it will reset the NDS03A
436 +If payload = 0x04FF, it will reset the NMDS200
525 525  
526 526  * (% style="color:#037691" %)**INTMOD**
527 527  
... ... @@ -528,122 +528,40 @@
528 528  Downlink Payload: 06000003, Set AT+INTMOD=3
529 529  
530 530  
531 -
532 532  == 2.6  ​LED Indicator ==
533 533  
534 534  
535 -The NDS03A has an internal LED which is to show the status of different states.
446 +The NMDS200 has an internal LED which is to show the status of different states.
536 536  
537 537  * When the device starts normally, the LED will light up for 1 second.
538 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
449 +* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
539 539  * For each uplink probe, LED will be on for 500ms.
540 540  
541 -== 2.7  Alarm Base on Timeout ==
542 542  
543 543  
544 -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:
545 545  
455 +== 2.7  Distance alarm function ==
546 546  
547 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
548 548  
549 -Keep Status = 1: Monitor Close to Open event
458 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
550 550  
551 -Keep Status = 0: Monitor Open to Close event
460 +**(% style="color:blue" %)Example 1:**
552 552  
462 +AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
553 553  
554 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
464 +AT+ ALARM2 =min,max
555 555  
556 -Range 0 ~~ 65535(0xFFFF) seconds.
557 557  
558 -If keep time = 0, Disable Alarm Base on Timeout feature.
467 +**(% style="color:blue" %)Example 2:**
559 559  
560 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
469 +AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
561 561  
562 562  
563 -(% style="color:blue" %)**AT Command to configure:**
564 564  
565 -(% style="color:blue" %)**PB14 PIN:**
566 566  
567 -(% 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.
474 +== 2.8  Set the number of data to be uploaded and the recording time ==
568 568  
569 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
570 570  
571 -
572 -(% style="color:blue" %)**PB15 PIN:**
573 -
574 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
575 -
576 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
577 -
578 -
579 -== 2.8  Set debug mode ==
580 -
581 -
582 -Feature: Enable or Disable debug mode
583 -
584 -(% style="color:blue" %)**AT Command: AT+DEBUG**
585 -
586 -[[image:image-20221021111629-21.png]]
587 -
588 -
589 -
590 -== 2.9  Clear Flash Record ==
591 -
592 -
593 -Feature: Clear flash storage for data log feature.
594 -
595 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
596 -
597 -[[image:image-20221021111527-19.png]]
598 -
599 -
600 -
601 -== 2.10  Count Mod ==
602 -
603 -
604 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
605 -
606 -[[image:image-20221118092935-1.png]]
607 -
608 -
609 -
610 -== 2.11  Interrupt Pin Channel Mod ==
611 -
612 -
613 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
614 -
615 -[[image:image-20221118093144-2.png]]
616 -
617 -
618 -
619 -== 2.12 TTRIG1/2 timeout status alarm ==
620 -
621 -
622 -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.
623 -
624 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
625 -
626 -[[image:image-20221118093512-3.png]]
627 -
628 -
629 -
630 -== 2.13  Select counting mode ==
631 -
632 -
633 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
634 -
635 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
636 -
637 -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.
638 -
639 -[[image:image-20221118093658-4.png]]
640 -
641 -
642 -
643 -
644 -== 2.14  Set the number of data to be uploaded and the recording time ==
645 -
646 -
647 647  (% style="color:blue" %)**AT Command:**
648 648  
649 649  (% 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)
... ... @@ -651,7 +651,7 @@
651 651  (% 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.
652 652  
653 653  
654 -== 2.15  Read or Clear cached data ==
484 +== 2.9  Read or Clear cached data ==
655 655  
656 656  
657 657  (% style="color:blue" %)**AT Command:**
... ... @@ -660,27 +660,24 @@
660 660  
661 661  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
662 662  
663 -[[image:image-20221118094227-5.png]]
493 +[[image:1670408172929-569.png]]
664 664  
665 665  
496 +== 2.10  ​Firmware Change Log ==
666 666  
667 -== 2.16  ​Firmware Change Log ==
668 668  
499 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
669 669  
670 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
671 -
672 672  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
673 673  
674 674  
504 +== 2.11  ​Battery Analysis ==
675 675  
676 -== 2.17  ​Battery Analysis ==
506 +=== 2.11.1  ​Battery Type ===
677 677  
678 678  
679 -=== 2.17.1  ​Battery Type ===
509 +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.
680 680  
681 -
682 -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.
683 -
684 684  The battery is designed to last for several years depends on the actual use environment and update interval. 
685 685  
686 686  The battery-related documents as below:
... ... @@ -694,10 +694,9 @@
694 694  [[image:image-20221021111911-26.png]] ​
695 695  
696 696  
524 +=== 2.11.2  Power consumption Analyze ===
697 697  
698 -=== 2.17.2  Power consumption Analyze ===
699 699  
700 -
701 701  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.
702 702  
703 703  Instruction to use as below:
... ... @@ -717,21 +717,18 @@
717 717  [[image:1666596205057-567.png]] ​
718 718  
719 719  
546 +=== 2.11.3  ​Battery Note ===
720 720  
721 -=== 2.17.3  ​Battery Note ===
722 722  
723 -
724 724  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.
725 725  
726 726  
552 +=== 2.11.4  Replace the battery ===
727 727  
728 -=== 2.17.4  Replace the battery ===
729 729  
555 +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).
730 730  
731 -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).
732 732  
733 -
734 -
735 735  = 3. ​ Access NB-IoT Module =
736 736  
737 737  
... ... @@ -739,13 +739,12 @@
739 739  
740 740  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/]] 
741 741  
565 +
742 742  [[image:image-20221118094449-6.png]] ​
743 743  
744 744  
745 -
746 746  = 4.  Using the AT Commands =
747 747  
748 -
749 749  == 4.1  Access AT Commands ==
750 750  
751 751  
... ... @@ -784,63 +784,55 @@
784 784  
785 785  AT+SERVADDR  : Server Address
786 786  
787 -AT+TR      :  Get or Set record time
609 +AT+TR      :  Get or Set record time
788 788  
789 -AT+NOUD      : Get or Set the number of data to be uploaded
611 +AT+NOUD :  Get or Set the number of data to be uploaded
790 790  
791 791  AT+CDP     :  Read or Clear cached data
792 792  
793 -AT+ DEBUG   : Enable or Disable debug mode
615 +AT+DEBUG:  Enable or Disable debug mode
794 794  
795 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
617 +AT+ALARM1:  Get or Set alarm of distance1
796 796  
797 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
619 +AT+ALARM2:  Get or Set alarm of distance2
798 798  
799 -AT+COUNTMOD  :  Get or Set the count mode
621 +AT+GETSENSORVALUE :  Returns the current sensor measurement
800 800  
801 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
623 +AT+POWERIC :  Get or set the Power IC flag
802 802  
803 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
804 804  
805 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
806 -
807 -AT+ CLRC   :  Clear current door open count
808 -
809 -
810 810  (% style="color:blue" %)**COAP Management**      
811 811  
812 -AT+URI            : Resource parameters
628 +AT+URI :  Resource parameters
813 813  
814 814  
815 815  (% style="color:blue" %)**UDP Management**
816 816  
817 -AT+CFM          : Upload confirmation mode (only valid for UDP)
633 +AT+CFM :  Upload confirmation mode (only valid for UDP)
818 818  
819 819  
820 820  (% style="color:blue" %)**MQTT Management**
821 821  
822 -AT+CLIENT               : Get or Set MQTT client
638 +AT+CLIENT  : Get or Set MQTT client
823 823  
824 -AT+UNAME  : Get or Set MQTT Username
640 +AT+UNAME : Get or Set MQTT Username
825 825  
826 -AT+PWD                  : Get or Set MQTT password
642 +AT+PWD  :  Get or Set MQTT password
827 827  
828 -AT+PUBTOPIC  : Get or Set MQTT publish topic
644 +AT+PUBTOPIC :  Get or Set MQTT publish topic
829 829  
830 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
646 +AT+SUBTOPIC :  Get or Set MQTT subscription topic
831 831  
832 832  
833 833  (% style="color:blue" %)**Information**          
834 834  
835 -AT+FDR  : Factory Data Reset
651 +AT+FDR :  Factory Data Reset
836 836  
837 -AT+PWORD  : Serial Access Password
653 +AT+PWORD :  Serial Access Password
838 838  
839 839  
840 -
841 841  = ​5.  FAQ =
842 842  
843 -
844 844  == 5.1 ​ How to Upgrade Firmware ==
845 845  
846 846  
... ... @@ -848,13 +848,11 @@
848 848  
849 849  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]]
850 850  
851 -(% 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.**
665 +(% 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.**
852 852  
853 853  
854 -
855 855  = 6.  Trouble Shooting =
856 856  
857 -
858 858  == 6.1  ​Connection problem when uploading firmware ==
859 859  
860 860  
... ... @@ -861,7 +861,6 @@
861 861  (% 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]]
862 862  
863 863  
864 -
865 865  == 6.2  AT Command input doesn't work ==
866 866  
867 867  
... ... @@ -868,20 +868,18 @@
868 868  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.
869 869  
870 870  
871 -
872 872  = 7. ​ Order Info =
873 873  
874 874  
875 -Part Number**:** NDS03A
685 +Part Number:**(% style="color:blue" %) NMDS200**
876 876  
877 877  
878 -
879 879  = 8.  Packing Info =
880 880  
881 881  
882 882  (% style="color:blue" %)**Package Includes**:
883 883  
884 -* NDS03A Open/Close Door Sensor x 1
693 +* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
885 885  
886 886  = 9.  Support =
887 887  
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
LMDS200_10.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 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

Applications

Navigation

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