Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 81.4 >
edited by Xiaoling
on 2022/12/07 18:13
To version < 41.1 >
edited by Edwin Chen
on 2022/10/23 00:08
>
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 +CPN01- NB-IoT Outdoor Open/Close Dry Contact Sensor User Manual
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -1,46 +1,34 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg]]
2 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/WebHome/1652856952171-363.png?rev=1.1||alt="1652856952171-363.png" height="578" width="588"]]
3 3  
4 +{{toc/}}
4 4  
5 -**Table of Contents：**
6 += **1. Introduction** =
6 6  
8 +== **1.1 ​**What is CPN01 **NB-IoT** Pulse/Contact Sensor ==
7 7  
10 +The Dragino CPN01 is an (% style="color:blue" %)**NB-IoT Dry Contact Sensor**(%%). It detects open/close status and uplinks the info to IoT server via NB-IoT network. User can see the (% style="color:blue" %)**dry contact status, open time, and open counts**(%%) in the IoT Server.
8 8  
12 +The CPN01 will send periodically data every day as well as for each dry contact action. It also counts the contact open times and calculates the last open duration. Users can also disable the uplink for each Open/Close event, instead, device can count each open event and uplink periodically.
9 9  
14 +CPN01 has** (% style="color:blue" %)Open-Alarm feature(%%)**, user can set this feature so CPN01 will send an alarm if the contact has been open exceeds a certain time.
10 10  
11 -= 1.  Introduction =
16 +CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures.
12 12  
13 -== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
18 +NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
19 +\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
20 +\\CPN01 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
21 +\\To use CPN01, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that CPN01 supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into CPN01 to get NB-IoT network connection.
14 14  
23 +​
15 15  
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.
25 +== **​1.2 Features** ==
18 18  
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.
21 -
22 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
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.
25 -
26 -NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technology**(%%) developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
27 -
28 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
29 -
30 -NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
31 -
32 -To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection.
33 -)))
34 -
35 -
36 -
37 -== ​1.2  Features ==
38 -
39 -
40 40  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
41 -* Short uplink interval for Distance Alarm
28 +* Open/Close detect
29 +* Open/Close statistics
42 42  * Monitor Battery Level
43 -* Microwave Radar for distance detection
31 +* Uplink on periodically and open/close event
44 44  * Datalog feature
45 45  * Uplink periodically
46 46  * Downlink to change configure
... ... @@ -51,104 +51,106 @@
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 ==
42 +== **1.3  Specification** ==
55 55  
44 +**Common DC Characteristics:**
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°
46 +* Supply Voltage: 2.1v ~~ 3.6v
47 +* Operating Temperature: -40 ~~ 85°C
65 65  
49 +**NB-IoT Spec:**
66 66  
67 -== 1.4  Storage Temperature ==
51 +* - B1 @H-FDD: 2100MHz
52 +* - B3 @H-FDD: 1800MHz
53 +* - B8 @H-FDD: 900MHz
54 +* - B5 @H-FDD: 850MHz
55 +* - B20 @H-FDD: 800MHz
56 +* - B28 @H-FDD: 700MHz
68 68  
58 +== **1.4 Installation** ==
69 69  
70 - -40°C to +85°C
60 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
71 71  
62 +[[image:image-20221021110329-1.png]]
72 72  
64 +[[image:image-20221022234602-2.png||height="288" width="922"]]
73 73  
74 74  
67 +== **1.5 ​Applications** ==
75 75  
76 -== 1.5 ​ Applications ==
69 +* Open/Close Detection
70 +* Pulse meter application
71 +* Dry Contact Detection
77 77  
73 +== **1.6 Mechanical** ==
78 78  
75 +​[[image:image-20221021110415-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
77 +== ** 1.7 Pin Definitions and Switch** ==
89 89  
90 -== 1.6  Specification ==
79 +[[image:image-20221021110429-4.png]]
91 91  
81 +=== **1.7.1 Pin Definition** ===
92 92  
93 -(% style="color:blue" %)**Common DC Characteristics:**
83 +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]]**.
94 94  
95 -* Supply Voltage: 2.1v ~~ 3.6v
96 -* Operating Temperature: 0 ~~ 70°C
97 97  
98 -(% style="color:blue" %)**NB-IoT Spec:**
86 +=== **1.7.2 Jumper JP2(Power ON/OFF)** ===
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
88 +Power on Device when putting this jumper.
106 106  
107 -== 1.7  Installation ==
108 108  
91 +=== **1.7.3 BOOT MODE / SW1** ===
109 109  
110 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
111 111  
94 +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.
112 112  
113 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
96 +2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
114 114  
115 115  
99 +=== **1.7.4 Reset Button** ===
116 116  
117 -== 1.8  Pin Definitions and Switch ==
118 118  
102 +Press to reboot the device.
119 119  
120 -[[image:1670404362039-351.png]]
121 121  
105 +=== **1.7.5 LED** ===
122 122  
123 -= 2.  Use NMDS200 to communicate with IoT Server =
124 124  
125 -== 2.1  How it works ==
108 +The LED will blink when :
126 126  
110 +1. Boot the device in flash mode
111 +1. Send an uplink packet
127 127  
128 -The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
113 += **2.  Use CPN01 to communicate with IoT Server** =
129 129  
130 -The diagram below shows the working flow in the default firmware of NMDS200:
115 +== **2.1  How it works** ==
131 131  
117 +The CPN01 is equipped with an NB-IoT module, the pre-loaded firmware in CPN01 will get **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.
118 +
119 +The diagram below shows the working flow in the default firmware of CPN01:
120 +
132 132  [[image:image-20221021110615-5.png]]
133 133  
134 134  
135 -== 2.2 ​ Configure NMDS200 ==
124 +== **2.2 ​ Configure CPN01** ==
136 136  
126 +=== **2.2.1 Test Requirement** ===
137 137  
138 -To use NMDS200 in your city, make sure to meet below requirements:
128 +To use CPN01 in your city, make sure to meet below requirements:
139 139  
140 140  * Your local operator has already distributed an NB-IoT Network.
141 -* The local NB-IoT network used the band that NMDS200 supports.
131 +* The local NB-IoT network used the band that CPN01 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.
134 +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 CoAP(120.24.4.116:5683) or raw UDP(120.24.4.116:5601) or MQTT(120.24.4.116:1883)or TCP(120.24.4.116:5600)protocol to send data to the test server.
145 145  
146 -[[image:image-20221207173300-4.png]]
136 +[[image:image-20221023000439-3.png]]
147 147  
138 + ​
148 148  
149 -=== 2.2.1 Insert NB-IoT SIM card ===
140 +=== **2.2.2 Insert SIM card** ===
150 150  
151 -
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,227 +156,187 @@
156 156  [[image:image-20221021110745-6.png]] ​
157 157  
158 158  
159 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
149 +=== **2.2.3 Connect USB – TTL to CPN01 to configure it** ===
160 160  
151 +User need to configure CPN01 via serial port to set the **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.
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.
153 +**Connection:**
163 163  
164 -(% style="color:blue" %)**Connection:**
155 + USB TTL GND <~-~-~-~-> GND
165 165  
166 -(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
157 + USB TTL TXD <~-~-~-~-> UART_RXD
167 167  
168 -(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD**
159 + USB TTL RXD <~-~-~-~-> UART_TXD
169 169  
170 -(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD**
171 -
172 -
173 173  In the PC, use below serial tool settings:
174 174  
175 -* Baud:  (% style="color:red" %)**9600**
163 +* Baud:  **9600**
164 +* Data bits:** 8**
165 +* Stop bits: **1**
166 +* Parity:  **None**
167 +* Flow Control: **None**
176 176  
177 -* Data bits:** (% style="color:red" %)8(%%)**
169 +Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
178 178  
179 -* Stop bits: (% style="color:red" %)**1**
180 -
181 -* Parity:  (% style="color:red" %)**None**
182 -
183 -* Flow Control: (% style="color:red" %)**None**
184 -
185 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
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.
173 +CPN01 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 -(% 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]]
176 +**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 193  
178 +=== **2.2.4 Use CoAP protocol to uplink data** ===
194 194  
180 +**Note: if you don't have CoAP server, you can refer this link to set up one: **[[**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/]]
195 195  
196 -=== 2.2.3 Use CoAP protocol to uplink data ===
182 +**Use below commands:**
197 197  
184 +* **AT+PRO=1**   ~/~/ Set to use CoAP protocol to uplink
185 +* **AT+SERVADDR=120.24.4.116,5683   ** ~/~/ to set CoAP server address and port
186 +* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path
198 198  
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 -
201 -
202 -(% style="color:blue" %)**Use below commands in NDS03A:**
203 -
204 -* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
205 -
206 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
207 -
208 -* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
209 -
210 210  For parameter description, please refer to AT command set
211 211  
212 212  [[image:image-20221021110948-8.png]]
213 213  
192 +After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server.
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.
194 +[[image:image-20221021110956-9.png]] ​
216 216  
217 -[[image:1670405841875-916.png]] ​
196 +=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** ===
218 218  
198 +This feature is supported since firmware version v1.0.1
219 219  
220 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
200 +* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
201 +* **AT+SERVADDR=120.24.4.116,5601   ** ~/~/ to set UDP server address and port
202 +* **AT+CFM=1       ** ~/~/If the server does not respond, this command is unnecessary
221 221  
222 -
223 -(% style="color:blue" %)**AT Commands:**
224 -
225 -* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
226 -
227 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  Set UDP server address and port
228 -
229 -* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
230 -
231 231  ​ [[image:image-20221021111025-10.png]]
232 232  
233 -
234 234  [[image:image-20221021111033-11.png||height="241" width="576"]]
235 235  
236 236  ​
237 237  
238 -=== 2.2.5 Use MQTT protocol to uplink data ===
210 +=== **2.2.6 Use MQTT protocol to uplink data** ===
239 239  
212 +This feature is supported since firmware version v110
240 240  
241 -(% style="color:blue" %)**AT Commands:**
214 +* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
215 +* **AT+SERVADDR=120.24.4.116,1883   ** ~/~/Set MQTT server address and port
216 +* **AT+CLIENT=CLIENT       ** ~/~/Set up the CLIENT of MQTT
217 +* **AT+UNAME=UNAME                               **~/~/Set the username of MQTT
218 +* **AT+PWD=PWD                                        **~/~/Set the password of MQTT
219 +* **AT+PUBTOPIC=NSE01_PUB                    **~/~/Set the sending topic of MQTT
220 +* **AT+SUBTOPIC=NSE01_SUB          ** ~/~/Set the subscription topic of MQTT
242 242  
243 -* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
222 +​ [[image:image-20221021111058-12.png]]
244 244  
245 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
224 +[[image:image-20221021111108-13.png]]
246 246  
247 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
248 -
249 -* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
250 -
251 -* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
252 -
253 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/  Set the sending topic of MQTT
254 -
255 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
256 -
257 -​ [[image:image-20221118103445-7.png]]
258 -
259 -
260 -[[image:1670405928926-116.png]]
261 -
262 262  ​
263 263  
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.
228 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
265 265  
230 +=== **2.2.7 Use TCP protocol to uplink data** ===
266 266  
267 -=== 2.2.6 Use TCP protocol to uplink data ===
232 +This feature is supported since firmware version v110
268 268  
234 +* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
235 +* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ to set TCP server address and port
269 269  
270 -(% style="color:blue" %)**AT Commands:**
237 +​ [[image:image-20221021111125-14.png]]
271 271  
272 -* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
273 -
274 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
275 -
276 -​ [[image:1670406036256-101.png||height="676" width="713"]]
277 -
278 -
279 279  [[image:image-20221021111131-15.png]]
280 280  
281 281  ​
282 282  
283 -=== 2.2.7 Change Update Interval ===
243 +=== **2.2.8 Change Update Interval** ===
284 284  
245 +User can use below command to change the **uplink interval**.
285 285  
286 -User can use below command to change the (% style="color:blue" %)**uplink interval**.
247 +* **AT+TDC=600      ** ~/~/ Set Update Interval to 600s
287 287  
288 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
249 +**NOTE:**
289 289  
290 -(% style="color:red" %)**NOTE:**
251 +**~1. By default, the device will send an uplink message every 1 hour.**
291 291  
292 -1.  By default, the device will send an uplink message every 4 hour.
253 +== **2.3  Uplink Payload** ==
293 293  
255 +In this mode, uplink payload includes 87 bytes in total by default.
294 294  
295 -== 2.3  Uplink Payload ==
257 +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.
296 296  
259 +|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**2**|**2**|4
260 +|**Value**|[[Device ID>>path:#H2.4.1A0A0DeviceID]]|[[Ver>>path:#H2.4.2A0VersionInfo]]|[[BAT>>path:#H2.4.3A0BatteryInfo]]|[[Signal Strength>>path:#H2.4.4A0SignalStrength]]|MOD|[[Interrupt>>path:#H2.4.8A0DigitalInterrupt]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|Time stamp
297 297  
298 -The uplink payload includes 23 bytes in total by default.
262 +|2|2|4|8 group
263 +|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|...
299 299  
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.
265 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
301 301  
267 +[[image:image-20221021111201-16.png||height="572" width="792"]]
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
269 +The payload is ASCII string, representative same HEX:
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" %)(((
309 -**1-32 group**
310 -)))
311 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
271 +**0x (% style="color:red" %)__0xf867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %)_0c78__  __(% style="color:#00b0f0" %)17__  __(% style="color:#7030a0" %)01__  __(% style="color:#d60093" %)00__  __(% style="color:#a14d07" %)01 __ __(% style="color:#0020b0" %)__ __00__  __(% style="color:#420042" %)000009__  __(% style="color:#663300" %) 000002__  __(% style="color:#d60093" %)6315537bb__  __(% style="color:#663300" %)// 0100000b02000002663510fed__  __0100000e0200000263510f39 010000000000000063510e85 010000000000000063510d2e 010000000000000063510c7a 010000000000000063510bc6 010000000000000063510954 010000000000000063510882 //(%%)**
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.
273 +where:
274 +*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
314 314  
315 -[[image:1670406261143-723.png]]
276 +*(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
316 316  
278 +*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
317 317  
318 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
280 +*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
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__(%%)**
282 +*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
321 321  
322 -**where:**
284 +*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00= 0
323 323  
324 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
286 +*(% style="color:#037691" %) **Contact Status:**(%%) 0x00= 0
325 325  
326 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
288 +*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0
327 327  
328 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
290 +*(% style="color:#037691" %) **Total pulse:0x09 =0**
329 329  
330 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
292 +*(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2
331 331  
332 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
294 +*(% style="color:#037691" %)**Time stamp :**(%%) 0x6315537b =1662342011
333 333  
334 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
296 +*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000b0200002663510fed
335 335  
336 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
298 +*(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
337 337  
338 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
300 +== **2.4  Payload Explanation and Sensor Interface** ==
339 339  
340 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
302 +=== **2.4.1  Device ID** ===
341 341  
304 +By default, the Device ID equal to the last 15 bits of IMEI.
342 342  
343 -== 2.4  Payload Explanation and Sensor Interface ==
306 +User can use **AT+DEUI** to set Device ID
344 344  
345 -=== 2.4.1  Device ID ===
346 -
347 -
348 -By default, the Device ID is equal to the last 15 bits of IMEI.
349 -
350 -User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
351 -
352 352  **Example:**
353 353  
354 354  AT+DEUI=868411056754138
355 355  
356 -The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
312 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
357 357  
314 +=== **2.4.2  Version Info** ===
358 358  
359 -=== 2.4.2  Version Info ===
316 +Specify the software version: 0x64=100, means firmware version 1.00.
360 360  
318 +For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0.
361 361  
362 -Specify the software version: 0x64=100, which means firmware version 1.00.
320 +=== **2.4.3  Battery Info** ===
363 363  
364 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
322 +Check the battery voltage for CPN01.
365 365  
366 -
367 -=== 2.4.3  Battery Info ===
368 -
369 -
370 -Check the battery voltage for NMDS200.
371 -
372 372  Ex1: 0x0B45 = 2885mV
373 373  
374 374  Ex2: 0x0B49 = 2889mV
375 375  
328 +=== **2.4.4  Signal Strength** ===
376 376  
377 -=== 2.4.4  Signal Strength ===
378 -
379 -
380 380  NB-IoT Network signal Strength.
381 381  
382 382  **Ex1: 0x1d = 29**
... ... @@ -391,43 +391,58 @@
391 391  
392 392  **99**    Not known or not detectable
393 393  
344 +=== **2.4.5 Calculate Flag** ===
394 394  
395 -=== 2.4.5  Distance ===
346 +The calculate flag is a user define field, IoT server can use this filed to handle different meter with different pulse factor. For example, if there are 100 water meters, meter 1 ~~50 are 1 liter/pulse and meter 51 ~~ 100 has 1.5 liter/pulse.
396 396  
348 +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.
397 397  
398 -[[image:1670407401682-959.png]]
350 +Default value: 0. 
399 399  
400 -(% style="color:blue" %)**Object1 Distance:**
352 +Range (6 bits): (b)000000 ~~ (b) 111111
401 401  
402 -Distance between sensor probe to the first object. (unit: cm)
354 +=== **2.4.6  Alarm** ===
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
356 +See [[Alarm Base on Timeout>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H3.5AlarmBaseonTimeout]]
405 405  
406 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
358 +=== **2.4.7 Contact Status** ===
407 407  
360 +0: Open
408 408  
409 -(% style="color:blue" %)**Object2 Distance:**
362 +1: Close
410 410  
411 -Distance between sensor probe to the second object. (unit: cm)
364 +=== **2.4.8 Total pulse** ===
412 412  
366 +Total pulse/counting base on dry [[contact trigger event>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.2SensorConfiguration2CFPORT3D4]]
413 413  
414 -=== 2.4.6  Timestamp ===
368 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
415 415  
370 +=== **2.4.9 The last open duration** ===
416 416  
417 -Timestamp : 0x6315537b =1662342011
372 +Dry Contact last open duration.
418 418  
374 +Unit: min.
419 419  
420 -== 2.5  Downlink Payload ==
376 +[[image:image-20221021111346-17.png||height="146" width="770"]]
421 421  
422 422  
423 -By default, NMDS200 prints the downlink payload to console port.
379 +=== **2.4.10  Timestamp** ===
424 424  
425 -[[image:image-20221021111414-18.png]] ​
381 +Time stamp : 0x6315537b =1662342011
426 426  
383 +Convert Unix timestamp to time 2022-9-5 9:40:11.
427 427  
385 +**~ **
386 +
387 +== **2.5  Downlink Payload** ==
388 +
389 +By default, CPN01 prints the downlink payload to console port.
390 +
391 +[[image:image-20221021111414-18.png]] ​
392 +
428 428  **Examples:**
429 429  
430 -* (% style="color:#037691" %)**Set TDC**
395 +* **Set TDC**
431 431  
432 432  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
433 433  
... ... @@ -435,202 +435,171 @@
435 435  
436 436  Payload:    01 00 00 3C    TDC=60S
437 437  
438 -* (% style="color:#037691" %)**Reset**
403 +* **Reset**
439 439  
440 -If payload = 0x04FF, it will reset the NMDS200
405 +If payload = 0x04FF, it will reset the NSE01
441 441  
442 -* (% style="color:#037691" %)**INTMOD**
407 +* **INTMOD**
443 443  
444 444  Downlink Payload: 06000003, Set AT+INTMOD=3
445 445  
411 +== **2.6  ​LED Indicator** ==
446 446  
447 -== 2.6  ​LED Indicator ==
413 +The CPN01 has an internal LED which is to show the status of different state.
448 448  
415 +* When power on, CPN01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
416 +* Then the LED will be on for 1 second means device is boot normally.
417 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
418 +* For each uplink probe, LED will be on for 500ms.
449 449  
450 -The NMDS200 has an internal LED which is to show the status of different states.
420 +== **2.7  Alarm Base on Timeout** ==
451 451  
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.
454 -* For each uplink probe, LED will be on for 500ms.
422 +CPL01 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:
455 455  
456 456  
425 +**~1. Keep Status: Status to be monitor**
457 457  
458 -== 2.7  Distance alarm function ==
427 +Keep Status = 1: Monitor Close to Open event
459 459  
429 +Keep Status = 0: Monitor Open to Close event
460 460  
461 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
462 462  
463 -**Example 1:**
432 +**2. Keep Time: Timeout to send an Alarm**
464 464  
465 -AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
434 +Range 0 ~~ 65535(0xFFFF) seconds.
466 466  
467 -AT+ ALARM2 =min,max
436 +If keep time = 0, Disable Alarm Base on Timeout feature.
468 468  
438 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
469 469  
470 -**Example 2:**
471 471  
472 -AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
441 +**AT Command** to configure:
473 473  
443 +**AT+TTRIG=1,30**  ~-~-> When the **Keep Status** change from connect to disconnect, and device remains in disconnect status for more than 30 seconds. CPL01 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.
474 474  
475 -== 2.8  Set debug mode ==
445 +**AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm.
476 476  
447 +== **2.8 Set debug mode** ==
477 477  
478 478  Feature: Enable or Disable debug mode
479 479  
480 -(% style="color:blue" %)**AT Command: AT+DEBUG**
481 481  
452 +**AT Command: AT+DEBUG**
453 +
482 482  [[image:image-20221021111629-21.png]]
483 483  
456 +== **2.9 Clear Flash Record** ==
484 484  
485 -
486 -== 2.9  Clear Flash Record ==
487 -
488 -
489 489  Feature: Clear flash storage for data log feature.
490 490  
491 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
460 +**AT Command: AT+CLRDTA**
492 492  
493 493  [[image:image-20221021111527-19.png]]
494 494  
464 +== ** 2.10 Set trigger mode** ==
495 495  
496 -== 2.10  Count Mod ==
466 +➢ AT Command: **AT+TTRMOD**
497 497  
468 +Feature: Set the trigger interrupt mode.
498 498  
499 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
470 +[[image:image-20221021111552-20.png]]
500 500  
501 -[[image:image-20221118092935-1.png]]
472 +== **2.11 Set the calculate flag** ==
502 502  
474 +Feature: Set the calculate flag
503 503  
504 -== 2.11  Interrupt Pin Channel Mod ==
476 +**AT Command: AT+CALCFLAG**
505 505  
478 +[[image:image-20221021111711-22.png]]
506 506  
507 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
480 +== **2.12 Set count number** ==
508 508  
509 -[[image:image-20221118093144-2.png]]
482 +Feature: Manually set the count number
510 510  
484 +**AT Command: AT+SETCNT**
511 511  
512 -== 2.12 TTRIG1/2 timeout status alarm ==
486 +[[image:image-20221021111748-24.png]]
513 513  
488 +== **2.13 Set the number of data to be uploaded and the recording time** ==
514 514  
515 -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.
490 +➢ AT Command:
516 516  
517 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
492 +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)
518 518  
519 -[[image:image-20221118093512-3.png]]
520 520  
495 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
521 521  
522 -== 2.13  Select counting mode ==
497 +== **2.14 Read or Clear cached data** ==
523 523  
499 +➢ AT Command:
524 524  
525 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
501 +AT+CDP    ~/~/ Read cached data
526 526  
527 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
503 +[[image:image-20221021111810-25.png||height="364" width="797"]]
528 528  
529 -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.
530 530  
531 -[[image:image-20221118093658-4.png]]
506 +AT+CDP=0    ~/~/ Clear cached data ​
532 532  
508 +== **2.15  ​Firmware Change Log** ==
533 533  
534 -== 2.14  Set the number of data to be uploaded and the recording time ==
510 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
535 535  
512 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
536 536  
537 -(% style="color:blue" %)**AT Command:**
514 +== **2.16  ​Battery Analysis** ==
538 538  
539 -(% 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)
516 +=== **2.16.1  ​Battery Type** ===
540 540  
541 -(% 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.
518 +The CPN01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-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.
542 542  
520 +The battery is designed to last for several years depends on the actually use environment and update interval. 
543 543  
544 -== 2.15  Read or Clear cached data ==
522 +The battery related documents as below:
545 545  
546 -
547 -(% style="color:blue" %)**AT Command:**
548 -
549 -(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
550 -
551 -(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
552 -
553 -[[image:image-20221118094227-5.png]]
554 -
555 -
556 -== 2.16  ​Firmware Change Log ==
557 -
558 -
559 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
560 -
561 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
562 -
563 -
564 -== 2.17  ​Battery Analysis ==
565 -
566 -=== 2.17.1  ​Battery Type ===
567 -
568 -
569 -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.
570 -
571 -The battery is designed to last for several years depends on the actual use environment and update interval. 
572 -
573 -The battery-related documents as below:
574 -
575 575  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
576 -
577 577  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
578 -
579 579  * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
580 580  
581 581  [[image:image-20221021111911-26.png]] ​
582 582  
530 +=== **2.16.2  Power consumption Analyze** ===
583 583  
584 -=== 2.17.2  Power consumption Analyze ===
585 -
586 -
587 587  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.
588 588  
589 589  Instruction to use as below:
590 590  
591 -(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
536 +**Step 1:  **Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
592 592  
593 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
538 +**Step 2: ** Open it and choose
594 594  
595 595  * Product Model
596 -
597 597  * Uplink Interval
598 -
599 599  * Working Mode
600 600  
601 601  And the Life expectation in difference case will be shown on the right.
602 602  
603 -[[image:1666596205057-567.png]] ​
546 +[[image:image-20221021111923-27.png||height="253" width="783"]] ​
604 604  
548 +=== **2.16.3  ​Battery Note** ===
605 605  
606 -=== 2.17.3  ​Battery Note ===
607 -
608 -
609 609  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.
610 610  
552 +=== **2.16.4  Replace the battery** ===
611 611  
612 -=== 2.17.4  Replace the battery ===
554 +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).
613 613  
556 += **3. ​ Access NB-IoT Module** =
614 614  
615 -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).
616 -
617 -
618 -= 3. ​ Access NB-IoT Module =
619 -
620 -
621 621  Users can directly access the AT command set of the NB-IoT module.
622 622  
623 623  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/]] 
624 624  
562 +[[image:image-20221021112006-28.png]] ​
625 625  
626 -[[image:image-20221118094449-6.png]] ​
564 += **4.  Using the AT Commands** =
627 627  
566 +== **4.1  Access AT Commands** ==
628 628  
629 -= 4.  Using the AT Commands =
630 -
631 -== 4.1  Access AT Commands ==
632 -
633 -
634 634  See this link for detail:  [[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
635 635  
636 636  AT+<CMD>?  : Help on <CMD>
... ... @@ -641,9 +641,8 @@
641 641  
642 642  AT+<CMD>=?  : Get the value
643 643  
578 +**General Commands**      
644 644  
645 -(% style="color:blue" %)**General Commands**      
646 -
647 647  AT  : Attention       
648 648  
649 649  AT?  : Short Help     
... ... @@ -666,41 +666,35 @@
666 666  
667 667  AT+SERVADDR  : Server Address
668 668  
669 -AT+TR      :  Get or Set record time
602 +AT+TR      : Get or Set record time"
670 670  
604 +
671 671  AT+NOUD      : Get or Set the number of data to be uploaded
672 672  
673 -AT+CDP     :  Read or Clear cached data
674 674  
675 -AT+ DEBUG   : Enable or Disable debug mode
608 +AT+CDP     : Read or Clear cached data
676 676  
677 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
678 678  
679 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
611 +AT+ DEBUG   : Enable or Disable debug mode
680 680  
681 -AT+COUNTMOD  :  Get or Set the count mode
613 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
682 682  
683 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
615 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
684 684  
685 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
617 +AT+ CALCFLAG   : Get or Set the calculate flag
686 686  
687 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
619 +AT+ CLRC   : Clear current door open count
688 688  
689 -AT+ CLRC   :  Clear current door open count
621 +**COAP Management**      
690 690  
691 -
692 -(% style="color:blue" %)**COAP Management**      
693 -
694 694  AT+URI            : Resource parameters
695 695  
625 +**UDP Management**
696 696  
697 -(% style="color:blue" %)**UDP Management**
698 -
699 699  AT+CFM          : Upload confirmation mode (only valid for UDP)
700 700  
629 +**MQTT Management**
701 701  
702 -(% style="color:blue" %)**MQTT Management**
703 -
704 704  AT+CLIENT               : Get or Set MQTT client
705 705  
706 706  AT+UNAME  : Get or Set MQTT Username
... ... @@ -711,58 +711,86 @@
711 711  
712 712  AT+SUBTOPIC  : Get or Set MQTT subscription topic
713 713  
641 +**Information**          
714 714  
715 -(% style="color:blue" %)**Information**          
716 -
717 717  AT+FDR  : Factory Data Reset
718 718  
719 719  AT+PWORD  : Serial Access Password
720 720  
647 += **​5.  FAQ** =
721 721  
722 -= ​5.  FAQ =
649 +== **5.1 ​ How to Upgrade Firmware** ==
723 723  
724 -== 5.1 ​ How to Upgrade Firmware ==
725 -
726 -
727 727  User can upgrade the firmware for 1) bug fix, 2) new feature release.
728 728  
729 729  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]]
730 730  
731 -(% 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.**
655 +**Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.**
732 732  
657 +== **5.2  Can I calibrate CPN01 to different soil types?** ==
733 733  
734 -= 6.  Trouble Shooting =
659 +CPN01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].
735 735  
736 -== 6.1  ​Connection problem when uploading firmware ==
661 += **6.  Trouble Shooting** =
737 737  
663 +== **6.1  ​Connection problem when uploading firmware** ==
738 738  
739 -(% 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]]
665 +**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]]
740 740  
667 +== **6.2  AT Command input doesn't work** ==
741 741  
742 -== 6.2  AT Command input doesn't work ==
669 +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 **ENTER** while sending out the command. Some serial tool doesn't send **ENTER** while press the send key, user need to add ENTER in their string.
743 743  
671 += **7. ​ Order Info** =
744 744  
745 -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.
673 +Part Number**:** CPN01
746 746  
675 += **8.  Packing Info** =
747 747  
748 -= 7. ​ Order Info =
677 +**Package Includes**:
749 749  
679 +* CPN01 NB-IoT Soil Moisture & EC Sensor x 1
680 +* External antenna x 1
750 750  
751 -Part Number**:** NDS03A
682 +**Dimension and weight**:
752 752  
684 +* Size: 195 x 125 x 55 mm
685 +* Weight:   420g
753 753  
754 -= 8.  Packing Info =
687 += **9.  Support** =
755 755  
689 +* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
690 +* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
756 756  
757 -(% style="color:blue" %)**Package Includes**:
692 +​
758 758  
759 -* NDS03A Open/Close Door Sensor x 1
760 760  
761 -= 9.  Support =
762 762  
763 763  
764 -* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
765 765  
766 -* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
767 767  
768 -​
699 +
700 +
701 +
702 +
703 +
704 +
705 +
706 +
707 +
708 +
709 +
710 +
711 +
712 +
713 +
714 +
715 +
716 +
717 +
718 +
719 +
720 +
721 +
722 +
723 +
1666596205057-567.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -179.8 KB
Content
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-20221117105556-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -133.3 KB
Content
image-20221117114459-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20221117114842-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -964.1 KB
Content
image-20221117114937-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.1 KB
Content
image-20221117114949-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -33.4 KB
Content
image-20221117115010-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -40.4 KB
Content
image-20221117142300-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -51.9 KB
Content
image-20221117150312-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.7 KB
Content
image-20221118092935-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.5 KB
Content
image-20221118093658-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -12.7 KB
Content
image-20221118094227-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.2 KB
Content
image-20221118094449-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.5 KB
Content
image-20221118103445-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.5 KB
Content
image-20221207170748-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.1 KB
Content
image-20221207170748-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.9 KB
Content
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