Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 67.6 >
edited by Xiaoling
on 2022/11/18 10:23
To version < 81.2 >
edited by Xiaoling
on 2022/12/07 18:05
>
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,55 +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 -NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technologyTCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
45 -)))
26 +NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technology**(%%) developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
46 46  
47 -(((
48 -NDS03A is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
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 -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.
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)
31 +
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.
53 53  )))
54 54  
55 55  
... ... @@ -58,10 +58,9 @@
58 58  
59 59  
60 60  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
61 -* Open/Close detect
62 -* Open/Close statistics
41 +* Short uplink interval for Distance Alarm
63 63  * Monitor Battery Level
64 -* connect two door sensors
43 +* Microwave Radar for distance detection
65 65  * Datalog feature
66 66  * Uplink periodically
67 67  * Downlink to change configure
... ... @@ -72,22 +72,27 @@
72 72  * Micro SIM card slot for NB-IoT SIM
73 73  * 8500mAh Battery for long-term use
74 74  
75 -== 1.3  Storage & Operation ==
76 76  
55 +== 1.3 Radar probe specification ==
77 77  
78 -Temperature -40°C to +85°C
79 79  
58 +* Measuring Method: FMCW
59 +* Frequency: 24.000 24.500 GHz
60 +* Measurement output power: 6dBm
61 +* Measure range: 0.5 20m
62 +* Accuracy: ±0.1m
63 +* Resolution: 0.01m
64 +* Horizontal Angel: 78°
65 +* Vertical Angel: 23°
80 80  
81 -== 1.4  Mechanical ==
82 82  
83 83  
84 -[[image:image-20221117114937-4.png]]
69 +== 1.4  Storage Temperature ==
85 85  
86 86  
87 -[[image:image-20221117114949-5.png]]
72 + -40°C to +85°C
88 88  
89 89  
90 -[[image:image-20221117115010-6.png]]
91 91  
92 92  
93 93  
... ... @@ -94,8 +94,16 @@
94 94  == 1.5 ​ Applications ==
95 95  
96 96  
97 -[[image:image-20221117114842-3.png]]
98 98  
82 +* Horizontal distance measurement
83 +* Liquid level measurement
84 +* Parking management system
85 +* Object proximity and presence detection
86 +* Intelligent trash can management system
87 +* Robot obstacle avoidance
88 +* Automatic control
89 +* Sewer
90 +* Bottom water level monitoring
99 99  
100 100  
101 101  == 1.6  Specification ==
... ... @@ -104,107 +104,63 @@
104 104  (% style="color:blue" %)**Common DC Characteristics:**
105 105  
106 106  * Supply Voltage: 2.1v ~~ 3.6v
107 -* Operating Temperature: -40 ~~ 85°C
99 +* Operating Temperature: 0 ~~ 70°C
108 108  
109 109  (% style="color:blue" %)**NB-IoT Spec:**
110 110  
111 -* - B1 @H-FDD: 2100MHz
112 -* - B3 @H-FDD: 1800MHz
113 -* - B8 @H-FDD: 900MHz
114 -* - B5 @H-FDD: 850MHz
115 -* - B20 @H-FDD: 800MHz
116 -* - B28 @H-FDD: 700MHz
103 +* B1 @H-FDD: 2100MHz
104 +* B3 @H-FDD: 1800MHz
105 +* B8 @H-FDD: 900MHz
106 +* B5 @H-FDD: 850MHz
107 +* B20 @H-FDD: 800MHz
108 +* B28 @H-FDD: 700MHz
117 117  
118 -== 1.7  Pin Definitions and Switch ==
119 119  
111 +== 1.7  Installation ==
120 120  
121 -[[image:image-20221021110429-4.png]]
122 122  
114 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
123 123  
124 -=== 1.7.1  Pin Definition ===
125 125  
117 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
126 126  
127 -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]]
128 128  
129 129  
121 +== 1.8  Pin Definitions and Switch ==
130 130  
131 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
132 132  
124 +[[image:1670404362039-351.png]]
133 133  
134 -Power on Device when putting this jumper.
135 135  
127 += 2.  Use NMDS200 to communicate with IoT Server =
136 136  
137 -
138 -=== 1.7.3  BOOT MODE / SW1 ===
139 -
140 -
141 -1)  ISP:  upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run.
142 -
143 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
144 -
145 -
146 -
147 -=== 1.7.4  Reset Button ===
148 -
149 -
150 -Press to reboot the device.
151 -
152 -
153 -
154 -=== 1.7.5  LED ===
155 -
156 -
157 -The LED will blink when :
158 -
159 -1.  Boot the device in flash mode
160 -
161 -2.  Send an uplink packet
162 -
163 -
164 -
165 -== 1.8  Magnet Distance ==
166 -
167 -
168 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
169 -
170 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
171 -
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.
132 +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:
134 +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  
139 +== 2.2 ​ Configure NMDS200 ==
186 186  
187 -== 2.2 ​ Configure NDS03A ==
188 188  
189 -=== 2.2.1 Test Requirement ===
142 +To use NMDS200 in your city, make sure to meet below requirements:
190 190  
191 -
192 -To use NDS03A in your city, make sure to meet below requirements:
193 -
194 194  * Your local operator has already distributed an NB-IoT Network.
195 -* The local NB-IoT network used the band that NDS03A supports.
145 +* The local NB-IoT network used the band that NMDS200 supports.
196 196  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
197 197  
198 -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.
148 +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.
199 199  
200 -[[image:image-20221117142300-1.png]]
150 +[[image:image-20221207173300-4.png]]
201 201  
202 - ​
203 203  
153 +=== 2.2.1 Insert NB-IoT SIM card ===
204 204  
205 -=== 2.2.2 Insert NB-IoT SIM card ===
206 206  
207 -
208 208  Insert the NB-IoT Card get from your provider.
209 209  
210 210  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -212,12 +212,11 @@
212 212  [[image:image-20221021110745-6.png]] ​
213 213  
214 214  
163 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
215 215  
216 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
217 217  
166 +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 -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.
220 -
221 221  (% style="color:blue" %)**Connection:**
222 222  
223 223  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -239,11 +239,11 @@
239 239  
240 240  * Flow Control: (% style="color:red" %)**None**
241 241  
242 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
189 +Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
243 243  
244 244  ​[[image:image-20221021110817-7.png]]
245 245  
246 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
193 +NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
247 247  
248 248  
249 249  (% 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]]
... ... @@ -250,7 +250,7 @@
250 250  
251 251  
252 252  
253 -=== 2.2.4 Use CoAP protocol to uplink data ===
200 +=== 2.2.3 Use CoAP protocol to uplink data ===
254 254  
255 255  
256 256  (% 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/]]
... ... @@ -269,15 +269,14 @@
269 269  [[image:image-20221021110948-8.png]]
270 270  
271 271  
272 -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.
219 +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.
273 273  
274 -[[image:image-20221021110956-9.png]] ​
221 +[[image:1670405841875-916.png]] ​
275 275  
276 276  
224 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
277 277  
278 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
279 279  
280 -
281 281  (% style="color:blue" %)**AT Commands:**
282 282  
283 283  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -293,10 +293,9 @@
293 293  
294 294  ​
295 295  
242 +=== 2.2.5 Use MQTT protocol to uplink data ===
296 296  
297 -=== 2.2.6 Use MQTT protocol to uplink data ===
298 298  
299 -
300 300  (% style="color:blue" %)**AT Commands:**
301 301  
302 302  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -313,10 +313,10 @@
313 313  
314 314  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
315 315  
316 -​ [[image:image-20221021111058-12.png]]
261 +​ [[image:image-20221118103445-7.png]]
317 317  
318 318  
319 -[[image:image-20221021111201-16.png||height="472" width="653"]]
264 +[[image:1670405928926-116.png]]
320 320  
321 321  ​
322 322  
... ... @@ -323,10 +323,9 @@
323 323  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.
324 324  
325 325  
271 +=== 2.2.6 Use TCP protocol to uplink data ===
326 326  
327 -=== 2.2.7 Use TCP protocol to uplink data ===
328 328  
329 -
330 330  (% style="color:blue" %)**AT Commands:**
331 331  
332 332  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -333,19 +333,19 @@
333 333  
334 334  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
335 335  
336 -​ [[image:image-20221021111125-14.png]]
280 +​ [[image:1670406036256-101.png||height="676" width="713"]]
337 337  
282 +
338 338  [[image:image-20221021111131-15.png]]
339 339  
340 340  ​
341 341  
287 +=== 2.2.7 Change Update Interval ===
342 342  
343 -=== 2.2.8 Change Update Interval ===
344 344  
345 -
346 346  User can use below command to change the (% style="color:blue" %)**uplink interval**.
347 347  
348 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
292 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
349 349  
350 350  (% style="color:red" %)**NOTE:**
351 351  
... ... @@ -352,77 +352,57 @@
352 352  1.  By default, the device will send an uplink message every 4 hour.
353 353  
354 354  
355 -
356 356  == 2.3  Uplink Payload ==
357 357  
358 358  
359 -The uplink payload includes 26 bytes in total by default.
302 +The uplink payload includes 23 bytes in total by default.
360 360  
361 361  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.
362 362  
363 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
364 364  
365 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
366 -|=(% scope="row" style="width: 93px;" %)**Size(bytes)**|(% style="width:67px" %)**8**|(% style="width:40px" %)**2**|(% style="width:45px" %)**2**|(% style="width:75px" %)**1**|(% style="width:54px" %)**1**|(% style="width:62px" %)**1**|(% style="width:60px" %)**1**|(% style="width:94px" %)**3**|(% style="width:93px" %)**3**
367 -|=(% 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)
307 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
308 +|=(% 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**
309 +|=(% 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
368 368  
369 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
370 -|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)(((
311 +(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
312 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
371 371  **1-32 group**
372 372  )))
373 -|(% 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" %)...
315 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
374 374  
375 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
317 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
376 376  
319 +[[image:1670406261143-723.png]]
377 377  
378 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
379 -|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:66px" %)**8**|(% style="width:40px" %)**2**|(% style="width:46px" %)**2**|(% style="width:70px" %)**1**|(% style="width:54px" %)**1**|(% style="width:55px" %)**1**|(% style="width:57px" %)**1**|(% style="width:86px" %)**3**|(% style="width:82px" %)**3**
380 -|=(% 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)
381 381  
382 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
383 -|(% style="width:59px" %)**1**|(% style="width:67px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:66px" %)**1**|(% style="width:92px" %)**3**
384 -|(% 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)
322 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
385 385  
386 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
387 -|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
388 -**1-32 group**
389 -)))
390 -|(% style="width:102px" %)last open time (pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:88px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
324 +**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__(%%)**
391 391  
392 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
393 -
394 -[[image:image-20221117145932-2.png]]
395 -
396 -
397 -The payload is ASCII string, representative same HEX:
398 -
399 -**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__(%%)**
400 -
401 401  **where:**
402 402  
403 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
328 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
404 404  
405 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
330 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
406 406  
407 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
332 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
408 408  
409 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
334 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
410 410  
411 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
336 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
412 412  
413 -* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0
338 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
414 414  
415 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
340 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
416 416  
417 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
342 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
418 418  
419 -* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
344 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
420 420  
421 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
422 422  
347 +
423 423  == 2.4  Payload Explanation and Sensor Interface ==
424 424  
425 -
426 426  === 2.4.1  Device ID ===
427 427  
428 428  
... ... @@ -442,13 +442,13 @@
442 442  
443 443  Specify the software version: 0x64=100, which means firmware version 1.00.
444 444  
445 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
369 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
446 446  
447 447  
448 448  === 2.4.3  Battery Info ===
449 449  
450 450  
451 -Check the battery voltage for NDS03A.
375 +Check the battery voltage for NMDS200.
452 452  
453 453  Ex1: 0x0B45 = 2885mV
454 454  
... ... @@ -473,35 +473,31 @@
473 473  **99**    Not known or not detectable
474 474  
475 475  
476 -=== 2.4.5  Disalarm: (default: 0) ===
400 +=== 2.4.5  Distance ===
477 477  
478 478  
479 -(% 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.
403 +[[image:1670407401682-959.png]]
480 480  
481 -(% 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.
405 +**(% style="color:blue" %)Object1 Distance:**
482 482  
483 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
407 +Distance between sensor probe to the first object. (unit: cm)
484 484  
409 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
485 485  
486 -=== 2.4.6  Keep Status & Keep Time ===
411 +**(% style="color:blue" %)0205(H) = 517 (D) = 517 cm.**
487 487  
488 488  
489 -Shows the configure value of Alarm Base on Timeout Feature
414 +**(% style="color:blue" %)Object2 Distance:**
490 490  
416 +Distance between sensor probe to the second object. (unit: cm)
491 491  
492 -=== 2.4.7  Timestamp ===
493 493  
419 +=== 2.4.6  Timestamp ===
494 494  
421 +
495 495  Timestamp : 0x6315537b =1662342011
496 496  
497 497  
498 -
499 -=== 2.4.8  Switch Dual Channel Mode ===
500 -
501 -
502 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
503 -
504 -
505 505  == 2.5  Downlink Payload ==
506 506  
507 507  
... ... @@ -529,7 +529,6 @@
529 529  Downlink Payload: 06000003, Set AT+INTMOD=3
530 530  
531 531  
532 -
533 533  == 2.6  ​LED Indicator ==
534 534  
535 535  
... ... @@ -598,7 +598,6 @@
598 598  [[image:image-20221021111527-19.png]]
599 599  
600 600  
601 -
602 602  == 2.10  Count Mod ==
603 603  
604 604  
... ... @@ -607,7 +607,6 @@
607 607  [[image:image-20221118092935-1.png]]
608 608  
609 609  
610 -
611 611  == 2.11  Interrupt Pin Channel Mod ==
612 612  
613 613  
... ... @@ -616,7 +616,6 @@
616 616  [[image:image-20221118093144-2.png]]
617 617  
618 618  
619 -
620 620  == 2.12 TTRIG1/2 timeout status alarm ==
621 621  
622 622  
... ... @@ -627,7 +627,6 @@
627 627  [[image:image-20221118093512-3.png]]
628 628  
629 629  
630 -
631 631  == 2.13  Select counting mode ==
632 632  
633 633  
... ... @@ -640,8 +640,6 @@
640 640  [[image:image-20221118093658-4.png]]
641 641  
642 642  
643 -
644 -
645 645  == 2.14  Set the number of data to be uploaded and the recording time ==
646 646  
647 647  
... ... @@ -664,19 +664,16 @@
664 664  [[image:image-20221118094227-5.png]]
665 665  
666 666  
667 -
668 668  == 2.16  ​Firmware Change Log ==
669 669  
670 670  
671 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
583 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
672 672  
673 673  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
674 674  
675 675  
676 -
677 677  == 2.17  ​Battery Analysis ==
678 678  
679 -
680 680  === 2.17.1  ​Battery Type ===
681 681  
682 682  
... ... @@ -695,7 +695,6 @@
695 695  [[image:image-20221021111911-26.png]] ​
696 696  
697 697  
698 -
699 699  === 2.17.2  Power consumption Analyze ===
700 700  
701 701  
... ... @@ -718,7 +718,6 @@
718 718  [[image:1666596205057-567.png]] ​
719 719  
720 720  
721 -
722 722  === 2.17.3  ​Battery Note ===
723 723  
724 724  
... ... @@ -725,7 +725,6 @@
725 725  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.
726 726  
727 727  
728 -
729 729  === 2.17.4  Replace the battery ===
730 730  
731 731  
... ... @@ -732,7 +732,6 @@
732 732  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).
733 733  
734 734  
735 -
736 736  = 3. ​ Access NB-IoT Module =
737 737  
738 738  
... ... @@ -740,13 +740,12 @@
740 740  
741 741  The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
742 742  
649 +
743 743  [[image:image-20221118094449-6.png]] ​
744 744  
745 745  
746 -
747 747  = 4.  Using the AT Commands =
748 748  
749 -
750 750  == 4.1  Access AT Commands ==
751 751  
752 752  
... ... @@ -838,10 +838,8 @@
838 838  AT+PWORD  : Serial Access Password
839 839  
840 840  
841 -
842 842  = ​5.  FAQ =
843 843  
844 -
845 845  == 5.1 ​ How to Upgrade Firmware ==
846 846  
847 847  
... ... @@ -852,10 +852,8 @@
852 852  (% 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.**
853 853  
854 854  
855 -
856 856  = 6.  Trouble Shooting =
857 857  
858 -
859 859  == 6.1  ​Connection problem when uploading firmware ==
860 860  
861 861  
... ... @@ -862,7 +862,6 @@
862 862  (% style="color:blue" %)**Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
863 863  
864 864  
865 -
866 866  == 6.2  AT Command input doesn't work ==
867 867  
868 868  
... ... @@ -869,7 +869,6 @@
869 869  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.
870 870  
871 871  
872 -
873 873  = 7. ​ Order Info =
874 874  
875 875  
... ... @@ -876,7 +876,6 @@
876 876  Part Number**:** NDS03A
877 877  
878 878  
879 -
880 880  = 8.  Packing Info =
881 881  
882 882  
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-20221118103445-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +43.5 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-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0