Changes for page NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 17:03
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 4 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.David - Content
-
... ... @@ -1,41 +1,30 @@ 1 1 (% style="text-align:center" %) 2 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 -**Table of Contents:** 7 - 8 8 {{toc/}} 9 9 6 += **1. Introduction** = 10 10 8 +== **1.1 **What is CPN01 **NB-IOT** Pulse/Contact Sensor == 11 11 10 +The Dragino CPL01 is a **NB-IOT Contact Sensor**. It detects open/close status and uplink to IoT server via LoRaWAN network. user can see the dry contact status, open time, open counts in the IoT Server. 12 12 12 +The CPL01 will send periodically data every day as well as for each dry contact action. It also counts the contact open times and calculate last open duration. User can also disable the uplink for each open/close event, instead, device can count each open event and uplink periodically. 13 13 14 - =1.Introduction=14 +CPL01 has the open alarm feature, user can set this feature so device will send Alarm if the contact has been open for a certain time. 15 15 16 +CPL01 is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures. 16 16 17 -== 1.1 What is CPN01 NB-IoT Pulse/Contact Sensor == 18 +NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage. 19 +\\CPN01 supports different uplink methods include **TCP,MQTT,UDP and CoAP **for different application requirement. 20 +\\CPN01 is powered by **8500mAh Li-SOCI2 battery**, It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 21 +\\To use CPN01, user needs to check if there is NB-IoT coverage in local area and with the bands CPN01 supports. If the local operate support it, user needs to get a **NB-IoT SIM card** from local operator and install CPN01 to get NB-IoT network connection 18 18 19 - 20 -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. 21 - 22 -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. 23 - 24 -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. 25 - 26 -CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures. 27 - 28 -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. 29 -\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements. 30 -\\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) 31 -\\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. 32 - 33 33 34 34 35 35 36 -== 1.2 26 +== **1.2 Features** == 37 37 38 - 39 39 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 40 40 * Open/Close detect 41 41 * Open/Close statistics ... ... @@ -42,7 +42,7 @@ 42 42 * Monitor Battery Level 43 43 * Uplink on periodically and open/close event 44 44 * Datalog feature 45 -* Uplink periodically 34 +* Uplink on periodically 46 46 * Downlink to change configure 47 47 * Wall Mountable 48 48 * Outdoor Use ... ... @@ -49,18 +49,16 @@ 49 49 * Ultra-Low Power consumption 50 50 * AT Commands to change parameters 51 51 * Micro SIM card slot for NB-IoT SIM 52 -* 8500mAh Battery for long -term use41 +* 8500mAh Battery for long term use 53 53 43 +== **1.3 Specification** == 54 54 55 - ==1.3Specification ==45 +**Common DC Characteristics:** 56 56 57 - 58 -(% style="color:blue" %)**Common DC Characteristics:** 59 - 60 60 * Supply Voltage: 2.1v ~~ 3.6v 61 61 * Operating Temperature: -40 ~~ 85°C 62 62 63 - (% style="color:blue" %)**NB-IoT Spec:**50 +**NB-IoT Spec:** 64 64 65 65 * - B1 @H-FDD: 2100MHz 66 66 * - B3 @H-FDD: 1800MHz ... ... @@ -69,243 +69,180 @@ 69 69 * - B20 @H-FDD: 800MHz 70 70 * - B28 @H-FDD: 700MHz 71 71 59 +== **1.4 Installation** == 72 72 73 - ==1.4Installation==61 +Connect CPL01 to an Open Close sensor like below. So it can detect the open/close event. 74 74 75 - 76 -Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event. 77 - 78 78 [[image:image-20221021110329-1.png]] 79 79 80 -[[image:image-2022102 2234602-2.png||height="288" width="922"]]65 +[[image:image-20221021110340-2.png]] 81 81 67 +== **1.5 Applications** == 82 82 83 - 84 -== 1.5 Applications == 85 - 86 - 87 87 * Open/Close Detection 88 88 * Pulse meter application 89 89 * Dry Contact Detection 90 90 73 +== **1.6 Mechanical** == 91 91 92 -== 1.6 Mechanical == 93 - 94 - 95 95 [[image:image-20221021110415-3.png]] 96 96 77 +== ** 1.7 Pin Definitions and Switch** == 97 97 98 - 99 -== 1.7 Pin Definitions and Switch == 100 - 101 101 [[image:image-20221021110429-4.png]] 102 102 81 +=== **1.7.1 Pin Definition** === 103 103 104 - ===1.7.1PinDefinition ===83 +CPL01 is pre-configured to connect to two external wires. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at: [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>url:https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]] 105 105 85 +=== **1.7.2 Jumper JP2(Power ON/OFF)** === 106 106 107 -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]]**. 108 108 109 - 110 - 111 -=== 1.7.2 Jumper JP2(Power ON/OFF) === 112 - 113 - 114 114 Power on Device when putting this jumper. 115 115 116 116 117 117 118 -=== 1.7.3 92 +=== **1.7.3 BOOT MODE / SW1** === 119 119 120 120 121 -1) The firmware won't run.95 +1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 122 122 123 -2) ingmode, the device starts to workfor NB-IoT connectionand sendsout console output for further debugging.97 +2) Flash: work mode, the device starts to work and send out console output for further debug 124 124 125 125 126 126 127 -=== 1.7.4 101 +=== **1.7.4 Reset Button** === 128 128 129 129 130 130 Press to reboot the device. 131 131 106 +== == 132 132 108 +=== **1.7.5 LED** === 133 133 134 -=== 1.7.5 LED === 135 135 111 +It will flash: 136 136 137 -The LED will blink when : 113 +1. Boot the device in flash mode 114 +1. Send an uplink packet 138 138 139 - 1.Bootthedevice in flashmode116 += **2. Use CPN01 to communicate with IoT Server** = 140 140 141 -2. Sendan uplinkpacket118 +== **2.1 How it works** == 142 142 120 +The CPN01 is equipped with a NB-IoT module, the pre-loaded firmware in CPN01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01. 143 143 122 +The diagram below shows the working flow in default firmware of CPN01: 144 144 145 -= 2. Use CPN01 to communicate with IoT Server = 146 - 147 - 148 -== 2.1 How it works == 149 - 150 - 151 -The CPN01 is equipped with an NB-IoT module, the pre-loaded firmware in CPN01 will get (% style="color:blue" %)**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. 152 - 153 -The diagram below shows the working flow in the default firmware of CPN01: 154 - 155 155 [[image:image-20221021110615-5.png]] 156 156 126 +== **2.2 Configure the CPN01** == 157 157 128 +=== **2.2.1 Test Requirement** === 158 158 159 - == 2.2 Configure CPN01==130 +To use CPN01 in your city, make sure meet below requirements: 160 160 161 - 162 -=== 2.2.1 Test Requirement === 163 - 164 - 165 -To use CPN01 in your city, make sure to meet below requirements: 166 - 167 -* Your local operator has already distributed an NB-IoT Network. 132 +* Your local operator has already distributed a NB-IoT Network there. 168 168 * The local NB-IoT network used the band that CPN01 supports. 169 169 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 170 170 171 -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 **(% 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.136 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The CPN01 will use CoAP(120.24.4.116:5683) or raw UDP(120.24.4.116:5601) or MQTT(120.24.4.116:1883)or TCP(120.24.4.116:5600)protocol to send data to the test server 172 172 173 -[[image:image-20221023000439-3.png]] 174 - 175 175 176 176 140 +=== **2.2.2 Insert SIM card** === 177 177 178 -=== 2.2.2 Insert NB-IoT SIM card === 179 - 180 - 181 181 Insert the NB-IoT Card get from your provider. 182 182 183 -User need sto take out the NB-IoT module and insert the SIM card like below:144 +User need to take out the NB-IoT module and insert the SIM card like below: 184 184 185 185 [[image:image-20221021110745-6.png]] 186 186 148 +=== **2.2.3 Connect USB – TTL to CPN01 to configure it** === 187 187 150 +User need to configure CPN01 via serial port to set the **Server Address** / **Uplink Topic** to define where and how-to uplink packets. CPN01 support AT Commands, user can use a USB to TTL adapter to connect to CPN01 and use AT Commands to configure it, as below. 188 188 189 - === 2.2.3ConnectUSB – TTL toCPN01 and configure it ===152 +**Connection:** 190 190 154 + USB TTL GND <~-~-~-~-> GND 191 191 192 - Userneed to configure CPN01 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. CPN01 support AT Commands, user can use a USBtoTTLadaptertoconnect to CPN01 and useATCommands to configure it, as below.156 + USB TTL TXD <~-~-~-~-> UART_RXD 193 193 194 - (%style="color:blue"%)**Connection:**158 + USB TTL RXD <~-~-~-~-> UART_TXD 195 195 196 -(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND** 197 - 198 -(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD** 199 - 200 -(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD** 201 - 202 - 203 203 In the PC, use below serial tool settings: 204 204 205 -* Baud: (% style="color:red" %)**9600** 162 +* Baud: **9600** 163 +* Data bits:** 8** 164 +* Stop bits: **1** 165 +* Parity: **None** 166 +* Flow Control: **None** 206 206 207 - * Databits:** (%style="color:red"%)8(%%)**168 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on CPN01. CPN01 will output system info once power on as below, we can enter the **password: 12345678** to access AT Command input. 208 208 209 -* Stop bits: (% style="color:red" %)**1** 210 - 211 -* Parity: (% style="color:red" %)**None** 212 - 213 -* Flow Control: (% style="color:red" %)**None** 214 - 215 -Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%). 216 - 217 217 [[image:image-20221021110817-7.png]] 218 218 219 - CPN01 willoutputsysteminfo once poweredonasbelow, wecan enterthe**password:12345678**access AT Commandinput.172 +**Note: the valid AT Commands can be found at: **[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]] 220 220 174 +=== **2.2.4 Use CoAP protocol to uplink data** === 221 221 222 - (% style="color:red" %)**Note: thevalid ATCommands canbeoundat:(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]176 +**Note: if you don't have CoAP server, you can refer this link to set up one: **[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 223 223 178 +**Use below commands:** 224 224 180 +* **AT+PRO=1** ~/~/ Set to use CoAP protocol to uplink 181 +* **AT+SERVADDR=120.24.4.116,5683 ** ~/~/ to set CoAP server address and port 182 +* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path 225 225 226 -=== 2.2.4 Use CoAP protocol to uplink data === 227 - 228 - 229 -(% 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/]] 230 - 231 - 232 -(% style="color:blue" %)**Use below commands in CPN01:** 233 - 234 -* (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 235 - 236 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ Set CoAP server address and port 237 - 238 -* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/ Set CoAP resource path 239 - 240 240 For parameter description, please refer to AT command set 241 241 242 242 [[image:image-20221021110948-8.png]] 243 243 188 +After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server. 244 244 245 -After configuring the server address and (% style="color:green" %)**reset CPN01**(%%) (via AT+ATZ ), CPN01 will start to uplink sensor values to the CoAP server. 246 - 247 247 [[image:image-20221021110956-9.png]] 248 248 192 +=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** === 249 249 194 +This feature is supported since firmware version v1.0.1 250 250 251 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 196 +* **AT+PRO=2 ** ~/~/ Set to use UDP protocol to uplink 197 +* **AT+SERVADDR=120.24.4.116,5601 ** ~/~/ to set UDP server address and port 198 +* **AT+CFM=1 ** ~/~/If the server does not respond, this command is unnecessary 252 252 253 - 254 -(% style="color:blue" %)**AT Commands:** 255 - 256 -* (% style="color:#037691" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 257 - 258 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ Set UDP server address and port 259 - 260 -* (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 261 - 262 262 [[image:image-20221021111025-10.png]] 263 263 264 - 265 265 [[image:image-20221021111033-11.png||height="241" width="576"]] 266 266 267 267 268 268 206 +=== **2.2.6 Use MQTT protocol to uplink data** === 269 269 270 - ===2.2.6UseMQTTprotocolto uplinkdata===208 +This feature is supported since firmware version v110 271 271 210 +* **AT+PRO=3 ** ~/~/Set to use MQTT protocol to uplink 211 +* **AT+SERVADDR=120.24.4.116,1883 ** ~/~/Set MQTT server address and port 212 +* **AT+CLIENT=CLIENT ** ~/~/Set up the CLIENT of MQTT 213 +* **AT+UNAME=UNAME **~/~/Set the username of MQTT 214 +* **AT+PWD=PWD **~/~/Set the password of MQTT 215 +* **AT+PUBTOPIC=NSE01_PUB **~/~/Set the sending topic of MQTT 216 +* **AT+SUBTOPIC=NSE01_SUB ** ~/~/Set the subscription topic of MQTT 272 272 273 -(% style="color:blue" %)**AT Commands:** 274 - 275 -* (% style="color:#037691" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 276 - 277 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 278 - 279 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT ** (%%) ~/~/ Set up the CLIENT of MQTT 280 - 281 -* (% style="color:#037691" %)**AT+UNAME=UNAME **(%%)** **~/~/ Set the username of MQTT 282 - 283 -* (% style="color:#037691" %)**AT+PWD=PWD **(%%)** **~/~/ Set the password of MQTT 284 - 285 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB **(%%)** **~/~/ Set the sending topic of MQTT 286 - 287 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB ** (%%) ~/~/ Set the subscription topic of MQTT 288 - 289 289 [[image:image-20221021111058-12.png]] 290 290 220 +[[image:image-20221021111108-13.png]] 291 291 292 -[[image:image-20221021111201-16.png||height="472" width="653"]] 293 - 294 294 295 295 296 -MQTT protocol has a much higher power consumption compare withUDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.224 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 297 297 226 +=== **2.2.7 Use TCP protocol to uplink data** === 298 298 228 +This feature is supported since firmware version v110 299 299 300 -=== 2.2.7 Use TCP protocol to uplink data === 230 +* **AT+PRO=4 ** ~/~/ Set to use TCP protocol to uplink 231 +* **AT+SERVADDR=120.24.4.116,5600 ** ~/~/ to set TCP server address and port 301 301 302 - 303 -(% style="color:blue" %)**AT Commands:** 304 - 305 -* (% style="color:#037691" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 306 - 307 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ Set TCP server address and port 308 - 309 309 [[image:image-20221021111125-14.png]] 310 310 311 311 [[image:image-20221021111131-15.png]] ... ... @@ -312,104 +312,85 @@ 312 312 313 313 314 314 239 +=== **2.2.8 Change Update Interval** === 315 315 316 - ===2.2.8ChangeUpdateInterval===241 +User can use below command to change the **uplink interval**. 317 317 243 +* **AT+TDC=600 ** ~/~/ Set Update Interval to 600s 318 318 319 - User can use below command to change the (% style="color:blue" %)**uplink interval**.245 +**NOTE:** 320 320 321 -* (% style="color:#037691"%)**AT+TDC=7200**(%%)~/~/ SetUpdateIntervalto7200s (2hours)247 +**~1. By default, the device will send an uplink message every 1 hour.** 322 322 323 - (%style="color:red" %)**NOTE:**249 +== **2.3 Uplink Payload** == 324 324 325 - 1.Bydefault,thedevicewillsendan uplinkmessageevery1 hour.251 +In this mode, uplink payload includes 87 bytes in total by default. 326 326 327 - 328 - 329 -== 2.3 Uplink Payload == 330 - 331 - 332 -The uplink payload includes 123 bytes in total by default. 333 - 334 334 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. 335 335 255 +|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**2**|**2**|4 256 +|**Value**|[[Device ID>>path:#H2.4.1A0A0DeviceID]]|[[Ver>>path:#H2.4.2A0VersionInfo]]|[[BAT>>path:#H2.4.3A0BatteryInfo]]|[[Signal Strength>>path:#H2.4.4A0SignalStrength]]|MOD|[[Interrupt>>path:#H2.4.8A0DigitalInterrupt]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|Time stamp 336 336 337 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:510px" %) 338 -|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:40px" %)**2**|(% style="width:44px" %)**2**|(% style="width:121px" %)**1**|(% style="width:52px" %)**1**|(% style="width:84px" %)**1**|(% style="width:116px" %)**1**|(% style="width:57px" %)**1**|(% style="width:91px" %)**3** 339 -|=(% style="width: 96px;" %)**Value**|(% style="width:84px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:44px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:121px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:52px" %)MOD|(% style="width:84px" %)[[ Calculate Flag>>||anchor="H2.4.5A0CalculateFlag"]]|(% style="width:116px" %)[[Contact Status>>||anchor="H2.4.7A0ContactStatus"]]|(% style="width:57px" %)[[Alarm>>||anchor="H2.4.6A0Alarm"]]|(% style="width:91px" %)[[Total pulse>>||anchor="H2.4.8A0Totalpulse"]] 258 +|2|2|4|8 group 259 +|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|... 340 340 341 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:510px" %) 342 -|(% style="width:176px" %)**3**|(% style="width:98px" %)**4**|(% style="width:115px" %)**1**|(% style="width:92px" %)**3**|(% style="width:110px" %)**1**|(% style="width:169px" %)**3**|(% style="width:97px" %)4|(% style="width:74px" %)**8 group** 343 -|(% style="width:176px" %)[[The last open duration>>||anchor="H2.4.9A0Thelastopenduration"]]|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% style="width:115px" %)Contact Status|(% style="width:92px" %)Total pulse|(% style="width:110px" %)Calculate Flag|(% style="width:169px" %)The last open duration|(% style="width:97px" %)Time stamp|(% style="width:74px" %)... 344 - 345 345 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data. 346 346 347 347 [[image:image-20221021111201-16.png||height="572" width="792"]] 348 348 349 - 350 350 The payload is ASCII string, representative same HEX: 351 351 352 -**0x (% style="color:red" %)__f867787050213317__ (% style="color:blue" %)__0064__ (% style="color:green" %) _0c78__(% style="color:#00b0f0" %)20b0" %)20042" %)__00__ (% style="color:#660066" %)__00__ (% style="color:#aaaa40" %)__09__(% style="color:#663300" %)66" %)__01(%%)__0100000e0200000263510f39____010000000000000063510e85____010000000000000063510d2e____010000000000000063510c7a____010000000000000063510bc6____010000000000000063510954____010000000000000063510882 __**267 +**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 __//(%%)** 353 353 354 -**where:** 269 +where: 270 +*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317** 355 355 356 -* Device ID:**(%%) 0xf867787050213317 = f867787050213317272 +*(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0** 357 357 358 -* Version:**(%%) 0x0064=100=1.0.0274 +*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V** 359 359 360 -* BAT:**(%%)0c78=3192mV =3.192V276 +*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23** 361 361 362 -* Singal:7=23278 +*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1** 363 363 364 -* Mod:**(%%) 0x01=1280 +*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00= 0** 365 365 366 -* lculateFlag:**(%%) 0x00=0282 +*(% style="color:#037691" %) **Contact Status:**(%%) 0x00= 0** 367 367 368 -* Contact Status:**(%%)284 +*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0** 369 369 370 -* Alarm:**(%%)0x00=0286 +*(% style="color:#037691" %) **Total pulse:0x09 =0** 371 371 372 -* otalpulse:**(%%)0x09=0288 +*(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2** 373 373 374 -* helastopenduration:02=2290 +*(% style="color:#037691" %)**Time stamp :**(%%) 0x6315537b =1662342011** 375 375 376 -* x6315537b=1662342011 (Unix Time)292 +*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000b0200002663510fed** 377 377 378 -* b02ed294 +*(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......** 379 379 380 - * (% style="color:#037691"%)**8sets of recorded data: ContactStatus, Totalpulse, Calculate Flag, The lastopenduration,Timemp :**(%%) 0100000e0200002663510f39,.......296 +== **2.4 Payload Explanation and Sensor Interface** == 381 381 298 +=== **2.4.1 Device ID** === 382 382 383 - ==2.4 PayloadExplanationandSensorInterface==300 +By default, the Device ID equal to the last 15 bits of IMEI. 384 384 302 +User can use **AT+DEUI** to set Device ID 385 385 386 -=== 2.4.1 Device ID === 387 - 388 - 389 -By default, the Device ID is equal to the last 15 bits of IMEI. 390 - 391 -User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID 392 - 393 393 **Example:** 394 394 395 395 AT+DEUI=868411056754138 396 396 397 -The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase theDevice ID.308 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 398 398 310 +=== **2.4.2 Version Info** === 399 399 312 +Specify the software version: 0x64=100, means firmware version 1.00. 400 400 401 - ===2.4.2VersionInfo ===314 +For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0. 402 402 316 +=== **2.4.3 Battery Info** === 403 403 404 -Specify the software version: 0x64=100, which means firmware version 1.00. 405 - 406 -For example 0x00 64 : This device is CPN01 with firmware version 1.0.0. 407 - 408 - 409 - 410 -=== 2.4.3 Battery Info === 411 - 412 - 413 413 Check the battery voltage for CPN01. 414 414 415 415 Ex1: 0x0B45 = 2885mV ... ... @@ -416,11 +416,8 @@ 416 416 417 417 Ex2: 0x0B49 = 2889mV 418 418 324 +=== **2.4.4 Signal Strength** === 419 419 420 - 421 -=== 2.4.4 Signal Strength === 422 - 423 - 424 424 NB-IoT Network signal Strength. 425 425 426 426 **Ex1: 0x1d = 29** ... ... @@ -435,13 +435,10 @@ 435 435 436 436 **99** Not known or not detectable 437 437 340 +=== **2.4.5 Calculate Flag** === 438 438 342 +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. 439 439 440 -=== 2.4.5 Calculate Flag === 441 - 442 - 443 -The calculate flag is a user defined field, IoT server can use this filed to handle different meters with different pulse factors. For example, if there are 100 water meters, meter 1~~50 are 1 liter/pulse and meter 51 ~~ 100 has 1.5 liter/pulse. 444 - 445 445 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. 446 446 447 447 Default value: 0. ... ... @@ -448,36 +448,24 @@ 448 448 449 449 Range (6 bits): (b)000000 ~~ (b) 111111 450 450 350 +=== **2.4.6 Alarm** === 451 451 352 +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]] 452 452 453 -=== 2.4. 6Alarm===354 +=== **2.4.7 Contact Status** === 454 454 455 - 456 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]] 457 - 458 - 459 - 460 -=== 2.4.7 Contact Status === 461 - 462 - 463 463 0: Open 464 464 465 465 1: Close 466 466 360 +=== **2.4.8 Total pulse** === 467 467 362 +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]] 468 468 469 -=== 2.4.8 Total pulse === 470 - 471 - 472 -Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]] 473 - 474 474 Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215 475 475 366 +=== **2.4.9 The last open duration** === 476 476 477 - 478 -=== 2.4.9 The last open duration === 479 - 480 - 481 481 Dry Contact last open duration. 482 482 483 483 Unit: min. ... ... @@ -485,28 +485,23 @@ 485 485 [[image:image-20221021111346-17.png||height="146" width="770"]] 486 486 487 487 375 +=== **2.4.10 Timestamp** === 488 488 489 - === 2.4.10Timestamp ===377 +Time stamp : 0x6315537b =1662342011 490 490 491 - 492 -Timestamp : 0x6315537b =1662342011 493 - 494 494 Convert Unix timestamp to time 2022-9-5 9:40:11. 495 495 496 496 **~ ** 497 497 383 +== **2.5 Downlink Payload** == 498 498 499 -== 2.5 Downlink Payload == 500 - 501 - 502 502 By default, CPN01 prints the downlink payload to console port. 503 503 504 504 [[image:image-20221021111414-18.png]] 505 505 506 - 507 507 **Examples:** 508 508 509 -* (% style="color:#037691" %)**Set TDC**391 +* **Set TDC** 510 510 511 511 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 512 512 ... ... @@ -514,40 +514,36 @@ 514 514 515 515 Payload: 01 00 00 3C TDC=60S 516 516 517 -* (% style="color:#037691" %)**Reset**399 +* **Reset** 518 518 519 519 If payload = 0x04FF, it will reset the NSE01 520 520 521 -* (% style="color:#037691" %)**INTMOD**403 +* **INTMOD** 522 522 523 523 Downlink Payload: 06000003, Set AT+INTMOD=3 524 524 407 +== **2.6 LED Indicator** == 525 525 409 +The CPN01 has an internal LED which is to show the status of different state. 526 526 527 -== 2.6 LED Indicator == 528 - 529 - 530 -The CPN01 has an internal LED which is to show the status of different states. 531 - 532 -* When the device starts normally, the LED will light up for 1 second. 411 +* 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) 412 +* Then the LED will be on for 1 second means device is boot normally. 533 533 * After CPN01 join NB-IoT network. The LED will be ON for 3 seconds. 534 534 * For each uplink probe, LED will be on for 500ms. 535 535 416 +== **2.7 Alarm Base on Timeout** == 536 536 537 - ==2.7 AlarmBaseonTimeout==418 +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: 538 538 539 539 540 - CPN01can monitor thetimeoutfor a statuschange,this feature can be usedtomonitor someevents such as door openingtoo long etc. Related Parameters are:421 +**~1. Keep Status: Status to be monitor** 541 541 542 - 543 -(% style="color:blue" %)**1. Keep Status: Status to be monitor** 544 - 545 545 Keep Status = 1: Monitor Close to Open event 546 546 547 547 Keep Status = 0: Monitor Open to Close event 548 548 549 549 550 - (% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**428 +**2. Keep Time: Timeout to send an Alarm** 551 551 552 552 Range 0 ~~ 65535(0xFFFF) seconds. 553 553 ... ... @@ -556,164 +556,123 @@ 556 556 If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout. 557 557 558 558 559 - (% style="color:blue" %)**AT Command to configure:**437 +**AT Command** to configure: 560 560 561 - (% style="color:#037691" %)**AT+TTRIG=1,30**(%%)**~-~->**When the **Keep Status** change from connectedto disconnect, and device remains in disconnect status for more than 30 seconds. CPN01 will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.439 +**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. 562 562 563 - (% style="color:#037691" %)**AT+TTRIG=0,0 **(%%)**~-~->**Default Value, disable timeout Alarm.441 +**AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm. 564 564 443 +== **2.8 Set debug mode** == 565 565 566 - 567 -== 2.8 Set debug mode == 568 - 569 - 570 570 Feature: Enable or Disable debug mode 571 571 572 -(% style="color:blue" %)**AT Command: AT+DEBUG** 573 573 448 +**AT Command: AT+DEBUG** 449 + 574 574 [[image:image-20221021111629-21.png]] 575 575 452 +== **2.9 Clear Flash Record** == 576 576 577 - 578 -== 2.9 Clear Flash Record == 579 - 580 - 581 581 Feature: Clear flash storage for data log feature. 582 582 583 - (% style="color:blue" %)**AT Command: AT+CLRDTA**456 +**AT Command: AT+CLRDTA** 584 584 585 585 [[image:image-20221021111527-19.png]] 586 586 460 +== ** 2.10 Set trigger mode** == 587 587 462 +➢ AT Command: **AT+TTRMOD** 588 588 589 -== 2.10 Set trigger mode == 590 - 591 - 592 -(% style="color:blue" %)**AT Command: AT+TTRMOD** 593 - 594 594 Feature: Set the trigger interrupt mode. 595 595 596 596 [[image:image-20221021111552-20.png]] 597 597 468 +== **2.11 Set the calculate flag** == 598 598 599 - 600 -== 2.11 Set the calculate flag == 601 - 602 - 603 603 Feature: Set the calculate flag 604 604 605 - (% style="color:blue" %)**AT Command: AT+CALCFLAG**472 +**AT Command: AT+CALCFLAG** 606 606 607 607 [[image:image-20221021111711-22.png]] 608 608 476 +== **2.12 Set count number** == 609 609 610 - 611 -== 2.12 Set count number == 612 - 613 - 614 614 Feature: Manually set the count number 615 615 616 - (% style="color:blue" %)**AT Command: AT+SETCNT**480 +**AT Command: AT+SETCNT** 617 617 618 618 [[image:image-20221021111748-24.png]] 619 619 484 +== **2.13 Set the number of data to be uploaded and the recording time** == 620 620 486 +➢ AT Command: 621 621 622 -= = 2.13Setthe numberofdatatobeuploadedandhe recording time==488 +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) 623 623 624 624 625 - (%style="color:blue"%)**ATCommand:**491 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 626 626 627 - (% style="color:#037691"%)**AT+TR=900**(%%)~/~/ Theunit is seconds,andthedefault is torecorddata onceevery 900 seconds.(The minimum can be setto 180 seconds)493 +== **2.14 Read or Clear cached data** == 628 628 629 - (%style="color:#037691" %)**AT+NOUD=8** (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data canbe uploaded.495 +➢ AT Command: 630 630 497 +AT+CDP ~/~/ Read cached data 631 631 632 - 633 -== 2.14 Read or Clear cached data == 634 - 635 - 636 -(% style="color:blue" %)**AT Command:** 637 - 638 -(% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 639 - 640 -(% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 641 - 642 642 [[image:image-20221021111810-25.png||height="364" width="797"]] 643 643 644 644 502 +AT+CDP=0 ~/~/ Clear cached data 645 645 646 -== 2.15 Firmware Change Log == 504 +== **2.15 Firmware Change Log** == 647 647 506 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]] 648 648 649 - DownloadURL & FirmwareChange log:https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]508 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 650 650 651 - Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]510 +== **2.16 Battery Analysis** == 652 652 512 +=== **2.16.1 Battery Type** === 653 653 514 +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. 654 654 655 - ==2.16 BatteryAnalysis==516 +The battery is designed to last for several years depends on the actually use environment and update interval. 656 656 518 +The battery related documents as below: 657 657 658 -=== 2.16.1 Battery Type === 659 - 660 - 661 -The CPN01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 662 - 663 -The battery is designed to last for several years depends on the actual use environment and update interval. 664 - 665 -The battery-related documents as below: 666 - 667 667 * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 668 - 669 669 * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 670 - 671 671 * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 672 672 673 673 [[image:image-20221021111911-26.png]] 674 674 526 +=== **2.16.2 Power consumption Analyze** === 675 675 676 - 677 -=== 2.16.2 Power consumption Analyze === 678 - 679 - 680 680 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. 681 681 682 682 Instruction to use as below: 683 683 684 - (% 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/]]532 +**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/]] 685 685 686 - (% style="color:blue" %)**Step 2: **(%%)Open it and choose534 +**Step 2: ** Open it and choose 687 687 688 688 * Product Model 689 - 690 690 * Uplink Interval 691 - 692 692 * Working Mode 693 693 694 694 And the Life expectation in difference case will be shown on the right. 695 695 696 -[[image: 1666596205057-567.png]] 542 +[[image:image-20221021111923-27.png||height="253" width="783"]] 697 697 544 +=== **2.16.3 Battery Note** === 698 698 699 - 700 -=== 2.16.3 Battery Note === 701 - 702 - 703 703 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. 704 704 548 +=== **2.16.4 Replace the battery** === 705 705 706 - 707 -=== 2.16.4 Replace the battery === 708 - 709 - 710 710 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). 711 711 552 += **3. Access NB-IoT Module** = 712 712 713 - 714 -= 3. Access NB-IoT Module = 715 - 716 - 717 717 Users can directly access the AT command set of the NB-IoT module. 718 718 719 719 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/]] ... ... @@ -720,14 +720,10 @@ 720 720 721 721 [[image:image-20221021112006-28.png]] 722 722 560 += **4. Using the AT Commands** = 723 723 562 +== **4.1 Access AT Commands** == 724 724 725 -= 4. Using the AT Commands = 726 - 727 - 728 -== 4.1 Access AT Commands == 729 - 730 - 731 731 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]] 732 732 733 733 AT+<CMD>? : Help on <CMD> ... ... @@ -738,9 +738,8 @@ 738 738 739 739 AT+<CMD>=? : Get the value 740 740 574 +**General Commands** 741 741 742 -(% style="color:blue" %)**General Commands** 743 - 744 744 AT : Attention 745 745 746 746 AT? : Short Help ... ... @@ -763,12 +763,15 @@ 763 763 764 764 AT+SERVADDR : Server Address 765 765 766 -AT+TR : 598 +AT+TR : Get or Set record time" 767 767 600 + 768 768 AT+NOUD : Get or Set the number of data to be uploaded 769 769 770 -AT+CDP : Read or Clear cached data 771 771 604 +AT+CDP : Read or Clear cached data 605 + 606 + 772 772 AT+ DEBUG : Enable or Disable debug mode 773 773 774 774 AT+ TTRIG : Get or Set Alarm Base on Timeout ... ... @@ -779,19 +779,16 @@ 779 779 780 780 AT+ CLRC : Clear current door open count 781 781 617 +**COAP Management** 782 782 783 -(% style="color:blue" %)**COAP Management** 784 - 785 785 AT+URI : Resource parameters 786 786 621 +**UDP Management** 787 787 788 -(% style="color:blue" %)**UDP Management** 789 - 790 790 AT+CFM : Upload confirmation mode (only valid for UDP) 791 791 625 +**MQTT Management** 792 792 793 -(% style="color:blue" %)**MQTT Management** 794 - 795 795 AT+CLIENT : Get or Set MQTT client 796 796 797 797 AT+UNAME : Get or Set MQTT Username ... ... @@ -802,72 +802,86 @@ 802 802 803 803 AT+SUBTOPIC : Get or Set MQTT subscription topic 804 804 637 +**Information** 805 805 806 -(% style="color:blue" %)**Information** 807 - 808 808 AT+FDR : Factory Data Reset 809 809 810 810 AT+PWORD : Serial Access Password 811 811 643 += **5. FAQ** = 812 812 645 +== **5.1 How to Upgrade Firmware** == 813 813 814 - =5.FAQ=647 +User can upgrade the firmware for 1) bug fix, 2) new feature release. 815 815 649 +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]] 816 816 817 - ==5.1HowtoUpgradeFirmware==651 +**Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.** 818 818 653 +== **5.2 Can I calibrate CPN01 to different soil types?** == 819 819 820 - Usercan upgrade thefirmware for1)bugfix,2)newfeaturerelease.655 +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]]. 821 821 822 - Pleaseseethis link forhow toupgrade: [[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]]657 += **6. Trouble Shooting** = 823 823 824 - (% style="color:red" %)**Notice: **(% style="color:blue"%)**CPN01**(%%)**and (% style="color:blue" %)CPL01(%%)**(% style="color:blue" %) (%%)**share the samemotherboard. They use the same connectionandmethod to update.**659 +== **6.1 Connection problem when uploading firmware** == 825 825 661 +**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]] 826 826 663 +== **6.2 AT Command input doesn't work** == 827 827 828 - =6.TroubleShooting=665 +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. 829 829 667 += **7. Order Info** = 830 830 831 - == 6.1 Connectionproblem whenuploading firmware==669 +Part Number**:** CPN01 832 832 671 += **8. Packing Info** = 833 833 834 - (% 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]]673 +**Package Includes**: 835 835 675 +* CPN01 NB-IoT Soil Moisture & EC Sensor x 1 676 +* External antenna x 1 836 836 678 +**Dimension and weight**: 837 837 838 -== 6.2 AT Command input doesn't work == 680 +* Size: 195 x 125 x 55 mm 681 +* Weight: 420g 839 839 683 += **9. Support** = 840 840 841 -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. 685 +* 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. 686 +* 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]] 842 842 688 + 843 843 844 844 845 -= 7. Order Info = 846 846 847 847 848 -Part Number**:** CPN01 849 849 850 850 851 851 852 -= 8. Packing Info = 853 853 854 854 855 -(% style="color:blue" %)**Package Includes**: 856 856 857 -* CPN01 Open/Close Sensor x 1 858 -* External antenna x 1 859 859 860 -(% style="color:blue" %)**Dimension and weight**: 861 861 862 -* Size: 195 x 125 x 55 mm 863 -* Weight: 420g 864 864 865 865 866 -= 9. Support = 867 867 868 868 869 -* 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. 870 870 871 -* 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]] 872 872 873 - 707 + 708 + 709 + 710 + 711 + 712 + 713 + 714 + 715 + 716 + 717 + 718 + 719 +
- 1666596205057-567.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -179.8 KB - Content
- image-20221022234529-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -43.3 KB - Content
- image-20221022234602-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -135.7 KB - Content
- image-20221023000439-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -82.1 KB - Content