Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 48.14 >
edited by Xiaoling
on 2022/10/24 16:39
To version < 82.2 >
edited by Xiaoling
on 2022/12/07 18:18
>
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
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,136 +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 Radar probe specification ==
54 54  
55 55  
56 -== 1.3  Specification ==
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°
57 57  
58 58  
59 -(% style="color:blue" %)**Common DC Characteristics:**
67 +== 1.4  Storage Temperature ==
60 60  
61 -* Supply Voltage: 2.1v ~~ 3.6v
62 -* Operating Temperature: -40 ~~ 85°C
63 63  
64 -(% style="color:blue" %)**NB-IoT Spec:**
70 + -40°C to +85°C
65 65  
66 -* - B1 @H-FDD: 2100MHz
67 -* - B3 @H-FDD: 1800MHz
68 -* - B8 @H-FDD: 900MHz
69 -* - B5 @H-FDD: 850MHz
70 -* - B20 @H-FDD: 800MHz
71 -* - B28 @H-FDD: 700MHz
72 72  
73 73  
74 74  
75 -== 1.4  Installation ==
76 76  
77 -
78 -Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
79 -
80 -[[image:image-20221021110329-1.png]]
81 -
82 -[[image:image-20221022234602-2.png||height="288" width="922"]]
83 -
84 -
85 -
86 86  == 1.5 ​ Applications ==
87 87  
88 88  
89 -* Open/Close Detection
90 -* Pulse meter application
91 -* Dry Contact Detection
92 92  
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
93 93  
90 +== 1.6  Specification ==
94 94  
95 -== 1.6  Mechanical ==
96 96  
93 +(% style="color:blue" %)**Common DC Characteristics:**
97 97  
98 -​[[image:image-20221021110415-3.png]]
95 +* Supply Voltage: 2.1v ~~ 3.6v
96 +* Operating Temperature: 0 ~~ 70°C
99 99  
98 +(% style="color:blue" %)**NB-IoT Spec:**
100 100  
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
101 101  
102 -== 1.7  Pin Definitions and Switch ==
107 +== 1.7  Installation ==
103 103  
104 -[[image:image-20221021110429-4.png]]
105 105  
110 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
106 106  
107 -=== 1.7.1  Pin Definition ===
108 108  
113 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
109 109  
110 -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]]**.
111 111  
112 112  
117 +== 1.8  Pin Definitions and Switch ==
113 113  
114 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
115 115  
120 +[[image:1670404362039-351.png]]
116 116  
117 -Power on Device when putting this jumper.
118 118  
123 += 2.  Use NMDS200 to communicate with IoT Server =
119 119  
120 -
121 -=== 1.7.3  BOOT MODE / SW1 ===
122 -
123 -
124 -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.
125 -
126 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
127 -
128 -
129 -
130 -=== 1.7.4  Reset Button ===
131 -
132 -
133 -Press to reboot the device.
134 -
135 -
136 -
137 -=== 1.7.5  LED ===
138 -
139 -
140 -The LED will blink when :
141 -
142 -1.  Boot the device in flash mode
143 -
144 -2.  Send an uplink packet
145 -
146 -
147 -
148 -= 2.  Use CPN01 to communicate with IoT Server =
149 -
150 -
151 151  == 2.1  How it works ==
152 152  
153 153  
154 -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.
155 155  
156 -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:
157 157  
158 158  [[image:image-20221021110615-5.png]]
159 159  
160 160  
135 +== 2.2 ​ Configure NMDS200 ==
161 161  
162 -== 2.2 ​ Configure CPN01 ==
163 163  
138 +To use NMDS200 in your city, make sure to meet below requirements:
164 164  
165 -=== 2.2.1 Test Requirement ===
166 -
167 -
168 -To use CPN01 in your city, make sure to meet below requirements:
169 -
170 170  * Your local operator has already distributed an NB-IoT Network.
171 -* The local NB-IoT network used the band that CPN01 supports.
141 +* The local NB-IoT network used the band that NMDS200 supports.
172 172  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
173 173  
174 -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.
175 175  
176 -[[image:image-20221023000439-3.png]]
146 +[[image:image-20221207173300-4.png]]
177 177  
178 - ​
179 179  
149 +=== 2.2.1 Insert NB-IoT SIM card ===
180 180  
181 -=== 2.2.2 Insert NB-IoT SIM card ===
182 182  
183 -
184 184  Insert the NB-IoT Card get from your provider.
185 185  
186 186  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -188,12 +188,11 @@
188 188  [[image:image-20221021110745-6.png]] ​
189 189  
190 190  
159 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
191 191  
192 -=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
193 193  
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.
194 194  
195 -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.
196 -
197 197  (% style="color:blue" %)**Connection:**
198 198  
199 199  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -215,11 +215,11 @@
215 215  
216 216  * Flow Control: (% style="color:red" %)**None**
217 217  
218 -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**(%%).
219 219  
220 220  ​[[image:image-20221021110817-7.png]]
221 221  
222 -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.
223 223  
224 224  
225 225  (% 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]]
... ... @@ -226,13 +226,13 @@
226 226  
227 227  
228 228  
229 -=== 2.2.4 Use CoAP protocol to uplink data ===
196 +=== 2.2.3 Use CoAP protocol to uplink data ===
230 230  
231 231  
232 232  (% 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/]]
233 233  
234 234  
235 -(% style="color:blue" %)**Use below commands in CPN01:**
202 +(% style="color:blue" %)**Use below commands in NDS03A:**
236 236  
237 237  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
238 238  
... ... @@ -245,15 +245,14 @@
245 245  [[image:image-20221021110948-8.png]]
246 246  
247 247  
248 -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.
249 249  
250 -[[image:image-20221021110956-9.png]] ​
217 +[[image:1670405841875-916.png]] ​
251 251  
252 252  
220 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
253 253  
254 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
255 255  
256 -
257 257  (% style="color:blue" %)**AT Commands:**
258 258  
259 259  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -269,10 +269,9 @@
269 269  
270 270  ​
271 271  
238 +=== 2.2.5 Use MQTT protocol to uplink data ===
272 272  
273 -=== 2.2.6 Use MQTT protocol to uplink data ===
274 274  
275 -
276 276  (% style="color:blue" %)**AT Commands:**
277 277  
278 278  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -289,10 +289,10 @@
289 289  
290 290  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
291 291  
292 -​ [[image:image-20221021111058-12.png]]
257 +​ [[image:image-20221118103445-7.png]]
293 293  
294 294  
295 -[[image:image-20221021111201-16.png||height="472" width="653"]]
260 +[[image:1670405928926-116.png]]
296 296  
297 297  ​
298 298  
... ... @@ -299,10 +299,9 @@
299 299  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.
300 300  
301 301  
267 +=== 2.2.6 Use TCP protocol to uplink data ===
302 302  
303 -=== 2.2.7 Use TCP protocol to uplink data ===
304 304  
305 -
306 306  (% style="color:blue" %)**AT Commands:**
307 307  
308 308  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -309,84 +309,75 @@
309 309  
310 310  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
311 311  
312 -​ [[image:image-20221021111125-14.png]]
276 +​ [[image:1670406036256-101.png||height="676" width="713"]]
313 313  
278 +
314 314  [[image:image-20221021111131-15.png]]
315 315  
316 316  ​
317 317  
283 +=== 2.2.7 Change Update Interval ===
318 318  
319 -=== 2.2.8 Change Update Interval ===
320 320  
321 -
322 322  User can use below command to change the (% style="color:blue" %)**uplink interval**.
323 323  
324 -* (% 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)
325 325  
326 326  (% style="color:red" %)**NOTE:**
327 327  
328 -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.
329 329  
330 330  
331 -
332 332  == 2.3  Uplink Payload ==
333 333  
334 334  
335 -The uplink payload includes 123 bytes in total by default.
298 +The uplink payload includes 23 bytes in total by default.
336 336  
337 -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.
338 338  
339 339  
340 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:510px" %)
341 -|=(% 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**
342 -|=(% 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
343 343  
344 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:510px" %)
345 -|(% style="width:176px" %)**3**|(% style="width:98px" %)**4**|(% style="width:115px" %)**1**|(% style="width:92px" %)**3**|(% style="width:110px" %)**1**|(% style="width:169px" %)**3**|(% style="width:97px" %)4|(% style="width:74px" %)**8 group**
346 -|(% 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:110px" %)Calculate Flag|(% style="width:169px" %)The last open duration|(% style="width:97px" %)Time stamp|(% style="width:74px" %)...
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" %)...
347 347  
348 -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.
349 349  
350 -[[image:image-20221021111201-16.png||height="572" width="792"]]
315 +[[image:1670406261143-723.png]]
351 351  
352 352  
353 -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
354 354  
355 -**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" %)09(% style="color:#663300" %) 02 (% 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__(%%)**
356 356  
357 357  **where:**
358 358  
359 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
324 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
360 360  
361 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
326 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
362 362  
363 -* (% style="color:#037691" %)**BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
328 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
364 364  
365 -* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
330 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
366 366  
367 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
332 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
368 368  
369 -* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
334 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
370 370  
371 -* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
336 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
372 372  
373 -* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
338 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
374 374  
375 -* (% style="color:#037691" %)**Total pulse: **(%%)0x09 =0
340 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
376 376  
377 -* (% style="color:#037691" %)**The last open duration: **(%%)0x02 =2
378 378  
379 -* (% style="color:#037691" %)** Time stamp :**(%%) 0x6315537b =1662342011 (Unix Time)
380 -
381 -* (% style="color:#037691" %)**Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 01  00000b  02  000026  63510fed
382 -
383 -* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
384 -
385 -
386 -
387 387  == 2.4  Payload Explanation and Sensor Interface ==
388 388  
389 -
390 390  === 2.4.1  Device ID ===
391 391  
392 392  
... ... @@ -401,20 +401,18 @@
401 401  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
402 402  
403 403  
404 -
405 405  === 2.4.2  Version Info ===
406 406  
407 407  
408 408  Specify the software version: 0x64=100, which means firmware version 1.00.
409 409  
410 -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.
411 411  
412 412  
413 -
414 414  === 2.4.3  Battery Info ===
415 415  
416 416  
417 -Check the battery voltage for CPN01.
370 +Check the battery voltage for NMDS200.
418 418  
419 419  Ex1: 0x0B45 = 2885mV
420 420  
... ... @@ -421,7 +421,6 @@
421 421  Ex2: 0x0B49 = 2889mV
422 422  
423 423  
424 -
425 425  === 2.4.4  Signal Strength ===
426 426  
427 427  
... ... @@ -440,70 +440,35 @@
440 440  **99**    Not known or not detectable
441 441  
442 442  
395 +=== 2.4.5  Distance ===
443 443  
444 -=== 2.4.5  Calculate Flag ===
445 445  
398 +[[image:1670407401682-959.png]]
446 446  
447 -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:**
448 448  
449 -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)
450 450  
451 -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
452 452  
453 -Range (6 bits): (b)000000 ~~ (b) 111111
406 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
454 454  
455 455  
409 +(% style="color:blue" %)**Object2 Distance:**
456 456  
457 -=== 2.4.6  Alarm ===
411 +Distance between sensor probe to the second object. (unit: cm)
458 458  
459 459  
460 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
414 +=== 2.4.6  Timestamp ===
461 461  
462 462  
463 -
464 -=== 2.4.7  Contact Status ===
465 -
466 -
467 -0: Open
468 -
469 -1: Close
470 -
471 -
472 -
473 -=== 2.4.8  Total pulse ===
474 -
475 -
476 -Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
477 -
478 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
479 -
480 -
481 -
482 -=== 2.4.9  The last open duration ===
483 -
484 -
485 -Dry Contact last open duration.
486 -
487 -Unit: min.
488 -
489 -[[image:image-20221021111346-17.png||height="146" width="770"]]
490 -
491 -
492 -
493 -=== 2.4.10  Timestamp ===
494 -
495 -
496 496  Timestamp : 0x6315537b =1662342011
497 497  
498 -Convert Unix timestamp to time 2022-9-5 9:40:11.
499 499  
500 -**~ **
501 -
502 -
503 503  == 2.5  Downlink Payload ==
504 504  
505 505  
506 -By default, CPN01 prints the downlink payload to console port.
423 +By default, NMDS200 prints the downlink payload to console port.
507 507  
508 508  [[image:image-20221021111414-18.png]] ​
509 509  
... ... @@ -520,7 +520,7 @@
520 520  
521 521  * (% style="color:#037691" %)**Reset**
522 522  
523 -If payload = 0x04FF, it will reset the NSE01
440 +If payload = 0x04FF, it will reset the NMDS200
524 524  
525 525  * (% style="color:#037691" %)**INTMOD**
526 526  
... ... @@ -527,117 +527,47 @@
527 527  Downlink Payload: 06000003, Set AT+INTMOD=3
528 528  
529 529  
530 -
531 531  == 2.6  ​LED Indicator ==
532 532  
533 533  
534 -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.
535 535  
536 536  * When the device starts normally, the LED will light up for 1 second.
537 -* 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.
538 538  * For each uplink probe, LED will be on for 500ms.
539 539  
540 540  
541 541  
542 -== 2.7  Alarm Base on Timeout ==
458 +== 2.7  Distance alarm function ==
543 543  
544 544  
545 -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:
461 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
546 546  
463 +**Example 1:**
547 547  
548 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
465 +AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
549 549  
550 -Keep Status = 1: Monitor Close to Open event
467 +AT+ ALARM2 =min,max
551 551  
552 -Keep Status = 0: Monitor Open to Close event
553 553  
470 +**Example 2:**
554 554  
555 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
472 +AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
556 556  
557 -Range 0 ~~ 65535(0xFFFF) seconds.
558 558  
559 -If keep time = 0, Disable Alarm Base on Timeout feature.
475 +== 2.8  Set the number of data to be uploaded and the recording time ==
560 560  
561 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
562 562  
563 -
564 -(% style="color:blue" %)**AT Command to configure:**
565 -
566 -(% 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.
567 -
568 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
569 -
570 -
571 -
572 -== 2.8  Set debug mode ==
573 -
574 -
575 -Feature: Enable or Disable debug mode
576 -
577 -(% style="color:blue" %)**AT Command: AT+DEBUG**
578 -
579 -[[image:image-20221021111629-21.png]]
580 -
581 -
582 -
583 -== 2.9  Clear Flash Record ==
584 -
585 -
586 -Feature: Clear flash storage for data log feature.
587 -
588 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
589 -
590 -[[image:image-20221021111527-19.png]]
591 -
592 -
593 -
594 -== 2.10  Set trigger mode ==
595 -
596 -
597 -(% style="color:blue" %)**AT Command: AT+TTRMOD**
598 -
599 -Feature: Set the trigger interrupt mode.
600 -
601 -[[image:image-20221021111552-20.png]]
602 -
603 -
604 -
605 -== 2.11  Set the calculate flag ==
606 -
607 -
608 -Feature: Set the calculate flag
609 -
610 -(% style="color:blue" %)**AT Command: AT+CALCFLAG**
611 -
612 -[[image:image-20221021111711-22.png]]
613 -
614 -
615 -
616 -== 2.12 Set count number ==
617 -
618 -
619 -Feature: Manually set the count number
620 -
621 -(% style="color:blue" %)**AT Command: AT+SETCNT**
622 -
623 -[[image:image-20221021111748-24.png]]
624 -
625 -
626 -
627 -== 2.13  Set the number of data to be uploaded and the recording time ==
628 -
629 -
630 630  (% style="color:blue" %)**AT Command:**
631 631  
632 -(% 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)
480 +(% 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)
633 633  
634 -(% 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.
482 +(% 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.
635 635  
636 636  
485 +== 2.9  Read or Clear cached data ==
637 637  
638 -== 2.14  Read or Clear cached data ==
639 639  
640 -
641 641  (% style="color:blue" %)**AT Command:**
642 642  
643 643  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -644,27 +644,24 @@
644 644  
645 645  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
646 646  
647 -[[image:image-20221021111810-25.png||height="364" width="797"]]
494 +[[image:1670408172929-569.png]]
648 648  
649 649  
497 +== 2.10  ​Firmware Change Log ==
650 650  
651 -== 2.15  ​Firmware Change Log ==
652 652  
500 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
653 653  
654 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
655 -
656 656  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
657 657  
658 658  
505 +== 2.11  ​Battery Analysis ==
659 659  
660 -== 2.16  ​Battery Analysis ==
507 +=== 2.11.1  ​Battery Type ===
661 661  
662 662  
663 -=== 2.16.1  ​Battery Type ===
510 +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.
664 664  
665 -
666 -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.
667 -
668 668  The battery is designed to last for several years depends on the actual use environment and update interval. 
669 669  
670 670  The battery-related documents as below:
... ... @@ -678,10 +678,9 @@
678 678  [[image:image-20221021111911-26.png]] ​
679 679  
680 680  
525 +=== 2.11.2  Power consumption Analyze ===
681 681  
682 -=== 2.16.2  Power consumption Analyze ===
683 683  
684 -
685 685  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.
686 686  
687 687  Instruction to use as below:
... ... @@ -701,21 +701,18 @@
701 701  [[image:1666596205057-567.png]] ​
702 702  
703 703  
547 +=== 2.11.3  ​Battery Note ===
704 704  
705 -=== 2.16.3  ​Battery Note ===
706 706  
707 -
708 708  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.
709 709  
710 710  
553 +=== 2.11.4  Replace the battery ===
711 711  
712 -=== 2.16.4  Replace the battery ===
713 713  
556 +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 714  
715 -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).
716 716  
717 -
718 -
719 719  = 3. ​ Access NB-IoT Module =
720 720  
721 721  
... ... @@ -723,13 +723,12 @@
723 723  
724 724  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/]] 
725 725  
726 -[[image:image-20221021112006-28.png]] ​
727 727  
567 +[[image:image-20221118094449-6.png]] ​
728 728  
729 729  
730 730  = 4.  Using the AT Commands =
731 731  
732 -
733 733  == 4.1  Access AT Commands ==
734 734  
735 735  
... ... @@ -776,15 +776,21 @@
776 776  
777 777  AT+ DEBUG   : Enable or Disable debug mode
778 778  
779 -AT+ TTRIG   : Get or Set Alarm Base on Timeout
618 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
780 780  
781 -AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
620 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
782 782  
783 -AT+ CALCFLAG   : Get or Set the calculate flag
622 +AT+COUNTMOD  :  Get or Set the count mode
784 784  
785 -AT+ CLRC   : Clear current door open count
624 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
786 786  
626 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
787 787  
628 +AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
629 +
630 +AT+ CLRC   :  Clear current door open count
631 +
632 +
788 788  (% style="color:blue" %)**COAP Management**      
789 789  
790 790  AT+URI            : Resource parameters
... ... @@ -815,10 +815,8 @@
815 815  AT+PWORD  : Serial Access Password
816 816  
817 817  
818 -
819 819  = ​5.  FAQ =
820 820  
821 -
822 822  == 5.1 ​ How to Upgrade Firmware ==
823 823  
824 824  
... ... @@ -826,13 +826,11 @@
826 826  
827 827  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]]
828 828  
829 -(% 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.**
672 +(% 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.**
830 830  
831 831  
832 -
833 833  = 6.  Trouble Shooting =
834 834  
835 -
836 836  == 6.1  ​Connection problem when uploading firmware ==
837 837  
838 838  
... ... @@ -839,7 +839,6 @@
839 839  (% 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]]
840 840  
841 841  
842 -
843 843  == 6.2  AT Command input doesn't work ==
844 844  
845 845  
... ... @@ -846,29 +846,19 @@
846 846  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.
847 847  
848 848  
849 -
850 850  = 7. ​ Order Info =
851 851  
852 852  
853 -Part Number**:** CPN01
692 +Part Number**:** NDS03A
854 854  
855 855  
856 -
857 857  = 8.  Packing Info =
858 858  
859 859  
860 860  (% style="color:blue" %)**Package Includes**:
861 861  
862 -* CPN01 Open/Close Sensor x 1
863 -* External antenna x 1
700 +* NDS03A Open/Close Door Sensor x 1
864 864  
865 -(% style="color:blue" %)**Dimension and weight**:
866 -
867 -* Size: 195 x 125 x 55 mm
868 -* Weight:   420g
869 -
870 -
871 -
872 872  = 9.  Support =
873 873  
874 874  
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
1670408172929-569.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +211.8 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