Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 70.24 >
edited by Xiaoling
on 2022/11/21 11:00
To version < 81.3 >
edited by Xiaoling
on 2022/12/07 18:09
>
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,59 +1,35 @@
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 -)))
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 -)))
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.
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 -)))
22 +NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
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 -)))
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.
42 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 -)))
28 +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 -)))
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)
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.
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.
57 57  )))
58 58  
59 59  
... ... @@ -62,10 +62,9 @@
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
41 +* Short uplink interval for Distance Alarm
67 67  * Monitor Battery Level
68 -* connect two door sensors
43 +* Microwave Radar for distance detection
69 69  * Datalog feature
70 70  * Uplink periodically
71 71  * Downlink to change configure
... ... @@ -76,34 +76,42 @@
76 76  * Micro SIM card slot for NB-IoT SIM
77 77  * 8500mAh Battery for long-term use
78 78  
54 +== 1.3 Radar probe specification ==
79 79  
80 80  
81 -== 1.3  Storage & Operation ==
57 +* Measuring Method: FMCW
58 +* Frequency: 24.000 24.500 GHz
59 +* Measurement output power: 6dBm
60 +* Measure range: 0.5 20m
61 +* Accuracy: ±0.1m
62 +* Resolution: 0.01m
63 +* Horizontal Angel: 78°
64 +* Vertical Angel: 23°
82 82  
83 83  
84 -Temperature -40°C to +85°C
67 +== 1.4  Storage Temperature ==
85 85  
86 86  
87 -== 1.4  Mechanical ==
70 + -40°C to +85°C
88 88  
89 89  
90 -[[image:image-20221117114937-4.png]]
91 91  
92 92  
93 -[[image:image-20221117114949-5.png]]
94 94  
95 -
96 -[[image:image-20221117115010-6.png]]
97 -
98 -
99 -
100 100  == 1.5 ​ Applications ==
101 101  
102 102  
103 -[[image:image-20221117114842-3.png]]
104 104  
80 +* Horizontal distance measurement
81 +* Liquid level measurement
82 +* Parking management system
83 +* Object proximity and presence detection
84 +* Intelligent trash can management system
85 +* Robot obstacle avoidance
86 +* Automatic control
87 +* Sewer
88 +* Bottom water level monitoring
105 105  
106 -
107 107  == 1.6  Specification ==
108 108  
109 109  
... ... @@ -110,7 +110,7 @@
110 110  (% style="color:blue" %)**Common DC Characteristics:**
111 111  
112 112  * Supply Voltage: 2.1v ~~ 3.6v
113 -* Operating Temperature: -40 ~~ 85°C
96 +* Operating Temperature: 0 ~~ 70°C
114 114  
115 115  (% style="color:blue" %)**NB-IoT Spec:**
116 116  
... ... @@ -121,87 +121,49 @@
121 121  * B20 @H-FDD: 800MHz
122 122  * B28 @H-FDD: 700MHz
123 123  
107 +== 1.7  Installation ==
124 124  
125 125  
126 -== 1.7  Pin Definitions and Switch ==
110 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
127 127  
128 128  
129 -[[image:image-20221021110429-4.png]]
113 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
130 130  
131 131  
132 -=== 1.7.1  Pin Definition ===
133 133  
117 +== 1.8  Pin Definitions and Switch ==
134 134  
135 -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]]
136 136  
120 +[[image:1670404362039-351.png]]
137 137  
138 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
139 139  
123 += 2.  Use NMDS200 to communicate with IoT Server =
140 140  
141 -Power on Device when putting this jumper.
142 -
143 -
144 -=== 1.7.3  BOOT MODE / SW1 ===
145 -
146 -
147 -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.
148 -
149 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
150 -
151 -
152 -=== 1.7.4  Reset Button ===
153 -
154 -
155 -Press to reboot the device.
156 -
157 -
158 -=== 1.7.5  LED ===
159 -
160 -
161 -The LED will blink when :
162 -
163 -1.  Boot the device in flash mode
164 -
165 -2.  Send an uplink packet
166 -
167 -
168 -== 1.8  Magnet Distance ==
169 -
170 -
171 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
172 -
173 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
174 -
175 -
176 -= 2.  Use NDS03A to communicate with IoT Server =
177 -
178 178  == 2.1  How it works ==
179 179  
180 180  
181 -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.
128 +The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
182 182  
183 -The diagram below shows the working flow in the default firmware of NDS03A:
130 +The diagram below shows the working flow in the default firmware of NMDS200:
184 184  
185 185  [[image:image-20221021110615-5.png]]
186 186  
187 187  
188 -== 2.2 ​ Configure NDS03A ==
135 +== 2.2 ​ Configure NMDS200 ==
189 189  
190 -=== 2.2.1 Test Requirement ===
191 191  
138 +To use NMDS200 in your city, make sure to meet below requirements:
192 192  
193 -To use NDS03A in your city, make sure to meet below requirements:
194 -
195 195  * Your local operator has already distributed an NB-IoT Network.
196 -* The local NB-IoT network used the band that NDS03A supports.
141 +* The local NB-IoT network used the band that NMDS200 supports.
197 197  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
198 198  
199 -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.
144 +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.
200 200  
201 -[[image:image-20221117142300-1.png]]
146 +[[image:image-20221207173300-4.png]]
202 202  
203 203  
204 -=== 2.2.2 Insert NB-IoT SIM card ===
149 +=== 2.2.1 Insert NB-IoT SIM card ===
205 205  
206 206  
207 207  Insert the NB-IoT Card get from your provider.
... ... @@ -211,10 +211,10 @@
211 211  [[image:image-20221021110745-6.png]] ​
212 212  
213 213  
214 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
159 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
215 215  
216 216  
217 -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.
162 +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.
218 218  
219 219  (% style="color:blue" %)**Connection:**
220 220  
... ... @@ -237,11 +237,11 @@
237 237  
238 238  * Flow Control: (% style="color:red" %)**None**
239 239  
240 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
185 +Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
241 241  
242 242  ​[[image:image-20221021110817-7.png]]
243 243  
244 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
189 +NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
245 245  
246 246  
247 247  (% 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]]
... ... @@ -248,7 +248,7 @@
248 248  
249 249  
250 250  
251 -=== 2.2.4 Use CoAP protocol to uplink data ===
196 +=== 2.2.3 Use CoAP protocol to uplink data ===
252 252  
253 253  
254 254  (% 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/]]
... ... @@ -267,12 +267,12 @@
267 267  [[image:image-20221021110948-8.png]]
268 268  
269 269  
270 -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.
215 +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.
271 271  
272 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
217 +[[image:1670405841875-916.png]] ​
273 273  
274 274  
275 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
220 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
276 276  
277 277  
278 278  (% style="color:blue" %)**AT Commands:**
... ... @@ -290,7 +290,7 @@
290 290  
291 291  ​
292 292  
293 -=== 2.2.6 Use MQTT protocol to uplink data ===
238 +=== 2.2.5 Use MQTT protocol to uplink data ===
294 294  
295 295  
296 296  (% style="color:blue" %)**AT Commands:**
... ... @@ -312,7 +312,7 @@
312 312  ​ [[image:image-20221118103445-7.png]]
313 313  
314 314  
315 -[[image:image-20221118103453-8.png||height="608" width="841"]]
260 +[[image:1670405928926-116.png]]
316 316  
317 317  ​
318 318  
... ... @@ -319,7 +319,7 @@
319 319  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.
320 320  
321 321  
322 -=== 2.2.7 Use TCP protocol to uplink data ===
267 +=== 2.2.6 Use TCP protocol to uplink data ===
323 323  
324 324  
325 325  (% style="color:blue" %)**AT Commands:**
... ... @@ -328,18 +328,19 @@
328 328  
329 329  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
330 330  
331 -​ [[image:image-20221021111125-14.png]]
276 +​ [[image:1670406036256-101.png||height="676" width="713"]]
332 332  
278 +
333 333  [[image:image-20221021111131-15.png]]
334 334  
335 335  ​
336 336  
337 -=== 2.2.8 Change Update Interval ===
283 +=== 2.2.7 Change Update Interval ===
338 338  
339 339  
340 340  User can use below command to change the (% style="color:blue" %)**uplink interval**.
341 341  
342 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
288 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
343 343  
344 344  (% style="color:red" %)**NOTE:**
345 345  
... ... @@ -349,72 +349,51 @@
349 349  == 2.3  Uplink Payload ==
350 350  
351 351  
352 -The uplink payload includes 26 bytes in total by default.
298 +The uplink payload includes 23 bytes in total by default.
353 353  
354 354  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.
355 355  
356 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
357 357  
358 358  (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
359 -|=(% 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**
360 -|=(% 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)
304 +|=(% 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**
305 +|=(% 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
361 361  
362 362  (% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
363 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
308 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
364 364  **1-32 group**
365 365  )))
366 -|(% 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" %)...
311 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
367 367  
368 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
313 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
369 369  
315 +[[image:1670406261143-723.png]]
370 370  
371 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
372 -|=(% 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**
373 -|=(% 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)
374 374  
375 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
376 -|(% 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**
377 -|(% 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)
318 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
378 378  
379 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
380 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
381 -**1-32 group**
382 -)))
383 -|(% 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" %)......
320 +**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__(%%)**
384 384  
385 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
386 -
387 -[[image:image-20221117145932-2.png]]
388 -
389 -
390 -The payload is ASCII string, representative same HEX:
391 -
392 -**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__(%%)**
393 -
394 394  **where:**
395 395  
396 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
324 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
397 397  
398 398  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
399 399  
400 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
328 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
401 401  
402 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
330 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
403 403  
404 404  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
405 405  
406 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
334 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
407 407  
408 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
336 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
409 409  
410 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
338 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
411 411  
412 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
340 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
413 413  
414 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
415 415  
416 -
417 -
418 418  == 2.4  Payload Explanation and Sensor Interface ==
419 419  
420 420  === 2.4.1  Device ID ===
... ... @@ -436,13 +436,13 @@
436 436  
437 437  Specify the software version: 0x64=100, which means firmware version 1.00.
438 438  
439 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
364 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
440 440  
441 441  
442 442  === 2.4.3  Battery Info ===
443 443  
444 444  
445 -Check the battery voltage for NDS03A.
370 +Check the battery voltage for NMDS200.
446 446  
447 447  Ex1: 0x0B45 = 2885mV
448 448  
... ... @@ -467,38 +467,35 @@
467 467  **99**    Not known or not detectable
468 468  
469 469  
470 -=== 2.4.5  Disalarm: (default: 0) ===
395 +=== 2.4.5  Distance ===
471 471  
472 472  
473 -(% 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.
398 +[[image:1670407401682-959.png]]
474 474  
475 -(% 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.
400 +(% style="color:blue" %)**Object1 Distance:**
476 476  
477 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
402 +Distance between sensor probe to the first object. (unit: cm)
478 478  
404 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
479 479  
480 -=== 2.4.6  Keep Status & Keep Time ===
406 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
481 481  
482 482  
483 -Shows the configure value of Alarm Base on Timeout Feature
409 +(% style="color:blue" %)**Object2 Distance:**
484 484  
411 +Distance between sensor probe to the second object. (unit: cm)
485 485  
486 -=== 2.4.7  Timestamp ===
487 487  
414 +=== 2.4.6  Timestamp ===
488 488  
416 +
489 489  Timestamp : 0x6315537b =1662342011
490 490  
491 491  
492 -=== 2.4.8  Switch Dual Channel Mode ===
493 -
494 -
495 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
496 -
497 -
498 498  == 2.5  Downlink Payload ==
499 499  
500 500  
501 -By default, NDS03A prints the downlink payload to console port.
423 +By default, NMDS200 prints the downlink payload to console port.
502 502  
503 503  [[image:image-20221021111414-18.png]] ​
504 504  
... ... @@ -515,7 +515,7 @@
515 515  
516 516  * (% style="color:#037691" %)**Reset**
517 517  
518 -If payload = 0x04FF, it will reset the NDS03A
440 +If payload = 0x04FF, it will reset the NMDS200
519 519  
520 520  * (% style="color:#037691" %)**INTMOD**
521 521  
... ... @@ -525,7 +525,7 @@
525 525  == 2.6  ​LED Indicator ==
526 526  
527 527  
528 -The NDS03A has an internal LED which is to show the status of different states.
450 +The NMDS200 has an internal LED which is to show the status of different states.
529 529  
530 530  * When the device starts normally, the LED will light up for 1 second.
531 531  * After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
... ... @@ -533,7 +533,7 @@
533 533  
534 534  
535 535  
536 -== 2.7  Alarm Base on Timeout ==
458 +== 2.7  Distance alarm function ==
537 537  
538 538  
539 539  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:
... ... @@ -857,8 +857,6 @@
857 857  
858 858  * NDS03A Open/Close Door Sensor x 1
859 859  
860 -
861 -
862 862  = 9.  Support =
863 863  
864 864  
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
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

Applications

Navigation

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