Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 83.7 >
edited by Xiaoling
on 2022/12/08 11:20
To version < 53.2 >
edited by Xiaoling
on 2022/11/17 11:08
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
1 +NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
Content
... ... @@ -1,10 +1,14 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg]]
2 +[[image:image-20221117105556-1.png]]
3 3  
4 4  
5 +
6 +
7 +
8 +
9 +
5 5  **Table of Contents：**
6 6  
7 -{{toc/}}
8 8  
9 9  
10 10  
... ... @@ -11,35 +11,40 @@
11 11  
12 12  = 1.  Introduction =
13 13  
14 -== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
15 15  
19 +== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
16 16  
21 +
17 17  (((
18 -The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor.
23 +The Dragino NDS03A is an Open/Close NB-IoT Door Sensor. It detects door open/close status and 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.
19 19  
20 -The NMDS200 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
25 +The NDS03A will send periodically data 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 21  
22 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
27 +NDS03A has a Datalog feature, it will record the open/close event and the user can retrieve the history from NB-IoT.
23 23  
24 -NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range.
29 +NDS03A has the 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.
25 25  
26 -NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technology**(%%) developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
31 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
32 +)))
27 27  
28 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
29 -
30 -NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
31 -
32 -To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection.
34 +(((
35 +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.
36 +\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
37 +\\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)
38 +\\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.
33 33  )))
34 34  
41 +​
35 35  
43 +
36 36  == ​1.2  Features ==
37 37  
38 38  
39 39  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
40 -* Short uplink interval for Distance Alarm
48 +* Open/Close detect
49 +* Open/Close statistics
41 41  * Monitor Battery Level
42 -* Microwave Radar for distance detection
51 +* Uplink on periodically and open/close event
43 43  * Datalog feature
44 44  * Uplink periodically
45 45  * Downlink to change configure
... ... @@ -50,99 +50,135 @@
50 50  * Micro SIM card slot for NB-IoT SIM
51 51  * 8500mAh Battery for long-term use
52 52  
53 -== 1.3 Radar probe specification ==
54 54  
63 +== 1.3  Specification ==
55 55  
56 -* Measuring Method: FMCW
57 -* Frequency: 24.000 24.500 GHz
58 -* Measurement output power: 6dBm
59 -* Measure range: 0.5 20m
60 -* Accuracy: ±0.1m
61 -* Resolution: 0.01m
62 -* Horizontal Angel: 78°
63 -* Vertical Angel: 23°
64 64  
65 -== 1.4  Storage Temperature ==
66 +(% style="color:blue" %)**Common DC Characteristics:**
66 66  
68 +* Supply Voltage: 2.1v ~~ 3.6v
69 +* Operating Temperature: -40 ~~ 85°C
67 67  
68 - -40°C to +85°C
71 +(% style="color:blue" %)**NB-IoT Spec:**
69 69  
73 +* - B1 @H-FDD: 2100MHz
74 +* - B3 @H-FDD: 1800MHz
75 +* - B8 @H-FDD: 900MHz
76 +* - B5 @H-FDD: 850MHz
77 +* - B20 @H-FDD: 800MHz
78 +* - B28 @H-FDD: 700MHz
70 70  
80 +
81 +== 1.4  Installation ==
82 +
83 +
84 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
85 +
86 +[[image:image-20221021110329-1.png]]
87 +
88 +
89 +[[image:image-20221022234602-2.png||height="288" width="922"]]
90 +
91 +
92 +
71 71  == 1.5 ​ Applications ==
72 72  
73 73  
74 -* Horizontal distance measurement
75 -* Liquid level measurement
76 -* Parking management system
77 -* Object proximity and presence detection
78 -* Intelligent trash can management system
79 -* Robot obstacle avoidance
80 -* Automatic control
81 -* Sewer
82 -* Bottom water level monitoring
96 +* Open/Close Detection
97 +* Pulse meter application
98 +* Dry Contact Detection
83 83  
84 -== 1.6  Specification ==
85 85  
101 +== 1.6  Mechanical ==
86 86  
87 -(% style="color:blue" %)**Common DC Characteristics:**
88 88  
89 -* Supply Voltage: 2.1v ~~ 3.6v
90 -* Operating Temperature: 0 ~~ 70°C
104 +​[[image:image-20221021110415-3.png]]
91 91  
92 -(% style="color:blue" %)**NB-IoT Spec:**
93 93  
94 -* B1 @H-FDD: 2100MHz
95 -* B3 @H-FDD: 1800MHz
96 -* B8 @H-FDD: 900MHz
97 -* B5 @H-FDD: 850MHz
98 -* B20 @H-FDD: 800MHz
99 -* B28 @H-FDD: 700MHz
100 100  
101 -== 1.7  Installation ==
108 +== 1.7  Pin Definitions and Switch ==
102 102  
103 103  
104 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
111 +[[image:image-20221021110429-4.png]]
105 105  
106 106  
107 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
114 +=== 1.7.1  Pin Definition ===
108 108  
109 109  
117 +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]]**.
110 110  
111 -== 1.8  Pin Definitions and Switch ==
112 112  
113 113  
114 -[[image:1670404362039-351.png]]
121 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
115 115  
116 116  
117 -= 2.  Use NMDS200 to communicate with IoT Server =
124 +Power on Device when putting this jumper.
118 118  
126 +
127 +
128 +=== 1.7.3  BOOT MODE / SW1 ===
129 +
130 +
131 +1)  ISP:  upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run.
132 +
133 +2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
134 +
135 +
136 +
137 +=== 1.7.4  Reset Button ===
138 +
139 +
140 +Press to reboot the device.
141 +
142 +
143 +
144 +=== 1.7.5  LED ===
145 +
146 +
147 +The LED will blink when :
148 +
149 +1.  Boot the device in flash mode
150 +
151 +2.  Send an uplink packet
152 +
153 +
154 +
155 += 2.  Use CPN01 to communicate with IoT Server =
156 +
157 +
119 119  == 2.1  How it works ==
120 120  
121 121  
122 -The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
161 +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.
123 123  
124 -The diagram below shows the working flow in the default firmware of NMDS200:
163 +The diagram below shows the working flow in the default firmware of CPN01:
125 125  
126 126  [[image:image-20221021110615-5.png]]
127 127  
128 128  
129 -== 2.2 ​ Configure NMDS200 ==
130 130  
169 +== 2.2 ​ Configure CPN01 ==
131 131  
132 -To use NMDS200 in your city, make sure to meet below requirements:
133 133  
172 +=== 2.2.1 Test Requirement ===
173 +
174 +
175 +To use CPN01 in your city, make sure to meet below requirements:
176 +
134 134  * Your local operator has already distributed an NB-IoT Network.
135 -* The local NB-IoT network used the band that NMDS200 supports.
178 +* The local NB-IoT network used the band that CPN01 supports.
136 136  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
137 137  
138 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NMDS200 will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
181 +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.
139 139  
140 -[[image:image-20221208090742-1.png]]
183 +[[image:image-20221023000439-3.png]]
141 141  
185 + ​
142 142  
143 -=== 2.2.1 Insert NB-IoT SIM card ===
144 144  
188 +=== 2.2.2 Insert NB-IoT SIM card ===
145 145  
190 +
146 146  Insert the NB-IoT Card get from your provider.
147 147  
148 148  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -150,11 +150,12 @@
150 150  [[image:image-20221021110745-6.png]] ​
151 151  
152 152  
153 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
154 154  
199 +=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
155 155  
156 -User need to configure NMDS200 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NMDS200 support AT Commands, user can use a USB to TTL adapter to connect to NMDS200 and use AT Commands to configure it, as below.
157 157  
202 +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.
203 +
158 158  (% style="color:blue" %)**Connection:**
159 159  
160 160  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -176,11 +176,11 @@
176 176  
177 177  * Flow Control: (% style="color:red" %)**None**
178 178  
179 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
225 +Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
180 180  
181 181  ​[[image:image-20221021110817-7.png]]
182 182  
183 -NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
229 +CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
184 184  
185 185  
186 186  (% 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]]
... ... @@ -187,13 +187,13 @@
187 187  
188 188  
189 189  
190 -=== 2.2.3 Use CoAP protocol to uplink data ===
236 +=== 2.2.4 Use CoAP protocol to uplink data ===
191 191  
192 192  
193 193  (% 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/]]
194 194  
195 195  
196 -(% style="color:blue" %)**Use below commands in NMDS200:**
242 +(% style="color:blue" %)**Use below commands in CPN01:**
197 197  
198 198  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
199 199  
... ... @@ -206,14 +206,15 @@
206 206  [[image:image-20221021110948-8.png]]
207 207  
208 208  
209 -After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server.
255 +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.
210 210  
211 -[[image:1670405841875-916.png]] ​
257 +[[image:image-20221021110956-9.png]] ​
212 212  
213 213  
214 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
215 215  
261 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
216 216  
263 +
217 217  (% style="color:blue" %)**AT Commands:**
218 218  
219 219  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -229,9 +229,10 @@
229 229  
230 230  ​
231 231  
232 -=== 2.2.5 Use MQTT protocol to uplink data ===
233 233  
280 +=== 2.2.6 Use MQTT protocol to uplink data ===
234 234  
282 +
235 235  (% style="color:blue" %)**AT Commands:**
236 236  
237 237  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -248,10 +248,10 @@
248 248  
249 249  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
250 250  
251 -​ [[image:image-20221118103445-7.png]]
299 +​ [[image:image-20221021111058-12.png]]
252 252  
253 253  
254 -[[image:1670405928926-116.png]]
302 +[[image:image-20221021111201-16.png||height="472" width="653"]]
255 255  
256 256  ​
257 257  
... ... @@ -258,9 +258,10 @@
258 258  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.
259 259  
260 260  
261 -=== 2.2.6 Use TCP protocol to uplink data ===
262 262  
310 +=== 2.2.7 Use TCP protocol to uplink data ===
263 263  
312 +
264 264  (% style="color:blue" %)**AT Commands:**
265 265  
266 266  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -267,74 +267,82 @@
267 267  
268 268  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
269 269  
270 -​ [[image:1670406036256-101.png||height="676" width="713"]]
319 +​ [[image:image-20221021111125-14.png]]
271 271  
272 -
273 273  [[image:image-20221021111131-15.png]]
274 274  
275 275  ​
276 276  
277 -=== 2.2.7 Change Update Interval ===
278 278  
326 +=== 2.2.8 Change Update Interval ===
279 279  
328 +
280 280  User can use below command to change the (% style="color:blue" %)**uplink interval**.
281 281  
282 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
331 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
283 283  
284 284  (% style="color:red" %)**NOTE:**
285 285  
286 -1.  By default, the device will send an uplink message every 4 hour.
335 +1.  By default, the device will send an uplink message every 1 hour.
287 287  
288 288  
338 +
289 289  == 2.3  Uplink Payload ==
290 290  
291 291  
292 -The uplink payload includes 23 bytes in total by default.
342 +The uplink payload includes 123 bytes in total by default.
293 293  
294 -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.
344 +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.
295 295  
296 296  
297 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
298 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:90px" %)**2**|(% style="width:100px" %)**2**
299 -|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) [[Distance 1>>||anchor="H2.4.5A0Distance"]] |(% style="width:93px" %) [[Distance 2>>||anchor="H2.4.5A0Distance"]]
347 +(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
348 +|=(% 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**
349 +|=(% 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"]]
300 300  
301 -(% border="1" style="background-color:#ffffcc; color:green; width:471px" %)
302 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:98px" %)(((
303 -**1-32 group**
304 -)))
305 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:98px" %)...
351 +(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
352 +|(% 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**
353 +|(% 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" %)...
306 306  
307 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
355 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
308 308  
309 -[[image:1670406261143-723.png]]
357 +[[image:image-20221021111201-16.png||height="572" width="792"]]
310 310  
311 311  
312 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
360 +The payload is ASCII string, representative same HEX:
313 313  
314 -**0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
362 +**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 __**
315 315  
316 316  **where:**
317 317  
318 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
366 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
319 319  
320 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
368 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
321 321  
322 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
370 +* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
323 323  
324 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
372 +* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
325 325  
326 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
374 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
327 327  
328 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
376 +* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
329 329  
330 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
378 +* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
331 331  
332 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
380 +* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
333 333  
334 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
382 +* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
335 335  
384 +* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
385 +
386 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
387 +
388 +* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
389 +
390 +* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
391 +
336 336  == 2.4  Payload Explanation and Sensor Interface ==
337 337  
394 +
338 338  === 2.4.1  Device ID ===
339 339  
340 340  
... ... @@ -349,18 +349,20 @@
349 349  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
350 350  
351 351  
409 +
352 352  === 2.4.2  Version Info ===
353 353  
354 354  
355 355  Specify the software version: 0x64=100, which means firmware version 1.00.
356 356  
357 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
415 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
358 358  
359 359  
418 +
360 360  === 2.4.3  Battery Info ===
361 361  
362 362  
363 -Check the battery voltage for NMDS200.
422 +Check the battery voltage for CPN01.
364 364  
365 365  Ex1: 0x0B45 = 2885mV
366 366  
... ... @@ -367,54 +367,89 @@
367 367  Ex2: 0x0B49 = 2889mV
368 368  
369 369  
429 +
370 370  === 2.4.4  Signal Strength ===
371 371  
372 372  
373 373  NB-IoT Network signal Strength.
374 374  
375 -(% style="color:blue" %)**Ex1: 0x1d = 29**
435 +**Ex1: 0x1d = 29**
376 376  
377 -(% style="color:#037691" %)**0** (%%) -113dBm or less
437 +**0**  -113dBm or less
378 378  
379 -(% style="color:#037691" %)**1**  (%%) -111dBm
439 +**1**  -111dBm
380 380  
381 -(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
441 +**2...30** -109dBm... -53dBm
382 382  
383 -(% style="color:#037691" %)**31** (%%) -51dBm or greater
443 +**31**   -51dBm or greater
384 384  
385 -(% style="color:#037691" %)**99** (%%) Not known or not detectable
445 +**99**    Not known or not detectable
386 386  
387 387  
388 -=== 2.4.5  Distance ===
389 389  
449 +=== 2.4.5  Calculate Flag ===
390 390  
391 -[[image:1670407401682-959.png]]
392 392  
452 +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.
393 393  
394 -(% style="color:blue" %)**Object1 Distance:**
454 +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.
395 395  
396 -Distance between sensor probe to the first object. (unit: cm)
456 +Default value: 0. 
397 397  
398 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
458 +Range (6 bits): (b)000000 ~~ (b) 111111
399 399  
400 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
401 401  
402 402  
403 -(% style="color:blue" %)**Object2 Distance:**
462 +=== 2.4.6  Alarm ===
404 404  
405 -Distance between sensor probe to the second object. (unit: cm)
406 406  
465 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
407 407  
408 -=== 2.4.6  Timestamp ===
409 409  
410 410  
469 +=== 2.4.7  Contact Status ===
470 +
471 +
472 +0: Open
473 +
474 +1: Close
475 +
476 +
477 +
478 +=== 2.4.8  Total pulse ===
479 +
480 +
481 +Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
482 +
483 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
484 +
485 +
486 +
487 +=== 2.4.9  The last open duration ===
488 +
489 +
490 +Dry Contact last open duration.
491 +
492 +Unit: min.
493 +
494 +[[image:image-20221021111346-17.png||height="146" width="770"]]
495 +
496 +
497 +
498 +=== 2.4.10  Timestamp ===
499 +
500 +
411 411  Timestamp : 0x6315537b =1662342011
412 412  
503 +Convert Unix timestamp to time 2022-9-5 9:40:11.
413 413  
505 +**~ **
506 +
507 +
414 414  == 2.5  Downlink Payload ==
415 415  
416 416  
417 -By default, NMDS200 prints the downlink payload to console port.
511 +By default, CPN01 prints the downlink payload to console port.
418 418  
419 419  [[image:image-20221021111414-18.png]] ​
420 420  
... ... @@ -431,7 +431,7 @@
431 431  
432 432  * (% style="color:#037691" %)**Reset**
433 433  
434 -If payload = 0x04FF, it will reset the NMDS200
528 +If payload = 0x04FF, it will reset the NSE01
435 435  
436 436  * (% style="color:#037691" %)**INTMOD**
437 437  
... ... @@ -438,46 +438,115 @@
438 438  Downlink Payload: 06000003, Set AT+INTMOD=3
439 439  
440 440  
535 +
441 441  == 2.6  ​LED Indicator ==
442 442  
443 443  
444 -The NMDS200 has an internal LED which is to show the status of different states.
539 +The CPN01 has an internal LED which is to show the status of different states.
445 445  
446 446  * When the device starts normally, the LED will light up for 1 second.
447 -* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
542 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
448 448  * For each uplink probe, LED will be on for 500ms.
449 449  
545 +== 2.7  Alarm Base on Timeout ==
450 450  
451 -== 2.7  Distance alarm function ==
452 452  
548 +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:
453 453  
454 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
455 455  
456 -(% style="color:#037691" %)**Example 1:**
551 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
457 457  
458 -AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
553 +Keep Status = 1: Monitor Close to Open event
459 459  
460 -AT+ ALARM2 =min,max
555 +Keep Status = 0: Monitor Open to Close event
461 461  
462 462  
463 -(% style="color:#037691" %)**Example 2:**
558 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
464 464  
465 -AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
560 +Range 0 ~~ 65535(0xFFFF) seconds.
466 466  
562 +If keep time = 0, Disable Alarm Base on Timeout feature.
467 467  
468 -== 2.8  Set the number of data to be uploaded and the recording time ==
564 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
469 469  
470 470  
567 +(% style="color:blue" %)**AT Command to configure:**
568 +
569 +(% 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.
570 +
571 +(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
572 +
573 +
574 +
575 +== 2.8  Set debug mode ==
576 +
577 +
578 +Feature: Enable or Disable debug mode
579 +
580 +(% style="color:blue" %)**AT Command: AT+DEBUG**
581 +
582 +[[image:image-20221021111629-21.png]]
583 +
584 +
585 +
586 +== 2.9  Clear Flash Record ==
587 +
588 +
589 +Feature: Clear flash storage for data log feature.
590 +
591 +(% style="color:blue" %)**AT Command: AT+CLRDTA**
592 +
593 +[[image:image-20221021111527-19.png]]
594 +
595 +
596 +
597 +== 2.10  Set trigger mode ==
598 +
599 +
600 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
601 +
602 +Feature: Set the trigger interrupt mode.
603 +
604 +[[image:image-20221021111552-20.png]]
605 +
606 +
607 +
608 +== 2.11  Set the calculate flag ==
609 +
610 +
611 +Feature: Set the calculate flag
612 +
613 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
614 +
615 +[[image:image-20221021111711-22.png]]
616 +
617 +
618 +
619 +== 2.12 Set count number ==
620 +
621 +
622 +Feature: Manually set the count number
623 +
624 +(% style="color:blue" %)**AT Command: AT+SETCNT**
625 +
626 +[[image:image-20221021111748-24.png]]
627 +
628 +
629 +
630 +== 2.13  Set the number of data to be uploaded and the recording time ==
631 +
632 +
471 471  (% style="color:blue" %)**AT Command:**
472 472  
473 -(% 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)
635 +(% 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)
474 474  
475 -(% 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.
637 +(% 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.
476 476  
477 477  
478 -== 2.9  Read or Clear cached data ==
479 479  
641 +== 2.14  Read or Clear cached data ==
480 480  
643 +
481 481  (% style="color:blue" %)**AT Command:**
482 482  
483 483  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -484,24 +484,27 @@
484 484  
485 485  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
486 486  
487 -[[image:1670408172929-569.png]]
650 +[[image:image-20221021111810-25.png||height="364" width="797"]]
488 488  
489 489  
490 -== 2.10  ​Firmware Change Log ==
491 491  
654 +== 2.15  ​Firmware Change Log ==
492 492  
493 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
494 494  
657 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
658 +
495 495  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
496 496  
497 497  
498 -== 2.11  ​Battery Analysis ==
499 499  
500 -=== 2.11.1  ​Battery Type ===
663 +== 2.16  ​Battery Analysis ==
501 501  
502 502  
503 -The NMDS200 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
666 +=== 2.16.1  ​Battery Type ===
504 504  
668 +
669 +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.
670 +
505 505  The battery is designed to last for several years depends on the actual use environment and update interval. 
506 506  
507 507  The battery-related documents as below:
... ... @@ -515,9 +515,10 @@
515 515  [[image:image-20221021111911-26.png]] ​
516 516  
517 517  
518 -=== 2.11.2  Power consumption Analyze ===
519 519  
685 +=== 2.16.2  Power consumption Analyze ===
520 520  
687 +
521 521  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.
522 522  
523 523  Instruction to use as below:
... ... @@ -537,18 +537,21 @@
537 537  [[image:1666596205057-567.png]] ​
538 538  
539 539  
540 -=== 2.11.3  ​Battery Note ===
541 541  
708 +=== 2.16.3  ​Battery Note ===
542 542  
710 +
543 543  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.
544 544  
545 545  
546 -=== 2.11.4  Replace the battery ===
547 547  
715 +=== 2.16.4  Replace the battery ===
548 548  
549 -The default battery pack of NMDS200 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
550 550  
718 +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).
551 551  
720 +
721 +
552 552  = 3. ​ Access NB-IoT Module =
553 553  
554 554  
... ... @@ -556,12 +556,13 @@
556 556  
557 557  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/]] 
558 558  
729 +[[image:image-20221021112006-28.png]] ​
559 559  
560 -[[image:image-20221118094449-6.png]] ​
561 561  
562 562  
563 563  = 4.  Using the AT Commands =
564 564  
735 +
565 565  == 4.1  Access AT Commands ==
566 566  
567 567  
... ... @@ -600,55 +600,57 @@
600 600  
601 601  AT+SERVADDR  : Server Address
602 602  
603 -AT+TR      :  Get or Set record time
774 +AT+TR      :  Get or Set record time
604 604  
605 -AT+NOUD :  Get or Set the number of data to be uploaded
776 +AT+NOUD      : Get or Set the number of data to be uploaded
606 606  
607 607  AT+CDP     :  Read or Clear cached data
608 608  
609 -AT+DEBUG:  Enable or Disable debug mode
780 +AT+ DEBUG   : Enable or Disable debug mode
610 610  
611 -AT+ALARM1:  Get or Set alarm of distance1
782 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
612 612  
613 -AT+ALARM2:  Get or Set alarm of distance2
784 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
614 614  
615 -AT+GETSENSORVALUE :  Returns the current sensor measurement
786 +AT+ CALCFLAG   : Get or Set the calculate flag
616 616  
617 -AT+POWERIC :  Get or set the Power IC flag
788 +AT+ CLRC   : Clear current door open count
618 618  
619 619  
620 620  (% style="color:blue" %)**COAP Management**      
621 621  
622 -AT+URI :  Resource parameters
793 +AT+URI            : Resource parameters
623 623  
624 624  
625 625  (% style="color:blue" %)**UDP Management**
626 626  
627 -AT+CFM :  Upload confirmation mode (only valid for UDP)
798 +AT+CFM          : Upload confirmation mode (only valid for UDP)
628 628  
629 629  
630 630  (% style="color:blue" %)**MQTT Management**
631 631  
632 -AT+CLIENT  : Get or Set MQTT client
803 +AT+CLIENT               : Get or Set MQTT client
633 633  
634 -AT+UNAME : Get or Set MQTT Username
805 +AT+UNAME  : Get or Set MQTT Username
635 635  
636 -AT+PWD  :  Get or Set MQTT password
807 +AT+PWD                  : Get or Set MQTT password
637 637  
638 -AT+PUBTOPIC :  Get or Set MQTT publish topic
809 +AT+PUBTOPIC  : Get or Set MQTT publish topic
639 639  
640 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
811 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
641 641  
642 642  
643 643  (% style="color:blue" %)**Information**          
644 644  
645 -AT+FDR :  Factory Data Reset
816 +AT+FDR  : Factory Data Reset
646 646  
647 -AT+PWORD :  Serial Access Password
818 +AT+PWORD  : Serial Access Password
648 648  
649 649  
821 +
650 650  = ​5.  FAQ =
651 651  
824 +
652 652  == 5.1 ​ How to Upgrade Firmware ==
653 653  
654 654  
... ... @@ -656,11 +656,13 @@
656 656  
657 657  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]]
658 658  
659 -(% style="color:red" %)**Notice: **(% style="color:blue" %)**NMDS200** (%%)**and (% style="color:blue" %)LMDS200(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
832 +(% 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.**
660 660  
661 661  
835 +
662 662  = 6.  Trouble Shooting =
663 663  
838 +
664 664  == 6.1  ​Connection problem when uploading firmware ==
665 665  
666 666  
... ... @@ -667,6 +667,7 @@
667 667  (% 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]]
668 668  
669 669  
845 +
670 670  == 6.2  AT Command input doesn't work ==
671 671  
672 672  
... ... @@ -673,19 +673,28 @@
673 673  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.
674 674  
675 675  
852 +
676 676  = 7. ​ Order Info =
677 677  
678 678  
679 -Part Number:(% style="color:blue" %)** NMDS200**
856 +Part Number**:** CPN01
680 680  
681 681  
859 +
682 682  = 8.  Packing Info =
683 683  
684 684  
685 685  (% style="color:blue" %)**Package Includes**:
686 686  
687 -* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
865 +* CPN01 Open/Close Sensor x 1
866 +* External antenna x 1
688 688  
868 +(% style="color:blue" %)**Dimension and weight**:
869 +
870 +* Size: 195 x 125 x 55 mm
871 +* Weight:   420g
872 +
873 +
689 689  = 9.  Support =
690 690  
691 691  
1670404362039-351.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -492.6 KB
Content
1670405841875-916.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.0 KB
Content
1670406261143-723.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content
1670407401682-959.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -23.7 KB
Content
1670408172929-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -211.8 KB
Content
LMDS200_10.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 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
image-20221207170748-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.1 KB
Content
image-20221207170748-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.9 KB
Content
image-20221207173200-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
image-20221207173300-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.0 KB
Content
image-20221208090742-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.7 KB
Content

Applications

Navigation

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