Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 76.1 >
edited by Xiaoling
on 2022/12/07 17:33
To version < 56.1 >
edited by Xiaoling
on 2022/11/17 11:49
>
Change comment: Uploaded new attachment "image-20221117114937-4.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
1 +NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
Content
... ... @@ -1,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,111 +51,129 @@
51 51  * Micro SIM card slot for NB-IoT SIM
52 52  * 8500mAh Battery for long-term use
53 53  
76 +== 1.3  Specification ==
54 54  
55 55  
56 -== 1.3 Radar probe specification ==
79 +(% style="color:blue" %)**Common DC Characteristics:**
57 57  
81 +* Supply Voltage: 2.1v ~~ 3.6v
82 +* Operating Temperature: -40 ~~ 85°C
58 58  
59 -* Measuring Method: FMCW
60 -* Frequency: 24.000 24.500 GHz
61 -* Measurement output power: 6dBm
62 -* Measure range: 0.5 20m
63 -* Accuracy: ±0.1m
64 -* Resolution: 0.01m
65 -* Horizontal Angel: 78°
66 -* Vertical Angel: 23°
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  
93 +== 1.4  Installation ==
69 69  
70 70  
71 -== 1.4  Storage Temperature ==
96 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
72 72  
98 +[[image:image-20221021110329-1.png]]
73 73  
74 - -40°C to +85°C
75 75  
101 +[[image:image-20221022234602-2.png||height="288" width="922"]]
76 76  
77 77  
78 78  
79 -
80 80  == 1.5 ​ Applications ==
81 81  
82 82  
108 +* Open/Close Detection
109 +* Pulse meter application
110 +* Dry Contact Detection
83 83  
84 -* Horizontal distance measurement
85 -* Liquid level measurement
86 -* Parking management system
87 -* Object proximity and presence detection
88 -* Intelligent trash can management system
89 -* Robot obstacle avoidance
90 -* Automatic control
91 -* Sewer
92 -* Bottom water level monitoring
112 +== 1.6  Mechanical ==
93 93  
94 94  
115 +​[[image:image-20221021110415-3.png]]
95 95  
96 -== 1.6  Specification ==
97 97  
98 98  
99 -(% style="color:blue" %)**Common DC Characteristics:**
119 +== 1.7  Pin Definitions and Switch ==
100 100  
101 -* Supply Voltage: 2.1v ~~ 3.6v
102 -* Operating Temperature: 0 ~~ 70°C
103 103  
104 -(% style="color:blue" %)**NB-IoT Spec:**
122 +[[image:image-20221021110429-4.png]]
105 105  
106 -* B1 @H-FDD: 2100MHz
107 -* B3 @H-FDD: 1800MHz
108 -* B8 @H-FDD: 900MHz
109 -* B5 @H-FDD: 850MHz
110 -* B20 @H-FDD: 800MHz
111 -* B28 @H-FDD: 700MHz
112 112  
125 +=== 1.7.1  Pin Definition ===
113 113  
114 114  
115 -== 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]]**.
116 116  
117 117  
118 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
119 119  
132 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
120 120  
121 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
122 122  
135 +Power on Device when putting this jumper.
123 123  
124 124  
125 -== 1.8  Pin Definitions and Switch ==
126 126  
139 +=== 1.7.3  BOOT MODE / SW1 ===
127 127  
128 -[[image:1670404362039-351.png]]
129 129  
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.
130 130  
131 -= 2.  Use NMDS200 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.
132 132  
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 +
133 133  == 2.1  How it works ==
134 134  
135 135  
136 -The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
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.
137 137  
138 -The diagram below shows the working flow in the default firmware of NMDS200:
174 +The diagram below shows the working flow in the default firmware of CPN01:
139 139  
140 140  [[image:image-20221021110615-5.png]]
141 141  
142 142  
143 -== 2.2 ​ Configure NDS03A ==
144 144  
180 +== 2.2 ​ Configure CPN01 ==
181 +
182 +
145 145  === 2.2.1 Test Requirement ===
146 146  
147 147  
148 -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:
149 149  
150 150  * Your local operator has already distributed an NB-IoT Network.
151 -* The local NB-IoT network used the band that NDS03A supports.
189 +* The local NB-IoT network used the band that CPN01 supports.
152 152  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
153 153  
154 -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.
155 155  
156 -[[image:image-20221117142300-1.png]]
194 +[[image:image-20221023000439-3.png]]
157 157  
196 + ​
158 158  
198 +
159 159  === 2.2.2 Insert NB-IoT SIM card ===
160 160  
161 161  
... ... @@ -166,11 +166,12 @@
166 166  [[image:image-20221021110745-6.png]] ​
167 167  
168 168  
169 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
170 170  
210 +=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
171 171  
172 -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.
173 173  
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 +
174 174  (% style="color:blue" %)**Connection:**
175 175  
176 176  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -192,11 +192,11 @@
192 192  
193 193  * Flow Control: (% style="color:red" %)**None**
194 194  
195 -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**(%%).
196 196  
197 197  ​[[image:image-20221021110817-7.png]]
198 198  
199 -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.
200 200  
201 201  
202 202  (% 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]]
... ... @@ -209,7 +209,7 @@
209 209  (% 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/]]
210 210  
211 211  
212 -(% style="color:blue" %)**Use below commands in NDS03A:**
253 +(% style="color:blue" %)**Use below commands in CPN01:**
213 213  
214 214  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
215 215  
... ... @@ -222,11 +222,12 @@
222 222  [[image:image-20221021110948-8.png]]
223 223  
224 224  
225 -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.
226 226  
227 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
268 +[[image:image-20221021110956-9.png]] ​
228 228  
229 229  
271 +
230 230  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
231 231  
232 232  
... ... @@ -245,6 +245,7 @@
245 245  
246 246  ​
247 247  
290 +
248 248  === 2.2.6 Use MQTT protocol to uplink data ===
249 249  
250 250  
... ... @@ -264,10 +264,10 @@
264 264  
265 265  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
266 266  
267 -​ [[image:image-20221118103445-7.png]]
310 +​ [[image:image-20221021111058-12.png]]
268 268  
269 269  
270 -[[image:image-20221118103453-8.png||height="608" width="841"]]
313 +[[image:image-20221021111201-16.png||height="472" width="653"]]
271 271  
272 272  ​
273 273  
... ... @@ -274,6 +274,7 @@
274 274  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.
275 275  
276 276  
320 +
277 277  === 2.2.7 Use TCP protocol to uplink data ===
278 278  
279 279  
... ... @@ -289,87 +289,76 @@
289 289  
290 290  ​
291 291  
336 +
292 292  === 2.2.8 Change Update Interval ===
293 293  
294 294  
295 295  User can use below command to change the (% style="color:blue" %)**uplink interval**.
296 296  
297 -* (% 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)
298 298  
299 299  (% style="color:red" %)**NOTE:**
300 300  
301 -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.
302 302  
303 303  
349 +
304 304  == 2.3  Uplink Payload ==
305 305  
306 306  
307 -The uplink payload includes 26 bytes in total by default.
353 +The uplink payload includes 123 bytes in total by default.
308 308  
309 -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.
310 310  
311 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
312 312  
313 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
314 -|=(% 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**
315 -|=(% 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"]]
316 316  
317 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
318 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
319 -**1-32 group**
320 -)))
321 -|(% 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" %)...
322 322  
323 -(% 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.
324 324  
368 +[[image:image-20221021111201-16.png||height="572" width="792"]]
325 325  
326 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
327 -|=(% 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**
328 -|=(% 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)
329 329  
330 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
331 -|(% 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**
332 -|(% 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)
333 -
334 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
335 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
336 -**1-32 group**
337 -)))
338 -|(% 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" %)......
339 -
340 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
341 -
342 -[[image:image-20221117145932-2.png]]
343 -
344 -
345 345  The payload is ASCII string, representative same HEX:
346 346  
347 -**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 __**
348 348  
349 349  **where:**
350 350  
351 351  * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
352 352  
353 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
379 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
354 354  
355 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
381 +* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
356 356  
357 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
383 +* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
358 358  
359 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
385 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
360 360  
361 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
387 +* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
362 362  
363 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
389 +* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
364 364  
365 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
391 +* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
366 366  
367 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
393 +* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
368 368  
369 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
395 +* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
370 370  
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 +
371 371  == 2.4  Payload Explanation and Sensor Interface ==
372 372  
405 +
373 373  === 2.4.1  Device ID ===
374 374  
375 375  
... ... @@ -384,18 +384,20 @@
384 384  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
385 385  
386 386  
420 +
387 387  === 2.4.2  Version Info ===
388 388  
389 389  
390 390  Specify the software version: 0x64=100, which means firmware version 1.00.
391 391  
392 -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.
393 393  
394 394  
429 +
395 395  === 2.4.3  Battery Info ===
396 396  
397 397  
398 -Check the battery voltage for NDS03A.
433 +Check the battery voltage for CPN01.
399 399  
400 400  Ex1: 0x0B45 = 2885mV
401 401  
... ... @@ -402,6 +402,7 @@
402 402  Ex2: 0x0B49 = 2889mV
403 403  
404 404  
440 +
405 405  === 2.4.4  Signal Strength ===
406 406  
407 407  
... ... @@ -420,38 +420,70 @@
420 420  **99**    Not known or not detectable
421 421  
422 422  
423 -=== 2.4.5  Disalarm: (default: 0) ===
424 424  
460 +=== 2.4.5  Calculate Flag ===
425 425  
426 -(% 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.
427 427  
428 -(% 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.
429 429  
430 - (% 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.
431 431  
467 +Default value: 0. 
432 432  
433 -=== 2.4.6  Keep Status & Keep Time ===
469 +Range (6 bits): (b)000000 ~~ (b) 111111
434 434  
435 435  
436 -Shows the configure value of Alarm Base on Timeout Feature
437 437  
473 +=== 2.4.6  Alarm ===
438 438  
439 -=== 2.4.7  Timestamp ===
440 440  
476 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
441 441  
442 -Timestamp : 0x6315537b =1662342011
443 443  
444 444  
445 -=== 2.4.8  Switch Dual Channel Mode ===
480 +=== 2.4.7  Contact Status ===
446 446  
447 447  
448 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
483 +0: Open
449 449  
485 +1: Close
450 450  
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 +
451 451  == 2.5  Downlink Payload ==
452 452  
453 453  
454 -By default, NDS03A prints the downlink payload to console port.
522 +By default, CPN01 prints the downlink payload to console port.
455 455  
456 456  [[image:image-20221021111414-18.png]] ​
457 457  
... ... @@ -468,7 +468,7 @@
468 468  
469 469  * (% style="color:#037691" %)**Reset**
470 470  
471 -If payload = 0x04FF, it will reset the NDS03A
539 +If payload = 0x04FF, it will reset the NSE01
472 472  
473 473  * (% style="color:#037691" %)**INTMOD**
474 474  
... ... @@ -475,19 +475,20 @@
475 475  Downlink Payload: 06000003, Set AT+INTMOD=3
476 476  
477 477  
546 +
478 478  == 2.6  ​LED Indicator ==
479 479  
480 480  
481 -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.
482 482  
483 483  * When the device starts normally, the LED will light up for 1 second.
484 -* 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.
485 485  * For each uplink probe, LED will be on for 500ms.
486 486  
487 487  == 2.7  Alarm Base on Timeout ==
488 488  
489 489  
490 -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:
491 491  
492 492  
493 493  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -503,25 +503,17 @@
503 503  
504 504  If keep time = 0, Disable Alarm Base on Timeout feature.
505 505  
506 -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.
507 507  
508 508  
509 509  (% style="color:blue" %)**AT Command to configure:**
510 510  
511 -(% 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.
512 512  
513 -(% 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.
514 -
515 515  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
516 516  
517 517  
518 -(% style="color:blue" %)**PB15 PIN:**
519 519  
520 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
521 -
522 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
523 -
524 -
525 525  == 2.8  Set debug mode ==
526 526  
527 527  
... ... @@ -543,57 +543,54 @@
543 543  [[image:image-20221021111527-19.png]]
544 544  
545 545  
546 -== 2.10  Count Mod ==
547 547  
608 +== 2.10  Set trigger mode ==
548 548  
549 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
550 550  
551 -[[image:image-20221118092935-1.png]]
611 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
552 552  
613 +Feature: Set the trigger interrupt mode.
553 553  
554 -== 2.11  Interrupt Pin Channel Mod ==
615 +[[image:image-20221021111552-20.png]]
555 555  
556 556  
557 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
558 558  
559 -[[image:image-20221118093144-2.png]]
619 +== 2.11  Set the calculate flag ==
560 560  
561 561  
562 -== 2.12 TTRIG1/2 timeout status alarm ==
622 +Feature: Set the calculate flag
563 563  
624 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
564 564  
565 -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]]
566 566  
567 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
568 568  
569 -[[image:image-20221118093512-3.png]]
570 570  
630 +== 2.12 Set count number ==
571 571  
572 -== 2.13  Select counting mode ==
573 573  
633 +Feature: Manually set the count number
574 574  
575 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
635 +(% style="color:blue" %)**AT Command: AT+SETCNT**
576 576  
577 -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]]
578 578  
579 -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.
580 580  
581 -[[image:image-20221118093658-4.png]]
582 582  
641 +== 2.13  Set the number of data to be uploaded and the recording time ==
583 583  
584 -== 2.14  Set the number of data to be uploaded and the recording time ==
585 585  
586 -
587 587  (% style="color:blue" %)**AT Command:**
588 588  
589 -(% 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)
590 590  
591 -(% 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.
592 592  
593 593  
594 -== 2.15  Read or Clear cached data ==
595 595  
652 +== 2.14  Read or Clear cached data ==
596 596  
654 +
597 597  (% style="color:blue" %)**AT Command:**
598 598  
599 599  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -600,24 +600,27 @@
600 600  
601 601  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
602 602  
603 -[[image:image-20221118094227-5.png]]
661 +[[image:image-20221021111810-25.png||height="364" width="797"]]
604 604  
605 605  
606 -== 2.16  ​Firmware Change Log ==
607 607  
665 +== 2.15  ​Firmware Change Log ==
608 608  
609 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
610 610  
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 +
611 611  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
612 612  
613 613  
614 -== 2.17  ​Battery Analysis ==
615 615  
616 -=== 2.17.1  ​Battery Type ===
674 +== 2.16  ​Battery Analysis ==
617 617  
618 618  
619 -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 ===
620 620  
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 +
621 621  The battery is designed to last for several years depends on the actual use environment and update interval. 
622 622  
623 623  The battery-related documents as below:
... ... @@ -631,9 +631,10 @@
631 631  [[image:image-20221021111911-26.png]] ​
632 632  
633 633  
634 -=== 2.17.2  Power consumption Analyze ===
635 635  
696 +=== 2.16.2  Power consumption Analyze ===
636 636  
698 +
637 637  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.
638 638  
639 639  Instruction to use as below:
... ... @@ -653,18 +653,21 @@
653 653  [[image:1666596205057-567.png]] ​
654 654  
655 655  
656 -=== 2.17.3  ​Battery Note ===
657 657  
719 +=== 2.16.3  ​Battery Note ===
658 658  
721 +
659 659  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.
660 660  
661 661  
662 -=== 2.17.4  Replace the battery ===
663 663  
726 +=== 2.16.4  Replace the battery ===
664 664  
665 -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).
666 666  
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).
667 667  
731 +
732 +
668 668  = 3. ​ Access NB-IoT Module =
669 669  
670 670  
... ... @@ -672,12 +672,13 @@
672 672  
673 673  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/]] 
674 674  
740 +[[image:image-20221021112006-28.png]] ​
675 675  
676 -[[image:image-20221118094449-6.png]] ​
677 677  
678 678  
679 679  = 4.  Using the AT Commands =
680 680  
746 +
681 681  == 4.1  Access AT Commands ==
682 682  
683 683  
... ... @@ -724,21 +724,15 @@
724 724  
725 725  AT+ DEBUG   : Enable or Disable debug mode
726 726  
727 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
793 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
728 728  
729 -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)
730 730  
731 -AT+COUNTMOD  :  Get or Set the count mode
797 +AT+ CALCFLAG   : Get or Set the calculate flag
732 732  
733 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
799 +AT+ CLRC   : Clear current door open count
734 734  
735 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
736 736  
737 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
738 -
739 -AT+ CLRC   :  Clear current door open count
740 -
741 -
742 742  (% style="color:blue" %)**COAP Management**      
743 743  
744 744  AT+URI            : Resource parameters
... ... @@ -769,8 +769,10 @@
769 769  AT+PWORD  : Serial Access Password
770 770  
771 771  
832 +
772 772  = ​5.  FAQ =
773 773  
835 +
774 774  == 5.1 ​ How to Upgrade Firmware ==
775 775  
776 776  
... ... @@ -778,11 +778,13 @@
778 778  
779 779  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]]
780 780  
781 -(% 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.**
782 782  
783 783  
846 +
784 784  = 6.  Trouble Shooting =
785 785  
849 +
786 786  == 6.1  ​Connection problem when uploading firmware ==
787 787  
788 788  
... ... @@ -789,6 +789,7 @@
789 789  (% 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]]
790 790  
791 791  
856 +
792 792  == 6.2  AT Command input doesn't work ==
793 793  
794 794  
... ... @@ -795,19 +795,27 @@
795 795  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.
796 796  
797 797  
863 +
798 798  = 7. ​ Order Info =
799 799  
800 800  
801 -Part Number**:** NDS03A
867 +Part Number**:** CPN01
802 802  
803 803  
870 +
804 804  = 8.  Packing Info =
805 805  
806 806  
807 807  (% style="color:blue" %)**Package Includes**:
808 808  
809 -* NDS03A Open/Close Door Sensor x 1
876 +* CPN01 Open/Close Sensor x 1
877 +* External antenna x 1
810 810  
879 +(% style="color:blue" %)**Dimension and weight**:
880 +
881 +* Size: 195 x 125 x 55 mm
882 +* Weight:   420g
883 +
811 811  = 9.  Support =
812 812  
813 813  
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-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
image-20221207173200-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
image-20221207173300-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.0 KB
Content

Applications

Navigation

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