Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 41.1 >
edited by Edwin Chen
on 2022/10/23 00:08
To version < 90.7 >
edited by Xiaoling
on 2023/04/04 14:55
>
Change comment: There is no comment for this version

Summary

Details

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

Applications

Navigation

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