Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 48.10 >
edited by Xiaoling
on 2022/10/24 16:15
To version < 67.5 >
edited by Xiaoling
on 2022/11/18 10:20
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -CPN01- NB-IoT Outdoor Open/Close Dry Contact Sensor User Manual
1 +NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
Content
... ... @@ -1,8 +1,12 @@
1 1  (% style="text-align:center" %)
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"]]
2 +[[image:image-20221117105556-1.png]]
3 3  
4 4  
5 5  
6 +
7 +
8 +
9 +
6 6  **Table of Contents：**
7 7  
8 8  {{toc/}}
... ... @@ -13,26 +13,43 @@
13 13  
14 14  = 1.  Introduction =
15 15  
20 +== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
16 16  
17 -== 1.1 ​ What is CPN01 NB-IoT Pulse/Contact Sensor ==
18 18  
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 +)))
19 19  
20 -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.
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.
29 +)))
21 21  
22 -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.
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.
33 +)))
23 23  
24 -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.
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.
37 +)))
25 25  
26 -CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures.
39 +(((
40 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
41 +)))
27 27  
28 -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.
29 -\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
30 -\\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)
31 -\\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.
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.
45 +)))
32 32  
33 -​
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 +)))
34 34  
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 +)))
35 35  
55 +
56 +
36 36  == ​1.2  Features ==
37 37  
38 38  
... ... @@ -40,7 +40,7 @@
40 40  * Open/Close detect
41 41  * Open/Close statistics
42 42  * Monitor Battery Level
43 -* Uplink on periodically and open/close event
64 +* connect two door sensors
44 44  * Datalog feature
45 45  * Uplink periodically
46 46  * Downlink to change configure
... ... @@ -51,53 +51,52 @@
51 51  * Micro SIM card slot for NB-IoT SIM
52 52  * 8500mAh Battery for long-term use
53 53  
75 +== 1.3  Storage & Operation ==
54 54  
55 -== 1.3  Specification ==
56 56  
78 +Temperature -40°C to +85°C
57 57  
58 -(% style="color:blue" %)**Common DC Characteristics:**
59 59  
60 -* Supply Voltage: 2.1v ~~ 3.6v
61 -* Operating Temperature: -40 ~~ 85°C
81 +== 1.4  Mechanical ==
62 62  
63 -(% style="color:blue" %)**NB-IoT Spec:**
64 64  
65 -* - B1 @H-FDD: 2100MHz
66 -* - B3 @H-FDD: 1800MHz
67 -* - B8 @H-FDD: 900MHz
68 -* - B5 @H-FDD: 850MHz
69 -* - B20 @H-FDD: 800MHz
70 -* - B28 @H-FDD: 700MHz
84 +[[image:image-20221117114937-4.png]]
71 71  
72 72  
73 -== 1.4  Installation ==
87 +[[image:image-20221117114949-5.png]]
74 74  
75 75  
76 -Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
90 +[[image:image-20221117115010-6.png]]
77 77  
78 -[[image:image-20221021110329-1.png]]
79 79  
80 -[[image:image-20221022234602-2.png||height="288" width="922"]]
81 81  
94 +== 1.5 ​ Applications ==
82 82  
83 83  
84 -== 1.5 ​ Applications ==
97 +[[image:image-20221117114842-3.png]]
85 85  
86 86  
87 -* Open/Close Detection
88 -* Pulse meter application
89 -* Dry Contact Detection
90 90  
101 +== 1.6  Specification ==
91 91  
92 -== 1.6  Mechanical ==
93 93  
104 +(% style="color:blue" %)**Common DC Characteristics:**
94 94  
95 -​[[image:image-20221021110415-3.png]]
106 +* Supply Voltage: 2.1v ~~ 3.6v
107 +* Operating Temperature: -40 ~~ 85°C
96 96  
109 +(% style="color:blue" %)**NB-IoT Spec:**
97 97  
111 +* - B1 @H-FDD: 2100MHz
112 +* - B3 @H-FDD: 1800MHz
113 +* - B8 @H-FDD: 900MHz
114 +* - B5 @H-FDD: 850MHz
115 +* - B20 @H-FDD: 800MHz
116 +* - B28 @H-FDD: 700MHz
98 98  
99 99  == 1.7  Pin Definitions and Switch ==
100 100  
120 +
101 101  [[image:image-20221021110429-4.png]]
102 102  
103 103  
... ... @@ -104,7 +104,7 @@
104 104  === 1.7.1  Pin Definition ===
105 105  
106 106  
107 -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]]**.
127 +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]]
108 108  
109 109  
110 110  
... ... @@ -142,35 +142,42 @@
142 142  
143 143  
144 144  
145 -= 2.  Use CPN01 to communicate with IoT Server =
165 +== 1.8  Magnet Distance ==
146 146  
147 147  
168 +(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
169 +
170 +(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
171 +
172 +
173 +
174 += 2.  Use NDS03A to communicate with IoT Server =
175 +
148 148  == 2.1  How it works ==
149 149  
150 150  
151 -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.
179 +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.
152 152  
153 -The diagram below shows the working flow in the default firmware of CPN01:
181 +The diagram below shows the working flow in the default firmware of NDS03A:
154 154  
155 155  [[image:image-20221021110615-5.png]]
156 156  
157 157  
158 158  
159 -== 2.2 ​ Configure CPN01 ==
187 +== 2.2 ​ Configure NDS03A ==
160 160  
161 -
162 162  === 2.2.1 Test Requirement ===
163 163  
164 164  
165 -To use CPN01 in your city, make sure to meet below requirements:
192 +To use NDS03A in your city, make sure to meet below requirements:
166 166  
167 167  * Your local operator has already distributed an NB-IoT Network.
168 -* The local NB-IoT network used the band that CPN01 supports.
195 +* The local NB-IoT network used the band that NDS03A supports.
169 169  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
170 170  
171 -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.
198 +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.
172 172  
173 -[[image:image-20221023000439-3.png]]
200 +[[image:image-20221117142300-1.png]]
174 174  
175 175   ​
176 176  
... ... @@ -186,10 +186,10 @@
186 186  
187 187  
188 188  
189 -=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
216 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
190 190  
191 191  
192 -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.
219 +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.
193 193  
194 194  (% style="color:blue" %)**Connection:**
195 195  
... ... @@ -212,11 +212,11 @@
212 212  
213 213  * Flow Control: (% style="color:red" %)**None**
214 214  
215 -Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
242 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
216 216  
217 217  ​[[image:image-20221021110817-7.png]]
218 218  
219 -CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
246 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
220 220  
221 221  
222 222  (% 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]]
... ... @@ -229,7 +229,7 @@
229 229  (% 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/]]
230 230  
231 231  
232 -(% style="color:blue" %)**Use below commands in CPN01:**
259 +(% style="color:blue" %)**Use below commands in NDS03A:**
233 233  
234 234  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
235 235  
... ... @@ -242,7 +242,7 @@
242 242  [[image:image-20221021110948-8.png]]
243 243  
244 244  
245 -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.
272 +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.
246 246  
247 247  [[image:image-20221021110956-9.png]] ​
248 248  
... ... @@ -318,11 +318,11 @@
318 318  
319 319  User can use below command to change the (% style="color:blue" %)**uplink interval**.
320 320  
321 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
348 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
322 322  
323 323  (% style="color:red" %)**NOTE:**
324 324  
325 -1.  By default, the device will send an uplink message every 1 hour.
352 +1.  By default, the device will send an uplink message every 4 hour.
326 326  
327 327  
328 328  
... ... @@ -329,57 +329,69 @@
329 329  == 2.3  Uplink Payload ==
330 330  
331 331  
332 -The uplink payload includes 123 bytes in total by default.
359 +The uplink payload includes 26 bytes in total by default.
333 333  
334 -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.
361 +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.
335 335  
363 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
336 336  
337 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:510px" %)
338 -|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:40px" %)**2**|(% style="width:44px" %)**2**|(% style="width:121px" %)**1**|(% style="width:52px" %)**1**|(% style="width:84px" %)**1**|(% style="width:116px" %)**1**|(% style="width:57px" %)**1**|(% style="width:91px" %)**3**
339 -|=(% 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"]]
365 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
366 +|=(% 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**
367 +|=(% 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)
340 340  
341 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:510px" %)
342 -|(% style="width:176px" %)**3**|(% style="width:98px" %)**4**|(% style="width:115px" %)**1**|(% style="width:92px" %)**3**|(% style="width:110px" %)**1**|(% style="width:169px" %)**3**|(% style="width:97px" %)4|(% style="width:74px" %)**8 group**
343 -|(% 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:110px" %)Calculate Flag|(% style="width:169px" %)The last open duration|(% style="width:97px" %)Time stamp|(% style="width:74px" %)...
369 +(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
370 +|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)(((
371 +**1-32 group**
372 +)))
373 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% 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" %)...
344 344  
345 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
375 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
346 346  
347 -[[image:image-20221021111201-16.png||height="572" width="792"]]
348 348  
378 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
379 +|=(% 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**
380 +|=(% 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)
349 349  
350 -The payload is ASCII string, representative same HEX:
382 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
383 +|(% 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**
384 +|(% 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|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
351 351  
352 -**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" %)09(% style="color:#663300" %) 02 (% style="color:#d60093" %)6315537b (% style="color:#660066" %)__01 00000b 02 0000026 63510fed__ (%%)__0100000e0200000263510f39__ __010000000000000063510e85__ __010000000000000063510d2e__ __010000000000000063510c7a__ __010000000000000063510bc6__ __010000000000000063510954__ __010000000000000063510882 __**
386 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
387 +|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
388 +**1-32 group**
389 +)))
390 +|(% 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|(% style="width:87px" %)......
353 353  
354 -**where:**
392 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
355 355  
356 -* (% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
394 +[[image:image-20221117145932-2.png]]
357 357  
358 -* (% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
359 359  
360 -* (% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
397 +The payload is ASCII string, representative same HEX:
361 361  
362 -* (% style="color:#037691" %) **Singal: **(%%)0x17 = 23
399 +**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__(%%)**
363 363  
364 -* (% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
401 +**where:**
365 365  
366 -* (% style="color:#037691" %) **Calculate Flag:**(%%) 0x00=0
403 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
367 367  
368 -* (% style="color:#037691" %) **Contact Status:**(%%) 0x00=0
405 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
369 369  
370 -* (% style="color:#037691" %) **Alarm: **(%%)0x00 =0
407 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
371 371  
372 -* (% style="color:#037691" %) **Total pulse: **(%%)0x09 =0
409 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
373 373  
374 -* (% style="color:#037691" %) **The last open duration: **(%%)0x02 =2
411 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
375 375  
376 -* (% style="color:#037691" %)** Time stamp :**(%%) 0x6315537b =1662342011 (Unix Time)
413 +* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0
377 377  
378 -* (% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 01  00000b  02  000026  63510fed
415 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
379 379  
380 -* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
417 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
381 381  
419 +* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
382 382  
421 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
383 383  
384 384  == 2.4  Payload Explanation and Sensor Interface ==
385 385  
... ... @@ -398,20 +398,18 @@
398 398  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
399 399  
400 400  
401 -
402 402  === 2.4.2  Version Info ===
403 403  
404 404  
405 405  Specify the software version: 0x64=100, which means firmware version 1.00.
406 406  
407 -For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
445 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
408 408  
409 409  
410 -
411 411  === 2.4.3  Battery Info ===
412 412  
413 413  
414 -Check the battery voltage for CPN01.
451 +Check the battery voltage for NDS03A.
415 415  
416 416  Ex1: 0x0B45 = 2885mV
417 417  
... ... @@ -418,7 +418,6 @@
418 418  Ex2: 0x0B49 = 2889mV
419 419  
420 420  
421 -
422 422  === 2.4.4  Signal Strength ===
423 423  
424 424  
... ... @@ -437,70 +437,39 @@
437 437  **99**    Not known or not detectable
438 438  
439 439  
476 +=== 2.4.5  Disalarm: (default: 0) ===
440 440  
441 -=== 2.4.5  Calculate Flag ===
442 442  
479 +(% 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.
443 443  
444 -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.
481 +(% 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.
445 445  
446 -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.
483 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
447 447  
448 -Default value: 0. 
449 449  
450 -Range (6 bits): (b)000000 ~~ (b) 111111
486 +=== 2.4.6  Keep Status & Keep Time ===
451 451  
452 452  
489 +Shows the configure value of Alarm Base on Timeout Feature
453 453  
454 -=== 2.4.6  Alarm ===
455 455  
492 +=== 2.4.7  Timestamp ===
456 456  
457 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
458 458  
495 +Timestamp : 0x6315537b =1662342011
459 459  
460 460  
461 -=== 2.4.7  Contact Status ===
462 462  
499 +=== 2.4.8  Switch Dual Channel Mode ===
463 463  
464 -0: Open
465 465  
466 -1: Close
502 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
467 467  
468 468  
469 -
470 -=== 2.4.8  Total pulse ===
471 -
472 -
473 -Total pulse/counting based on dry [[contact trigger event>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.2SensorConfiguration2CFPORT3D4]]
474 -
475 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
476 -
477 -
478 -
479 -=== 2.4.9  The last open duration ===
480 -
481 -
482 -Dry Contact last open duration.
483 -
484 -Unit: min.
485 -
486 -[[image:image-20221021111346-17.png||height="146" width="770"]]
487 -
488 -
489 -
490 -=== 2.4.10  Timestamp ===
491 -
492 -
493 -Timestamp : 0x6315537b =1662342011
494 -
495 -Convert Unix timestamp to time 2022-9-5 9:40:11.
496 -
497 -**~ **
498 -
499 -
500 500  == 2.5  Downlink Payload ==
501 501  
502 502  
503 -By default, CPN01 prints the downlink payload to console port.
508 +By default, NDS03A prints the downlink payload to console port.
504 504  
505 505  [[image:image-20221021111414-18.png]] ​
506 506  
... ... @@ -517,7 +517,7 @@
517 517  
518 518  * (% style="color:#037691" %)**Reset**
519 519  
520 -If payload = 0x04FF, it will reset the NSE01
525 +If payload = 0x04FF, it will reset the NDS03A
521 521  
522 522  * (% style="color:#037691" %)**INTMOD**
523 523  
... ... @@ -528,16 +528,16 @@
528 528  == 2.6  ​LED Indicator ==
529 529  
530 530  
531 -The CPN01 has an internal LED which is to show the status of different states.
536 +The NDS03A has an internal LED which is to show the status of different states.
532 532  
533 533  * When the device starts normally, the LED will light up for 1 second.
534 -* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
539 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
535 535  * For each uplink probe, LED will be on for 500ms.
536 536  
537 537  == 2.7  Alarm Base on Timeout ==
538 538  
539 539  
540 -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:
545 +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:
541 541  
542 542  
543 543  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -553,17 +553,25 @@
553 553  
554 554  If keep time = 0, Disable Alarm Base on Timeout feature.
555 555  
556 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
561 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
557 557  
558 558  
559 559  (% style="color:blue" %)**AT Command to configure:**
560 560  
561 -(% 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.
566 +(% style="color:blue" %)**PB14 PIN:**
562 562  
568 +(% 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.
569 +
563 563  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
564 564  
565 565  
573 +(% style="color:blue" %)**PB15 PIN:**
566 566  
575 +(% style="color:#037691" %)**AT+TTRIG2=1,30**
576 +
577 +(% style="color:#037691" %)**AT+TTRIG2=0,0 **
578 +
579 +
567 567  == 2.8  Set debug mode ==
568 568  
569 569  
... ... @@ -586,79 +586,88 @@
586 586  
587 587  
588 588  
589 -== 2.10  Set trigger mode ==
602 +== 2.10  Count Mod ==
590 590  
591 591  
592 -(% style="color:blue" %)**AT Command: AT+TTRMOD**
605 +(% style="color:blue" %)**AT Command: AT+COUNTMOD**
593 593  
594 -Feature: Set the trigger interrupt mode.
607 +[[image:image-20221118092935-1.png]]
595 595  
596 -[[image:image-20221021111552-20.png]]
597 597  
598 598  
611 +== 2.11  Interrupt Pin Channel Mod ==
599 599  
600 -== 2.11  Set the calculate flag ==
601 601  
614 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
602 602  
603 -Feature: Set the calculate flag
616 +[[image:image-20221118093144-2.png]]
604 604  
605 -(% style="color:blue" %)**AT Command: AT+CALCFLAG**
606 606  
607 -[[image:image-20221021111711-22.png]]
608 608  
620 +== 2.12 TTRIG1/2 timeout status alarm ==
609 609  
610 610  
611 -== 2.12 Set count number ==
623 +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.
612 612  
625 +(% style="color:blue" %)**AT Command: AT+TTRALARM**
613 613  
614 -Feature: Manually set the count number
627 +[[image:image-20221118093512-3.png]]
615 615  
616 -(% style="color:blue" %)**AT Command: AT+SETCNT**
617 617  
618 -[[image:image-20221021111748-24.png]]
619 619  
631 +== 2.13  Select counting mode ==
620 620  
621 621  
622 -== 2.13  Set the number of data to be uploaded and the recording time ==
634 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
623 623  
636 +When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
624 624  
625 -(% style="color:blue" %)**AT Command:**
638 +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.
626 626  
627 -(% 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)
640 +[[image:image-20221118093658-4.png]]
628 628  
629 -(% 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.
630 630  
631 631  
632 632  
633 -== 2.14  Read or Clear cached data ==
645 +== 2.14  Set the number of data to be uploaded and the recording time ==
634 634  
635 635  
636 636  (% style="color:blue" %)**AT Command:**
637 637  
650 +(% 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)
651 +
652 +(% 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.
653 +
654 +
655 +== 2.15  Read or Clear cached data ==
656 +
657 +
658 +(% style="color:blue" %)**AT Command:**
659 +
638 638  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
639 639  
640 640  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
641 641  
642 -[[image:image-20221021111810-25.png||height="364" width="797"]]
664 +[[image:image-20221118094227-5.png]]
643 643  
644 644  
645 645  
646 -== 2.15  ​Firmware Change Log ==
668 +== 2.16  ​Firmware Change Log ==
647 647  
648 648  
649 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
671 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
650 650  
651 -Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
673 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
652 652  
653 653  
654 654  
655 -== 2.16  ​Battery Analysis ==
677 +== 2.17  ​Battery Analysis ==
656 656  
657 657  
658 -=== 2.16.1  ​Battery Type ===
680 +=== 2.17.1  ​Battery Type ===
659 659  
660 660  
661 -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.
683 +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.
662 662  
663 663  The battery is designed to last for several years depends on the actual use environment and update interval. 
664 664  
... ... @@ -674,7 +674,7 @@
674 674  
675 675  
676 676  
677 -=== 2.16.2  Power consumption Analyze ===
699 +=== 2.17.2  Power consumption Analyze ===
678 678  
679 679  
680 680  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.
... ... @@ -697,7 +697,7 @@
697 697  
698 698  
699 699  
700 -=== 2.16.3  ​Battery Note ===
722 +=== 2.17.3  ​Battery Note ===
701 701  
702 702  
703 703  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.
... ... @@ -704,10 +704,10 @@
704 704  
705 705  
706 706  
707 -=== 2.16.4  Replace the battery ===
729 +=== 2.17.4  Replace the battery ===
708 708  
709 709  
710 -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).
732 +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).
711 711  
712 712  
713 713  
... ... @@ -718,7 +718,7 @@
718 718  
719 719  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/]] 
720 720  
721 -[[image:image-20221021112006-28.png]] ​
743 +[[image:image-20221118094449-6.png]] ​
722 722  
723 723  
724 724  
... ... @@ -771,15 +771,21 @@
771 771  
772 772  AT+ DEBUG   : Enable or Disable debug mode
773 773  
774 -AT+ TTRIG   : Get or Set Alarm Base on Timeout
796 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
775 775  
776 -AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
798 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
777 777  
778 -AT+ CALCFLAG   : Get or Set the calculate flag
800 +AT+COUNTMOD  :  Get or Set the count mode
779 779  
780 -AT+ CLRC   : Clear current door open count
802 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
781 781  
804 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
782 782  
806 +AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
807 +
808 +AT+ CLRC   :  Clear current door open count
809 +
810 +
783 783  (% style="color:blue" %)**COAP Management**      
784 784  
785 785  AT+URI            : Resource parameters
... ... @@ -821,7 +821,7 @@
821 821  
822 822  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]]
823 823  
824 -(% 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.**
852 +(% 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.**
825 825  
826 826  
827 827  
... ... @@ -845,7 +845,7 @@
845 845  = 7. ​ Order Info =
846 846  
847 847  
848 -Part Number**:** CPN01
876 +Part Number**:** NDS03A
849 849  
850 850  
851 851  
... ... @@ -854,14 +854,8 @@
854 854  
855 855  (% style="color:blue" %)**Package Includes**:
856 856  
857 -* CPN01 Open/Close Sensor x 1
858 -* External antenna x 1
885 +* NDS03A Open/Close Door Sensor x 1
859 859  
860 -(% style="color:blue" %)**Dimension and weight**:
861 -
862 -* Size: 195 x 125 x 55 mm
863 -* Weight:   420g
864 -
865 865  = 9.  Support =
866 866  
867 867  
image-20221117105556-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +133.3 KB
Content
image-20221117114459-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +14.9 KB
Content
image-20221117114842-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +964.1 KB
Content
image-20221117114937-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +79.1 KB
Content
image-20221117114949-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +33.4 KB
Content
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

Applications

Navigation

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