Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 57.1 >
edited by Xiaoling
on 2022/11/17 11:49
To version < 70.25 >
edited by Xiaoling
on 2022/12/07 16:40
>
Change comment: Update document after refactoring.

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
... ... @@ -9,13 +9,14 @@
9 9  
10 10  **Table of Contents：**
11 11  
12 +{{toc/}}
12 12  
13 13  
14 14  
15 15  
17 +
16 16  = 1.  Introduction =
17 17  
18 -
19 19  == 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
20 20  
21 21  
... ... @@ -40,10 +40,14 @@
40 40  )))
41 41  
42 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 +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 45  
46 46  (((
48 +NDS03A supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
49 +)))
50 +
51 +(((
47 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 48  )))
49 49  
... ... @@ -52,9 +52,7 @@
52 52  )))
53 53  
54 54  
55 -​
56 56  
57 -
58 58  == ​1.2  Features ==
59 59  
60 60  
... ... @@ -62,7 +62,7 @@
62 62  * Open/Close detect
63 63  * Open/Close statistics
64 64  * Monitor Battery Level
65 -* Uplink on periodically and open/close event
68 +* connect two door sensors
66 66  * Datalog feature
67 67  * Uplink periodically
68 68  * Downlink to change configure
... ... @@ -73,49 +73,53 @@
73 73  * Micro SIM card slot for NB-IoT SIM
74 74  * 8500mAh Battery for long-term use
75 75  
76 -== 1.3  Specification ==
77 77  
78 78  
79 -(% style="color:blue" %)**Common DC Characteristics:**
81 +== 1.3  Storage & Operation ==
80 80  
81 -* Supply Voltage: 2.1v ~~ 3.6v
82 -* Operating Temperature: -40 ~~ 85°C
83 83  
84 -(% style="color:blue" %)**NB-IoT Spec:**
84 +Temperature -40°C to +85°C
85 85  
86 -* - B1 @H-FDD: 2100MHz
87 -* - B3 @H-FDD: 1800MHz
88 -* - B8 @H-FDD: 900MHz
89 -* - B5 @H-FDD: 850MHz
90 -* - B20 @H-FDD: 800MHz
91 -* - B28 @H-FDD: 700MHz
92 92  
93 -== 1.4  Installation ==
87 +== 1.4  Mechanical ==
94 94  
95 95  
96 -Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
90 +[[image:image-20221117114937-4.png]]
97 97  
98 -[[image:image-20221021110329-1.png]]
99 99  
93 +[[image:image-20221117114949-5.png]]
100 100  
101 -[[image:image-20221022234602-2.png||height="288" width="922"]]
102 102  
96 +[[image:image-20221117115010-6.png]]
103 103  
104 104  
99 +
105 105  == 1.5 ​ Applications ==
106 106  
107 107  
108 -* Open/Close Detection
109 -* Pulse meter application
110 -* Dry Contact Detection
103 +[[image:image-20221117114842-3.png]]
111 111  
112 -== 1.6  Mechanical ==
113 113  
114 114  
115 -​[[image:image-20221021110415-3.png]]
107 +== 1.6  Specification ==
116 116  
117 117  
110 +(% style="color:blue" %)**Common DC Characteristics:**
118 118  
112 +* Supply Voltage: 2.1v ~~ 3.6v
113 +* Operating Temperature: -40 ~~ 85°C
114 +
115 +(% style="color:blue" %)**NB-IoT Spec:**
116 +
117 +* B1 @H-FDD: 2100MHz
118 +* B3 @H-FDD: 1800MHz
119 +* B8 @H-FDD: 900MHz
120 +* B5 @H-FDD: 850MHz
121 +* B20 @H-FDD: 800MHz
122 +* B28 @H-FDD: 700MHz
123 +
124 +
125 +
119 119  == 1.7  Pin Definitions and Switch ==
120 120  
121 121  
... ... @@ -125,10 +125,9 @@
125 125  === 1.7.1  Pin Definition ===
126 126  
127 127  
128 -CPN01 is pre-configured to connect to two external wires. The other pins are not used. If user wants to know more about other pins, please refer to the **[[LSN50v2 User Manual>>doc:Main.User Manual for LoRaWAN End Nodes.LSN50 & LSN50-V2 - LoRaWAN Sensor Node User Manual.WebHome]]**.
135 +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]]
129 129  
130 130  
131 -
132 132  === 1.7.2  Jumper JP2(Power ON/OFF) ===
133 133  
134 134  
... ... @@ -135,7 +135,6 @@
135 135  Power on Device when putting this jumper.
136 136  
137 137  
138 -
139 139  === 1.7.3  BOOT MODE / SW1 ===
140 140  
141 141  
... ... @@ -144,7 +144,6 @@
144 144  2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
145 145  
146 146  
147 -
148 148  === 1.7.4  Reset Button ===
149 149  
150 150  
... ... @@ -151,7 +151,6 @@
151 151  Press to reboot the device.
152 152  
153 153  
154 -
155 155  === 1.7.5  LED ===
156 156  
157 157  
... ... @@ -162,40 +162,42 @@
162 162  2.  Send an uplink packet
163 163  
164 164  
168 +== 1.8  Magnet Distance ==
165 165  
166 -= 2.  Use CPN01 to communicate with IoT Server =
167 167  
171 +(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
168 168  
169 -== 2.1  How it works ==
173 +(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
170 170  
171 171  
172 -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.
176 += 2.  Use NDS03A to communicate with IoT Server =
173 173  
174 -The diagram below shows the working flow in the default firmware of CPN01:
178 +== 2.1  How it works ==
175 175  
176 -[[image:image-20221021110615-5.png]]
177 177  
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.
178 178  
183 +The diagram below shows the working flow in the default firmware of NDS03A:
179 179  
180 -== 2.2 ​ Configure CPN01 ==
185 +[[image:image-20221021110615-5.png]]
181 181  
182 182  
188 +== 2.2 ​ Configure NDS03A ==
189 +
183 183  === 2.2.1 Test Requirement ===
184 184  
185 185  
186 -To use CPN01 in your city, make sure to meet below requirements:
193 +To use NDS03A in your city, make sure to meet below requirements:
187 187  
188 188  * Your local operator has already distributed an NB-IoT Network.
189 -* The local NB-IoT network used the band that CPN01 supports.
196 +* The local NB-IoT network used the band that NDS03A supports.
190 190  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
191 191  
192 -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.
199 +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.
193 193  
194 -[[image:image-20221023000439-3.png]]
201 +[[image:image-20221117142300-1.png]]
195 195  
196 - ​
197 197  
198 -
199 199  === 2.2.2 Insert NB-IoT SIM card ===
200 200  
201 201  
... ... @@ -206,12 +206,11 @@
206 206  [[image:image-20221021110745-6.png]] ​
207 207  
208 208  
214 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
209 209  
210 -=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
211 211  
217 +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.
212 212  
213 -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.
214 -
215 215  (% style="color:blue" %)**Connection:**
216 216  
217 217  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -233,11 +233,11 @@
233 233  
234 234  * Flow Control: (% style="color:red" %)**None**
235 235  
236 -Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
240 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
237 237  
238 238  ​[[image:image-20221021110817-7.png]]
239 239  
240 -CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
244 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
241 241  
242 242  
243 243  (% 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]]
... ... @@ -250,7 +250,7 @@
250 250  (% 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/]]
251 251  
252 252  
253 -(% style="color:blue" %)**Use below commands in CPN01:**
257 +(% style="color:blue" %)**Use below commands in NDS03A:**
254 254  
255 255  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
256 256  
... ... @@ -263,12 +263,11 @@
263 263  [[image:image-20221021110948-8.png]]
264 264  
265 265  
266 -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.
270 +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.
267 267  
268 -[[image:image-20221021110956-9.png]] ​
272 +[[image:image-20221118103547-9.png||height="605" width="837"]] ​
269 269  
270 270  
271 -
272 272  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
273 273  
274 274  
... ... @@ -287,7 +287,6 @@
287 287  
288 288  ​
289 289  
290 -
291 291  === 2.2.6 Use MQTT protocol to uplink data ===
292 292  
293 293  
... ... @@ -307,10 +307,10 @@
307 307  
308 308  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
309 309  
310 -​ [[image:image-20221021111058-12.png]]
312 +​ [[image:image-20221118103445-7.png]]
311 311  
312 312  
313 -[[image:image-20221021111201-16.png||height="472" width="653"]]
315 +[[image:image-20221118103453-8.png||height="608" width="841"]]
314 314  
315 315  ​
316 316  
... ... @@ -317,7 +317,6 @@
317 317  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.
318 318  
319 319  
320 -
321 321  === 2.2.7 Use TCP protocol to uplink data ===
322 322  
323 323  
... ... @@ -333,76 +333,89 @@
333 333  
334 334  ​
335 335  
336 -
337 337  === 2.2.8 Change Update Interval ===
338 338  
339 339  
340 340  User can use below command to change the (% style="color:blue" %)**uplink interval**.
341 341  
342 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
342 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
343 343  
344 344  (% style="color:red" %)**NOTE:**
345 345  
346 -1.  By default, the device will send an uplink message every 1 hour.
346 +1.  By default, the device will send an uplink message every 4 hour.
347 347  
348 348  
349 -
350 350  == 2.3  Uplink Payload ==
351 351  
352 352  
353 -The uplink payload includes 123 bytes in total by default.
352 +The uplink payload includes 26 bytes in total by default.
354 354  
355 -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.
354 +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.
356 356  
356 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
357 357  
358 -(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
359 -|=(% 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**
360 -|=(% 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"]]
358 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
359 +|=(% 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**
360 +|=(% 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)
361 361  
362 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
363 -|(% 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**
364 -|(% 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" %)...
362 +(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
363 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
364 +**1-32 group**
365 +)))
366 +|(% 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" %)...
365 365  
366 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
368 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
367 367  
368 -[[image:image-20221021111201-16.png||height="572" width="792"]]
369 369  
371 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
372 +|=(% 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**
373 +|=(% 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)
370 370  
375 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
376 +|(% 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**
377 +|(% 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)
378 +
379 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
380 +|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
381 +**1-32 group**
382 +)))
383 +|(% 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" %)......
384 +
385 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
386 +
387 +[[image:image-20221117145932-2.png]]
388 +
389 +
371 371  The payload is ASCII string, representative same HEX:
372 372  
373 -**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 __**
392 +**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__(%%)**
374 374  
375 375  **where:**
376 376  
377 377  * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
378 378  
379 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
398 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
380 380  
381 -* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
400 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
382 382  
383 -* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
402 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
384 384  
385 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
404 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
386 386  
387 -* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
406 +* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
388 388  
389 -* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
408 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
390 390  
391 -* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
410 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
392 392  
393 -* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
412 +* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
394 394  
395 -* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
414 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
396 396  
397 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
398 398  
399 -* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
400 400  
401 -* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
402 -
403 403  == 2.4  Payload Explanation and Sensor Interface ==
404 404  
405 -
406 406  === 2.4.1  Device ID ===
407 407  
408 408  
... ... @@ -417,20 +417,18 @@
417 417  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
418 418  
419 419  
420 -
421 421  === 2.4.2  Version Info ===
422 422  
423 423  
424 424  Specify the software version: 0x64=100, which means firmware version 1.00.
425 425  
426 -For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
439 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
427 427  
428 428  
429 -
430 430  === 2.4.3  Battery Info ===
431 431  
432 432  
433 -Check the battery voltage for CPN01.
445 +Check the battery voltage for NDS03A.
434 434  
435 435  Ex1: 0x0B45 = 2885mV
436 436  
... ... @@ -437,7 +437,6 @@
437 437  Ex2: 0x0B49 = 2889mV
438 438  
439 439  
440 -
441 441  === 2.4.4  Signal Strength ===
442 442  
443 443  
... ... @@ -456,70 +456,38 @@
456 456  **99**    Not known or not detectable
457 457  
458 458  
470 +=== 2.4.5  Disalarm: (default: 0) ===
459 459  
460 -=== 2.4.5  Calculate Flag ===
461 461  
473 +(% 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.
462 462  
463 -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.
475 +(% 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.
464 464  
465 -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.
477 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
466 466  
467 -Default value: 0. 
468 468  
469 -Range (6 bits): (b)000000 ~~ (b) 111111
480 +=== 2.4.6  Keep Status & Keep Time ===
470 470  
471 471  
483 +Shows the configure value of Alarm Base on Timeout Feature
472 472  
473 -=== 2.4.6  Alarm ===
474 474  
486 +=== 2.4.7  Timestamp ===
475 475  
476 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
477 477  
489 +Timestamp : 0x6315537b =1662342011
478 478  
479 479  
480 -=== 2.4.7  Contact Status ===
492 +=== 2.4.8  Switch Dual Channel Mode ===
481 481  
482 482  
483 -0: Open
495 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
484 484  
485 -1: Close
486 486  
487 -
488 -
489 -=== 2.4.8  Total pulse ===
490 -
491 -
492 -Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
493 -
494 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
495 -
496 -
497 -
498 -=== 2.4.9  The last open duration ===
499 -
500 -
501 -Dry Contact last open duration.
502 -
503 -Unit: min.
504 -
505 -[[image:image-20221021111346-17.png||height="146" width="770"]]
506 -
507 -
508 -
509 -=== 2.4.10  Timestamp ===
510 -
511 -
512 -Timestamp : 0x6315537b =1662342011
513 -
514 -Convert Unix timestamp to time 2022-9-5 9:40:11.
515 -
516 -**~ **
517 -
518 -
519 519  == 2.5  Downlink Payload ==
520 520  
521 521  
522 -By default, CPN01 prints the downlink payload to console port.
501 +By default, NDS03A prints the downlink payload to console port.
523 523  
524 524  [[image:image-20221021111414-18.png]] ​
525 525  
... ... @@ -536,7 +536,7 @@
536 536  
537 537  * (% style="color:#037691" %)**Reset**
538 538  
539 -If payload = 0x04FF, it will reset the NSE01
518 +If payload = 0x04FF, it will reset the NDS03A
540 540  
541 541  * (% style="color:#037691" %)**INTMOD**
542 542  
... ... @@ -543,20 +543,21 @@
543 543  Downlink Payload: 06000003, Set AT+INTMOD=3
544 544  
545 545  
546 -
547 547  == 2.6  ​LED Indicator ==
548 548  
549 549  
550 -The CPN01 has an internal LED which is to show the status of different states.
528 +The NDS03A has an internal LED which is to show the status of different states.
551 551  
552 552  * When the device starts normally, the LED will light up for 1 second.
553 -* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
531 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
554 554  * For each uplink probe, LED will be on for 500ms.
555 555  
534 +
535 +
556 556  == 2.7  Alarm Base on Timeout ==
557 557  
558 558  
559 -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:
539 +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:
560 560  
561 561  
562 562  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -572,17 +572,25 @@
572 572  
573 573  If keep time = 0, Disable Alarm Base on Timeout feature.
574 574  
575 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
555 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
576 576  
577 577  
578 578  (% style="color:blue" %)**AT Command to configure:**
579 579  
580 -(% 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.
560 +(% style="color:blue" %)**PB14 PIN:**
581 581  
562 +(% 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.
563 +
582 582  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
583 583  
584 584  
567 +(% style="color:blue" %)**PB15 PIN:**
585 585  
569 +(% style="color:#037691" %)**AT+TTRIG2=1,30**
570 +
571 +(% style="color:#037691" %)**AT+TTRIG2=0,0 **
572 +
573 +
586 586  == 2.8  Set debug mode ==
587 587  
588 588  
... ... @@ -604,54 +604,57 @@
604 604  [[image:image-20221021111527-19.png]]
605 605  
606 606  
595 +== 2.10  Count Mod ==
607 607  
608 -== 2.10  Set trigger mode ==
609 609  
598 +(% style="color:blue" %)**AT Command: AT+COUNTMOD**
610 610  
611 -(% style="color:blue" %)**AT Command: AT+TTRMOD**
600 +[[image:image-20221118092935-1.png]]
612 612  
613 -Feature: Set the trigger interrupt mode.
614 614  
615 -[[image:image-20221021111552-20.png]]
603 +== 2.11  Interrupt Pin Channel Mod ==
616 616  
617 617  
606 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
618 618  
619 -== 2.11  Set the calculate flag ==
608 +[[image:image-20221118093144-2.png]]
620 620  
621 621  
622 -Feature: Set the calculate flag
611 +== 2.12 TTRIG1/2 timeout status alarm ==
623 623  
624 -(% style="color:blue" %)**AT Command: AT+CALCFLAG**
625 625  
626 -[[image:image-20221021111711-22.png]]
614 +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.
627 627  
616 +(% style="color:blue" %)**AT Command: AT+TTRALARM**
628 628  
618 +[[image:image-20221118093512-3.png]]
629 629  
630 -== 2.12 Set count number ==
631 631  
621 +== 2.13  Select counting mode ==
632 632  
633 -Feature: Manually set the count number
634 634  
635 -(% style="color:blue" %)**AT Command: AT+SETCNT**
624 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
636 636  
637 -[[image:image-20221021111748-24.png]]
626 +When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
638 638  
628 +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.
639 639  
630 +[[image:image-20221118093658-4.png]]
640 640  
641 -== 2.13  Set the number of data to be uploaded and the recording time ==
642 642  
633 +== 2.14  Set the number of data to be uploaded and the recording time ==
643 643  
635 +
644 644  (% style="color:blue" %)**AT Command:**
645 645  
646 -(% 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)
638 +(% 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)
647 647  
648 -(% 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.
640 +(% 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.
649 649  
650 650  
643 +== 2.15  Read or Clear cached data ==
651 651  
652 -== 2.14  Read or Clear cached data ==
653 653  
654 -
655 655  (% style="color:blue" %)**AT Command:**
656 656  
657 657  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -658,27 +658,24 @@
658 658  
659 659  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
660 660  
661 -[[image:image-20221021111810-25.png||height="364" width="797"]]
652 +[[image:image-20221118094227-5.png]]
662 662  
663 663  
655 +== 2.16  ​Firmware Change Log ==
664 664  
665 -== 2.15  ​Firmware Change Log ==
666 666  
658 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
667 667  
668 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
669 -
670 670  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
671 671  
672 672  
663 +== 2.17  ​Battery Analysis ==
673 673  
674 -== 2.16  ​Battery Analysis ==
665 +=== 2.17.1  ​Battery Type ===
675 675  
676 676  
677 -=== 2.16.1  ​Battery Type ===
668 +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.
678 678  
679 -
680 -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.
681 -
682 682  The battery is designed to last for several years depends on the actual use environment and update interval. 
683 683  
684 684  The battery-related documents as below:
... ... @@ -692,10 +692,9 @@
692 692  [[image:image-20221021111911-26.png]] ​
693 693  
694 694  
683 +=== 2.17.2  Power consumption Analyze ===
695 695  
696 -=== 2.16.2  Power consumption Analyze ===
697 697  
698 -
699 699  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.
700 700  
701 701  Instruction to use as below:
... ... @@ -715,21 +715,18 @@
715 715  [[image:1666596205057-567.png]] ​
716 716  
717 717  
705 +=== 2.17.3  ​Battery Note ===
718 718  
719 -=== 2.16.3  ​Battery Note ===
720 720  
721 -
722 722  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.
723 723  
724 724  
711 +=== 2.17.4  Replace the battery ===
725 725  
726 -=== 2.16.4  Replace the battery ===
727 727  
714 +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).
728 728  
729 -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).
730 730  
731 -
732 -
733 733  = 3. ​ Access NB-IoT Module =
734 734  
735 735  
... ... @@ -737,13 +737,12 @@
737 737  
738 738  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/]] 
739 739  
740 -[[image:image-20221021112006-28.png]] ​
741 741  
725 +[[image:image-20221118094449-6.png]] ​
742 742  
743 743  
744 744  = 4.  Using the AT Commands =
745 745  
746 -
747 747  == 4.1  Access AT Commands ==
748 748  
749 749  
... ... @@ -790,15 +790,21 @@
790 790  
791 791  AT+ DEBUG   : Enable or Disable debug mode
792 792  
793 -AT+ TTRIG   : Get or Set Alarm Base on Timeout
776 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
794 794  
795 -AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
778 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
796 796  
797 -AT+ CALCFLAG   : Get or Set the calculate flag
780 +AT+COUNTMOD  :  Get or Set the count mode
798 798  
799 -AT+ CLRC   : Clear current door open count
782 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
800 800  
784 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
801 801  
786 +AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
787 +
788 +AT+ CLRC   :  Clear current door open count
789 +
790 +
802 802  (% style="color:blue" %)**COAP Management**      
803 803  
804 804  AT+URI            : Resource parameters
... ... @@ -829,10 +829,8 @@
829 829  AT+PWORD  : Serial Access Password
830 830  
831 831  
832 -
833 833  = ​5.  FAQ =
834 834  
835 -
836 836  == 5.1 ​ How to Upgrade Firmware ==
837 837  
838 838  
... ... @@ -840,13 +840,11 @@
840 840  
841 841  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]]
842 842  
843 -(% 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.**
830 +(% 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.**
844 844  
845 845  
846 -
847 847  = 6.  Trouble Shooting =
848 848  
849 -
850 850  == 6.1  ​Connection problem when uploading firmware ==
851 851  
852 852  
... ... @@ -853,7 +853,6 @@
853 853  (% 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]]
854 854  
855 855  
856 -
857 857  == 6.2  AT Command input doesn't work ==
858 858  
859 859  
... ... @@ -860,26 +860,20 @@
860 860  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.
861 861  
862 862  
863 -
864 864  = 7. ​ Order Info =
865 865  
866 866  
867 -Part Number**:** CPN01
850 +Part Number**:** NDS03A
868 868  
869 869  
870 -
871 871  = 8.  Packing Info =
872 872  
873 873  
874 874  (% style="color:blue" %)**Package Includes**:
875 875  
876 -* CPN01 Open/Close Sensor x 1
877 -* External antenna x 1
858 +* NDS03A Open/Close Door Sensor x 1
878 878  
879 -(% style="color:blue" %)**Dimension and weight**:
880 880  
881 -* Size: 195 x 125 x 55 mm
882 -* Weight:   420g
883 883  
884 884  = 9.  Support =
885 885  
image-20221117115010-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +40.4 KB
Content
image-20221117142300-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +51.9 KB
Content
image-20221117150312-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +8.7 KB
Content
image-20221118092935-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +9.5 KB
Content
image-20221118093658-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +12.7 KB
Content
image-20221118094227-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +29.2 KB
Content
image-20221118094449-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.5 KB
Content
image-20221118103445-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +43.5 KB
Content

Applications

Navigation

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