Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 53.1 >
edited by Xiaoling
on 2022/11/17 10:55
To version < 74.2 >
edited by Xiaoling
on 2022/12/07 17:12
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
1 +NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
Content
... ... @@ -1,46 +1,37 @@
1 1  (% style="text-align:center" %)
2 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/WebHome/1652856952171-363.png?rev=1.1||alt="1652856952171-363.png" height="578" width="588"]]
2 +[[image:LMDS200_10.jpg]]
3 3  
4 4  
5 -
6 6  **Table of Contents：**
7 7  
8 -{{toc/}}
9 9  
10 10  
11 11  
12 12  
13 -
14 14  = 1.  Introduction =
15 15  
13 +== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
16 16  
17 -== 1.1 ​ What is CPN01 NB-IoT Pulse/Contact Sensor ==
18 18  
19 -
20 20  (((
21 -The Dragino CPN01 is an (% style="color:blue" %)**NB-IoT Dry Contact Sensor**(%%). It detects open/close status and uplinks the info to IoT server via NB-IoT network. User can see the (% style="color:blue" %)**dry contact status, open time, and open counts**(%%) in the IoT Server.
22 -)))
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.
23 23  
24 -(((
25 -The CPN01 will send periodically data every day as well as for each dry contact action. It also counts the contact open times and calculates the last open duration. Users can also disable the uplink for each Open/Close event, instead, device can count each open event and uplink periodically.
26 -)))
27 27  
28 -(((
29 -CPN01 has** (% style="color:blue" %)Open-Alarm feature(%%)**, user can set this feature so CPN01 will send an alarm if the contact has been open exceeds a certain time.
30 -)))
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 31  
32 -(((
33 -CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures.
34 -)))
22 +NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
35 35  
36 -(((
37 -NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
38 -\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
39 -\\CPN01 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)
40 -\\To use CPN01, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that CPN01 supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into CPN01 to get NB-IoT network connection.
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.
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.
27 +
28 +NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
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.
41 41  )))
42 42  
43 -​
44 44  
45 45  
46 46  == ​1.2  Features ==
... ... @@ -47,10 +47,9 @@
47 47  
48 48  
49 49  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
50 -* Open/Close detect
51 -* Open/Close statistics
41 +* Short uplink interval for Distance Alarm
52 52  * Monitor Battery Level
53 -* Uplink on periodically and open/close event
43 +* Microwave Radar for distance detection
54 54  * Datalog feature
55 55  * Uplink periodically
56 56  * Downlink to change configure
... ... @@ -61,135 +61,109 @@
61 61  * Micro SIM card slot for NB-IoT SIM
62 62  * 8500mAh Battery for long-term use
63 63  
54 +== 1.3 Radar probe specification ==
64 64  
65 65  
66 -== 1.3  Specification ==
57 +Measuring Method: FMCW
58 +Frequency: 24.000 24.500 GHz
59 +Measurement output power: 6dBm
60 +Measure range: 0.5 20m
61 +Accuracy: ±0.1m
62 +Resolution: 0.01m
63 +Horizontal Angel: 78°
64 +Vertical Angel: 23°
67 67  
68 68  
69 -(% style="color:blue" %)**Common DC Characteristics:**
70 70  
71 -* Supply Voltage: 2.1v ~~ 3.6v
72 -* Operating Temperature: -40 ~~ 85°C
73 73  
74 -(% style="color:blue" %)**NB-IoT Spec:**
69 +== 1.4  Storage Temperature ==
75 75  
76 -* - B1 @H-FDD: 2100MHz
77 -* - B3 @H-FDD: 1800MHz
78 -* - B8 @H-FDD: 900MHz
79 -* - B5 @H-FDD: 850MHz
80 -* - B20 @H-FDD: 800MHz
81 -* - B28 @H-FDD: 700MHz
82 82  
72 + -40°C to +85°C
83 83  
84 84  
85 -== 1.4  Installation ==
86 86  
87 87  
88 -Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
89 89  
90 -[[image:image-20221021110329-1.png]]
91 -
92 -
93 -[[image:image-20221022234602-2.png||height="288" width="922"]]
94 -
95 -
96 -
97 97  == 1.5 ​ Applications ==
98 98  
99 99  
100 -* Open/Close Detection
101 -* Pulse meter application
102 -* Dry Contact Detection
103 103  
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
104 104  
105 105  
106 -== 1.6  Mechanical ==
107 107  
94 +== 1.6  Specification ==
108 108  
109 -​[[image:image-20221021110415-3.png]]
110 110  
97 +(% style="color:blue" %)**Common DC Characteristics:**
111 111  
99 +* Supply Voltage: 2.1v ~~ 3.6v
100 +* Operating Temperature: 0 ~~ 70°C
112 112  
113 -== 1.7  Pin Definitions and Switch ==
102 +(% style="color:blue" %)**NB-IoT Spec:**
114 114  
104 +* B1 @H-FDD: 2100MHz
105 +* B3 @H-FDD: 1800MHz
106 +* B8 @H-FDD: 900MHz
107 +* B5 @H-FDD: 850MHz
108 +* B20 @H-FDD: 800MHz
109 +* B28 @H-FDD: 700MHz
115 115  
116 -[[image:image-20221021110429-4.png]]
117 117  
118 118  
119 -=== 1.7.1  Pin Definition ===
113 +== 1.7  Installation ==
120 120  
121 121  
122 -CPN01 is pre-configured to connect to two external wires. The other pins are not used. If user wants to know more about other pins, please refer to the **[[LSN50v2 User Manual>>doc:Main.User Manual for LoRaWAN End Nodes.LSN50 & LSN50-V2 - LoRaWAN Sensor Node User Manual.WebHome]]**.
116 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
123 123  
124 124  
119 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
125 125  
126 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
127 127  
128 128  
129 -Power on Device when putting this jumper.
123 +== 1.8  Pin Definitions and Switch ==
130 130  
131 131  
126 +[[image:1670404362039-351.png]]
132 132  
133 -=== 1.7.3  BOOT MODE / SW1 ===
134 134  
129 += 2.  Use NDS03A to communicate with IoT Server =
135 135  
136 -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.
137 -
138 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
139 -
140 -
141 -
142 -=== 1.7.4  Reset Button ===
143 -
144 -
145 -Press to reboot the device.
146 -
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 -
160 -= 2.  Use CPN01 to communicate with IoT Server =
161 -
162 -
163 163  == 2.1  How it works ==
164 164  
165 165  
166 -The CPN01 is equipped with an NB-IoT module, the pre-loaded firmware in CPN01 will get (% style="color:blue" %)**Open/Close Event or Count**(%%) from sensor and send the value to the NB-IoT network. The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01.
134 +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.
167 167  
168 -The diagram below shows the working flow in the default firmware of CPN01:
136 +The diagram below shows the working flow in the default firmware of NDS03A:
169 169  
170 170  [[image:image-20221021110615-5.png]]
171 171  
172 172  
141 +== 2.2 ​ Configure NDS03A ==
173 173  
174 -== 2.2 ​ Configure CPN01 ==
175 -
176 -
177 177  === 2.2.1 Test Requirement ===
178 178  
179 179  
180 -To use CPN01 in your city, make sure to meet below requirements:
146 +To use NDS03A in your city, make sure to meet below requirements:
181 181  
182 182  * Your local operator has already distributed an NB-IoT Network.
183 -* The local NB-IoT network used the band that CPN01 supports.
149 +* The local NB-IoT network used the band that NDS03A supports.
184 184  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
185 185  
186 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The CPN01 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.
152 +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.
187 187  
188 -[[image:image-20221023000439-3.png]]
154 +[[image:image-20221117142300-1.png]]
189 189  
190 - ​
191 191  
192 -
193 193  === 2.2.2 Insert NB-IoT SIM card ===
194 194  
195 195  
... ... @@ -200,12 +200,11 @@
200 200  [[image:image-20221021110745-6.png]] ​
201 201  
202 202  
167 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
203 203  
204 -=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
205 205  
170 +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.
206 206  
207 -User need to configure CPN01 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. CPN01 support AT Commands, user can use a USB to TTL adapter to connect to CPN01 and use AT Commands to configure it, as below.
208 -
209 209  (% style="color:blue" %)**Connection:**
210 210  
211 211  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -227,11 +227,11 @@
227 227  
228 228  * Flow Control: (% style="color:red" %)**None**
229 229  
230 -Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
193 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
231 231  
232 232  ​[[image:image-20221021110817-7.png]]
233 233  
234 -CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
197 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
235 235  
236 236  
237 237  (% 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]]
... ... @@ -244,7 +244,7 @@
244 244  (% 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/]]
245 245  
246 246  
247 -(% style="color:blue" %)**Use below commands in CPN01:**
210 +(% style="color:blue" %)**Use below commands in NDS03A:**
248 248  
249 249  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
250 250  
... ... @@ -257,12 +257,11 @@
257 257  [[image:image-20221021110948-8.png]]
258 258  
259 259  
260 -After configuring the server address and (% style="color:green" %)**reset CPN01**(%%) (via AT+ATZ ), CPN01 will start to uplink sensor values to the CoAP server.
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.
261 261  
262 -[[image:image-20221021110956-9.png]] ​
225 +[[image:image-20221118103547-9.png||height="605" width="837"]] ​
263 263  
264 264  
265 -
266 266  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
267 267  
268 268  
... ... @@ -281,7 +281,6 @@
281 281  
282 282  ​
283 283  
284 -
285 285  === 2.2.6 Use MQTT protocol to uplink data ===
286 286  
287 287  
... ... @@ -301,10 +301,10 @@
301 301  
302 302  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
303 303  
304 -​ [[image:image-20221021111058-12.png]]
265 +​ [[image:image-20221118103445-7.png]]
305 305  
306 306  
307 -[[image:image-20221021111201-16.png||height="472" width="653"]]
268 +[[image:image-20221118103453-8.png||height="608" width="841"]]
308 308  
309 309  ​
310 310  
... ... @@ -311,7 +311,6 @@
311 311  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.
312 312  
313 313  
314 -
315 315  === 2.2.7 Use TCP protocol to uplink data ===
316 316  
317 317  
... ... @@ -327,77 +327,87 @@
327 327  
328 328  ​
329 329  
330 -
331 331  === 2.2.8 Change Update Interval ===
332 332  
333 333  
334 334  User can use below command to change the (% style="color:blue" %)**uplink interval**.
335 335  
336 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
295 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
337 337  
338 338  (% style="color:red" %)**NOTE:**
339 339  
340 -1.  By default, the device will send an uplink message every 1 hour.
299 +1.  By default, the device will send an uplink message every 4 hour.
341 341  
342 342  
343 -
344 344  == 2.3  Uplink Payload ==
345 345  
346 346  
347 -The uplink payload includes 123 bytes in total by default.
305 +The uplink payload includes 26 bytes in total by default.
348 348  
349 -Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
307 +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.
350 350  
309 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
351 351  
352 -(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
353 -|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:60px" %)**3**
354 -|=(% style="width: 96px;" %)**Value**|(% style="width:84px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:44px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:121px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:52px" %)MOD|(% style="width:84px" %)[[ Calculate Flag>>||anchor="H2.4.5A0CalculateFlag"]]|(% style="width:116px" %)[[Contact Status>>||anchor="H2.4.7A0ContactStatus"]]|(% style="width:57px" %)[[Alarm>>||anchor="H2.4.6A0Alarm"]]|(% style="width:91px" %)[[Total pulse>>||anchor="H2.4.8A0Totalpulse"]]
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**
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)
355 355  
356 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
357 -|(% style="width:100px" %)**3**|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:100px" %)**3**|(% style="width:80px" %)4|(% style="width:50px" %)**8 group**
358 -|(% style="width:176px" %)[[The last open duration>>||anchor="H2.4.9A0Thelastopenduration"]]|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% style="width:115px" %)Contact Status|(% style="width:92px" %)Total pulse|(% style="width:169px" %)The last open duration|(% style="width:97px" %)Time stamp|(% style="width:74px" %)...
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" %)(((
317 +**1-32 group**
318 +)))
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" %)...
359 359  
360 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
321 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
361 361  
362 -[[image:image-20221021111201-16.png||height="572" width="792"]]
363 363  
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**
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)
364 364  
365 -The payload is ASCII string, representative same HEX:
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**
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)
366 366  
367 -**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0c78__(% style="color:#00b0f0" %) __17__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__ (% style="color:#660066" %)__00__ (% style="color:#aaaa40" %)__000009__(% style="color:#663300" %) __000002__ (% style="color:#d60093" %)__6315537b__ (% style="color:#660066" %)__01 00000b 02 0000026 63510fed__ (%%)__0100000e0200000263510f39__ __010000000000000063510e85__ __010000000000000063510d2e__ __010000000000000063510c7a__ __010000000000000063510bc6__ __010000000000000063510954__ __010000000000000063510882 __**
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" %)(((
334 +**1-32 group**
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" %)......
368 368  
369 -**where:**
338 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
370 370  
371 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
340 +[[image:image-20221117145932-2.png]]
372 372  
373 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
374 374  
375 -* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
343 +The payload is ASCII string, representative same HEX:
376 376  
377 -* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
345 +**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__(%%)**
378 378  
379 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
347 +**where:**
380 380  
381 -* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
349 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
382 382  
383 -* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
351 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
384 384  
385 -* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
353 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
386 386  
387 -* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
355 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
388 388  
389 -* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
357 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
390 390  
391 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
359 +* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
392 392  
393 -* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
361 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
394 394  
395 -* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
363 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
396 396  
365 +* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
397 397  
367 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
368 +
398 398  == 2.4  Payload Explanation and Sensor Interface ==
399 399  
400 -
401 401  === 2.4.1  Device ID ===
402 402  
403 403  
... ... @@ -412,20 +412,18 @@
412 412  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
413 413  
414 414  
415 -
416 416  === 2.4.2  Version Info ===
417 417  
418 418  
419 419  Specify the software version: 0x64=100, which means firmware version 1.00.
420 420  
421 -For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
390 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
422 422  
423 423  
424 -
425 425  === 2.4.3  Battery Info ===
426 426  
427 427  
428 -Check the battery voltage for CPN01.
396 +Check the battery voltage for NDS03A.
429 429  
430 430  Ex1: 0x0B45 = 2885mV
431 431  
... ... @@ -432,7 +432,6 @@
432 432  Ex2: 0x0B49 = 2889mV
433 433  
434 434  
435 -
436 436  === 2.4.4  Signal Strength ===
437 437  
438 438  
... ... @@ -451,70 +451,38 @@
451 451  **99**    Not known or not detectable
452 452  
453 453  
421 +=== 2.4.5  Disalarm: (default: 0) ===
454 454  
455 -=== 2.4.5  Calculate Flag ===
456 456  
424 +(% 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.
457 457  
458 -The calculate flag is a user defined field, IoT server can use this filed to handle different meters with different pulse factors. For example, if there are 100 water meters, meter 1~~50 are 1 liter/pulse and meter 51 ~~ 100 has 1.5 liter/pulse.
426 +(% 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.
459 459  
460 -User can set calculate flag to 1 for meter 1~~50 and 2 for meter 51 ~~ 100, So IoT Server can use this field for calculation.
428 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
461 461  
462 -Default value: 0. 
463 463  
464 -Range (6 bits): (b)000000 ~~ (b) 111111
431 +=== 2.4.6  Keep Status & Keep Time ===
465 465  
466 466  
434 +Shows the configure value of Alarm Base on Timeout Feature
467 467  
468 -=== 2.4.6  Alarm ===
469 469  
437 +=== 2.4.7  Timestamp ===
470 470  
471 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
472 472  
440 +Timestamp : 0x6315537b =1662342011
473 473  
474 474  
475 -=== 2.4.7  Contact Status ===
443 +=== 2.4.8  Switch Dual Channel Mode ===
476 476  
477 477  
478 -0: Open
446 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
479 479  
480 -1: Close
481 481  
482 -
483 -
484 -=== 2.4.8  Total pulse ===
485 -
486 -
487 -Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
488 -
489 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
490 -
491 -
492 -
493 -=== 2.4.9  The last open duration ===
494 -
495 -
496 -Dry Contact last open duration.
497 -
498 -Unit: min.
499 -
500 -[[image:image-20221021111346-17.png||height="146" width="770"]]
501 -
502 -
503 -
504 -=== 2.4.10  Timestamp ===
505 -
506 -
507 -Timestamp : 0x6315537b =1662342011
508 -
509 -Convert Unix timestamp to time 2022-9-5 9:40:11.
510 -
511 -**~ **
512 -
513 -
514 514  == 2.5  Downlink Payload ==
515 515  
516 516  
517 -By default, CPN01 prints the downlink payload to console port.
452 +By default, NDS03A prints the downlink payload to console port.
518 518  
519 519  [[image:image-20221021111414-18.png]] ​
520 520  
... ... @@ -531,7 +531,7 @@
531 531  
532 532  * (% style="color:#037691" %)**Reset**
533 533  
534 -If payload = 0x04FF, it will reset the NSE01
469 +If payload = 0x04FF, it will reset the NDS03A
535 535  
536 536  * (% style="color:#037691" %)**INTMOD**
537 537  
... ... @@ -538,21 +538,19 @@
538 538  Downlink Payload: 06000003, Set AT+INTMOD=3
539 539  
540 540  
541 -
542 542  == 2.6  ​LED Indicator ==
543 543  
544 544  
545 -The CPN01 has an internal LED which is to show the status of different states.
479 +The NDS03A has an internal LED which is to show the status of different states.
546 546  
547 547  * When the device starts normally, the LED will light up for 1 second.
548 -* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
482 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
549 549  * For each uplink probe, LED will be on for 500ms.
550 550  
551 -
552 552  == 2.7  Alarm Base on Timeout ==
553 553  
554 554  
555 -CPN01 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:
488 +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:
556 556  
557 557  
558 558  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -568,17 +568,25 @@
568 568  
569 569  If keep time = 0, Disable Alarm Base on Timeout feature.
570 570  
571 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
504 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
572 572  
573 573  
574 574  (% style="color:blue" %)**AT Command to configure:**
575 575  
576 -(% 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. CPN01 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.
509 +(% style="color:blue" %)**PB14 PIN:**
577 577  
511 +(% 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.
512 +
578 578  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
579 579  
580 580  
516 +(% style="color:blue" %)**PB15 PIN:**
581 581  
518 +(% style="color:#037691" %)**AT+TTRIG2=1,30**
519 +
520 +(% style="color:#037691" %)**AT+TTRIG2=0,0 **
521 +
522 +
582 582  == 2.8  Set debug mode ==
583 583  
584 584  
... ... @@ -600,54 +600,57 @@
600 600  [[image:image-20221021111527-19.png]]
601 601  
602 602  
544 +== 2.10  Count Mod ==
603 603  
604 -== 2.10  Set trigger mode ==
605 605  
547 +(% style="color:blue" %)**AT Command: AT+COUNTMOD**
606 606  
607 -(% style="color:blue" %)**AT Command: AT+TTRMOD**
549 +[[image:image-20221118092935-1.png]]
608 608  
609 -Feature: Set the trigger interrupt mode.
610 610  
611 -[[image:image-20221021111552-20.png]]
552 +== 2.11  Interrupt Pin Channel Mod ==
612 612  
613 613  
555 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
614 614  
615 -== 2.11  Set the calculate flag ==
557 +[[image:image-20221118093144-2.png]]
616 616  
617 617  
618 -Feature: Set the calculate flag
560 +== 2.12 TTRIG1/2 timeout status alarm ==
619 619  
620 -(% style="color:blue" %)**AT Command: AT+CALCFLAG**
621 621  
622 -[[image:image-20221021111711-22.png]]
563 +It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval.
623 623  
565 +(% style="color:blue" %)**AT Command: AT+TTRALARM**
624 624  
567 +[[image:image-20221118093512-3.png]]
625 625  
626 -== 2.12 Set count number ==
627 627  
570 +== 2.13  Select counting mode ==
628 628  
629 -Feature: Manually set the count number
630 630  
631 -(% style="color:blue" %)**AT Command: AT+SETCNT**
573 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
632 632  
633 -[[image:image-20221021111748-24.png]]
575 +When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
634 634  
577 +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.
635 635  
579 +[[image:image-20221118093658-4.png]]
636 636  
637 -== 2.13  Set the number of data to be uploaded and the recording time ==
638 638  
582 +== 2.14  Set the number of data to be uploaded and the recording time ==
639 639  
584 +
640 640  (% style="color:blue" %)**AT Command:**
641 641  
642 -(% 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)
587 +(% 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)
643 643  
644 -(% style="color:#037691" %)**AT+NOUD=8 ** (%%)~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
589 +(% 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.
645 645  
646 646  
592 +== 2.15  Read or Clear cached data ==
647 647  
648 -== 2.14  Read or Clear cached data ==
649 649  
650 -
651 651  (% style="color:blue" %)**AT Command:**
652 652  
653 653  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -654,27 +654,24 @@
654 654  
655 655  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
656 656  
657 -[[image:image-20221021111810-25.png||height="364" width="797"]]
601 +[[image:image-20221118094227-5.png]]
658 658  
659 659  
604 +== 2.16  ​Firmware Change Log ==
660 660  
661 -== 2.15  ​Firmware Change Log ==
662 662  
607 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
663 663  
664 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
665 -
666 666  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
667 667  
668 668  
612 +== 2.17  ​Battery Analysis ==
669 669  
670 -== 2.16  ​Battery Analysis ==
614 +=== 2.17.1  ​Battery Type ===
671 671  
672 672  
673 -=== 2.16.1  ​Battery Type ===
617 +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.
674 674  
675 -
676 -The CPN01 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.
677 -
678 678  The battery is designed to last for several years depends on the actual use environment and update interval. 
679 679  
680 680  The battery-related documents as below:
... ... @@ -688,10 +688,9 @@
688 688  [[image:image-20221021111911-26.png]] ​
689 689  
690 690  
632 +=== 2.17.2  Power consumption Analyze ===
691 691  
692 -=== 2.16.2  Power consumption Analyze ===
693 693  
694 -
695 695  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.
696 696  
697 697  Instruction to use as below:
... ... @@ -711,21 +711,18 @@
711 711  [[image:1666596205057-567.png]] ​
712 712  
713 713  
654 +=== 2.17.3  ​Battery Note ===
714 714  
715 -=== 2.16.3  ​Battery Note ===
716 716  
717 -
718 718  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.
719 719  
720 720  
660 +=== 2.17.4  Replace the battery ===
721 721  
722 -=== 2.16.4  Replace the battery ===
723 723  
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).
724 724  
725 -The default battery pack of CPN01 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).
726 726  
727 -
728 -
729 729  = 3. ​ Access NB-IoT Module =
730 730  
731 731  
... ... @@ -733,13 +733,12 @@
733 733  
734 734  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/]] 
735 735  
736 -[[image:image-20221021112006-28.png]] ​
737 737  
674 +[[image:image-20221118094449-6.png]] ​
738 738  
739 739  
740 740  = 4.  Using the AT Commands =
741 741  
742 -
743 743  == 4.1  Access AT Commands ==
744 744  
745 745  
... ... @@ -786,15 +786,21 @@
786 786  
787 787  AT+ DEBUG   : Enable or Disable debug mode
788 788  
789 -AT+ TTRIG   : Get or Set Alarm Base on Timeout
725 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
790 790  
791 -AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
727 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
792 792  
793 -AT+ CALCFLAG   : Get or Set the calculate flag
729 +AT+COUNTMOD  :  Get or Set the count mode
794 794  
795 -AT+ CLRC   : Clear current door open count
731 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
796 796  
733 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
797 797  
735 +AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
736 +
737 +AT+ CLRC   :  Clear current door open count
738 +
739 +
798 798  (% style="color:blue" %)**COAP Management**      
799 799  
800 800  AT+URI            : Resource parameters
... ... @@ -825,10 +825,8 @@
825 825  AT+PWORD  : Serial Access Password
826 826  
827 827  
828 -
829 829  = ​5.  FAQ =
830 830  
831 -
832 832  == 5.1 ​ How to Upgrade Firmware ==
833 833  
834 834  
... ... @@ -836,13 +836,11 @@
836 836  
837 837  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]]
838 838  
839 -(% style="color:red" %)**Notice: **(% style="color:blue" %)**CPN01** (%%)**and (% style="color:blue" %)CPL01(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
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.**
840 840  
841 841  
842 -
843 843  = 6.  Trouble Shooting =
844 844  
845 -
846 846  == 6.1  ​Connection problem when uploading firmware ==
847 847  
848 848  
... ... @@ -849,7 +849,6 @@
849 849  (% 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]]
850 850  
851 851  
852 -
853 853  == 6.2  AT Command input doesn't work ==
854 854  
855 855  
... ... @@ -856,29 +856,19 @@
856 856  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.
857 857  
858 858  
859 -
860 860  = 7. ​ Order Info =
861 861  
862 862  
863 -Part Number**:** CPN01
799 +Part Number**:** NDS03A
864 864  
865 865  
866 -
867 867  = 8.  Packing Info =
868 868  
869 869  
870 870  (% style="color:blue" %)**Package Includes**:
871 871  
872 -* CPN01 Open/Close Sensor x 1
873 -* External antenna x 1
807 +* NDS03A Open/Close Door Sensor x 1
874 874  
875 -(% style="color:blue" %)**Dimension and weight**:
876 -
877 -* Size: 195 x 125 x 55 mm
878 -* Weight:   420g
879 -
880 -
881 -
882 882  = 9.  Support =
883 883  
884 884  
1670404362039-351.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +492.6 KB
Content
LMDS200_10.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
image-20221117114459-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +14.9 KB
Content
image-20221117114842-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +964.1 KB
Content
image-20221117114937-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +79.1 KB
Content
image-20221117114949-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +33.4 KB
Content
image-20221117115010-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +40.4 KB
Content
image-20221117142300-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +51.9 KB
Content
image-20221117150312-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +8.7 KB
Content
image-20221118092935-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +9.5 KB
Content
image-20221118093658-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +12.7 KB
Content
image-20221118094227-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +29.2 KB
Content
image-20221118094449-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.5 KB
Content
image-20221118103445-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +43.5 KB
Content
image-20221207170748-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.1 KB
Content
image-20221207170748-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +29.9 KB
Content

Applications

Navigation

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