Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 26 removed)
  • 1670404362039-351.png
  • 1670405841875-916.png
  • 1670405928926-116.png
  • 1670406036256-101.png
  • 1670406261143-723.png
  • 1670407401682-959.png
  • 1670408172929-569.png
  • 1670471530120-960.png
  • 1670471559211-638.png
  • 1670471584490-640.png
  • 1670471613823-833.png
  • LMDS200_10.jpg
  • image-20221118092935-1.png
  • image-20221118093144-2.png
  • image-20221118093512-3.png
  • image-20221118093658-4.png
  • image-20221118094227-5.png
  • image-20221118094449-6.png
  • image-20221118103445-7.png
  • image-20221118103453-8.png
  • image-20221118103547-9.png
  • image-20221207170748-1.png
  • image-20221207170748-2.png
  • image-20221207173200-3.png
  • image-20221207173300-4.png
  • image-20221208090742-1.png

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
	1	+NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual

Content

...	...	@@ -1,10 +1,14 @@
1	1	(% style="text-align:center" %)
2		-[[image:LMDS200_10.jpg]]
	2	+[[image:image-20221117105556-1.png]]
3	3
4	4
	5	+
	6	+
	7	+
	8	+
	9	+
5	5	**Table of Contents：**
6	6
7		-{{toc/}}
8	8
9	9
10	10
...	...	@@ -11,49 +11,51 @@
11	11
12	12	= 1.  Introduction =
13	13
14		-== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
	18	+== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
15	15
16	16
17	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.
	22	+The Dragino NDS03A is an (% style="color:blue" %)**Open/Close NB-IoT Door Sensor**(%%). It detects door (% style="color:blue" %)**open/close status**(%%) and (% style="color:blue" %)**uplinks**(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server.
19	19	)))
20	20
21	21	(((
22		-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.
	26	+The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically.
23	23	)))
24	24
25	25	(((
26		-NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
	30	+NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT.
27	27	)))
28	28
29	29	(((
30		-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.
	34	+NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time.
31	31	)))
32	32
33	33	(((
34		-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.
	38	+NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
35	35	)))
36	36
37	37	(((
38		-NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
	42	+NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technologyTCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
39	39	)))
40	40
41	41	(((
42		-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)
	46	+NDS03A 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)
43	43	)))
44	44
45	45	(((
46		-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.
	50	+To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection.
47	47	)))
48	48
49	49
	54	+
50	50	== ​1.2  Features ==
51	51
52	52
53	53	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
54		-* Short uplink interval for Distance Alarm
	59	+* Open/Close detect
	60	+* Open/Close statistics
55	55	* Monitor Battery Level
56		-* Microwave Radar for distance detection
	62	+* connect two door sensors
57	57	* Datalog feature
58	58	* Uplink periodically
59	59	* Downlink to change configure
...	...	@@ -64,40 +64,29 @@
64	64	* Micro SIM card slot for NB-IoT SIM
65	65	* 8500mAh Battery for long-term use
66	66
	73	+== 1.3  Storage & Operation ==
67	67
68	68
69		-== 1.3 Radar probe specification ==
	76	+Temperature -40°C to +85°C
70	70
71	71
72		-* Measuring Method: FMCW
73		-* Frequency: 24.000 ~~ 24.500 GHz
74		-* Measurement output power: 6dBm
75		-* Measure range: 0.5 ~~ 20m
76		-* Accuracy: ±0.1m
77		-* Resolution: 0.01m
78		-* Horizontal Angel: 78°
79		-* Vertical Angel: 23°
	79	+== 1.4  Mechanical ==
80	80
81	81
	82	+[[image:image-20221117114937-4.png]]
82	82
83		-== 1.4  Storage Temperature ==
84	84
	85	+[[image:image-20221117114949-5.png]]
85	85
86		- -40°C to +85°C
87	87
	88	+[[image:image-20221117115010-6.png]]
88	88
	90	+
	91	+
89	89	== 1.5 ​ Applications ==
90	90
91	91
92		-* Horizontal distance measurement
93		-* Liquid level measurement
94		-* Parking management system
95		-* Object proximity and presence detection
96		-* Intelligent trash can management system
97		-* Robot obstacle avoidance
98		-* Automatic control
99		-* Sewer
100		-* Bottom water level monitoring
	95	+[[image:image-20221117114842-3.png]]
101	101
102	102
103	103
...	...	@@ -107,67 +107,107 @@
107	107	(% style="color:blue" %)**Common DC Characteristics:**
108	108
109	109	* Supply Voltage: 2.1v ~~ 3.6v
110		-* Operating Temperature: 0 ~~ 70°C
	105	+* Operating Temperature: -40 ~~ 85°C
111	111
112	112	(% style="color:blue" %)**NB-IoT Spec:**
113	113
114		-* B1 @H-FDD: 2100MHz
115		-* B3 @H-FDD: 1800MHz
116		-* B8 @H-FDD: 900MHz
117		-* B5 @H-FDD: 850MHz
118		-* B20 @H-FDD: 800MHz
119		-* B28 @H-FDD: 700MHz
	109	+* - B1 @H-FDD: 2100MHz
	110	+* - B3 @H-FDD: 1800MHz
	111	+* - B8 @H-FDD: 900MHz
	112	+* - B5 @H-FDD: 850MHz
	113	+* - B20 @H-FDD: 800MHz
	114	+* - B28 @H-FDD: 700MHz
120	120
	116	+== 1.7  Pin Definitions and Switch ==
121	121
122	122
123		-== 1.7  Installation ==
	119	+[[image:image-20221021110429-4.png]]
124	124
125	125
126		-Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
	122	+=== 1.7.1  Pin Definition ===
127	127
128	128
129		-[[image:image-20221207170748-1.png]]
	125	+The device is pre-configured to connect to a door sensor. 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>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
130	130
131	131
132		- [[image:image-20221207170748-2.png||height="345" width="634"]]
133	133
	129	+=== 1.7.2  Jumper JP2(Power ON/OFF) ===
134	134
135	135
136		-== 1.8  Pin Definitions and Switch ==
	132	+Power on Device when putting this jumper.
137	137
138	138
139		-[[image:1670404362039-351.png]]
140	140
	136	+=== 1.7.3  BOOT MODE / SW1 ===
141	141
142		-= 2.  Use NMDS200 to communicate with IoT Server =
143	143
	139	+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.
	140	+
	141	+2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
	142	+
	143	+
	144	+
	145	+=== 1.7.4  Reset Button ===
	146	+
	147	+
	148	+Press to reboot the device.
	149	+
	150	+
	151	+
	152	+=== 1.7.5  LED ===
	153	+
	154	+
	155	+The LED will blink when :
	156	+
	157	+1.  Boot the device in flash mode
	158	+
	159	+2.  Send an uplink packet
	160	+
	161	+
	162	+
	163	+== 1.8  Magnet Distance ==
	164	+
	165	+
	166	+(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
	167	+
	168	+(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
	169	+
	170	+
	171	+
	172	+= 2.  Use CPN01 to communicate with IoT Server =
	173	+
144	144	== 2.1  How it works ==
145	145
146	146
147		-The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
	177	+In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.
148	148
149		-The diagram below shows the working flow in the default firmware of NMDS200:
	179	+The diagram below shows the working flow in the default firmware of NDS03A:
150	150
151		-[[image:image-20221021110615-5.png||height="996" width="492"]]
	181	+[[image:image-20221021110615-5.png]]
152	152
153	153
154		-== 2.2 ​ Configure NMDS200 ==
155	155
	185	+== 2.2 ​ Configure NDS03A ==
156	156
157		-To use NMDS200 in your city, make sure to meet below requirements:
	187	+=== 2.2.1 Test Requirement ===
158	158
	189	+
	190	+To use NDS03A in your city, make sure to meet below requirements:
	191	+
159	159	* Your local operator has already distributed an NB-IoT Network.
160		-* The local NB-IoT network used the band that NMDS200 supports.
	193	+* The local NB-IoT network used the band that NDS03A supports.
161	161	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
162	162
163		-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.
	196	+Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDS03A 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.
164	164
165		-[[image:image-20221208090742-1.png]]
	198	+[[image:image-20221117142300-1.png]]
166	166
	200	+ ​
167	167
168		-=== 2.2.1 Insert NB-IoT SIM card ===
169	169
	203	+=== 2.2.2 Insert NB-IoT SIM card ===
170	170
	205	+
171	171	Insert the NB-IoT Card get from your provider.
172	172
173	173	User needs to take out the NB-IoT module and insert the SIM card like below:
...	...	@@ -175,11 +175,12 @@
175	175	[[image:image-20221021110745-6.png]] ​
176	176
177	177
178		-=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
179	179
	214	+=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
180	180
181		-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.
182	182
	217	+User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
	218	+
183	183	(% style="color:blue" %)**Connection:**
184	184
185	185	(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
...	...	@@ -201,23 +201,24 @@
201	201
202	202	* Flow Control: (% style="color:red" %)**None**
203	203
204		-Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
	240	+Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
205	205
206	206	​[[image:image-20221021110817-7.png]]
207	207
208		-NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
	244	+NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
209	209
210	210
211	211	(% 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]]
212	212
213	213
214		-=== 2.2.3 Use CoAP protocol to uplink data ===
215	215
	251	+=== 2.2.4 Use CoAP protocol to uplink data ===
216	216
	253	+
217	217	(% 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/]]
218	218
219	219
220		-(% style="color:blue" %)**Use below commands in NMDS200:**
	257	+(% style="color:blue" %)**Use below commands in CPN01:**
221	221
222	222	* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
223	223
...	...	@@ -227,17 +227,18 @@
227	227
228	228	For parameter description, please refer to AT command set
229	229
230		-[[image:1670471530120-960.png||height="647" width="674"]]
	267	+[[image:image-20221021110948-8.png]]
231	231
232	232
233		-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.
	270	+After configuring the server address and (% style="color:green" %)**reset CPN01**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
234	234
235		-[[image:1670405841875-916.png]] ​
	272	+[[image:image-20221021110956-9.png]] ​
236	236
237	237
238		-=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
239	239
	276	+=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
240	240
	278	+
241	241	(% style="color:blue" %)**AT Commands:**
242	242
243	243	* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
...	...	@@ -246,7 +246,7 @@
246	246
247	247	* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
248	248
249		-​ [[image:1670471559211-638.png]]
	287	+​ [[image:image-20221021111025-10.png]]
250	250
251	251
252	252	[[image:image-20221021111033-11.png||height="241" width="576"]]
...	...	@@ -253,9 +253,10 @@
253	253
254	254	​
255	255
256		-=== 2.2.5 Use MQTT protocol to uplink data ===
257	257
	295	+=== 2.2.6 Use MQTT protocol to uplink data ===
258	258
	297	+
259	259	(% style="color:blue" %)**AT Commands:**
260	260
261	261	* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
...	...	@@ -272,10 +272,10 @@
272	272
273	273	* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
274	274
275		-​ ​​​​​​​[[image:1670471584490-640.png]]
	314	+​ [[image:image-20221021111058-12.png]]
276	276
277	277
278		-[[image:1670405928926-116.png]]
	317	+[[image:image-20221021111201-16.png||height="472" width="653"]]
279	279
280	280	​
281	281
...	...	@@ -282,9 +282,10 @@
282	282	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.
283	283
284	284
285		-=== 2.2.6 Use TCP protocol to uplink data ===
286	286
	325	+=== 2.2.7 Use TCP protocol to uplink data ===
287	287
	327	+
288	288	(% style="color:blue" %)**AT Commands:**
289	289
290	290	* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
...	...	@@ -291,19 +291,19 @@
291	291
292	292	* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
293	293
294		-​ ​​​​​​​[[image:1670471613823-833.png]]
	334	+​ [[image:image-20221021111125-14.png]]
295	295
296		-
297	297	[[image:image-20221021111131-15.png]]
298	298
299	299	​
300	300
301		-=== 2.2.7 Change Update Interval ===
302	302
	341	+=== 2.2.8 Change Update Interval ===
303	303
	343	+
304	304	User can use below command to change the (% style="color:blue" %)**uplink interval**.
305	305
306		-* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
	346	+* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
307	307
308	308	(% style="color:red" %)**NOTE:**
309	309
...	...	@@ -310,57 +310,79 @@
310	310	1.  By default, the device will send an uplink message every 4 hour.
311	311
312	312
	353	+
313	313	== 2.3  Uplink Payload ==
314	314
315	315
316		-The uplink payload includes 23 bytes in total by default.
	357	+The uplink payload includes 26 bytes in total by default.
317	317
318	318	Each time the device uploads a data package. The user can use the AT+NOUD command to upload the recorded data.Up to 32 sets of recorded data can be uploaded.
319	319
	361	+(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
320	320
321		-(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %)
322		-|=(% 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**
323		-|=(% 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"]]
	363	+(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
	364	+|=(% scope="row" style="width: 93px;" %)**Size(bytes)**|(% style="width:67px" %)**8**|(% style="width:40px" %)**2**|(% style="width:45px" %)**2**|(% style="width:75px" %)**1**|(% style="width:54px" %)**1**|(% style="width:62px" %)**1**|(% style="width:60px" %)**1**|(% style="width:94px" %)**3**|(% style="width:93px" %)**3**
	365	+|=(% 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" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.4.6A0Alarm"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
324	324
325		-(% border="1" style="background-color:#ffffcc; color:green; width:429px" %)
326		-|(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((
	367	+(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
	368	+|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)(((
327	327	**1-32 group**
328	328	)))
329		-|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...
	371	+|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
330	330
331		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
332	332
333		-[[image:1670406261143-723.png]]
	374	+(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
334	334
335	335
336		-The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
	377	+(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
	378	+|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:66px" %)**8**|(% style="width:40px" %)**2**|(% style="width:46px" %)**2**|(% style="width:70px" %)**1**|(% style="width:54px" %)**1**|(% style="width:55px" %)**1**|(% style="width:57px" %)**1**|(% style="width:86px" %)**3**|(% style="width:82px" %)**3**
	379	+|=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.4.6A0Alarm"]]|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
337	337
338		-**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__(%%)**
	381	+(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
	382	+|(% style="width:59px" %)**1**|(% style="width:67px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:66px" %)**1**|(% style="width:92px" %)**3**
	383	+|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPN01-%20NB-IoT%20Outdoor%20OpenClose%20Dry%20Contact%20Sensor%C2%A0User%20Manual/#H2.4.7A0ContactStatus]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)Time stamp|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
339	339
	385	+(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
	386	+|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
	387	+**1-32 group**
	388	+)))
	389	+|(% style="width:102px" %)last open time (pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:88px" %)last open time(pb15)|(% style="width:63px" %)Time stamp|(% style="width:87px" %)...
	390	+
	391	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
	392	+
	393	+[[image:image-20221117145932-2.png]]
	394	+
	395	+
	396	+The payload is ASCII string, representative same HEX:
	397	+
	398	+**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)**
	399	+
340	340	**where:**
341	341
342		-* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
	402	+* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
343	343
344		-* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
	404	+* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
345	345
346		-* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
	406	+* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
347	347
348		-* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
	408	+* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
349	349
350		-* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
	410	+* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
351	351
352		-* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
	412	+* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0
353	353
354		-* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
	414	+* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
355	355
356		-* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
	416	+* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
357	357
358		-* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
	418	+* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
359	359
	420	+* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
360	360
361	361
362	362	== 2.4  Payload Explanation and Sensor Interface ==
363	363
	425	+
364	364	=== 2.4.1  Device ID ===
365	365
366	366
...	...	@@ -375,18 +375,20 @@
375	375	The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
376	376
377	377
	440	+
378	378	=== 2.4.2  Version Info ===
379	379
380	380
381	381	Specify the software version: 0x64=100, which means firmware version 1.00.
382	382
383		-For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
	446	+For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
384	384
385	385
	449	+
386	386	=== 2.4.3  Battery Info ===
387	387
388	388
389		-Check the battery voltage for NMDS200.
	453	+Check the battery voltage for CPN01.
390	390
391	391	Ex1: 0x0B45 = 2885mV
392	392
...	...	@@ -393,54 +393,89 @@
393	393	Ex2: 0x0B49 = 2889mV
394	394
395	395
	460	+
396	396	=== 2.4.4  Signal Strength ===
397	397
398	398
399	399	NB-IoT Network signal Strength.
400	400
401		-(% style="color:blue" %)**Ex1: 0x1d = 29**
	466	+**Ex1: 0x1d = 29**
402	402
403		-(% style="color:#037691" %)**0** (%%) -113dBm or less
	468	+**0**  -113dBm or less
404	404
405		-(% style="color:#037691" %)**1**  (%%) -111dBm
	470	+**1**  -111dBm
406	406
407		-(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
	472	+**2...30** -109dBm... -53dBm
408	408
409		-(% style="color:#037691" %)**31** (%%) -51dBm or greater
	474	+**31**   -51dBm or greater
410	410
411		-(% style="color:#037691" %)**99** (%%) Not known or not detectable
	476	+**99**    Not known or not detectable
412	412
413	413
414		-=== 2.4.5  Distance ===
415	415
	480	+=== 2.4.5  Calculate Flag ===
416	416
417		-[[image:1670407401682-959.png]]
418	418
	483	+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.
419	419
420		-(% style="color:blue" %)**Object1 Distance:**
	485	+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.
421	421
422		-Distance between sensor probe to the first object. (unit: cm)
	487	+Default value: 0.
423	423
424		-For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
	489	+Range (6 bits): (b)000000 ~~ (b) 111111
425	425
426		-(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
427	427
428	428
429		-(% style="color:blue" %)**Object2 Distance:**
	493	+=== 2.4.6  Alarm ===
430	430
431		-Distance between sensor probe to the second object. (unit: cm)
432	432
	496	+See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
433	433
434		-=== 2.4.6  Timestamp ===
435	435
436	436
	500	+=== 2.4.7  Contact Status ===
	501	+
	502	+
	503	+0: Open
	504	+
	505	+1: Close
	506	+
	507	+
	508	+
	509	+=== 2.4.8  Total pulse ===
	510	+
	511	+
	512	+Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
	513	+
	514	+Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
	515	+
	516	+
	517	+
	518	+=== 2.4.9  The last open duration ===
	519	+
	520	+
	521	+Dry Contact last open duration.
	522	+
	523	+Unit: min.
	524	+
	525	+[[image:image-20221021111346-17.png||height="146" width="770"]]
	526	+
	527	+
	528	+
	529	+=== 2.4.10  Timestamp ===
	530	+
	531	+
437	437	Timestamp : 0x6315537b =1662342011
438	438
	534	+Convert Unix timestamp to time 2022-9-5 9:40:11.
439	439
	536	+**~ **
	537	+
	538	+
440	440	== 2.5  Downlink Payload ==
441	441
442	442
443		-By default, NMDS200 prints the downlink payload to console port.
	542	+By default, CPN01 prints the downlink payload to console port.
444	444
445	445	[[image:image-20221021111414-18.png]] ​
446	446
...	...	@@ -457,7 +457,7 @@
457	457
458	458	* (% style="color:#037691" %)**Reset**
459	459
460		-If payload = 0x04FF, it will reset the NMDS200
	559	+If payload = 0x04FF, it will reset the NSE01
461	461
462	462	* (% style="color:#037691" %)**INTMOD**
463	463
...	...	@@ -464,47 +464,115 @@
464	464	Downlink Payload: 06000003, Set AT+INTMOD=3
465	465
466	466
	566	+
467	467	== 2.6  ​LED Indicator ==
468	468
469	469
470		-The NMDS200 has an internal LED which is to show the status of different states.
	570	+The CPN01 has an internal LED which is to show the status of different states.
471	471
472	472	* When the device starts normally, the LED will light up for 1 second.
473		-* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
	573	+* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
474	474	* For each uplink probe, LED will be on for 500ms.
475	475
	576	+== 2.7  Alarm Base on Timeout ==
476	476
477	477
478		-== 2.7  Distance alarm function ==
	579	+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:
479	479
480	480
481		-(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
	582	+(% style="color:blue" %)**1. Keep Status: Status to be monitor**
482	482
483		-(% style="color:#037691" %)**Example 1:**
	584	+Keep Status = 1: Monitor Close to Open event
484	484
485		-AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
	586	+Keep Status = 0: Monitor Open to Close event
486	486
487		-AT+ ALARM2 =min,max
488	488
	589	+(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
489	489
490		-(% style="color:#037691" %)**Example 2:**
	591	+Range 0 ~~ 65535(0xFFFF) seconds.
491	491
492		-AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
	593	+If keep time = 0, Disable Alarm Base on Timeout feature.
493	493
	595	+If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
494	494
495		-== 2.8  Set the number of data to be uploaded and the recording time ==
496	496
	598	+(% style="color:blue" %)**AT Command to configure:**
497	497
	600	+(% style="color:#037691" %)**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.
	601	+
	602	+(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
	603	+
	604	+
	605	+
	606	+== 2.8  Set debug mode ==
	607	+
	608	+
	609	+Feature: Enable or Disable debug mode
	610	+
	611	+(% style="color:blue" %)**AT Command: AT+DEBUG**
	612	+
	613	+[[image:image-20221021111629-21.png]]
	614	+
	615	+
	616	+
	617	+== 2.9  Clear Flash Record ==
	618	+
	619	+
	620	+Feature: Clear flash storage for data log feature.
	621	+
	622	+(% style="color:blue" %)**AT Command: AT+CLRDTA**
	623	+
	624	+[[image:image-20221021111527-19.png]]
	625	+
	626	+
	627	+
	628	+== 2.10  Set trigger mode ==
	629	+
	630	+
	631	+(% style="color:blue" %)**AT Command: AT+TTRMOD**
	632	+
	633	+Feature: Set the trigger interrupt mode.
	634	+
	635	+[[image:image-20221021111552-20.png]]
	636	+
	637	+
	638	+
	639	+== 2.11  Set the calculate flag ==
	640	+
	641	+
	642	+Feature: Set the calculate flag
	643	+
	644	+(% style="color:blue" %)**AT Command: AT+CALCFLAG**
	645	+
	646	+[[image:image-20221021111711-22.png]]
	647	+
	648	+
	649	+
	650	+== 2.12 Set count number ==
	651	+
	652	+
	653	+Feature: Manually set the count number
	654	+
	655	+(% style="color:blue" %)**AT Command: AT+SETCNT**
	656	+
	657	+[[image:image-20221021111748-24.png]]
	658	+
	659	+
	660	+
	661	+== 2.13  Set the number of data to be uploaded and the recording time ==
	662	+
	663	+
498	498	(% style="color:blue" %)**AT Command:**
499	499
500		-(% 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)
	666	+(% 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)
501	501
502		-(% 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.
	668	+(% style="color:#037691" %)**AT+NOUD=8 ** (%%)~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
503	503
504	504
505		-== 2.9  Read or Clear cached data ==
506	506
	672	+== 2.14  Read or Clear cached data ==
507	507
	674	+
508	508	(% style="color:blue" %)**AT Command:**
509	509
510	510	(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
...	...	@@ -511,24 +511,27 @@
511	511
512	512	(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
513	513
514		-[[image:1670408172929-569.png]]
	681	+[[image:image-20221021111810-25.png||height="364" width="797"]]
515	515
516	516
517		-== 2.10  ​Firmware Change Log ==
518	518
	685	+== 2.15  ​Firmware Change Log ==
519	519
520		-Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
521	521
	688	+Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
	689	+
522	522	Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
523	523
524	524
525		-== 2.11  ​Battery Analysis ==
526	526
527		-=== 2.11.1  ​Battery Type ===
	694	+== 2.16  ​Battery Analysis ==
528	528
529	529
530		-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.
	697	+=== 2.16.1  ​Battery Type ===
531	531
	699	+
	700	+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.
	701	+
532	532	The battery is designed to last for several years depends on the actual use environment and update interval.
533	533
534	534	The battery-related documents as below:
...	...	@@ -542,9 +542,10 @@
542	542	[[image:image-20221021111911-26.png]] ​
543	543
544	544
545		-=== 2.11.2  Power consumption Analyze ===
546	546
	716	+=== 2.16.2  Power consumption Analyze ===
547	547
	718	+
548	548	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.
549	549
550	550	Instruction to use as below:
...	...	@@ -564,18 +564,21 @@
564	564	[[image:1666596205057-567.png]] ​
565	565
566	566
567		-=== 2.11.3  ​Battery Note ===
568	568
	739	+=== 2.16.3  ​Battery Note ===
569	569
	741	+
570	570	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.
571	571
572	572
573		-=== 2.11.4  Replace the battery ===
574	574
	746	+=== 2.16.4  Replace the battery ===
575	575
576		-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).
577	577
	749	+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).
578	578
	751	+
	752	+
579	579	= 3. ​ Access NB-IoT Module =
580	580
581	581
...	...	@@ -583,12 +583,13 @@
583	583
584	584	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/]]
585	585
	760	+[[image:image-20221021112006-28.png]] ​
586	586
587		-[[image:image-20221118094449-6.png]] ​
588	588
589	589
590	590	= 4.  Using the AT Commands =
591	591
	766	+
592	592	== 4.1  Access AT Commands ==
593	593
594	594
...	...	@@ -619,63 +619,65 @@
619	619
620	620	AT+INTMOD            : Set the trigger interrupt mode
621	621
622		-AT+5VT  : Set extend the time of 5V power
	797	+AT+5VT  : Set extend the time of 5V power
623	623
624		-AT+PRO  : Choose agreement
	799	+AT+PRO  : Choose agreement
625	625
626		-AT+RXDL  : Extend the sending and receiving time
	801	+AT+RXDL  : Extend the sending and receiving time
627	627
628		-AT+SERVADDR  : Server Address
	803	+AT+SERVADDR  : Server Address
629	629
630		-AT+TR      :  Get or Set record time
	805	+AT+TR      :  Get or Set record time
631	631
632		-AT+NOUD :  Get or Set the number of data to be uploaded
	807	+AT+NOUD      : Get or Set the number of data to be uploaded
633	633
634	634	AT+CDP     :  Read or Clear cached data
635	635
636		-AT+DEBUG:  Enable or Disable debug mode
	811	+AT+ DEBUG   : Enable or Disable debug mode
637	637
638		-AT+ALARM1:  Get or Set alarm of distance1
	813	+AT+ TTRIG   : Get or Set Alarm Base on Timeout
639	639
640		-AT+ALARM2:  Get or Set alarm of distance2
	815	+AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
641	641
642		-AT+GETSENSORVALUE :  Returns the current sensor measurement
	817	+AT+ CALCFLAG   : Get or Set the calculate flag
643	643
644		-AT+POWERIC :  Get or set the Power IC flag
	819	+AT+ CLRC   : Clear current door open count
645	645
646	646
647	647	(% style="color:blue" %)**COAP Management**
648	648
649		-AT+URI :  Resource parameters
	824	+AT+URI            : Resource parameters
650	650
651	651
652	652	(% style="color:blue" %)**UDP Management**
653	653
654		-AT+CFM :  Upload confirmation mode (only valid for UDP)
	829	+AT+CFM          : Upload confirmation mode (only valid for UDP)
655	655
656	656
657	657	(% style="color:blue" %)**MQTT Management**
658	658
659		-AT+CLIENT  : Get or Set MQTT client
	834	+AT+CLIENT               : Get or Set MQTT client
660	660
661		-AT+UNAME : Get or Set MQTT Username
	836	+AT+UNAME  : Get or Set MQTT Username
662	662
663		-AT+PWD  :  Get or Set MQTT password
	838	+AT+PWD                  : Get or Set MQTT password
664	664
665		-AT+PUBTOPIC :  Get or Set MQTT publish topic
	840	+AT+PUBTOPIC  : Get or Set MQTT publish topic
666	666
667		-AT+SUBTOPIC :  Get or Set MQTT subscription topic
	842	+AT+SUBTOPIC  : Get or Set MQTT subscription topic
668	668
669	669
670	670	(% style="color:blue" %)**Information**
671	671
672		-AT+FDR :  Factory Data Reset
	847	+AT+FDR  : Factory Data Reset
673	673
674		-AT+PWORD :  Serial Access Password
	849	+AT+PWORD  : Serial Access Password
675	675
676	676
	852	+
677	677	= ​5.  FAQ =
678	678
	855	+
679	679	== 5.1 ​ How to Upgrade Firmware ==
680	680
681	681
...	...	@@ -683,11 +683,13 @@
683	683
684	684	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]]
685	685
686		-(% 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.**
	863	+(% style="color:red" %)**Notice: **(% style="color:blue" %)**CPN01** (%%)**and (% style="color:blue" %)CPL01(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
687	687
688	688
	866	+
689	689	= 6.  Trouble Shooting =
690	690
	869	+
691	691	== 6.1  ​Connection problem when uploading firmware ==
692	692
693	693
...	...	@@ -694,6 +694,7 @@
694	694	(% 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]]
695	695
696	696
	876	+
697	697	== 6.2  AT Command input doesn't work ==
698	698
699	699
...	...	@@ -700,20 +700,26 @@
700	700	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.
701	701
702	702
	883	+
703	703	= 7. ​ Order Info =
704	704
705	705
706		-Part Number:(% style="color:blue" %)** NMDS200**
	887	+Part Number**:** CPN01
707	707
708	708
	890	+
709	709	= 8.  Packing Info =
710	710
711	711
712	712	(% style="color:blue" %)**Package Includes**:
713	713
714		-* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
	896	+* CPN01 Open/Close Sensor x 1
	897	+* External antenna x 1
715	715
	899	+(% style="color:blue" %)**Dimension and weight**:
716	716
	901	+* Size: 195 x 125 x 55 mm
	902	+* Weight:   420g
717	717
718	718	= 9.  Support =
719	719

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

1670471530120-960.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-67.6 KB

Content

1670471559211-638.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-170.6 KB

Content

1670471584490-640.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-91.1 KB

Content

1670471613823-833.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-181.0 KB

Content

LMDS200_10.jpg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-39.9 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