Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 83.7 >
edited by Xiaoling
on 2022/12/08 11:20
To version < 48.1 >
edited by Xiaoling
on 2022/10/24 15:23
>
Change comment: Uploaded new attachment "1666596205057-567.png", version {1}

Summary

Details

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

Applications

Navigation

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