Changes for page NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual

Last modified by Mengting Qiu on 2024/04/02 17:03

From version < 40.1 >

edited by Edwin Chen
on 2022/10/23 00:07

To version < 48.15 >

edited by Xiaoling
on 2022/10/24 16:40

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 1 added, 0 removed)
- 1666596205057-567.png

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.Edwin
++XWiki.Xiaoling

Content

@@ -1,12 +1,22 @@
  (% style="text-align:center" %)
  [[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"]]
++
++
++**Table of Contents：**
++
  {{toc/}}
--= **1. Introduction** =
--== **1.1 **What is CPN01 **NB-IoT** Pulse/Contact Sensor ==
++
++
++= 1.  Introduction =
++
++
++== 1.1  What is CPN01 NB-IoT Pulse/Contact Sensor ==
++
++
  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.
  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.
@@ -22,8 +22,10 @@
--== **1.2 Features** ==
++== 1.2  Features ==
++
++
  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
  * Open/Close detect
  * Open/Close statistics
@@ -39,14 +39,17 @@
  * Micro SIM card slot for NB-IoT SIM
  * 8500mAh Battery for long-term use
--== **1.3  Specification** ==
--**Common DC Characteristics:**
++== 1.3  Specification ==
++
++
++(% style="color:blue" %)**Common DC Characteristics:**
++
  * Supply Voltage: 2.1v ~~ 3.6v
  * Operating Temperature: -40 ~~ 85°C
--**NB-IoT Spec:**
++(% style="color:blue" %)**NB-IoT Spec:**
  * - B1 @H-FDD: 2100MHz
  * - B3 @H-FDD: 1800MHz
@@ -55,8 +55,11 @@
  * - B20 @H-FDD: 800MHz
  * - B28 @H-FDD: 700MHz
--== **1.4 Installation** ==
++
++== 1.4  Installation ==
++
++
  Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
  [[image:image-20221021110329-1.png]]
@@ -64,68 +64,89 @@
  [[image:image-20221022234602-2.png||height="288" width="922"]]
--== **1.5 Applications** ==
++== 1.5  Applications ==
++
++
  * Open/Close Detection
  * Pulse meter application
  * Dry Contact Detection
--== **1.6 Mechanical** ==
++
++== 1.6  Mechanical ==
++
++
  [[image:image-20221021110415-3.png]]
--== ** 1.7 Pin Definitions and Switch** ==
++
++== 1.7  Pin Definitions and Switch ==
++
  [[image:image-20221021110429-4.png]]
--=== **1.7.1 Pin Definition** ===
++=== 1.7.1  Pin Definition ===
++
++
  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]]**.
--=== **1.7.2 Jumper JP2(Power ON/OFF)** ===
++=== 1.7.2  Jumper JP2(Power ON/OFF) ===
++
++
  Power on Device when putting this jumper.
--=== **1.7.3 BOOT MODE / SW1** ===
++=== 1.7.3  BOOT MODE / SW1 ===
--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.
--2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
++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.
++2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
--=== **1.7.4 Reset Button** ===
++=== 1.7.4  Reset Button ===
++
++
  Press to reboot the device.
--=== **1.7.5 LED** ===
++=== 1.7.5  LED ===
++
  The LED will blink when :
--1. Boot the device in flash mode
--1. Send an uplink packet
++1.  Boot the device in flash mode
++2.  Send an uplink packet
--= **2.  Use CPN01 to communicate with IoT Server** =
--== **2.1  How it works** ==
--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.
++= 2.  Use CPN01 to communicate with IoT Server =
++
++== 2.1  How it works ==
++
++
++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.
++
  The diagram below shows the working flow in the default firmware of CPN01:
  [[image:image-20221021110615-5.png]]
--== **2.2  Configure CPN01** ==
--=== **2.2.1  Test Requirement** ===
++== 2.2  Configure CPN01 ==
++
++=== 2.2.1  Test Requirement ===
++
++
  To use CPN01 in your city, make sure to meet below requirements:
  * Your local operator has already distributed an NB-IoT Network.
@@ -132,14 +132,16 @@
  * The local NB-IoT network used the band that CPN01 supports.
  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
--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.
++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.
  [[image:image-20221023000439-3.png]]
--=== **2.2.2  Insert SIM card** ===
++=== 2.2.2  Insert NB-IoT SIM card ===
++
++
  Insert the NB-IoT Card get from your provider.
  User needs to take out the NB-IoT module and insert the SIM card like below:
@@ -147,94 +147,127 @@
  [[image:image-20221021110745-6.png]]
--=== **2.2.3  Connect USB – TTL to CPN01 to configure it** ===
--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.
++=== 2.2.3  Connect USB – TTL to CPN01 and configure it ===
--**Connection:**
-- USB TTL GND <~-~-~-~-> GND
++User need 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 USB to TTL adapter to connect to CPN01 and use AT Commands to configure it, as below.
-- USB TTL TXD <~-~-~-~-> UART_RXD
++(% style="color:blue" %)**Connection:**
-- USB TTL RXD <~-~-~-~-> UART_TXD
++(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
++(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD**
++
++(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD**
++
++
  In the PC, use below serial tool settings:
--* Baud:       **9600**
--* Data bits:** 8**
--* Stop bits: **1**
--* Parity:      **None**
--* Flow Control: **None**
++* Baud:       (% style="color:red" %)**9600**
--Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:yellow" %)**Yellow Jumper**(%%).
++* Data bits:** (% style="color:red" %)8(%%)**
++* Stop bits: (% style="color:red" %)**1**
++
++* Parity:      (% style="color:red" %)**None**
++
++* Flow Control: (% style="color:red" %)**None**
++
++Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
++
  [[image:image-20221021110817-7.png]]
  CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
--**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]]
++(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
--=== **2.2.4  Use CoAP protocol to uplink data** ===
--**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/]]
--**Use below commands:**
++=== 2.2.4  Use CoAP protocol to uplink data ===
--* **AT+PRO=1**                                               ~/~/ Set to use CoAP protocol to uplink
--* **AT+SERVADDR=120.24.4.116,5683   **  ~/~/ to set CoAP server address and port
--* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" **       ~/~/Set COAP resource path
++(% 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/]]
++
++
++(% style="color:blue" %)**Use below commands in CPN01:**
++
++* (% style="color:#037691" %)**AT+PRO=1**                (%%)                                ~/~/ Set to use CoAP protocol to uplink
++
++* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)   ~/~/ Set CoAP server address and port
++
++* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" **   (%%)                    ~/~/  Set CoAP resource path
++
  For parameter description, please refer to AT command set
  [[image:image-20221021110948-8.png]]
--After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server.
++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.
++
  [[image:image-20221021110956-9.png]]
--=== **2.2.5  Use UDP protocol to uplink data(Default protocol)** ===
--This feature is supported since firmware version v1.0.1
--* **AT+PRO=2   **  ~/~/ Set to use UDP protocol to uplink
--* **AT+SERVADDR=120.24.4.116,5601   **   ~/~/ to set UDP server address and port
--* **AT+CFM=1       **    ~/~/If the server does not respond, this command is unnecessary
++=== 2.2.5  Use UDP protocol to uplink data(Default protocol) ===
++
++(% style="color:blue" %)**AT Commands:**
++
++* (% style="color:#037691" %)**AT+PRO=2   **  (%%) ~/~/  Set to use UDP protocol to uplink
++
++* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%)  ~/~/  Set UDP server address and port
++
++* (% style="color:#037691" %)**AT+CFM=1       **  (%%)  ~/~/  If the server does not respond, this command is unnecessary
++
   [[image:image-20221021111025-10.png]]
++
  [[image:image-20221021111033-11.png||height="241" width="576"]]
--=== **2.2.6  Use MQTT protocol to uplink data** ===
--This feature is supported since firmware version v110
++=== 2.2.6  Use MQTT protocol to uplink data ===
--* **AT+PRO=3   **                                              ~/~/Set to use MQTT protocol to uplink
--* **AT+SERVADDR=120.24.4.116,1883   **      ~/~/Set MQTT server address and port
--* **AT+CLIENT=CLIENT       **                           ~/~/Set up the CLIENT of MQTT
--* **AT+UNAME=UNAME                               **~/~/Set the username of MQTT
--* **AT+PWD=PWD                                        **~/~/Set the password of MQTT
--* **AT+PUBTOPIC=NSE01_PUB                    **~/~/Set the sending topic of MQTT
--* **AT+SUBTOPIC=NSE01_SUB          **          ~/~/Set the subscription topic of MQTT
++(% style="color:blue" %)**AT Commands:**
++
++* (% style="color:#037691" %)**AT+PRO=3   **                (%%)                              ~/~/  Set to use MQTT protocol to uplink
++
++* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   **  (%%)    ~/~/  Set MQTT server address and port
++
++* (% style="color:#037691" %)**AT+CLIENT=CLIENT       **          (%%)                 ~/~/  Set up the CLIENT of MQTT
++
++* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)**          **~/~/  Set the username of MQTT
++
++* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)**               **~/~/  Set the password of MQTT
++
++* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)**      **~/~/  Set the sending topic of MQTT
++
++* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          **   (%%)       ~/~/  Set the subscription topic of MQTT
++
   [[image:image-20221021111058-12.png]]
--[[image:image-20221021111108-13.png]]
++[[image:image-20221021111201-16.png||height="472" width="653"]]
++
--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.
++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.
--=== **2.2.7  Use TCP protocol to uplink data** ===
--This feature is supported since firmware version v110
--* **AT+PRO=4   **                                           ~/~/ Set to use TCP protocol to uplink
--* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ to set TCP server address and port
++=== 2.2.7  Use TCP protocol to uplink data ===
++
++(% style="color:blue" %)**AT Commands:**
++
++* (% style="color:#037691" %)**AT+PRO=4   **                          (%%)                  ~/~/  Set to use TCP protocol to uplink
++
++* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   **   (%%) ~/~/  Set TCP server address and port
++
   [[image:image-20221021111125-14.png]]
  [[image:image-20221021111131-15.png]]
@@ -241,85 +241,105 @@
--=== **2.2.8  Change Update Interval** ===
--User can use below command to change the **uplink interval**.
++=== 2.2.8  Change Update Interval ===
--* **AT+TDC=600      **  ~/~/ Set Update Interval to 600s
--**NOTE:**
++User can use below command to change the (% style="color:blue" %)**uplink interval**.
--**~1. By default, the device will send an uplink message every 1 hour.**
++* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
--== **2.3  Uplink Payload** ==
++(% style="color:red" %)**NOTE:**
--In this mode, uplink payload includes 87 bytes in total by default.
++1.  By default, the device will send an uplink message every 1 hour.
++
++
++== 2.3  Uplink Payload ==
++
++
++The uplink payload includes 123 bytes in total by default.
++
  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.
--|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**2**|**2**|4
--|**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
--|2|2|4|8 group
--|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|...
++(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:510px" %)
++|=(% 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**
++|=(% 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"]]
++(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:510px" %)
++|(% 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**
++|(% 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" %)...
++
  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
  [[image:image-20221021111201-16.png||height="572" width="792"]]
++
  The payload is ASCII string, representative same HEX:
--**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 //(%%)**
++**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" %)__09__(% style="color:#663300" %) __02__ (% style="color:#d60093" %)__6315537b__ (% style="color:#660066" %)__01 00000b 02 0000026 63510fed__ (%%)__0100000e0200000263510f39__ __010000000000000063510e85__ __010000000000000063510d2e__ __010000000000000063510c7a__ __010000000000000063510bc6__ __010000000000000063510954__ __010000000000000063510882 __**
--where:
--*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
++**where:**
--*(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
++* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
--*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
++* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
--*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
++* (% style="color:#037691" %)**BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
--*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
++* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
--*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00= 0
++* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
--*(% style="color:#037691" %) **Contact Status:**(%%) 0x00= 0
++* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
--*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0
++* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
--*(% style="color:#037691" %) **Total pulse:0x09 =0**
++* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
--*(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2
++* (% style="color:#037691" %)**Total pulse: **(%%)0x09 =0
--*(% style="color:#037691" %)**Time stamp :**(%%) 0x6315537b =1662342011
++* (% style="color:#037691" %)**The last open duration: **(%%)0x02 =2
--*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000b0200002663510fed
++* (% style="color:#037691" %)** Time stamp :**(%%) 0x6315537b =1662342011 (Unix Time)
--*(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
++* (% style="color:#037691" %)**Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 01  00000b  02  000026  63510fed
--== **2.4  Payload Explanation and Sensor Interface** ==
++* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
--=== **2.4.1  Device ID** ===
--By default, the Device ID equal to the last 15 bits of IMEI.
--User can use **AT+DEUI** to set Device ID
++== 2.4  Payload Explanation and Sensor Interface ==
++
++=== 2.4.1  Device ID ===
++
++
++By default, the Device ID is equal to the last 15 bits of IMEI.
++
++User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
++
  **Example:**
  AT+DEUI=868411056754138
--The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
++The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
--=== **2.4.2  Version Info** ===
--Specify the software version: 0x64=100, means firmware version 1.00.
--For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0.
++=== 2.4.2  Version Info ===
--=== **2.4.3  Battery Info** ===
++Specify the software version: 0x64=100, which means firmware version 1.00.
++
++For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
++
++
++
++=== 2.4.3  Battery Info ===
++
++
  Check the battery voltage for CPN01.
  Ex1: 0x0B45 = 2885mV
@@ -326,8 +326,11 @@
  Ex2: 0x0B49 = 2889mV
--=== **2.4.4  Signal Strength** ===
++
++=== 2.4.4  Signal Strength ===
++
++
  NB-IoT Network signal Strength.
  **Ex1: 0x1d = 29**
@@ -342,10 +342,13 @@
  **99**      Not known or not detectable
--=== **2.4.5 Calculate Flag** ===
--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.
++=== 2.4.5  Calculate Flag ===
++
++
++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.
++
  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.
  Default value: 0.
@@ -352,24 +352,36 @@
  Range (6 bits): (b)000000 ~~ (b) 111111
--=== **2.4.6   Alarm** ===
--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]]
--=== **2.4.7 Contact Status** ===
++=== 2.4.6  Alarm ===
++
++See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
++
++
++
++=== 2.4.7  Contact Status ===
++
++
 : Open
 : Close
--=== **2.4.8 Total pulse** ===
--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]]
++=== 2.4.8  Total pulse ===
++
++
++Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
++
  Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
--=== **2.4.9 The last open duration** ===
++
++=== 2.4.9  The last open duration ===
++
++
  Dry Contact last open duration.
  Unit: min.
@@ -377,23 +377,28 @@
  [[image:image-20221021111346-17.png||height="146" width="770"]]
--=== **2.4.10  Timestamp** ===
--Time stamp : 0x6315537b =1662342011
++=== 2.4.10  Timestamp ===
++
++Timestamp : 0x6315537b =1662342011
++
  Convert Unix timestamp to time 2022-9-5 9:40:11.
  **~ **
--== **2.5  Downlink Payload** ==
++== 2.5  Downlink Payload ==
++
++
  By default, CPN01 prints the downlink payload to console port.
  [[image:image-20221021111414-18.png]]
++
  **Examples:**
--* **Set TDC**
++* (% style="color:#037691" %)**Set TDC**
  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
@@ -401,36 +401,41 @@
  Payload:    01 00 00 3C    TDC=60S
--* **Reset**
++* (% style="color:#037691" %)**Reset**
  If payload = 0x04FF, it will reset the NSE01
--* **INTMOD**
++* (% style="color:#037691" %)**INTMOD**
  Downlink Payload: 06000003, Set AT+INTMOD=3
--== **2.6  LED Indicator** ==
--The CPN01 has an internal LED which is to show the status of different state.
--* 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)
--* Then the LED will be on for 1 second means device is boot normally.
++== 2.6  LED Indicator ==
++
++
++The CPN01 has an internal LED which is to show the status of different states.
++
++* When the device starts normally, the LED will light up for 1 second.
  * After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
  * For each uplink probe, LED will be on for 500ms.
--== **2.7  Alarm Base on Timeout** ==
--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:
++== 2.7  Alarm Base on Timeout ==
--**~1. Keep Status: Status to be monitor**
++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:
++
++
++(% style="color:blue" %)**1. Keep Status: Status to be monitor**
++
  Keep Status = 1: Monitor Close to Open event
  Keep Status = 0: Monitor Open to Close event
--**2. Keep Time: Timeout to send an Alarm**
++(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
  Range 0 ~~ 65535(0xFFFF) seconds.
@@ -439,123 +439,164 @@
  If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
--**AT Command** to configure:
++(% style="color:blue" %)**AT Command to configure:**
--**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.
++(% style="color:#037691" %)**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.
--**AT+TTIG=0,0 **      ~-~-> Default Value, disable timeout Alarm.
++(% style="color:#037691" %)**AT+TTRIG=0,0 **  (%%)    **~-~->** Default Value, disable timeout Alarm.
--== **2.8 Set debug mode** ==
--Feature: Enable or Disable debug mode
++== 2.8  Set debug mode ==
--**AT Command: AT+DEBUG**
++Feature: Enable or Disable debug mode
++
++(% style="color:blue" %)**AT Command: AT+DEBUG**
++
  [[image:image-20221021111629-21.png]]
--== **2.9 Clear Flash Record** ==
++
++== 2.9  Clear Flash Record ==
++
++
  Feature: Clear flash storage for data log feature.
--**AT Command: AT+CLRDTA**
++(% style="color:blue" %)**AT Command: AT+CLRDTA**
  [[image:image-20221021111527-19.png]]
--== ** 2.10 Set trigger mode** ==
--➢ AT Command: **AT+TTRMOD**
++== 2.10  Set trigger mode ==
++
++
++(% style="color:blue" %)**AT Command: AT+TTRMOD**
++
  Feature: Set the trigger interrupt mode.
  [[image:image-20221021111552-20.png]]
--== **2.11 Set the calculate flag** ==
++
++== 2.11  Set the calculate flag ==
++
++
  Feature: Set the calculate flag
--**AT Command: AT+CALCFLAG**
++(% style="color:blue" %)**AT Command: AT+CALCFLAG**
  [[image:image-20221021111711-22.png]]
--== **2.12  Set count number** ==
++
++== 2.12  Set count number ==
++
++
  Feature: Manually set the count number
--**AT Command: AT+SETCNT**
++(% style="color:blue" %)**AT Command: AT+SETCNT**
  [[image:image-20221021111748-24.png]]
--== **2.13 Set the number of data to be uploaded and the recording time** ==
--➢ AT Command:
--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)
++== 2.13  Set the number of data to be uploaded and the recording time ==
--AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
++(% style="color:blue" %)**AT Command:**
--== **2.14 Read or Clear cached data** ==
++(% style="color:#037691" %)**AT+TR=900**        (%%)~/~/  The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
--➢ AT Command:
++(% style="color:#037691" %)**AT+NOUD=8 **     (%%)~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
--AT+CDP    ~/~/ Read cached data
++
++== 2.14  Read or Clear cached data ==
++
++
++(% style="color:blue" %)**AT Command:**
++
++(% style="color:#037691" %)**AT+CDP**  (%%)       ~/~/ Read cached data
++
++(% style="color:#037691" %)**AT+CDP=0**  (%%)  ~/~/ Clear cached data
++
  [[image:image-20221021111810-25.png||height="364" width="797"]]
--AT+CDP=0    ~/~/ Clear cached data
--== **2.15  Firmware Change Log** ==
++== 2.15  Firmware Change Log ==
--Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
--Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
++Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
--== **2.16  Battery Analysis** ==
++Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
--=== **2.16.1  Battery Type** ===
--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.
--The battery is designed to last for several years depends on the actually use environment and update interval.
++== 2.16  Battery Analysis ==
--The battery related documents as below:
++=== 2.16.1  Battery Type ===
++
++
++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.
++
++The battery is designed to last for several years depends on the actual use environment and update interval.
++
++The battery-related documents as below:
++
  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
++
  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
++
  * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
  [[image:image-20221021111911-26.png]]
--=== **2.16.2  Power consumption Analyze** ===
++
++=== 2.16.2  Power consumption Analyze ===
++
++
  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.
  Instruction to use as below:
--**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/]]
++(% 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/]]
--**Step 2: ** Open it and choose
++(% style="color:blue" %)**Step 2: **(%%) Open it and choose
  * Product Model
++
  * Uplink Interval
++
  * Working Mode
  And the Life expectation in difference case will be shown on the right.
--[[image:image-20221021111923-27.png||height="253" width="783"]]
++[[image:1666596205057-567.png]]
--=== **2.16.3  Battery Note** ===
++
++=== 2.16.3  Battery Note ===
++
++
  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.
--=== **2.16.4  Replace the battery** ===
++
++=== 2.16.4  Replace the battery ===
++
++
  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).
--= **3.  Access NB-IoT Module** =
++
++= 3.  Access NB-IoT Module =
++
++
  Users can directly access the AT command set of the NB-IoT module.
  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/]]
@@ -562,10 +562,14 @@
  [[image:image-20221021112006-28.png]]
--= **4.  Using the AT Commands** =
--== **4.1  Access AT Commands** ==
++= 4.  Using the AT Commands =
++
++
++== 4.1  Access AT Commands ==
++
++
  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]]
  AT+<CMD>?                    : Help on <CMD>
@@ -576,8 +576,9 @@
  AT+<CMD>=?                  : Get the value
--**General Commands**
++(% style="color:blue" %)**General Commands**
++
  AT                            : Attention
  AT?                           : Short Help
@@ -600,15 +600,12 @@
  AT+SERVADDR          : Server Address
--AT+TR      : Get or Set record time"
++AT+TR      :       Get or Set record time
--
  AT+NOUD      : Get or Set the number of data to be uploaded
++AT+CDP     :   Read or Clear cached data
--AT+CDP     : Read or Clear cached data
--
--
  AT+ DEBUG   : Enable or Disable debug mode
  AT+ TTRIG   : Get or Set Alarm Base on Timeout
@@ -619,16 +619,19 @@
  AT+ CLRC   : Clear current door open count
--**COAP Management**
++(% style="color:blue" %)**COAP Management**
++
  AT+URI            : Resource parameters
--**UDP Management**
++(% style="color:blue" %)**UDP Management**
++
  AT+CFM          : Upload confirmation mode (only valid for UDP)
--**MQTT Management**
++(% style="color:blue" %)**MQTT Management**
++
  AT+CLIENT               : Get or Set MQTT client
  AT+UNAME             : Get or Set MQTT Username
@@ -639,86 +639,73 @@
  AT+SUBTOPIC          : Get or Set MQTT subscription topic
--**Information**
++(% style="color:blue" %)**Information**
++
  AT+FDR              : Factory Data Reset
  AT+PWORD       : Serial Access Password
--= **5.  FAQ** =
--== **5.1  How to Upgrade Firmware** ==
--User can upgrade the firmware for 1) bug fix, 2) new feature release.
++= 5.  FAQ =
--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]]
--**Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.**
++== 5.1  How to Upgrade Firmware ==
--== **5.2  Can I calibrate CPN01 to different soil types?** ==
--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]].
++User can upgrade the firmware for 1) bug fix, 2) new feature release.
--= **6.  Trouble Shooting** =
++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]]
--== **6.1  Connection problem when uploading firmware** ==
++(% style="color:red" %)**Notice: **(% style="color:blue" %)**CPN01** (%%)**and (% style="color:blue" %)CPL01(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
--**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]]
--== **6.2  AT Command input doesn't work** ==
--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.
++= 6.  Trouble Shooting =
--= **7.  Order Info** =
--Part Number**:** CPN01
++== 6.1  Connection problem when uploading firmware ==
--= **8.  Packing Info** =
--**Package Includes**:
++(% 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]]
--* CPN01 NB-IoT Soil Moisture & EC Sensor x 1
--* External antenna x 1
--**Dimension and weight**:
--* Size: 195 x 125 x 55 mm
--* Weight:   420g
++== 6.2  AT Command input doesn't work ==
--= **9.  Support** =
--* 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.
--* 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]]
++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.
--
++= 7.  Order Info =
++Part Number**:** CPN01
++= 8.  Packing Info =
++(% style="color:blue" %)**Package Includes**:
++* CPN01 Open/Close Sensor x 1
++* External antenna x 1
++(% style="color:blue" %)**Dimension and weight**:
++* Size: 195 x 125 x 55 mm
++* Weight:   420g
++= 9.  Support =
++* 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.
++* 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]]
--
--
--
--
--
--
--
--
--
--
--
--
++

1666596205057-567.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+179.8 KB

Content

Changes for page NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual

Summary

Details

Applications

Navigation