Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 90.10 >
edited by Xiaoling
on 2023/05/25 18:07
To version < 76.1 >
edited by Xiaoling
on 2022/12/07 17:33
>
Change comment: Uploaded new attachment "image-20221207173300-4.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,28 +1,13 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg||height="572" width="572"]]
2 +[[image:LMDS200_10.jpg]]
3 3  
4 4  
5 -
6 -
7 -
8 -(% style="display:none" %) (%%)
9 -
10 -
11 -
12 -
13 -
14 14  **Table of Contents：**
15 15  
16 -{{toc/}}
17 17  
18 18  
19 19  
20 20  
21 -
22 -
23 -
24 -
25 -
26 26  = 1.  Introduction =
27 27  
28 28  == 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
... ... @@ -30,37 +30,25 @@
30 30  
31 31  (((
32 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.
33 -)))
34 34  
35 -(((
19 +
36 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.
37 -)))
38 38  
39 -(((
40 40  NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
41 -)))
42 42  
43 -(((
44 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.
45 -)))
46 46  
47 -(((
48 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.
49 -)))
50 50  
51 -(((
52 52  NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
53 -)))
54 54  
55 -(((
56 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)
57 -)))
58 58  
59 -(((
60 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.
61 61  )))
62 62  
63 63  
36 +
64 64  == ​1.2  Features ==
65 65  
66 66  
... ... @@ -79,13 +79,14 @@
79 79  * 8500mAh Battery for long-term use
80 80  
81 81  
55 +
82 82  == 1.3 Radar probe specification ==
83 83  
84 84  
85 85  * Measuring Method: FMCW
86 -* Frequency: 24.000 ~~ 24.500 GHz
60 +* Frequency: 24.000 24.500 GHz
87 87  * Measurement output power: 6dBm
88 -* Measure range: 0.5 ~~ 20m
62 +* Measure range: 0.5 20m
89 89  * Accuracy: ±0.1m
90 90  * Resolution: 0.01m
91 91  * Horizontal Angel: 78°
... ... @@ -92,6 +92,8 @@
92 92  * Vertical Angel: 23°
93 93  
94 94  
69 +
70 +
95 95  == 1.4  Storage Temperature ==
96 96  
97 97  
... ... @@ -98,9 +98,13 @@
98 98   -40°C to +85°C
99 99  
100 100  
77 +
78 +
79 +
101 101  == 1.5 ​ Applications ==
102 102  
103 103  
83 +
104 104  * Horizontal distance measurement
105 105  * Liquid level measurement
106 106  * Parking management system
... ... @@ -112,6 +112,7 @@
112 112  * Bottom water level monitoring
113 113  
114 114  
95 +
115 115  == 1.6  Specification ==
116 116  
117 117  
... ... @@ -130,6 +130,7 @@
130 130  * B28 @H-FDD: 700MHz
131 131  
132 132  
114 +
133 133  == 1.7  Installation ==
134 134  
135 135  
... ... @@ -136,12 +136,10 @@
136 136  Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
137 137  
138 138  
139 -[[image:image-20221207170748-1.png]]
121 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
140 140  
141 141  
142 - [[image:image-20221207170748-2.png||height="345" width="634"]]
143 143  
144 -
145 145  == 1.8  Pin Definitions and Switch ==
146 146  
147 147  
... ... @@ -157,24 +157,26 @@
157 157  
158 158  The diagram below shows the working flow in the default firmware of NMDS200:
159 159  
160 -[[image:image-20221021110615-5.png||height="996" width="492"]]
140 +[[image:image-20221021110615-5.png]]
161 161  
162 162  
163 -== 2.2 ​ Configure NMDS200 ==
143 +== 2.2 ​ Configure NDS03A ==
164 164  
145 +=== 2.2.1 Test Requirement ===
165 165  
166 -To use NMDS200 in your city, make sure to meet below requirements:
167 167  
148 +To use NDS03A in your city, make sure to meet below requirements:
149 +
168 168  * Your local operator has already distributed an NB-IoT Network.
169 -* The local NB-IoT network used the band that NMDS200 supports.
151 +* The local NB-IoT network used the band that NDS03A supports.
170 170  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
171 171  
172 -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.
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.
173 173  
174 -[[image:image-20221209090938-1.png]]
156 +[[image:image-20221117142300-1.png]]
175 175  
176 176  
177 -=== 2.2.1 Insert NB-IoT SIM card ===
159 +=== 2.2.2 Insert NB-IoT SIM card ===
178 178  
179 179  
180 180  Insert the NB-IoT Card get from your provider.
... ... @@ -184,10 +184,10 @@
184 184  [[image:image-20221021110745-6.png]] ​
185 185  
186 186  
187 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
169 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
188 188  
189 189  
190 -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.
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.
191 191  
192 192  (% style="color:blue" %)**Connection:**
193 193  
... ... @@ -210,23 +210,24 @@
210 210  
211 211  * Flow Control: (% style="color:red" %)**None**
212 212  
213 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
195 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
214 214  
215 215  ​[[image:image-20221021110817-7.png]]
216 216  
217 -NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
199 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
218 218  
219 219  
220 220  (% 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]]
221 221  
222 222  
223 -=== 2.2.3 Use CoAP protocol to uplink data ===
224 224  
206 +=== 2.2.4 Use CoAP protocol to uplink data ===
225 225  
208 +
226 226  (% 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/]]
227 227  
228 228  
229 -(% style="color:blue" %)**Use below commands in NMDS200:**
212 +(% style="color:blue" %)**Use below commands in NDS03A:**
230 230  
231 231  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
232 232  
... ... @@ -236,15 +236,15 @@
236 236  
237 237  For parameter description, please refer to AT command set
238 238  
239 -[[image:1670471530120-960.png||height="647" width="674"]]
222 +[[image:image-20221021110948-8.png]]
240 240  
241 241  
242 -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.
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.
243 243  
244 -[[image:1670405841875-916.png]] ​
227 +[[image:image-20221118103547-9.png||height="605" width="837"]] ​
245 245  
246 246  
247 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
230 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
248 248  
249 249  
250 250  (% style="color:blue" %)**AT Commands:**
... ... @@ -255,7 +255,7 @@
255 255  
256 256  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
257 257  
258 -​ [[image:1670471559211-638.png]]
241 +​ [[image:image-20221021111025-10.png]]
259 259  
260 260  
261 261  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -262,7 +262,7 @@
262 262  
263 263  ​
264 264  
265 -=== 2.2.5 Use MQTT protocol to uplink data ===
248 +=== 2.2.6 Use MQTT protocol to uplink data ===
266 266  
267 267  
268 268  (% style="color:blue" %)**AT Commands:**
... ... @@ -281,10 +281,10 @@
281 281  
282 282  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
283 283  
284 -​ [[image:1670471584490-640.png]]
267 +​ [[image:image-20221118103445-7.png]]
285 285  
286 286  
287 -[[image:1670405928926-116.png]]
270 +[[image:image-20221118103453-8.png||height="608" width="841"]]
288 288  
289 289  ​
290 290  
... ... @@ -291,7 +291,7 @@
291 291  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.
292 292  
293 293  
294 -=== 2.2.6 Use TCP protocol to uplink data ===
277 +=== 2.2.7 Use TCP protocol to uplink data ===
295 295  
296 296  
297 297  (% style="color:blue" %)**AT Commands:**
... ... @@ -300,19 +300,18 @@
300 300  
301 301  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
302 302  
303 -​ [[image:1670471613823-833.png]]
286 +​ [[image:image-20221021111125-14.png]]
304 304  
305 -
306 306  [[image:image-20221021111131-15.png]]
307 307  
308 308  ​
309 309  
310 -=== 2.2.7 Change Update Interval ===
292 +=== 2.2.8 Change Update Interval ===
311 311  
312 312  
313 313  User can use below command to change the (% style="color:blue" %)**uplink interval**.
314 314  
315 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
297 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
316 316  
317 317  (% style="color:red" %)**NOTE:**
318 318  
... ... @@ -322,48 +322,70 @@
322 322  == 2.3  Uplink Payload ==
323 323  
324 324  
325 -The uplink payload includes 23 bytes in total by default.
307 +The uplink payload includes 26 bytes in total by default.
326 326  
327 327  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.
328 328  
311 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
329 329  
330 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %)
331 -|=(% 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**
332 -|=(% 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"]]
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)
333 333  
334 -(% border="1" style="background-color:#ffffcc; color:green; width:429px" %)
335 -|(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((
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" %)(((
336 336  **1-32 group**
337 337  )))
338 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...
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" %)...
339 339  
340 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
323 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
341 341  
342 -[[image:1670406261143-723.png]]
343 343  
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)
344 344  
345 -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__(%%)**
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)
346 346  
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" %)......
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 +
347 347  **where:**
348 348  
349 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
351 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
350 350  
351 351  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
352 352  
353 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
355 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
354 354  
355 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
357 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
356 356  
357 357  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
358 358  
359 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
361 +* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
360 360  
361 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
363 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
362 362  
363 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
365 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
364 364  
365 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
367 +* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
366 366  
369 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
370 +
367 367  == 2.4  Payload Explanation and Sensor Interface ==
368 368  
369 369  === 2.4.1  Device ID ===
... ... @@ -385,13 +385,13 @@
385 385  
386 386  Specify the software version: 0x64=100, which means firmware version 1.00.
387 387  
388 -For example 0x00 64 : This device is NMDS200 with firmware version 1.0.0.
392 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
389 389  
390 390  
391 391  === 2.4.3  Battery Info ===
392 392  
393 393  
394 -Check the battery voltage for NMDS200.
398 +Check the battery voltage for NDS03A.
395 395  
396 396  Ex1: 0x0B45 = 2885mV
397 397  
... ... @@ -403,49 +403,51 @@
403 403  
404 404  NB-IoT Network signal Strength.
405 405  
406 -(% style="color:blue" %)**Ex1: 0x1d = 29**
410 +**Ex1: 0x1d = 29**
407 407  
408 -(% style="color:#037691" %)**0** (%%) -113dBm or less
412 +**0**  -113dBm or less
409 409  
410 -(% style="color:#037691" %)**1**  (%%) -111dBm
414 +**1**  -111dBm
411 411  
412 -(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
416 +**2...30** -109dBm... -53dBm
413 413  
414 -(% style="color:#037691" %)**31** (%%) -51dBm or greater
418 +**31**   -51dBm or greater
415 415  
416 -(% style="color:#037691" %)**99** (%%) Not known or not detectable
420 +**99**    Not known or not detectable
417 417  
418 418  
419 -=== 2.4.5  Distance ===
423 +=== 2.4.5  Disalarm: (default: 0) ===
420 420  
421 421  
422 -[[image:1670407401682-959.png]]
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.
423 423  
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.
424 424  
425 -(% style="color:blue" %)**Object1 Distance:**
430 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
426 426  
427 -Distance between sensor probe to the first object. (unit: cm)
428 428  
429 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
433 +=== 2.4.6  Keep Status & Keep Time ===
430 430  
431 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
432 432  
436 +Shows the configure value of Alarm Base on Timeout Feature
433 433  
434 -(% style="color:blue" %)**Object2 Distance:**
435 435  
436 -Distance between sensor probe to the second object. (unit: cm)
439 +=== 2.4.7  Timestamp ===
437 437  
438 438  
439 -=== 2.4.6  Timestamp ===
442 +Timestamp : 0x6315537b =1662342011
440 440  
441 441  
442 -Timestamp : 0x6315537b =1662342011
445 +=== 2.4.8  Switch Dual Channel Mode ===
443 443  
444 444  
448 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
449 +
450 +
445 445  == 2.5  Downlink Payload ==
446 446  
447 447  
448 -By default, NMDS200 prints the downlink payload to console port.
454 +By default, NDS03A prints the downlink payload to console port.
449 449  
450 450  [[image:image-20221021111414-18.png]] ​
451 451  
... ... @@ -462,7 +462,7 @@
462 462  
463 463  * (% style="color:#037691" %)**Reset**
464 464  
465 -If payload = 0x04FF, it will reset the NMDS200
471 +If payload = 0x04FF, it will reset the NDS03A
466 466  
467 467  * (% style="color:#037691" %)**INTMOD**
468 468  
... ... @@ -472,32 +472,112 @@
472 472  == 2.6  ​LED Indicator ==
473 473  
474 474  
475 -The NMDS200 has an internal LED which is to show the status of different states.
481 +The NDS03A has an internal LED which is to show the status of different states.
476 476  
477 477  * When the device starts normally, the LED will light up for 1 second.
478 -* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
484 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
479 479  * For each uplink probe, LED will be on for 500ms.
480 480  
481 -== 2.7  Distance alarm function ==
487 +== 2.7  Alarm Base on Timeout ==
482 482  
483 483  
484 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
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:
485 485  
486 -(% style="color:#037691" %)**Example 1:**
487 487  
488 -AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
493 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
489 489  
490 -AT+ ALARM2 =min,max
495 +Keep Status = 1: Monitor Close to Open event
491 491  
497 +Keep Status = 0: Monitor Open to Close event
492 492  
493 -(% style="color:#037691" %)**Example 2:**
494 494  
495 -AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
500 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
496 496  
502 +Range 0 ~~ 65535(0xFFFF) seconds.
497 497  
498 -== 2.8  Set the number of data to be uploaded and the recording time ==
504 +If keep time = 0, Disable Alarm Base on Timeout feature.
499 499  
506 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
500 500  
508 +
509 +(% style="color:blue" %)**AT Command to configure:**
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 +
501 501  (% style="color:blue" %)**AT Command:**
502 502  
503 503  (% 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)
... ... @@ -505,7 +505,7 @@
505 505  (% 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.
506 506  
507 507  
508 -== 2.9  Read or Clear cached data ==
594 +== 2.15  Read or Clear cached data ==
509 509  
510 510  
511 511  (% style="color:blue" %)**AT Command:**
... ... @@ -514,25 +514,71 @@
514 514  
515 515  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
516 516  
517 -[[image:1670408172929-569.png]]
603 +[[image:image-20221118094227-5.png]]
518 518  
519 519  
520 -== 2.10  ​Firmware Change Log ==
606 +== 2.16  ​Firmware Change Log ==
521 521  
522 522  
523 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]
609 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
524 524  
525 525  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
526 526  
527 527  
528 -== 2.11 Battery & Power Consumption ==
614 +== 2.17  ​Battery Analysis ==
529 529  
616 +=== 2.17.1  ​Battery Type ===
530 530  
531 -NMDS200 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
532 532  
533 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
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.
534 534  
621 +The battery is designed to last for several years depends on the actual use environment and update interval. 
535 535  
623 +The battery-related documents as below:
624 +
625 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
626 +
627 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
628 +
629 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
630 +
631 +[[image:image-20221021111911-26.png]] ​
632 +
633 +
634 +=== 2.17.2  Power consumption Analyze ===
635 +
636 +
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.
638 +
639 +Instruction to use as below:
640 +
641 +(% 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/]]
642 +
643 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
644 +
645 +* Product Model
646 +
647 +* Uplink Interval
648 +
649 +* Working Mode
650 +
651 +And the Life expectation in difference case will be shown on the right.
652 +
653 +[[image:1666596205057-567.png]] ​
654 +
655 +
656 +=== 2.17.3  ​Battery Note ===
657 +
658 +
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 +
661 +
662 +=== 2.17.4  Replace the battery ===
663 +
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).
666 +
667 +
536 536  = 3. ​ Access NB-IoT Module =
537 537  
538 538  
... ... @@ -576,59 +576,65 @@
576 576  
577 577  AT+INTMOD            : Set the trigger interrupt mode
578 578  
579 -AT+5VT  : Set extend the time of 5V power  
711 +AT+5VT  : Set extend the time of 5V power  
580 580  
581 -AT+PRO  : Choose agreement
713 +AT+PRO  : Choose agreement
582 582  
583 -AT+RXDL  : Extend the sending and receiving time
715 +AT+RXDL  : Extend the sending and receiving time
584 584  
585 -AT+SERVADDR  : Server Address
717 +AT+SERVADDR  : Server Address
586 586  
587 -AT+TR      :  Get or Set record time
719 +AT+TR      :  Get or Set record time
588 588  
589 -AT+NOUD :  Get or Set the number of data to be uploaded
721 +AT+NOUD      : Get or Set the number of data to be uploaded
590 590  
591 591  AT+CDP     :  Read or Clear cached data
592 592  
593 -AT+DEBUG:  Enable or Disable debug mode
725 +AT+ DEBUG   : Enable or Disable debug mode
594 594  
595 -AT+ALARM1:  Get or Set alarm of distance1
727 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
596 596  
597 -AT+ALARM2:  Get or Set alarm of distance2
729 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
598 598  
599 -AT+GETSENSORVALUE :  Returns the current sensor measurement
731 +AT+COUNTMOD  :  Get or Set the count mode
600 600  
601 -AT+POWERIC :  Get or set the Power IC flag
733 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
602 602  
735 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
603 603  
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 +
604 604  (% style="color:blue" %)**COAP Management**      
605 605  
606 -AT+URI :  Resource parameters
744 +AT+URI            : Resource parameters
607 607  
608 608  
609 609  (% style="color:blue" %)**UDP Management**
610 610  
611 -AT+CFM :  Upload confirmation mode (only valid for UDP)
749 +AT+CFM          : Upload confirmation mode (only valid for UDP)
612 612  
613 613  
614 614  (% style="color:blue" %)**MQTT Management**
615 615  
616 -AT+CLIENT  : Get or Set MQTT client
754 +AT+CLIENT               : Get or Set MQTT client
617 617  
618 -AT+UNAME : Get or Set MQTT Username
756 +AT+UNAME  : Get or Set MQTT Username
619 619  
620 -AT+PWD  :  Get or Set MQTT password
758 +AT+PWD                  : Get or Set MQTT password
621 621  
622 -AT+PUBTOPIC :  Get or Set MQTT publish topic
760 +AT+PUBTOPIC  : Get or Set MQTT publish topic
623 623  
624 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
762 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
625 625  
626 626  
627 627  (% style="color:blue" %)**Information**          
628 628  
629 -AT+FDR :  Factory Data Reset
767 +AT+FDR  : Factory Data Reset
630 630  
631 -AT+PWORD :  Serial Access Password
769 +AT+PWORD  : Serial Access Password
632 632  
633 633  
634 634  = ​5.  FAQ =
... ... @@ -640,7 +640,7 @@
640 640  
641 641  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]]
642 642  
643 -(% 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.**
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.**
644 644  
645 645  
646 646  = 6.  Trouble Shooting =
... ... @@ -657,16 +657,10 @@
657 657  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.
658 658  
659 659  
660 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
661 -
662 -
663 -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]]//**.
664 -
665 -
666 666  = 7. ​ Order Info =
667 667  
668 668  
669 -Part Number:(% style="color:blue" %)** NMDS200**
801 +Part Number**:** NDS03A
670 670  
671 671  
672 672  = 8.  Packing Info =
... ... @@ -674,9 +674,8 @@
674 674  
675 675  (% style="color:blue" %)**Package Includes**:
676 676  
677 -* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
809 +* NDS03A Open/Close Door Sensor x 1
678 678  
679 -
680 680  = 9.  Support =
681 681  
682 682  
1670405841875-916.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.0 KB
Content
1670406261143-723.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content
1670407401682-959.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -23.7 KB
Content
1670408172929-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -211.8 KB
Content
1670471530120-960.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -67.6 KB
Content
1670471559211-638.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -170.6 KB
Content
1670471584490-640.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.1 KB
Content
1670471613823-833.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.0 KB
Content
image-20221208090742-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.7 KB
Content
image-20221209090938-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -121.9 KB
Content
image-20221212171610-1.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -756.0 KB
Content

Applications

Navigation

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