Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 70.23 >
edited by Xiaoling
on 2022/11/21 10:58
To version < 83.2 >
edited by Xiaoling
on 2022/12/08 09:28
>
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,71 +1,44 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20221117105556-1.png]]
2 +[[image:LMDS200_10.jpg]]
3 3  
4 4  
5 -
6 -
7 -
8 -
9 -
10 10  **Table of Contents：**
11 11  
12 -{{toc/}}
13 13  
14 14  
15 15  
16 16  
17 -
18 18  = 1.  Introduction =
19 19  
20 -== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
13 +== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
21 21  
22 22  
23 23  (((
24 -The Dragino NDS03A is an (% style="color:blue" %)**Open/Close NB-IoT Door Sensor**(%%). It detects door (% style="color:blue" %)**open/close status**(%%) and (% style="color:blue" %)**uplinks**(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server.
25 -)))
17 +The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor.
26 26  
27 -(((
28 -The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically.
29 -)))
19 +The NMDS200 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
30 30  
31 -(((
32 -NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT.
33 -)))
21 +NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
34 34  
35 -(((
36 -NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time.
37 -)))
23 +NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range.
38 38  
39 -(((
40 -NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
41 -)))
42 -
43 -(((
44 44  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.
45 -)))
46 46  
47 -(((
48 -NDS03A supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
49 -)))
27 +NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
50 50  
51 -(((
52 -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)
53 -)))
29 +NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
54 54  
55 -(((
56 -To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection.
31 +To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection.
57 57  )))
58 58  
59 59  
60 -
61 61  == ​1.2  Features ==
62 62  
63 63  
64 64  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
65 -* Open/Close detect
66 -* Open/Close statistics
39 +* Short uplink interval for Distance Alarm
67 67  * Monitor Battery Level
68 -* connect two door sensors
41 +* Microwave Radar for distance detection
69 69  * Datalog feature
70 70  * Uplink periodically
71 71  * Downlink to change configure
... ... @@ -76,33 +76,37 @@
76 76  * Micro SIM card slot for NB-IoT SIM
77 77  * 8500mAh Battery for long-term use
78 78  
52 +== 1.3 Radar probe specification ==
79 79  
80 -== 1.3  Storage & Operation ==
81 81  
55 +* Measuring Method: FMCW
56 +* Frequency: 24.000 24.500 GHz
57 +* Measurement output power: 6dBm
58 +* Measure range: 0.5 20m
59 +* Accuracy: ±0.1m
60 +* Resolution: 0.01m
61 +* Horizontal Angel: 78°
62 +* Vertical Angel: 23°
82 82  
83 -Temperature -40°C to +85°C
64 +== 1.4  Storage Temperature ==
84 84  
85 85  
86 -== 1.4  Mechanical ==
67 + -40°C to +85°C
87 87  
88 88  
89 -[[image:image-20221117114937-4.png]]
90 -
91 -
92 -[[image:image-20221117114949-5.png]]
93 -
94 -
95 -[[image:image-20221117115010-6.png]]
96 -
97 -
98 -
99 99  == 1.5 ​ Applications ==
100 100  
101 101  
102 -[[image:image-20221117114842-3.png]]
73 +* Horizontal distance measurement
74 +* Liquid level measurement
75 +* Parking management system
76 +* Object proximity and presence detection
77 +* Intelligent trash can management system
78 +* Robot obstacle avoidance
79 +* Automatic control
80 +* Sewer
81 +* Bottom water level monitoring
103 103  
104 -
105 -
106 106  == 1.6  Specification ==
107 107  
108 108  
... ... @@ -109,97 +109,60 @@
109 109  (% style="color:blue" %)**Common DC Characteristics:**
110 110  
111 111  * Supply Voltage: 2.1v ~~ 3.6v
112 -* Operating Temperature: -40 ~~ 85°C
89 +* Operating Temperature: 0 ~~ 70°C
113 113  
114 114  (% style="color:blue" %)**NB-IoT Spec:**
115 115  
116 -* - B1 @H-FDD: 2100MHz
117 -* - B3 @H-FDD: 1800MHz
118 -* - B8 @H-FDD: 900MHz
119 -* - B5 @H-FDD: 850MHz
120 -* - B20 @H-FDD: 800MHz
121 -* - B28 @H-FDD: 700MHz
93 +* B1 @H-FDD: 2100MHz
94 +* B3 @H-FDD: 1800MHz
95 +* B8 @H-FDD: 900MHz
96 +* B5 @H-FDD: 850MHz
97 +* B20 @H-FDD: 800MHz
98 +* B28 @H-FDD: 700MHz
122 122  
100 +== 1.7  Installation ==
123 123  
124 -== 1.7  Pin Definitions and Switch ==
125 125  
103 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
126 126  
127 -[[image:image-20221021110429-4.png]]
128 128  
106 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
129 129  
130 -=== 1.7.1  Pin Definition ===
131 131  
132 132  
133 -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]]
110 +== 1.8  Pin Definitions and Switch ==
134 134  
135 135  
136 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
113 +[[image:1670404362039-351.png]]
137 137  
138 138  
139 -Power on Device when putting this jumper.
116 += 2.  Use NMDS200 to communicate with IoT Server =
140 140  
141 -
142 -=== 1.7.3  BOOT MODE / SW1 ===
143 -
144 -
145 -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.
146 -
147 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
148 -
149 -
150 -=== 1.7.4  Reset Button ===
151 -
152 -
153 -Press to reboot the device.
154 -
155 -
156 -=== 1.7.5  LED ===
157 -
158 -
159 -The LED will blink when :
160 -
161 -1.  Boot the device in flash mode
162 -
163 -2.  Send an uplink packet
164 -
165 -
166 -== 1.8  Magnet Distance ==
167 -
168 -
169 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
170 -
171 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
172 -
173 -
174 -= 2.  Use NDS03A to communicate with IoT Server =
175 -
176 176  == 2.1  How it works ==
177 177  
178 178  
179 -In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.
121 +The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
180 180  
181 -The diagram below shows the working flow in the default firmware of NDS03A:
123 +The diagram below shows the working flow in the default firmware of NMDS200:
182 182  
183 183  [[image:image-20221021110615-5.png]]
184 184  
185 185  
186 -== 2.2 ​ Configure NDS03A ==
128 +== 2.2 ​ Configure NMDS200 ==
187 187  
188 -=== 2.2.1 Test Requirement ===
189 189  
131 +To use NMDS200 in your city, make sure to meet below requirements:
190 190  
191 -To use NDS03A in your city, make sure to meet below requirements:
192 -
193 193  * Your local operator has already distributed an NB-IoT Network.
194 -* The local NB-IoT network used the band that NDS03A supports.
134 +* The local NB-IoT network used the band that NMDS200 supports.
195 195  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
196 196  
197 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDS03A will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
137 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NMDS200 will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
198 198  
199 -[[image:image-20221117142300-1.png]]
139 +[[image:image-20221208090742-1.png]]
200 200  
201 201  
202 -=== 2.2.2 Insert NB-IoT SIM card ===
142 +=== 2.2.1 Insert NB-IoT SIM card ===
203 203  
204 204  
205 205  Insert the NB-IoT Card get from your provider.
... ... @@ -209,10 +209,10 @@
209 209  [[image:image-20221021110745-6.png]] ​
210 210  
211 211  
212 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
152 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
213 213  
214 214  
215 -User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
155 +User need to configure NMDS200 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NMDS200 support AT Commands, user can use a USB to TTL adapter to connect to NMDS200 and use AT Commands to configure it, as below.
216 216  
217 217  (% style="color:blue" %)**Connection:**
218 218  
... ... @@ -235,11 +235,11 @@
235 235  
236 236  * Flow Control: (% style="color:red" %)**None**
237 237  
238 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
178 +Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
239 239  
240 240  ​[[image:image-20221021110817-7.png]]
241 241  
242 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
182 +NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
243 243  
244 244  
245 245  (% 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]]
... ... @@ -246,13 +246,13 @@
246 246  
247 247  
248 248  
249 -=== 2.2.4 Use CoAP protocol to uplink data ===
189 +=== 2.2.3 Use CoAP protocol to uplink data ===
250 250  
251 251  
252 252  (% 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/]]
253 253  
254 254  
255 -(% style="color:blue" %)**Use below commands in NDS03A:**
195 +(% style="color:blue" %)**Use below commands in NMDS200:**
256 256  
257 257  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
258 258  
... ... @@ -265,12 +265,12 @@
265 265  [[image:image-20221021110948-8.png]]
266 266  
267 267  
268 -After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
208 +After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server.
269 269  
270 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
210 +[[image:1670405841875-916.png]] ​
271 271  
272 272  
273 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
213 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
274 274  
275 275  
276 276  (% style="color:blue" %)**AT Commands:**
... ... @@ -288,7 +288,7 @@
288 288  
289 289  ​
290 290  
291 -=== 2.2.6 Use MQTT protocol to uplink data ===
231 +=== 2.2.5 Use MQTT protocol to uplink data ===
292 292  
293 293  
294 294  (% style="color:blue" %)**AT Commands:**
... ... @@ -310,7 +310,7 @@
310 310  ​ [[image:image-20221118103445-7.png]]
311 311  
312 312  
313 -[[image:image-20221118103453-8.png||height="608" width="841"]]
253 +[[image:1670405928926-116.png]]
314 314  
315 315  ​
316 316  
... ... @@ -317,7 +317,7 @@
317 317  MQTT protocol has a much higher power consumption compare with UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
318 318  
319 319  
320 -=== 2.2.7 Use TCP protocol to uplink data ===
260 +=== 2.2.6 Use TCP protocol to uplink data ===
321 321  
322 322  
323 323  (% style="color:blue" %)**AT Commands:**
... ... @@ -326,18 +326,19 @@
326 326  
327 327  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
328 328  
329 -​ [[image:image-20221021111125-14.png]]
269 +​ [[image:1670406036256-101.png||height="676" width="713"]]
330 330  
271 +
331 331  [[image:image-20221021111131-15.png]]
332 332  
333 333  ​
334 334  
335 -=== 2.2.8 Change Update Interval ===
276 +=== 2.2.7 Change Update Interval ===
336 336  
337 337  
338 338  User can use below command to change the (% style="color:blue" %)**uplink interval**.
339 339  
340 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
281 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
341 341  
342 342  (% style="color:red" %)**NOTE:**
343 343  
... ... @@ -347,70 +347,50 @@
347 347  == 2.3  Uplink Payload ==
348 348  
349 349  
350 -The uplink payload includes 26 bytes in total by default.
291 +The uplink payload includes 23 bytes in total by default.
351 351  
352 352  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.
353 353  
354 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
355 355  
356 356  (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
357 -|=(% 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**
358 -|=(% 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)
297 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:90px" %)**2**|(% style="width:100px" %)**2**
298 +|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) Distance 1 |(% style="width:93px" %) Distance  2
359 359  
360 360  (% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
361 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
301 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
362 362  **1-32 group**
363 363  )))
364 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
304 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
365 365  
366 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
306 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
367 367  
308 +[[image:1670406261143-723.png]]
368 368  
369 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
370 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:45px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:60px" %)**1**|(% style="width:60px" %)**1**|(% style="width:87px" %)**3**|(% style="width:80px" %)**3**
371 -|=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
372 372  
373 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
374 -|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:75px" %)**1**|(% style="width:75px" %)**3**
375 -|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
311 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
376 376  
377 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
378 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
379 -**1-32 group**
380 -)))
381 -|(% style="width:102px" %)last open time(pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:100px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
313 +**0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
382 382  
383 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
384 -
385 -[[image:image-20221117145932-2.png]]
386 -
387 -
388 -The payload is ASCII string, representative same HEX:
389 -
390 -**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)**
391 -
392 392  **where:**
393 393  
394 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
317 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
395 395  
396 396  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
397 397  
398 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
321 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
399 399  
400 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
323 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
401 401  
402 402  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
403 403  
404 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
327 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
405 405  
406 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
329 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
407 407  
408 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
331 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
409 409  
410 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
333 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
411 411  
412 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
413 -
414 414  == 2.4  Payload Explanation and Sensor Interface ==
415 415  
416 416  === 2.4.1  Device ID ===
... ... @@ -432,13 +432,13 @@
432 432  
433 433  Specify the software version: 0x64=100, which means firmware version 1.00.
434 434  
435 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
356 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
436 436  
437 437  
438 438  === 2.4.3  Battery Info ===
439 439  
440 440  
441 -Check the battery voltage for NDS03A.
362 +Check the battery voltage for NMDS200.
442 442  
443 443  Ex1: 0x0B45 = 2885mV
444 444  
... ... @@ -463,38 +463,36 @@
463 463  **99**    Not known or not detectable
464 464  
465 465  
466 -=== 2.4.5  Disalarm: (default: 0) ===
387 +=== 2.4.5  Distance ===
467 467  
468 468  
469 -(% 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.
390 +[[image:1670407401682-959.png]]
470 470  
471 -(% 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.
472 472  
473 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
393 +(% style="color:blue" %)**Object1 Distance:**
474 474  
395 +Distance between sensor probe to the first object. (unit: cm)
475 475  
476 -=== 2.4.6  Keep Status & Keep Time ===
397 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
477 477  
399 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
478 478  
479 -Shows the configure value of Alarm Base on Timeout Feature
480 480  
402 +(% style="color:blue" %)**Object2 Distance:**
481 481  
482 -=== 2.4.7  Timestamp ===
404 +Distance between sensor probe to the second object. (unit: cm)
483 483  
484 484  
485 -Timestamp : 0x6315537b =1662342011
407 +=== 2.4.6  Timestamp ===
486 486  
487 487  
488 -=== 2.4.8  Switch Dual Channel Mode ===
410 +Timestamp : 0x6315537b =1662342011
489 489  
490 490  
491 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
492 -
493 -
494 494  == 2.5  Downlink Payload ==
495 495  
496 496  
497 -By default, NDS03A prints the downlink payload to console port.
416 +By default, NMDS200 prints the downlink payload to console port.
498 498  
499 499  [[image:image-20221021111414-18.png]] ​
500 500  
... ... @@ -511,7 +511,7 @@
511 511  
512 512  * (% style="color:#037691" %)**Reset**
513 513  
514 -If payload = 0x04FF, it will reset the NDS03A
433 +If payload = 0x04FF, it will reset the NMDS200
515 515  
516 516  * (% style="color:#037691" %)**INTMOD**
517 517  
... ... @@ -521,112 +521,37 @@
521 521  == 2.6  ​LED Indicator ==
522 522  
523 523  
524 -The NDS03A has an internal LED which is to show the status of different states.
443 +The NMDS200 has an internal LED which is to show the status of different states.
525 525  
526 526  * When the device starts normally, the LED will light up for 1 second.
527 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
446 +* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
528 528  * For each uplink probe, LED will be on for 500ms.
529 529  
530 -== 2.7  Alarm Base on Timeout ==
531 531  
532 532  
533 -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:
534 534  
452 +== 2.7  Distance alarm function ==
535 535  
536 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
537 537  
538 -Keep Status = 1: Monitor Close to Open event
455 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
539 539  
540 -Keep Status = 0: Monitor Open to Close event
457 +**(% style="color:blue" %)Example 1:**
541 541  
459 +AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
542 542  
543 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
461 +AT+ ALARM2 =min,max
544 544  
545 -Range 0 ~~ 65535(0xFFFF) seconds.
546 546  
547 -If keep time = 0, Disable Alarm Base on Timeout feature.
464 +**(% style="color:blue" %)Example 2:**
548 548  
549 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
466 +AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
550 550  
551 551  
552 -(% style="color:blue" %)**AT Command to configure:**
553 553  
554 -(% style="color:blue" %)**PB14 PIN:**
555 555  
556 -(% 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.
471 +== 2.8  Set the number of data to be uploaded and the recording time ==
557 557  
558 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
559 559  
560 -
561 -(% style="color:blue" %)**PB15 PIN:**
562 -
563 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
564 -
565 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
566 -
567 -
568 -== 2.8  Set debug mode ==
569 -
570 -
571 -Feature: Enable or Disable debug mode
572 -
573 -(% style="color:blue" %)**AT Command: AT+DEBUG**
574 -
575 -[[image:image-20221021111629-21.png]]
576 -
577 -
578 -
579 -== 2.9  Clear Flash Record ==
580 -
581 -
582 -Feature: Clear flash storage for data log feature.
583 -
584 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
585 -
586 -[[image:image-20221021111527-19.png]]
587 -
588 -
589 -== 2.10  Count Mod ==
590 -
591 -
592 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
593 -
594 -[[image:image-20221118092935-1.png]]
595 -
596 -
597 -== 2.11  Interrupt Pin Channel Mod ==
598 -
599 -
600 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
601 -
602 -[[image:image-20221118093144-2.png]]
603 -
604 -
605 -== 2.12 TTRIG1/2 timeout status alarm ==
606 -
607 -
608 -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.
609 -
610 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
611 -
612 -[[image:image-20221118093512-3.png]]
613 -
614 -
615 -== 2.13  Select counting mode ==
616 -
617 -
618 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
619 -
620 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
621 -
622 -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.
623 -
624 -[[image:image-20221118093658-4.png]]
625 -
626 -
627 -== 2.14  Set the number of data to be uploaded and the recording time ==
628 -
629 -
630 630  (% style="color:blue" %)**AT Command:**
631 631  
632 632  (% 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)
... ... @@ -634,7 +634,7 @@
634 634  (% 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.
635 635  
636 636  
637 -== 2.15  Read or Clear cached data ==
481 +== 2.9  Read or Clear cached data ==
638 638  
639 639  
640 640  (% style="color:blue" %)**AT Command:**
... ... @@ -643,10 +643,10 @@
643 643  
644 644  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
645 645  
646 -[[image:image-20221118094227-5.png]]
490 +[[image:1670408172929-569.png]]
647 647  
648 648  
649 -== 2.16  ​Firmware Change Log ==
493 +== 2.10  ​Firmware Change Log ==
650 650  
651 651  
652 652  Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
... ... @@ -654,12 +654,12 @@
654 654  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
655 655  
656 656  
657 -== 2.17  ​Battery Analysis ==
501 +== 2.11  ​Battery Analysis ==
658 658  
659 -=== 2.17.1  ​Battery Type ===
503 +=== 2.11.1  ​Battery Type ===
660 660  
661 661  
662 -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.
506 +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.
663 663  
664 664  The battery is designed to last for several years depends on the actual use environment and update interval. 
665 665  
... ... @@ -674,7 +674,7 @@
674 674  [[image:image-20221021111911-26.png]] ​
675 675  
676 676  
677 -=== 2.17.2  Power consumption Analyze ===
521 +=== 2.11.2  Power consumption Analyze ===
678 678  
679 679  
680 680  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.
... ... @@ -696,16 +696,16 @@
696 696  [[image:1666596205057-567.png]] ​
697 697  
698 698  
699 -=== 2.17.3  ​Battery Note ===
543 +=== 2.11.3  ​Battery Note ===
700 700  
701 701  
702 702  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.
703 703  
704 704  
705 -=== 2.17.4  Replace the battery ===
549 +=== 2.11.4  Replace the battery ===
706 706  
707 707  
708 -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).
552 +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).
709 709  
710 710  
711 711  = 3. ​ Access NB-IoT Module =
... ... @@ -759,57 +759,51 @@
759 759  
760 760  AT+SERVADDR  : Server Address
761 761  
762 -AT+TR      :  Get or Set record time
606 +AT+TR      :  Get or Set record time
763 763  
764 -AT+NOUD      : Get or Set the number of data to be uploaded
608 +AT+NOUD :  Get or Set the number of data to be uploaded
765 765  
766 766  AT+CDP     :  Read or Clear cached data
767 767  
768 -AT+ DEBUG   : Enable or Disable debug mode
612 +AT+DEBUG:  Enable or Disable debug mode
769 769  
770 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
614 +AT+ALARM1:  Get or Set alarm of distance1
771 771  
772 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
616 +AT+ALARM2:  Get or Set alarm of distance2
773 773  
774 -AT+COUNTMOD  :  Get or Set the count mode
618 +AT+GETSENSORVALUE :  Returns the current sensor measurement
775 775  
776 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
620 +AT+POWERIC :  Get or set the Power IC flag
777 777  
778 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
779 779  
780 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
781 -
782 -AT+ CLRC   :  Clear current door open count
783 -
784 -
785 785  (% style="color:blue" %)**COAP Management**      
786 786  
787 -AT+URI            : Resource parameters
625 +AT+URI :  Resource parameters
788 788  
789 789  
790 790  (% style="color:blue" %)**UDP Management**
791 791  
792 -AT+CFM          : Upload confirmation mode (only valid for UDP)
630 +AT+CFM :  Upload confirmation mode (only valid for UDP)
793 793  
794 794  
795 795  (% style="color:blue" %)**MQTT Management**
796 796  
797 -AT+CLIENT               : Get or Set MQTT client
635 +AT+CLIENT  : Get or Set MQTT client
798 798  
799 -AT+UNAME  : Get or Set MQTT Username
637 +AT+UNAME : Get or Set MQTT Username
800 800  
801 -AT+PWD                  : Get or Set MQTT password
639 +AT+PWD  :  Get or Set MQTT password
802 802  
803 -AT+PUBTOPIC  : Get or Set MQTT publish topic
641 +AT+PUBTOPIC :  Get or Set MQTT publish topic
804 804  
805 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
643 +AT+SUBTOPIC :  Get or Set MQTT subscription topic
806 806  
807 807  
808 808  (% style="color:blue" %)**Information**          
809 809  
810 -AT+FDR  : Factory Data Reset
648 +AT+FDR :  Factory Data Reset
811 811  
812 -AT+PWORD  : Serial Access Password
650 +AT+PWORD :  Serial Access Password
813 813  
814 814  
815 815  = ​5.  FAQ =
... ... @@ -821,7 +821,7 @@
821 821  
822 822  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]]
823 823  
824 -(% 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.**
662 +(% 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.**
825 825  
826 826  
827 827  = 6.  Trouble Shooting =
... ... @@ -841,7 +841,7 @@
841 841  = 7. ​ Order Info =
842 842  
843 843  
844 -Part Number**:** NDS03A
682 +Part Number:**(% style="color:blue" %) NMDS200**
845 845  
846 846  
847 847  = 8.  Packing Info =
... ... @@ -849,9 +849,8 @@
849 849  
850 850  (% style="color:blue" %)**Package Includes**:
851 851  
852 -* NDS03A Open/Close Door Sensor x 1
690 +* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
853 853  
854 -
855 855  = 9.  Support =
856 856  
857 857  
1670404362039-351.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +492.6 KB
Content
1670405841875-916.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +181.0 KB
Content
1670406261143-723.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.9 KB
Content
1670407401682-959.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +23.7 KB
Content
1670408172929-569.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +211.8 KB
Content
LMDS200_10.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
image-20221207170748-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.1 KB
Content
image-20221207170748-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +29.9 KB
Content
image-20221207173200-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.7 KB
Content
image-20221207173300-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.0 KB
Content
image-20221208090742-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +79.7 KB
Content

Applications

Navigation

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