Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 70.18 >
edited by Xiaoling
on 2022/11/18 11:20
To version < 90.12 >
edited by Xiaoling
on 2023/05/26 10:14
>
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,34 +72,37 @@
72 72  * Micro SIM card slot for NB-IoT SIM
73 73  * 8500mAh Battery for long-term use
74 74  
81 +== 1.3 Radar probe specification ==
75 75  
76 76  
77 -== 1.3  Storage & Operation ==
84 +* Measuring Method: FMCW
85 +* Frequency: 24.000 ~~ 24.500 GHz
86 +* Measurement output power: 6dBm
87 +* Measure range: 0.5 ~~ 20m
88 +* Accuracy: ±0.1m
89 +* Resolution: 0.01m
90 +* Horizontal Angel: 78°
91 +* Vertical Angel: 23°
78 78  
93 +== 1.4  Storage Temperature ==
79 79  
80 -Temperature -40°C to +85°C
81 81  
96 + -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]]
102 +* Horizontal distance measurement
103 +* Liquid level measurement
104 +* Parking management system
105 +* Object proximity and presence detection
106 +* Intelligent trash can management system
107 +* Robot obstacle avoidance
108 +* Automatic control
109 +* Sewer
110 +* Bottom water level monitoring
100 100  
101 -
102 -
103 103  == 1.6  Specification ==
104 104  
105 105  
... ... @@ -106,98 +106,62 @@
106 106  (% style="color:blue" %)**Common DC Characteristics:**
107 107  
108 108  * Supply Voltage: 2.1v ~~ 3.6v
109 -* Operating Temperature: -40 ~~ 85°C
118 +* 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
122 +* B1 @H-FDD: 2100MHz
123 +* B3 @H-FDD: 1800MHz
124 +* B8 @H-FDD: 900MHz
125 +* B5 @H-FDD: 850MHz
126 +* B20 @H-FDD: 800MHz
127 +* B28 @H-FDD: 700MHz
119 119  
129 +== 1.7  Installation ==
120 120  
121 121  
122 -== 1.7  Pin Definitions and Switch ==
132 +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]]
135 +[[image:image-20221207170748-1.png]]
126 126  
127 127  
128 -=== 1.7.1  Pin Definition ===
138 + [[image:image-20221207170748-2.png||height="345" width="634"]]
129 129  
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]]
141 +== 1.8  Pin Definitions and Switch ==
132 132  
133 133  
134 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
144 +[[image:1670404362039-351.png]]
135 135  
136 136  
137 -Power on Device when putting this jumper.
147 += 2.  Use NMDS200 to communicate with IoT Server =
138 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.
152 +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:
154 +The diagram below shows the working flow in the default firmware of NMDS200:
180 180  
181 -[[image:image-20221021110615-5.png]]
156 +[[image:image-20221021110615-5.png||height="996" width="492"]]
182 182  
183 183  
184 -== 2.2 ​ Configure NDS03A ==
159 +== 2.2 ​ Configure NMDS200 ==
185 185  
186 -=== 2.2.1 Test Requirement ===
187 187  
162 +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.
165 +* 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.
168 +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]]
170 +[[image:image-20221209090938-1.png]]
198 198  
199 199  
200 -=== 2.2.2 Insert NB-IoT SIM card ===
173 +=== 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 ===
183 +=== 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.
186 +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,24 +233,23 @@
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**(%%).
209 +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.
213 +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 244  
245 245  
219 +=== 2.2.3 Use CoAP protocol to uplink data ===
246 246  
247 -=== 2.2.4 Use CoAP protocol to uplink data ===
248 248  
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:**
225 +(% 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  
... ... @@ -260,15 +260,15 @@
260 260  
261 261  For parameter description, please refer to AT command set
262 262  
263 -[[image:image-20221021110948-8.png]]
235 +[[image:1670471530120-960.png||height="647" width="674"]]
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.
238 +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"]] ​
240 +[[image:1670405841875-916.png]] ​
269 269  
270 270  
271 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
243 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
272 272  
273 273  
274 274  (% style="color:blue" %)**AT Commands:**
... ... @@ -279,7 +279,7 @@
279 279  
280 280  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
281 281  
282 -​ [[image:image-20221021111025-10.png]]
254 +​ [[image:1670471559211-638.png]]
283 283  
284 284  
285 285  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -286,7 +286,7 @@
286 286  
287 287  ​
288 288  
289 -=== 2.2.6 Use MQTT protocol to uplink data ===
261 +=== 2.2.5 Use MQTT protocol to uplink data ===
290 290  
291 291  
292 292  (% style="color:blue" %)**AT Commands:**
... ... @@ -305,10 +305,10 @@
305 305  
306 306  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
307 307  
308 -​ [[image:image-20221118103445-7.png]]
280 +​ [[image:1670471584490-640.png]]
309 309  
310 310  
311 -[[image:image-20221118103453-8.png||height="608" width="841"]]
283 +[[image:1670405928926-116.png]]
312 312  
313 313  ​
314 314  
... ... @@ -315,7 +315,7 @@
315 315  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.
316 316  
317 317  
318 -=== 2.2.7 Use TCP protocol to uplink data ===
290 +=== 2.2.6 Use TCP protocol to uplink data ===
319 319  
320 320  
321 321  (% style="color:blue" %)**AT Commands:**
... ... @@ -324,18 +324,19 @@
324 324  
325 325  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
326 326  
327 -​ [[image:image-20221021111125-14.png]]
299 +​ [[image:1670471613823-833.png]]
328 328  
301 +
329 329  [[image:image-20221021111131-15.png]]
330 330  
331 331  ​
332 332  
333 -=== 2.2.8 Change Update Interval ===
306 +=== 2.2.7 Change Update Interval ===
334 334  
335 335  
336 336  User can use below command to change the (% style="color:blue" %)**uplink interval**.
337 337  
338 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
311 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
339 339  
340 340  (% style="color:red" %)**NOTE:**
341 341  
... ... @@ -345,74 +345,48 @@
345 345  == 2.3  Uplink Payload ==
346 346  
347 347  
348 -The uplink payload includes 26 bytes in total by default.
321 +The uplink payload includes 23 bytes in total by default.
349 349  
350 350  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.
351 351  
352 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
353 353  
354 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
355 -|=(% 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:60px" %)**1**|(% style="width:90px" %)**3**|(% style="width:100px" %)**3**
356 -|=(% 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)
326 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
327 +|=(% scope="row" style="width: 60px;background-color:#4F81BD;color:white" %)**Size(bytes)**|(% style="width:50px;background-color:#4F81BD;color:white" %)**8**|(% style="width:30px;background-color:#4F81BD;color:white" %)**2**|(% style="width:30px;background-color:#4F81BD;color:white" %)**2**|(% style="width:75px;background-color:#4F81BD;color:white" %)**1**|(% style="width:30px;background-color:#4F81BD;color:white" %)**1**|(% style="width:50px;background-color:#4F81BD;color:white" %)**1**|(% style="width:60px;background-color:#4F81BD;color:white" %)**2**|(% style="width:60px;background-color:#4F81BD;color:white" %)**2**
328 +|=(% 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"]]
357 357  
358 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
359 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
330 +(% border="1" style="background-color:#ffffcc; color:green; width:429px" %)
331 +|(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((
360 360  **1-32 group**
361 361  )))
362 -|(% 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" %)...
334 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...
363 363  
336 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
364 364  
338 +[[image:1670406261143-723.png]]
365 365  
366 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
367 367  
341 +The payload is ASCII string, representative same HEX: **0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
368 368  
369 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
370 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:45px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:60px" %)**1**|(% style="width:60px" %)**1**|(% style="width:88px" %)**3**|(% style="width:80px" %)**3**
371 -|=(% 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)
372 -
373 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
374 -|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:75px" %)**1**|(% style="width:75px" %)**3**
375 -|(% 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)
376 -
377 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
378 -|(% style="width:90px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
379 -**1-32 group**
380 -)))
381 -|(% style="width:102px" %)last open time (pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:100px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
382 -
383 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
384 -
385 -[[image:image-20221117145932-2.png]]
386 -
387 -
388 -The payload is ASCII string, representative same HEX:
389 -
390 -**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__(%%)**
391 -
392 392  **where:**
393 393  
394 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
345 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
395 395  
396 396  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
397 397  
398 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
349 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
399 399  
400 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
351 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
401 401  
402 402  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
403 403  
404 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
355 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
405 405  
406 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
357 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
407 407  
408 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
359 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
409 409  
410 -* (% style="color:#037691" %)**last open time:  **(%%)0x000017 =23
361 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
411 411  
412 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
413 -
414 -
415 -
416 416  == 2.4  Payload Explanation and Sensor Interface ==
417 417  
418 418  === 2.4.1  Device ID ===
... ... @@ -434,13 +434,13 @@
434 434  
435 435  Specify the software version: 0x64=100, which means firmware version 1.00.
436 436  
437 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
384 +For example 0x00 64 : This device is NMDS200 with firmware version 1.0.0.
438 438  
439 439  
440 440  === 2.4.3  Battery Info ===
441 441  
442 442  
443 -Check the battery voltage for NDS03A.
390 +Check the battery voltage for NMDS200.
444 444  
445 445  Ex1: 0x0B45 = 2885mV
446 446  
... ... @@ -452,52 +452,56 @@
452 452  
453 453  NB-IoT Network signal Strength.
454 454  
455 -**Ex1: 0x1d = 29**
402 +(% style="color:blue" %)**Ex1: 0x1d = 29**
456 456  
457 -**0**  -113dBm or less
404 +(% style="color:#037691" %)**0** (%%) -113dBm or less
458 458  
459 -**1**  -111dBm
406 +(% style="color:#037691" %)**1**  (%%) -111dBm
460 460  
461 -**2...30** -109dBm... -53dBm
408 +(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
462 462  
463 -**31**   -51dBm or greater
410 +(% style="color:#037691" %)**31** (%%) -51dBm or greater
464 464  
465 -**99**    Not known or not detectable
412 +(% style="color:#037691" %)**99** (%%) Not known or not detectable
466 466  
467 467  
468 -=== 2.4.5  Disalarm: (default: 0) ===
415 +=== 2.4.5  Distance ===
469 469  
470 470  
471 -(% 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.
418 +[[image:1670407401682-959.png]]
472 472  
473 -(% 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.
474 474  
475 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
421 +(% style="color:blue" %)**Object1 Distance:**
476 476  
423 +Distance between sensor probe to the first object. (unit: cm)
477 477  
478 -=== 2.4.6  Keep Status & Keep Time ===
425 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
479 479  
427 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
480 480  
481 -Shows the configure value of Alarm Base on Timeout Feature
482 482  
430 +(% style="color:blue" %)**Object2 Distance:**
483 483  
484 -=== 2.4.7  Timestamp ===
432 +Distance between sensor probe to the second object. (unit: cm)
485 485  
486 486  
487 -Timestamp : 0x6315537b =1662342011
435 +=== 2.4.6  Timestamp ===
488 488  
489 489  
490 -=== 2.4.8  Switch Dual Channel Mode ===
438 +Timestamp : 0x6315537b =1662342011
491 491  
492 492  
493 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
494 -
495 -
496 496  == 2.5  Downlink Payload ==
497 497  
498 498  
499 -By default, NDS03A prints the downlink payload to console port.
444 +By default, NMDS200 prints the downlink payload to console port.
500 500  
446 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
447 +|(% style="background-color:#d9e2f3; color:#0070c0" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:97px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:183px" %)**Downlink payload size(bytes)**
448 +|TDC (Transmit Time Interval)|Any|(% style="width:97px" %)01|(% style="width:183px" %)4
449 +|RESET|Any|(% style="width:97px" %)04|(% style="width:183px" %)2
450 +|INTMOD|Any|(% style="width:97px" %)06|(% style="width:183px" %)4
451 +
501 501  [[image:image-20221021111414-18.png]] ​
502 502  
503 503  
... ... @@ -513,7 +513,7 @@
513 513  
514 514  * (% style="color:#037691" %)**Reset**
515 515  
516 -If payload = 0x04FF, it will reset the NDS03A
467 +If payload = 0x04FF, it will reset the NMDS200
517 517  
518 518  * (% style="color:#037691" %)**INTMOD**
519 519  
... ... @@ -523,114 +523,32 @@
523 523  == 2.6  ​LED Indicator ==
524 524  
525 525  
526 -The NDS03A has an internal LED which is to show the status of different states.
477 +The NMDS200 has an internal LED which is to show the status of different states.
527 527  
528 528  * When the device starts normally, the LED will light up for 1 second.
529 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
480 +* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
530 530  * For each uplink probe, LED will be on for 500ms.
531 531  
483 +== 2.7  Distance alarm function ==
532 532  
533 533  
534 -== 2.7  Alarm Base on Timeout ==
486 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
535 535  
488 +(% style="color:#037691" %)**Example 1:**
536 536  
537 -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:
490 +AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
538 538  
492 +AT+ ALARM2 =min,max
539 539  
540 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
541 541  
542 -Keep Status = 1: Monitor Close to Open event
495 +(% style="color:#037691" %)**Example 2:**
543 543  
544 -Keep Status = 0: Monitor Open to Close event
497 +AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
545 545  
546 546  
547 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
500 +== 2.8  Set the number of data to be uploaded and the recording time ==
548 548  
549 -Range 0 ~~ 65535(0xFFFF) seconds.
550 550  
551 -If keep time = 0, Disable Alarm Base on Timeout feature.
552 -
553 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
554 -
555 -
556 -(% style="color:blue" %)**AT Command to configure:**
557 -
558 -(% style="color:blue" %)**PB14 PIN:**
559 -
560 -(% 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.
561 -
562 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
563 -
564 -
565 -(% style="color:blue" %)**PB15 PIN:**
566 -
567 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
568 -
569 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
570 -
571 -
572 -== 2.8  Set debug mode ==
573 -
574 -
575 -Feature: Enable or Disable debug mode
576 -
577 -(% style="color:blue" %)**AT Command: AT+DEBUG**
578 -
579 -[[image:image-20221021111629-21.png]]
580 -
581 -
582 -
583 -== 2.9  Clear Flash Record ==
584 -
585 -
586 -Feature: Clear flash storage for data log feature.
587 -
588 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
589 -
590 -[[image:image-20221021111527-19.png]]
591 -
592 -
593 -== 2.10  Count Mod ==
594 -
595 -
596 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
597 -
598 -[[image:image-20221118092935-1.png]]
599 -
600 -
601 -== 2.11  Interrupt Pin Channel Mod ==
602 -
603 -
604 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
605 -
606 -[[image:image-20221118093144-2.png]]
607 -
608 -
609 -== 2.12 TTRIG1/2 timeout status alarm ==
610 -
611 -
612 -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.
613 -
614 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
615 -
616 -[[image:image-20221118093512-3.png]]
617 -
618 -
619 -== 2.13  Select counting mode ==
620 -
621 -
622 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
623 -
624 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
625 -
626 -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.
627 -
628 -[[image:image-20221118093658-4.png]]
629 -
630 -
631 -== 2.14  Set the number of data to be uploaded and the recording time ==
632 -
633 -
634 634  (% style="color:blue" %)**AT Command:**
635 635  
636 636  (% 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)
... ... @@ -638,7 +638,7 @@
638 638  (% 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.
639 639  
640 640  
641 -== 2.15  Read or Clear cached data ==
510 +== 2.9  Read or Clear cached data ==
642 642  
643 643  
644 644  (% style="color:blue" %)**AT Command:**
... ... @@ -647,71 +647,25 @@
647 647  
648 648  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
649 649  
650 -[[image:image-20221118094227-5.png]]
519 +[[image:1670408172929-569.png]]
651 651  
652 652  
653 -== 2.16  ​Firmware Change Log ==
522 +== 2.10  ​Firmware Change Log ==
654 654  
655 655  
656 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
525 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]
657 657  
658 658  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
659 659  
660 660  
661 -== 2.17  ​Battery Analysis ==
530 +== 2.11 Battery & Power Consumption ==
662 662  
663 -=== 2.17.1  ​Battery Type ===
664 664  
533 +NMDS200 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
665 665  
666 -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.
535 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
667 667  
668 -The battery is designed to last for several years depends on the actual use environment and update interval. 
669 669  
670 -The battery-related documents as below:
671 -
672 -* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
673 -
674 -* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
675 -
676 -* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
677 -
678 -[[image:image-20221021111911-26.png]] ​
679 -
680 -
681 -=== 2.17.2  Power consumption Analyze ===
682 -
683 -
684 -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.
685 -
686 -Instruction to use as below:
687 -
688 -(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
689 -
690 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
691 -
692 -* Product Model
693 -
694 -* Uplink Interval
695 -
696 -* Working Mode
697 -
698 -And the Life expectation in difference case will be shown on the right.
699 -
700 -[[image:1666596205057-567.png]] ​
701 -
702 -
703 -=== 2.17.3  ​Battery Note ===
704 -
705 -
706 -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.
707 -
708 -
709 -=== 2.17.4  Replace the battery ===
710 -
711 -
712 -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).
713 -
714 -
715 715  = 3. ​ Access NB-IoT Module =
716 716  
717 717  
... ... @@ -719,6 +719,7 @@
719 719  
720 720  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/]] 
721 721  
545 +
722 722  [[image:image-20221118094449-6.png]] ​
723 723  
724 724  
... ... @@ -754,65 +754,59 @@
754 754  
755 755  AT+INTMOD            : Set the trigger interrupt mode
756 756  
757 -AT+5VT  : Set extend the time of 5V power  
581 +AT+5VT  : Set extend the time of 5V power  
758 758  
759 -AT+PRO  : Choose agreement
583 +AT+PRO  : Choose agreement
760 760  
761 -AT+RXDL  : Extend the sending and receiving time
585 +AT+RXDL  : Extend the sending and receiving time
762 762  
763 -AT+SERVADDR  : Server Address
587 +AT+SERVADDR  : Server Address
764 764  
765 -AT+TR      :  Get or Set record time
589 +AT+TR      :  Get or Set record time
766 766  
767 -AT+NOUD      : Get or Set the number of data to be uploaded
591 +AT+NOUD :  Get or Set the number of data to be uploaded
768 768  
769 769  AT+CDP     :  Read or Clear cached data
770 770  
771 -AT+ DEBUG   : Enable or Disable debug mode
595 +AT+DEBUG:  Enable or Disable debug mode
772 772  
773 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
597 +AT+ALARM1:  Get or Set alarm of distance1
774 774  
775 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
599 +AT+ALARM2:  Get or Set alarm of distance2
776 776  
777 -AT+COUNTMOD  :  Get or Set the count mode
601 +AT+GETSENSORVALUE :  Returns the current sensor measurement
778 778  
779 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
603 +AT+POWERIC :  Get or set the Power IC flag
780 780  
781 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
782 782  
783 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
784 -
785 -AT+ CLRC   :  Clear current door open count
786 -
787 -
788 788  (% style="color:blue" %)**COAP Management**      
789 789  
790 -AT+URI            : Resource parameters
608 +AT+URI :  Resource parameters
791 791  
792 792  
793 793  (% style="color:blue" %)**UDP Management**
794 794  
795 -AT+CFM          : Upload confirmation mode (only valid for UDP)
613 +AT+CFM :  Upload confirmation mode (only valid for UDP)
796 796  
797 797  
798 798  (% style="color:blue" %)**MQTT Management**
799 799  
800 -AT+CLIENT               : Get or Set MQTT client
618 +AT+CLIENT  : Get or Set MQTT client
801 801  
802 -AT+UNAME  : Get or Set MQTT Username
620 +AT+UNAME : Get or Set MQTT Username
803 803  
804 -AT+PWD                  : Get or Set MQTT password
622 +AT+PWD  :  Get or Set MQTT password
805 805  
806 -AT+PUBTOPIC  : Get or Set MQTT publish topic
624 +AT+PUBTOPIC :  Get or Set MQTT publish topic
807 807  
808 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
626 +AT+SUBTOPIC :  Get or Set MQTT subscription topic
809 809  
810 810  
811 811  (% style="color:blue" %)**Information**          
812 812  
813 -AT+FDR  : Factory Data Reset
631 +AT+FDR :  Factory Data Reset
814 814  
815 -AT+PWORD  : Serial Access Password
633 +AT+PWORD :  Serial Access Password
816 816  
817 817  
818 818  = ​5.  FAQ =
... ... @@ -824,7 +824,7 @@
824 824  
825 825  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]]
826 826  
827 -(% 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.**
645 +(% 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.**
828 828  
829 829  
830 830  = 6.  Trouble Shooting =
... ... @@ -841,10 +841,16 @@
841 841  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.
842 842  
843 843  
662 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
663 +
664 +
665 +This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
666 +
667 +
844 844  = 7. ​ Order Info =
845 845  
846 846  
847 -Part Number**:** NDS03A
671 +Part Number:(% style="color:blue" %)** NMDS200**
848 848  
849 849  
850 850  = 8.  Packing Info =
... ... @@ -852,10 +852,8 @@
852 852  
853 853  (% style="color:blue" %)**Package Includes**:
854 854  
855 -* NDS03A Open/Close Door Sensor x 1
679 +* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
856 856  
857 -
858 -
859 859  = 9.  Support =
860 860  
861 861  
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-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