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 (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -137,7 +137,7 @@ 137 137 138 138 139 139 140 -=== **2.2.2 Insert NB-IoTSIM card** ===140 +=== **2.2.2 Insert SIM card** === 141 141 142 142 Insert the NB-IoT Card get from your provider. 143 143 ... ... @@ -146,7 +146,7 @@ 146 146 [[image:image-20221021110745-6.png]] 147 147 148 148 149 -=== **2.2.3 Connect USB – TTL to CPN01 andconfigure it** ===149 +=== **2.2.3 Connect USB – TTL to CPN01 to configure it** === 150 150 151 151 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. 152 152 ... ... @@ -175,35 +175,30 @@ 175 175 176 176 **Note: the valid AT Commands can be found at: **[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]] 177 177 178 - 179 179 === **2.2.4 Use CoAP protocol to uplink data** === 180 180 181 -**Note: if you don't have aCoAP server, you can refer this link to set upa 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/]]180 +**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/]] 182 182 182 +**Use below commands:** 183 183 184 -**Use below commands in CPN01:** 185 - 186 186 * **AT+PRO=1** ~/~/ Set to use CoAP protocol to uplink 187 -* **AT+SERVADDR=120.24.4.116,5683 ** Set CoAP server address and port188 -* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set C oAP resource path185 +* **AT+SERVADDR=120.24.4.116,5683 ** ~/~/ to set CoAP server address and port 186 +* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path 189 189 190 190 For parameter description, please refer to AT command set 191 191 192 192 [[image:image-20221021110948-8.png]] 193 193 192 +After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server. 194 194 195 -After configuring the server address and **reset CPN01** (via AT+ATZ ), CPN01 will start to uplink sensor values to the CoAP server. 196 - 197 197 [[image:image-20221021110956-9.png]] 198 198 199 - 200 200 === **2.2.5 Use UDP protocol to uplink data(Default protocol)** === 201 201 198 +This feature is supported since firmware version v1.0.1 202 202 203 -**AT Commands:** 204 - 205 205 * **AT+PRO=2 ** ~/~/ Set to use UDP protocol to uplink 206 -* **AT+SERVADDR=120.24.4.116,5601 ** ~/~/ Set UDP server address and port201 +* **AT+SERVADDR=120.24.4.116,5601 ** ~/~/ to set UDP server address and port 207 207 * **AT+CFM=1 ** ~/~/If the server does not respond, this command is unnecessary 208 208 209 209 [[image:image-20221021111025-10.png]] ... ... @@ -214,9 +214,8 @@ 214 214 215 215 === **2.2.6 Use MQTT protocol to uplink data** === 216 216 212 +This feature is supported since firmware version v110 217 217 218 -**AT Commands:** 219 - 220 220 * **AT+PRO=3 ** ~/~/Set to use MQTT protocol to uplink 221 221 * **AT+SERVADDR=120.24.4.116,1883 ** ~/~/Set MQTT server address and port 222 222 * **AT+CLIENT=CLIENT ** ~/~/Set up the CLIENT of MQTT ... ... @@ -231,15 +231,14 @@ 231 231 232 232 233 233 234 -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.228 +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. 235 235 236 - 237 237 === **2.2.7 Use TCP protocol to uplink data** === 238 238 239 - **ATCommands**232 +This feature is supported since firmware version v110 240 240 241 241 * **AT+PRO=4 ** ~/~/ Set to use TCP protocol to uplink 242 -* **AT+SERVADDR=120.24.4.116,5600 ** Set TCP server address and port235 +* **AT+SERVADDR=120.24.4.116,5600 ** ~/~/ to set TCP server address and port 243 243 244 244 [[image:image-20221021111125-14.png]] 245 245 ... ... @@ -251,16 +251,15 @@ 251 251 252 252 User can use below command to change the **uplink interval**. 253 253 254 -* **AT+TDC= 7200 ** ~/~/ Set Update Interval to7200s(2 hours)247 +* **AT+TDC=600 ** ~/~/ Set Update Interval to 600s 255 255 256 256 **NOTE:** 257 257 258 258 **~1. By default, the device will send an uplink message every 1 hour.** 259 259 260 - 261 261 == **2.3 Uplink Payload** == 262 262 263 - The uplink payload includes 87 bytes in total by default.255 +In this mode, uplink payload includes 87 bytes in total by default. 264 264 265 265 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. 266 266 ... ... @@ -289,9 +289,9 @@ 289 289 290 290 *(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1 291 291 292 -*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00=0 284 +*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00= 0 293 293 294 -*(% style="color:#037691" %) **Contact Status:**(%%) 0x00=0 286 +*(% style="color:#037691" %) **Contact Status:**(%%) 0x00= 0 295 295 296 296 *(% style="color:#037691" %) **Alarm:**(%%)0x00 =0 297 297 ... ... @@ -299,18 +299,17 @@ 299 299 300 300 *(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2 301 301 302 -*(% style="color:#037691" %)** (Unix Time)294 +*(% style="color:#037691" %)**Time stamp :**(%%) 0x6315537b =1662342011 303 303 304 304 *(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000b0200002663510fed 305 305 306 306 *(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,....... 307 307 308 - 309 309 == **2.4 Payload Explanation and Sensor Interface** == 310 310 311 311 === **2.4.1 Device ID** === 312 312 313 -By default, the Device ID isequal to the last 15 bits of IMEI.304 +By default, the Device ID equal to the last 15 bits of IMEI. 314 314 315 315 User can use **AT+DEUI** to set Device ID 316 316 ... ... @@ -318,16 +318,14 @@ 318 318 319 319 AT+DEUI=868411056754138 320 320 321 -The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase theDevice ID.312 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 322 322 323 - 324 324 === **2.4.2 Version Info** === 325 325 326 -Specify the software version: 0x64=100, whichmeans firmware version 1.00.316 +Specify the software version: 0x64=100, means firmware version 1.00. 327 327 328 -For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.318 +For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0. 329 329 330 - 331 331 === **2.4.3 Battery Info** === 332 332 333 333 Check the battery voltage for CPN01. ... ... @@ -336,7 +336,6 @@ 336 336 337 337 Ex2: 0x0B49 = 2889mV 338 338 339 - 340 340 === **2.4.4 Signal Strength** === 341 341 342 342 NB-IoT Network signal Strength. ... ... @@ -353,10 +353,9 @@ 353 353 354 354 **99** Not known or not detectable 355 355 356 - 357 357 === **2.4.5 Calculate Flag** === 358 358 359 -The calculate flag is a user define dfield, IoT server can use this filed to handle different meterswith 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.346 +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. 360 360 361 361 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. 362 362 ... ... @@ -364,12 +364,10 @@ 364 364 365 365 Range (6 bits): (b)000000 ~~ (b) 111111 366 366 367 - 368 368 === **2.4.6 Alarm** === 369 369 370 370 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]] 371 371 372 - 373 373 === **2.4.7 Contact Status** === 374 374 375 375 0: Open ... ... @@ -376,14 +376,12 @@ 376 376 377 377 1: Close 378 378 379 - 380 380 === **2.4.8 Total pulse** === 381 381 382 -Total pulse/counting base don 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]]366 +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 383 384 384 Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215 385 385 386 - 387 387 === **2.4.9 The last open duration** === 388 388 389 389 Dry Contact last open duration. ... ... @@ -395,7 +395,7 @@ 395 395 396 396 === **2.4.10 Timestamp** === 397 397 398 -Timestamp : 0x6315537b =1662342011 381 +Time stamp : 0x6315537b =1662342011 399 399 400 400 Convert Unix timestamp to time 2022-9-5 9:40:11. 401 401 ... ... @@ -427,7 +427,7 @@ 427 427 428 428 == **2.6 LED Indicator** == 429 429 430 -The CPN01 has an internal LED which is to show the status of different state s.413 +The CPN01 has an internal LED which is to show the status of different state. 431 431 432 432 * 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) 433 433 * Then the LED will be on for 1 second means device is boot normally. ... ... @@ -434,10 +434,9 @@ 434 434 * After CPN01 join NB-IoT network. The LED will be ON for 3 seconds. 435 435 * For each uplink probe, LED will be on for 500ms. 436 436 437 - 438 438 == **2.7 Alarm Base on Timeout** == 439 439 440 -CP N01 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:422 +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: 441 441 442 442 443 443 **~1. Keep Status: Status to be monitor** ... ... @@ -458,11 +458,10 @@ 458 458 459 459 **AT Command** to configure: 460 460 461 -**AT+TTRIG=1,30** ~-~-> When the **Keep Status** change from connect edto 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.443 +**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. 462 462 463 463 **AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm. 464 464 465 - 466 466 == **2.8 Set debug mode** == 467 467 468 468 Feature: Enable or Disable debug mode ... ... @@ -534,11 +534,11 @@ 534 534 535 535 === **2.16.1 Battery Type** === 536 536 537 -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. 518 +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. 538 538 539 -The battery is designed to last for several years depends on the actual use environment and update interval. 520 +The battery is designed to last for several years depends on the actually use environment and update interval. 540 540 541 -The battery -related documents as below:522 +The battery related documents as below: 542 542 543 543 * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 544 544 * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] ... ... @@ -572,7 +572,6 @@ 572 572 573 573 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). 574 574 575 - 576 576 = **3. Access NB-IoT Module** = 577 577 578 578 Users can directly access the AT command set of the NB-IoT module. ... ... @@ -672,10 +672,12 @@ 672 672 673 673 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]] 674 674 675 -**Notice, **CPN01 **and **CP L01 **share the same mother board. They use the same connection and method to update.**655 +**Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.** 676 676 677 - 657 +== **5.2 Can I calibrate CPN01 to different soil types?** == 678 678 659 +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]]. 660 + 679 679 = **6. Trouble Shooting** = 680 680 681 681 == **6.1 Connection problem when uploading firmware** == ... ... @@ -682,22 +682,19 @@ 682 682 683 683 **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]] 684 684 685 - 686 686 == **6.2 AT Command input doesn't work** == 687 687 688 688 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. 689 689 690 - 691 691 = **7. Order Info** = 692 692 693 693 Part Number**:** CPN01 694 694 695 - 696 696 = **8. Packing Info** = 697 697 698 698 **Package Includes**: 699 699 700 -* CPN01 Open/Close Sensor x 1679 +* CPN01 NB-IoT Soil Moisture & EC Sensor x 1 701 701 * External antenna x 1 702 702 703 703 **Dimension and weight**: