Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 104.5
edited by Xiaoling
on 2022/09/09 12:00
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,24 +57,19 @@
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  
74 -
75 -
76 -
77 -
78 78  == 1.3  Specification ==
79 79  
80 80  
... ... @@ -92,98 +92,75 @@
92 92  * - B20 @H-FDD: 800MHz
93 93  * - B28 @H-FDD: 700MHz
94 94  
95 -(% style="color:#037691" %)**Battery:**
74 +Probe(% style="color:#037691" %)** Specification:**
96 96  
97 -* Li/SOCI2 un-chargeable battery
98 -* Capacity: 8500mAh
99 -* Self Discharge: <1% / Year @ 25°C
100 -* Max continuously current: 130mA
101 -* 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.
102 102  
103 -(% style="color:#037691" %)**Power Consumption**
78 +[[image:image-20220708101224-1.png]]
104 104  
105 -* STOP Mode: 10uA @ 3.3v
106 -* Max transmit power: 350mA@3.3v
107 107  
108 108  
109 -
110 -
111 -
112 112  == ​1.4  Applications ==
113 113  
114 -
115 -* Smart Buildings & Home Automation
116 -* Logistics and Supply Chain Management
117 -* Smart Metering
118 118  * Smart Agriculture
119 -* Smart Cities
120 -* Smart Factory
121 121  
122 122  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
123 123  ​
124 124  
125 -
126 -
127 -
128 128  == 1.5  Pin Definitions ==
129 129  
130 130  
131 -[[image:1657328609906-564.png]]
92 +[[image:1657246476176-652.png]]
132 132  
133 133  
134 134  
135 -= 2.  Use NDDS75 to communicate with IoT Server =
96 += 2.  Use NSE01 to communicate with IoT Server =
136 136  
137 -
138 138  == 2.1  How it works ==
139 139  
140 140  
141 141  (((
142 -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.
143 143  )))
144 144  
145 145  
146 146  (((
147 -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:
148 148  )))
149 149  
150 -(((
151 -
152 -)))
110 +[[image:image-20220708101605-2.png]]
153 153  
154 -[[image:1657328659945-416.png]]
155 -
156 156  (((
157 157  
158 158  )))
159 159  
160 160  
161 -== 2.2 ​ Configure the NDDS75 ==
162 162  
118 +== 2.2 ​ Configure the NSE01 ==
163 163  
120 +
164 164  === 2.2.1 Test Requirement ===
165 165  
166 166  
167 167  (((
168 -To use NDDS75 in your city, make sure meet below requirements:
125 +To use NSE01 in your city, make sure meet below requirements:
169 169  )))
170 170  
171 171  * Your local operator has already distributed a NB-IoT Network there.
172 -* The local NB-IoT network used the band that NDDS75 supports.
129 +* The local NB-IoT network used the band that NSE01 supports.
173 173  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
174 174  
175 175  (((
176 -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
177 177  )))
178 178  
179 179  
180 -[[image:1657328756309-230.png]]
137 +[[image:1657249419225-449.png]]
181 181  
182 182  
183 183  
184 184  === 2.2.2 Insert SIM card ===
185 185  
186 -
187 187  (((
188 188  Insert the NB-IoT Card get from your provider.
189 189  )))
... ... @@ -193,22 +193,19 @@
193 193  )))
194 194  
195 195  
196 -[[image:1657328884227-504.png]]
152 +[[image:1657249468462-536.png]]
197 197  
198 198  
199 199  
200 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
156 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
201 201  
202 -
203 203  (((
204 204  (((
205 -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.
206 206  )))
207 207  )))
208 208  
209 -[[image:image-20220709092052-2.png]]
210 210  
211 -
212 212  **Connection:**
213 213  
214 214   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -227,14 +227,13 @@
227 227  * Flow Control: (% style="color:green" %)**None**
228 228  
229 229  (((
230 -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.
231 231  )))
232 232  
233 -[[image:1657329814315-101.png]]
186 +[[image:image-20220708110657-3.png]]
234 234  
235 -
236 236  (((
237 -(% 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/]]
238 238  )))
239 239  
240 240  
... ... @@ -241,76 +241,59 @@
241 241  
242 242  === 2.2.4 Use CoAP protocol to uplink data ===
243 243  
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/]]
244 244  
245 -(% 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/]]**
246 246  
247 -
248 -(((
249 249  **Use below commands:**
250 -)))
251 251  
252 -* (((
253 -(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
254 -)))
255 -* (((
256 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
257 -)))
258 -* (((
259 -(% 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
260 260  
261 -
262 -
263 -)))
264 -
265 -(((
266 266  For parameter description, please refer to AT command set
267 267  
268 -
269 -)))
207 +[[image:1657249793983-486.png]]
270 270  
271 -[[image:1657330452568-615.png]]
272 272  
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.
273 273  
212 +[[image:1657249831934-534.png]]
274 274  
275 -(((
276 -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.
277 277  
278 -
279 -)))
280 280  
281 -[[image:1657330472797-498.png]]
282 -
283 -
284 -
285 285  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
286 286  
218 +This feature is supported since firmware version v1.0.1
287 287  
288 -* (% 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
289 289  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
290 -* (% 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
291 291  
292 -[[image:1657330501006-241.png]]
225 +[[image:1657249864775-321.png]]
293 293  
294 294  
295 -[[image:1657330533775-472.png]]
228 +[[image:1657249930215-289.png]]
296 296  
297 297  
298 298  
299 299  === 2.2.6 Use MQTT protocol to uplink data ===
300 300  
234 +This feature is supported since firmware version v110
301 301  
302 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
303 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
304 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
305 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
306 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
307 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
308 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
309 309  
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 +
310 310  [[image:1657249978444-674.png]]
311 311  
312 312  
313 -[[image:1657330723006-866.png]]
248 +[[image:1657249990869-686.png]]
314 314  
315 315  
316 316  (((
... ... @@ -321,135 +321,72 @@
321 321  
322 322  === 2.2.7 Use TCP protocol to uplink data ===
323 323  
259 +This feature is supported since firmware version v110
324 324  
261 +
325 325  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
326 326  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
327 327  
328 -[[image:image-20220709093918-1.png]]
265 +[[image:1657250217799-140.png]]
329 329  
330 330  
331 -[[image:image-20220709093918-2.png]]
268 +[[image:1657250255956-604.png]]
332 332  
333 333  
334 334  
335 335  === 2.2.8 Change Update Interval ===
336 336  
337 -
338 338  User can use below command to change the (% style="color:green" %)**uplink interval**.
339 339  
340 340  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
341 341  
342 342  (((
343 -
344 -
345 -
346 346  (% style="color:red" %)**NOTE:**
280 +)))
347 347  
348 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
349 -
350 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
282 +(((
283 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
351 351  )))
352 352  
353 -(% 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).**
354 354  
355 355  
356 -
357 357  == 2.3  Uplink Payload ==
358 358  
290 +In this mode, uplink payload includes in total 18 bytes
359 359  
360 -=== 2.3.1  Before Firmware 1.3.2 ===
361 -
362 -
363 -In this mode, uplink payload includes in total 14 bytes
364 -
365 -(% 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" %)
366 366  |=(% style="width: 60px;" %)(((
367 367  **Size(bytes)**
368 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
369 -|(% 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"]]
370 370  
371 371  (((
372 -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.
373 373  )))
374 374  
375 375  
376 -[[image:1657331036973-987.png]]
303 +[[image:image-20220708111918-4.png]]
377 377  
378 378  
379 -(((
380 -The payload is **ASCII** string, representative same HEX:
381 -)))
382 -
383 -(((
384 -0x72403155615900640c6c19029200 where:
385 -)))
386 -
387 -* (((
388 -Device ID: 0x724031556159 = 724031556159
389 -)))
390 -* (((
391 -Version:  0x0064=100=1.0.0
392 -)))
393 -
394 -* (((
395 -BAT:  0x0c6c = 3180 mV = 3.180V
396 -)))
397 -* (((
398 -Signal: 0x19 = 25
399 -)))
400 -* (((
401 -Distance: 0x0292= 658 mm
402 -)))
403 -* (((
404 -Interrupt: 0x00 = 0
405 -
406 -
407 -
408 -
409 -
410 -)))
411 -
412 -=== **2.3.2  Since firmware v1.3.2** ===
413 -
414 -
415 -In this mode, uplink payload includes 69 bytes in total by default.
416 -
417 -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.
418 -
419 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
420 -|(% 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
421 -|(% 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.......
422 -
423 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
424 -
425 -[[image:image-20220908175246-1.png]]
426 -
427 -
428 428  The payload is ASCII string, representative same HEX:
429 429  
430 -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:
431 431  
432 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
433 -* (% style="color:red" %)Version: 0x0084=132=1.3.2
434 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
435 -* (% style="color:blue" %)Singal: 0x1e = 30
436 -* (% style="color:red" %)Mod: 0x01 = 1
437 -* Interrupt: 0x00= 0
438 -* Distance: 0x0039= 57 = 57
439 -* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
440 -* Distance,Time stamp : 00396319baf0
441 -* (% 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
442 442  
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
443 443  
444 -
445 -
446 -
447 447  == 2.4  Payload Explanation and Sensor Interface ==
448 448  
449 449  
450 450  === 2.4.1  Device ID ===
451 451  
452 -
453 453  (((
454 454  By default, the Device ID equal to the last 6 bytes of IMEI.
455 455  )))
... ... @@ -456,12 +456,10 @@
456 456  
457 457  (((
458 458  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
459 -
460 -
461 461  )))
462 462  
463 463  (((
464 -(% style="color:blue" %)**Example :**
334 +**Example:**
465 465  )))
466 466  
467 467  (((
... ... @@ -469,32 +469,19 @@
469 469  )))
470 470  
471 471  (((
472 -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.
473 473  )))
474 474  
475 475  
476 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
477 477  
478 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
479 -
480 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
481 -
482 -
483 -(% style="color:blue" %)**Example :**
484 -
485 -AT+DEUI=868411056754138
486 -
487 -
488 -
489 489  === 2.4.2  Version Info ===
490 490  
491 -
492 492  (((
493 493  Specify the software version: 0x64=100, means firmware version 1.00.
494 494  )))
495 495  
496 496  (((
497 -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.
498 498  )))
499 499  
500 500  
... ... @@ -501,6 +501,9 @@
501 501  
502 502  === 2.4.3  Battery Info ===
503 503  
361 +(((
362 +Check the battery voltage for LSE01.
363 +)))
504 504  
505 505  (((
506 506  Ex1: 0x0B45 = 2885mV
... ... @@ -514,7 +514,6 @@
514 514  
515 515  === 2.4.4  Signal Strength ===
516 516  
517 -
518 518  (((
519 519  NB-IoT Network signal Strength.
520 520  )))
... ... @@ -545,22 +545,65 @@
545 545  
546 546  
547 547  
548 -=== 2.4.5  Distance ===
407 +=== 2.4.5  Soil Moisture ===
549 549  
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 +)))
550 550  
551 -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 +)))
552 552  
553 553  (((
554 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
422 +
555 555  )))
556 556  
557 557  (((
426 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
427 +)))
428 +
429 +
430 +
431 +=== 2.4.6  Soil Temperature ===
432 +
558 558  (((
559 -(% 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
560 560  )))
436 +
437 +(((
438 +**Example**:
561 561  )))
562 562  
563 563  (((
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 +(((
564 564  
565 565  )))
566 566  
... ... @@ -568,11 +568,10 @@
568 568  
569 569  )))
570 570  
571 -=== 2.4.6  Digital Interrupt ===
473 +=== 2.4.8  Digital Interrupt ===
572 572  
573 -
574 574  (((
575 -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.
576 576  )))
577 577  
578 578  (((
... ... @@ -603,24 +603,19 @@
603 603  
604 604  
605 605  
606 -=== 2.4.7  ​+5V Output ===
507 +=== 2.4.9  ​+5V Output ===
607 607  
608 -
609 609  (((
610 -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. 
611 611  )))
612 612  
613 613  
614 614  (((
615 615  The 5V output time can be controlled by AT Command.
616 -
617 -
618 618  )))
619 619  
620 620  (((
621 621  (% style="color:blue" %)**AT+5VT=1000**
622 -
623 -
624 624  )))
625 625  
626 626  (((
... ... @@ -631,12 +631,11 @@
631 631  
632 632  == 2.5  Downlink Payload ==
633 633  
530 +By default, NSE01 prints the downlink payload to console port.
634 634  
635 -By default, NDDS75 prints the downlink payload to console port.
532 +[[image:image-20220708133731-5.png]]
636 636  
637 -[[image:image-20220709100028-1.png]]
638 638  
639 -
640 640  (((
641 641  (% style="color:blue" %)**Examples:**
642 642  )))
... ... @@ -670,7 +670,7 @@
670 670  )))
671 671  
672 672  (((
673 -If payload = 0x04FF, it will reset the NDDS75
568 +If payload = 0x04FF, it will reset the NSE01
674 674  )))
675 675  
676 676  
... ... @@ -682,99 +682,78 @@
682 682  
683 683  
684 684  
685 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
580 +== 2.6  ​LED Indicator ==
686 686  
582 +(((
583 +The NSE01 has an internal LED which is to show the status of different state.
687 687  
688 -(% style="color:blue" %)** ➢ AT Command:**
689 689  
690 -(% 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 +)))
691 691  
692 -² When min=0, and max≠0, Alarm higher than max
693 693  
694 -² When min≠0, and max=0, Alarm lower than min
695 695  
696 -² When min≠0 and max≠0, Alarm higher than max or lower than min
697 697  
595 +== 2.7  Installation in Soil ==
698 698  
699 -(% style="color:blue" %)** Example:**
597 +__**Measurement the soil surface**__
700 700  
701 -**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 +)))
702 702  
603 +[[image:1657259653666-883.png]] ​
703 703  
704 704  
705 -== 2.7  Set the number of data to be uploaded and the recording time ==
606 +(((
607 +
706 706  
609 +(((
610 +Dig a hole with diameter > 20CM.
611 +)))
707 707  
708 -(% style="color:blue" %)** ➢ AT Command:**
613 +(((
614 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
615 +)))
616 +)))
709 709  
710 -* (% 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)
711 -* (% 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.
618 +[[image:1654506665940-119.png]]
712 712  
713 -
714 -
715 -
716 -== 2.8  Read or Clear cached data ==
717 -
718 -
719 -(% style="color:blue" %)** ➢ AT Command:**
720 -
721 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data
722 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
723 -
724 -
725 -
726 -[[image:image-20220908175333-2.png]]
727 -
728 -
729 -
730 -== 2.9  ​LED Indicator ==
731 -
732 -
733 -The NDDS75 has an internal LED which is to show the status of different state.
734 -
735 -
736 -* 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)
737 -* Then the LED will be on for 1 second means device is boot normally.
738 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
739 -* For each uplink probe, LED will be on for 500ms.
740 -
741 741  (((
742 742  
743 743  )))
744 744  
745 745  
625 +== 2.8  ​Firmware Change Log ==
746 746  
747 -== 2.10  ​Firmware Change Log ==
748 748  
628 +Download URL & Firmware Change log
749 749  
750 -(((
751 -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]]
752 -)))
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/]]
753 753  
754 -(((
755 -
756 -)))
757 757  
758 -(((
759 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
760 -)))
633 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
761 761  
762 762  
763 763  
764 -== 2.11  ​Battery Analysis ==
637 +== 2.9  ​Battery Analysis ==
765 765  
639 +=== 2.9.1  ​Battery Type ===
766 766  
767 -=== 2.11.1  ​Battery Type ===
768 768  
769 -
770 770  (((
771 -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.
772 772  )))
773 773  
646 +
774 774  (((
775 775  The battery is designed to last for several years depends on the actually use environment and update interval. 
776 776  )))
777 777  
651 +
778 778  (((
779 779  The battery related documents as below:
780 780  )))
... ... @@ -784,14 +784,13 @@
784 784  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
785 785  
786 786  (((
787 -[[image:image-20220709101450-2.png]]
661 +[[image:image-20220708140453-6.png]]
788 788  )))
789 789  
790 790  
791 791  
792 -=== 2.11.2  Power consumption Analyze ===
666 +=== 2.9.2  Power consumption Analyze ===
793 793  
794 -
795 795  (((
796 796  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.
797 797  )))
... ... @@ -824,13 +824,12 @@
824 824  And the Life expectation in difference case will be shown on the right.
825 825  )))
826 826  
827 -[[image:image-20220709110451-3.png]]
700 +[[image:image-20220708141352-7.jpeg]]
828 828  
829 829  
830 830  
831 -=== 2.11.3  ​Battery Note ===
704 +=== 2.9.3  ​Battery Note ===
832 832  
833 -
834 834  (((
835 835  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.
836 836  )))
... ... @@ -837,11 +837,10 @@
837 837  
838 838  
839 839  
840 -=== 2.11.4  Replace the battery ===
712 +=== 2.9.4  Replace the battery ===
841 841  
842 -
843 843  (((
844 -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).
845 845  )))
846 846  
847 847  
... ... @@ -848,7 +848,6 @@
848 848  
849 849  = 3. ​ Access NB-IoT Module =
850 850  
851 -
852 852  (((
853 853  Users can directly access the AT command set of the NB-IoT module.
854 854  )))
... ... @@ -855,23 +855,19 @@
855 855  
856 856  (((
857 857  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/]] 
858 -
859 -
860 860  )))
861 861  
862 -[[image:1657333200519-600.png]]
730 +[[image:1657261278785-153.png]]
863 863  
864 864  
865 865  
866 866  = 4.  Using the AT Commands =
867 867  
868 -
869 869  == 4.1  Access AT Commands ==
870 870  
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/]]
871 871  
872 -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]]
873 873  
874 -
875 875  AT+<CMD>?  : Help on <CMD>
876 876  
877 877  AT+<CMD>         : Run <CMD>
... ... @@ -911,23 +911,7 @@
911 911  
912 912  AT+SERVADDR  : Server Address
913 913  
914 -AT+TR      : Get or Set record time"
915 915  
916 -AT+APN     : Get or set the APN
917 -
918 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
919 -
920 -AT+DNSCFG  : Get or Set DNS Server
921 -
922 -AT+GETSENSORVALUE   : Returns the current sensor measurement
923 -
924 -AT+NOUD      : Get or Set the number of data to be uploaded
925 -
926 -AT+CDP     : Read or Clear cached data
927 -
928 -AT+LDDSALARM : Get or Set alarm of distance
929 -
930 -
931 931  (% style="color:#037691" %)**COAP Management**      
932 932  
933 933  AT+URI            : Resource parameters
... ... @@ -961,7 +961,6 @@
961 961  
962 962  = ​5.  FAQ =
963 963  
964 -
965 965  == 5.1 ​ How to Upgrade Firmware ==
966 966  
967 967  
... ... @@ -974,14 +974,20 @@
974 974  )))
975 975  
976 976  (((
977 -(% 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.
978 978  )))
979 979  
980 980  
981 981  
982 -= 6.  Trouble Shooting =
831 +== 5.2  Can I calibrate NSE01 to different soil types? ==
983 983  
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 +)))
984 984  
837 +
838 += 6.  Trouble Shooting =
839 +
985 985  == 6.1  ​Connection problem when uploading firmware ==
986 986  
987 987  
... ... @@ -997,7 +997,6 @@
997 997  
998 998  == 6.2  AT Command input doesn't work ==
999 999  
1000 -
1001 1001  (((
1002 1002  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.
1003 1003  
... ... @@ -1008,7 +1008,7 @@
1008 1008  = 7. ​ Order Info =
1009 1009  
1010 1010  
1011 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
865 +Part Number**:** (% style="color:#4f81bd" %)**NSE01**
1012 1012  
1013 1013  
1014 1014  (% class="wikigeneratedid" %)
... ... @@ -1023,7 +1023,7 @@
1023 1023  
1024 1024  (% style="color:#037691" %)**Package Includes**:
1025 1025  
1026 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
880 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
1027 1027  * External antenna x 1
1028 1028  )))
1029 1029  
... ... @@ -1030,13 +1030,10 @@
1030 1030  (((
1031 1031  
1032 1032  
1033 -
1034 1034  (% style="color:#037691" %)**Dimension and weight**:
1035 1035  
1036 -* Device Size: 13.0 x 5 x 4.5 cm
1037 -* Device Weight: 150g
1038 -* Package Size / pcs : 15 x 12x 5.5 cm
1039 -* Weight / pcs : 220g
889 +* Size: 195 x 125 x 55 mm
890 +* Weight:   420g
1040 1040  )))
1041 1041  
1042 1042  (((
... ... @@ -1048,6 +1048,5 @@
1048 1048  
1049 1049  = 9.  Support =
1050 1050  
1051 -
1052 1052  * 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.
1053 1053  * 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