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, 22 added, 0 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
- image-20221118103445-7.png
- image-20221118103453-8.png
- image-20221118103547-9.png
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - CPN01-NB-IoTOutdoor Open/Close DryContactSensor User Manual1 +NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. David1 +XWiki.Xiaoling - Content
-
... ... @@ -1,36 +1,69 @@ 1 1 (% style="text-align:center" %) 2 -[[image: http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/WebHome/1652856952171-363.png?rev=1.1||alt="1652856952171-363.png" height="578" width="588"]]2 +[[image:image-20221117105556-1.png]] 3 3 4 4 5 -= **1. Introduction** = 6 6 7 -== **1.1 **What is CPN01 **NB-IOT** Pulse/Contact Sensor == 8 8 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. 10 10 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. 12 12 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. 14 14 15 - CPL01 is designedfor outdoor use. It has a weatherproofenclosure and industrial level battery to work inlowto high temperatures.10 +**Table of Contents:** 16 16 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 12 +{{toc/}} 21 21 22 - 23 23 24 24 25 -== **1.2 Features** == 26 26 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 + 27 27 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 28 28 * Open/Close detect 29 29 * Open/Close statistics 30 30 * Monitor Battery Level 31 -* Uplinkonperiodicallyandopen/closeevent64 +* connect two door sensors 32 32 * Datalog feature 33 -* Uplink onperiodically66 +* Uplink periodically 34 34 * Downlink to change configure 35 35 * Wall Mountable 36 36 * Outdoor Use ... ... @@ -37,16 +37,45 @@ 37 37 * Ultra-Low Power consumption 38 38 * AT Commands to change parameters 39 39 * Micro SIM card slot for NB-IoT SIM 40 -* 8500mAh Battery for long 73 +* 8500mAh Battery for long-term use 41 41 42 -== **1.3 Specification** == 43 43 44 -**Common DC Characteristics:** 45 45 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 + 46 46 * Supply Voltage: 2.1v ~~ 3.6v 47 47 * Operating Temperature: -40 ~~ 85°C 48 48 49 -**NB-IoT Spec:** 111 +(% style="color:blue" %)**NB-IoT Spec:** 50 50 51 51 * - B1 @H-FDD: 2100MHz 52 52 * - B3 @H-FDD: 1800MHz ... ... @@ -55,261 +55,339 @@ 55 55 * - B20 @H-FDD: 800MHz 56 56 * - B28 @H-FDD: 700MHz 57 57 58 -== **1.4 Installation** == 59 59 60 -Connect CPL01 to an Open Close sensor like below. So it can detect the open/close event. 61 61 62 - [[image:image-20221021110329-1.png]]122 +== 1.7 Pin Definitions and Switch == 63 63 64 -[[image:image-20221021110340-2.png]] 65 65 66 - == **1.5 Applications** ==125 +[[image:image-20221021110429-4.png]] 67 67 68 -* Open/Close Detection 69 -* Pulse meter application 70 -* Dry Contact Detection 71 71 72 -== **1.6Mechanical**==128 +=== 1.7.1 Pin Definition === 73 73 74 -[[image:image-20221021110415-3.png]] 75 75 76 - ==**1.7 PinDefinitions and Switch**==131 +The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at: [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]] 77 77 78 -[[image:image-20221021110429-4.png]] 79 79 80 -=== **1.7.1PinDefinition**===134 +=== 1.7.2 Jumper JP2(Power ON/OFF) === 81 81 82 -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]] 83 83 84 - === **1.7.2 JumperJP2(PowerON/OFF)**===137 +Power on Device when putting this jumper. 85 85 86 86 87 - PoweronDevicewhenputtingthis jumper.140 +=== 1.7.3 BOOT MODE / SW1 === 88 88 89 89 143 +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. 90 90 91 - ===**1.7.3BOOTMODE/SW1**===145 +2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging. 92 92 93 93 94 -1 )ISP: upgrademode, device won't have anysignal in this mode. butready forupgrade firmware. LED won'twork. Firmware won'trun.148 +=== 1.7.4 Reset Button === 95 95 96 -2) Flash: work mode, the device starts to work and send out console output for further debug 97 97 151 +Press to reboot the device. 98 98 99 99 100 -=== **1.7.4ResetButton**===154 +=== 1.7.5 LED === 101 101 102 102 103 - Presstorebootthedevice.157 +The LED will blink when : 104 104 105 - ====159 +1. Boot the device in flash mode 106 106 107 - === **1.7.5LED**===161 +2. Send an uplink packet 108 108 109 109 110 - Itwillflash:164 +== 1.8 Magnet Distance == 111 111 112 -1. Boot the device in flash mode 113 -1. Send an uplink packet 114 114 115 - =**2. Use CPN01tocommunicatewith IoTServer**=167 +(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm 116 116 117 -= =**2.1 Howit works**==169 +(% style="color:blue" %)**Iron Door:**(%%)** **30 ~~ 45mm 118 118 119 -The CPN01 is equipped with a NB-IoT module, the pre-loaded firmware in CPN01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01. 120 120 121 - Thediagrambelowshowsthe workingflowin default firmwareof CPN01:172 += 2. Use NDS03A to communicate with IoT Server = 122 122 174 +== 2.1 How it works == 175 + 176 + 177 +In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A. 178 + 179 +The diagram below shows the working flow in the default firmware of NDS03A: 180 + 123 123 [[image:image-20221021110615-5.png]] 124 124 125 -== **2.2 Configure the CPN01** == 126 126 127 -== =**2.2.1Test Requirement**===184 +== 2.2 Configure NDS03A == 128 128 129 - Touse CPN01inyour city, makeure meetbelow requirements:186 +=== 2.2.1 Test Requirement === 130 130 131 -* Your local operator has already distributed a NB-IoT Network there. 132 -* The local NB-IoT network used the band that CPN01 supports. 188 + 189 +To use NDS03A in your city, make sure to meet below requirements: 190 + 191 +* Your local operator has already distributed an NB-IoT Network. 192 +* The local NB-IoT network used the band that NDS03A supports. 133 133 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 134 134 135 -Below figure shows our testing structure. CPN01will 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 server195 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDS03A will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server. 136 136 137 - 197 +[[image:image-20221117142300-1.png]] 138 138 139 -=== **2.2.2 Insert SIM card** === 140 140 200 +=== 2.2.2 Insert NB-IoT SIM card === 201 + 202 + 141 141 Insert the NB-IoT Card get from your provider. 142 142 143 -User need to take out the NB-IoT module and insert the SIM card like below: 205 +User needs to take out the NB-IoT module and insert the SIM card like below: 144 144 145 145 [[image:image-20221021110745-6.png]] 146 146 147 -=== **2.2.3 Connect USB – TTL to CPN01 to configure it** === 148 148 149 - UserneedtoconfigureCPN01 via serial port to set the **Server Address** / **Uplink Topic** to definewhere and how-to uplink packets.CPN01 support AT Commands, user can use aUSBtoTTLadapter toconnect to CPN01 and useATCommandstoconfigure it,as below.210 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it === 150 150 151 -**Connection:** 152 152 153 - USB TTL GND<~-~-~-~->GND213 +User need 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 USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below. 154 154 155 - USBTTL TXD <~-~-~-~-> UART_RXD215 +(% style="color:blue" %)**Connection:** 156 156 157 - USB TTL RXD <~-~-~-~->UART_TXD217 +(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND** 158 158 219 +(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD** 220 + 221 +(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD** 222 + 223 + 159 159 In the PC, use below serial tool settings: 160 160 161 -* Baud: **9600** 162 -* Data bits:** 8** 163 -* Stop bits: **1** 164 -* Parity: **None** 165 -* Flow Control: **None** 226 +* Baud: (% style="color:red" %)**9600** 166 166 167 - Makesuretheswitch isin FLASH position, then power on device byconnecting the jumper on CPN01. CPN01 will output system info once power on as below, we can enterthe **password:12345678**to access AT Command input.228 +* Data bits:** (% style="color:red" %)8(%%)** 168 168 230 +* Stop bits: (% style="color:red" %)**1** 231 + 232 +* Parity: (% style="color:red" %)**None** 233 + 234 +* Flow Control: (% style="color:red" %)**None** 235 + 236 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%). 237 + 169 169 [[image:image-20221021110817-7.png]] 170 170 171 - **Note:thevalidAT Commands canbefoundat:**[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]240 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input. 172 172 173 -=== **2.2.4 Use CoAP protocol to uplink data** === 174 174 175 -**Note: if you don'taveCoAP server,youcanrefer thislinkto setupone: **[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]243 +(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]] 176 176 177 -**Use below commands:** 178 178 179 -* **AT+PRO=1** ~/~/ Set to use CoAP protocol to uplink 180 -* **AT+SERVADDR=120.24.4.116,5683 ** ~/~/ to set CoAP server address and port 181 -* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path 182 182 247 +=== 2.2.4 Use CoAP protocol to uplink data === 248 + 249 + 250 +(% style="color:red" %)**Note: if you don't have a CoAP server, you can refer this link to set up a CoAP server: **(%%)[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 251 + 252 + 253 +(% style="color:blue" %)**Use below commands in NDS03A:** 254 + 255 +* (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 256 + 257 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ Set CoAP server address and port 258 + 259 +* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/ Set CoAP resource path 260 + 183 183 For parameter description, please refer to AT command set 184 184 185 185 [[image:image-20221021110948-8.png]] 186 186 187 -After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server. 188 188 189 - [[image:image-20221021110956-9.png]]266 +After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server. 190 190 191 - === **2.2.5Use UDPprotocolto uplinkdata(Default protocol)**===268 +[[image:image-20221118103547-9.png||height="605" width="837"]] 192 192 193 -This feature is supported since firmware version v1.0.1 194 194 195 -* **AT+PRO=2 ** ~/~/ Set to use UDP protocol to uplink 196 -* **AT+SERVADDR=120.24.4.116,5601 ** ~/~/ to set UDP server address and port 197 -* **AT+CFM=1 ** ~/~/If the server does not respond, this command is unnecessary 271 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 198 198 199 - [[image:image-20221021111025-10.png]] 200 200 274 +(% style="color:blue" %)**AT Commands:** 275 + 276 +* (% style="color:#037691" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 277 + 278 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ Set UDP server address and port 279 + 280 +* (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 281 + 282 + [[image:image-20221021111025-10.png]] 283 + 284 + 201 201 [[image:image-20221021111033-11.png||height="241" width="576"]] 202 202 203 203 204 204 205 -=== **2.2.6 Use MQTT protocol to uplink data**===289 +=== 2.2.6 Use MQTT protocol to uplink data === 206 206 207 -This feature is supported since firmware version v110 208 208 209 -* **AT+PRO=3 ** ~/~/Set to use MQTT protocol to uplink 210 -* **AT+SERVADDR=120.24.4.116,1883 ** ~/~/Set MQTT server address and port 211 -* **AT+CLIENT=CLIENT ** ~/~/Set up the CLIENT of MQTT 212 -* **AT+UNAME=UNAME **~/~/Set the username of MQTT 213 -* **AT+PWD=PWD **~/~/Set the password of MQTT 214 -* **AT+PUBTOPIC=NSE01_PUB **~/~/Set the sending topic of MQTT 215 -* **AT+SUBTOPIC=NSE01_SUB ** ~/~/Set the subscription topic of MQTT 292 +(% style="color:blue" %)**AT Commands:** 216 216 217 - [[image:image-20221021111058-12.png]]294 +* (% style="color:#037691" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 218 218 219 - [[image:image-20221021111108-13.png]]296 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 220 220 298 +* (% style="color:#037691" %)**AT+CLIENT=CLIENT ** (%%) ~/~/ Set up the CLIENT of MQTT 299 + 300 +* (% style="color:#037691" %)**AT+UNAME=UNAME **(%%)** **~/~/ Set the username of MQTT 301 + 302 +* (% style="color:#037691" %)**AT+PWD=PWD **(%%)** **~/~/ Set the password of MQTT 303 + 304 +* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB **(%%)** **~/~/ Set the sending topic of MQTT 305 + 306 +* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB ** (%%) ~/~/ Set the subscription topic of MQTT 307 + 308 + [[image:image-20221118103445-7.png]] 309 + 310 + 311 +[[image:image-20221118103453-8.png||height="608" width="841"]] 312 + 221 221 222 222 223 -MQTT protocol has a much higher power consumption compare vsUDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.315 +MQTT protocol has a much higher power consumption compare with UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 224 224 225 -=== **2.2.7 Use TCP protocol to uplink data** === 226 226 227 - Thisfeatureissupported sincefirmwareversionv110318 +=== 2.2.7 Use TCP protocol to uplink data === 228 228 229 -* **AT+PRO=4 ** ~/~/ Set to use TCP protocol to uplink 230 -* **AT+SERVADDR=120.24.4.116,5600 ** ~/~/ to set TCP server address and port 231 231 232 - [[image:image-20221021111125-14.png]]321 +(% style="color:blue" %)**AT Commands:** 233 233 323 +* (% style="color:#037691" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 324 + 325 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ Set TCP server address and port 326 + 327 + [[image:image-20221021111125-14.png]] 328 + 234 234 [[image:image-20221021111131-15.png]] 235 235 236 236 237 237 238 -=== **2.2.8 Change Update Interval**===333 +=== 2.2.8 Change Update Interval === 239 239 240 -User can use below command to change the **uplink interval**. 241 241 242 - ***AT+TDC=600**~/~/SetUpdateIntervalto 600s336 +User can use below command to change the (% style="color:blue" %)**uplink interval**. 243 243 244 -** NOTE:**338 +* (% style="color:#037691" %)**AT+TDC=14400 ** (%%) ~/~/ Set Update Interval to 14400s (4 hours) 245 245 246 - **~1.Bydefault, thedevice will sendan uplink message every 1 hour.**340 +(% style="color:red" %)**NOTE:** 247 247 248 - == **2.3UplinkPayload**==342 +1. By default, the device will send an uplink message every 4 hour. 249 249 250 -In this mode, uplink payload includes 87 bytes in total by default. 251 251 252 - Eachtimethe device uploads a data package,8 sets of recorded data will be attached. Up to32 sets of recorded data can be uploaded.345 +== 2.3 Uplink Payload == 253 253 254 -|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**2**|**2**|4 255 -|**Value**|[[Device ID>>path:#H2.4.1A0A0DeviceID]]|[[Ver>>path:#H2.4.2A0VersionInfo]]|[[BAT>>path:#H2.4.3A0BatteryInfo]]|[[Signal Strength>>path:#H2.4.4A0SignalStrength]]|MOD|[[Interrupt>>path:#H2.4.8A0DigitalInterrupt]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|Time stamp 256 256 257 -|2|2|4|8 group 258 -|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|... 348 +The uplink payload includes 26 bytes in total by default. 259 259 260 - IfweusetheMQTT client to subscribetothisMQTTtopic,we can seethefollowinginformationwhentheCPN01uplinkdata.350 +Each time the device uploads a data package. The user can use the AT+NOUD command to upload the recorded data.Up to 32 sets of recorded data can be uploaded. 261 261 262 - [[image:image-20221021111201-16.png||height="572"width="792"]]352 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:** 263 263 354 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 355 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**1**|(% style="width:90px" %)**3**|(% style="width:100px" %)**3** 356 +|=(% 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) 357 + 358 +(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %) 359 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)((( 360 +**1-32 group** 361 +))) 362 +|(% 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" %)... 363 + 364 + 365 + 366 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:** 367 + 368 + 369 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 370 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:45px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:60px" %)**1**|(% style="width:60px" %)**1**|(% style="width:88px" %)**3**|(% style="width:80px" %)**3** 371 +|=(% 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) 372 + 373 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 374 +|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:75px" %)**1**|(% style="width:75px" %)**3** 375 +|(% 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) 376 + 377 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %) 378 +|(% style="width:90px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)((( 379 +**1-32 group** 380 +))) 381 +|(% style="width:102px" %)last open time (pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:100px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)...... 382 + 383 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data. 384 + 385 +[[image:image-20221117145932-2.png]] 386 + 387 + 264 264 The payload is ASCII string, representative same HEX: 265 265 266 -0xf86778705021331700640c 7817010001000000090000026315537b0100000b02000002663510fed0100000e0200000263510f39010000000000000063510e85010000000000000063510d2e010000000000000063510c7a010000000000000063510bc6010000000000000063510954010000000000000063510882 where:390 +**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__(%%)** 267 267 268 -* **Device ID: 0x f867787050213317 = f867787050213317** 269 -* **Version: 0x0064=100=1.0.0** 392 +**where:** 270 270 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,.......** 394 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317 282 282 283 - ==**2.4Payload Explanationand Sensor Interface** ==396 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 284 284 285 -= ==**2.4.1 DeviceID** ===398 +* (% style="color:#037691" %)**BAT :**(%%) 0x0ccf = 3279 mV = 3.279V 286 286 287 - Bydefault,theDevice ID equaltothe last15bitsof IMEI.400 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25 288 288 289 - Usercanuse **AT+DEUI**tosetDeviceID402 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 290 290 404 +* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0 405 + 406 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0 407 + 408 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22 409 + 410 +* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23 411 + 412 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time) 413 + 414 + 415 + 416 +== 2.4 Payload Explanation and Sensor Interface == 417 + 418 +=== 2.4.1 Device ID === 419 + 420 + 421 +By default, the Device ID is equal to the last 15 bits of IMEI. 422 + 423 +User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID 424 + 291 291 **Example:** 292 292 293 293 AT+DEUI=868411056754138 294 294 295 -The Device ID is stored in a non e-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.429 +The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID. 296 296 297 -=== **2.4.2 Version Info** === 298 298 299 - Specifythesoftwareversion:0x64=100, meansfirmware version1.00.432 +=== 2.4.2 Version Info === 300 300 301 -For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0. 302 302 303 - ===**2.4.3BatteryInfo**===435 +Specify the software version: 0x64=100, which means firmware version 1.00. 304 304 305 - CheckthebatteryvoltageforCPN01.437 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0. 306 306 439 + 440 +=== 2.4.3 Battery Info === 441 + 442 + 443 +Check the battery voltage for NDS03A. 444 + 307 307 Ex1: 0x0B45 = 2885mV 308 308 309 309 Ex2: 0x0B49 = 2889mV 310 310 311 -=== **2.4.4 Signal Strength** === 312 312 450 +=== 2.4.4 Signal Strength === 451 + 452 + 313 313 NB-IoT Network signal Strength. 314 314 315 315 **Ex1: 0x1d = 29** ... ... @@ -324,58 +324,46 @@ 324 324 325 325 **99** Not known or not detectable 326 326 327 -=== **2.4.5 Calculate Flag** === 328 328 329 - Thecalculateflagisuser define field, IoT server can use this filed to handle differentmeterwithdifferent pulsefactor. For example, if there are 100 water meters, meter 1 ~~50 are 1 liter/pulse and meter51 ~~ 100has 1.5 liter/pulse.468 +=== 2.4.5 Disalarm: (default: 0) === 330 330 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. 332 332 333 - Default value:0.471 +(% style="color:blue" %)**If Disalarm = 1**(%%), NDS03A will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many open/close event, and platform only care about the total number of pulse. 334 334 335 - Range(6bits):(b)000000~~(b)111111473 +(% style="color:blue" %)**If Disalarm = 0**(%%), NDS03A will send uplink 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. 336 336 337 -= ==**2.4.6Alarm**===475 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast. 338 338 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]] 340 340 341 -=== **2.4.7ContactStatus**===478 +=== 2.4.6 Keep Status & Keep Time === 342 342 343 -0: Open 344 344 345 - 1:Close481 +Shows the configure value of Alarm Base on Timeout Feature 346 346 347 -=== **2.4.8 Total pulse** === 348 348 349 - Totalpulse/counting base on dry[[contacttrigger 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]]484 +=== 2.4.7 Timestamp === 350 350 351 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215 352 352 353 - === **2.4.9Thelastopenduration**===487 +Timestamp : 0x6315537b =1662342011 354 354 355 -Dry Contact last open duration. 356 356 357 - Unit:min.490 +=== 2.4.8 Switch Dual Channel Mode === 358 358 359 -[[image:image-20221021111346-17.png||height="146" width="770"]] 360 360 493 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function. 361 361 362 -=== **2.4.10 Timestamp** === 363 363 364 - Timestamp: 0x6315537b=1662342011496 +== 2.5 Downlink Payload == 365 365 366 -Convert Unix timestamp to time 2022-9-5 9:40:11. 367 367 368 - **~**499 +By default, NDS03A prints the downlink payload to console port. 369 369 370 -== **2.5 Downlink Payload** == 371 - 372 -By default, CPN01 prints the downlink payload to console port. 373 - 374 374 [[image:image-20221021111414-18.png]] 375 375 503 + 376 376 **Examples:** 377 377 378 -* **Set TDC** 506 +* (% style="color:#037691" %)**Set TDC** 379 379 380 380 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 381 381 ... ... @@ -383,171 +383,222 @@ 383 383 384 384 Payload: 01 00 00 3C TDC=60S 385 385 386 -* **Reset** 514 +* (% style="color:#037691" %)**Reset** 387 387 388 -If payload = 0x04FF, it will reset the NS E01516 +If payload = 0x04FF, it will reset the NDS03A 389 389 390 -* **INTMOD** 518 +* (% style="color:#037691" %)**INTMOD** 391 391 392 392 Downlink Payload: 06000003, Set AT+INTMOD=3 393 393 394 -== **2.6 LED Indicator** == 395 395 396 - TheCPN01has an internalLEDwhich is to show the statusof differentstate.523 +== 2.6 LED Indicator == 397 397 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. 525 + 526 +The NDS03A has an internal LED which is to show the status of different states. 527 + 528 +* When the device starts normally, the LED will light up for 1 second. 529 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds. 401 401 * For each uplink probe, LED will be on for 500ms. 402 402 403 -== **2.7 Alarm Base on Timeout** == 404 404 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: 406 406 534 +== 2.7 Alarm Base on Timeout == 407 407 408 -**~1. Keep Status: Status to be monitor** 409 409 537 +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: 538 + 539 + 540 +(% style="color:blue" %)**1. Keep Status: Status to be monitor** 541 + 410 410 Keep Status = 1: Monitor Close to Open event 411 411 412 412 Keep Status = 0: Monitor Open to Close event 413 413 414 414 415 -**2. Keep Time: Timeout to send an Alarm** 547 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm** 416 416 417 417 Range 0 ~~ 65535(0xFFFF) seconds. 418 418 419 419 If keep time = 0, Disable Alarm Base on Timeout feature. 420 420 421 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn ’t change after timeout.553 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout. 422 422 423 423 424 -**AT Command **to configure:556 +(% style="color:blue" %)**AT Command to configure:** 425 425 426 - **AT+TTRIG=1,30**~-~-> When the **Keep Status** change from connectto disconnect, and device remains in disconnect status formore 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 of1^^st^^ byteof payload) on this uplink packet is set to 1.558 +(% style="color:blue" %)**PB14 PIN:** 427 427 428 -**AT+TTIG= 0,0DefaultValue,disable timeoutAlarm.560 +(% style="color:#037691" %)**AT+TTRIG=1,30** (%%) **~-~->** When the **Keep Status** change from connected to disconnect, and device remains in disconnect status for more than 30 seconds. NDS03A 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. 429 429 430 -== ** 2.8 Setdebugmode**==562 +(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm. 431 431 432 -Feature: Enable or Disable debug mode 433 433 565 +(% style="color:blue" %)**PB15 PIN:** 434 434 435 - **ATCommand: AT+DEBUG**567 +(% style="color:#037691" %)**AT+TTRIG2=1,30** 436 436 569 +(% style="color:#037691" %)**AT+TTRIG2=0,0 ** 570 + 571 + 572 +== 2.8 Set debug mode == 573 + 574 + 575 +Feature: Enable or Disable debug mode 576 + 577 +(% style="color:blue" %)**AT Command: AT+DEBUG** 578 + 437 437 [[image:image-20221021111629-21.png]] 438 438 439 -== **2.9 Clear Flash Record** == 440 440 582 + 583 +== 2.9 Clear Flash Record == 584 + 585 + 441 441 Feature: Clear flash storage for data log feature. 442 442 443 -**AT Command: AT+CLRDTA** 588 +(% style="color:blue" %)**AT Command: AT+CLRDTA** 444 444 445 445 [[image:image-20221021111527-19.png]] 446 446 447 -== ** 2.10 Set trigger mode** == 448 448 449 - ➢ATCommand:**AT+TTRMOD**593 +== 2.10 Count Mod == 450 450 451 -Feature: Set the trigger interrupt mode. 452 452 453 - [[image:image-20221021111552-20.png]]596 +(% style="color:blue" %)**AT Command: AT+COUNTMOD** 454 454 455 - == **2.11 Set the calculateflag** ==598 +[[image:image-20221118092935-1.png]] 456 456 457 -Feature: Set the calculate flag 458 458 459 - **ATCommand:AT+CALCFLAG**601 +== 2.11 Interrupt Pin Channel Mod == 460 460 461 -[[image:image-20221021111711-22.png]] 462 462 463 -= =**2.12Set countnumber**==604 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL** 464 464 465 - Feature:Manually set the count number606 +[[image:image-20221118093144-2.png]] 466 466 467 -**AT Command: AT+SETCNT** 468 468 469 - [[image:image-20221021111748-24.png]]609 +== 2.12 TTRIG1/2 timeout status alarm == 470 470 471 -== **2.13 Set the number of data to be uploaded and the recording time** == 472 472 473 - ➢ATCommand:612 +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. 474 474 475 - AT+TR=900~/~/The unit isseconds, andthe default is to record dataonce every 900 seconds.(Theminimum canbe set to 180 seconds)614 +(% style="color:blue" %)**AT Command: AT+TTRALARM** 476 476 616 +[[image:image-20221118093512-3.png]] 477 477 478 -AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 479 479 480 -== **2.14Read or Clearcacheddata**==619 +== 2.13 Select counting mode == 481 481 482 -➢ AT Command: 483 483 484 -AT +CDP~/~/ Readcached data622 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b** 485 485 486 - [[image:image-20221021111810-25.png||height="364"width="797"]]624 +When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted. 487 487 626 +When (% style="color:red" %)**b=0**(%%), it is the last door open duration, and when (% style="color:red" %)**b=1**(%%),the last door close duration. 488 488 489 - AT+CDP=0 ~/~/ Clear cached data 628 +[[image:image-20221118093658-4.png]] 490 490 491 -== **2.15 Firmware Change Log** == 492 492 493 - DownloadURL& FirmwareChangelog: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]631 +== 2.14 Set the number of data to be uploaded and the recording time == 494 494 495 -Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 496 496 497 - ==**2.16 BatteryAnalysis**==634 +(% style="color:blue" %)**AT Command:** 498 498 499 -= ==**2.16.1Battery Type**===636 +(% 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) 500 500 501 - TheCPN01 batteryisacombinationofan8500mAhLi/SOCI2Batteryanda Super Capacitor.Thebattery isnone-rechargeablebatterytypewithaowdischargerate(<2%per year). Thistypeofbattery iscommonlyusedinIoT devicessuchas water meter.638 +(% 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. 502 502 503 -The battery is designed to last for several years depends on the actually use environment and update interval. 504 504 505 - Thebatteryrelated documentsasbelow:641 +== 2.15 Read or Clear cached data == 506 506 643 + 644 +(% style="color:blue" %)**AT Command:** 645 + 646 +(% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 647 + 648 +(% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 649 + 650 +[[image:image-20221118094227-5.png]] 651 + 652 + 653 +== 2.16 Firmware Change Log == 654 + 655 + 656 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]] 657 + 658 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 659 + 660 + 661 +== 2.17 Battery Analysis == 662 + 663 +=== 2.17.1 Battery Type === 664 + 665 + 666 +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. 667 + 668 +The battery is designed to last for several years depends on the actual use environment and update interval. 669 + 670 +The battery-related documents as below: 671 + 507 507 * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 673 + 508 508 * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 675 + 509 509 * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 510 510 511 511 [[image:image-20221021111911-26.png]] 512 512 513 -=== **2.16.2 Power consumption Analyze** === 514 514 681 +=== 2.17.2 Power consumption Analyze === 682 + 683 + 515 515 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. 516 516 517 517 Instruction to use as below: 518 518 519 -**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/]] 688 +(% 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/]] 520 520 521 -**Step 2: ** Open it and choose 690 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 522 522 523 523 * Product Model 693 + 524 524 * Uplink Interval 695 + 525 525 * Working Mode 526 526 527 527 And the Life expectation in difference case will be shown on the right. 528 528 529 -[[image: image-20221021111923-27.png||height="253" width="783"]] 700 +[[image:1666596205057-567.png]] 530 530 531 -=== **2.16.3 Battery Note** === 532 532 703 +=== 2.17.3 Battery Note === 704 + 705 + 533 533 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. 534 534 535 -=== **2.16.4 Replace the battery** === 536 536 537 - Thedefault battery pack of CPN01 includes a ER26500 plus super capacitor.If user can't find this pack locally, they can find ER26500 orequivalence without the SPC1520 capacitor, which willalso work in mostcase.The SPC can enlargethe batterylife for high frequency use (update period below 5 minutes).709 +=== 2.17.4 Replace the battery === 538 538 539 -= **3. Access NB-IoT Module** = 540 540 712 +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). 713 + 714 + 715 += 3. Access NB-IoT Module = 716 + 717 + 541 541 Users can directly access the AT command set of the NB-IoT module. 542 542 543 543 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/]] 544 544 545 -[[image:image-20221 021112006-28.png]] 722 +[[image:image-20221118094449-6.png]] 546 546 547 -= **4. Using the AT Commands** = 548 548 549 -= =**4.1AccessAT Commands**==725 += 4. Using the AT Commands = 550 550 727 +== 4.1 Access AT Commands == 728 + 729 + 551 551 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]] 552 552 553 553 AT+<CMD>? : Help on <CMD> ... ... @@ -558,8 +558,9 @@ 558 558 559 559 AT+<CMD>=? : Get the value 560 560 561 -**General Commands** 562 562 741 +(% style="color:blue" %)**General Commands** 742 + 563 563 AT : Attention 564 564 565 565 AT? : Short Help ... ... @@ -582,35 +582,41 @@ 582 582 583 583 AT+SERVADDR : Server Address 584 584 585 -AT+TR : Get or Set record time "765 +AT+TR : Get or Set record time 586 586 587 - 588 588 AT+NOUD : Get or Set the number of data to be uploaded 589 589 769 +AT+CDP : Read or Clear cached data 590 590 591 -AT+ CDPReadorClearcached data771 +AT+ DEBUG : Enable or Disable debug mode 592 592 773 +AT+ TTRIG1 : Get or Set PB14 PIN Alarm Base on Timeout 593 593 594 -AT+ DEBUG :Enable orDisabledebugmode775 +AT+ TTRIG2 : Get or Set PB15 PIN Alarm Base on Timeout 595 595 596 -AT+ TRIGAlarm Base onTimeout777 +AT+COUNTMOD : Get or Set the count mode 597 597 598 -AT+ MODtrigger interruptmode(0:falling,1:rising)779 +AT+TTRCHANNEL : Get or Set the number of interrupt channels 599 599 600 -AT+ CALCFLAG: Get or Set thecalculateflag781 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute) 601 601 602 -AT+ CLRCClearcurrentdoor openunt783 +AT+DISALARM : Enable/Disable Alarm for door open/close or water leak event 603 603 604 - **COAPManagement**785 +AT+ CLRC : Clear current door open count 605 605 787 + 788 +(% style="color:blue" %)**COAP Management** 789 + 606 606 AT+URI : Resource parameters 607 607 608 -**UDP Management** 609 609 793 +(% style="color:blue" %)**UDP Management** 794 + 610 610 AT+CFM : Upload confirmation mode (only valid for UDP) 611 611 612 -**MQTT Management** 613 613 798 +(% style="color:blue" %)**MQTT Management** 799 + 614 614 AT+CLIENT : Get or Set MQTT client 615 615 616 616 AT+UNAME : Get or Set MQTT Username ... ... @@ -621,86 +621,60 @@ 621 621 622 622 AT+SUBTOPIC : Get or Set MQTT subscription topic 623 623 624 -**Information** 625 625 811 +(% style="color:blue" %)**Information** 812 + 626 626 AT+FDR : Factory Data Reset 627 627 628 628 AT+PWORD : Serial Access Password 629 629 630 -= **5. FAQ** = 631 631 632 -= =**5.1 How to UpgradeFirmware**==818 += 5. FAQ = 633 633 820 +== 5.1 How to Upgrade Firmware == 821 + 822 + 634 634 User can upgrade the firmware for 1) bug fix, 2) new feature release. 635 635 636 636 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]] 637 637 638 -**Notice ,**CPN01**and **CPN01**share the same mother board. They use the same connection and method to update.**827 +(% style="color:red" %)**Notice: **(% style="color:blue" %)**NDS03A** (%%)**and (% style="color:blue" %)LDS03A(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.** 639 639 640 -== **5.2 Can I calibrate CPN01 to different soil types?** == 641 641 642 - CPN01is calibrated for saline-alkali soil and loamy soil.If users want to use it for other soil, they can calibrate the value in the IoTplatform baseon the value measuredby saline-alkalisoil 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]].830 += 6. Trouble Shooting = 643 643 644 -= **6.TroubleShooting**=832 +== 6.1 Connection problem when uploading firmware == 645 645 646 -== **6.1 Connection problem when uploading firmware** == 647 647 648 -**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]] 835 +(% 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]] 649 649 650 -== **6.2 AT Command input doesn't work** == 651 651 652 - Inthe 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 sendingout the command.Some serialtooldoesn'tsend **ENTER**while press the sendkey,user need to add ENTER in their string.838 +== 6.2 AT Command input doesn't work == 653 653 654 -= **7. Order Info** = 655 655 656 -Part Num ber**:**CPN01841 +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. 657 657 658 -= **8. Packing Info** = 659 659 660 - **Package Includes**:844 += 7. Order Info = 661 661 662 -* CPN01 NB-IoT Soil Moisture & EC Sensor x 1 663 -* External antenna x 1 664 664 665 - **Dimensionandweight**:847 +Part Number**:** NDS03A 666 666 667 -* Size: 195 x 125 x 55 mm 668 -* Weight: 420g 669 669 670 -= **9.Support**=850 += 8. Packing Info = 671 671 672 -* 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. 673 -* 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]] 674 674 675 - 853 +(% style="color:blue" %)**Package Includes**: 676 676 855 +* NDS03A Open/Close Door Sensor x 1 677 677 678 678 679 679 859 += 9. Support = 680 680 681 681 862 +* 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. 682 682 864 +* 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]] 683 683 684 - 685 - 686 - 687 - 688 - 689 - 690 - 691 - 692 - 693 - 694 - 695 - 696 - 697 - 698 - 699 - 700 - 701 - 702 - 703 - 704 - 705 - 706 - 866 +
- 1666596205057-567.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +179.8 KB - Content
- image-20221022234529-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +43.3 KB - Content
- image-20221022234602-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +135.7 KB - Content
- image-20221023000439-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +82.1 KB - Content
- image-20221117105556-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +133.3 KB - Content
- image-20221117114459-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +14.9 KB - Content
- image-20221117114842-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +964.1 KB - Content
- image-20221117114937-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +79.1 KB - Content
- image-20221117114949-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +33.4 KB - Content
- image-20221117115010-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +40.4 KB - Content
- image-20221117142300-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +147.8 KB - Content
- image-20221117145932-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +51.9 KB - Content
- image-20221117150312-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +8.7 KB - Content
- image-20221118092935-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +13.1 KB - Content
- image-20221118093144-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +11.7 KB - Content
- image-20221118093512-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +9.5 KB - Content
- image-20221118093658-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +12.7 KB - Content
- image-20221118094227-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +29.2 KB - Content
- image-20221118094449-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +76.5 KB - Content
- image-20221118103445-7.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +20.4 KB - Content
- image-20221118103453-8.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +46.2 KB - Content
- image-20221118103547-9.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +43.5 KB - Content