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

Summary

Details

Page properties
Content
... ... @@ -4,7 +4,6 @@
4 4  
5 5  **Table of Contents：**
6 6  
7 -{{toc/}}
8 8  
9 9  
10 10  
... ... @@ -15,31 +15,51 @@
15 15  
16 16  
17 17  (((
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.
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 +)))
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.
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 +)))
21 21  
22 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
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 +)))
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.
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 +)))
25 25  
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 +(((
26 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.
38 +)))
27 27  
28 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
40 +(((
41 +NDS03A supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
42 +)))
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)
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)
46 +)))
31 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.
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.
33 33  )))
34 34  
35 35  
53 +
36 36  == ​1.2  Features ==
37 37  
38 38  
39 39  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
40 -* Short uplink interval for Distance Alarm
58 +* Open/Close detect
59 +* Open/Close statistics
41 41  * Monitor Battery Level
42 -* Microwave Radar for distance detection
61 +* connect two door sensors
43 43  * Datalog feature
44 44  * Uplink periodically
45 45  * Downlink to change configure
... ... @@ -50,37 +50,33 @@
50 50  * Micro SIM card slot for NB-IoT SIM
51 51  * 8500mAh Battery for long-term use
52 52  
53 -== 1.3 Radar probe specification ==
54 54  
73 +== 1.3  Storage & Operation ==
55 55  
56 -* Measuring Method: FMCW
57 -* Frequency: 24.000 24.500 GHz
58 -* Measurement output power: 6dBm
59 -* Measure range: 0.5 20m
60 -* Accuracy: ±0.1m
61 -* Resolution: 0.01m
62 -* Horizontal Angel: 78°
63 -* Vertical Angel: 23°
64 64  
65 -== 1.4  Storage Temperature ==
76 +Temperature -40°C to +85°C
66 66  
67 67  
68 - -40°C to +85°C
79 +== 1.4  Mechanical ==
69 69  
70 70  
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 +
71 71  == 1.5 ​ Applications ==
72 72  
73 73  
74 -* Horizontal distance measurement
75 -* Liquid level measurement
76 -* Parking management system
77 -* Object proximity and presence detection
78 -* Intelligent trash can management system
79 -* Robot obstacle avoidance
80 -* Automatic control
81 -* Sewer
82 -* Bottom water level monitoring
95 +[[image:image-20221117114842-3.png]]
83 83  
97 +
98 +
84 84  == 1.6  Specification ==
85 85  
86 86  
... ... @@ -87,7 +87,7 @@
87 87  (% style="color:blue" %)**Common DC Characteristics:**
88 88  
89 89  * Supply Voltage: 2.1v ~~ 3.6v
90 -* Operating Temperature: 0 ~~ 70°C
105 +* Operating Temperature: -40 ~~ 85°C
91 91  
92 92  (% style="color:blue" %)**NB-IoT Spec:**
93 93  
... ... @@ -98,49 +98,86 @@
98 98  * B20 @H-FDD: 800MHz
99 99  * B28 @H-FDD: 700MHz
100 100  
101 -== 1.7  Installation ==
102 102  
117 +== 1.7  Pin Definitions and Switch ==
103 103  
104 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
105 105  
120 +[[image:image-20221021110429-4.png]]
106 106  
107 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
108 108  
123 +=== 1.7.1  Pin Definition ===
109 109  
110 110  
111 -== 1.8  Pin Definitions and Switch ==
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]]
112 112  
113 113  
114 -[[image:1670404362039-351.png]]
129 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
115 115  
116 116  
117 -= 2.  Use NMDS200 to communicate with IoT Server =
132 +Power on Device when putting this jumper.
118 118  
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 +
119 119  == 2.1  How it works ==
120 120  
121 121  
122 -The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
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.
123 123  
124 -The diagram below shows the working flow in the default firmware of NMDS200:
174 +The diagram below shows the working flow in the default firmware of NDS03A:
125 125  
126 126  [[image:image-20221021110615-5.png]]
127 127  
128 128  
129 -== 2.2 ​ Configure NMDS200 ==
179 +== 2.2 ​ Configure NDS03A ==
130 130  
181 +=== 2.2.1 Test Requirement ===
131 131  
132 -To use NMDS200 in your city, make sure to meet below requirements:
133 133  
184 +To use NDS03A in your city, make sure to meet below requirements:
185 +
134 134  * Your local operator has already distributed an NB-IoT Network.
135 -* The local NB-IoT network used the band that NMDS200 supports.
187 +* The local NB-IoT network used the band that NDS03A supports.
136 136  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
137 137  
138 -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.
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.
139 139  
140 -[[image:image-20221208090742-1.png]]
192 +[[image:image-20221117142300-1.png]]
141 141  
142 142  
143 -=== 2.2.1 Insert NB-IoT SIM card ===
195 +=== 2.2.2 Insert NB-IoT SIM card ===
144 144  
145 145  
146 146  Insert the NB-IoT Card get from your provider.
... ... @@ -150,10 +150,10 @@
150 150  [[image:image-20221021110745-6.png]] ​
151 151  
152 152  
153 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
205 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
154 154  
155 155  
156 -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.
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.
157 157  
158 158  (% style="color:blue" %)**Connection:**
159 159  
... ... @@ -176,11 +176,11 @@
176 176  
177 177  * Flow Control: (% style="color:red" %)**None**
178 178  
179 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
231 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
180 180  
181 181  ​[[image:image-20221021110817-7.png]]
182 182  
183 -NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
235 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
184 184  
185 185  
186 186  (% 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]]
... ... @@ -187,13 +187,13 @@
187 187  
188 188  
189 189  
190 -=== 2.2.3 Use CoAP protocol to uplink data ===
242 +=== 2.2.4 Use CoAP protocol to uplink data ===
191 191  
192 192  
193 193  (% 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/]]
194 194  
195 195  
196 -(% style="color:blue" %)**Use below commands in NMDS200:**
248 +(% style="color:blue" %)**Use below commands in NDS03A:**
197 197  
198 198  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
199 199  
... ... @@ -206,12 +206,12 @@
206 206  [[image:image-20221021110948-8.png]]
207 207  
208 208  
209 -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.
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.
210 210  
211 -[[image:1670405841875-916.png]] ​
263 +[[image:image-20221118103547-9.png||height="605" width="837"]] ​
212 212  
213 213  
214 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
266 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
215 215  
216 216  
217 217  (% style="color:blue" %)**AT Commands:**
... ... @@ -229,7 +229,7 @@
229 229  
230 230  ​
231 231  
232 -=== 2.2.5 Use MQTT protocol to uplink data ===
284 +=== 2.2.6 Use MQTT protocol to uplink data ===
233 233  
234 234  
235 235  (% style="color:blue" %)**AT Commands:**
... ... @@ -251,7 +251,7 @@
251 251  ​ [[image:image-20221118103445-7.png]]
252 252  
253 253  
254 -[[image:1670405928926-116.png]]
306 +[[image:image-20221118103453-8.png||height="608" width="841"]]
255 255  
256 256  ​
257 257  
... ... @@ -258,7 +258,7 @@
258 258  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.
259 259  
260 260  
261 -=== 2.2.6 Use TCP protocol to uplink data ===
313 +=== 2.2.7 Use TCP protocol to uplink data ===
262 262  
263 263  
264 264  (% style="color:blue" %)**AT Commands:**
... ... @@ -267,19 +267,18 @@
267 267  
268 268  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
269 269  
270 -​ [[image:1670406036256-101.png||height="676" width="713"]]
322 +​ [[image:image-20221021111125-14.png]]
271 271  
272 -
273 273  [[image:image-20221021111131-15.png]]
274 274  
275 275  ​
276 276  
277 -=== 2.2.7 Change Update Interval ===
328 +=== 2.2.8 Change Update Interval ===
278 278  
279 279  
280 280  User can use below command to change the (% style="color:blue" %)**uplink interval**.
281 281  
282 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
333 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
283 283  
284 284  (% style="color:red" %)**NOTE:**
285 285  
... ... @@ -289,50 +289,71 @@
289 289  == 2.3  Uplink Payload ==
290 290  
291 291  
292 -The uplink payload includes 23 bytes in total by default.
343 +The uplink payload includes 26 bytes in total by default.
293 293  
294 294  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.
295 295  
347 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
296 296  
297 297  (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
298 -|=(% 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**
299 -|=(% 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"]]
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)
300 300  
301 -(% border="1" style="background-color:#ffffcc; color:green; width:471px" %)
302 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:98px" %)(((
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" %)(((
303 303  **1-32 group**
304 304  )))
305 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:98px" %)...
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" %)...
306 306  
307 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
359 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
308 308  
309 -[[image:1670406261143-723.png]]
310 310  
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)
311 311  
312 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
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)
313 313  
314 -**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__(%%)**
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" %)......
315 315  
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 +
316 316  **where:**
317 317  
318 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
387 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
319 319  
320 320  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
321 321  
322 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
391 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
323 323  
324 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
393 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
325 325  
326 326  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
327 327  
328 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
397 +* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
329 329  
330 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
399 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
331 331  
332 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
401 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
333 333  
334 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
403 +* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
335 335  
405 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
406 +
407 +
336 336  == 2.4  Payload Explanation and Sensor Interface ==
337 337  
338 338  === 2.4.1  Device ID ===
... ... @@ -354,13 +354,13 @@
354 354  
355 355  Specify the software version: 0x64=100, which means firmware version 1.00.
356 356  
357 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
429 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
358 358  
359 359  
360 360  === 2.4.3  Battery Info ===
361 361  
362 362  
363 -Check the battery voltage for NMDS200.
435 +Check the battery voltage for NDS03A.
364 364  
365 365  Ex1: 0x0B45 = 2885mV
366 366  
... ... @@ -372,49 +372,51 @@
372 372  
373 373  NB-IoT Network signal Strength.
374 374  
375 -(% style="color:blue" %)**Ex1: 0x1d = 29**
447 +**Ex1: 0x1d = 29**
376 376  
377 -(% style="color:#037691" %)**0** (%%) -113dBm or less
449 +**0**  -113dBm or less
378 378  
379 -(% style="color:#037691" %)**1**  (%%) -111dBm
451 +**1**  -111dBm
380 380  
381 -(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
453 +**2...30** -109dBm... -53dBm
382 382  
383 -(% style="color:#037691" %)**31** (%%) -51dBm or greater
455 +**31**   -51dBm or greater
384 384  
385 -(% style="color:#037691" %)**99** (%%) Not known or not detectable
457 +**99**    Not known or not detectable
386 386  
387 387  
388 -=== 2.4.5  Distance ===
460 +=== 2.4.5  Disalarm: (default: 0) ===
389 389  
390 390  
391 -[[image:1670407401682-959.png]]
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.
392 392  
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.
393 393  
394 -(% style="color:blue" %)**Object1 Distance:**
467 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
395 395  
396 -Distance between sensor probe to the first object. (unit: cm)
397 397  
398 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
470 +=== 2.4.6  Keep Status & Keep Time ===
399 399  
400 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
401 401  
473 +Shows the configure value of Alarm Base on Timeout Feature
402 402  
403 -(% style="color:blue" %)**Object2 Distance:**
404 404  
405 -Distance between sensor probe to the second object. (unit: cm)
476 +=== 2.4.7  Timestamp ===
406 406  
407 407  
408 -=== 2.4.6  Timestamp ===
479 +Timestamp : 0x6315537b =1662342011
409 409  
410 410  
411 -Timestamp : 0x6315537b =1662342011
482 +=== 2.4.8  Switch Dual Channel Mode ===
412 412  
413 413  
485 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
486 +
487 +
414 414  == 2.5  Downlink Payload ==
415 415  
416 416  
417 -By default, NMDS200 prints the downlink payload to console port.
491 +By default, NDS03A prints the downlink payload to console port.
418 418  
419 419  [[image:image-20221021111414-18.png]] ​
420 420  
... ... @@ -431,7 +431,7 @@
431 431  
432 432  * (% style="color:#037691" %)**Reset**
433 433  
434 -If payload = 0x04FF, it will reset the NMDS200
508 +If payload = 0x04FF, it will reset the NDS03A
435 435  
436 436  * (% style="color:#037691" %)**INTMOD**
437 437  
... ... @@ -441,33 +441,113 @@
441 441  == 2.6  ​LED Indicator ==
442 442  
443 443  
444 -The NMDS200 has an internal LED which is to show the status of different states.
518 +The NDS03A has an internal LED which is to show the status of different states.
445 445  
446 446  * When the device starts normally, the LED will light up for 1 second.
447 -* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
521 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
448 448  * For each uplink probe, LED will be on for 500ms.
449 449  
450 450  
451 -== 2.7  Distance alarm function ==
525 +== 2.7  Alarm Base on Timeout ==
452 452  
453 453  
454 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
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:
455 455  
456 -(% style="color:#037691" %)**Example 1:**
457 457  
458 -AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
531 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
459 459  
460 -AT+ ALARM2 =min,max
533 +Keep Status = 1: Monitor Close to Open event
461 461  
535 +Keep Status = 0: Monitor Open to Close event
462 462  
463 -(% style="color:#037691" %)**Example 2:**
464 464  
465 -AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
538 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
466 466  
540 +Range 0 ~~ 65535(0xFFFF) seconds.
467 467  
468 -== 2.8  Set the number of data to be uploaded and the recording time ==
542 +If keep time = 0, Disable Alarm Base on Timeout feature.
469 469  
544 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
470 470  
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 +
471 471  (% style="color:blue" %)**AT Command:**
472 472  
473 473  (% 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)
... ... @@ -475,7 +475,7 @@
475 475  (% 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.
476 476  
477 477  
478 -== 2.9  Read or Clear cached data ==
632 +== 2.15  Read or Clear cached data ==
479 479  
480 480  
481 481  (% style="color:blue" %)**AT Command:**
... ... @@ -484,10 +484,10 @@
484 484  
485 485  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
486 486  
487 -[[image:1670408172929-569.png]]
641 +[[image:image-20221118094227-5.png]]
488 488  
489 489  
490 -== 2.10  ​Firmware Change Log ==
644 +== 2.16  ​Firmware Change Log ==
491 491  
492 492  
493 493  Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
... ... @@ -495,12 +495,12 @@
495 495  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
496 496  
497 497  
498 -== 2.11  ​Battery Analysis ==
652 +== 2.17  ​Battery Analysis ==
499 499  
500 -=== 2.11.1  ​Battery Type ===
654 +=== 2.17.1  ​Battery Type ===
501 501  
502 502  
503 -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.
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.
504 504  
505 505  The battery is designed to last for several years depends on the actual use environment and update interval. 
506 506  
... ... @@ -515,7 +515,7 @@
515 515  [[image:image-20221021111911-26.png]] ​
516 516  
517 517  
518 -=== 2.11.2  Power consumption Analyze ===
672 +=== 2.17.2  Power consumption Analyze ===
519 519  
520 520  
521 521  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.
... ... @@ -537,16 +537,16 @@
537 537  [[image:1666596205057-567.png]] ​
538 538  
539 539  
540 -=== 2.11.3  ​Battery Note ===
694 +=== 2.17.3  ​Battery Note ===
541 541  
542 542  
543 543  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.
544 544  
545 545  
546 -=== 2.11.4  Replace the battery ===
700 +=== 2.17.4  Replace the battery ===
547 547  
548 548  
549 -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).
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).
550 550  
551 551  
552 552  = 3. ​ Access NB-IoT Module =
... ... @@ -600,51 +600,57 @@
600 600  
601 601  AT+SERVADDR  : Server Address
602 602  
603 -AT+TR      :  Get or Set record time
757 +AT+TR      :  Get or Set record time
604 604  
605 -AT+NOUD :  Get or Set the number of data to be uploaded
759 +AT+NOUD      : Get or Set the number of data to be uploaded
606 606  
607 607  AT+CDP     :  Read or Clear cached data
608 608  
609 -AT+DEBUG:  Enable or Disable debug mode
763 +AT+ DEBUG   : Enable or Disable debug mode
610 610  
611 -AT+ALARM1:  Get or Set alarm of distance1
765 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
612 612  
613 -AT+ALARM2:  Get or Set alarm of distance2
767 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
614 614  
615 -AT+GETSENSORVALUE :  Returns the current sensor measurement
769 +AT+COUNTMOD  :  Get or Set the count mode
616 616  
617 -AT+POWERIC :  Get or set the Power IC flag
771 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
618 618  
773 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
619 619  
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 +
620 620  (% style="color:blue" %)**COAP Management**      
621 621  
622 -AT+URI :  Resource parameters
782 +AT+URI            : Resource parameters
623 623  
624 624  
625 625  (% style="color:blue" %)**UDP Management**
626 626  
627 -AT+CFM :  Upload confirmation mode (only valid for UDP)
787 +AT+CFM          : Upload confirmation mode (only valid for UDP)
628 628  
629 629  
630 630  (% style="color:blue" %)**MQTT Management**
631 631  
632 -AT+CLIENT  : Get or Set MQTT client
792 +AT+CLIENT               : Get or Set MQTT client
633 633  
634 -AT+UNAME : Get or Set MQTT Username
794 +AT+UNAME  : Get or Set MQTT Username
635 635  
636 -AT+PWD  :  Get or Set MQTT password
796 +AT+PWD                  : Get or Set MQTT password
637 637  
638 -AT+PUBTOPIC :  Get or Set MQTT publish topic
798 +AT+PUBTOPIC  : Get or Set MQTT publish topic
639 639  
640 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
800 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
641 641  
642 642  
643 643  (% style="color:blue" %)**Information**          
644 644  
645 -AT+FDR :  Factory Data Reset
805 +AT+FDR  : Factory Data Reset
646 646  
647 -AT+PWORD :  Serial Access Password
807 +AT+PWORD  : Serial Access Password
648 648  
649 649  
650 650  = ​5.  FAQ =
... ... @@ -656,7 +656,7 @@
656 656  
657 657  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]]
658 658  
659 -(% 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.**
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.**
660 660  
661 661  
662 662  = 6.  Trouble Shooting =
... ... @@ -676,7 +676,7 @@
676 676  = 7. ​ Order Info =
677 677  
678 678  
679 -Part Number:(% style="color:blue" %)** NMDS200**
839 +Part Number**:** NDS03A
680 680  
681 681  
682 682  = 8.  Packing Info =
... ... @@ -684,8 +684,9 @@
684 684  
685 685  (% style="color:blue" %)**Package Includes**:
686 686  
687 -* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
847 +* NDS03A Open/Close Door Sensor x 1
688 688  
849 +
689 689  = 9.  Support =
690 690  
691 691  
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
1670408172929-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -211.8 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
image-20221208090742-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.7 KB
Content

Applications

Navigation

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