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