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
  • LMDS200_10.jpg
  • image-20221117105556-1.png
  • image-20221117114459-2.png
  • 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

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,37 +1,46 @@
1	1	(% style="text-align:center" %)
2		-[[image:LMDS200_10.jpg]]
	2	+[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/WebHome/1652856952171-363.png?rev=1.1||alt="1652856952171-363.png" height="578" width="588"]]
3	3
4	4
	5	+
5	5	**Table of Contents：**
6	6
	8	+{{toc/}}
7	7
8	8
9	9
10	10
	13	+
11	11	= 1.  Introduction =
12	12
13		-== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
14	14
	17	+== 1.1 ​ What is CPN01 NB-IoT Pulse/Contact Sensor ==
15	15
	19	+
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.
	21	+The Dragino CPN01 is an (% style="color:blue" %)**NB-IoT Dry Contact Sensor**(%%). It detects open/close status and uplinks the info to IoT server via NB-IoT network. User can see the (% style="color:blue" %)**dry contact status, open time, and open counts**(%%) in the IoT Server.
	22	+)))
18	18
	24	+(((
	25	+The CPN01 will send periodically data every day as well as for each dry contact action. It also counts the contact open times and calculates the last open duration. Users can also disable the uplink for each Open/Close event, instead, device can count each open event and uplink periodically.
	26	+)))
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.
	28	+(((
	29	+CPN01 has** (% style="color:blue" %)Open-Alarm feature(%%)**, user can set this feature so CPN01 will send an alarm if the contact has been open exceeds a certain time.
	30	+)))
21	21
22		-NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
	32	+(((
	33	+CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures.
	34	+)))
23	23
24		-NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range.
25		-
26		-NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technology**(%%) developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
27		-
28		-NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
29		-
30		-NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
31		-
32		-To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection.
	36	+(((
	37	+NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
	38	+\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
	39	+\\CPN01 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
	40	+\\To use CPN01, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that CPN01 supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into CPN01 to get NB-IoT network connection.
33	33	)))
34	34
	43	+​
35	35
36	36
37	37	== ​1.2  Features ==
...	...	@@ -38,9 +38,10 @@
38	38
39	39
40	40	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
41		-* Short uplink interval for Distance Alarm
	50	+* Open/Close detect
	51	+* Open/Close statistics
42	42	* Monitor Battery Level
43		-* Microwave Radar for distance detection
	53	+* Uplink on periodically and open/close event
44	44	* Datalog feature
45	45	* Uplink periodically
46	46	* Downlink to change configure
...	...	@@ -52,107 +52,137 @@
52	52	* 8500mAh Battery for long-term use
53	53
54	54
55		-== 1.3 Radar probe specification ==
56	56
	66	+== 1.3  Specification ==
57	57
58		-* Measuring Method: FMCW
59		-* Frequency: 24.000 24.500 GHz
60		-* Measurement output power: 6dBm
61		-* Measure range: 0.5 20m
62		-* Accuracy: ±0.1m
63		-* Resolution: 0.01m
64		-* Horizontal Angel: 78°
65		-* Vertical Angel: 23°
66	66
	69	+(% style="color:blue" %)**Common DC Characteristics:**
67	67
	71	+* Supply Voltage: 2.1v ~~ 3.6v
	72	+* Operating Temperature: -40 ~~ 85°C
68	68
69		-== 1.4  Storage Temperature ==
	74	+(% style="color:blue" %)**NB-IoT Spec:**
70	70
	76	+* - B1 @H-FDD: 2100MHz
	77	+* - B3 @H-FDD: 1800MHz
	78	+* - B8 @H-FDD: 900MHz
	79	+* - B5 @H-FDD: 850MHz
	80	+* - B20 @H-FDD: 800MHz
	81	+* - B28 @H-FDD: 700MHz
71	71
72		- -40°C to +85°C
73	73
74	74
	85	+== 1.4  Installation ==
75	75
76	76
	88	+Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
77	77
	90	+[[image:image-20221021110329-1.png]]
	91	+
	92	+
	93	+[[image:image-20221022234602-2.png||height="288" width="922"]]
	94	+
	95	+
	96	+
78	78	== 1.5 ​ Applications ==
79	79
80	80
	100	+* Open/Close Detection
	101	+* Pulse meter application
	102	+* Dry Contact Detection
81	81
82		-* Horizontal distance measurement
83		-* Liquid level measurement
84		-* Parking management system
85		-* Object proximity and presence detection
86		-* Intelligent trash can management system
87		-* Robot obstacle avoidance
88		-* Automatic control
89		-* Sewer
90		-* Bottom water level monitoring
91	91
92	92
93		-== 1.6  Specification ==
	106	+== 1.6  Mechanical ==
94	94
95	95
96		-(% style="color:blue" %)**Common DC Characteristics:**
	109	+​[[image:image-20221021110415-3.png]]
97	97
98		-* Supply Voltage: 2.1v ~~ 3.6v
99		-* Operating Temperature: 0 ~~ 70°C
100	100
101		-(% style="color:blue" %)**NB-IoT Spec:**
102	102
103		-* B1 @H-FDD: 2100MHz
104		-* B3 @H-FDD: 1800MHz
105		-* B8 @H-FDD: 900MHz
106		-* B5 @H-FDD: 850MHz
107		-* B20 @H-FDD: 800MHz
108		-* B28 @H-FDD: 700MHz
	113	+== 1.7  Pin Definitions and Switch ==
109	109
110	110
111		-== 1.7  Installation ==
	116	+[[image:image-20221021110429-4.png]]
112	112
113	113
114		-Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
	119	+=== 1.7.1  Pin Definition ===
115	115
116	116
117		-[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
	122	+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]]**.
118	118
119	119
120	120
121		-== 1.8  Pin Definitions and Switch ==
	126	+=== 1.7.2  Jumper JP2(Power ON/OFF) ===
122	122
123	123
124		-[[image:1670404362039-351.png]]
	129	+Power on Device when putting this jumper.
125	125
126	126
127		-= 2.  Use NMDS200 to communicate with IoT Server =
128	128
	133	+=== 1.7.3  BOOT MODE / SW1 ===
	134	+
	135	+
	136	+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.
	137	+
	138	+2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
	139	+
	140	+
	141	+
	142	+=== 1.7.4  Reset Button ===
	143	+
	144	+
	145	+Press to reboot the device.
	146	+
	147	+
	148	+
	149	+=== 1.7.5  LED ===
	150	+
	151	+
	152	+The LED will blink when :
	153	+
	154	+1.  Boot the device in flash mode
	155	+
	156	+2.  Send an uplink packet
	157	+
	158	+
	159	+
	160	+= 2.  Use CPN01 to communicate with IoT Server =
	161	+
	162	+
129	129	== 2.1  How it works ==
130	130
131	131
132		-The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
	166	+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.
133	133
134		-The diagram below shows the working flow in the default firmware of NMDS200:
	168	+The diagram below shows the working flow in the default firmware of CPN01:
135	135
136	136	[[image:image-20221021110615-5.png]]
137	137
138	138
139		-== 2.2 ​ Configure NMDS200 ==
140	140
	174	+== 2.2 ​ Configure CPN01 ==
141	141
142		-To use NMDS200 in your city, make sure to meet below requirements:
143	143
	177	+=== 2.2.1 Test Requirement ===
	178	+
	179	+
	180	+To use CPN01 in your city, make sure to meet below requirements:
	181	+
144	144	* Your local operator has already distributed an NB-IoT Network.
145		-* The local NB-IoT network used the band that NMDS200 supports.
	183	+* The local NB-IoT network used the band that CPN01 supports.
146	146	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
147	147
148		-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.
	186	+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.
149	149
150		-[[image:image-20221207173300-4.png]]
	188	+[[image:image-20221023000439-3.png]]
151	151
	190	+ ​
152	152
153		-=== 2.2.1 Insert NB-IoT SIM card ===
154	154
	193	+=== 2.2.2 Insert NB-IoT SIM card ===
155	155
	195	+
156	156	Insert the NB-IoT Card get from your provider.
157	157
158	158	User needs to take out the NB-IoT module and insert the SIM card like below:
...	...	@@ -160,11 +160,12 @@
160	160	[[image:image-20221021110745-6.png]] ​
161	161
162	162
163		-=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
164	164
	204	+=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
165	165
166		-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.
167	167
	207	+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.
	208	+
168	168	(% style="color:blue" %)**Connection:**
169	169
170	170	(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
...	...	@@ -186,11 +186,11 @@
186	186
187	187	* Flow Control: (% style="color:red" %)**None**
188	188
189		-Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
	230	+Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
190	190
191	191	​[[image:image-20221021110817-7.png]]
192	192
193		-NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
	234	+CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
194	194
195	195
196	196	(% 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]]
...	...	@@ -197,13 +197,13 @@
197	197
198	198
199	199
200		-=== 2.2.3 Use CoAP protocol to uplink data ===
	241	+=== 2.2.4 Use CoAP protocol to uplink data ===
201	201
202	202
203	203	(% 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/]]
204	204
205	205
206		-(% style="color:blue" %)**Use below commands in NDS03A:**
	247	+(% style="color:blue" %)**Use below commands in CPN01:**
207	207
208	208	* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
209	209
...	...	@@ -216,14 +216,15 @@
216	216	[[image:image-20221021110948-8.png]]
217	217
218	218
219		-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.
	260	+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.
220	220
221		-[[image:1670405841875-916.png]] ​
	262	+[[image:image-20221021110956-9.png]] ​
222	222
223	223
224		-=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
225	225
	266	+=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
226	226
	268	+
227	227	(% style="color:blue" %)**AT Commands:**
228	228
229	229	* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
...	...	@@ -239,9 +239,10 @@
239	239
240	240	​
241	241
242		-=== 2.2.5 Use MQTT protocol to uplink data ===
243	243
	285	+=== 2.2.6 Use MQTT protocol to uplink data ===
244	244
	287	+
245	245	(% style="color:blue" %)**AT Commands:**
246	246
247	247	* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
...	...	@@ -258,10 +258,10 @@
258	258
259	259	* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
260	260
261		-​ [[image:image-20221118103445-7.png]]
	304	+​ [[image:image-20221021111058-12.png]]
262	262
263	263
264		-[[image:1670405928926-116.png]]
	307	+[[image:image-20221021111201-16.png||height="472" width="653"]]
265	265
266	266	​
267	267
...	...	@@ -268,9 +268,10 @@
268	268	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.
269	269
270	270
271		-=== 2.2.6 Use TCP protocol to uplink data ===
272	272
	315	+=== 2.2.7 Use TCP protocol to uplink data ===
273	273
	317	+
274	274	(% style="color:blue" %)**AT Commands:**
275	275
276	276	* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
...	...	@@ -277,76 +277,83 @@
277	277
278	278	* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
279	279
280		-​ [[image:1670406036256-101.png||height="676" width="713"]]
	324	+​ [[image:image-20221021111125-14.png]]
281	281
282		-
283	283	[[image:image-20221021111131-15.png]]
284	284
285	285	​
286	286
287		-=== 2.2.7 Change Update Interval ===
288	288
	331	+=== 2.2.8 Change Update Interval ===
289	289
	333	+
290	290	User can use below command to change the (% style="color:blue" %)**uplink interval**.
291	291
292		-* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
	336	+* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
293	293
294	294	(% style="color:red" %)**NOTE:**
295	295
296		-1.  By default, the device will send an uplink message every 4 hour.
	340	+1.  By default, the device will send an uplink message every 1 hour.
297	297
298	298
	343	+
299	299	== 2.3  Uplink Payload ==
300	300
301	301
302		-The uplink payload includes 23 bytes in total by default.
	347	+The uplink payload includes 123 bytes in total by default.
303	303
304		-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.
	349	+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.
305	305
306	306
307		-(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
308		-|=(% 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**
309		-|=(% 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 |(% style="width:93px" %) Distance  2
	352	+(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
	353	+|=(% 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**
	354	+|=(% 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"]]
310	310
311		-(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
312		-|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
313		-**1-32 group**
314		-)))
315		-|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
	356	+(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
	357	+|(% 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**
	358	+|(% 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" %)...
316	316
317		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
	360	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
318	318
319		-[[image:1670406261143-723.png]]
	362	+[[image:image-20221021111201-16.png||height="572" width="792"]]
320	320
321	321
322		-The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
	365	+The payload is ASCII string, representative same HEX:
323	323
324		-**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__(%%)**
	367	+**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 __**
325	325
326	326	**where:**
327	327
328		-* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
	371	+* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
329	329
330		-* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
	373	+* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
331	331
332		-* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
	375	+* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
333	333
334		-* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
	377	+* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
335	335
336		-* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
	379	+* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
337	337
338		-* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
	381	+* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
339	339
340		-* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
	383	+* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
341	341
342		-* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
	385	+* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
343	343
344		-* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
	387	+* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
345	345
	389	+* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
346	346
	391	+* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
347	347
	393	+* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
	394	+
	395	+* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
	396	+
	397	+
348	348	== 2.4  Payload Explanation and Sensor Interface ==
349	349
	400	+
350	350	=== 2.4.1  Device ID ===
351	351
352	352
...	...	@@ -361,18 +361,20 @@
361	361	The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
362	362
363	363
	415	+
364	364	=== 2.4.2  Version Info ===
365	365
366	366
367	367	Specify the software version: 0x64=100, which means firmware version 1.00.
368	368
369		-For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
	421	+For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
370	370
371	371
	424	+
372	372	=== 2.4.3  Battery Info ===
373	373
374	374
375		-Check the battery voltage for NDS03A.
	428	+Check the battery voltage for CPN01.
376	376
377	377	Ex1: 0x0B45 = 2885mV
378	378
...	...	@@ -379,6 +379,7 @@
379	379	Ex2: 0x0B49 = 2889mV
380	380
381	381
	435	+
382	382	=== 2.4.4  Signal Strength ===
383	383
384	384
...	...	@@ -397,38 +397,70 @@
397	397	**99**    Not known or not detectable
398	398
399	399
400		-=== 2.4.5  Disalarm: (default: 0) ===
401	401
	455	+=== 2.4.5  Calculate Flag ===
402	402
403		-(% style="color:blue" %)**If Disalarm = 1**(%%), NDS03A will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many open/close event, and platform only care about the total number of pulse.
404	404
405		-(% style="color:blue" %)**If Disalarm = 0**(%%), NDS03A will send uplink at every TDC periodically and send data on each open/close event. This is useful for the application user need to monitor the open/close event in real-time.
	458	+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.
406	406
407		- (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
	460	+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.
408	408
	462	+Default value: 0.
409	409
410		-=== 2.4.6  Keep Status & Keep Time ===
	464	+Range (6 bits): (b)000000 ~~ (b) 111111
411	411
412	412
413		-Shows the configure value of Alarm Base on Timeout Feature
414	414
	468	+=== 2.4.6  Alarm ===
415	415
416		-=== 2.4.7  Timestamp ===
417	417
	471	+See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
418	418
419		-Timestamp : 0x6315537b =1662342011
420	420
421	421
422		-=== 2.4.8  Switch Dual Channel Mode ===
	475	+=== 2.4.7  Contact Status ===
423	423
424	424
425		-NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
	478	+0: Open
426	426
	480	+1: Close
427	427
	482	+
	483	+
	484	+=== 2.4.8  Total pulse ===
	485	+
	486	+
	487	+Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
	488	+
	489	+Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
	490	+
	491	+
	492	+
	493	+=== 2.4.9  The last open duration ===
	494	+
	495	+
	496	+Dry Contact last open duration.
	497	+
	498	+Unit: min.
	499	+
	500	+[[image:image-20221021111346-17.png||height="146" width="770"]]
	501	+
	502	+
	503	+
	504	+=== 2.4.10  Timestamp ===
	505	+
	506	+
	507	+Timestamp : 0x6315537b =1662342011
	508	+
	509	+Convert Unix timestamp to time 2022-9-5 9:40:11.
	510	+
	511	+**~ **
	512	+
	513	+
428	428	== 2.5  Downlink Payload ==
429	429
430	430
431		-By default, NDS03A prints the downlink payload to console port.
	517	+By default, CPN01 prints the downlink payload to console port.
432	432
433	433	[[image:image-20221021111414-18.png]] ​
434	434
...	...	@@ -445,7 +445,7 @@
445	445
446	446	* (% style="color:#037691" %)**Reset**
447	447
448		-If payload = 0x04FF, it will reset the NDS03A
	534	+If payload = 0x04FF, it will reset the NSE01
449	449
450	450	* (% style="color:#037691" %)**INTMOD**
451	451
...	...	@@ -452,19 +452,21 @@
452	452	Downlink Payload: 06000003, Set AT+INTMOD=3
453	453
454	454
	541	+
455	455	== 2.6  ​LED Indicator ==
456	456
457	457
458		-The NDS03A has an internal LED which is to show the status of different states.
	545	+The CPN01 has an internal LED which is to show the status of different states.
459	459
460	460	* When the device starts normally, the LED will light up for 1 second.
461		-* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
	548	+* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
462	462	* For each uplink probe, LED will be on for 500ms.
463	463
	551	+
464	464	== 2.7  Alarm Base on Timeout ==
465	465
466	466
467		-NDS03A 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:
	555	+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:
468	468
469	469
470	470	(% style="color:blue" %)**1. Keep Status: Status to be monitor**
...	...	@@ -480,25 +480,17 @@
480	480
481	481	If keep time = 0, Disable Alarm Base on Timeout feature.
482	482
483		-If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
	571	+If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
484	484
485	485
486	486	(% style="color:blue" %)**AT Command to configure:**
487	487
488		-(% style="color:blue" %)**PB14 PIN:**
	576	+(% 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.
489	489
490		-(% 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. NDS03A 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.
491		-
492	492	(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
493	493
494	494
495		-(% style="color:blue" %)**PB15 PIN:**
496	496
497		-(% style="color:#037691" %)**AT+TTRIG2=1,30**
498		-
499		-(% style="color:#037691" %)**AT+TTRIG2=0,0 **
500		-
501		-
502	502	== 2.8  Set debug mode ==
503	503
504	504
...	...	@@ -520,57 +520,54 @@
520	520	[[image:image-20221021111527-19.png]]
521	521
522	522
523		-== 2.10  Count Mod ==
524	524
	604	+== 2.10  Set trigger mode ==
525	525
526		-(% style="color:blue" %)**AT Command: AT+COUNTMOD**
527	527
528		-[[image:image-20221118092935-1.png]]
	607	+(% style="color:blue" %)**AT Command: AT+TTRMOD**
529	529
	609	+Feature: Set the trigger interrupt mode.
530	530
531		-== 2.11  Interrupt Pin Channel Mod ==
	611	+[[image:image-20221021111552-20.png]]
532	532
533	533
534		-(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
535	535
536		-[[image:image-20221118093144-2.png]]
	615	+== 2.11  Set the calculate flag ==
537	537
538	538
539		-== 2.12 TTRIG1/2 timeout status alarm ==
	618	+Feature: Set the calculate flag
540	540
	620	+(% style="color:blue" %)**AT Command: AT+CALCFLAG**
541	541
542		-It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval.
	622	+[[image:image-20221021111711-22.png]]
543	543
544		-(% style="color:blue" %)**AT Command: AT+TTRALARM**
545	545
546		-[[image:image-20221118093512-3.png]]
547	547
	626	+== 2.12 Set count number ==
548	548
549		-== 2.13  Select counting mode ==
550	550
	629	+Feature: Manually set the count number
551	551
552		-(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
	631	+(% style="color:blue" %)**AT Command: AT+SETCNT**
553	553
554		-When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
	633	+[[image:image-20221021111748-24.png]]
555	555
556		-When (% style="color:red" %)**b=0**(%%), it is the last door open duration, and when (% style="color:red" %)**b=1**(%%),the last door close duration.
557	557
558		-[[image:image-20221118093658-4.png]]
559	559
	637	+== 2.13  Set the number of data to be uploaded and the recording time ==
560	560
561		-== 2.14  Set the number of data to be uploaded and the recording time ==
562	562
563		-
564	564	(% style="color:blue" %)**AT Command:**
565	565
566		-(% 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)
	642	+(% 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)
567	567
568		-(% 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.
	644	+(% 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.
569	569
570	570
571		-== 2.15  Read or Clear cached data ==
572	572
	648	+== 2.14  Read or Clear cached data ==
573	573
	650	+
574	574	(% style="color:blue" %)**AT Command:**
575	575
576	576	(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
...	...	@@ -577,24 +577,27 @@
577	577
578	578	(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
579	579
580		-[[image:image-20221118094227-5.png]]
	657	+[[image:image-20221021111810-25.png||height="364" width="797"]]
581	581
582	582
583		-== 2.16  ​Firmware Change Log ==
584	584
	661	+== 2.15  ​Firmware Change Log ==
585	585
586		-Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
587	587
	664	+Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
	665	+
588	588	Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
589	589
590	590
591		-== 2.17  ​Battery Analysis ==
592	592
593		-=== 2.17.1  ​Battery Type ===
	670	+== 2.16  ​Battery Analysis ==
594	594
595	595
596		-The NDS03A 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.
	673	+=== 2.16.1  ​Battery Type ===
597	597
	675	+
	676	+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.
	677	+
598	598	The battery is designed to last for several years depends on the actual use environment and update interval.
599	599
600	600	The battery-related documents as below:
...	...	@@ -608,9 +608,10 @@
608	608	[[image:image-20221021111911-26.png]] ​
609	609
610	610
611		-=== 2.17.2  Power consumption Analyze ===
612	612
	692	+=== 2.16.2  Power consumption Analyze ===
613	613
	694	+
614	614	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.
615	615
616	616	Instruction to use as below:
...	...	@@ -630,18 +630,21 @@
630	630	[[image:1666596205057-567.png]] ​
631	631
632	632
633		-=== 2.17.3  ​Battery Note ===
634	634
	715	+=== 2.16.3  ​Battery Note ===
635	635
	717	+
636	636	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.
637	637
638	638
639		-=== 2.17.4  Replace the battery ===
640	640
	722	+=== 2.16.4  Replace the battery ===
641	641
642		-The default battery pack of NDS03A 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).
643	643
	725	+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).
644	644
	727	+
	728	+
645	645	= 3. ​ Access NB-IoT Module =
646	646
647	647
...	...	@@ -649,12 +649,13 @@
649	649
650	650	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/]]
651	651
	736	+[[image:image-20221021112006-28.png]] ​
652	652
653		-[[image:image-20221118094449-6.png]] ​
654	654
655	655
656	656	= 4.  Using the AT Commands =
657	657
	742	+
658	658	== 4.1  Access AT Commands ==
659	659
660	660
...	...	@@ -701,21 +701,15 @@
701	701
702	702	AT+ DEBUG   : Enable or Disable debug mode
703	703
704		-AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
	789	+AT+ TTRIG   : Get or Set Alarm Base on Timeout
705	705
706		-AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
	791	+AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
707	707
708		-AT+COUNTMOD  :  Get or Set the count mode
	793	+AT+ CALCFLAG   : Get or Set the calculate flag
709	709
710		-AT+TTRCHANNEL  : Get or Set the number of interrupt channels
	795	+AT+ CLRC   : Clear current door open count
711	711
712		-AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
713	713
714		-AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
715		-
716		-AT+ CLRC   :  Clear current door open count
717		-
718		-
719	719	(% style="color:blue" %)**COAP Management**
720	720
721	721	AT+URI            : Resource parameters
...	...	@@ -746,8 +746,10 @@
746	746	AT+PWORD  : Serial Access Password
747	747
748	748
	828	+
749	749	= ​5.  FAQ =
750	750
	831	+
751	751	== 5.1 ​ How to Upgrade Firmware ==
752	752
753	753
...	...	@@ -755,11 +755,13 @@
755	755
756	756	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]]
757	757
758		-(% style="color:red" %)**Notice: **(% style="color:blue" %)**NDS03A** (%%)**and (% style="color:blue" %)LDS03A(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
	839	+(% 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.**
759	759
760	760
	842	+
761	761	= 6.  Trouble Shooting =
762	762
	845	+
763	763	== 6.1  ​Connection problem when uploading firmware ==
764	764
765	765
...	...	@@ -766,6 +766,7 @@
766	766	(% 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]]
767	767
768	768
	852	+
769	769	== 6.2  AT Command input doesn't work ==
770	770
771	771
...	...	@@ -772,19 +772,29 @@
772	772	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.
773	773
774	774
	859	+
775	775	= 7. ​ Order Info =
776	776
777	777
778		-Part Number**:** NDS03A
	863	+Part Number**:** CPN01
779	779
780	780
	866	+
781	781	= 8.  Packing Info =
782	782
783	783
784	784	(% style="color:blue" %)**Package Includes**:
785	785
786		-* NDS03A Open/Close Door Sensor x 1
	872	+* CPN01 Open/Close Sensor x 1
	873	+* External antenna x 1
787	787
	875	+(% style="color:blue" %)**Dimension and weight**:
	876	+
	877	+* Size: 195 x 125 x 55 mm
	878	+* Weight:   420g
	879	+
	880	+
	881	+
788	788	= 9.  Support =
789	789
790	790

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

LMDS200_10.jpg

Author

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

Size

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

Content

image-20221117105556-1.png

Author

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

Size

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

Content

image-20221117114459-2.png

Author

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

Size

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

Content

image-20221117114842-3.png

Author

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

Size

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

Content

image-20221117114937-4.png

Author

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

Size

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

Content

image-20221117114949-5.png

Author

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

Size

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

Content

image-20221117115010-6.png

Author

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

Size

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

Content

image-20221117142300-1.png

Author

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

Size

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

Content

image-20221117145932-2.png

Author

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

Size

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

Content

image-20221117150312-3.png

Author

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

Size

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

Content

image-20221118092935-1.png

Author

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

Size

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

Content

image-20221118093144-2.png

Author

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

Size

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

Content

image-20221118093512-3.png

Author

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

Size

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

Content

image-20221118093658-4.png

Author

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

Size

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

Content

image-20221118094227-5.png

Author

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

Size

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

Content

image-20221118094449-6.png

Author

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

Size

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

Content

image-20221118103445-7.png

Author

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

Size

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

Content

image-20221118103453-8.png

Author

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

Size

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

Content

image-20221118103547-9.png

Author

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

Size

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

Content

image-20221207170748-1.png

Author

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

Size

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

Content

image-20221207170748-2.png

Author

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

Size

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

Content

image-20221207173200-3.png

Author

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

Size

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

Content

image-20221207173300-4.png

Author

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

Size

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

Content