Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 61.1 >
edited by Xiaoling
on 2022/11/17 15:03
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,39 +15,26 @@
15 15  
16 16  = 1.  Introduction =
17 17  
18 -== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
13 +== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
19 19  
20 20  
21 21  (((
22 -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.
23 -)))
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.
24 24  
25 -(((
26 -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.
27 -)))
28 28  
29 -(((
30 -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.
31 -)))
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.
32 32  
33 -(((
34 -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.
35 -)))
22 +NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
36 36  
37 -(((
38 -NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
39 -)))
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.
40 40  
41 -(((
42 -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.
43 -)))
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.
44 44  
45 -(((
46 -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)
47 -)))
28 +NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
48 48  
49 -(((
50 -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.
51 51  )))
52 52  
53 53  
... ... @@ -56,10 +56,9 @@
56 56  
57 57  
58 58  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
59 -* Open/Close detect
60 -* Open/Close statistics
41 +* Short uplink interval for Distance Alarm
61 61  * Monitor Battery Level
62 -* connect two door sensors
43 +* Microwave Radar for distance detection
63 63  * Datalog feature
64 64  * Uplink periodically
65 65  * Downlink to change configure
... ... @@ -71,31 +71,42 @@
71 71  * 8500mAh Battery for long-term use
72 72  
73 73  
55 +== 1.3 Radar probe specification ==
74 74  
75 -== 1.3  Storage & Operation ==
76 76  
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°
77 77  
78 -Temperature -40°C to +85°C
79 79  
80 80  
81 -== 1.4  Mechanical ==
69 +== 1.4  Storage Temperature ==
82 82  
83 83  
84 -[[image:image-20221117114937-4.png]]
72 + -40°C to +85°C
85 85  
86 86  
87 -[[image:image-20221117114949-5.png]]
88 88  
89 89  
90 -[[image:image-20221117115010-6.png]]
91 91  
92 -
93 -
94 94  == 1.5 ​ Applications ==
95 95  
96 96  
97 -[[image:image-20221117114842-3.png]]
98 98  
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
99 99  
100 100  
101 101  == 1.6  Specification ==
... ... @@ -104,109 +104,63 @@
104 104  (% style="color:blue" %)**Common DC Characteristics:**
105 105  
106 106  * Supply Voltage: 2.1v ~~ 3.6v
107 -* Operating Temperature: -40 ~~ 85°C
99 +* Operating Temperature: 0 ~~ 70°C
108 108  
109 109  (% style="color:blue" %)**NB-IoT Spec:**
110 110  
111 -* - B1 @H-FDD: 2100MHz
112 -* - B3 @H-FDD: 1800MHz
113 -* - B8 @H-FDD: 900MHz
114 -* - B5 @H-FDD: 850MHz
115 -* - B20 @H-FDD: 800MHz
116 -* - 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
117 117  
118 118  
111 +== 1.7  Installation ==
119 119  
120 -== 1.7  Pin Definitions and Switch ==
121 121  
114 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
122 122  
123 -[[image:image-20221021110429-4.png]]
124 124  
117 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
125 125  
126 -=== 1.7.1  Pin Definition ===
127 127  
128 128  
129 -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]]
121 +== 1.8  Pin Definitions and Switch ==
130 130  
131 131  
124 +[[image:1670404362039-351.png]]
132 132  
133 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
134 134  
127 += 2.  Use NMDS200 to communicate with IoT Server =
135 135  
136 -Power on Device when putting this jumper.
137 -
138 -
139 -
140 -=== 1.7.3  BOOT MODE / SW1 ===
141 -
142 -
143 -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.
144 -
145 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
146 -
147 -
148 -
149 -=== 1.7.4  Reset Button ===
150 -
151 -
152 -Press to reboot the device.
153 -
154 -
155 -
156 -=== 1.7.5  LED ===
157 -
158 -
159 -The LED will blink when :
160 -
161 -1.  Boot the device in flash mode
162 -
163 -2.  Send an uplink packet
164 -
165 -
166 -
167 -== 1.8  Magnet Distance ==
168 -
169 -
170 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
171 -
172 -(% style="color:blue" %)**Iron Door:**(%%)**  **30 ~~ 45mm
173 -
174 -
175 -
176 -= 2.  Use CPN01 to communicate with IoT Server =
177 -
178 178  == 2.1  How it works ==
179 179  
180 180  
181 -In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.
132 +The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
182 182  
183 -The diagram below shows the working flow in the default firmware of NDS03A:
134 +The diagram below shows the working flow in the default firmware of NMDS200:
184 184  
185 185  [[image:image-20221021110615-5.png]]
186 186  
187 187  
139 +== 2.2 ​ Configure NMDS200 ==
188 188  
189 -== 2.2 ​ Configure NDS03A ==
190 190  
191 -=== 2.2.1 Test Requirement ===
142 +To use NMDS200 in your city, make sure to meet below requirements:
192 192  
193 -
194 -To use NDS03A in your city, make sure to meet below requirements:
195 -
196 196  * Your local operator has already distributed an NB-IoT Network.
197 -* The local NB-IoT network used the band that NDS03A supports.
145 +* The local NB-IoT network used the band that NMDS200 supports.
198 198  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
199 199  
200 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDS03A 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.
201 201  
202 -[[image:image-20221117142300-1.png]]
150 +[[image:image-20221207173300-4.png]]
203 203  
204 - ​
205 205  
153 +=== 2.2.1 Insert NB-IoT SIM card ===
206 206  
207 -=== 2.2.2 Insert NB-IoT SIM card ===
208 208  
209 -
210 210  Insert the NB-IoT Card get from your provider.
211 211  
212 212  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -214,12 +214,11 @@
214 214  [[image:image-20221021110745-6.png]] ​
215 215  
216 216  
163 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
217 217  
218 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
219 219  
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.
220 220  
221 -User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
222 -
223 223  (% style="color:blue" %)**Connection:**
224 224  
225 225  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -241,11 +241,11 @@
241 241  
242 242  * Flow Control: (% style="color:red" %)**None**
243 243  
244 -Make sure the switch is in FLASH position, then power on NDS03A 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**(%%).
245 245  
246 246  ​[[image:image-20221021110817-7.png]]
247 247  
248 -NDS03A 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.
249 249  
250 250  
251 251  (% 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]]
... ... @@ -252,13 +252,13 @@
252 252  
253 253  
254 254  
255 -=== 2.2.4 Use CoAP protocol to uplink data ===
200 +=== 2.2.3 Use CoAP protocol to uplink data ===
256 256  
257 257  
258 258  (% 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/]]
259 259  
260 260  
261 -(% style="color:blue" %)**Use below commands in CPN01:**
206 +(% style="color:blue" %)**Use below commands in NDS03A:**
262 262  
263 263  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
264 264  
... ... @@ -271,15 +271,14 @@
271 271  [[image:image-20221021110948-8.png]]
272 272  
273 273  
274 -After configuring the server address and (% style="color:green" %)**reset CPN01**(%%) (via AT+ATZ ), NDS03A 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.
275 275  
276 -[[image:image-20221021110956-9.png]] ​
221 +[[image:1670405841875-916.png]] ​
277 277  
278 278  
224 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
279 279  
280 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
281 281  
282 -
283 283  (% style="color:blue" %)**AT Commands:**
284 284  
285 285  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -295,10 +295,9 @@
295 295  
296 296  ​
297 297  
242 +=== 2.2.5 Use MQTT protocol to uplink data ===
298 298  
299 -=== 2.2.6 Use MQTT protocol to uplink data ===
300 300  
301 -
302 302  (% style="color:blue" %)**AT Commands:**
303 303  
304 304  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -315,10 +315,10 @@
315 315  
316 316  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
317 317  
318 -​ [[image:image-20221021111058-12.png]]
261 +​ [[image:image-20221118103445-7.png]]
319 319  
320 320  
321 -[[image:image-20221021111201-16.png||height="472" width="653"]]
264 +[[image:1670405928926-116.png]]
322 322  
323 323  ​
324 324  
... ... @@ -325,10 +325,9 @@
325 325  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.
326 326  
327 327  
271 +=== 2.2.6 Use TCP protocol to uplink data ===
328 328  
329 -=== 2.2.7 Use TCP protocol to uplink data ===
330 330  
331 -
332 332  (% style="color:blue" %)**AT Commands:**
333 333  
334 334  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -335,19 +335,19 @@
335 335  
336 336  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
337 337  
338 -​ [[image:image-20221021111125-14.png]]
280 +​ [[image:1670406036256-101.png||height="676" width="713"]]
339 339  
282 +
340 340  [[image:image-20221021111131-15.png]]
341 341  
342 342  ​
343 343  
287 +=== 2.2.7 Change Update Interval ===
344 344  
345 -=== 2.2.8 Change Update Interval ===
346 346  
347 -
348 348  User can use below command to change the (% style="color:blue" %)**uplink interval**.
349 349  
350 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
292 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
351 351  
352 352  (% style="color:red" %)**NOTE:**
353 353  
... ... @@ -354,63 +354,57 @@
354 354  1.  By default, the device will send an uplink message every 4 hour.
355 355  
356 356  
357 -
358 358  == 2.3  Uplink Payload ==
359 359  
360 360  
361 -The uplink payload includes 123 bytes in total by default.
302 +The uplink payload includes 23 bytes in total by default.
362 362  
363 -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.
364 364  
365 365  
366 -(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
367 -|=(% 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**
368 -|=(% 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
369 369  
370 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
371 -|(% 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**
372 -|(% 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" %)...
373 373  
374 -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.
375 375  
376 -[[image:image-20221021111201-16.png||height="572" width="792"]]
319 +[[image:1670406261143-723.png]]
377 377  
378 378  
379 -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
380 380  
381 -**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__(%%)**
382 382  
383 383  **where:**
384 384  
385 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
328 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
386 386  
387 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
330 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
388 388  
389 -* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
332 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
390 390  
391 -* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
334 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
392 392  
393 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
336 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
394 394  
395 -* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
338 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
396 396  
397 -* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
340 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
398 398  
399 -* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
342 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
400 400  
401 -* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
344 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
402 402  
403 -* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
404 404  
405 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
406 406  
407 -* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
408 -
409 -* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
410 -
411 411  == 2.4  Payload Explanation and Sensor Interface ==
412 412  
413 -
414 414  === 2.4.1  Device ID ===
415 415  
416 416  
... ... @@ -425,20 +425,18 @@
425 425  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
426 426  
427 427  
428 -
429 429  === 2.4.2  Version Info ===
430 430  
431 431  
432 432  Specify the software version: 0x64=100, which means firmware version 1.00.
433 433  
434 -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.
435 435  
436 436  
437 -
438 438  === 2.4.3  Battery Info ===
439 439  
440 440  
441 -Check the battery voltage for CPN01.
375 +Check the battery voltage for NMDS200.
442 442  
443 443  Ex1: 0x0B45 = 2885mV
444 444  
... ... @@ -445,7 +445,6 @@
445 445  Ex2: 0x0B49 = 2889mV
446 446  
447 447  
448 -
449 449  === 2.4.4  Signal Strength ===
450 450  
451 451  
... ... @@ -464,70 +464,35 @@
464 464  **99**    Not known or not detectable
465 465  
466 466  
400 +=== 2.4.5  Distance ===
467 467  
468 -=== 2.4.5  Calculate Flag ===
469 469  
403 +[[image:1670407401682-959.png]]
470 470  
471 -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:**
472 472  
473 -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)
474 474  
475 -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
476 476  
477 -Range (6 bits): (b)000000 ~~ (b) 111111
411 +**(% style="color:blue" %)0205(H) = 517 (D) = 517 cm.**
478 478  
479 479  
414 +**(% style="color:blue" %)Object2 Distance:**
480 480  
481 -=== 2.4.6  Alarm ===
416 +Distance between sensor probe to the second object. (unit: cm)
482 482  
483 483  
484 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
419 +=== 2.4.6  Timestamp ===
485 485  
486 486  
487 -
488 -=== 2.4.7  Contact Status ===
489 -
490 -
491 -0: Open
492 -
493 -1: Close
494 -
495 -
496 -
497 -=== 2.4.8  Total pulse ===
498 -
499 -
500 -Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
501 -
502 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
503 -
504 -
505 -
506 -=== 2.4.9  The last open duration ===
507 -
508 -
509 -Dry Contact last open duration.
510 -
511 -Unit: min.
512 -
513 -[[image:image-20221021111346-17.png||height="146" width="770"]]
514 -
515 -
516 -
517 -=== 2.4.10  Timestamp ===
518 -
519 -
520 520  Timestamp : 0x6315537b =1662342011
521 521  
522 -Convert Unix timestamp to time 2022-9-5 9:40:11.
523 523  
524 -**~ **
525 -
526 -
527 527  == 2.5  Downlink Payload ==
528 528  
529 529  
530 -By default, CPN01 prints the downlink payload to console port.
428 +By default, NDS03A prints the downlink payload to console port.
531 531  
532 532  [[image:image-20221021111414-18.png]] ​
533 533  
... ... @@ -544,7 +544,7 @@
544 544  
545 545  * (% style="color:#037691" %)**Reset**
546 546  
547 -If payload = 0x04FF, it will reset the NSE01
445 +If payload = 0x04FF, it will reset the NDS03A
548 548  
549 549  * (% style="color:#037691" %)**INTMOD**
550 550  
... ... @@ -551,20 +551,19 @@
551 551  Downlink Payload: 06000003, Set AT+INTMOD=3
552 552  
553 553  
554 -
555 555  == 2.6  ​LED Indicator ==
556 556  
557 557  
558 -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.
559 559  
560 560  * When the device starts normally, the LED will light up for 1 second.
561 -* 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.
562 562  * For each uplink probe, LED will be on for 500ms.
563 563  
564 564  == 2.7  Alarm Base on Timeout ==
565 565  
566 566  
567 -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:
568 568  
569 569  
570 570  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -580,17 +580,25 @@
580 580  
581 581  If keep time = 0, Disable Alarm Base on Timeout feature.
582 582  
583 -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.
584 584  
585 585  
586 586  (% style="color:blue" %)**AT Command to configure:**
587 587  
588 -(% 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:**
589 589  
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 +
590 590  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
591 591  
592 592  
492 +(% style="color:blue" %)**PB15 PIN:**
593 593  
494 +(% style="color:#037691" %)**AT+TTRIG2=1,30**
495 +
496 +(% style="color:#037691" %)**AT+TTRIG2=0,0 **
497 +
498 +
594 594  == 2.8  Set debug mode ==
595 595  
596 596  
... ... @@ -612,54 +612,57 @@
612 612  [[image:image-20221021111527-19.png]]
613 613  
614 614  
520 +== 2.10  Count Mod ==
615 615  
616 -== 2.10  Set trigger mode ==
617 617  
523 +(% style="color:blue" %)**AT Command: AT+COUNTMOD**
618 618  
619 -(% style="color:blue" %)**AT Command: AT+TTRMOD**
525 +[[image:image-20221118092935-1.png]]
620 620  
621 -Feature: Set the trigger interrupt mode.
622 622  
623 -[[image:image-20221021111552-20.png]]
528 +== 2.11  Interrupt Pin Channel Mod ==
624 624  
625 625  
531 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
626 626  
627 -== 2.11  Set the calculate flag ==
533 +[[image:image-20221118093144-2.png]]
628 628  
629 629  
630 -Feature: Set the calculate flag
536 +== 2.12 TTRIG1/2 timeout status alarm ==
631 631  
632 -(% style="color:blue" %)**AT Command: AT+CALCFLAG**
633 633  
634 -[[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.
635 635  
541 +(% style="color:blue" %)**AT Command: AT+TTRALARM**
636 636  
543 +[[image:image-20221118093512-3.png]]
637 637  
638 -== 2.12 Set count number ==
639 639  
546 +== 2.13  Select counting mode ==
640 640  
641 -Feature: Manually set the count number
642 642  
643 -(% style="color:blue" %)**AT Command: AT+SETCNT**
549 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
644 644  
645 -[[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.
646 646  
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.
647 647  
555 +[[image:image-20221118093658-4.png]]
648 648  
649 -== 2.13  Set the number of data to be uploaded and the recording time ==
650 650  
558 +== 2.14  Set the number of data to be uploaded and the recording time ==
651 651  
560 +
652 652  (% style="color:blue" %)**AT Command:**
653 653  
654 -(% 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)
655 655  
656 -(% 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.
657 657  
658 658  
568 +== 2.15  Read or Clear cached data ==
659 659  
660 -== 2.14  Read or Clear cached data ==
661 661  
662 -
663 663  (% style="color:blue" %)**AT Command:**
664 664  
665 665  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -666,27 +666,24 @@
666 666  
667 667  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
668 668  
669 -[[image:image-20221021111810-25.png||height="364" width="797"]]
577 +[[image:image-20221118094227-5.png]]
670 670  
671 671  
580 +== 2.16  ​Firmware Change Log ==
672 672  
673 -== 2.15  ​Firmware Change Log ==
674 674  
583 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
675 675  
676 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
677 -
678 678  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
679 679  
680 680  
588 +== 2.17  ​Battery Analysis ==
681 681  
682 -== 2.16  ​Battery Analysis ==
590 +=== 2.17.1  ​Battery Type ===
683 683  
684 684  
685 -=== 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.
686 686  
687 -
688 -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.
689 -
690 690  The battery is designed to last for several years depends on the actual use environment and update interval. 
691 691  
692 692  The battery-related documents as below:
... ... @@ -700,10 +700,9 @@
700 700  [[image:image-20221021111911-26.png]] ​
701 701  
702 702  
608 +=== 2.17.2  Power consumption Analyze ===
703 703  
704 -=== 2.16.2  Power consumption Analyze ===
705 705  
706 -
707 707  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.
708 708  
709 709  Instruction to use as below:
... ... @@ -723,21 +723,18 @@
723 723  [[image:1666596205057-567.png]] ​
724 724  
725 725  
630 +=== 2.17.3  ​Battery Note ===
726 726  
727 -=== 2.16.3  ​Battery Note ===
728 728  
729 -
730 730  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.
731 731  
732 732  
636 +=== 2.17.4  Replace the battery ===
733 733  
734 -=== 2.16.4  Replace the battery ===
735 735  
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).
736 736  
737 -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).
738 738  
739 -
740 -
741 741  = 3. ​ Access NB-IoT Module =
742 742  
743 743  
... ... @@ -745,13 +745,12 @@
745 745  
746 746  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/]] 
747 747  
748 -[[image:image-20221021112006-28.png]] ​
749 749  
650 +[[image:image-20221118094449-6.png]] ​
750 750  
751 751  
752 752  = 4.  Using the AT Commands =
753 753  
754 -
755 755  == 4.1  Access AT Commands ==
756 756  
757 757  
... ... @@ -798,15 +798,21 @@
798 798  
799 799  AT+ DEBUG   : Enable or Disable debug mode
800 800  
801 -AT+ TTRIG   : Get or Set Alarm Base on Timeout
701 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
802 802  
803 -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
804 804  
805 -AT+ CALCFLAG   : Get or Set the calculate flag
705 +AT+COUNTMOD  :  Get or Set the count mode
806 806  
807 -AT+ CLRC   : Clear current door open count
707 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
808 808  
709 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
809 809  
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 +
810 810  (% style="color:blue" %)**COAP Management**      
811 811  
812 812  AT+URI            : Resource parameters
... ... @@ -837,10 +837,8 @@
837 837  AT+PWORD  : Serial Access Password
838 838  
839 839  
840 -
841 841  = ​5.  FAQ =
842 842  
843 -
844 844  == 5.1 ​ How to Upgrade Firmware ==
845 845  
846 846  
... ... @@ -848,13 +848,11 @@
848 848  
849 849  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]]
850 850  
851 -(% 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.**
852 852  
853 853  
854 -
855 855  = 6.  Trouble Shooting =
856 856  
857 -
858 858  == 6.1  ​Connection problem when uploading firmware ==
859 859  
860 860  
... ... @@ -861,7 +861,6 @@
861 861  (% 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]]
862 862  
863 863  
864 -
865 865  == 6.2  AT Command input doesn't work ==
866 866  
867 867  
... ... @@ -868,27 +868,19 @@
868 868  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.
869 869  
870 870  
871 -
872 872  = 7. ​ Order Info =
873 873  
874 874  
875 -Part Number**:** CPN01
775 +Part Number**:** NDS03A
876 876  
877 877  
878 -
879 879  = 8.  Packing Info =
880 880  
881 881  
882 882  (% style="color:blue" %)**Package Includes**:
883 883  
884 -* CPN01 Open/Close Sensor x 1
885 -* External antenna x 1
783 +* NDS03A Open/Close Door Sensor x 1
886 886  
887 -(% style="color:blue" %)**Dimension and weight**:
888 -
889 -* Size: 195 x 125 x 55 mm
890 -* Weight:   420g
891 -
892 892  = 9.  Support =
893 893  
894 894  
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-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