Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 104.3
edited by Xiaoling
on 2022/09/09 11:50
Change comment: There is no comment for this version
To version 75.2
edited by Xiaoling
on 2022/07/09 08:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,7 +7,6 @@
7 7  
8 8  **Table of Contents:**
9 9  
10 -{{toc/}}
11 11  
12 12  
13 13  
... ... @@ -16,7 +16,6 @@
16 16  
17 17  = 1.  Introduction =
18 18  
19 -
20 20  == 1.1 ​ What is NDDS75 Distance Detection Sensor ==
21 21  
22 22  (((
... ... @@ -23,34 +23,20 @@
23 23  
24 24  
25 25  (((
26 -(((
27 27  The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
25 +\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
26 +\\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.
27 +\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
28 +\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
29 +\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
28 28  )))
29 29  
30 -(((
31 -The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
32 +
32 32  )))
33 33  
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 -)))
35 +[[image:1654503236291-817.png]]
37 37  
38 -(((
39 -NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
40 -)))
41 41  
42 -(((
43 -NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
44 -)))
45 -
46 -(((
47 -To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
48 -)))
49 -)))
50 -
51 -
52 -)))
53 -
54 54  [[image:1657327959271-447.png]]
55 55  
56 56  
... ... @@ -57,17 +57,16 @@
57 57  
58 58  == 1.2 ​ Features ==
59 59  
60 -
61 61  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
62 -* Ultra low power consumption
63 -* Distance Detection by Ultrasonic technology
64 -* Flat object range 280mm - 7500mm
65 -* Accuracy: ±(1cm+S*0.3%) (S: Distance)
66 -* Cable Length: 25cm
45 +* Monitor Soil Moisture
46 +* Monitor Soil Temperature
47 +* Monitor Soil Conductivity
67 67  * AT Commands to change parameters
68 68  * Uplink on periodically
69 69  * Downlink to change configure
70 70  * IP66 Waterproof Enclosure
52 +* Ultra-Low Power consumption
53 +* AT Commands to change parameters
71 71  * Micro SIM card slot for NB-IoT SIM
72 72  * 8500mAh Battery for long term use
73 73  
... ... @@ -88,94 +88,75 @@
88 88  * - B20 @H-FDD: 800MHz
89 89  * - B28 @H-FDD: 700MHz
90 90  
91 -(% style="color:#037691" %)**Battery:**
74 +Probe(% style="color:#037691" %)** Specification:**
92 92  
93 -* Li/SOCI2 un-chargeable battery
94 -* Capacity: 8500mAh
95 -* Self Discharge: <1% / Year @ 25°C
96 -* Max continuously current: 130mA
97 -* Max boost current: 2A, 1 second
76 +Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
98 98  
99 -(% style="color:#037691" %)**Power Consumption**
78 +[[image:image-20220708101224-1.png]]
100 100  
101 -* STOP Mode: 10uA @ 3.3v
102 -* Max transmit power: 350mA@3.3v
103 103  
81 +
104 104  == ​1.4  Applications ==
105 105  
106 -
107 -* Smart Buildings & Home Automation
108 -* Logistics and Supply Chain Management
109 -* Smart Metering
110 110  * Smart Agriculture
111 -* Smart Cities
112 -* Smart Factory
113 113  
114 114  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
115 115  ​
116 116  
117 -
118 -
119 -
120 120  == 1.5  Pin Definitions ==
121 121  
122 122  
123 -[[image:1657328609906-564.png]]
92 +[[image:1657246476176-652.png]]
124 124  
125 125  
126 126  
127 -= 2.  Use NDDS75 to communicate with IoT Server =
96 += 2.  Use NSE01 to communicate with IoT Server =
128 128  
129 -
130 130  == 2.1  How it works ==
131 131  
132 132  
133 133  (((
134 -The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
102 +The NSE01 is equipped with a NB-IoT module, the pre-loaded firmware in NSE01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NSE01.
135 135  )))
136 136  
137 137  
138 138  (((
139 -The diagram below shows the working flow in default firmware of NDDS75:
107 +The diagram below shows the working flow in default firmware of NSE01:
140 140  )))
141 141  
142 -(((
143 -
144 -)))
110 +[[image:image-20220708101605-2.png]]
145 145  
146 -[[image:1657328659945-416.png]]
147 -
148 148  (((
149 149  
150 150  )))
151 151  
152 152  
153 -== 2.2 ​ Configure the NDDS75 ==
154 154  
118 +== 2.2 ​ Configure the NSE01 ==
155 155  
120 +
156 156  === 2.2.1 Test Requirement ===
157 157  
158 158  
159 159  (((
160 -To use NDDS75 in your city, make sure meet below requirements:
125 +To use NSE01 in your city, make sure meet below requirements:
161 161  )))
162 162  
163 163  * Your local operator has already distributed a NB-IoT Network there.
164 -* The local NB-IoT network used the band that NDDS75 supports.
129 +* The local NB-IoT network used the band that NSE01 supports.
165 165  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
166 166  
167 167  (((
168 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server.
133 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NSE01 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
169 169  )))
170 170  
171 171  
172 -[[image:1657328756309-230.png]]
137 +[[image:1657249419225-449.png]]
173 173  
174 174  
175 175  
176 176  === 2.2.2 Insert SIM card ===
177 177  
178 -
179 179  (((
180 180  Insert the NB-IoT Card get from your provider.
181 181  )))
... ... @@ -185,22 +185,19 @@
185 185  )))
186 186  
187 187  
188 -[[image:1657328884227-504.png]]
152 +[[image:1657249468462-536.png]]
189 189  
190 190  
191 191  
192 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
156 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
193 193  
194 -
195 195  (((
196 196  (((
197 -User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
160 +User need to configure NSE01 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01 support AT Commands, user can use a USB to TTL adapter to connect to NSE01 and use AT Commands to configure it, as below.
198 198  )))
199 199  )))
200 200  
201 -[[image:image-20220709092052-2.png]]
202 202  
203 -
204 204  **Connection:**
205 205  
206 206   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -219,14 +219,13 @@
219 219  * Flow Control: (% style="color:green" %)**None**
220 220  
221 221  (((
222 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
183 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSE01. NSE01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
223 223  )))
224 224  
225 -[[image:1657329814315-101.png]]
186 +[[image:image-20220708110657-3.png]]
226 226  
227 -
228 228  (((
229 -(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]**
189 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
230 230  )))
231 231  
232 232  
... ... @@ -233,76 +233,59 @@
233 233  
234 234  === 2.2.4 Use CoAP protocol to uplink data ===
235 235  
196 +(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
236 236  
237 -(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**
238 238  
239 -
240 -(((
241 241  **Use below commands:**
242 -)))
243 243  
244 -* (((
245 -(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
246 -)))
247 -* (((
248 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
249 -)))
250 -* (((
251 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
201 +* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
202 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
203 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
252 252  
253 -
254 -
255 -)))
256 -
257 -(((
258 258  For parameter description, please refer to AT command set
259 259  
260 -
261 -)))
207 +[[image:1657249793983-486.png]]
262 262  
263 -[[image:1657330452568-615.png]]
264 264  
210 +After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server.
265 265  
212 +[[image:1657249831934-534.png]]
266 266  
267 -(((
268 -After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
269 269  
270 -
271 -)))
272 272  
273 -[[image:1657330472797-498.png]]
274 -
275 -
276 -
277 277  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
278 278  
218 +This feature is supported since firmware version v1.0.1
279 279  
280 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
220 +
221 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
281 281  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
282 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
223 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
283 283  
284 -[[image:1657330501006-241.png]]
225 +[[image:1657249864775-321.png]]
285 285  
286 286  
287 -[[image:1657330533775-472.png]]
228 +[[image:1657249930215-289.png]]
288 288  
289 289  
290 290  
291 291  === 2.2.6 Use MQTT protocol to uplink data ===
292 292  
234 +This feature is supported since firmware version v110
293 293  
294 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
295 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
296 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
297 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
298 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
299 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
300 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
301 301  
237 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
238 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
239 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
240 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
241 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
242 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
243 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
244 +
302 302  [[image:1657249978444-674.png]]
303 303  
304 304  
305 -[[image:1657330723006-866.png]]
248 +[[image:1657249990869-686.png]]
306 306  
307 307  
308 308  (((
... ... @@ -313,132 +313,72 @@
313 313  
314 314  === 2.2.7 Use TCP protocol to uplink data ===
315 315  
259 +This feature is supported since firmware version v110
316 316  
261 +
317 317  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
318 318  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
319 319  
320 -[[image:image-20220709093918-1.png]]
265 +[[image:1657250217799-140.png]]
321 321  
322 322  
323 -[[image:image-20220709093918-2.png]]
268 +[[image:1657250255956-604.png]]
324 324  
325 325  
326 326  
327 327  === 2.2.8 Change Update Interval ===
328 328  
329 -
330 330  User can use below command to change the (% style="color:green" %)**uplink interval**.
331 331  
332 332  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
333 333  
334 334  (((
335 -(% style="color:red" %)**NOTE 1: By default, the device will send an uplink message every 1 hour.**
279 +(% style="color:red" %)**NOTE:**
280 +)))
336 336  
337 -
282 +(((
283 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
338 338  )))
339 339  
340 -(% style="color:red" %)**NOTE 2: When the firmware version is v1.3.2 and later firmware:**
341 341  
342 -(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
343 343  
344 -
345 -
346 346  == 2.3  Uplink Payload ==
347 347  
290 +In this mode, uplink payload includes in total 18 bytes
348 348  
349 -=== 2.3.1  Before Firmware 1.3.2 ===
350 -
351 -
352 -In this mode, uplink payload includes in total 14 bytes
353 -
354 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
292 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
355 355  |=(% style="width: 60px;" %)(((
356 356  **Size(bytes)**
357 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
358 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
295 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 50px;" %)**1**
296 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:108px" %)[[Soil Moisture>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H2.4.6A0SoilTemperature"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H2.4.7A0SoilConductivity28EC29"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]
359 359  
360 360  (((
361 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
299 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
362 362  )))
363 363  
364 364  
365 -[[image:1657331036973-987.png]]
303 +[[image:image-20220708111918-4.png]]
366 366  
367 367  
368 -(((
369 -The payload is **ASCII** string, representative same HEX:
370 -)))
371 -
372 -(((
373 -0x72403155615900640c6c19029200 where:
374 -)))
375 -
376 -* (((
377 -Device ID: 0x724031556159 = 724031556159
378 -)))
379 -* (((
380 -Version:  0x0064=100=1.0.0
381 -)))
382 -
383 -* (((
384 -BAT:  0x0c6c = 3180 mV = 3.180V
385 -)))
386 -* (((
387 -Signal: 0x19 = 25
388 -)))
389 -* (((
390 -Distance: 0x0292= 658 mm
391 -)))
392 -* (((
393 -Interrupt: 0x00 = 0
394 -
395 -
396 -
397 -
398 -
399 -)))
400 -
401 -=== **2.3.2  Since firmware v1.3.2** ===
402 -
403 -
404 -In this mode, uplink payload includes 69 bytes in total by default.
405 -
406 -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.
407 -
408 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
409 -|(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4
410 -|(% style="width:95px" %)**Value**|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp.......
411 -
412 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
413 -
414 -[[image:image-20220908175246-1.png]]
415 -
416 -
417 417  The payload is ASCII string, representative same HEX:
418 418  
419 -0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where:
308 +0x72403155615900640c7817075e0a8c02f900 where:
420 420  
421 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
422 -* (% style="color:red" %)Version: 0x0084=132=1.3.2
423 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
424 -* (% style="color:blue" %)Singal: 0x1e = 30
425 -* (% style="color:red" %)Mod: 0x01 = 1
426 -* Interrupt: 0x00= 0
427 -* Distance: 0x0039= 57 = 57
428 -* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
429 -* Distance,Time stamp : 00396319baf0
430 -* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
310 +* Device ID: 0x 724031556159 = 724031556159
311 +* Version: 0x0064=100=1.0.0
431 431  
313 +* BAT: 0x0c78 = 3192 mV = 3.192V
314 +* Singal: 0x17 = 23
315 +* Soil Moisture: 0x075e= 1886 = 18.86  %
316 +* Soil Temperature:0x0a8c =2700=27 °C
317 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
318 +* Interrupt: 0x00 = 0
432 432  
433 -
434 -
435 -
436 436  == 2.4  Payload Explanation and Sensor Interface ==
437 437  
438 438  
439 439  === 2.4.1  Device ID ===
440 440  
441 -
442 442  (((
443 443  By default, the Device ID equal to the last 6 bytes of IMEI.
444 444  )))
... ... @@ -445,12 +445,10 @@
445 445  
446 446  (((
447 447  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
448 -
449 -
450 450  )))
451 451  
452 452  (((
453 -(% style="color:blue" %)**Example :**
334 +**Example:**
454 454  )))
455 455  
456 456  (((
... ... @@ -458,32 +458,19 @@
458 458  )))
459 459  
460 460  (((
461 -The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
342 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
462 462  )))
463 463  
464 464  
465 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
466 466  
467 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
468 -
469 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
470 -
471 -
472 -(% style="color:blue" %)**Example :**
473 -
474 -AT+DEUI=868411056754138
475 -
476 -
477 -
478 478  === 2.4.2  Version Info ===
479 479  
480 -
481 481  (((
482 482  Specify the software version: 0x64=100, means firmware version 1.00.
483 483  )))
484 484  
485 485  (((
486 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
354 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
487 487  )))
488 488  
489 489  
... ... @@ -490,6 +490,9 @@
490 490  
491 491  === 2.4.3  Battery Info ===
492 492  
361 +(((
362 +Check the battery voltage for LSE01.
363 +)))
493 493  
494 494  (((
495 495  Ex1: 0x0B45 = 2885mV
... ... @@ -503,7 +503,6 @@
503 503  
504 504  === 2.4.4  Signal Strength ===
505 505  
506 -
507 507  (((
508 508  NB-IoT Network signal Strength.
509 509  )))
... ... @@ -534,22 +534,65 @@
534 534  
535 535  
536 536  
537 -=== 2.4.5  Distance ===
407 +=== 2.4.5  Soil Moisture ===
538 538  
409 +(((
410 +(((
411 +Get the moisture content of the soil. The value range of the register is 0-10000(Decimal), divide this value by 100 to get the percentage of moisture in the soil.
412 +)))
413 +)))
539 539  
540 -Get the distance. Flat object range 280mm - 7500mm.
415 +(((
416 +(((
417 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
418 +)))
419 +)))
541 541  
542 542  (((
543 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
422 +
544 544  )))
545 545  
546 546  (((
426 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
427 +)))
428 +
429 +
430 +
431 +=== 2.4.6  Soil Temperature ===
432 +
547 547  (((
548 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
434 +Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is __**0x09 0xEC**__, the temperature content in the soil is
549 549  )))
436 +
437 +(((
438 +**Example**:
550 550  )))
551 551  
552 552  (((
442 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
443 +)))
444 +
445 +(((
446 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
447 +)))
448 +
449 +
450 +
451 +=== 2.4.7  Soil Conductivity (EC) ===
452 +
453 +(((
454 +Obtain (% style="color:#4f81bd" %)**__soluble salt concentration__**(%%) in soil or (% style="color:#4f81bd" %)**__soluble ion concentration in liquid fertilizer__**(%%) or (% style="color:#4f81bd" %)**__planting medium__**(%%). The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000).
455 +)))
456 +
457 +(((
458 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
459 +)))
460 +
461 +(((
462 +Generally, the EC value of irrigation water is less than 800uS / cm.
463 +)))
464 +
465 +(((
553 553  
554 554  )))
555 555  
... ... @@ -557,11 +557,10 @@
557 557  
558 558  )))
559 559  
560 -=== 2.4.6  Digital Interrupt ===
473 +=== 2.4.8  Digital Interrupt ===
561 561  
562 -
563 563  (((
564 -Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
476 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server.
565 565  )))
566 566  
567 567  (((
... ... @@ -592,24 +592,19 @@
592 592  
593 593  
594 594  
595 -=== 2.4.7  ​+5V Output ===
507 +=== 2.4.9  ​+5V Output ===
596 596  
597 -
598 598  (((
599 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
510 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
600 600  )))
601 601  
602 602  
603 603  (((
604 604  The 5V output time can be controlled by AT Command.
605 -
606 -
607 607  )))
608 608  
609 609  (((
610 610  (% style="color:blue" %)**AT+5VT=1000**
611 -
612 -
613 613  )))
614 614  
615 615  (((
... ... @@ -620,12 +620,11 @@
620 620  
621 621  == 2.5  Downlink Payload ==
622 622  
530 +By default, NSE01 prints the downlink payload to console port.
623 623  
624 -By default, NDDS75 prints the downlink payload to console port.
532 +[[image:image-20220708133731-5.png]]
625 625  
626 -[[image:image-20220709100028-1.png]]
627 627  
628 -
629 629  (((
630 630  (% style="color:blue" %)**Examples:**
631 631  )))
... ... @@ -659,7 +659,7 @@
659 659  )))
660 660  
661 661  (((
662 -If payload = 0x04FF, it will reset the NDDS75
568 +If payload = 0x04FF, it will reset the NSE01
663 663  )))
664 664  
665 665  
... ... @@ -671,100 +671,78 @@
671 671  
672 672  
673 673  
674 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
580 +== 2.6  ​LED Indicator ==
675 675  
582 +(((
583 +The NSE01 has an internal LED which is to show the status of different state.
676 676  
677 -(% style="color:blue" %)** ➢ AT Command:**
678 678  
679 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
586 +* When power on, NSE01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
587 +* Then the LED will be on for 1 second means device is boot normally.
588 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
589 +* For each uplink probe, LED will be on for 500ms.
590 +)))
680 680  
681 -² When min=0, and max≠0, Alarm higher than max
682 682  
683 -² When min≠0, and max=0, Alarm lower than min
684 684  
685 -² When min≠0 and max≠0, Alarm higher than max or lower than min
686 686  
595 +== 2.7  Installation in Soil ==
687 687  
688 -(% style="color:blue" %)** Example:**
597 +__**Measurement the soil surface**__
689 689  
690 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
599 +(((
600 +Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]]
601 +)))
691 691  
603 +[[image:1657259653666-883.png]] ​
692 692  
693 693  
694 -== 2.7  Set the number of data to be uploaded and the recording time ==
606 +(((
607 +
695 695  
609 +(((
610 +Dig a hole with diameter > 20CM.
611 +)))
696 696  
697 -(% style="color:blue" %)** ➢ AT Command:**
613 +(((
614 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
615 +)))
616 +)))
698 698  
699 -(% 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)
618 +[[image:1654506665940-119.png]]
700 700  
701 -(% 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.
702 -
703 -
704 -
705 -== 2.8  Read or Clear cached data ==
706 -
707 -
708 -(% style="color:blue" %)** ➢ AT Command:**
709 -
710 -(% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data
711 -
712 -
713 -[[image:image-20220908175333-2.png]]
714 -
715 -
716 -(% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/ Clear cached data
717 -
718 -
719 -
720 -== 2.9  ​LED Indicator ==
721 -
722 -
723 -The NDDS75 has an internal LED which is to show the status of different state.
724 -
725 -
726 -* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
727 -* Then the LED will be on for 1 second means device is boot normally.
728 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
729 -* For each uplink probe, LED will be on for 500ms.
730 -
731 731  (((
732 732  
733 733  )))
734 734  
735 735  
625 +== 2.8  ​Firmware Change Log ==
736 736  
737 -== 2.10  ​Firmware Change Log ==
738 738  
628 +Download URL & Firmware Change log
739 739  
740 -(((
741 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]]
742 -)))
630 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
743 743  
744 -(((
745 -
746 -)))
747 747  
748 -(((
749 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
750 -)))
633 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
751 751  
752 752  
753 753  
754 -== 2.11  ​Battery Analysis ==
637 +== 2.9  ​Battery Analysis ==
755 755  
639 +=== 2.9.1  ​Battery Type ===
756 756  
757 -=== 2.11.1  ​Battery Type ===
758 758  
759 -
760 760  (((
761 -The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-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.
643 +The NSE01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-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.
762 762  )))
763 763  
646 +
764 764  (((
765 765  The battery is designed to last for several years depends on the actually use environment and update interval. 
766 766  )))
767 767  
651 +
768 768  (((
769 769  The battery related documents as below:
770 770  )))
... ... @@ -774,14 +774,13 @@
774 774  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
775 775  
776 776  (((
777 -[[image:image-20220709101450-2.png]]
661 +[[image:image-20220708140453-6.png]]
778 778  )))
779 779  
780 780  
781 781  
782 -=== 2.11.2  Power consumption Analyze ===
666 +=== 2.9.2  Power consumption Analyze ===
783 783  
784 -
785 785  (((
786 786  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.
787 787  )))
... ... @@ -814,13 +814,12 @@
814 814  And the Life expectation in difference case will be shown on the right.
815 815  )))
816 816  
817 -[[image:image-20220709110451-3.png]]
700 +[[image:image-20220708141352-7.jpeg]]
818 818  
819 819  
820 820  
821 -=== 2.11.3  ​Battery Note ===
704 +=== 2.9.3  ​Battery Note ===
822 822  
823 -
824 824  (((
825 825  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.
826 826  )))
... ... @@ -827,11 +827,10 @@
827 827  
828 828  
829 829  
830 -=== 2.11.4  Replace the battery ===
712 +=== 2.9.4  Replace the battery ===
831 831  
832 -
833 833  (((
834 -The default battery pack of NDDS75 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).
715 +The default battery pack of NSE01 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).
835 835  )))
836 836  
837 837  
... ... @@ -838,7 +838,6 @@
838 838  
839 839  = 3. ​ Access NB-IoT Module =
840 840  
841 -
842 842  (((
843 843  Users can directly access the AT command set of the NB-IoT module.
844 844  )))
... ... @@ -845,23 +845,19 @@
845 845  
846 846  (((
847 847  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/]] 
848 -
849 -
850 850  )))
851 851  
852 -[[image:1657333200519-600.png]]
730 +[[image:1657261278785-153.png]]
853 853  
854 854  
855 855  
856 856  = 4.  Using the AT Commands =
857 857  
858 -
859 859  == 4.1  Access AT Commands ==
860 860  
738 +See this link for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
861 861  
862 -See this link for detail:  [[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]
863 863  
864 -
865 865  AT+<CMD>?  : Help on <CMD>
866 866  
867 867  AT+<CMD>         : Run <CMD>
... ... @@ -901,23 +901,7 @@
901 901  
902 902  AT+SERVADDR  : Server Address
903 903  
904 -AT+TR      : Get or Set record time"
905 905  
906 -AT+APN     : Get or set the APN
907 -
908 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
909 -
910 -AT+DNSCFG  : Get or Set DNS Server
911 -
912 -AT+GETSENSORVALUE   : Returns the current sensor measurement
913 -
914 -AT+NOUD      : Get or Set the number of data to be uploaded
915 -
916 -AT+CDP     : Read or Clear cached data
917 -
918 -AT+LDDSALARM : Get or Set alarm of distance
919 -
920 -
921 921  (% style="color:#037691" %)**COAP Management**      
922 922  
923 923  AT+URI            : Resource parameters
... ... @@ -951,7 +951,6 @@
951 951  
952 952  = ​5.  FAQ =
953 953  
954 -
955 955  == 5.1 ​ How to Upgrade Firmware ==
956 956  
957 957  
... ... @@ -964,14 +964,20 @@
964 964  )))
965 965  
966 966  (((
967 -(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
826 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
968 968  )))
969 969  
970 970  
971 971  
972 -= 6.  Trouble Shooting =
831 +== 5.2  Can I calibrate NSE01 to different soil types? ==
973 973  
833 +(((
834 +NSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].
835 +)))
974 974  
837 +
838 += 6.  Trouble Shooting =
839 +
975 975  == 6.1  ​Connection problem when uploading firmware ==
976 976  
977 977  
... ... @@ -987,7 +987,6 @@
987 987  
988 988  == 6.2  AT Command input doesn't work ==
989 989  
990 -
991 991  (((
992 992  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.
993 993  
... ... @@ -998,7 +998,7 @@
998 998  = 7. ​ Order Info =
999 999  
1000 1000  
1001 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
865 +Part Number**:** (% style="color:#4f81bd" %)**NSE01**
1002 1002  
1003 1003  
1004 1004  (% class="wikigeneratedid" %)
... ... @@ -1013,7 +1013,7 @@
1013 1013  
1014 1014  (% style="color:#037691" %)**Package Includes**:
1015 1015  
1016 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
880 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
1017 1017  * External antenna x 1
1018 1018  )))
1019 1019  
... ... @@ -1020,13 +1020,10 @@
1020 1020  (((
1021 1021  
1022 1022  
1023 -
1024 1024  (% style="color:#037691" %)**Dimension and weight**:
1025 1025  
1026 -* Device Size: 13.0 x 5 x 4.5 cm
1027 -* Device Weight: 150g
1028 -* Package Size / pcs : 15 x 12x 5.5 cm
1029 -* Weight / pcs : 220g
889 +* Size: 195 x 125 x 55 mm
890 +* Weight:   420g
1030 1030  )))
1031 1031  
1032 1032  (((
... ... @@ -1038,6 +1038,5 @@
1038 1038  
1039 1039  = 9.  Support =
1040 1040  
1041 -
1042 1042  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1043 1043  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
1657328609906-564.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -492.6 KB
Content
1657328659945-416.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
1657328756309-230.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.5 KB
Content
1657328884227-504.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -483.6 KB
Content
1657329814315-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -85.3 KB
Content
1657330452568-615.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -71.3 KB
Content
1657330472797-498.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -68.9 KB
Content
1657330501006-241.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -119.2 KB
Content
1657330533775-472.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -74.9 KB
Content
1657330723006-866.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -74.1 KB
Content
1657331036973-987.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -83.8 KB
Content
1657332990863-496.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.2 KB
Content
1657333200519-600.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
image-20220709092052-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -247.3 KB
Content
image-20220709093918-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -42.2 KB
Content
image-20220709093918-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -61.9 KB
Content
image-20220709100028-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.8 KB
Content
image-20220709101450-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.5 KB
Content
image-20220709110451-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -611.5 KB
Content
image-20220908175246-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -31.1 KB
Content