Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 77.1 >
edited by Xiaoling
on 2022/12/07 17:37
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,48 +51,32 @@
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 55  
56 -== 1.3 Radar probe specification ==
78 +Temperature -40°C to +85°C
57 57  
58 58  
59 -* Measuring Method: FMCW
60 -* Frequency: 24.000 24.500 GHz
61 -* Measurement output power: 6dBm
62 -* Measure range: 0.5 20m
63 -* Accuracy: ±0.1m
64 -* Resolution: 0.01m
65 -* Horizontal Angel: 78°
66 -* Vertical Angel: 23°
81 +== 1.4  Mechanical ==
67 67  
68 68  
84 +[[image:image-20221117114937-4.png]]
69 69  
70 70  
71 -== 1.4  Storage Temperature ==
87 +[[image:image-20221117114949-5.png]]
72 72  
73 73  
74 - -40°C to +85°C
90 +[[image:image-20221117115010-6.png]]
75 75  
76 76  
77 77  
78 -
79 -
80 80  == 1.5 ​ Applications ==
81 81  
82 82  
97 +[[image:image-20221117114842-3.png]]
83 83  
84 -* Horizontal distance measurement
85 -* Liquid level measurement
86 -* Parking management system
87 -* Object proximity and presence detection
88 -* Intelligent trash can management system
89 -* Robot obstacle avoidance
90 -* Automatic control
91 -* Sewer
92 -* Bottom water level monitoring
93 93  
94 94  
95 -
96 96  == 1.6  Specification ==
97 97  
98 98  
... ... @@ -99,64 +99,107 @@
99 99  (% style="color:blue" %)**Common DC Characteristics:**
100 100  
101 101  * Supply Voltage: 2.1v ~~ 3.6v
102 -* Operating Temperature: 0 ~~ 70°C
107 +* Operating Temperature: -40 ~~ 85°C
103 103  
104 104  (% style="color:blue" %)**NB-IoT Spec:**
105 105  
106 -* B1 @H-FDD: 2100MHz
107 -* B3 @H-FDD: 1800MHz
108 -* B8 @H-FDD: 900MHz
109 -* B5 @H-FDD: 850MHz
110 -* B20 @H-FDD: 800MHz
111 -* 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
112 112  
118 +== 1.7  Pin Definitions and Switch ==
113 113  
114 114  
115 -== 1.7  Installation ==
121 +[[image:image-20221021110429-4.png]]
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.
124 +=== 1.7.1  Pin Definition ===
119 119  
120 120  
121 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
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]]
122 122  
123 123  
124 124  
125 -== 1.8  Pin Definitions and Switch ==
131 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
126 126  
127 127  
128 -[[image:1670404362039-351.png]]
134 +Power on Device when putting this jumper.
129 129  
130 130  
131 -= 2.  Use NMDS200 to communicate with IoT Server =
132 132  
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 +
133 133  == 2.1  How it works ==
134 134  
135 135  
136 -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.
137 137  
138 -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:
139 139  
140 140  [[image:image-20221021110615-5.png]]
141 141  
142 142  
143 -== 2.2 ​ Configure NMDS200 ==
144 144  
187 +== 2.2 ​ Configure NDS03A ==
145 145  
146 -To use NMDS200 in your city, make sure to meet below requirements:
189 +=== 2.2.1 Test Requirement ===
147 147  
191 +
192 +To use NDS03A in your city, make sure to meet below requirements:
193 +
148 148  * Your local operator has already distributed an NB-IoT Network.
149 -* The local NB-IoT network used the band that NMDS200 supports.
195 +* The local NB-IoT network used the band that NDS03A supports.
150 150  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
151 151  
152 -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.
153 153  
154 -[[image:image-20221207173300-4.png]]
200 +[[image:image-20221117142300-1.png]]
155 155  
202 + ​
156 156  
157 -=== 2.2.1 Insert NB-IoT SIM card ===
158 158  
205 +=== 2.2.2 Insert NB-IoT SIM card ===
159 159  
207 +
160 160  Insert the NB-IoT Card get from your provider.
161 161  
162 162  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -164,6 +164,7 @@
164 164  [[image:image-20221021110745-6.png]] ​
165 165  
166 166  
215 +
167 167  === 2.2.3 Connect USB – TTL to NDS03A and configure it ===
168 168  
169 169  
... ... @@ -222,9 +222,10 @@
222 222  
223 223  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.
224 224  
225 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
274 +[[image:image-20221021110956-9.png]] ​
226 226  
227 227  
277 +
228 228  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
229 229  
230 230  
... ... @@ -243,6 +243,7 @@
243 243  
244 244  ​
245 245  
296 +
246 246  === 2.2.6 Use MQTT protocol to uplink data ===
247 247  
248 248  
... ... @@ -262,10 +262,10 @@
262 262  
263 263  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
264 264  
265 -​ [[image:image-20221118103445-7.png]]
316 +​ [[image:image-20221021111058-12.png]]
266 266  
267 267  
268 -[[image:image-20221118103453-8.png||height="608" width="841"]]
319 +[[image:image-20221021111201-16.png||height="472" width="653"]]
269 269  
270 270  ​
271 271  
... ... @@ -272,6 +272,7 @@
272 272  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.
273 273  
274 274  
326 +
275 275  === 2.2.7 Use TCP protocol to uplink data ===
276 276  
277 277  
... ... @@ -287,6 +287,7 @@
287 287  
288 288  ​
289 289  
342 +
290 290  === 2.2.8 Change Update Interval ===
291 291  
292 292  
... ... @@ -299,6 +299,7 @@
299 299  1.  By default, the device will send an uplink message every 4 hour.
300 300  
301 301  
355 +
302 302  == 2.3  Uplink Payload ==
303 303  
304 304  
... ... @@ -308,12 +308,12 @@
308 308  
309 309  (% style="color:blue" %)**When AT+TTRCHANNEL=1:**
310 310  
311 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
312 -|=(% 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**
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**
313 313  |=(% 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)
314 314  
315 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
316 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% 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" %)(((
317 317  **1-32 group**
318 318  )))
319 319  |(% 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" %)...
... ... @@ -321,19 +321,19 @@
321 321  (% style="color:blue" %)**When AT+TTRCHANNEL=2:**
322 322  
323 323  
324 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
325 -|=(% 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**
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**
326 326  |=(% 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)
327 327  
328 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
329 -|(% 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**
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**
330 330  |(% 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)
331 331  
332 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
333 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
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" %)(((
334 334  **1-32 group**
335 335  )))
336 -|(% 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" %)......
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" %)......
337 337  
338 338  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
339 339  
... ... @@ -348,21 +348,21 @@
348 348  
349 349  * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
350 350  
351 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
405 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
352 352  
353 353  * (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
354 354  
355 355  * (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
356 356  
357 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
411 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
358 358  
359 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
413 +* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0
360 360  
361 361  * (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
362 362  
363 363  * (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
364 364  
365 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
419 +* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
366 366  
367 367  * (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
368 368  
... ... @@ -440,6 +440,7 @@
440 440  Timestamp : 0x6315537b =1662342011
441 441  
442 442  
497 +
443 443  === 2.4.8  Switch Dual Channel Mode ===
444 444  
445 445  
... ... @@ -473,6 +473,7 @@
473 473  Downlink Payload: 06000003, Set AT+INTMOD=3
474 474  
475 475  
531 +
476 476  == 2.6  ​LED Indicator ==
477 477  
478 478  
... ... @@ -541,6 +541,7 @@
541 541  [[image:image-20221021111527-19.png]]
542 542  
543 543  
600 +
544 544  == 2.10  Count Mod ==
545 545  
546 546  
... ... @@ -549,6 +549,7 @@
549 549  [[image:image-20221118092935-1.png]]
550 550  
551 551  
609 +
552 552  == 2.11  Interrupt Pin Channel Mod ==
553 553  
554 554  
... ... @@ -557,6 +557,7 @@
557 557  [[image:image-20221118093144-2.png]]
558 558  
559 559  
618 +
560 560  == 2.12 TTRIG1/2 timeout status alarm ==
561 561  
562 562  
... ... @@ -567,6 +567,7 @@
567 567  [[image:image-20221118093512-3.png]]
568 568  
569 569  
629 +
570 570  == 2.13  Select counting mode ==
571 571  
572 572  
... ... @@ -579,6 +579,8 @@
579 579  [[image:image-20221118093658-4.png]]
580 580  
581 581  
642 +
643 +
582 582  == 2.14  Set the number of data to be uploaded and the recording time ==
583 583  
584 584  
... ... @@ -601,16 +601,19 @@
601 601  [[image:image-20221118094227-5.png]]
602 602  
603 603  
666 +
604 604  == 2.16  ​Firmware Change Log ==
605 605  
606 606  
607 -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]]
608 608  
609 609  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
610 610  
611 611  
675 +
612 612  == 2.17  ​Battery Analysis ==
613 613  
678 +
614 614  === 2.17.1  ​Battery Type ===
615 615  
616 616  
... ... @@ -629,6 +629,7 @@
629 629  [[image:image-20221021111911-26.png]] ​
630 630  
631 631  
697 +
632 632  === 2.17.2  Power consumption Analyze ===
633 633  
634 634  
... ... @@ -651,6 +651,7 @@
651 651  [[image:1666596205057-567.png]] ​
652 652  
653 653  
720 +
654 654  === 2.17.3  ​Battery Note ===
655 655  
656 656  
... ... @@ -657,6 +657,7 @@
657 657  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.
658 658  
659 659  
727 +
660 660  === 2.17.4  Replace the battery ===
661 661  
662 662  
... ... @@ -663,6 +663,7 @@
663 663  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).
664 664  
665 665  
734 +
666 666  = 3. ​ Access NB-IoT Module =
667 667  
668 668  
... ... @@ -670,12 +670,13 @@
670 670  
671 671  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/]] 
672 672  
673 -
674 674  [[image:image-20221118094449-6.png]] ​
675 675  
676 676  
745 +
677 677  = 4.  Using the AT Commands =
678 678  
748 +
679 679  == 4.1  Access AT Commands ==
680 680  
681 681  
... ... @@ -767,8 +767,10 @@
767 767  AT+PWORD  : Serial Access Password
768 768  
769 769  
840 +
770 770  = ​5.  FAQ =
771 771  
843 +
772 772  == 5.1 ​ How to Upgrade Firmware ==
773 773  
774 774  
... ... @@ -779,8 +779,10 @@
779 779  (% 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.**
780 780  
781 781  
854 +
782 782  = 6.  Trouble Shooting =
783 783  
857 +
784 784  == 6.1  ​Connection problem when uploading firmware ==
785 785  
786 786  
... ... @@ -787,6 +787,7 @@
787 787  (% 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]]
788 788  
789 789  
864 +
790 790  == 6.2  AT Command input doesn't work ==
791 791  
792 792  
... ... @@ -793,6 +793,7 @@
793 793  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.
794 794  
795 795  
871 +
796 796  = 7. ​ Order Info =
797 797  
798 798  
... ... @@ -799,6 +799,7 @@
799 799  Part Number**:** NDS03A
800 800  
801 801  
878 +
802 802  = 8.  Packing Info =
803 803  
804 804  
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
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-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0