Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 90.9 >
edited by Xiaoling
on 2023/04/24 10:09
To version < 39.1 >
edited by Edwin Chen
on 2022/10/23 00:04
>
Change comment: Uploaded new attachment "image-20221023000439-3.png", version {1}

Summary

Details

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