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