Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 75.1 >
edited by Xiaoling
on 2022/12/07 17:32
To version < 88.2 >
edited by Xiaoling
on 2022/12/09 09:14
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,13 +1,28 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg]]
2 +[[image:LMDS200_10.jpg||height="572" width="572"]]
3 3  
4 4  
5 +
6 +
7 +
8 +(% style="display:none" %) (%%)
9 +
10 +
11 +
12 +
13 +
5 5  **Table of Contents：**
6 6  
16 +{{toc/}}
7 7  
8 8  
9 9  
10 10  
21 +
22 +
23 +
24 +
25 +
11 11  = 1.  Introduction =
12 12  
13 13  == 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
... ... @@ -15,25 +15,37 @@
15 15  
16 16  (((
17 17  The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor.
33 +)))
18 18  
19 -
35 +(((
20 20  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.
37 +)))
21 21  
39 +(((
22 22  NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
41 +)))
23 23  
43 +(((
24 24  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.
45 +)))
25 25  
47 +(((
26 26  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.
49 +)))
27 27  
51 +(((
28 28  NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
53 +)))
29 29  
55 +(((
30 30  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)
57 +)))
31 31  
59 +(((
32 32  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.
33 33  )))
34 34  
35 35  
36 -
37 37  == ​1.2  Features ==
38 38  
39 39  
... ... @@ -57,9 +57,9 @@
57 57  
58 58  
59 59  * Measuring Method: FMCW
60 -* Frequency: 24.000 24.500 GHz
87 +* Frequency: 24.000 ~~ 24.500 GHz
61 61  * Measurement output power: 6dBm
62 -* Measure range: 0.5 20m
89 +* Measure range: 0.5 ~~ 20m
63 63  * Accuracy: ±0.1m
64 64  * Resolution: 0.01m
65 65  * Horizontal Angel: 78°
... ... @@ -67,7 +67,6 @@
67 67  
68 68  
69 69  
70 -
71 71  == 1.4  Storage Temperature ==
72 72  
73 73  
... ... @@ -74,13 +74,9 @@
74 74   -40°C to +85°C
75 75  
76 76  
77 -
78 -
79 -
80 80  == 1.5 ​ Applications ==
81 81  
82 82  
83 -
84 84  * Horizontal distance measurement
85 85  * Liquid level measurement
86 86  * Parking management system
... ... @@ -118,10 +118,12 @@
118 118  Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
119 119  
120 120  
121 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
143 +[[image:image-20221207170748-1.png]]
122 122  
123 123  
146 + [[image:image-20221207170748-2.png||height="345" width="634"]]
124 124  
148 +
125 125  == 1.8  Pin Definitions and Switch ==
126 126  
127 127  
... ... @@ -137,26 +137,24 @@
137 137  
138 138  The diagram below shows the working flow in the default firmware of NMDS200:
139 139  
140 -[[image:image-20221021110615-5.png]]
164 +[[image:image-20221021110615-5.png||height="996" width="492"]]
141 141  
142 142  
143 -== 2.2 ​ Configure NDS03A ==
167 +== 2.2 ​ Configure NMDS200 ==
144 144  
145 -=== 2.2.1 Test Requirement ===
146 146  
170 +To use NMDS200 in your city, make sure to meet below requirements:
147 147  
148 -To use NDS03A in your city, make sure to meet below requirements:
149 -
150 150  * Your local operator has already distributed an NB-IoT Network.
151 -* The local NB-IoT network used the band that NDS03A supports.
173 +* The local NB-IoT network used the band that NMDS200 supports.
152 152  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
153 153  
154 -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.
155 155  
156 -[[image:image-20221117142300-1.png]]
178 +[[image:image-20221209090938-1.png]]
157 157  
158 158  
159 -=== 2.2.2 Insert NB-IoT SIM card ===
181 +=== 2.2.1 Insert NB-IoT SIM card ===
160 160  
161 161  
162 162  Insert the NB-IoT Card get from your provider.
... ... @@ -166,10 +166,10 @@
166 166  [[image:image-20221021110745-6.png]] ​
167 167  
168 168  
169 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
191 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
170 170  
171 171  
172 -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.
173 173  
174 174  (% style="color:blue" %)**Connection:**
175 175  
... ... @@ -192,24 +192,23 @@
192 192  
193 193  * Flow Control: (% style="color:red" %)**None**
194 194  
195 -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**(%%).
196 196  
197 197  ​[[image:image-20221021110817-7.png]]
198 198  
199 -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.
200 200  
201 201  
202 202  (% 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]]
203 203  
204 204  
227 +=== 2.2.3 Use CoAP protocol to uplink data ===
205 205  
206 -=== 2.2.4 Use CoAP protocol to uplink data ===
207 207  
208 -
209 209  (% 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/]]
210 210  
211 211  
212 -(% style="color:blue" %)**Use below commands in NDS03A:**
233 +(% style="color:blue" %)**Use below commands in NMDS200:**
213 213  
214 214  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
215 215  
... ... @@ -219,15 +219,15 @@
219 219  
220 220  For parameter description, please refer to AT command set
221 221  
222 -[[image:image-20221021110948-8.png]]
243 +[[image:1670471530120-960.png||height="647" width="674"]]
223 223  
224 224  
225 -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.
226 226  
227 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
248 +[[image:1670405841875-916.png]] ​
228 228  
229 229  
230 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
251 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
231 231  
232 232  
233 233  (% style="color:blue" %)**AT Commands:**
... ... @@ -238,7 +238,7 @@
238 238  
239 239  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
240 240  
241 -​ [[image:image-20221021111025-10.png]]
262 +​ [[image:1670471559211-638.png]]
242 242  
243 243  
244 244  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -245,7 +245,7 @@
245 245  
246 246  ​
247 247  
248 -=== 2.2.6 Use MQTT protocol to uplink data ===
269 +=== 2.2.5 Use MQTT protocol to uplink data ===
249 249  
250 250  
251 251  (% style="color:blue" %)**AT Commands:**
... ... @@ -264,10 +264,10 @@
264 264  
265 265  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
266 266  
267 -​ [[image:image-20221118103445-7.png]]
288 +​ [[image:1670471584490-640.png]]
268 268  
269 269  
270 -[[image:image-20221118103453-8.png||height="608" width="841"]]
291 +[[image:1670405928926-116.png]]
271 271  
272 272  ​
273 273  
... ... @@ -274,7 +274,7 @@
274 274  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.
275 275  
276 276  
277 -=== 2.2.7 Use TCP protocol to uplink data ===
298 +=== 2.2.6 Use TCP protocol to uplink data ===
278 278  
279 279  
280 280  (% style="color:blue" %)**AT Commands:**
... ... @@ -283,18 +283,19 @@
283 283  
284 284  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
285 285  
286 -​ [[image:image-20221021111125-14.png]]
307 +​ ​​​​​​​[[image:1670471613823-833.png]]
287 287  
309 +
288 288  [[image:image-20221021111131-15.png]]
289 289  
290 290  ​
291 291  
292 -=== 2.2.8 Change Update Interval ===
314 +=== 2.2.7 Change Update Interval ===
293 293  
294 294  
295 295  User can use below command to change the (% style="color:blue" %)**uplink interval**.
296 296  
297 -* (% 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)
298 298  
299 299  (% style="color:red" %)**NOTE:**
300 300  
... ... @@ -304,70 +304,52 @@
304 304  == 2.3  Uplink Payload ==
305 305  
306 306  
307 -The uplink payload includes 26 bytes in total by default.
329 +The uplink payload includes 23 bytes in total by default.
308 308  
309 309  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.
310 310  
311 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
312 312  
313 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
314 -|=(% 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**
315 -|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
334 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %)
335 +|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:30px" %)**2**|(% style="width:30px" %)**2**|(% style="width:75px" %)**1**|(% style="width:30px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**
336 +|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) [[Distance 1>>||anchor="H2.4.5A0Distance"]] |(% style="width:93px" %) [[Distance 2>>||anchor="H2.4.5A0Distance"]]
316 316  
317 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
318 -|(% 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" style="background-color:#ffffcc; color:green; width:429px" %)
339 +|(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((
319 319  **1-32 group**
320 320  )))
321 -|(% 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" %)...
322 322  
323 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
344 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
324 324  
346 +[[image:1670406261143-723.png]]
325 325  
326 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
327 -|=(% 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**
328 -|=(% 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)
329 329  
330 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
331 -|(% 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**
332 -|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
349 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
333 333  
334 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
335 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
336 -**1-32 group**
337 -)))
338 -|(% 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" %)......
351 +**0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
339 339  
340 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
341 -
342 -[[image:image-20221117145932-2.png]]
343 -
344 -
345 -The payload is ASCII string, representative same HEX:
346 -
347 -**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__(%%)**
348 -
349 349  **where:**
350 350  
351 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
355 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
352 352  
353 353  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
354 354  
355 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
359 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
356 356  
357 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
361 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
358 358  
359 359  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
360 360  
361 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
365 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
362 362  
363 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
367 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
364 364  
365 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
369 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
366 366  
367 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
371 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
368 368  
369 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
370 370  
374 +
371 371  == 2.4  Payload Explanation and Sensor Interface ==
372 372  
373 373  === 2.4.1  Device ID ===
... ... @@ -389,13 +389,13 @@
389 389  
390 390  Specify the software version: 0x64=100, which means firmware version 1.00.
391 391  
392 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
396 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
393 393  
394 394  
395 395  === 2.4.3  Battery Info ===
396 396  
397 397  
398 -Check the battery voltage for NDS03A.
402 +Check the battery voltage for NMDS200.
399 399  
400 400  Ex1: 0x0B45 = 2885mV
401 401  
... ... @@ -407,51 +407,49 @@
407 407  
408 408  NB-IoT Network signal Strength.
409 409  
410 -**Ex1: 0x1d = 29**
414 +(% style="color:blue" %)**Ex1: 0x1d = 29**
411 411  
412 -**0**  -113dBm or less
416 +(% style="color:#037691" %)**0** (%%) -113dBm or less
413 413  
414 -**1**  -111dBm
418 +(% style="color:#037691" %)**1**  (%%) -111dBm
415 415  
416 -**2...30** -109dBm... -53dBm
420 +(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
417 417  
418 -**31**   -51dBm or greater
422 +(% style="color:#037691" %)**31** (%%) -51dBm or greater
419 419  
420 -**99**    Not known or not detectable
424 +(% style="color:#037691" %)**99** (%%) Not known or not detectable
421 421  
422 422  
423 -=== 2.4.5  Disalarm: (default: 0) ===
427 +=== 2.4.5  Distance ===
424 424  
425 425  
426 -(% style="color:blue" %)**If Disalarm = 1**(%%), NDS03A will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many open/close event, and platform only care about the total number of pulse.
430 +[[image:1670407401682-959.png]]
427 427  
428 -(% 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.
429 429  
430 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
433 +(% style="color:blue" %)**Object1 Distance:**
431 431  
435 +Distance between sensor probe to the first object. (unit: cm)
432 432  
433 -=== 2.4.6  Keep Status & Keep Time ===
437 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
434 434  
439 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
435 435  
436 -Shows the configure value of Alarm Base on Timeout Feature
437 437  
442 +(% style="color:blue" %)**Object2 Distance:**
438 438  
439 -=== 2.4.7  Timestamp ===
444 +Distance between sensor probe to the second object. (unit: cm)
440 440  
441 441  
442 -Timestamp : 0x6315537b =1662342011
447 +=== 2.4.6  Timestamp ===
443 443  
444 444  
445 -=== 2.4.8  Switch Dual Channel Mode ===
450 +Timestamp : 0x6315537b =1662342011
446 446  
447 447  
448 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
449 -
450 -
451 451  == 2.5  Downlink Payload ==
452 452  
453 453  
454 -By default, NDS03A prints the downlink payload to console port.
456 +By default, NMDS200 prints the downlink payload to console port.
455 455  
456 456  [[image:image-20221021111414-18.png]] ​
457 457  
... ... @@ -468,7 +468,7 @@
468 468  
469 469  * (% style="color:#037691" %)**Reset**
470 470  
471 -If payload = 0x04FF, it will reset the NDS03A
473 +If payload = 0x04FF, it will reset the NMDS200
472 472  
473 473  * (% style="color:#037691" %)**INTMOD**
474 474  
... ... @@ -478,112 +478,34 @@
478 478  == 2.6  ​LED Indicator ==
479 479  
480 480  
481 -The NDS03A has an internal LED which is to show the status of different states.
483 +The NMDS200 has an internal LED which is to show the status of different states.
482 482  
483 483  * When the device starts normally, the LED will light up for 1 second.
484 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
486 +* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
485 485  * For each uplink probe, LED will be on for 500ms.
486 486  
487 -== 2.7  Alarm Base on Timeout ==
488 488  
489 489  
490 -NDS03A can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are:
491 +== 2.7  Distance alarm function ==
491 491  
492 492  
493 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
494 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
494 494  
495 -Keep Status = 1: Monitor Close to Open event
496 +(% style="color:#037691" %)**Example 1:**
496 496  
497 -Keep Status = 0: Monitor Open to Close event
498 +AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
498 498  
500 +AT+ ALARM2 =min,max
499 499  
500 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
501 501  
502 -Range 0 ~~ 65535(0xFFFF) seconds.
503 +(% style="color:#037691" %)**Example 2:**
503 503  
504 -If keep time = 0, Disable Alarm Base on Timeout feature.
505 +AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
505 505  
506 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
507 507  
508 +== 2.8  Set the number of data to be uploaded and the recording time ==
508 508  
509 -(% style="color:blue" %)**AT Command to configure:**
510 510  
511 -(% style="color:blue" %)**PB14 PIN:**
512 -
513 -(% 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.
514 -
515 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
516 -
517 -
518 -(% style="color:blue" %)**PB15 PIN:**
519 -
520 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
521 -
522 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
523 -
524 -
525 -== 2.8  Set debug mode ==
526 -
527 -
528 -Feature: Enable or Disable debug mode
529 -
530 -(% style="color:blue" %)**AT Command: AT+DEBUG**
531 -
532 -[[image:image-20221021111629-21.png]]
533 -
534 -
535 -
536 -== 2.9  Clear Flash Record ==
537 -
538 -
539 -Feature: Clear flash storage for data log feature.
540 -
541 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
542 -
543 -[[image:image-20221021111527-19.png]]
544 -
545 -
546 -== 2.10  Count Mod ==
547 -
548 -
549 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
550 -
551 -[[image:image-20221118092935-1.png]]
552 -
553 -
554 -== 2.11  Interrupt Pin Channel Mod ==
555 -
556 -
557 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
558 -
559 -[[image:image-20221118093144-2.png]]
560 -
561 -
562 -== 2.12 TTRIG1/2 timeout status alarm ==
563 -
564 -
565 -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.
566 -
567 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
568 -
569 -[[image:image-20221118093512-3.png]]
570 -
571 -
572 -== 2.13  Select counting mode ==
573 -
574 -
575 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
576 -
577 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
578 -
579 -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.
580 -
581 -[[image:image-20221118093658-4.png]]
582 -
583 -
584 -== 2.14  Set the number of data to be uploaded and the recording time ==
585 -
586 -
587 587  (% style="color:blue" %)**AT Command:**
588 588  
589 589  (% 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)
... ... @@ -591,7 +591,7 @@
591 591  (% 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.
592 592  
593 593  
594 -== 2.15  Read or Clear cached data ==
518 +== 2.9  Read or Clear cached data ==
595 595  
596 596  
597 597  (% style="color:blue" %)**AT Command:**
... ... @@ -600,10 +600,10 @@
600 600  
601 601  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
602 602  
603 -[[image:image-20221118094227-5.png]]
527 +[[image:1670408172929-569.png]]
604 604  
605 605  
606 -== 2.16  ​Firmware Change Log ==
530 +== 2.10  ​Firmware Change Log ==
607 607  
608 608  
609 609  Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
... ... @@ -611,12 +611,12 @@
611 611  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
612 612  
613 613  
614 -== 2.17  ​Battery Analysis ==
538 +== 2.11  ​Battery Analysis ==
615 615  
616 -=== 2.17.1  ​Battery Type ===
540 +=== 2.11.1  ​Battery Type ===
617 617  
618 618  
619 -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.
543 +The NMDS200 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
620 620  
621 621  The battery is designed to last for several years depends on the actual use environment and update interval. 
622 622  
... ... @@ -631,7 +631,7 @@
631 631  [[image:image-20221021111911-26.png]] ​
632 632  
633 633  
634 -=== 2.17.2  Power consumption Analyze ===
558 +=== 2.11.2  Power consumption Analyze ===
635 635  
636 636  
637 637  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.
... ... @@ -653,16 +653,16 @@
653 653  [[image:1666596205057-567.png]] ​
654 654  
655 655  
656 -=== 2.17.3  ​Battery Note ===
580 +=== 2.11.3  ​Battery Note ===
657 657  
658 658  
659 659  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.
660 660  
661 661  
662 -=== 2.17.4  Replace the battery ===
586 +=== 2.11.4  Replace the battery ===
663 663  
664 664  
665 -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).
589 +The default battery pack of NMDS200 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
666 666  
667 667  
668 668  = 3. ​ Access NB-IoT Module =
... ... @@ -708,65 +708,59 @@
708 708  
709 709  AT+INTMOD            : Set the trigger interrupt mode
710 710  
711 -AT+5VT  : Set extend the time of 5V power  
635 +AT+5VT  : Set extend the time of 5V power  
712 712  
713 -AT+PRO  : Choose agreement
637 +AT+PRO  : Choose agreement
714 714  
715 -AT+RXDL  : Extend the sending and receiving time
639 +AT+RXDL  : Extend the sending and receiving time
716 716  
717 -AT+SERVADDR  : Server Address
641 +AT+SERVADDR  : Server Address
718 718  
719 -AT+TR      :  Get or Set record time
643 +AT+TR      :  Get or Set record time
720 720  
721 -AT+NOUD      : Get or Set the number of data to be uploaded
645 +AT+NOUD :  Get or Set the number of data to be uploaded
722 722  
723 723  AT+CDP     :  Read or Clear cached data
724 724  
725 -AT+ DEBUG   : Enable or Disable debug mode
649 +AT+DEBUG:  Enable or Disable debug mode
726 726  
727 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
651 +AT+ALARM1:  Get or Set alarm of distance1
728 728  
729 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
653 +AT+ALARM2:  Get or Set alarm of distance2
730 730  
731 -AT+COUNTMOD  :  Get or Set the count mode
655 +AT+GETSENSORVALUE :  Returns the current sensor measurement
732 732  
733 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
657 +AT+POWERIC :  Get or set the Power IC flag
734 734  
735 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
736 736  
737 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
738 -
739 -AT+ CLRC   :  Clear current door open count
740 -
741 -
742 742  (% style="color:blue" %)**COAP Management**      
743 743  
744 -AT+URI            : Resource parameters
662 +AT+URI :  Resource parameters
745 745  
746 746  
747 747  (% style="color:blue" %)**UDP Management**
748 748  
749 -AT+CFM          : Upload confirmation mode (only valid for UDP)
667 +AT+CFM :  Upload confirmation mode (only valid for UDP)
750 750  
751 751  
752 752  (% style="color:blue" %)**MQTT Management**
753 753  
754 -AT+CLIENT               : Get or Set MQTT client
672 +AT+CLIENT  : Get or Set MQTT client
755 755  
756 -AT+UNAME  : Get or Set MQTT Username
674 +AT+UNAME : Get or Set MQTT Username
757 757  
758 -AT+PWD                  : Get or Set MQTT password
676 +AT+PWD  :  Get or Set MQTT password
759 759  
760 -AT+PUBTOPIC  : Get or Set MQTT publish topic
678 +AT+PUBTOPIC :  Get or Set MQTT publish topic
761 761  
762 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
680 +AT+SUBTOPIC :  Get or Set MQTT subscription topic
763 763  
764 764  
765 765  (% style="color:blue" %)**Information**          
766 766  
767 -AT+FDR  : Factory Data Reset
685 +AT+FDR :  Factory Data Reset
768 768  
769 -AT+PWORD  : Serial Access Password
687 +AT+PWORD :  Serial Access Password
770 770  
771 771  
772 772  = ​5.  FAQ =
... ... @@ -778,7 +778,7 @@
778 778  
779 779  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]]
780 780  
781 -(% style="color:red" %)**Notice: **(% style="color:blue" %)**NDS03A** (%%)**and (% style="color:blue" %)LDS03A(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
699 +(% style="color:red" %)**Notice: **(% style="color:blue" %)**NMDS200** (%%)**and (% style="color:blue" %)LMDS200(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
782 782  
783 783  
784 784  = 6.  Trouble Shooting =
... ... @@ -798,7 +798,7 @@
798 798  = 7. ​ Order Info =
799 799  
800 800  
801 -Part Number**:** NDS03A
719 +Part Number:(% style="color:blue" %)** NMDS200**
802 802  
803 803  
804 804  = 8.  Packing Info =
... ... @@ -806,8 +806,10 @@
806 806  
807 807  (% style="color:blue" %)**Package Includes**:
808 808  
809 -* NDS03A Open/Close Door Sensor x 1
727 +* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
810 810  
729 +
730 +
811 811  = 9.  Support =
812 812  
813 813  
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
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

Applications

Navigation

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