Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 29 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-20221117114842-3.png
  • image-20221117114937-4.png
  • image-20221117114949-5.png
  • image-20221117115010-6.png
  • 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,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,35 +11,54 @@
11	11
12	12	= 1.  Introduction =
13	13
14		-== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
15	15
	19	+== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
16	16
	21	+
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.
	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	+)))
19	19
20		-The NMDS200 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
	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	+)))
21	21
22		-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	+)))
23	23
24		-NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range.
	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	+)))
25	25
26		-NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technology**(%%) developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
	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	+)))
27	27
28		-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	+)))
29	29
30		-NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
	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	+)))
31	31
32		-To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection.
	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.
33	33	)))
34	34
35	35
	55	+​
	56	+
	57	+
36	36	== ​1.2  Features ==
37	37
38	38
39	39	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
40		-* Short uplink interval for Distance Alarm
	62	+* Open/Close detect
	63	+* Open/Close statistics
41	41	* Monitor Battery Level
42		-* Microwave Radar for distance detection
	65	+* Uplink on periodically and open/close event
43	43	* Datalog feature
44	44	* Uplink periodically
45	45	* Downlink to change configure
...	...	@@ -50,99 +50,132 @@
50	50	* Micro SIM card slot for NB-IoT SIM
51	51	* 8500mAh Battery for long-term use
52	52
53		-== 1.3 Radar probe specification ==
	76	+== 1.3  Specification ==
54	54
55	55
56		-* Measuring Method: FMCW
57		-* Frequency: 24.000 24.500 GHz
58		-* Measurement output power: 6dBm
59		-* Measure range: 0.5 20m
60		-* Accuracy: ±0.1m
61		-* Resolution: 0.01m
62		-* Horizontal Angel: 78°
63		-* Vertical Angel: 23°
	79	+(% style="color:blue" %)**Common DC Characteristics:**
64	64
65		-== 1.4  Storage Temperature ==
	81	+* Supply Voltage: 2.1v ~~ 3.6v
	82	+* Operating Temperature: -40 ~~ 85°C
66	66
	84	+(% style="color:blue" %)**NB-IoT Spec:**
67	67
68		- -40°C to +85°C
	86	+* - B1 @H-FDD: 2100MHz
	87	+* - B3 @H-FDD: 1800MHz
	88	+* - B8 @H-FDD: 900MHz
	89	+* - B5 @H-FDD: 850MHz
	90	+* - B20 @H-FDD: 800MHz
	91	+* - B28 @H-FDD: 700MHz
69	69
	93	+== 1.4  Installation ==
70	70
	95	+
	96	+Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
	97	+
	98	+[[image:image-20221021110329-1.png]]
	99	+
	100	+
	101	+[[image:image-20221022234602-2.png||height="288" width="922"]]
	102	+
	103	+
	104	+
71	71	== 1.5 ​ Applications ==
72	72
73	73
74		-* Horizontal distance measurement
75		-* Liquid level measurement
76		-* Parking management system
77		-* Object proximity and presence detection
78		-* Intelligent trash can management system
79		-* Robot obstacle avoidance
80		-* Automatic control
81		-* Sewer
82		-* Bottom water level monitoring
	108	+* Open/Close Detection
	109	+* Pulse meter application
	110	+* Dry Contact Detection
83	83
84		-== 1.6  Specification ==
	112	+== 1.6  Mechanical ==
85	85
86	86
87		-(% style="color:blue" %)**Common DC Characteristics:**
	115	+​[[image:image-20221021110415-3.png]]
88	88
89		-* Supply Voltage: 2.1v ~~ 3.6v
90		-* Operating Temperature: 0 ~~ 70°C
91	91
92		-(% style="color:blue" %)**NB-IoT Spec:**
93	93
94		-* B1 @H-FDD: 2100MHz
95		-* B3 @H-FDD: 1800MHz
96		-* B8 @H-FDD: 900MHz
97		-* B5 @H-FDD: 850MHz
98		-* B20 @H-FDD: 800MHz
99		-* B28 @H-FDD: 700MHz
	119	+== 1.7  Pin Definitions and Switch ==
100	100
101		-== 1.7  Installation ==
102	102
	122	+[[image:image-20221021110429-4.png]]
103	103
104		-Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
105	105
	125	+=== 1.7.1  Pin Definition ===
106	106
107		-[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
108	108
	128	+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]]**.
109	109
110	110
111		-== 1.8  Pin Definitions and Switch ==
112	112
	132	+=== 1.7.2  Jumper JP2(Power ON/OFF) ===
113	113
114		-[[image:1670404362039-351.png]]
115	115
	135	+Power on Device when putting this jumper.
116	116
117		-= 2.  Use NMDS200 to communicate with IoT Server =
118	118
	138	+
	139	+=== 1.7.3  BOOT MODE / SW1 ===
	140	+
	141	+
	142	+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.
	143	+
	144	+2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
	145	+
	146	+
	147	+
	148	+=== 1.7.4  Reset Button ===
	149	+
	150	+
	151	+Press to reboot the device.
	152	+
	153	+
	154	+
	155	+=== 1.7.5  LED ===
	156	+
	157	+
	158	+The LED will blink when :
	159	+
	160	+1.  Boot the device in flash mode
	161	+
	162	+2.  Send an uplink packet
	163	+
	164	+
	165	+
	166	+= 2.  Use CPN01 to communicate with IoT Server =
	167	+
	168	+
119	119	== 2.1  How it works ==
120	120
121	121
122		-The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
	172	+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.
123	123
124		-The diagram below shows the working flow in the default firmware of NMDS200:
	174	+The diagram below shows the working flow in the default firmware of CPN01:
125	125
126	126	[[image:image-20221021110615-5.png]]
127	127
128	128
129		-== 2.2 ​ Configure NMDS200 ==
130	130
	180	+== 2.2 ​ Configure CPN01 ==
131	131
132		-To use NMDS200 in your city, make sure to meet below requirements:
133	133
	183	+=== 2.2.1 Test Requirement ===
	184	+
	185	+
	186	+To use CPN01 in your city, make sure to meet below requirements:
	187	+
134	134	* Your local operator has already distributed an NB-IoT Network.
135		-* The local NB-IoT network used the band that NMDS200 supports.
	189	+* The local NB-IoT network used the band that CPN01 supports.
136	136	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
137	137
138		-Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NMDS200 will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
	192	+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.
139	139
140		-[[image:image-20221208090742-1.png]]
	194	+[[image:image-20221023000439-3.png]]
141	141
	196	+ ​
142	142
143		-=== 2.2.1 Insert NB-IoT SIM card ===
144	144
	199	+=== 2.2.2 Insert NB-IoT SIM card ===
145	145
	201	+
146	146	Insert the NB-IoT Card get from your provider.
147	147
148	148	User needs to take out the NB-IoT module and insert the SIM card like below:
...	...	@@ -150,11 +150,12 @@
150	150	[[image:image-20221021110745-6.png]] ​
151	151
152	152
153		-=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
154	154
	210	+=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
155	155
156		-User need to configure NMDS200 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NMDS200 support AT Commands, user can use a USB to TTL adapter to connect to NMDS200 and use AT Commands to configure it, as below.
157	157
	213	+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.
	214	+
158	158	(% style="color:blue" %)**Connection:**
159	159
160	160	(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
...	...	@@ -176,11 +176,11 @@
176	176
177	177	* Flow Control: (% style="color:red" %)**None**
178	178
179		-Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
	236	+Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
180	180
181	181	​[[image:image-20221021110817-7.png]]
182	182
183		-NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
	240	+CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
184	184
185	185
186	186	(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
...	...	@@ -187,13 +187,13 @@
187	187
188	188
189	189
190		-=== 2.2.3 Use CoAP protocol to uplink data ===
	247	+=== 2.2.4 Use CoAP protocol to uplink data ===
191	191
192	192
193	193	(% style="color:red" %)**Note: if you don't have a CoAP server, you can refer this link to set up a CoAP server: **(%%)[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
194	194
195	195
196		-(% style="color:blue" %)**Use below commands in NMDS200:**
	253	+(% style="color:blue" %)**Use below commands in CPN01:**
197	197
198	198	* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
199	199
...	...	@@ -206,14 +206,15 @@
206	206	[[image:image-20221021110948-8.png]]
207	207
208	208
209		-After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server.
	266	+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.
210	210
211		-[[image:1670405841875-916.png]] ​
	268	+[[image:image-20221021110956-9.png]] ​
212	212
213	213
214		-=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
215	215
	272	+=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
216	216
	274	+
217	217	(% style="color:blue" %)**AT Commands:**
218	218
219	219	* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
...	...	@@ -229,9 +229,10 @@
229	229
230	230	​
231	231
232		-=== 2.2.5 Use MQTT protocol to uplink data ===
233	233
	291	+=== 2.2.6 Use MQTT protocol to uplink data ===
234	234
	293	+
235	235	(% style="color:blue" %)**AT Commands:**
236	236
237	237	* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
...	...	@@ -248,10 +248,10 @@
248	248
249	249	* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
250	250
251		-​ [[image:image-20221118103445-7.png]]
	310	+​ [[image:image-20221021111058-12.png]]
252	252
253	253
254		-[[image:1670405928926-116.png]]
	313	+[[image:image-20221021111201-16.png||height="472" width="653"]]
255	255
256	256	​
257	257
...	...	@@ -258,9 +258,10 @@
258	258	MQTT protocol has a much higher power consumption compare with UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
259	259
260	260
261		-=== 2.2.6 Use TCP protocol to uplink data ===
262	262
	321	+=== 2.2.7 Use TCP protocol to uplink data ===
263	263
	323	+
264	264	(% style="color:blue" %)**AT Commands:**
265	265
266	266	* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
...	...	@@ -267,75 +267,82 @@
267	267
268	268	* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
269	269
270		-​ [[image:1670406036256-101.png||height="676" width="713"]]
	330	+​ [[image:image-20221021111125-14.png]]
271	271
272		-
273	273	[[image:image-20221021111131-15.png]]
274	274
275	275	​
276	276
277		-=== 2.2.7 Change Update Interval ===
278	278
	337	+=== 2.2.8 Change Update Interval ===
279	279
	339	+
280	280	User can use below command to change the (% style="color:blue" %)**uplink interval**.
281	281
282		-* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
	342	+* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
283	283
284	284	(% style="color:red" %)**NOTE:**
285	285
286		-1.  By default, the device will send an uplink message every 4 hour.
	346	+1.  By default, the device will send an uplink message every 1 hour.
287	287
288	288
	349	+
289	289	== 2.3  Uplink Payload ==
290	290
291	291
292		-The uplink payload includes 23 bytes in total by default.
	353	+The uplink payload includes 123 bytes in total by default.
293	293
294		-Each time the device uploads a data package. The user can use the AT+NOUD command to upload the recorded data.Up to 32 sets of recorded data can be uploaded.
	355	+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.
295	295
296	296
297		-(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
298		-|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:90px" %)**2**|(% style="width:100px" %)**2**
299		-|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) [[Distance 1>>||anchor="H2.4.5A0Distance"]] |(% style="width:93px" %) [[Distance  2>>||anchor="H2.4.5A0Distance"]]
	358	+(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
	359	+|=(% 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**
	360	+|=(% 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"]]
300	300
301		-(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
302		-|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
303		-**1-32 group**
304		-)))
305		-|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
	362	+(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
	363	+|(% 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**
	364	+|(% 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" %)...
306	306
307		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
	366	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
308	308
309		-[[image:1670406261143-723.png]]
	368	+[[image:image-20221021111201-16.png||height="572" width="792"]]
310	310
311	311
312		-The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
	371	+The payload is ASCII string, representative same HEX:
313	313
314		-**0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
	373	+**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 __**
315	315
316	316	**where:**
317	317
318		-* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
	377	+* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
319	319
320		-* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
	379	+* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
321	321
322		-* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
	381	+* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
323	323
324		-* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
	383	+* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
325	325
326		-* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
	385	+* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
327	327
328		-* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
	387	+* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
329	329
330		-* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
	389	+* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
331	331
332		-* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
	391	+* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
333	333
334		-* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
	393	+* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
335	335
	395	+* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
336	336
	397	+* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
	398	+
	399	+* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
	400	+
	401	+* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
	402	+
337	337	== 2.4  Payload Explanation and Sensor Interface ==
338	338
	405	+
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
	420	+
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.
	426	+For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
359	359
360	360
	429	+
361	361	=== 2.4.3  Battery Info ===
362	362
363	363
364		-Check the battery voltage for NMDS200.
	433	+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
	440	+
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**
	446	+**Ex1: 0x1d = 29**
377	377
378		-(% style="color:#037691" %)**0** (%%) -113dBm or less
	448	+**0**  -113dBm or less
379	379
380		-(% style="color:#037691" %)**1**  (%%) -111dBm
	450	+**1**  -111dBm
381	381
382		-(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
	452	+**2...30** -109dBm... -53dBm
383	383
384		-(% style="color:#037691" %)**31** (%%) -51dBm or greater
	454	+**31**   -51dBm or greater
385	385
386		-(% style="color:#037691" %)**99** (%%) Not known or not detectable
	456	+**99**    Not known or not detectable
387	387
388	388
389		-=== 2.4.5  Distance ===
390	390
	460	+=== 2.4.5  Calculate Flag ===
391	391
392		-[[image:1670407401682-959.png]]
393	393
	463	+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:**
	465	+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)
	467	+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
	469	+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:**
	473	+=== 2.4.6  Alarm ===
405	405
406		-Distance between sensor probe to the second object. (unit: cm)
407	407
	476	+See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
408	408
409		-=== 2.4.6  Timestamp ===
410	410
411	411
	480	+=== 2.4.7  Contact Status ===
	481	+
	482	+
	483	+0: Open
	484	+
	485	+1: Close
	486	+
	487	+
	488	+
	489	+=== 2.4.8  Total pulse ===
	490	+
	491	+
	492	+Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
	493	+
	494	+Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
	495	+
	496	+
	497	+
	498	+=== 2.4.9  The last open duration ===
	499	+
	500	+
	501	+Dry Contact last open duration.
	502	+
	503	+Unit: min.
	504	+
	505	+[[image:image-20221021111346-17.png||height="146" width="770"]]
	506	+
	507	+
	508	+
	509	+=== 2.4.10  Timestamp ===
	510	+
	511	+
412	412	Timestamp : 0x6315537b =1662342011
413	413
	514	+Convert Unix timestamp to time 2022-9-5 9:40:11.
414	414
	516	+**~ **
	517	+
	518	+
415	415	== 2.5  Downlink Payload ==
416	416
417	417
418		-By default, NMDS200 prints the downlink payload to console port.
	522	+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
	539	+If payload = 0x04FF, it will reset the NSE01
436	436
437	437	* (% style="color:#037691" %)**INTMOD**
438	438
...	...	@@ -439,47 +439,115 @@
439	439	Downlink Payload: 06000003, Set AT+INTMOD=3
440	440
441	441
	546	+
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.
	550	+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.
	553	+* 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
	556	+== 2.7  Alarm Base on Timeout ==
451	451
452	452
453		-== 2.7  Distance alarm function ==
	559	+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**
	562	+(% style="color:blue" %)**1. Keep Status: Status to be monitor**
457	457
458		-(% style="color:#037691" %)**Example 1:**
	564	+Keep Status = 1: Monitor Close to Open event
459	459
460		-AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
	566	+Keep Status = 0: Monitor Open to Close event
461	461
462		-AT+ ALARM2 =min,max
463	463
	569	+(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
464	464
465		-(% style="color:#037691" %)**Example 2:**
	571	+Range 0 ~~ 65535(0xFFFF) seconds.
466	466
467		-AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
	573	+If keep time = 0, Disable Alarm Base on Timeout feature.
468	468
	575	+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		-== 2.8  Set the number of data to be uploaded and the recording time ==
471	471
	578	+(% style="color:blue" %)**AT Command to configure:**
472	472
	580	+(% 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.
	581	+
	582	+(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
	583	+
	584	+
	585	+
	586	+== 2.8  Set debug mode ==
	587	+
	588	+
	589	+Feature: Enable or Disable debug mode
	590	+
	591	+(% style="color:blue" %)**AT Command: AT+DEBUG**
	592	+
	593	+[[image:image-20221021111629-21.png]]
	594	+
	595	+
	596	+
	597	+== 2.9  Clear Flash Record ==
	598	+
	599	+
	600	+Feature: Clear flash storage for data log feature.
	601	+
	602	+(% style="color:blue" %)**AT Command: AT+CLRDTA**
	603	+
	604	+[[image:image-20221021111527-19.png]]
	605	+
	606	+
	607	+
	608	+== 2.10  Set trigger mode ==
	609	+
	610	+
	611	+(% style="color:blue" %)**AT Command: AT+TTRMOD**
	612	+
	613	+Feature: Set the trigger interrupt mode.
	614	+
	615	+[[image:image-20221021111552-20.png]]
	616	+
	617	+
	618	+
	619	+== 2.11  Set the calculate flag ==
	620	+
	621	+
	622	+Feature: Set the calculate flag
	623	+
	624	+(% style="color:blue" %)**AT Command: AT+CALCFLAG**
	625	+
	626	+[[image:image-20221021111711-22.png]]
	627	+
	628	+
	629	+
	630	+== 2.12 Set count number ==
	631	+
	632	+
	633	+Feature: Manually set the count number
	634	+
	635	+(% style="color:blue" %)**AT Command: AT+SETCNT**
	636	+
	637	+[[image:image-20221021111748-24.png]]
	638	+
	639	+
	640	+
	641	+== 2.13  Set the number of data to be uploaded and the recording time ==
	642	+
	643	+
473	473	(% style="color:blue" %)**AT Command:**
474	474
475		-(% 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)
	646	+(% 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)
476	476
477		-(% 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.
	648	+(% 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.
478	478
479	479
480		-== 2.9  Read or Clear cached data ==
481	481
	652	+== 2.14  Read or Clear cached data ==
482	482
	654	+
483	483	(% style="color:blue" %)**AT Command:**
484	484
485	485	(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
...	...	@@ -486,24 +486,27 @@
486	486
487	487	(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
488	488
489		-[[image:1670408172929-569.png]]
	661	+[[image:image-20221021111810-25.png||height="364" width="797"]]
490	490
491	491
492		-== 2.10  ​Firmware Change Log ==
493	493
	665	+== 2.15  ​Firmware Change Log ==
494	494
495		-Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
496	496
	668	+Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
	669	+
497	497	Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
498	498
499	499
500		-== 2.11  ​Battery Analysis ==
501	501
502		-=== 2.11.1  ​Battery Type ===
	674	+== 2.16  ​Battery Analysis ==
503	503
504	504
505		-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.
	677	+=== 2.16.1  ​Battery Type ===
506	506
	679	+
	680	+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.
	681	+
507	507	The battery is designed to last for several years depends on the actual use environment and update interval.
508	508
509	509	The battery-related documents as below:
...	...	@@ -517,9 +517,10 @@
517	517	[[image:image-20221021111911-26.png]] ​
518	518
519	519
520		-=== 2.11.2  Power consumption Analyze ===
521	521
	696	+=== 2.16.2  Power consumption Analyze ===
522	522
	698	+
523	523	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.
524	524
525	525	Instruction to use as below:
...	...	@@ -539,18 +539,21 @@
539	539	[[image:1666596205057-567.png]] ​
540	540
541	541
542		-=== 2.11.3  ​Battery Note ===
543	543
	719	+=== 2.16.3  ​Battery Note ===
544	544
	721	+
545	545	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.
546	546
547	547
548		-=== 2.11.4  Replace the battery ===
549	549
	726	+=== 2.16.4  Replace the battery ===
550	550
551		-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).
552	552
	729	+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).
553	553
	731	+
	732	+
554	554	= 3. ​ Access NB-IoT Module =
555	555
556	556
...	...	@@ -558,12 +558,13 @@
558	558
559	559	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/]]
560	560
	740	+[[image:image-20221021112006-28.png]] ​
561	561
562		-[[image:image-20221118094449-6.png]] ​
563	563
564	564
565	565	= 4.  Using the AT Commands =
566	566
	746	+
567	567	== 4.1  Access AT Commands ==
568	568
569	569
...	...	@@ -602,55 +602,57 @@
602	602
603	603	AT+SERVADDR  : Server Address
604	604
605		-AT+TR      :  Get or Set record time
	785	+AT+TR      :  Get or Set record time
606	606
607		-AT+NOUD :  Get or Set the number of data to be uploaded
	787	+AT+NOUD      : Get or Set the number of data to be uploaded
608	608
609	609	AT+CDP     :  Read or Clear cached data
610	610
611		-AT+DEBUG:  Enable or Disable debug mode
	791	+AT+ DEBUG   : Enable or Disable debug mode
612	612
613		-AT+ALARM1:  Get or Set alarm of distance1
	793	+AT+ TTRIG   : Get or Set Alarm Base on Timeout
614	614
615		-AT+ALARM2:  Get or Set alarm of distance2
	795	+AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
616	616
617		-AT+GETSENSORVALUE :  Returns the current sensor measurement
	797	+AT+ CALCFLAG   : Get or Set the calculate flag
618	618
619		-AT+POWERIC :  Get or set the Power IC flag
	799	+AT+ CLRC   : Clear current door open count
620	620
621	621
622	622	(% style="color:blue" %)**COAP Management**
623	623
624		-AT+URI :  Resource parameters
	804	+AT+URI            : Resource parameters
625	625
626	626
627	627	(% style="color:blue" %)**UDP Management**
628	628
629		-AT+CFM :  Upload confirmation mode (only valid for UDP)
	809	+AT+CFM          : Upload confirmation mode (only valid for UDP)
630	630
631	631
632	632	(% style="color:blue" %)**MQTT Management**
633	633
634		-AT+CLIENT  : Get or Set MQTT client
	814	+AT+CLIENT               : Get or Set MQTT client
635	635
636		-AT+UNAME : Get or Set MQTT Username
	816	+AT+UNAME  : Get or Set MQTT Username
637	637
638		-AT+PWD  :  Get or Set MQTT password
	818	+AT+PWD                  : Get or Set MQTT password
639	639
640		-AT+PUBTOPIC :  Get or Set MQTT publish topic
	820	+AT+PUBTOPIC  : Get or Set MQTT publish topic
641	641
642		-AT+SUBTOPIC :  Get or Set MQTT subscription topic
	822	+AT+SUBTOPIC  : Get or Set MQTT subscription topic
643	643
644	644
645	645	(% style="color:blue" %)**Information**
646	646
647		-AT+FDR :  Factory Data Reset
	827	+AT+FDR  : Factory Data Reset
648	648
649		-AT+PWORD :  Serial Access Password
	829	+AT+PWORD  : Serial Access Password
650	650
651	651
	832	+
652	652	= ​5.  FAQ =
653	653
	835	+
654	654	== 5.1 ​ How to Upgrade Firmware ==
655	655
656	656
...	...	@@ -658,11 +658,13 @@
658	658
659	659	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]]
660	660
661		-(% 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.**
	843	+(% 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.**
662	662
663	663
	846	+
664	664	= 6.  Trouble Shooting =
665	665
	849	+
666	666	== 6.1  ​Connection problem when uploading firmware ==
667	667
668	668
...	...	@@ -669,6 +669,7 @@
669	669	(% 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]]
670	670
671	671
	856	+
672	672	== 6.2  AT Command input doesn't work ==
673	673
674	674
...	...	@@ -675,19 +675,27 @@
675	675	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.
676	676
677	677
	863	+
678	678	= 7. ​ Order Info =
679	679
680	680
681		-Part Number:(% style="color:blue" %)** NMDS200**
	867	+Part Number**:** CPN01
682	682
683	683
	870	+
684	684	= 8.  Packing Info =
685	685
686	686
687	687	(% style="color:blue" %)**Package Includes**:
688	688
689		-* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
	876	+* CPN01 Open/Close Sensor x 1
	877	+* External antenna x 1
690	690
	879	+(% style="color:blue" %)**Dimension and weight**:
	880	+
	881	+* Size: 195 x 125 x 55 mm
	882	+* Weight:   420g
	883	+
691	691	= 9.  Support =
692	692
693	693

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-20221117114842-3.png

Author

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

Size

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

Content

image-20221117114937-4.png

Author

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

Size

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

Content

image-20221117114949-5.png

Author

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

Size

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

Content

image-20221117115010-6.png

Author

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

Size

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

Content

image-20221117142300-1.png

Author

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

Size

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

Content

image-20221117145932-2.png

Author

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

Size

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

Content

image-20221117150312-3.png

Author

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

Size

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

Content

image-20221118092935-1.png

Author

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

Size

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

Content

image-20221118093144-2.png

Author

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

Size

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

Content

image-20221118093512-3.png

Author

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

Size

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

Content

image-20221118093658-4.png

Author

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

Size

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

Content

image-20221118094227-5.png

Author

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

Size

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

Content

image-20221118094449-6.png

Author

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

Size

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

Content

image-20221118103445-7.png

Author

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

Size

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

Content

image-20221118103453-8.png

Author

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

Size

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

Content

image-20221118103547-9.png

Author

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

Size

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

Content

image-20221207170748-1.png

Author

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

Size

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

Content

image-20221207170748-2.png

Author

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

Size

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

Content

image-20221207173200-3.png

Author

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

Size

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

Content

image-20221207173300-4.png

Author

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

Size

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

Content

image-20221208090742-1.png

Author

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

Size

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

Content