Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 13 removed)
  • 1670404362039-351.png
  • 1670405841875-916.png
  • 1670405928926-116.png
  • 1670406036256-101.png
  • 1670406261143-723.png
  • 1670407401682-959.png
  • 1670408172929-569.png
  • LMDS200_10.jpg
  • image-20221207170748-1.png
  • image-20221207170748-2.png
  • image-20221207173200-3.png
  • image-20221207173300-4.png
  • image-20221208090742-1.png

Details

Page properties

Title

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

Content

...	...	@@ -1,7 +1,12 @@
1	1	(% style="text-align:center" %)
2		-[[image:LMDS200_10.jpg]]
	2	+[[image:image-20221117105556-1.png]]
3	3
4	4
	5	+
	6	+
	7	+
	8	+
	9	+
5	5	**Table of Contents：**
6	6
7	7	{{toc/}}
...	...	@@ -9,51 +9,58 @@
9	9
10	10
11	11
	17	+
12	12	= 1.  Introduction =
13	13
14		-== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
	20	+== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
15	15
16	16
17	17	(((
18		-The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor.
	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.
19	19	)))
20	20
21	21	(((
22		-The NMDS200 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
	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.
23	23	)))
24	24
25	25	(((
26		-NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
	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.
27	27	)))
28	28
29	29	(((
30		-NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range.
	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.
31	31	)))
32	32
33	33	(((
	40	+NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
	41	+)))
	42	+
	43	+(((
34	34	NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technology**(%%) developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
35	35	)))
36	36
37	37	(((
38		-NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
	48	+NDS03A supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
39	39	)))
40	40
41	41	(((
42		-NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
	52	+NDS03A is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
43	43	)))
44	44
45	45	(((
46		-To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection.
	56	+To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection.
47	47	)))
48	48
49	49
	60	+
50	50	== ​1.2  Features ==
51	51
52	52
53	53	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
54		-* Short uplink interval for Distance Alarm
	65	+* Open/Close detect
	66	+* Open/Close statistics
55	55	* Monitor Battery Level
56		-* Microwave Radar for distance detection
	68	+* connect two door sensors
57	57	* Datalog feature
58	58	* Uplink periodically
59	59	* Downlink to change configure
...	...	@@ -64,37 +64,34 @@
64	64	* Micro SIM card slot for NB-IoT SIM
65	65	* 8500mAh Battery for long-term use
66	66
67		-== 1.3 Radar probe specification ==
68	68
69	69
70		-* Measuring Method: FMCW
71		-* Frequency: 24.000 24.500 GHz
72		-* Measurement output power: 6dBm
73		-* Measure range: 0.5 20m
74		-* Accuracy: ±0.1m
75		-* Resolution: 0.01m
76		-* Horizontal Angel: 78°
77		-* Vertical Angel: 23°
	81	+== 1.3  Storage & Operation ==
78	78
79		-== 1.4  Storage Temperature ==
80	80
	84	+Temperature -40°C to +85°C
81	81
82		- -40°C to +85°C
83	83
	87	+== 1.4  Mechanical ==
84	84
	89	+
	90	+[[image:image-20221117114937-4.png]]
	91	+
	92	+
	93	+[[image:image-20221117114949-5.png]]
	94	+
	95	+
	96	+[[image:image-20221117115010-6.png]]
	97	+
	98	+
	99	+
85	85	== 1.5 ​ Applications ==
86	86
87	87
88		-* Horizontal distance measurement
89		-* Liquid level measurement
90		-* Parking management system
91		-* Object proximity and presence detection
92		-* Intelligent trash can management system
93		-* Robot obstacle avoidance
94		-* Automatic control
95		-* Sewer
96		-* Bottom water level monitoring
	103	+[[image:image-20221117114842-3.png]]
97	97
	105	+
	106	+
98	98	== 1.6  Specification ==
99	99
100	100
...	...	@@ -101,7 +101,7 @@
101	101	(% style="color:blue" %)**Common DC Characteristics:**
102	102
103	103	* Supply Voltage: 2.1v ~~ 3.6v
104		-* Operating Temperature: 0 ~~ 70°C
	113	+* Operating Temperature: -40 ~~ 85°C
105	105
106	106	(% style="color:blue" %)**NB-IoT Spec:**
107	107
...	...	@@ -112,52 +112,87 @@
112	112	* B20 @H-FDD: 800MHz
113	113	* B28 @H-FDD: 700MHz
114	114
115		-== 1.7  Installation ==
116	116
117	117
118		-Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
	126	+== 1.7  Pin Definitions and Switch ==
119	119
120	120
121		-[[image:image-20221207170748-1.png]]
	129	+[[image:image-20221021110429-4.png]]
122	122
123	123
124		- [[image:image-20221207170748-2.png||height="345" width="634"]]
	132	+=== 1.7.1  Pin Definition ===
125	125
126	126
	135	+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]]
127	127
128		-== 1.8  Pin Definitions and Switch ==
129	129
	138	+=== 1.7.2  Jumper JP2(Power ON/OFF) ===
130	130
131		-[[image:1670404362039-351.png]]
132	132
	141	+Power on Device when putting this jumper.
133	133
134		-= 2.  Use NMDS200 to communicate with IoT Server =
135	135
	144	+=== 1.7.3  BOOT MODE / SW1 ===
	145	+
	146	+
	147	+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.
	148	+
	149	+2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
	150	+
	151	+
	152	+=== 1.7.4  Reset Button ===
	153	+
	154	+
	155	+Press to reboot the device.
	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	+== 1.8  Magnet Distance ==
	169	+
	170	+
	171	+(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
	172	+
	173	+(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
	174	+
	175	+
	176	+= 2.  Use NDS03A to communicate with IoT Server =
	177	+
136	136	== 2.1  How it works ==
137	137
138	138
139		-The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
	181	+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.
140	140
141		-The diagram below shows the working flow in the default firmware of NMDS200:
	183	+The diagram below shows the working flow in the default firmware of NDS03A:
142	142
143	143	[[image:image-20221021110615-5.png]]
144	144
145	145
146		-== 2.2 ​ Configure NMDS200 ==
	188	+== 2.2 ​ Configure NDS03A ==
147	147
	190	+=== 2.2.1 Test Requirement ===
148	148
149		-To use NMDS200 in your city, make sure to meet below requirements:
150	150
	193	+To use NDS03A in your city, make sure to meet below requirements:
	194	+
151	151	* Your local operator has already distributed an NB-IoT Network.
152		-* The local NB-IoT network used the band that NMDS200 supports.
	196	+* The local NB-IoT network used the band that NDS03A supports.
153	153	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
154	154
155		-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.
	199	+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.
156	156
157		-[[image:image-20221208090742-1.png]]
	201	+[[image:image-20221117142300-1.png]]
158	158
159	159
160		-=== 2.2.1 Insert NB-IoT SIM card ===
	204	+=== 2.2.2 Insert NB-IoT SIM card ===
161	161
162	162
163	163	Insert the NB-IoT Card get from your provider.
...	...	@@ -167,10 +167,10 @@
167	167	[[image:image-20221021110745-6.png]] ​
168	168
169	169
170		-=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
	214	+=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
171	171
172	172
173		-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.
	217	+User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
174	174
175	175	(% style="color:blue" %)**Connection:**
176	176
...	...	@@ -193,11 +193,11 @@
193	193
194	194	* Flow Control: (% style="color:red" %)**None**
195	195
196		-Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
	240	+Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
197	197
198	198	​[[image:image-20221021110817-7.png]]
199	199
200		-NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
	244	+NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
201	201
202	202
203	203	(% 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]]
...	...	@@ -204,13 +204,13 @@
204	204
205	205
206	206
207		-=== 2.2.3 Use CoAP protocol to uplink data ===
	251	+=== 2.2.4 Use CoAP protocol to uplink data ===
208	208
209	209
210	210	(% 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/]]
211	211
212	212
213		-(% style="color:blue" %)**Use below commands in NMDS200:**
	257	+(% style="color:blue" %)**Use below commands in NDS03A:**
214	214
215	215	* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
216	216
...	...	@@ -223,12 +223,12 @@
223	223	[[image:image-20221021110948-8.png]]
224	224
225	225
226		-After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server.
	270	+After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
227	227
228		-[[image:1670405841875-916.png]] ​
	272	+[[image:image-20221118103547-9.png||height="605" width="837"]] ​
229	229
230	230
231		-=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
	275	+=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
232	232
233	233
234	234	(% style="color:blue" %)**AT Commands:**
...	...	@@ -246,7 +246,7 @@
246	246
247	247	​
248	248
249		-=== 2.2.5 Use MQTT protocol to uplink data ===
	293	+=== 2.2.6 Use MQTT protocol to uplink data ===
250	250
251	251
252	252	(% style="color:blue" %)**AT Commands:**
...	...	@@ -268,7 +268,7 @@
268	268	​ [[image:image-20221118103445-7.png]]
269	269
270	270
271		-[[image:1670405928926-116.png]]
	315	+[[image:image-20221118103453-8.png||height="608" width="841"]]
272	272
273	273	​
274	274
...	...	@@ -275,7 +275,7 @@
275	275	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.
276	276
277	277
278		-=== 2.2.6 Use TCP protocol to uplink data ===
	322	+=== 2.2.7 Use TCP protocol to uplink data ===
279	279
280	280
281	281	(% style="color:blue" %)**AT Commands:**
...	...	@@ -284,19 +284,18 @@
284	284
285	285	* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
286	286
287		-​ [[image:1670406036256-101.png||height="676" width="713"]]
	331	+​ [[image:image-20221021111125-14.png]]
288	288
289		-
290	290	[[image:image-20221021111131-15.png]]
291	291
292	292	​
293	293
294		-=== 2.2.7 Change Update Interval ===
	337	+=== 2.2.8 Change Update Interval ===
295	295
296	296
297	297	User can use below command to change the (% style="color:blue" %)**uplink interval**.
298	298
299		-* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
	342	+* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
300	300
301	301	(% style="color:red" %)**NOTE:**
302	302
...	...	@@ -306,51 +306,72 @@
306	306	== 2.3  Uplink Payload ==
307	307
308	308
309		-The uplink payload includes 23 bytes in total by default.
	352	+The uplink payload includes 26 bytes in total by default.
310	310
311	311	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.
312	312
	356	+(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
313	313
314		-(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %)
315		-|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:30px" %)**2**|(% style="width:30px" %)**2**|(% style="width:75px" %)**1**|(% style="width:30px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**
316		-|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) [[Distance 1>>||anchor="H2.4.5A0Distance"]] |(% style="width:93px" %) [[Distance 2>>||anchor="H2.4.5A0Distance"]]
	358	+(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
	359	+|=(% 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:60px" %)**1**|(% style="width:90px" %)**3**|(% style="width:100px" %)**3**
	360	+|=(% 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)
317	317
318		-(% border="1" style="background-color:#ffffcc; color:green; width:350px" %)
319		-|(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((
	362	+(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
	363	+|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
320	320	**1-32 group**
321	321	)))
322		-|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:98px" %)...
	366	+|(% 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" %)...
323	323
324		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
	368	+(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
325	325
326		-[[image:1670406261143-723.png]]
327	327
	371	+(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
	372	+|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:45px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:60px" %)**1**|(% style="width:60px" %)**1**|(% style="width:87px" %)**3**|(% style="width:80px" %)**3**
	373	+|=(% 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)
328	328
329		-The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
	375	+(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
	376	+|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:75px" %)**1**|(% style="width:75px" %)**3**
	377	+|(% 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)
330	330
331		-**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__(%%)**
	379	+(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
	380	+|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
	381	+**1-32 group**
	382	+)))
	383	+|(% style="width:102px" %)last open time(pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:100px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
332	332
	385	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
	386	+
	387	+[[image:image-20221117145932-2.png]]
	388	+
	389	+
	390	+The payload is ASCII string, representative same HEX:
	391	+
	392	+**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__(%%)**
	393	+
333	333	**where:**
334	334
335		-* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
	396	+* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
336	336
337	337	* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
338	338
339		-* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
	400	+* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
340	340
341		-* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
	402	+* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
342	342
343	343	* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
344	344
345		-* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
	406	+* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
346	346
347		-* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
	408	+* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
348	348
349		-* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
	410	+* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
350	350
351		-* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
	412	+* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
352	352
	414	+* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
353	353
	416	+
	417	+
354	354	== 2.4  Payload Explanation and Sensor Interface ==
355	355
356	356	=== 2.4.1  Device ID ===
...	...	@@ -372,13 +372,13 @@
372	372
373	373	Specify the software version: 0x64=100, which means firmware version 1.00.
374	374
375		-For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
	439	+For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
376	376
377	377
378	378	=== 2.4.3  Battery Info ===
379	379
380	380
381		-Check the battery voltage for NMDS200.
	445	+Check the battery voltage for NDS03A.
382	382
383	383	Ex1: 0x0B45 = 2885mV
384	384
...	...	@@ -390,49 +390,51 @@
390	390
391	391	NB-IoT Network signal Strength.
392	392
393		-(% style="color:blue" %)**Ex1: 0x1d = 29**
	457	+**Ex1: 0x1d = 29**
394	394
395		-(% style="color:#037691" %)**0** (%%) -113dBm or less
	459	+**0**  -113dBm or less
396	396
397		-(% style="color:#037691" %)**1**  (%%) -111dBm
	461	+**1**  -111dBm
398	398
399		-(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
	463	+**2...30** -109dBm... -53dBm
400	400
401		-(% style="color:#037691" %)**31** (%%) -51dBm or greater
	465	+**31**   -51dBm or greater
402	402
403		-(% style="color:#037691" %)**99** (%%) Not known or not detectable
	467	+**99**    Not known or not detectable
404	404
405	405
406		-=== 2.4.5  Distance ===
	470	+=== 2.4.5  Disalarm: (default: 0) ===
407	407
408	408
409		-[[image:1670407401682-959.png]]
	473	+(% 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.
410	410
	475	+(% 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.
411	411
412		-(% style="color:blue" %)**Object1 Distance:**
	477	+ (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
413	413
414		-Distance between sensor probe to the first object. (unit: cm)
415	415
416		-For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
	480	+=== 2.4.6  Keep Status & Keep Time ===
417	417
418		-(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
419	419
	483	+Shows the configure value of Alarm Base on Timeout Feature
420	420
421		-(% style="color:blue" %)**Object2 Distance:**
422	422
423		-Distance between sensor probe to the second object. (unit: cm)
	486	+=== 2.4.7  Timestamp ===
424	424
425	425
426		-=== 2.4.6  Timestamp ===
	489	+Timestamp : 0x6315537b =1662342011
427	427
428	428
429		-Timestamp : 0x6315537b =1662342011
	492	+=== 2.4.8  Switch Dual Channel Mode ===
430	430
431	431
	495	+NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
	496	+
	497	+
432	432	== 2.5  Downlink Payload ==
433	433
434	434
435		-By default, NMDS200 prints the downlink payload to console port.
	501	+By default, NDS03A prints the downlink payload to console port.
436	436
437	437	[[image:image-20221021111414-18.png]] ​
438	438
...	...	@@ -449,7 +449,7 @@
449	449
450	450	* (% style="color:#037691" %)**Reset**
451	451
452		-If payload = 0x04FF, it will reset the NMDS200
	518	+If payload = 0x04FF, it will reset the NDS03A
453	453
454	454	* (% style="color:#037691" %)**INTMOD**
455	455
...	...	@@ -459,33 +459,114 @@
459	459	== 2.6  ​LED Indicator ==
460	460
461	461
462		-The NMDS200 has an internal LED which is to show the status of different states.
	528	+The NDS03A has an internal LED which is to show the status of different states.
463	463
464	464	* When the device starts normally, the LED will light up for 1 second.
465		-* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
	531	+* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
466	466	* For each uplink probe, LED will be on for 500ms.
467	467
468	468
469		-== 2.7  Distance alarm function ==
470	470
	536	+== 2.7  Alarm Base on Timeout ==
471	471
472		-(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
473	473
474		-(% style="color:#037691" %)**Example 1:**
	539	+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:
475	475
476		-AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
477	477
478		-AT+ ALARM2 =min,max
	542	+(% style="color:blue" %)**1. Keep Status: Status to be monitor**
479	479
	544	+Keep Status = 1: Monitor Close to Open event
480	480
481		-(% style="color:#037691" %)**Example 2:**
	546	+Keep Status = 0: Monitor Open to Close event
482	482
483		-AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
484	484
	549	+(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
485	485
486		-== 2.8  Set the number of data to be uploaded and the recording time ==
	551	+Range 0 ~~ 65535(0xFFFF) seconds.
487	487
	553	+If keep time = 0, Disable Alarm Base on Timeout feature.
488	488
	555	+If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
	556	+
	557	+
	558	+(% style="color:blue" %)**AT Command to configure:**
	559	+
	560	+(% style="color:blue" %)**PB14 PIN:**
	561	+
	562	+(% 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.
	563	+
	564	+(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
	565	+
	566	+
	567	+(% style="color:blue" %)**PB15 PIN:**
	568	+
	569	+(% style="color:#037691" %)**AT+TTRIG2=1,30**
	570	+
	571	+(% style="color:#037691" %)**AT+TTRIG2=0,0 **
	572	+
	573	+
	574	+== 2.8  Set debug mode ==
	575	+
	576	+
	577	+Feature: Enable or Disable debug mode
	578	+
	579	+(% style="color:blue" %)**AT Command: AT+DEBUG**
	580	+
	581	+[[image:image-20221021111629-21.png]]
	582	+
	583	+
	584	+
	585	+== 2.9  Clear Flash Record ==
	586	+
	587	+
	588	+Feature: Clear flash storage for data log feature.
	589	+
	590	+(% style="color:blue" %)**AT Command: AT+CLRDTA**
	591	+
	592	+[[image:image-20221021111527-19.png]]
	593	+
	594	+
	595	+== 2.10  Count Mod ==
	596	+
	597	+
	598	+(% style="color:blue" %)**AT Command: AT+COUNTMOD**
	599	+
	600	+[[image:image-20221118092935-1.png]]
	601	+
	602	+
	603	+== 2.11  Interrupt Pin Channel Mod ==
	604	+
	605	+
	606	+(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
	607	+
	608	+[[image:image-20221118093144-2.png]]
	609	+
	610	+
	611	+== 2.12 TTRIG1/2 timeout status alarm ==
	612	+
	613	+
	614	+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.
	615	+
	616	+(% style="color:blue" %)**AT Command: AT+TTRALARM**
	617	+
	618	+[[image:image-20221118093512-3.png]]
	619	+
	620	+
	621	+== 2.13  Select counting mode ==
	622	+
	623	+
	624	+(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
	625	+
	626	+When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
	627	+
	628	+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.
	629	+
	630	+[[image:image-20221118093658-4.png]]
	631	+
	632	+
	633	+== 2.14  Set the number of data to be uploaded and the recording time ==
	634	+
	635	+
489	489	(% style="color:blue" %)**AT Command:**
490	490
491	491	(% 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)
...	...	@@ -493,7 +493,7 @@
493	493	(% 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.
494	494
495	495
496		-== 2.9  Read or Clear cached data ==
	643	+== 2.15  Read or Clear cached data ==
497	497
498	498
499	499	(% style="color:blue" %)**AT Command:**
...	...	@@ -502,10 +502,10 @@
502	502
503	503	(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
504	504
505		-[[image:1670408172929-569.png]]
	652	+[[image:image-20221118094227-5.png]]
506	506
507	507
508		-== 2.10  ​Firmware Change Log ==
	655	+== 2.16  ​Firmware Change Log ==
509	509
510	510
511	511	Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
...	...	@@ -513,12 +513,12 @@
513	513	Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
514	514
515	515
516		-== 2.11  ​Battery Analysis ==
	663	+== 2.17  ​Battery Analysis ==
517	517
518		-=== 2.11.1  ​Battery Type ===
	665	+=== 2.17.1  ​Battery Type ===
519	519
520	520
521		-The NMDS200 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
	668	+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.
522	522
523	523	The battery is designed to last for several years depends on the actual use environment and update interval.
524	524
...	...	@@ -533,7 +533,7 @@
533	533	[[image:image-20221021111911-26.png]] ​
534	534
535	535
536		-=== 2.11.2  Power consumption Analyze ===
	683	+=== 2.17.2  Power consumption Analyze ===
537	537
538	538
539	539	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.
...	...	@@ -555,16 +555,16 @@
555	555	[[image:1666596205057-567.png]] ​
556	556
557	557
558		-=== 2.11.3  ​Battery Note ===
	705	+=== 2.17.3  ​Battery Note ===
559	559
560	560
561	561	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.
562	562
563	563
564		-=== 2.11.4  Replace the battery ===
	711	+=== 2.17.4  Replace the battery ===
565	565
566	566
567		-The default battery pack of NMDS200 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
	714	+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).
568	568
569	569
570	570	= 3. ​ Access NB-IoT Module =
...	...	@@ -610,59 +610,65 @@
610	610
611	611	AT+INTMOD            : Set the trigger interrupt mode
612	612
613		-AT+5VT  : Set extend the time of 5V power
	760	+AT+5VT  : Set extend the time of 5V power
614	614
615		-AT+PRO  : Choose agreement
	762	+AT+PRO  : Choose agreement
616	616
617		-AT+RXDL  : Extend the sending and receiving time
	764	+AT+RXDL  : Extend the sending and receiving time
618	618
619		-AT+SERVADDR  : Server Address
	766	+AT+SERVADDR  : Server Address
620	620
621		-AT+TR      :  Get or Set record time
	768	+AT+TR      :  Get or Set record time
622	622
623		-AT+NOUD :  Get or Set the number of data to be uploaded
	770	+AT+NOUD      : Get or Set the number of data to be uploaded
624	624
625	625	AT+CDP     :  Read or Clear cached data
626	626
627		-AT+DEBUG:  Enable or Disable debug mode
	774	+AT+ DEBUG   : Enable or Disable debug mode
628	628
629		-AT+ALARM1:  Get or Set alarm of distance1
	776	+AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
630	630
631		-AT+ALARM2:  Get or Set alarm of distance2
	778	+AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
632	632
633		-AT+GETSENSORVALUE :  Returns the current sensor measurement
	780	+AT+COUNTMOD  :  Get or Set the count mode
634	634
635		-AT+POWERIC :  Get or set the Power IC flag
	782	+AT+TTRCHANNEL  : Get or Set the number of interrupt channels
636	636
	784	+AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
637	637
	786	+AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
	787	+
	788	+AT+ CLRC   :  Clear current door open count
	789	+
	790	+
638	638	(% style="color:blue" %)**COAP Management**
639	639
640		-AT+URI :  Resource parameters
	793	+AT+URI            : Resource parameters
641	641
642	642
643	643	(% style="color:blue" %)**UDP Management**
644	644
645		-AT+CFM :  Upload confirmation mode (only valid for UDP)
	798	+AT+CFM          : Upload confirmation mode (only valid for UDP)
646	646
647	647
648	648	(% style="color:blue" %)**MQTT Management**
649	649
650		-AT+CLIENT  : Get or Set MQTT client
	803	+AT+CLIENT               : Get or Set MQTT client
651	651
652		-AT+UNAME : Get or Set MQTT Username
	805	+AT+UNAME  : Get or Set MQTT Username
653	653
654		-AT+PWD  :  Get or Set MQTT password
	807	+AT+PWD                  : Get or Set MQTT password
655	655
656		-AT+PUBTOPIC :  Get or Set MQTT publish topic
	809	+AT+PUBTOPIC  : Get or Set MQTT publish topic
657	657
658		-AT+SUBTOPIC :  Get or Set MQTT subscription topic
	811	+AT+SUBTOPIC  : Get or Set MQTT subscription topic
659	659
660	660
661	661	(% style="color:blue" %)**Information**
662	662
663		-AT+FDR :  Factory Data Reset
	816	+AT+FDR  : Factory Data Reset
664	664
665		-AT+PWORD :  Serial Access Password
	818	+AT+PWORD  : Serial Access Password
666	666
667	667
668	668	= ​5.  FAQ =
...	...	@@ -674,7 +674,7 @@
674	674
675	675	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]]
676	676
677		-(% 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.**
	830	+(% 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.**
678	678
679	679
680	680	= 6.  Trouble Shooting =
...	...	@@ -694,7 +694,7 @@
694	694	= 7. ​ Order Info =
695	695
696	696
697		-Part Number:(% style="color:blue" %)** NMDS200**
	850	+Part Number**:** NDS03A
698	698
699	699
700	700	= 8.  Packing Info =
...	...	@@ -702,9 +702,10 @@
702	702
703	703	(% style="color:blue" %)**Package Includes**:
704	704
705		-* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
	858	+* NDS03A Open/Close Door Sensor x 1
706	706
707	707
	861	+
708	708	= 9.  Support =
709	709
710	710

1670404362039-351.png

Author

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

Size

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

Content

1670405841875-916.png

Author

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

Size

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

Content

1670405928926-116.png

Author

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

Size

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

Content

1670406036256-101.png

Author

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

Size

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

Content

1670406261143-723.png

Author

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

Size

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

Content

1670407401682-959.png

Author

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

Size

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

Content

1670408172929-569.png

Author

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

Size

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

Content

LMDS200_10.jpg

Author

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

Size

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

Content

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