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:
Uploaded new attachment "image-20221117114937-4.png", version {1}
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 8 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - CPN01-NB-IoTOutdoor Open/Close DryContactSensor User Manual1 +NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.Xiaoling - Content
-
... ... @@ -1,28 +1,63 @@ 1 1 (% style="text-align:center" %) 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"]]2 +[[image:image-20221117105556-1.png]] 3 3 4 -{{toc/}} 5 5 6 -= **1. Introduction** = 7 7 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 Nb-IoT network. User can see the 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. 13 13 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 - CPN01 is designedfor outdoor use. It has a weatherproofenclosure and industrial-level battery to work inlowto high temperatures.10 +**Table of Contents:** 17 17 18 -NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage. 19 -\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements. 20 -\\CPN01 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 21 -\\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. 22 22 13 + 14 + 15 + 16 += 1. Introduction = 17 + 18 + 19 +== 1.1 What is NDS03A NB-IoT Open/Close Door Sensor == 20 + 21 + 22 +((( 23 +The Dragino NDS03A is an (% style="color:blue" %)**Open/Close NB-IoT Door Sensor**(%%). It detects door (% style="color:blue" %)**open/close status**(%%) and (% style="color:blue" %)**uplinks**(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server. 24 +))) 25 + 26 +((( 27 +The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically. 28 +))) 29 + 30 +((( 31 +NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT. 32 +))) 33 + 34 +((( 35 +NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time. 36 +))) 37 + 38 +((( 39 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures. 40 +))) 41 + 42 +((( 43 +NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technologyTCP, MQTT, UDP, and CoAP**(%%) for different application requirements. 44 +))) 45 + 46 +((( 47 +NDS03A is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 48 +))) 49 + 50 +((( 51 +To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection. 52 +))) 53 + 54 + 23 23 24 -== **1.2 Features** == 25 25 57 + 58 +== 1.2 Features == 59 + 60 + 26 26 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 27 27 * Open/Close detect 28 28 * Open/Close statistics ... ... @@ -38,14 +38,15 @@ 38 38 * Micro SIM card slot for NB-IoT SIM 39 39 * 8500mAh Battery for long-term use 40 40 41 -== **1.3 Specification**==76 +== 1.3 Specification == 42 42 43 -**Common DC Characteristics:** 44 44 79 +(% style="color:blue" %)**Common DC Characteristics:** 80 + 45 45 * Supply Voltage: 2.1v ~~ 3.6v 46 46 * Operating Temperature: -40 ~~ 85°C 47 47 48 -**NB-IoT Spec:** 84 +(% style="color:blue" %)**NB-IoT Spec:** 49 49 50 50 * - B1 @H-FDD: 2100MHz 51 51 * - B3 @H-FDD: 1800MHz ... ... @@ -54,180 +54,243 @@ 54 54 * - B20 @H-FDD: 800MHz 55 55 * - B28 @H-FDD: 700MHz 56 56 57 -== **1.4 Installation**==93 +== 1.4 Installation == 58 58 59 -Connect CPL01 to an Open Close sensor like below. So it can detect the open/close event. 60 60 96 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event. 97 + 61 61 [[image:image-20221021110329-1.png]] 62 62 63 -[[image:image-20221021110340-2.png]] 64 64 65 - == **1.5 Applications**==101 +[[image:image-20221022234602-2.png||height="288" width="922"]] 66 66 103 + 104 + 105 +== 1.5 Applications == 106 + 107 + 67 67 * Open/Close Detection 68 68 * Pulse meter application 69 69 * Dry Contact Detection 70 70 71 -== **1.6 Mechanical**==112 +== 1.6 Mechanical == 72 72 114 + 73 73 [[image:image-20221021110415-3.png]] 74 74 75 -== ** 1.7 Pin Definitions and Switch** == 76 76 118 + 119 +== 1.7 Pin Definitions and Switch == 120 + 121 + 77 77 [[image:image-20221021110429-4.png]] 78 78 79 -=== **1.7.1 Pin Definition** === 80 80 81 - CPL01 ispre-configured to connect to two external wires. The other pins are not used. If user wantsto 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]]125 +=== 1.7.1 Pin Definition === 82 82 83 -=== **1.7.2 Jumper JP2(Power ON/OFF)** === 84 84 128 +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]]**. 85 85 130 + 131 + 132 +=== 1.7.2 Jumper JP2(Power ON/OFF) === 133 + 134 + 86 86 Power on Device when putting this jumper. 87 87 88 88 89 89 90 -=== **1.7.3 BOOT MODE / SW1**===139 +=== 1.7.3 BOOT MODE / SW1 === 91 91 92 92 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.142 +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. 94 94 95 -2) Flash: work mode, the device starts to work and send out console output for further debug 144 +2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging. 96 96 97 97 98 98 99 -=== **1.7.4 Reset Button**===148 +=== 1.7.4 Reset Button === 100 100 101 101 102 102 Press to reboot the device. 103 103 104 -== == 105 105 106 -=== **1.7.5 LED** === 107 107 155 +=== 1.7.5 LED === 108 108 109 -It will flash: 110 110 111 -1. Boot the device in flash mode 112 -1. Send an uplink packet 158 +The LED will blink when : 113 113 114 - = **2.UseCPN01tocommunicatewithIoT Server** =160 +1. Boot the device in flash mode 115 115 116 - == **2.1Howitworks**==162 +2. Send an uplink packet 117 117 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. 119 119 120 -The diagram below shows the working flow in default firmware of CPN01: 121 121 166 += 2. Use CPN01 to communicate with IoT Server = 167 + 168 + 169 +== 2.1 How it works == 170 + 171 + 172 +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. 173 + 174 +The diagram below shows the working flow in the default firmware of CPN01: 175 + 122 122 [[image:image-20221021110615-5.png]] 123 123 124 -== **2.2 Configure the CPN01** == 125 125 126 -=== **2.2.1 Test Requirement** === 127 127 128 - Touse CPN01in your city, make sure meet below requirements:180 +== 2.2 Configure CPN01 == 129 129 130 -* Your local operator has already distributed a NB-IoT Network there. 182 + 183 +=== 2.2.1 Test Requirement === 184 + 185 + 186 +To use CPN01 in your city, make sure to meet below requirements: 187 + 188 +* Your local operator has already distributed an NB-IoT Network. 131 131 * The local NB-IoT network used the band that CPN01 supports. 132 132 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 133 133 134 -Below figure shows our testing structure. 192 +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. 135 135 194 +[[image:image-20221023000439-3.png]] 195 + 136 136 137 137 138 -=== **2.2.2 Insert SIM card** === 139 139 199 +=== 2.2.2 Insert NB-IoT SIM card === 200 + 201 + 140 140 Insert the NB-IoT Card get from your provider. 141 141 142 -User need to take out the NB-IoT module and insert the SIM card like below: 204 +User needs to take out the NB-IoT module and insert the SIM card like below: 143 143 144 144 [[image:image-20221021110745-6.png]] 145 145 146 -=== **2.2.3 Connect USB – TTL to CPN01 to configure it** === 147 147 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. 149 149 150 - **Connection:**210 +=== 2.2.3 Connect USB – TTL to CPN01 and configure it === 151 151 152 - USB TTL GND <~-~-~-~-> GND 153 153 154 - USB TTL TXD<~-~-~-~->UART_RXD213 +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. 155 155 156 - USBTTL RXD <~-~-~-~-> UART_TXD215 +(% style="color:blue" %)**Connection:** 157 157 217 +(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND** 218 + 219 +(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD** 220 + 221 +(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD** 222 + 223 + 158 158 In the PC, use below serial tool settings: 159 159 160 -* Baud: **9600** 161 -* Data bits:** 8** 162 -* Stop bits: **1** 163 -* Parity: **None** 164 -* Flow Control: **None** 226 +* Baud: (% style="color:red" %)**9600** 165 165 166 - Makesuretheswitch isin FLASH position, then power on device byconnecting the jumper on CPN01. CPN01 will output system info once power on as below, we can enterthe **password:12345678**to access AT Command input.228 +* Data bits:** (% style="color:red" %)8(%%)** 167 167 230 +* Stop bits: (% style="color:red" %)**1** 231 + 232 +* Parity: (% style="color:red" %)**None** 233 + 234 +* Flow Control: (% style="color:red" %)**None** 235 + 236 +Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%). 237 + 168 168 [[image:image-20221021110817-7.png]] 169 169 170 - **Note:thevalidAT Commands canbefoundat:**[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]240 +CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input. 171 171 172 -=== **2.2.4 Use CoAP protocol to uplink data** === 173 173 174 -**Note: if you don'taveCoAP server,youcanrefer thislinkto setupone: **[[**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/]]243 +(% 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]] 175 175 176 -**Use below commands:** 177 177 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 181 181 247 +=== 2.2.4 Use CoAP protocol to uplink data === 248 + 249 + 250 +(% 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/]] 251 + 252 + 253 +(% style="color:blue" %)**Use below commands in CPN01:** 254 + 255 +* (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 256 + 257 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ Set CoAP server address and port 258 + 259 +* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/ Set CoAP resource path 260 + 182 182 For parameter description, please refer to AT command set 183 183 184 184 [[image:image-20221021110948-8.png]] 185 185 186 -After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server. 187 187 266 +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. 267 + 188 188 [[image:image-20221021110956-9.png]] 189 189 190 -=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** === 191 191 192 -This feature is supported since firmware version v1.0.1 193 193 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 272 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 197 197 274 + 275 +(% style="color:blue" %)**AT Commands:** 276 + 277 +* (% style="color:#037691" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 278 + 279 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ Set UDP server address and port 280 + 281 +* (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 282 + 198 198 [[image:image-20221021111025-10.png]] 199 199 285 + 200 200 [[image:image-20221021111033-11.png||height="241" width="576"]] 201 201 202 202 203 203 204 -=== **2.2.6 Use MQTT protocol to uplink data** === 205 205 206 - Thisfeatureissupported sincefirmwareversionv110291 +=== 2.2.6 Use MQTT protocol to uplink data === 207 207 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 215 215 294 +(% style="color:blue" %)**AT Commands:** 295 + 296 +* (% style="color:#037691" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 297 + 298 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 299 + 300 +* (% style="color:#037691" %)**AT+CLIENT=CLIENT ** (%%) ~/~/ Set up the CLIENT of MQTT 301 + 302 +* (% style="color:#037691" %)**AT+UNAME=UNAME **(%%)** **~/~/ Set the username of MQTT 303 + 304 +* (% style="color:#037691" %)**AT+PWD=PWD **(%%)** **~/~/ Set the password of MQTT 305 + 306 +* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB **(%%)** **~/~/ Set the sending topic of MQTT 307 + 308 +* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB ** (%%) ~/~/ Set the subscription topic of MQTT 309 + 216 216 [[image:image-20221021111058-12.png]] 217 217 218 -[[image:image-20221021111108-13.png]] 219 219 313 +[[image:image-20221021111201-16.png||height="472" width="653"]] 314 + 220 220 221 221 222 -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.317 +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. 223 223 224 -=== **2.2.7 Use TCP protocol to uplink data** === 225 225 226 -This feature is supported since firmware version v110 227 227 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 321 +=== 2.2.7 Use TCP protocol to uplink data === 230 230 323 + 324 +(% style="color:blue" %)**AT Commands:** 325 + 326 +* (% style="color:#037691" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 327 + 328 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ Set TCP server address and port 329 + 231 231 [[image:image-20221021111125-14.png]] 232 232 233 233 [[image:image-20221021111131-15.png]] ... ... @@ -234,85 +234,103 @@ 234 234 235 235 236 236 237 -=== **2.2.8 Change Update Interval** === 238 238 239 - Usercanusebelow command to change the**uplink interval**.337 +=== 2.2.8 Change Update Interval === 240 240 241 -* **AT+TDC=600 ** ~/~/ Set Update Interval to 600s 242 242 243 -** NOTE:**340 +User can use below command to change the (% style="color:blue" %)**uplink interval**. 244 244 245 -* *~1.Bydefault, thedevice willsendanuplinkmessage every1hour.**342 +* (% style="color:#037691" %)**AT+TDC=7200 ** (%%) ~/~/ Set Update Interval to 7200s (2 hours) 246 246 247 - ==**2.3 Uplink Payload**==344 +(% style="color:red" %)**NOTE:** 248 248 249 - Inthismode,uplinkpayloadincludes87bytes intotalbydefault.346 +1. By default, the device will send an uplink message every 1 hour. 250 250 348 + 349 + 350 +== 2.3 Uplink Payload == 351 + 352 + 353 +The uplink payload includes 123 bytes in total by default. 354 + 251 251 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. 252 252 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 255 255 256 -|2|2|4|8 group 257 -|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|... 358 +(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %) 359 +|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:60px" %)**3** 360 +|=(% style="width: 96px;" %)**Value**|(% style="width:84px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:44px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:121px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:52px" %)MOD|(% style="width:84px" %)[[ Calculate Flag>>||anchor="H2.4.5A0CalculateFlag"]]|(% style="width:116px" %)[[Contact Status>>||anchor="H2.4.7A0ContactStatus"]]|(% style="width:57px" %)[[Alarm>>||anchor="H2.4.6A0Alarm"]]|(% style="width:91px" %)[[Total pulse>>||anchor="H2.4.8A0Totalpulse"]] 258 258 362 +(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %) 363 +|(% style="width:100px" %)**3**|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:100px" %)**3**|(% style="width:80px" %)4|(% style="width:50px" %)**8 group** 364 +|(% 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" %)... 365 + 259 259 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data. 260 260 261 261 [[image:image-20221021111201-16.png||height="572" width="792"]] 262 262 370 + 263 263 The payload is ASCII string, representative same HEX: 264 264 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__20b0" %)____00____(% style="color:#420042" %)000009____(% style="color:#663300" %)__(% style="color:#d60093" %)6315537bb____(% style="color:#663300" %)//0100000b02000002663510fed__//(%%)**373 +**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 00000b 02 0000026 63510fed__ (%%)__0100000e0200000263510f39__ __010000000000000063510e85__ __010000000000000063510d2e__ __010000000000000063510c7a__ __010000000000000063510bc6__ __010000000000000063510954__ __010000000000000063510882 __** 266 266 267 -where: 268 -*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317 375 +**where:** 269 269 270 -*(% style="color:#037691" %) Version:**(%%) 0x0064=100=1.0.0377 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317 271 271 272 -*(% style="color:#037691" %) BAT:**(%%) 0x0c78=3192 mV=3.192V379 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 273 273 274 -*(% style="color:#037691" %) Singal:**(%%)0x17 = 23381 +* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V 275 275 276 -*(% style="color:#037691" %) Mod:**(%%)01 =1383 +* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23 277 277 278 -*(% style="color:#037691" %) Calculate Flag:**(%%) 0x00=0385 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 279 279 280 -*(% style="color:#037691" %) ontactStatus:**(%%) 0x00=387 +* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0 281 281 282 -*(% style="color:#037691" %) Alarm:**(%%)0x00389 +* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0 283 283 284 -*(% style="color:#037691" %) Totalpulse:0x09=0**391 +* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0 285 285 286 -*(% style="color:#037691" %) he lastopen duration:**(%%)0x02=2393 +* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9 287 287 288 -*(% style="color:#037691" %)**T ime stamp :**(%%)6315537b=1662342011395 +* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2 289 289 290 -*(% style="color:#037691" %) Contact Status,Total pulse, Calculate Flag, The last open duration ,Time00000b0200002663510fed397 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time) 291 291 292 -*(% style="color:#037691" %) 8 sets of recorded data:Contact Status, Total pulse,Calculate Flag,The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......399 +* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01 00000b 000026 63510fed 293 293 294 -= =**2.4PayloadExplanationndSensorInterface**==401 +* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,....... 295 295 296 -== =**2.4.1Device ID**===403 +== 2.4 Payload Explanation and Sensor Interface == 297 297 298 -By default, the Device ID equal to the last 15 bits of IMEI. 299 299 300 - Usercan use **AT+DEUI** to set Device ID406 +=== 2.4.1 Device ID === 301 301 408 + 409 +By default, the Device ID is equal to the last 15 bits of IMEI. 410 + 411 +User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID 412 + 302 302 **Example:** 303 303 304 304 AT+DEUI=868411056754138 305 305 306 -The Device ID is stored in a non e-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.417 +The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID. 307 307 308 -=== **2.4.2 Version Info** === 309 309 310 -Specify the software version: 0x64=100, means firmware version 1.00. 311 311 312 - Forexample: 0x00 64: this device is CPN01 with firmware version1.0.0.421 +=== 2.4.2 Version Info === 313 313 314 -=== **2.4.3 Battery Info** === 315 315 424 +Specify the software version: 0x64=100, which means firmware version 1.00. 425 + 426 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0. 427 + 428 + 429 + 430 +=== 2.4.3 Battery Info === 431 + 432 + 316 316 Check the battery voltage for CPN01. 317 317 318 318 Ex1: 0x0B45 = 2885mV ... ... @@ -319,8 +319,11 @@ 319 319 320 320 Ex2: 0x0B49 = 2889mV 321 321 322 -=== **2.4.4 Signal Strength** === 323 323 440 + 441 +=== 2.4.4 Signal Strength === 442 + 443 + 324 324 NB-IoT Network signal Strength. 325 325 326 326 **Ex1: 0x1d = 29** ... ... @@ -335,10 +335,13 @@ 335 335 336 336 **99** Not known or not detectable 337 337 338 -=== **2.4.5 Calculate Flag** === 339 339 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. 341 341 460 +=== 2.4.5 Calculate Flag === 461 + 462 + 463 +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. 464 + 342 342 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. 343 343 344 344 Default value: 0. ... ... @@ -345,24 +345,36 @@ 345 345 346 346 Range (6 bits): (b)000000 ~~ (b) 111111 347 347 348 -=== **2.4.6 Alarm** === 349 349 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]] 351 351 352 -=== **2.4.7ContactStatus**===473 +=== 2.4.6 Alarm === 353 353 475 + 476 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]] 477 + 478 + 479 + 480 +=== 2.4.7 Contact Status === 481 + 482 + 354 354 0: Open 355 355 356 356 1: Close 357 357 358 -=== **2.4.8 Total pulse** === 359 359 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]] 361 361 489 +=== 2.4.8 Total pulse === 490 + 491 + 492 +Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]] 493 + 362 362 Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215 363 363 364 -=== **2.4.9 The last open duration** === 365 365 497 + 498 +=== 2.4.9 The last open duration === 499 + 500 + 366 366 Dry Contact last open duration. 367 367 368 368 Unit: min. ... ... @@ -370,23 +370,28 @@ 370 370 [[image:image-20221021111346-17.png||height="146" width="770"]] 371 371 372 372 373 -=== **2.4.10 Timestamp** === 374 374 375 -Time : 0x6315537b=1662342011509 +=== 2.4.10 Timestamp === 376 376 511 + 512 +Timestamp : 0x6315537b =1662342011 513 + 377 377 Convert Unix timestamp to time 2022-9-5 9:40:11. 378 378 379 379 **~ ** 380 380 381 -== **2.5 Downlink Payload** == 382 382 519 +== 2.5 Downlink Payload == 520 + 521 + 383 383 By default, CPN01 prints the downlink payload to console port. 384 384 385 385 [[image:image-20221021111414-18.png]] 386 386 526 + 387 387 **Examples:** 388 388 389 -* **Set TDC** 529 +* (% style="color:#037691" %)**Set TDC** 390 390 391 391 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 392 392 ... ... @@ -394,36 +394,39 @@ 394 394 395 395 Payload: 01 00 00 3C TDC=60S 396 396 397 -* **Reset** 537 +* (% style="color:#037691" %)**Reset** 398 398 399 399 If payload = 0x04FF, it will reset the NSE01 400 400 401 -* **INTMOD** 541 +* (% style="color:#037691" %)**INTMOD** 402 402 403 403 Downlink Payload: 06000003, Set AT+INTMOD=3 404 404 405 -== **2.6 LED Indicator** == 406 406 407 -The CPN01 has an internal LED which is to show the status of different state. 408 408 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. 547 +== 2.6 LED Indicator == 548 + 549 + 550 +The CPN01 has an internal LED which is to show the status of different states. 551 + 552 +* When the device starts normally, the LED will light up for 1 second. 411 411 * After CPN01 join NB-IoT network. The LED will be ON for 3 seconds. 412 412 * For each uplink probe, LED will be on for 500ms. 413 413 414 -== **2.7 Alarm Base on Timeout**==556 +== 2.7 Alarm Base on Timeout == 415 415 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: 417 417 559 +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 -**~1. Keep Status: Status to be monitor** 420 420 562 +(% style="color:blue" %)**1. Keep Status: Status to be monitor** 563 + 421 421 Keep Status = 1: Monitor Close to Open event 422 422 423 423 Keep Status = 0: Monitor Open to Close event 424 424 425 425 426 -**2. Keep Time: Timeout to send an Alarm** 569 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm** 427 427 428 428 Range 0 ~~ 65535(0xFFFF) seconds. 429 429 ... ... @@ -432,123 +432,164 @@ 432 432 If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout. 433 433 434 434 435 -**AT Command **to configure:578 +(% style="color:blue" %)**AT Command to configure:** 436 436 437 -**AT+TTRIG=1,30** 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.580 +(% 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. 438 438 439 -**AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm. 582 +(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm. 440 440 441 -== **2.8 Set debug mode** == 442 442 443 -Feature: Enable or Disable debug mode 444 444 586 +== 2.8 Set debug mode == 445 445 446 -**AT Command: AT+DEBUG** 447 447 589 +Feature: Enable or Disable debug mode 590 + 591 +(% style="color:blue" %)**AT Command: AT+DEBUG** 592 + 448 448 [[image:image-20221021111629-21.png]] 449 449 450 -== **2.9 Clear Flash Record** == 451 451 596 + 597 +== 2.9 Clear Flash Record == 598 + 599 + 452 452 Feature: Clear flash storage for data log feature. 453 453 454 -**AT Command: AT+CLRDTA** 602 +(% style="color:blue" %)**AT Command: AT+CLRDTA** 455 455 456 456 [[image:image-20221021111527-19.png]] 457 457 458 -== ** 2.10 Set trigger mode** == 459 459 460 -➢ AT Command: **AT+TTRMOD** 461 461 608 +== 2.10 Set trigger mode == 609 + 610 + 611 +(% style="color:blue" %)**AT Command: AT+TTRMOD** 612 + 462 462 Feature: Set the trigger interrupt mode. 463 463 464 464 [[image:image-20221021111552-20.png]] 465 465 466 -== **2.11 Set the calculate flag** == 467 467 618 + 619 +== 2.11 Set the calculate flag == 620 + 621 + 468 468 Feature: Set the calculate flag 469 469 470 -**AT Command: AT+CALCFLAG** 624 +(% style="color:blue" %)**AT Command: AT+CALCFLAG** 471 471 472 472 [[image:image-20221021111711-22.png]] 473 473 474 -== **2.12 Set count number** == 475 475 629 + 630 +== 2.12 Set count number == 631 + 632 + 476 476 Feature: Manually set the count number 477 477 478 -**AT Command: AT+SETCNT** 635 +(% style="color:blue" %)**AT Command: AT+SETCNT** 479 479 480 480 [[image:image-20221021111748-24.png]] 481 481 482 -== **2.13 Set the number of data to be uploaded and the recording time** == 483 483 484 -➢ AT Command: 485 485 486 - AT+TR=900~/~/Theunitis seconds, andthedefaultistorecordataonceevery900 seconds.( The minimum can beset to 180 seconds)641 +== 2.13 Set the number of data to be uploaded and the recording time == 487 487 488 488 489 - AT+NOUD=8~/~/The device uploads8 sets of recorded databy default. Up to 32 setsofrecord data canbe uploaded.644 +(% style="color:blue" %)**AT Command:** 490 490 491 -= =**2.14ReadorClearcacheddata**==646 +(% 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) 492 492 493 - ➢ATCommand:648 +(% 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. 494 494 495 -AT+CDP ~/~/ Read cached data 496 496 651 + 652 +== 2.14 Read or Clear cached data == 653 + 654 + 655 +(% style="color:blue" %)**AT Command:** 656 + 657 +(% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 658 + 659 +(% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 660 + 497 497 [[image:image-20221021111810-25.png||height="364" width="797"]] 498 498 499 499 500 -AT+CDP=0 ~/~/ Clear cached data 501 501 502 -== **2.15 Firmware Change Log**==665 +== 2.15 Firmware Change Log == 503 503 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]] 505 505 506 - Upgrade Instruction: [[UpgradeFirmware>>path:#H5.1200BHowtoUpgradeFirmware]]668 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]] 507 507 508 - == **2.16 BatteryAnalysis**==670 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 509 509 510 -=== **2.16.1 Battery Type** === 511 511 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. 513 513 514 - Thebatteryis designed to last for severalearsdependson the actually use environment and update interval.674 +== 2.16 Battery Analysis == 515 515 516 -The battery related documents as below: 517 517 677 +=== 2.16.1 Battery Type === 678 + 679 + 680 +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. 681 + 682 +The battery is designed to last for several years depends on the actual use environment and update interval. 683 + 684 +The battery-related documents as below: 685 + 518 518 * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 687 + 519 519 * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 689 + 520 520 * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 521 521 522 522 [[image:image-20221021111911-26.png]] 523 523 524 -=== **2.16.2 Power consumption Analyze** === 525 525 695 + 696 +=== 2.16.2 Power consumption Analyze === 697 + 698 + 526 526 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. 527 527 528 528 Instruction to use as below: 529 529 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/]] 703 +(% 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/]] 531 531 532 -**Step 2: ** Open it and choose 705 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 533 533 534 534 * Product Model 708 + 535 535 * Uplink Interval 710 + 536 536 * Working Mode 537 537 538 538 And the Life expectation in difference case will be shown on the right. 539 539 540 -[[image: image-20221021111923-27.png||height="253" width="783"]] 715 +[[image:1666596205057-567.png]] 541 541 542 -=== **2.16.3 Battery Note** === 543 543 718 + 719 +=== 2.16.3 Battery Note === 720 + 721 + 544 544 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. 545 545 546 -=== **2.16.4 Replace the battery** === 547 547 725 + 726 +=== 2.16.4 Replace the battery === 727 + 728 + 548 548 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). 549 549 550 -= **3. Access NB-IoT Module** = 551 551 732 + 733 += 3. Access NB-IoT Module = 734 + 735 + 552 552 Users can directly access the AT command set of the NB-IoT module. 553 553 554 554 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/]] ... ... @@ -555,10 +555,14 @@ 555 555 556 556 [[image:image-20221021112006-28.png]] 557 557 558 -= **4. Using the AT Commands** = 559 559 560 -== **4.1 Access AT Commands** == 561 561 744 += 4. Using the AT Commands = 745 + 746 + 747 +== 4.1 Access AT Commands == 748 + 749 + 562 562 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]] 563 563 564 564 AT+<CMD>? : Help on <CMD> ... ... @@ -569,8 +569,9 @@ 569 569 570 570 AT+<CMD>=? : Get the value 571 571 572 -**General Commands** 573 573 761 +(% style="color:blue" %)**General Commands** 762 + 574 574 AT : Attention 575 575 576 576 AT? : Short Help ... ... @@ -593,15 +593,12 @@ 593 593 594 594 AT+SERVADDR : Server Address 595 595 596 -AT+TR : Get or Set record time "785 +AT+TR : Get or Set record time 597 597 598 - 599 599 AT+NOUD : Get or Set the number of data to be uploaded 600 600 789 +AT+CDP : Read or Clear cached data 601 601 602 -AT+CDP : Read or Clear cached data 603 - 604 - 605 605 AT+ DEBUG : Enable or Disable debug mode 606 606 607 607 AT+ TTRIG : Get or Set Alarm Base on Timeout ... ... @@ -612,16 +612,19 @@ 612 612 613 613 AT+ CLRC : Clear current door open count 614 614 615 -**COAP Management** 616 616 802 +(% style="color:blue" %)**COAP Management** 803 + 617 617 AT+URI : Resource parameters 618 618 619 -**UDP Management** 620 620 807 +(% style="color:blue" %)**UDP Management** 808 + 621 621 AT+CFM : Upload confirmation mode (only valid for UDP) 622 622 623 -**MQTT Management** 624 624 812 +(% style="color:blue" %)**MQTT Management** 813 + 625 625 AT+CLIENT : Get or Set MQTT client 626 626 627 627 AT+UNAME : Get or Set MQTT Username ... ... @@ -632,86 +632,71 @@ 632 632 633 633 AT+SUBTOPIC : Get or Set MQTT subscription topic 634 634 635 -**Information** 636 636 825 +(% style="color:blue" %)**Information** 826 + 637 637 AT+FDR : Factory Data Reset 638 638 639 639 AT+PWORD : Serial Access Password 640 640 641 -= **5. FAQ** = 642 642 643 -== **5.1 How to Upgrade Firmware** == 644 644 645 - Usercanupgradethe firmware for 1) bug fix, 2) new feature release.833 += 5. FAQ = 646 646 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]] 648 648 649 - **Notice,**CPN01**and**CPN01**sharethe same motherboard. Theyuse the same connection andmethod to update.**836 +== 5.1 How to Upgrade Firmware == 650 650 651 -== **5.2 Can I calibrate CPN01 to different soil types?** == 652 652 653 - CPN01 iscalibrated forsaline-alkalisoil and loamy soil. Ifusers want to useitfor othersoil, they can calibratethe value in the IoT platformbaseon the valuemeasured by saline-alkalisoiland loamy soil. The formula can befoundat[[this link>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].839 +User can upgrade the firmware for 1) bug fix, 2) new feature release. 654 654 655 - =**6.Trouble** =841 +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]] 656 656 657 -== ** 6.1Connection problemwhenuploadingfirmware**==843 +(% 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.** 658 658 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]] 660 660 661 -== **6.2 AT Command input doesn't work** == 662 662 663 - Inthecase if usercan see the console outputbut can't type input to the device. Pleasecheck if you already include the **ENTER** while sendingoutthe command. Some serial tool doesn't send **ENTER** while press the send key, user need to add ENTER in their string.847 += 6. Trouble Shooting = 664 664 665 -= **7. Order Info** = 666 666 667 - PartNumber**:** CPN01850 +== 6.1 Connection problem when uploading firmware == 668 668 669 -= **8. Packing Info** = 670 670 671 -**Package **:853 +(% 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]] 672 672 673 -* CPN01 NB-IoT Soil Moisture & EC Sensor x 1 674 -* External antenna x 1 675 675 676 -**Dimension and weight**: 677 677 678 -* Size: 195 x 125 x 55 mm 679 -* Weight: 420g 857 +== 6.2 AT Command input doesn't work == 680 680 681 -= **9. Support** = 682 682 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]] 860 +In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER** (%%)while press the send key, user need to add ENTER in their string. 685 685 686 - 687 687 688 688 864 += 7. Order Info = 689 689 690 690 867 +Part Number**:** CPN01 691 691 692 692 693 693 871 += 8. Packing Info = 694 694 695 695 874 +(% style="color:blue" %)**Package Includes**: 696 696 876 +* CPN01 Open/Close Sensor x 1 877 +* External antenna x 1 697 697 879 +(% style="color:blue" %)**Dimension and weight**: 698 698 881 +* Size: 195 x 125 x 55 mm 882 +* Weight: 420g 699 699 884 += 9. Support = 700 700 701 701 887 +* 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. 702 702 889 +* 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]] 703 703 704 - 705 - 706 - 707 - 708 - 709 - 710 - 711 - 712 - 713 - 714 - 715 - 716 - 717 - 891 +
- 1666596205057-567.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +179.8 KB - Content
- image-20221022234529-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +43.3 KB - Content
- image-20221022234602-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +135.7 KB - Content
- image-20221023000439-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +82.1 KB - Content
- image-20221117105556-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +133.3 KB - Content
- image-20221117114459-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +14.9 KB - Content
- image-20221117114842-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +964.1 KB - Content
- image-20221117114937-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +79.1 KB - Content