Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 25 removed)
  • 1670404362039-351.png
  • 1670405841875-916.png
  • 1670405928926-116.png
  • 1670406036256-101.png
  • 1670406261143-723.png
  • 1670407401682-959.png
  • 1670408172929-569.png
  • LMDS200_10.jpg
  • image-20221117142300-1.png
  • image-20221117145932-2.png
  • image-20221117150312-3.png
  • 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,7 +1,12 @@
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	7
...	...	@@ -10,35 +10,52 @@
10	10
11	11	= 1.  Introduction =
12	12
13		-== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
14	14
	19	+== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
15	15
	21	+
16	16	(((
17		-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.
	23	+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.
	24	+)))
18	18
19		-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	+(((
	27	+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.
	28	+)))
20	20
21		-NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
	30	+(((
	31	+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.
	32	+)))
22	22
23		-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	+(((
	35	+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.
	36	+)))
24	24
25		-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	+(((
	39	+NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
	40	+)))
26	26
27		-NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
	42	+(((
	43	+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.
	44	+)))
28	28
29		-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	+(((
	47	+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)
	48	+)))
30	30
31		-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	+(((
	51	+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.
32	32	)))
33	33
34	34
	55	+
35	35	== ​1.2  Features ==
36	36
37	37
38	38	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
39		-* Short uplink interval for Distance Alarm
	60	+* Open/Close detect
	61	+* Open/Close statistics
40	40	* Monitor Battery Level
41		-* Microwave Radar for distance detection
	63	+* connect two door sensors
42	42	* Datalog feature
43	43	* Uplink periodically
44	44	* Downlink to change configure
...	...	@@ -49,37 +49,38 @@
49	49	* Micro SIM card slot for NB-IoT SIM
50	50	* 8500mAh Battery for long-term use
51	51
52		-== 1.3 Radar probe specification ==
53	53
54	54
55		-* Measuring Method: FMCW
56		-* Frequency: 24.000 24.500 GHz
57		-* Measurement output power: 6dBm
58		-* Measure range: 0.5 20m
59		-* Accuracy: ±0.1m
60		-* Resolution: 0.01m
61		-* Horizontal Angel: 78°
62		-* Vertical Angel: 23°
63	63
64		-== 1.4  Storage Temperature ==
	77	+== 1.3  Storage & Operation ==
65	65
66	66
67		- -40°C to +85°C
	80	+Temperature -40°C to +85°C
68	68
69	69
	83	+== 1.4  Mechanical ==
	84	+
	85	+
	86	+[[image:image-20221117114937-4.png]]
	87	+
	88	+
	89	+[[image:image-20221117114949-5.png]]
	90	+
	91	+
	92	+[[image:image-20221117115010-6.png]]
	93	+
	94	+
	95	+
	96	+
	97	+
	98	+
70	70	== 1.5 ​ Applications ==
71	71
72	72
73		-* Horizontal distance measurement
74		-* Liquid level measurement
75		-* Parking management system
76		-* Object proximity and presence detection
77		-* Intelligent trash can management system
78		-* Robot obstacle avoidance
79		-* Automatic control
80		-* Sewer
81		-* Bottom water level monitoring
	102	+[[image:image-20221117114842-3.png]]
82	82
	104	+
	105	+
83	83	== 1.6  Specification ==
84	84
85	85
...	...	@@ -86,62 +86,111 @@
86	86	(% style="color:blue" %)**Common DC Characteristics:**
87	87
88	88	* Supply Voltage: 2.1v ~~ 3.6v
89		-* Operating Temperature: 0 ~~ 70°C
	112	+* Operating Temperature: -40 ~~ 85°C
90	90
91	91	(% style="color:blue" %)**NB-IoT Spec:**
92	92
93		-* B1 @H-FDD: 2100MHz
94		-* B3 @H-FDD: 1800MHz
95		-* B8 @H-FDD: 900MHz
96		-* B5 @H-FDD: 850MHz
97		-* B20 @H-FDD: 800MHz
98		-* B28 @H-FDD: 700MHz
	116	+* - B1 @H-FDD: 2100MHz
	117	+* - B3 @H-FDD: 1800MHz
	118	+* - B8 @H-FDD: 900MHz
	119	+* - B5 @H-FDD: 850MHz
	120	+* - B20 @H-FDD: 800MHz
	121	+* - B28 @H-FDD: 700MHz
99	99
100		-== 1.7  Installation ==
101	101
102	102
103		-Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
	125	+== 1.7  Pin Definitions and Switch ==
104	104
105	105
106		-[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
	128	+[[image:image-20221021110429-4.png]]
107	107
108	108
	131	+=== 1.7.1  Pin Definition ===
109	109
110		-== 1.8  Pin Definitions and Switch ==
111	111
	134	+CPN01 is pre-configured to connect to two external wires. The other pins are not used. If user wants to know more about other pins, please refer to the **[[LSN50v2 User Manual>>doc:Main.User Manual for LoRaWAN End Nodes.LSN50 & LSN50-V2 - LoRaWAN Sensor Node User Manual.WebHome]]**.
112	112
113		-[[image:1670404362039-351.png]]
114	114
115	115
116		-= 2.  Use NMDS200 to communicate with IoT Server =
	138	+=== 1.7.2  Jumper JP2(Power ON/OFF) ===
117	117
	140	+
	141	+Power on Device when putting this jumper.
	142	+
	143	+
	144	+
	145	+=== 1.7.3  BOOT MODE / SW1 ===
	146	+
	147	+
	148	+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.
	149	+
	150	+2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
	151	+
	152	+
	153	+
	154	+=== 1.7.4  Reset Button ===
	155	+
	156	+
	157	+Press to reboot the device.
	158	+
	159	+
	160	+
	161	+=== 1.7.5  LED ===
	162	+
	163	+
	164	+The LED will blink when :
	165	+
	166	+1.  Boot the device in flash mode
	167	+
	168	+2.  Send an uplink packet
	169	+
	170	+
	171	+
	172	+== 1.8  Magnet Distance ==
	173	+
	174	+
	175	+**Wood Door:** 10 ~~ 30mm
	176	+
	177	+**Iron Door:  **30 ~~ 45mm
	178	+
	179	+
	180	+
	181	+= 2.  Use CPN01 to communicate with IoT Server =
	182	+
	183	+
118	118	== 2.1  How it works ==
119	119
120	120
121		-The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
	187	+The CPN01 is equipped with an NB-IoT module, the pre-loaded firmware in CPN01 will get (% style="color:blue" %)**Open/Close Event or Count**(%%) from sensor and send the value to the NB-IoT network. The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01.
122	122
123		-The diagram below shows the working flow in the default firmware of NMDS200:
	189	+The diagram below shows the working flow in the default firmware of CPN01:
124	124
125	125	[[image:image-20221021110615-5.png]]
126	126
127	127
128		-== 2.2 ​ Configure NMDS200 ==
129	129
	195	+== 2.2 ​ Configure CPN01 ==
130	130
131		-To use NMDS200 in your city, make sure to meet below requirements:
132	132
	198	+=== 2.2.1 Test Requirement ===
	199	+
	200	+
	201	+To use CPN01 in your city, make sure to meet below requirements:
	202	+
133	133	* Your local operator has already distributed an NB-IoT Network.
134		-* The local NB-IoT network used the band that NMDS200 supports.
	204	+* The local NB-IoT network used the band that CPN01 supports.
135	135	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
136	136
137		-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.
	207	+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** (% 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.
138	138
139		-[[image:image-20221208090742-1.png]]
	209	+[[image:image-20221023000439-3.png]]
140	140
	211	+ ​
141	141
142		-=== 2.2.1 Insert NB-IoT SIM card ===
143	143
	214	+=== 2.2.2 Insert NB-IoT SIM card ===
144	144
	216	+
145	145	Insert the NB-IoT Card get from your provider.
146	146
147	147	User needs to take out the NB-IoT module and insert the SIM card like below:
...	...	@@ -149,11 +149,12 @@
149	149	[[image:image-20221021110745-6.png]] ​
150	150
151	151
152		-=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
153	153
	225	+=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
154	154
155		-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.
156	156
	228	+User need to configure CPN01 via serial port to set the (% style="color:red" %)**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.
	229	+
157	157	(% style="color:blue" %)**Connection:**
158	158
159	159	(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
...	...	@@ -175,11 +175,11 @@
175	175
176	176	* Flow Control: (% style="color:red" %)**None**
177	177
178		-Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
	251	+Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
179	179
180	180	​[[image:image-20221021110817-7.png]]
181	181
182		-NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
	255	+CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
183	183
184	184
185	185	(% 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,13 +186,13 @@
186	186
187	187
188	188
189		-=== 2.2.3 Use CoAP protocol to uplink data ===
	262	+=== 2.2.4 Use CoAP protocol to uplink data ===
190	190
191	191
192	192	(% style="color:red" %)**Note: if you don't have a CoAP server, you can refer this link to set up a CoAP server: **(%%)[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
193	193
194	194
195		-(% style="color:blue" %)**Use below commands in NMDS200:**
	268	+(% style="color:blue" %)**Use below commands in CPN01:**
196	196
197	197	* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
198	198
...	...	@@ -205,14 +205,15 @@
205	205	[[image:image-20221021110948-8.png]]
206	206
207	207
208		-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.
	281	+After configuring the server address and (% style="color:green" %)**reset CPN01**(%%) (via AT+ATZ ), CPN01 will start to uplink sensor values to the CoAP server.
209	209
210		-[[image:1670405841875-916.png]] ​
	283	+[[image:image-20221021110956-9.png]] ​
211	211
212	212
213		-=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
214	214
	287	+=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
215	215
	289	+
216	216	(% style="color:blue" %)**AT Commands:**
217	217
218	218	* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
...	...	@@ -228,9 +228,10 @@
228	228
229	229	​
230	230
231		-=== 2.2.5 Use MQTT protocol to uplink data ===
232	232
	306	+=== 2.2.6 Use MQTT protocol to uplink data ===
233	233
	308	+
234	234	(% style="color:blue" %)**AT Commands:**
235	235
236	236	* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
...	...	@@ -247,10 +247,10 @@
247	247
248	248	* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
249	249
250		-​ [[image:image-20221118103445-7.png]]
	325	+​ [[image:image-20221021111058-12.png]]
251	251
252	252
253		-[[image:1670405928926-116.png]]
	328	+[[image:image-20221021111201-16.png||height="472" width="653"]]
254	254
255	255	​
256	256
...	...	@@ -257,9 +257,10 @@
257	257	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.
258	258
259	259
260		-=== 2.2.6 Use TCP protocol to uplink data ===
261	261
	336	+=== 2.2.7 Use TCP protocol to uplink data ===
262	262
	338	+
263	263	(% style="color:blue" %)**AT Commands:**
264	264
265	265	* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
...	...	@@ -266,76 +266,82 @@
266	266
267	267	* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
268	268
269		-​ [[image:1670406036256-101.png||height="676" width="713"]]
	345	+​ [[image:image-20221021111125-14.png]]
270	270
271		-
272	272	[[image:image-20221021111131-15.png]]
273	273
274	274	​
275	275
276		-=== 2.2.7 Change Update Interval ===
277	277
	352	+=== 2.2.8 Change Update Interval ===
278	278
	354	+
279	279	User can use below command to change the (% style="color:blue" %)**uplink interval**.
280	280
281		-* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
	357	+* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
282	282
283	283	(% style="color:red" %)**NOTE:**
284	284
285		-1.  By default, the device will send an uplink message every 4 hour.
	361	+1.  By default, the device will send an uplink message every 1 hour.
286	286
287	287
	364	+
288	288	== 2.3  Uplink Payload ==
289	289
290	290
291		-The uplink payload includes 23 bytes in total by default.
	368	+The uplink payload includes 123 bytes in total by default.
292	292
293		-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.
	370	+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.
294	294
295	295
296		-(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
297		-|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:90px" %)**2**|(% style="width:100px" %)**2**
298		-|=(% 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.5A0A0Distance"]] |(% style="width:93px" %) [[Distance  2>>||anchor="H2.4.5A0A0Distance"]]
	373	+(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
	374	+|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:60px" %)**3**
	375	+|=(% style="width: 96px;" %)**Value**|(% style="width:84px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:44px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:121px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:52px" %)MOD|(% style="width:84px" %)[[ Calculate Flag>>||anchor="H2.4.5A0CalculateFlag"]]|(% style="width:116px" %)[[Contact Status>>||anchor="H2.4.7A0ContactStatus"]]|(% style="width:57px" %)[[Alarm>>||anchor="H2.4.6A0Alarm"]]|(% style="width:91px" %)[[Total pulse>>||anchor="H2.4.8A0Totalpulse"]]
299	299
300		-(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
301		-|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
302		-**1-32 group**
303		-)))
304		-|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
	377	+(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
	378	+|(% style="width:100px" %)**3**|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:100px" %)**3**|(% style="width:80px" %)4|(% style="width:50px" %)**8 group**
	379	+|(% style="width:176px" %)[[The last open duration>>||anchor="H2.4.9A0Thelastopenduration"]]|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% style="width:115px" %)Contact Status|(% style="width:92px" %)Total pulse|(% style="width:169px" %)The last open duration|(% style="width:97px" %)Time stamp|(% style="width:74px" %)...
305	305
306		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
	381	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
307	307
308		-[[image:1670406261143-723.png]]
	383	+[[image:image-20221021111201-16.png||height="572" width="792"]]
309	309
310	310
311		-The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
	386	+The payload is ASCII string, representative same HEX:
312	312
313		-**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__(%%)**
	388	+**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0c78__(% style="color:#00b0f0" %) __17__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__ (% style="color:#660066" %)__00__ (% style="color:#aaaa40" %)__000009__(% style="color:#663300" %) __000002__ (% style="color:#d60093" %)__6315537b__ (% style="color:#660066" %)__01 00000b 02 0000026 63510fed__ (%%)__0100000e0200000263510f39__ __010000000000000063510e85__ __010000000000000063510d2e__ __010000000000000063510c7a__ __010000000000000063510bc6__ __010000000000000063510954__ __010000000000000063510882 __**
314	314
315	315	**where:**
316	316
317		-* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
	392	+* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
318	318
319		-* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
	394	+* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
320	320
321		-* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
	396	+* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
322	322
323		-* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
	398	+* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
324	324
325		-* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
	400	+* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
326	326
327		-* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
	402	+* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
328	328
329		-* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
	404	+* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
330	330
331		-* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
	406	+* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
332	332
333		-* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
	408	+* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
334	334
	410	+* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
335	335
	412	+* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
336	336
	414	+* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
	415	+
	416	+* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
	417	+
337	337	== 2.4  Payload Explanation and Sensor Interface ==
338	338
	420	+
339	339	=== 2.4.1  Device ID ===
340	340
341	341
...	...	@@ -350,18 +350,20 @@
350	350	The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
351	351
352	352
	435	+
353	353	=== 2.4.2  Version Info ===
354	354
355	355
356	356	Specify the software version: 0x64=100, which means firmware version 1.00.
357	357
358		-For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
	441	+For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
359	359
360	360
	444	+
361	361	=== 2.4.3  Battery Info ===
362	362
363	363
364		-Check the battery voltage for NMDS200.
	448	+Check the battery voltage for CPN01.
365	365
366	366	Ex1: 0x0B45 = 2885mV
367	367
...	...	@@ -368,54 +368,89 @@
368	368	Ex2: 0x0B49 = 2889mV
369	369
370	370
	455	+
371	371	=== 2.4.4  Signal Strength ===
372	372
373	373
374	374	NB-IoT Network signal Strength.
375	375
376		-(% style="color:blue" %)**Ex1: 0x1d = 29**
	461	+**Ex1: 0x1d = 29**
377	377
378		-(% style="color:#037691" %)**0** (%%) -113dBm or less
	463	+**0**  -113dBm or less
379	379
380		-(% style="color:#037691" %)**1**  (%%) -111dBm
	465	+**1**  -111dBm
381	381
382		-(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
	467	+**2...30** -109dBm... -53dBm
383	383
384		-(% style="color:#037691" %)**31** (%%) -51dBm or greater
	469	+**31**   -51dBm or greater
385	385
386		-(% style="color:#037691" %)**99** (%%) Not known or not detectable
	471	+**99**    Not known or not detectable
387	387
388	388
389		-=== 2.4.5  Distance ===
390	390
	475	+=== 2.4.5  Calculate Flag ===
391	391
392		-[[image:1670407401682-959.png]]
393	393
	478	+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.
394	394
395		-(% style="color:blue" %)**Object1 Distance:**
	480	+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.
396	396
397		-Distance between sensor probe to the first object. (unit: cm)
	482	+Default value: 0.
398	398
399		-For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
	484	+Range (6 bits): (b)000000 ~~ (b) 111111
400	400
401		-(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
402	402
403	403
404		-(% style="color:blue" %)**Object2 Distance:**
	488	+=== 2.4.6  Alarm ===
405	405
406		-Distance between sensor probe to the second object. (unit: cm)
407	407
	491	+See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
408	408
409		-=== 2.4.6  Timestamp ===
410	410
411	411
	495	+=== 2.4.7  Contact Status ===
	496	+
	497	+
	498	+0: Open
	499	+
	500	+1: Close
	501	+
	502	+
	503	+
	504	+=== 2.4.8  Total pulse ===
	505	+
	506	+
	507	+Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
	508	+
	509	+Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
	510	+
	511	+
	512	+
	513	+=== 2.4.9  The last open duration ===
	514	+
	515	+
	516	+Dry Contact last open duration.
	517	+
	518	+Unit: min.
	519	+
	520	+[[image:image-20221021111346-17.png||height="146" width="770"]]
	521	+
	522	+
	523	+
	524	+=== 2.4.10  Timestamp ===
	525	+
	526	+
412	412	Timestamp : 0x6315537b =1662342011
413	413
	529	+Convert Unix timestamp to time 2022-9-5 9:40:11.
414	414
	531	+**~ **
	532	+
	533	+
415	415	== 2.5  Downlink Payload ==
416	416
417	417
418		-By default, NMDS200 prints the downlink payload to console port.
	537	+By default, CPN01 prints the downlink payload to console port.
419	419
420	420	[[image:image-20221021111414-18.png]] ​
421	421
...	...	@@ -432,7 +432,7 @@
432	432
433	433	* (% style="color:#037691" %)**Reset**
434	434
435		-If payload = 0x04FF, it will reset the NMDS200
	554	+If payload = 0x04FF, it will reset the NSE01
436	436
437	437	* (% style="color:#037691" %)**INTMOD**
438	438
...	...	@@ -439,49 +439,115 @@
439	439	Downlink Payload: 06000003, Set AT+INTMOD=3
440	440
441	441
	561	+
442	442	== 2.6  ​LED Indicator ==
443	443
444	444
445		-The NMDS200 has an internal LED which is to show the status of different states.
	565	+The CPN01 has an internal LED which is to show the status of different states.
446	446
447	447	* When the device starts normally, the LED will light up for 1 second.
448		-* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
	568	+* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
449	449	* For each uplink probe, LED will be on for 500ms.
450	450
	571	+== 2.7  Alarm Base on Timeout ==
451	451
452	452
453		-== 2.7  Distance alarm function ==
	574	+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:
454	454
455	455
456		-(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
	577	+(% style="color:blue" %)**1. Keep Status: Status to be monitor**
457	457
458		-(% style="color:#037691" %)**Example 1:**
	579	+Keep Status = 1: Monitor Close to Open event
459	459
460		-AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
	581	+Keep Status = 0: Monitor Open to Close event
461	461
462		-AT+ ALARM2 =min,max
463	463
	584	+(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
464	464
465		-(% style="color:#037691" %)**Example 2:**
	586	+Range 0 ~~ 65535(0xFFFF) seconds.
466	466
467		-AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
	588	+If keep time = 0, Disable Alarm Base on Timeout feature.
468	468
	590	+If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
469	469
470	470
	593	+(% style="color:blue" %)**AT Command to configure:**
471	471
472		-== 2.8  Set the number of data to be uploaded and the recording time ==
	595	+(% 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.
473	473
	597	+(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
474	474
	599	+
	600	+
	601	+== 2.8  Set debug mode ==
	602	+
	603	+
	604	+Feature: Enable or Disable debug mode
	605	+
	606	+(% style="color:blue" %)**AT Command: AT+DEBUG**
	607	+
	608	+[[image:image-20221021111629-21.png]]
	609	+
	610	+
	611	+
	612	+== 2.9  Clear Flash Record ==
	613	+
	614	+
	615	+Feature: Clear flash storage for data log feature.
	616	+
	617	+(% style="color:blue" %)**AT Command: AT+CLRDTA**
	618	+
	619	+[[image:image-20221021111527-19.png]]
	620	+
	621	+
	622	+
	623	+== 2.10  Set trigger mode ==
	624	+
	625	+
	626	+(% style="color:blue" %)**AT Command: AT+TTRMOD**
	627	+
	628	+Feature: Set the trigger interrupt mode.
	629	+
	630	+[[image:image-20221021111552-20.png]]
	631	+
	632	+
	633	+
	634	+== 2.11  Set the calculate flag ==
	635	+
	636	+
	637	+Feature: Set the calculate flag
	638	+
	639	+(% style="color:blue" %)**AT Command: AT+CALCFLAG**
	640	+
	641	+[[image:image-20221021111711-22.png]]
	642	+
	643	+
	644	+
	645	+== 2.12 Set count number ==
	646	+
	647	+
	648	+Feature: Manually set the count number
	649	+
	650	+(% style="color:blue" %)**AT Command: AT+SETCNT**
	651	+
	652	+[[image:image-20221021111748-24.png]]
	653	+
	654	+
	655	+
	656	+== 2.13  Set the number of data to be uploaded and the recording time ==
	657	+
	658	+
475	475	(% style="color:blue" %)**AT Command:**
476	476
477		-(% 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)
	661	+(% 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)
478	478
479		-(% 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.
	663	+(% 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.
480	480
481	481
482		-== 2.9  Read or Clear cached data ==
483	483
	667	+== 2.14  Read or Clear cached data ==
484	484
	669	+
485	485	(% style="color:blue" %)**AT Command:**
486	486
487	487	(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
...	...	@@ -488,24 +488,27 @@
488	488
489	489	(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
490	490
491		-[[image:1670408172929-569.png]]
	676	+[[image:image-20221021111810-25.png||height="364" width="797"]]
492	492
493	493
494		-== 2.10  ​Firmware Change Log ==
495	495
	680	+== 2.15  ​Firmware Change Log ==
496	496
497		-Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
498	498
	683	+Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
	684	+
499	499	Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
500	500
501	501
502		-== 2.11  ​Battery Analysis ==
503	503
504		-=== 2.11.1  ​Battery Type ===
	689	+== 2.16  ​Battery Analysis ==
505	505
506	506
507		-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.
	692	+=== 2.16.1  ​Battery Type ===
508	508
	694	+
	695	+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.
	696	+
509	509	The battery is designed to last for several years depends on the actual use environment and update interval.
510	510
511	511	The battery-related documents as below:
...	...	@@ -519,9 +519,10 @@
519	519	[[image:image-20221021111911-26.png]] ​
520	520
521	521
522		-=== 2.11.2  Power consumption Analyze ===
523	523
	711	+=== 2.16.2  Power consumption Analyze ===
524	524
	713	+
525	525	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.
526	526
527	527	Instruction to use as below:
...	...	@@ -541,18 +541,21 @@
541	541	[[image:1666596205057-567.png]] ​
542	542
543	543
544		-=== 2.11.3  ​Battery Note ===
545	545
	734	+=== 2.16.3  ​Battery Note ===
546	546
	736	+
547	547	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.
548	548
549	549
550		-=== 2.11.4  Replace the battery ===
551	551
	741	+=== 2.16.4  Replace the battery ===
552	552
553		-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).
554	554
	744	+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).
555	555
	746	+
	747	+
556	556	= 3. ​ Access NB-IoT Module =
557	557
558	558
...	...	@@ -560,12 +560,13 @@
560	560
561	561	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/]]
562	562
	755	+[[image:image-20221021112006-28.png]] ​
563	563
564		-[[image:image-20221118094449-6.png]] ​
565	565
566	566
567	567	= 4.  Using the AT Commands =
568	568
	761	+
569	569	== 4.1  Access AT Commands ==
570	570
571	571
...	...	@@ -604,55 +604,57 @@
604	604
605	605	AT+SERVADDR  : Server Address
606	606
607		-AT+TR      :  Get or Set record time
	800	+AT+TR      :  Get or Set record time
608	608
609		-AT+NOUD :  Get or Set the number of data to be uploaded
	802	+AT+NOUD      : Get or Set the number of data to be uploaded
610	610
611	611	AT+CDP     :  Read or Clear cached data
612	612
613		-AT+DEBUG:  Enable or Disable debug mode
	806	+AT+ DEBUG   : Enable or Disable debug mode
614	614
615		-AT+ALARM1:  Get or Set alarm of distance1
	808	+AT+ TTRIG   : Get or Set Alarm Base on Timeout
616	616
617		-AT+ALARM2:  Get or Set alarm of distance2
	810	+AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
618	618
619		-AT+GETSENSORVALUE :  Returns the current sensor measurement
	812	+AT+ CALCFLAG   : Get or Set the calculate flag
620	620
621		-AT+POWERIC :  Get or set the Power IC flag
	814	+AT+ CLRC   : Clear current door open count
622	622
623	623
624	624	(% style="color:blue" %)**COAP Management**
625	625
626		-AT+URI :  Resource parameters
	819	+AT+URI            : Resource parameters
627	627
628	628
629	629	(% style="color:blue" %)**UDP Management**
630	630
631		-AT+CFM :  Upload confirmation mode (only valid for UDP)
	824	+AT+CFM          : Upload confirmation mode (only valid for UDP)
632	632
633	633
634	634	(% style="color:blue" %)**MQTT Management**
635	635
636		-AT+CLIENT  : Get or Set MQTT client
	829	+AT+CLIENT               : Get or Set MQTT client
637	637
638		-AT+UNAME : Get or Set MQTT Username
	831	+AT+UNAME  : Get or Set MQTT Username
639	639
640		-AT+PWD  :  Get or Set MQTT password
	833	+AT+PWD                  : Get or Set MQTT password
641	641
642		-AT+PUBTOPIC :  Get or Set MQTT publish topic
	835	+AT+PUBTOPIC  : Get or Set MQTT publish topic
643	643
644		-AT+SUBTOPIC :  Get or Set MQTT subscription topic
	837	+AT+SUBTOPIC  : Get or Set MQTT subscription topic
645	645
646	646
647	647	(% style="color:blue" %)**Information**
648	648
649		-AT+FDR :  Factory Data Reset
	842	+AT+FDR  : Factory Data Reset
650	650
651		-AT+PWORD :  Serial Access Password
	844	+AT+PWORD  : Serial Access Password
652	652
653	653
	847	+
654	654	= ​5.  FAQ =
655	655
	850	+
656	656	== 5.1 ​ How to Upgrade Firmware ==
657	657
658	658
...	...	@@ -660,11 +660,13 @@
660	660
661	661	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]]
662	662
663		-(% 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.**
	858	+(% 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.**
664	664
665	665
	861	+
666	666	= 6.  Trouble Shooting =
667	667
	864	+
668	668	== 6.1  ​Connection problem when uploading firmware ==
669	669
670	670
...	...	@@ -671,6 +671,7 @@
671	671	(% 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]]
672	672
673	673
	871	+
674	674	== 6.2  AT Command input doesn't work ==
675	675
676	676
...	...	@@ -677,19 +677,27 @@
677	677	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.
678	678
679	679
	878	+
680	680	= 7. ​ Order Info =
681	681
682	682
683		-Part Number:(% style="color:blue" %)** NMDS200**
	882	+Part Number**:** CPN01
684	684
685	685
	885	+
686	686	= 8.  Packing Info =
687	687
688	688
689	689	(% style="color:blue" %)**Package Includes**:
690	690
691		-* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
	891	+* CPN01 Open/Close Sensor x 1
	892	+* External antenna x 1
692	692
	894	+(% style="color:blue" %)**Dimension and weight**:
	895	+
	896	+* Size: 195 x 125 x 55 mm
	897	+* Weight:   420g
	898	+
693	693	= 9.  Support =
694	694
695	695

1670404362039-351.png

Author

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

Size

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

Content

1670405841875-916.png

Author

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

Size

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

Content

1670405928926-116.png

Author

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

Size

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

Content

1670406036256-101.png

Author

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

Size

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

Content

1670406261143-723.png

Author

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

Size

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

Content

1670407401682-959.png

Author

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

Size

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

Content

1670408172929-569.png

Author

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

Size

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

Content

LMDS200_10.jpg

Author

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

Size

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

Content

image-20221117142300-1.png

Author

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

Size

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

Content

image-20221117145932-2.png

Author

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

Size

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

Content

image-20221117150312-3.png

Author

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

Size

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

Content

image-20221118092935-1.png

Author

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

Size

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

Content

image-20221118093144-2.png

Author

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

Size

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

Content

image-20221118093512-3.png

Author

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

Size

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

Content

image-20221118093658-4.png

Author

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

Size

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

Content

image-20221118094227-5.png

Author

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

Size

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

Content

image-20221118094449-6.png

Author

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

Size

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

Content

image-20221118103445-7.png

Author

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

Size

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

Content

image-20221118103453-8.png

Author

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

Size

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

Content

image-20221118103547-9.png

Author

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

Size

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

Content

image-20221207170748-1.png

Author

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

Size

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

Content

image-20221207170748-2.png

Author

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

Size

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

Content

image-20221207173200-3.png

Author

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

Size

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

Content

image-20221207173300-4.png

Author

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

Size

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

Content

image-20221208090742-1.png

Author

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

Size

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

Content