Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 70.3 >
edited by Xiaoling
on 2022/11/18 10:40
To version < 83.4 >
edited by Xiaoling
on 2022/12/08 09:47
>
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,34 +72,37 @@
72 72  * Micro SIM card slot for NB-IoT SIM
73 73  * 8500mAh Battery for long-term use
74 74  
52 +== 1.3 Radar probe specification ==
75 75  
76 76  
77 -== 1.3  Storage & Operation ==
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°
78 78  
64 +== 1.4  Storage Temperature ==
79 79  
80 -Temperature -40°C to +85°C
81 81  
67 + -40°C to +85°C
82 82  
83 -== 1.4  Mechanical ==
84 84  
85 -
86 -[[image:image-20221117114937-4.png]]
87 -
88 -
89 -[[image:image-20221117114949-5.png]]
90 -
91 -
92 -[[image:image-20221117115010-6.png]]
93 -
94 -
95 -
96 96  == 1.5 ​ Applications ==
97 97  
98 98  
99 -[[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
100 100  
101 -
102 -
103 103  == 1.6  Specification ==
104 104  
105 105  
... ... @@ -106,98 +106,60 @@
106 106  (% style="color:blue" %)**Common DC Characteristics:**
107 107  
108 108  * Supply Voltage: 2.1v ~~ 3.6v
109 -* Operating Temperature: -40 ~~ 85°C
89 +* Operating Temperature: 0 ~~ 70°C
110 110  
111 111  (% style="color:blue" %)**NB-IoT Spec:**
112 112  
113 -* - B1 @H-FDD: 2100MHz
114 -* - B3 @H-FDD: 1800MHz
115 -* - B8 @H-FDD: 900MHz
116 -* - B5 @H-FDD: 850MHz
117 -* - B20 @H-FDD: 800MHz
118 -* - 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
119 119  
100 +== 1.7  Installation ==
120 120  
121 121  
122 -== 1.7  Pin Definitions and Switch ==
103 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
123 123  
124 124  
125 -[[image:image-20221021110429-4.png]]
106 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
126 126  
127 127  
128 -=== 1.7.1  Pin Definition ===
129 129  
110 +== 1.8  Pin Definitions and Switch ==
130 130  
131 -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]]
132 132  
113 +[[image:1670404362039-351.png]]
133 133  
134 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
135 135  
116 += 2.  Use NMDS200 to communicate with IoT Server =
136 136  
137 -Power on Device when putting this jumper.
138 -
139 -
140 -=== 1.7.3  BOOT MODE / SW1 ===
141 -
142 -
143 -1)  ISP:  upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run.
144 -
145 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
146 -
147 -
148 -=== 1.7.4  Reset Button ===
149 -
150 -
151 -Press to reboot the device.
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 -== 1.8  Magnet Distance ==
165 -
166 -
167 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
168 -
169 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
170 -
171 -
172 -= 2.  Use NDS03A to communicate with IoT Server =
173 -
174 174  == 2.1  How it works ==
175 175  
176 176  
177 -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.
178 178  
179 -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:
180 180  
181 181  [[image:image-20221021110615-5.png]]
182 182  
183 183  
184 -== 2.2 ​ Configure NDS03A ==
128 +== 2.2 ​ Configure NMDS200 ==
185 185  
186 -=== 2.2.1 Test Requirement ===
187 187  
131 +To use NMDS200 in your city, make sure to meet below requirements:
188 188  
189 -To use NDS03A in your city, make sure to meet below requirements:
190 -
191 191  * Your local operator has already distributed an NB-IoT Network.
192 -* The local NB-IoT network used the band that NDS03A supports.
134 +* The local NB-IoT network used the band that NMDS200 supports.
193 193  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
194 194  
195 -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.
196 196  
197 -[[image:image-20221117142300-1.png]]
139 +[[image:image-20221208090742-1.png]]
198 198  
199 199  
200 -=== 2.2.2 Insert NB-IoT SIM card ===
142 +=== 2.2.1 Insert NB-IoT SIM card ===
201 201  
202 202  
203 203  Insert the NB-IoT Card get from your provider.
... ... @@ -207,10 +207,10 @@
207 207  [[image:image-20221021110745-6.png]] ​
208 208  
209 209  
210 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
152 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
211 211  
212 212  
213 -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.
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.
214 214  
215 215  (% style="color:blue" %)**Connection:**
216 216  
... ... @@ -233,11 +233,11 @@
233 233  
234 234  * Flow Control: (% style="color:red" %)**None**
235 235  
236 -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**(%%).
237 237  
238 238  ​[[image:image-20221021110817-7.png]]
239 239  
240 -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.
241 241  
242 242  
243 243  (% 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]]
... ... @@ -244,13 +244,13 @@
244 244  
245 245  
246 246  
247 -=== 2.2.4 Use CoAP protocol to uplink data ===
189 +=== 2.2.3 Use CoAP protocol to uplink data ===
248 248  
249 249  
250 250  (% 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/]]
251 251  
252 252  
253 -(% style="color:blue" %)**Use below commands in NDS03A:**
195 +(% style="color:blue" %)**Use below commands in NMDS200:**
254 254  
255 255  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
256 256  
... ... @@ -263,15 +263,14 @@
263 263  [[image:image-20221021110948-8.png]]
264 264  
265 265  
266 -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.
267 267  
268 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
210 +[[image:1670405841875-916.png]] ​
269 269  
270 270  
213 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
271 271  
272 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
273 273  
274 -
275 275  (% style="color:blue" %)**AT Commands:**
276 276  
277 277  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -287,10 +287,9 @@
287 287  
288 288  ​
289 289  
231 +=== 2.2.5 Use MQTT protocol to uplink data ===
290 290  
291 -=== 2.2.6 Use MQTT protocol to uplink data ===
292 292  
293 -
294 294  (% style="color:blue" %)**AT Commands:**
295 295  
296 296  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -310,7 +310,7 @@
310 310  ​ [[image:image-20221118103445-7.png]]
311 311  
312 312  
313 -[[image:image-20221118103453-8.png||height="608" width="841"]]
253 +[[image:1670405928926-116.png]]
314 314  
315 315  ​
316 316  
... ... @@ -317,10 +317,9 @@
317 317  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.
318 318  
319 319  
260 +=== 2.2.6 Use TCP protocol to uplink data ===
320 320  
321 -=== 2.2.7 Use TCP protocol to uplink data ===
322 322  
323 -
324 324  (% style="color:blue" %)**AT Commands:**
325 325  
326 326  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -327,19 +327,19 @@
327 327  
328 328  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
329 329  
330 -​ [[image:image-20221021111125-14.png]]
269 +​ [[image:1670406036256-101.png||height="676" width="713"]]
331 331  
271 +
332 332  [[image:image-20221021111131-15.png]]
333 333  
334 334  ​
335 335  
276 +=== 2.2.7 Change Update Interval ===
336 336  
337 -=== 2.2.8 Change Update Interval ===
338 338  
339 -
340 340  User can use below command to change the (% style="color:blue" %)**uplink interval**.
341 341  
342 -* (% 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)
343 343  
344 344  (% style="color:red" %)**NOTE:**
345 345  
... ... @@ -346,78 +346,55 @@
346 346  1.  By default, the device will send an uplink message every 4 hour.
347 347  
348 348  
349 -
350 350  == 2.3  Uplink Payload ==
351 351  
352 352  
353 -The uplink payload includes 26 bytes in total by default.
291 +The uplink payload includes 23 bytes in total by default.
354 354  
355 355  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.
356 356  
357 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
358 358  
359 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
360 -|=(% 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**
361 -|=(% 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"]]
362 362  
363 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
364 -|(% 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" %)(((
365 365  **1-32 group**
366 366  )))
367 -|(% 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" %)...
368 368  
306 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
369 369  
308 +[[image:1670406261143-723.png]]
370 370  
371 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
372 372  
311 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
373 373  
374 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
375 -|=(% 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**
376 -|=(% 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)
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__(%%)**
377 377  
378 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
379 -|(% 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**
380 -|(% 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)
381 -
382 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
383 -|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
384 -**1-32 group**
385 -)))
386 -|(% 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" %)......
387 -
388 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
389 -
390 -[[image:image-20221117145932-2.png]]
391 -
392 -
393 -The payload is ASCII string, representative same HEX:
394 -
395 -**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__(%%)**
396 -
397 397  **where:**
398 398  
399 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
317 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
400 400  
401 401  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
402 402  
403 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
321 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
404 404  
405 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
323 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
406 406  
407 407  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
408 408  
409 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
327 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
410 410  
411 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
329 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
412 412  
413 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
331 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
414 414  
415 -* (% style="color:#037691" %)**last open time:  **(%%)0x000017 =23
333 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
416 416  
417 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
418 418  
419 419  
420 -
421 421  == 2.4  Payload Explanation and Sensor Interface ==
422 422  
423 423  === 2.4.1  Device ID ===
... ... @@ -439,13 +439,13 @@
439 439  
440 440  Specify the software version: 0x64=100, which means firmware version 1.00.
441 441  
442 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
358 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
443 443  
444 444  
445 445  === 2.4.3  Battery Info ===
446 446  
447 447  
448 -Check the battery voltage for NDS03A.
364 +Check the battery voltage for NMDS200.
449 449  
450 450  Ex1: 0x0B45 = 2885mV
451 451  
... ... @@ -457,51 +457,49 @@
457 457  
458 458  NB-IoT Network signal Strength.
459 459  
460 -**Ex1: 0x1d = 29**
376 +(% style="color:blue" %)**Ex1: 0x1d = 29**
461 461  
462 -**0**  -113dBm or less
378 +(% style="color:#037691" %)**0** (%%) -113dBm or less
463 463  
464 -**1**  -111dBm
380 +(% style="color:#037691" %)**1**  (%%) -111dBm
465 465  
466 -**2...30** -109dBm... -53dBm
382 +(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
467 467  
468 -**31**   -51dBm or greater
384 +(% style="color:#037691" %)**31** (%%) -51dBm or greater
469 469  
470 -**99**    Not known or not detectable
386 +(% style="color:#037691" %)**99** (%%) Not known or not detectable
471 471  
472 472  
473 -=== 2.4.5  Disalarm: (default: 0) ===
389 +=== 2.4.5  Distance ===
474 474  
475 475  
476 -(% 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.
392 +[[image:1670407401682-959.png]]
477 477  
478 -(% 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.
479 479  
480 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
395 +(% style="color:blue" %)**Object1 Distance:**
481 481  
397 +Distance between sensor probe to the first object. (unit: cm)
482 482  
483 -=== 2.4.6  Keep Status & Keep Time ===
399 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
484 484  
401 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
485 485  
486 -Shows the configure value of Alarm Base on Timeout Feature
487 487  
404 +(% style="color:blue" %)**Object2 Distance:**
488 488  
489 -=== 2.4.7  Timestamp ===
406 +Distance between sensor probe to the second object. (unit: cm)
490 490  
491 491  
492 -Timestamp : 0x6315537b =1662342011
409 +=== 2.4.6  Timestamp ===
493 493  
494 494  
495 -=== 2.4.8  Switch Dual Channel Mode ===
412 +Timestamp : 0x6315537b =1662342011
496 496  
497 497  
498 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
499 -
500 -
501 501  == 2.5  Downlink Payload ==
502 502  
503 503  
504 -By default, NDS03A prints the downlink payload to console port.
418 +By default, NMDS200 prints the downlink payload to console port.
505 505  
506 506  [[image:image-20221021111414-18.png]] ​
507 507  
... ... @@ -518,7 +518,7 @@
518 518  
519 519  * (% style="color:#037691" %)**Reset**
520 520  
521 -If payload = 0x04FF, it will reset the NDS03A
435 +If payload = 0x04FF, it will reset the NMDS200
522 522  
523 523  * (% style="color:#037691" %)**INTMOD**
524 524  
... ... @@ -528,120 +528,36 @@
528 528  == 2.6  ​LED Indicator ==
529 529  
530 530  
531 -The NDS03A has an internal LED which is to show the status of different states.
445 +The NMDS200 has an internal LED which is to show the status of different states.
532 532  
533 533  * When the device starts normally, the LED will light up for 1 second.
534 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
448 +* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
535 535  * For each uplink probe, LED will be on for 500ms.
536 536  
537 537  
538 538  
539 -== 2.7  Alarm Base on Timeout ==
453 +== 2.7  Distance alarm function ==
540 540  
541 541  
542 -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:
456 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
543 543  
458 +(% style="color:#037691" %)**Example 1:**
544 544  
545 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
460 +AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
546 546  
547 -Keep Status = 1: Monitor Close to Open event
462 +AT+ ALARM2 =min,max
548 548  
549 -Keep Status = 0: Monitor Open to Close event
550 550  
465 +(% style="color:#037691" %)**Example 2:**
551 551  
552 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
467 +AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
553 553  
554 -Range 0 ~~ 65535(0xFFFF) seconds.
555 555  
556 -If keep time = 0, Disable Alarm Base on Timeout feature.
557 557  
558 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
559 559  
472 +== 2.8  Set the number of data to be uploaded and the recording time ==
560 560  
561 -(% style="color:blue" %)**AT Command to configure:**
562 562  
563 -(% style="color:blue" %)**PB14 PIN:**
564 -
565 -(% 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.
566 -
567 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
568 -
569 -
570 -(% style="color:blue" %)**PB15 PIN:**
571 -
572 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
573 -
574 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
575 -
576 -
577 -== 2.8  Set debug mode ==
578 -
579 -
580 -Feature: Enable or Disable debug mode
581 -
582 -(% style="color:blue" %)**AT Command: AT+DEBUG**
583 -
584 -[[image:image-20221021111629-21.png]]
585 -
586 -
587 -
588 -== 2.9  Clear Flash Record ==
589 -
590 -
591 -Feature: Clear flash storage for data log feature.
592 -
593 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
594 -
595 -[[image:image-20221021111527-19.png]]
596 -
597 -
598 -
599 -== 2.10  Count Mod ==
600 -
601 -
602 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
603 -
604 -[[image:image-20221118092935-1.png]]
605 -
606 -
607 -
608 -== 2.11  Interrupt Pin Channel Mod ==
609 -
610 -
611 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
612 -
613 -[[image:image-20221118093144-2.png]]
614 -
615 -
616 -
617 -== 2.12 TTRIG1/2 timeout status alarm ==
618 -
619 -
620 -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.
621 -
622 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
623 -
624 -[[image:image-20221118093512-3.png]]
625 -
626 -
627 -
628 -== 2.13  Select counting mode ==
629 -
630 -
631 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
632 -
633 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
634 -
635 -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.
636 -
637 -[[image:image-20221118093658-4.png]]
638 -
639 -
640 -
641 -
642 -== 2.14  Set the number of data to be uploaded and the recording time ==
643 -
644 -
645 645  (% style="color:blue" %)**AT Command:**
646 646  
647 647  (% 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)
... ... @@ -649,7 +649,7 @@
649 649  (% 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.
650 650  
651 651  
652 -== 2.15  Read or Clear cached data ==
482 +== 2.9  Read or Clear cached data ==
653 653  
654 654  
655 655  (% style="color:blue" %)**AT Command:**
... ... @@ -658,27 +658,24 @@
658 658  
659 659  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
660 660  
661 -[[image:image-20221118094227-5.png]]
491 +[[image:1670408172929-569.png]]
662 662  
663 663  
494 +== 2.10  ​Firmware Change Log ==
664 664  
665 -== 2.16  ​Firmware Change Log ==
666 666  
667 -
668 668  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 670  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
671 671  
672 672  
502 +== 2.11  ​Battery Analysis ==
673 673  
674 -== 2.17  ​Battery Analysis ==
504 +=== 2.11.1  ​Battery Type ===
675 675  
676 676  
677 -=== 2.17.1  ​Battery Type ===
507 +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.
678 678  
679 -
680 -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.
681 -
682 682  The battery is designed to last for several years depends on the actual use environment and update interval. 
683 683  
684 684  The battery-related documents as below:
... ... @@ -692,10 +692,9 @@
692 692  [[image:image-20221021111911-26.png]] ​
693 693  
694 694  
522 +=== 2.11.2  Power consumption Analyze ===
695 695  
696 -=== 2.17.2  Power consumption Analyze ===
697 697  
698 -
699 699  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.
700 700  
701 701  Instruction to use as below:
... ... @@ -715,21 +715,18 @@
715 715  [[image:1666596205057-567.png]] ​
716 716  
717 717  
544 +=== 2.11.3  ​Battery Note ===
718 718  
719 -=== 2.17.3  ​Battery Note ===
720 720  
721 -
722 722  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.
723 723  
724 724  
550 +=== 2.11.4  Replace the battery ===
725 725  
726 -=== 2.17.4  Replace the battery ===
727 727  
553 +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).
728 728  
729 -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).
730 730  
731 -
732 -
733 733  = 3. ​ Access NB-IoT Module =
734 734  
735 735  
... ... @@ -737,13 +737,12 @@
737 737  
738 738  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/]] 
739 739  
563 +
740 740  [[image:image-20221118094449-6.png]] ​
741 741  
742 742  
743 -
744 744  = 4.  Using the AT Commands =
745 745  
746 -
747 747  == 4.1  Access AT Commands ==
748 748  
749 749  
... ... @@ -782,63 +782,55 @@
782 782  
783 783  AT+SERVADDR  : Server Address
784 784  
785 -AT+TR      :  Get or Set record time
607 +AT+TR      :  Get or Set record time
786 786  
787 -AT+NOUD      : Get or Set the number of data to be uploaded
609 +AT+NOUD :  Get or Set the number of data to be uploaded
788 788  
789 789  AT+CDP     :  Read or Clear cached data
790 790  
791 -AT+ DEBUG   : Enable or Disable debug mode
613 +AT+DEBUG:  Enable or Disable debug mode
792 792  
793 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
615 +AT+ALARM1:  Get or Set alarm of distance1
794 794  
795 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
617 +AT+ALARM2:  Get or Set alarm of distance2
796 796  
797 -AT+COUNTMOD  :  Get or Set the count mode
619 +AT+GETSENSORVALUE :  Returns the current sensor measurement
798 798  
799 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
621 +AT+POWERIC :  Get or set the Power IC flag
800 800  
801 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
802 802  
803 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
804 -
805 -AT+ CLRC   :  Clear current door open count
806 -
807 -
808 808  (% style="color:blue" %)**COAP Management**      
809 809  
810 -AT+URI            : Resource parameters
626 +AT+URI :  Resource parameters
811 811  
812 812  
813 813  (% style="color:blue" %)**UDP Management**
814 814  
815 -AT+CFM          : Upload confirmation mode (only valid for UDP)
631 +AT+CFM :  Upload confirmation mode (only valid for UDP)
816 816  
817 817  
818 818  (% style="color:blue" %)**MQTT Management**
819 819  
820 -AT+CLIENT               : Get or Set MQTT client
636 +AT+CLIENT  : Get or Set MQTT client
821 821  
822 -AT+UNAME  : Get or Set MQTT Username
638 +AT+UNAME : Get or Set MQTT Username
823 823  
824 -AT+PWD                  : Get or Set MQTT password
640 +AT+PWD  :  Get or Set MQTT password
825 825  
826 -AT+PUBTOPIC  : Get or Set MQTT publish topic
642 +AT+PUBTOPIC :  Get or Set MQTT publish topic
827 827  
828 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
644 +AT+SUBTOPIC :  Get or Set MQTT subscription topic
829 829  
830 830  
831 831  (% style="color:blue" %)**Information**          
832 832  
833 -AT+FDR  : Factory Data Reset
649 +AT+FDR :  Factory Data Reset
834 834  
835 -AT+PWORD  : Serial Access Password
651 +AT+PWORD :  Serial Access Password
836 836  
837 837  
838 -
839 839  = ​5.  FAQ =
840 840  
841 -
842 842  == 5.1 ​ How to Upgrade Firmware ==
843 843  
844 844  
... ... @@ -846,13 +846,11 @@
846 846  
847 847  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]]
848 848  
849 -(% 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.**
663 +(% 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.**
850 850  
851 851  
852 -
853 853  = 6.  Trouble Shooting =
854 854  
855 -
856 856  == 6.1  ​Connection problem when uploading firmware ==
857 857  
858 858  
... ... @@ -859,7 +859,6 @@
859 859  (% 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]]
860 860  
861 861  
862 -
863 863  == 6.2  AT Command input doesn't work ==
864 864  
865 865  
... ... @@ -866,20 +866,18 @@
866 866  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.
867 867  
868 868  
869 -
870 870  = 7. ​ Order Info =
871 871  
872 872  
873 -Part Number**:** NDS03A
683 +Part Number:(% style="color:blue" %)** NMDS200**
874 874  
875 875  
876 -
877 877  = 8.  Packing Info =
878 878  
879 879  
880 880  (% style="color:blue" %)**Package Includes**:
881 881  
882 -* NDS03A Open/Close Door Sensor x 1
691 +* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
883 883  
884 884  = 9.  Support =
885 885  
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-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0