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, 3 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.David - Content
-
... ... @@ -7,11 +7,11 @@ 7 7 8 8 == **1.1 **What is CPN01 **NB-IoT** Pulse/Contact Sensor == 9 9 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 N b-IoT network. User can see the (% style="color:blue" %)dry contact status, open time, and open counts(%%) in the IoT Server.10 +The Dragino CPN01 is an (% style="color:blue" %)**NB-IoT Dry Contact Sensor**(%%). It detects open/close status and uplinks the info to IoT server via NB-IoT network. User can see the (% style="color:blue" %)**dry contact status, open time, and open counts**(%%) in the IoT Server. 11 11 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.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 -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. 14 +CPN01 has** (% style="color:blue" %)Open-Alarm feature(%%)**, user can set this feature so CPN01 will send an alarm if the contact has been open exceeds a certain time. 15 15 16 16 CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures. 17 17 ... ... @@ -57,12 +57,13 @@ 57 57 58 58 == **1.4 Installation** == 59 59 60 -Connect CP L01 to an Open Close sensor like below. So it can detect theopen/close event.60 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event. 61 61 62 62 [[image:image-20221021110329-1.png]] 63 63 64 -[[image:image-2022102 1110340-2.png]]64 +[[image:image-20221022234602-2.png||height="288" width="922"]] 65 65 66 + 66 66 == **1.5 Applications** == 67 67 68 68 * Open/Close Detection ... ... @@ -79,35 +79,32 @@ 79 79 80 80 === **1.7.1 Pin Definition** === 81 81 82 -CP L01 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 usermanualof LSN50v2 at:[[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>url:https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]83 +CPN01 is pre-configured to connect to two external wires. The other pins are not used. If user wants to know more about other pins, please refer to the **[[LSN50v2 User Manual>>doc:Main.User Manual for LoRaWAN End Nodes.LSN50 & LSN50-V2 - LoRaWAN Sensor Node User Manual.WebHome]]**. 83 83 85 + 84 84 === **1.7.2 Jumper JP2(Power ON/OFF)** === 85 85 86 - 87 87 Power on Device when putting this jumper. 88 88 89 89 90 - 91 91 === **1.7.3 BOOT MODE / SW1** === 92 92 93 93 94 -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.94 +1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run. 95 95 96 -2) Flash: work mode, the device starts to work and send out console output for further debug 96 +2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging. 97 97 98 98 99 - 100 100 === **1.7.4 Reset Button** === 101 101 102 102 103 103 Press to reboot the device. 104 104 105 -== == 106 106 107 107 === **1.7.5 LED** === 108 108 109 109 110 - Itwillflash:108 +The LED will blink when : 111 111 112 112 1. Boot the device in flash mode 113 113 1. Send an uplink packet ... ... @@ -116,36 +116,40 @@ 116 116 117 117 == **2.1 How it works** == 118 118 119 -The CPN01 is equipped with a NB-IoT module, the pre-loaded firmware in CPN01 will get en vironmentdatafrom sensorsand send the value tolocalNB-IoT networkvia the NB-IoT module.117 +The CPN01 is equipped with an NB-IoT module, the pre-loaded firmware in CPN01 will get **Open/Close Event or Count** from sensor and send the value to the NB-IoT network. The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01. 120 120 121 -The diagram below shows the working flow in default firmware of CPN01: 119 +The diagram below shows the working flow in the default firmware of CPN01: 122 122 123 123 [[image:image-20221021110615-5.png]] 124 124 125 -== **2.2 Configure the CPN01** == 126 126 124 +== **2.2 Configure CPN01** == 125 + 127 127 === **2.2.1 Test Requirement** === 128 128 129 -To use CPN01 in your city, make sure meet below requirements: 128 +To use CPN01 in your city, make sure to meet below requirements: 130 130 131 -* Your local operator has already distributed a NB-IoT Network there.130 +* Your local operator has already distributed an NB-IoT Network. 132 132 * The local NB-IoT network used the band that CPN01 supports. 133 133 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 134 134 135 -Below figure shows our testing structure. 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. 136 136 136 +[[image:image-20221023000439-3.png]] 137 + 137 137 138 138 139 -=== **2.2.2 Insert SIM card** === 140 +=== **2.2.2 Insert NB-IoT SIM card** === 140 140 141 141 Insert the NB-IoT Card get from your provider. 142 142 143 -User need to take out the NB-IoT module and insert the SIM card like below: 144 +User needs to take out the NB-IoT module and insert the SIM card like below: 144 144 145 145 [[image:image-20221021110745-6.png]] 146 146 147 -=== **2.2.3 Connect USB – TTL to CPN01 to configure it** === 148 148 149 +=== **2.2.3 Connect USB – TTL to CPN01 and configure it** === 150 + 149 149 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. 150 150 151 151 **Connection:** ... ... @@ -164,36 +164,44 @@ 164 164 * Parity: **None** 165 165 * Flow Control: **None** 166 166 167 -Make sure the switch is in FLASH position, then power on deviceby connecting thejumperon CPN01. CPN01 will outputsystem info once poweras below,wecan enterthe**password: 12345678** to access AT Command input.169 +Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%). 168 168 169 169 [[image:image-20221021110817-7.png]] 170 170 173 +CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input. 174 + 175 + 171 171 **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]] 172 172 178 + 173 173 === **2.2.4 Use CoAP protocol to uplink data** === 174 174 175 -**Note: if you don't have CoAP server, you can refer this link to set up o ne: **[[**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/]]181 +**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/]] 176 176 177 -**Use below commands:** 178 178 184 +**Use below commands in CPN01:** 185 + 179 179 * **AT+PRO=1** ~/~/ Set to use CoAP protocol to uplink 180 -* **AT+SERVADDR=120.24.4.116,5683 ** ~/~/ to set CoAP server address and port181 -* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set C OAP resource path187 +* **AT+SERVADDR=120.24.4.116,5683 ** ~/~/ Set CoAP server address and port 188 +* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set CoAP resource path 182 182 183 183 For parameter description, please refer to AT command set 184 184 185 185 [[image:image-20221021110948-8.png]] 186 186 187 -After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server. 188 188 195 +After configuring the server address and **reset CPN01** (via AT+ATZ ), CPN01 will start to uplink sensor values to the CoAP server. 196 + 189 189 [[image:image-20221021110956-9.png]] 190 190 199 + 191 191 === **2.2.5 Use UDP protocol to uplink data(Default protocol)** === 192 192 193 -This feature is supported since firmware version v1.0.1 194 194 203 +**AT Commands:** 204 + 195 195 * **AT+PRO=2 ** ~/~/ Set to use UDP protocol to uplink 196 -* **AT+SERVADDR=120.24.4.116,5601 ** ~/~/ to set UDP server address and port206 +* **AT+SERVADDR=120.24.4.116,5601 ** ~/~/ Set UDP server address and port 197 197 * **AT+CFM=1 ** ~/~/If the server does not respond, this command is unnecessary 198 198 199 199 [[image:image-20221021111025-10.png]] ... ... @@ -204,8 +204,9 @@ 204 204 205 205 === **2.2.6 Use MQTT protocol to uplink data** === 206 206 207 -This feature is supported since firmware version v110 208 208 218 +**AT Commands:** 219 + 209 209 * **AT+PRO=3 ** ~/~/Set to use MQTT protocol to uplink 210 210 * **AT+SERVADDR=120.24.4.116,1883 ** ~/~/Set MQTT server address and port 211 211 * **AT+CLIENT=CLIENT ** ~/~/Set up the CLIENT of MQTT ... ... @@ -220,14 +220,15 @@ 220 220 221 221 222 222 223 -MQTT protocol has a much higher power consumption compare vsUDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.234 +MQTT protocol has a much higher power consumption compare with UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 224 224 236 + 225 225 === **2.2.7 Use TCP protocol to uplink data** === 226 226 227 -T hisfeature is supported since firmware versionv110239 +**AT Commands** 228 228 229 229 * **AT+PRO=4 ** ~/~/ Set to use TCP protocol to uplink 230 -* **AT+SERVADDR=120.24.4.116,5600 ** ~/~/ to set TCP server address and port242 +* **AT+SERVADDR=120.24.4.116,5600 ** ~/~/ Set TCP server address and port 231 231 232 232 [[image:image-20221021111125-14.png]] 233 233 ... ... @@ -239,23 +239,25 @@ 239 239 240 240 User can use below command to change the **uplink interval**. 241 241 242 -* **AT+TDC= 600 ** ~/~/ Set Update Interval to600s254 +* **AT+TDC=7200 ** ~/~/ Set Update Interval to 7200s (2 hours) 243 243 244 244 **NOTE:** 245 245 246 246 **~1. By default, the device will send an uplink message every 1 hour.** 247 247 260 + 248 248 == **2.3 Uplink Payload** == 249 249 250 - In this mode,uplink payload includes87bytes in total by default.263 +The uplink payload includes 123 bytes in total by default. 251 251 252 252 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. 253 253 254 -|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|** 2**|**2**|4255 -|**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|[[SoilTemperature>>path:#H2.4.6A0SoilTemperature]]|Time stamp267 +|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**1**|**1**|**3** 268 +|**Value**|[[Device ID>>path:#H2.4.1A0A0DeviceID]]|[[Ver>>path:#H2.4.2A0VersionInfo]]|[[BAT>>path:#H2.4.3A0BatteryInfo]]|[[Signal Strength>>path:#H2.4.4A0SignalStrength]]|MOD|[[ Calculate Flag>>path:#H2.4.8A0DigitalInterrupt]]|Contact Status|Alarm|Total pulse 256 256 257 -|2|2|4|8 group 258 -|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|... 270 +(% style="width:1201px" %) 271 +|**3**|**4**|**1**|**3**|**1**|**3**|4|**8 group**|(% style="width:1px" %) 272 +|The last open duration|Time stamp|Contact Status|Total pulse|Calculate Flag|The last open duration|Time stamp|...|(% style="width:1px" %) 259 259 260 260 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data. 261 261 ... ... @@ -276,9 +276,9 @@ 276 276 277 277 *(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1 278 278 279 -*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00= 293 +*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00=0 280 280 281 -*(% style="color:#037691" %) **Contact Status:**(%%) 0x00= 295 +*(% style="color:#037691" %) **Contact Status:**(%%) 0x00=0 282 282 283 283 *(% style="color:#037691" %) **Alarm:**(%%)0x00 =0 284 284 ... ... @@ -286,17 +286,18 @@ 286 286 287 287 *(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2 288 288 289 -*(% style="color:#037691" %)**Time stamp :**(%%) 0x6315537b =1662342011 303 +*(% style="color:#037691" %)** Time stamp :**(%%) 0x6315537b =1662342011 (Unix Time) 290 290 291 -*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000b0200002663510fed 305 +*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 01 00000b 02 000026 63510fed 292 292 293 293 *(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,....... 294 294 309 + 295 295 == **2.4 Payload Explanation and Sensor Interface** == 296 296 297 297 === **2.4.1 Device ID** === 298 298 299 -By default, the Device ID equal to the last 15 bits of IMEI. 314 +By default, the Device ID is equal to the last 15 bits of IMEI. 300 300 301 301 User can use **AT+DEUI** to set Device ID 302 302 ... ... @@ -304,14 +304,16 @@ 304 304 305 305 AT+DEUI=868411056754138 306 306 307 -The Device ID is stored in a non e-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.322 +The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID. 308 308 324 + 309 309 === **2.4.2 Version Info** === 310 310 311 -Specify the software version: 0x64=100, means firmware version 1.00. 327 +Specify the software version: 0x64=100, which means firmware version 1.00. 312 312 313 -For example :0x00 64 :this device is CPN01 with firmware version 1.0.0.329 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0. 314 314 331 + 315 315 === **2.4.3 Battery Info** === 316 316 317 317 Check the battery voltage for CPN01. ... ... @@ -320,6 +320,7 @@ 320 320 321 321 Ex2: 0x0B49 = 2889mV 322 322 340 + 323 323 === **2.4.4 Signal Strength** === 324 324 325 325 NB-IoT Network signal Strength. ... ... @@ -336,9 +336,10 @@ 336 336 337 337 **99** Not known or not detectable 338 338 357 + 339 339 === **2.4.5 Calculate Flag** === 340 340 341 -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 360 +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. 342 342 343 343 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. 344 344 ... ... @@ -346,10 +346,12 @@ 346 346 347 347 Range (6 bits): (b)000000 ~~ (b) 111111 348 348 368 + 349 349 === **2.4.6 Alarm** === 350 350 351 351 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]] 352 352 373 + 353 353 === **2.4.7 Contact Status** === 354 354 355 355 0: Open ... ... @@ -356,12 +356,14 @@ 356 356 357 357 1: Close 358 358 380 + 359 359 === **2.4.8 Total pulse** === 360 360 361 -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]] 383 +Total pulse/counting based 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]] 362 362 363 363 Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215 364 364 387 + 365 365 === **2.4.9 The last open duration** === 366 366 367 367 Dry Contact last open duration. ... ... @@ -373,7 +373,7 @@ 373 373 374 374 === **2.4.10 Timestamp** === 375 375 376 -Time 399 +Timestamp : 0x6315537b =1662342011 377 377 378 378 Convert Unix timestamp to time 2022-9-5 9:40:11. 379 379 ... ... @@ -405,16 +405,15 @@ 405 405 406 406 == **2.6 LED Indicator** == 407 407 408 -The CPN01 has an internal LED which is to show the status of different state. 431 +The CPN01 has an internal LED which is to show the status of different states. 409 409 410 -* 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) 411 -* Then the LED will be on for 1 second means device is boot normally. 433 +* When the device starts normally, the LED will light up for 1 second. 412 412 * After CPN01 join NB-IoT network. The LED will be ON for 3 seconds. 413 413 * For each uplink probe, LED will be on for 500ms. 414 414 415 415 == **2.7 Alarm Base on Timeout** == 416 416 417 -CP L01 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:439 +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: 418 418 419 419 420 420 **~1. Keep Status: Status to be monitor** ... ... @@ -435,10 +435,11 @@ 435 435 436 436 **AT Command** to configure: 437 437 438 -**AT+TTRIG=1,30** ~-~-> When the **Keep Status** change from connect to disconnect, and device remains in disconnect status for more than 30 seconds. CP L01 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.460 +**AT+TTRIG=1,30** ~-~-> When the **Keep Status** change from connected to 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 439 440 -**AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm. 462 +**AT+TTRIG=0,0 ** ~-~-> Default Value, disable timeout Alarm. 441 441 464 + 442 442 == **2.8 Set debug mode** == 443 443 444 444 Feature: Enable or Disable debug mode ... ... @@ -510,11 +510,11 @@ 510 510 511 511 === **2.16.1 Battery Type** === 512 512 513 -The CPN01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non e-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.536 +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. 514 514 515 -The battery is designed to last for several years depends on the actual lyuse environment and update interval.538 +The battery is designed to last for several years depends on the actual use environment and update interval. 516 516 517 -The battery 540 +The battery-related documents as below: 518 518 519 519 * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 520 520 * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] ... ... @@ -548,6 +548,7 @@ 548 548 549 549 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). 550 550 574 + 551 551 = **3. Access NB-IoT Module** = 552 552 553 553 Users can directly access the AT command set of the NB-IoT module. ... ... @@ -647,12 +647,9 @@ 647 647 648 648 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]] 649 649 650 -**Notice, **CPN01 **and **CP N01 **share the same mother board. They use the same connection and method to update.**674 +**Notice, **CPN01 **and **CPL01 **share the same mother board. They use the same connection and method to update.** 651 651 652 -== **5.2 Can I calibrate CPN01 to different soil types?** == 653 653 654 -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]]. 655 - 656 656 = **6. Trouble Shooting** = 657 657 658 658 == **6.1 Connection problem when uploading firmware** == ... ... @@ -659,19 +659,22 @@ 659 659 660 660 **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]] 661 661 683 + 662 662 == **6.2 AT Command input doesn't work** == 663 663 664 664 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. 665 665 688 + 666 666 = **7. Order Info** = 667 667 668 668 Part Number**:** CPN01 669 669 693 + 670 670 = **8. Packing Info** = 671 671 672 672 **Package Includes**: 673 673 674 -* CPN01 NB-IoT SoilMoisture& ECSensor x 1698 +* CPN01 Open/Close Sensor x 1 675 675 * External antenna x 1 676 676 677 677 **Dimension and weight**:
- image-20221022234529-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +43.3 KB - Content
- image-20221022234602-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +135.7 KB - Content
- image-20221023000439-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +82.1 KB - Content