Changes for page NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 17:03
Change comment:
Uploaded new attachment "image-20221021112006-28.png", version {1}
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 19 removed)
- 1666596205057-567.png
- image-20221022234529-1.png
- image-20221022234602-2.png
- image-20221023000439-3.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,69 +1,36 @@ 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"]] 3 3 4 4 5 +**~1. Introduction** 5 5 7 +**1.1 **What is CPN01 **NB-IOT** Pulse/Contact Sensor 6 6 9 +The Dragino CPL01 is a **NB-IOT Contact Sensor**. It detects open/close status and uplink to IoT server via LoRaWAN network. user can see the dry contact status, open time, open counts in the IoT Server. 7 7 11 +The CPL01 will send periodically data every day as well as for each dry contact action. It also counts the contact open times and calculate last open duration. User can also disable the uplink for each open/close event, instead, device can count each open event and uplink periodically. 8 8 13 +CPL01 has the open alarm feature, user can set this feature so device will send Alarm if the contact has been open for a certain time. 9 9 10 - **Table ofContents:**15 +CPL01 is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures. 11 11 12 -{{toc/}} 17 +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. 18 +\\CPN01 supports different uplink methods include **TCP,MQTT,UDP and CoAP **for different application requirement. 19 +\\CPN01 is powered by **8500mAh Li-SOCI2 battery**, It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 20 +\\To use CPN01, user needs to check if there is NB-IoT coverage in local area and with the bands CPN01 supports. If the local operate support it, user needs to get a **NB-IoT SIM card** from local operator and install CPN01 to get NB-IoT network connection 13 13 22 + 14 14 15 15 25 +**1.2 Features** 16 16 17 - 18 -= 1. Introduction = 19 - 20 -== 1.1 What is NDS03A NB-IoT Open/Close Door Sensor == 21 - 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 -))) 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 -))) 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 -* Uplink periodically 33 +* Uplink on periodically 67 67 * Downlink to change configure 68 68 * Wall Mountable 69 69 * Outdoor Use ... ... @@ -70,43 +70,16 @@ 70 70 * Ultra-Low Power consumption 71 71 * AT Commands to change parameters 72 72 * Micro SIM card slot for NB-IoT SIM 73 -* 8500mAh Battery for long -term use40 +* 8500mAh Battery for long term use 74 74 75 - ==1.3 Storage & Operation==42 +**1.3 Specification** 76 76 44 +**Common DC Characteristics:** 77 77 78 -Temperature -40°C to +85°C 79 - 80 - 81 -== 1.4 Mechanical == 82 - 83 - 84 -[[image:image-20221117114937-4.png]] 85 - 86 - 87 -[[image:image-20221117114949-5.png]] 88 - 89 - 90 -[[image:image-20221117115010-6.png]] 91 - 92 - 93 - 94 -== 1.5 Applications == 95 - 96 - 97 -[[image:image-20221117114842-3.png]] 98 - 99 - 100 - 101 -== 1.6 Specification == 102 - 103 - 104 -(% style="color:blue" %)**Common DC Characteristics:** 105 - 106 106 * Supply Voltage: 2.1v ~~ 3.6v 107 107 * Operating Temperature: -40 ~~ 85°C 108 108 109 - (% style="color:blue" %)**NB-IoT Spec:**49 +**NB-IoT Spec:** 110 110 111 111 * - B1 @H-FDD: 2100MHz 112 112 * - B3 @H-FDD: 1800MHz ... ... @@ -115,36 +115,47 @@ 115 115 * - B20 @H-FDD: 800MHz 116 116 * - B28 @H-FDD: 700MHz 117 117 118 - ==1.7PinDefinitions and Switch ==58 +**1.4 Installation** 119 119 60 +Connect CPL01 to an Open Close sensor like below. So it can detect the open/close event. 120 120 121 -[[image:image -20221021110429-4.png]]62 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image001.png]] [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image002.png]] 122 122 64 +**1.5 Applications** 123 123 124 -=== 1.7.1 Pin Definition === 66 +* Open/Close Detection 67 +* Pulse meter application 68 +* Dry Contact Detection 125 125 70 +**1.6 Mechanical** 126 126 127 - The deviceis pre-configured to connect to a doorsensor. The other pinsare not used.If user wants to know more about otherpins,please referto the user manual ofLSN50v2 at: [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]72 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image003.png]] 128 128 74 +**~ 1.7 Pin Definitions and Switch** 129 129 76 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image004.png]] 130 130 131 - ===1.7.2Jumper JP2(Power ON/OFF) ===78 +**1.7.1 Pin Definition** 132 132 80 +CPL01 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 user manual of LSN50v2 at: [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>url:https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]] 133 133 82 +**1.7.2 Jumper JP2(Power ON/OFF)** 83 + 84 + 134 134 Power on Device when putting this jumper. 135 135 136 136 137 137 138 - ===1.7.3===89 +**1.7.3 BOOT MODE / SW1** 139 139 140 140 141 -1) The firmware won't run.92 +1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 142 142 143 -2) ingmode, the device starts to workfor NB-IoT connectionand sendsout console output for further debugging.94 +2) Flash: work mode, the device starts to work and send out console output for further debug 144 144 145 145 146 146 147 - ===1.7.4===98 +**1.7.4 Reset Button** 148 148 149 149 150 150 Press to reboot the device. ... ... @@ -151,313 +151,214 @@ 151 151 152 152 153 153 154 - ===1.7.5===105 +**1.7.5 LED** 155 155 156 156 157 - TheLEDwillblink when:108 +It will flash: 158 158 159 -1. Boot the device in flash mode 110 +1. Boot the device in flash mode 111 +1. Send an uplink packet 160 160 161 -2. Send an uplink packet 162 162 114 +**2. Use CPN01 to communicate with IoT Server** 163 163 116 +**2.1 How it works** 164 164 165 - ==1.8MagnetDistance==118 +The CPN01 is equipped with a NB-IoT module, the pre-loaded firmware in CPN01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01. 166 166 120 +The diagram below shows the working flow in default firmware of CPN01: 167 167 168 - (%style="color:blue"%)**Wood Door:**(%%)10~~ 30mm122 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image005.png||alt="说明: image-20220708101605-2.png"]] 169 169 170 - (%style="color:blue"%)**IronDoor:**(%%)** **30 ~~ 45mm124 +**2.2 Configure the CPN01** 171 171 126 +**2.2.1 Test Requirement** 172 172 128 +To use CPN01 in your city, make sure meet below requirements: 173 173 174 -= 2. Use NDS03A to communicate with IoT Server = 175 - 176 -== 2.1 How it works == 177 - 178 - 179 -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. 180 - 181 -The diagram below shows the working flow in the default firmware of NDS03A: 182 - 183 -[[image:image-20221021110615-5.png]] 184 - 185 - 186 - 187 -== 2.2 Configure NDS03A == 188 - 189 -=== 2.2.1 Test Requirement === 190 - 191 - 192 -To use NDS03A in your city, make sure to meet below requirements: 193 - 194 -* Your local operator has already distributed an NB-IoT Network. 195 -* The local NB-IoT network used the band that NDS03A supports. 130 +* Your local operator has already distributed a NB-IoT Network there. 131 +* The local NB-IoT network used the band that CPN01 supports. 196 196 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 197 197 198 -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 199 199 200 -[[image:image-20221117142300-1.png]] 201 - 202 202 203 203 138 +**2.2.2 Insert SIM card** 204 204 205 -=== 2.2.2 Insert NB-IoT SIM card === 206 - 207 - 208 208 Insert the NB-IoT Card get from your provider. 209 209 210 -User need sto take out the NB-IoT module and insert the SIM card like below:142 +User need to take out the NB-IoT module and insert the SIM card like below: 211 211 212 -[[image:image -20221021110745-6.png]] 144 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image006.png||alt="说明: 1657249468462-536.png"]] 213 213 146 +**2.2.3 Connect USB – TTL to CPN01 to configure it** 214 214 148 +User need to configure CPN01 via serial port to set the **Server Address** / **Uplink Topic** to define where and how-to uplink packets. CPN01 support AT Commands, user can use a USB to TTL adapter to connect to CPN01 and use AT Commands to configure it, as below. 215 215 216 - === 2.2.3ConnectUSB – TTL toNDS03A and configure it ===150 +**Connection:** 217 217 152 + USB TTL GND <~-~-~-~-> GND 218 218 219 - 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 to NDS03AanduseATCommands to configure it, as below.154 + USB TTL TXD <~-~-~-~-> UART_RXD 220 220 221 - (%style="color:blue"%)**Connection:**156 + USB TTL RXD <~-~-~-~-> UART_TXD 222 222 223 -(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND** 224 - 225 -(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD** 226 - 227 -(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD** 228 - 229 - 230 230 In the PC, use below serial tool settings: 231 231 232 -* Baud: (% style="color:red" %)**9600** 160 +* Baud: **9600** 161 +* Data bits:** 8** 162 +* Stop bits: **1** 163 +* Parity: **None** 164 +* Flow Control: **None** 233 233 234 - * Databits:** (%style="color:red"%)8(%%)**166 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on CPN01. CPN01 will output system info once power on as below, we can enter the **password: 12345678** to access AT Command input. 235 235 236 - * Stop bits:(%style="color:red" %)**1**168 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image007.png]] 237 237 238 -* Parity:(%style="color:red" %)**None**170 +**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]] 239 239 240 -* FlowControl: (% style="color:red"%)**None**172 +**2.2.4 Use CoAP protocol to uplink data** 241 241 242 - Makesurethe switchis inFLASH position, thenpoweronNDS03A byconnecting the(% style="color:orange" %)**YellowJumper**(%%).174 +**Note: if you don't have CoAP server, you can refer this link to set up one: **[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 243 243 244 - [[image:image-20221021110817-7.png]]176 +**Use below commands:** 245 245 246 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input. 178 +* **AT+PRO=1** ~/~/ Set to use CoAP protocol to uplink 179 +* **AT+SERVADDR=120.24.4.116,5683 ** ~/~/ to set CoAP server address and port 180 +* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path 247 247 248 - 249 -(% 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]] 250 - 251 - 252 - 253 -=== 2.2.4 Use CoAP protocol to uplink data === 254 - 255 - 256 -(% style="color:red" %)**Note: if you don't have a CoAP server, you can refer this link to set up a CoAP server: **(%%)[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 257 - 258 - 259 -(% style="color:blue" %)**Use below commands in NDS03A:** 260 - 261 -* (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 262 - 263 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ Set CoAP server address and port 264 - 265 -* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/ Set CoAP resource path 266 - 267 267 For parameter description, please refer to AT command set 268 268 269 -[[image:i mage-20221021110948-8.png]]184 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image008.png]] 270 270 186 +After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server. 271 271 272 - After configuring thever addressand (% style="color:green" %)**resetNDS03A**(%%) (via AT+ATZ ), NDS03A willstart to uplink sensor values to the CoAP server.188 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image009.png]] 273 273 274 - [[image:image-20221021110956-9.png]]190 +**2.2.5 Use UDP protocol to uplink data(Default protocol)** 275 275 192 +This feature is supported since firmware version v1.0.1 276 276 194 +* **AT+PRO=2 ** ~/~/ Set to use UDP protocol to uplink 195 +* **AT+SERVADDR=120.24.4.116,5601 ** ~/~/ to set UDP server address and port 196 +* **AT+CFM=1 ** ~/~/If the server does not respond, this command is unnecessary 277 277 278 - ===2.2.5UseUDPprotocol to uplink data(Defaultprotocol) ===198 + [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image010.png]] 279 279 200 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image011.png||alt="说明: 1657249930215-289.png"]] 280 280 281 -(% style="color:blue" %)**AT Commands:** 282 - 283 -* (% style="color:#037691" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 284 - 285 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ Set UDP server address and port 286 - 287 -* (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 288 - 289 - [[image:image-20221021111025-10.png]] 290 - 291 - 292 -[[image:image-20221021111033-11.png||height="241" width="576"]] 293 - 294 294 295 295 204 +**2.2.6 Use MQTT protocol to uplink data** 296 296 297 - ===2.2.6UseMQTTprotocolto uplinkdata===206 +This feature is supported since firmware version v110 298 298 208 +* **AT+PRO=3 ** ~/~/Set to use MQTT protocol to uplink 209 +* **AT+SERVADDR=120.24.4.116,1883 ** ~/~/Set MQTT server address and port 210 +* **AT+CLIENT=CLIENT ** ~/~/Set up the CLIENT of MQTT 211 +* **AT+UNAME=UNAME **~/~/Set the username of MQTT 212 +* **AT+PWD=PWD **~/~/Set the password of MQTT 213 +* **AT+PUBTOPIC=NSE01_PUB **~/~/Set the sending topic of MQTT 214 +* **AT+SUBTOPIC=NSE01_SUB ** ~/~/Set the subscription topic of MQTT 299 299 300 - (%style="color:blue" %)**ATCommands:**216 + [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image012.png]] 301 301 302 - * (% style="color:#037691" %)**AT+PRO=3 ** (%%) ~/~/Set to useQTTprotocoltouplink218 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image013.png]] 303 303 304 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 305 - 306 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT ** (%%) ~/~/ Set up the CLIENT of MQTT 307 - 308 -* (% style="color:#037691" %)**AT+UNAME=UNAME **(%%)** **~/~/ Set the username of MQTT 309 - 310 -* (% style="color:#037691" %)**AT+PWD=PWD **(%%)** **~/~/ Set the password of MQTT 311 - 312 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB **(%%)** **~/~/ Set the sending topic of MQTT 313 - 314 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB ** (%%) ~/~/ Set the subscription topic of MQTT 315 - 316 - [[image:image-20221021111058-12.png]] 317 - 318 - 319 -[[image:image-20221021111201-16.png||height="472" width="653"]] 320 - 321 321 322 322 323 -MQTT protocol has a much higher power consumption compare withUDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.222 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 324 324 224 +**2.2.7 Use TCP protocol to uplink data** 325 325 226 +This feature is supported since firmware version v110 326 326 327 -=== 2.2.7 Use TCP protocol to uplink data === 228 +* **AT+PRO=4 ** ~/~/ Set to use TCP protocol to uplink 229 +* **AT+SERVADDR=120.24.4.116,5600 ** ~/~/ to set TCP server address and port 328 328 231 + [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image014.png]] 329 329 330 - (% style="color:blue" %)**ATCommands:**233 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image015.png||alt="说明: 1657250255956-604.png"]] 331 331 332 -* (% style="color:#037691" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 333 - 334 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ Set TCP server address and port 335 - 336 - [[image:image-20221021111125-14.png]] 337 - 338 -[[image:image-20221021111131-15.png]] 339 - 340 340 341 341 237 +**2.2.8 Change Update Interval** 342 342 343 - ===2.2.8ChangeUpdateInterval===239 +User can use below command to change the **uplink interval**. 344 344 241 +* **AT+TDC=600 ** ~/~/ Set Update Interval to 600s 345 345 346 - User can use below command to change the (% style="color:blue" %)**uplink interval**.243 +**NOTE:** 347 347 348 -* (% style="color:#037691"%)**AT+TDC=14400**(%%)~/~/ SetUpdateIntervalto14400s(4hours)245 +**~1. By default, the device will send an uplink message every 1 hour.** 349 349 350 - (%style="color:red" %)**NOTE:**247 +**2.3 Uplink Payload** 351 351 352 - 1.Bydefault,thedevicewillsendan uplinkmessageevery4 hour.249 +In this mode, uplink payload includes 87 bytes in total by default. 353 353 251 +Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded. 354 354 253 +|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**2**|**2**|4 254 +|**Value**|[[Device ID>>path:#H2.4.1A0A0DeviceID]]|[[Ver>>path:#H2.4.2A0VersionInfo]]|[[BAT>>path:#H2.4.3A0BatteryInfo]]|[[Signal Strength>>path:#H2.4.4A0SignalStrength]]|MOD|[[Interrupt>>path:#H2.4.8A0DigitalInterrupt]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|Time stamp 355 355 356 -== 2.3 Uplink Payload == 357 357 257 +|2|2|4|8 group 258 +|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|... 358 358 359 - The uplinkpayloadincludes26bytes intotalbydefault.260 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data. 360 360 361 - Each timethe device uploads a data package. The usercan use theAT+NOUDcommandto upload the recorded data.Upto 32setsof recorded datacan be uploaded.262 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image016.png]] 362 362 363 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:** 364 - 365 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %) 366 -|=(% 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** 367 -|=(% 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) 368 - 369 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %) 370 -|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)((( 371 -**1-32 group** 372 -))) 373 -|(% 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" %)... 374 - 375 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:** 376 - 377 - 378 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %) 379 -|=(% 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** 380 -|=(% 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) 381 - 382 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %) 383 -|(% 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** 384 -|(% 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) 385 - 386 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %) 387 -|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)((( 388 -**1-32 group** 389 -))) 390 -|(% 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" %)...... 391 - 392 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data. 393 - 394 -[[image:image-20221117145932-2.png]] 395 - 396 - 397 397 The payload is ASCII string, representative same HEX: 398 398 399 - **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__(%%)**266 +0xf86778705021331700640c7817010001000000090000026315537b 0100000b02000002663510fed0100000e0200000263510f39010000000000000063510e85010000000000000063510d2e010000000000000063510c7a010000000000000063510bc6010000000000000063510954010000000000000063510882 where: 400 400 401 -**where:** 268 +* **Device ID: 0x f867787050213317 = f867787050213317** 269 +* **Version: 0x0064=100=1.0.0** 402 402 403 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317 271 +* **BAT: 0x0c78 = 3192 mV = 3.192V** 272 +* **Singal: 0x17 = 23** 273 +* **Mod: 0x01 = 1** 274 +* **Calculate Flag: 0x00= 0** 275 +* **Contact Status: 0x00= 0** 276 +* **Alarm:0x00 =0** 277 +* **Total pulse:0x09 =0** 278 +* **The last open duration:0x02 =2** 279 +* **Time stamp : 0x6315537b =1662342011** 280 +* **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp : 0100000b0200002663510fed** 281 +* **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp : 0100000e0200002663510f39,.......** 404 404 405 -* (% style="color:#037691"%)**Version:**(%%) 0x0064=100=1.0.0283 +**2.4 Payload Explanation and Sensor Interface** 406 406 407 -* (% style="color:#037691"%)**BAT :**(%%) 0x0ccf = 3279 mV = 3.279V285 +**2.4.1 Device ID** 408 408 409 - *(%style="color:#037691"%)**Singal:**(%%)0x19=25287 +By default, the Device ID equal to the last 15 bits of IMEI. 410 410 411 - *(%style="color:#037691"%)**Mod:**(%%)0x01=1289 +User can use **AT+DEUI** to set Device ID 412 412 413 -* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0 414 - 415 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0 416 - 417 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22 418 - 419 -* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23 420 - 421 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time) 422 - 423 -== 2.4 Payload Explanation and Sensor Interface == 424 - 425 - 426 -=== 2.4.1 Device ID === 427 - 428 - 429 -By default, the Device ID is equal to the last 15 bits of IMEI. 430 - 431 -User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID 432 - 433 433 **Example:** 434 434 435 435 AT+DEUI=868411056754138 436 436 437 -The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase theDevice ID.295 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 438 438 297 +**2.4.2 Version Info** 439 439 440 - ===2.4.2VersionInfo===299 +Specify the software version: 0x64=100, means firmware version 1.00. 441 441 301 +For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0. 442 442 443 - Specifythe softwareversion:0x64=100, which meansfirmware version 1.00.303 +**2.4.3 Battery Info** 444 444 445 - For example 0x00 64 : This deviceis NDS03A 1 withfirmware version1.0.0.305 +Check the battery voltage for CPN01. 446 446 447 - 448 -=== 2.4.3 Battery Info === 449 - 450 - 451 -Check the battery voltage for NDS03A. 452 - 453 453 Ex1: 0x0B45 = 2885mV 454 454 455 455 Ex2: 0x0B49 = 2889mV 456 456 311 +**2.4.4 Signal Strength** 457 457 458 -=== 2.4.4 Signal Strength === 459 - 460 - 461 461 NB-IoT Network signal Strength. 462 462 463 463 **Ex1: 0x1d = 29** ... ... @@ -472,47 +472,58 @@ 472 472 473 473 **99** Not known or not detectable 474 474 327 +**2.4.5 Calculate Flag** 475 475 476 - ===2.4.5Disalarm:(default:0)===329 +The calculate flag is a user define field, IoT server can use this filed to handle different meter with different pulse factor. For example, if there are 100 water meters, meter 1 ~~50 are 1 liter/pulse and meter 51 ~~ 100 has 1.5 liter/pulse. 477 477 331 +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 = 1**(%%), NDS03A will only senduplink atevery TDC periodically. This is normallyusefor pulse meter application, in this application, there are many open/close event, and platform only care about the total number of pulse.333 +Default value: 0. 480 480 481 - (% style="color:blue"%)**IfDisalarm= 0**(%%), NDS03Awillsenduplink at every TDC periodically and send data on each open/close event. This is useful for the application user need to monitor the open/close event in real-time.335 +Range (6 bits): (b)000000 ~~ (b) 111111 482 482 483 - (% style="color:red" %)**Note:**(%%)WhenDisalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.337 +**2.4.6 Alarm** 484 484 339 +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]] 485 485 486 - ===2.4.6KeepStatus& Keep Time ===341 +**2.4.7 Contact Status** 487 487 343 +0: Open 488 488 489 - Showsthe configure valueof Alarm Baseon Timeout Feature345 +1: Close 490 490 347 +**2.4.8 Total pulse** 491 491 492 - ===2.4.7Timestamp ===349 +Total pulse/counting base on dry [[contact trigger event>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.2SensorConfiguration2CFPORT3D4]] 493 493 351 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215 494 494 495 -T imestamp: 0x6315537b =1662342011353 +**2.4.9 The last open duration** 496 496 355 +Dry Contact last open duration. 497 497 357 +Unit: min. 498 498 499 - === 2.4.8 Switch DualhannelMode===359 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image017.png]] 500 500 501 501 502 - NDS03A can connect two door sensors.Another door sensor can be connected to PB15pin. Both channelssupportlarmfunction.362 +**2.4.10 Timestamp** 503 503 364 +Time stamp : 0x6315537b =1662342011 504 504 505 - == 2.5 DownlinkPayload==366 +Convert Unix timestamp to time 2022-9-5 9:40:11. 506 506 368 +**~ ** 507 507 508 - Bydefault, NDS03A prints the downlinkpayloadto console port.370 +**2.5 Downlink Payload** 509 509 510 - [[image:image-20221021111414-18.png]]372 +By default, CPN01 prints the downlink payload to console port. 511 511 374 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image018.png||alt="说明: image-20220708133731-5.png"]] 512 512 513 513 **Examples:** 514 514 515 -* (% style="color:#037691" %)**Set TDC**378 +* **Set TDC** 516 516 517 517 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 518 518 ... ... @@ -520,236 +520,178 @@ 520 520 521 521 Payload: 01 00 00 3C TDC=60S 522 522 523 -* (% style="color:#037691" %)**Reset**386 +* **Reset** 524 524 525 -If payload = 0x04FF, it will reset the N DS03A388 +If payload = 0x04FF, it will reset the NSE01 526 526 527 -* (% style="color:#037691" %)**INTMOD**390 +* **INTMOD** 528 528 529 529 Downlink Payload: 06000003, Set AT+INTMOD=3 530 530 394 +**2.6 LED Indicator** 531 531 396 +The CPN01 has an internal LED which is to show the status of different state. 532 532 533 -== 2.6 LED Indicator == 534 - 535 - 536 -The NDS03A has an internal LED which is to show the status of different states. 537 - 538 -* When the device starts normally, the LED will light up for 1 second. 539 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds. 398 +* 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) 399 +* Then the LED will be on for 1 second means device is boot normally. 400 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds. 540 540 * For each uplink probe, LED will be on for 500ms. 541 541 542 - ==2.7==403 +**2.7 ** Alarm Base on Timeout 543 543 405 +CPL01 can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are: 544 544 545 -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: 546 546 408 +**~1. Keep Status: Status to be monitor** 547 547 548 -(% style="color:blue" %)**1. Keep Status: Status to be monitor** 549 - 550 550 Keep Status = 1: Monitor Close to Open event 551 551 552 552 Keep Status = 0: Monitor Open to Close event 553 553 554 554 555 - (% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**415 +**2. Keep Time: Timeout to send an Alarm** 556 556 557 557 Range 0 ~~ 65535(0xFFFF) seconds. 558 558 559 559 If keep time = 0, Disable Alarm Base on Timeout feature. 560 560 561 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn 't change after timeout.421 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout. 562 562 563 563 564 - (% style="color:blue" %)**AT Command to configure:**424 +**AT Command** to configure: 565 565 566 - (%style="color:blue"%)**PB14PIN:**426 +**AT+TTRIG=1,30** ~-~-> When the **Keep Status** change from connect to disconnect, and device remains in disconnect status for more than 30 seconds. CPL01 will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1. 567 567 568 - (% 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.428 +**AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm. 569 569 570 - (% style="color:#037691" %)**AT+TTRIG=0,0**(%%) **~-~->** DefaultValue,disabletimeoutAlarm.430 +**2.8** Set debug mode 571 571 572 - 573 -(% style="color:blue" %)**PB15 PIN:** 574 - 575 -(% style="color:#037691" %)**AT+TTRIG2=1,30** 576 - 577 -(% style="color:#037691" %)**AT+TTRIG2=0,0 ** 578 - 579 - 580 -== 2.8 Set debug mode == 581 - 582 - 583 583 Feature: Enable or Disable debug mode 584 584 585 -(% style="color:blue" %)**AT Command: AT+DEBUG** 586 586 587 - [[image:image-20221021111629-21.png]]435 +**AT Command: AT+DEBUG** 588 588 437 +|**Command Example**|**Function**|**Response** 438 +|AT+DEBUG =0|Disable debug mode to 0|OK 439 +|AT+ DEBUG =1|Enable debug mode to 1|OK 589 589 441 +== 2.9 Clear Flash Record == 590 590 591 -== 2.9 Clear Flash Record == 592 - 593 - 594 594 Feature: Clear flash storage for data log feature. 595 595 596 - (% style="color:blue" %)**AT Command: AT+CLRDTA**445 +**AT Command: AT+CLRDTA** 597 597 598 -[[image:image-2022 1021111527-19.png]]447 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image019.png||alt="说明: image-20220609151132-7.png"]] 599 599 449 +**~ 2.10 **Set trigger mode 600 600 451 +➢ AT Command: **AT+TTRMOD** 601 601 602 - ==2.10CountMod==453 +Feature: Set the trigger interrupt mode. 603 603 455 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image020.png||alt="说明: image-20220609151344-9.png"]] 604 604 605 - (%style="color:blue"%)**AT Command: AT+COUNTMOD**457 +**2.11** Set the calculate flag 606 606 607 - [[image:image-20221118092935-1.png]]459 +Feature: Set the calculate flag 608 608 461 +**AT Command: AT+CALCFLAG** 609 609 463 +|**Command Example**|**Function**|**Response** 464 +|AT+CALCFLAG =1|Set the calculate flag to 1.|OK 465 +|AT+CALCFLAG =2|Set the calculate flag to 2.|OK 610 610 611 - ==2.11InterruptPinChannel Mod ==467 +**2.12** Set count number 612 612 469 +Feature: Manually set the count number 613 613 614 - (% style="color:blue" %)**AT Command: AT+TTRCHANNEL**471 +**AT Command: AT+SETCNT** 615 615 616 -[[image:image-20221118093144-2.png]] 473 +|**Command Example**|**Function**|**Response** 474 +|AT+ SETCNT =0|Set the count number to 0.|OK 475 +|AT+ SETCNT =100|Set the count number to 100.|OK 617 617 618 618 478 +**2.13 Set the number of data to be uploaded and the recording time** 619 619 620 - ==2.12TTRIG1/2timeout status alarm==480 +➢ AT Command: 621 621 482 +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) 622 622 623 -It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval. 624 624 625 - (%style="color:blue"%)**ATCommand:AT+TTRALARM**485 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 626 626 627 - [[image:image-20221118093512-3.png]]487 +**2.14 Read or Clear cached data** 628 628 489 +➢ AT Command: 629 629 491 +AT+CDP ~/~/ Read cached data 630 630 631 - == 2.13 Selectuntingmode==493 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image021.png]] 632 632 633 633 634 - (%style="color:blue"%)**AT Command:AT+TTRMODx=a,b**496 +AT+CDP=0 ~/~/ Clear cached data 635 635 636 - When (% style="color:red" %)**a=0**(%%),thedooris openedto count,and when (%style="color:red" %)**a=1**(%%),the closed door is counted.498 +**2.15 Firmware Change Log** 637 637 638 - When(% style="color:red"%)**b=0**(%%), itisthe lastooren duration,andwhen(% style="color:red" %)**b=1**(%%),the lastrclose duration.500 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]] 639 639 640 -[[ image:image-20221118093658-4.png]]502 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 641 641 504 +**2.16 Battery Analysis** 642 642 506 +**2.16.1 Battery Type** 643 643 508 +The CPN01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 644 644 645 - == 2.14 Setthe numberofdatatobeuploadedandtherecordingtime==510 +The battery is designed to last for several years depends on the actually use environment and update interval. 646 646 512 +The battery related documents as below: 647 647 648 -(% style="color:blue" %)**AT Command:** 649 - 650 -(% 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) 651 - 652 -(% 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. 653 - 654 - 655 -== 2.15 Read or Clear cached data == 656 - 657 - 658 -(% style="color:blue" %)**AT Command:** 659 - 660 -(% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 661 - 662 -(% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 663 - 664 -[[image:image-20221118094227-5.png]] 665 - 666 - 667 - 668 -== 2.16 Firmware Change Log == 669 - 670 - 671 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]] 672 - 673 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 674 - 675 - 676 - 677 -== 2.17 Battery Analysis == 678 - 679 - 680 -=== 2.17.1 Battery Type === 681 - 682 - 683 -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. 684 - 685 -The battery is designed to last for several years depends on the actual use environment and update interval. 686 - 687 -The battery-related documents as below: 688 - 689 689 * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 690 - 691 691 * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 692 - 693 693 * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 694 694 695 -[[image:image-2022 1021111911-26.png]] 518 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image022.png||alt="说明: image-20220708140453-6.png"]] 696 696 520 +**2.16.2 Power consumption Analyze** 697 697 698 - 699 -=== 2.17.2 Power consumption Analyze === 700 - 701 - 702 702 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. 703 703 704 704 Instruction to use as below: 705 705 706 - (% 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/]]526 +**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/]] 707 707 708 - (% style="color:blue" %)**Step 2: **(%%)Open it and choose528 +**Step 2: ** Open it and choose 709 709 710 710 * Product Model 711 - 712 712 * Uplink Interval 713 - 714 714 * Working Mode 715 715 716 716 And the Life expectation in difference case will be shown on the right. 717 717 718 -[[image:1 666596205057-567.png]] 536 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image023.jpg||alt="说明: image-20220708141352-7.jpeg"]] 719 719 538 +**2.16.3 Battery Note** 720 720 721 - 722 -=== 2.17.3 Battery Note === 723 - 724 - 725 725 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. 726 726 542 +**2.16.4 Replace the battery** 727 727 544 +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). 728 728 729 - === 2.17.4Replacethebattery ===546 +**3. Access NB-IoT Module** 730 730 731 - 732 -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). 733 - 734 - 735 - 736 -= 3. Access NB-IoT Module = 737 - 738 - 739 739 Users can directly access the AT command set of the NB-IoT module. 740 740 741 741 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/]] 742 742 743 -[[image:image -20221118094449-6.png]] 552 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image024.png||alt="说明: 1657261278785-153.png"]] 744 744 554 +**4. Using the AT Commands** 745 745 556 +**4.1 Access AT Commands** 746 746 747 -= 4. Using the AT Commands = 748 - 749 - 750 -== 4.1 Access AT Commands == 751 - 752 - 753 753 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]] 754 754 755 755 AT+<CMD>? : Help on <CMD> ... ... @@ -760,9 +760,8 @@ 760 760 761 761 AT+<CMD>=? : Get the value 762 762 568 +**General Commands** 763 763 764 -(% style="color:blue" %)**General Commands** 765 - 766 766 AT : Attention 767 767 768 768 AT? : Short Help ... ... @@ -785,41 +785,35 @@ 785 785 786 786 AT+SERVADDR : Server Address 787 787 788 -AT+TR : 592 +AT+TR : Get or Set record time" 789 789 594 + 790 790 AT+NOUD : Get or Set the number of data to be uploaded 791 791 792 -AT+CDP : Read or Clear cached data 793 793 794 -AT+ EBUG:Enable orDisabledebugmode598 +AT+CDP : Read or Clear cached data 795 795 796 -AT+ TTRIG1 : Get or Set PB14 PIN Alarm Base on Timeout 797 797 798 -AT+ TTRIG2:GetorSetPB15 PIN Alarm Baseon Timeout601 +AT+ DEBUG : Enable or Disable debug mode 799 799 800 -AT+ COUNTMOD:thecountmode603 +AT+ TTRIG : Get or Set Alarm Base on Timeout 801 801 802 -AT+TTR CHANNEL: Get or Set thenumberofinterruptchannels605 +AT+ TTRMOD : Get or Set the trigger interrupt mode(0:falling,1:rising) 803 803 804 -AT+ TTRALARMTTRIG1 of Alarm interval(unit: minute)607 +AT+ CALCFLAG : Get or Set the calculate flag 805 805 806 -AT+ DISALARM:Enable/Disable Alarmfor door open/close or water leak event609 +AT+ CLRC : Clear current door open count 807 807 808 -A T+CLRC : Clear current door opencount611 +**COAP Management** 809 809 810 - 811 -(% style="color:blue" %)**COAP Management** 812 - 813 813 AT+URI : Resource parameters 814 814 615 +**UDP Management** 815 815 816 -(% style="color:blue" %)**UDP Management** 817 - 818 818 AT+CFM : Upload confirmation mode (only valid for UDP) 819 819 619 +**MQTT Management** 820 820 821 -(% style="color:blue" %)**MQTT Management** 822 - 823 823 AT+CLIENT : Get or Set MQTT client 824 824 825 825 AT+UNAME : Get or Set MQTT Username ... ... @@ -830,65 +830,86 @@ 830 830 831 831 AT+SUBTOPIC : Get or Set MQTT subscription topic 832 832 631 +**Information** 833 833 834 -(% style="color:blue" %)**Information** 835 - 836 836 AT+FDR : Factory Data Reset 837 837 838 838 AT+PWORD : Serial Access Password 839 839 637 +**5. FAQ** 840 840 639 +**5.1 How to Upgrade Firmware** 841 841 842 - =5.FAQ=641 +User can upgrade the firmware for 1) bug fix, 2) new feature release. 843 843 643 +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]] 844 844 845 - ==5.1HowtoUpgradeFirmware==645 +**Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.** 846 846 647 +**5.2 Can I calibrate CPN01 to different soil types?** 847 847 848 - Usercan upgrade thefirmware for1)bugfix,2)newfeaturerelease.649 +CPN01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]]. 849 849 850 - Pleasesee this link forhow toupgrade: [[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]]651 +**6. Trouble Shooting** 851 851 852 - (% style="color:red" %)**Notice:**(% style="color:blue" %)**NDS03A** (%%)**and (% style="color:blue" %)LDS03A(%%)**(% style="color:blue" %) (%%)**share the samemotherboard. They use the same connectionandmethod to update.**653 +**6.1 Connection problem when uploading firmware** 853 853 655 +**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]] 854 854 657 +**6.2 AT Command input doesn't work** 855 855 856 - =6.TroubleShooting=659 +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. 857 857 661 +**7. Order Info** 858 858 859 - == 6.1 Connectionproblem whenuploading firmware==663 +Part Number**:** CPN01 860 860 665 +**8. Packing Info** 861 861 862 - (% 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]]667 +**Package Includes**: 863 863 669 +* CPN01 NB-IoT Soil Moisture & EC Sensor x 1 670 +* External antenna x 1 864 864 672 +**Dimension and weight**: 865 865 866 -== 6.2 AT Command input doesn't work == 674 +* Size: 195 x 125 x 55 mm 675 +* Weight: 420g 867 867 677 +**9. Support** 868 868 869 -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. 679 +* 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. 680 +* 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 682 + 871 871 872 872 873 -= 7. Order Info = 874 874 875 875 876 -Part Number**:** NDS03A 877 877 878 878 879 879 880 -= 8. Packing Info = 881 881 882 882 883 -(% style="color:blue" %)**Package Includes**: 884 884 885 -* NDS03A Open/Close Door Sensor x 1 886 886 887 -= 9. Support = 888 888 889 889 890 -* 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. 891 891 892 -* 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]] 893 893 894 - 698 + 699 + 700 + 701 + 702 + 703 + 704 + 705 + 706 + 707 + 708 + 709 + 710 + 711 + 712 + 713 +
- 1666596205057-567.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -179.8 KB - Content
- image-20221022234529-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -43.3 KB - Content
- image-20221022234602-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -135.7 KB - Content
- image-20221023000439-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -82.1 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