Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 58.3 >
edited by Xiaoling
on 2022/11/17 13:52
To version < 81.2 >
edited by Xiaoling
on 2022/12/07 18:05
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
1 +NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
Content
... ... @@ -1,12 +1,7 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20221117105556-1.png]]
2 +[[image:LMDS200_10.jpg]]
3 3  
4 4  
5 -
6 -
7 -
8 -
9 -
10 10  **Table of Contents：**
11 11  
12 12  
... ... @@ -15,40 +15,26 @@
15 15  
16 16  = 1.  Introduction =
17 17  
13 +== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
18 18  
19 -== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
20 20  
21 -
22 22  (((
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 -)))
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.
25 25  
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 -)))
29 29  
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 -)))
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.
33 33  
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 -)))
22 +NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
37 37  
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 -)))
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.
41 41  
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 -)))
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.
45 45  
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 -)))
28 +NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
49 49  
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.
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.
52 52  )))
53 53  
54 54  
... ... @@ -57,10 +57,9 @@
57 57  
58 58  
59 59  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
60 -* Open/Close detect
61 -* Open/Close statistics
41 +* Short uplink interval for Distance Alarm
62 62  * Monitor Battery Level
63 -* connect two door sensors
43 +* Microwave Radar for distance detection
64 64  * Datalog feature
65 65  * Uplink periodically
66 66  * Downlink to change configure
... ... @@ -72,35 +72,42 @@
72 72  * 8500mAh Battery for long-term use
73 73  
74 74  
55 +== 1.3 Radar probe specification ==
75 75  
76 76  
77 -== 1.3  Storage & Operation ==
58 +* Measuring Method: FMCW
59 +* Frequency: 24.000 24.500 GHz
60 +* Measurement output power: 6dBm
61 +* Measure range: 0.5 20m
62 +* Accuracy: ±0.1m
63 +* Resolution: 0.01m
64 +* Horizontal Angel: 78°
65 +* Vertical Angel: 23°
78 78  
79 79  
80 -Temperature -40°C to +85°C
81 81  
69 +== 1.4  Storage Temperature ==
82 82  
83 -== 1.4  Mechanical ==
84 84  
72 + -40°C to +85°C
85 85  
86 -[[image:image-20221117114937-4.png]]
87 87  
88 88  
89 -[[image:image-20221117114949-5.png]]
90 90  
91 91  
92 -[[image:image-20221117115010-6.png]]
93 -
94 -
95 -
96 -
97 -
98 -
99 99  == 1.5 ​ Applications ==
100 100  
101 101  
102 -[[image:image-20221117114842-3.png]]
103 103  
82 +* Horizontal distance measurement
83 +* Liquid level measurement
84 +* Parking management system
85 +* Object proximity and presence detection
86 +* Intelligent trash can management system
87 +* Robot obstacle avoidance
88 +* Automatic control
89 +* Sewer
90 +* Bottom water level monitoring
104 104  
105 105  
106 106  == 1.6  Specification ==
... ... @@ -109,111 +109,63 @@
109 109  (% style="color:blue" %)**Common DC Characteristics:**
110 110  
111 111  * Supply Voltage: 2.1v ~~ 3.6v
112 -* Operating Temperature: -40 ~~ 85°C
99 +* Operating Temperature: 0 ~~ 70°C
113 113  
114 114  (% style="color:blue" %)**NB-IoT Spec:**
115 115  
116 -* - B1 @H-FDD: 2100MHz
117 -* - B3 @H-FDD: 1800MHz
118 -* - B8 @H-FDD: 900MHz
119 -* - B5 @H-FDD: 850MHz
120 -* - B20 @H-FDD: 800MHz
121 -* - B28 @H-FDD: 700MHz
103 +* B1 @H-FDD: 2100MHz
104 +* B3 @H-FDD: 1800MHz
105 +* B8 @H-FDD: 900MHz
106 +* B5 @H-FDD: 850MHz
107 +* B20 @H-FDD: 800MHz
108 +* B28 @H-FDD: 700MHz
122 122  
123 123  
111 +== 1.7  Installation ==
124 124  
125 -== 1.7  Pin Definitions and Switch ==
126 126  
114 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
127 127  
128 -[[image:image-20221021110429-4.png]]
129 129  
117 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
130 130  
131 -=== 1.7.1  Pin Definition ===
132 132  
133 133  
134 -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]]**.
121 +== 1.8  Pin Definitions and Switch ==
135 135  
136 136  
124 +[[image:1670404362039-351.png]]
137 137  
138 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
139 139  
127 += 2.  Use NMDS200 to communicate with IoT Server =
140 140  
141 -Power on Device when putting this jumper.
142 -
143 -
144 -
145 -=== 1.7.3  BOOT MODE / SW1 ===
146 -
147 -
148 -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.
149 -
150 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
151 -
152 -
153 -
154 -=== 1.7.4  Reset Button ===
155 -
156 -
157 -Press to reboot the device.
158 -
159 -
160 -
161 -=== 1.7.5  LED ===
162 -
163 -
164 -The LED will blink when :
165 -
166 -1.  Boot the device in flash mode
167 -
168 -2.  Send an uplink packet
169 -
170 -
171 -
172 -== 1.8  Magnet Distance ==
173 -
174 -
175 -**Wood Door:** 10 ~~ 30mm
176 -
177 -**Iron Door:  **30 ~~ 45mm
178 -
179 -
180 -
181 -= 2.  Use CPN01 to communicate with IoT Server =
182 -
183 -
184 184  == 2.1  How it works ==
185 185  
186 186  
187 -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.
132 +The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
188 188  
189 -The diagram below shows the working flow in the default firmware of CPN01:
134 +The diagram below shows the working flow in the default firmware of NMDS200:
190 190  
191 191  [[image:image-20221021110615-5.png]]
192 192  
193 193  
139 +== 2.2 ​ Configure NMDS200 ==
194 194  
195 -== 2.2 ​ Configure CPN01 ==
196 196  
142 +To use NMDS200 in your city, make sure to meet below requirements:
197 197  
198 -=== 2.2.1 Test Requirement ===
199 -
200 -
201 -To use CPN01 in your city, make sure to meet below requirements:
202 -
203 203  * Your local operator has already distributed an NB-IoT Network.
204 -* The local NB-IoT network used the band that CPN01 supports.
145 +* The local NB-IoT network used the band that NMDS200 supports.
205 205  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
206 206  
207 -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.
148 +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.
208 208  
209 -[[image:image-20221023000439-3.png]]
150 +[[image:image-20221207173300-4.png]]
210 210  
211 - ​
212 212  
153 +=== 2.2.1 Insert NB-IoT SIM card ===
213 213  
214 -=== 2.2.2 Insert NB-IoT SIM card ===
215 215  
216 -
217 217  Insert the NB-IoT Card get from your provider.
218 218  
219 219  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -221,12 +221,11 @@
221 221  [[image:image-20221021110745-6.png]] ​
222 222  
223 223  
163 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
224 224  
225 -=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
226 226  
166 +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.
227 227  
228 -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.
229 -
230 230  (% style="color:blue" %)**Connection:**
231 231  
232 232  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -248,11 +248,11 @@
248 248  
249 249  * Flow Control: (% style="color:red" %)**None**
250 250  
251 -Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
189 +Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
252 252  
253 253  ​[[image:image-20221021110817-7.png]]
254 254  
255 -CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
193 +NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
256 256  
257 257  
258 258  (% 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]]
... ... @@ -259,13 +259,13 @@
259 259  
260 260  
261 261  
262 -=== 2.2.4 Use CoAP protocol to uplink data ===
200 +=== 2.2.3 Use CoAP protocol to uplink data ===
263 263  
264 264  
265 265  (% 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/]]
266 266  
267 267  
268 -(% style="color:blue" %)**Use below commands in CPN01:**
206 +(% style="color:blue" %)**Use below commands in NDS03A:**
269 269  
270 270  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
271 271  
... ... @@ -278,15 +278,14 @@
278 278  [[image:image-20221021110948-8.png]]
279 279  
280 280  
281 -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.
219 +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.
282 282  
283 -[[image:image-20221021110956-9.png]] ​
221 +[[image:1670405841875-916.png]] ​
284 284  
285 285  
224 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
286 286  
287 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
288 288  
289 -
290 290  (% style="color:blue" %)**AT Commands:**
291 291  
292 292  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -302,10 +302,9 @@
302 302  
303 303  ​
304 304  
242 +=== 2.2.5 Use MQTT protocol to uplink data ===
305 305  
306 -=== 2.2.6 Use MQTT protocol to uplink data ===
307 307  
308 -
309 309  (% style="color:blue" %)**AT Commands:**
310 310  
311 311  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -322,10 +322,10 @@
322 322  
323 323  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
324 324  
325 -​ [[image:image-20221021111058-12.png]]
261 +​ [[image:image-20221118103445-7.png]]
326 326  
327 327  
328 -[[image:image-20221021111201-16.png||height="472" width="653"]]
264 +[[image:1670405928926-116.png]]
329 329  
330 330  ​
331 331  
... ... @@ -332,10 +332,9 @@
332 332  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.
333 333  
334 334  
271 +=== 2.2.6 Use TCP protocol to uplink data ===
335 335  
336 -=== 2.2.7 Use TCP protocol to uplink data ===
337 337  
338 -
339 339  (% style="color:blue" %)**AT Commands:**
340 340  
341 341  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -342,82 +342,76 @@
342 342  
343 343  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
344 344  
345 -​ [[image:image-20221021111125-14.png]]
280 +​ [[image:1670406036256-101.png||height="676" width="713"]]
346 346  
282 +
347 347  [[image:image-20221021111131-15.png]]
348 348  
349 349  ​
350 350  
287 +=== 2.2.7 Change Update Interval ===
351 351  
352 -=== 2.2.8 Change Update Interval ===
353 353  
354 -
355 355  User can use below command to change the (% style="color:blue" %)**uplink interval**.
356 356  
357 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
292 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
358 358  
359 359  (% style="color:red" %)**NOTE:**
360 360  
361 -1.  By default, the device will send an uplink message every 1 hour.
296 +1.  By default, the device will send an uplink message every 4 hour.
362 362  
363 363  
364 -
365 365  == 2.3  Uplink Payload ==
366 366  
367 367  
368 -The uplink payload includes 123 bytes in total by default.
302 +The uplink payload includes 23 bytes in total by default.
369 369  
370 -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.
304 +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.
371 371  
372 372  
373 -(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
374 -|=(% 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**
375 -|=(% 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"]]
307 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
308 +|=(% 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**
309 +|=(% 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
376 376  
377 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
378 -|(% 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**
379 -|(% 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" %)...
311 +(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
312 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
313 +**1-32 group**
314 +)))
315 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
380 380  
381 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
317 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
382 382  
383 -[[image:image-20221021111201-16.png||height="572" width="792"]]
319 +[[image:1670406261143-723.png]]
384 384  
385 385  
386 -The payload is ASCII string, representative same HEX:
322 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
387 387  
388 -**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 __**
324 +**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__(%%)**
389 389  
390 390  **where:**
391 391  
392 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
328 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
393 393  
394 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
330 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
395 395  
396 -* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
332 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
397 397  
398 -* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
334 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
399 399  
400 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
336 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
401 401  
402 -* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
338 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
403 403  
404 -* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
340 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
405 405  
406 -* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
342 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
407 407  
408 -* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
344 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
409 409  
410 -* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
411 411  
412 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
413 413  
414 -* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
415 -
416 -* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
417 -
418 418  == 2.4  Payload Explanation and Sensor Interface ==
419 419  
420 -
421 421  === 2.4.1  Device ID ===
422 422  
423 423  
... ... @@ -432,20 +432,18 @@
432 432  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
433 433  
434 434  
435 -
436 436  === 2.4.2  Version Info ===
437 437  
438 438  
439 439  Specify the software version: 0x64=100, which means firmware version 1.00.
440 440  
441 -For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
369 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
442 442  
443 443  
444 -
445 445  === 2.4.3  Battery Info ===
446 446  
447 447  
448 -Check the battery voltage for CPN01.
375 +Check the battery voltage for NMDS200.
449 449  
450 450  Ex1: 0x0B45 = 2885mV
451 451  
... ... @@ -452,7 +452,6 @@
452 452  Ex2: 0x0B49 = 2889mV
453 453  
454 454  
455 -
456 456  === 2.4.4  Signal Strength ===
457 457  
458 458  
... ... @@ -471,70 +471,35 @@
471 471  **99**    Not known or not detectable
472 472  
473 473  
400 +=== 2.4.5  Distance ===
474 474  
475 -=== 2.4.5  Calculate Flag ===
476 476  
403 +[[image:1670407401682-959.png]]
477 477  
478 -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.
405 +**(% style="color:blue" %)Object1 Distance:**
479 479  
480 -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.
407 +Distance between sensor probe to the first object. (unit: cm)
481 481  
482 -Default value: 0. 
409 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
483 483  
484 -Range (6 bits): (b)000000 ~~ (b) 111111
411 +**(% style="color:blue" %)0205(H) = 517 (D) = 517 cm.**
485 485  
486 486  
414 +**(% style="color:blue" %)Object2 Distance:**
487 487  
488 -=== 2.4.6  Alarm ===
416 +Distance between sensor probe to the second object. (unit: cm)
489 489  
490 490  
491 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
419 +=== 2.4.6  Timestamp ===
492 492  
493 493  
494 -
495 -=== 2.4.7  Contact Status ===
496 -
497 -
498 -0: Open
499 -
500 -1: Close
501 -
502 -
503 -
504 -=== 2.4.8  Total pulse ===
505 -
506 -
507 -Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
508 -
509 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
510 -
511 -
512 -
513 -=== 2.4.9  The last open duration ===
514 -
515 -
516 -Dry Contact last open duration.
517 -
518 -Unit: min.
519 -
520 -[[image:image-20221021111346-17.png||height="146" width="770"]]
521 -
522 -
523 -
524 -=== 2.4.10  Timestamp ===
525 -
526 -
527 527  Timestamp : 0x6315537b =1662342011
528 528  
529 -Convert Unix timestamp to time 2022-9-5 9:40:11.
530 530  
531 -**~ **
532 -
533 -
534 534  == 2.5  Downlink Payload ==
535 535  
536 536  
537 -By default, CPN01 prints the downlink payload to console port.
428 +By default, NDS03A prints the downlink payload to console port.
538 538  
539 539  [[image:image-20221021111414-18.png]] ​
540 540  
... ... @@ -551,7 +551,7 @@
551 551  
552 552  * (% style="color:#037691" %)**Reset**
553 553  
554 -If payload = 0x04FF, it will reset the NSE01
445 +If payload = 0x04FF, it will reset the NDS03A
555 555  
556 556  * (% style="color:#037691" %)**INTMOD**
557 557  
... ... @@ -558,20 +558,19 @@
558 558  Downlink Payload: 06000003, Set AT+INTMOD=3
559 559  
560 560  
561 -
562 562  == 2.6  ​LED Indicator ==
563 563  
564 564  
565 -The CPN01 has an internal LED which is to show the status of different states.
455 +The NDS03A has an internal LED which is to show the status of different states.
566 566  
567 567  * When the device starts normally, the LED will light up for 1 second.
568 -* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
458 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
569 569  * For each uplink probe, LED will be on for 500ms.
570 570  
571 571  == 2.7  Alarm Base on Timeout ==
572 572  
573 573  
574 -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:
464 +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:
575 575  
576 576  
577 577  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -587,17 +587,25 @@
587 587  
588 588  If keep time = 0, Disable Alarm Base on Timeout feature.
589 589  
590 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
480 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
591 591  
592 592  
593 593  (% style="color:blue" %)**AT Command to configure:**
594 594  
595 -(% 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.
485 +(% style="color:blue" %)**PB14 PIN:**
596 596  
487 +(% 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.
488 +
597 597  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
598 598  
599 599  
492 +(% style="color:blue" %)**PB15 PIN:**
600 600  
494 +(% style="color:#037691" %)**AT+TTRIG2=1,30**
495 +
496 +(% style="color:#037691" %)**AT+TTRIG2=0,0 **
497 +
498 +
601 601  == 2.8  Set debug mode ==
602 602  
603 603  
... ... @@ -619,54 +619,57 @@
619 619  [[image:image-20221021111527-19.png]]
620 620  
621 621  
520 +== 2.10  Count Mod ==
622 622  
623 -== 2.10  Set trigger mode ==
624 624  
523 +(% style="color:blue" %)**AT Command: AT+COUNTMOD**
625 625  
626 -(% style="color:blue" %)**AT Command: AT+TTRMOD**
525 +[[image:image-20221118092935-1.png]]
627 627  
628 -Feature: Set the trigger interrupt mode.
629 629  
630 -[[image:image-20221021111552-20.png]]
528 +== 2.11  Interrupt Pin Channel Mod ==
631 631  
632 632  
531 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
633 633  
634 -== 2.11  Set the calculate flag ==
533 +[[image:image-20221118093144-2.png]]
635 635  
636 636  
637 -Feature: Set the calculate flag
536 +== 2.12 TTRIG1/2 timeout status alarm ==
638 638  
639 -(% style="color:blue" %)**AT Command: AT+CALCFLAG**
640 640  
641 -[[image:image-20221021111711-22.png]]
539 +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.
642 642  
541 +(% style="color:blue" %)**AT Command: AT+TTRALARM**
643 643  
543 +[[image:image-20221118093512-3.png]]
644 644  
645 -== 2.12 Set count number ==
646 646  
546 +== 2.13  Select counting mode ==
647 647  
648 -Feature: Manually set the count number
649 649  
650 -(% style="color:blue" %)**AT Command: AT+SETCNT**
549 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
651 651  
652 -[[image:image-20221021111748-24.png]]
551 +When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
653 653  
553 +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.
654 654  
555 +[[image:image-20221118093658-4.png]]
655 655  
656 -== 2.13  Set the number of data to be uploaded and the recording time ==
657 657  
558 +== 2.14  Set the number of data to be uploaded and the recording time ==
658 658  
560 +
659 659  (% style="color:blue" %)**AT Command:**
660 660  
661 -(% 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)
563 +(% 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)
662 662  
663 -(% 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.
565 +(% 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.
664 664  
665 665  
568 +== 2.15  Read or Clear cached data ==
666 666  
667 -== 2.14  Read or Clear cached data ==
668 668  
669 -
670 670  (% style="color:blue" %)**AT Command:**
671 671  
672 672  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -673,27 +673,24 @@
673 673  
674 674  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
675 675  
676 -[[image:image-20221021111810-25.png||height="364" width="797"]]
577 +[[image:image-20221118094227-5.png]]
677 677  
678 678  
580 +== 2.16  ​Firmware Change Log ==
679 679  
680 -== 2.15  ​Firmware Change Log ==
681 681  
583 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
682 682  
683 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
684 -
685 685  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
686 686  
687 687  
588 +== 2.17  ​Battery Analysis ==
688 688  
689 -== 2.16  ​Battery Analysis ==
590 +=== 2.17.1  ​Battery Type ===
690 690  
691 691  
692 -=== 2.16.1  ​Battery Type ===
593 +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.
693 693  
694 -
695 -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.
696 -
697 697  The battery is designed to last for several years depends on the actual use environment and update interval. 
698 698  
699 699  The battery-related documents as below:
... ... @@ -707,10 +707,9 @@
707 707  [[image:image-20221021111911-26.png]] ​
708 708  
709 709  
608 +=== 2.17.2  Power consumption Analyze ===
710 710  
711 -=== 2.16.2  Power consumption Analyze ===
712 712  
713 -
714 714  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.
715 715  
716 716  Instruction to use as below:
... ... @@ -730,21 +730,18 @@
730 730  [[image:1666596205057-567.png]] ​
731 731  
732 732  
630 +=== 2.17.3  ​Battery Note ===
733 733  
734 -=== 2.16.3  ​Battery Note ===
735 735  
736 -
737 737  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.
738 738  
739 739  
636 +=== 2.17.4  Replace the battery ===
740 740  
741 -=== 2.16.4  Replace the battery ===
742 742  
639 +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).
743 743  
744 -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).
745 745  
746 -
747 -
748 748  = 3. ​ Access NB-IoT Module =
749 749  
750 750  
... ... @@ -752,13 +752,12 @@
752 752  
753 753  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/]] 
754 754  
755 -[[image:image-20221021112006-28.png]] ​
756 756  
650 +[[image:image-20221118094449-6.png]] ​
757 757  
758 758  
759 759  = 4.  Using the AT Commands =
760 760  
761 -
762 762  == 4.1  Access AT Commands ==
763 763  
764 764  
... ... @@ -805,15 +805,21 @@
805 805  
806 806  AT+ DEBUG   : Enable or Disable debug mode
807 807  
808 -AT+ TTRIG   : Get or Set Alarm Base on Timeout
701 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
809 809  
810 -AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
703 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
811 811  
812 -AT+ CALCFLAG   : Get or Set the calculate flag
705 +AT+COUNTMOD  :  Get or Set the count mode
813 813  
814 -AT+ CLRC   : Clear current door open count
707 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
815 815  
709 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
816 816  
711 +AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
712 +
713 +AT+ CLRC   :  Clear current door open count
714 +
715 +
817 817  (% style="color:blue" %)**COAP Management**      
818 818  
819 819  AT+URI            : Resource parameters
... ... @@ -844,10 +844,8 @@
844 844  AT+PWORD  : Serial Access Password
845 845  
846 846  
847 -
848 848  = ​5.  FAQ =
849 849  
850 -
851 851  == 5.1 ​ How to Upgrade Firmware ==
852 852  
853 853  
... ... @@ -855,13 +855,11 @@
855 855  
856 856  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]]
857 857  
858 -(% 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.**
755 +(% 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.**
859 859  
860 860  
861 -
862 862  = 6.  Trouble Shooting =
863 863  
864 -
865 865  == 6.1  ​Connection problem when uploading firmware ==
866 866  
867 867  
... ... @@ -868,7 +868,6 @@
868 868  (% 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]]
869 869  
870 870  
871 -
872 872  == 6.2  AT Command input doesn't work ==
873 873  
874 874  
... ... @@ -875,27 +875,19 @@
875 875  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.
876 876  
877 877  
878 -
879 879  = 7. ​ Order Info =
880 880  
881 881  
882 -Part Number**:** CPN01
775 +Part Number**:** NDS03A
883 883  
884 884  
885 -
886 886  = 8.  Packing Info =
887 887  
888 888  
889 889  (% style="color:blue" %)**Package Includes**:
890 890  
891 -* CPN01 Open/Close Sensor x 1
892 -* External antenna x 1
783 +* NDS03A Open/Close Door Sensor x 1
893 893  
894 -(% style="color:blue" %)**Dimension and weight**:
895 -
896 -* Size: 195 x 125 x 55 mm
897 -* Weight:   420g
898 -
899 899  = 9.  Support =
900 900  
901 901  
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-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