Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 81.3 >
edited by Xiaoling
on 2022/12/07 18:09
To version < 61.3 >
edited by Xiaoling
on 2022/11/17 16:39
>
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,26 +10,39 @@
10 10  
11 11  = 1.  Introduction =
12 12  
13 -== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
18 +== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
14 14  
15 15  
16 16  (((
17 -The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor.
22 +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.
23 +)))
18 18  
25 +(((
26 +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.
27 +)))
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.
29 +(((
30 +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.
31 +)))
21 21  
22 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
33 +(((
34 +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.
35 +)))
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.
37 +(((
38 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
39 +)))
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.
41 +(((
42 +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.
43 +)))
27 27  
28 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
45 +(((
46 +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)
47 +)))
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.
49 +(((
50 +To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection.
33 33  )))
34 34  
35 35  
... ... @@ -38,9 +38,10 @@
38 38  
39 39  
40 40  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
41 -* Short uplink interval for Distance Alarm
59 +* Open/Close detect
60 +* Open/Close statistics
42 42  * Monitor Battery Level
43 -* Microwave Radar for distance detection
62 +* connect two door sensors
44 44  * Datalog feature
45 45  * Uplink periodically
46 46  * Downlink to change configure
... ... @@ -51,42 +51,32 @@
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 ==
73 +== 1.3  Storage & Operation ==
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°
76 +Temperature -40°C to +85°C
65 65  
66 66  
67 -== 1.4  Storage Temperature ==
79 +== 1.4  Mechanical ==
68 68  
69 69  
70 - -40°C to +85°C
82 +[[image:image-20221117114937-4.png]]
71 71  
72 72  
85 +[[image:image-20221117114949-5.png]]
73 73  
74 74  
88 +[[image:image-20221117115010-6.png]]
75 75  
90 +
91 +
76 76  == 1.5 ​ Applications ==
77 77  
78 78  
95 +[[image:image-20221117114842-3.png]]
79 79  
80 -* Horizontal distance measurement
81 -* Liquid level measurement
82 -* Parking management system
83 -* Object proximity and presence detection
84 -* Intelligent trash can management system
85 -* Robot obstacle avoidance
86 -* Automatic control
87 -* Sewer
88 -* Bottom water level monitoring
89 89  
98 +
90 90  == 1.6  Specification ==
91 91  
92 92  
... ... @@ -93,62 +93,107 @@
93 93  (% style="color:blue" %)**Common DC Characteristics:**
94 94  
95 95  * Supply Voltage: 2.1v ~~ 3.6v
96 -* Operating Temperature: 0 ~~ 70°C
105 +* Operating Temperature: -40 ~~ 85°C
97 97  
98 98  (% style="color:blue" %)**NB-IoT Spec:**
99 99  
100 -* B1 @H-FDD: 2100MHz
101 -* B3 @H-FDD: 1800MHz
102 -* B8 @H-FDD: 900MHz
103 -* B5 @H-FDD: 850MHz
104 -* B20 @H-FDD: 800MHz
105 -* B28 @H-FDD: 700MHz
109 +* - B1 @H-FDD: 2100MHz
110 +* - B3 @H-FDD: 1800MHz
111 +* - B8 @H-FDD: 900MHz
112 +* - B5 @H-FDD: 850MHz
113 +* - B20 @H-FDD: 800MHz
114 +* - B28 @H-FDD: 700MHz
106 106  
107 -== 1.7  Installation ==
116 +== 1.7  Pin Definitions and Switch ==
108 108  
109 109  
110 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
119 +[[image:image-20221021110429-4.png]]
111 111  
112 112  
113 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
122 +=== 1.7.1  Pin Definition ===
114 114  
115 115  
125 +The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at:  [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
116 116  
117 -== 1.8  Pin Definitions and Switch ==
118 118  
119 119  
120 -[[image:1670404362039-351.png]]
129 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
121 121  
122 122  
123 -= 2.  Use NMDS200 to communicate with IoT Server =
132 +Power on Device when putting this jumper.
124 124  
134 +
135 +
136 +=== 1.7.3  BOOT MODE / SW1 ===
137 +
138 +
139 +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.
140 +
141 +2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
142 +
143 +
144 +
145 +=== 1.7.4  Reset Button ===
146 +
147 +
148 +Press to reboot the device.
149 +
150 +
151 +
152 +=== 1.7.5  LED ===
153 +
154 +
155 +The LED will blink when :
156 +
157 +1.  Boot the device in flash mode
158 +
159 +2.  Send an uplink packet
160 +
161 +
162 +
163 +== 1.8  Magnet Distance ==
164 +
165 +
166 +(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
167 +
168 +(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
169 +
170 +
171 +
172 += 2.  Use CPN01 to communicate with IoT Server =
173 +
125 125  == 2.1  How it works ==
126 126  
127 127  
128 -The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
177 +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.
129 129  
130 -The diagram below shows the working flow in the default firmware of NMDS200:
179 +The diagram below shows the working flow in the default firmware of NDS03A:
131 131  
132 132  [[image:image-20221021110615-5.png]]
133 133  
134 134  
135 -== 2.2 ​ Configure NMDS200 ==
136 136  
185 +== 2.2 ​ Configure NDS03A ==
137 137  
138 -To use NMDS200 in your city, make sure to meet below requirements:
187 +=== 2.2.1 Test Requirement ===
139 139  
189 +
190 +To use NDS03A in your city, make sure to meet below requirements:
191 +
140 140  * Your local operator has already distributed an NB-IoT Network.
141 -* The local NB-IoT network used the band that NMDS200 supports.
193 +* The local NB-IoT network used the band that NDS03A supports.
142 142  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
143 143  
144 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NMDS200 will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
196 +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.
145 145  
146 -[[image:image-20221207173300-4.png]]
198 +[[image:image-20221117142300-1.png]]
147 147  
200 + ​
148 148  
149 -=== 2.2.1 Insert NB-IoT SIM card ===
150 150  
203 +=== 2.2.2 Insert NB-IoT SIM card ===
151 151  
205 +
152 152  Insert the NB-IoT Card get from your provider.
153 153  
154 154  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -156,11 +156,12 @@
156 156  [[image:image-20221021110745-6.png]] ​
157 157  
158 158  
159 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
160 160  
214 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
161 161  
162 -User need to configure NMDS200 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NMDS200 support AT Commands, user can use a USB to TTL adapter to connect to NMDS200 and use AT Commands to configure it, as below.
163 163  
217 +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.
218 +
164 164  (% style="color:blue" %)**Connection:**
165 165  
166 166  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -182,11 +182,11 @@
182 182  
183 183  * Flow Control: (% style="color:red" %)**None**
184 184  
185 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
240 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
186 186  
187 187  ​[[image:image-20221021110817-7.png]]
188 188  
189 -NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
244 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
190 190  
191 191  
192 192  (% 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]]
... ... @@ -193,13 +193,13 @@
193 193  
194 194  
195 195  
196 -=== 2.2.3 Use CoAP protocol to uplink data ===
251 +=== 2.2.4 Use CoAP protocol to uplink data ===
197 197  
198 198  
199 199  (% 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/]]
200 200  
201 201  
202 -(% style="color:blue" %)**Use below commands in NDS03A:**
257 +(% style="color:blue" %)**Use below commands in CPN01:**
203 203  
204 204  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
205 205  
... ... @@ -212,14 +212,15 @@
212 212  [[image:image-20221021110948-8.png]]
213 213  
214 214  
215 -After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server.
270 +After configuring the server address and (% style="color:green" %)**reset CPN01**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
216 216  
217 -[[image:1670405841875-916.png]] ​
272 +[[image:image-20221021110956-9.png]] ​
218 218  
219 219  
220 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
221 221  
276 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
222 222  
278 +
223 223  (% style="color:blue" %)**AT Commands:**
224 224  
225 225  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -235,9 +235,10 @@
235 235  
236 236  ​
237 237  
238 -=== 2.2.5 Use MQTT protocol to uplink data ===
239 239  
295 +=== 2.2.6 Use MQTT protocol to uplink data ===
240 240  
297 +
241 241  (% style="color:blue" %)**AT Commands:**
242 242  
243 243  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -254,10 +254,10 @@
254 254  
255 255  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
256 256  
257 -​ [[image:image-20221118103445-7.png]]
314 +​ [[image:image-20221021111058-12.png]]
258 258  
259 259  
260 -[[image:1670405928926-116.png]]
317 +[[image:image-20221021111201-16.png||height="472" width="653"]]
261 261  
262 262  ​
263 263  
... ... @@ -264,9 +264,10 @@
264 264  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.
265 265  
266 266  
267 -=== 2.2.6 Use TCP protocol to uplink data ===
268 268  
325 +=== 2.2.7 Use TCP protocol to uplink data ===
269 269  
327 +
270 270  (% style="color:blue" %)**AT Commands:**
271 271  
272 272  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -273,19 +273,19 @@
273 273  
274 274  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
275 275  
276 -​ [[image:1670406036256-101.png||height="676" width="713"]]
334 +​ [[image:image-20221021111125-14.png]]
277 277  
278 -
279 279  [[image:image-20221021111131-15.png]]
280 280  
281 281  ​
282 282  
283 -=== 2.2.7 Change Update Interval ===
284 284  
341 +=== 2.2.8 Change Update Interval ===
285 285  
343 +
286 286  User can use below command to change the (% style="color:blue" %)**uplink interval**.
287 287  
288 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
346 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
289 289  
290 290  (% style="color:red" %)**NOTE:**
291 291  
... ... @@ -292,56 +292,81 @@
292 292  1.  By default, the device will send an uplink message every 4 hour.
293 293  
294 294  
353 +
295 295  == 2.3  Uplink Payload ==
296 296  
297 297  
298 -The uplink payload includes 23 bytes in total by default.
357 +The uplink payload includes 26 bytes in total by default.
299 299  
300 300  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.
301 301  
361 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
302 302  
303 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
304 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:90px" %)**2**|(% style="width:100px" %)**2**
305 -|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) Distance 1 |(% style="width:93px" %) Distance  2
363 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
364 +|=(% scope="row" style="width: 93px;" %)**Size(bytes)**|(% style="width:67px" %)**8**|(% style="width:40px" %)**2**|(% style="width:45px" %)**2**|(% style="width:75px" %)**1**|(% style="width:54px" %)**1**|(% style="width:62px" %)**1**|(% style="width:60px" %)**1**|(% style="width:94px" %)**3**|(% style="width:93px" %)**3**
365 +|=(% 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.4.6A0Alarm"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
306 306  
307 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
308 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
367 +(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
368 +|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)(((
309 309  **1-32 group**
310 310  )))
311 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
371 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% 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" %)...
312 312  
313 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
314 314  
315 -[[image:1670406261143-723.png]]
374 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
316 316  
317 317  
318 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
377 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
378 +|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:66px" %)**8**|(% style="width:40px" %)**2**|(% style="width:46px" %)**2**|(% style="width:70px" %)**1**|(% style="width:54px" %)**1**|(% style="width:55px" %)**1**|(% style="width:57px" %)**1**|(% style="width:86px" %)**3**|(% style="width:82px" %)**3**
379 +|=(% 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|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.4.6A0Alarm"]]|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
319 319  
320 -**0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
381 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
382 +|(% style="width:59px" %)**1**|(% style="width:67px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:66px" %)**1**|(% style="width:92px" %)**3**
383 +|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPN01-%20NB-IoT%20Outdoor%20OpenClose%20Dry%20Contact%20Sensor%C2%A0User%20Manual/#H2.4.7A0ContactStatus]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)Time stamp|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
321 321  
385 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
386 +|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
387 +**1-32 group**
388 +)))
389 +|(% style="width:102px" %)last open time (pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:88px" %)last open time(pb15)|(% style="width:63px" %)Time stamp|(% style="width:87px" %)...
390 +
391 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
392 +
393 +[[image:image-20221117145932-2.png]]
394 +
395 +
396 +The payload is ASCII string, representative same HEX:
397 +
398 +**0x **f867787050213317  0064  0ccf 19 01 00 00 000016 000017 637590df
399 +
400 +**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__(%%)**
401 +
322 322  **where:**
323 323  
324 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
404 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
325 325  
326 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
406 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
327 327  
328 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
408 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
329 329  
330 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
410 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
331 331  
332 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
412 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
333 333  
334 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
414 +* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0
335 335  
336 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
416 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
337 337  
338 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
418 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
339 339  
340 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
420 +* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
341 341  
422 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
342 342  
424 +
343 343  == 2.4  Payload Explanation and Sensor Interface ==
344 344  
427 +
345 345  === 2.4.1  Device ID ===
346 346  
347 347  
... ... @@ -356,18 +356,20 @@
356 356  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
357 357  
358 358  
442 +
359 359  === 2.4.2  Version Info ===
360 360  
361 361  
362 362  Specify the software version: 0x64=100, which means firmware version 1.00.
363 363  
364 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
448 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
365 365  
366 366  
451 +
367 367  === 2.4.3  Battery Info ===
368 368  
369 369  
370 -Check the battery voltage for NMDS200.
455 +Check the battery voltage for CPN01.
371 371  
372 372  Ex1: 0x0B45 = 2885mV
373 373  
... ... @@ -374,6 +374,7 @@
374 374  Ex2: 0x0B49 = 2889mV
375 375  
376 376  
462 +
377 377  === 2.4.4  Signal Strength ===
378 378  
379 379  
... ... @@ -392,35 +392,70 @@
392 392  **99**    Not known or not detectable
393 393  
394 394  
395 -=== 2.4.5  Distance ===
396 396  
482 +=== 2.4.5  Calculate Flag ===
397 397  
398 -[[image:1670407401682-959.png]]
399 399  
400 -(% style="color:blue" %)**Object1 Distance:**
485 +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.
401 401  
402 -Distance between sensor probe to the first object. (unit: cm)
487 +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.
403 403  
404 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
489 +Default value: 0. 
405 405  
406 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
491 +Range (6 bits): (b)000000 ~~ (b) 111111
407 407  
408 408  
409 -(% style="color:blue" %)**Object2 Distance:**
410 410  
411 -Distance between sensor probe to the second object. (unit: cm)
495 +=== 2.4.6  Alarm ===
412 412  
413 413  
414 -=== 2.4.6  Timestamp ===
498 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
415 415  
416 416  
501 +
502 +=== 2.4.7  Contact Status ===
503 +
504 +
505 +0: Open
506 +
507 +1: Close
508 +
509 +
510 +
511 +=== 2.4.8  Total pulse ===
512 +
513 +
514 +Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
515 +
516 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
517 +
518 +
519 +
520 +=== 2.4.9  The last open duration ===
521 +
522 +
523 +Dry Contact last open duration.
524 +
525 +Unit: min.
526 +
527 +[[image:image-20221021111346-17.png||height="146" width="770"]]
528 +
529 +
530 +
531 +=== 2.4.10  Timestamp ===
532 +
533 +
417 417  Timestamp : 0x6315537b =1662342011
418 418  
536 +Convert Unix timestamp to time 2022-9-5 9:40:11.
419 419  
538 +**~ **
539 +
540 +
420 420  == 2.5  Downlink Payload ==
421 421  
422 422  
423 -By default, NMDS200 prints the downlink payload to console port.
544 +By default, CPN01 prints the downlink payload to console port.
424 424  
425 425  [[image:image-20221021111414-18.png]] ​
426 426  
... ... @@ -437,7 +437,7 @@
437 437  
438 438  * (% style="color:#037691" %)**Reset**
439 439  
440 -If payload = 0x04FF, it will reset the NMDS200
561 +If payload = 0x04FF, it will reset the NSE01
441 441  
442 442  * (% style="color:#037691" %)**INTMOD**
443 443  
... ... @@ -444,23 +444,22 @@
444 444  Downlink Payload: 06000003, Set AT+INTMOD=3
445 445  
446 446  
568 +
447 447  == 2.6  ​LED Indicator ==
448 448  
449 449  
450 -The NMDS200 has an internal LED which is to show the status of different states.
572 +The CPN01 has an internal LED which is to show the status of different states.
451 451  
452 452  * When the device starts normally, the LED will light up for 1 second.
453 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
575 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
454 454  * For each uplink probe, LED will be on for 500ms.
455 455  
578 +== 2.7  Alarm Base on Timeout ==
456 456  
457 457  
458 -== 2.7  Distance alarm function ==
581 +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:
459 459  
460 460  
461 -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:
462 -
463 -
464 464  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
465 465  
466 466  Keep Status = 1: Monitor Close to Open event
... ... @@ -474,25 +474,17 @@
474 474  
475 475  If keep time = 0, Disable Alarm Base on Timeout feature.
476 476  
477 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
597 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
478 478  
479 479  
480 480  (% style="color:blue" %)**AT Command to configure:**
481 481  
482 -(% style="color:blue" %)**PB14 PIN:**
602 +(% 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.
483 483  
484 -(% 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.
485 -
486 486  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
487 487  
488 488  
489 -(% style="color:blue" %)**PB15 PIN:**
490 490  
491 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
492 -
493 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
494 -
495 -
496 496  == 2.8  Set debug mode ==
497 497  
498 498  
... ... @@ -514,57 +514,54 @@
514 514  [[image:image-20221021111527-19.png]]
515 515  
516 516  
517 -== 2.10  Count Mod ==
518 518  
630 +== 2.10  Set trigger mode ==
519 519  
520 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
521 521  
522 -[[image:image-20221118092935-1.png]]
633 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
523 523  
635 +Feature: Set the trigger interrupt mode.
524 524  
525 -== 2.11  Interrupt Pin Channel Mod ==
637 +[[image:image-20221021111552-20.png]]
526 526  
527 527  
528 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
529 529  
530 -[[image:image-20221118093144-2.png]]
641 +== 2.11  Set the calculate flag ==
531 531  
532 532  
533 -== 2.12 TTRIG1/2 timeout status alarm ==
644 +Feature: Set the calculate flag
534 534  
646 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
535 535  
536 -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.
648 +[[image:image-20221021111711-22.png]]
537 537  
538 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
539 539  
540 -[[image:image-20221118093512-3.png]]
541 541  
652 +== 2.12 Set count number ==
542 542  
543 -== 2.13  Select counting mode ==
544 544  
655 +Feature: Manually set the count number
545 545  
546 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
657 +(% style="color:blue" %)**AT Command: AT+SETCNT**
547 547  
548 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
659 +[[image:image-20221021111748-24.png]]
549 549  
550 -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.
551 551  
552 -[[image:image-20221118093658-4.png]]
553 553  
663 +== 2.13  Set the number of data to be uploaded and the recording time ==
554 554  
555 -== 2.14  Set the number of data to be uploaded and the recording time ==
556 556  
557 -
558 558  (% style="color:blue" %)**AT Command:**
559 559  
560 -(% 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)
668 +(% 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)
561 561  
562 -(% 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.
670 +(% 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.
563 563  
564 564  
565 -== 2.15  Read or Clear cached data ==
566 566  
674 +== 2.14  Read or Clear cached data ==
567 567  
676 +
568 568  (% style="color:blue" %)**AT Command:**
569 569  
570 570  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -571,24 +571,27 @@
571 571  
572 572  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
573 573  
574 -[[image:image-20221118094227-5.png]]
683 +[[image:image-20221021111810-25.png||height="364" width="797"]]
575 575  
576 576  
577 -== 2.16  ​Firmware Change Log ==
578 578  
687 +== 2.15  ​Firmware Change Log ==
579 579  
580 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
581 581  
690 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
691 +
582 582  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
583 583  
584 584  
585 -== 2.17  ​Battery Analysis ==
586 586  
587 -=== 2.17.1  ​Battery Type ===
696 +== 2.16  ​Battery Analysis ==
588 588  
589 589  
590 -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.
699 +=== 2.16.1  ​Battery Type ===
591 591  
701 +
702 +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.
703 +
592 592  The battery is designed to last for several years depends on the actual use environment and update interval. 
593 593  
594 594  The battery-related documents as below:
... ... @@ -602,9 +602,10 @@
602 602  [[image:image-20221021111911-26.png]] ​
603 603  
604 604  
605 -=== 2.17.2  Power consumption Analyze ===
606 606  
718 +=== 2.16.2  Power consumption Analyze ===
607 607  
720 +
608 608  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.
609 609  
610 610  Instruction to use as below:
... ... @@ -624,18 +624,21 @@
624 624  [[image:1666596205057-567.png]] ​
625 625  
626 626  
627 -=== 2.17.3  ​Battery Note ===
628 628  
741 +=== 2.16.3  ​Battery Note ===
629 629  
743 +
630 630  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.
631 631  
632 632  
633 -=== 2.17.4  Replace the battery ===
634 634  
748 +=== 2.16.4  Replace the battery ===
635 635  
636 -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).
637 637  
751 +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).
638 638  
753 +
754 +
639 639  = 3. ​ Access NB-IoT Module =
640 640  
641 641  
... ... @@ -643,12 +643,13 @@
643 643  
644 644  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/]] 
645 645  
762 +[[image:image-20221021112006-28.png]] ​
646 646  
647 -[[image:image-20221118094449-6.png]] ​
648 648  
649 649  
650 650  = 4.  Using the AT Commands =
651 651  
768 +
652 652  == 4.1  Access AT Commands ==
653 653  
654 654  
... ... @@ -695,21 +695,15 @@
695 695  
696 696  AT+ DEBUG   : Enable or Disable debug mode
697 697  
698 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
815 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
699 699  
700 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
817 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
701 701  
702 -AT+COUNTMOD  :  Get or Set the count mode
819 +AT+ CALCFLAG   : Get or Set the calculate flag
703 703  
704 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
821 +AT+ CLRC   : Clear current door open count
705 705  
706 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
707 707  
708 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
709 -
710 -AT+ CLRC   :  Clear current door open count
711 -
712 -
713 713  (% style="color:blue" %)**COAP Management**      
714 714  
715 715  AT+URI            : Resource parameters
... ... @@ -740,8 +740,10 @@
740 740  AT+PWORD  : Serial Access Password
741 741  
742 742  
854 +
743 743  = ​5.  FAQ =
744 744  
857 +
745 745  == 5.1 ​ How to Upgrade Firmware ==
746 746  
747 747  
... ... @@ -749,11 +749,13 @@
749 749  
750 750  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]]
751 751  
752 -(% 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.**
865 +(% 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.**
753 753  
754 754  
868 +
755 755  = 6.  Trouble Shooting =
756 756  
871 +
757 757  == 6.1  ​Connection problem when uploading firmware ==
758 758  
759 759  
... ... @@ -760,6 +760,7 @@
760 760  (% 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]]
761 761  
762 762  
878 +
763 763  == 6.2  AT Command input doesn't work ==
764 764  
765 765  
... ... @@ -766,19 +766,27 @@
766 766  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.
767 767  
768 768  
885 +
769 769  = 7. ​ Order Info =
770 770  
771 771  
772 -Part Number**:** NDS03A
889 +Part Number**:** CPN01
773 773  
774 774  
892 +
775 775  = 8.  Packing Info =
776 776  
777 777  
778 778  (% style="color:blue" %)**Package Includes**:
779 779  
780 -* NDS03A Open/Close Door Sensor x 1
898 +* CPN01 Open/Close Sensor x 1
899 +* External antenna x 1
781 781  
901 +(% style="color:blue" %)**Dimension and weight**:
902 +
903 +* Size: 195 x 125 x 55 mm
904 +* Weight:   420g
905 +
782 782  = 9.  Support =
783 783  
784 784  
1670404362039-351.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -492.6 KB
Content
1670405841875-916.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.0 KB
Content
1670406261143-723.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content
1670407401682-959.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -23.7 KB
Content
LMDS200_10.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 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