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

Applications

Navigation

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