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

Applications

Navigation

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