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