Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 83.3 >
edited by Xiaoling
on 2022/12/08 09:33
To version < 32.1 >
edited by David Huang
on 2022/10/21 11:24
>
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.David
Content
... ... @@ -1,46 +1,37 @@
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 CPL01 is a **NB-IOT Contact Sensor**. It detects open/close status and uplink to IoT server via LoRaWAN network. user can see the dry contact status, open time, open counts in the IoT Server.
8 8  
12 +The CPL01 will send periodically data every day as well as for each dry contact action. It also counts the contact open times and calculate last open duration. User can also disable the uplink for each open/close event, instead, device can count each open event and uplink periodically.
9 9  
14 +CPL01 has the open alarm feature, user can set this feature so device will send Alarm if the contact has been open for a certain time.
10 10  
11 -= 1.  Introduction =
16 +CPL01 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 include **TCP,MQTT,UDP and CoAP  **for different application requirement.
20 +\\CPN01 is powered by  **8500mAh Li-SOCI2 battery**, It is designed for long term use 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 local area and with the bands CPN01 supports. If the local operate support it, user needs to get a **NB-IoT SIM card** from local operator and install 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.
18 18  
19 -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.
26 +== **​1.2 Features** ==
20 20  
21 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
22 -
23 -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.
24 -
25 -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.
26 -
27 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
28 -
29 -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)
30 -
31 -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.
32 -)))
33 -
34 -
35 -== ​1.2  Features ==
36 -
37 -
38 38  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
39 -* Short uplink interval for Distance Alarm
29 +* Open/Close detect
30 +* Open/Close statistics
40 40  * Monitor Battery Level
41 -* Microwave Radar for distance detection
32 +* Uplink on periodically and open/close event
42 42  * Datalog feature
43 -* Uplink periodically
34 +* Uplink on periodically
44 44  * Downlink to change configure
45 45  * Wall Mountable
46 46  * Outdoor Use
... ... @@ -47,530 +47,517 @@
47 47  * Ultra-Low Power consumption
48 48  * AT Commands to change parameters
49 49  * Micro SIM card slot for NB-IoT SIM
50 -* 8500mAh Battery for long-term use
41 +* 8500mAh Battery for long term use
51 51  
52 -== 1.3 Radar probe specification ==
43 +== **1.3  Specification** ==
53 53  
45 +**Common DC Characteristics:**
54 54  
55 -* Measuring Method: FMCW
56 -* Frequency: 24.000 24.500 GHz
57 -* Measurement output power: 6dBm
58 -* Measure range: 0.5 20m
59 -* Accuracy: ±0.1m
60 -* Resolution: 0.01m
61 -* Horizontal Angel: 78°
62 -* Vertical Angel: 23°
47 +* Supply Voltage: 2.1v ~~ 3.6v
48 +* Operating Temperature: -40 ~~ 85°C
63 63  
64 -== 1.4  Storage Temperature ==
50 +**NB-IoT Spec:**
65 65  
52 +* - B1 @H-FDD: 2100MHz
53 +* - B3 @H-FDD: 1800MHz
54 +* - B8 @H-FDD: 900MHz
55 +* - B5 @H-FDD: 850MHz
56 +* - B20 @H-FDD: 800MHz
57 +* - B28 @H-FDD: 700MHz
66 66  
67 - -40°C to +85°C
59 +== **1.4 Installation** ==
68 68  
61 +Connect CPL01 to an Open Close sensor like below. So it can detect the open/close event.
69 69  
70 -== 1.5 ​ Applications ==
63 +[[image:image-20221021110329-1.png]]
71 71  
65 +[[image:image-20221021110340-2.png]]
72 72  
73 -* Horizontal distance measurement
74 -* Liquid level measurement
75 -* Parking management system
76 -* Object proximity and presence detection
77 -* Intelligent trash can management system
78 -* Robot obstacle avoidance
79 -* Automatic control
80 -* Sewer
81 -* Bottom water level monitoring
67 +== **1.5 ​Applications** ==
82 82  
83 -== 1.6  Specification ==
69 +* Open/Close Detection
70 +* Pulse meter application
71 +* Dry Contact Detection
84 84  
73 +== **1.6 Mechanical** ==
85 85  
86 -(% style="color:blue" %)**Common DC Characteristics:**
75 +​[[image:image-20221021110415-3.png]]
87 87  
88 -* Supply Voltage: 2.1v ~~ 3.6v
89 -* Operating Temperature: 0 ~~ 70°C
77 +== ** 1.7 Pin Definitions and Switch** ==
90 90  
91 -(% style="color:blue" %)**NB-IoT Spec:**
79 +[[image:image-20221021110429-4.png]]
92 92  
93 -* B1 @H-FDD: 2100MHz
94 -* B3 @H-FDD: 1800MHz
95 -* B8 @H-FDD: 900MHz
96 -* B5 @H-FDD: 850MHz
97 -* B20 @H-FDD: 800MHz
98 -* B28 @H-FDD: 700MHz
81 +=== **1.7.1 Pin Definition** ===
99 99  
100 -== 1.7  Installation ==
83 +CPL01 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 user manual of LSN50v2 at: [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>url:https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
101 101  
85 +=== **1.7.2 Jumper JP2(Power ON/OFF)** ===
102 102  
103 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
104 104  
88 +Power on Device when putting this jumper.
105 105  
106 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
107 107  
108 108  
92 +=== **1.7.3 BOOT MODE / SW1** ===
109 109  
110 -== 1.8  Pin Definitions and Switch ==
111 111  
95 +1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
112 112  
113 -[[image:1670404362039-351.png]]
97 +2) Flash: work mode, the device starts to work and send out console output for further debug
114 114  
115 115  
116 -= 2.  Use NMDS200 to communicate with IoT Server =
117 117  
118 -== 2.1  How it works ==
101 +=== **1.7.4 Reset Button** ===
119 119  
120 120  
121 -The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
104 +Press to reboot the device.
122 122  
123 -The diagram below shows the working flow in the default firmware of NMDS200:
106 +== ==
124 124  
125 -[[image:image-20221021110615-5.png]]
108 +=== **1.7.5 LED** ===
126 126  
127 127  
128 -== 2.2 ​ Configure NMDS200 ==
111 +It will flash:
129 129  
113 +1. Boot the device in flash mode
114 +1. Send an uplink packet
130 130  
131 -To use NMDS200 in your city, make sure to meet below requirements:
116 += **2.  Use CPN01 to communicate with IoT Server** =
132 132  
133 -* Your local operator has already distributed an NB-IoT Network.
134 -* The local NB-IoT network used the band that NMDS200 supports.
135 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
118 +== **2.1  How it works** ==
136 136  
137 -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.
120 +The CPN01 is equipped with a NB-IoT module, the pre-loaded firmware in CPN01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01.
138 138  
139 -[[image:image-20221208090742-1.png]]
122 +The diagram below shows the working flow in default firmware of CPN01:
140 140  
124 +[[image:image-20221021110615-5.png]]
141 141  
142 -=== 2.2.1 Insert NB-IoT SIM card ===
126 +== **2.2 ​ Configure the CPN01** ==
143 143  
128 +=== **2.2.1 Test Requirement** ===
144 144  
145 -Insert the NB-IoT Card get from your provider.
130 +To use CPN01 in your city, make sure meet below requirements:
146 146  
147 -User needs to take out the NB-IoT module and insert the SIM card like below:
132 +* Your local operator has already distributed a NB-IoT Network there.
133 +* The local NB-IoT network used the band that CPN01 supports.
134 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
148 148  
149 -[[image:image-20221021110745-6.png]] ​
136 +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
150 150  
138 + ​
151 151  
152 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
140 +=== **2.2.2 Insert SIM card** ===
153 153  
142 +Insert the NB-IoT Card get from your provider.
154 154  
155 -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.
144 +User need to take out the NB-IoT module and insert the SIM card like below:
156 156  
157 -(% style="color:blue" %)**Connection:**
146 +[[image:image-20221021110745-6.png]] ​
158 158  
159 -(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
148 +=== **2.2.3 Connect USB – TTL to CPN01 to configure it** ===
160 160  
161 -(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD**
150 +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.
162 162  
163 -(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD**
152 +**Connection:**
164 164  
154 + USB TTL GND <~-~-~-~-> GND
165 165  
166 -In the PC, use below serial tool settings:
156 + USB TTL TXD <~-~-~-~-> UART_RXD
167 167  
168 -* Baud:  (% style="color:red" %)**9600**
158 + USB TTL RXD <~-~-~-~-> UART_TXD
169 169  
170 -* Data bits:** (% style="color:red" %)8(%%)**
160 +In the PC, use below serial tool settings:
171 171  
172 -* Stop bits: (% style="color:red" %)**1**
162 +* Baud:  **9600**
163 +* Data bits:** 8**
164 +* Stop bits: **1**
165 +* Parity:  **None**
166 +* Flow Control: **None**
173 173  
174 -* Parity:  (% style="color:red" %)**None**
168 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on CPN01. CPN01 will output system info once power on as below, we can enter the **password: 12345678** to access AT Command input.
175 175  
176 -* Flow Control: (% style="color:red" %)**None**
177 -
178 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
179 -
180 180  ​[[image:image-20221021110817-7.png]]
181 181  
182 -NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
172 +**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]]
183 183  
174 +=== **2.2.4 Use CoAP protocol to uplink data** ===
184 184  
185 -(% 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: 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/]]
186 186  
178 +**Use below commands:**
187 187  
180 +* **AT+PRO=1**   ~/~/ Set to use CoAP protocol to uplink
181 +* **AT+SERVADDR=120.24.4.116,5683   ** ~/~/ to set CoAP server address and port
182 +* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path
188 188  
189 -=== 2.2.3 Use CoAP protocol to uplink data ===
190 -
191 -
192 -(% 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/]]
193 -
194 -
195 -(% style="color:blue" %)**Use below commands in NMDS200:**
196 -
197 -* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
198 -
199 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
200 -
201 -* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
202 -
203 203  For parameter description, please refer to AT command set
204 204  
205 205  [[image:image-20221021110948-8.png]]
206 206  
188 +After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server.
207 207  
208 -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.
190 +[[image:image-20221021110956-9.png]] ​
209 209  
210 -[[image:1670405841875-916.png]] ​
192 +=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** ===
211 211  
194 +This feature is supported since firmware version v1.0.1
212 212  
213 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
196 +* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
197 +* **AT+SERVADDR=120.24.4.116,5601   ** ~/~/ to set UDP server address and port
198 +* **AT+CFM=1       ** ~/~/If the server does not respond, this command is unnecessary
214 214  
215 -
216 -(% style="color:blue" %)**AT Commands:**
217 -
218 -* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
219 -
220 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  Set UDP server address and port
221 -
222 -* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
223 -
224 224  ​ [[image:image-20221021111025-10.png]]
225 225  
226 -
227 227  [[image:image-20221021111033-11.png||height="241" width="576"]]
228 228  
229 229  ​
230 230  
231 -=== 2.2.5 Use MQTT protocol to uplink data ===
206 +=== **2.2.6 Use MQTT protocol to uplink data** ===
232 232  
208 +This feature is supported since firmware version v110
233 233  
234 -(% style="color:blue" %)**AT Commands:**
210 +* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
211 +* **AT+SERVADDR=120.24.4.116,1883   ** ~/~/Set MQTT server address and port
212 +* **AT+CLIENT=CLIENT       ** ~/~/Set up the CLIENT of MQTT
213 +* **AT+UNAME=UNAME                               **~/~/Set the username of MQTT
214 +* **AT+PWD=PWD                                        **~/~/Set the password of MQTT
215 +* **AT+PUBTOPIC=NSE01_PUB                    **~/~/Set the sending topic of MQTT
216 +* **AT+SUBTOPIC=NSE01_SUB          ** ~/~/Set the subscription topic of MQTT
235 235  
236 -* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
218 +​ [[image:image-20221021111058-12.png]]
237 237  
238 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
220 +[[image:image-20221021111108-13.png]]
239 239  
240 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
241 -
242 -* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
243 -
244 -* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
245 -
246 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/  Set the sending topic of MQTT
247 -
248 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
249 -
250 -​ [[image:image-20221118103445-7.png]]
251 -
252 -
253 -[[image:1670405928926-116.png]]
254 -
255 255  ​
256 256  
257 -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.
224 +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.
258 258  
226 +=== **2.2.7 Use TCP protocol to uplink data** ===
259 259  
260 -=== 2.2.6 Use TCP protocol to uplink data ===
228 +This feature is supported since firmware version v110
261 261  
230 +* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
231 +* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ to set TCP server address and port
262 262  
263 -(% style="color:blue" %)**AT Commands:**
233 +​ [[image:image-20221021111125-14.png]]
264 264  
265 -* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
266 -
267 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
268 -
269 -​ [[image:1670406036256-101.png||height="676" width="713"]]
270 -
271 -
272 272  [[image:image-20221021111131-15.png]]
273 273  
274 274  ​
275 275  
276 -=== 2.2.7 Change Update Interval ===
239 +=== **2.2.8 Change Update Interval** ===
277 277  
241 +User can use below command to change the **uplink interval**.
278 278  
279 -User can use below command to change the (% style="color:blue" %)**uplink interval**.
243 +* **AT+TDC=600      ** ~/~/ Set Update Interval to 600s
280 280  
281 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
245 +**NOTE:**
282 282  
283 -(% style="color:red" %)**NOTE:**
247 +**~1. By default, the device will send an uplink message every 1 hour.**
284 284  
285 -1.  By default, the device will send an uplink message every 4 hour.
249 +== **2.3  Uplink Payload** ==
286 286  
251 +In this mode, uplink payload includes 87 bytes in total by default.
287 287  
288 -== 2.3  Uplink Payload ==
253 +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.
289 289  
255 +|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**2**|**2**|4
256 +|**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
290 290  
291 -The uplink payload includes 23 bytes in total by default.
258 +|2|2|4|8 group
259 +|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|...
292 292  
293 -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.
261 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
294 294  
263 +[[image:image-20221021111201-16.png||height="572" width="792"]]
295 295  
296 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
297 -|=(% 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**
298 -|=(% 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>>||anchor="H2.4.5A0A0Distance"]] |(% style="width:93px" %) [[Distance  2>>||anchor="H2.4.5A0A0Distance"]]
265 +The payload is ASCII string, representative same HEX:
299 299  
300 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
301 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
302 -**1-32 group**
303 -)))
304 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
267 +0xf86778705021331700640c7817010001000000090000026315537b 0100000b02000002663510fed0100000e0200000263510f39010000000000000063510e85010000000000000063510d2e010000000000000063510c7a010000000000000063510bc6010000000000000063510954010000000000000063510882 where:
305 305  
306 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
269 +* **Device ID: 0x f867787050213317 = f867787050213317**
270 +* **Version: 0x0064=100=1.0.0**
307 307  
308 -[[image:1670406261143-723.png]]
272 +* **BAT: 0x0c78 = 3192 mV = 3.192V**
273 +* **Singal: 0x17 = 23**
274 +* **Mod: 0x01 = 1**
275 +* **Calculate Flag: 0x00= 0**
276 +* **Contact Status: 0x00= 0**
277 +* **Alarm:0x00 =0**
278 +* **Total pulse:0x09 =0**
279 +* **The last open duration:0x02 =2**
280 +* **Time stamp : 0x6315537b =1662342011**
281 +* **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp : 0100000b0200002663510fed**
282 +* **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp : 0100000e0200002663510f39,.......**
309 309  
284 +== **2.4  Payload Explanation and Sensor Interface** ==
310 310  
311 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
286 +=== **2.4.1  Device ID** ===
312 312  
313 -**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__(%%)**
288 +By default, the Device ID equal to the last 15 bits of IMEI.
314 314  
315 -**where:**
290 +User can use **AT+DEUI** to set Device ID
316 316  
317 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
292 +**Example:**
318 318  
319 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
294 +AT+DEUI=868411056754138
320 320  
321 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
296 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
322 322  
323 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
298 +=== **2.4.2  Version Info** ===
324 324  
325 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
300 +Specify the software version: 0x64=100, means firmware version 1.00.
326 326  
327 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
302 +For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0.
328 328  
329 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
304 +=== **2.4.3  Battery Info** ===
330 330  
331 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
306 +Check the battery voltage for CPN01.
332 332  
333 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
308 +Ex1: 0x0B45 = 2885mV
334 334  
310 +Ex2: 0x0B49 = 2889mV
335 335  
312 +=== **2.4.4  Signal Strength** ===
336 336  
314 +NB-IoT Network signal Strength.
337 337  
338 -== 2.4  Payload Explanation and Sensor Interface ==
316 +**Ex1: 0x1d = 29**
339 339  
340 -=== 2.4.1  Device ID ===
318 +**0**  -113dBm or less
341 341  
320 +**1**  -111dBm
342 342  
343 -By default, the Device ID is equal to the last 15 bits of IMEI.
322 +**2...30** -109dBm... -53dBm
344 344  
345 -User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
324 +**31**   -51dBm or greater
346 346  
347 -**Example:**
326 +**99**    Not known or not detectable
348 348  
349 -AT+DEUI=868411056754138
328 +=== **2.4.5 Calculate Flag** ===
350 350  
351 -The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
330 +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.
352 352  
332 +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.
353 353  
354 -=== 2.4.2  Version Info ===
334 +Default value: 0. 
355 355  
336 +Range (6 bits): (b)000000 ~~ (b) 111111
356 356  
357 -Specify the software version: 0x64=100, which means firmware version 1.00.
338 +=== **2.4.6  Alarm** ===
358 358  
359 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
340 +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]]
360 360  
342 +=== **2.4.7 Contact Status** ===
361 361  
362 -=== 2.4.3  Battery Info ===
344 +0: Open
363 363  
346 +1: Close
364 364  
365 -Check the battery voltage for NMDS200.
348 +=== **2.4.8 Total pulse** ===
366 366  
367 -Ex1: 0x0B45 = 2885mV
350 +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]]
368 368  
369 -Ex2: 0x0B49 = 2889mV
352 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
370 370  
354 +=== **2.4.9 The last open duration** ===
371 371  
372 -=== 2.4.4  Signal Strength ===
356 +Dry Contact last open duration.
373 373  
358 +Unit: min.
374 374  
375 -NB-IoT Network signal Strength.
360 +[[image:image-20221021111346-17.png||height="146" width="770"]]
376 376  
377 -**(% style="color:blue" %)Ex1: 0x1d = 29**
378 378  
379 -**(% style="color:#037691" %)0** (%%) -113dBm or less
363 +=== **2.4.10  Timestamp** ===
380 380  
381 -**(% style="color:#037691" %)1**  (%%) -111dBm
365 +Time stamp : 0x6315537b =1662342011
382 382  
383 -**(% style="color:#037691" %)2...30** (%%) -109dBm... -53dBm
367 +Convert Unix timestamp to time 2022-9-5 9:40:11.
384 384  
385 -**(% style="color:#037691" %)31** (%%)  -51dBm or greater
369 +**~ **
386 386  
387 -**(% style="color:#037691" %)99** (%%)   Not known or not detectable
371 +== **2.5  Downlink Payload** ==
388 388  
373 +By default, CPN01 prints the downlink payload to console port.
389 389  
390 -=== 2.4.5  Distance ===
375 +[[image:image-20221021111414-18.png]] ​
391 391  
377 +**Examples:**
392 392  
393 -[[image:1670407401682-959.png]]
379 +* **Set TDC**
394 394  
381 +If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
395 395  
396 -(% style="color:blue" %)**Object1 Distance:**
383 +Payload:    01 00 00 1E    TDC=30S
397 397  
398 -Distance between sensor probe to the first object. (unit: cm)
385 +Payload:    01 00 00 3C    TDC=60S
399 399  
400 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
387 +* **Reset**
401 401  
402 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
389 +If payload = 0x04FF, it will reset the NSE01
403 403  
391 +* **INTMOD**
404 404  
405 -(% style="color:blue" %)**Object2 Distance:**
393 +Downlink Payload: 06000003, Set AT+INTMOD=3
406 406  
407 -Distance between sensor probe to the second object. (unit: cm)
395 +== **2.6  ​LED Indicator** ==
408 408  
397 +The CPN01 has an internal LED which is to show the status of different state.
409 409  
410 -=== 2.4.6  Timestamp ===
399 +* 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)
400 +* Then the LED will be on for 1 second means device is boot normally.
401 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
402 +* For each uplink probe, LED will be on for 500ms.
411 411  
404 +== **2.7  Alarm Base on Timeout** ==
412 412  
413 -Timestamp : 0x6315537b =1662342011
406 +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:
414 414  
415 415  
416 -== 2.5  Downlink Payload ==
409 +**~1. Keep Status: Status to be monitor**
417 417  
411 +Keep Status = 1: Monitor Close to Open event
418 418  
419 -By default, NMDS200 prints the downlink payload to console port.
413 +Keep Status = 0: Monitor Open to Close event
420 420  
421 -[[image:image-20221021111414-18.png]] ​
422 422  
416 +**2. Keep Time: Timeout to send an Alarm**
423 423  
424 -**Examples:**
418 +Range 0 ~~ 65535(0xFFFF) seconds.
425 425  
426 -* (% style="color:#037691" %)**Set TDC**
420 +If keep time = 0, Disable Alarm Base on Timeout feature.
427 427  
428 -If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
422 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
429 429  
430 -Payload:    01 00 00 1E    TDC=30S
431 431  
432 -Payload:    01 00 00 3C    TDC=60S
425 +**AT Command** to configure:
433 433  
434 -* (% style="color:#037691" %)**Reset**
427 +**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.
435 435  
436 -If payload = 0x04FF, it will reset the NMDS200
429 +**AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm.
437 437  
438 -* (% style="color:#037691" %)**INTMOD**
431 +== **2.8 Set debug mode** ==
439 439  
440 -Downlink Payload: 06000003, Set AT+INTMOD=3
433 +Feature: Enable or Disable debug mode
441 441  
442 442  
443 -== 2.6  ​LED Indicator ==
436 +**AT Command: AT+DEBUG**
444 444  
438 +[[image:image-20221021111629-21.png]]
445 445  
446 -The NMDS200 has an internal LED which is to show the status of different states.
440 +== **2.9 Clear Flash Record** ==
447 447  
448 -* When the device starts normally, the LED will light up for 1 second.
449 -* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
450 -* For each uplink probe, LED will be on for 500ms.
442 +Feature: Clear flash storage for data log feature.
451 451  
444 +**AT Command: AT+CLRDTA**
452 452  
446 +[[image:image-20221021111527-19.png]]
453 453  
448 +== ** 2.10 Set trigger mode** ==
454 454  
455 -== 2.7  Distance alarm function ==
450 +➢ AT Command: **AT+TTRMOD**
456 456  
452 +Feature: Set the trigger interrupt mode.
457 457  
458 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
454 +[[image:image-20221021111552-20.png]]
459 459  
460 -**(% style="color:blue" %)Example 1:**
456 +== **2.11 Set the calculate flag** ==
461 461  
462 -AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
458 +Feature: Set the calculate flag
463 463  
464 -AT+ ALARM2 =min,max
460 +**AT Command: AT+CALCFLAG**
465 465  
462 +[[image:image-20221021111711-22.png]]
466 466  
467 -**(% style="color:blue" %)Example 2:**
464 +== **2.12 Set count number** ==
468 468  
469 -AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
466 +Feature: Manually set the count number
470 470  
468 +**AT Command: AT+SETCNT**
471 471  
470 +[[image:image-20221021111748-24.png]]
472 472  
472 +== **2.13 Set the number of data to be uploaded and the recording time** ==
473 473  
474 -== 2.8  Set the number of data to be uploaded and the recording time ==
474 +➢ AT Command:
475 475  
476 +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)
476 476  
477 -(% style="color:blue" %)**AT Command:**
478 478  
479 -(% 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)
479 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
480 480  
481 -(% 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.
481 +== **2.14 Read or Clear cached data** ==
482 482  
483 +➢ AT Command:
483 483  
484 -== 2.9  Read or Clear cached data ==
485 +AT+CDP    ~/~/ Read cached data
485 485  
487 +[[image:image-20221021111810-25.png||height="364" width="797"]]
486 486  
487 -(% style="color:blue" %)**AT Command:**
488 488  
489 -(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
490 +AT+CDP=0    ~/~/ Clear cached data ​
490 490  
491 -(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
492 +== **2.15  ​Firmware Change Log** ==
492 492  
493 -[[image:1670408172929-569.png]]
494 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
494 494  
496 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
495 495  
496 -== 2.10  ​Firmware Change Log ==
498 +== **2.16  ​Battery Analysis** ==
497 497  
500 +=== **2.16.1  ​Battery Type** ===
498 498  
499 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
502 +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.
500 500  
501 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
504 +The battery is designed to last for several years depends on the actually use environment and update interval. 
502 502  
506 +The battery related documents as below:
503 503  
504 -== 2.11  ​Battery Analysis ==
505 -
506 -=== 2.11.1  ​Battery Type ===
507 -
508 -
509 -The NMDS200 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.
510 -
511 -The battery is designed to last for several years depends on the actual use environment and update interval. 
512 -
513 -The battery-related documents as below:
514 -
515 515  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
516 -
517 517  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
518 -
519 519  * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
520 520  
521 521  [[image:image-20221021111911-26.png]] ​
522 522  
514 +=== **2.16.2  Power consumption Analyze** ===
523 523  
524 -=== 2.11.2  Power consumption Analyze ===
525 -
526 -
527 527  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.
528 528  
529 529  Instruction to use as below:
530 530  
531 -(% 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/]]
520 +**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/]]
532 532  
533 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
522 +**Step 2: ** Open it and choose
534 534  
535 535  * Product Model
536 -
537 537  * Uplink Interval
538 -
539 539  * Working Mode
540 540  
541 541  And the Life expectation in difference case will be shown on the right.
542 542  
543 -[[image:1666596205057-567.png]] ​
530 +[[image:image-20221021111923-27.png||height="253" width="783"]] ​
544 544  
532 +=== **2.16.3  ​Battery Note** ===
545 545  
546 -=== 2.11.3  ​Battery Note ===
547 -
548 -
549 549  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.
550 550  
536 +=== **2.16.4  Replace the battery** ===
551 551  
552 -=== 2.11.4  Replace the battery ===
538 +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).
553 553  
540 += **3. ​ Access NB-IoT Module** =
554 554  
555 -The default battery pack of NMDS200 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).
556 -
557 -
558 -= 3. ​ Access NB-IoT Module =
559 -
560 -
561 561  Users can directly access the AT command set of the NB-IoT module.
562 562  
563 563  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/]] 
564 564  
546 +[[image:image-20221021112006-28.png]] ​
565 565  
566 -[[image:image-20221118094449-6.png]] ​
548 += **4.  Using the AT Commands** =
567 567  
550 +== **4.1  Access AT Commands** ==
568 568  
569 -= 4.  Using the AT Commands =
570 -
571 -== 4.1  Access AT Commands ==
572 -
573 -
574 574  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]]
575 575  
576 576  AT+<CMD>?  : Help on <CMD>
... ... @@ -581,9 +581,8 @@
581 581  
582 582  AT+<CMD>=?  : Get the value
583 583  
562 +**General Commands**      
584 584  
585 -(% style="color:blue" %)**General Commands**      
586 -
587 587  AT  : Attention       
588 588  
589 589  AT?  : Short Help     
... ... @@ -606,97 +606,125 @@
606 606  
607 607  AT+SERVADDR  : Server Address
608 608  
609 -AT+TR      :  Get or Set record time
586 +AT+TR      : Get or Set record time"
610 610  
611 -AT+NOUD :  Get or Set the number of data to be uploaded
612 612  
613 -AT+CDP     :  Read or Clear cached data
589 +AT+NOUD      : Get or Set the number of data to be uploaded
614 614  
615 -AT+DEBUG:  Enable or Disable debug mode
616 616  
617 -AT+ALARM1:  Get or Set alarm of distance1
592 +AT+CDP     : Read or Clear cached data
618 618  
619 -AT+ALARM2:  Get or Set alarm of distance2
620 620  
621 -AT+GETSENSORVALUE :  Returns the current sensor measurement
595 +AT+ DEBUG   : Enable or Disable debug mode
622 622  
623 -AT+POWERIC :  Get or set the Power IC flag
597 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
624 624  
599 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
625 625  
626 -(% style="color:blue" %)**COAP Management**      
601 +AT+ CALCFLAG   : Get or Set the calculate flag
627 627  
628 -AT+URI :  Resource parameters
603 +AT+ CLRC   : Clear current door open count
629 629  
605 +**COAP Management**      
630 630  
631 -(% style="color:blue" %)**UDP Management**
607 +AT+URI            : Resource parameters
632 632  
633 -AT+CFM :  Upload confirmation mode (only valid for UDP)
609 +**UDP Management**
634 634  
611 +AT+CFM          : Upload confirmation mode (only valid for UDP)
635 635  
636 -(% style="color:blue" %)**MQTT Management**
613 +**MQTT Management**
637 637  
638 -AT+CLIENT  : Get or Set MQTT client
615 +AT+CLIENT               : Get or Set MQTT client
639 639  
640 -AT+UNAME : Get or Set MQTT Username
617 +AT+UNAME  : Get or Set MQTT Username
641 641  
642 -AT+PWD  :  Get or Set MQTT password
619 +AT+PWD                  : Get or Set MQTT password
643 643  
644 -AT+PUBTOPIC :  Get or Set MQTT publish topic
621 +AT+PUBTOPIC  : Get or Set MQTT publish topic
645 645  
646 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
623 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
647 647  
625 +**Information**          
648 648  
649 -(% style="color:blue" %)**Information**          
627 +AT+FDR  : Factory Data Reset
650 650  
651 -AT+FDR :  Factory Data Reset
629 +AT+PWORD  : Serial Access Password
652 652  
653 -AT+PWORD :  Serial Access Password
631 += **​5.  FAQ** =
654 654  
633 +== **5.1 ​ How to Upgrade Firmware** ==
655 655  
656 -= ​5.  FAQ =
635 +User can upgrade the firmware for 1) bug fix, 2) new feature release.
657 657  
658 -== 5.1 ​ How to Upgrade Firmware ==
637 +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]]
659 659  
639 +**Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.**
660 660  
661 -User can upgrade the firmware for 1) bug fix, 2) new feature release.
641 +== **5.2  Can I calibrate CPN01 to different soil types?** ==
662 662  
663 -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]]
643 +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]].
664 664  
665 -(% style="color:red" %)**Notice: **(% style="color:blue" %)**NMDS200** (%%)**and (% style="color:blue" %)LMDS200(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
645 += **6.  Trouble Shooting** =
666 666  
647 +== **6.1  ​Connection problem when uploading firmware** ==
667 667  
668 -= 6.  Trouble Shooting =
649 +**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]]
669 669  
670 -== 6.1  ​Connection problem when uploading firmware ==
651 +== **6.2  AT Command input doesn't work** ==
671 671  
653 +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.
672 672  
673 -(% 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]]
655 += **7. ​ Order Info** =
674 674  
657 +Part Number**:** CPN01
675 675  
676 -== 6.2  AT Command input doesn't work ==
659 += **8.  Packing Info** =
677 677  
661 +**Package Includes**:
678 678  
679 -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.
663 +* CPN01 NB-IoT Soil Moisture & EC Sensor x 1
664 +* External antenna x 1
680 680  
666 +**Dimension and weight**:
681 681  
682 -= 7. ​ Order Info =
668 +* Size: 195 x 125 x 55 mm
669 +* Weight:   420g
683 683  
671 += **9.  Support** =
684 684  
685 -Part Number:**(% style="color:blue" %) NMDS200**
673 +* 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.
674 +* 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]]
686 686  
676 +​
687 687  
688 -= 8.  Packing Info =
689 689  
690 690  
691 -(% style="color:blue" %)**Package Includes**:
692 692  
693 -* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
694 694  
695 -= 9.  Support =
696 696  
697 697  
698 -* 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.
699 699  
700 -* 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]]
701 701  
702 -​
686 +
687 +
688 +
689 +
690 +
691 +
692 +
693 +
694 +
695 +
696 +
697 +
698 +
699 +
700 +
701 +
702 +
703 +
704 +
705 +
706 +
707 +
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
1670408172929-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -211.8 KB
Content
LMDS200_10.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 KB
Content
image-20221022234529-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.3 KB
Content
image-20221022234602-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -135.7 KB
Content
image-20221023000439-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -82.1 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
image-20221208090742-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.7 KB
Content

Applications

Navigation

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