Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 81.3 >
edited by Xiaoling
on 2022/12/07 18:09
To version < 70.2 >
edited by Xiaoling
on 2022/11/18 10:39
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
1 +NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
Content
... ... @@ -1,35 +1,55 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg]]
2 +[[image:image-20221117105556-1.png]]
3 3  
4 4  
5 +
6 +
7 +
8 +
9 +
5 5  **Table of Contents：**
6 6  
12 +{{toc/}}
7 7  
8 8  
9 9  
10 10  
17 +
11 11  = 1.  Introduction =
12 12  
13 -== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
20 +== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
14 14  
15 15  
16 16  (((
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.
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 +)))
18 18  
27 +(((
28 +The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically.
29 +)))
19 19  
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.
31 +(((
32 +NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT.
33 +)))
21 21  
22 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
35 +(((
36 +NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time.
37 +)))
23 23  
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.
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 +)))
25 25  
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.
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 +)))
27 27  
28 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
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 +)))
29 29  
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.
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.
33 33  )))
34 34  
35 35  
... ... @@ -38,9 +38,10 @@
38 38  
39 39  
40 40  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
41 -* Short uplink interval for Distance Alarm
61 +* Open/Close detect
62 +* Open/Close statistics
42 42  * Monitor Battery Level
43 -* Microwave Radar for distance detection
64 +* connect two door sensors
44 44  * Datalog feature
45 45  * Uplink periodically
46 46  * Downlink to change configure
... ... @@ -51,42 +51,34 @@
51 51  * Micro SIM card slot for NB-IoT SIM
52 52  * 8500mAh Battery for long-term use
53 53  
54 -== 1.3 Radar probe specification ==
55 55  
56 56  
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°
77 +== 1.3  Storage & Operation ==
65 65  
66 66  
67 -== 1.4  Storage Temperature ==
80 +Temperature -40°C to +85°C
68 68  
69 69  
70 - -40°C to +85°C
83 +== 1.4  Mechanical ==
71 71  
72 72  
86 +[[image:image-20221117114937-4.png]]
73 73  
74 74  
89 +[[image:image-20221117114949-5.png]]
75 75  
91 +
92 +[[image:image-20221117115010-6.png]]
93 +
94 +
95 +
76 76  == 1.5 ​ Applications ==
77 77  
78 78  
99 +[[image:image-20221117114842-3.png]]
79 79  
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
89 89  
102 +
90 90  == 1.6  Specification ==
91 91  
92 92  
... ... @@ -93,62 +93,109 @@
93 93  (% style="color:blue" %)**Common DC Characteristics:**
94 94  
95 95  * Supply Voltage: 2.1v ~~ 3.6v
96 -* Operating Temperature: 0 ~~ 70°C
109 +* Operating Temperature: -40 ~~ 85°C
97 97  
98 98  (% style="color:blue" %)**NB-IoT Spec:**
99 99  
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
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
106 106  
107 -== 1.7  Installation ==
108 108  
109 109  
110 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
122 +== 1.7  Pin Definitions and Switch ==
111 111  
112 112  
113 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
125 +[[image:image-20221021110429-4.png]]
114 114  
115 115  
128 +=== 1.7.1  Pin Definition ===
116 116  
117 -== 1.8  Pin Definitions and Switch ==
118 118  
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]]
119 119  
120 -[[image:1670404362039-351.png]]
121 121  
122 122  
123 -= 2.  Use NMDS200 to communicate with IoT Server =
135 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
124 124  
137 +
138 +Power on Device when putting this jumper.
139 +
140 +
141 +
142 +=== 1.7.3  BOOT MODE / SW1 ===
143 +
144 +
145 +1)  ISP:  upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run.
146 +
147 +2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
148 +
149 +
150 +
151 +=== 1.7.4  Reset Button ===
152 +
153 +
154 +Press to reboot the device.
155 +
156 +
157 +
158 +=== 1.7.5  LED ===
159 +
160 +
161 +The LED will blink when :
162 +
163 +1.  Boot the device in flash mode
164 +
165 +2.  Send an uplink packet
166 +
167 +
168 +
169 +== 1.8  Magnet Distance ==
170 +
171 +
172 +(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
173 +
174 +(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
175 +
176 +
177 +
178 += 2.  Use NDS03A to communicate with IoT Server =
179 +
125 125  == 2.1  How it works ==
126 126  
127 127  
128 -The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
183 +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.
129 129  
130 -The diagram below shows the working flow in the default firmware of NMDS200:
185 +The diagram below shows the working flow in the default firmware of NDS03A:
131 131  
132 132  [[image:image-20221021110615-5.png]]
133 133  
134 134  
135 -== 2.2 ​ Configure NMDS200 ==
136 136  
191 +== 2.2 ​ Configure NDS03A ==
137 137  
138 -To use NMDS200 in your city, make sure to meet below requirements:
193 +=== 2.2.1 Test Requirement ===
139 139  
195 +
196 +To use NDS03A in your city, make sure to meet below requirements:
197 +
140 140  * Your local operator has already distributed an NB-IoT Network.
141 -* The local NB-IoT network used the band that NMDS200 supports.
199 +* The local NB-IoT network used the band that NDS03A supports.
142 142  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
143 143  
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.
202 +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.
145 145  
146 -[[image:image-20221207173300-4.png]]
204 +[[image:image-20221117142300-1.png]]
147 147  
206 + ​
148 148  
149 -=== 2.2.1 Insert NB-IoT SIM card ===
150 150  
209 +=== 2.2.2 Insert NB-IoT SIM card ===
151 151  
211 +
152 152  Insert the NB-IoT Card get from your provider.
153 153  
154 154  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -156,11 +156,12 @@
156 156  [[image:image-20221021110745-6.png]] ​
157 157  
158 158  
159 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
160 160  
220 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
161 161  
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.
163 163  
223 +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.
224 +
164 164  (% style="color:blue" %)**Connection:**
165 165  
166 166  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -182,11 +182,11 @@
182 182  
183 183  * Flow Control: (% style="color:red" %)**None**
184 184  
185 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
246 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
186 186  
187 187  ​[[image:image-20221021110817-7.png]]
188 188  
189 -NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
250 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
190 190  
191 191  
192 192  (% 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]]
... ... @@ -193,7 +193,7 @@
193 193  
194 194  
195 195  
196 -=== 2.2.3 Use CoAP protocol to uplink data ===
257 +=== 2.2.4 Use CoAP protocol to uplink data ===
197 197  
198 198  
199 199  (% 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/]]
... ... @@ -212,14 +212,15 @@
212 212  [[image:image-20221021110948-8.png]]
213 213  
214 214  
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.
276 +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.
216 216  
217 -[[image:1670405841875-916.png]] ​
278 +[[image:image-20221118103547-9.png||height="605" width="837"]] ​
218 218  
219 219  
220 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
221 221  
282 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
222 222  
284 +
223 223  (% style="color:blue" %)**AT Commands:**
224 224  
225 225  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -235,9 +235,10 @@
235 235  
236 236  ​
237 237  
238 -=== 2.2.5 Use MQTT protocol to uplink data ===
239 239  
301 +=== 2.2.6 Use MQTT protocol to uplink data ===
240 240  
303 +
241 241  (% style="color:blue" %)**AT Commands:**
242 242  
243 243  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -257,7 +257,7 @@
257 257  ​ [[image:image-20221118103445-7.png]]
258 258  
259 259  
260 -[[image:1670405928926-116.png]]
323 +[[image:image-20221118103453-8.png||height="608" width="841"]]
261 261  
262 262  ​
263 263  
... ... @@ -264,9 +264,10 @@
264 264  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.
265 265  
266 266  
267 -=== 2.2.6 Use TCP protocol to uplink data ===
268 268  
331 +=== 2.2.7 Use TCP protocol to uplink data ===
269 269  
333 +
270 270  (% style="color:blue" %)**AT Commands:**
271 271  
272 272  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -273,19 +273,19 @@
273 273  
274 274  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
275 275  
276 -​ [[image:1670406036256-101.png||height="676" width="713"]]
340 +​ [[image:image-20221021111125-14.png]]
277 277  
278 -
279 279  [[image:image-20221021111131-15.png]]
280 280  
281 281  ​
282 282  
283 -=== 2.2.7 Change Update Interval ===
284 284  
347 +=== 2.2.8 Change Update Interval ===
285 285  
349 +
286 286  User can use below command to change the (% style="color:blue" %)**uplink interval**.
287 287  
288 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
352 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
289 289  
290 290  (% style="color:red" %)**NOTE:**
291 291  
... ... @@ -292,54 +292,78 @@
292 292  1.  By default, the device will send an uplink message every 4 hour.
293 293  
294 294  
359 +
295 295  == 2.3  Uplink Payload ==
296 296  
297 297  
298 -The uplink payload includes 23 bytes in total by default.
363 +The uplink payload includes 26 bytes in total by default.
299 299  
300 300  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.
301 301  
367 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
302 302  
303 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
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
369 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
370 +|=(% 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**
371 +|=(% 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)
306 306  
307 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
308 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
373 +(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
374 +|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)(((
309 309  **1-32 group**
310 310  )))
311 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
377 +|(% 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" %)...
312 312  
313 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
314 314  
315 -[[image:1670406261143-723.png]]
316 316  
381 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
317 317  
318 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
319 319  
320 -**0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
384 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
385 +|=(% 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**
386 +|=(% 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)
321 321  
388 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
389 +|(% 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**
390 +|(% 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)
391 +
392 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
393 +|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
394 +**1-32 group**
395 +)))
396 +|(% 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" %)......
397 +
398 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
399 +
400 +[[image:image-20221117145932-2.png]]
401 +
402 +
403 +The payload is ASCII string, representative same HEX:
404 +
405 +**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__(%%)**
406 +
322 322  **where:**
323 323  
324 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
409 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
325 325  
326 326  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
327 327  
328 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
413 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
329 329  
330 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
415 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
331 331  
332 332  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
333 333  
334 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
419 +* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
335 335  
336 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
421 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
337 337  
338 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
423 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
339 339  
340 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
425 +* (% style="color:#037691" %)**last open time:  **(%%)0x000017 =23
341 341  
427 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
342 342  
429 +
430 +
343 343  == 2.4  Payload Explanation and Sensor Interface ==
344 344  
345 345  === 2.4.1  Device ID ===
... ... @@ -361,13 +361,13 @@
361 361  
362 362  Specify the software version: 0x64=100, which means firmware version 1.00.
363 363  
364 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
452 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
365 365  
366 366  
367 367  === 2.4.3  Battery Info ===
368 368  
369 369  
370 -Check the battery voltage for NMDS200.
458 +Check the battery voltage for NDS03A.
371 371  
372 372  Ex1: 0x0B45 = 2885mV
373 373  
... ... @@ -392,35 +392,38 @@
392 392  **99**    Not known or not detectable
393 393  
394 394  
395 -=== 2.4.5  Distance ===
483 +=== 2.4.5  Disalarm: (default: 0) ===
396 396  
397 397  
398 -[[image:1670407401682-959.png]]
486 +(% 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.
399 399  
400 -(% style="color:blue" %)**Object1 Distance:**
488 +(% 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.
401 401  
402 -Distance between sensor probe to the first object. (unit: cm)
490 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
403 403  
404 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
405 405  
406 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
493 +=== 2.4.6  Keep Status & Keep Time ===
407 407  
408 408  
409 -(% style="color:blue" %)**Object2 Distance:**
496 +Shows the configure value of Alarm Base on Timeout Feature
410 410  
411 -Distance between sensor probe to the second object. (unit: cm)
412 412  
499 +=== 2.4.7  Timestamp ===
413 413  
414 -=== 2.4.6  Timestamp ===
415 415  
416 -
417 417  Timestamp : 0x6315537b =1662342011
418 418  
419 419  
505 +=== 2.4.8  Switch Dual Channel Mode ===
506 +
507 +
508 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
509 +
510 +
420 420  == 2.5  Downlink Payload ==
421 421  
422 422  
423 -By default, NMDS200 prints the downlink payload to console port.
514 +By default, NDS03A prints the downlink payload to console port.
424 424  
425 425  [[image:image-20221021111414-18.png]] ​
426 426  
... ... @@ -437,7 +437,7 @@
437 437  
438 438  * (% style="color:#037691" %)**Reset**
439 439  
440 -If payload = 0x04FF, it will reset the NMDS200
531 +If payload = 0x04FF, it will reset the NDS03A
441 441  
442 442  * (% style="color:#037691" %)**INTMOD**
443 443  
... ... @@ -447,7 +447,7 @@
447 447  == 2.6  ​LED Indicator ==
448 448  
449 449  
450 -The NMDS200 has an internal LED which is to show the status of different states.
541 +The NDS03A has an internal LED which is to show the status of different states.
451 451  
452 452  * When the device starts normally, the LED will light up for 1 second.
453 453  * After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
... ... @@ -455,7 +455,7 @@
455 455  
456 456  
457 457  
458 -== 2.7  Distance alarm function ==
549 +== 2.7  Alarm Base on Timeout ==
459 459  
460 460  
461 461  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:
... ... @@ -514,6 +514,7 @@
514 514  [[image:image-20221021111527-19.png]]
515 515  
516 516  
608 +
517 517  == 2.10  Count Mod ==
518 518  
519 519  
... ... @@ -522,6 +522,7 @@
522 522  [[image:image-20221118092935-1.png]]
523 523  
524 524  
617 +
525 525  == 2.11  Interrupt Pin Channel Mod ==
526 526  
527 527  
... ... @@ -530,6 +530,7 @@
530 530  [[image:image-20221118093144-2.png]]
531 531  
532 532  
626 +
533 533  == 2.12 TTRIG1/2 timeout status alarm ==
534 534  
535 535  
... ... @@ -540,6 +540,7 @@
540 540  [[image:image-20221118093512-3.png]]
541 541  
542 542  
637 +
543 543  == 2.13  Select counting mode ==
544 544  
545 545  
... ... @@ -552,6 +552,8 @@
552 552  [[image:image-20221118093658-4.png]]
553 553  
554 554  
650 +
651 +
555 555  == 2.14  Set the number of data to be uploaded and the recording time ==
556 556  
557 557  
... ... @@ -574,6 +574,7 @@
574 574  [[image:image-20221118094227-5.png]]
575 575  
576 576  
674 +
577 577  == 2.16  ​Firmware Change Log ==
578 578  
579 579  
... ... @@ -582,8 +582,10 @@
582 582  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
583 583  
584 584  
683 +
585 585  == 2.17  ​Battery Analysis ==
586 586  
686 +
587 587  === 2.17.1  ​Battery Type ===
588 588  
589 589  
... ... @@ -602,6 +602,7 @@
602 602  [[image:image-20221021111911-26.png]] ​
603 603  
604 604  
705 +
605 605  === 2.17.2  Power consumption Analyze ===
606 606  
607 607  
... ... @@ -624,6 +624,7 @@
624 624  [[image:1666596205057-567.png]] ​
625 625  
626 626  
728 +
627 627  === 2.17.3  ​Battery Note ===
628 628  
629 629  
... ... @@ -630,6 +630,7 @@
630 630  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.
631 631  
632 632  
735 +
633 633  === 2.17.4  Replace the battery ===
634 634  
635 635  
... ... @@ -636,6 +636,7 @@
636 636  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).
637 637  
638 638  
742 +
639 639  = 3. ​ Access NB-IoT Module =
640 640  
641 641  
... ... @@ -643,12 +643,13 @@
643 643  
644 644  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/]] 
645 645  
646 -
647 647  [[image:image-20221118094449-6.png]] ​
648 648  
649 649  
753 +
650 650  = 4.  Using the AT Commands =
651 651  
756 +
652 652  == 4.1  Access AT Commands ==
653 653  
654 654  
... ... @@ -740,8 +740,10 @@
740 740  AT+PWORD  : Serial Access Password
741 741  
742 742  
848 +
743 743  = ​5.  FAQ =
744 744  
851 +
745 745  == 5.1 ​ How to Upgrade Firmware ==
746 746  
747 747  
... ... @@ -752,8 +752,10 @@
752 752  (% 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.**
753 753  
754 754  
862 +
755 755  = 6.  Trouble Shooting =
756 756  
865 +
757 757  == 6.1  ​Connection problem when uploading firmware ==
758 758  
759 759  
... ... @@ -760,6 +760,7 @@
760 760  (% 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]]
761 761  
762 762  
872 +
763 763  == 6.2  AT Command input doesn't work ==
764 764  
765 765  
... ... @@ -766,6 +766,7 @@
766 766  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.
767 767  
768 768  
879 +
769 769  = 7. ​ Order Info =
770 770  
771 771  
... ... @@ -772,6 +772,7 @@
772 772  Part Number**:** NDS03A
773 773  
774 774  
886 +
775 775  = 8.  Packing Info =
776 776  
777 777  
1670404362039-351.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -492.6 KB
Content
1670405841875-916.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.0 KB
Content
1670406261143-723.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content
1670407401682-959.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -23.7 KB
Content
LMDS200_10.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 KB
Content
image-20221207170748-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.1 KB
Content
image-20221207170748-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.9 KB
Content
image-20221207173200-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
image-20221207173300-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.0 KB
Content

Applications

Navigation

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