Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 29 removed)
  • 1670404362039-351.png
  • 1670405841875-916.png
  • 1670405928926-116.png
  • 1670406036256-101.png
  • 1670406261143-723.png
  • 1670407401682-959.png
  • 1670408172929-569.png
  • LMDS200_10.jpg
  • image-20221117114459-2.png
  • image-20221117114842-3.png
  • image-20221117114937-4.png
  • image-20221117114949-5.png
  • image-20221117115010-6.png
  • image-20221117142300-1.png
  • image-20221117145932-2.png
  • image-20221117150312-3.png
  • image-20221118092935-1.png
  • image-20221118093144-2.png
  • image-20221118093512-3.png
  • image-20221118093658-4.png
  • image-20221118094227-5.png
  • image-20221118094449-6.png
  • image-20221118103445-7.png
  • image-20221118103453-8.png
  • image-20221118103547-9.png
  • image-20221207170748-1.png
  • image-20221207170748-2.png
  • image-20221207173200-3.png
  • image-20221207173300-4.png

Details

Page properties

Title

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

Content

...	...	@@ -1,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
...	...	@@ -10,37 +10,54 @@
10	10
11	11	= 1.  Introduction =
12	12
13		-== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
14	14
	19	+== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
15	15
	21	+
16	16	(((
17		-The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor.
	23	+The Dragino NDS03A is an (% style="color:blue" %)**Open/Close NB-IoT Door Sensor**(%%). It detects door (% style="color:blue" %)**open/close status**(%%) and (% style="color:blue" %)**uplinks**(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server.
	24	+)))
18	18
	26	+(((
	27	+The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically.
	28	+)))
19	19
20		-The NMDS200 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
	30	+(((
	31	+NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT.
	32	+)))
21	21
22		-NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
	34	+(((
	35	+NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time.
	36	+)))
23	23
24		-NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range.
	38	+(((
	39	+NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
	40	+)))
25	25
26		-NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technology**(%%) developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
	42	+(((
	43	+NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technologyTCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
	44	+)))
27	27
28		-NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
	46	+(((
	47	+NDS03A is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
	48	+)))
29	29
30		-NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
31		-
32		-To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection.
	50	+(((
	51	+To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection.
33	33	)))
34	34
35	35
	55	+​
36	36
	57	+
37	37	== ​1.2  Features ==
38	38
39	39
40	40	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
41		-* Short uplink interval for Distance Alarm
	62	+* Open/Close detect
	63	+* Open/Close statistics
42	42	* Monitor Battery Level
43		-* Microwave Radar for distance detection
	65	+* Uplink on periodically and open/close event
44	44	* Datalog feature
45	45	* Uplink periodically
46	46	* Downlink to change configure
...	...	@@ -51,104 +51,132 @@
51	51	* Micro SIM card slot for NB-IoT SIM
52	52	* 8500mAh Battery for long-term use
53	53
54		-== 1.3 Radar probe specification ==
	76	+== 1.3  Specification ==
55	55
56	56
57		-* Measuring Method: FMCW
58		-* Frequency: 24.000 24.500 GHz
59		-* Measurement output power: 6dBm
60		-* Measure range: 0.5 20m
61		-* Accuracy: ±0.1m
62		-* Resolution: 0.01m
63		-* Horizontal Angel: 78°
64		-* Vertical Angel: 23°
	79	+(% style="color:blue" %)**Common DC Characteristics:**
65	65
	81	+* Supply Voltage: 2.1v ~~ 3.6v
	82	+* Operating Temperature: -40 ~~ 85°C
66	66
67		-== 1.4  Storage Temperature ==
	84	+(% style="color:blue" %)**NB-IoT Spec:**
68	68
	86	+* - B1 @H-FDD: 2100MHz
	87	+* - B3 @H-FDD: 1800MHz
	88	+* - B8 @H-FDD: 900MHz
	89	+* - B5 @H-FDD: 850MHz
	90	+* - B20 @H-FDD: 800MHz
	91	+* - B28 @H-FDD: 700MHz
69	69
70		- -40°C to +85°C
	93	+== 1.4  Installation ==
71	71
72	72
	96	+Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
73	73
	98	+[[image:image-20221021110329-1.png]]
74	74
75	75
	101	+[[image:image-20221022234602-2.png||height="288" width="922"]]
	102	+
	103	+
	104	+
76	76	== 1.5 ​ Applications ==
77	77
78	78
	108	+* Open/Close Detection
	109	+* Pulse meter application
	110	+* Dry Contact Detection
79	79
80		-* Horizontal distance measurement
81		-* Liquid level measurement
82		-* Parking management system
83		-* Object proximity and presence detection
84		-* Intelligent trash can management system
85		-* Robot obstacle avoidance
86		-* Automatic control
87		-* Sewer
88		-* Bottom water level monitoring
	112	+== 1.6  Mechanical ==
89	89
90		-== 1.6  Specification ==
91	91
	115	+​[[image:image-20221021110415-3.png]]
92	92
93		-(% style="color:blue" %)**Common DC Characteristics:**
94	94
95		-* Supply Voltage: 2.1v ~~ 3.6v
96		-* Operating Temperature: 0 ~~ 70°C
97	97
98		-(% style="color:blue" %)**NB-IoT Spec:**
	119	+== 1.7  Pin Definitions and Switch ==
99	99
100		-* B1 @H-FDD: 2100MHz
101		-* B3 @H-FDD: 1800MHz
102		-* B8 @H-FDD: 900MHz
103		-* B5 @H-FDD: 850MHz
104		-* B20 @H-FDD: 800MHz
105		-* B28 @H-FDD: 700MHz
106	106
107		-== 1.7  Installation ==
	122	+[[image:image-20221021110429-4.png]]
108	108
109	109
110		-Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
	125	+=== 1.7.1  Pin Definition ===
111	111
112	112
113		-[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
	128	+CPN01 is pre-configured to connect to two external wires. The other pins are not used. If user wants to know more about other pins, please refer to the **[[LSN50v2 User Manual>>doc:Main.User Manual for LoRaWAN End Nodes.LSN50 & LSN50-V2 - LoRaWAN Sensor Node User Manual.WebHome]]**.
114	114
115	115
116	116
117		-== 1.8  Pin Definitions and Switch ==
	132	+=== 1.7.2  Jumper JP2(Power ON/OFF) ===
118	118
119	119
120		-[[image:1670404362039-351.png]]
	135	+Power on Device when putting this jumper.
121	121
122	122
123		-= 2.  Use NMDS200 to communicate with IoT Server =
124	124
	139	+=== 1.7.3  BOOT MODE / SW1 ===
	140	+
	141	+
	142	+1)  ISP:  upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run.
	143	+
	144	+2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
	145	+
	146	+
	147	+
	148	+=== 1.7.4  Reset Button ===
	149	+
	150	+
	151	+Press to reboot the device.
	152	+
	153	+
	154	+
	155	+=== 1.7.5  LED ===
	156	+
	157	+
	158	+The LED will blink when :
	159	+
	160	+1.  Boot the device in flash mode
	161	+
	162	+2.  Send an uplink packet
	163	+
	164	+
	165	+
	166	+= 2.  Use CPN01 to communicate with IoT Server =
	167	+
	168	+
125	125	== 2.1  How it works ==
126	126
127	127
128		-The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
	172	+The CPN01 is equipped with an NB-IoT module, the pre-loaded firmware in CPN01 will get (% style="color:blue" %)**Open/Close Event or Count**(%%) from sensor and send the value to the NB-IoT network. The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01.
129	129
130		-The diagram below shows the working flow in the default firmware of NMDS200:
	174	+The diagram below shows the working flow in the default firmware of CPN01:
131	131
132	132	[[image:image-20221021110615-5.png]]
133	133
134	134
135		-== 2.2 ​ Configure NMDS200 ==
136	136
	180	+== 2.2 ​ Configure CPN01 ==
137	137
138		-To use NMDS200 in your city, make sure to meet below requirements:
139	139
	183	+=== 2.2.1 Test Requirement ===
	184	+
	185	+
	186	+To use CPN01 in your city, make sure to meet below requirements:
	187	+
140	140	* Your local operator has already distributed an NB-IoT Network.
141		-* The local NB-IoT network used the band that NMDS200 supports.
	189	+* The local NB-IoT network used the band that CPN01 supports.
142	142	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
143	143
144		-Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NMDS200 will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
	192	+Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The CPN01 will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
145	145
146		-[[image:image-20221207173300-4.png]]
	194	+[[image:image-20221023000439-3.png]]
147	147
	196	+ ​
148	148
149		-=== 2.2.1 Insert NB-IoT SIM card ===
150	150
	199	+=== 2.2.2 Insert NB-IoT SIM card ===
151	151
	201	+
152	152	Insert the NB-IoT Card get from your provider.
153	153
154	154	User needs to take out the NB-IoT module and insert the SIM card like below:
...	...	@@ -156,11 +156,12 @@
156	156	[[image:image-20221021110745-6.png]] ​
157	157
158	158
159		-=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
160	160
	210	+=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
161	161
162		-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.
163	163
	213	+User need to configure CPN01 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. CPN01 support AT Commands, user can use a USB to TTL adapter to connect to CPN01 and use AT Commands to configure it, as below.
	214	+
164	164	(% style="color:blue" %)**Connection:**
165	165
166	166	(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
...	...	@@ -182,11 +182,11 @@
182	182
183	183	* Flow Control: (% style="color:red" %)**None**
184	184
185		-Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
	236	+Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
186	186
187	187	​[[image:image-20221021110817-7.png]]
188	188
189		-NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
	240	+CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
190	190
191	191
192	192	(% 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]]
...	...	@@ -193,13 +193,13 @@
193	193
194	194
195	195
196		-=== 2.2.3 Use CoAP protocol to uplink data ===
	247	+=== 2.2.4 Use CoAP protocol to uplink data ===
197	197
198	198
199	199	(% 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/]]
200	200
201	201
202		-(% style="color:blue" %)**Use below commands in NDS03A:**
	253	+(% style="color:blue" %)**Use below commands in CPN01:**
203	203
204	204	* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
205	205
...	...	@@ -212,14 +212,15 @@
212	212	[[image:image-20221021110948-8.png]]
213	213
214	214
215		-After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server.
	266	+After configuring the server address and (% style="color:green" %)**reset CPN01**(%%) (via AT+ATZ ), CPN01 will start to uplink sensor values to the CoAP server.
216	216
217		-[[image:1670405841875-916.png]] ​
	268	+[[image:image-20221021110956-9.png]] ​
218	218
219	219
220		-=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
221	221
	272	+=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
222	222
	274	+
223	223	(% style="color:blue" %)**AT Commands:**
224	224
225	225	* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
...	...	@@ -235,9 +235,10 @@
235	235
236	236	​
237	237
238		-=== 2.2.5 Use MQTT protocol to uplink data ===
239	239
	291	+=== 2.2.6 Use MQTT protocol to uplink data ===
240	240
	293	+
241	241	(% style="color:blue" %)**AT Commands:**
242	242
243	243	* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
...	...	@@ -254,10 +254,10 @@
254	254
255	255	* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
256	256
257		-​ [[image:image-20221118103445-7.png]]
	310	+​ [[image:image-20221021111058-12.png]]
258	258
259	259
260		-[[image:1670405928926-116.png]]
	313	+[[image:image-20221021111201-16.png||height="472" width="653"]]
261	261
262	262	​
263	263
...	...	@@ -264,9 +264,10 @@
264	264	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.
265	265
266	266
267		-=== 2.2.6 Use TCP protocol to uplink data ===
268	268
	321	+=== 2.2.7 Use TCP protocol to uplink data ===
269	269
	323	+
270	270	(% style="color:blue" %)**AT Commands:**
271	271
272	272	* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
...	...	@@ -273,75 +273,82 @@
273	273
274	274	* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
275	275
276		-​ [[image:1670406036256-101.png||height="676" width="713"]]
	330	+​ [[image:image-20221021111125-14.png]]
277	277
278		-
279	279	[[image:image-20221021111131-15.png]]
280	280
281	281	​
282	282
283		-=== 2.2.7 Change Update Interval ===
284	284
	337	+=== 2.2.8 Change Update Interval ===
285	285
	339	+
286	286	User can use below command to change the (% style="color:blue" %)**uplink interval**.
287	287
288		-* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
	342	+* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
289	289
290	290	(% style="color:red" %)**NOTE:**
291	291
292		-1.  By default, the device will send an uplink message every 4 hour.
	346	+1.  By default, the device will send an uplink message every 1 hour.
293	293
294	294
	349	+
295	295	== 2.3  Uplink Payload ==
296	296
297	297
298		-The uplink payload includes 23 bytes in total by default.
	353	+The uplink payload includes 123 bytes in total by default.
299	299
300		-Each time the device uploads a data package. The user can use the AT+NOUD command to upload the recorded data.Up to 32 sets of recorded data can be uploaded.
	355	+Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
301	301
302	302
303		-(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
304		-|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:90px" %)**2**|(% style="width:100px" %)**2**
305		-|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) Distance 1 |(% style="width:93px" %) Distance  2
	358	+(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
	359	+|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:60px" %)**3**
	360	+|=(% style="width: 96px;" %)**Value**|(% style="width:84px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:44px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:121px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:52px" %)MOD|(% style="width:84px" %)[[ Calculate Flag>>||anchor="H2.4.5A0CalculateFlag"]]|(% style="width:116px" %)[[Contact Status>>||anchor="H2.4.7A0ContactStatus"]]|(% style="width:57px" %)[[Alarm>>||anchor="H2.4.6A0Alarm"]]|(% style="width:91px" %)[[Total pulse>>||anchor="H2.4.8A0Totalpulse"]]
306	306
307		-(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
308		-|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
309		-**1-32 group**
310		-)))
311		-|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
	362	+(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
	363	+|(% style="width:100px" %)**3**|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:100px" %)**3**|(% style="width:80px" %)4|(% style="width:50px" %)**8 group**
	364	+|(% style="width:176px" %)[[The last open duration>>||anchor="H2.4.9A0Thelastopenduration"]]|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% style="width:115px" %)Contact Status|(% style="width:92px" %)Total pulse|(% style="width:169px" %)The last open duration|(% style="width:97px" %)Time stamp|(% style="width:74px" %)...
312	312
313		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
	366	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
314	314
315		-[[image:1670406261143-723.png]]
	368	+[[image:image-20221021111201-16.png||height="572" width="792"]]
316	316
317	317
318		-The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
	371	+The payload is ASCII string, representative same HEX:
319	319
320		-**0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
	373	+**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0c78__(% style="color:#00b0f0" %) __17__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__ (% style="color:#660066" %)__00__ (% style="color:#aaaa40" %)__000009__(% style="color:#663300" %) __000002__ (% style="color:#d60093" %)__6315537b__ (% style="color:#660066" %)__01 00000b 02 0000026 63510fed__ (%%)__0100000e0200000263510f39__ __010000000000000063510e85__ __010000000000000063510d2e__ __010000000000000063510c7a__ __010000000000000063510bc6__ __010000000000000063510954__ __010000000000000063510882 __**
321	321
322	322	**where:**
323	323
324		-* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
	377	+* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
325	325
326		-* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
	379	+* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
327	327
328		-* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
	381	+* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
329	329
330		-* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
	383	+* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
331	331
332		-* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
	385	+* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
333	333
334		-* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
	387	+* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
335	335
336		-* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
	389	+* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
337	337
338		-* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
	391	+* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
339	339
340		-* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
	393	+* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
341	341
	395	+* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
342	342
	397	+* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
	398	+
	399	+* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
	400	+
	401	+* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
	402	+
343	343	== 2.4  Payload Explanation and Sensor Interface ==
344	344
	405	+
345	345	=== 2.4.1  Device ID ===
346	346
347	347
...	...	@@ -356,18 +356,20 @@
356	356	The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
357	357
358	358
	420	+
359	359	=== 2.4.2  Version Info ===
360	360
361	361
362	362	Specify the software version: 0x64=100, which means firmware version 1.00.
363	363
364		-For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
	426	+For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
365	365
366	366
	429	+
367	367	=== 2.4.3  Battery Info ===
368	368
369	369
370		-Check the battery voltage for NMDS200.
	433	+Check the battery voltage for CPN01.
371	371
372	372	Ex1: 0x0B45 = 2885mV
373	373
...	...	@@ -374,6 +374,7 @@
374	374	Ex2: 0x0B49 = 2889mV
375	375
376	376
	440	+
377	377	=== 2.4.4  Signal Strength ===
378	378
379	379
...	...	@@ -392,35 +392,70 @@
392	392	**99**    Not known or not detectable
393	393
394	394
395		-=== 2.4.5  Distance ===
396	396
	460	+=== 2.4.5  Calculate Flag ===
397	397
398		-[[image:1670407401682-959.png]]
399	399
400		-(% style="color:blue" %)**Object1 Distance:**
	463	+The calculate flag is a user defined field, IoT server can use this filed to handle different meters with different pulse factors. For example, if there are 100 water meters, meter 1~~50 are 1 liter/pulse and meter 51 ~~ 100 has 1.5 liter/pulse.
401	401
402		-Distance between sensor probe to the first object. (unit: cm)
	465	+User can set calculate flag to 1 for meter 1~~50 and 2 for meter 51 ~~ 100, So IoT Server can use this field for calculation.
403	403
404		-For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
	467	+Default value: 0.
405	405
406		-(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
	469	+Range (6 bits): (b)000000 ~~ (b) 111111
407	407
408	408
409		-(% style="color:blue" %)**Object2 Distance:**
410	410
411		-Distance between sensor probe to the second object. (unit: cm)
	473	+=== 2.4.6  Alarm ===
412	412
413	413
414		-=== 2.4.6  Timestamp ===
	476	+See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
415	415
416	416
	479	+
	480	+=== 2.4.7  Contact Status ===
	481	+
	482	+
	483	+0: Open
	484	+
	485	+1: Close
	486	+
	487	+
	488	+
	489	+=== 2.4.8  Total pulse ===
	490	+
	491	+
	492	+Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
	493	+
	494	+Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
	495	+
	496	+
	497	+
	498	+=== 2.4.9  The last open duration ===
	499	+
	500	+
	501	+Dry Contact last open duration.
	502	+
	503	+Unit: min.
	504	+
	505	+[[image:image-20221021111346-17.png||height="146" width="770"]]
	506	+
	507	+
	508	+
	509	+=== 2.4.10  Timestamp ===
	510	+
	511	+
417	417	Timestamp : 0x6315537b =1662342011
418	418
	514	+Convert Unix timestamp to time 2022-9-5 9:40:11.
419	419
	516	+**~ **
	517	+
	518	+
420	420	== 2.5  Downlink Payload ==
421	421
422	422
423		-By default, NMDS200 prints the downlink payload to console port.
	522	+By default, CPN01 prints the downlink payload to console port.
424	424
425	425	[[image:image-20221021111414-18.png]] ​
426	426
...	...	@@ -437,7 +437,7 @@
437	437
438	438	* (% style="color:#037691" %)**Reset**
439	439
440		-If payload = 0x04FF, it will reset the NMDS200
	539	+If payload = 0x04FF, it will reset the NSE01
441	441
442	442	* (% style="color:#037691" %)**INTMOD**
443	443
...	...	@@ -444,34 +444,46 @@
444	444	Downlink Payload: 06000003, Set AT+INTMOD=3
445	445
446	446
	546	+
447	447	== 2.6  ​LED Indicator ==
448	448
449	449
450		-The NMDS200 has an internal LED which is to show the status of different states.
	550	+The CPN01 has an internal LED which is to show the status of different states.
451	451
452	452	* When the device starts normally, the LED will light up for 1 second.
453		-* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
	553	+* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
454	454	* For each uplink probe, LED will be on for 500ms.
455	455
	556	+== 2.7  Alarm Base on Timeout ==
456	456
457	457
458		-== 2.7  Distance alarm function ==
	559	+CPN01 can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are:
459	459
460	460
461		-(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
	562	+(% style="color:blue" %)**1. Keep Status: Status to be monitor**
462	462
463		-**Example 1:**
	564	+Keep Status = 1: Monitor Close to Open event
464	464
465		-AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
	566	+Keep Status = 0: Monitor Open to Close event
466	466
467		-AT+ ALARM2 =min,max
468	468
	569	+(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
469	469
470		-**Example 2:**
	571	+Range 0 ~~ 65535(0xFFFF) seconds.
471	471
472		-AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
	573	+If keep time = 0, Disable Alarm Base on Timeout feature.
473	473
	575	+If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
474	474
	577	+
	578	+(% style="color:blue" %)**AT Command to configure:**
	579	+
	580	+(% style="color:#037691" %)**AT+TTRIG=1,30** (%%) **~-~->**  When the **Keep Status** change from connected to disconnect, and device remains in disconnect status for more than 30 seconds. CPN01 will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
	581	+
	582	+(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
	583	+
	584	+
	585	+
475	475	== 2.8  Set debug mode ==
476	476
477	477
...	...	@@ -493,57 +493,54 @@
493	493	[[image:image-20221021111527-19.png]]
494	494
495	495
496		-== 2.10  Count Mod ==
497	497
	608	+== 2.10  Set trigger mode ==
498	498
499		-(% style="color:blue" %)**AT Command: AT+COUNTMOD**
500	500
501		-[[image:image-20221118092935-1.png]]
	611	+(% style="color:blue" %)**AT Command: AT+TTRMOD**
502	502
	613	+Feature: Set the trigger interrupt mode.
503	503
504		-== 2.11  Interrupt Pin Channel Mod ==
	615	+[[image:image-20221021111552-20.png]]
505	505
506	506
507		-(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
508	508
509		-[[image:image-20221118093144-2.png]]
	619	+== 2.11  Set the calculate flag ==
510	510
511	511
512		-== 2.12 TTRIG1/2 timeout status alarm ==
	622	+Feature: Set the calculate flag
513	513
	624	+(% style="color:blue" %)**AT Command: AT+CALCFLAG**
514	514
515		-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.
	626	+[[image:image-20221021111711-22.png]]
516	516
517		-(% style="color:blue" %)**AT Command: AT+TTRALARM**
518	518
519		-[[image:image-20221118093512-3.png]]
520	520
	630	+== 2.12 Set count number ==
521	521
522		-== 2.13  Select counting mode ==
523	523
	633	+Feature: Manually set the count number
524	524
525		-(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
	635	+(% style="color:blue" %)**AT Command: AT+SETCNT**
526	526
527		-When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
	637	+[[image:image-20221021111748-24.png]]
528	528
529		-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.
530	530
531		-[[image:image-20221118093658-4.png]]
532	532
	641	+== 2.13  Set the number of data to be uploaded and the recording time ==
533	533
534		-== 2.14  Set the number of data to be uploaded and the recording time ==
535	535
536		-
537	537	(% style="color:blue" %)**AT Command:**
538	538
539		-(% style="color:#037691" %)**AT+TR=900**(%%)  ~/~/  The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
	646	+(% style="color:#037691" %)**AT+TR=900**        (%%)~/~/  The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
540	540
541		-(% style="color:#037691" %)**AT+NOUD=8**(%%)** ** ~/~/  The device uploads 0 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
	648	+(% style="color:#037691" %)**AT+NOUD=8 ** (%%)~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
542	542
543	543
544		-== 2.15  Read or Clear cached data ==
545	545
	652	+== 2.14  Read or Clear cached data ==
546	546
	654	+
547	547	(% style="color:blue" %)**AT Command:**
548	548
549	549	(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
...	...	@@ -550,24 +550,27 @@
550	550
551	551	(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
552	552
553		-[[image:image-20221118094227-5.png]]
	661	+[[image:image-20221021111810-25.png||height="364" width="797"]]
554	554
555	555
556		-== 2.16  ​Firmware Change Log ==
557	557
	665	+== 2.15  ​Firmware Change Log ==
558	558
559		-Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
560	560
	668	+Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
	669	+
561	561	Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
562	562
563	563
564		-== 2.17  ​Battery Analysis ==
565	565
566		-=== 2.17.1  ​Battery Type ===
	674	+== 2.16  ​Battery Analysis ==
567	567
568	568
569		-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.
	677	+=== 2.16.1  ​Battery Type ===
570	570
	679	+
	680	+The CPN01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
	681	+
571	571	The battery is designed to last for several years depends on the actual use environment and update interval.
572	572
573	573	The battery-related documents as below:
...	...	@@ -581,9 +581,10 @@
581	581	[[image:image-20221021111911-26.png]] ​
582	582
583	583
584		-=== 2.17.2  Power consumption Analyze ===
585	585
	696	+=== 2.16.2  Power consumption Analyze ===
586	586
	698	+
587	587	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.
588	588
589	589	Instruction to use as below:
...	...	@@ -603,18 +603,21 @@
603	603	[[image:1666596205057-567.png]] ​
604	604
605	605
606		-=== 2.17.3  ​Battery Note ===
607	607
	719	+=== 2.16.3  ​Battery Note ===
608	608
	721	+
609	609	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.
610	610
611	611
612		-=== 2.17.4  Replace the battery ===
613	613
	726	+=== 2.16.4  Replace the battery ===
614	614
615		-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).
616	616
	729	+The default battery pack of CPN01 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
617	617
	731	+
	732	+
618	618	= 3. ​ Access NB-IoT Module =
619	619
620	620
...	...	@@ -622,12 +622,13 @@
622	622
623	623	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/]]
624	624
	740	+[[image:image-20221021112006-28.png]] ​
625	625
626		-[[image:image-20221118094449-6.png]] ​
627	627
628	628
629	629	= 4.  Using the AT Commands =
630	630
	746	+
631	631	== 4.1  Access AT Commands ==
632	632
633	633
...	...	@@ -674,21 +674,15 @@
674	674
675	675	AT+ DEBUG   : Enable or Disable debug mode
676	676
677		-AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
	793	+AT+ TTRIG   : Get or Set Alarm Base on Timeout
678	678
679		-AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
	795	+AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
680	680
681		-AT+COUNTMOD  :  Get or Set the count mode
	797	+AT+ CALCFLAG   : Get or Set the calculate flag
682	682
683		-AT+TTRCHANNEL  : Get or Set the number of interrupt channels
	799	+AT+ CLRC   : Clear current door open count
684	684
685		-AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
686	686
687		-AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
688		-
689		-AT+ CLRC   :  Clear current door open count
690		-
691		-
692	692	(% style="color:blue" %)**COAP Management**
693	693
694	694	AT+URI            : Resource parameters
...	...	@@ -719,8 +719,10 @@
719	719	AT+PWORD  : Serial Access Password
720	720
721	721
	832	+
722	722	= ​5.  FAQ =
723	723
	835	+
724	724	== 5.1 ​ How to Upgrade Firmware ==
725	725
726	726
...	...	@@ -728,11 +728,13 @@
728	728
729	729	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]]
730	730
731		-(% 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.**
	843	+(% style="color:red" %)**Notice: **(% style="color:blue" %)**CPN01** (%%)**and (% style="color:blue" %)CPL01(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
732	732
733	733
	846	+
734	734	= 6.  Trouble Shooting =
735	735
	849	+
736	736	== 6.1  ​Connection problem when uploading firmware ==
737	737
738	738
...	...	@@ -739,6 +739,7 @@
739	739	(% 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]]
740	740
741	741
	856	+
742	742	== 6.2  AT Command input doesn't work ==
743	743
744	744
...	...	@@ -745,19 +745,27 @@
745	745	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.
746	746
747	747
	863	+
748	748	= 7. ​ Order Info =
749	749
750	750
751		-Part Number**:** NDS03A
	867	+Part Number**:** CPN01
752	752
753	753
	870	+
754	754	= 8.  Packing Info =
755	755
756	756
757	757	(% style="color:blue" %)**Package Includes**:
758	758
759		-* NDS03A Open/Close Door Sensor x 1
	876	+* CPN01 Open/Close Sensor x 1
	877	+* External antenna x 1
760	760
	879	+(% style="color:blue" %)**Dimension and weight**:
	880	+
	881	+* Size: 195 x 125 x 55 mm
	882	+* Weight:   420g
	883	+
761	761	= 9.  Support =
762	762
763	763

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-20221117114459-2.png

Author

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

Size

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

Content

image-20221117114842-3.png

Author

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

Size

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

Content

image-20221117114937-4.png

Author

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

Size

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

Content

image-20221117114949-5.png

Author

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

Size

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

Content

image-20221117115010-6.png

Author

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

Size

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

Content

image-20221117142300-1.png

Author

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

Size

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

Content

image-20221117145932-2.png

Author

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

Size

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

Content

image-20221117150312-3.png

Author

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

Size

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

Content

image-20221118092935-1.png

Author

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

Size

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

Content

image-20221118093144-2.png

Author

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

Size

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

Content

image-20221118093512-3.png

Author

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

Size

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

Content

image-20221118093658-4.png

Author

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

Size

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

Content

image-20221118094227-5.png

Author

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

Size

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

Content

image-20221118094449-6.png

Author

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

Size

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

Content

image-20221118103445-7.png

Author

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

Size

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

Content

image-20221118103453-8.png

Author

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

Size

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

Content

image-20221118103547-9.png

Author

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

Size

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

Content

image-20221207170748-1.png

Author

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

Size

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

Content

image-20221207170748-2.png

Author

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

Size

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

Content

image-20221207173200-3.png

Author

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

Size

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

Content

image-20221207173300-4.png

Author

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

Size

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

Content