Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 70.21 >
edited by Xiaoling
on 2022/11/18 11:23
To version < 91.2 >
edited by Xiaoling
on 2023/08/15 14:21
>
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
... ... @@ -73,29 +73,39 @@
73 73  * 8500mAh Battery for long-term use
74 74  
75 75  
76 -== 1.3  Storage & Operation ==
77 77  
83 +== 1.3 Radar probe specification ==
78 78  
79 -Temperature -40°C to +85°C
80 80  
86 +* Measuring Method: FMCW
87 +* Frequency: 24.000 ~~ 24.500 GHz
88 +* Measurement output power: 6dBm
89 +* Measure range: 0.5 ~~ 20m
90 +* Accuracy: ±0.1m
91 +* Resolution: 0.01m
92 +* Horizontal Angel: 78°
93 +* Vertical Angel: 23°
81 81  
82 -== 1.4  Mechanical ==
83 83  
84 84  
85 -[[image:image-20221117114937-4.png]]
97 +== 1.4  Storage Temperature ==
86 86  
87 87  
88 -[[image:image-20221117114949-5.png]]
100 + -40°C to +85°C
89 89  
90 90  
91 -[[image:image-20221117115010-6.png]]
92 -
93 -
94 -
95 95  == 1.5 ​ Applications ==
96 96  
97 97  
98 -[[image:image-20221117114842-3.png]]
106 +* Horizontal distance measurement
107 +* Liquid level measurement
108 +* Parking management system
109 +* Object proximity and presence detection
110 +* Intelligent trash can management system
111 +* Robot obstacle avoidance
112 +* Automatic control
113 +* Sewer
114 +* Bottom water level monitoring
99 99  
100 100  
101 101  
... ... @@ -105,97 +105,64 @@
105 105  (% style="color:blue" %)**Common DC Characteristics:**
106 106  
107 107  * Supply Voltage: 2.1v ~~ 3.6v
108 -* Operating Temperature: -40 ~~ 85°C
124 +* Operating Temperature: 0 ~~ 70°C
109 109  
110 110  (% style="color:blue" %)**NB-IoT Spec:**
111 111  
112 -* - B1 @H-FDD: 2100MHz
113 -* - B3 @H-FDD: 1800MHz
114 -* - B8 @H-FDD: 900MHz
115 -* - B5 @H-FDD: 850MHz
116 -* - B20 @H-FDD: 800MHz
117 -* - B28 @H-FDD: 700MHz
128 +* B1 @H-FDD: 2100MHz
129 +* B3 @H-FDD: 1800MHz
130 +* B8 @H-FDD: 900MHz
131 +* B5 @H-FDD: 850MHz
132 +* B20 @H-FDD: 800MHz
133 +* B28 @H-FDD: 700MHz
118 118  
119 119  
120 -== 1.7  Pin Definitions and Switch ==
121 121  
137 +== 1.7  Installation ==
122 122  
123 -[[image:image-20221021110429-4.png]]
124 124  
140 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
125 125  
126 -=== 1.7.1  Pin Definition ===
127 127  
143 +[[image:image-20221207170748-1.png]]
128 128  
129 -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]]
130 130  
146 + [[image:image-20221207170748-2.png||height="345" width="634"]]
131 131  
132 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
133 133  
149 +== 1.8  Pin Definitions and Switch ==
134 134  
135 -Power on Device when putting this jumper.
136 136  
152 +[[image:1670404362039-351.png]]
137 137  
138 -=== 1.7.3  BOOT MODE / SW1 ===
139 139  
155 += 2.  Use NMDS200 to communicate with IoT Server =
140 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 -=== 1.7.4  Reset Button ===
147 -
148 -
149 -Press to reboot the device.
150 -
151 -
152 -=== 1.7.5  LED ===
153 -
154 -
155 -The LED will blink when :
156 -
157 -1.  Boot the device in flash mode
158 -
159 -2.  Send an uplink packet
160 -
161 -
162 -== 1.8  Magnet Distance ==
163 -
164 -
165 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
166 -
167 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
168 -
169 -
170 -= 2.  Use NDS03A to communicate with IoT Server =
171 -
172 172  == 2.1  How it works ==
173 173  
174 174  
175 -In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.
160 +The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
176 176  
177 -The diagram below shows the working flow in the default firmware of NDS03A:
162 +The diagram below shows the working flow in the default firmware of NMDS200:
178 178  
179 -[[image:image-20221021110615-5.png]]
164 +[[image:image-20221021110615-5.png||height="996" width="492"]]
180 180  
181 181  
182 -== 2.2 ​ Configure NDS03A ==
167 +== 2.2 ​ Configure NMDS200 ==
183 183  
184 -=== 2.2.1 Test Requirement ===
185 185  
170 +To use NMDS200 in your city, make sure to meet below requirements:
186 186  
187 -To use NDS03A in your city, make sure to meet below requirements:
188 -
189 189  * Your local operator has already distributed an NB-IoT Network.
190 -* The local NB-IoT network used the band that NDS03A supports.
173 +* The local NB-IoT network used the band that NMDS200 supports.
191 191  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
192 192  
193 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDS03A will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
176 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NMDS200 will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
194 194  
195 -[[image:image-20221117142300-1.png]]
178 +[[image:image-20221209090938-1.png]]
196 196  
197 197  
198 -=== 2.2.2 Insert NB-IoT SIM card ===
181 +=== 2.2.1 Insert NB-IoT SIM card ===
199 199  
200 200  
201 201  Insert the NB-IoT Card get from your provider.
... ... @@ -205,10 +205,10 @@
205 205  [[image:image-20221021110745-6.png]] ​
206 206  
207 207  
208 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
191 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
209 209  
210 210  
211 -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.
194 +User need to configure NMDS200 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NMDS200 support AT Commands, user can use a USB to TTL adapter to connect to NMDS200 and use AT Commands to configure it, as below.
212 212  
213 213  (% style="color:blue" %)**Connection:**
214 214  
... ... @@ -231,24 +231,23 @@
231 231  
232 232  * Flow Control: (% style="color:red" %)**None**
233 233  
234 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
217 +Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
235 235  
236 236  ​[[image:image-20221021110817-7.png]]
237 237  
238 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
221 +NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
239 239  
240 240  
241 241  (% 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]]
242 242  
243 243  
227 +=== 2.2.3 Use CoAP protocol to uplink data ===
244 244  
245 -=== 2.2.4 Use CoAP protocol to uplink data ===
246 246  
247 -
248 248  (% 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/]]
249 249  
250 250  
251 -(% style="color:blue" %)**Use below commands in NDS03A:**
233 +(% style="color:blue" %)**Use below commands in NMDS200:**
252 252  
253 253  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
254 254  
... ... @@ -258,15 +258,15 @@
258 258  
259 259  For parameter description, please refer to AT command set
260 260  
261 -[[image:image-20221021110948-8.png]]
243 +[[image:1670471530120-960.png||height="647" width="674"]]
262 262  
263 263  
264 -After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
246 +After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server.
265 265  
266 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
248 +[[image:1670405841875-916.png]] ​
267 267  
268 268  
269 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
251 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
270 270  
271 271  
272 272  (% style="color:blue" %)**AT Commands:**
... ... @@ -277,7 +277,7 @@
277 277  
278 278  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
279 279  
280 -​ [[image:image-20221021111025-10.png]]
262 +​ [[image:1670471559211-638.png]]
281 281  
282 282  
283 283  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -284,7 +284,7 @@
284 284  
285 285  ​
286 286  
287 -=== 2.2.6 Use MQTT protocol to uplink data ===
269 +=== 2.2.5 Use MQTT protocol to uplink data ===
288 288  
289 289  
290 290  (% style="color:blue" %)**AT Commands:**
... ... @@ -303,10 +303,10 @@
303 303  
304 304  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
305 305  
306 -​ [[image:image-20221118103445-7.png]]
288 +​ [[image:1670471584490-640.png]]
307 307  
308 308  
309 -[[image:image-20221118103453-8.png||height="608" width="841"]]
291 +[[image:1670405928926-116.png]]
310 310  
311 311  ​
312 312  
... ... @@ -313,7 +313,7 @@
313 313  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.
314 314  
315 315  
316 -=== 2.2.7 Use TCP protocol to uplink data ===
298 +=== 2.2.6 Use TCP protocol to uplink data ===
317 317  
318 318  
319 319  (% style="color:blue" %)**AT Commands:**
... ... @@ -322,18 +322,19 @@
322 322  
323 323  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
324 324  
325 -​ [[image:image-20221021111125-14.png]]
307 +​ [[image:1670471613823-833.png]]
326 326  
309 +
327 327  [[image:image-20221021111131-15.png]]
328 328  
329 329  ​
330 330  
331 -=== 2.2.8 Change Update Interval ===
314 +=== 2.2.7 Change Update Interval ===
332 332  
333 333  
334 334  User can use below command to change the (% style="color:blue" %)**uplink interval**.
335 335  
336 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
319 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
337 337  
338 338  (% style="color:red" %)**NOTE:**
339 339  
... ... @@ -343,70 +343,48 @@
343 343  == 2.3  Uplink Payload ==
344 344  
345 345  
346 -The uplink payload includes 26 bytes in total by default.
329 +The uplink payload includes 23 bytes in total by default.
347 347  
348 348  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.
349 349  
350 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
351 351  
352 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
353 -|=(% 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**
354 -|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
334 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
335 +|(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:50px" %)**8**|(% style="background-color:#4f81bd; color:white; width:31px" %)**2**|(% style="background-color:#4f81bd; color:white; width:31px" %)**2**|(% style="background-color:#4f81bd; color:white; width:75px" %)**1**|(% style="background-color:#4f81bd; color:white; width:31px" %)**1**|(% style="background-color:#4f81bd; color:white; width:51px" %)**1**|(% style="background-color:#4f81bd; color:white; width:61px" %)**2**|(% style="background-color:#4f81bd; color:white; width:60px" %)**2**
336 +|(% style="width:93px" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) [[Distance 1>>||anchor="H2.4.5A0Distance"]] |(% style="width:93px" %) [[Distance 2>>||anchor="H2.4.5A0Distance"]]
355 355  
356 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
357 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
338 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:430px" %)
339 +|(% style="background-color:#4f81bd; color:white; width:80px" %)**4**|(% style="background-color:#4f81bd; color:white; width:80px" %)**2**|(% style="background-color:#4f81bd; color:white; width:80px" %)**2**|(% style="background-color:#4f81bd; color:white; width:80px" %)**4**|(% style="background-color:#4f81bd; color:white; width:110px" %)(((
358 358  **1-32 group**
359 359  )))
360 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
342 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...
361 361  
344 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
362 362  
363 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
346 +[[image:1670406261143-723.png]]
364 364  
365 365  
366 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
367 -|=(% 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:87px" %)**3**|(% style="width:80px" %)**3**
368 -|=(% 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)
349 +The payload is ASCII string, representative same HEX: **0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
369 369  
370 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
371 -|(% 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**
372 -|(% 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)
373 -
374 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
375 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
376 -**1-32 group**
377 -)))
378 -|(% 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" %)......
379 -
380 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
381 -
382 -[[image:image-20221117145932-2.png]]
383 -
384 -
385 -The payload is ASCII string, representative same HEX:
386 -
387 -**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__(%%)**
388 -
389 389  **where:**
390 390  
391 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
353 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
392 392  
393 393  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
394 394  
395 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
357 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
396 396  
397 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
359 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
398 398  
399 399  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
400 400  
401 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
363 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
402 402  
403 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
365 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
404 404  
405 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
367 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
406 406  
407 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
369 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
408 408  
409 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
410 410  
411 411  
412 412  == 2.4  Payload Explanation and Sensor Interface ==
... ... @@ -430,13 +430,13 @@
430 430  
431 431  Specify the software version: 0x64=100, which means firmware version 1.00.
432 432  
433 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
394 +For example 0x00 64 : This device is NMDS200 with firmware version 1.0.0.
434 434  
435 435  
436 436  === 2.4.3  Battery Info ===
437 437  
438 438  
439 -Check the battery voltage for NDS03A.
400 +Check the battery voltage for NMDS200.
440 440  
441 441  Ex1: 0x0B45 = 2885mV
442 442  
... ... @@ -448,55 +448,56 @@
448 448  
449 449  NB-IoT Network signal Strength.
450 450  
451 -**Ex1: 0x1d = 29**
412 +(% style="color:blue" %)**Ex1: 0x1d = 29**
452 452  
453 -**0**  -113dBm or less
414 +(% style="color:#037691" %)**0** (%%) -113dBm or less
454 454  
455 -**1**  -111dBm
416 +(% style="color:#037691" %)**1**  (%%) -111dBm
456 456  
457 -**2...30** -109dBm... -53dBm
418 +(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
458 458  
459 -**31**   -51dBm or greater
420 +(% style="color:#037691" %)**31** (%%) -51dBm or greater
460 460  
461 -**99**    Not known or not detectable
422 +(% style="color:#037691" %)**99** (%%) Not known or not detectable
462 462  
463 463  
464 -=== 2.4.5  Disalarm: (default: 0) ===
425 +=== 2.4.5  Distance ===
465 465  
466 466  
467 -(% 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.
428 +[[image:1670407401682-959.png]]
468 468  
469 -(% 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.
470 470  
471 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
431 +(% style="color:blue" %)**Object1 Distance:**
472 472  
433 +Distance between sensor probe to the first object. (unit: cm)
473 473  
474 -=== 2.4.6  Keep Status & Keep Time ===
435 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
475 475  
437 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
476 476  
477 -Shows the configure value of Alarm Base on Timeout Feature
478 478  
440 +(% style="color:blue" %)**Object2 Distance:**
479 479  
480 -=== 2.4.7  Timestamp ===
442 +Distance between sensor probe to the second object. (unit: cm)
481 481  
482 482  
483 -Timestamp : 0x6315537b =1662342011
445 +=== 2.4.6  Timestamp ===
484 484  
485 485  
486 -=== 2.4.8  Switch Dual Channel Mode ===
448 +Timestamp : 0x6315537b =1662342011
487 487  
488 488  
489 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
490 -
491 -
492 492  == 2.5  Downlink Payload ==
493 493  
494 494  
495 -By default, NDS03A prints the downlink payload to console port.
454 +By default, NMDS200 prints the downlink payload to console port.
496 496  
497 -[[image:image-20221021111414-18.png]] ​
456 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
457 +|(% style="background-color:#4f81bd; color:white" %)**Downlink Control Type**|(% style="background-color:#4f81bd; color:white" %)**FPort**|(% style="background-color:#4f81bd; color:white; width:97px" %)**Type Code**|(% style="background-color:#4f81bd; color:white; width:183px" %)**Downlink payload size(bytes)**
458 +|TDC (Transmit Time Interval)|Any|(% style="width:97px" %)01|(% style="width:183px" %)4
459 +|RESET|Any|(% style="width:97px" %)04|(% style="width:183px" %)2
460 +|INTMOD|Any|(% style="width:97px" %)06|(% style="width:183px" %)4
498 498  
499 -
500 500  **Examples:**
501 501  
502 502  * (% style="color:#037691" %)**Set TDC**
... ... @@ -509,7 +509,7 @@
509 509  
510 510  * (% style="color:#037691" %)**Reset**
511 511  
512 -If payload = 0x04FF, it will reset the NDS03A
474 +If payload = 0x04FF, it will reset the NMDS200
513 513  
514 514  * (% style="color:#037691" %)**INTMOD**
515 515  
... ... @@ -519,121 +519,42 @@
519 519  == 2.6  ​LED Indicator ==
520 520  
521 521  
522 -The NDS03A has an internal LED which is to show the status of different states.
484 +The NMDS200 has an internal LED which is to show the status of different states.
523 523  
524 524  * When the device starts normally, the LED will light up for 1 second.
525 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
487 +* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
526 526  * For each uplink probe, LED will be on for 500ms.
527 527  
528 528  
529 -== 2.7  Alarm Base on Timeout ==
530 530  
492 +== 2.7  Distance alarm function ==
531 531  
532 -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:
533 533  
495 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
534 534  
535 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
497 +(% style="color:#037691" %)**Example 1:**
536 536  
537 -Keep Status = 1: Monitor Close to Open event
499 +AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
538 538  
539 -Keep Status = 0: Monitor Open to Close event
501 +AT+ ALARM2 =min,max
540 540  
541 541  
542 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
504 +(% style="color:#037691" %)**Example 2:**
543 543  
544 -Range 0 ~~ 65535(0xFFFF) seconds.
506 +AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
545 545  
546 -If keep time = 0, Disable Alarm Base on Timeout feature.
547 547  
548 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
509 +== 2.8  Set the number of data to be uploaded and the recording time ==
549 549  
550 550  
551 -(% style="color:blue" %)**AT Command to configure:**
552 -
553 -(% style="color:blue" %)**PB14 PIN:**
554 -
555 -(% 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.
556 -
557 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
558 -
559 -
560 -(% style="color:blue" %)**PB15 PIN:**
561 -
562 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
563 -
564 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
565 -
566 -
567 -== 2.8  Set debug mode ==
568 -
569 -
570 -Feature: Enable or Disable debug mode
571 -
572 -(% style="color:blue" %)**AT Command: AT+DEBUG**
573 -
574 -[[image:image-20221021111629-21.png]]
575 -
576 -
577 -
578 -== 2.9  Clear Flash Record ==
579 -
580 -
581 -Feature: Clear flash storage for data log feature.
582 -
583 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
584 -
585 -[[image:image-20221021111527-19.png]]
586 -
587 -
588 -== 2.10  Count Mod ==
589 -
590 -
591 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
592 -
593 -[[image:image-20221118092935-1.png]]
594 -
595 -
596 -== 2.11  Interrupt Pin Channel Mod ==
597 -
598 -
599 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
600 -
601 -[[image:image-20221118093144-2.png]]
602 -
603 -
604 -== 2.12 TTRIG1/2 timeout status alarm ==
605 -
606 -
607 -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.
608 -
609 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
610 -
611 -[[image:image-20221118093512-3.png]]
612 -
613 -
614 -== 2.13  Select counting mode ==
615 -
616 -
617 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
618 -
619 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
620 -
621 -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.
622 -
623 -[[image:image-20221118093658-4.png]]
624 -
625 -
626 -== 2.14  Set the number of data to be uploaded and the recording time ==
627 -
628 -
629 629  (% style="color:blue" %)**AT Command:**
630 630  
631 -(% 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)
514 +(% 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, **also the time when the alarm function sends an uplink when it detects an alarm)**
632 632  
633 633  (% 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.
634 634  
635 635  
636 -== 2.15  Read or Clear cached data ==
519 +== 2.9  Read or Clear cached data ==
637 637  
638 638  
639 639  (% style="color:blue" %)**AT Command:**
... ... @@ -642,71 +642,25 @@
642 642  
643 643  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
644 644  
645 -[[image:image-20221118094227-5.png]]
528 +[[image:1670408172929-569.png]]
646 646  
647 647  
648 -== 2.16  ​Firmware Change Log ==
531 +== 2.10  ​Firmware Change Log ==
649 649  
650 650  
651 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
534 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]
652 652  
653 653  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
654 654  
655 655  
656 -== 2.17  ​Battery Analysis ==
539 +== 2.11 Battery & Power Consumption ==
657 657  
658 -=== 2.17.1  ​Battery Type ===
659 659  
542 +NMDS200 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
660 660  
661 -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.
544 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
662 662  
663 -The battery is designed to last for several years depends on the actual use environment and update interval. 
664 664  
665 -The battery-related documents as below:
666 -
667 -* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
668 -
669 -* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
670 -
671 -* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
672 -
673 -[[image:image-20221021111911-26.png]] ​
674 -
675 -
676 -=== 2.17.2  Power consumption Analyze ===
677 -
678 -
679 -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.
680 -
681 -Instruction to use as below:
682 -
683 -(% 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/]]
684 -
685 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
686 -
687 -* Product Model
688 -
689 -* Uplink Interval
690 -
691 -* Working Mode
692 -
693 -And the Life expectation in difference case will be shown on the right.
694 -
695 -[[image:1666596205057-567.png]] ​
696 -
697 -
698 -=== 2.17.3  ​Battery Note ===
699 -
700 -
701 -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.
702 -
703 -
704 -=== 2.17.4  Replace the battery ===
705 -
706 -
707 -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).
708 -
709 -
710 710  = 3. ​ Access NB-IoT Module =
711 711  
712 712  
... ... @@ -714,6 +714,7 @@
714 714  
715 715  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/]] 
716 716  
554 +
717 717  [[image:image-20221118094449-6.png]] ​
718 718  
719 719  
... ... @@ -749,65 +749,59 @@
749 749  
750 750  AT+INTMOD            : Set the trigger interrupt mode
751 751  
752 -AT+5VT  : Set extend the time of 5V power  
590 +AT+5VT  : Set extend the time of 5V power  
753 753  
754 -AT+PRO  : Choose agreement
592 +AT+PRO  : Choose agreement
755 755  
756 -AT+RXDL  : Extend the sending and receiving time
594 +AT+RXDL  : Extend the sending and receiving time
757 757  
758 -AT+SERVADDR  : Server Address
596 +AT+SERVADDR  : Server Address
759 759  
760 -AT+TR      :  Get or Set record time
598 +AT+TR      :  Get or Set record time
761 761  
762 -AT+NOUD      : Get or Set the number of data to be uploaded
600 +AT+NOUD :  Get or Set the number of data to be uploaded
763 763  
764 764  AT+CDP     :  Read or Clear cached data
765 765  
766 -AT+ DEBUG   : Enable or Disable debug mode
604 +AT+DEBUG:  Enable or Disable debug mode
767 767  
768 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
606 +AT+ALARM1:  Get or Set alarm of distance1
769 769  
770 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
608 +AT+ALARM2:  Get or Set alarm of distance2
771 771  
772 -AT+COUNTMOD  :  Get or Set the count mode
610 +AT+GETSENSORVALUE :  Returns the current sensor measurement
773 773  
774 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
612 +AT+POWERIC :  Get or set the Power IC flag
775 775  
776 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
777 777  
778 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
779 -
780 -AT+ CLRC   :  Clear current door open count
781 -
782 -
783 783  (% style="color:blue" %)**COAP Management**      
784 784  
785 -AT+URI            : Resource parameters
617 +AT+URI :  Resource parameters
786 786  
787 787  
788 788  (% style="color:blue" %)**UDP Management**
789 789  
790 -AT+CFM          : Upload confirmation mode (only valid for UDP)
622 +AT+CFM :  Upload confirmation mode (only valid for UDP)
791 791  
792 792  
793 793  (% style="color:blue" %)**MQTT Management**
794 794  
795 -AT+CLIENT               : Get or Set MQTT client
627 +AT+CLIENT  : Get or Set MQTT client
796 796  
797 -AT+UNAME  : Get or Set MQTT Username
629 +AT+UNAME : Get or Set MQTT Username
798 798  
799 -AT+PWD                  : Get or Set MQTT password
631 +AT+PWD  :  Get or Set MQTT password
800 800  
801 -AT+PUBTOPIC  : Get or Set MQTT publish topic
633 +AT+PUBTOPIC :  Get or Set MQTT publish topic
802 802  
803 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
635 +AT+SUBTOPIC :  Get or Set MQTT subscription topic
804 804  
805 805  
806 806  (% style="color:blue" %)**Information**          
807 807  
808 -AT+FDR  : Factory Data Reset
640 +AT+FDR :  Factory Data Reset
809 809  
810 -AT+PWORD  : Serial Access Password
642 +AT+PWORD :  Serial Access Password
811 811  
812 812  
813 813  = ​5.  FAQ =
... ... @@ -819,7 +819,7 @@
819 819  
820 820  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]]
821 821  
822 -(% 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.**
654 +(% 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.**
823 823  
824 824  
825 825  = 6.  Trouble Shooting =
... ... @@ -836,10 +836,16 @@
836 836  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.
837 837  
838 838  
671 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
672 +
673 +
674 +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]]//**.
675 +
676 +
839 839  = 7. ​ Order Info =
840 840  
841 841  
842 -Part Number**:** NDS03A
680 +Part Number:(% style="color:blue" %)** NMDS200**
843 843  
844 844  
845 845  = 8.  Packing Info =
... ... @@ -847,9 +847,10 @@
847 847  
848 848  (% style="color:blue" %)**Package Includes**:
849 849  
850 -* NDS03A Open/Close Door Sensor x 1
688 +* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
851 851  
852 852  
691 +
853 853  = 9.  Support =
854 854  
855 855  
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