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

Applications

Navigation

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