Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 31.1 >
edited by David Huang
on 2022/10/21 11:21
To version < 90.7 >
edited by Xiaoling
on 2023/04/04 14:55
>
Change comment: There is no comment for this version

Summary

Details

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

Applications

Navigation

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