Changes for page NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 17:03
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 16 removed)
- 1666596205057-567.png
- image-20221117105556-1.png
- image-20221117114459-2.png
- image-20221117114842-3.png
- image-20221117114937-4.png
- image-20221117114949-5.png
- image-20221117115010-6.png
- image-20221117142300-1.png
- image-20221117145932-2.png
- image-20221117150312-3.png
- image-20221118092935-1.png
- image-20221118093144-2.png
- image-20221118093512-3.png
- image-20221118093658-4.png
- image-20221118094227-5.png
- image-20221118094449-6.png
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -N DS03A- OutdoorNB-IoTOpen/Close Door Sensor User Manual1 +CPN01- NB-IoT Outdoor Open/Close Dry Contact Sensor User Manual - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.David - Content
-
... ... @@ -1,65 +1,34 @@ 1 1 (% style="text-align:center" %) 2 -[[image:i mage-20221117105556-1.png]]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"]] 3 3 4 +{{toc/}} 4 4 6 += **1. Introduction** = 5 5 8 +== **1.1 **What is CPN01 **NB-IoT** Pulse/Contact Sensor == 6 6 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. 7 7 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. 8 8 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. 9 9 10 - **Table ofContents:**16 +CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures. 11 11 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. 12 12 23 + 13 13 25 +== **1.2 Features** == 14 14 15 - 16 -= 1. Introduction = 17 - 18 -== 1.1 What is NDS03A NB-IoT Open/Close Door Sensor == 19 - 20 - 21 -((( 22 -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. 23 -))) 24 - 25 -((( 26 -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. 27 -))) 28 - 29 -((( 30 -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. 31 -))) 32 - 33 -((( 34 -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. 35 -))) 36 - 37 -((( 38 -NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures. 39 -))) 40 - 41 -((( 42 -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. 43 -))) 44 - 45 -((( 46 -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) 47 -))) 48 - 49 -((( 50 -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. 51 -))) 52 - 53 - 54 - 55 -== 1.2 Features == 56 - 57 - 58 58 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 59 59 * Open/Close detect 60 60 * Open/Close statistics 61 61 * Monitor Battery Level 62 -* connecttwodoorsensors31 +* Uplink on periodically and open/close event 63 63 * Datalog feature 64 64 * Uplink periodically 65 65 * Downlink to change configure ... ... @@ -70,41 +70,14 @@ 70 70 * Micro SIM card slot for NB-IoT SIM 71 71 * 8500mAh Battery for long-term use 72 72 73 -== 1.3 S torage & Operation ==42 +== **1.3 Specification** == 74 74 44 +**Common DC Characteristics:** 75 75 76 -Temperature -40°C to +85°C 77 - 78 - 79 -== 1.4 Mechanical == 80 - 81 - 82 -[[image:image-20221117114937-4.png]] 83 - 84 - 85 -[[image:image-20221117114949-5.png]] 86 - 87 - 88 -[[image:image-20221117115010-6.png]] 89 - 90 - 91 - 92 -== 1.5 Applications == 93 - 94 - 95 -[[image:image-20221117114842-3.png]] 96 - 97 - 98 - 99 -== 1.6 Specification == 100 - 101 - 102 -(% style="color:blue" %)**Common DC Characteristics:** 103 - 104 104 * Supply Voltage: 2.1v ~~ 3.6v 105 105 * Operating Temperature: -40 ~~ 85°C 106 106 107 - (% style="color:blue" %)**NB-IoT Spec:**49 +**NB-IoT Spec:** 108 108 109 109 * - B1 @H-FDD: 2100MHz 110 110 * - B3 @H-FDD: 1800MHz ... ... @@ -113,96 +113,90 @@ 113 113 * - B20 @H-FDD: 800MHz 114 114 * - B28 @H-FDD: 700MHz 115 115 116 -== 1. 7PinDefinitionsand Switch==58 +== **1.4 Installation** == 117 117 60 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event. 118 118 119 -[[image:image-20221021110 429-4.png]]62 +[[image:image-20221021110329-1.png]] 120 120 64 +[[image:image-20221022234602-2.png||height="288" width="922"]] 121 121 122 -=== 1.7.1 Pin Definition === 123 123 67 +== **1.5 Applications** == 124 124 125 -The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at: [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]] 69 +* Open/Close Detection 70 +* Pulse meter application 71 +* Dry Contact Detection 126 126 73 +== **1.6 Mechanical** == 127 127 75 +[[image:image-20221021110415-3.png]] 128 128 129 -== =1.7.2Jumper JP2(PowerON/OFF)===77 +== ** 1.7 Pin Definitions and Switch** == 130 130 79 +[[image:image-20221021110429-4.png]] 131 131 132 - Poweron Device whenputtingthis jumper.81 +=== **1.7.1 Pin Definition** === 133 133 83 +CPN01 is pre-configured to connect to two external wires. The other pins are not used. If user wants to know more about other pins, please refer to the **[[LSN50v2 User Manual>>doc:Main.User Manual for LoRaWAN End Nodes.LSN50 & LSN50-V2 - LoRaWAN Sensor Node User Manual.WebHome]]**. 134 134 135 135 136 -=== 1.7. 3BOOTMODE/SW1===86 +=== **1.7.2 Jumper JP2(Power ON/OFF)** === 137 137 88 +Power on Device when putting this jumper. 138 138 139 -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. 140 140 141 - 2)Flash:working mode, the device starts to work for NB-IoTconnectionandsendsout console output for further debugging.91 +=== **1.7.3 BOOT MODE / SW1** === 142 142 143 143 94 +1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run. 144 144 145 - ===1.7.4Reset Button===96 +2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging. 146 146 147 147 148 - Presstoreboot thedevice.99 +=== **1.7.4 Reset Button** === 149 149 150 150 102 +Press to reboot the device. 151 151 152 -=== 1.7.5 LED === 153 153 105 +=== **1.7.5 LED** === 154 154 107 + 155 155 The LED will blink when : 156 156 157 -1. Boot the device in flash mode 110 +1. Boot the device in flash mode 111 +1. Send an uplink packet 158 158 159 -2. Sendanuplink packet113 += **2. Use CPN01 to communicate with IoT Server** = 160 160 115 +== **2.1 How it works** == 161 161 117 +The CPN01 is equipped with an NB-IoT module, the pre-loaded firmware in CPN01 will get **Open/Close Event or Count** from sensor and send the value to the NB-IoT network. The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01. 162 162 163 - ==1.8 MagnetDistance==119 +The diagram below shows the working flow in the default firmware of CPN01: 164 164 165 - 166 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm 167 - 168 -(% style="color:blue" %)**Iron Door:**(%%)** **30 ~~ 45mm 169 - 170 - 171 - 172 -= 2. Use NDS03A to communicate with IoT Server = 173 - 174 -== 2.1 How it works == 175 - 176 - 177 -In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A. 178 - 179 -The diagram below shows the working flow in the default firmware of NDS03A: 180 - 181 181 [[image:image-20221021110615-5.png]] 182 182 183 183 124 +== **2.2 Configure CPN01** == 184 184 185 -== 2.2 ConfigureNDS03A==126 +=== **2.2.1 Test Requirement** === 186 186 187 - ===2.2.1TestRequirement===128 +To use CPN01 in your city, make sure to meet below requirements: 188 188 189 - 190 -To use NDS03A in your city, make sure to meet below requirements: 191 - 192 192 * Your local operator has already distributed an NB-IoT Network. 193 -* The local NB-IoT network used the band that N DS03Asupports.131 +* The local NB-IoT network used the band that CPN01 supports. 194 194 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 195 195 196 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The N DS03Awill 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.134 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The CPN01 will use CoAP(120.24.4.116:5683) or raw UDP(120.24.4.116:5601) or MQTT(120.24.4.116:1883)or TCP(120.24.4.116:5600)protocol to send data to the test server. 197 197 198 -[[image:image-20221 117142300-1.png]]136 +[[image:image-20221023000439-3.png]] 199 199 200 200 201 201 140 +=== **2.2.2 Insert NB-IoT SIM card** === 202 202 203 -=== 2.2.2 Insert NB-IoT SIM card === 204 - 205 - 206 206 Insert the NB-IoT Card get from your provider. 207 207 208 208 User needs to take out the NB-IoT module and insert the SIM card like below: ... ... @@ -210,127 +210,101 @@ 210 210 [[image:image-20221021110745-6.png]] 211 211 212 212 149 +=== **2.2.3 Connect USB – TTL to CPN01 and configure it** === 213 213 214 - ===2.2.3Connect USB–TTL to NDS03A and configure it===151 +User need to configure CPN01 via serial port to set the **Server Address** / **Uplink Topic** to define where and how-to uplink packets. CPN01 support AT Commands, user can use a USB to TTL adapter to connect to CPN01 and use AT Commands to configure it, as below. 215 215 153 +**Connection:** 216 216 217 - Userneed to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USBtoTTLadapter to connect toNDS03Aanduse AT Commands to configure it, as below.155 + USB TTL GND <~-~-~-~-> GND 218 218 219 - (%style="color:blue"%)**Connection:**157 + USB TTL TXD <~-~-~-~-> UART_RXD 220 220 221 - (%style="background-color:yellow" %)**USB TTLGND <~-~-~-~->GND**159 + USB TTL RXD <~-~-~-~-> UART_TXD 222 222 223 -(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD** 224 - 225 -(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD** 226 - 227 - 228 228 In the PC, use below serial tool settings: 229 229 230 -* Baud: (% style="color:red" %)**9600** 163 +* Baud: **9600** 164 +* Data bits:** 8** 165 +* Stop bits: **1** 166 +* Parity: **None** 167 +* Flow Control: **None** 231 231 232 - * Databits:**(% style="color:red" %)8(%%)**169 +Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%). 233 233 234 -* Stop bits: (% style="color:red" %)**1** 235 - 236 -* Parity: (% style="color:red" %)**None** 237 - 238 -* Flow Control: (% style="color:red" %)**None** 239 - 240 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%). 241 - 242 242 [[image:image-20221021110817-7.png]] 243 243 244 -N DS03Awill output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.173 +CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input. 245 245 246 246 247 - (% 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 +**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]] 248 248 249 249 179 +=== **2.2.4 Use CoAP protocol to uplink data** === 250 250 251 - ===2.2.4Use CoAPprotocol to uplink===181 +**Note: if you don't have a CoAP server, you can refer this link to set up a CoAP server: **[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 252 252 253 253 254 - (% style="color:red" %)**Note: if you don't have a CoAPserver,you can refer thislink toset 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/]]184 +**Use below commands in CPN01:** 255 255 186 +* **AT+PRO=1** ~/~/ Set to use CoAP protocol to uplink 187 +* **AT+SERVADDR=120.24.4.116,5683 ** ~/~/ Set CoAP server address and port 188 +* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set CoAP resource path 256 256 257 -(% style="color:blue" %)**Use below commands in NDS03A:** 258 - 259 -* (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 260 - 261 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ Set CoAP server address and port 262 - 263 -* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/ Set CoAP resource path 264 - 265 265 For parameter description, please refer to AT command set 266 266 267 267 [[image:image-20221021110948-8.png]] 268 268 269 269 270 -After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%)(via AT+ATZ ), NDS03Awill start to uplink sensor values to the CoAP server.195 +After configuring the server address and **reset CPN01** (via AT+ATZ ), CPN01 will start to uplink sensor values to the CoAP server. 271 271 272 272 [[image:image-20221021110956-9.png]] 273 273 274 274 200 +=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** === 275 275 276 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 277 277 203 +**AT Commands:** 278 278 279 -(% style="color:blue" %)**AT Commands:** 205 +* **AT+PRO=2 ** ~/~/ Set to use UDP protocol to uplink 206 +* **AT+SERVADDR=120.24.4.116,5601 ** ~/~/ Set UDP server address and port 207 +* **AT+CFM=1 ** ~/~/If the server does not respond, this command is unnecessary 280 280 281 -* (% style="color:#037691" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 282 - 283 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ Set UDP server address and port 284 - 285 -* (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 286 - 287 287 [[image:image-20221021111025-10.png]] 288 288 289 - 290 290 [[image:image-20221021111033-11.png||height="241" width="576"]] 291 291 292 292 293 293 215 +=== **2.2.6 Use MQTT protocol to uplink data** === 294 294 295 -=== 2.2.6 Use MQTT protocol to uplink data === 296 296 218 +**AT Commands:** 297 297 298 -(% style="color:blue" %)**AT Commands:** 220 +* **AT+PRO=3 ** ~/~/Set to use MQTT protocol to uplink 221 +* **AT+SERVADDR=120.24.4.116,1883 ** ~/~/Set MQTT server address and port 222 +* **AT+CLIENT=CLIENT ** ~/~/Set up the CLIENT of MQTT 223 +* **AT+UNAME=UNAME **~/~/Set the username of MQTT 224 +* **AT+PWD=PWD **~/~/Set the password of MQTT 225 +* **AT+PUBTOPIC=NSE01_PUB **~/~/Set the sending topic of MQTT 226 +* **AT+SUBTOPIC=NSE01_SUB ** ~/~/Set the subscription topic of MQTT 299 299 300 -* (% style="color:#037691" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 301 - 302 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 303 - 304 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT ** (%%) ~/~/ Set up the CLIENT of MQTT 305 - 306 -* (% style="color:#037691" %)**AT+UNAME=UNAME **(%%)** **~/~/ Set the username of MQTT 307 - 308 -* (% style="color:#037691" %)**AT+PWD=PWD **(%%)** **~/~/ Set the password of MQTT 309 - 310 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB **(%%)** **~/~/ Set the sending topic of MQTT 311 - 312 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB ** (%%) ~/~/ Set the subscription topic of MQTT 313 - 314 314 [[image:image-20221021111058-12.png]] 315 315 230 +[[image:image-20221021111108-13.png]] 316 316 317 -[[image:image-20221021111201-16.png||height="472" width="653"]] 318 - 319 319 320 320 321 321 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. 322 322 323 323 237 +=== **2.2.7 Use TCP protocol to uplink data** === 324 324 325 - === 2.2.7 UseTCPprotocol to uplinkdata ===239 +**AT Commands** 326 326 241 +* **AT+PRO=4 ** ~/~/ Set to use TCP protocol to uplink 242 +* **AT+SERVADDR=120.24.4.116,5600 ** ~/~/ Set TCP server address and port 327 327 328 -(% style="color:blue" %)**AT Commands:** 329 - 330 -* (% style="color:#037691" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 331 - 332 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ Set TCP server address and port 333 - 334 334 [[image:image-20221021111125-14.png]] 335 335 336 336 [[image:image-20221021111131-15.png]] ... ... @@ -337,96 +337,73 @@ 337 337 338 338 339 339 250 +=== **2.2.8 Change Update Interval** === 340 340 341 - ===2.2.8ChangeUpdateInterval===252 +User can use below command to change the **uplink interval**. 342 342 254 +* **AT+TDC=7200 ** ~/~/ Set Update Interval to 7200s (2 hours) 343 343 344 - User can use below command to change the (% style="color:blue" %)**uplink interval**.256 +**NOTE:** 345 345 346 -* (% style="color:#037691"%)**AT+TDC=14400**(%%)~/~/ SetUpdateIntervalto14400s(4hours)258 +**~1. By default, the device will send an uplink message every 1 hour.** 347 347 348 -(% style="color:red" %)**NOTE:** 349 349 350 - 1.By default, the device will send an uplinkmessage every4 hour.261 +== **2.3 Uplink Payload** == 351 351 263 +The uplink payload includes 123 bytes in total by default. 352 352 265 +Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded. 353 353 354 -== 2.3 Uplink Payload == 267 +|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**1**|**1**|**3** 268 +|**Value**|[[Device ID>>path:#H2.4.1A0A0DeviceID]]|[[Ver>>path:#H2.4.2A0VersionInfo]]|[[BAT>>path:#H2.4.3A0BatteryInfo]]|[[Signal Strength>>path:#H2.4.4A0SignalStrength]]|MOD|[[ Calculate Flag>>path:#H2.4.8A0DigitalInterrupt]]|Contact Status|Alarm|Total pulse 355 355 270 +(% style="width:1201px" %) 271 +|**3**|**4**|**1**|**3**|**1**|**3**|4|**8 group**|(% style="width:1px" %) 272 +|The last open duration|Time stamp|Contact Status|Total pulse|Calculate Flag|The last open duration|Time stamp|...|(% style="width:1px" %) 356 356 357 - The uplinkpayloadincludes26bytes intotalbydefault.274 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data. 358 358 359 - Each timethe device uploads a data package.The user canuse theAT+NOUD command to upload the recorded data.Up to 32sets of recorded data can be uploaded.276 +[[image:image-20221021111201-16.png||height="572" width="792"]] 360 360 361 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:** 362 - 363 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %) 364 -|=(% scope="row" style="width: 93px;" %)**Size(bytes)**|(% style="width:67px" %)**8**|(% style="width:40px" %)**2**|(% style="width:45px" %)**2**|(% style="width:75px" %)**1**|(% style="width:54px" %)**1**|(% style="width:62px" %)**1**|(% style="width:60px" %)**1**|(% style="width:94px" %)**3**|(% style="width:93px" %)**3** 365 -|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.4.6A0Alarm"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14) 366 - 367 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %) 368 -|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)((( 369 -**1-32 group** 370 -))) 371 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)... 372 - 373 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:** 374 - 375 - 376 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %) 377 -|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:66px" %)**8**|(% style="width:40px" %)**2**|(% style="width:46px" %)**2**|(% style="width:70px" %)**1**|(% style="width:54px" %)**1**|(% style="width:55px" %)**1**|(% style="width:57px" %)**1**|(% style="width:86px" %)**3**|(% style="width:82px" %)**3** 378 -|=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.4.6A0Alarm"]]|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14) 379 - 380 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %) 381 -|(% style="width:59px" %)**1**|(% style="width:67px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:66px" %)**1**|(% style="width:92px" %)**3** 382 -|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPN01-%20NB-IoT%20Outdoor%20OpenClose%20Dry%20Contact%20Sensor%C2%A0User%20Manual/#H2.4.7A0ContactStatus]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)Time stamp|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14) 383 - 384 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %) 385 -|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)((( 386 -**1-32 group** 387 -))) 388 -|(% style="width:102px" %)last open time (pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:88px" %)last open time(pb15)|(% style="width:63px" %)Time stamp|(% style="width:87px" %)... 389 - 390 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data. 391 - 392 -[[image:image-20221117145932-2.png]] 393 - 394 - 395 395 The payload is ASCII string, representative same HEX: 396 396 397 -**0x (% style="color:red" %)__f867787050213317__ (% style="color:blue" %)__0064__ (% style="color:green" %) _0ccf__(% style="color:#00b0f0" %)19__(% style="color:#7030a0" %)__01__(% style="color:#0020b0" %)__00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %)__000017__ (% style="color:#d60093" %)__637590df__(%%)**280 +**0x (% style="color:red" %)__0xf867787050213317__ (% style="color:blue" %)__0064__ (% style="color:green" %)_0c78__ __(% style="color:#00b0f0" %)17__ __(% style="color:#7030a0" %)01__ __(% style="color:#d60093" %)00__ __(% style="color:#a14d07" %)01 __ __(% style="color:#0020b0" %)__ __00__ __(% style="color:#420042" %)000009__ __(% style="color:#663300" %) 000002__ __(% style="color:#d60093" %)6315537bb__ __(% style="color:#663300" %)// 0100000b02000002663510fed__ __0100000e0200000263510f39 010000000000000063510e85 010000000000000063510d2e 010000000000000063510c7a 010000000000000063510bc6 010000000000000063510954 010000000000000063510882 //(%%)** 398 398 399 -**where:** 282 +where: 283 +*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317 400 400 401 -* Device ID:**(%%) 0xf867787050213317 = f867787050213317285 +*(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0 402 402 403 -* Version:**(%%) 0x0064=100=1.0.0287 +*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V 404 404 405 -* BAT:**(%%)0ccf = 3279mV=3.279V289 +*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23 406 406 407 -* Singal:9=25291 +*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1 408 408 409 -* Mod:**(%%) 0x01=1293 +*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00=0 410 410 411 -* DoorStatus:**(%%) 0x00=0295 +*(% style="color:#037691" %) **Contact Status:**(%%) 0x00=0 412 412 413 -* Status:297 +*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0 414 414 415 -* dooropen num:**(%%)0x000016=22299 +*(% style="color:#037691" %) **Total pulse:0x09 =0** 416 416 417 -* me:00017=23301 +*(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2 418 418 419 -* 7590df=1668649183(Unix Time)303 +*(% style="color:#037691" %)** Time stamp :**(%%) 0x6315537b =1662342011 (Unix Time) 420 420 421 -= =2.4PayloadExplanationandSensorInterface==305 +*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000b0200002663510fed 422 422 307 +*(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,....... 423 423 424 -=== 2.4.1 Device ID === 425 425 310 +== **2.4 Payload Explanation and Sensor Interface** == 426 426 312 +=== **2.4.1 Device ID** === 313 + 427 427 By default, the Device ID is equal to the last 15 bits of IMEI. 428 428 429 -User can use (% style="color:blue" %)**AT+DEUI**(%%)to set Device ID316 +User can use **AT+DEUI** to set Device ID 430 430 431 431 **Example:** 432 432 ... ... @@ -435,27 +435,24 @@ 435 435 The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID. 436 436 437 437 438 -=== 2.4.2 Version Info === 325 +=== **2.4.2 Version Info** === 439 439 440 - 441 441 Specify the software version: 0x64=100, which means firmware version 1.00. 442 442 443 -For example 0x00 64 : This device is N DS03A1 with firmware version 1.0.0.329 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0. 444 444 445 445 446 -=== 2.4.3 Battery Info === 332 +=== **2.4.3 Battery Info** === 447 447 334 +Check the battery voltage for CPN01. 448 448 449 -Check the battery voltage for NDS03A. 450 - 451 451 Ex1: 0x0B45 = 2885mV 452 452 453 453 Ex2: 0x0B49 = 2889mV 454 454 455 455 456 -=== 2.4.4 Signal Strength === 341 +=== **2.4.4 Signal Strength** === 457 457 458 - 459 459 NB-IoT Network signal Strength. 460 460 461 461 **Ex1: 0x1d = 29** ... ... @@ -471,46 +471,62 @@ 471 471 **99** Not known or not detectable 472 472 473 473 474 -=== 2.4.5 Disalarm: (default:0)===358 +=== **2.4.5 Calculate Flag** === 475 475 360 +The calculate flag is a user defined field, IoT server can use this filed to handle different meters with different pulse factors. For example, if there are 100 water meters, meter 1~~50 are 1 liter/pulse and meter 51 ~~ 100 has 1.5 liter/pulse. 476 476 477 - (%style="color:blue"%)**IfDisalarm=1**(%%),NDS03A willonlysend uplink atveryTDCperiodically. This isnormallyuseforpulsemeterapplication,inthisapplication,therearemanyopen/closeevent,andplatformonlycare aboutthe totalnumber of pulse.362 +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. 478 478 479 - (% style="color:blue" %)**IfDisalarm = 0**(%%), NDS03A will senduplink atevery TDC periodically and send data on each open/close event. This isusefulfor the application user need to monitor the open/close event in real-time.364 +Default value: 0. 480 480 481 - ( %style="color:red" %)**Note:**(%%)When Disalarm=0,ahigh frequently open/close event will cause lots of uplink and drainbatteryvery fast.366 +Range (6 bits): (b)000000 ~~ (b) 111111 482 482 483 483 484 -=== 2.4.6 KeepStatus & Keep Time===369 +=== **2.4.6 Alarm** === 485 485 371 +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]] 486 486 487 -Shows the configure value of Alarm Base on Timeout Feature 488 488 374 +=== **2.4.7 Contact Status** === 489 489 490 - ===2.4.7 Timestamp===376 +0: Open 491 491 378 +1: Close 492 492 493 -Timestamp : 0x6315537b =1662342011 494 494 381 +=== **2.4.8 Total pulse** === 495 495 383 +Total pulse/counting based on dry [[contact trigger event>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.2SensorConfiguration2CFPORT3D4]] 496 496 497 - ===2.4.8SwitchDualChannelMode===385 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215 498 498 499 499 500 - NDS03Acan connect two door sensors.Anotherdoor sensor can be connectedtoPB15pin.Both channels supportalarm function.388 +=== **2.4.9 The last open duration** === 501 501 390 +Dry Contact last open duration. 502 502 503 - == 2.5 DownlinkPayload ==392 +Unit: min. 504 504 394 +[[image:image-20221021111346-17.png||height="146" width="770"]] 505 505 506 -By default, NDS03A prints the downlink payload to console port. 507 507 508 - [[image:image-20221021111414-18.png]]397 +=== **2.4.10 Timestamp** === 509 509 399 +Timestamp : 0x6315537b =1662342011 510 510 401 +Convert Unix timestamp to time 2022-9-5 9:40:11. 402 + 403 +**~ ** 404 + 405 +== **2.5 Downlink Payload** == 406 + 407 +By default, CPN01 prints the downlink payload to console port. 408 + 409 +[[image:image-20221021111414-18.png]] 410 + 511 511 **Examples:** 512 512 513 -* (% style="color:#037691" %)**Set TDC**413 +* **Set TDC** 514 514 515 515 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 516 516 ... ... @@ -518,236 +518,173 @@ 518 518 519 519 Payload: 01 00 00 3C TDC=60S 520 520 521 -* (% style="color:#037691" %)**Reset**421 +* **Reset** 522 522 523 -If payload = 0x04FF, it will reset the N DS03A423 +If payload = 0x04FF, it will reset the NSE01 524 524 525 -* (% style="color:#037691" %)**INTMOD**425 +* **INTMOD** 526 526 527 527 Downlink Payload: 06000003, Set AT+INTMOD=3 528 528 429 +== **2.6 LED Indicator** == 529 529 431 +The CPN01 has an internal LED which is to show the status of different states. 530 530 531 -== 2.6 LED Indicator == 532 - 533 - 534 -The NDS03A has an internal LED which is to show the status of different states. 535 - 536 -* When the device starts normally, the LED will light up for 1 second. 537 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds. 433 +* 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) 434 +* Then the LED will be on for 1 second means device is boot normally. 435 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds. 538 538 * For each uplink probe, LED will be on for 500ms. 539 539 540 -== 2.7 Alarm Base on Timeout == 438 +== **2.7 Alarm Base on Timeout** == 541 541 440 +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: 542 542 543 -NDS03A 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: 544 544 443 +**~1. Keep Status: Status to be monitor** 545 545 546 -(% style="color:blue" %)**1. Keep Status: Status to be monitor** 547 - 548 548 Keep Status = 1: Monitor Close to Open event 549 549 550 550 Keep Status = 0: Monitor Open to Close event 551 551 552 552 553 - (% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**450 +**2. Keep Time: Timeout to send an Alarm** 554 554 555 555 Range 0 ~~ 65535(0xFFFF) seconds. 556 556 557 557 If keep time = 0, Disable Alarm Base on Timeout feature. 558 558 559 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn 't change after timeout.456 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout. 560 560 561 561 562 - (% style="color:blue" %)**AT Command to configure:**459 +**AT Command** to configure: 563 563 564 - (%style="color:blue"%)**PB14PIN:**461 +**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. 565 565 566 - (% style="color:#037691" %)**AT+TTRIG=1,30**(%%)**~-~->**When the **Keep Status** changefrom connected to disconnect,and device remains in disconnect status for morethan30 seconds. NDS03A will sendan 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]] (thesecond bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.463 +**AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm. 567 567 568 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm. 569 569 466 +== **2.8 Set debug mode** == 570 570 571 -(% style="color:blue" %)**PB15 PIN:** 572 - 573 -(% style="color:#037691" %)**AT+TTRIG2=1,30** 574 - 575 -(% style="color:#037691" %)**AT+TTRIG2=0,0 ** 576 - 577 - 578 -== 2.8 Set debug mode == 579 - 580 - 581 581 Feature: Enable or Disable debug mode 582 582 583 -(% style="color:blue" %)**AT Command: AT+DEBUG** 584 584 471 +**AT Command: AT+DEBUG** 472 + 585 585 [[image:image-20221021111629-21.png]] 586 586 475 +== **2.9 Clear Flash Record** == 587 587 588 - 589 -== 2.9 Clear Flash Record == 590 - 591 - 592 592 Feature: Clear flash storage for data log feature. 593 593 594 - (% style="color:blue" %)**AT Command: AT+CLRDTA**479 +**AT Command: AT+CLRDTA** 595 595 596 596 [[image:image-20221021111527-19.png]] 597 597 483 +== ** 2.10 Set trigger mode** == 598 598 485 +➢ AT Command: **AT+TTRMOD** 599 599 600 - ==2.10CountMod==487 +Feature: Set the trigger interrupt mode. 601 601 489 +[[image:image-20221021111552-20.png]] 602 602 603 - (%style="color:blue"%)**AT Command: AT+COUNTMOD**491 +== **2.11 Set the calculate flag** == 604 604 605 - [[image:image-20221118092935-1.png]]493 +Feature: Set the calculate flag 606 606 495 +**AT Command: AT+CALCFLAG** 607 607 497 +[[image:image-20221021111711-22.png]] 608 608 609 -== 2.1 1InterruptPinChannelMod==499 +== **2.12 Set count number** == 610 610 501 +Feature: Manually set the count number 611 611 612 - (% style="color:blue" %)**AT Command: AT+TTRCHANNEL**503 +**AT Command: AT+SETCNT** 613 613 614 -[[image:image-2022111 8093144-2.png]]505 +[[image:image-20221021111748-24.png]] 615 615 507 +== **2.13 Set the number of data to be uploaded and the recording time** == 616 616 509 +➢ AT Command: 617 617 618 - == 2.12TTRIG1/2timeout statusalarm==511 +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) 619 619 620 620 621 - It needs to be used withAT+TTRIG1or AT+TTRIG2. WhenTTRIG1 or TTRIG2 timesoutandcausesanalarm, andthestatus does not changesubsequently,an alarmpacketwillbesentatthe alarminterval.514 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 622 622 623 - (%style="color:blue"%)**AT Command:AT+TTRALARM**516 +== **2.14 Read or Clear cached data** == 624 624 625 - [[image:image-20221118093512-3.png]]518 +➢ AT Command: 626 626 520 +AT+CDP ~/~/ Read cached data 627 627 522 +[[image:image-20221021111810-25.png||height="364" width="797"]] 628 628 629 -== 2.13 Select counting mode == 630 630 525 +AT+CDP=0 ~/~/ Clear cached data 631 631 632 - (% style="color:blue"%)**ATCommand:AT+TTRMODx=a,b**527 +== **2.15 Firmware Change Log** == 633 633 634 - When(% style="color:red"%)**a=0**(%%), thedoor isened tount,andwhen(% style="color:red" %)**a=1**(%%),the closeddoor iscounted.529 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]] 635 635 636 - When (% style="color:red" %)**b=0**(%%), it is thelastdooropen duration,andwhen (%style="color:red" %)**b=1**(%%),the lastdoorcloseduration.531 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 637 637 638 - [[image:image-20221118093658-4.png]]533 +== **2.16 Battery Analysis** == 639 639 535 +=== **2.16.1 Battery Type** === 640 640 537 +The CPN01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 641 641 642 - 643 -== 2.14 Set the number of data to be uploaded and the recording time == 644 - 645 - 646 -(% style="color:blue" %)**AT Command:** 647 - 648 -(% 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) 649 - 650 -(% style="color:#037691" %)**AT+NOUD=8**(%%)** ** ~/~/ The device uploads 0 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 651 - 652 - 653 -== 2.15 Read or Clear cached data == 654 - 655 - 656 -(% style="color:blue" %)**AT Command:** 657 - 658 -(% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 659 - 660 -(% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 661 - 662 -[[image:image-20221118094227-5.png]] 663 - 664 - 665 - 666 -== 2.16 Firmware Change Log == 667 - 668 - 669 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]] 670 - 671 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 672 - 673 - 674 - 675 -== 2.17 Battery Analysis == 676 - 677 - 678 -=== 2.17.1 Battery Type === 679 - 680 - 681 -The NDS03A 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. 682 - 683 683 The battery is designed to last for several years depends on the actual use environment and update interval. 684 684 685 685 The battery-related documents as below: 686 686 687 687 * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 688 - 689 689 * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 690 - 691 691 * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 692 692 693 693 [[image:image-20221021111911-26.png]] 694 694 549 +=== **2.16.2 Power consumption Analyze** === 695 695 696 - 697 -=== 2.17.2 Power consumption Analyze === 698 - 699 - 700 700 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. 701 701 702 702 Instruction to use as below: 703 703 704 - (% 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/]]555 +**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/]] 705 705 706 - (% style="color:blue" %)**Step 2: **(%%)Open it and choose557 +**Step 2: ** Open it and choose 707 707 708 708 * Product Model 709 - 710 710 * Uplink Interval 711 - 712 712 * Working Mode 713 713 714 714 And the Life expectation in difference case will be shown on the right. 715 715 716 -[[image: 1666596205057-567.png]] 565 +[[image:image-20221021111923-27.png||height="253" width="783"]] 717 717 567 +=== **2.16.3 Battery Note** === 718 718 719 - 720 -=== 2.17.3 Battery Note === 721 - 722 - 723 723 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. 724 724 571 +=== **2.16.4 Replace the battery** === 725 725 573 +The default battery pack of CPN01 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes). 726 726 727 -=== 2.17.4 Replace the battery === 728 728 576 += **3. Access NB-IoT Module** = 729 729 730 -The default battery pack of NDS03A 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). 731 - 732 - 733 - 734 -= 3. Access NB-IoT Module = 735 - 736 - 737 737 Users can directly access the AT command set of the NB-IoT module. 738 738 739 739 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/]] 740 740 741 -[[image:image-2022111 8094449-6.png]] 582 +[[image:image-20221021112006-28.png]] 742 742 584 += **4. Using the AT Commands** = 743 743 586 +== **4.1 Access AT Commands** == 744 744 745 -= 4. Using the AT Commands = 746 - 747 - 748 -== 4.1 Access AT Commands == 749 - 750 - 751 751 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]] 752 752 753 753 AT+<CMD>? : Help on <CMD> ... ... @@ -758,9 +758,8 @@ 758 758 759 759 AT+<CMD>=? : Get the value 760 760 598 +**General Commands** 761 761 762 -(% style="color:blue" %)**General Commands** 763 - 764 764 AT : Attention 765 765 766 766 AT? : Short Help ... ... @@ -783,41 +783,35 @@ 783 783 784 784 AT+SERVADDR : Server Address 785 785 786 -AT+TR : 622 +AT+TR : Get or Set record time" 787 787 624 + 788 788 AT+NOUD : Get or Set the number of data to be uploaded 789 789 790 -AT+CDP : Read or Clear cached data 791 791 792 -AT+ EBUG:Enable orDisabledebugmode628 +AT+CDP : Read or Clear cached data 793 793 794 -AT+ TTRIG1 : Get or Set PB14 PIN Alarm Base on Timeout 795 795 796 -AT+ TTRIG2:GetorSetPB15 PIN Alarm Baseon Timeout631 +AT+ DEBUG : Enable or Disable debug mode 797 797 798 -AT+ COUNTMOD:thecountmode633 +AT+ TTRIG : Get or Set Alarm Base on Timeout 799 799 800 -AT+TTR CHANNEL: Get or Set thenumberofinterruptchannels635 +AT+ TTRMOD : Get or Set the trigger interrupt mode(0:falling,1:rising) 801 801 802 -AT+ TTRALARMTTRIG1 of Alarm interval(unit: minute)637 +AT+ CALCFLAG : Get or Set the calculate flag 803 803 804 -AT+ DISALARM:Enable/Disable Alarmfor door open/close or water leak event639 +AT+ CLRC : Clear current door open count 805 805 806 -A T+CLRC : Clear current door opencount641 +**COAP Management** 807 807 808 - 809 -(% style="color:blue" %)**COAP Management** 810 - 811 811 AT+URI : Resource parameters 812 812 645 +**UDP Management** 813 813 814 -(% style="color:blue" %)**UDP Management** 815 - 816 816 AT+CFM : Upload confirmation mode (only valid for UDP) 817 817 649 +**MQTT Management** 818 818 819 -(% style="color:blue" %)**MQTT Management** 820 - 821 821 AT+CLIENT : Get or Set MQTT client 822 822 823 823 AT+UNAME : Get or Set MQTT Username ... ... @@ -828,65 +828,86 @@ 828 828 829 829 AT+SUBTOPIC : Get or Set MQTT subscription topic 830 830 661 +**Information** 831 831 832 -(% style="color:blue" %)**Information** 833 - 834 834 AT+FDR : Factory Data Reset 835 835 836 836 AT+PWORD : Serial Access Password 837 837 667 += **5. FAQ** = 838 838 669 +== **5.1 How to Upgrade Firmware** == 839 839 840 - =5.FAQ=671 +User can upgrade the firmware for 1) bug fix, 2) new feature release. 841 841 673 +Please see this link for how to upgrade: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]] 842 842 843 - ==5.1HowtoUpgradeFirmware==675 +**Notice, **CPN01 **and **CPL01 **share the same mother board. They use the same connection and method to update.** 844 844 845 845 846 - Usercanupgradethe firmware for 1) bug fix, 2)newfeature release.678 += **6. Trouble Shooting** = 847 847 848 - Pleaseseethis 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]]680 +== **6.1 Connection problem when uploading firmware** == 849 849 850 - (% style="color:red"%)**Notice: **(% style="color:blue"%)**NDS03A** (%%)**and(%yle="color:blue"%)LDS03A(%%)**(%style="color:blue" %) (%%)**sharethe sameotherboard. They usethe sameconnectionnd methodpdate.**682 +**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]] 851 851 852 852 685 +== **6.2 AT Command input doesn't work** == 853 853 854 - =6.TroubleShooting=687 +In the case if user can see the console output but can't type input to the device. Please check if you already include the **ENTER** while sending out the command. Some serial tool doesn't send **ENTER** while press the send key, user need to add ENTER in their string. 855 855 856 856 857 -= =6.1Connectionproblemwhenuploadingfirmware==690 += **7. Order Info** = 858 858 692 +Part Number**:** CPN01 859 859 860 -(% 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]] 861 861 695 += **8. Packing Info** = 862 862 697 +**Package Includes**: 863 863 864 -== 6.2 AT Command input doesn't work == 699 +* CPN01 Open/Close Sensor x 1 700 +* External antenna x 1 865 865 702 +**Dimension and weight**: 866 866 867 -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. 704 +* Size: 195 x 125 x 55 mm 705 +* Weight: 420g 868 868 707 += **9. Support** = 869 869 709 +* 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. 710 +* 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]] 870 870 871 - = 7.Order Info =712 + 872 872 873 873 874 -Part Number**:** NDS03A 875 875 876 876 877 877 878 -= 8. Packing Info = 879 879 880 880 881 -(% style="color:blue" %)**Package Includes**: 882 882 883 -* NDS03A Open/Close Door Sensor x 1 884 884 885 -= 9. Support = 886 886 887 887 888 -* 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. 889 889 890 -* 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]] 891 891 892 - 726 + 727 + 728 + 729 + 730 + 731 + 732 + 733 + 734 + 735 + 736 + 737 + 738 + 739 + 740 + 741 + 742 + 743 +
- 1666596205057-567.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -179.8 KB - Content
- image-20221117105556-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -133.3 KB - Content
- image-20221117114459-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -14.9 KB - Content
- image-20221117114842-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -964.1 KB - Content
- image-20221117114937-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -79.1 KB - Content
- image-20221117114949-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -33.4 KB - Content
- image-20221117115010-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -40.4 KB - Content
- image-20221117142300-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -147.8 KB - Content
- image-20221117145932-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -51.9 KB - Content
- image-20221117150312-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -8.7 KB - Content
- image-20221118092935-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -13.1 KB - Content
- image-20221118093144-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -11.7 KB - Content
- image-20221118093512-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -9.5 KB - Content
- image-20221118093658-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -12.7 KB - Content
- image-20221118094227-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -29.2 KB - Content
- image-20221118094449-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -76.5 KB - Content