Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 83.1 >
edited by Xiaoling
on 2022/12/08 09:07
To version < 37.1 >
edited by Edwin Chen
on 2022/10/22 23:46
>
Change comment: Uploaded new attachment "image-20221022234602-2.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
1 +CPN01- NB-IoT Outdoor Open/Close Dry Contact Sensor User Manual
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -1,46 +1,34 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg]]
2 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/WebHome/1652856952171-363.png?rev=1.1||alt="1652856952171-363.png" height="578" width="588"]]
3 3  
4 +{{toc/}}
4 4  
5 -**Table of Contents：**
6 += **1. Introduction** =
6 6  
8 +== **1.1 ​**What is CPN01 **NB-IoT** Pulse/Contact Sensor ==
7 7  
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.
8 8  
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.
9 9  
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.
10 10  
11 -= 1.  Introduction =
16 +CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures.
12 12  
13 -== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
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.
14 14  
23 +​
15 15  
16 -(((
17 -The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor.
25 +== **​1.2 Features** ==
18 18  
19 -
20 -The NMDS200 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
21 -
22 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
23 -
24 -NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range.
25 -
26 -NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**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.
27 -
28 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
29 -
30 -NMDS200 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)
31 -
32 -To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection.
33 -)))
34 -
35 -
36 -
37 -== ​1.2  Features ==
38 -
39 -
40 40  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
41 -* Short uplink interval for Distance Alarm
28 +* Open/Close detect
29 +* Open/Close statistics
42 42  * Monitor Battery Level
43 -* Microwave Radar for distance detection
31 +* Uplink on periodically and open/close event
44 44  * Datalog feature
45 45  * Uplink periodically
46 46  * Downlink to change configure
... ... @@ -51,527 +51,527 @@
51 51  * Micro SIM card slot for NB-IoT SIM
52 52  * 8500mAh Battery for long-term use
53 53  
54 -== 1.3 Radar probe specification ==
42 +== **1.3  Specification** ==
55 55  
44 +**Common DC Characteristics:**
56 56  
57 -* Measuring Method: FMCW
58 -* Frequency: 24.000 24.500 GHz
59 -* Measurement output power: 6dBm
60 -* Measure range: 0.5 20m
61 -* Accuracy: ±0.1m
62 -* Resolution: 0.01m
63 -* Horizontal Angel: 78°
64 -* Vertical Angel: 23°
46 +* Supply Voltage: 2.1v ~~ 3.6v
47 +* Operating Temperature: -40 ~~ 85°C
65 65  
49 +**NB-IoT Spec:**
66 66  
67 -== 1.4  Storage Temperature ==
51 +* - B1 @H-FDD: 2100MHz
52 +* - B3 @H-FDD: 1800MHz
53 +* - B8 @H-FDD: 900MHz
54 +* - B5 @H-FDD: 850MHz
55 +* - B20 @H-FDD: 800MHz
56 +* - B28 @H-FDD: 700MHz
68 68  
58 +== **1.4 Installation** ==
69 69  
70 - -40°C to +85°C
60 +Connect CPL01 to an Open Close sensor like below. So it can detect the open/close event.
71 71  
62 +[[image:image-20221021110329-1.png]]
72 72  
64 +[[image:image-20221021110340-2.png]]
73 73  
66 +== **1.5 ​Applications** ==
74 74  
68 +* Open/Close Detection
69 +* Pulse meter application
70 +* Dry Contact Detection
75 75  
76 -== 1.5 ​ Applications ==
72 +== **1.6 Mechanical** ==
77 77  
74 +​[[image:image-20221021110415-3.png]]
78 78  
76 +== ** 1.7 Pin Definitions and Switch** ==
79 79  
80 -* Horizontal distance measurement
81 -* Liquid level measurement
82 -* Parking management system
83 -* Object proximity and presence detection
84 -* Intelligent trash can management system
85 -* Robot obstacle avoidance
86 -* Automatic control
87 -* Sewer
88 -* Bottom water level monitoring
78 +[[image:image-20221021110429-4.png]]
89 89  
90 -== 1.6  Specification ==
80 +=== **1.7.1 Pin Definition** ===
91 91  
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]]
92 92  
93 -(% style="color:blue" %)**Common DC Characteristics:**
84 +=== **1.7.2 Jumper JP2(Power ON/OFF)** ===
94 94  
95 -* Supply Voltage: 2.1v ~~ 3.6v
96 -* Operating Temperature: 0 ~~ 70°C
97 97  
98 -(% style="color:blue" %)**NB-IoT Spec:**
87 +Power on Device when putting this jumper.
99 99  
100 -* B1 @H-FDD: 2100MHz
101 -* B3 @H-FDD: 1800MHz
102 -* B8 @H-FDD: 900MHz
103 -* B5 @H-FDD: 850MHz
104 -* B20 @H-FDD: 800MHz
105 -* B28 @H-FDD: 700MHz
106 106  
107 -== 1.7  Installation ==
108 108  
91 +=== **1.7.3 BOOT MODE / SW1** ===
109 109  
110 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
111 111  
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.
112 112  
113 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
96 +2) Flash: work mode, the device starts to work and send out console output for further debug
114 114  
115 115  
116 116  
117 -== 1.8  Pin Definitions and Switch ==
100 +=== **1.7.4 Reset Button** ===
118 118  
119 119  
120 -[[image:1670404362039-351.png]]
103 +Press to reboot the device.
121 121  
105 +== ==
122 122  
123 -= 2.  Use NMDS200 to communicate with IoT Server =
107 +=== **1.7.5 LED** ===
124 124  
125 -== 2.1  How it works ==
126 126  
110 +It will flash:
127 127  
128 -The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
112 +1. Boot the device in flash mode
113 +1. Send an uplink packet
129 129  
130 -The diagram below shows the working flow in the default firmware of NMDS200:
115 += **2.  Use CPN01 to communicate with IoT Server** =
131 131  
132 -[[image:image-20221021110615-5.png]]
117 +== **2.1  How it works** ==
133 133  
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.
134 134  
135 -== 2.2 ​ Configure NMDS200 ==
121 +The diagram below shows the working flow in default firmware of CPN01:
136 136  
123 +[[image:image-20221021110615-5.png]]
137 137  
138 -To use NMDS200 in your city, make sure to meet below requirements:
125 +== **2.2 ​ Configure the CPN01** ==
139 139  
140 -* Your local operator has already distributed an NB-IoT Network.
141 -* The local NB-IoT network used the band that NMDS200 supports.
142 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
127 +=== **2.2.1 Test Requirement** ===
143 143  
144 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NMDS200 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.
129 +To use CPN01 in your city, make sure meet below requirements:
145 145  
146 -[[image:image-20221207173300-4.png]]
131 +* Your local operator has already distributed a NB-IoT Network there.
132 +* The local NB-IoT network used the band that CPN01 supports.
133 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
147 147  
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
148 148  
149 -=== 2.2.1 Insert NB-IoT SIM card ===
137 + ​
150 150  
139 +=== **2.2.2 Insert SIM card** ===
151 151  
152 152  Insert the NB-IoT Card get from your provider.
153 153  
154 -User needs to take out the NB-IoT module and insert the SIM card like below:
143 +User need to take out the NB-IoT module and insert the SIM card like below:
155 155  
156 156  [[image:image-20221021110745-6.png]] ​
157 157  
147 +=== **2.2.3 Connect USB – TTL to CPN01 to configure it** ===
158 158  
159 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
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.
160 160  
151 +**Connection:**
161 161  
162 -User need to configure NMDS200 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NMDS200 support AT Commands, user can use a USB to TTL adapter to connect to NMDS200 and use AT Commands to configure it, as below.
153 + USB TTL GND <~-~-~-~-> GND
163 163  
164 -(% style="color:blue" %)**Connection:**
155 + USB TTL TXD <~-~-~-~-> UART_RXD
165 165  
166 -(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
157 + USB TTL RXD <~-~-~-~-> UART_TXD
167 167  
168 -(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD**
169 -
170 -(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD**
171 -
172 -
173 173  In the PC, use below serial tool settings:
174 174  
175 -* Baud:  (% style="color:red" %)**9600**
161 +* Baud:  **9600**
162 +* Data bits:** 8**
163 +* Stop bits: **1**
164 +* Parity:  **None**
165 +* Flow Control: **None**
176 176  
177 -* Data bits:** (% style="color:red" %)8(%%)**
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.
178 178  
179 -* Stop bits: (% style="color:red" %)**1**
180 -
181 -* Parity:  (% style="color:red" %)**None**
182 -
183 -* Flow Control: (% style="color:red" %)**None**
184 -
185 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
186 -
187 187  ​[[image:image-20221021110817-7.png]]
188 188  
189 -NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
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]]
190 190  
173 +=== **2.2.4 Use CoAP protocol to uplink data** ===
191 191  
192 -(% 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]]
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/]]
193 193  
177 +**Use below commands:**
194 194  
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
195 195  
196 -=== 2.2.3 Use CoAP protocol to uplink data ===
197 -
198 -
199 -(% 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/]]
200 -
201 -
202 -(% style="color:blue" %)**Use below commands in NDS03A:**
203 -
204 -* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
205 -
206 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
207 -
208 -* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
209 -
210 210  For parameter description, please refer to AT command set
211 211  
212 212  [[image:image-20221021110948-8.png]]
213 213  
187 +After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server.
214 214  
215 -After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server.
189 +[[image:image-20221021110956-9.png]] ​
216 216  
217 -[[image:1670405841875-916.png]] ​
191 +=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** ===
218 218  
193 +This feature is supported since firmware version v1.0.1
219 219  
220 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
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
221 221  
222 -
223 -(% style="color:blue" %)**AT Commands:**
224 -
225 -* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
226 -
227 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  Set UDP server address and port
228 -
229 -* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
230 -
231 231  ​ [[image:image-20221021111025-10.png]]
232 232  
233 -
234 234  [[image:image-20221021111033-11.png||height="241" width="576"]]
235 235  
236 236  ​
237 237  
238 -=== 2.2.5 Use MQTT protocol to uplink data ===
205 +=== **2.2.6 Use MQTT protocol to uplink data** ===
239 239  
207 +This feature is supported since firmware version v110
240 240  
241 -(% style="color:blue" %)**AT Commands:**
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
242 242  
243 -* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
217 +​ [[image:image-20221021111058-12.png]]
244 244  
245 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
219 +[[image:image-20221021111108-13.png]]
246 246  
247 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
221 +​
248 248  
249 -* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
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.
250 250  
251 -* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
225 +=== **2.2.7 Use TCP protocol to uplink data** ===
252 252  
253 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/  Set the sending topic of MQTT
227 +This feature is supported since firmware version v110
254 254  
255 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
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
256 256  
257 -​ [[image:image-20221118103445-7.png]]
232 +​ [[image:image-20221021111125-14.png]]
258 258  
234 +[[image:image-20221021111131-15.png]]
259 259  
260 -[[image:1670405928926-116.png]]
261 -
262 262  ​
263 263  
264 -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.
238 +=== **2.2.8 Change Update Interval** ===
265 265  
240 +User can use below command to change the **uplink interval**.
266 266  
267 -=== 2.2.6 Use TCP protocol to uplink data ===
242 +* **AT+TDC=600      ** ~/~/ Set Update Interval to 600s
268 268  
244 +**NOTE:**
269 269  
270 -(% style="color:blue" %)**AT Commands:**
246 +**~1. By default, the device will send an uplink message every 1 hour.**
271 271  
272 -* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
248 +== **2.3  Uplink Payload** ==
273 273  
274 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
250 +In this mode, uplink payload includes 87 bytes in total by default.
275 275  
276 -​ [[image:1670406036256-101.png||height="676" width="713"]]
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.
277 277  
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
278 278  
279 -[[image:image-20221021111131-15.png]]
257 +|2|2|4|8 group
258 +|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|...
280 280  
281 -​
260 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
282 282  
283 -=== 2.2.7 Change Update Interval ===
262 +[[image:image-20221021111201-16.png||height="572" width="792"]]
284 284  
264 +The payload is ASCII string, representative same HEX:
285 285  
286 -User can use below command to change the (% style="color:blue" %)**uplink interval**.
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 //(%%)**
287 287  
288 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
268 +where:
269 +*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
289 289  
290 -(% style="color:red" %)**NOTE:**
271 +*(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
291 291  
292 -1.  By default, the device will send an uplink message every 4 hour.
273 +*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
293 293  
275 +*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
294 294  
295 -== 2.3  Uplink Payload ==
277 +*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
296 296  
279 +*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00= 0
297 297  
298 -The uplink payload includes 23 bytes in total by default.
281 +*(% style="color:#037691" %) **Contact Status:**(%%) 0x00= 0
299 299  
300 -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.
283 +*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0
301 301  
285 +*(% style="color:#037691" %) **Total pulse:0x09 =0**
302 302  
303 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
304 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:90px" %)**2**|(% style="width:100px" %)**2**
305 -|=(% 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" %)Exit flag|(% style="width:94px" %) Distance 1 |(% style="width:93px" %) Distance  2
287 +*(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2
306 306  
307 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
308 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
309 -**1-32 group**
310 -)))
311 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
289 +*(% style="color:#037691" %)**Time stamp :**(%%) 0x6315537b =1662342011
312 312  
313 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
291 +*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000b0200002663510fed
314 314  
315 -[[image:1670406261143-723.png]]
293 +*(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
316 316  
295 +== **2.4  Payload Explanation and Sensor Interface** ==
317 317  
318 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
297 +=== **2.4.1  Device ID** ===
319 319  
320 -**0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
299 +By default, the Device ID equal to the last 15 bits of IMEI.
321 321  
322 -**where:**
301 +User can use **AT+DEUI** to set Device ID
323 323  
324 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
303 +**Example:**
325 325  
326 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
305 +AT+DEUI=868411056754138
327 327  
328 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
307 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
329 329  
330 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
309 +=== **2.4.2  Version Info** ===
331 331  
332 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
311 +Specify the software version: 0x64=100, means firmware version 1.00.
333 333  
334 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
313 +For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0.
335 335  
336 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
315 +=== **2.4.3  Battery Info** ===
337 337  
338 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
317 +Check the battery voltage for CPN01.
339 339  
340 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
319 +Ex1: 0x0B45 = 2885mV
341 341  
321 +Ex2: 0x0B49 = 2889mV
342 342  
343 -== 2.4  Payload Explanation and Sensor Interface ==
323 +=== **2.4.4  Signal Strength** ===
344 344  
345 -=== 2.4.1  Device ID ===
325 +NB-IoT Network signal Strength.
346 346  
327 +**Ex1: 0x1d = 29**
347 347  
348 -By default, the Device ID is equal to the last 15 bits of IMEI.
329 +**0**  -113dBm or less
349 349  
350 -User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
331 +**1**  -111dBm
351 351  
352 -**Example:**
333 +**2...30** -109dBm... -53dBm
353 353  
354 -AT+DEUI=868411056754138
335 +**31**   -51dBm or greater
355 355  
356 -The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
337 +**99**    Not known or not detectable
357 357  
339 +=== **2.4.5 Calculate Flag** ===
358 358  
359 -=== 2.4.2  Version Info ===
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.
360 360  
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.
361 361  
362 -Specify the software version: 0x64=100, which means firmware version 1.00.
345 +Default value: 0. 
363 363  
364 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
347 +Range (6 bits): (b)000000 ~~ (b) 111111
365 365  
349 +=== **2.4.6  Alarm** ===
366 366  
367 -=== 2.4.3  Battery Info ===
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]]
368 368  
353 +=== **2.4.7 Contact Status** ===
369 369  
370 -Check the battery voltage for NMDS200.
355 +0: Open
371 371  
372 -Ex1: 0x0B45 = 2885mV
357 +1: Close
373 373  
374 -Ex2: 0x0B49 = 2889mV
359 +=== **2.4.8 Total pulse** ===
375 375  
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]]
376 376  
377 -=== 2.4.4  Signal Strength ===
363 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
378 378  
365 +=== **2.4.9 The last open duration** ===
379 379  
380 -NB-IoT Network signal Strength.
367 +Dry Contact last open duration.
381 381  
382 -**Ex1: 0x1d = 29**
369 +Unit: min.
383 383  
384 -**0**  -113dBm or less
371 +[[image:image-20221021111346-17.png||height="146" width="770"]]
385 385  
386 -**1**  -111dBm
387 387  
388 -**2...30** -109dBm... -53dBm
374 +=== **2.4.10  Timestamp** ===
389 389  
390 -**31**   -51dBm or greater
376 +Time stamp : 0x6315537b =1662342011
391 391  
392 -**99**    Not known or not detectable
378 +Convert Unix timestamp to time 2022-9-5 9:40:11.
393 393  
380 +**~ **
394 394  
395 -=== 2.4.5  Distance ===
382 +== **2.5  Downlink Payload** ==
396 396  
384 +By default, CPN01 prints the downlink payload to console port.
397 397  
398 -[[image:1670407401682-959.png]]
386 +[[image:image-20221021111414-18.png]] ​
399 399  
400 -(% style="color:blue" %)**Object1 Distance:**
388 +**Examples:**
401 401  
402 -Distance between sensor probe to the first object. (unit: cm)
390 +* **Set TDC**
403 403  
404 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
392 +If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
405 405  
406 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
394 +Payload:    01 00 00 1E    TDC=30S
407 407  
396 +Payload:    01 00 00 3C    TDC=60S
408 408  
409 -(% style="color:blue" %)**Object2 Distance:**
398 +* **Reset**
410 410  
411 -Distance between sensor probe to the second object. (unit: cm)
400 +If payload = 0x04FF, it will reset the NSE01
412 412  
402 +* **INTMOD**
413 413  
414 -=== 2.4.6  Timestamp ===
404 +Downlink Payload: 06000003, Set AT+INTMOD=3
415 415  
406 +== **2.6  ​LED Indicator** ==
416 416  
417 -Timestamp : 0x6315537b =1662342011
408 +The CPN01 has an internal LED which is to show the status of different state.
418 418  
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.
413 +* For each uplink probe, LED will be on for 500ms.
419 419  
420 -== 2.5  Downlink Payload ==
415 +== **2.7  Alarm Base on Timeout** ==
421 421  
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:
422 422  
423 -By default, NMDS200 prints the downlink payload to console port.
424 424  
425 -[[image:image-20221021111414-18.png]] ​
420 +**~1. Keep Status: Status to be monitor**
426 426  
422 +Keep Status = 1: Monitor Close to Open event
427 427  
428 -**Examples:**
424 +Keep Status = 0: Monitor Open to Close event
429 429  
430 -* (% style="color:#037691" %)**Set TDC**
431 431  
432 -If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
427 +**2. Keep Time: Timeout to send an Alarm**
433 433  
434 -Payload:    01 00 00 1E    TDC=30S
429 +Range 0 ~~ 65535(0xFFFF) seconds.
435 435  
436 -Payload:    01 00 00 3C    TDC=60S
431 +If keep time = 0, Disable Alarm Base on Timeout feature.
437 437  
438 -* (% style="color:#037691" %)**Reset**
433 +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 -If payload = 0x04FF, it will reset the NMDS200
441 441  
442 -* (% style="color:#037691" %)**INTMOD**
436 +**AT Command** to configure:
443 443  
444 -Downlink Payload: 06000003, Set AT+INTMOD=3
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.
445 445  
440 +**AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm.
446 446  
447 -== 2.6  ​LED Indicator ==
442 +== **2.8 Set debug mode** ==
448 448  
444 +Feature: Enable or Disable debug mode
449 449  
450 -The NMDS200 has an internal LED which is to show the status of different states.
451 451  
452 -* When the device starts normally, the LED will light up for 1 second.
453 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
454 -* For each uplink probe, LED will be on for 500ms.
447 +**AT Command: AT+DEBUG**
455 455  
449 +[[image:image-20221021111629-21.png]]
456 456  
451 +== **2.9 Clear Flash Record** ==
457 457  
458 -== 2.7  Distance alarm function ==
453 +Feature: Clear flash storage for data log feature.
459 459  
455 +**AT Command: AT+CLRDTA**
460 460  
461 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
457 +[[image:image-20221021111527-19.png]]
462 462  
463 -**Example 1:**
459 +== ** 2.10 Set trigger mode** ==
464 464  
465 -AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
461 +➢ AT Command: **AT+TTRMOD**
466 466  
467 -AT+ ALARM2 =min,max
463 +Feature: Set the trigger interrupt mode.
468 468  
465 +[[image:image-20221021111552-20.png]]
469 469  
470 -**Example 2:**
467 +== **2.11 Set the calculate flag** ==
471 471  
472 -AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
469 +Feature: Set the calculate flag
473 473  
471 +**AT Command: AT+CALCFLAG**
474 474  
475 -== 2.8  Set the number of data to be uploaded and the recording time ==
473 +[[image:image-20221021111711-22.png]]
476 476  
475 +== **2.12 Set count number** ==
477 477  
478 -(% style="color:blue" %)**AT Command:**
477 +Feature: Manually set the count number
479 479  
480 -(% 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)
479 +**AT Command: AT+SETCNT**
481 481  
482 -(% 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.
481 +[[image:image-20221021111748-24.png]]
483 483  
483 +== **2.13 Set the number of data to be uploaded and the recording time** ==
484 484  
485 -== 2.9  Read or Clear cached data ==
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)
487 487  
488 -(% style="color:blue" %)**AT Command:**
489 489  
490 -(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
490 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
491 491  
492 -(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
492 +== **2.14 Read or Clear cached data** ==
493 493  
494 -[[image:1670408172929-569.png]]
494 +➢ AT Command:
495 495  
496 +AT+CDP    ~/~/ Read cached data
496 496  
497 -== 2.10  ​Firmware Change Log ==
498 +[[image:image-20221021111810-25.png||height="364" width="797"]]
498 498  
499 499  
500 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
501 +AT+CDP=0    ~/~/ Clear cached data ​
501 501  
502 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
503 +== **2.15  ​Firmware Change Log** ==
503 503  
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]]
504 504  
505 -== 2.11  ​Battery Analysis ==
507 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
506 506  
507 -=== 2.11.1  ​Battery Type ===
509 +== **2.16  ​Battery Analysis** ==
508 508  
511 +=== **2.16.1  ​Battery Type** ===
509 509  
510 -The NMDS200 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.
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.
511 511  
512 -The battery is designed to last for several years depends on the actual use environment and update interval. 
515 +The battery is designed to last for several years depends on the actually use environment and update interval. 
513 513  
514 -The battery-related documents as below:
517 +The battery related documents as below:
515 515  
516 516  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
517 -
518 518  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
519 -
520 520  * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
521 521  
522 522  [[image:image-20221021111911-26.png]] ​
523 523  
525 +=== **2.16.2  Power consumption Analyze** ===
524 524  
525 -=== 2.11.2  Power consumption Analyze ===
526 -
527 -
528 528  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.
529 529  
530 530  Instruction to use as below:
531 531  
532 -(% 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/]]
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/]]
533 533  
534 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
533 +**Step 2: ** Open it and choose
535 535  
536 536  * Product Model
537 -
538 538  * Uplink Interval
539 -
540 540  * Working Mode
541 541  
542 542  And the Life expectation in difference case will be shown on the right.
543 543  
544 -[[image:1666596205057-567.png]] ​
541 +[[image:image-20221021111923-27.png||height="253" width="783"]] ​
545 545  
543 +=== **2.16.3  ​Battery Note** ===
546 546  
547 -=== 2.11.3  ​Battery Note ===
548 -
549 -
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  
547 +=== **2.16.4  Replace the battery** ===
552 552  
553 -=== 2.11.4  Replace the battery ===
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).
554 554  
551 += **3. ​ Access NB-IoT Module** =
555 555  
556 -The default battery pack of NMDS200 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).
557 -
558 -
559 -= 3. ​ Access NB-IoT Module =
560 -
561 -
562 562  Users can directly access the AT command set of the NB-IoT module.
563 563  
564 564  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/]] 
565 565  
557 +[[image:image-20221021112006-28.png]] ​
566 566  
567 -[[image:image-20221118094449-6.png]] ​
559 += **4.  Using the AT Commands** =
568 568  
561 +== **4.1  Access AT Commands** ==
569 569  
570 -= 4.  Using the AT Commands =
571 -
572 -== 4.1  Access AT Commands ==
573 -
574 -
575 575  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]]
576 576  
577 577  AT+<CMD>?  : Help on <CMD>
... ... @@ -582,9 +582,8 @@
582 582  
583 583  AT+<CMD>=?  : Get the value
584 584  
573 +**General Commands**      
585 585  
586 -(% style="color:blue" %)**General Commands**      
587 -
588 588  AT  : Attention       
589 589  
590 590  AT?  : Short Help     
... ... @@ -607,41 +607,35 @@
607 607  
608 608  AT+SERVADDR  : Server Address
609 609  
610 -AT+TR      :  Get or Set record time
597 +AT+TR      : Get or Set record time"
611 611  
599 +
612 612  AT+NOUD      : Get or Set the number of data to be uploaded
613 613  
614 -AT+CDP     :  Read or Clear cached data
615 615  
616 -AT+ DEBUG   : Enable or Disable debug mode
603 +AT+CDP     : Read or Clear cached data
617 617  
618 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
619 619  
620 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
606 +AT+ DEBUG   : Enable or Disable debug mode
621 621  
622 -AT+COUNTMOD  :  Get or Set the count mode
608 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
623 623  
624 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
610 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
625 625  
626 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
612 +AT+ CALCFLAG   : Get or Set the calculate flag
627 627  
628 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
614 +AT+ CLRC   : Clear current door open count
629 629  
630 -AT+ CLRC   :  Clear current door open count
616 +**COAP Management**      
631 631  
632 -
633 -(% style="color:blue" %)**COAP Management**      
634 -
635 635  AT+URI            : Resource parameters
636 636  
620 +**UDP Management**
637 637  
638 -(% style="color:blue" %)**UDP Management**
639 -
640 640  AT+CFM          : Upload confirmation mode (only valid for UDP)
641 641  
624 +**MQTT Management**
642 642  
643 -(% style="color:blue" %)**MQTT Management**
644 -
645 645  AT+CLIENT               : Get or Set MQTT client
646 646  
647 647  AT+UNAME  : Get or Set MQTT Username
... ... @@ -652,58 +652,86 @@
652 652  
653 653  AT+SUBTOPIC  : Get or Set MQTT subscription topic
654 654  
636 +**Information**          
655 655  
656 -(% style="color:blue" %)**Information**          
657 -
658 658  AT+FDR  : Factory Data Reset
659 659  
660 660  AT+PWORD  : Serial Access Password
661 661  
642 += **​5.  FAQ** =
662 662  
663 -= ​5.  FAQ =
644 +== **5.1 ​ How to Upgrade Firmware** ==
664 664  
665 -== 5.1 ​ How to Upgrade Firmware ==
666 -
667 -
668 668  User can upgrade the firmware for 1) bug fix, 2) new feature release.
669 669  
670 670  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]]
671 671  
672 -(% 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.**
650 +**Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.**
673 673  
652 +== **5.2  Can I calibrate CPN01 to different soil types?** ==
674 674  
675 -= 6.  Trouble Shooting =
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]].
676 676  
677 -== 6.1  ​Connection problem when uploading firmware ==
656 += **6.  Trouble Shooting** =
678 678  
658 +== **6.1  ​Connection problem when uploading firmware** ==
679 679  
680 -(% 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]]
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]]
681 681  
662 +== **6.2  AT Command input doesn't work** ==
682 682  
683 -== 6.2  AT Command input doesn't work ==
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.
684 684  
666 += **7. ​ Order Info** =
685 685  
686 -In the case if user can see the console output but can't type input to the device. Please check if you already include the (% 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.
668 +Part Number**:** CPN01
687 687  
670 += **8.  Packing Info** =
688 688  
689 -= 7. ​ Order Info =
672 +**Package Includes**:
690 690  
674 +* CPN01 NB-IoT Soil Moisture & EC Sensor x 1
675 +* External antenna x 1
691 691  
692 -Part Number**:** NDS03A
677 +**Dimension and weight**:
693 693  
679 +* Size: 195 x 125 x 55 mm
680 +* Weight:   420g
694 694  
695 -= 8.  Packing Info =
682 += **9.  Support** =
696 696  
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]]
697 697  
698 -(% style="color:blue" %)**Package Includes**:
687 +​
699 699  
700 -* NDS03A Open/Close Door Sensor x 1
701 701  
702 -= 9.  Support =
703 703  
704 704  
705 -* 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.
706 706  
707 -* 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]]
708 708  
709 -​
694 +
695 +
696 +
697 +
698 +
699 +
700 +
701 +
702 +
703 +
704 +
705 +
706 +
707 +
708 +
709 +
710 +
711 +
712 +
713 +
714 +
715 +
716 +
717 +
718 +
1666596205057-567.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -179.8 KB
Content
1670404362039-351.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -492.6 KB
Content
1670405841875-916.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.0 KB
Content
1670406261143-723.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content
1670407401682-959.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -23.7 KB
Content
1670408172929-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -211.8 KB
Content
LMDS200_10.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 KB
Content
image-20221023000439-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -82.1 KB
Content
image-20221117105556-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -133.3 KB
Content
image-20221117114459-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20221117114842-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -964.1 KB
Content
image-20221117114937-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.1 KB
Content
image-20221117114949-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -33.4 KB
Content
image-20221117115010-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -40.4 KB
Content
image-20221117142300-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -51.9 KB
Content
image-20221117150312-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.7 KB
Content
image-20221118092935-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.5 KB
Content
image-20221118093658-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -12.7 KB
Content
image-20221118094227-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.2 KB
Content
image-20221118094449-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.5 KB
Content
image-20221118103445-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.5 KB
Content
image-20221207170748-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.1 KB
Content
image-20221207170748-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.9 KB
Content
image-20221207173200-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
image-20221207173300-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.0 KB
Content
image-20221208090742-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.7 KB
Content

Applications

Navigation

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