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, 19 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
- image-20221118103445-7.png
- image-20221118103453-8.png
- image-20221118103547-9.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,67 +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 - 5 - 6 - 7 - 8 - 9 - 10 -**Table of Contents:** 11 - 12 12 {{toc/}} 13 13 6 += **1. Introduction** = 14 14 8 +== **1.1 **What is CPN01 **NB-IoT** Pulse/Contact Sensor == 15 15 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. 16 16 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. 17 17 18 -= 1.Introduction=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. 19 19 20 - ==1.1What isNDS03ANB-IoTOpen/CloseDoorSensor==16 +CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures. 21 21 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 23 -((( 24 -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. 25 -))) 23 + 26 26 27 -((( 28 -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. 29 -))) 25 +== **1.2 Features** == 30 30 31 -((( 32 -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. 33 -))) 34 - 35 -((( 36 -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. 37 -))) 38 - 39 -((( 40 -NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures. 41 -))) 42 - 43 -((( 44 -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. 45 -))) 46 - 47 -((( 48 -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) 49 -))) 50 - 51 -((( 52 -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. 53 -))) 54 - 55 - 56 - 57 -== 1.2 Features == 58 - 59 - 60 60 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 61 61 * Open/Close detect 62 62 * Open/Close statistics 63 63 * Monitor Battery Level 64 -* connecttwodoorsensors31 +* Uplink on periodically and open/close event 65 65 * Datalog feature 66 66 * Uplink periodically 67 67 * Downlink to change configure ... ... @@ -72,43 +72,14 @@ 72 72 * Micro SIM card slot for NB-IoT SIM 73 73 * 8500mAh Battery for long-term use 74 74 42 +== **1.3 Specification** == 75 75 44 +**Common DC Characteristics:** 76 76 77 -== 1.3 Storage & Operation == 78 - 79 - 80 -Temperature -40°C to +85°C 81 - 82 - 83 -== 1.4 Mechanical == 84 - 85 - 86 -[[image:image-20221117114937-4.png]] 87 - 88 - 89 -[[image:image-20221117114949-5.png]] 90 - 91 - 92 -[[image:image-20221117115010-6.png]] 93 - 94 - 95 - 96 -== 1.5 Applications == 97 - 98 - 99 -[[image:image-20221117114842-3.png]] 100 - 101 - 102 - 103 -== 1.6 Specification == 104 - 105 - 106 -(% style="color:blue" %)**Common DC Characteristics:** 107 - 108 108 * Supply Voltage: 2.1v ~~ 3.6v 109 109 * Operating Temperature: -40 ~~ 85°C 110 110 111 - (% style="color:blue" %)**NB-IoT Spec:**49 +**NB-IoT Spec:** 112 112 113 113 * - B1 @H-FDD: 2100MHz 114 114 * - B3 @H-FDD: 1800MHz ... ... @@ -117,98 +117,90 @@ 117 117 * - B20 @H-FDD: 800MHz 118 118 * - B28 @H-FDD: 700MHz 119 119 58 +== **1.4 Installation** == 120 120 60 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event. 121 121 122 - == 1.7 Pin Definitionsand Switch ==62 +[[image:image-20221021110329-1.png]] 123 123 64 +[[image:image-20221022234602-2.png||height="288" width="922"]] 124 124 125 -[[image:image-20221021110429-4.png]] 126 126 67 +== **1.5 Applications** == 127 127 128 -=== 1.7.1 Pin Definition === 69 +* Open/Close Detection 70 +* Pulse meter application 71 +* Dry Contact Detection 129 129 73 +== **1.6 Mechanical** == 130 130 131 - The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to knowmoreabout other pins, please refer to the usermanual of LSN50v2at: [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]75 +[[image:image-20221021110415-3.png]] 132 132 77 +== ** 1.7 Pin Definitions and Switch** == 133 133 79 +[[image:image-20221021110429-4.png]] 134 134 135 -=== 1.7. 2Jumper JP2(PowerON/OFF)===81 +=== **1.7.1 Pin Definition** === 136 136 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]]**. 137 137 138 -Power on Device when putting this jumper. 139 139 86 +=== **1.7.2 Jumper JP2(Power ON/OFF)** === 140 140 88 +Power on Device when putting this jumper. 141 141 142 -=== 1.7.3 BOOT MODE / SW1 === 143 143 91 +=== **1.7.3 BOOT MODE / SW1** === 144 144 145 -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. 146 146 147 - 2)Flash:working mode,thedevicestarts towork for NB-IoT connectionandsendsoutconsoleoutputforfurtherdebugging.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. 148 148 96 +2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging. 149 149 150 150 151 -=== 1.7.4 99 +=== **1.7.4 Reset Button** === 152 152 153 153 154 154 Press to reboot the device. 155 155 156 156 105 +=== **1.7.5 LED** === 157 157 158 -=== 1.7.5 LED === 159 159 160 - 161 161 The LED will blink when : 162 162 163 -1. Boot the device in flash mode 110 +1. Boot the device in flash mode 111 +1. Send an uplink packet 164 164 165 -2. Sendanuplink packet113 += **2. Use CPN01 to communicate with IoT Server** = 166 166 115 +== **2.1 How it works** == 167 167 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. 168 168 169 - ==1.8 MagnetDistance==119 +The diagram below shows the working flow in the default firmware of CPN01: 170 170 171 - 172 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm 173 - 174 -(% style="color:blue" %)**Iron Door:**(%%)** **30 ~~ 45mm 175 - 176 - 177 - 178 -= 2. Use NDS03A to communicate with IoT Server = 179 - 180 -== 2.1 How it works == 181 - 182 - 183 -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. 184 - 185 -The diagram below shows the working flow in the default firmware of NDS03A: 186 - 187 187 [[image:image-20221021110615-5.png]] 188 188 189 189 124 +== **2.2 Configure CPN01** == 190 190 191 -== 2.2 ConfigureNDS03A==126 +=== **2.2.1 Test Requirement** === 192 192 193 - ===2.2.1TestRequirement===128 +To use CPN01 in your city, make sure to meet below requirements: 194 194 195 - 196 -To use NDS03A in your city, make sure to meet below requirements: 197 - 198 198 * Your local operator has already distributed an NB-IoT Network. 199 -* The local NB-IoT network used the band that N DS03Asupports.131 +* The local NB-IoT network used the band that CPN01 supports. 200 200 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 201 201 202 -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. 203 203 204 -[[image:image-20221 117142300-1.png]]136 +[[image:image-20221023000439-3.png]] 205 205 206 206 207 207 140 +=== **2.2.2 Insert NB-IoT SIM card** === 208 208 209 -=== 2.2.2 Insert NB-IoT SIM card === 210 - 211 - 212 212 Insert the NB-IoT Card get from your provider. 213 213 214 214 User needs to take out the NB-IoT module and insert the SIM card like below: ... ... @@ -216,127 +216,101 @@ 216 216 [[image:image-20221021110745-6.png]] 217 217 218 218 149 +=== **2.2.3 Connect USB – TTL to CPN01 and configure it** === 219 219 220 - ===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. 221 221 153 +**Connection:** 222 222 223 - 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 224 224 225 - (%style="color:blue"%)**Connection:**157 + USB TTL TXD <~-~-~-~-> UART_RXD 226 226 227 - (%style="background-color:yellow" %)**USB TTLGND <~-~-~-~->GND**159 + USB TTL RXD <~-~-~-~-> UART_TXD 228 228 229 -(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD** 230 - 231 -(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD** 232 - 233 - 234 234 In the PC, use below serial tool settings: 235 235 236 -* Baud: (% style="color:red" %)**9600** 163 +* Baud: **9600** 164 +* Data bits:** 8** 165 +* Stop bits: **1** 166 +* Parity: **None** 167 +* Flow Control: **None** 237 237 238 - * 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**(%%). 239 239 240 -* Stop bits: (% style="color:red" %)**1** 241 - 242 -* Parity: (% style="color:red" %)**None** 243 - 244 -* Flow Control: (% style="color:red" %)**None** 245 - 246 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%). 247 - 248 248 [[image:image-20221021110817-7.png]] 249 249 250 -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. 251 251 252 252 253 - (% 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]] 254 254 255 255 179 +=== **2.2.4 Use CoAP protocol to uplink data** === 256 256 257 - ===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/]] 258 258 259 259 260 - (% 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:** 261 261 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=0,0,11,2,"mqtt" ** ~/~/Set CoAP resource path 262 262 263 -(% style="color:blue" %)**Use below commands in NDS03A:** 264 - 265 -* (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 266 - 267 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ Set CoAP server address and port 268 - 269 -* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/ Set CoAP resource path 270 - 271 271 For parameter description, please refer to AT command set 272 272 273 273 [[image:image-20221021110948-8.png]] 274 274 275 275 276 -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. 277 277 278 -[[image:image-2022111 8103547-9.png||height="605" width="837"]] 197 +[[image:image-20221021110956-9.png]] 279 279 280 280 200 +=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** === 281 281 282 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 283 283 203 +**AT Commands:** 284 284 285 -(% 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 286 286 287 -* (% style="color:#037691" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 288 - 289 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ Set UDP server address and port 290 - 291 -* (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 292 - 293 293 [[image:image-20221021111025-10.png]] 294 294 295 - 296 296 [[image:image-20221021111033-11.png||height="241" width="576"]] 297 297 298 298 299 299 215 +=== **2.2.6 Use MQTT protocol to uplink data** === 300 300 301 -=== 2.2.6 Use MQTT protocol to uplink data === 302 302 218 +**AT Commands:** 303 303 304 -(% 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 305 305 306 - *(% style="color:#037691" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTTprotocol to uplink228 + [[image:image-20221021111058-12.png]] 307 307 308 - * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ SetMQTT server address and port230 +[[image:image-20221021111201-16.png||height="472" width="653"]] 309 309 310 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT ** (%%) ~/~/ Set up the CLIENT of MQTT 311 - 312 -* (% style="color:#037691" %)**AT+UNAME=UNAME **(%%)** **~/~/ Set the username of MQTT 313 - 314 -* (% style="color:#037691" %)**AT+PWD=PWD **(%%)** **~/~/ Set the password of MQTT 315 - 316 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB **(%%)** **~/~/ Set the sending topic of MQTT 317 - 318 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB ** (%%) ~/~/ Set the subscription topic of MQTT 319 - 320 - [[image:image-20221118103445-7.png]] 321 - 322 - 323 -[[image:image-20221118103453-8.png||height="608" width="841"]] 324 - 325 325 326 326 327 327 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. 328 328 329 329 237 +=== **2.2.7 Use TCP protocol to uplink data** === 330 330 331 - === 2.2.7 UseTCPprotocol to uplinkdata ===239 +**AT Commands** 332 332 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 333 333 334 -(% style="color:blue" %)**AT Commands:** 335 - 336 -* (% style="color:#037691" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 337 - 338 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ Set TCP server address and port 339 - 340 340 [[image:image-20221021111125-14.png]] 341 341 342 342 [[image:image-20221021111131-15.png]] ... ... @@ -343,99 +343,73 @@ 343 343 344 344 345 345 250 +=== **2.2.8 Change Update Interval** === 346 346 347 - ===2.2.8ChangeUpdateInterval===252 +User can use below command to change the **uplink interval**. 348 348 254 +* **AT+TDC=7200 ** ~/~/ Set Update Interval to 7200s (2 hours) 349 349 350 - User can use below command to change the (% style="color:blue" %)**uplink interval**.256 +**NOTE:** 351 351 352 -* (% style="color:#037691"%)**AT+TDC=14400**(%%)~/~/ SetUpdateIntervalto14400s(4hours)258 +**~1. By default, the device will send an uplink message every 1 hour.** 353 353 354 -(% style="color:red" %)**NOTE:** 355 355 356 - 1.By default, the device will send an uplinkmessage every4 hour.261 +== **2.3 Uplink Payload** == 357 357 263 +The uplink payload includes 123 bytes in total by default. 358 358 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. 359 359 360 -== 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 361 361 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" %) 362 362 363 - 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. 364 364 365 - 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"]] 366 366 367 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:** 368 - 369 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %) 370 -|=(% 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** 371 -|=(% 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.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14) 372 - 373 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %) 374 -|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)((( 375 -**1-32 group** 376 -))) 377 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% 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" %)... 378 - 379 - 380 - 381 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:** 382 - 383 - 384 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %) 385 -|=(% 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** 386 -|=(% 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(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14) 387 - 388 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %) 389 -|(% 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** 390 -|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14) 391 - 392 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %) 393 -|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)((( 394 -**1-32 group** 395 -))) 396 -|(% 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>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)...... 397 - 398 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data. 399 - 400 -[[image:image-20221117145932-2.png]] 401 - 402 - 403 403 The payload is ASCII string, representative same HEX: 404 404 405 -**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 //(%%)** 406 406 407 -**where:** 282 +where: 283 +*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317 408 408 409 -* Device ID:**(%%) 0xf867787050213317 = f867787050213317285 +*(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0 410 410 411 -* Version:**(%%)064=100=1.0.0287 +*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V 412 412 413 -* BAT:**(%%)0ccf = 3279mV=3.279V289 +*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23 414 414 415 -* Singal:9=25291 +*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1 416 416 417 -* Mod:**(%%)1=1293 +*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00=0 418 418 419 -* DoorStatus:**(%%)295 +*(% style="color:#037691" %) **Contact Status:**(%%) 0x00=0 420 420 421 -* Status:297 +*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0 422 422 423 -* dooropen num:**(%%)0x000016=22299 +*(% style="color:#037691" %) **Total pulse:0x09 =0** 424 424 425 -* me:00017=23301 +*(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2 426 426 427 -* 7590df=1668649183(Unix Time)303 +*(% style="color:#037691" %)** Time stamp :**(%%) 0x6315537b =1662342011 (Unix Time) 428 428 305 +*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 01 00000b 02 000026 63510fed 429 429 307 +*(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,....... 430 430 431 -== 2.4 Payload Explanation and Sensor Interface == 432 432 433 -== =2.4.1Device ID===310 +== **2.4 Payload Explanation and Sensor Interface** == 434 434 312 +=== **2.4.1 Device ID** === 435 435 436 436 By default, the Device ID is equal to the last 15 bits of IMEI. 437 437 438 -User can use (% style="color:blue" %)**AT+DEUI**(%%)to set Device ID316 +User can use **AT+DEUI** to set Device ID 439 439 440 440 **Example:** 441 441 ... ... @@ -444,27 +444,24 @@ 444 444 The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID. 445 445 446 446 447 -=== 2.4.2 Version Info === 325 +=== **2.4.2 Version Info** === 448 448 449 - 450 450 Specify the software version: 0x64=100, which means firmware version 1.00. 451 451 452 -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. 453 453 454 454 455 -=== 2.4.3 Battery Info === 332 +=== **2.4.3 Battery Info** === 456 456 334 +Check the battery voltage for CPN01. 457 457 458 -Check the battery voltage for NDS03A. 459 - 460 460 Ex1: 0x0B45 = 2885mV 461 461 462 462 Ex2: 0x0B49 = 2889mV 463 463 464 464 465 -=== 2.4.4 Signal Strength === 341 +=== **2.4.4 Signal Strength** === 466 466 467 - 468 468 NB-IoT Network signal Strength. 469 469 470 470 **Ex1: 0x1d = 29** ... ... @@ -480,45 +480,62 @@ 480 480 **99** Not known or not detectable 481 481 482 482 483 -=== 2.4.5 Disalarm: (default:0)===358 +=== **2.4.5 Calculate Flag** === 484 484 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. 485 485 486 - (%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. 487 487 488 - (% 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. 489 489 490 - ( %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 491 491 492 492 493 -=== 2.4.6 KeepStatus & Keep Time===369 +=== **2.4.6 Alarm** === 494 494 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]] 495 495 496 -Shows the configure value of Alarm Base on Timeout Feature 497 497 374 +=== **2.4.7 Contact Status** === 498 498 499 - ===2.4.7 Timestamp===376 +0: Open 500 500 378 +1: Close 501 501 502 -Timestamp : 0x6315537b =1662342011 503 503 381 +=== **2.4.8 Total pulse** === 504 504 505 - ===2.4.8 SwitchDualChannelMode===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]] 506 506 385 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215 507 507 508 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function. 509 509 388 +=== **2.4.9 The last open duration** === 510 510 511 - == 2.5DownlinkPayload ==390 +Dry Contact last open duration. 512 512 392 +Unit: min. 513 513 514 - By default, NDS03Aprints thedownlink payloado console port.394 +[[image:image-20221021111346-17.png||height="146" width="770"]] 515 515 516 -[[image:image-20221021111414-18.png]] 517 517 397 +=== **2.4.10 Timestamp** === 518 518 399 +Timestamp : 0x6315537b =1662342011 400 + 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 + 519 519 **Examples:** 520 520 521 -* (% style="color:#037691" %)**Set TDC**413 +* **Set TDC** 522 522 523 523 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 524 524 ... ... @@ -526,237 +526,172 @@ 526 526 527 527 Payload: 01 00 00 3C TDC=60S 528 528 529 -* (% style="color:#037691" %)**Reset**421 +* **Reset** 530 530 531 -If payload = 0x04FF, it will reset the N DS03A423 +If payload = 0x04FF, it will reset the NSE01 532 532 533 -* (% style="color:#037691" %)**INTMOD**425 +* **INTMOD** 534 534 535 535 Downlink Payload: 06000003, Set AT+INTMOD=3 536 536 429 +== **2.6 LED Indicator** == 537 537 538 - ==2.6LEDIndicator==431 +The CPN01 has an internal LED which is to show the status of different states. 539 539 540 - 541 -The NDS03A has an internal LED which is to show the status of different states. 542 - 543 543 * When the device starts normally, the LED will light up for 1 second. 544 -* After N DS03Ajoin NB-IoT network. The LED will be ON for 3 seconds.434 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds. 545 545 * For each uplink probe, LED will be on for 500ms. 546 546 437 +== **2.7 Alarm Base on Timeout** == 547 547 439 +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: 548 548 549 -== 2.7 Alarm Base on Timeout == 550 550 442 +**~1. Keep Status: Status to be monitor** 551 551 552 -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: 553 - 554 - 555 -(% style="color:blue" %)**1. Keep Status: Status to be monitor** 556 - 557 557 Keep Status = 1: Monitor Close to Open event 558 558 559 559 Keep Status = 0: Monitor Open to Close event 560 560 561 561 562 - (% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**449 +**2. Keep Time: Timeout to send an Alarm** 563 563 564 564 Range 0 ~~ 65535(0xFFFF) seconds. 565 565 566 566 If keep time = 0, Disable Alarm Base on Timeout feature. 567 567 568 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn 't change after timeout.455 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout. 569 569 570 570 571 - (% style="color:blue" %)**AT Command to configure:**458 +**AT Command** to configure: 572 572 573 - (%style="color:blue"%)**PB14PIN:**460 +**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. 574 574 575 - (% 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.462 +**AT+TTRIG=0,0 ** ~-~-> Default Value, disable timeout Alarm. 576 576 577 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm. 578 578 465 +== **2.8 Set debug mode** == 579 579 580 -(% style="color:blue" %)**PB15 PIN:** 581 - 582 -(% style="color:#037691" %)**AT+TTRIG2=1,30** 583 - 584 -(% style="color:#037691" %)**AT+TTRIG2=0,0 ** 585 - 586 - 587 -== 2.8 Set debug mode == 588 - 589 - 590 590 Feature: Enable or Disable debug mode 591 591 592 -(% style="color:blue" %)**AT Command: AT+DEBUG** 593 593 470 +**AT Command: AT+DEBUG** 471 + 594 594 [[image:image-20221021111629-21.png]] 595 595 474 +== **2.9 Clear Flash Record** == 596 596 597 - 598 -== 2.9 Clear Flash Record == 599 - 600 - 601 601 Feature: Clear flash storage for data log feature. 602 602 603 - (% style="color:blue" %)**AT Command: AT+CLRDTA**478 +**AT Command: AT+CLRDTA** 604 604 605 605 [[image:image-20221021111527-19.png]] 606 606 482 +== ** 2.10 Set trigger mode** == 607 607 484 +➢ AT Command: **AT+TTRMOD** 608 608 609 - ==2.10CountMod==486 +Feature: Set the trigger interrupt mode. 610 610 488 +[[image:image-20221021111552-20.png]] 611 611 612 - (%style="color:blue"%)**AT Command: AT+COUNTMOD**490 +== **2.11 Set the calculate flag** == 613 613 614 - [[image:image-20221118092935-1.png]]492 +Feature: Set the calculate flag 615 615 494 +**AT Command: AT+CALCFLAG** 616 616 496 +[[image:image-20221021111711-22.png]] 617 617 618 -== 2.1 1InterruptPinChannelMod==498 +== **2.12 Set count number** == 619 619 500 +Feature: Manually set the count number 620 620 621 - (% style="color:blue" %)**AT Command: AT+TTRCHANNEL**502 +**AT Command: AT+SETCNT** 622 622 623 -[[image:image-2022111 8093144-2.png]]504 +[[image:image-20221021111748-24.png]] 624 624 506 +== **2.13 Set the number of data to be uploaded and the recording time** == 625 625 508 +➢ AT Command: 626 626 627 - == 2.12TTRIG1/2timeout statusalarm==510 +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) 628 628 629 629 630 - It needs to be used withAT+TTRIG1or AT+TTRIG2. WhenTTRIG1 or TTRIG2 timesoutandcausesanalarm, andthestatus does not changesubsequently,an alarmpacketwillbesentatthe alarminterval.513 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 631 631 632 - (%style="color:blue"%)**AT Command:AT+TTRALARM**515 +== **2.14 Read or Clear cached data** == 633 633 634 - [[image:image-20221118093512-3.png]]517 +➢ AT Command: 635 635 519 +AT+CDP ~/~/ Read cached data 636 636 521 +[[image:image-20221021111810-25.png||height="364" width="797"]] 637 637 638 -== 2.13 Select counting mode == 639 639 524 +AT+CDP=0 ~/~/ Clear cached data 640 640 641 - (% style="color:blue"%)**ATCommand:AT+TTRMODx=a,b**526 +== **2.15 Firmware Change Log** == 642 642 643 - When(% style="color:red"%)**a=0**(%%), thedoor isened tount,andwhen(% style="color:red" %)**a=1**(%%),the closeddoor iscounted.528 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]] 644 644 645 - When (% style="color:red" %)**b=0**(%%), it is thelastdooropen duration,andwhen (%style="color:red" %)**b=1**(%%),the lastdoorcloseduration.530 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 646 646 647 - [[image:image-20221118093658-4.png]]532 +== **2.16 Battery Analysis** == 648 648 534 +=== **2.16.1 Battery Type** === 649 649 536 +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. 650 650 651 - 652 -== 2.14 Set the number of data to be uploaded and the recording time == 653 - 654 - 655 -(% style="color:blue" %)**AT Command:** 656 - 657 -(% 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) 658 - 659 -(% 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. 660 - 661 - 662 -== 2.15 Read or Clear cached data == 663 - 664 - 665 -(% style="color:blue" %)**AT Command:** 666 - 667 -(% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 668 - 669 -(% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 670 - 671 -[[image:image-20221118094227-5.png]] 672 - 673 - 674 - 675 -== 2.16 Firmware Change Log == 676 - 677 - 678 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]] 679 - 680 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 681 - 682 - 683 - 684 -== 2.17 Battery Analysis == 685 - 686 - 687 -=== 2.17.1 Battery Type === 688 - 689 - 690 -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. 691 - 692 692 The battery is designed to last for several years depends on the actual use environment and update interval. 693 693 694 694 The battery-related documents as below: 695 695 696 696 * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 697 - 698 698 * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 699 - 700 700 * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 701 701 702 702 [[image:image-20221021111911-26.png]] 703 703 548 +=== **2.16.2 Power consumption Analyze** === 704 704 705 - 706 -=== 2.17.2 Power consumption Analyze === 707 - 708 - 709 709 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. 710 710 711 711 Instruction to use as below: 712 712 713 - (% 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/]]554 +**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/]] 714 714 715 - (% style="color:blue" %)**Step 2: **(%%)Open it and choose556 +**Step 2: ** Open it and choose 716 716 717 717 * Product Model 718 - 719 719 * Uplink Interval 720 - 721 721 * Working Mode 722 722 723 723 And the Life expectation in difference case will be shown on the right. 724 724 725 -[[image: 1666596205057-567.png]] 564 +[[image:image-20221021111923-27.png||height="253" width="783"]] 726 726 566 +=== **2.16.3 Battery Note** === 727 727 728 - 729 -=== 2.17.3 Battery Note === 730 - 731 - 732 732 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. 733 733 570 +=== **2.16.4 Replace the battery** === 734 734 572 +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). 735 735 736 -=== 2.17.4 Replace the battery === 737 737 575 += **3. Access NB-IoT Module** = 738 738 739 -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). 740 - 741 - 742 - 743 -= 3. Access NB-IoT Module = 744 - 745 - 746 746 Users can directly access the AT command set of the NB-IoT module. 747 747 748 748 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/]] 749 749 750 -[[image:image-2022111 8094449-6.png]] 581 +[[image:image-20221021112006-28.png]] 751 751 583 += **4. Using the AT Commands** = 752 752 585 +== **4.1 Access AT Commands** == 753 753 754 -= 4. Using the AT Commands = 755 - 756 - 757 -== 4.1 Access AT Commands == 758 - 759 - 760 760 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]] 761 761 762 762 AT+<CMD>? : Help on <CMD> ... ... @@ -767,9 +767,8 @@ 767 767 768 768 AT+<CMD>=? : Get the value 769 769 597 +**General Commands** 770 770 771 -(% style="color:blue" %)**General Commands** 772 - 773 773 AT : Attention 774 774 775 775 AT? : Short Help ... ... @@ -792,41 +792,35 @@ 792 792 793 793 AT+SERVADDR : Server Address 794 794 795 -AT+TR : 621 +AT+TR : Get or Set record time" 796 796 623 + 797 797 AT+NOUD : Get or Set the number of data to be uploaded 798 798 799 -AT+CDP : Read or Clear cached data 800 800 801 -AT+ EBUG:Enable orDisabledebugmode627 +AT+CDP : Read or Clear cached data 802 802 803 -AT+ TTRIG1 : Get or Set PB14 PIN Alarm Base on Timeout 804 804 805 -AT+ TTRIG2:GetorSetPB15 PIN Alarm Baseon Timeout630 +AT+ DEBUG : Enable or Disable debug mode 806 806 807 -AT+ COUNTMOD:thecountmode632 +AT+ TTRIG : Get or Set Alarm Base on Timeout 808 808 809 -AT+TTR CHANNEL: Get or Set thenumberofinterruptchannels634 +AT+ TTRMOD : Get or Set the trigger interrupt mode(0:falling,1:rising) 810 810 811 -AT+ TTRALARMTTRIG1 of Alarm interval(unit: minute)636 +AT+ CALCFLAG : Get or Set the calculate flag 812 812 813 -AT+ DISALARM:Enable/Disable Alarmfor door open/close or water leak event638 +AT+ CLRC : Clear current door open count 814 814 815 -A T+CLRC : Clear current door opencount640 +**COAP Management** 816 816 817 - 818 -(% style="color:blue" %)**COAP Management** 819 - 820 820 AT+URI : Resource parameters 821 821 644 +**UDP Management** 822 822 823 -(% style="color:blue" %)**UDP Management** 824 - 825 825 AT+CFM : Upload confirmation mode (only valid for UDP) 826 826 648 +**MQTT Management** 827 827 828 -(% style="color:blue" %)**MQTT Management** 829 - 830 830 AT+CLIENT : Get or Set MQTT client 831 831 832 832 AT+UNAME : Get or Set MQTT Username ... ... @@ -837,65 +837,86 @@ 837 837 838 838 AT+SUBTOPIC : Get or Set MQTT subscription topic 839 839 660 +**Information** 840 840 841 -(% style="color:blue" %)**Information** 842 - 843 843 AT+FDR : Factory Data Reset 844 844 845 845 AT+PWORD : Serial Access Password 846 846 666 += **5. FAQ** = 847 847 668 +== **5.1 How to Upgrade Firmware** == 848 848 849 - =5.FAQ=670 +User can upgrade the firmware for 1) bug fix, 2) new feature release. 850 850 672 +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]] 851 851 852 - ==5.1HowtoUpgradeFirmware==674 +**Notice, **CPN01 **and **CPL01 **share the same mother board. They use the same connection and method to update.** 853 853 854 854 855 - Usercanupgradethe firmware for 1) bug fix, 2)newfeature release.677 += **6. Trouble Shooting** = 856 856 857 - 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]]679 +== **6.1 Connection problem when uploading firmware** == 858 858 859 - (% style="color:red"%)**Notice: **(% style="color:blue"%)**NDS03A** (%%)**and(%yle="color:blue"%)LDS03A(%%)**(%style="color:blue" %) (%%)**sharethe sameotherboard. They usethe sameconnectionnd methodpdate.**681 +**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]] 860 860 861 861 684 +== **6.2 AT Command input doesn't work** == 862 862 863 - =6.TroubleShooting=686 +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. 864 864 865 865 866 -= =6.1Connectionproblemwhenuploadingfirmware==689 += **7. Order Info** = 867 867 691 +Part Number**:** CPN01 868 868 869 -(% 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]] 870 870 694 += **8. Packing Info** = 871 871 696 +**Package Includes**: 872 872 873 -== 6.2 AT Command input doesn't work == 698 +* CPN01 Open/Close Sensor x 1 699 +* External antenna x 1 874 874 701 +**Dimension and weight**: 875 875 876 -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. 703 +* Size: 195 x 125 x 55 mm 704 +* Weight: 420g 877 877 706 += **9. Support** = 878 878 708 +* 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. 709 +* 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]] 879 879 880 - = 7.Order Info =711 + 881 881 882 882 883 -Part Number**:** NDS03A 884 884 885 885 886 886 887 -= 8. Packing Info = 888 888 889 889 890 -(% style="color:blue" %)**Package Includes**: 891 891 892 -* NDS03A Open/Close Door Sensor x 1 893 893 894 -= 9. Support = 895 895 896 896 897 -* 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. 898 898 899 -* 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]] 900 900 901 - 725 + 726 + 727 + 728 + 729 + 730 + 731 + 732 + 733 + 734 + 735 + 736 + 737 + 738 + 739 + 740 + 741 + 742 +
- 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
- image-20221118103445-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -20.4 KB - Content
- image-20221118103453-8.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -46.2 KB - Content
- image-20221118103547-9.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -43.5 KB - Content