Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 52.1 >
edited by David Huang
on 2022/10/25 09:09
To version < 81.3 >
edited by Xiaoling
on 2022/12/07 18:09
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -CPN01- NB-IoT Outdoor Open/Close Dry Contact Sensor User Manual
1 +NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.David
1 +XWiki.Xiaoling
Content
... ... @@ -1,46 +1,46 @@
1 1  (% style="text-align:center" %)
2 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/WebHome/1652856952171-363.png?rev=1.1||alt="1652856952171-363.png" height="578" width="588"]]
2 +[[image:LMDS200_10.jpg]]
3 3  
4 4  
5 -
6 6  **Table of Contents：**
7 7  
8 -{{toc/}}
9 9  
10 10  
11 11  
12 12  
13 -
14 14  = 1.  Introduction =
15 15  
13 +== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
16 16  
17 -== 1.1 ​ What is CPN01 NB-IoT Pulse/Contact Sensor ==
18 18  
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.
19 19  
20 -The Dragino CPN01 is an (% style="color:blue" %)**NB-IoT Dry Contact Sensor**(%%). It detects open/close status and uplinks the info to IoT server via NB-IoT network. User can see the (% style="color:blue" %)**dry contact status, open time, and open counts**(%%) in the IoT Server.
21 21  
22 -The CPN01 will send periodically data every day as well as for each dry contact action. It also counts the contact open times and calculates the last open duration. Users can also disable the uplink for each Open/Close event, instead, device can count each open event and uplink periodically.
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.
23 23  
24 -CPN01 has** (% style="color:blue" %)Open-Alarm feature(%%)**, user can set this feature so CPN01 will send an alarm if the contact has been open exceeds a certain time.
22 +NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
25 25  
26 -CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures.
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.
27 27  
28 -NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
29 -\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
30 -\\CPN01 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
31 -\\To use CPN01, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that CPN01 supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into CPN01 to get NB-IoT network connection.
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.
32 32  
33 -​
28 +NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
34 34  
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)
35 35  
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.
33 +)))
34 +
35 +
36 +
36 36  == ​1.2  Features ==
37 37  
38 38  
39 39  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
40 -* Open/Close detect
41 -* Open/Close statistics
41 +* Short uplink interval for Distance Alarm
42 42  * Monitor Battery Level
43 -* Uplink on periodically and open/close event
43 +* Microwave Radar for distance detection
44 44  * Datalog feature
45 45  * Uplink periodically
46 46  * Downlink to change configure
... ... @@ -51,130 +51,104 @@
51 51  * Micro SIM card slot for NB-IoT SIM
52 52  * 8500mAh Battery for long-term use
53 53  
54 -== 1.3  Specification ==
54 +== 1.3 Radar probe specification ==
55 55  
56 56  
57 -(% style="color:blue" %)**Common DC Characteristics:**
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°
58 58  
59 -* Supply Voltage: 2.1v ~~ 3.6v
60 -* Operating Temperature: -40 ~~ 85°C
61 61  
62 -(% style="color:blue" %)**NB-IoT Spec:**
67 +== 1.4  Storage Temperature ==
63 63  
64 -* - B1 @H-FDD: 2100MHz
65 -* - B3 @H-FDD: 1800MHz
66 -* - B8 @H-FDD: 900MHz
67 -* - B5 @H-FDD: 850MHz
68 -* - B20 @H-FDD: 800MHz
69 -* - B28 @H-FDD: 700MHz
70 70  
71 -== 1.4  Installation ==
70 + -40°C to +85°C
72 72  
73 73  
74 -Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
75 75  
76 -[[image:image-20221021110329-1.png]]
77 77  
78 -[[image:image-20221022234602-2.png||height="288" width="922"]]
79 79  
80 -
81 -
82 82  == 1.5 ​ Applications ==
83 83  
84 84  
85 -* Open/Close Detection
86 -* Pulse meter application
87 -* Dry Contact Detection
88 88  
89 -== 1.6  Mechanical ==
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
90 90  
90 +== 1.6  Specification ==
91 91  
92 -​[[image:image-20221021110415-3.png]]
93 93  
93 +(% style="color:blue" %)**Common DC Characteristics:**
94 94  
95 +* Supply Voltage: 2.1v ~~ 3.6v
96 +* Operating Temperature: 0 ~~ 70°C
95 95  
96 -== 1.7  Pin Definitions and Switch ==
98 +(% style="color:blue" %)**NB-IoT Spec:**
97 97  
98 -[[image:image-20221021110429-4.png]]
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
99 99  
107 +== 1.7  Installation ==
100 100  
101 -=== 1.7.1  Pin Definition ===
102 102  
110 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
103 103  
104 -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]]**.
105 105  
113 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
106 106  
107 107  
108 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
109 109  
117 +== 1.8  Pin Definitions and Switch ==
110 110  
111 -Power on Device when putting this jumper.
112 112  
120 +[[image:1670404362039-351.png]]
113 113  
114 114  
115 -=== 1.7.3  BOOT MODE / SW1 ===
123 += 2.  Use NMDS200 to communicate with IoT Server =
116 116  
117 -
118 -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.
119 -
120 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
121 -
122 -
123 -
124 -=== 1.7.4  Reset Button ===
125 -
126 -
127 -Press to reboot the device.
128 -
129 -
130 -
131 -=== 1.7.5  LED ===
132 -
133 -
134 -The LED will blink when :
135 -
136 -1.  Boot the device in flash mode
137 -
138 -2.  Send an uplink packet
139 -
140 -
141 -
142 -= 2.  Use CPN01 to communicate with IoT Server =
143 -
144 -
145 145  == 2.1  How it works ==
146 146  
147 147  
148 -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.
128 +The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
149 149  
150 -The diagram below shows the working flow in the default firmware of CPN01:
130 +The diagram below shows the working flow in the default firmware of NMDS200:
151 151  
152 152  [[image:image-20221021110615-5.png]]
153 153  
154 154  
135 +== 2.2 ​ Configure NMDS200 ==
155 155  
156 -== 2.2 ​ Configure CPN01 ==
157 157  
138 +To use NMDS200 in your city, make sure to meet below requirements:
158 158  
159 -=== 2.2.1 Test Requirement ===
160 -
161 -
162 -To use CPN01 in your city, make sure to meet below requirements:
163 -
164 164  * Your local operator has already distributed an NB-IoT Network.
165 -* The local NB-IoT network used the band that CPN01 supports.
141 +* The local NB-IoT network used the band that NMDS200 supports.
166 166  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
167 167  
168 -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.
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.
169 169  
170 -[[image:image-20221023000439-3.png]]
146 +[[image:image-20221207173300-4.png]]
171 171  
172 - ​
173 173  
149 +=== 2.2.1 Insert NB-IoT SIM card ===
174 174  
175 -=== 2.2.2 Insert NB-IoT SIM card ===
176 176  
177 -
178 178  Insert the NB-IoT Card get from your provider.
179 179  
180 180  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -182,12 +182,11 @@
182 182  [[image:image-20221021110745-6.png]] ​
183 183  
184 184  
159 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
185 185  
186 -=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
187 187  
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.
188 188  
189 -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.
190 -
191 191  (% style="color:blue" %)**Connection:**
192 192  
193 193  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -209,11 +209,11 @@
209 209  
210 210  * Flow Control: (% style="color:red" %)**None**
211 211  
212 -Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
185 +Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
213 213  
214 214  ​[[image:image-20221021110817-7.png]]
215 215  
216 -CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
189 +NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
217 217  
218 218  
219 219  (% 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]]
... ... @@ -220,13 +220,13 @@
220 220  
221 221  
222 222  
223 -=== 2.2.4 Use CoAP protocol to uplink data ===
196 +=== 2.2.3 Use CoAP protocol to uplink data ===
224 224  
225 225  
226 226  (% 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/]]
227 227  
228 228  
229 -(% style="color:blue" %)**Use below commands in CPN01:**
202 +(% style="color:blue" %)**Use below commands in NDS03A:**
230 230  
231 231  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
232 232  
... ... @@ -239,15 +239,14 @@
239 239  [[image:image-20221021110948-8.png]]
240 240  
241 241  
242 -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.
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.
243 243  
244 -[[image:image-20221021110956-9.png]] ​
217 +[[image:1670405841875-916.png]] ​
245 245  
246 246  
220 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
247 247  
248 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
249 249  
250 -
251 251  (% style="color:blue" %)**AT Commands:**
252 252  
253 253  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -263,10 +263,9 @@
263 263  
264 264  ​
265 265  
238 +=== 2.2.5 Use MQTT protocol to uplink data ===
266 266  
267 -=== 2.2.6 Use MQTT protocol to uplink data ===
268 268  
269 -
270 270  (% style="color:blue" %)**AT Commands:**
271 271  
272 272  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -283,10 +283,10 @@
283 283  
284 284  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
285 285  
286 -​ [[image:image-20221021111058-12.png]]
257 +​ [[image:image-20221118103445-7.png]]
287 287  
288 288  
289 -[[image:image-20221021111201-16.png||height="472" width="653"]]
260 +[[image:1670405928926-116.png]]
290 290  
291 291  ​
292 292  
... ... @@ -293,10 +293,9 @@
293 293  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.
294 294  
295 295  
267 +=== 2.2.6 Use TCP protocol to uplink data ===
296 296  
297 -=== 2.2.7 Use TCP protocol to uplink data ===
298 298  
299 -
300 300  (% style="color:blue" %)**AT Commands:**
301 301  
302 302  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -303,82 +303,75 @@
303 303  
304 304  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
305 305  
306 -​ [[image:image-20221021111125-14.png]]
276 +​ [[image:1670406036256-101.png||height="676" width="713"]]
307 307  
278 +
308 308  [[image:image-20221021111131-15.png]]
309 309  
310 310  ​
311 311  
283 +=== 2.2.7 Change Update Interval ===
312 312  
313 -=== 2.2.8 Change Update Interval ===
314 314  
315 -
316 316  User can use below command to change the (% style="color:blue" %)**uplink interval**.
317 317  
318 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
288 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
319 319  
320 320  (% style="color:red" %)**NOTE:**
321 321  
322 -1.  By default, the device will send an uplink message every 1 hour.
292 +1.  By default, the device will send an uplink message every 4 hour.
323 323  
324 324  
325 -
326 326  == 2.3  Uplink Payload ==
327 327  
328 328  
329 -The uplink payload includes 123 bytes in total by default.
298 +The uplink payload includes 23 bytes in total by default.
330 330  
331 -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.
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.
332 332  
333 333  
334 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:510px" %)
335 -|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:40px" %)**2**|(% style="width:44px" %)**2**|(% style="width:121px" %)**1**|(% style="width:52px" %)**1**|(% style="width:84px" %)**1**|(% style="width:116px" %)**1**|(% style="width:57px" %)**1**|(% style="width:91px" %)**3**
336 -|=(% 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"]]
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
337 337  
338 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:490px" %)
339 -|(% style="width:176px" %)**3**|(% style="width:98px" %)**4**|(% style="width:115px" %)**1**|(% style="width:92px" %)**3**|(% style="width:169px" %)**3**|(% style="width:97px" %)4|(% style="width:74px" %)**8 group**|(% style="width:1px" %)
340 -|(% 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" %)...|(% style="width:1px" %)
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" %)...
341 341  
342 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
313 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
343 343  
344 -[[image:image-20221021111201-16.png||height="572" width="792"]]
315 +[[image:1670406261143-723.png]]
345 345  
346 346  
347 -The payload is ASCII string, representative same HEX:
318 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
348 348  
349 -**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 __**
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__(%%)**
350 350  
351 351  **where:**
352 352  
353 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
324 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
354 354  
355 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
326 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
356 356  
357 -* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
328 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
358 358  
359 -* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
330 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
360 360  
361 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
332 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
362 362  
363 -* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
334 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
364 364  
365 -* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
336 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
366 366  
367 -* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
338 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
368 368  
369 -* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
340 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
370 370  
371 -* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
372 372  
373 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
374 -
375 -* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
376 -
377 -* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
378 -
379 379  == 2.4  Payload Explanation and Sensor Interface ==
380 380  
381 -
382 382  === 2.4.1  Device ID ===
383 383  
384 384  
... ... @@ -393,20 +393,18 @@
393 393  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
394 394  
395 395  
396 -
397 397  === 2.4.2  Version Info ===
398 398  
399 399  
400 400  Specify the software version: 0x64=100, which means firmware version 1.00.
401 401  
402 -For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
364 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
403 403  
404 404  
405 -
406 406  === 2.4.3  Battery Info ===
407 407  
408 408  
409 -Check the battery voltage for CPN01.
370 +Check the battery voltage for NMDS200.
410 410  
411 411  Ex1: 0x0B45 = 2885mV
412 412  
... ... @@ -413,7 +413,6 @@
413 413  Ex2: 0x0B49 = 2889mV
414 414  
415 415  
416 -
417 417  === 2.4.4  Signal Strength ===
418 418  
419 419  
... ... @@ -432,70 +432,35 @@
432 432  **99**    Not known or not detectable
433 433  
434 434  
395 +=== 2.4.5  Distance ===
435 435  
436 -=== 2.4.5  Calculate Flag ===
437 437  
398 +[[image:1670407401682-959.png]]
438 438  
439 -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.
400 +(% style="color:blue" %)**Object1 Distance:**
440 440  
441 -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.
402 +Distance between sensor probe to the first object. (unit: cm)
442 442  
443 -Default value: 0. 
404 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
444 444  
445 -Range (6 bits): (b)000000 ~~ (b) 111111
406 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
446 446  
447 447  
409 +(% style="color:blue" %)**Object2 Distance:**
448 448  
449 -=== 2.4.6  Alarm ===
411 +Distance between sensor probe to the second object. (unit: cm)
450 450  
451 451  
452 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
414 +=== 2.4.6  Timestamp ===
453 453  
454 454  
455 -
456 -=== 2.4.7  Contact Status ===
457 -
458 -
459 -0: Open
460 -
461 -1: Close
462 -
463 -
464 -
465 -=== 2.4.8  Total pulse ===
466 -
467 -
468 -Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
469 -
470 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
471 -
472 -
473 -
474 -=== 2.4.9  The last open duration ===
475 -
476 -
477 -Dry Contact last open duration.
478 -
479 -Unit: min.
480 -
481 -[[image:image-20221021111346-17.png||height="146" width="770"]]
482 -
483 -
484 -
485 -=== 2.4.10  Timestamp ===
486 -
487 -
488 488  Timestamp : 0x6315537b =1662342011
489 489  
490 -Convert Unix timestamp to time 2022-9-5 9:40:11.
491 491  
492 -**~ **
493 -
494 -
495 495  == 2.5  Downlink Payload ==
496 496  
497 497  
498 -By default, CPN01 prints the downlink payload to console port.
423 +By default, NMDS200 prints the downlink payload to console port.
499 499  
500 500  [[image:image-20221021111414-18.png]] ​
501 501  
... ... @@ -512,7 +512,7 @@
512 512  
513 513  * (% style="color:#037691" %)**Reset**
514 514  
515 -If payload = 0x04FF, it will reset the NSE01
440 +If payload = 0x04FF, it will reset the NMDS200
516 516  
517 517  * (% style="color:#037691" %)**INTMOD**
518 518  
... ... @@ -519,22 +519,23 @@
519 519  Downlink Payload: 06000003, Set AT+INTMOD=3
520 520  
521 521  
522 -
523 523  == 2.6  ​LED Indicator ==
524 524  
525 525  
526 -The CPN01 has an internal LED which is to show the status of different states.
450 +The NMDS200 has an internal LED which is to show the status of different states.
527 527  
528 528  * When the device starts normally, the LED will light up for 1 second.
529 -* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
453 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
530 530  * For each uplink probe, LED will be on for 500ms.
531 531  
532 -== 2.7  Alarm Base on Timeout ==
533 533  
534 534  
535 -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:
458 +== 2.7  Distance alarm function ==
536 536  
537 537  
461 +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:
462 +
463 +
538 538  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
539 539  
540 540  Keep Status = 1: Monitor Close to Open event
... ... @@ -548,17 +548,25 @@
548 548  
549 549  If keep time = 0, Disable Alarm Base on Timeout feature.
550 550  
551 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
477 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
552 552  
553 553  
554 554  (% style="color:blue" %)**AT Command to configure:**
555 555  
556 -(% 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.
482 +(% style="color:blue" %)**PB14 PIN:**
557 557  
484 +(% 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.
485 +
558 558  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
559 559  
560 560  
489 +(% style="color:blue" %)**PB15 PIN:**
561 561  
491 +(% style="color:#037691" %)**AT+TTRIG2=1,30**
492 +
493 +(% style="color:#037691" %)**AT+TTRIG2=0,0 **
494 +
495 +
562 562  == 2.8  Set debug mode ==
563 563  
564 564  
... ... @@ -580,54 +580,57 @@
580 580  [[image:image-20221021111527-19.png]]
581 581  
582 582  
517 +== 2.10  Count Mod ==
583 583  
584 -== 2.10  Set trigger mode ==
585 585  
520 +(% style="color:blue" %)**AT Command: AT+COUNTMOD**
586 586  
587 -(% style="color:blue" %)**AT Command: AT+TTRMOD**
522 +[[image:image-20221118092935-1.png]]
588 588  
589 -Feature: Set the trigger interrupt mode.
590 590  
591 -[[image:image-20221021111552-20.png]]
525 +== 2.11  Interrupt Pin Channel Mod ==
592 592  
593 593  
528 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
594 594  
595 -== 2.11  Set the calculate flag ==
530 +[[image:image-20221118093144-2.png]]
596 596  
597 597  
598 -Feature: Set the calculate flag
533 +== 2.12 TTRIG1/2 timeout status alarm ==
599 599  
600 -(% style="color:blue" %)**AT Command: AT+CALCFLAG**
601 601  
602 -[[image:image-20221021111711-22.png]]
536 +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.
603 603  
538 +(% style="color:blue" %)**AT Command: AT+TTRALARM**
604 604  
540 +[[image:image-20221118093512-3.png]]
605 605  
606 -== 2.12 Set count number ==
607 607  
543 +== 2.13  Select counting mode ==
608 608  
609 -Feature: Manually set the count number
610 610  
611 -(% style="color:blue" %)**AT Command: AT+SETCNT**
546 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
612 612  
613 -[[image:image-20221021111748-24.png]]
548 +When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
614 614  
550 +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.
615 615  
552 +[[image:image-20221118093658-4.png]]
616 616  
617 -== 2.13  Set the number of data to be uploaded and the recording time ==
618 618  
555 +== 2.14  Set the number of data to be uploaded and the recording time ==
619 619  
557 +
620 620  (% style="color:blue" %)**AT Command:**
621 621  
622 -(% 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)
560 +(% 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)
623 623  
624 -(% 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.
562 +(% 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.
625 625  
626 626  
565 +== 2.15  Read or Clear cached data ==
627 627  
628 -== 2.14  Read or Clear cached data ==
629 629  
630 -
631 631  (% style="color:blue" %)**AT Command:**
632 632  
633 633  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -634,27 +634,24 @@
634 634  
635 635  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
636 636  
637 -[[image:image-20221021111810-25.png||height="364" width="797"]]
574 +[[image:image-20221118094227-5.png]]
638 638  
639 639  
577 +== 2.16  ​Firmware Change Log ==
640 640  
641 -== 2.15  ​Firmware Change Log ==
642 642  
580 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
643 643  
644 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
645 -
646 646  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
647 647  
648 648  
585 +== 2.17  ​Battery Analysis ==
649 649  
650 -== 2.16  ​Battery Analysis ==
587 +=== 2.17.1  ​Battery Type ===
651 651  
652 652  
653 -=== 2.16.1  ​Battery Type ===
590 +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.
654 654  
655 -
656 -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.
657 -
658 658  The battery is designed to last for several years depends on the actual use environment and update interval. 
659 659  
660 660  The battery-related documents as below:
... ... @@ -668,10 +668,9 @@
668 668  [[image:image-20221021111911-26.png]] ​
669 669  
670 670  
605 +=== 2.17.2  Power consumption Analyze ===
671 671  
672 -=== 2.16.2  Power consumption Analyze ===
673 673  
674 -
675 675  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.
676 676  
677 677  Instruction to use as below:
... ... @@ -691,21 +691,18 @@
691 691  [[image:1666596205057-567.png]] ​
692 692  
693 693  
627 +=== 2.17.3  ​Battery Note ===
694 694  
695 -=== 2.16.3  ​Battery Note ===
696 696  
697 -
698 698  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.
699 699  
700 700  
633 +=== 2.17.4  Replace the battery ===
701 701  
702 -=== 2.16.4  Replace the battery ===
703 703  
636 +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).
704 704  
705 -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).
706 706  
707 -
708 -
709 709  = 3. ​ Access NB-IoT Module =
710 710  
711 711  
... ... @@ -713,13 +713,12 @@
713 713  
714 714  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/]] 
715 715  
716 -[[image:image-20221021112006-28.png]] ​
717 717  
647 +[[image:image-20221118094449-6.png]] ​
718 718  
719 719  
720 720  = 4.  Using the AT Commands =
721 721  
722 -
723 723  == 4.1  Access AT Commands ==
724 724  
725 725  
... ... @@ -766,15 +766,21 @@
766 766  
767 767  AT+ DEBUG   : Enable or Disable debug mode
768 768  
769 -AT+ TTRIG   : Get or Set Alarm Base on Timeout
698 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
770 770  
771 -AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
700 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
772 772  
773 -AT+ CALCFLAG   : Get or Set the calculate flag
702 +AT+COUNTMOD  :  Get or Set the count mode
774 774  
775 -AT+ CLRC   : Clear current door open count
704 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
776 776  
706 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
777 777  
708 +AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
709 +
710 +AT+ CLRC   :  Clear current door open count
711 +
712 +
778 778  (% style="color:blue" %)**COAP Management**      
779 779  
780 780  AT+URI            : Resource parameters
... ... @@ -805,10 +805,8 @@
805 805  AT+PWORD  : Serial Access Password
806 806  
807 807  
808 -
809 809  = ​5.  FAQ =
810 810  
811 -
812 812  == 5.1 ​ How to Upgrade Firmware ==
813 813  
814 814  
... ... @@ -816,13 +816,11 @@
816 816  
817 817  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]]
818 818  
819 -(% 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.**
752 +(% 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.**
820 820  
821 821  
822 -
823 823  = 6.  Trouble Shooting =
824 824  
825 -
826 826  == 6.1  ​Connection problem when uploading firmware ==
827 827  
828 828  
... ... @@ -829,7 +829,6 @@
829 829  (% 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]]
830 830  
831 831  
832 -
833 833  == 6.2  AT Command input doesn't work ==
834 834  
835 835  
... ... @@ -836,27 +836,19 @@
836 836  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.
837 837  
838 838  
839 -
840 840  = 7. ​ Order Info =
841 841  
842 842  
843 -Part Number**:** CPN01
772 +Part Number**:** NDS03A
844 844  
845 845  
846 -
847 847  = 8.  Packing Info =
848 848  
849 849  
850 850  (% style="color:blue" %)**Package Includes**:
851 851  
852 -* CPN01 Open/Close Sensor x 1
853 -* External antenna x 1
780 +* NDS03A Open/Close Door Sensor x 1
854 854  
855 -(% style="color:blue" %)**Dimension and weight**:
856 -
857 -* Size: 195 x 125 x 55 mm
858 -* Weight:   420g
859 -
860 860  = 9.  Support =
861 861  
862 862  
1670404362039-351.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +492.6 KB
Content
1670405841875-916.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +181.0 KB
Content
1670406261143-723.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.9 KB
Content
1670407401682-959.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +23.7 KB
Content
LMDS200_10.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
image-20221117105556-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +133.3 KB
Content
image-20221117114459-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +14.9 KB
Content
image-20221117114842-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +964.1 KB
Content
image-20221117114937-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +79.1 KB
Content
image-20221117114949-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +33.4 KB
Content
image-20221117115010-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +40.4 KB
Content
image-20221117142300-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +51.9 KB
Content
image-20221117150312-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +8.7 KB
Content
image-20221118092935-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +9.5 KB
Content
image-20221118093658-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +12.7 KB
Content
image-20221118094227-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +29.2 KB
Content
image-20221118094449-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.5 KB
Content
image-20221118103445-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +43.5 KB
Content
image-20221207170748-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.1 KB
Content
image-20221207170748-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +29.9 KB
Content
image-20221207173200-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.7 KB
Content
image-20221207173300-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.0 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0