Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 83.9 >
edited by Xiaoling
on 2022/12/08 11:31
To version < 42.1 >
edited by Edwin Chen
on 2022/10/23 00:32
>
Change comment: There is no comment for this version

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