Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 71.2 >
edited by Xiaoling
on 2022/12/07 16:49
To version < 83.9 >
edited by Xiaoling
on 2022/12/08 11:31
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,6 +4,7 @@
4 4  
5 5  **Table of Contents：**
6 6  
7 +{{toc/}}
7 7  
8 8  
9 9  
... ... @@ -14,51 +14,45 @@
14 14  
15 15  
16 16  (((
17 -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.
18 +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.
18 18  )))
19 19  
20 20  (((
21 -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.
22 +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.
22 22  )))
23 23  
24 24  (((
25 -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.
26 +NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
26 26  )))
27 27  
28 28  (((
29 -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.
30 +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.
30 30  )))
31 31  
32 32  (((
33 -NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
34 -)))
35 -
36 -(((
37 37  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.
38 38  )))
39 39  
40 40  (((
41 -NDS03A supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
38 +NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
42 42  )))
43 43  
44 44  (((
45 -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)
42 +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)
46 46  )))
47 47  
48 48  (((
49 -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.
46 +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.
50 50  )))
51 51  
52 52  
53 -
54 54  == ​1.2  Features ==
55 55  
56 56  
57 57  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
58 -* Open/Close detect
59 -* Open/Close statistics
54 +* Short uplink interval for Distance Alarm
60 60  * Monitor Battery Level
61 -* connect two door sensors
56 +* Microwave Radar for distance detection
62 62  * Datalog feature
63 63  * Uplink periodically
64 64  * Downlink to change configure
... ... @@ -69,33 +69,37 @@
69 69  * Micro SIM card slot for NB-IoT SIM
70 70  * 8500mAh Battery for long-term use
71 71  
67 +== 1.3 Radar probe specification ==
72 72  
73 -== 1.3  Storage & Operation ==
74 74  
70 +* Measuring Method: FMCW
71 +* Frequency: 24.000 24.500 GHz
72 +* Measurement output power: 6dBm
73 +* Measure range: 0.5 20m
74 +* Accuracy: ±0.1m
75 +* Resolution: 0.01m
76 +* Horizontal Angel: 78°
77 +* Vertical Angel: 23°
75 75  
76 -Temperature -40°C to +85°C
79 +== 1.4  Storage Temperature ==
77 77  
78 78  
79 -== 1.4  Mechanical ==
82 + -40°C to +85°C
80 80  
81 81  
82 -[[image:image-20221117114937-4.png]]
83 -
84 -
85 -[[image:image-20221117114949-5.png]]
86 -
87 -
88 -[[image:image-20221117115010-6.png]]
89 -
90 -
91 -
92 92  == 1.5 ​ Applications ==
93 93  
94 94  
95 -[[image:image-20221117114842-3.png]]
88 +* Horizontal distance measurement
89 +* Liquid level measurement
90 +* Parking management system
91 +* Object proximity and presence detection
92 +* Intelligent trash can management system
93 +* Robot obstacle avoidance
94 +* Automatic control
95 +* Sewer
96 +* Bottom water level monitoring
96 96  
97 -
98 -
99 99  == 1.6  Specification ==
100 100  
101 101  
... ... @@ -102,7 +102,7 @@
102 102  (% style="color:blue" %)**Common DC Characteristics:**
103 103  
104 104  * Supply Voltage: 2.1v ~~ 3.6v
105 -* Operating Temperature: -40 ~~ 85°C
104 +* Operating Temperature: 0 ~~ 70°C
106 106  
107 107  (% style="color:blue" %)**NB-IoT Spec:**
108 108  
... ... @@ -113,86 +113,49 @@
113 113  * B20 @H-FDD: 800MHz
114 114  * B28 @H-FDD: 700MHz
115 115  
115 +== 1.7  Installation ==
116 116  
117 -== 1.7  Pin Definitions and Switch ==
118 118  
118 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
119 119  
120 -[[image:image-20221021110429-4.png]]
121 121  
121 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
122 122  
123 -=== 1.7.1  Pin Definition ===
124 124  
125 125  
126 -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]]
125 +== 1.8  Pin Definitions and Switch ==
127 127  
128 128  
129 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
128 +[[image:1670404362039-351.png]]
130 130  
131 131  
132 -Power on Device when putting this jumper.
131 += 2.  Use NMDS200 to communicate with IoT Server =
133 133  
134 -
135 -=== 1.7.3  BOOT MODE / SW1 ===
136 -
137 -
138 -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.
139 -
140 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
141 -
142 -
143 -=== 1.7.4  Reset Button ===
144 -
145 -
146 -Press to reboot the device.
147 -
148 -
149 -=== 1.7.5  LED ===
150 -
151 -
152 -The LED will blink when :
153 -
154 -1.  Boot the device in flash mode
155 -
156 -2.  Send an uplink packet
157 -
158 -
159 -== 1.8  Magnet Distance ==
160 -
161 -
162 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
163 -
164 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
165 -
166 -
167 -= 2.  Use NDS03A to communicate with IoT Server =
168 -
169 169  == 2.1  How it works ==
170 170  
171 171  
172 -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.
136 +The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
173 173  
174 -The diagram below shows the working flow in the default firmware of NDS03A:
138 +The diagram below shows the working flow in the default firmware of NMDS200:
175 175  
176 176  [[image:image-20221021110615-5.png]]
177 177  
178 178  
179 -== 2.2 ​ Configure NDS03A ==
143 +== 2.2 ​ Configure NMDS200 ==
180 180  
181 -=== 2.2.1 Test Requirement ===
182 182  
146 +To use NMDS200 in your city, make sure to meet below requirements:
183 183  
184 -To use NDS03A in your city, make sure to meet below requirements:
185 -
186 186  * Your local operator has already distributed an NB-IoT Network.
187 -* The local NB-IoT network used the band that NDS03A supports.
149 +* The local NB-IoT network used the band that NMDS200 supports.
188 188  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
189 189  
190 -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.
152 +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.
191 191  
192 -[[image:image-20221117142300-1.png]]
154 +[[image:image-20221208090742-1.png]]
193 193  
194 194  
195 -=== 2.2.2 Insert NB-IoT SIM card ===
157 +=== 2.2.1 Insert NB-IoT SIM card ===
196 196  
197 197  
198 198  Insert the NB-IoT Card get from your provider.
... ... @@ -202,10 +202,10 @@
202 202  [[image:image-20221021110745-6.png]] ​
203 203  
204 204  
205 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
167 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
206 206  
207 207  
208 -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.
170 +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.
209 209  
210 210  (% style="color:blue" %)**Connection:**
211 211  
... ... @@ -228,11 +228,11 @@
228 228  
229 229  * Flow Control: (% style="color:red" %)**None**
230 230  
231 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
193 +Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
232 232  
233 233  ​[[image:image-20221021110817-7.png]]
234 234  
235 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
197 +NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
236 236  
237 237  
238 238  (% 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]]
... ... @@ -239,13 +239,13 @@
239 239  
240 240  
241 241  
242 -=== 2.2.4 Use CoAP protocol to uplink data ===
204 +=== 2.2.3 Use CoAP protocol to uplink data ===
243 243  
244 244  
245 245  (% 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/]]
246 246  
247 247  
248 -(% style="color:blue" %)**Use below commands in NDS03A:**
210 +(% style="color:blue" %)**Use below commands in NMDS200:**
249 249  
250 250  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
251 251  
... ... @@ -258,12 +258,12 @@
258 258  [[image:image-20221021110948-8.png]]
259 259  
260 260  
261 -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.
223 +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.
262 262  
263 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
225 +[[image:1670405841875-916.png]] ​
264 264  
265 265  
266 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
228 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
267 267  
268 268  
269 269  (% style="color:blue" %)**AT Commands:**
... ... @@ -281,7 +281,7 @@
281 281  
282 282  ​
283 283  
284 -=== 2.2.6 Use MQTT protocol to uplink data ===
246 +=== 2.2.5 Use MQTT protocol to uplink data ===
285 285  
286 286  
287 287  (% style="color:blue" %)**AT Commands:**
... ... @@ -303,7 +303,7 @@
303 303  ​ [[image:image-20221118103445-7.png]]
304 304  
305 305  
306 -[[image:image-20221118103453-8.png||height="608" width="841"]]
268 +[[image:1670405928926-116.png]]
307 307  
308 308  ​
309 309  
... ... @@ -310,7 +310,7 @@
310 310  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.
311 311  
312 312  
313 -=== 2.2.7 Use TCP protocol to uplink data ===
275 +=== 2.2.6 Use TCP protocol to uplink data ===
314 314  
315 315  
316 316  (% style="color:blue" %)**AT Commands:**
... ... @@ -319,18 +319,19 @@
319 319  
320 320  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
321 321  
322 -​ [[image:image-20221021111125-14.png]]
284 +​ [[image:1670406036256-101.png||height="676" width="713"]]
323 323  
286 +
324 324  [[image:image-20221021111131-15.png]]
325 325  
326 326  ​
327 327  
328 -=== 2.2.8 Change Update Interval ===
291 +=== 2.2.7 Change Update Interval ===
329 329  
330 330  
331 331  User can use below command to change the (% style="color:blue" %)**uplink interval**.
332 332  
333 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
296 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
334 334  
335 335  (% style="color:red" %)**NOTE:**
336 336  
... ... @@ -340,71 +340,51 @@
340 340  == 2.3  Uplink Payload ==
341 341  
342 342  
343 -The uplink payload includes 26 bytes in total by default.
306 +The uplink payload includes 23 bytes in total by default.
344 344  
345 345  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.
346 346  
347 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
348 348  
349 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
350 -|=(% 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**
351 -|=(% 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)
311 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %)
312 +|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:30px" %)**2**|(% style="width:30px" %)**2**|(% style="width:75px" %)**1**|(% style="width:30px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**
313 +|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) [[Distance 1>>||anchor="H2.4.5A0Distance"]] |(% style="width:93px" %) [[Distance 2>>||anchor="H2.4.5A0Distance"]]
352 352  
353 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
354 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
315 +(% border="1" style="background-color:#ffffcc; color:green; width:350px" %)
316 +|(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((
355 355  **1-32 group**
356 356  )))
357 -|(% 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" %)...
319 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:98px" %)...
358 358  
359 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
321 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
360 360  
323 +[[image:1670406261143-723.png]]
361 361  
362 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
363 -|=(% 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**
364 -|=(% 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)
365 365  
366 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
367 -|(% 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**
368 -|(% 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)
326 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
369 369  
370 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
371 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
372 -**1-32 group**
373 -)))
374 -|(% 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" %)......
328 +**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__(%%)**
375 375  
376 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
377 -
378 -[[image:image-20221117145932-2.png]]
379 -
380 -
381 -The payload is ASCII string, representative same HEX:
382 -
383 -**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__(%%)**
384 -
385 385  **where:**
386 386  
387 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
332 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
388 388  
389 389  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
390 390  
391 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
336 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
392 392  
393 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
338 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
394 394  
395 395  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
396 396  
397 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
342 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
398 398  
399 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
344 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
400 400  
401 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
346 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
402 402  
403 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
348 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
404 404  
405 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
406 406  
407 -
408 408  == 2.4  Payload Explanation and Sensor Interface ==
409 409  
410 410  === 2.4.1  Device ID ===
... ... @@ -426,13 +426,13 @@
426 426  
427 427  Specify the software version: 0x64=100, which means firmware version 1.00.
428 428  
429 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
372 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
430 430  
431 431  
432 432  === 2.4.3  Battery Info ===
433 433  
434 434  
435 -Check the battery voltage for NDS03A.
378 +Check the battery voltage for NMDS200.
436 436  
437 437  Ex1: 0x0B45 = 2885mV
438 438  
... ... @@ -444,51 +444,49 @@
444 444  
445 445  NB-IoT Network signal Strength.
446 446  
447 -**Ex1: 0x1d = 29**
390 +(% style="color:blue" %)**Ex1: 0x1d = 29**
448 448  
449 -**0**  -113dBm or less
392 +(% style="color:#037691" %)**0** (%%) -113dBm or less
450 450  
451 -**1**  -111dBm
394 +(% style="color:#037691" %)**1**  (%%) -111dBm
452 452  
453 -**2...30** -109dBm... -53dBm
396 +(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
454 454  
455 -**31**   -51dBm or greater
398 +(% style="color:#037691" %)**31** (%%) -51dBm or greater
456 456  
457 -**99**    Not known or not detectable
400 +(% style="color:#037691" %)**99** (%%) Not known or not detectable
458 458  
459 459  
460 -=== 2.4.5  Disalarm: (default: 0) ===
403 +=== 2.4.5  Distance ===
461 461  
462 462  
463 -(% 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.
406 +[[image:1670407401682-959.png]]
464 464  
465 -(% 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.
466 466  
467 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
409 +(% style="color:blue" %)**Object1 Distance:**
468 468  
411 +Distance between sensor probe to the first object. (unit: cm)
469 469  
470 -=== 2.4.6  Keep Status & Keep Time ===
413 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
471 471  
415 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
472 472  
473 -Shows the configure value of Alarm Base on Timeout Feature
474 474  
418 +(% style="color:blue" %)**Object2 Distance:**
475 475  
476 -=== 2.4.7  Timestamp ===
420 +Distance between sensor probe to the second object. (unit: cm)
477 477  
478 478  
479 -Timestamp : 0x6315537b =1662342011
423 +=== 2.4.6  Timestamp ===
480 480  
481 481  
482 -=== 2.4.8  Switch Dual Channel Mode ===
426 +Timestamp : 0x6315537b =1662342011
483 483  
484 484  
485 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
486 -
487 -
488 488  == 2.5  Downlink Payload ==
489 489  
490 490  
491 -By default, NDS03A prints the downlink payload to console port.
432 +By default, NMDS200 prints the downlink payload to console port.
492 492  
493 493  [[image:image-20221021111414-18.png]] ​
494 494  
... ... @@ -505,7 +505,7 @@
505 505  
506 506  * (% style="color:#037691" %)**Reset**
507 507  
508 -If payload = 0x04FF, it will reset the NDS03A
449 +If payload = 0x04FF, it will reset the NMDS200
509 509  
510 510  * (% style="color:#037691" %)**INTMOD**
511 511  
... ... @@ -515,113 +515,33 @@
515 515  == 2.6  ​LED Indicator ==
516 516  
517 517  
518 -The NDS03A has an internal LED which is to show the status of different states.
459 +The NMDS200 has an internal LED which is to show the status of different states.
519 519  
520 520  * When the device starts normally, the LED will light up for 1 second.
521 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
462 +* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
522 522  * For each uplink probe, LED will be on for 500ms.
523 523  
524 524  
525 -== 2.7  Alarm Base on Timeout ==
466 +== 2.7  Distance alarm function ==
526 526  
527 527  
528 -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:
469 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
529 529  
471 +(% style="color:#037691" %)**Example 1:**
530 530  
531 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
473 +AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
532 532  
533 -Keep Status = 1: Monitor Close to Open event
475 +AT+ ALARM2 =min,max
534 534  
535 -Keep Status = 0: Monitor Open to Close event
536 536  
478 +(% style="color:#037691" %)**Example 2:**
537 537  
538 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
480 +AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
539 539  
540 -Range 0 ~~ 65535(0xFFFF) seconds.
541 541  
542 -If keep time = 0, Disable Alarm Base on Timeout feature.
483 +== 2.8  Set the number of data to be uploaded and the recording time ==
543 543  
544 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
545 545  
546 -
547 -(% style="color:blue" %)**AT Command to configure:**
548 -
549 -(% style="color:blue" %)**PB14 PIN:**
550 -
551 -(% 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.
552 -
553 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
554 -
555 -
556 -(% style="color:blue" %)**PB15 PIN:**
557 -
558 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
559 -
560 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
561 -
562 -
563 -== 2.8  Set debug mode ==
564 -
565 -
566 -Feature: Enable or Disable debug mode
567 -
568 -(% style="color:blue" %)**AT Command: AT+DEBUG**
569 -
570 -[[image:image-20221021111629-21.png]]
571 -
572 -
573 -
574 -== 2.9  Clear Flash Record ==
575 -
576 -
577 -Feature: Clear flash storage for data log feature.
578 -
579 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
580 -
581 -[[image:image-20221021111527-19.png]]
582 -
583 -
584 -== 2.10  Count Mod ==
585 -
586 -
587 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
588 -
589 -[[image:image-20221118092935-1.png]]
590 -
591 -
592 -== 2.11  Interrupt Pin Channel Mod ==
593 -
594 -
595 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
596 -
597 -[[image:image-20221118093144-2.png]]
598 -
599 -
600 -== 2.12 TTRIG1/2 timeout status alarm ==
601 -
602 -
603 -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.
604 -
605 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
606 -
607 -[[image:image-20221118093512-3.png]]
608 -
609 -
610 -== 2.13  Select counting mode ==
611 -
612 -
613 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
614 -
615 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
616 -
617 -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.
618 -
619 -[[image:image-20221118093658-4.png]]
620 -
621 -
622 -== 2.14  Set the number of data to be uploaded and the recording time ==
623 -
624 -
625 625  (% style="color:blue" %)**AT Command:**
626 626  
627 627  (% 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)
... ... @@ -629,7 +629,7 @@
629 629  (% 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.
630 630  
631 631  
632 -== 2.15  Read or Clear cached data ==
493 +== 2.9  Read or Clear cached data ==
633 633  
634 634  
635 635  (% style="color:blue" %)**AT Command:**
... ... @@ -638,10 +638,10 @@
638 638  
639 639  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
640 640  
641 -[[image:image-20221118094227-5.png]]
502 +[[image:1670408172929-569.png]]
642 642  
643 643  
644 -== 2.16  ​Firmware Change Log ==
505 +== 2.10  ​Firmware Change Log ==
645 645  
646 646  
647 647  Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
... ... @@ -649,12 +649,12 @@
649 649  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
650 650  
651 651  
652 -== 2.17  ​Battery Analysis ==
513 +== 2.11  ​Battery Analysis ==
653 653  
654 -=== 2.17.1  ​Battery Type ===
515 +=== 2.11.1  ​Battery Type ===
655 655  
656 656  
657 -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.
518 +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.
658 658  
659 659  The battery is designed to last for several years depends on the actual use environment and update interval. 
660 660  
... ... @@ -669,7 +669,7 @@
669 669  [[image:image-20221021111911-26.png]] ​
670 670  
671 671  
672 -=== 2.17.2  Power consumption Analyze ===
533 +=== 2.11.2  Power consumption Analyze ===
673 673  
674 674  
675 675  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.
... ... @@ -691,16 +691,16 @@
691 691  [[image:1666596205057-567.png]] ​
692 692  
693 693  
694 -=== 2.17.3  ​Battery Note ===
555 +=== 2.11.3  ​Battery Note ===
695 695  
696 696  
697 697  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.
698 698  
699 699  
700 -=== 2.17.4  Replace the battery ===
561 +=== 2.11.4  Replace the battery ===
701 701  
702 702  
703 -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).
564 +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).
704 704  
705 705  
706 706  = 3. ​ Access NB-IoT Module =
... ... @@ -746,65 +746,59 @@
746 746  
747 747  AT+INTMOD            : Set the trigger interrupt mode
748 748  
749 -AT+5VT  : Set extend the time of 5V power  
610 +AT+5VT  : Set extend the time of 5V power  
750 750  
751 -AT+PRO  : Choose agreement
612 +AT+PRO  : Choose agreement
752 752  
753 -AT+RXDL  : Extend the sending and receiving time
614 +AT+RXDL  : Extend the sending and receiving time
754 754  
755 -AT+SERVADDR  : Server Address
616 +AT+SERVADDR  : Server Address
756 756  
757 -AT+TR      :  Get or Set record time
618 +AT+TR      :  Get or Set record time
758 758  
759 -AT+NOUD      : Get or Set the number of data to be uploaded
620 +AT+NOUD :  Get or Set the number of data to be uploaded
760 760  
761 761  AT+CDP     :  Read or Clear cached data
762 762  
763 -AT+ DEBUG   : Enable or Disable debug mode
624 +AT+DEBUG:  Enable or Disable debug mode
764 764  
765 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
626 +AT+ALARM1:  Get or Set alarm of distance1
766 766  
767 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
628 +AT+ALARM2:  Get or Set alarm of distance2
768 768  
769 -AT+COUNTMOD  :  Get or Set the count mode
630 +AT+GETSENSORVALUE :  Returns the current sensor measurement
770 770  
771 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
632 +AT+POWERIC :  Get or set the Power IC flag
772 772  
773 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
774 774  
775 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
776 -
777 -AT+ CLRC   :  Clear current door open count
778 -
779 -
780 780  (% style="color:blue" %)**COAP Management**      
781 781  
782 -AT+URI            : Resource parameters
637 +AT+URI :  Resource parameters
783 783  
784 784  
785 785  (% style="color:blue" %)**UDP Management**
786 786  
787 -AT+CFM          : Upload confirmation mode (only valid for UDP)
642 +AT+CFM :  Upload confirmation mode (only valid for UDP)
788 788  
789 789  
790 790  (% style="color:blue" %)**MQTT Management**
791 791  
792 -AT+CLIENT               : Get or Set MQTT client
647 +AT+CLIENT  : Get or Set MQTT client
793 793  
794 -AT+UNAME  : Get or Set MQTT Username
649 +AT+UNAME : Get or Set MQTT Username
795 795  
796 -AT+PWD                  : Get or Set MQTT password
651 +AT+PWD  :  Get or Set MQTT password
797 797  
798 -AT+PUBTOPIC  : Get or Set MQTT publish topic
653 +AT+PUBTOPIC :  Get or Set MQTT publish topic
799 799  
800 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
655 +AT+SUBTOPIC :  Get or Set MQTT subscription topic
801 801  
802 802  
803 803  (% style="color:blue" %)**Information**          
804 804  
805 -AT+FDR  : Factory Data Reset
660 +AT+FDR :  Factory Data Reset
806 806  
807 -AT+PWORD  : Serial Access Password
662 +AT+PWORD :  Serial Access Password
808 808  
809 809  
810 810  = ​5.  FAQ =
... ... @@ -816,7 +816,7 @@
816 816  
817 817  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]]
818 818  
819 -(% 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.**
674 +(% 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.**
820 820  
821 821  
822 822  = 6.  Trouble Shooting =
... ... @@ -836,7 +836,7 @@
836 836  = 7. ​ Order Info =
837 837  
838 838  
839 -Part Number**:** NDS03A
694 +Part Number:(% style="color:blue" %)** NMDS200**
840 840  
841 841  
842 842  = 8.  Packing Info =
... ... @@ -844,7 +844,7 @@
844 844  
845 845  (% style="color:blue" %)**Package Includes**:
846 846  
847 -* NDS03A Open/Close Door Sensor x 1
702 +* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
848 848  
849 849  
850 850  = 9.  Support =
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
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