Summary

• Page properties (3 modified, 0 added, 0 removed)
• Attachments (0 modified, 5 added, 0 removed)
  • 1666596205057-567.png
  • image-20221117105556-1.png
  • image-20221117114459-2.png
  • image-20221117114842-3.png
  • image-20221117114937-4.png

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,29 +1,63 @@
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		-{{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.
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.
	10	+**Table of Contents：**
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
	13	+
	14	+
	15	+
	16	+= 1.  Introduction =
	17	+
	18	+
	19	+== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
	20	+
	21	+
	22	+(((
	23	+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.
	24	+)))
	25	+
	26	+(((
	27	+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.
	28	+)))
	29	+
	30	+(((
	31	+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.
	32	+)))
	33	+
	34	+(((
	35	+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.
	36	+)))
	37	+
	38	+(((
	39	+NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
	40	+)))
	41	+
	42	+(((
	43	+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.
	44	+)))
	45	+
	46	+(((
	47	+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)
	48	+)))
	49	+
	50	+(((
	51	+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.
	52	+)))
	53	+
	54	+
23	23	​
24	24
25		-== **​1.2 Features** ==
26	26
	58	+== ​1.2  Features ==
	59	+
	60	+
27	27	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
28	28	* Open/Close detect
29	29	* Open/Close statistics
...	...	@@ -39,14 +39,15 @@
39	39	* Micro SIM card slot for NB-IoT SIM
40	40	* 8500mAh Battery for long-term use
41	41
42		-== **1.3  Specification** ==
	76	+== 1.3  Specification ==
43	43
44		-**Common DC Characteristics:**
45	45
	79	+(% style="color:blue" %)**Common DC Characteristics:**
	80	+
46	46	* Supply Voltage: 2.1v ~~ 3.6v
47	47	* Operating Temperature: -40 ~~ 85°C
48	48
49		-**NB-IoT Spec:**
	84	+(% style="color:blue" %)**NB-IoT Spec:**
50	50
51	51	* - B1 @H-FDD: 2100MHz
52	52	* - B3 @H-FDD: 1800MHz
...	...	@@ -55,76 +55,99 @@
55	55	* - B20 @H-FDD: 800MHz
56	56	* - B28 @H-FDD: 700MHz
57	57
58		-== **1.4 Installation** ==
	93	+== 1.4  Installation ==
59	59
	95	+
60	60	Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
61	61
62	62	[[image:image-20221021110329-1.png]]
63	63
	100	+
64	64	[[image:image-20221022234602-2.png||height="288" width="922"]]
65	65
66	66
67		-== **1.5 ​Applications** ==
68	68
	105	+== 1.5 ​ Applications ==
	106	+
	107	+
69	69	* Open/Close Detection
70	70	* Pulse meter application
71	71	* Dry Contact Detection
72	72
73		-== **1.6 Mechanical** ==
	112	+== 1.6  Mechanical ==
74	74
	114	+
75	75	​[[image:image-20221021110415-3.png]]
76	76
77		-== ** 1.7 Pin Definitions and Switch** ==
78	78
	118	+
	119	+== 1.7  Pin Definitions and Switch ==
	120	+
	121	+
79	79	[[image:image-20221021110429-4.png]]
80	80
81		-=== **1.7.1 Pin Definition** ===
82	82
	125	+=== 1.7.1  Pin Definition ===
	126	+
	127	+
83	83	CPN01 is pre-configured to connect to two external wires. The other pins are not used. If user wants to know more about other pins, please refer to the **[[LSN50v2 User Manual>>doc:Main.User Manual for LoRaWAN End Nodes.LSN50 & LSN50-V2 - LoRaWAN Sensor Node User Manual.WebHome]]**.
84	84
85	85
86		-=== **1.7.2 Jumper JP2(Power ON/OFF)** ===
87	87
	132	+=== 1.7.2  Jumper JP2(Power ON/OFF) ===
	133	+
	134	+
88	88	Power on Device when putting this jumper.
89	89
90	90
91		-=== **1.7.3 BOOT MODE / SW1** ===
92	92
	139	+=== 1.7.3  BOOT MODE / SW1 ===
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. The firmware won't run.
95	95
96		-2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
	142	+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.
97	97
	144	+2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
98	98
99		-=== **1.7.4 Reset Button** ===
100	100
101	101
	148	+=== 1.7.4  Reset Button ===
	149	+
	150	+
102	102	Press to reboot the device.
103	103
104	104
105		-=== **1.7.5 LED** ===
106	106
	155	+=== 1.7.5  LED ===
107	107
	157	+
108	108	The LED will blink when :
109	109
110		-1. Boot the device in flash mode
111		-1. Send an uplink packet
	160	+1.  Boot the device in flash mode
112	112
113		-= **2.  Use CPN01 to communicate with IoT Server** =
	162	+2.  Send an uplink packet
114	114
115		-== **2.1  How it works** ==
116	116
117		-The CPN01 is equipped with an NB-IoT module, the pre-loaded firmware in CPN01 will get **Open/Close Event or Count** from sensor and send the value to the NB-IoT network. The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01.
118	118
	166	+= 2.  Use CPN01 to communicate with IoT Server =
	167	+
	168	+
	169	+== 2.1  How it works ==
	170	+
	171	+
	172	+The CPN01 is equipped with an NB-IoT module, the pre-loaded firmware in CPN01 will get (% style="color:blue" %)**Open/Close Event or Count**(%%) from sensor and send the value to the NB-IoT network. The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01.
	173	+
119	119	The diagram below shows the working flow in the default firmware of CPN01:
120	120
121	121	[[image:image-20221021110615-5.png]]
122	122
123	123
124		-== **2.2 ​ Configure CPN01** ==
125	125
126		-=== **2.2.1 Test Requirement** ===
	180	+== 2.2 ​ Configure CPN01 ==
127	127
	182	+
	183	+=== 2.2.1 Test Requirement ===
	184	+
	185	+
128	128	To use CPN01 in your city, make sure to meet below requirements:
129	129
130	130	* Your local operator has already distributed an NB-IoT Network.
...	...	@@ -131,14 +131,16 @@
131	131	* The local NB-IoT network used the band that CPN01 supports.
132	132	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
133	133
134		-Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The CPN01 will use CoAP(120.24.4.116:5683) or raw UDP(120.24.4.116:5601) or MQTT(120.24.4.116:1883)or TCP(120.24.4.116:5600)protocol to send data to the test server.
	192	+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** (% 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.
135	135
136	136	[[image:image-20221023000439-3.png]]
137	137
138	138	​
139	139
140		-=== **2.2.2 Insert SIM card** ===
141	141
	199	+=== 2.2.2 Insert NB-IoT SIM card ===
	200	+
	201	+
142	142	Insert the NB-IoT Card get from your provider.
143	143
144	144	User needs to take out the NB-IoT module and insert the SIM card like below:
...	...	@@ -146,26 +146,33 @@
146	146	[[image:image-20221021110745-6.png]] ​
147	147
148	148
149		-=== **2.2.3 Connect USB – TTL to CPN01 to configure it** ===
150	150
151		-User need to configure CPN01 via serial port to set the **Server Address** / **Uplink Topic** to define where and how-to uplink packets. CPN01 support AT Commands, user can use a USB to TTL adapter to connect to CPN01 and use AT Commands to configure it, as below.
	210	+=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
152	152
153		-**Connection:**
154	154
155		- USB TTL GND <~-~-~-~-> GND
	213	+User need to configure CPN01 via serial port to set the (% style="color:red" %)**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.
156	156
157		- USB TTL TXD <~-~-~-~-> UART_RXD
	215	+(% style="color:blue" %)**Connection:**
158	158
159		- USB TTL RXD <~-~-~-~-> UART_TXD
	217	+(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
160	160
	219	+(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD**
	220	+
	221	+(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD**
	222	+
	223	+
161	161	In the PC, use below serial tool settings:
162	162
163		-* Baud:  **9600**
164		-* Data bits:** 8**
165		-* Stop bits: **1**
166		-* Parity:  **None**
167		-* Flow Control: **None**
	226	+* Baud:  (% style="color:red" %)**9600**
168	168
	228	+* Data bits:** (% style="color:red" %)8(%%)**
	229	+
	230	+* Stop bits: (% style="color:red" %)**1**
	231	+
	232	+* Parity:  (% style="color:red" %)**None**
	233	+
	234	+* Flow Control: (% style="color:red" %)**None**
	235	+
169	169	Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
170	170
171	171	​[[image:image-20221021110817-7.png]]
...	...	@@ -173,67 +173,93 @@
173	173	CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
174	174
175	175
176		-**Note: the valid AT Commands can be found at:  **[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
	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]]
177	177
178		-=== **2.2.4 Use CoAP protocol to uplink data** ===
179	179
180		-**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/]]
181	181
182		-**Use below commands:**
	247	+=== 2.2.4 Use CoAP protocol to uplink data ===
183	183
184		-* **AT+PRO=1**   ~/~/ Set to use CoAP protocol to uplink
185		-* **AT+SERVADDR=120.24.4.116,5683   ** ~/~/ to set CoAP server address and port
186		-* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path
187	187
	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 CPN01:**
	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	+
188	188	For parameter description, please refer to AT command set
189	189
190	190	[[image:image-20221021110948-8.png]]
191	191
192		-After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server.
193	193
	266	+After configuring the server address and (% style="color:green" %)**reset CPN01**(%%) (via AT+ATZ ), CPN01 will start to uplink sensor values to the CoAP server.
	267	+
194	194	[[image:image-20221021110956-9.png]] ​
195	195
196		-=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** ===
197	197
198		-This feature is supported since firmware version v1.0.1
199	199
200		-* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
201		-* **AT+SERVADDR=120.24.4.116,5601   ** ~/~/ to set UDP server address and port
202		-* **AT+CFM=1       ** ~/~/If the server does not respond, this command is unnecessary
	272	+=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
203	203
	274	+
	275	+(% style="color:blue" %)**AT Commands:**
	276	+
	277	+* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
	278	+
	279	+* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  Set UDP server address and port
	280	+
	281	+* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
	282	+
204	204	​ [[image:image-20221021111025-10.png]]
205	205
	285	+
206	206	[[image:image-20221021111033-11.png||height="241" width="576"]]
207	207
208	208	​
209	209
210		-=== **2.2.6 Use MQTT protocol to uplink data** ===
211	211
212		-This feature is supported since firmware version v110
	291	+=== 2.2.6 Use MQTT protocol to uplink data ===
213	213
214		-* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
215		-* **AT+SERVADDR=120.24.4.116,1883   ** ~/~/Set MQTT server address and port
216		-* **AT+CLIENT=CLIENT       ** ~/~/Set up the CLIENT of MQTT
217		-* **AT+UNAME=UNAME                               **~/~/Set the username of MQTT
218		-* **AT+PWD=PWD                                        **~/~/Set the password of MQTT
219		-* **AT+PUBTOPIC=NSE01_PUB                    **~/~/Set the sending topic of MQTT
220		-* **AT+SUBTOPIC=NSE01_SUB          ** ~/~/Set the subscription topic of MQTT
221	221
	294	+(% style="color:blue" %)**AT Commands:**
	295	+
	296	+* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
	297	+
	298	+* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
	299	+
	300	+* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
	301	+
	302	+* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
	303	+
	304	+* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
	305	+
	306	+* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/  Set the sending topic of MQTT
	307	+
	308	+* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
	309	+
222	222	​ [[image:image-20221021111058-12.png]]
223	223
224		-[[image:image-20221021111108-13.png]]
225	225
	313	+[[image:image-20221021111201-16.png||height="472" width="653"]]
	314	+
226	226	​
227	227
228		-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.
	317	+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.
229	229
230		-=== **2.2.7 Use TCP protocol to uplink data** ===
231	231
232		-This feature is supported since firmware version v110
233	233
234		-* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
235		-* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ to set TCP server address and port
	321	+=== 2.2.7 Use TCP protocol to uplink data ===
236	236
	323	+
	324	+(% style="color:blue" %)**AT Commands:**
	325	+
	326	+* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
	327	+
	328	+* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
	329	+
237	237	​ [[image:image-20221021111125-14.png]]
238	238
239	239	[[image:image-20221021111131-15.png]]
...	...	@@ -240,85 +240,103 @@
240	240
241	241	​
242	242
243		-=== **2.2.8 Change Update Interval** ===
244	244
245		-User can use below command to change the **uplink interval**.
	337	+=== 2.2.8 Change Update Interval ===
246	246
247		-* **AT+TDC=600      ** ~/~/ Set Update Interval to 600s
248	248
249		-**NOTE:**
	340	+User can use below command to change the (% style="color:blue" %)**uplink interval**.
250	250
251		-**~1. By default, the device will send an uplink message every 1 hour.**
	342	+* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
252	252
253		-== **2.3  Uplink Payload** ==
	344	+(% style="color:red" %)**NOTE:**
254	254
255		-In this mode, uplink payload includes 87 bytes in total by default.
	346	+1.  By default, the device will send an uplink message every 1 hour.
256	256
	348	+
	349	+
	350	+== 2.3  Uplink Payload ==
	351	+
	352	+
	353	+The uplink payload includes 123 bytes in total by default.
	354	+
257	257	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.
258	258
259		-|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**2**|**2**|4
260		-|**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
261	261
262		-|2|2|4|8 group
263		-|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|...
	358	+(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
	359	+|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:60px" %)**3**
	360	+|=(% style="width: 96px;" %)**Value**|(% style="width:84px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:44px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:121px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:52px" %)MOD|(% style="width:84px" %)[[ Calculate Flag>>||anchor="H2.4.5A0CalculateFlag"]]|(% style="width:116px" %)[[Contact Status>>||anchor="H2.4.7A0ContactStatus"]]|(% style="width:57px" %)[[Alarm>>||anchor="H2.4.6A0Alarm"]]|(% style="width:91px" %)[[Total pulse>>||anchor="H2.4.8A0Totalpulse"]]
264	264
	362	+(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
	363	+|(% style="width:100px" %)**3**|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:100px" %)**3**|(% style="width:80px" %)4|(% style="width:50px" %)**8 group**
	364	+|(% style="width:176px" %)[[The last open duration>>||anchor="H2.4.9A0Thelastopenduration"]]|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% style="width:115px" %)Contact Status|(% style="width:92px" %)Total pulse|(% style="width:169px" %)The last open duration|(% style="width:97px" %)Time stamp|(% style="width:74px" %)...
	365	+
265	265	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
266	266
267	267	[[image:image-20221021111201-16.png||height="572" width="792"]]
268	268
	370	+
269	269	The payload is ASCII string, representative same HEX:
270	270
271		-**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 //(%%)**
	373	+**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0c78__(% style="color:#00b0f0" %) __17__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__ (% style="color:#660066" %)__00__ (% style="color:#aaaa40" %)__000009__(% style="color:#663300" %) __000002__ (% style="color:#d60093" %)__6315537b__ (% style="color:#660066" %)__01 00000b 02 0000026 63510fed__ (%%)__0100000e0200000263510f39__ __010000000000000063510e85__ __010000000000000063510d2e__ __010000000000000063510c7a__ __010000000000000063510bc6__ __010000000000000063510954__ __010000000000000063510882 __**
272	272
273		-where:
274		-*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
	375	+**where:**
275	275
276		-*(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
	377	+* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
277	277
278		-*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
	379	+* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
279	279
280		-*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
	381	+* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
281	281
282		-*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
	383	+* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
283	283
284		-*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00= 0
	385	+* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
285	285
286		-*(% style="color:#037691" %) **Contact Status:**(%%) 0x00= 0
	387	+* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
287	287
288		-*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0
	389	+* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
289	289
290		-*(% style="color:#037691" %) **Total pulse:0x09 =0**
	391	+* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
291	291
292		-*(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2
	393	+* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
293	293
294		-*(% style="color:#037691" %)**Time stamp :**(%%) 0x6315537b =1662342011
	395	+* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
295	295
296		-*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000b0200002663510fed
	397	+* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
297	297
298		-*(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
	399	+* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
299	299
300		-== **2.4  Payload Explanation and Sensor Interface** ==
	401	+* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
301	301
302		-=== **2.4.1  Device ID** ===
	403	+== 2.4  Payload Explanation and Sensor Interface ==
303	303
304		-By default, the Device ID equal to the last 15 bits of IMEI.
305	305
306		-User can use **AT+DEUI** to set Device ID
	406	+=== 2.4.1  Device ID ===
307	307
	408	+
	409	+By default, the Device ID is equal to the last 15 bits of IMEI.
	410	+
	411	+User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
	412	+
308	308	**Example:**
309	309
310	310	AT+DEUI=868411056754138
311	311
312		-The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
	417	+The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
313	313
314		-=== **2.4.2  Version Info** ===
315	315
316		-Specify the software version: 0x64=100, means firmware version 1.00.
317	317
318		-For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0.
	421	+=== 2.4.2  Version Info ===
319	319
320		-=== **2.4.3  Battery Info** ===
321	321
	424	+Specify the software version: 0x64=100, which means firmware version 1.00.
	425	+
	426	+For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
	427	+
	428	+
	429	+
	430	+=== 2.4.3  Battery Info ===
	431	+
	432	+
322	322	Check the battery voltage for CPN01.
323	323
324	324	Ex1: 0x0B45 = 2885mV
...	...	@@ -325,8 +325,11 @@
325	325
326	326	Ex2: 0x0B49 = 2889mV
327	327
328		-=== **2.4.4  Signal Strength** ===
329	329
	440	+
	441	+=== 2.4.4  Signal Strength ===
	442	+
	443	+
330	330	NB-IoT Network signal Strength.
331	331
332	332	**Ex1: 0x1d = 29**
...	...	@@ -341,10 +341,13 @@
341	341
342	342	**99**    Not known or not detectable
343	343
344		-=== **2.4.5 Calculate Flag** ===
345	345
346		-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.
347	347
	460	+=== 2.4.5  Calculate Flag ===
	461	+
	462	+
	463	+The calculate flag is a user defined field, IoT server can use this filed to handle different meters with different pulse factors. For example, if there are 100 water meters, meter 1~~50 are 1 liter/pulse and meter 51 ~~ 100 has 1.5 liter/pulse.
	464	+
348	348	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.
349	349
350	350	Default value: 0.
...	...	@@ -351,24 +351,36 @@
351	351
352	352	Range (6 bits): (b)000000 ~~ (b) 111111
353	353
354		-=== **2.4.6  Alarm** ===
355	355
356		-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]]
357	357
358		-=== **2.4.7 Contact Status** ===
	473	+=== 2.4.6  Alarm ===
359	359
	475	+
	476	+See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
	477	+
	478	+
	479	+
	480	+=== 2.4.7  Contact Status ===
	481	+
	482	+
360	360	0: Open
361	361
362	362	1: Close
363	363
364		-=== **2.4.8 Total pulse** ===
365	365
366		-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]]
367	367
	489	+=== 2.4.8  Total pulse ===
	490	+
	491	+
	492	+Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
	493	+
368	368	Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
369	369
370		-=== **2.4.9 The last open duration** ===
371	371
	497	+
	498	+=== 2.4.9  The last open duration ===
	499	+
	500	+
372	372	Dry Contact last open duration.
373	373
374	374	Unit: min.
...	...	@@ -376,23 +376,28 @@
376	376	[[image:image-20221021111346-17.png||height="146" width="770"]]
377	377
378	378
379		-=== **2.4.10  Timestamp** ===
380	380
381		-Time stamp : 0x6315537b =1662342011
	509	+=== 2.4.10  Timestamp ===
382	382
	511	+
	512	+Timestamp : 0x6315537b =1662342011
	513	+
383	383	Convert Unix timestamp to time 2022-9-5 9:40:11.
384	384
385	385	**~ **
386	386
387		-== **2.5  Downlink Payload** ==
388	388
	519	+== 2.5  Downlink Payload ==
	520	+
	521	+
389	389	By default, CPN01 prints the downlink payload to console port.
390	390
391	391	[[image:image-20221021111414-18.png]] ​
392	392
	526	+
393	393	**Examples:**
394	394
395		-* **Set TDC**
	529	+* (% style="color:#037691" %)**Set TDC**
396	396
397	397	If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
398	398
...	...	@@ -400,36 +400,39 @@
400	400
401	401	Payload:    01 00 00 3C    TDC=60S
402	402
403		-* **Reset**
	537	+* (% style="color:#037691" %)**Reset**
404	404
405	405	If payload = 0x04FF, it will reset the NSE01
406	406
407		-* **INTMOD**
	541	+* (% style="color:#037691" %)**INTMOD**
408	408
409	409	Downlink Payload: 06000003, Set AT+INTMOD=3
410	410
411		-== **2.6  ​LED Indicator** ==
412	412
413		-The CPN01 has an internal LED which is to show the status of different state.
414	414
415		-* 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)
416		-* Then the LED will be on for 1 second means device is boot normally.
	547	+== 2.6  ​LED Indicator ==
	548	+
	549	+
	550	+The CPN01 has an internal LED which is to show the status of different states.
	551	+
	552	+* When the device starts normally, the LED will light up for 1 second.
417	417	* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
418	418	* For each uplink probe, LED will be on for 500ms.
419	419
420		-== **2.7  Alarm Base on Timeout** ==
	556	+== 2.7  Alarm Base on Timeout ==
421	421
422		-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:
423	423
	559	+CPN01 can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are:
424	424
425		-**~1. Keep Status: Status to be monitor**
426	426
	562	+(% style="color:blue" %)**1. Keep Status: Status to be monitor**
	563	+
427	427	Keep Status = 1: Monitor Close to Open event
428	428
429	429	Keep Status = 0: Monitor Open to Close event
430	430
431	431
432		-**2. Keep Time: Timeout to send an Alarm**
	569	+(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
433	433
434	434	Range 0 ~~ 65535(0xFFFF) seconds.
435	435
...	...	@@ -438,123 +438,164 @@
438	438	If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
439	439
440	440
441		-**AT Command** to configure:
	578	+(% style="color:blue" %)**AT Command to configure:**
442	442
443		-**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.
	580	+(% 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. CPN01 will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
444	444
445		-**AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm.
	582	+(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
446	446
447		-== **2.8 Set debug mode** ==
448	448
449		-Feature: Enable or Disable debug mode
450	450
	586	+== 2.8  Set debug mode ==
451	451
452		-**AT Command: AT+DEBUG**
453	453
	589	+Feature: Enable or Disable debug mode
	590	+
	591	+(% style="color:blue" %)**AT Command: AT+DEBUG**
	592	+
454	454	[[image:image-20221021111629-21.png]]
455	455
456		-== **2.9 Clear Flash Record** ==
457	457
	596	+
	597	+== 2.9  Clear Flash Record ==
	598	+
	599	+
458	458	Feature: Clear flash storage for data log feature.
459	459
460		-**AT Command: AT+CLRDTA**
	602	+(% style="color:blue" %)**AT Command: AT+CLRDTA**
461	461
462	462	[[image:image-20221021111527-19.png]]
463	463
464		-== ** 2.10 Set trigger mode** ==
465	465
466		-➢ AT Command: **AT+TTRMOD**
467	467
	608	+== 2.10  Set trigger mode ==
	609	+
	610	+
	611	+(% style="color:blue" %)**AT Command: AT+TTRMOD**
	612	+
468	468	Feature: Set the trigger interrupt mode.
469	469
470	470	[[image:image-20221021111552-20.png]]
471	471
472		-== **2.11 Set the calculate flag** ==
473	473
	618	+
	619	+== 2.11  Set the calculate flag ==
	620	+
	621	+
474	474	Feature: Set the calculate flag
475	475
476		-**AT Command: AT+CALCFLAG**
	624	+(% style="color:blue" %)**AT Command: AT+CALCFLAG**
477	477
478	478	[[image:image-20221021111711-22.png]]
479	479
480		-== **2.12 Set count number** ==
481	481
	629	+
	630	+== 2.12 Set count number ==
	631	+
	632	+
482	482	Feature: Manually set the count number
483	483
484		-**AT Command: AT+SETCNT**
	635	+(% style="color:blue" %)**AT Command: AT+SETCNT**
485	485
486	486	[[image:image-20221021111748-24.png]]
487	487
488		-== **2.13 Set the number of data to be uploaded and the recording time** ==
489	489
490		-➢ AT Command:
491	491
492		-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)
	641	+== 2.13  Set the number of data to be uploaded and the recording time ==
493	493
494	494
495		-AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
	644	+(% style="color:blue" %)**AT Command:**
496	496
497		-== **2.14 Read or Clear cached data** ==
	646	+(% 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)
498	498
499		-➢ AT Command:
	648	+(% style="color:#037691" %)**AT+NOUD=8 ** (%%)~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
500	500
501		-AT+CDP    ~/~/ Read cached data
502	502
	651	+
	652	+== 2.14  Read or Clear cached data ==
	653	+
	654	+
	655	+(% style="color:blue" %)**AT Command:**
	656	+
	657	+(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
	658	+
	659	+(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
	660	+
503	503	[[image:image-20221021111810-25.png||height="364" width="797"]]
504	504
505	505
506		-AT+CDP=0    ~/~/ Clear cached data ​
507	507
508		-== **2.15  ​Firmware Change Log** ==
	665	+== 2.15  ​Firmware Change Log ==
509	509
510		-Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
511	511
512		-Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
	668	+Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
513	513
514		-== **2.16  ​Battery Analysis** ==
	670	+Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
515	515
516		-=== **2.16.1  ​Battery Type** ===
517	517
518		-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.
519	519
520		-The battery is designed to last for several years depends on the actually use environment and update interval.
	674	+== 2.16  ​Battery Analysis ==
521	521
522		-The battery related documents as below:
523	523
	677	+=== 2.16.1  ​Battery Type ===
	678	+
	679	+
	680	+The CPN01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
	681	+
	682	+The battery is designed to last for several years depends on the actual use environment and update interval.
	683	+
	684	+The battery-related documents as below:
	685	+
524	524	* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	687	+
525	525	* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	689	+
526	526	* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
527	527
528	528	[[image:image-20221021111911-26.png]] ​
529	529
530		-=== **2.16.2  Power consumption Analyze** ===
531	531
	695	+
	696	+=== 2.16.2  Power consumption Analyze ===
	697	+
	698	+
532	532	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.
533	533
534	534	Instruction to use as below:
535	535
536		-**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/]]
	703	+(% 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/]]
537	537
538		-**Step 2: ** Open it and choose
	705	+(% style="color:blue" %)**Step 2: **(%%) Open it and choose
539	539
540	540	* Product Model
	708	+
541	541	* Uplink Interval
	710	+
542	542	* Working Mode
543	543
544	544	And the Life expectation in difference case will be shown on the right.
545	545
546		-[[image:image-20221021111923-27.png||height="253" width="783"]] ​
	715	+[[image:1666596205057-567.png]] ​
547	547
548		-=== **2.16.3  ​Battery Note** ===
549	549
	718	+
	719	+=== 2.16.3  ​Battery Note ===
	720	+
	721	+
550	550	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.
551	551
552		-=== **2.16.4  Replace the battery** ===
553	553
	725	+
	726	+=== 2.16.4  Replace the battery ===
	727	+
	728	+
554	554	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).
555	555
556		-= **3. ​ Access NB-IoT Module** =
557	557
	732	+
	733	+= 3. ​ Access NB-IoT Module =
	734	+
	735	+
558	558	Users can directly access the AT command set of the NB-IoT module.
559	559
560	560	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/]]
...	...	@@ -561,10 +561,14 @@
561	561
562	562	[[image:image-20221021112006-28.png]] ​
563	563
564		-= **4.  Using the AT Commands** =
565	565
566		-== **4.1  Access AT Commands** ==
567	567
	744	+= 4.  Using the AT Commands =
	745	+
	746	+
	747	+== 4.1  Access AT Commands ==
	748	+
	749	+
568	568	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]]
569	569
570	570	AT+<CMD>?  : Help on <CMD>
...	...	@@ -575,8 +575,9 @@
575	575
576	576	AT+<CMD>=?  : Get the value
577	577
578		-**General Commands**
579	579
	761	+(% style="color:blue" %)**General Commands**
	762	+
580	580	AT  : Attention
581	581
582	582	AT?  : Short Help
...	...	@@ -599,15 +599,12 @@
599	599
600	600	AT+SERVADDR  : Server Address
601	601
602		-AT+TR      : Get or Set record time"
	785	+AT+TR      :  Get or Set record time
603	603
604		-
605	605	AT+NOUD      : Get or Set the number of data to be uploaded
606	606
	789	+AT+CDP     :  Read or Clear cached data
607	607
608		-AT+CDP     : Read or Clear cached data
609		-
610		-
611	611	AT+ DEBUG   : Enable or Disable debug mode
612	612
613	613	AT+ TTRIG   : Get or Set Alarm Base on Timeout
...	...	@@ -618,16 +618,19 @@
618	618
619	619	AT+ CLRC   : Clear current door open count
620	620
621		-**COAP Management**
622	622
	802	+(% style="color:blue" %)**COAP Management**
	803	+
623	623	AT+URI            : Resource parameters
624	624
625		-**UDP Management**
626	626
	807	+(% style="color:blue" %)**UDP Management**
	808	+
627	627	AT+CFM          : Upload confirmation mode (only valid for UDP)
628	628
629		-**MQTT Management**
630	630
	812	+(% style="color:blue" %)**MQTT Management**
	813	+
631	631	AT+CLIENT               : Get or Set MQTT client
632	632
633	633	AT+UNAME  : Get or Set MQTT Username
...	...	@@ -638,86 +638,71 @@
638	638
639	639	AT+SUBTOPIC  : Get or Set MQTT subscription topic
640	640
641		-**Information**
642	642
	825	+(% style="color:blue" %)**Information**
	826	+
643	643	AT+FDR  : Factory Data Reset
644	644
645	645	AT+PWORD  : Serial Access Password
646	646
647		-= **​5.  FAQ** =
648	648
649		-== **5.1 ​ How to Upgrade Firmware** ==
650	650
651		-User can upgrade the firmware for 1) bug fix, 2) new feature release.
	833	+= ​5.  FAQ =
652	652
653		-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]]
654	654
655		-**Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.**
	836	+== 5.1 ​ How to Upgrade Firmware ==
656	656
657		-== **5.2  Can I calibrate CPN01 to different soil types?** ==
658	658
659		-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]].
	839	+User can upgrade the firmware for 1) bug fix, 2) new feature release.
660	660
661		-= **6.  Trouble Shooting** =
	841	+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]]
662	662
663		-== **6.1  ​Connection problem when uploading firmware** ==
	843	+(% style="color:red" %)**Notice: **(% style="color:blue" %)**CPN01** (%%)**and (% style="color:blue" %)CPL01(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
664	664
665		-**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]]
666	666
667		-== **6.2  AT Command input doesn't work** ==
668	668
669		-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.
	847	+= 6.  Trouble Shooting =
670	670
671		-= **7. ​ Order Info** =
672	672
673		-Part Number**:** CPN01
	850	+== 6.1  ​Connection problem when uploading firmware ==
674	674
675		-= **8.  Packing Info** =
676	676
677		-**Package Includes**:
	853	+(% 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]]
678	678
679		-* CPN01 NB-IoT Soil Moisture & EC Sensor x 1
680		-* External antenna x 1
681	681
682		-**Dimension and weight**:
683	683
684		-* Size: 195 x 125 x 55 mm
685		-* Weight:   420g
	857	+== 6.2  AT Command input doesn't work ==
686	686
687		-= **9.  Support** =
688	688
689		-* 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.
690		-* 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]]
	860	+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.
691	691
692		-​
693	693
694	694
	864	+= 7. ​ Order Info =
695	695
696	696
	867	+Part Number**:** CPN01
697	697
698	698
699	699
	871	+= 8.  Packing Info =
700	700
701	701
	874	+(% style="color:blue" %)**Package Includes**:
702	702
	876	+* CPN01 Open/Close Sensor x 1
	877	+* External antenna x 1
703	703
	879	+(% style="color:blue" %)**Dimension and weight**:
704	704
	881	+* Size: 195 x 125 x 55 mm
	882	+* Weight:   420g
705	705
	884	+= 9.  Support =
706	706
707	707
	887	+* 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.
708	708
	889	+* 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]]
709	709
710		-
711		-
712		-
713		-
714		-
715		-
716		-
717		-
718		-
719		-
720		-
721		-
722		-
723		-
	891	+​

1666596205057-567.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+179.8 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