Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 19 removed)
  • 1670404362039-351.png
  • 1670405841875-916.png
  • 1670405928926-116.png
  • 1670406036256-101.png
  • 1670406261143-723.png
  • 1670407401682-959.png
  • 1670408172929-569.png
  • 1670471530120-960.png
  • 1670471559211-638.png
  • 1670471584490-640.png
  • 1670471613823-833.png
  • LMDS200_10.jpg
  • image-20221207170748-1.png
  • image-20221207170748-2.png
  • image-20221207173200-3.png
  • image-20221207173300-4.png
  • image-20221208090742-1.png
  • image-20221209090938-1.png
  • image-20221212171610-1.jpeg

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,16 +1,12 @@
1	1	(% style="text-align:center" %)
2		-[[image:LMDS200_10.jpg||height="572" width="572"]]
	2	+[[image:image-20221117105556-1.png]]
3	3
4	4
5	5
6	6
7	7
8		-(% style="display:none" %) (%%)
9	9
10	10
11		-
12		-
13		-
14	14	**Table of Contents：**
15	15
16	16	{{toc/}}
...	...	@@ -19,55 +19,53 @@
19	19
20	20
21	21
22		-
23		-
24		-
25		-
26	26	= 1.  Introduction =
27	27
28		-== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
	20	+== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
29	29
30	30
31	31	(((
32		-The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor.
	24	+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.
33	33	)))
34	34
35	35	(((
36		-The NMDS200 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
	28	+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.
37	37	)))
38	38
39	39	(((
40		-NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
	32	+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.
41	41	)))
42	42
43	43	(((
44		-NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range.
	36	+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.
45	45	)))
46	46
47	47	(((
48		-NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technology**(%%) developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
	40	+NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
49	49	)))
50	50
51	51	(((
52		-NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
	44	+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.
53	53	)))
54	54
55	55	(((
56		-NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
	48	+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)
57	57	)))
58	58
59	59	(((
60		-To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection.
	52	+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.
61	61	)))
62	62
63	63
	56	+
64	64	== ​1.2  Features ==
65	65
66	66
67	67	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
68		-* Short uplink interval for Distance Alarm
	61	+* Open/Close detect
	62	+* Open/Close statistics
69	69	* Monitor Battery Level
70		-* Microwave Radar for distance detection
	64	+* connect two door sensors
71	71	* Datalog feature
72	72	* Uplink periodically
73	73	* Downlink to change configure
...	...	@@ -80,38 +80,29 @@
80	80
81	81
82	82
83		-== 1.3 Radar probe specification ==
	77	+== 1.3  Storage & Operation ==
84	84
85	85
86		-* Measuring Method: FMCW
87		-* Frequency: 24.000 ~~ 24.500 GHz
88		-* Measurement output power: 6dBm
89		-* Measure range: 0.5 ~~ 20m
90		-* Accuracy: ±0.1m
91		-* Resolution: 0.01m
92		-* Horizontal Angel: 78°
93		-* Vertical Angel: 23°
	80	+Temperature -40°C to +85°C
94	94
95	95
	83	+== 1.4  Mechanical ==
96	96
97		-== 1.4  Storage Temperature ==
98	98
	86	+[[image:image-20221117114937-4.png]]
99	99
100		- -40°C to +85°C
101	101
	89	+[[image:image-20221117114949-5.png]]
102	102
	91	+
	92	+[[image:image-20221117115010-6.png]]
	93	+
	94	+
	95	+
103	103	== 1.5 ​ Applications ==
104	104
105	105
106		-* Horizontal distance measurement
107		-* Liquid level measurement
108		-* Parking management system
109		-* Object proximity and presence detection
110		-* Intelligent trash can management system
111		-* Robot obstacle avoidance
112		-* Automatic control
113		-* Sewer
114		-* Bottom water level monitoring
	99	+[[image:image-20221117114842-3.png]]
115	115
116	116
117	117
...	...	@@ -121,66 +121,109 @@
121	121	(% style="color:blue" %)**Common DC Characteristics:**
122	122
123	123	* Supply Voltage: 2.1v ~~ 3.6v
124		-* Operating Temperature: 0 ~~ 70°C
	109	+* Operating Temperature: -40 ~~ 85°C
125	125
126	126	(% style="color:blue" %)**NB-IoT Spec:**
127	127
128		-* B1 @H-FDD: 2100MHz
129		-* B3 @H-FDD: 1800MHz
130		-* B8 @H-FDD: 900MHz
131		-* B5 @H-FDD: 850MHz
132		-* B20 @H-FDD: 800MHz
133		-* B28 @H-FDD: 700MHz
	113	+* - B1 @H-FDD: 2100MHz
	114	+* - B3 @H-FDD: 1800MHz
	115	+* - B8 @H-FDD: 900MHz
	116	+* - B5 @H-FDD: 850MHz
	117	+* - B20 @H-FDD: 800MHz
	118	+* - B28 @H-FDD: 700MHz
134	134
135	135
136	136
137		-== 1.7  Installation ==
	122	+== 1.7  Pin Definitions and Switch ==
138	138
139	139
140		-Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
	125	+[[image:image-20221021110429-4.png]]
141	141
142	142
143		-[[image:image-20221207170748-1.png]]
	128	+=== 1.7.1  Pin Definition ===
144	144
145	145
146		- [[image:image-20221207170748-2.png||height="345" width="634"]]
	131	+The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at:  [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
147	147
148	148
149		-== 1.8  Pin Definitions and Switch ==
150	150
	135	+=== 1.7.2  Jumper JP2(Power ON/OFF) ===
151	151
152		-[[image:1670404362039-351.png]]
153	153
	138	+Power on Device when putting this jumper.
154	154
155		-= 2.  Use NMDS200 to communicate with IoT Server =
156	156
	141	+
	142	+=== 1.7.3  BOOT MODE / SW1 ===
	143	+
	144	+
	145	+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.
	146	+
	147	+2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
	148	+
	149	+
	150	+
	151	+=== 1.7.4  Reset Button ===
	152	+
	153	+
	154	+Press to reboot the device.
	155	+
	156	+
	157	+
	158	+=== 1.7.5  LED ===
	159	+
	160	+
	161	+The LED will blink when :
	162	+
	163	+1.  Boot the device in flash mode
	164	+
	165	+2.  Send an uplink packet
	166	+
	167	+
	168	+
	169	+== 1.8  Magnet Distance ==
	170	+
	171	+
	172	+(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
	173	+
	174	+(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
	175	+
	176	+
	177	+
	178	+= 2.  Use NDS03A to communicate with IoT Server =
	179	+
157	157	== 2.1  How it works ==
158	158
159	159
160		-The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
	183	+In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.
161	161
162		-The diagram below shows the working flow in the default firmware of NMDS200:
	185	+The diagram below shows the working flow in the default firmware of NDS03A:
163	163
164		-[[image:image-20221021110615-5.png||height="996" width="492"]]
	187	+[[image:image-20221021110615-5.png]]
165	165
166	166
167		-== 2.2 ​ Configure NMDS200 ==
168	168
	191	+== 2.2 ​ Configure NDS03A ==
169	169
170		-To use NMDS200 in your city, make sure to meet below requirements:
	193	+=== 2.2.1 Test Requirement ===
171	171
	195	+
	196	+To use NDS03A in your city, make sure to meet below requirements:
	197	+
172	172	* Your local operator has already distributed an NB-IoT Network.
173		-* The local NB-IoT network used the band that NMDS200 supports.
	199	+* The local NB-IoT network used the band that NDS03A supports.
174	174	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
175	175
176		-Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NMDS200 will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
	202	+Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDS03A will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
177	177
178		-[[image:image-20221209090938-1.png]]
	204	+[[image:image-20221117142300-1.png]]
179	179
	206	+ ​
180	180
181		-=== 2.2.1 Insert NB-IoT SIM card ===
182	182
	209	+=== 2.2.2 Insert NB-IoT SIM card ===
183	183
	211	+
184	184	Insert the NB-IoT Card get from your provider.
185	185
186	186	User needs to take out the NB-IoT module and insert the SIM card like below:
...	...	@@ -188,11 +188,12 @@
188	188	[[image:image-20221021110745-6.png]] ​
189	189
190	190
191		-=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
192	192
	220	+=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
193	193
194		-User need to configure NMDS200 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NMDS200 support AT Commands, user can use a USB to TTL adapter to connect to NMDS200 and use AT Commands to configure it, as below.
195	195
	223	+User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
	224	+
196	196	(% style="color:blue" %)**Connection:**
197	197
198	198	(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
...	...	@@ -214,23 +214,24 @@
214	214
215	215	* Flow Control: (% style="color:red" %)**None**
216	216
217		-Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
	246	+Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
218	218
219	219	​[[image:image-20221021110817-7.png]]
220	220
221		-NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
	250	+NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
222	222
223	223
224	224	(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
225	225
226	226
227		-=== 2.2.3 Use CoAP protocol to uplink data ===
228	228
	257	+=== 2.2.4 Use CoAP protocol to uplink data ===
229	229
	259	+
230	230	(% style="color:red" %)**Note: if you don't have a CoAP server, you can refer this link to set up a CoAP server: **(%%)[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
231	231
232	232
233		-(% style="color:blue" %)**Use below commands in NMDS200:**
	263	+(% style="color:blue" %)**Use below commands in NDS03A:**
234	234
235	235	* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
236	236
...	...	@@ -240,17 +240,18 @@
240	240
241	241	For parameter description, please refer to AT command set
242	242
243		-[[image:1670471530120-960.png||height="647" width="674"]]
	273	+[[image:image-20221021110948-8.png]]
244	244
245	245
246		-After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server.
	276	+After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
247	247
248		-[[image:1670405841875-916.png]] ​
	278	+[[image:image-20221118103547-9.png||height="605" width="837"]] ​
249	249
250	250
251		-=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
252	252
	282	+=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
253	253
	284	+
254	254	(% style="color:blue" %)**AT Commands:**
255	255
256	256	* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
...	...	@@ -259,7 +259,7 @@
259	259
260	260	* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
261	261
262		-​ [[image:1670471559211-638.png]]
	293	+​ [[image:image-20221021111025-10.png]]
263	263
264	264
265	265	[[image:image-20221021111033-11.png||height="241" width="576"]]
...	...	@@ -266,9 +266,10 @@
266	266
267	267	​
268	268
269		-=== 2.2.5 Use MQTT protocol to uplink data ===
270	270
	301	+=== 2.2.6 Use MQTT protocol to uplink data ===
271	271
	303	+
272	272	(% style="color:blue" %)**AT Commands:**
273	273
274	274	* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
...	...	@@ -285,10 +285,10 @@
285	285
286	286	* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
287	287
288		-​ [[image:1670471584490-640.png]]
	320	+​ [[image:image-20221118103445-7.png]]
289	289
290	290
291		-[[image:1670405928926-116.png]]
	323	+[[image:image-20221118103453-8.png||height="608" width="841"]]
292	292
293	293	​
294	294
...	...	@@ -295,9 +295,10 @@
295	295	MQTT protocol has a much higher power consumption compare with UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
296	296
297	297
298		-=== 2.2.6 Use TCP protocol to uplink data ===
299	299
	331	+=== 2.2.7 Use TCP protocol to uplink data ===
300	300
	333	+
301	301	(% style="color:blue" %)**AT Commands:**
302	302
303	303	* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
...	...	@@ -304,19 +304,19 @@
304	304
305	305	* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
306	306
307		-​ [[image:1670471613823-833.png]]
	340	+​ [[image:image-20221021111125-14.png]]
308	308
309		-
310	310	[[image:image-20221021111131-15.png]]
311	311
312	312	​
313	313
314		-=== 2.2.7 Change Update Interval ===
315	315
	347	+=== 2.2.8 Change Update Interval ===
316	316
	349	+
317	317	User can use below command to change the (% style="color:blue" %)**uplink interval**.
318	318
319		-* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
	352	+* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
320	320
321	321	(% style="color:red" %)**NOTE:**
322	322
...	...	@@ -323,53 +323,78 @@
323	323	1.  By default, the device will send an uplink message every 4 hour.
324	324
325	325
	359	+
326	326	== 2.3  Uplink Payload ==
327	327
328	328
329		-The uplink payload includes 23 bytes in total by default.
	363	+The uplink payload includes 26 bytes in total by default.
330	330
331	331	Each time the device uploads a data package. The user can use the AT+NOUD command to upload the recorded data.Up to 32 sets of recorded data can be uploaded.
332	332
	367	+(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
333	333
334		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
335		-|(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:50px" %)**8**|(% style="background-color:#4f81bd; color:white; width:31px" %)**2**|(% style="background-color:#4f81bd; color:white; width:31px" %)**2**|(% style="background-color:#4f81bd; color:white; width:75px" %)**1**|(% style="background-color:#4f81bd; color:white; width:31px" %)**1**|(% style="background-color:#4f81bd; color:white; width:51px" %)**1**|(% style="background-color:#4f81bd; color:white; width:61px" %)**2**|(% style="background-color:#4f81bd; color:white; width:60px" %)**2**
336		-|(% style="width:93px" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) [[Distance 1>>||anchor="H2.4.5A0Distance"]] |(% style="width:93px" %) [[Distance 2>>||anchor="H2.4.5A0Distance"]]
	369	+(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
	370	+|=(% scope="row" style="width: 93px;" %)**Size(bytes)**|(% style="width:67px" %)**8**|(% style="width:40px" %)**2**|(% style="width:45px" %)**2**|(% style="width:75px" %)**1**|(% style="width:54px" %)**1**|(% style="width:62px" %)**1**|(% style="width:60px" %)**1**|(% style="width:94px" %)**3**|(% style="width:93px" %)**3**
	371	+|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
337	337
338		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:430px" %)
339		-|(% style="background-color:#4f81bd; color:white; width:80px" %)**4**|(% style="background-color:#4f81bd; color:white; width:80px" %)**2**|(% style="background-color:#4f81bd; color:white; width:80px" %)**2**|(% style="background-color:#4f81bd; color:white; width:80px" %)**4**|(% style="background-color:#4f81bd; color:white; width:110px" %)(((
	373	+(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
	374	+|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)(((
340	340	**1-32 group**
341	341	)))
342		-|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...
	377	+|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
343	343
344		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
345	345
346		-[[image:1670406261143-723.png]]
347	347
	381	+(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
348	348
349		-The payload is ASCII string, representative same HEX: **0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
350	350
	384	+(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
	385	+|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:66px" %)**8**|(% style="width:40px" %)**2**|(% style="width:46px" %)**2**|(% style="width:70px" %)**1**|(% style="width:54px" %)**1**|(% style="width:55px" %)**1**|(% style="width:57px" %)**1**|(% style="width:86px" %)**3**|(% style="width:82px" %)**3**
	386	+|=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
	387	+
	388	+(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
	389	+|(% style="width:59px" %)**1**|(% style="width:67px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:66px" %)**1**|(% style="width:92px" %)**3**
	390	+|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
	391	+
	392	+(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
	393	+|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
	394	+**1-32 group**
	395	+)))
	396	+|(% style="width:102px" %)last open time (pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:88px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
	397	+
	398	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
	399	+
	400	+[[image:image-20221117145932-2.png]]
	401	+
	402	+
	403	+The payload is ASCII string, representative same HEX:
	404	+
	405	+**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)**
	406	+
351	351	**where:**
352	352
353		-* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
	409	+* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
354	354
355	355	* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
356	356
357		-* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
	413	+* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
358	358
359		-* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
	415	+* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
360	360
361	361	* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
362	362
363		-* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
	419	+* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
364	364
365		-* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
	421	+* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
366	366
367		-* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
	423	+* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
368	368
369		-* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
	425	+* (% style="color:#037691" %)**last open time:  **(%%)0x000017 =23
370	370
	427	+* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
371	371
372	372
	430	+
373	373	== 2.4  Payload Explanation and Sensor Interface ==
374	374
375	375	=== 2.4.1  Device ID ===
...	...	@@ -391,13 +391,13 @@
391	391
392	392	Specify the software version: 0x64=100, which means firmware version 1.00.
393	393
394		-For example 0x00 64 : This device is NMDS200 with firmware version 1.0.0.
	452	+For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
395	395
396	396
397	397	=== 2.4.3  Battery Info ===
398	398
399	399
400		-Check the battery voltage for NMDS200.
	458	+Check the battery voltage for NDS03A.
401	401
402	402	Ex1: 0x0B45 = 2885mV
403	403
...	...	@@ -409,56 +409,55 @@
409	409
410	410	NB-IoT Network signal Strength.
411	411
412		-(% style="color:blue" %)**Ex1: 0x1d = 29**
	470	+**Ex1: 0x1d = 29**
413	413
414		-(% style="color:#037691" %)**0** (%%) -113dBm or less
	472	+**0**  -113dBm or less
415	415
416		-(% style="color:#037691" %)**1**  (%%) -111dBm
	474	+**1**  -111dBm
417	417
418		-(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
	476	+**2...30** -109dBm... -53dBm
419	419
420		-(% style="color:#037691" %)**31** (%%) -51dBm or greater
	478	+**31**   -51dBm or greater
421	421
422		-(% style="color:#037691" %)**99** (%%) Not known or not detectable
	480	+**99**    Not known or not detectable
423	423
424	424
425		-=== 2.4.5  Distance ===
	483	+=== 2.4.5  Disalarm: (default: 0) ===
426	426
427	427
428		-[[image:1670407401682-959.png]]
	486	+(% 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.
429	429
	488	+(% 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.
430	430
431		-(% style="color:blue" %)**Object1 Distance:**
	490	+ (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
432	432
433		-Distance between sensor probe to the first object. (unit: cm)
434	434
435		-For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
	493	+=== 2.4.6  Keep Status & Keep Time ===
436	436
437		-(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
438	438
	496	+Shows the configure value of Alarm Base on Timeout Feature
439	439
440		-(% style="color:blue" %)**Object2 Distance:**
441	441
442		-Distance between sensor probe to the second object. (unit: cm)
	499	+=== 2.4.7  Timestamp ===
443	443
444	444
445		-=== 2.4.6  Timestamp ===
	502	+Timestamp : 0x6315537b =1662342011
446	446
447	447
448		-Timestamp : 0x6315537b =1662342011
	505	+=== 2.4.8  Switch Dual Channel Mode ===
449	449
450	450
	508	+NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
	509	+
	510	+
451	451	== 2.5  Downlink Payload ==
452	452
453	453
454		-By default, NMDS200 prints the downlink payload to console port.
	514	+By default, NDS03A prints the downlink payload to console port.
455	455
456		-(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
457		-|(% style="background-color:#4f81bd; color:white" %)**Downlink Control Type**|(% style="background-color:#4f81bd; color:white" %)**FPort**|(% style="background-color:#4f81bd; color:white; width:97px" %)**Type Code**|(% style="background-color:#4f81bd; color:white; width:183px" %)**Downlink payload size(bytes)**
458		-|TDC (Transmit Time Interval)|Any|(% style="width:97px" %)01|(% style="width:183px" %)4
459		-|RESET|Any|(% style="width:97px" %)04|(% style="width:183px" %)2
460		-|INTMOD|Any|(% style="width:97px" %)06|(% style="width:183px" %)4
	516	+[[image:image-20221021111414-18.png]] ​
461	461
	518	+
462	462	**Examples:**
463	463
464	464	* (% style="color:#037691" %)**Set TDC**
...	...	@@ -471,7 +471,7 @@
471	471
472	472	* (% style="color:#037691" %)**Reset**
473	473
474		-If payload = 0x04FF, it will reset the NMDS200
	531	+If payload = 0x04FF, it will reset the NDS03A
475	475
476	476	* (% style="color:#037691" %)**INTMOD**
477	477
...	...	@@ -481,34 +481,120 @@
481	481	== 2.6  ​LED Indicator ==
482	482
483	483
484		-The NMDS200 has an internal LED which is to show the status of different states.
	541	+The NDS03A has an internal LED which is to show the status of different states.
485	485
486	486	* When the device starts normally, the LED will light up for 1 second.
487		-* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
	544	+* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
488	488	* For each uplink probe, LED will be on for 500ms.
489	489
490	490
491	491
492		-== 2.7  Distance alarm function ==
	549	+== 2.7  Alarm Base on Timeout ==
493	493
494	494
495		-(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
	552	+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:
496	496
497		-(% style="color:#037691" %)**Example 1:**
498	498
499		-AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
	555	+(% style="color:blue" %)**1. Keep Status: Status to be monitor**
500	500
501		-AT+ ALARM2 =min,max
	557	+Keep Status = 1: Monitor Close to Open event
502	502
	559	+Keep Status = 0: Monitor Open to Close event
503	503
504		-(% style="color:#037691" %)**Example 2:**
505	505
506		-AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
	562	+(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
507	507
	564	+Range 0 ~~ 65535(0xFFFF) seconds.
508	508
509		-== 2.8  Set the number of data to be uploaded and the recording time ==
	566	+If keep time = 0, Disable Alarm Base on Timeout feature.
510	510
	568	+If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
511	511
	570	+
	571	+(% style="color:blue" %)**AT Command to configure:**
	572	+
	573	+(% style="color:blue" %)**PB14 PIN:**
	574	+
	575	+(% 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.
	576	+
	577	+(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
	578	+
	579	+
	580	+(% style="color:blue" %)**PB15 PIN:**
	581	+
	582	+(% style="color:#037691" %)**AT+TTRIG2=1,30**
	583	+
	584	+(% style="color:#037691" %)**AT+TTRIG2=0,0 **
	585	+
	586	+
	587	+== 2.8  Set debug mode ==
	588	+
	589	+
	590	+Feature: Enable or Disable debug mode
	591	+
	592	+(% style="color:blue" %)**AT Command: AT+DEBUG**
	593	+
	594	+[[image:image-20221021111629-21.png]]
	595	+
	596	+
	597	+
	598	+== 2.9  Clear Flash Record ==
	599	+
	600	+
	601	+Feature: Clear flash storage for data log feature.
	602	+
	603	+(% style="color:blue" %)**AT Command: AT+CLRDTA**
	604	+
	605	+[[image:image-20221021111527-19.png]]
	606	+
	607	+
	608	+
	609	+== 2.10  Count Mod ==
	610	+
	611	+
	612	+(% style="color:blue" %)**AT Command: AT+COUNTMOD**
	613	+
	614	+[[image:image-20221118092935-1.png]]
	615	+
	616	+
	617	+
	618	+== 2.11  Interrupt Pin Channel Mod ==
	619	+
	620	+
	621	+(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
	622	+
	623	+[[image:image-20221118093144-2.png]]
	624	+
	625	+
	626	+
	627	+== 2.12 TTRIG1/2 timeout status alarm ==
	628	+
	629	+
	630	+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.
	631	+
	632	+(% style="color:blue" %)**AT Command: AT+TTRALARM**
	633	+
	634	+[[image:image-20221118093512-3.png]]
	635	+
	636	+
	637	+
	638	+== 2.13  Select counting mode ==
	639	+
	640	+
	641	+(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
	642	+
	643	+When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
	644	+
	645	+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.
	646	+
	647	+[[image:image-20221118093658-4.png]]
	648	+
	649	+
	650	+
	651	+
	652	+== 2.14  Set the number of data to be uploaded and the recording time ==
	653	+
	654	+
512	512	(% style="color:blue" %)**AT Command:**
513	513
514	514	(% 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)
...	...	@@ -516,7 +516,7 @@
516	516	(% 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.
517	517
518	518
519		-== 2.9  Read or Clear cached data ==
	662	+== 2.15  Read or Clear cached data ==
520	520
521	521
522	522	(% style="color:blue" %)**AT Command:**
...	...	@@ -525,25 +525,78 @@
525	525
526	526	(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
527	527
528		-[[image:1670408172929-569.png]]
	671	+[[image:image-20221118094227-5.png]]
529	529
530	530
531		-== 2.10  ​Firmware Change Log ==
532	532
	675	+== 2.16  ​Firmware Change Log ==
533	533
534		-Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]
535	535
	678	+Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
	679	+
536	536	Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
537	537
538	538
539		-== 2.11 Battery & Power Consumption ==
540	540
	684	+== 2.17  ​Battery Analysis ==
541	541
542		-NMDS200 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
543	543
544		-[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
	687	+=== 2.17.1  ​Battery Type ===
545	545
546	546
	690	+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.
	691	+
	692	+The battery is designed to last for several years depends on the actual use environment and update interval.
	693	+
	694	+The battery-related documents as below:
	695	+
	696	+* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	697	+
	698	+* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	699	+
	700	+* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	701	+
	702	+[[image:image-20221021111911-26.png]] ​
	703	+
	704	+
	705	+
	706	+=== 2.17.2  Power consumption Analyze ===
	707	+
	708	+
	709	+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.
	710	+
	711	+Instruction to use as below:
	712	+
	713	+(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
	714	+
	715	+(% style="color:blue" %)**Step 2: **(%%) Open it and choose
	716	+
	717	+* Product Model
	718	+
	719	+* Uplink Interval
	720	+
	721	+* Working Mode
	722	+
	723	+And the Life expectation in difference case will be shown on the right.
	724	+
	725	+[[image:1666596205057-567.png]] ​
	726	+
	727	+
	728	+
	729	+=== 2.17.3  ​Battery Note ===
	730	+
	731	+
	732	+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.
	733	+
	734	+
	735	+
	736	+=== 2.17.4  Replace the battery ===
	737	+
	738	+
	739	+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).
	740	+
	741	+
	742	+
547	547	= 3. ​ Access NB-IoT Module =
548	548
549	549
...	...	@@ -551,12 +551,13 @@
551	551
552	552	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/]]
553	553
554		-
555	555	[[image:image-20221118094449-6.png]] ​
556	556
557	557
	753	+
558	558	= 4.  Using the AT Commands =
559	559
	756	+
560	560	== 4.1  Access AT Commands ==
561	561
562	562
...	...	@@ -587,63 +587,71 @@
587	587
588	588	AT+INTMOD            : Set the trigger interrupt mode
589	589
590		-AT+5VT  : Set extend the time of 5V power
	787	+AT+5VT  : Set extend the time of 5V power
591	591
592		-AT+PRO  : Choose agreement
	789	+AT+PRO  : Choose agreement
593	593
594		-AT+RXDL  : Extend the sending and receiving time
	791	+AT+RXDL  : Extend the sending and receiving time
595	595
596		-AT+SERVADDR  : Server Address
	793	+AT+SERVADDR  : Server Address
597	597
598		-AT+TR      :  Get or Set record time
	795	+AT+TR      :  Get or Set record time
599	599
600		-AT+NOUD :  Get or Set the number of data to be uploaded
	797	+AT+NOUD      : Get or Set the number of data to be uploaded
601	601
602	602	AT+CDP     :  Read or Clear cached data
603	603
604		-AT+DEBUG:  Enable or Disable debug mode
	801	+AT+ DEBUG   : Enable or Disable debug mode
605	605
606		-AT+ALARM1:  Get or Set alarm of distance1
	803	+AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
607	607
608		-AT+ALARM2:  Get or Set alarm of distance2
	805	+AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
609	609
610		-AT+GETSENSORVALUE :  Returns the current sensor measurement
	807	+AT+COUNTMOD  :  Get or Set the count mode
611	611
612		-AT+POWERIC :  Get or set the Power IC flag
	809	+AT+TTRCHANNEL  : Get or Set the number of interrupt channels
613	613
	811	+AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
614	614
	813	+AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
	814	+
	815	+AT+ CLRC   :  Clear current door open count
	816	+
	817	+
615	615	(% style="color:blue" %)**COAP Management**
616	616
617		-AT+URI :  Resource parameters
	820	+AT+URI            : Resource parameters
618	618
619	619
620	620	(% style="color:blue" %)**UDP Management**
621	621
622		-AT+CFM :  Upload confirmation mode (only valid for UDP)
	825	+AT+CFM          : Upload confirmation mode (only valid for UDP)
623	623
624	624
625	625	(% style="color:blue" %)**MQTT Management**
626	626
627		-AT+CLIENT  : Get or Set MQTT client
	830	+AT+CLIENT               : Get or Set MQTT client
628	628
629		-AT+UNAME : Get or Set MQTT Username
	832	+AT+UNAME  : Get or Set MQTT Username
630	630
631		-AT+PWD  :  Get or Set MQTT password
	834	+AT+PWD                  : Get or Set MQTT password
632	632
633		-AT+PUBTOPIC :  Get or Set MQTT publish topic
	836	+AT+PUBTOPIC  : Get or Set MQTT publish topic
634	634
635		-AT+SUBTOPIC :  Get or Set MQTT subscription topic
	838	+AT+SUBTOPIC  : Get or Set MQTT subscription topic
636	636
637	637
638	638	(% style="color:blue" %)**Information**
639	639
640		-AT+FDR :  Factory Data Reset
	843	+AT+FDR  : Factory Data Reset
641	641
642		-AT+PWORD :  Serial Access Password
	845	+AT+PWORD  : Serial Access Password
643	643
644	644
	848	+
645	645	= ​5.  FAQ =
646	646
	851	+
647	647	== 5.1 ​ How to Upgrade Firmware ==
648	648
649	649
...	...	@@ -651,11 +651,13 @@
651	651
652	652	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]]
653	653
654		-(% 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.**
	859	+(% 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.**
655	655
656	656
	862	+
657	657	= 6.  Trouble Shooting =
658	658
	865	+
659	659	== 6.1  ​Connection problem when uploading firmware ==
660	660
661	661
...	...	@@ -662,6 +662,7 @@
662	662	(% 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]]
663	663
664	664
	872	+
665	665	== 6.2  AT Command input doesn't work ==
666	666
667	667
...	...	@@ -668,27 +668,21 @@
668	668	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.
669	669
670	670
671		-== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
672	672
673		-
674		-This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
675		-
676		-
677	677	= 7. ​ Order Info =
678	678
679	679
680		-Part Number:(% style="color:blue" %)** NMDS200**
	883	+Part Number**:** NDS03A
681	681
682	682
	886	+
683	683	= 8.  Packing Info =
684	684
685	685
686	686	(% style="color:blue" %)**Package Includes**:
687	687
688		-* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
	892	+* NDS03A Open/Close Door Sensor x 1
689	689
690		-
691		-
692	692	= 9.  Support =
693	693
694	694

1670404362039-351.png

Author

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

Size

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

Content

1670405841875-916.png

Author

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

Size

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

Content

1670405928926-116.png

Author

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

Size

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

Content

1670406036256-101.png

Author

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

Size

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

Content

1670406261143-723.png

Author

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

Size

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

Content

1670407401682-959.png

Author

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

Size

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

Content

1670408172929-569.png

Author

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

Size

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

Content

1670471530120-960.png

Author

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

Size

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

Content

1670471559211-638.png

Author

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

Size

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

Content

1670471584490-640.png

Author

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

Size

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

Content

1670471613823-833.png

Author

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

Size

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

Content

LMDS200_10.jpg

Author

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

Size

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

Content

image-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

image-20221209090938-1.png

Author

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

Size

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

Content

image-20221212171610-1.jpeg

Author

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

Size

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

Content