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