Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 90.14 >
edited by Xiaoling
on 2023/05/26 10:16
To version < 74.1 >
edited by Xiaoling
on 2022/12/07 17:12
>
Change comment: Uploaded new attachment "1670404362039-351.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,28 +1,13 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg||height="572" width="572"]]
2 +[[image:LMDS200_10.jpg]]
3 3  
4 4  
5 -
6 -
7 -
8 -(% style="display:none" %) (%%)
9 -
10 -
11 -
12 -
13 -
14 14  **Table of Contents：**
15 15  
16 -{{toc/}}
17 17  
18 18  
19 19  
20 20  
21 -
22 -
23 -
24 -
25 -
26 26  = 1.  Introduction =
27 27  
28 28  == 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
... ... @@ -29,45 +29,51 @@
29 29  
30 30  
31 31  (((
32 -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.
33 33  )))
34 34  
35 35  (((
36 -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.
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.
37 37  )))
38 38  
39 39  (((
40 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
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.
41 41  )))
42 42  
43 43  (((
44 -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.
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.
45 45  )))
46 46  
47 47  (((
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 +(((
48 48  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.
49 49  )))
50 50  
51 51  (((
52 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
41 +NDS03A supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
53 53  )))
54 54  
55 55  (((
56 -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)
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)
57 57  )))
58 58  
59 59  (((
60 -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.
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.
61 61  )))
62 62  
63 63  
53 +
64 64  == ​1.2  Features ==
65 65  
66 66  
67 67  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
68 -* Short uplink interval for Distance Alarm
58 +* Open/Close detect
59 +* Open/Close statistics
69 69  * Monitor Battery Level
70 -* Microwave Radar for distance detection
61 +* connect two door sensors
71 71  * Datalog feature
72 72  * Uplink periodically
73 73  * Downlink to change configure
... ... @@ -78,37 +78,33 @@
78 78  * Micro SIM card slot for NB-IoT SIM
79 79  * 8500mAh Battery for long-term use
80 80  
81 -== 1.3 Radar probe specification ==
82 82  
73 +== 1.3  Storage & Operation ==
83 83  
84 -* Measuring Method: FMCW
85 -* Frequency: 24.000 ~~ 24.500 GHz
86 -* Measurement output power: 6dBm
87 -* Measure range: 0.5 ~~ 20m
88 -* Accuracy: ±0.1m
89 -* Resolution: 0.01m
90 -* Horizontal Angel: 78°
91 -* Vertical Angel: 23°
92 92  
93 -== 1.4  Storage Temperature ==
76 +Temperature -40°C to +85°C
94 94  
95 95  
96 - -40°C to +85°C
79 +== 1.4  Mechanical ==
97 97  
98 98  
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 +
99 99  == 1.5 ​ Applications ==
100 100  
101 101  
102 -* Horizontal distance measurement
103 -* Liquid level measurement
104 -* Parking management system
105 -* Object proximity and presence detection
106 -* Intelligent trash can management system
107 -* Robot obstacle avoidance
108 -* Automatic control
109 -* Sewer
110 -* Bottom water level monitoring
95 +[[image:image-20221117114842-3.png]]
111 111  
97 +
98 +
112 112  == 1.6  Specification ==
113 113  
114 114  
... ... @@ -115,7 +115,7 @@
115 115  (% style="color:blue" %)**Common DC Characteristics:**
116 116  
117 117  * Supply Voltage: 2.1v ~~ 3.6v
118 -* Operating Temperature: 0 ~~ 70°C
105 +* Operating Temperature: -40 ~~ 85°C
119 119  
120 120  (% style="color:blue" %)**NB-IoT Spec:**
121 121  
... ... @@ -126,51 +126,86 @@
126 126  * B20 @H-FDD: 800MHz
127 127  * B28 @H-FDD: 700MHz
128 128  
129 -== 1.7  Installation ==
130 130  
117 +== 1.7  Pin Definitions and Switch ==
131 131  
132 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
133 133  
120 +[[image:image-20221021110429-4.png]]
134 134  
135 -[[image:image-20221207170748-1.png]]
136 136  
123 +=== 1.7.1  Pin Definition ===
137 137  
138 - [[image:image-20221207170748-2.png||height="345" width="634"]]
139 139  
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]]
140 140  
141 -== 1.8  Pin Definitions and Switch ==
142 142  
129 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
143 143  
144 -[[image:1670404362039-351.png]]
145 145  
132 +Power on Device when putting this jumper.
146 146  
147 -= 2.  Use NMDS200 to communicate with IoT Server =
148 148  
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 +
149 149  == 2.1  How it works ==
150 150  
151 151  
152 -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.
153 153  
154 -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:
155 155  
156 -[[image:image-20221021110615-5.png||height="996" width="492"]]
176 +[[image:image-20221021110615-5.png]]
157 157  
158 158  
159 -== 2.2 ​ Configure NMDS200 ==
179 +== 2.2 ​ Configure NDS03A ==
160 160  
181 +=== 2.2.1 Test Requirement ===
161 161  
162 -To use NMDS200 in your city, make sure to meet below requirements:
163 163  
184 +To use NDS03A in your city, make sure to meet below requirements:
185 +
164 164  * Your local operator has already distributed an NB-IoT Network.
165 -* The local NB-IoT network used the band that NMDS200 supports.
187 +* The local NB-IoT network used the band that NDS03A supports.
166 166  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
167 167  
168 -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.
169 169  
170 -[[image:image-20221209090938-1.png]]
192 +[[image:image-20221117142300-1.png]]
171 171  
172 172  
173 -=== 2.2.1 Insert NB-IoT SIM card ===
195 +=== 2.2.2 Insert NB-IoT SIM card ===
174 174  
175 175  
176 176  Insert the NB-IoT Card get from your provider.
... ... @@ -180,10 +180,10 @@
180 180  [[image:image-20221021110745-6.png]] ​
181 181  
182 182  
183 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
205 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
184 184  
185 185  
186 -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.
187 187  
188 188  (% style="color:blue" %)**Connection:**
189 189  
... ... @@ -206,23 +206,24 @@
206 206  
207 207  * Flow Control: (% style="color:red" %)**None**
208 208  
209 -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**(%%).
210 210  
211 211  ​[[image:image-20221021110817-7.png]]
212 212  
213 -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.
214 214  
215 215  
216 216  (% 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]]
217 217  
218 218  
219 -=== 2.2.3 Use CoAP protocol to uplink data ===
220 220  
242 +=== 2.2.4 Use CoAP protocol to uplink data ===
221 221  
244 +
222 222  (% 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/]]
223 223  
224 224  
225 -(% style="color:blue" %)**Use below commands in NMDS200:**
248 +(% style="color:blue" %)**Use below commands in NDS03A:**
226 226  
227 227  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
228 228  
... ... @@ -232,15 +232,15 @@
232 232  
233 233  For parameter description, please refer to AT command set
234 234  
235 -[[image:1670471530120-960.png||height="647" width="674"]]
258 +[[image:image-20221021110948-8.png]]
236 236  
237 237  
238 -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.
239 239  
240 -[[image:1670405841875-916.png]] ​
263 +[[image:image-20221118103547-9.png||height="605" width="837"]] ​
241 241  
242 242  
243 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
266 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
244 244  
245 245  
246 246  (% style="color:blue" %)**AT Commands:**
... ... @@ -251,7 +251,7 @@
251 251  
252 252  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
253 253  
254 -​ [[image:1670471559211-638.png]]
277 +​ [[image:image-20221021111025-10.png]]
255 255  
256 256  
257 257  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -258,7 +258,7 @@
258 258  
259 259  ​
260 260  
261 -=== 2.2.5 Use MQTT protocol to uplink data ===
284 +=== 2.2.6 Use MQTT protocol to uplink data ===
262 262  
263 263  
264 264  (% style="color:blue" %)**AT Commands:**
... ... @@ -277,10 +277,10 @@
277 277  
278 278  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
279 279  
280 -​ [[image:1670471584490-640.png]]
303 +​ [[image:image-20221118103445-7.png]]
281 281  
282 282  
283 -[[image:1670405928926-116.png]]
306 +[[image:image-20221118103453-8.png||height="608" width="841"]]
284 284  
285 285  ​
286 286  
... ... @@ -287,7 +287,7 @@
287 287  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.
288 288  
289 289  
290 -=== 2.2.6 Use TCP protocol to uplink data ===
313 +=== 2.2.7 Use TCP protocol to uplink data ===
291 291  
292 292  
293 293  (% style="color:blue" %)**AT Commands:**
... ... @@ -296,19 +296,18 @@
296 296  
297 297  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
298 298  
299 -​ [[image:1670471613823-833.png]]
322 +​ [[image:image-20221021111125-14.png]]
300 300  
301 -
302 302  [[image:image-20221021111131-15.png]]
303 303  
304 304  ​
305 305  
306 -=== 2.2.7 Change Update Interval ===
328 +=== 2.2.8 Change Update Interval ===
307 307  
308 308  
309 309  User can use below command to change the (% style="color:blue" %)**uplink interval**.
310 310  
311 -* (% 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)
312 312  
313 313  (% style="color:red" %)**NOTE:**
314 314  
... ... @@ -318,48 +318,71 @@
318 318  == 2.3  Uplink Payload ==
319 319  
320 320  
321 -The uplink payload includes 23 bytes in total by default.
343 +The uplink payload includes 26 bytes in total by default.
322 322  
323 323  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.
324 324  
347 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
325 325  
326 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
327 -|=(% scope="row" style="width: 60px;background-color:#4F81BD;color:white" %)**Size(bytes)**|(% style="width:50px;background-color:#4F81BD;color:white" %)**8**|(% style="width:30px;background-color:#4F81BD;color:white" %)**2**|(% style="width:30px;background-color:#4F81BD;color:white" %)**2**|(% style="width:75px;background-color:#4F81BD;color:white" %)**1**|(% style="width:30px;background-color:#4F81BD;color:white" %)**1**|(% style="width:50px;background-color:#4F81BD;color:white" %)**1**|(% style="width:60px;background-color:#4F81BD;color:white" %)**2**|(% style="width:60px;background-color:#4F81BD;color:white" %)**2**
328 -|=(% 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"]]
349 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
350 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**1**|(% style="width:90px" %)**3**|(% style="width:100px" %)**3**
351 +|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
329 329  
330 -(% border="1" style="background-color:#f2f2f2; width:429px" %)
331 -|(% style="width:60px;background-color:#4F81BD;color:white" %)**4**|(% style="width:60px;background-color:#4F81BD;color:white" %)**2**|(% style="width:60px;background-color:#4F81BD;color:white" %)**2**|(% style="width:60px;background-color:#4F81BD;color:white" %)**4**|(% style="width:100px;background-color:#4F81BD;color:white" %)(((
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" %)(((
332 332  **1-32 group**
333 333  )))
334 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...
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" %)...
335 335  
336 -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:**
337 337  
338 -[[image:1670406261143-723.png]]
339 339  
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)
340 340  
341 -The payload is ASCII string, representative same HEX: **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__(%%)**
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)
342 342  
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" %)......
375 +
376 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
377 +
378 +[[image:image-20221117145932-2.png]]
379 +
380 +
381 +The payload is ASCII string, representative same HEX:
382 +
383 +**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)**
384 +
343 343  **where:**
344 344  
345 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
387 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
346 346  
347 347  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
348 348  
349 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
391 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
350 350  
351 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
393 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
352 352  
353 353  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
354 354  
355 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
397 +* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
356 356  
357 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
399 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
358 358  
359 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
401 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
360 360  
361 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
403 +* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
362 362  
405 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
406 +
407 +
363 363  == 2.4  Payload Explanation and Sensor Interface ==
364 364  
365 365  === 2.4.1  Device ID ===
... ... @@ -381,13 +381,13 @@
381 381  
382 382  Specify the software version: 0x64=100, which means firmware version 1.00.
383 383  
384 -For example 0x00 64 : This device is NMDS200 with firmware version 1.0.0.
429 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
385 385  
386 386  
387 387  === 2.4.3  Battery Info ===
388 388  
389 389  
390 -Check the battery voltage for NMDS200.
435 +Check the battery voltage for NDS03A.
391 391  
392 392  Ex1: 0x0B45 = 2885mV
393 393  
... ... @@ -399,55 +399,53 @@
399 399  
400 400  NB-IoT Network signal Strength.
401 401  
402 -(% style="color:blue" %)**Ex1: 0x1d = 29**
447 +**Ex1: 0x1d = 29**
403 403  
404 -(% style="color:#037691" %)**0** (%%) -113dBm or less
449 +**0**  -113dBm or less
405 405  
406 -(% style="color:#037691" %)**1**  (%%) -111dBm
451 +**1**  -111dBm
407 407  
408 -(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
453 +**2...30** -109dBm... -53dBm
409 409  
410 -(% style="color:#037691" %)**31** (%%) -51dBm or greater
455 +**31**   -51dBm or greater
411 411  
412 -(% style="color:#037691" %)**99** (%%) Not known or not detectable
457 +**99**    Not known or not detectable
413 413  
414 414  
415 -=== 2.4.5  Distance ===
460 +=== 2.4.5  Disalarm: (default: 0) ===
416 416  
417 417  
418 -[[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.
419 419  
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.
420 420  
421 -(% 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.
422 422  
423 -Distance between sensor probe to the first object. (unit: cm)
424 424  
425 -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 ===
426 426  
427 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
428 428  
473 +Shows the configure value of Alarm Base on Timeout Feature
429 429  
430 -(% style="color:blue" %)**Object2 Distance:**
431 431  
432 -Distance between sensor probe to the second object. (unit: cm)
476 +=== 2.4.7  Timestamp ===
433 433  
434 434  
435 -=== 2.4.6  Timestamp ===
479 +Timestamp : 0x6315537b =1662342011
436 436  
437 437  
438 -Timestamp : 0x6315537b =1662342011
482 +=== 2.4.8  Switch Dual Channel Mode ===
439 439  
440 440  
485 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
486 +
487 +
441 441  == 2.5  Downlink Payload ==
442 442  
443 443  
444 -By default, NMDS200 prints the downlink payload to console port.
491 +By default, NDS03A prints the downlink payload to console port.
445 445  
446 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
447 -|(% style="background-color:#d9e2f3; color:#0070c0" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:97px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:183px" %)**Downlink payload size(bytes)**
448 -|TDC (Transmit Time Interval)|Any|(% style="width:97px" %)01|(% style="width:183px" %)4
449 -|RESET|Any|(% style="width:97px" %)04|(% style="width:183px" %)2
450 -|INTMOD|Any|(% style="width:97px" %)06|(% style="width:183px" %)4
493 +[[image:image-20221021111414-18.png]] ​
451 451  
452 452  
453 453  **Examples:**
... ... @@ -462,7 +462,7 @@
462 462  
463 463  * (% style="color:#037691" %)**Reset**
464 464  
465 -If payload = 0x04FF, it will reset the NMDS200
508 +If payload = 0x04FF, it will reset the NDS03A
466 466  
467 467  * (% style="color:#037691" %)**INTMOD**
468 468  
... ... @@ -472,32 +472,113 @@
472 472  == 2.6  ​LED Indicator ==
473 473  
474 474  
475 -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.
476 476  
477 477  * When the device starts normally, the LED will light up for 1 second.
478 -* 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.
479 479  * For each uplink probe, LED will be on for 500ms.
480 480  
481 -== 2.7  Distance alarm function ==
482 482  
525 +== 2.7  Alarm Base on Timeout ==
483 483  
484 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
485 485  
486 -(% style="color:#037691" %)**Example 1:**
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:
487 487  
488 -AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
489 489  
490 -AT+ ALARM2 =min,max
531 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
491 491  
533 +Keep Status = 1: Monitor Close to Open event
492 492  
493 -(% style="color:#037691" %)**Example 2:**
535 +Keep Status = 0: Monitor Open to Close event
494 494  
495 -AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
496 496  
538 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
497 497  
498 -== 2.8  Set the number of data to be uploaded and the recording time ==
540 +Range 0 ~~ 65535(0xFFFF) seconds.
499 499  
542 +If keep time = 0, Disable Alarm Base on Timeout feature.
500 500  
544 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
545 +
546 +
547 +(% style="color:blue" %)**AT Command to configure:**
548 +
549 +(% style="color:blue" %)**PB14 PIN:**
550 +
551 +(% style="color:#037691" %)**AT+TTRIG=1,30** (%%) **~-~->**  When the **Keep Status** change from connected to disconnect, and device remains in disconnect status for more than 30 seconds. NDS03A will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
552 +
553 +(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
554 +
555 +
556 +(% style="color:blue" %)**PB15 PIN:**
557 +
558 +(% style="color:#037691" %)**AT+TTRIG2=1,30**
559 +
560 +(% style="color:#037691" %)**AT+TTRIG2=0,0 **
561 +
562 +
563 +== 2.8  Set debug mode ==
564 +
565 +
566 +Feature: Enable or Disable debug mode
567 +
568 +(% style="color:blue" %)**AT Command: AT+DEBUG**
569 +
570 +[[image:image-20221021111629-21.png]]
571 +
572 +
573 +
574 +== 2.9  Clear Flash Record ==
575 +
576 +
577 +Feature: Clear flash storage for data log feature.
578 +
579 +(% style="color:blue" %)**AT Command: AT+CLRDTA**
580 +
581 +[[image:image-20221021111527-19.png]]
582 +
583 +
584 +== 2.10  Count Mod ==
585 +
586 +
587 +(% style="color:blue" %)**AT Command: AT+COUNTMOD**
588 +
589 +[[image:image-20221118092935-1.png]]
590 +
591 +
592 +== 2.11  Interrupt Pin Channel Mod ==
593 +
594 +
595 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
596 +
597 +[[image:image-20221118093144-2.png]]
598 +
599 +
600 +== 2.12 TTRIG1/2 timeout status alarm ==
601 +
602 +
603 +It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval.
604 +
605 +(% style="color:blue" %)**AT Command: AT+TTRALARM**
606 +
607 +[[image:image-20221118093512-3.png]]
608 +
609 +
610 +== 2.13  Select counting mode ==
611 +
612 +
613 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
614 +
615 +When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
616 +
617 +When (% style="color:red" %)**b=0**(%%), it is the last door open duration, and when (% style="color:red" %)**b=1**(%%),the last door close duration.
618 +
619 +[[image:image-20221118093658-4.png]]
620 +
621 +
622 +== 2.14  Set the number of data to be uploaded and the recording time ==
623 +
624 +
501 501  (% style="color:blue" %)**AT Command:**
502 502  
503 503  (% 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)
... ... @@ -505,7 +505,7 @@
505 505  (% 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.
506 506  
507 507  
508 -== 2.9  Read or Clear cached data ==
632 +== 2.15  Read or Clear cached data ==
509 509  
510 510  
511 511  (% style="color:blue" %)**AT Command:**
... ... @@ -514,25 +514,71 @@
514 514  
515 515  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
516 516  
517 -[[image:1670408172929-569.png]]
641 +[[image:image-20221118094227-5.png]]
518 518  
519 519  
520 -== 2.10  ​Firmware Change Log ==
644 +== 2.16  ​Firmware Change Log ==
521 521  
522 522  
523 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]
647 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
524 524  
525 525  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
526 526  
527 527  
528 -== 2.11 Battery & Power Consumption ==
652 +== 2.17  ​Battery Analysis ==
529 529  
654 +=== 2.17.1  ​Battery Type ===
530 530  
531 -NMDS200 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
532 532  
533 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
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.
534 534  
659 +The battery is designed to last for several years depends on the actual use environment and update interval. 
535 535  
661 +The battery-related documents as below:
662 +
663 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
664 +
665 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
666 +
667 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
668 +
669 +[[image:image-20221021111911-26.png]] ​
670 +
671 +
672 +=== 2.17.2  Power consumption Analyze ===
673 +
674 +
675 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
676 +
677 +Instruction to use as below:
678 +
679 +(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
680 +
681 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
682 +
683 +* Product Model
684 +
685 +* Uplink Interval
686 +
687 +* Working Mode
688 +
689 +And the Life expectation in difference case will be shown on the right.
690 +
691 +[[image:1666596205057-567.png]] ​
692 +
693 +
694 +=== 2.17.3  ​Battery Note ===
695 +
696 +
697 +The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
698 +
699 +
700 +=== 2.17.4  Replace the battery ===
701 +
702 +
703 +The default battery pack of NDS03A includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
704 +
705 +
536 536  = 3. ​ Access NB-IoT Module =
537 537  
538 538  
... ... @@ -576,59 +576,65 @@
576 576  
577 577  AT+INTMOD            : Set the trigger interrupt mode
578 578  
579 -AT+5VT  : Set extend the time of 5V power  
749 +AT+5VT  : Set extend the time of 5V power  
580 580  
581 -AT+PRO  : Choose agreement
751 +AT+PRO  : Choose agreement
582 582  
583 -AT+RXDL  : Extend the sending and receiving time
753 +AT+RXDL  : Extend the sending and receiving time
584 584  
585 -AT+SERVADDR  : Server Address
755 +AT+SERVADDR  : Server Address
586 586  
587 -AT+TR      :  Get or Set record time
757 +AT+TR      :  Get or Set record time
588 588  
589 -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
590 590  
591 591  AT+CDP     :  Read or Clear cached data
592 592  
593 -AT+DEBUG:  Enable or Disable debug mode
763 +AT+ DEBUG   : Enable or Disable debug mode
594 594  
595 -AT+ALARM1:  Get or Set alarm of distance1
765 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
596 596  
597 -AT+ALARM2:  Get or Set alarm of distance2
767 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
598 598  
599 -AT+GETSENSORVALUE :  Returns the current sensor measurement
769 +AT+COUNTMOD  :  Get or Set the count mode
600 600  
601 -AT+POWERIC :  Get or set the Power IC flag
771 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
602 602  
773 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
603 603  
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 +
604 604  (% style="color:blue" %)**COAP Management**      
605 605  
606 -AT+URI :  Resource parameters
782 +AT+URI            : Resource parameters
607 607  
608 608  
609 609  (% style="color:blue" %)**UDP Management**
610 610  
611 -AT+CFM :  Upload confirmation mode (only valid for UDP)
787 +AT+CFM          : Upload confirmation mode (only valid for UDP)
612 612  
613 613  
614 614  (% style="color:blue" %)**MQTT Management**
615 615  
616 -AT+CLIENT  : Get or Set MQTT client
792 +AT+CLIENT               : Get or Set MQTT client
617 617  
618 -AT+UNAME : Get or Set MQTT Username
794 +AT+UNAME  : Get or Set MQTT Username
619 619  
620 -AT+PWD  :  Get or Set MQTT password
796 +AT+PWD                  : Get or Set MQTT password
621 621  
622 -AT+PUBTOPIC :  Get or Set MQTT publish topic
798 +AT+PUBTOPIC  : Get or Set MQTT publish topic
623 623  
624 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
800 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
625 625  
626 626  
627 627  (% style="color:blue" %)**Information**          
628 628  
629 -AT+FDR :  Factory Data Reset
805 +AT+FDR  : Factory Data Reset
630 630  
631 -AT+PWORD :  Serial Access Password
807 +AT+PWORD  : Serial Access Password
632 632  
633 633  
634 634  = ​5.  FAQ =
... ... @@ -640,7 +640,7 @@
640 640  
641 641  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]]
642 642  
643 -(% 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.**
644 644  
645 645  
646 646  = 6.  Trouble Shooting =
... ... @@ -657,16 +657,10 @@
657 657  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.
658 658  
659 659  
660 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
661 -
662 -
663 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
664 -
665 -
666 666  = 7. ​ Order Info =
667 667  
668 668  
669 -Part Number:(% style="color:blue" %)** NMDS200**
839 +Part Number**:** NDS03A
670 670  
671 671  
672 672  = 8.  Packing Info =
... ... @@ -674,8 +674,9 @@
674 674  
675 675  (% style="color:blue" %)**Package Includes**:
676 676  
677 -* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
847 +* NDS03A Open/Close Door Sensor x 1
678 678  
849 +
679 679  = 9.  Support =
680 680  
681 681  
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
1670471530120-960.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -67.6 KB
Content
1670471559211-638.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -170.6 KB
Content
1670471584490-640.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.1 KB
Content
1670471613823-833.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.0 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
image-20221209090938-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -121.9 KB
Content
image-20221212171610-1.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -756.0 KB
Content

Applications

Navigation

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