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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
1 +NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
Content
... ... @@ -1,7 +1,12 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg]]
2 +[[image:image-20221117105556-1.png]]
3 3  
4 4  
5 +
6 +
7 +
8 +
9 +
5 5  **Table of Contents：**
6 6  
7 7  
... ... @@ -10,37 +10,54 @@
10 10  
11 11  = 1.  Introduction =
12 12  
13 -== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
14 14  
19 +== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
15 15  
21 +
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.
23 +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.
24 +)))
18 18  
26 +(((
27 +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.
28 +)))
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.
30 +(((
31 +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.
32 +)))
21 21  
22 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
34 +(((
35 +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.
36 +)))
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.
38 +(((
39 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
40 +)))
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.
42 +(((
43 +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.
44 +)))
27 27  
28 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
46 +(((
47 +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)
48 +)))
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.
50 +(((
51 +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  
55 +​
36 36  
57 +
37 37  == ​1.2  Features ==
38 38  
39 39  
40 40  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
41 -* Short uplink interval for Distance Alarm
62 +* Open/Close detect
63 +* Open/Close statistics
42 42  * Monitor Battery Level
43 -* Microwave Radar for distance detection
65 +* Uplink on periodically and open/close event
44 44  * Datalog feature
45 45  * Uplink periodically
46 46  * Downlink to change configure
... ... @@ -51,109 +51,129 @@
51 51  * Micro SIM card slot for NB-IoT SIM
52 52  * 8500mAh Battery for long-term use
53 53  
54 -== 1.3 Radar probe specification ==
76 +== 1.3  Specification ==
55 55  
56 56  
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°
79 +(% style="color:blue" %)**Common DC Characteristics:**
65 65  
81 +* Supply Voltage: 2.1v ~~ 3.6v
82 +* Operating Temperature: -40 ~~ 85°C
66 66  
84 +(% style="color:blue" %)**NB-IoT Spec:**
67 67  
86 +* - B1 @H-FDD: 2100MHz
87 +* - B3 @H-FDD: 1800MHz
88 +* - B8 @H-FDD: 900MHz
89 +* - B5 @H-FDD: 850MHz
90 +* - B20 @H-FDD: 800MHz
91 +* - B28 @H-FDD: 700MHz
68 68  
69 -== 1.4  Storage Temperature ==
93 +== 1.4  Installation ==
70 70  
71 71  
72 - -40°C to +85°C
96 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
73 73  
98 +[[image:image-20221021110329-1.png]]
74 74  
75 75  
101 +[[image:image-20221022234602-2.png||height="288" width="922"]]
76 76  
77 77  
104 +
78 78  == 1.5 ​ Applications ==
79 79  
80 80  
108 +* Open/Close Detection
109 +* Pulse meter application
110 +* Dry Contact Detection
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
112 +== 1.6  Mechanical ==
91 91  
92 92  
115 +​[[image:image-20221021110415-3.png]]
93 93  
94 -== 1.6  Specification ==
95 95  
96 96  
97 -(% style="color:blue" %)**Common DC Characteristics:**
119 +== 1.7  Pin Definitions and Switch ==
98 98  
99 -* Supply Voltage: 2.1v ~~ 3.6v
100 -* Operating Temperature: 0 ~~ 70°C
101 101  
102 -(% style="color:blue" %)**NB-IoT Spec:**
122 +[[image:image-20221021110429-4.png]]
103 103  
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
110 110  
125 +=== 1.7.1  Pin Definition ===
111 111  
112 112  
113 -== 1.7  Installation ==
128 +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]]**.
114 114  
115 115  
116 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
117 117  
132 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
118 118  
119 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
120 120  
135 +Power on Device when putting this jumper.
121 121  
122 122  
123 -== 1.8  Pin Definitions and Switch ==
124 124  
139 +=== 1.7.3  BOOT MODE / SW1 ===
125 125  
126 -[[image:1670404362039-351.png]]
127 127  
142 +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.
128 128  
129 -= 2.  Use NDS03A to communicate with IoT Server =
144 +2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
130 130  
146 +
147 +
148 +=== 1.7.4  Reset Button ===
149 +
150 +
151 +Press to reboot the device.
152 +
153 +
154 +
155 +=== 1.7.5  LED ===
156 +
157 +
158 +The LED will blink when :
159 +
160 +1.  Boot the device in flash mode
161 +
162 +2.  Send an uplink packet
163 +
164 +
165 +
166 += 2.  Use CPN01 to communicate with IoT Server =
167 +
168 +
131 131  == 2.1  How it works ==
132 132  
133 133  
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.
172 +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.
135 135  
136 -The diagram below shows the working flow in the default firmware of NDS03A:
174 +The diagram below shows the working flow in the default firmware of CPN01:
137 137  
138 138  [[image:image-20221021110615-5.png]]
139 139  
140 140  
141 -== 2.2 ​ Configure NDS03A ==
142 142  
180 +== 2.2 ​ Configure CPN01 ==
181 +
182 +
143 143  === 2.2.1 Test Requirement ===
144 144  
145 145  
146 -To use NDS03A in your city, make sure to meet below requirements:
186 +To use CPN01 in your city, make sure to meet below requirements:
147 147  
148 148  * Your local operator has already distributed an NB-IoT Network.
149 -* The local NB-IoT network used the band that NDS03A supports.
189 +* The local NB-IoT network used the band that CPN01 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 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.
192 +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.
153 153  
154 -[[image:image-20221117142300-1.png]]
194 +[[image:image-20221023000439-3.png]]
155 155  
196 + ​
156 156  
198 +
157 157  === 2.2.2 Insert NB-IoT SIM card ===
158 158  
159 159  
... ... @@ -164,11 +164,12 @@
164 164  [[image:image-20221021110745-6.png]] ​
165 165  
166 166  
167 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
168 168  
210 +=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
169 169  
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.
171 171  
213 +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.
214 +
172 172  (% style="color:blue" %)**Connection:**
173 173  
174 174  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -190,11 +190,11 @@
190 190  
191 191  * Flow Control: (% style="color:red" %)**None**
192 192  
193 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
236 +Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
194 194  
195 195  ​[[image:image-20221021110817-7.png]]
196 196  
197 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
240 +CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
198 198  
199 199  
200 200  (% 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]]
... ... @@ -207,7 +207,7 @@
207 207  (% 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/]]
208 208  
209 209  
210 -(% style="color:blue" %)**Use below commands in NDS03A:**
253 +(% style="color:blue" %)**Use below commands in CPN01:**
211 211  
212 212  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
213 213  
... ... @@ -220,11 +220,12 @@
220 220  [[image:image-20221021110948-8.png]]
221 221  
222 222  
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.
266 +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.
224 224  
225 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
268 +[[image:image-20221021110956-9.png]] ​
226 226  
227 227  
271 +
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  
290 +
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]]
310 +​ [[image:image-20221021111058-12.png]]
266 266  
267 267  
268 -[[image:image-20221118103453-8.png||height="608" width="841"]]
313 +[[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  
320 +
275 275  === 2.2.7 Use TCP protocol to uplink data ===
276 276  
277 277  
... ... @@ -287,87 +287,76 @@
287 287  
288 288  ​
289 289  
336 +
290 290  === 2.2.8 Change Update Interval ===
291 291  
292 292  
293 293  User can use below command to change the (% style="color:blue" %)**uplink interval**.
294 294  
295 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
342 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
296 296  
297 297  (% style="color:red" %)**NOTE:**
298 298  
299 -1.  By default, the device will send an uplink message every 4 hour.
346 +1.  By default, the device will send an uplink message every 1 hour.
300 300  
301 301  
349 +
302 302  == 2.3  Uplink Payload ==
303 303  
304 304  
305 -The uplink payload includes 26 bytes in total by default.
353 +The uplink payload includes 123 bytes in total by default.
306 306  
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.
355 +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.
308 308  
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**
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)
358 +(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
359 +|=(% 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**
360 +|=(% 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"]]
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" %)(((
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" %)...
362 +(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
363 +|(% 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**
364 +|(% 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" %)...
320 320  
321 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
366 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
322 322  
368 +[[image:image-20221021111201-16.png||height="572" width="792"]]
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**
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**
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 -
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" %)......
337 -
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 -
340 -[[image:image-20221117145932-2.png]]
341 -
342 -
343 343  The payload is ASCII string, representative same HEX:
344 344  
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__(%%)**
373 +**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 __**
346 346  
347 347  **where:**
348 348  
349 349  * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
350 350  
351 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
379 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
352 352  
353 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
381 +* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
354 354  
355 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
383 +* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
356 356  
357 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
385 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
358 358  
359 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
387 +* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
360 360  
361 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
389 +* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
362 362  
363 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
391 +* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
364 364  
365 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
393 +* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
366 366  
367 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
395 +* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
368 368  
397 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
398 +
399 +* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
400 +
401 +* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
402 +
369 369  == 2.4  Payload Explanation and Sensor Interface ==
370 370  
405 +
371 371  === 2.4.1  Device ID ===
372 372  
373 373  
... ... @@ -382,18 +382,20 @@
382 382  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
383 383  
384 384  
420 +
385 385  === 2.4.2  Version Info ===
386 386  
387 387  
388 388  Specify the software version: 0x64=100, which means firmware version 1.00.
389 389  
390 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
426 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
391 391  
392 392  
429 +
393 393  === 2.4.3  Battery Info ===
394 394  
395 395  
396 -Check the battery voltage for NDS03A.
433 +Check the battery voltage for CPN01.
397 397  
398 398  Ex1: 0x0B45 = 2885mV
399 399  
... ... @@ -400,6 +400,7 @@
400 400  Ex2: 0x0B49 = 2889mV
401 401  
402 402  
440 +
403 403  === 2.4.4  Signal Strength ===
404 404  
405 405  
... ... @@ -418,38 +418,70 @@
418 418  **99**    Not known or not detectable
419 419  
420 420  
421 -=== 2.4.5  Disalarm: (default: 0) ===
422 422  
460 +=== 2.4.5  Calculate Flag ===
423 423  
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.
425 425  
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.
463 +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.
427 427  
428 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
465 +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.
429 429  
467 +Default value: 0. 
430 430  
431 -=== 2.4.6  Keep Status & Keep Time ===
469 +Range (6 bits): (b)000000 ~~ (b) 111111
432 432  
433 433  
434 -Shows the configure value of Alarm Base on Timeout Feature
435 435  
473 +=== 2.4.6  Alarm ===
436 436  
437 -=== 2.4.7  Timestamp ===
438 438  
476 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
439 439  
440 -Timestamp : 0x6315537b =1662342011
441 441  
442 442  
443 -=== 2.4.8  Switch Dual Channel Mode ===
480 +=== 2.4.7  Contact Status ===
444 444  
445 445  
446 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
483 +0: Open
447 447  
485 +1: Close
448 448  
487 +
488 +
489 +=== 2.4.8  Total pulse ===
490 +
491 +
492 +Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
493 +
494 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
495 +
496 +
497 +
498 +=== 2.4.9  The last open duration ===
499 +
500 +
501 +Dry Contact last open duration.
502 +
503 +Unit: min.
504 +
505 +[[image:image-20221021111346-17.png||height="146" width="770"]]
506 +
507 +
508 +
509 +=== 2.4.10  Timestamp ===
510 +
511 +
512 +Timestamp : 0x6315537b =1662342011
513 +
514 +Convert Unix timestamp to time 2022-9-5 9:40:11.
515 +
516 +**~ **
517 +
518 +
449 449  == 2.5  Downlink Payload ==
450 450  
451 451  
452 -By default, NDS03A prints the downlink payload to console port.
522 +By default, CPN01 prints the downlink payload to console port.
453 453  
454 454  [[image:image-20221021111414-18.png]] ​
455 455  
... ... @@ -466,7 +466,7 @@
466 466  
467 467  * (% style="color:#037691" %)**Reset**
468 468  
469 -If payload = 0x04FF, it will reset the NDS03A
539 +If payload = 0x04FF, it will reset the NSE01
470 470  
471 471  * (% style="color:#037691" %)**INTMOD**
472 472  
... ... @@ -473,19 +473,20 @@
473 473  Downlink Payload: 06000003, Set AT+INTMOD=3
474 474  
475 475  
546 +
476 476  == 2.6  ​LED Indicator ==
477 477  
478 478  
479 -The NDS03A has an internal LED which is to show the status of different states.
550 +The CPN01 has an internal LED which is to show the status of different states.
480 480  
481 481  * When the device starts normally, the LED will light up for 1 second.
482 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
553 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
483 483  * For each uplink probe, LED will be on for 500ms.
484 484  
485 485  == 2.7  Alarm Base on Timeout ==
486 486  
487 487  
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:
559 +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:
489 489  
490 490  
491 491  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -501,25 +501,17 @@
501 501  
502 502  If keep time = 0, Disable Alarm Base on Timeout feature.
503 503  
504 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
575 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
505 505  
506 506  
507 507  (% style="color:blue" %)**AT Command to configure:**
508 508  
509 -(% style="color:blue" %)**PB14 PIN:**
580 +(% 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.
510 510  
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 -
513 513  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
514 514  
515 515  
516 -(% style="color:blue" %)**PB15 PIN:**
517 517  
518 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
519 -
520 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
521 -
522 -
523 523  == 2.8  Set debug mode ==
524 524  
525 525  
... ... @@ -541,57 +541,54 @@
541 541  [[image:image-20221021111527-19.png]]
542 542  
543 543  
544 -== 2.10  Count Mod ==
545 545  
608 +== 2.10  Set trigger mode ==
546 546  
547 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
548 548  
549 -[[image:image-20221118092935-1.png]]
611 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
550 550  
613 +Feature: Set the trigger interrupt mode.
551 551  
552 -== 2.11  Interrupt Pin Channel Mod ==
615 +[[image:image-20221021111552-20.png]]
553 553  
554 554  
555 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
556 556  
557 -[[image:image-20221118093144-2.png]]
619 +== 2.11  Set the calculate flag ==
558 558  
559 559  
560 -== 2.12 TTRIG1/2 timeout status alarm ==
622 +Feature: Set the calculate flag
561 561  
624 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
562 562  
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.
626 +[[image:image-20221021111711-22.png]]
564 564  
565 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
566 566  
567 -[[image:image-20221118093512-3.png]]
568 568  
630 +== 2.12 Set count number ==
569 569  
570 -== 2.13  Select counting mode ==
571 571  
633 +Feature: Manually set the count number
572 572  
573 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
635 +(% style="color:blue" %)**AT Command: AT+SETCNT**
574 574  
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.
637 +[[image:image-20221021111748-24.png]]
576 576  
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.
578 578  
579 -[[image:image-20221118093658-4.png]]
580 580  
641 +== 2.13  Set the number of data to be uploaded and the recording time ==
581 581  
582 -== 2.14  Set the number of data to be uploaded and the recording time ==
583 583  
584 -
585 585  (% style="color:blue" %)**AT Command:**
586 586  
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)
646 +(% 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)
588 588  
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.
648 +(% 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.
590 590  
591 591  
592 -== 2.15  Read or Clear cached data ==
593 593  
652 +== 2.14  Read or Clear cached data ==
594 594  
654 +
595 595  (% style="color:blue" %)**AT Command:**
596 596  
597 597  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -598,24 +598,27 @@
598 598  
599 599  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
600 600  
601 -[[image:image-20221118094227-5.png]]
661 +[[image:image-20221021111810-25.png||height="364" width="797"]]
602 602  
603 603  
604 -== 2.16  ​Firmware Change Log ==
605 605  
665 +== 2.15  ​Firmware Change Log ==
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]]
608 608  
668 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
669 +
609 609  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
610 610  
611 611  
612 -== 2.17  ​Battery Analysis ==
613 613  
614 -=== 2.17.1  ​Battery Type ===
674 +== 2.16  ​Battery Analysis ==
615 615  
616 616  
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.
677 +=== 2.16.1  ​Battery Type ===
618 618  
679 +
680 +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.
681 +
619 619  The battery is designed to last for several years depends on the actual use environment and update interval. 
620 620  
621 621  The battery-related documents as below:
... ... @@ -629,9 +629,10 @@
629 629  [[image:image-20221021111911-26.png]] ​
630 630  
631 631  
632 -=== 2.17.2  Power consumption Analyze ===
633 633  
696 +=== 2.16.2  Power consumption Analyze ===
634 634  
698 +
635 635  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.
636 636  
637 637  Instruction to use as below:
... ... @@ -651,18 +651,21 @@
651 651  [[image:1666596205057-567.png]] ​
652 652  
653 653  
654 -=== 2.17.3  ​Battery Note ===
655 655  
719 +=== 2.16.3  ​Battery Note ===
656 656  
721 +
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  
660 -=== 2.17.4  Replace the battery ===
661 661  
726 +=== 2.16.4  Replace the battery ===
662 662  
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  
729 +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).
665 665  
731 +
732 +
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  
740 +[[image:image-20221021112006-28.png]] ​
673 673  
674 -[[image:image-20221118094449-6.png]] ​
675 675  
676 676  
677 677  = 4.  Using the AT Commands =
678 678  
746 +
679 679  == 4.1  Access AT Commands ==
680 680  
681 681  
... ... @@ -722,21 +722,15 @@
722 722  
723 723  AT+ DEBUG   : Enable or Disable debug mode
724 724  
725 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
793 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
726 726  
727 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
795 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
728 728  
729 -AT+COUNTMOD  :  Get or Set the count mode
797 +AT+ CALCFLAG   : Get or Set the calculate flag
730 730  
731 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
799 +AT+ CLRC   : Clear current door open count
732 732  
733 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
734 734  
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 -
740 740  (% style="color:blue" %)**COAP Management**      
741 741  
742 742  AT+URI            : Resource parameters
... ... @@ -767,8 +767,10 @@
767 767  AT+PWORD  : Serial Access Password
768 768  
769 769  
832 +
770 770  = ​5.  FAQ =
771 771  
835 +
772 772  == 5.1 ​ How to Upgrade Firmware ==
773 773  
774 774  
... ... @@ -776,11 +776,13 @@
776 776  
777 777  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]]
778 778  
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.**
843 +(% 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.**
780 780  
781 781  
846 +
782 782  = 6.  Trouble Shooting =
783 783  
849 +
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  
856 +
790 790  == 6.2  AT Command input doesn't work ==
791 791  
792 792  
... ... @@ -793,19 +793,27 @@
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  
863 +
796 796  = 7. ​ Order Info =
797 797  
798 798  
799 -Part Number**:** NDS03A
867 +Part Number**:** CPN01
800 800  
801 801  
870 +
802 802  = 8.  Packing Info =
803 803  
804 804  
805 805  (% style="color:blue" %)**Package Includes**:
806 806  
807 -* NDS03A Open/Close Door Sensor x 1
876 +* CPN01 Open/Close Sensor x 1
877 +* External antenna x 1
808 808  
879 +(% style="color:blue" %)**Dimension and weight**:
880 +
881 +* Size: 195 x 125 x 55 mm
882 +* Weight:   420g
883 +
809 809  = 9.  Support =
810 810  
811 811  
1670404362039-351.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -492.6 KB
Content
LMDS200_10.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 KB
Content
image-20221117114459-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20221117114842-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -964.1 KB
Content
image-20221117114937-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.1 KB
Content
image-20221117114949-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -33.4 KB
Content
image-20221117115010-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -40.4 KB
Content
image-20221117142300-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -51.9 KB
Content
image-20221117150312-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.7 KB
Content
image-20221118092935-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.5 KB
Content
image-20221118093658-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -12.7 KB
Content
image-20221118094227-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.2 KB
Content
image-20221118094449-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.5 KB
Content
image-20221118103445-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.5 KB
Content
image-20221207170748-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.1 KB
Content
image-20221207170748-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.9 KB
Content

Applications

Navigation

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