Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 75.3
edited by Xiaoling
on 2022/07/09 08:58
Change comment: There is no comment for this version
To version 103.1
edited by David Huang
on 2022/09/08 18:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.David
Content
... ... @@ -7,6 +7,7 @@
7 7  
8 8  **Table of Contents:**
9 9  
10 +{{toc/}}
10 10  
11 11  
12 12  
... ... @@ -15,6 +15,7 @@
15 15  
16 16  = 1.  Introduction =
17 17  
19 +
18 18  == 1.1 ​ What is NDDS75 Distance Detection Sensor ==
19 19  
20 20  (((
... ... @@ -21,20 +21,34 @@
21 21  
22 22  
23 23  (((
26 +(((
24 24  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.
30 30  )))
31 31  
32 -
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.
33 33  )))
34 34  
35 -[[image:1654503236291-817.png]]
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 +)))
36 36  
38 +(((
39 +NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
40 +)))
37 37  
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 +
38 38  [[image:1657327959271-447.png]]
39 39  
40 40  
... ... @@ -56,7 +56,6 @@
56 56  * 8500mAh Battery for long term use
57 57  
58 58  
59 -
60 60  == 1.3  Specification ==
61 61  
62 62  
... ... @@ -74,7 +74,6 @@
74 74  * - B20 @H-FDD: 800MHz
75 75  * - B28 @H-FDD: 700MHz
76 76  
77 -
78 78  (% style="color:#037691" %)**Battery:**
79 79  
80 80  * Li/SOCI2 un-chargeable battery
... ... @@ -83,7 +83,6 @@
83 83  * Max continuously current: 130mA
84 84  * Max boost current: 2A, 1 second
85 85  
86 -
87 87  (% style="color:#037691" %)**Power Consumption**
88 88  
89 89  * STOP Mode: 10uA @ 3.3v
... ... @@ -90,69 +90,81 @@
90 90  * Max transmit power: 350mA@3.3v
91 91  
92 92  
93 -
94 -
95 95  == ​1.4  Applications ==
96 96  
108 +
109 +* Smart Buildings & Home Automation
110 +* Logistics and Supply Chain Management
111 +* Smart Metering
97 97  * Smart Agriculture
113 +* Smart Cities
114 +* Smart Factory
98 98  
99 99  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
100 100  ​
101 101  
119 +
120 +
121 +
102 102  == 1.5  Pin Definitions ==
103 103  
104 104  
105 -[[image:1657246476176-652.png]]
125 +[[image:1657328609906-564.png]]
106 106  
107 107  
108 108  
109 -= 2.  Use NSE01 to communicate with IoT Server =
129 += 2.  Use NDDS75 to communicate with IoT Server =
110 110  
131 +
111 111  == 2.1  How it works ==
112 112  
113 113  
114 114  (((
115 -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.
136 +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.
116 116  )))
117 117  
118 118  
119 119  (((
120 -The diagram below shows the working flow in default firmware of NSE01:
141 +The diagram below shows the working flow in default firmware of NDDS75:
121 121  )))
122 122  
123 -[[image:image-20220708101605-2.png]]
124 -
125 125  (((
126 126  
127 127  )))
128 128  
148 +[[image:1657328659945-416.png]]
129 129  
150 +(((
151 +
152 +)))
130 130  
131 -== 2.2 ​ Configure the NSE01 ==
132 132  
155 +== 2.2 ​ Configure the NDDS75 ==
133 133  
157 +
134 134  === 2.2.1 Test Requirement ===
135 135  
136 136  
137 137  (((
138 -To use NSE01 in your city, make sure meet below requirements:
162 +To use NDDS75 in your city, make sure meet below requirements:
139 139  )))
140 140  
141 141  * Your local operator has already distributed a NB-IoT Network there.
142 -* The local NB-IoT network used the band that NSE01 supports.
166 +* The local NB-IoT network used the band that NDDS75 supports.
143 143  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
144 144  
145 145  (((
146 -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
170 +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.
147 147  )))
148 148  
149 149  
150 -[[image:1657249419225-449.png]]
174 +[[image:1657328756309-230.png]]
151 151  
152 152  
153 153  
154 154  === 2.2.2 Insert SIM card ===
155 155  
180 +
156 156  (((
157 157  Insert the NB-IoT Card get from your provider.
158 158  )))
... ... @@ -162,19 +162,22 @@
162 162  )))
163 163  
164 164  
165 -[[image:1657249468462-536.png]]
190 +[[image:1657328884227-504.png]]
166 166  
167 167  
168 168  
169 -=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
194 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
170 170  
196 +
171 171  (((
172 172  (((
173 -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.
199 +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.
174 174  )))
175 175  )))
176 176  
203 +[[image:image-20220709092052-2.png]]
177 177  
205 +
178 178  **Connection:**
179 179  
180 180   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -193,13 +193,14 @@
193 193  * Flow Control: (% style="color:green" %)**None**
194 194  
195 195  (((
196 -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.
224 +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.
197 197  )))
198 198  
199 -[[image:image-20220708110657-3.png]]
227 +[[image:1657329814315-101.png]]
200 200  
229 +
201 201  (((
202 -(% 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/]]
231 +(% 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]]**
203 203  )))
204 204  
205 205  
... ... @@ -206,59 +206,72 @@
206 206  
207 207  === 2.2.4 Use CoAP protocol to uplink data ===
208 208  
209 -(% 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/]]
210 210  
239 +(% 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/]]**
211 211  
241 +
242 +(((
212 212  **Use below commands:**
244 +)))
213 213  
214 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
215 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
216 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
246 +* (((
247 +(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
248 +)))
249 +* (((
250 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
251 +)))
252 +* (((
253 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
217 217  
255 +
256 +
257 +)))
258 +
259 +(((
218 218  For parameter description, please refer to AT command set
261 +)))
219 219  
220 -[[image:1657249793983-486.png]]
263 +[[image:1657330452568-615.png]]
221 221  
222 222  
223 -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.
224 224  
225 -[[image:1657249831934-534.png]]
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 +)))
226 226  
271 +[[image:1657330472797-498.png]]
227 227  
228 228  
274 +
229 229  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
230 230  
231 -This feature is supported since firmware version v1.0.1
232 232  
233 -
234 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
278 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
235 235  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
236 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
280 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
237 237  
238 -[[image:1657249864775-321.png]]
282 +[[image:1657330501006-241.png]]
239 239  
240 240  
241 -[[image:1657249930215-289.png]]
285 +[[image:1657330533775-472.png]]
242 242  
243 243  
244 244  
245 245  === 2.2.6 Use MQTT protocol to uplink data ===
246 246  
247 -This feature is supported since firmware version v110
248 248  
292 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
293 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
294 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
295 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
296 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
297 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
298 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
249 249  
250 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
251 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
252 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
253 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
254 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
255 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
256 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
257 -
258 258  [[image:1657249978444-674.png]]
259 259  
260 260  
261 -[[image:1657249990869-686.png]]
303 +[[image:1657330723006-866.png]]
262 262  
263 263  
264 264  (((
... ... @@ -269,72 +269,119 @@
269 269  
270 270  === 2.2.7 Use TCP protocol to uplink data ===
271 271  
272 -This feature is supported since firmware version v110
273 273  
274 -
275 275  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
276 276  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
277 277  
278 -[[image:1657250217799-140.png]]
318 +[[image:image-20220709093918-1.png]]
279 279  
280 280  
281 -[[image:1657250255956-604.png]]
321 +[[image:image-20220709093918-2.png]]
282 282  
283 283  
284 284  
285 285  === 2.2.8 Change Update Interval ===
286 286  
327 +
287 287  User can use below command to change the (% style="color:green" %)**uplink interval**.
288 288  
289 289  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
290 290  
291 291  (((
292 -(% style="color:red" %)**NOTE:**
293 -)))
333 +(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.**
294 294  
295 -(((
296 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
335 +
297 297  )))
298 298  
338 +**NOTE:When the firmware version is v1.3.2 and later firmware:**
299 299  
340 +**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).**
300 300  
342 +
301 301  == 2.3  Uplink Payload ==
302 302  
303 -In this mode, uplink payload includes in total 18 bytes
304 304  
305 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
346 +In this mode, uplink payload includes in total 14 bytes
347 +
348 +
349 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
306 306  |=(% style="width: 60px;" %)(((
307 307  **Size(bytes)**
308 -)))|=(% 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**
309 -|(% 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"]]
352 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
353 +|(% 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"]]
310 310  
311 311  (((
312 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
356 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
313 313  )))
314 314  
315 315  
316 -[[image:image-20220708111918-4.png]]
360 +[[image:1657331036973-987.png]]
317 317  
318 318  
363 +(((
319 319  The payload is ASCII string, representative same HEX:
365 +)))
320 320  
321 -0x72403155615900640c7817075e0a8c02f900 where:
367 +(((
368 +0x72403155615900640c6c19029200 where:
369 +)))
322 322  
323 -* Device ID: 0x 724031556159 = 724031556159
324 -* Version: 0x0064=100=1.0.0
371 +* (((
372 +Device ID: 0x724031556159 = 724031556159
373 +)))
374 +* (((
375 +Version: 0x0064=100=1.0.0
376 +)))
325 325  
326 -* BAT: 0x0c78 = 3192 mV = 3.192V
327 -* Singal: 0x17 = 23
328 -* Soil Moisture: 0x075e= 1886 = 18.86  %
329 -* Soil Temperature:0x0a8c =2700=27 °C
330 -* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
331 -* Interrupt: 0x00 = 0
378 +* (((
379 +BAT: 0x0c6c = 3180 mV = 3.180V
380 +)))
381 +* (((
382 +Signal: 0x19 = 25
383 +)))
384 +* (((
385 +Distance: 0x0292= 658 mm
386 +)))
387 +* (((
388 +Interrupt: 0x00 = 0
332 332  
390 +
391 +)))
392 +
393 +**NOTE:When the firmware version is v1.3.2 and later firmware:**
394 +
395 +In this mode, uplink payload includes 69 bytes in total by default.
396 +
397 +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.
398 +
399 +|**Size(bytes)**|**8**|2|2|1|1|1|2|4|2|4
400 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Distance|Timestamp|Distance|Timestamp.......
401 +
402 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
403 +
404 +[[image:image-20220908175246-1.png]]
405 +
406 +The payload is ASCII string, representative same HEX:
407 +
408 +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:
409 +
410 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
411 +* (% style="color:red" %)Version: 0x0084=132=1.3.2
412 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
413 +* (% style="color:blue" %)Singal: 0x1e = 30
414 +* (% style="color:red" %)Mod: 0x01 = 1
415 +* Interrupt: 0x00= 0
416 +* Distance: 0x0039= 57 = 57
417 +* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
418 +* Distance,Time stamp : 00396319baf0
419 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
420 +
333 333  == 2.4  Payload Explanation and Sensor Interface ==
334 334  
335 335  
336 336  === 2.4.1  Device ID ===
337 337  
426 +
338 338  (((
339 339  By default, the Device ID equal to the last 6 bytes of IMEI.
340 340  )))
... ... @@ -341,6 +341,8 @@
341 341  
342 342  (((
343 343  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
433 +
434 +
344 344  )))
345 345  
346 346  (((
... ... @@ -352,19 +352,29 @@
352 352  )))
353 353  
354 354  (((
355 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
446 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
356 356  )))
357 357  
358 358  
450 +**NOTE:When the firmware version is v1.3.2 and later firmware:**
359 359  
452 +By default, the Device ID equal to the last 15 bits of IMEI.
453 +
454 +User can use **AT+DEUI** to set Device ID
455 +
456 +**Example:**
457 +
458 +AT+DEUI=868411056754138
459 +
360 360  === 2.4.2  Version Info ===
361 361  
462 +
362 362  (((
363 363  Specify the software version: 0x64=100, means firmware version 1.00.
364 364  )))
365 365  
366 366  (((
367 -For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
468 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
368 368  )))
369 369  
370 370  
... ... @@ -371,9 +371,6 @@
371 371  
372 372  === 2.4.3  Battery Info ===
373 373  
374 -(((
375 -Check the battery voltage for LSE01.
376 -)))
377 377  
378 378  (((
379 379  Ex1: 0x0B45 = 2885mV
... ... @@ -387,6 +387,7 @@
387 387  
388 388  === 2.4.4  Signal Strength ===
389 389  
488 +
390 390  (((
391 391  NB-IoT Network signal Strength.
392 392  )))
... ... @@ -417,65 +417,22 @@
417 417  
418 418  
419 419  
420 -=== 2.4.5  Soil Moisture ===
519 +=== 2.4.5  Distance ===
421 421  
422 -(((
423 -(((
424 -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.
425 -)))
426 -)))
427 427  
428 -(((
429 -(((
430 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
431 -)))
432 -)))
522 +Get the distance. Flat object range 280mm - 7500mm.
433 433  
434 434  (((
435 -
525 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
436 436  )))
437 437  
438 438  (((
439 -(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
440 -)))
441 -
442 -
443 -
444 -=== 2.4.6  Soil Temperature ===
445 -
446 446  (((
447 -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
530 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
448 448  )))
449 -
450 -(((
451 -**Example**:
452 452  )))
453 453  
454 454  (((
455 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
456 -)))
457 -
458 -(((
459 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
460 -)))
461 -
462 -
463 -
464 -=== 2.4.7  Soil Conductivity (EC) ===
465 -
466 -(((
467 -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).
468 -)))
469 -
470 -(((
471 -For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
472 -)))
473 -
474 -(((
475 -Generally, the EC value of irrigation water is less than 800uS / cm.
476 -)))
477 -
478 -(((
479 479  
480 480  )))
481 481  
... ... @@ -483,10 +483,11 @@
483 483  
484 484  )))
485 485  
486 -=== 2.4.8  Digital Interrupt ===
542 +=== 2.4.6  Digital Interrupt ===
487 487  
544 +
488 488  (((
489 -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.
546 +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.
490 490  )))
491 491  
492 492  (((
... ... @@ -517,19 +517,24 @@
517 517  
518 518  
519 519  
520 -=== 2.4.9  ​+5V Output ===
577 +=== 2.4.7  ​+5V Output ===
521 521  
579 +
522 522  (((
523 -NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
581 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
524 524  )))
525 525  
526 526  
527 527  (((
528 528  The 5V output time can be controlled by AT Command.
587 +
588 +
529 529  )))
530 530  
531 531  (((
532 532  (% style="color:blue" %)**AT+5VT=1000**
593 +
594 +
533 533  )))
534 534  
535 535  (((
... ... @@ -540,11 +540,12 @@
540 540  
541 541  == 2.5  Downlink Payload ==
542 542  
543 -By default, NSE01 prints the downlink payload to console port.
544 544  
545 -[[image:image-20220708133731-5.png]]
606 +By default, NDDS75 prints the downlink payload to console port.
546 546  
608 +[[image:image-20220709100028-1.png]]
547 547  
610 +
548 548  (((
549 549  (% style="color:blue" %)**Examples:**
550 550  )))
... ... @@ -578,7 +578,7 @@
578 578  )))
579 579  
580 580  (((
581 -If payload = 0x04FF, it will reset the NSE01
644 +If payload = 0x04FF, it will reset the NDDS75
582 582  )))
583 583  
584 584  
... ... @@ -589,79 +589,89 @@
589 589  )))
590 590  
591 591  
655 +== 2.6 Distance alarm function ==
592 592  
593 -== 2.6  ​LED Indicator ==
657 +➢ AT Command:
594 594  
595 -(((
596 -The NSE01 has an internal LED which is to show the status of different state.
659 +AT+ LDDSALARM=min,max
597 597  
661 +² When min=0, and max≠0, Alarm higher than max
598 598  
599 -* 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)
600 -* Then the LED will be on for 1 second means device is boot normally.
601 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
602 -* For each uplink probe, LED will be on for 500ms.
603 -)))
663 +² When min≠0, and max=0, Alarm lower than min
604 604  
665 +² When min≠0 and max≠0, Alarm higher than max or lower than min
605 605  
667 +Example:
606 606  
669 +AT+ LDDSALARM=260,2000 ~/~/ Alarm when distance lower than 260.
607 607  
608 -== 2.7  Installation in Soil ==
609 609  
610 -__**Measurement the soil surface**__
672 +== 2.7 Set the number of data to be uploaded and the recording time ==
611 611  
612 -(((
613 -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]]
614 -)))
674 +➢ AT Command:
615 615  
616 -[[image:1657259653666-883.png]] ​
676 +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)
617 617  
678 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
618 618  
619 -(((
620 -
680 +== 2.8 Read or Clear cached data ==
621 621  
622 -(((
623 -Dig a hole with diameter > 20CM.
624 -)))
682 +➢ AT Command:
625 625  
626 -(((
627 -Horizontal insert the probe to the soil and fill the hole for long term measurement.
628 -)))
629 -)))
684 +AT+CDP ~/~/ Read cached data
630 630  
631 -[[image:1654506665940-119.png]]
686 +[[image:image-20220908175333-2.png]]
632 632  
688 +AT+CDP=0 ~/~/ Clear cached data
689 +
690 +== 2.9  ​LED Indicator ==
691 +
692 +
693 +The NDDS75 has an internal LED which is to show the status of different state.
694 +
695 +
696 +* 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)
697 +* Then the LED will be on for 1 second means device is boot normally.
698 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
699 +* For each uplink probe, LED will be on for 500ms.
700 +
633 633  (((
634 634  
635 635  )))
636 636  
637 637  
638 -== 2.8  ​Firmware Change Log ==
639 639  
707 +== 2.10  ​Firmware Change Log ==
640 640  
641 -Download URL & Firmware Change log
642 642  
643 -[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
710 +(((
711 +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]]
712 +)))
644 644  
714 +(((
715 +
716 +)))
645 645  
646 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
718 +(((
719 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
720 +)))
647 647  
648 648  
649 649  
650 -== 2.9  ​Battery Analysis ==
724 +== 2.11  ​Battery Analysis ==
651 651  
652 -=== 2.9.1  ​Battery Type ===
653 653  
727 +=== 2.11.1  ​Battery Type ===
654 654  
729 +
655 655  (((
656 -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.
731 +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.
657 657  )))
658 658  
659 -
660 660  (((
661 661  The battery is designed to last for several years depends on the actually use environment and update interval. 
662 662  )))
663 663  
664 -
665 665  (((
666 666  The battery related documents as below:
667 667  )))
... ... @@ -671,13 +671,14 @@
671 671  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
672 672  
673 673  (((
674 -[[image:image-20220708140453-6.png]]
747 +[[image:image-20220709101450-2.png]]
675 675  )))
676 676  
677 677  
678 678  
679 -=== 2.9.2  Power consumption Analyze ===
752 +=== 2.11.2  Power consumption Analyze ===
680 680  
754 +
681 681  (((
682 682  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.
683 683  )))
... ... @@ -710,12 +710,13 @@
710 710  And the Life expectation in difference case will be shown on the right.
711 711  )))
712 712  
713 -[[image:image-20220708141352-7.jpeg]]
787 +[[image:image-20220709110451-3.png]]
714 714  
715 715  
716 716  
717 -=== 2.9.3  ​Battery Note ===
791 +=== 2.11.3  ​Battery Note ===
718 718  
793 +
719 719  (((
720 720  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.
721 721  )))
... ... @@ -722,10 +722,11 @@
722 722  
723 723  
724 724  
725 -=== 2.9.4  Replace the battery ===
800 +=== 2.11.4  Replace the battery ===
726 726  
802 +
727 727  (((
728 -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).
804 +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).
729 729  )))
730 730  
731 731  
... ... @@ -732,6 +732,7 @@
732 732  
733 733  = 3. ​ Access NB-IoT Module =
734 734  
811 +
735 735  (((
736 736  Users can directly access the AT command set of the NB-IoT module.
737 737  )))
... ... @@ -738,19 +738,23 @@
738 738  
739 739  (((
740 740  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/]] 
818 +
819 +
741 741  )))
742 742  
743 -[[image:1657261278785-153.png]]
822 +[[image:1657333200519-600.png]]
744 744  
745 745  
746 746  
747 747  = 4.  Using the AT Commands =
748 748  
828 +
749 749  == 4.1  Access AT Commands ==
750 750  
751 -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/]]
752 752  
832 +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]]
753 753  
834 +
754 754  AT+<CMD>?  : Help on <CMD>
755 755  
756 756  AT+<CMD>         : Run <CMD>
... ... @@ -790,7 +790,23 @@
790 790  
791 791  AT+SERVADDR  : Server Address
792 792  
874 +AT+TR      : Get or Set record time"
793 793  
876 +AT+APN     : Get or set the APN
877 +
878 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
879 +
880 +AT+DNSCFG  : Get or Set DNS Server
881 +
882 +AT+GETSENSORVALUE   : Returns the current sensor measurement
883 +
884 +AT+NOUD      : Get or Set the number of data to be uploaded
885 +
886 +AT+CDP     : Read or Clear cached data
887 +
888 +AT+LDDSALARM : Get or Set alarm of distance
889 +
890 +
794 794  (% style="color:#037691" %)**COAP Management**      
795 795  
796 796  AT+URI            : Resource parameters
... ... @@ -824,6 +824,7 @@
824 824  
825 825  = ​5.  FAQ =
826 826  
924 +
827 827  == 5.1 ​ How to Upgrade Firmware ==
828 828  
829 829  
... ... @@ -836,20 +836,14 @@
836 836  )))
837 837  
838 838  (((
839 -(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
937 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
840 840  )))
841 841  
842 842  
843 843  
844 -== 5.2  Can I calibrate NSE01 to different soil types? ==
845 -
846 -(((
847 -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]].
848 -)))
849 -
850 -
851 851  = 6.  Trouble Shooting =
852 852  
944 +
853 853  == 6.1  ​Connection problem when uploading firmware ==
854 854  
855 855  
... ... @@ -865,6 +865,7 @@
865 865  
866 866  == 6.2  AT Command input doesn't work ==
867 867  
960 +
868 868  (((
869 869  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.
870 870  
... ... @@ -875,7 +875,7 @@
875 875  = 7. ​ Order Info =
876 876  
877 877  
878 -Part Number**:** (% style="color:#4f81bd" %)**NSE01**
971 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
879 879  
880 880  
881 881  (% class="wikigeneratedid" %)
... ... @@ -890,7 +890,7 @@
890 890  
891 891  (% style="color:#037691" %)**Package Includes**:
892 892  
893 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
986 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
894 894  * External antenna x 1
895 895  )))
896 896  
... ... @@ -897,10 +897,13 @@
897 897  (((
898 898  
899 899  
993 +
900 900  (% style="color:#037691" %)**Dimension and weight**:
901 901  
902 -* Size: 195 x 125 x 55 mm
903 -* Weight:   420g
996 +* Device Size: 13.0 x 5 x 4.5 cm
997 +* Device Weight: 150g
998 +* Package Size / pcs : 15 x 12x 5.5 cm
999 +* Weight / pcs : 220g
904 904  )))
905 905  
906 906  (((
... ... @@ -912,5 +912,6 @@
912 912  
913 913  = 9.  Support =
914 914  
1011 +
915 915  * 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.
916 916  * 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,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +492.6 KB
Content
1657328659945-416.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.8 KB
Content
1657328756309-230.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.5 KB
Content
1657328884227-504.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +483.6 KB
Content
1657329814315-101.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.3 KB
Content
1657330452568-615.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +71.3 KB
Content
1657330472797-498.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +68.9 KB
Content
1657330501006-241.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +119.2 KB
Content
1657330533775-472.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +74.9 KB
Content
1657330723006-866.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +74.1 KB
Content
1657331036973-987.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +83.8 KB
Content
1657332990863-496.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.2 KB
Content
1657333200519-600.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
image-20220709092052-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +247.3 KB
Content
image-20220709093918-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +42.2 KB
Content
image-20220709093918-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +61.9 KB
Content
image-20220709100028-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +8.8 KB
Content
image-20220709101450-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.5 KB
Content
image-20220709110451-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +611.5 KB
Content
image-20220908175246-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +31.1 KB
Content