Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 70.22 >
edited by Xiaoling
on 2022/11/18 11:25
To version < 83.1 >
edited by Xiaoling
on 2022/12/08 09:07
>
Change comment: Uploaded new attachment "image-20221208090742-1.png", version {1}

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,34 +72,42 @@
72 72  * Micro SIM card slot for NB-IoT SIM
73 73  * 8500mAh Battery for long-term use
74 74  
54 +== 1.3 Radar probe specification ==
75 75  
76 76  
77 -== 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°
78 78  
79 79  
80 -Temperature -40°C to +85°C
67 +== 1.4  Storage Temperature ==
81 81  
82 82  
83 -== 1.4  Mechanical ==
70 + -40°C to +85°C
84 84  
85 85  
86 -[[image:image-20221117114937-4.png]]
87 87  
88 88  
89 -[[image:image-20221117114949-5.png]]
90 90  
91 -
92 -[[image:image-20221117115010-6.png]]
93 -
94 -
95 -
96 96  == 1.5 ​ Applications ==
97 97  
98 98  
99 -[[image:image-20221117114842-3.png]]
100 100  
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
101 101  
102 -
103 103  == 1.6  Specification ==
104 104  
105 105  
... ... @@ -106,98 +106,60 @@
106 106  (% style="color:blue" %)**Common DC Characteristics:**
107 107  
108 108  * Supply Voltage: 2.1v ~~ 3.6v
109 -* Operating Temperature: -40 ~~ 85°C
96 +* Operating Temperature: 0 ~~ 70°C
110 110  
111 111  (% style="color:blue" %)**NB-IoT Spec:**
112 112  
113 -* - B1 @H-FDD: 2100MHz
114 -* - B3 @H-FDD: 1800MHz
115 -* - B8 @H-FDD: 900MHz
116 -* - B5 @H-FDD: 850MHz
117 -* - B20 @H-FDD: 800MHz
118 -* - B28 @H-FDD: 700MHz
100 +* B1 @H-FDD: 2100MHz
101 +* B3 @H-FDD: 1800MHz
102 +* B8 @H-FDD: 900MHz
103 +* B5 @H-FDD: 850MHz
104 +* B20 @H-FDD: 800MHz
105 +* B28 @H-FDD: 700MHz
119 119  
107 +== 1.7  Installation ==
120 120  
121 121  
122 -== 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.
123 123  
124 124  
125 -[[image:image-20221021110429-4.png]]
113 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
126 126  
127 127  
128 -=== 1.7.1  Pin Definition ===
129 129  
117 +== 1.8  Pin Definitions and Switch ==
130 130  
131 -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]]
132 132  
120 +[[image:1670404362039-351.png]]
133 133  
134 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
135 135  
123 += 2.  Use NMDS200 to communicate with IoT Server =
136 136  
137 -Power on Device when putting this jumper.
138 -
139 -
140 -=== 1.7.3  BOOT MODE / SW1 ===
141 -
142 -
143 -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.
144 -
145 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
146 -
147 -
148 -=== 1.7.4  Reset Button ===
149 -
150 -
151 -Press to reboot the device.
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 -== 1.8  Magnet Distance ==
165 -
166 -
167 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
168 -
169 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
170 -
171 -
172 -= 2.  Use NDS03A to communicate with IoT Server =
173 -
174 174  == 2.1  How it works ==
175 175  
176 176  
177 -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.
178 178  
179 -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:
180 180  
181 181  [[image:image-20221021110615-5.png]]
182 182  
183 183  
184 -== 2.2 ​ Configure NDS03A ==
135 +== 2.2 ​ Configure NMDS200 ==
185 185  
186 -=== 2.2.1 Test Requirement ===
187 187  
138 +To use NMDS200 in your city, make sure to meet below requirements:
188 188  
189 -To use NDS03A in your city, make sure to meet below requirements:
190 -
191 191  * Your local operator has already distributed an NB-IoT Network.
192 -* The local NB-IoT network used the band that NDS03A supports.
141 +* The local NB-IoT network used the band that NMDS200 supports.
193 193  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
194 194  
195 -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.
196 196  
197 -[[image:image-20221117142300-1.png]]
146 +[[image:image-20221207173300-4.png]]
198 198  
199 199  
200 -=== 2.2.2 Insert NB-IoT SIM card ===
149 +=== 2.2.1 Insert NB-IoT SIM card ===
201 201  
202 202  
203 203  Insert the NB-IoT Card get from your provider.
... ... @@ -207,10 +207,10 @@
207 207  [[image:image-20221021110745-6.png]] ​
208 208  
209 209  
210 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
159 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
211 211  
212 212  
213 -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.
214 214  
215 215  (% style="color:blue" %)**Connection:**
216 216  
... ... @@ -233,11 +233,11 @@
233 233  
234 234  * Flow Control: (% style="color:red" %)**None**
235 235  
236 -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**(%%).
237 237  
238 238  ​[[image:image-20221021110817-7.png]]
239 239  
240 -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.
241 241  
242 242  
243 243  (% 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]]
... ... @@ -244,7 +244,7 @@
244 244  
245 245  
246 246  
247 -=== 2.2.4 Use CoAP protocol to uplink data ===
196 +=== 2.2.3 Use CoAP protocol to uplink data ===
248 248  
249 249  
250 250  (% 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/]]
... ... @@ -263,12 +263,12 @@
263 263  [[image:image-20221021110948-8.png]]
264 264  
265 265  
266 -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.
267 267  
268 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
217 +[[image:1670405841875-916.png]] ​
269 269  
270 270  
271 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
220 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
272 272  
273 273  
274 274  (% style="color:blue" %)**AT Commands:**
... ... @@ -286,7 +286,7 @@
286 286  
287 287  ​
288 288  
289 -=== 2.2.6 Use MQTT protocol to uplink data ===
238 +=== 2.2.5 Use MQTT protocol to uplink data ===
290 290  
291 291  
292 292  (% style="color:blue" %)**AT Commands:**
... ... @@ -308,7 +308,7 @@
308 308  ​ [[image:image-20221118103445-7.png]]
309 309  
310 310  
311 -[[image:image-20221118103453-8.png||height="608" width="841"]]
260 +[[image:1670405928926-116.png]]
312 312  
313 313  ​
314 314  
... ... @@ -315,7 +315,7 @@
315 315  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.
316 316  
317 317  
318 -=== 2.2.7 Use TCP protocol to uplink data ===
267 +=== 2.2.6 Use TCP protocol to uplink data ===
319 319  
320 320  
321 321  (% style="color:blue" %)**AT Commands:**
... ... @@ -324,18 +324,19 @@
324 324  
325 325  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
326 326  
327 -​ [[image:image-20221021111125-14.png]]
276 +​ [[image:1670406036256-101.png||height="676" width="713"]]
328 328  
278 +
329 329  [[image:image-20221021111131-15.png]]
330 330  
331 331  ​
332 332  
333 -=== 2.2.8 Change Update Interval ===
283 +=== 2.2.7 Change Update Interval ===
334 334  
335 335  
336 336  User can use below command to change the (% style="color:blue" %)**uplink interval**.
337 337  
338 -* (% 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)
339 339  
340 340  (% style="color:red" %)**NOTE:**
341 341  
... ... @@ -345,73 +345,51 @@
345 345  == 2.3  Uplink Payload ==
346 346  
347 347  
348 -The uplink payload includes 26 bytes in total by default.
298 +The uplink payload includes 23 bytes in total by default.
349 349  
350 350  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.
351 351  
352 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
353 353  
354 354  (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
355 -|=(% 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**
356 -|=(% 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
357 357  
358 358  (% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
359 -|(% 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" %)(((
360 360  **1-32 group**
361 361  )))
362 -|(% 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" %)...
363 363  
313 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
364 364  
365 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
315 +[[image:1670406261143-723.png]]
366 366  
367 367  
368 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
369 -|=(% 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**
370 -|=(% 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)
318 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
371 371  
372 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
373 -|(% 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**
374 -|(% 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)
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__(%%)**
375 375  
376 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
377 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
378 -**1-32 group**
379 -)))
380 -|(% 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" %)......
381 -
382 -
383 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
384 -
385 -[[image:image-20221117145932-2.png]]
386 -
387 -
388 -The payload is ASCII string, representative same HEX:
389 -
390 -**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)**
391 -
392 392  **where:**
393 393  
394 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
324 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
395 395  
396 396  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
397 397  
398 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
328 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
399 399  
400 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
330 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
401 401  
402 402  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
403 403  
404 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
334 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
405 405  
406 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
336 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
407 407  
408 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
338 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
409 409  
410 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
340 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
411 411  
412 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
413 413  
414 -
415 415  == 2.4  Payload Explanation and Sensor Interface ==
416 416  
417 417  === 2.4.1  Device ID ===
... ... @@ -433,13 +433,13 @@
433 433  
434 434  Specify the software version: 0x64=100, which means firmware version 1.00.
435 435  
436 -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.
437 437  
438 438  
439 439  === 2.4.3  Battery Info ===
440 440  
441 441  
442 -Check the battery voltage for NDS03A.
370 +Check the battery voltage for NMDS200.
443 443  
444 444  Ex1: 0x0B45 = 2885mV
445 445  
... ... @@ -464,38 +464,35 @@
464 464  **99**    Not known or not detectable
465 465  
466 466  
467 -=== 2.4.5  Disalarm: (default: 0) ===
395 +=== 2.4.5  Distance ===
468 468  
469 469  
470 -(% 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]]
471 471  
472 -(% 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:**
473 473  
474 - (% 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)
475 475  
404 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
476 476  
477 -=== 2.4.6  Keep Status & Keep Time ===
406 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
478 478  
479 479  
480 -Shows the configure value of Alarm Base on Timeout Feature
409 +(% style="color:blue" %)**Object2 Distance:**
481 481  
411 +Distance between sensor probe to the second object. (unit: cm)
482 482  
483 -=== 2.4.7  Timestamp ===
484 484  
414 +=== 2.4.6  Timestamp ===
485 485  
416 +
486 486  Timestamp : 0x6315537b =1662342011
487 487  
488 488  
489 -=== 2.4.8  Switch Dual Channel Mode ===
490 -
491 -
492 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
493 -
494 -
495 495  == 2.5  Downlink Payload ==
496 496  
497 497  
498 -By default, NDS03A prints the downlink payload to console port.
423 +By default, NMDS200 prints the downlink payload to console port.
499 499  
500 500  [[image:image-20221021111414-18.png]] ​
501 501  
... ... @@ -512,7 +512,7 @@
512 512  
513 513  * (% style="color:#037691" %)**Reset**
514 514  
515 -If payload = 0x04FF, it will reset the NDS03A
440 +If payload = 0x04FF, it will reset the NMDS200
516 516  
517 517  * (% style="color:#037691" %)**INTMOD**
518 518  
... ... @@ -522,7 +522,7 @@
522 522  == 2.6  ​LED Indicator ==
523 523  
524 524  
525 -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.
526 526  
527 527  * When the device starts normally, the LED will light up for 1 second.
528 528  * After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
... ... @@ -529,106 +529,27 @@
529 529  * For each uplink probe, LED will be on for 500ms.
530 530  
531 531  
532 -== 2.7  Alarm Base on Timeout ==
533 533  
458 +== 2.7  Distance alarm function ==
534 534  
535 -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:
536 536  
461 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
537 537  
538 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
463 +**Example 1:**
539 539  
540 -Keep Status = 1: Monitor Close to Open event
465 +AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
541 541  
542 -Keep Status = 0: Monitor Open to Close event
467 +AT+ ALARM2 =min,max
543 543  
544 544  
545 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
470 +**Example 2:**
546 546  
547 -Range 0 ~~ 65535(0xFFFF) seconds.
472 +AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
548 548  
549 -If keep time = 0, Disable Alarm Base on Timeout feature.
550 550  
551 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
475 +== 2.8  Set the number of data to be uploaded and the recording time ==
552 552  
553 553  
554 -(% style="color:blue" %)**AT Command to configure:**
555 -
556 -(% style="color:blue" %)**PB14 PIN:**
557 -
558 -(% 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.
559 -
560 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
561 -
562 -
563 -(% style="color:blue" %)**PB15 PIN:**
564 -
565 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
566 -
567 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
568 -
569 -
570 -== 2.8  Set debug mode ==
571 -
572 -
573 -Feature: Enable or Disable debug mode
574 -
575 -(% style="color:blue" %)**AT Command: AT+DEBUG**
576 -
577 -[[image:image-20221021111629-21.png]]
578 -
579 -
580 -
581 -== 2.9  Clear Flash Record ==
582 -
583 -
584 -Feature: Clear flash storage for data log feature.
585 -
586 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
587 -
588 -[[image:image-20221021111527-19.png]]
589 -
590 -
591 -== 2.10  Count Mod ==
592 -
593 -
594 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
595 -
596 -[[image:image-20221118092935-1.png]]
597 -
598 -
599 -== 2.11  Interrupt Pin Channel Mod ==
600 -
601 -
602 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
603 -
604 -[[image:image-20221118093144-2.png]]
605 -
606 -
607 -== 2.12 TTRIG1/2 timeout status alarm ==
608 -
609 -
610 -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.
611 -
612 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
613 -
614 -[[image:image-20221118093512-3.png]]
615 -
616 -
617 -== 2.13  Select counting mode ==
618 -
619 -
620 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
621 -
622 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
623 -
624 -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.
625 -
626 -[[image:image-20221118093658-4.png]]
627 -
628 -
629 -== 2.14  Set the number of data to be uploaded and the recording time ==
630 -
631 -
632 632  (% style="color:blue" %)**AT Command:**
633 633  
634 634  (% 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)
... ... @@ -636,7 +636,7 @@
636 636  (% 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.
637 637  
638 638  
639 -== 2.15  Read or Clear cached data ==
485 +== 2.9  Read or Clear cached data ==
640 640  
641 641  
642 642  (% style="color:blue" %)**AT Command:**
... ... @@ -645,10 +645,10 @@
645 645  
646 646  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
647 647  
648 -[[image:image-20221118094227-5.png]]
494 +[[image:1670408172929-569.png]]
649 649  
650 650  
651 -== 2.16  ​Firmware Change Log ==
497 +== 2.10  ​Firmware Change Log ==
652 652  
653 653  
654 654  Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
... ... @@ -656,12 +656,12 @@
656 656  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
657 657  
658 658  
659 -== 2.17  ​Battery Analysis ==
505 +== 2.11  ​Battery Analysis ==
660 660  
661 -=== 2.17.1  ​Battery Type ===
507 +=== 2.11.1  ​Battery Type ===
662 662  
663 663  
664 -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.
510 +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.
665 665  
666 666  The battery is designed to last for several years depends on the actual use environment and update interval. 
667 667  
... ... @@ -676,7 +676,7 @@
676 676  [[image:image-20221021111911-26.png]] ​
677 677  
678 678  
679 -=== 2.17.2  Power consumption Analyze ===
525 +=== 2.11.2  Power consumption Analyze ===
680 680  
681 681  
682 682  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.
... ... @@ -698,16 +698,16 @@
698 698  [[image:1666596205057-567.png]] ​
699 699  
700 700  
701 -=== 2.17.3  ​Battery Note ===
547 +=== 2.11.3  ​Battery Note ===
702 702  
703 703  
704 704  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.
705 705  
706 706  
707 -=== 2.17.4  Replace the battery ===
553 +=== 2.11.4  Replace the battery ===
708 708  
709 709  
710 -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).
556 +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).
711 711  
712 712  
713 713  = 3. ​ Access NB-IoT Module =
... ... @@ -853,8 +853,6 @@
853 853  
854 854  * NDS03A Open/Close Door Sensor x 1
855 855  
856 -
857 -
858 858  = 9.  Support =
859 859  
860 860  
1670404362039-351.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +492.6 KB
Content
1670405841875-916.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +181.0 KB
Content
1670406261143-723.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.9 KB
Content
1670407401682-959.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +23.7 KB
Content
1670408172929-569.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +211.8 KB
Content
LMDS200_10.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
image-20221207170748-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.1 KB
Content
image-20221207170748-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +29.9 KB
Content
image-20221207173200-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.7 KB
Content
image-20221207173300-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.0 KB
Content
image-20221208090742-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +79.7 KB
Content

Applications

Navigation

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