Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 89.1 >
edited by David Huang
on 2022/12/12 09:03
To version < 74.1 >
edited by Xiaoling
on 2022/12/07 17:12
>
Change comment: Uploaded new attachment "1670404362039-351.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.David
1 +XWiki.Xiaoling
Content
... ... @@ -1,28 +1,13 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg||height="572" width="572"]]
2 +[[image:LMDS200_10.jpg]]
3 3  
4 4  
5 -
6 -
7 -
8 -(% style="display:none" %) (%%)
9 -
10 -
11 -
12 -
13 -
14 14  **Table of Contents：**
15 15  
16 -{{toc/}}
17 17  
18 18  
19 19  
20 20  
21 -
22 -
23 -
24 -
25 -
26 26  = 1.  Introduction =
27 27  
28 28  == 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
... ... @@ -29,45 +29,51 @@
29 29  
30 30  
31 31  (((
32 -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.
17 +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.
33 33  )))
34 34  
35 35  (((
36 -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.
21 +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.
37 37  )))
38 38  
39 39  (((
40 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
25 +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.
41 41  )))
42 42  
43 43  (((
44 -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.
29 +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.
45 45  )))
46 46  
47 47  (((
33 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
34 +)))
35 +
36 +(((
48 48  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.
49 49  )))
50 50  
51 51  (((
52 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
41 +NDS03A supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
53 53  )))
54 54  
55 55  (((
56 -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)
45 +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)
57 57  )))
58 58  
59 59  (((
60 -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.
49 +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.
61 61  )))
62 62  
63 63  
53 +
64 64  == ​1.2  Features ==
65 65  
66 66  
67 67  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
68 -* Short uplink interval for Distance Alarm
58 +* Open/Close detect
59 +* Open/Close statistics
69 69  * Monitor Battery Level
70 -* Microwave Radar for distance detection
61 +* connect two door sensors
71 71  * Datalog feature
72 72  * Uplink periodically
73 73  * Downlink to change configure
... ... @@ -79,39 +79,32 @@
79 79  * 8500mAh Battery for long-term use
80 80  
81 81  
82 -== 1.3 Radar probe specification ==
73 +== 1.3  Storage & Operation ==
83 83  
84 84  
85 -* Measuring Method: FMCW
86 -* Frequency: 24.000 ~~ 24.500 GHz
87 -* Measurement output power: 6dBm
88 -* Measure range: 0.5 ~~ 20m
89 -* Accuracy: ±0.1m
90 -* Resolution: 0.01m
91 -* Horizontal Angel: 78°
92 -* Vertical Angel: 23°
76 +Temperature -40°C to +85°C
93 93  
94 94  
95 -== 1.4  Storage Temperature ==
79 +== 1.4  Mechanical ==
96 96  
97 97  
98 - -40°C to +85°C
82 +[[image:image-20221117114937-4.png]]
99 99  
100 100  
85 +[[image:image-20221117114949-5.png]]
86 +
87 +
88 +[[image:image-20221117115010-6.png]]
89 +
90 +
91 +
101 101  == 1.5 ​ Applications ==
102 102  
103 103  
104 -* Horizontal distance measurement
105 -* Liquid level measurement
106 -* Parking management system
107 -* Object proximity and presence detection
108 -* Intelligent trash can management system
109 -* Robot obstacle avoidance
110 -* Automatic control
111 -* Sewer
112 -* Bottom water level monitoring
95 +[[image:image-20221117114842-3.png]]
113 113  
114 114  
98 +
115 115  == 1.6  Specification ==
116 116  
117 117  
... ... @@ -118,7 +118,7 @@
118 118  (% style="color:blue" %)**Common DC Characteristics:**
119 119  
120 120  * Supply Voltage: 2.1v ~~ 3.6v
121 -* Operating Temperature: 0 ~~ 70°C
105 +* Operating Temperature: -40 ~~ 85°C
122 122  
123 123  (% style="color:blue" %)**NB-IoT Spec:**
124 124  
... ... @@ -130,51 +130,85 @@
130 130  * B28 @H-FDD: 700MHz
131 131  
132 132  
133 -== 1.7  Installation ==
117 +== 1.7  Pin Definitions and Switch ==
134 134  
135 135  
136 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
120 +[[image:image-20221021110429-4.png]]
137 137  
138 138  
139 -[[image:image-20221207170748-1.png]]
123 +=== 1.7.1  Pin Definition ===
140 140  
141 141  
142 - [[image:image-20221207170748-2.png||height="345" width="634"]]
126 +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]]
143 143  
144 144  
145 -== 1.8  Pin Definitions and Switch ==
129 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
146 146  
147 147  
148 -[[image:1670404362039-351.png]]
132 +Power on Device when putting this jumper.
149 149  
150 150  
151 -= 2.  Use NMDS200 to communicate with IoT Server =
135 +=== 1.7.3  BOOT MODE / SW1 ===
152 152  
137 +
138 +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.
139 +
140 +2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
141 +
142 +
143 +=== 1.7.4  Reset Button ===
144 +
145 +
146 +Press to reboot the device.
147 +
148 +
149 +=== 1.7.5  LED ===
150 +
151 +
152 +The LED will blink when :
153 +
154 +1.  Boot the device in flash mode
155 +
156 +2.  Send an uplink packet
157 +
158 +
159 +== 1.8  Magnet Distance ==
160 +
161 +
162 +(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
163 +
164 +(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
165 +
166 +
167 += 2.  Use NDS03A to communicate with IoT Server =
168 +
153 153  == 2.1  How it works ==
154 154  
155 155  
156 -The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
172 +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.
157 157  
158 -The diagram below shows the working flow in the default firmware of NMDS200:
174 +The diagram below shows the working flow in the default firmware of NDS03A:
159 159  
160 -[[image:image-20221021110615-5.png||height="996" width="492"]]
176 +[[image:image-20221021110615-5.png]]
161 161  
162 162  
163 -== 2.2 ​ Configure NMDS200 ==
179 +== 2.2 ​ Configure NDS03A ==
164 164  
181 +=== 2.2.1 Test Requirement ===
165 165  
166 -To use NMDS200 in your city, make sure to meet below requirements:
167 167  
184 +To use NDS03A in your city, make sure to meet below requirements:
185 +
168 168  * Your local operator has already distributed an NB-IoT Network.
169 -* The local NB-IoT network used the band that NMDS200 supports.
187 +* The local NB-IoT network used the band that NDS03A supports.
170 170  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
171 171  
172 -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.
190 +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.
173 173  
174 -[[image:image-20221209090938-1.png]]
192 +[[image:image-20221117142300-1.png]]
175 175  
176 176  
177 -=== 2.2.1 Insert NB-IoT SIM card ===
195 +=== 2.2.2 Insert NB-IoT SIM card ===
178 178  
179 179  
180 180  Insert the NB-IoT Card get from your provider.
... ... @@ -184,10 +184,10 @@
184 184  [[image:image-20221021110745-6.png]] ​
185 185  
186 186  
187 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
205 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
188 188  
189 189  
190 -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.
208 +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.
191 191  
192 192  (% style="color:blue" %)**Connection:**
193 193  
... ... @@ -210,23 +210,24 @@
210 210  
211 211  * Flow Control: (% style="color:red" %)**None**
212 212  
213 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
231 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
214 214  
215 215  ​[[image:image-20221021110817-7.png]]
216 216  
217 -NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
235 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
218 218  
219 219  
220 220  (% 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]]
221 221  
222 222  
223 -=== 2.2.3 Use CoAP protocol to uplink data ===
224 224  
242 +=== 2.2.4 Use CoAP protocol to uplink data ===
225 225  
244 +
226 226  (% 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/]]
227 227  
228 228  
229 -(% style="color:blue" %)**Use below commands in NMDS200:**
248 +(% style="color:blue" %)**Use below commands in NDS03A:**
230 230  
231 231  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
232 232  
... ... @@ -236,15 +236,15 @@
236 236  
237 237  For parameter description, please refer to AT command set
238 238  
239 -[[image:1670471530120-960.png||height="647" width="674"]]
258 +[[image:image-20221021110948-8.png]]
240 240  
241 241  
242 -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.
261 +After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
243 243  
244 -[[image:1670405841875-916.png]] ​
263 +[[image:image-20221118103547-9.png||height="605" width="837"]] ​
245 245  
246 246  
247 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
266 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
248 248  
249 249  
250 250  (% style="color:blue" %)**AT Commands:**
... ... @@ -255,7 +255,7 @@
255 255  
256 256  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
257 257  
258 -​ [[image:1670471559211-638.png]]
277 +​ [[image:image-20221021111025-10.png]]
259 259  
260 260  
261 261  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -262,7 +262,7 @@
262 262  
263 263  ​
264 264  
265 -=== 2.2.5 Use MQTT protocol to uplink data ===
284 +=== 2.2.6 Use MQTT protocol to uplink data ===
266 266  
267 267  
268 268  (% style="color:blue" %)**AT Commands:**
... ... @@ -281,10 +281,10 @@
281 281  
282 282  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
283 283  
284 -​ [[image:1670471584490-640.png]]
303 +​ [[image:image-20221118103445-7.png]]
285 285  
286 286  
287 -[[image:1670405928926-116.png]]
306 +[[image:image-20221118103453-8.png||height="608" width="841"]]
288 288  
289 289  ​
290 290  
... ... @@ -291,7 +291,7 @@
291 291  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.
292 292  
293 293  
294 -=== 2.2.6 Use TCP protocol to uplink data ===
313 +=== 2.2.7 Use TCP protocol to uplink data ===
295 295  
296 296  
297 297  (% style="color:blue" %)**AT Commands:**
... ... @@ -300,19 +300,18 @@
300 300  
301 301  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
302 302  
303 -​ [[image:1670471613823-833.png]]
322 +​ [[image:image-20221021111125-14.png]]
304 304  
305 -
306 306  [[image:image-20221021111131-15.png]]
307 307  
308 308  ​
309 309  
310 -=== 2.2.7 Change Update Interval ===
328 +=== 2.2.8 Change Update Interval ===
311 311  
312 312  
313 313  User can use below command to change the (% style="color:blue" %)**uplink interval**.
314 314  
315 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
333 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
316 316  
317 317  (% style="color:red" %)**NOTE:**
318 318  
... ... @@ -322,51 +322,71 @@
322 322  == 2.3  Uplink Payload ==
323 323  
324 324  
325 -The uplink payload includes 23 bytes in total by default.
343 +The uplink payload includes 26 bytes in total by default.
326 326  
327 327  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.
328 328  
347 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
329 329  
330 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %)
331 -|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:30px" %)**2**|(% style="width:30px" %)**2**|(% style="width:75px" %)**1**|(% style="width:30px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**
332 -|=(% 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>>||anchor="H2.4.5A0Distance"]] |(% style="width:93px" %) [[Distance 2>>||anchor="H2.4.5A0Distance"]]
349 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
350 +|=(% 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:60px" %)**1**|(% style="width:90px" %)**3**|(% style="width:100px" %)**3**
351 +|=(% 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" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
333 333  
334 -(% border="1" style="background-color:#ffffcc; color:green; width:429px" %)
335 -|(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((
353 +(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
354 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
336 336  **1-32 group**
337 337  )))
338 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...
357 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
339 339  
340 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
359 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
341 341  
342 -[[image:1670406261143-723.png]]
343 343  
362 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
363 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:45px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:60px" %)**1**|(% style="width:60px" %)**1**|(% style="width:87px" %)**3**|(% style="width:80px" %)**3**
364 +|=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
344 344  
345 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
366 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
367 +|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:75px" %)**1**|(% style="width:75px" %)**3**
368 +|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
346 346  
347 -**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__(%%)**
370 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
371 +|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
372 +**1-32 group**
373 +)))
374 +|(% style="width:102px" %)last open time(pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:100px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
348 348  
376 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
377 +
378 +[[image:image-20221117145932-2.png]]
379 +
380 +
381 +The payload is ASCII string, representative same HEX:
382 +
383 +**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)**
384 +
349 349  **where:**
350 350  
351 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
387 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
352 352  
353 353  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
354 354  
355 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
391 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
356 356  
357 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
393 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
358 358  
359 359  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
360 360  
361 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
397 +* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
362 362  
363 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
399 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
364 364  
365 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
401 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
366 366  
367 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
403 +* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
368 368  
405 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
369 369  
407 +
370 370  == 2.4  Payload Explanation and Sensor Interface ==
371 371  
372 372  === 2.4.1  Device ID ===
... ... @@ -388,13 +388,13 @@
388 388  
389 389  Specify the software version: 0x64=100, which means firmware version 1.00.
390 390  
391 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
429 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
392 392  
393 393  
394 394  === 2.4.3  Battery Info ===
395 395  
396 396  
397 -Check the battery voltage for NMDS200.
435 +Check the battery voltage for NDS03A.
398 398  
399 399  Ex1: 0x0B45 = 2885mV
400 400  
... ... @@ -406,49 +406,51 @@
406 406  
407 407  NB-IoT Network signal Strength.
408 408  
409 -(% style="color:blue" %)**Ex1: 0x1d = 29**
447 +**Ex1: 0x1d = 29**
410 410  
411 -(% style="color:#037691" %)**0** (%%) -113dBm or less
449 +**0**  -113dBm or less
412 412  
413 -(% style="color:#037691" %)**1**  (%%) -111dBm
451 +**1**  -111dBm
414 414  
415 -(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
453 +**2...30** -109dBm... -53dBm
416 416  
417 -(% style="color:#037691" %)**31** (%%) -51dBm or greater
455 +**31**   -51dBm or greater
418 418  
419 -(% style="color:#037691" %)**99** (%%) Not known or not detectable
457 +**99**    Not known or not detectable
420 420  
421 421  
422 -=== 2.4.5  Distance ===
460 +=== 2.4.5  Disalarm: (default: 0) ===
423 423  
424 424  
425 -[[image:1670407401682-959.png]]
463 +(% 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.
426 426  
465 +(% 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.
427 427  
428 -(% style="color:blue" %)**Object1 Distance:**
467 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
429 429  
430 -Distance between sensor probe to the first object. (unit: cm)
431 431  
432 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
470 +=== 2.4.6  Keep Status & Keep Time ===
433 433  
434 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
435 435  
473 +Shows the configure value of Alarm Base on Timeout Feature
436 436  
437 -(% style="color:blue" %)**Object2 Distance:**
438 438  
439 -Distance between sensor probe to the second object. (unit: cm)
476 +=== 2.4.7  Timestamp ===
440 440  
441 441  
442 -=== 2.4.6  Timestamp ===
479 +Timestamp : 0x6315537b =1662342011
443 443  
444 444  
445 -Timestamp : 0x6315537b =1662342011
482 +=== 2.4.8  Switch Dual Channel Mode ===
446 446  
447 447  
485 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
486 +
487 +
448 448  == 2.5  Downlink Payload ==
449 449  
450 450  
451 -By default, NMDS200 prints the downlink payload to console port.
491 +By default, NDS03A prints the downlink payload to console port.
452 452  
453 453  [[image:image-20221021111414-18.png]] ​
454 454  
... ... @@ -465,7 +465,7 @@
465 465  
466 466  * (% style="color:#037691" %)**Reset**
467 467  
468 -If payload = 0x04FF, it will reset the NMDS200
508 +If payload = 0x04FF, it will reset the NDS03A
469 469  
470 470  * (% style="color:#037691" %)**INTMOD**
471 471  
... ... @@ -475,33 +475,113 @@
475 475  == 2.6  ​LED Indicator ==
476 476  
477 477  
478 -The NMDS200 has an internal LED which is to show the status of different states.
518 +The NDS03A has an internal LED which is to show the status of different states.
479 479  
480 480  * When the device starts normally, the LED will light up for 1 second.
481 -* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
521 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
482 482  * For each uplink probe, LED will be on for 500ms.
483 483  
484 484  
485 -== 2.7  Distance alarm function ==
525 +== 2.7  Alarm Base on Timeout ==
486 486  
487 487  
488 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
528 +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:
489 489  
490 -(% style="color:#037691" %)**Example 1:**
491 491  
492 -AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
531 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
493 493  
494 -AT+ ALARM2 =min,max
533 +Keep Status = 1: Monitor Close to Open event
495 495  
535 +Keep Status = 0: Monitor Open to Close event
496 496  
497 -(% style="color:#037691" %)**Example 2:**
498 498  
499 -AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
538 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
500 500  
540 +Range 0 ~~ 65535(0xFFFF) seconds.
501 501  
502 -== 2.8  Set the number of data to be uploaded and the recording time ==
542 +If keep time = 0, Disable Alarm Base on Timeout feature.
503 503  
544 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
504 504  
546 +
547 +(% style="color:blue" %)**AT Command to configure:**
548 +
549 +(% style="color:blue" %)**PB14 PIN:**
550 +
551 +(% 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.
552 +
553 +(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
554 +
555 +
556 +(% style="color:blue" %)**PB15 PIN:**
557 +
558 +(% style="color:#037691" %)**AT+TTRIG2=1,30**
559 +
560 +(% style="color:#037691" %)**AT+TTRIG2=0,0 **
561 +
562 +
563 +== 2.8  Set debug mode ==
564 +
565 +
566 +Feature: Enable or Disable debug mode
567 +
568 +(% style="color:blue" %)**AT Command: AT+DEBUG**
569 +
570 +[[image:image-20221021111629-21.png]]
571 +
572 +
573 +
574 +== 2.9  Clear Flash Record ==
575 +
576 +
577 +Feature: Clear flash storage for data log feature.
578 +
579 +(% style="color:blue" %)**AT Command: AT+CLRDTA**
580 +
581 +[[image:image-20221021111527-19.png]]
582 +
583 +
584 +== 2.10  Count Mod ==
585 +
586 +
587 +(% style="color:blue" %)**AT Command: AT+COUNTMOD**
588 +
589 +[[image:image-20221118092935-1.png]]
590 +
591 +
592 +== 2.11  Interrupt Pin Channel Mod ==
593 +
594 +
595 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
596 +
597 +[[image:image-20221118093144-2.png]]
598 +
599 +
600 +== 2.12 TTRIG1/2 timeout status alarm ==
601 +
602 +
603 +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.
604 +
605 +(% style="color:blue" %)**AT Command: AT+TTRALARM**
606 +
607 +[[image:image-20221118093512-3.png]]
608 +
609 +
610 +== 2.13  Select counting mode ==
611 +
612 +
613 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
614 +
615 +When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
616 +
617 +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.
618 +
619 +[[image:image-20221118093658-4.png]]
620 +
621 +
622 +== 2.14  Set the number of data to be uploaded and the recording time ==
623 +
624 +
505 505  (% style="color:blue" %)**AT Command:**
506 506  
507 507  (% 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)
... ... @@ -509,7 +509,7 @@
509 509  (% 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.
510 510  
511 511  
512 -== 2.9  Read or Clear cached data ==
632 +== 2.15  Read or Clear cached data ==
513 513  
514 514  
515 515  (% style="color:blue" %)**AT Command:**
... ... @@ -518,10 +518,10 @@
518 518  
519 519  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
520 520  
521 -[[image:1670408172929-569.png]]
641 +[[image:image-20221118094227-5.png]]
522 522  
523 523  
524 -== 2.10  ​Firmware Change Log ==
644 +== 2.16  ​Firmware Change Log ==
525 525  
526 526  
527 527  Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
... ... @@ -529,12 +529,12 @@
529 529  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
530 530  
531 531  
532 -== 2.11  ​Battery Analysis ==
652 +== 2.17  ​Battery Analysis ==
533 533  
534 -=== 2.11.1  ​Battery Type ===
654 +=== 2.17.1  ​Battery Type ===
535 535  
536 536  
537 -The NMDS200 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
657 +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.
538 538  
539 539  The battery is designed to last for several years depends on the actual use environment and update interval. 
540 540  
... ... @@ -549,7 +549,7 @@
549 549  [[image:image-20221021111911-26.png]] ​
550 550  
551 551  
552 -=== 2.11.2  Power consumption Analyze ===
672 +=== 2.17.2  Power consumption Analyze ===
553 553  
554 554  
555 555  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.
... ... @@ -571,16 +571,16 @@
571 571  [[image:1666596205057-567.png]] ​
572 572  
573 573  
574 -=== 2.11.3  ​Battery Note ===
694 +=== 2.17.3  ​Battery Note ===
575 575  
576 576  
577 577  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.
578 578  
579 579  
580 -=== 2.11.4  Replace the battery ===
700 +=== 2.17.4  Replace the battery ===
581 581  
582 582  
583 -The default battery pack of NMDS200 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
703 +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).
584 584  
585 585  
586 586  = 3. ​ Access NB-IoT Module =
... ... @@ -626,59 +626,65 @@
626 626  
627 627  AT+INTMOD            : Set the trigger interrupt mode
628 628  
629 -AT+5VT  : Set extend the time of 5V power  
749 +AT+5VT  : Set extend the time of 5V power  
630 630  
631 -AT+PRO  : Choose agreement
751 +AT+PRO  : Choose agreement
632 632  
633 -AT+RXDL  : Extend the sending and receiving time
753 +AT+RXDL  : Extend the sending and receiving time
634 634  
635 -AT+SERVADDR  : Server Address
755 +AT+SERVADDR  : Server Address
636 636  
637 -AT+TR      :  Get or Set record time
757 +AT+TR      :  Get or Set record time
638 638  
639 -AT+NOUD :  Get or Set the number of data to be uploaded
759 +AT+NOUD      : Get or Set the number of data to be uploaded
640 640  
641 641  AT+CDP     :  Read or Clear cached data
642 642  
643 -AT+DEBUG:  Enable or Disable debug mode
763 +AT+ DEBUG   : Enable or Disable debug mode
644 644  
645 -AT+ALARM1:  Get or Set alarm of distance1
765 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
646 646  
647 -AT+ALARM2:  Get or Set alarm of distance2
767 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
648 648  
649 -AT+GETSENSORVALUE :  Returns the current sensor measurement
769 +AT+COUNTMOD  :  Get or Set the count mode
650 650  
651 -AT+POWERIC :  Get or set the Power IC flag
771 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
652 652  
773 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
653 653  
775 +AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
776 +
777 +AT+ CLRC   :  Clear current door open count
778 +
779 +
654 654  (% style="color:blue" %)**COAP Management**      
655 655  
656 -AT+URI :  Resource parameters
782 +AT+URI            : Resource parameters
657 657  
658 658  
659 659  (% style="color:blue" %)**UDP Management**
660 660  
661 -AT+CFM :  Upload confirmation mode (only valid for UDP)
787 +AT+CFM          : Upload confirmation mode (only valid for UDP)
662 662  
663 663  
664 664  (% style="color:blue" %)**MQTT Management**
665 665  
666 -AT+CLIENT  : Get or Set MQTT client
792 +AT+CLIENT               : Get or Set MQTT client
667 667  
668 -AT+UNAME : Get or Set MQTT Username
794 +AT+UNAME  : Get or Set MQTT Username
669 669  
670 -AT+PWD  :  Get or Set MQTT password
796 +AT+PWD                  : Get or Set MQTT password
671 671  
672 -AT+PUBTOPIC :  Get or Set MQTT publish topic
798 +AT+PUBTOPIC  : Get or Set MQTT publish topic
673 673  
674 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
800 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
675 675  
676 676  
677 677  (% style="color:blue" %)**Information**          
678 678  
679 -AT+FDR :  Factory Data Reset
805 +AT+FDR  : Factory Data Reset
680 680  
681 -AT+PWORD :  Serial Access Password
807 +AT+PWORD  : Serial Access Password
682 682  
683 683  
684 684  = ​5.  FAQ =
... ... @@ -690,7 +690,7 @@
690 690  
691 691  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]]
692 692  
693 -(% style="color:red" %)**Notice: **(% style="color:blue" %)**NMDS200** (%%)**and (% style="color:blue" %)LMDS200(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
819 +(% 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.**
694 694  
695 695  
696 696  = 6.  Trouble Shooting =
... ... @@ -710,7 +710,7 @@
710 710  = 7. ​ Order Info =
711 711  
712 712  
713 -Part Number:(% style="color:blue" %)** NMDS200**
839 +Part Number**:** NDS03A
714 714  
715 715  
716 716  = 8.  Packing Info =
... ... @@ -718,7 +718,7 @@
718 718  
719 719  (% style="color:blue" %)**Package Includes**:
720 720  
721 -* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
847 +* NDS03A Open/Close Door Sensor x 1
722 722  
723 723  
724 724  = 9.  Support =
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
1670408172929-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -211.8 KB
Content
1670471530120-960.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -67.6 KB
Content
1670471559211-638.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -170.6 KB
Content
1670471584490-640.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.1 KB
Content
1670471613823-833.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.0 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
image-20221208090742-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.7 KB
Content
image-20221209090938-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -121.9 KB
Content

Applications

Navigation

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