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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
1 +NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
Content
... ... @@ -1,7 +1,12 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg]]
2 +[[image:image-20221117105556-1.png]]
3 3  
4 4  
5 +
6 +
7 +
8 +
9 +
5 5  **Table of Contents：**
6 6  
7 7  
... ... @@ -10,26 +10,40 @@
10 10  
11 11  = 1.  Introduction =
12 12  
13 -== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
14 14  
19 +== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
15 15  
21 +
16 16  (((
17 -The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor.
23 +The Dragino NDS03A is an (% style="color:blue" %)**Open/Close NB-IoT Door Sensor**(%%). It detects door (% style="color:blue" %)**open/close status**(%%) and (% style="color:blue" %)**uplinks**(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server.
24 +)))
18 18  
26 +(((
27 +The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically.
28 +)))
19 19  
20 -The NMDS200 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
30 +(((
31 +NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT.
32 +)))
21 21  
22 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
34 +(((
35 +NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time.
36 +)))
23 23  
24 -NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range.
38 +(((
39 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
40 +)))
25 25  
26 -NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technology**(%%) developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
42 +(((
43 +NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technologyTCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
44 +)))
27 27  
28 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
46 +(((
47 +NDS03A is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
48 +)))
29 29  
30 -NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
31 -
32 -To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection.
50 +(((
51 +To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection.
33 33  )))
34 34  
35 35  
... ... @@ -38,9 +38,10 @@
38 38  
39 39  
40 40  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
41 -* Short uplink interval for Distance Alarm
60 +* Open/Close detect
61 +* Open/Close statistics
42 42  * Monitor Battery Level
43 -* Microwave Radar for distance detection
63 +* connect two door sensors
44 44  * Datalog feature
45 45  * Uplink periodically
46 46  * Downlink to change configure
... ... @@ -52,42 +52,31 @@
52 52  * 8500mAh Battery for long-term use
53 53  
54 54  
55 -== 1.3 Radar probe specification ==
56 56  
76 +== 1.3  Storage & Operation ==
57 57  
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°
66 66  
79 +Temperature -40°C to +85°C
67 67  
68 68  
69 -== 1.4  Storage Temperature ==
82 +== 1.4  Mechanical ==
70 70  
71 71  
72 - -40°C to +85°C
85 +[[image:image-20221117114937-4.png]]
73 73  
74 74  
88 +[[image:image-20221117114949-5.png]]
75 75  
76 76  
91 +[[image:image-20221117115010-6.png]]
77 77  
93 +
94 +
78 78  == 1.5 ​ Applications ==
79 79  
80 80  
98 +[[image:image-20221117114842-3.png]]
81 81  
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
91 91  
92 92  
93 93  == 1.6  Specification ==
... ... @@ -96,63 +96,111 @@
96 96  (% style="color:blue" %)**Common DC Characteristics:**
97 97  
98 98  * Supply Voltage: 2.1v ~~ 3.6v
99 -* Operating Temperature: 0 ~~ 70°C
108 +* Operating Temperature: -40 ~~ 85°C
100 100  
101 101  (% style="color:blue" %)**NB-IoT Spec:**
102 102  
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
112 +* - B1 @H-FDD: 2100MHz
113 +* - B3 @H-FDD: 1800MHz
114 +* - B8 @H-FDD: 900MHz
115 +* - B5 @H-FDD: 850MHz
116 +* - B20 @H-FDD: 800MHz
117 +* - B28 @H-FDD: 700MHz
109 109  
110 110  
111 -== 1.7  Installation ==
112 112  
121 +== 1.7  Pin Definitions and Switch ==
113 113  
114 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
115 115  
124 +[[image:image-20221021110429-4.png]]
116 116  
117 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
118 118  
127 +=== 1.7.1  Pin Definition ===
119 119  
120 120  
121 -== 1.8  Pin Definitions and Switch ==
130 +The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at:  [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
122 122  
123 123  
124 -[[image:1670404362039-351.png]]
125 125  
134 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
126 126  
127 -= 2.  Use NMDS200 to communicate with IoT Server =
128 128  
137 +Power on Device when putting this jumper.
138 +
139 +
140 +
141 +=== 1.7.3  BOOT MODE / SW1 ===
142 +
143 +
144 +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.
145 +
146 +2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
147 +
148 +
149 +
150 +=== 1.7.4  Reset Button ===
151 +
152 +
153 +Press to reboot the device.
154 +
155 +
156 +
157 +=== 1.7.5  LED ===
158 +
159 +
160 +The LED will blink when :
161 +
162 +1.  Boot the device in flash mode
163 +
164 +2.  Send an uplink packet
165 +
166 +
167 +
168 +== 1.8  Magnet Distance ==
169 +
170 +
171 +(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
172 +
173 +(% style="color:blue" %)**Iron Door:**(%%)**  **30 ~~ 45mm
174 +
175 +
176 +
177 += 2.  Use CPN01 to communicate with IoT Server =
178 +
179 +
129 129  == 2.1  How it works ==
130 130  
131 131  
132 -The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
183 +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.
133 133  
134 -The diagram below shows the working flow in the default firmware of NMDS200:
185 +The diagram below shows the working flow in the default firmware of CPN01:
135 135  
136 136  [[image:image-20221021110615-5.png]]
137 137  
138 138  
139 -== 2.2 ​ Configure NMDS200 ==
140 140  
191 +== 2.2 ​ Configure CPN01 ==
141 141  
142 -To use NMDS200 in your city, make sure to meet below requirements:
143 143  
194 +=== 2.2.1 Test Requirement ===
195 +
196 +
197 +To use CPN01 in your city, make sure to meet below requirements:
198 +
144 144  * Your local operator has already distributed an NB-IoT Network.
145 -* The local NB-IoT network used the band that NMDS200 supports.
200 +* The local NB-IoT network used the band that CPN01 supports.
146 146  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
147 147  
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.
203 +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.
149 149  
150 -[[image:image-20221207173300-4.png]]
205 +[[image:image-20221023000439-3.png]]
151 151  
207 + ​
152 152  
153 -=== 2.2.1 Insert NB-IoT SIM card ===
154 154  
210 +=== 2.2.2 Insert NB-IoT SIM card ===
155 155  
212 +
156 156  Insert the NB-IoT Card get from your provider.
157 157  
158 158  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -160,11 +160,12 @@
160 160  [[image:image-20221021110745-6.png]] ​
161 161  
162 162  
163 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
164 164  
221 +=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
165 165  
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.
167 167  
224 +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.
225 +
168 168  (% style="color:blue" %)**Connection:**
169 169  
170 170  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -186,11 +186,11 @@
186 186  
187 187  * Flow Control: (% style="color:red" %)**None**
188 188  
189 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
247 +Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
190 190  
191 191  ​[[image:image-20221021110817-7.png]]
192 192  
193 -NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
251 +CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
194 194  
195 195  
196 196  (% 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]]
... ... @@ -197,13 +197,13 @@
197 197  
198 198  
199 199  
200 -=== 2.2.3 Use CoAP protocol to uplink data ===
258 +=== 2.2.4 Use CoAP protocol to uplink data ===
201 201  
202 202  
203 203  (% 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/]]
204 204  
205 205  
206 -(% style="color:blue" %)**Use below commands in NDS03A:**
264 +(% style="color:blue" %)**Use below commands in CPN01:**
207 207  
208 208  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
209 209  
... ... @@ -216,14 +216,15 @@
216 216  [[image:image-20221021110948-8.png]]
217 217  
218 218  
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.
277 +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.
220 220  
221 -[[image:1670405841875-916.png]] ​
279 +[[image:image-20221021110956-9.png]] ​
222 222  
223 223  
224 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
225 225  
283 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
226 226  
285 +
227 227  (% style="color:blue" %)**AT Commands:**
228 228  
229 229  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -239,9 +239,10 @@
239 239  
240 240  ​
241 241  
242 -=== 2.2.5 Use MQTT protocol to uplink data ===
243 243  
302 +=== 2.2.6 Use MQTT protocol to uplink data ===
244 244  
304 +
245 245  (% style="color:blue" %)**AT Commands:**
246 246  
247 247  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -258,10 +258,10 @@
258 258  
259 259  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
260 260  
261 -​ [[image:image-20221118103445-7.png]]
321 +​ [[image:image-20221021111058-12.png]]
262 262  
263 263  
264 -[[image:1670405928926-116.png]]
324 +[[image:image-20221021111201-16.png||height="472" width="653"]]
265 265  
266 266  ​
267 267  
... ... @@ -268,9 +268,10 @@
268 268  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.
269 269  
270 270  
271 -=== 2.2.6 Use TCP protocol to uplink data ===
272 272  
332 +=== 2.2.7 Use TCP protocol to uplink data ===
273 273  
334 +
274 274  (% style="color:blue" %)**AT Commands:**
275 275  
276 276  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -277,76 +277,82 @@
277 277  
278 278  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
279 279  
280 -​ [[image:1670406036256-101.png||height="676" width="713"]]
341 +​ [[image:image-20221021111125-14.png]]
281 281  
282 -
283 283  [[image:image-20221021111131-15.png]]
284 284  
285 285  ​
286 286  
287 -=== 2.2.7 Change Update Interval ===
288 288  
348 +=== 2.2.8 Change Update Interval ===
289 289  
350 +
290 290  User can use below command to change the (% style="color:blue" %)**uplink interval**.
291 291  
292 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
353 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
293 293  
294 294  (% style="color:red" %)**NOTE:**
295 295  
296 -1.  By default, the device will send an uplink message every 4 hour.
357 +1.  By default, the device will send an uplink message every 1 hour.
297 297  
298 298  
360 +
299 299  == 2.3  Uplink Payload ==
300 300  
301 301  
302 -The uplink payload includes 23 bytes in total by default.
364 +The uplink payload includes 123 bytes in total by default.
303 303  
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.
366 +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.
305 305  
306 306  
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
369 +(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
370 +|=(% 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**
371 +|=(% 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"]]
310 310  
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" %)...
373 +(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
374 +|(% 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**
375 +|(% 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" %)...
316 316  
317 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
377 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
318 318  
319 -[[image:1670406261143-723.png]]
379 +[[image:image-20221021111201-16.png||height="572" width="792"]]
320 320  
321 321  
322 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
382 +The payload is ASCII string, representative same HEX:
323 323  
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__(%%)**
384 +**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 __**
325 325  
326 326  **where:**
327 327  
328 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
388 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
329 329  
330 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
390 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
331 331  
332 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
392 +* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
333 333  
334 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
394 +* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
335 335  
336 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
396 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
337 337  
338 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
398 +* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
339 339  
340 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
400 +* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
341 341  
342 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
402 +* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
343 343  
344 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
404 +* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
345 345  
406 +* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
346 346  
408 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
347 347  
410 +* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
411 +
412 +* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
413 +
348 348  == 2.4  Payload Explanation and Sensor Interface ==
349 349  
416 +
350 350  === 2.4.1  Device ID ===
351 351  
352 352  
... ... @@ -361,18 +361,20 @@
361 361  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
362 362  
363 363  
431 +
364 364  === 2.4.2  Version Info ===
365 365  
366 366  
367 367  Specify the software version: 0x64=100, which means firmware version 1.00.
368 368  
369 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
437 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
370 370  
371 371  
440 +
372 372  === 2.4.3  Battery Info ===
373 373  
374 374  
375 -Check the battery voltage for NMDS200.
444 +Check the battery voltage for CPN01.
376 376  
377 377  Ex1: 0x0B45 = 2885mV
378 378  
... ... @@ -379,6 +379,7 @@
379 379  Ex2: 0x0B49 = 2889mV
380 380  
381 381  
451 +
382 382  === 2.4.4  Signal Strength ===
383 383  
384 384  
... ... @@ -397,35 +397,70 @@
397 397  **99**    Not known or not detectable
398 398  
399 399  
400 -=== 2.4.5  Distance ===
401 401  
471 +=== 2.4.5  Calculate Flag ===
402 402  
403 -[[image:1670407401682-959.png]]
404 404  
405 -**(% style="color:blue" %)Object1 Distance:**
474 +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.
406 406  
407 -Distance between sensor probe to the first object. (unit: cm)
476 +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.
408 408  
409 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
478 +Default value: 0. 
410 410  
411 -**(% style="color:blue" %)0205(H) = 517 (D) = 517 cm.**
480 +Range (6 bits): (b)000000 ~~ (b) 111111
412 412  
413 413  
414 -**(% style="color:blue" %)Object2 Distance:**
415 415  
416 -Distance between sensor probe to the second object. (unit: cm)
484 +=== 2.4.6  Alarm ===
417 417  
418 418  
419 -=== 2.4.6  Timestamp ===
487 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
420 420  
421 421  
490 +
491 +=== 2.4.7  Contact Status ===
492 +
493 +
494 +0: Open
495 +
496 +1: Close
497 +
498 +
499 +
500 +=== 2.4.8  Total pulse ===
501 +
502 +
503 +Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
504 +
505 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
506 +
507 +
508 +
509 +=== 2.4.9  The last open duration ===
510 +
511 +
512 +Dry Contact last open duration.
513 +
514 +Unit: min.
515 +
516 +[[image:image-20221021111346-17.png||height="146" width="770"]]
517 +
518 +
519 +
520 +=== 2.4.10  Timestamp ===
521 +
522 +
422 422  Timestamp : 0x6315537b =1662342011
423 423  
525 +Convert Unix timestamp to time 2022-9-5 9:40:11.
424 424  
527 +**~ **
528 +
529 +
425 425  == 2.5  Downlink Payload ==
426 426  
427 427  
428 -By default, NDS03A prints the downlink payload to console port.
533 +By default, CPN01 prints the downlink payload to console port.
429 429  
430 430  [[image:image-20221021111414-18.png]] ​
431 431  
... ... @@ -442,7 +442,7 @@
442 442  
443 443  * (% style="color:#037691" %)**Reset**
444 444  
445 -If payload = 0x04FF, it will reset the NDS03A
550 +If payload = 0x04FF, it will reset the NSE01
446 446  
447 447  * (% style="color:#037691" %)**INTMOD**
448 448  
... ... @@ -449,19 +449,20 @@
449 449  Downlink Payload: 06000003, Set AT+INTMOD=3
450 450  
451 451  
557 +
452 452  == 2.6  ​LED Indicator ==
453 453  
454 454  
455 -The NDS03A has an internal LED which is to show the status of different states.
561 +The CPN01 has an internal LED which is to show the status of different states.
456 456  
457 457  * When the device starts normally, the LED will light up for 1 second.
458 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
564 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
459 459  * For each uplink probe, LED will be on for 500ms.
460 460  
461 461  == 2.7  Alarm Base on Timeout ==
462 462  
463 463  
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:
570 +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:
465 465  
466 466  
467 467  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -477,25 +477,17 @@
477 477  
478 478  If keep time = 0, Disable Alarm Base on Timeout feature.
479 479  
480 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
586 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
481 481  
482 482  
483 483  (% style="color:blue" %)**AT Command to configure:**
484 484  
485 -(% style="color:blue" %)**PB14 PIN:**
591 +(% 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.
486 486  
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 -
489 489  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
490 490  
491 491  
492 -(% style="color:blue" %)**PB15 PIN:**
493 493  
494 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
495 -
496 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
497 -
498 -
499 499  == 2.8  Set debug mode ==
500 500  
501 501  
... ... @@ -517,57 +517,54 @@
517 517  [[image:image-20221021111527-19.png]]
518 518  
519 519  
520 -== 2.10  Count Mod ==
521 521  
619 +== 2.10  Set trigger mode ==
522 522  
523 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
524 524  
525 -[[image:image-20221118092935-1.png]]
622 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
526 526  
624 +Feature: Set the trigger interrupt mode.
527 527  
528 -== 2.11  Interrupt Pin Channel Mod ==
626 +[[image:image-20221021111552-20.png]]
529 529  
530 530  
531 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
532 532  
533 -[[image:image-20221118093144-2.png]]
630 +== 2.11  Set the calculate flag ==
534 534  
535 535  
536 -== 2.12 TTRIG1/2 timeout status alarm ==
633 +Feature: Set the calculate flag
537 537  
635 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
538 538  
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.
637 +[[image:image-20221021111711-22.png]]
540 540  
541 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
542 542  
543 -[[image:image-20221118093512-3.png]]
544 544  
641 +== 2.12 Set count number ==
545 545  
546 -== 2.13  Select counting mode ==
547 547  
644 +Feature: Manually set the count number
548 548  
549 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
646 +(% style="color:blue" %)**AT Command: AT+SETCNT**
550 550  
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.
648 +[[image:image-20221021111748-24.png]]
552 552  
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.
554 554  
555 -[[image:image-20221118093658-4.png]]
556 556  
652 +== 2.13  Set the number of data to be uploaded and the recording time ==
557 557  
558 -== 2.14  Set the number of data to be uploaded and the recording time ==
559 559  
560 -
561 561  (% style="color:blue" %)**AT Command:**
562 562  
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)
657 +(% 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)
564 564  
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.
659 +(% 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.
566 566  
567 567  
568 -== 2.15  Read or Clear cached data ==
569 569  
663 +== 2.14  Read or Clear cached data ==
570 570  
665 +
571 571  (% style="color:blue" %)**AT Command:**
572 572  
573 573  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -574,24 +574,27 @@
574 574  
575 575  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
576 576  
577 -[[image:image-20221118094227-5.png]]
672 +[[image:image-20221021111810-25.png||height="364" width="797"]]
578 578  
579 579  
580 -== 2.16  ​Firmware Change Log ==
581 581  
676 +== 2.15  ​Firmware Change Log ==
582 582  
583 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
584 584  
679 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
680 +
585 585  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
586 586  
587 587  
588 -== 2.17  ​Battery Analysis ==
589 589  
590 -=== 2.17.1  ​Battery Type ===
685 +== 2.16  ​Battery Analysis ==
591 591  
592 592  
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.
688 +=== 2.16.1  ​Battery Type ===
594 594  
690 +
691 +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.
692 +
595 595  The battery is designed to last for several years depends on the actual use environment and update interval. 
596 596  
597 597  The battery-related documents as below:
... ... @@ -605,9 +605,10 @@
605 605  [[image:image-20221021111911-26.png]] ​
606 606  
607 607  
608 -=== 2.17.2  Power consumption Analyze ===
609 609  
707 +=== 2.16.2  Power consumption Analyze ===
610 610  
709 +
611 611  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.
612 612  
613 613  Instruction to use as below:
... ... @@ -627,18 +627,21 @@
627 627  [[image:1666596205057-567.png]] ​
628 628  
629 629  
630 -=== 2.17.3  ​Battery Note ===
631 631  
730 +=== 2.16.3  ​Battery Note ===
632 632  
732 +
633 633  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.
634 634  
635 635  
636 -=== 2.17.4  Replace the battery ===
637 637  
737 +=== 2.16.4  Replace the battery ===
638 638  
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).
640 640  
740 +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).
641 641  
742 +
743 +
642 642  = 3. ​ Access NB-IoT Module =
643 643  
644 644  
... ... @@ -646,12 +646,13 @@
646 646  
647 647  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/]] 
648 648  
751 +[[image:image-20221021112006-28.png]] ​
649 649  
650 -[[image:image-20221118094449-6.png]] ​
651 651  
652 652  
653 653  = 4.  Using the AT Commands =
654 654  
757 +
655 655  == 4.1  Access AT Commands ==
656 656  
657 657  
... ... @@ -698,21 +698,15 @@
698 698  
699 699  AT+ DEBUG   : Enable or Disable debug mode
700 700  
701 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
804 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
702 702  
703 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
806 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
704 704  
705 -AT+COUNTMOD  :  Get or Set the count mode
808 +AT+ CALCFLAG   : Get or Set the calculate flag
706 706  
707 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
810 +AT+ CLRC   : Clear current door open count
708 708  
709 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
710 710  
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 -
716 716  (% style="color:blue" %)**COAP Management**      
717 717  
718 718  AT+URI            : Resource parameters
... ... @@ -743,8 +743,10 @@
743 743  AT+PWORD  : Serial Access Password
744 744  
745 745  
843 +
746 746  = ​5.  FAQ =
747 747  
846 +
748 748  == 5.1 ​ How to Upgrade Firmware ==
749 749  
750 750  
... ... @@ -752,11 +752,13 @@
752 752  
753 753  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]]
754 754  
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.**
854 +(% 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.**
756 756  
757 757  
857 +
758 758  = 6.  Trouble Shooting =
759 759  
860 +
760 760  == 6.1  ​Connection problem when uploading firmware ==
761 761  
762 762  
... ... @@ -763,6 +763,7 @@
763 763  (% 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]]
764 764  
765 765  
867 +
766 766  == 6.2  AT Command input doesn't work ==
767 767  
768 768  
... ... @@ -769,19 +769,27 @@
769 769  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.
770 770  
771 771  
874 +
772 772  = 7. ​ Order Info =
773 773  
774 774  
775 -Part Number**:** NDS03A
878 +Part Number**:** CPN01
776 776  
777 777  
881 +
778 778  = 8.  Packing Info =
779 779  
780 780  
781 781  (% style="color:blue" %)**Package Includes**:
782 782  
783 -* NDS03A Open/Close Door Sensor x 1
887 +* CPN01 Open/Close Sensor x 1
888 +* External antenna x 1
784 784  
890 +(% style="color:blue" %)**Dimension and weight**:
891 +
892 +* Size: 195 x 125 x 55 mm
893 +* Weight:   420g
894 +
785 785  = 9.  Support =
786 786  
787 787  
1670404362039-351.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -492.6 KB
Content
1670405841875-916.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.0 KB
Content
1670406261143-723.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content
1670407401682-959.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -23.7 KB
Content
LMDS200_10.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 KB
Content
image-20221117142300-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -51.9 KB
Content
image-20221117150312-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.7 KB
Content
image-20221118092935-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.5 KB
Content
image-20221118093658-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -12.7 KB
Content
image-20221118094227-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.2 KB
Content
image-20221118094449-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.5 KB
Content
image-20221118103445-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.5 KB
Content
image-20221207170748-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.1 KB
Content
image-20221207170748-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.9 KB
Content
image-20221207173200-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
image-20221207173300-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.0 KB
Content

Applications

Navigation

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