Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 80.2 >
edited by Xiaoling
on 2022/12/07 18:00
To version < 69.1 >
edited by Xiaoling
on 2022/11/18 10:34
>
Change comment: Uploaded new attachment "image-20221118103453-8.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,35 +1,55 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg]]
2 +[[image:image-20221117105556-1.png]]
3 3  
4 4  
5 +
6 +
7 +
8 +
9 +
5 5  **Table of Contents：**
6 6  
12 +{{toc/}}
7 7  
8 8  
9 9  
10 10  
17 +
11 11  = 1.  Introduction =
12 12  
13 -== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
20 +== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
14 14  
15 15  
16 16  (((
17 -The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor.
24 +The Dragino NDS03A is an (% style="color:blue" %)**Open/Close NB-IoT Door Sensor**(%%). It detects door (% style="color:blue" %)**open/close status**(%%) and (% style="color:blue" %)**uplinks**(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server.
25 +)))
18 18  
27 +(((
28 +The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically.
29 +)))
19 19  
20 -The NMDS200 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
31 +(((
32 +NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT.
33 +)))
21 21  
22 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
35 +(((
36 +NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time.
37 +)))
23 23  
24 -NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range.
39 +(((
40 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
41 +)))
25 25  
26 -NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technology**(%%) developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
43 +(((
44 +NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technologyTCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
45 +)))
27 27  
28 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
47 +(((
48 +NDS03A is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
49 +)))
29 29  
30 -NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
31 -
32 -To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection.
51 +(((
52 +To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection.
33 33  )))
34 34  
35 35  
... ... @@ -38,9 +38,10 @@
38 38  
39 39  
40 40  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
41 -* Short uplink interval for Distance Alarm
61 +* Open/Close detect
62 +* Open/Close statistics
42 42  * Monitor Battery Level
43 -* Microwave Radar for distance detection
64 +* connect two door sensors
44 44  * Datalog feature
45 45  * Uplink periodically
46 46  * Downlink to change configure
... ... @@ -51,27 +51,22 @@
51 51  * Micro SIM card slot for NB-IoT SIM
52 52  * 8500mAh Battery for long-term use
53 53  
75 +== 1.3  Storage & Operation ==
54 54  
55 -== 1.3 Radar probe specification ==
56 56  
78 +Temperature -40°C to +85°C
57 57  
58 -* Measuring Method: FMCW
59 -* Frequency: 24.000 24.500 GHz
60 -* Measurement output power: 6dBm
61 -* Measure range: 0.5 20m
62 -* Accuracy: ±0.1m
63 -* Resolution: 0.01m
64 -* Horizontal Angel: 78°
65 -* Vertical Angel: 23°
66 66  
81 +== 1.4  Mechanical ==
67 67  
68 68  
69 -== 1.4  Storage Temperature ==
84 +[[image:image-20221117114937-4.png]]
70 70  
71 71  
72 - -40°C to +85°C
87 +[[image:image-20221117114949-5.png]]
73 73  
74 74  
90 +[[image:image-20221117115010-6.png]]
75 75  
76 76  
77 77  
... ... @@ -78,16 +78,8 @@
78 78  == 1.5 ​ Applications ==
79 79  
80 80  
97 +[[image:image-20221117114842-3.png]]
81 81  
82 -* Horizontal distance measurement
83 -* Liquid level measurement
84 -* Parking management system
85 -* Object proximity and presence detection
86 -* Intelligent trash can management system
87 -* Robot obstacle avoidance
88 -* Automatic control
89 -* Sewer
90 -* Bottom water level monitoring
91 91  
92 92  
93 93  == 1.6  Specification ==
... ... @@ -96,63 +96,107 @@
96 96  (% style="color:blue" %)**Common DC Characteristics:**
97 97  
98 98  * Supply Voltage: 2.1v ~~ 3.6v
99 -* Operating Temperature: 0 ~~ 70°C
107 +* Operating Temperature: -40 ~~ 85°C
100 100  
101 101  (% style="color:blue" %)**NB-IoT Spec:**
102 102  
103 -* B1 @H-FDD: 2100MHz
104 -* B3 @H-FDD: 1800MHz
105 -* B8 @H-FDD: 900MHz
106 -* B5 @H-FDD: 850MHz
107 -* B20 @H-FDD: 800MHz
108 -* 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
109 109  
118 +== 1.7  Pin Definitions and Switch ==
110 110  
111 -== 1.7  Installation ==
112 112  
121 +[[image:image-20221021110429-4.png]]
113 113  
114 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
115 115  
124 +=== 1.7.1  Pin Definition ===
116 116  
117 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
118 118  
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]]
119 119  
120 120  
121 -== 1.8  Pin Definitions and Switch ==
122 122  
131 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
123 123  
124 -[[image:1670404362039-351.png]]
125 125  
134 +Power on Device when putting this jumper.
126 126  
127 -= 2.  Use NMDS200 to communicate with IoT Server =
128 128  
137 +
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 +
129 129  == 2.1  How it works ==
130 130  
131 131  
132 -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.
133 133  
134 -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:
135 135  
136 136  [[image:image-20221021110615-5.png]]
137 137  
138 138  
139 -== 2.2 ​ Configure NMDS200 ==
140 140  
187 +== 2.2 ​ Configure NDS03A ==
141 141  
142 -To use NMDS200 in your city, make sure to meet below requirements:
189 +=== 2.2.1 Test Requirement ===
143 143  
191 +
192 +To use NDS03A in your city, make sure to meet below requirements:
193 +
144 144  * Your local operator has already distributed an NB-IoT Network.
145 -* The local NB-IoT network used the band that NMDS200 supports.
195 +* The local NB-IoT network used the band that NDS03A supports.
146 146  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
147 147  
148 -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.
149 149  
150 -[[image:image-20221207173300-4.png]]
200 +[[image:image-20221117142300-1.png]]
151 151  
202 + ​
152 152  
153 -=== 2.2.1 Insert NB-IoT SIM card ===
154 154  
205 +=== 2.2.2 Insert NB-IoT SIM card ===
155 155  
207 +
156 156  Insert the NB-IoT Card get from your provider.
157 157  
158 158  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -160,11 +160,12 @@
160 160  [[image:image-20221021110745-6.png]] ​
161 161  
162 162  
163 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
164 164  
216 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
165 165  
166 -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.
167 167  
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 +
168 168  (% style="color:blue" %)**Connection:**
169 169  
170 170  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -186,11 +186,11 @@
186 186  
187 187  * Flow Control: (% style="color:red" %)**None**
188 188  
189 -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**(%%).
190 190  
191 191  ​[[image:image-20221021110817-7.png]]
192 192  
193 -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.
194 194  
195 195  
196 196  (% 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]]
... ... @@ -197,7 +197,7 @@
197 197  
198 198  
199 199  
200 -=== 2.2.3 Use CoAP protocol to uplink data ===
253 +=== 2.2.4 Use CoAP protocol to uplink data ===
201 201  
202 202  
203 203  (% 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/]]
... ... @@ -216,14 +216,15 @@
216 216  [[image:image-20221021110948-8.png]]
217 217  
218 218  
219 -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.
220 220  
221 -[[image:1670405841875-916.png]] ​
274 +[[image:image-20221021110956-9.png]] ​
222 222  
223 223  
224 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
225 225  
278 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
226 226  
280 +
227 227  (% style="color:blue" %)**AT Commands:**
228 228  
229 229  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -239,9 +239,10 @@
239 239  
240 240  ​
241 241  
242 -=== 2.2.5 Use MQTT protocol to uplink data ===
243 243  
297 +=== 2.2.6 Use MQTT protocol to uplink data ===
244 244  
299 +
245 245  (% style="color:blue" %)**AT Commands:**
246 246  
247 247  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -258,10 +258,10 @@
258 258  
259 259  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
260 260  
261 -​ [[image:image-20221118103445-7.png]]
316 +​ [[image:image-20221021111058-12.png]]
262 262  
263 263  
264 -[[image:1670405928926-116.png]]
319 +[[image:image-20221021111201-16.png||height="472" width="653"]]
265 265  
266 266  ​
267 267  
... ... @@ -268,9 +268,10 @@
268 268  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.
269 269  
270 270  
271 -=== 2.2.6 Use TCP protocol to uplink data ===
272 272  
327 +=== 2.2.7 Use TCP protocol to uplink data ===
273 273  
329 +
274 274  (% style="color:blue" %)**AT Commands:**
275 275  
276 276  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -277,19 +277,19 @@
277 277  
278 278  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
279 279  
280 -​ [[image:1670406036256-101.png||height="676" width="713"]]
336 +​ [[image:image-20221021111125-14.png]]
281 281  
282 -
283 283  [[image:image-20221021111131-15.png]]
284 284  
285 285  ​
286 286  
287 -=== 2.2.7 Change Update Interval ===
288 288  
343 +=== 2.2.8 Change Update Interval ===
289 289  
345 +
290 290  User can use below command to change the (% style="color:blue" %)**uplink interval**.
291 291  
292 -* (% 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)
293 293  
294 294  (% style="color:red" %)**NOTE:**
295 295  
... ... @@ -296,55 +296,74 @@
296 296  1.  By default, the device will send an uplink message every 4 hour.
297 297  
298 298  
355 +
299 299  == 2.3  Uplink Payload ==
300 300  
301 301  
302 -The uplink payload includes 23 bytes in total by default.
359 +The uplink payload includes 26 bytes in total by default.
303 303  
304 304  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.
305 305  
363 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
306 306  
307 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
308 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:90px" %)**2**|(% style="width:100px" %)**2**
309 -|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) Distance 1 |(% style="width:93px" %) Distance  2
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)
310 310  
311 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
312 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
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" %)(((
313 313  **1-32 group**
314 314  )))
315 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
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" %)...
316 316  
317 -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:**
318 318  
319 -[[image:1670406261143-723.png]]
320 320  
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)
321 321  
322 -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)
323 323  
324 -**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" %)......
325 325  
326 -**where:**
392 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
327 327  
328 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
394 +[[image:image-20221117145932-2.png]]
329 329  
330 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
331 331  
332 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
397 +The payload is ASCII string, representative same HEX:
333 333  
334 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
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__(%%)**
335 335  
336 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
401 +**where:**
337 337  
338 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
403 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
339 339  
340 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
405 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
341 341  
342 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
407 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
343 343  
344 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
409 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
345 345  
411 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
346 346  
413 +* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0
347 347  
415 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
416 +
417 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
418 +
419 +* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
420 +
421 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
422 +
348 348  == 2.4  Payload Explanation and Sensor Interface ==
349 349  
350 350  === 2.4.1  Device ID ===
... ... @@ -419,6 +419,7 @@
419 419  Timestamp : 0x6315537b =1662342011
420 420  
421 421  
497 +
422 422  === 2.4.8  Switch Dual Channel Mode ===
423 423  
424 424  
... ... @@ -452,6 +452,7 @@
452 452  Downlink Payload: 06000003, Set AT+INTMOD=3
453 453  
454 454  
531 +
455 455  == 2.6  ​LED Indicator ==
456 456  
457 457  
... ... @@ -520,6 +520,7 @@
520 520  [[image:image-20221021111527-19.png]]
521 521  
522 522  
600 +
523 523  == 2.10  Count Mod ==
524 524  
525 525  
... ... @@ -528,6 +528,7 @@
528 528  [[image:image-20221118092935-1.png]]
529 529  
530 530  
609 +
531 531  == 2.11  Interrupt Pin Channel Mod ==
532 532  
533 533  
... ... @@ -536,6 +536,7 @@
536 536  [[image:image-20221118093144-2.png]]
537 537  
538 538  
618 +
539 539  == 2.12 TTRIG1/2 timeout status alarm ==
540 540  
541 541  
... ... @@ -546,6 +546,7 @@
546 546  [[image:image-20221118093512-3.png]]
547 547  
548 548  
629 +
549 549  == 2.13  Select counting mode ==
550 550  
551 551  
... ... @@ -558,6 +558,8 @@
558 558  [[image:image-20221118093658-4.png]]
559 559  
560 560  
642 +
643 +
561 561  == 2.14  Set the number of data to be uploaded and the recording time ==
562 562  
563 563  
... ... @@ -580,16 +580,19 @@
580 580  [[image:image-20221118094227-5.png]]
581 581  
582 582  
666 +
583 583  == 2.16  ​Firmware Change Log ==
584 584  
585 585  
586 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
670 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
587 587  
588 588  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
589 589  
590 590  
675 +
591 591  == 2.17  ​Battery Analysis ==
592 592  
678 +
593 593  === 2.17.1  ​Battery Type ===
594 594  
595 595  
... ... @@ -608,6 +608,7 @@
608 608  [[image:image-20221021111911-26.png]] ​
609 609  
610 610  
697 +
611 611  === 2.17.2  Power consumption Analyze ===
612 612  
613 613  
... ... @@ -630,6 +630,7 @@
630 630  [[image:1666596205057-567.png]] ​
631 631  
632 632  
720 +
633 633  === 2.17.3  ​Battery Note ===
634 634  
635 635  
... ... @@ -636,6 +636,7 @@
636 636  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.
637 637  
638 638  
727 +
639 639  === 2.17.4  Replace the battery ===
640 640  
641 641  
... ... @@ -642,6 +642,7 @@
642 642  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).
643 643  
644 644  
734 +
645 645  = 3. ​ Access NB-IoT Module =
646 646  
647 647  
... ... @@ -649,12 +649,13 @@
649 649  
650 650  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/]] 
651 651  
652 -
653 653  [[image:image-20221118094449-6.png]] ​
654 654  
655 655  
745 +
656 656  = 4.  Using the AT Commands =
657 657  
748 +
658 658  == 4.1  Access AT Commands ==
659 659  
660 660  
... ... @@ -746,8 +746,10 @@
746 746  AT+PWORD  : Serial Access Password
747 747  
748 748  
840 +
749 749  = ​5.  FAQ =
750 750  
843 +
751 751  == 5.1 ​ How to Upgrade Firmware ==
752 752  
753 753  
... ... @@ -758,8 +758,10 @@
758 758  (% 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.**
759 759  
760 760  
854 +
761 761  = 6.  Trouble Shooting =
762 762  
857 +
763 763  == 6.1  ​Connection problem when uploading firmware ==
764 764  
765 765  
... ... @@ -766,6 +766,7 @@
766 766  (% 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]]
767 767  
768 768  
864 +
769 769  == 6.2  AT Command input doesn't work ==
770 770  
771 771  
... ... @@ -772,6 +772,7 @@
772 772  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.
773 773  
774 774  
871 +
775 775  = 7. ​ Order Info =
776 776  
777 777  
... ... @@ -778,6 +778,7 @@
778 778  Part Number**:** NDS03A
779 779  
780 780  
878 +
781 781  = 8.  Packing Info =
782 782  
783 783  
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
LMDS200_10.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 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

Applications

Navigation

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