Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 75.2
edited by Xiaoling
on 2022/07/09 08:52
on 2022/07/09 08:52
Change comment:
There is no comment for this version
To version 103.1
edited by David Huang
on 2022/09/08 18:02
on 2022/09/08 18:02
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 21 added, 0 removed)
- 1657328609906-564.png
- 1657328659945-416.png
- 1657328756309-230.png
- 1657328884227-504.png
- 1657329814315-101.png
- 1657330452568-615.png
- 1657330472797-498.png
- 1657330501006-241.png
- 1657330533775-472.png
- 1657330723006-866.png
- 1657331036973-987.png
- 1657332990863-496.png
- 1657333200519-600.png
- image-20220709092052-2.png
- image-20220709093918-1.png
- image-20220709093918-2.png
- image-20220709100028-1.png
- image-20220709101450-2.png
- image-20220709110451-3.png
- image-20220908175246-1.png
- image-20220908175333-2.png
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +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 ... ... @@ -41,19 +41,21 @@ 41 41 42 42 == 1.2 Features == 43 43 60 + 44 44 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 45 -* Monitor Soil Moisture 46 -* Monitor Soil Temperature 47 -* Monitor Soil Conductivity 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 48 48 * AT Commands to change parameters 49 49 * Uplink on periodically 50 50 * Downlink to change configure 51 51 * IP66 Waterproof Enclosure 52 -* Ultra-Low Power consumption 53 -* AT Commands to change parameters 54 54 * Micro SIM card slot for NB-IoT SIM 55 55 * 8500mAh Battery for long term use 56 56 74 + 57 57 == 1.3 Specification == 58 58 59 59 ... ... @@ -71,75 +71,95 @@ 71 71 * - B20 @H-FDD: 800MHz 72 72 * - B28 @H-FDD: 700MHz 73 73 74 - Probe(% style="color:#037691" %)**Specification:**92 +(% style="color:#037691" %)**Battery:** 75 75 76 -Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height. 94 +* Li/SOCI2 un-chargeable battery 95 +* Capacity: 8500mAh 96 +* Self Discharge: <1% / Year @ 25°C 97 +* Max continuously current: 130mA 98 +* Max boost current: 2A, 1 second 77 77 78 - [[image:image-20220708101224-1.png]]100 +(% style="color:#037691" %)**Power Consumption** 79 79 102 +* STOP Mode: 10uA @ 3.3v 103 +* Max transmit power: 350mA@3.3v 80 80 81 81 82 82 == 1.4 Applications == 83 83 108 + 109 +* Smart Buildings & Home Automation 110 +* Logistics and Supply Chain Management 111 +* Smart Metering 84 84 * Smart Agriculture 113 +* Smart Cities 114 +* Smart Factory 85 85 86 86 (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %) 87 87 88 88 119 + 120 + 121 + 89 89 == 1.5 Pin Definitions == 90 90 91 91 92 -[[image:16572 46476176-652.png]]125 +[[image:1657328609906-564.png]] 93 93 94 94 95 95 96 -= 2. Use NS E01to communicate with IoT Server =129 += 2. Use NDDS75 to communicate with IoT Server = 97 97 131 + 98 98 == 2.1 How it works == 99 99 100 100 101 101 ((( 102 -The NS E01is equipped with a NB-IoT module, the pre-loaded firmware in NSE01will 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. 103 103 ))) 104 104 105 105 106 106 ((( 107 -The diagram below shows the working flow in default firmware of NS E01:141 +The diagram below shows the working flow in default firmware of NDDS75: 108 108 ))) 109 109 110 -[[image:image-20220708101605-2.png]] 111 - 112 112 ((( 113 113 114 114 ))) 115 115 148 +[[image:1657328659945-416.png]] 116 116 150 +((( 151 + 152 +))) 117 117 118 -== 2.2 Configure the NSE01 == 119 119 155 +== 2.2 Configure the NDDS75 == 120 120 157 + 121 121 === 2.2.1 Test Requirement === 122 122 123 123 124 124 ((( 125 -To use NS E01in your city, make sure meet below requirements:162 +To use NDDS75 in your city, make sure meet below requirements: 126 126 ))) 127 127 128 128 * Your local operator has already distributed a NB-IoT Network there. 129 -* The local NB-IoT network used the band that NS E01supports.166 +* The local NB-IoT network used the band that NDDS75 supports. 130 130 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 131 131 132 132 ((( 133 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The E01will 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 server170 +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. 134 134 ))) 135 135 136 136 137 -[[image:16572 49419225-449.png]]174 +[[image:1657328756309-230.png]] 138 138 139 139 140 140 141 141 === 2.2.2 Insert SIM card === 142 142 180 + 143 143 ((( 144 144 Insert the NB-IoT Card get from your provider. 145 145 ))) ... ... @@ -149,19 +149,22 @@ 149 149 ))) 150 150 151 151 152 -[[image:16572 49468462-536.png]]190 +[[image:1657328884227-504.png]] 153 153 154 154 155 155 156 -=== 2.2.3 Connect USB – TTL to NS E01to configure it ===194 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 157 157 196 + 158 158 ((( 159 159 ((( 160 -User need to configure NS E01via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01support AT Commands, user can use a USB to TTL adapter to connect to NSE01and 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. 161 161 ))) 162 162 ))) 163 163 203 +[[image:image-20220709092052-2.png]] 164 164 205 + 165 165 **Connection:** 166 166 167 167 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -180,13 +180,14 @@ 180 180 * Flow Control: (% style="color:green" %)**None** 181 181 182 182 ((( 183 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NS E01. NSE01will 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. 184 184 ))) 185 185 186 -[[image: image-20220708110657-3.png]]227 +[[image:1657329814315-101.png]] 187 187 229 + 188 188 ((( 189 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[http:~~/~~/www.dr agino.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]]** 190 190 ))) 191 191 192 192 ... ... @@ -193,59 +193,72 @@ 193 193 194 194 === 2.2.4 Use CoAP protocol to uplink data === 195 195 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/]] 197 197 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/]]** 198 198 241 + 242 +((( 199 199 **Use below commands:** 244 +))) 200 200 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 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 204 204 255 + 256 + 257 +))) 258 + 259 +((( 205 205 For parameter description, please refer to AT command set 261 +))) 206 206 207 -[[image:1657 249793983-486.png]]263 +[[image:1657330452568-615.png]] 208 208 209 209 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. 211 211 212 -[[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 +))) 213 213 271 +[[image:1657330472797-498.png]] 214 214 215 215 274 + 216 216 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 217 217 218 -This feature is supported since firmware version v1.0.1 219 219 220 - 221 -* (% 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 222 222 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 223 -* (% 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 224 224 225 -[[image:1657 249864775-321.png]]282 +[[image:1657330501006-241.png]] 226 226 227 227 228 -[[image:1657 249930215-289.png]]285 +[[image:1657330533775-472.png]] 229 229 230 230 231 231 232 232 === 2.2.6 Use MQTT protocol to uplink data === 233 233 234 -This feature is supported since firmware version v110 235 235 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 236 236 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 - 245 245 [[image:1657249978444-674.png]] 246 246 247 247 248 -[[image:16572 49990869-686.png]]303 +[[image:1657330723006-866.png]] 249 249 250 250 251 251 ((( ... ... @@ -256,72 +256,119 @@ 256 256 257 257 === 2.2.7 Use TCP protocol to uplink data === 258 258 259 -This feature is supported since firmware version v110 260 260 261 - 262 262 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 263 263 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 264 264 265 -[[image: 1657250217799-140.png]]318 +[[image:image-20220709093918-1.png]] 266 266 267 267 268 -[[image: 1657250255956-604.png]]321 +[[image:image-20220709093918-2.png]] 269 269 270 270 271 271 272 272 === 2.2.8 Change Update Interval === 273 273 327 + 274 274 User can use below command to change the (% style="color:green" %)**uplink interval**. 275 275 276 276 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 277 277 278 278 ((( 279 -(% style="color:red" %)**NOTE:** 280 -))) 333 +(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.** 281 281 282 -((( 283 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 335 + 284 284 ))) 285 285 338 +**NOTE:When the firmware version is v1.3.2 and later firmware:** 286 286 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).** 287 287 342 + 288 288 == 2.3 Uplink Payload == 289 289 290 -In this mode, uplink payload includes in total 18 bytes 291 291 292 -(% 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" %) 293 293 |=(% style="width: 60px;" %)((( 294 294 **Size(bytes)** 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:10 8px" %)[[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"]] 297 297 298 298 ((( 299 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NS E01 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. 300 300 ))) 301 301 302 302 303 -[[image: image-20220708111918-4.png]]360 +[[image:1657331036973-987.png]] 304 304 305 305 363 +((( 306 306 The payload is ASCII string, representative same HEX: 365 +))) 307 307 308 -0x72403155615900640c7817075e0a8c02f900 where: 367 +((( 368 +0x72403155615900640c6c19029200 where: 369 +))) 309 309 310 -* Device ID: 0x 724031556159 = 724031556159 311 -* Version: 0x0064=100=1.0.0 371 +* ((( 372 +Device ID: 0x724031556159 = 724031556159 373 +))) 374 +* ((( 375 +Version: 0x0064=100=1.0.0 376 +))) 312 312 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 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 319 319 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 + 320 320 == 2.4 Payload Explanation and Sensor Interface == 321 321 322 322 323 323 === 2.4.1 Device ID === 324 324 426 + 325 325 ((( 326 326 By default, the Device ID equal to the last 6 bytes of IMEI. 327 327 ))) ... ... @@ -328,6 +328,8 @@ 328 328 329 329 ((( 330 330 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 433 + 434 + 331 331 ))) 332 332 333 333 ((( ... ... @@ -339,19 +339,29 @@ 339 339 ))) 340 340 341 341 ((( 342 -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. 343 343 ))) 344 344 345 345 450 +**NOTE:When the firmware version is v1.3.2 and later firmware:** 346 346 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 + 347 347 === 2.4.2 Version Info === 348 348 462 + 349 349 ((( 350 350 Specify the software version: 0x64=100, means firmware version 1.00. 351 351 ))) 352 352 353 353 ((( 354 -For example: 0x00 64 : this device is NS E01with firmware version 1.0.0.468 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 355 355 ))) 356 356 357 357 ... ... @@ -358,9 +358,6 @@ 358 358 359 359 === 2.4.3 Battery Info === 360 360 361 -((( 362 -Check the battery voltage for LSE01. 363 -))) 364 364 365 365 ((( 366 366 Ex1: 0x0B45 = 2885mV ... ... @@ -374,6 +374,7 @@ 374 374 375 375 === 2.4.4 Signal Strength === 376 376 488 + 377 377 ((( 378 378 NB-IoT Network signal Strength. 379 379 ))) ... ... @@ -404,65 +404,22 @@ 404 404 405 405 406 406 407 -=== 2.4.5 Soil Moisture ===519 +=== 2.4.5 Distance === 408 408 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 -))) 414 414 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 -))) 522 +Get the distance. Flat object range 280mm - 7500mm. 420 420 421 421 ((( 422 - 525 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 423 423 ))) 424 424 425 425 ((( 426 -(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.** 427 -))) 428 - 429 - 430 - 431 -=== 2.4.6 Soil Temperature === 432 - 433 433 ((( 434 - Getthetemperatureinthesoil.Thevaluerangeoftheregisteris-4000-+800(Decimal),dividethisvalueby100togetthetemperatureinthesoil.Forexample,ifthedatayougetfromtheregisteris__**0x090xEC**__,thetemperaturecontentinthesoilis530 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 435 435 ))) 436 - 437 -((( 438 -**Example**: 439 439 ))) 440 440 441 441 ((( 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 -((( 466 466 467 467 ))) 468 468 ... ... @@ -470,10 +470,11 @@ 470 470 471 471 ))) 472 472 473 -=== 2.4. 8Digital Interrupt ===542 +=== 2.4.6 Digital Interrupt === 474 474 544 + 475 475 ((( 476 -Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NS E01will 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. 477 477 ))) 478 478 479 479 ((( ... ... @@ -504,19 +504,24 @@ 504 504 505 505 506 506 507 -=== 2.4. 9+5V Output ===577 +=== 2.4.7 +5V Output === 508 508 579 + 509 509 ((( 510 -NS E01will 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. 511 511 ))) 512 512 513 513 514 514 ((( 515 515 The 5V output time can be controlled by AT Command. 587 + 588 + 516 516 ))) 517 517 518 518 ((( 519 519 (% style="color:blue" %)**AT+5VT=1000** 593 + 594 + 520 520 ))) 521 521 522 522 ((( ... ... @@ -527,11 +527,12 @@ 527 527 528 528 == 2.5 Downlink Payload == 529 529 530 -By default, NSE01 prints the downlink payload to console port. 531 531 532 - [[image:image-20220708133731-5.png]]606 +By default, NDDS75 prints the downlink payload to console port. 533 533 608 +[[image:image-20220709100028-1.png]] 534 534 610 + 535 535 ((( 536 536 (% style="color:blue" %)**Examples:** 537 537 ))) ... ... @@ -565,7 +565,7 @@ 565 565 ))) 566 566 567 567 ((( 568 -If payload = 0x04FF, it will reset the NS E01644 +If payload = 0x04FF, it will reset the NDDS75 569 569 ))) 570 570 571 571 ... ... @@ -576,79 +576,89 @@ 576 576 ))) 577 577 578 578 655 +== 2.6 Distance alarm function == 579 579 580 - ==2.6LED Indicator ==657 +➢ AT Command: 581 581 582 -((( 583 -The NSE01 has an internal LED which is to show the status of different state. 659 +AT+ LDDSALARM=min,max 584 584 661 +² When min=0, and max≠0, Alarm higher than max 585 585 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 -))) 663 +² When min≠0, and max=0, Alarm lower than min 591 591 665 +² When min≠0 and max≠0, Alarm higher than max or lower than min 592 592 667 +Example: 593 593 669 +AT+ LDDSALARM=260,2000 ~/~/ Alarm when distance lower than 260. 594 594 595 -== 2.7 Installation in Soil == 596 596 597 - __**Measurementthesoilsurface**__672 +== 2.7 Set the number of data to be uploaded and the recording time == 598 598 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 -))) 674 +➢ AT Command: 602 602 603 - [[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) 604 604 678 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 605 605 606 -((( 607 - 680 +== 2.8 Read or Clear cached data == 608 608 609 -((( 610 -Dig a hole with diameter > 20CM. 611 -))) 682 +➢ AT Command: 612 612 613 -((( 614 -Horizontal insert the probe to the soil and fill the hole for long term measurement. 615 -))) 616 -))) 684 +AT+CDP ~/~/ Read cached data 617 617 618 -[[image: 1654506665940-119.png]]686 +[[image:image-20220908175333-2.png]] 619 619 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 + 620 620 ((( 621 621 622 622 ))) 623 623 624 624 625 -== 2.8 Firmware Change Log == 626 626 707 +== 2.10 Firmware Change Log == 627 627 628 -Download URL & Firmware Change log 629 629 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/]] 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 +))) 631 631 714 +((( 715 + 716 +))) 632 632 633 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 718 +((( 719 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 720 +))) 634 634 635 635 636 636 637 -== 2. 9Battery Analysis ==724 +== 2.11 Battery Analysis == 638 638 639 -=== 2.9.1 Battery Type === 640 640 727 +=== 2.11.1 Battery Type === 641 641 729 + 642 642 ((( 643 -The NS E01battery 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. 644 644 ))) 645 645 646 - 647 647 ((( 648 648 The battery is designed to last for several years depends on the actually use environment and update interval. 649 649 ))) 650 650 651 - 652 652 ((( 653 653 The battery related documents as below: 654 654 ))) ... ... @@ -658,13 +658,14 @@ 658 658 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 659 659 660 660 ((( 661 -[[image:image-2022070 8140453-6.png]]747 +[[image:image-20220709101450-2.png]] 662 662 ))) 663 663 664 664 665 665 666 -=== 2. 9.2 Power consumption Analyze ===752 +=== 2.11.2 Power consumption Analyze === 667 667 754 + 668 668 ((( 669 669 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. 670 670 ))) ... ... @@ -697,12 +697,13 @@ 697 697 And the Life expectation in difference case will be shown on the right. 698 698 ))) 699 699 700 -[[image:image-2022070 8141352-7.jpeg]]787 +[[image:image-20220709110451-3.png]] 701 701 702 702 703 703 704 -=== 2. 9.3 Battery Note ===791 +=== 2.11.3 Battery Note === 705 705 793 + 706 706 ((( 707 707 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. 708 708 ))) ... ... @@ -709,10 +709,11 @@ 709 709 710 710 711 711 712 -=== 2. 9.4 Replace the battery ===800 +=== 2.11.4 Replace the battery === 713 713 802 + 714 714 ((( 715 -The default battery pack of NS E01includes 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). 716 716 ))) 717 717 718 718 ... ... @@ -719,6 +719,7 @@ 719 719 720 720 = 3. Access NB-IoT Module = 721 721 811 + 722 722 ((( 723 723 Users can directly access the AT command set of the NB-IoT module. 724 724 ))) ... ... @@ -725,19 +725,23 @@ 725 725 726 726 ((( 727 727 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 + 728 728 ))) 729 729 730 -[[image:16572 61278785-153.png]]822 +[[image:1657333200519-600.png]] 731 731 732 732 733 733 734 734 = 4. Using the AT Commands = 735 735 828 + 736 736 == 4.1 Access AT Commands == 737 737 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/]] 739 739 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]] 740 740 834 + 741 741 AT+<CMD>? : Help on <CMD> 742 742 743 743 AT+<CMD> : Run <CMD> ... ... @@ -777,7 +777,23 @@ 777 777 778 778 AT+SERVADDR : Server Address 779 779 874 +AT+TR : Get or Set record time" 780 780 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 + 781 781 (% style="color:#037691" %)**COAP Management** 782 782 783 783 AT+URI : Resource parameters ... ... @@ -811,6 +811,7 @@ 811 811 812 812 = 5. FAQ = 813 813 924 + 814 814 == 5.1 How to Upgrade Firmware == 815 815 816 816 ... ... @@ -823,20 +823,14 @@ 823 823 ))) 824 824 825 825 ((( 826 -(% style="color:red" %)Notice, NS E01and LSE01share 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.** 827 827 ))) 828 828 829 829 830 830 831 -== 5.2 Can I calibrate NSE01 to different soil types? == 832 - 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 -))) 836 - 837 - 838 838 = 6. Trouble Shooting = 839 839 944 + 840 840 == 6.1 Connection problem when uploading firmware == 841 841 842 842 ... ... @@ -852,6 +852,7 @@ 852 852 853 853 == 6.2 AT Command input doesn't work == 854 854 960 + 855 855 ((( 856 856 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. 857 857 ... ... @@ -862,7 +862,7 @@ 862 862 = 7. Order Info = 863 863 864 864 865 -Part Number**:** (% style="color:#4f81bd" %)**NS E01**971 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 866 866 867 867 868 868 (% class="wikigeneratedid" %) ... ... @@ -877,7 +877,7 @@ 877 877 878 878 (% style="color:#037691" %)**Package Includes**: 879 879 880 -* NS E01NB-IoTSoil Moisture&ECSensor x 1986 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1 881 881 * External antenna x 1 882 882 ))) 883 883 ... ... @@ -884,10 +884,13 @@ 884 884 ((( 885 885 886 886 993 + 887 887 (% style="color:#037691" %)**Dimension and weight**: 888 888 889 -* Size: 195 x 125 x 55 mm 890 -* 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 891 891 ))) 892 892 893 893 ((( ... ... @@ -899,5 +899,6 @@ 899 899 900 900 = 9. Support = 901 901 1011 + 902 902 * 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. 903 903 * 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