Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 83.11 >
edited by Xiaoling
on 2022/12/08 11:33
To version < 68.1 >
edited by Xiaoling
on 2022/11/18 10:34
>
Change comment: Uploaded new attachment "image-20221118103445-7.png", version {1}

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,7 +1,12 @@
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  
7 7  {{toc/}}
... ... @@ -9,51 +9,54 @@
9 9  
10 10  
11 11  
17 +
12 12  = 1.  Introduction =
13 13  
14 -== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
20 +== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
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.
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.
19 19  )))
20 20  
21 21  (((
22 -The NMDS200 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
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.
23 23  )))
24 24  
25 25  (((
26 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
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.
27 27  )))
28 28  
29 29  (((
30 -NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range.
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.
31 31  )))
32 32  
33 33  (((
34 -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.
40 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
35 35  )))
36 36  
37 37  (((
38 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
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.
39 39  )))
40 40  
41 41  (((
42 -NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
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)
43 43  )))
44 44  
45 45  (((
46 -To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection.
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.
47 47  )))
48 48  
49 49  
56 +
50 50  == ​1.2  Features ==
51 51  
52 52  
53 53  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
54 -* Short uplink interval for Distance Alarm
61 +* Open/Close detect
62 +* Open/Close statistics
55 55  * Monitor Battery Level
56 -* Microwave Radar for distance detection
64 +* connect two door sensors
57 57  * Datalog feature
58 58  * Uplink periodically
59 59  * Downlink to change configure
... ... @@ -64,37 +64,32 @@
64 64  * Micro SIM card slot for NB-IoT SIM
65 65  * 8500mAh Battery for long-term use
66 66  
67 -== 1.3 Radar probe specification ==
75 +== 1.3  Storage & Operation ==
68 68  
69 69  
70 -* Measuring Method: FMCW
71 -* Frequency: 24.000 24.500 GHz
72 -* Measurement output power: 6dBm
73 -* Measure range: 0.5 20m
74 -* Accuracy: ±0.1m
75 -* Resolution: 0.01m
76 -* Horizontal Angel: 78°
77 -* Vertical Angel: 23°
78 +Temperature -40°C to +85°C
78 78  
79 -== 1.4  Storage Temperature ==
80 80  
81 +== 1.4  Mechanical ==
81 81  
82 - -40°C to +85°C
83 83  
84 +[[image:image-20221117114937-4.png]]
84 84  
86 +
87 +[[image:image-20221117114949-5.png]]
88 +
89 +
90 +[[image:image-20221117115010-6.png]]
91 +
92 +
93 +
85 85  == 1.5 ​ Applications ==
86 86  
87 87  
88 -* Horizontal distance measurement
89 -* Liquid level measurement
90 -* Parking management system
91 -* Object proximity and presence detection
92 -* Intelligent trash can management system
93 -* Robot obstacle avoidance
94 -* Automatic control
95 -* Sewer
96 -* Bottom water level monitoring
97 +[[image:image-20221117114842-3.png]]
97 97  
99 +
100 +
98 98  == 1.6  Specification ==
99 99  
100 100  
... ... @@ -101,65 +101,107 @@
101 101  (% style="color:blue" %)**Common DC Characteristics:**
102 102  
103 103  * Supply Voltage: 2.1v ~~ 3.6v
104 -* Operating Temperature: 0 ~~ 70°C
107 +* Operating Temperature: -40 ~~ 85°C
105 105  
106 106  (% style="color:blue" %)**NB-IoT Spec:**
107 107  
108 -* B1 @H-FDD: 2100MHz
109 -* B3 @H-FDD: 1800MHz
110 -* B8 @H-FDD: 900MHz
111 -* B5 @H-FDD: 850MHz
112 -* B20 @H-FDD: 800MHz
113 -* B28 @H-FDD: 700MHz
111 +* - B1 @H-FDD: 2100MHz
112 +* - B3 @H-FDD: 1800MHz
113 +* - B8 @H-FDD: 900MHz
114 +* - B5 @H-FDD: 850MHz
115 +* - B20 @H-FDD: 800MHz
116 +* - B28 @H-FDD: 700MHz
114 114  
115 -== 1.7  Installation ==
118 +== 1.7  Pin Definitions and Switch ==
116 116  
117 117  
118 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
121 +[[image:image-20221021110429-4.png]]
119 119  
120 120  
121 -[[image:image-20221207170748-1.png]]
124 +=== 1.7.1  Pin Definition ===
122 122  
123 123  
124 - [[image:image-20221207170748-2.png||height="345" width="634"]]
127 +The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at:  [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
125 125  
126 126  
127 127  
128 -== 1.8  Pin Definitions and Switch ==
131 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
129 129  
130 130  
131 -[[image:1670404362039-351.png]]
134 +Power on Device when putting this jumper.
132 132  
133 133  
134 -= 2.  Use NMDS200 to communicate with IoT Server =
135 135  
138 +=== 1.7.3  BOOT MODE / SW1 ===
139 +
140 +
141 +1)  ISP:  upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run.
142 +
143 +2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
144 +
145 +
146 +
147 +=== 1.7.4  Reset Button ===
148 +
149 +
150 +Press to reboot the device.
151 +
152 +
153 +
154 +=== 1.7.5  LED ===
155 +
156 +
157 +The LED will blink when :
158 +
159 +1.  Boot the device in flash mode
160 +
161 +2.  Send an uplink packet
162 +
163 +
164 +
165 +== 1.8  Magnet Distance ==
166 +
167 +
168 +(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
169 +
170 +(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
171 +
172 +
173 +
174 += 2.  Use NDS03A to communicate with IoT Server =
175 +
136 136  == 2.1  How it works ==
137 137  
138 138  
139 -The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
179 +In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.
140 140  
141 -The diagram below shows the working flow in the default firmware of NMDS200:
181 +The diagram below shows the working flow in the default firmware of NDS03A:
142 142  
143 143  [[image:image-20221021110615-5.png]]
144 144  
145 145  
146 -== 2.2 ​ Configure NMDS200 ==
147 147  
187 +== 2.2 ​ Configure NDS03A ==
148 148  
149 -To use NMDS200 in your city, make sure to meet below requirements:
189 +=== 2.2.1 Test Requirement ===
150 150  
191 +
192 +To use NDS03A in your city, make sure to meet below requirements:
193 +
151 151  * Your local operator has already distributed an NB-IoT Network.
152 -* The local NB-IoT network used the band that NMDS200 supports.
195 +* The local NB-IoT network used the band that NDS03A supports.
153 153  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
154 154  
155 -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.
198 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDS03A will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
156 156  
157 -[[image:image-20221208090742-1.png]]
200 +[[image:image-20221117142300-1.png]]
158 158  
202 + ​
159 159  
160 -=== 2.2.1 Insert NB-IoT SIM card ===
161 161  
205 +=== 2.2.2 Insert NB-IoT SIM card ===
162 162  
207 +
163 163  Insert the NB-IoT Card get from your provider.
164 164  
165 165  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -167,11 +167,12 @@
167 167  [[image:image-20221021110745-6.png]] ​
168 168  
169 169  
170 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
171 171  
216 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
172 172  
173 -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.
174 174  
219 +User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
220 +
175 175  (% style="color:blue" %)**Connection:**
176 176  
177 177  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -193,11 +193,11 @@
193 193  
194 194  * Flow Control: (% style="color:red" %)**None**
195 195  
196 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
242 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
197 197  
198 198  ​[[image:image-20221021110817-7.png]]
199 199  
200 -NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
246 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
201 201  
202 202  
203 203  (% 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]]
... ... @@ -204,13 +204,13 @@
204 204  
205 205  
206 206  
207 -=== 2.2.3 Use CoAP protocol to uplink data ===
253 +=== 2.2.4 Use CoAP protocol to uplink data ===
208 208  
209 209  
210 210  (% 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/]]
211 211  
212 212  
213 -(% style="color:blue" %)**Use below commands in NMDS200:**
259 +(% style="color:blue" %)**Use below commands in NDS03A:**
214 214  
215 215  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
216 216  
... ... @@ -223,14 +223,15 @@
223 223  [[image:image-20221021110948-8.png]]
224 224  
225 225  
226 -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.
272 +After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
227 227  
228 -[[image:1670405841875-916.png]] ​
274 +[[image:image-20221021110956-9.png]] ​
229 229  
230 230  
231 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
232 232  
278 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
233 233  
280 +
234 234  (% style="color:blue" %)**AT Commands:**
235 235  
236 236  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -246,9 +246,10 @@
246 246  
247 247  ​
248 248  
249 -=== 2.2.5 Use MQTT protocol to uplink data ===
250 250  
297 +=== 2.2.6 Use MQTT protocol to uplink data ===
251 251  
299 +
252 252  (% style="color:blue" %)**AT Commands:**
253 253  
254 254  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -265,10 +265,10 @@
265 265  
266 266  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
267 267  
268 -​ [[image:image-20221118103445-7.png]]
316 +​ [[image:image-20221021111058-12.png]]
269 269  
270 270  
271 -[[image:1670405928926-116.png]]
319 +[[image:image-20221021111201-16.png||height="472" width="653"]]
272 272  
273 273  ​
274 274  
... ... @@ -275,9 +275,10 @@
275 275  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.
276 276  
277 277  
278 -=== 2.2.6 Use TCP protocol to uplink data ===
279 279  
327 +=== 2.2.7 Use TCP protocol to uplink data ===
280 280  
329 +
281 281  (% style="color:blue" %)**AT Commands:**
282 282  
283 283  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -284,19 +284,19 @@
284 284  
285 285  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
286 286  
287 -​ [[image:1670406036256-101.png||height="676" width="713"]]
336 +​ [[image:image-20221021111125-14.png]]
288 288  
289 -
290 290  [[image:image-20221021111131-15.png]]
291 291  
292 292  ​
293 293  
294 -=== 2.2.7 Change Update Interval ===
295 295  
343 +=== 2.2.8 Change Update Interval ===
296 296  
345 +
297 297  User can use below command to change the (% style="color:blue" %)**uplink interval**.
298 298  
299 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
348 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
300 300  
301 301  (% style="color:red" %)**NOTE:**
302 302  
... ... @@ -303,53 +303,73 @@
303 303  1.  By default, the device will send an uplink message every 4 hour.
304 304  
305 305  
355 +
306 306  == 2.3  Uplink Payload ==
307 307  
308 308  
309 -The uplink payload includes 23 bytes in total by default.
359 +The uplink payload includes 26 bytes in total by default.
310 310  
311 311  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.
312 312  
363 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
313 313  
314 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %)
315 -|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:30px" %)**2**|(% style="width:30px" %)**2**|(% style="width:75px" %)**1**|(% style="width:30px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**
316 -|=(% 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"]]
365 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
366 +|=(% scope="row" style="width: 93px;" %)**Size(bytes)**|(% style="width:67px" %)**8**|(% style="width:40px" %)**2**|(% style="width:45px" %)**2**|(% style="width:75px" %)**1**|(% style="width:54px" %)**1**|(% style="width:62px" %)**1**|(% style="width:60px" %)**1**|(% style="width:94px" %)**3**|(% style="width:93px" %)**3**
367 +|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
317 317  
318 -(% border="1" style="background-color:#ffffcc; color:green; width:350px" %)
319 -|(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((
369 +(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
370 +|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)(((
320 320  **1-32 group**
321 321  )))
322 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:98px" %)...
373 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
323 323  
324 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
375 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
325 325  
326 -[[image:1670406261143-723.png]]
327 327  
378 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
379 +|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:66px" %)**8**|(% style="width:40px" %)**2**|(% style="width:46px" %)**2**|(% style="width:70px" %)**1**|(% style="width:54px" %)**1**|(% style="width:55px" %)**1**|(% style="width:57px" %)**1**|(% style="width:86px" %)**3**|(% style="width:82px" %)**3**
380 +|=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
328 328  
329 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
382 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
383 +|(% style="width:59px" %)**1**|(% style="width:67px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:66px" %)**1**|(% style="width:92px" %)**3**
384 +|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
330 330  
331 -**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__(%%)**
386 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
387 +|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
388 +**1-32 group**
389 +)))
390 +|(% style="width:102px" %)last open time (pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:88px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
332 332  
392 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
393 +
394 +[[image:image-20221117145932-2.png]]
395 +
396 +
397 +The payload is ASCII string, representative same HEX:
398 +
399 +**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)**
400 +
333 333  **where:**
334 334  
335 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
403 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
336 336  
337 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
405 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
338 338  
339 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
407 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
340 340  
341 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
409 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
342 342  
343 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
411 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
344 344  
345 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
413 +* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0
346 346  
347 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
415 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
348 348  
349 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
417 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
350 350  
351 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
419 +* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
352 352  
421 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
353 353  
354 354  == 2.4  Payload Explanation and Sensor Interface ==
355 355  
... ... @@ -372,13 +372,13 @@
372 372  
373 373  Specify the software version: 0x64=100, which means firmware version 1.00.
374 374  
375 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
444 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
376 376  
377 377  
378 378  === 2.4.3  Battery Info ===
379 379  
380 380  
381 -Check the battery voltage for NMDS200.
450 +Check the battery voltage for NDS03A.
382 382  
383 383  Ex1: 0x0B45 = 2885mV
384 384  
... ... @@ -390,49 +390,52 @@
390 390  
391 391  NB-IoT Network signal Strength.
392 392  
393 -(% style="color:blue" %)**Ex1: 0x1d = 29**
462 +**Ex1: 0x1d = 29**
394 394  
395 -(% style="color:#037691" %)**0** (%%) -113dBm or less
464 +**0**  -113dBm or less
396 396  
397 -(% style="color:#037691" %)**1**  (%%) -111dBm
466 +**1**  -111dBm
398 398  
399 -(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
468 +**2...30** -109dBm... -53dBm
400 400  
401 -(% style="color:#037691" %)**31** (%%) -51dBm or greater
470 +**31**   -51dBm or greater
402 402  
403 -(% style="color:#037691" %)**99** (%%) Not known or not detectable
472 +**99**    Not known or not detectable
404 404  
405 405  
406 -=== 2.4.5  Distance ===
475 +=== 2.4.5  Disalarm: (default: 0) ===
407 407  
408 408  
409 -[[image:1670407401682-959.png]]
478 +(% 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.
410 410  
480 +(% 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.
411 411  
412 -(% style="color:blue" %)**Object1 Distance:**
482 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
413 413  
414 -Distance between sensor probe to the first object. (unit: cm)
415 415  
416 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
485 +=== 2.4.6  Keep Status & Keep Time ===
417 417  
418 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
419 419  
488 +Shows the configure value of Alarm Base on Timeout Feature
420 420  
421 -(% style="color:blue" %)**Object2 Distance:**
422 422  
423 -Distance between sensor probe to the second object. (unit: cm)
491 +=== 2.4.7  Timestamp ===
424 424  
425 425  
426 -=== 2.4.6  Timestamp ===
494 +Timestamp : 0x6315537b =1662342011
427 427  
428 428  
429 -Timestamp : 0x6315537b =1662342011
430 430  
498 +=== 2.4.8  Switch Dual Channel Mode ===
431 431  
500 +
501 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
502 +
503 +
432 432  == 2.5  Downlink Payload ==
433 433  
434 434  
435 -By default, NMDS200 prints the downlink payload to console port.
507 +By default, NDS03A prints the downlink payload to console port.
436 436  
437 437  [[image:image-20221021111414-18.png]] ​
438 438  
... ... @@ -449,7 +449,7 @@
449 449  
450 450  * (% style="color:#037691" %)**Reset**
451 451  
452 -If payload = 0x04FF, it will reset the NMDS200
524 +If payload = 0x04FF, it will reset the NDS03A
453 453  
454 454  * (% style="color:#037691" %)**INTMOD**
455 455  
... ... @@ -456,36 +456,122 @@
456 456  Downlink Payload: 06000003, Set AT+INTMOD=3
457 457  
458 458  
531 +
459 459  == 2.6  ​LED Indicator ==
460 460  
461 461  
462 -The NMDS200 has an internal LED which is to show the status of different states.
535 +The NDS03A has an internal LED which is to show the status of different states.
463 463  
464 464  * When the device starts normally, the LED will light up for 1 second.
465 -* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
538 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
466 466  * For each uplink probe, LED will be on for 500ms.
467 467  
541 +== 2.7  Alarm Base on Timeout ==
468 468  
469 -== 2.7  Distance alarm function ==
470 470  
544 +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:
471 471  
472 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
473 473  
474 -(% style="color:#037691" %)**Example 1:**
547 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
475 475  
476 -AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
549 +Keep Status = 1: Monitor Close to Open event
477 477  
478 -AT+ ALARM2 =min,max
551 +Keep Status = 0: Monitor Open to Close event
479 479  
480 480  
481 -(% style="color:#037691" %)**Example 2:**
554 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
482 482  
483 -AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
556 +Range 0 ~~ 65535(0xFFFF) seconds.
484 484  
558 +If keep time = 0, Disable Alarm Base on Timeout feature.
485 485  
486 -== 2.8  Set the number of data to be uploaded and the recording time ==
560 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
487 487  
488 488  
563 +(% style="color:blue" %)**AT Command to configure:**
564 +
565 +(% style="color:blue" %)**PB14 PIN:**
566 +
567 +(% 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.
568 +
569 +(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
570 +
571 +
572 +(% style="color:blue" %)**PB15 PIN:**
573 +
574 +(% style="color:#037691" %)**AT+TTRIG2=1,30**
575 +
576 +(% style="color:#037691" %)**AT+TTRIG2=0,0 **
577 +
578 +
579 +== 2.8  Set debug mode ==
580 +
581 +
582 +Feature: Enable or Disable debug mode
583 +
584 +(% style="color:blue" %)**AT Command: AT+DEBUG**
585 +
586 +[[image:image-20221021111629-21.png]]
587 +
588 +
589 +
590 +== 2.9  Clear Flash Record ==
591 +
592 +
593 +Feature: Clear flash storage for data log feature.
594 +
595 +(% style="color:blue" %)**AT Command: AT+CLRDTA**
596 +
597 +[[image:image-20221021111527-19.png]]
598 +
599 +
600 +
601 +== 2.10  Count Mod ==
602 +
603 +
604 +(% style="color:blue" %)**AT Command: AT+COUNTMOD**
605 +
606 +[[image:image-20221118092935-1.png]]
607 +
608 +
609 +
610 +== 2.11  Interrupt Pin Channel Mod ==
611 +
612 +
613 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
614 +
615 +[[image:image-20221118093144-2.png]]
616 +
617 +
618 +
619 +== 2.12 TTRIG1/2 timeout status alarm ==
620 +
621 +
622 +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.
623 +
624 +(% style="color:blue" %)**AT Command: AT+TTRALARM**
625 +
626 +[[image:image-20221118093512-3.png]]
627 +
628 +
629 +
630 +== 2.13  Select counting mode ==
631 +
632 +
633 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
634 +
635 +When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
636 +
637 +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.
638 +
639 +[[image:image-20221118093658-4.png]]
640 +
641 +
642 +
643 +
644 +== 2.14  Set the number of data to be uploaded and the recording time ==
645 +
646 +
489 489  (% style="color:blue" %)**AT Command:**
490 490  
491 491  (% 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)
... ... @@ -493,7 +493,7 @@
493 493  (% 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.
494 494  
495 495  
496 -== 2.9  Read or Clear cached data ==
654 +== 2.15  Read or Clear cached data ==
497 497  
498 498  
499 499  (% style="color:blue" %)**AT Command:**
... ... @@ -502,24 +502,27 @@
502 502  
503 503  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
504 504  
505 -[[image:1670408172929-569.png]]
663 +[[image:image-20221118094227-5.png]]
506 506  
507 507  
508 -== 2.10  ​Firmware Change Log ==
509 509  
667 +== 2.16  ​Firmware Change Log ==
510 510  
511 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
512 512  
670 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
671 +
513 513  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
514 514  
515 515  
516 -== 2.11  ​Battery Analysis ==
517 517  
518 -=== 2.11.1  ​Battery Type ===
676 +== 2.17  ​Battery Analysis ==
519 519  
520 520  
521 -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.
679 +=== 2.17.1  ​Battery Type ===
522 522  
681 +
682 +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.
683 +
523 523  The battery is designed to last for several years depends on the actual use environment and update interval. 
524 524  
525 525  The battery-related documents as below:
... ... @@ -533,9 +533,10 @@
533 533  [[image:image-20221021111911-26.png]] ​
534 534  
535 535  
536 -=== 2.11.2  Power consumption Analyze ===
537 537  
698 +=== 2.17.2  Power consumption Analyze ===
538 538  
700 +
539 539  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.
540 540  
541 541  Instruction to use as below:
... ... @@ -555,18 +555,21 @@
555 555  [[image:1666596205057-567.png]] ​
556 556  
557 557  
558 -=== 2.11.3  ​Battery Note ===
559 559  
721 +=== 2.17.3  ​Battery Note ===
560 560  
723 +
561 561  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.
562 562  
563 563  
564 -=== 2.11.4  Replace the battery ===
565 565  
728 +=== 2.17.4  Replace the battery ===
566 566  
567 -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).
568 568  
731 +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).
569 569  
733 +
734 +
570 570  = 3. ​ Access NB-IoT Module =
571 571  
572 572  
... ... @@ -574,12 +574,13 @@
574 574  
575 575  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/]] 
576 576  
577 -
578 578  [[image:image-20221118094449-6.png]] ​
579 579  
580 580  
745 +
581 581  = 4.  Using the AT Commands =
582 582  
748 +
583 583  == 4.1  Access AT Commands ==
584 584  
585 585  
... ... @@ -610,63 +610,71 @@
610 610  
611 611  AT+INTMOD            : Set the trigger interrupt mode
612 612  
613 -AT+5VT  : Set extend the time of 5V power  
779 +AT+5VT  : Set extend the time of 5V power  
614 614  
615 -AT+PRO  : Choose agreement
781 +AT+PRO  : Choose agreement
616 616  
617 -AT+RXDL  : Extend the sending and receiving time
783 +AT+RXDL  : Extend the sending and receiving time
618 618  
619 -AT+SERVADDR  : Server Address
785 +AT+SERVADDR  : Server Address
620 620  
621 -AT+TR      :  Get or Set record time
787 +AT+TR      :  Get or Set record time
622 622  
623 -AT+NOUD :  Get or Set the number of data to be uploaded
789 +AT+NOUD      : Get or Set the number of data to be uploaded
624 624  
625 625  AT+CDP     :  Read or Clear cached data
626 626  
627 -AT+DEBUG:  Enable or Disable debug mode
793 +AT+ DEBUG   : Enable or Disable debug mode
628 628  
629 -AT+ALARM1:  Get or Set alarm of distance1
795 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
630 630  
631 -AT+ALARM2:  Get or Set alarm of distance2
797 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
632 632  
633 -AT+GETSENSORVALUE :  Returns the current sensor measurement
799 +AT+COUNTMOD  :  Get or Set the count mode
634 634  
635 -AT+POWERIC :  Get or set the Power IC flag
801 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
636 636  
803 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
637 637  
805 +AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
806 +
807 +AT+ CLRC   :  Clear current door open count
808 +
809 +
638 638  (% style="color:blue" %)**COAP Management**      
639 639  
640 -AT+URI :  Resource parameters
812 +AT+URI            : Resource parameters
641 641  
642 642  
643 643  (% style="color:blue" %)**UDP Management**
644 644  
645 -AT+CFM :  Upload confirmation mode (only valid for UDP)
817 +AT+CFM          : Upload confirmation mode (only valid for UDP)
646 646  
647 647  
648 648  (% style="color:blue" %)**MQTT Management**
649 649  
650 -AT+CLIENT  : Get or Set MQTT client
822 +AT+CLIENT               : Get or Set MQTT client
651 651  
652 -AT+UNAME : Get or Set MQTT Username
824 +AT+UNAME  : Get or Set MQTT Username
653 653  
654 -AT+PWD  :  Get or Set MQTT password
826 +AT+PWD                  : Get or Set MQTT password
655 655  
656 -AT+PUBTOPIC :  Get or Set MQTT publish topic
828 +AT+PUBTOPIC  : Get or Set MQTT publish topic
657 657  
658 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
830 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
659 659  
660 660  
661 661  (% style="color:blue" %)**Information**          
662 662  
663 -AT+FDR :  Factory Data Reset
835 +AT+FDR  : Factory Data Reset
664 664  
665 -AT+PWORD :  Serial Access Password
837 +AT+PWORD  : Serial Access Password
666 666  
667 667  
840 +
668 668  = ​5.  FAQ =
669 669  
843 +
670 670  == 5.1 ​ How to Upgrade Firmware ==
671 671  
672 672  
... ... @@ -674,11 +674,13 @@
674 674  
675 675  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]]
676 676  
677 -(% 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.**
851 +(% 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.**
678 678  
679 679  
854 +
680 680  = 6.  Trouble Shooting =
681 681  
857 +
682 682  == 6.1  ​Connection problem when uploading firmware ==
683 683  
684 684  
... ... @@ -685,6 +685,7 @@
685 685  (% 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]]
686 686  
687 687  
864 +
688 688  == 6.2  AT Command input doesn't work ==
689 689  
690 690  
... ... @@ -691,20 +691,21 @@
691 691  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.
692 692  
693 693  
871 +
694 694  = 7. ​ Order Info =
695 695  
696 696  
697 -Part Number:(% style="color:blue" %)** NMDS200**
875 +Part Number**:** NDS03A
698 698  
699 699  
878 +
700 700  = 8.  Packing Info =
701 701  
702 702  
703 703  (% style="color:blue" %)**Package Includes**:
704 704  
705 -* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
884 +* NDS03A Open/Close Door Sensor x 1
706 706  
707 -
708 708  = 9.  Support =
709 709  
710 710  
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
LMDS200_10.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.5 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