Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 37.1 >
edited by Edwin Chen
on 2022/10/22 23:46
To version < 68.1 >
edited by Xiaoling
on 2022/11/18 10:34
>
Change comment: Uploaded new attachment "image-20221118103445-7.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -CPN01- NB-IoT Outdoor Open/Close Dry Contact Sensor User Manual
1 +NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -1,34 +1,67 @@
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 +
5 +
6 +
7 +
8 +
9 +
10 +**Table of Contents：**
11 +
4 4  {{toc/}}
5 5  
6 -= **1. Introduction** =
7 7  
8 -== **1.1 ​**What is CPN01 **NB-IoT** Pulse/Contact Sensor ==
9 9  
10 -The Dragino CPN01 is an (% style="color:blue" %)**NB-IoT Dry Contact Sensor**(%%). It detects open/close status and uplinks the info to IoT server via Nb-IoT network. User can see the (% style="color:blue" %)dry contact status, open time, and open counts(%%) in the IoT Server.
11 11  
12 -The CPN01 will send periodically data every day as well as for each dry contact action. It also counts the contact open times and calculates the last open duration. Users can also disable the uplink for each open/close event, instead, device can count each open event and uplink periodically.
13 13  
14 -CPN01 has (% style="color:blue" %)Open-Alarm feature(%%), user can set this feature so CPN01 will send an alarm if the contact has been open exceeds a certain time.
18 += 1.  Introduction =
15 15  
16 -CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures.
20 +== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
17 17  
18 -NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
19 -\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
20 -\\CPN01 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
21 -\\To use CPN01, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that CPN01 supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into CPN01 to get NB-IoT network connection.
22 22  
23 -​
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 +)))
24 24  
25 -== **​1.2 Features** ==
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 +)))
26 26  
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 -* Uplink on periodically and open/close event
64 +* connect two door sensors
32 32  * Datalog feature
33 33  * Uplink periodically
34 34  * Downlink to change configure
... ... @@ -39,14 +39,41 @@
39 39  * Micro SIM card slot for NB-IoT SIM
40 40  * 8500mAh Battery for long-term use
41 41  
42 -== **1.3  Specification** ==
75 +== 1.3  Storage & Operation ==
43 43  
44 -**Common DC Characteristics:**
45 45  
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 +
46 46  * Supply Voltage: 2.1v ~~ 3.6v
47 47  * Operating Temperature: -40 ~~ 85°C
48 48  
49 -**NB-IoT Spec:**
109 +(% style="color:blue" %)**NB-IoT Spec:**
50 50  
51 51  * - B1 @H-FDD: 2100MHz
52 52  * - B3 @H-FDD: 1800MHz
... ... @@ -55,180 +55,224 @@
55 55  * - B20 @H-FDD: 800MHz
56 56  * - B28 @H-FDD: 700MHz
57 57  
58 -== **1.4 Installation** ==
118 +== 1.7  Pin Definitions and Switch ==
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]]
121 +[[image:image-20221021110429-4.png]]
63 63  
64 -[[image:image-20221021110340-2.png]]
65 65  
66 -== **1.5 ​Applications** ==
124 +=== 1.7.1  Pin Definition ===
67 67  
68 -* Open/Close Detection
69 -* Pulse meter application
70 -* Dry Contact Detection
71 71  
72 -== **1.6 Mechanical** ==
127 +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]]
73 73  
74 -​[[image:image-20221021110415-3.png]]
75 75  
76 -== ** 1.7 Pin Definitions and Switch** ==
77 77  
78 -[[image:image-20221021110429-4.png]]
131 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
79 79  
80 -=== **1.7.1 Pin Definition** ===
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]]
134 +Power on Device when putting this jumper.
83 83  
84 -=== **1.7.2 Jumper JP2(Power ON/OFF)** ===
85 85  
86 86  
87 -Power on Device when putting this jumper.
138 +=== 1.7.3  BOOT MODE / SW1 ===
88 88  
89 89  
141 +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.3 BOOT MODE / SW1** ===
143 +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: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
95 95  
96 -2) Flash: work mode, the device starts to work and send out console output for further debug
147 +=== 1.7.4  Reset Button ===
97 97  
98 98  
150 +Press to reboot the device.
99 99  
100 -=== **1.7.4 Reset Button** ===
101 101  
102 102  
103 -Press to reboot the device.
154 +=== 1.7.5  LED ===
104 104  
105 -== ==
106 106  
107 -=== **1.7.5 LED** ===
157 +The LED will blink when :
108 108  
159 +1.  Boot the device in flash mode
109 109  
110 -It will flash:
161 +2.  Send an uplink packet
111 111  
112 -1. Boot the device in flash mode
113 -1. Send an uplink packet
114 114  
115 -= **2.  Use CPN01 to communicate with IoT Server** =
116 116  
117 -== **2.1  How it works** ==
165 +== 1.8  Magnet Distance ==
118 118  
119 -The CPN01 is equipped with a NB-IoT module, the pre-loaded firmware in CPN01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01.
120 120  
121 -The diagram below shows the working flow in default firmware of CPN01:
168 +(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
122 122  
170 +(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
171 +
172 +
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 +
123 123  [[image:image-20221021110615-5.png]]
124 124  
125 -== **2.2 ​ Configure the CPN01** ==
126 126  
127 -=== **2.2.1 Test Requirement** ===
128 128  
129 -To use CPN01 in your city, make sure meet below requirements:
187 +== 2.2 ​ Configure NDS03A ==
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.
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.
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. 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
198 +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  
200 +[[image:image-20221117142300-1.png]]
201 +
137 137   ​
138 138  
139 -=== **2.2.2 Insert SIM card** ===
140 140  
205 +=== 2.2.2 Insert NB-IoT SIM card ===
206 +
207 +
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:
210 +User needs to take out the NB-IoT module and insert the SIM card like below:
144 144  
145 145  [[image:image-20221021110745-6.png]] ​
146 146  
147 -=== **2.2.3 Connect USB – TTL to CPN01 to configure it** ===
148 148  
149 -User need to configure CPN01 via serial port to set the **Server Address** / **Uplink Topic** to define where and how-to uplink packets. CPN01 support AT Commands, user can use a USB to TTL adapter to connect to CPN01 and use AT Commands to configure it, as below.
150 150  
151 -**Connection:**
216 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
152 152  
153 - USB TTL GND <~-~-~-~-> GND
154 154  
155 - USB TTL TXD <~-~-~-~-> UART_RXD
219 +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.
156 156  
157 - USB TTL RXD <~-~-~-~-> UART_TXD
221 +(% style="color:blue" %)**Connection:**
158 158  
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 +
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**
232 +* Baud:  (% style="color:red" %)**9600**
166 166  
167 -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.
234 +* Data bits:** (% style="color:red" %)8(%%)**
168 168  
236 +* Stop bits: (% style="color:red" %)**1**
237 +
238 +* Parity:  (% style="color:red" %)**None**
239 +
240 +* Flow Control: (% style="color:red" %)**None**
241 +
242 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
243 +
169 169  ​[[image:image-20221021110817-7.png]]
170 170  
171 -**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]]
246 +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'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/]]
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]]
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  
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 +
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  
272 +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.
273 +
189 189  [[image:image-20221021110956-9.png]] ​
190 190  
191 -=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** ===
192 192  
193 -This feature is supported since firmware version v1.0.1
194 194  
195 -* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
196 -* **AT+SERVADDR=120.24.4.116,5601   ** ~/~/ to set UDP server address and port
197 -* **AT+CFM=1       ** ~/~/If the server does not respond, this command is unnecessary
278 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
198 198  
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 +
199 199  ​ [[image:image-20221021111025-10.png]]
200 200  
291 +
201 201  [[image:image-20221021111033-11.png||height="241" width="576"]]
202 202  
203 203  ​
204 204  
205 -=== **2.2.6 Use MQTT protocol to uplink data** ===
206 206  
207 -This feature is supported since firmware version v110
297 +=== 2.2.6 Use MQTT protocol to uplink data ===
208 208  
209 -* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
210 -* **AT+SERVADDR=120.24.4.116,1883   ** ~/~/Set MQTT server address and port
211 -* **AT+CLIENT=CLIENT       ** ~/~/Set up the CLIENT of MQTT
212 -* **AT+UNAME=UNAME                               **~/~/Set the username of MQTT
213 -* **AT+PWD=PWD                                        **~/~/Set the password of MQTT
214 -* **AT+PUBTOPIC=NSE01_PUB                    **~/~/Set the sending topic of MQTT
215 -* **AT+SUBTOPIC=NSE01_SUB          ** ~/~/Set the subscription topic of MQTT
216 216  
300 +(% style="color:blue" %)**AT Commands:**
301 +
302 +* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
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 +
217 217  ​ [[image:image-20221021111058-12.png]]
218 218  
219 -[[image:image-20221021111108-13.png]]
220 220  
319 +[[image:image-20221021111201-16.png||height="472" width="653"]]
320 +
221 221  ​
222 222  
223 -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.
323 +MQTT protocol has a much higher power consumption compare with UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
224 224  
225 -=== **2.2.7 Use TCP protocol to uplink data** ===
226 226  
227 -This feature is supported since firmware version v110
228 228  
229 -* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
230 -* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ to set TCP server address and port
327 +=== 2.2.7 Use TCP protocol to uplink data ===
231 231  
329 +
330 +(% style="color:blue" %)**AT Commands:**
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 +
232 232  ​ [[image:image-20221021111125-14.png]]
233 233  
234 234  [[image:image-20221021111131-15.png]]
... ... @@ -235,93 +235,124 @@
235 235  
236 236  ​
237 237  
238 -=== **2.2.8 Change Update Interval** ===
239 239  
240 -User can use below command to change the **uplink interval**.
343 +=== 2.2.8 Change Update Interval ===
241 241  
242 -* **AT+TDC=600      ** ~/~/ Set Update Interval to 600s
243 243  
244 -**NOTE:**
346 +User can use below command to change the (% style="color:blue" %)**uplink interval**.
245 245  
246 -**~1. By default, the device will send an uplink message every 1 hour.**
348 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
247 247  
248 -== **2.3  Uplink Payload** ==
350 +(% style="color:red" %)**NOTE:**
249 249  
250 -In this mode, uplink payload includes 87 bytes in total by default.
352 +1.  By default, the device will send an uplink message every 4 hour.
251 251  
252 -Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
253 253  
254 -|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**2**|**2**|4
255 -|**Value**|[[Device ID>>path:#H2.4.1A0A0DeviceID]]|[[Ver>>path:#H2.4.2A0VersionInfo]]|[[BAT>>path:#H2.4.3A0BatteryInfo]]|[[Signal Strength>>path:#H2.4.4A0SignalStrength]]|MOD|[[Interrupt>>path:#H2.4.8A0DigitalInterrupt]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|Time stamp
256 256  
257 -|2|2|4|8 group
258 -|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|...
356 +== 2.3  Uplink Payload ==
259 259  
260 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
261 261  
262 -[[image:image-20221021111201-16.png||height="572" width="792"]]
359 +The uplink payload includes 26 bytes in total by default.
263 263  
264 -The payload is ASCII string, representative same HEX:
361 +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.
265 265  
266 -**0x (% style="color:red" %)__0xf867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %)_0c78__  __(% style="color:#00b0f0" %)17__  __(% style="color:#7030a0" %)01__  __(% style="color:#d60093" %)00__  __(% style="color:#a14d07" %)01 __ __(% style="color:#0020b0" %)__ __00__  __(% style="color:#420042" %)000009__  __(% style="color:#663300" %) 000002__  __(% style="color:#d60093" %)6315537bb__  __(% style="color:#663300" %)// 0100000b02000002663510fed__  __0100000e0200000263510f39 010000000000000063510e85 010000000000000063510d2e 010000000000000063510c7a 010000000000000063510bc6 010000000000000063510954 010000000000000063510882 //(%%)**
363 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
267 267  
268 -where:
269 -*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
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)
270 270  
271 -*(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
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" %)...
272 272  
273 -*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
375 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
274 274  
275 -*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
276 276  
277 -*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
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)
278 278  
279 -*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00= 0
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)
280 280  
281 -*(% style="color:#037691" %) **Contact Status:**(%%) 0x00= 0
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" %)......
282 282  
283 -*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0
392 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
284 284  
285 -*(% style="color:#037691" %) **Total pulse:0x09 =0**
394 +[[image:image-20221117145932-2.png]]
286 286  
287 -*(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2
288 288  
289 -*(% style="color:#037691" %)**Time stamp :**(%%) 0x6315537b =1662342011
397 +The payload is ASCII string, representative same HEX:
290 290  
291 -*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000b0200002663510fed
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__(%%)**
292 292  
293 -*(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
401 +**where:**
294 294  
295 -== **2.4  Payload Explanation and Sensor Interface** ==
403 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
296 296  
297 -=== **2.4.1  Device ID** ===
405 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
298 298  
299 -By default, the Device ID equal to the last 15 bits of IMEI.
407 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
300 300  
301 -User can use **AT+DEUI** to set Device ID
409 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
302 302  
411 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
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 +=== 2.4.1  Device ID ===
426 +
427 +
428 +By default, the Device ID is equal to the last 15 bits of IMEI.
429 +
430 +User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
431 +
303 303  **Example:**
304 304  
305 305  AT+DEUI=868411056754138
306 306  
307 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
436 +The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
308 308  
309 -=== **2.4.2  Version Info** ===
310 310  
311 -Specify the software version: 0x64=100, means firmware version 1.00.
439 +=== 2.4.2  Version Info ===
312 312  
313 -For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0.
314 314  
315 -=== **2.4.3  Battery Info** ===
442 +Specify the software version: 0x64=100, which means firmware version 1.00.
316 316  
317 -Check the battery voltage for CPN01.
444 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
318 318  
446 +
447 +=== 2.4.3  Battery Info ===
448 +
449 +
450 +Check the battery voltage for NDS03A.
451 +
319 319  Ex1: 0x0B45 = 2885mV
320 320  
321 321  Ex2: 0x0B49 = 2889mV
322 322  
323 -=== **2.4.4  Signal Strength** ===
324 324  
457 +=== 2.4.4  Signal Strength ===
458 +
459 +
325 325  NB-IoT Network signal Strength.
326 326  
327 327  **Ex1: 0x1d = 29**
... ... @@ -336,58 +336,47 @@
336 336  
337 337  **99**    Not known or not detectable
338 338  
339 -=== **2.4.5 Calculate Flag** ===
340 340  
341 -The calculate flag is a user define field, IoT server can use this filed to handle different meter with different pulse factor. For example, if there are 100 water meters, meter 1 ~~50 are 1 liter/pulse and meter 51 ~~ 100 has 1.5 liter/pulse.
475 +=== 2.4.5  Disalarm: (default: 0) ===
342 342  
343 -User can set calculate flag to 1 for meter 1~~50 and 2 for meter 51 ~~ 100, So IoT Server can use this field for calculation.
344 344  
345 -Default value: 0. 
478 +(% 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.
346 346  
347 -Range (6 bits): (b)000000 ~~ (b) 111111
480 +(% 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.
348 348  
349 -=== **2.4.6  Alarm** ===
482 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
350 350  
351 -See [[Alarm Base on Timeout>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H3.5AlarmBaseonTimeout]]
352 352  
353 -=== **2.4.7 Contact Status** ===
485 +=== 2.4.6  Keep Status & Keep Time ===
354 354  
355 -0: Open
356 356  
357 -1: Close
488 +Shows the configure value of Alarm Base on Timeout Feature
358 358  
359 -=== **2.4.8 Total pulse** ===
360 360  
361 -Total pulse/counting base on dry [[contact trigger event>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.2SensorConfiguration2CFPORT3D4]]
491 +=== 2.4.7  Timestamp ===
362 362  
363 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
364 364  
365 -=== **2.4.9 The last open duration** ===
494 +Timestamp : 0x6315537b =1662342011
366 366  
367 -Dry Contact last open duration.
368 368  
369 -Unit: min.
370 370  
371 -[[image:image-20221021111346-17.png||height="146" width="770"]]
498 +=== 2.4.8  Switch Dual Channel Mode ===
372 372  
373 373  
374 -=== **2.4.10  Timestamp** ===
501 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
375 375  
376 -Time stamp : 0x6315537b =1662342011
377 377  
378 -Convert Unix timestamp to time 2022-9-5 9:40:11.
504 +== 2.5  Downlink Payload ==
379 379  
380 -**~ **
381 381  
382 -== **2.5  Downlink Payload** ==
507 +By default, NDS03A prints the downlink payload to console port.
383 383  
384 -By default, CPN01 prints the downlink payload to console port.
385 -
386 386  [[image:image-20221021111414-18.png]] ​
387 387  
511 +
388 388  **Examples:**
389 389  
390 -* **Set TDC**
514 +* (% style="color:#037691" %)**Set TDC**
391 391  
392 392  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
393 393  
... ... @@ -395,171 +395,236 @@
395 395  
396 396  Payload:    01 00 00 3C    TDC=60S
397 397  
398 -* **Reset**
522 +* (% style="color:#037691" %)**Reset**
399 399  
400 -If payload = 0x04FF, it will reset the NSE01
524 +If payload = 0x04FF, it will reset the NDS03A
401 401  
402 -* **INTMOD**
526 +* (% style="color:#037691" %)**INTMOD**
403 403  
404 404  Downlink Payload: 06000003, Set AT+INTMOD=3
405 405  
406 -== **2.6  ​LED Indicator** ==
407 407  
408 -The CPN01 has an internal LED which is to show the status of different state.
409 409  
410 -* When power on, CPN01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
411 -* Then the LED will be on for 1 second means device is boot normally.
412 -* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
532 +== 2.6  ​LED Indicator ==
533 +
534 +
535 +The NDS03A has an internal LED which is to show the status of different states.
536 +
537 +* When the device starts normally, the LED will light up for 1 second.
538 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
413 413  * For each uplink probe, LED will be on for 500ms.
414 414  
415 -== **2.7  Alarm Base on Timeout** ==
541 +== 2.7  Alarm Base on Timeout ==
416 416  
417 -CPL01 can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are:
418 418  
544 +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:
419 419  
420 -**~1. Keep Status: Status to be monitor**
421 421  
547 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
548 +
422 422  Keep Status = 1: Monitor Close to Open event
423 423  
424 424  Keep Status = 0: Monitor Open to Close event
425 425  
426 426  
427 -**2. Keep Time: Timeout to send an Alarm**
554 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
428 428  
429 429  Range 0 ~~ 65535(0xFFFF) seconds.
430 430  
431 431  If keep time = 0, Disable Alarm Base on Timeout feature.
432 432  
433 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
560 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
434 434  
435 435  
436 -**AT Command** to configure:
563 +(% style="color:blue" %)**AT Command to configure:**
437 437  
438 -**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.
565 +(% style="color:blue" %)**PB14 PIN:**
439 439  
440 -**AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm.
567 +(% 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.
441 441  
442 -== **2.8 Set debug mode** ==
569 +(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
443 443  
444 -Feature: Enable or Disable debug mode
445 445  
572 +(% style="color:blue" %)**PB15 PIN:**
446 446  
447 -**AT Command: AT+DEBUG**
574 +(% style="color:#037691" %)**AT+TTRIG2=1,30**
448 448  
576 +(% style="color:#037691" %)**AT+TTRIG2=0,0 **
577 +
578 +
579 +== 2.8  Set debug mode ==
580 +
581 +
582 +Feature: Enable or Disable debug mode
583 +
584 +(% style="color:blue" %)**AT Command: AT+DEBUG**
585 +
449 449  [[image:image-20221021111629-21.png]]
450 450  
451 -== **2.9 Clear Flash Record** ==
452 452  
589 +
590 +== 2.9  Clear Flash Record ==
591 +
592 +
453 453  Feature: Clear flash storage for data log feature.
454 454  
455 -**AT Command: AT+CLRDTA**
595 +(% style="color:blue" %)**AT Command: AT+CLRDTA**
456 456  
457 457  [[image:image-20221021111527-19.png]]
458 458  
459 -== ** 2.10 Set trigger mode** ==
460 460  
461 -➢ AT Command: **AT+TTRMOD**
462 462  
463 -Feature: Set the trigger interrupt mode.
601 +== 2.10  Count Mod ==
464 464  
465 -[[image:image-20221021111552-20.png]]
466 466  
467 -== **2.11 Set the calculate flag** ==
604 +(% style="color:blue" %)**AT Command: AT+COUNTMOD**
468 468  
469 -Feature: Set the calculate flag
606 +[[image:image-20221118092935-1.png]]
470 470  
471 -**AT Command: AT+CALCFLAG**
472 472  
473 -[[image:image-20221021111711-22.png]]
474 474  
475 -== **2.12 Set count number** ==
610 +== 2.11  Interrupt Pin Channel Mod ==
476 476  
477 -Feature: Manually set the count number
478 478  
479 -**AT Command: AT+SETCNT**
613 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
480 480  
481 -[[image:image-20221021111748-24.png]]
615 +[[image:image-20221118093144-2.png]]
482 482  
483 -== **2.13 Set the number of data to be uploaded and the recording time** ==
484 484  
485 -➢ AT Command:
486 486  
487 -AT+TR=900  ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
619 +== 2.12 TTRIG1/2 timeout status alarm ==
488 488  
489 489  
490 -AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
622 +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.
491 491  
492 -== **2.14 Read or Clear cached data** ==
624 +(% style="color:blue" %)**AT Command: AT+TTRALARM**
493 493  
494 -➢ AT Command:
626 +[[image:image-20221118093512-3.png]]
495 495  
496 -AT+CDP    ~/~/ Read cached data
497 497  
498 -[[image:image-20221021111810-25.png||height="364" width="797"]]
499 499  
630 +== 2.13  Select counting mode ==
500 500  
501 -AT+CDP=0    ~/~/ Clear cached data ​
502 502  
503 -== **2.15  ​Firmware Change Log** ==
633 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
504 504  
505 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
635 +When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
506 506  
507 -Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
637 +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.
508 508  
509 -== **2.16  ​Battery Analysis** ==
639 +[[image:image-20221118093658-4.png]]
510 510  
511 -=== **2.16.1  ​Battery Type** ===
512 512  
513 -The CPN01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
514 514  
515 -The battery is designed to last for several years depends on the actually use environment and update interval. 
516 516  
517 -The battery related documents as below:
644 +== 2.14  Set the number of data to be uploaded and the recording time ==
518 518  
646 +
647 +(% style="color:blue" %)**AT Command:**
648 +
649 +(% 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)
650 +
651 +(% 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.
652 +
653 +
654 +== 2.15  Read or Clear cached data ==
655 +
656 +
657 +(% style="color:blue" %)**AT Command:**
658 +
659 +(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
660 +
661 +(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
662 +
663 +[[image:image-20221118094227-5.png]]
664 +
665 +
666 +
667 +== 2.16  ​Firmware Change Log ==
668 +
669 +
670 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
671 +
672 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
673 +
674 +
675 +
676 +== 2.17  ​Battery Analysis ==
677 +
678 +
679 +=== 2.17.1  ​Battery Type ===
680 +
681 +
682 +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.
683 +
684 +The battery is designed to last for several years depends on the actual use environment and update interval. 
685 +
686 +The battery-related documents as below:
687 +
519 519  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
689 +
520 520  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
691 +
521 521  * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
522 522  
523 523  [[image:image-20221021111911-26.png]] ​
524 524  
525 -=== **2.16.2  Power consumption Analyze** ===
526 526  
697 +
698 +=== 2.17.2  Power consumption Analyze ===
699 +
700 +
527 527  Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
528 528  
529 529  Instruction to use as below:
530 530  
531 -**Step 1:  **Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
705 +(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
532 532  
533 -**Step 2: ** Open it and choose
707 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
534 534  
535 535  * Product Model
710 +
536 536  * Uplink Interval
712 +
537 537  * Working Mode
538 538  
539 539  And the Life expectation in difference case will be shown on the right.
540 540  
541 -[[image:image-20221021111923-27.png||height="253" width="783"]] ​
717 +[[image:1666596205057-567.png]] ​
542 542  
543 -=== **2.16.3  ​Battery Note** ===
544 544  
720 +
721 +=== 2.17.3  ​Battery Note ===
722 +
723 +
545 545  The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
546 546  
547 -=== **2.16.4  Replace the battery** ===
548 548  
549 -The default battery pack of CPN01 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
550 550  
551 -= **3. ​ Access NB-IoT Module** =
728 +=== 2.17.4  Replace the battery ===
552 552  
730 +
731 +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).
732 +
733 +
734 +
735 += 3. ​ Access NB-IoT Module =
736 +
737 +
553 553  Users can directly access the AT command set of the NB-IoT module.
554 554  
555 555  The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
556 556  
557 -[[image:image-20221021112006-28.png]] ​
742 +[[image:image-20221118094449-6.png]] ​
558 558  
559 -= **4.  Using the AT Commands** =
560 560  
561 -== **4.1  Access AT Commands** ==
562 562  
746 += 4.  Using the AT Commands =
747 +
748 +
749 +== 4.1  Access AT Commands ==
750 +
751 +
563 563  See this link for detail:  [[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
564 564  
565 565  AT+<CMD>?  : Help on <CMD>
... ... @@ -570,8 +570,9 @@
570 570  
571 571  AT+<CMD>=?  : Get the value
572 572  
573 -**General Commands**      
574 574  
763 +(% style="color:blue" %)**General Commands**      
764 +
575 575  AT  : Attention       
576 576  
577 577  AT?  : Short Help     
... ... @@ -594,35 +594,41 @@
594 594  
595 595  AT+SERVADDR  : Server Address
596 596  
597 -AT+TR      : Get or Set record time"
787 +AT+TR      :  Get or Set record time
598 598  
599 -
600 600  AT+NOUD      : Get or Set the number of data to be uploaded
601 601  
791 +AT+CDP     :  Read or Clear cached data
602 602  
603 -AT+CDP     : Read or Clear cached data
793 +AT+ DEBUG   : Enable or Disable debug mode
604 604  
795 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
605 605  
606 -AT+ DEBUG   : Enable or Disable debug mode
797 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
607 607  
608 -AT+ TTRIG   : Get or Set Alarm Base on Timeout
799 +AT+COUNTMOD  :  Get or Set the count mode
609 609  
610 -AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
801 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
611 611  
612 -AT+ CALCFLAG   : Get or Set the calculate flag
803 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
613 613  
614 -AT+ CLRC   : Clear current door open count
805 +AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
615 615  
616 -**COAP Management**      
807 +AT+ CLRC   :  Clear current door open count
617 617  
809 +
810 +(% style="color:blue" %)**COAP Management**      
811 +
618 618  AT+URI            : Resource parameters
619 619  
620 -**UDP Management**
621 621  
815 +(% style="color:blue" %)**UDP Management**
816 +
622 622  AT+CFM          : Upload confirmation mode (only valid for UDP)
623 623  
624 -**MQTT Management**
625 625  
820 +(% style="color:blue" %)**MQTT Management**
821 +
626 626  AT+CLIENT               : Get or Set MQTT client
627 627  
628 628  AT+UNAME  : Get or Set MQTT Username
... ... @@ -633,86 +633,65 @@
633 633  
634 634  AT+SUBTOPIC  : Get or Set MQTT subscription topic
635 635  
636 -**Information**          
637 637  
833 +(% style="color:blue" %)**Information**          
834 +
638 638  AT+FDR  : Factory Data Reset
639 639  
640 640  AT+PWORD  : Serial Access Password
641 641  
642 -= **​5.  FAQ** =
643 643  
644 -== **5.1 ​ How to Upgrade Firmware** ==
645 645  
646 -User can upgrade the firmware for 1) bug fix, 2) new feature release.
841 += ​5.  FAQ =
647 647  
648 -Please see this link for how to upgrade:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
649 649  
650 -**Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.**
844 +== 5.1 ​ How to Upgrade Firmware ==
651 651  
652 -== **5.2  Can I calibrate CPN01 to different soil types?** ==
653 653  
654 -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]].
847 +User can upgrade the firmware for 1) bug fix, 2) new feature release.
655 655  
656 -= **6.  Trouble Shooting** =
849 +Please see this link for how to upgrade:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
657 657  
658 -== **6.1  ​Connection problem when uploading firmware** ==
851 +(% 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.**
659 659  
660 -**Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
661 661  
662 -== **6.2  AT Command input doesn't work** ==
663 663  
664 -In the case if user can see the console output but can't type input to the device. Please check if you already include the **ENTER** while sending out the command. Some serial tool doesn't send **ENTER** while press the send key, user need to add ENTER in their string.
855 += 6.  Trouble Shooting =
665 665  
666 -= **7. ​ Order Info** =
667 667  
668 -Part Number**:** CPN01
858 +== 6.1  ​Connection problem when uploading firmware ==
669 669  
670 -= **8.  Packing Info** =
671 671  
672 -**Package Includes**:
861 +(% style="color:blue" %)**Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
673 673  
674 -* CPN01 NB-IoT Soil Moisture & EC Sensor x 1
675 -* External antenna x 1
676 676  
677 -**Dimension and weight**:
678 678  
679 -* Size: 195 x 125 x 55 mm
680 -* Weight:   420g
865 +== 6.2  AT Command input doesn't work ==
681 681  
682 -= **9.  Support** =
683 683  
684 -* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
685 -* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
868 +In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER** (%%)while press the send key, user need to add ENTER in their string.
686 686  
687 -​
688 688  
689 689  
872 += 7. ​ Order Info =
690 690  
691 691  
875 +Part Number**:** NDS03A
692 692  
693 693  
694 694  
879 += 8.  Packing Info =
695 695  
696 696  
882 +(% style="color:blue" %)**Package Includes**:
697 697  
884 +* NDS03A Open/Close Door Sensor x 1
698 698  
886 += 9.  Support =
699 699  
700 700  
889 +* 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.
701 701  
891 +* 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]]
702 702  
703 -
704 -
705 -
706 -
707 -
708 -
709 -
710 -
711 -
712 -
713 -
714 -
715 -
716 -
717 -
718 -
893 +​
1666596205057-567.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +179.8 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

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0