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