Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 70.2 >
edited by Xiaoling
on 2022/11/18 10:39
To version < 52.5 >
edited by Xiaoling
on 2022/10/25 15:59
>
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 +CPN01- NB-IoT Outdoor Open/Close Dry Contact Sensor User Manual
Content
... ... @@ -1,12 +1,8 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20221117105556-1.png]]
2 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/WebHome/1652856952171-363.png?rev=1.1||alt="1652856952171-363.png" height="578" width="588"]]
3 3  
4 4  
5 5  
6 -
7 -
8 -
9 -
10 10  **Table of Contents：**
11 11  
12 12  {{toc/}}
... ... @@ -17,43 +17,36 @@
17 17  
18 18  = 1.  Introduction =
19 19  
20 -== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
21 21  
17 +== 1.1 ​ What is CPN01 NB-IoT Pulse/Contact Sensor ==
22 22  
23 -(((
24 -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.
25 -)))
26 26  
27 27  (((
28 -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.
21 +The Dragino CPN01 is an (% style="color:blue" %)**NB-IoT Dry Contact Sensor**(%%). It detects open/close status and uplinks the info to IoT server via NB-IoT network. User can see the (% style="color:blue" %)**dry contact status, open time, and open counts**(%%) in the IoT Server.
29 29  )))
30 30  
31 31  (((
32 -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.
25 +The CPN01 will send periodically data every day as well as for each dry contact action. It also counts the contact open times and calculates the last open duration. Users can also disable the uplink for each Open/Close event, instead, device can count each open event and uplink periodically.
33 33  )))
34 34  
35 35  (((
36 -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.
29 +CPN01 has** (% style="color:blue" %)Open-Alarm feature(%%)**, user can set this feature so CPN01 will send an alarm if the contact has been open exceeds a certain time.
37 37  )))
38 38  
39 39  (((
40 -NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
33 +CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures.
41 41  )))
42 42  
43 43  (((
44 -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.
37 +NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
38 +\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
39 +\\CPN01 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
40 +\\To use CPN01, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that CPN01 supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into CPN01 to get NB-IoT network connection.
45 45  )))
46 46  
47 -(((
48 -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)
49 -)))
43 +​
50 50  
51 -(((
52 -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.
53 -)))
54 54  
55 -
56 -
57 57  == ​1.2  Features ==
58 58  
59 59  
... ... @@ -61,7 +61,7 @@
61 61  * Open/Close detect
62 62  * Open/Close statistics
63 63  * Monitor Battery Level
64 -* connect two door sensors
53 +* Uplink on periodically and open/close event
65 65  * Datalog feature
66 66  * Uplink periodically
67 67  * Downlink to change configure
... ... @@ -74,48 +74,50 @@
74 74  
75 75  
76 76  
77 -== 1.3  Storage & Operation ==
66 +== 1.3  Specification ==
78 78  
79 79  
80 -Temperature -40°C to +85°C
69 +(% style="color:blue" %)**Common DC Characteristics:**
81 81  
71 +* Supply Voltage: 2.1v ~~ 3.6v
72 +* Operating Temperature: -40 ~~ 85°C
82 82  
83 -== 1.4  Mechanical ==
74 +(% style="color:blue" %)**NB-IoT Spec:**
84 84  
76 +* - B1 @H-FDD: 2100MHz
77 +* - B3 @H-FDD: 1800MHz
78 +* - B8 @H-FDD: 900MHz
79 +* - B5 @H-FDD: 850MHz
80 +* - B20 @H-FDD: 800MHz
81 +* - B28 @H-FDD: 700MHz
85 85  
86 -[[image:image-20221117114937-4.png]]
87 87  
88 88  
89 -[[image:image-20221117114949-5.png]]
85 +== 1.4  Installation ==
90 90  
91 91  
92 -[[image:image-20221117115010-6.png]]
88 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
93 93  
90 +[[image:image-20221021110329-1.png]]
94 94  
95 95  
96 -== 1.5 ​ Applications ==
93 +[[image:image-20221022234602-2.png||height="288" width="922"]]
97 97  
98 98  
99 -[[image:image-20221117114842-3.png]]
100 100  
97 +== 1.5 ​ Applications ==
101 101  
102 102  
103 -== 1.6  Specification ==
100 +* Open/Close Detection
101 +* Pulse meter application
102 +* Dry Contact Detection
104 104  
105 105  
106 -(% style="color:blue" %)**Common DC Characteristics:**
107 107  
108 -* Supply Voltage: 2.1v ~~ 3.6v
109 -* Operating Temperature: -40 ~~ 85°C
106 +== 1.6  Mechanical ==
110 110  
111 -(% style="color:blue" %)**NB-IoT Spec:**
112 112  
113 -* - B1 @H-FDD: 2100MHz
114 -* - B3 @H-FDD: 1800MHz
115 -* - B8 @H-FDD: 900MHz
116 -* - B5 @H-FDD: 850MHz
117 -* - B20 @H-FDD: 800MHz
118 -* - B28 @H-FDD: 700MHz
109 +​[[image:image-20221021110415-3.png]]
119 119  
120 120  
121 121  
... ... @@ -128,7 +128,7 @@
128 128  === 1.7.1  Pin Definition ===
129 129  
130 130  
131 -The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at:  [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
122 +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]]**.
132 132  
133 133  
134 134  
... ... @@ -166,42 +166,35 @@
166 166  
167 167  
168 168  
169 -== 1.8  Magnet Distance ==
160 += 2.  Use CPN01 to communicate with IoT Server =
170 170  
171 171  
172 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
173 -
174 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
175 -
176 -
177 -
178 -= 2.  Use NDS03A to communicate with IoT Server =
179 -
180 180  == 2.1  How it works ==
181 181  
182 182  
183 -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.
166 +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.
184 184  
185 -The diagram below shows the working flow in the default firmware of NDS03A:
168 +The diagram below shows the working flow in the default firmware of CPN01:
186 186  
187 187  [[image:image-20221021110615-5.png]]
188 188  
189 189  
190 190  
191 -== 2.2 ​ Configure NDS03A ==
174 +== 2.2 ​ Configure CPN01 ==
192 192  
176 +
193 193  === 2.2.1 Test Requirement ===
194 194  
195 195  
196 -To use NDS03A in your city, make sure to meet below requirements:
180 +To use CPN01 in your city, make sure to meet below requirements:
197 197  
198 198  * Your local operator has already distributed an NB-IoT Network.
199 -* The local NB-IoT network used the band that NDS03A supports.
183 +* The local NB-IoT network used the band that CPN01 supports.
200 200  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
201 201  
202 -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.
186 +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.
203 203  
204 -[[image:image-20221117142300-1.png]]
188 +[[image:image-20221023000439-3.png]]
205 205  
206 206   ​
207 207  
... ... @@ -217,10 +217,10 @@
217 217  
218 218  
219 219  
220 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
204 +=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
221 221  
222 222  
223 -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.
207 +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.
224 224  
225 225  (% style="color:blue" %)**Connection:**
226 226  
... ... @@ -243,11 +243,11 @@
243 243  
244 244  * Flow Control: (% style="color:red" %)**None**
245 245  
246 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
230 +Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
247 247  
248 248  ​[[image:image-20221021110817-7.png]]
249 249  
250 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
234 +CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
251 251  
252 252  
253 253  (% 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]]
... ... @@ -260,7 +260,7 @@
260 260  (% 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/]]
261 261  
262 262  
263 -(% style="color:blue" %)**Use below commands in NDS03A:**
247 +(% style="color:blue" %)**Use below commands in CPN01:**
264 264  
265 265  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
266 266  
... ... @@ -273,9 +273,9 @@
273 273  [[image:image-20221021110948-8.png]]
274 274  
275 275  
276 -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.
260 +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.
277 277  
278 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
262 +[[image:image-20221021110956-9.png]] ​
279 279  
280 280  
281 281  
... ... @@ -317,10 +317,10 @@
317 317  
318 318  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
319 319  
320 -​ [[image:image-20221118103445-7.png]]
304 +​ [[image:image-20221021111058-12.png]]
321 321  
322 322  
323 -[[image:image-20221118103453-8.png||height="608" width="841"]]
307 +[[image:image-20221021111201-16.png||height="472" width="653"]]
324 324  
325 325  ​
326 326  
... ... @@ -349,11 +349,11 @@
349 349  
350 350  User can use below command to change the (% style="color:blue" %)**uplink interval**.
351 351  
352 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
336 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
353 353  
354 354  (% style="color:red" %)**NOTE:**
355 355  
356 -1.  By default, the device will send an uplink message every 4 hour.
340 +1.  By default, the device will send an uplink message every 1 hour.
357 357  
358 358  
359 359  
... ... @@ -360,76 +360,61 @@
360 360  == 2.3  Uplink Payload ==
361 361  
362 362  
363 -The uplink payload includes 26 bytes in total by default.
347 +The uplink payload includes 123 bytes in total by default.
364 364  
365 -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.
349 +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.
366 366  
367 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
368 368  
369 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
370 -|=(% scope="row" style="width: 93px;" %)**Size(bytes)**|(% style="width:67px" %)**8**|(% style="width:40px" %)**2**|(% style="width:45px" %)**2**|(% style="width:75px" %)**1**|(% style="width:54px" %)**1**|(% style="width:62px" %)**1**|(% style="width:60px" %)**1**|(% style="width:94px" %)**3**|(% style="width:93px" %)**3**
371 -|=(% 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)
352 +(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
353 +|=(% 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**
354 +|=(% 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"]]
372 372  
373 373  (% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
374 -|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)(((
375 -**1-32 group**
376 -)))
377 -|(% 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" %)...
357 +|(% style="width:120px" %)**3**|(% style="width:50px" %)**4**|(% style="width:80px" %)**1**|(% style="width:50px" %)**3**|(% style="width:120px" %)**3**|(% style="width:80px" %)4|(% style="width:50px" %)**8 group**
358 +|(% 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" %)...
378 378  
360 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
379 379  
362 +[[image:image-20221021111201-16.png||height="572" width="792"]]
380 380  
381 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
382 382  
383 -
384 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
385 -|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:66px" %)**8**|(% style="width:40px" %)**2**|(% style="width:46px" %)**2**|(% style="width:70px" %)**1**|(% style="width:54px" %)**1**|(% style="width:55px" %)**1**|(% style="width:57px" %)**1**|(% style="width:86px" %)**3**|(% style="width:82px" %)**3**
386 -|=(% 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)
387 -
388 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
389 -|(% style="width:59px" %)**1**|(% style="width:67px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:66px" %)**1**|(% style="width:92px" %)**3**
390 -|(% 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)
391 -
392 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
393 -|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
394 -**1-32 group**
395 -)))
396 -|(% style="width:102px" %)last open time (pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:88px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
397 -
398 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
399 -
400 -[[image:image-20221117145932-2.png]]
401 -
402 -
403 403  The payload is ASCII string, representative same HEX:
404 404  
405 -**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__(%%)**
367 +**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 __**
406 406  
407 407  **where:**
408 408  
409 409  * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
410 410  
411 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
373 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
412 412  
413 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
375 +* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
414 414  
415 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
377 +* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
416 416  
417 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
379 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
418 418  
419 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
381 +* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
420 420  
421 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
383 +* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
422 422  
423 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
385 +* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
424 424  
425 -* (% style="color:#037691" %)**last open time:  **(%%)0x000017 =23
387 +* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
426 426  
427 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
389 +* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
428 428  
391 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
429 429  
393 +* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
430 430  
395 +* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
396 +
397 +
398 +
431 431  == 2.4  Payload Explanation and Sensor Interface ==
432 432  
401 +
433 433  === 2.4.1  Device ID ===
434 434  
435 435  
... ... @@ -444,18 +444,20 @@
444 444  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
445 445  
446 446  
416 +
447 447  === 2.4.2  Version Info ===
448 448  
449 449  
450 450  Specify the software version: 0x64=100, which means firmware version 1.00.
451 451  
452 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
422 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
453 453  
454 454  
425 +
455 455  === 2.4.3  Battery Info ===
456 456  
457 457  
458 -Check the battery voltage for NDS03A.
429 +Check the battery voltage for CPN01.
459 459  
460 460  Ex1: 0x0B45 = 2885mV
461 461  
... ... @@ -462,6 +462,7 @@
462 462  Ex2: 0x0B49 = 2889mV
463 463  
464 464  
436 +
465 465  === 2.4.4  Signal Strength ===
466 466  
467 467  
... ... @@ -480,38 +480,70 @@
480 480  **99**    Not known or not detectable
481 481  
482 482  
483 -=== 2.4.5  Disalarm: (default: 0) ===
484 484  
456 +=== 2.4.5  Calculate Flag ===
485 485  
486 -(% 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.
487 487  
488 -(% 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.
459 +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.
489 489  
490 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
461 +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.
491 491  
463 +Default value: 0. 
492 492  
493 -=== 2.4.6  Keep Status & Keep Time ===
465 +Range (6 bits): (b)000000 ~~ (b) 111111
494 494  
495 495  
496 -Shows the configure value of Alarm Base on Timeout Feature
497 497  
469 +=== 2.4.6  Alarm ===
498 498  
499 -=== 2.4.7  Timestamp ===
500 500  
472 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
501 501  
502 -Timestamp : 0x6315537b =1662342011
503 503  
504 504  
505 -=== 2.4.8  Switch Dual Channel Mode ===
476 +=== 2.4.7  Contact Status ===
506 506  
507 507  
508 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
479 +0: Open
509 509  
481 +1: Close
510 510  
483 +
484 +
485 +=== 2.4.8  Total pulse ===
486 +
487 +
488 +Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
489 +
490 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
491 +
492 +
493 +
494 +=== 2.4.9  The last open duration ===
495 +
496 +
497 +Dry Contact last open duration.
498 +
499 +Unit: min.
500 +
501 +[[image:image-20221021111346-17.png||height="146" width="770"]]
502 +
503 +
504 +
505 +=== 2.4.10  Timestamp ===
506 +
507 +
508 +Timestamp : 0x6315537b =1662342011
509 +
510 +Convert Unix timestamp to time 2022-9-5 9:40:11.
511 +
512 +**~ **
513 +
514 +
511 511  == 2.5  Downlink Payload ==
512 512  
513 513  
514 -By default, NDS03A prints the downlink payload to console port.
518 +By default, CPN01 prints the downlink payload to console port.
515 515  
516 516  [[image:image-20221021111414-18.png]] ​
517 517  
... ... @@ -528,7 +528,7 @@
528 528  
529 529  * (% style="color:#037691" %)**Reset**
530 530  
531 -If payload = 0x04FF, it will reset the NDS03A
535 +If payload = 0x04FF, it will reset the NSE01
532 532  
533 533  * (% style="color:#037691" %)**INTMOD**
534 534  
... ... @@ -535,13 +535,14 @@
535 535  Downlink Payload: 06000003, Set AT+INTMOD=3
536 536  
537 537  
542 +
538 538  == 2.6  ​LED Indicator ==
539 539  
540 540  
541 -The NDS03A has an internal LED which is to show the status of different states.
546 +The CPN01 has an internal LED which is to show the status of different states.
542 542  
543 543  * When the device starts normally, the LED will light up for 1 second.
544 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
549 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
545 545  * For each uplink probe, LED will be on for 500ms.
546 546  
547 547  
... ... @@ -549,7 +549,7 @@
549 549  == 2.7  Alarm Base on Timeout ==
550 550  
551 551  
552 -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:
557 +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:
553 553  
554 554  
555 555  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -565,25 +565,17 @@
565 565  
566 566  If keep time = 0, Disable Alarm Base on Timeout feature.
567 567  
568 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
573 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
569 569  
570 570  
571 571  (% style="color:blue" %)**AT Command to configure:**
572 572  
573 -(% style="color:blue" %)**PB14 PIN:**
578 +(% 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.
574 574  
575 -(% 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.
576 -
577 577  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
578 578  
579 579  
580 -(% style="color:blue" %)**PB15 PIN:**
581 581  
582 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
583 -
584 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
585 -
586 -
587 587  == 2.8  Set debug mode ==
588 588  
589 589  
... ... @@ -606,88 +606,79 @@
606 606  
607 607  
608 608  
609 -== 2.10  Count Mod ==
606 +== 2.10  Set trigger mode ==
610 610  
611 611  
612 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
609 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
613 613  
614 -[[image:image-20221118092935-1.png]]
611 +Feature: Set the trigger interrupt mode.
615 615  
613 +[[image:image-20221021111552-20.png]]
616 616  
617 617  
618 -== 2.11  Interrupt Pin Channel Mod ==
619 619  
617 +== 2.11  Set the calculate flag ==
620 620  
621 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
622 622  
623 -[[image:image-20221118093144-2.png]]
620 +Feature: Set the calculate flag
624 624  
622 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
625 625  
624 +[[image:image-20221021111711-22.png]]
626 626  
627 -== 2.12 TTRIG1/2 timeout status alarm ==
628 628  
629 629  
630 -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.
628 +== 2.12 Set count number ==
631 631  
632 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
633 633  
634 -[[image:image-20221118093512-3.png]]
631 +Feature: Manually set the count number
635 635  
633 +(% style="color:blue" %)**AT Command: AT+SETCNT**
636 636  
635 +[[image:image-20221021111748-24.png]]
637 637  
638 -== 2.13  Select counting mode ==
639 639  
640 640  
641 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
639 +== 2.13  Set the number of data to be uploaded and the recording time ==
642 642  
643 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
644 644  
645 -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.
642 +(% style="color:blue" %)**AT Command:**
646 646  
647 -[[image:image-20221118093658-4.png]]
644 +(% 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)
648 648  
646 +(% 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.
649 649  
650 650  
651 651  
652 -== 2.14  Set the number of data to be uploaded and the recording time ==
650 +== 2.14  Read or Clear cached data ==
653 653  
654 654  
655 655  (% style="color:blue" %)**AT Command:**
656 656  
657 -(% style="color:#037691" %)**AT+TR=900**(%%)  ~/~/  The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
658 -
659 -(% 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.
660 -
661 -
662 -== 2.15  Read or Clear cached data ==
663 -
664 -
665 -(% style="color:blue" %)**AT Command:**
666 -
667 667  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
668 668  
669 669  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
670 670  
671 -[[image:image-20221118094227-5.png]]
659 +[[image:image-20221021111810-25.png||height="364" width="797"]]
672 672  
673 673  
674 674  
675 -== 2.16  ​Firmware Change Log ==
663 +== 2.15  ​Firmware Change Log ==
676 676  
677 677  
678 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
666 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
679 679  
680 680  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
681 681  
682 682  
683 683  
684 -== 2.17  ​Battery Analysis ==
672 +== 2.16  ​Battery Analysis ==
685 685  
686 686  
687 -=== 2.17.1  ​Battery Type ===
675 +=== 2.16.1  ​Battery Type ===
688 688  
689 689  
690 -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 +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.
691 691  
692 692  The battery is designed to last for several years depends on the actual use environment and update interval. 
693 693  
... ... @@ -703,7 +703,7 @@
703 703  
704 704  
705 705  
706 -=== 2.17.2  Power consumption Analyze ===
694 +=== 2.16.2  Power consumption Analyze ===
707 707  
708 708  
709 709  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.
... ... @@ -726,7 +726,7 @@
726 726  
727 727  
728 728  
729 -=== 2.17.3  ​Battery Note ===
717 +=== 2.16.3  ​Battery Note ===
730 730  
731 731  
732 732  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.
... ... @@ -733,10 +733,10 @@
733 733  
734 734  
735 735  
736 -=== 2.17.4  Replace the battery ===
724 +=== 2.16.4  Replace the battery ===
737 737  
738 738  
739 -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).
727 +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).
740 740  
741 741  
742 742  
... ... @@ -747,7 +747,7 @@
747 747  
748 748  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/]] 
749 749  
750 -[[image:image-20221118094449-6.png]] ​
738 +[[image:image-20221021112006-28.png]] ​
751 751  
752 752  
753 753  
... ... @@ -800,21 +800,15 @@
800 800  
801 801  AT+ DEBUG   : Enable or Disable debug mode
802 802  
803 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
791 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
804 804  
805 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
793 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
806 806  
807 -AT+COUNTMOD  :  Get or Set the count mode
795 +AT+ CALCFLAG   : Get or Set the calculate flag
808 808  
809 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
797 +AT+ CLRC   : Clear current door open count
810 810  
811 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
812 812  
813 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
814 -
815 -AT+ CLRC   :  Clear current door open count
816 -
817 -
818 818  (% style="color:blue" %)**COAP Management**      
819 819  
820 820  AT+URI            : Resource parameters
... ... @@ -856,7 +856,7 @@
856 856  
857 857  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]]
858 858  
859 -(% 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.**
841 +(% 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.**
860 860  
861 861  
862 862  
... ... @@ -880,7 +880,7 @@
880 880  = 7. ​ Order Info =
881 881  
882 882  
883 -Part Number**:** NDS03A
865 +Part Number**:** CPN01
884 884  
885 885  
886 886  
... ... @@ -889,8 +889,16 @@
889 889  
890 890  (% style="color:blue" %)**Package Includes**:
891 891  
892 -* NDS03A Open/Close Door Sensor x 1
874 +* CPN01 Open/Close Sensor x 1
875 +* External antenna x 1
893 893  
877 +(% style="color:blue" %)**Dimension and weight**:
878 +
879 +* Size: 195 x 125 x 55 mm
880 +* Weight:   420g
881 +
882 +
883 +
894 894  = 9.  Support =
895 895  
896 896  
image-20221117105556-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -133.3 KB
Content
image-20221117114459-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20221117114842-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -964.1 KB
Content
image-20221117114937-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.1 KB
Content
image-20221117114949-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -33.4 KB
Content
image-20221117115010-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -40.4 KB
Content
image-20221117142300-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -51.9 KB
Content
image-20221117150312-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.7 KB
Content
image-20221118092935-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.5 KB
Content
image-20221118093658-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -12.7 KB
Content
image-20221118094227-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.2 KB
Content
image-20221118094449-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.5 KB
Content
image-20221118103445-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.5 KB
Content

Applications

Navigation

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