Summary

• Page properties (1 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
  • 1670471530120-960.png
  • image-20221207170748-1.png
  • image-20221207170748-2.png
  • image-20221207173200-3.png
  • image-20221207173300-4.png
  • image-20221208090742-1.png

Details

Page properties

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
...	...	@@ -66,38 +66,29 @@
66	66
67	67
68	68
69		-== 1.3 Radar probe specification ==
	81	+== 1.3  Storage & Operation ==
70	70
71	71
72		-* Measuring Method: FMCW
73		-* Frequency: 24.000 ~~ 24.500 GHz
74		-* Measurement output power: 6dBm
75		-* Measure range: 0.5 ~~ 20m
76		-* Accuracy: ±0.1m
77		-* Resolution: 0.01m
78		-* Horizontal Angel: 78°
79		-* Vertical Angel: 23°
	84	+Temperature -40°C to +85°C
80	80
81	81
	87	+== 1.4  Mechanical ==
82	82
83		-== 1.4  Storage Temperature ==
84	84
	90	+[[image:image-20221117114937-4.png]]
85	85
86		- -40°C to +85°C
87	87
	93	+[[image:image-20221117114949-5.png]]
88	88
	95	+
	96	+[[image:image-20221117115010-6.png]]
	97	+
	98	+
	99	+
89	89	== 1.5 ​ Applications ==
90	90
91	91
92		-* Horizontal distance measurement
93		-* Liquid level measurement
94		-* Parking management system
95		-* Object proximity and presence detection
96		-* Intelligent trash can management system
97		-* Robot obstacle avoidance
98		-* Automatic control
99		-* Sewer
100		-* Bottom water level monitoring
	103	+[[image:image-20221117114842-3.png]]
101	101
102	102
103	103
...	...	@@ -107,7 +107,7 @@
107	107	(% style="color:blue" %)**Common DC Characteristics:**
108	108
109	109	* Supply Voltage: 2.1v ~~ 3.6v
110		-* Operating Temperature: 0 ~~ 70°C
	113	+* Operating Temperature: -40 ~~ 85°C
111	111
112	112	(% style="color:blue" %)**NB-IoT Spec:**
113	113
...	...	@@ -120,52 +120,85 @@
120	120
121	121
122	122
123		-== 1.7  Installation ==
	126	+== 1.7  Pin Definitions and Switch ==
124	124
125	125
126		-Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
	129	+[[image:image-20221021110429-4.png]]
127	127
128	128
129		-[[image:image-20221207170748-1.png]]
	132	+=== 1.7.1  Pin Definition ===
130	130
131	131
132		- [[image:image-20221207170748-2.png||height="345" width="634"]]
	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]]
133	133
134	134
	138	+=== 1.7.2  Jumper JP2(Power ON/OFF) ===
135	135
136		-== 1.8  Pin Definitions and Switch ==
137	137
	141	+Power on Device when putting this jumper.
138	138
139		-[[image:1670404362039-351.png]]
140	140
	144	+=== 1.7.3  BOOT MODE / SW1 ===
141	141
142		-= 2.  Use NMDS200 to communicate with IoT Server =
143	143
	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	+
144	144	== 2.1  How it works ==
145	145
146	146
147		-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.
148	148
149		-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:
150	150
151		-[[image:image-20221021110615-5.png||height="996" width="492"]]
	185	+[[image:image-20221021110615-5.png]]
152	152
153	153
154		-== 2.2 ​ Configure NMDS200 ==
	188	+== 2.2 ​ Configure NDS03A ==
155	155
	190	+=== 2.2.1 Test Requirement ===
156	156
157		-To use NMDS200 in your city, make sure to meet below requirements:
158	158
	193	+To use NDS03A in your city, make sure to meet below requirements:
	194	+
159	159	* Your local operator has already distributed an NB-IoT Network.
160		-* The local NB-IoT network used the band that NMDS200 supports.
	196	+* The local NB-IoT network used the band that NDS03A supports.
161	161	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
162	162
163		-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.
164	164
165		-[[image:image-20221208090742-1.png]]
	201	+[[image:image-20221117142300-1.png]]
166	166
167	167
168		-=== 2.2.1 Insert NB-IoT SIM card ===
	204	+=== 2.2.2 Insert NB-IoT SIM card ===
169	169
170	170
171	171	Insert the NB-IoT Card get from your provider.
...	...	@@ -175,10 +175,10 @@
175	175	[[image:image-20221021110745-6.png]] ​
176	176
177	177
178		-=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
	214	+=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
179	179
180	180
181		-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.
182	182
183	183	(% style="color:blue" %)**Connection:**
184	184
...	...	@@ -201,23 +201,24 @@
201	201
202	202	* Flow Control: (% style="color:red" %)**None**
203	203
204		-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**(%%).
205	205
206	206	​[[image:image-20221021110817-7.png]]
207	207
208		-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.
209	209
210	210
211	211	(% 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]]
212	212
213	213
214		-=== 2.2.3 Use CoAP protocol to uplink data ===
215	215
	251	+=== 2.2.4 Use CoAP protocol to uplink data ===
216	216
	253	+
217	217	(% 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/]]
218	218
219	219
220		-(% style="color:blue" %)**Use below commands in NMDS200:**
	257	+(% style="color:blue" %)**Use below commands in NDS03A:**
221	221
222	222	* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
223	223
...	...	@@ -230,12 +230,12 @@
230	230	[[image:image-20221021110948-8.png]]
231	231
232	232
233		-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.
234	234
235		-[[image:1670405841875-916.png]] ​
	272	+[[image:image-20221118103547-9.png||height="605" width="837"]] ​
236	236
237	237
238		-=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
	275	+=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
239	239
240	240
241	241	(% style="color:blue" %)**AT Commands:**
...	...	@@ -253,7 +253,7 @@
253	253
254	254	​
255	255
256		-=== 2.2.5 Use MQTT protocol to uplink data ===
	293	+=== 2.2.6 Use MQTT protocol to uplink data ===
257	257
258	258
259	259	(% style="color:blue" %)**AT Commands:**
...	...	@@ -275,7 +275,7 @@
275	275	​ [[image:image-20221118103445-7.png]]
276	276
277	277
278		-[[image:1670405928926-116.png]]
	315	+[[image:image-20221118103453-8.png||height="608" width="841"]]
279	279
280	280	​
281	281
...	...	@@ -282,7 +282,7 @@
282	282	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.
283	283
284	284
285		-=== 2.2.6 Use TCP protocol to uplink data ===
	322	+=== 2.2.7 Use TCP protocol to uplink data ===
286	286
287	287
288	288	(% style="color:blue" %)**AT Commands:**
...	...	@@ -291,19 +291,18 @@
291	291
292	292	* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
293	293
294		-​ [[image:1670406036256-101.png||height="676" width="713"]]
	331	+​ [[image:image-20221021111125-14.png]]
295	295
296		-
297	297	[[image:image-20221021111131-15.png]]
298	298
299	299	​
300	300
301		-=== 2.2.7 Change Update Interval ===
	337	+=== 2.2.8 Change Update Interval ===
302	302
303	303
304	304	User can use below command to change the (% style="color:blue" %)**uplink interval**.
305	305
306		-* (% 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)
307	307
308	308	(% style="color:red" %)**NOTE:**
309	309
...	...	@@ -313,52 +313,72 @@
313	313	== 2.3  Uplink Payload ==
314	314
315	315
316		-The uplink payload includes 23 bytes in total by default.
	352	+The uplink payload includes 26 bytes in total by default.
317	317
318	318	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.
319	319
	356	+(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
320	320
321		-(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %)
322		-|=(% 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**
323		-|=(% 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)
324	324
325		-(% border="1" style="background-color:#ffffcc; color:green; width:429px" %)
326		-|(% 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" %)(((
327	327	**1-32 group**
328	328	)))
329		-|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...
	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" %)...
330	330
331		-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:**
332	332
333		-[[image:1670406261143-723.png]]
334	334
	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)
335	335
336		-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)
337	337
338		-**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" %)......
339	339
	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	+
340	340	**where:**
341	341
342		-* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
	396	+* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
343	343
344	344	* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
345	345
346		-* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
	400	+* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
347	347
348		-* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
	402	+* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
349	349
350	350	* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
351	351
352		-* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
	406	+* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
353	353
354		-* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
	408	+* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
355	355
356		-* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
	410	+* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
357	357
358		-* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
	412	+* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
359	359
	414	+* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
360	360
361	361
	417	+
362	362	== 2.4  Payload Explanation and Sensor Interface ==
363	363
364	364	=== 2.4.1  Device ID ===
...	...	@@ -380,13 +380,13 @@
380	380
381	381	Specify the software version: 0x64=100, which means firmware version 1.00.
382	382
383		-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.
384	384
385	385
386	386	=== 2.4.3  Battery Info ===
387	387
388	388
389		-Check the battery voltage for NMDS200.
	445	+Check the battery voltage for NDS03A.
390	390
391	391	Ex1: 0x0B45 = 2885mV
392	392
...	...	@@ -398,49 +398,51 @@
398	398
399	399	NB-IoT Network signal Strength.
400	400
401		-(% style="color:blue" %)**Ex1: 0x1d = 29**
	457	+**Ex1: 0x1d = 29**
402	402
403		-(% style="color:#037691" %)**0** (%%) -113dBm or less
	459	+**0**  -113dBm or less
404	404
405		-(% style="color:#037691" %)**1**  (%%) -111dBm
	461	+**1**  -111dBm
406	406
407		-(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
	463	+**2...30** -109dBm... -53dBm
408	408
409		-(% style="color:#037691" %)**31** (%%) -51dBm or greater
	465	+**31**   -51dBm or greater
410	410
411		-(% style="color:#037691" %)**99** (%%) Not known or not detectable
	467	+**99**    Not known or not detectable
412	412
413	413
414		-=== 2.4.5  Distance ===
	470	+=== 2.4.5  Disalarm: (default: 0) ===
415	415
416	416
417		-[[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.
418	418
	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.
419	419
420		-(% 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.
421	421
422		-Distance between sensor probe to the first object. (unit: cm)
423	423
424		-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 ===
425	425
426		-(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
427	427
	483	+Shows the configure value of Alarm Base on Timeout Feature
428	428
429		-(% style="color:blue" %)**Object2 Distance:**
430	430
431		-Distance between sensor probe to the second object. (unit: cm)
	486	+=== 2.4.7  Timestamp ===
432	432
433	433
434		-=== 2.4.6  Timestamp ===
	489	+Timestamp : 0x6315537b =1662342011
435	435
436	436
437		-Timestamp : 0x6315537b =1662342011
	492	+=== 2.4.8  Switch Dual Channel Mode ===
438	438
439	439
	495	+NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
	496	+
	497	+
440	440	== 2.5  Downlink Payload ==
441	441
442	442
443		-By default, NMDS200 prints the downlink payload to console port.
	501	+By default, NDS03A prints the downlink payload to console port.
444	444
445	445	[[image:image-20221021111414-18.png]] ​
446	446
...	...	@@ -457,7 +457,7 @@
457	457
458	458	* (% style="color:#037691" %)**Reset**
459	459
460		-If payload = 0x04FF, it will reset the NMDS200
	518	+If payload = 0x04FF, it will reset the NDS03A
461	461
462	462	* (% style="color:#037691" %)**INTMOD**
463	463
...	...	@@ -467,34 +467,114 @@
467	467	== 2.6  ​LED Indicator ==
468	468
469	469
470		-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.
471	471
472	472	* When the device starts normally, the LED will light up for 1 second.
473		-* 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.
474	474	* For each uplink probe, LED will be on for 500ms.
475	475
476	476
477	477
478		-== 2.7  Distance alarm function ==
	536	+== 2.7  Alarm Base on Timeout ==
479	479
480	480
481		-(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
	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:
482	482
483		-(% style="color:#037691" %)**Example 1:**
484	484
485		-AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
	542	+(% style="color:blue" %)**1. Keep Status: Status to be monitor**
486	486
487		-AT+ ALARM2 =min,max
	544	+Keep Status = 1: Monitor Close to Open event
488	488
	546	+Keep Status = 0: Monitor Open to Close event
489	489
490		-(% style="color:#037691" %)**Example 2:**
491	491
492		-AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
	549	+(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
493	493
	551	+Range 0 ~~ 65535(0xFFFF) seconds.
494	494
495		-== 2.8  Set the number of data to be uploaded and the recording time ==
	553	+If keep time = 0, Disable Alarm Base on Timeout feature.
496	496
	555	+If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
497	497
	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	+
498	498	(% style="color:blue" %)**AT Command:**
499	499
500	500	(% 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)
...	...	@@ -502,7 +502,7 @@
502	502	(% 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.
503	503
504	504
505		-== 2.9  Read or Clear cached data ==
	643	+== 2.15  Read or Clear cached data ==
506	506
507	507
508	508	(% style="color:blue" %)**AT Command:**
...	...	@@ -511,10 +511,10 @@
511	511
512	512	(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
513	513
514		-[[image:1670408172929-569.png]]
	652	+[[image:image-20221118094227-5.png]]
515	515
516	516
517		-== 2.10  ​Firmware Change Log ==
	655	+== 2.16  ​Firmware Change Log ==
518	518
519	519
520	520	Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
...	...	@@ -522,12 +522,12 @@
522	522	Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
523	523
524	524
525		-== 2.11  ​Battery Analysis ==
	663	+== 2.17  ​Battery Analysis ==
526	526
527		-=== 2.11.1  ​Battery Type ===
	665	+=== 2.17.1  ​Battery Type ===
528	528
529	529
530		-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.
531	531
532	532	The battery is designed to last for several years depends on the actual use environment and update interval.
533	533
...	...	@@ -542,7 +542,7 @@
542	542	[[image:image-20221021111911-26.png]] ​
543	543
544	544
545		-=== 2.11.2  Power consumption Analyze ===
	683	+=== 2.17.2  Power consumption Analyze ===
546	546
547	547
548	548	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.
...	...	@@ -564,16 +564,16 @@
564	564	[[image:1666596205057-567.png]] ​
565	565
566	566
567		-=== 2.11.3  ​Battery Note ===
	705	+=== 2.17.3  ​Battery Note ===
568	568
569	569
570	570	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.
571	571
572	572
573		-=== 2.11.4  Replace the battery ===
	711	+=== 2.17.4  Replace the battery ===
574	574
575	575
576		-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).
577	577
578	578
579	579	= 3. ​ Access NB-IoT Module =
...	...	@@ -619,59 +619,65 @@
619	619
620	620	AT+INTMOD            : Set the trigger interrupt mode
621	621
622		-AT+5VT  : Set extend the time of 5V power
	760	+AT+5VT  : Set extend the time of 5V power
623	623
624		-AT+PRO  : Choose agreement
	762	+AT+PRO  : Choose agreement
625	625
626		-AT+RXDL  : Extend the sending and receiving time
	764	+AT+RXDL  : Extend the sending and receiving time
627	627
628		-AT+SERVADDR  : Server Address
	766	+AT+SERVADDR  : Server Address
629	629
630		-AT+TR      :  Get or Set record time
	768	+AT+TR      :  Get or Set record time
631	631
632		-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
633	633
634	634	AT+CDP     :  Read or Clear cached data
635	635
636		-AT+DEBUG:  Enable or Disable debug mode
	774	+AT+ DEBUG   : Enable or Disable debug mode
637	637
638		-AT+ALARM1:  Get or Set alarm of distance1
	776	+AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
639	639
640		-AT+ALARM2:  Get or Set alarm of distance2
	778	+AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
641	641
642		-AT+GETSENSORVALUE :  Returns the current sensor measurement
	780	+AT+COUNTMOD  :  Get or Set the count mode
643	643
644		-AT+POWERIC :  Get or set the Power IC flag
	782	+AT+TTRCHANNEL  : Get or Set the number of interrupt channels
645	645
	784	+AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
646	646
	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	+
647	647	(% style="color:blue" %)**COAP Management**
648	648
649		-AT+URI :  Resource parameters
	793	+AT+URI            : Resource parameters
650	650
651	651
652	652	(% style="color:blue" %)**UDP Management**
653	653
654		-AT+CFM :  Upload confirmation mode (only valid for UDP)
	798	+AT+CFM          : Upload confirmation mode (only valid for UDP)
655	655
656	656
657	657	(% style="color:blue" %)**MQTT Management**
658	658
659		-AT+CLIENT  : Get or Set MQTT client
	803	+AT+CLIENT               : Get or Set MQTT client
660	660
661		-AT+UNAME : Get or Set MQTT Username
	805	+AT+UNAME  : Get or Set MQTT Username
662	662
663		-AT+PWD  :  Get or Set MQTT password
	807	+AT+PWD                  : Get or Set MQTT password
664	664
665		-AT+PUBTOPIC :  Get or Set MQTT publish topic
	809	+AT+PUBTOPIC  : Get or Set MQTT publish topic
666	666
667		-AT+SUBTOPIC :  Get or Set MQTT subscription topic
	811	+AT+SUBTOPIC  : Get or Set MQTT subscription topic
668	668
669	669
670	670	(% style="color:blue" %)**Information**
671	671
672		-AT+FDR :  Factory Data Reset
	816	+AT+FDR  : Factory Data Reset
673	673
674		-AT+PWORD :  Serial Access Password
	818	+AT+PWORD  : Serial Access Password
675	675
676	676
677	677	= ​5.  FAQ =
...	...	@@ -683,7 +683,7 @@
683	683
684	684	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]]
685	685
686		-(% 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.**
687	687
688	688
689	689	= 6.  Trouble Shooting =
...	...	@@ -703,7 +703,7 @@
703	703	= 7. ​ Order Info =
704	704
705	705
706		-Part Number:(% style="color:blue" %)** NMDS200**
	850	+Part Number**:** NDS03A
707	707
708	708
709	709	= 8.  Packing Info =
...	...	@@ -711,7 +711,7 @@
711	711
712	712	(% style="color:blue" %)**Package Includes**:
713	713
714		-* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
	858	+* NDS03A Open/Close Door Sensor x 1
715	715
716	716
717	717

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

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