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