<
From version < 90.2 >
edited by Xiaoling
on 2022/07/09 09:45
To version < 105.1 >
edited by David Huang
on 2022/10/08 11:49
>
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  
... ... @@ -55,6 +55,7 @@
55 55  * Micro SIM card slot for NB-IoT SIM
56 56  * 8500mAh Battery for long term use
57 57  
74 +
58 58  == 1.3  Specification ==
59 59  
60 60  
... ... @@ -88,6 +88,7 @@
88 88  
89 89  == ​1.4  Applications ==
90 90  
108 +
91 91  * Smart Buildings & Home Automation
92 92  * Logistics and Supply Chain Management
93 93  * Smart Metering
... ... @@ -100,6 +100,7 @@
100 100  
101 101  
102 102  
121 +
103 103  == 1.5  Pin Definitions ==
104 104  
105 105  
... ... @@ -109,8 +109,10 @@
109 109  
110 110  = 2.  Use NDDS75 to communicate with IoT Server =
111 111  
131 +
112 112  == 2.1  How it works ==
113 113  
134 +
114 114  (((
115 115  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  )))
... ... @@ -136,16 +136,17 @@
136 136  
137 137  === 2.2.1 Test Requirement ===
138 138  
160 +
139 139  (((
140 140  To use NDDS75 in your city, make sure meet below requirements:
141 141  )))
142 142  
143 143  * Your local operator has already distributed a NB-IoT Network there.
144 -* The local NB-IoT network used the band that NSE01 supports.
166 +* The local NB-IoT network used the band that NDDS75 supports.
145 145  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
146 146  
147 147  (((
148 -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
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.
149 149  )))
150 150  
151 151  
... ... @@ -155,6 +155,7 @@
155 155  
156 156  === 2.2.2 Insert SIM card ===
157 157  
180 +
158 158  (((
159 159  Insert the NB-IoT Card get from your provider.
160 160  )))
... ... @@ -170,6 +170,7 @@
170 170  
171 171  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
172 172  
196 +
173 173  (((
174 174  (((
175 175  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.
... ... @@ -178,15 +178,16 @@
178 178  
179 179  [[image:image-20220709092052-2.png]]
180 180  
181 -**Connection:**
182 182  
183 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
206 +(% style="color:blue" %)**Connection:**
184 184  
185 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
208 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
186 186  
187 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
210 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
188 188  
212 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
189 189  
214 +
190 190  In the PC, use below serial tool settings:
191 191  
192 192  * Baud:  (% style="color:green" %)**9600**
... ... @@ -201,8 +201,9 @@
201 201  
202 202  [[image:1657329814315-101.png]]
203 203  
229 +
204 204  (((
205 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
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]]**
206 206  )))
207 207  
208 208  
... ... @@ -209,22 +209,43 @@
209 209  
210 210  === 2.2.4 Use CoAP protocol to uplink data ===
211 211  
212 -(% 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/]]
213 213  
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/]]**
214 214  
241 +
242 +(((
215 215  **Use below commands:**
244 +)))
216 216  
217 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
218 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
219 -* (% 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
220 220  
255 +
256 +
257 +)))
258 +
259 +(((
221 221  For parameter description, please refer to AT command set
222 222  
262 +
263 +)))
264 +
223 223  [[image:1657330452568-615.png]]
224 224  
225 225  
268 +
269 +(((
226 226  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.
227 227  
272 +
273 +)))
274 +
228 228  [[image:1657330472797-498.png]]
229 229  
230 230  
... ... @@ -232,10 +232,11 @@
232 232  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
233 233  
234 234  
235 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
236 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
237 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
282 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
283 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
284 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
238 238  
286 +
239 239  [[image:1657330501006-241.png]]
240 240  
241 241  
... ... @@ -246,13 +246,13 @@
246 246  === 2.2.6 Use MQTT protocol to uplink data ===
247 247  
248 248  
249 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
250 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
251 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
252 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
253 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
254 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
255 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
297 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
298 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
299 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
300 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
301 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
302 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
303 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
256 256  
257 257  [[image:1657249978444-674.png]]
258 258  
... ... @@ -269,8 +269,8 @@
269 269  === 2.2.7 Use TCP protocol to uplink data ===
270 270  
271 271  
272 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
273 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
320 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
321 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
274 274  
275 275  [[image:image-20220709093918-1.png]]
276 276  
... ... @@ -281,30 +281,39 @@
281 281  
282 282  === 2.2.8 Change Update Interval ===
283 283  
332 +
284 284  User can use below command to change the (% style="color:green" %)**uplink interval**.
285 285  
286 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
335 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
287 287  
288 288  (((
338 +
339 +
340 +
289 289  (% style="color:red" %)**NOTE:**
290 -)))
291 291  
292 -(((
293 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
343 +(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
344 +
345 +(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
294 294  )))
295 295  
348 +(% 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).**
296 296  
297 297  
351 +
298 298  == 2.3  Uplink Payload ==
299 299  
300 -In this mode, uplink payload includes in total 14 bytes
301 301  
355 +=== 2.3.1  Before Firmware v1.3.2 ===
302 302  
303 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
357 +
358 +In this mode, uplink payload includes in total 14 bytes
359 +
360 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
304 304  |=(% style="width: 60px;" %)(((
305 305  **Size(bytes)**
306 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**1**
307 -|(% 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" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]
363 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
364 +|(% 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"]]
308 308  
309 309  (((
310 310  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
... ... @@ -313,8 +313,9 @@
313 313  
314 314  [[image:1657331036973-987.png]]
315 315  
373 +
316 316  (((
317 -The payload is ASCII string, representative same HEX:
375 +The payload is **ASCII** string, representative same HEX:
318 318  )))
319 319  
320 320  (((
... ... @@ -325,11 +325,11 @@
325 325  Device ID: 0x724031556159 = 724031556159
326 326  )))
327 327  * (((
328 -Version: 0x0064=100=1.0.0
386 +Version:  0x0064=100=1.0.0
329 329  )))
330 330  
331 331  * (((
332 -BAT: 0x0c6c = 3180 mV = 3.180V
390 +BAT:  0x0c6c = 3180 mV = 3.180V
333 333  )))
334 334  * (((
335 335  Signal: 0x19 = 25
... ... @@ -339,16 +339,51 @@
339 339  )))
340 340  * (((
341 341  Interrupt: 0x00 = 0
400 +
401 +
402 +
403 +
404 +
342 342  )))
343 343  
407 +=== **2.3.2  Since firmware v1.3.2** ===
344 344  
345 345  
410 +In this mode, uplink payload includes 69 bytes in total by default.
346 346  
412 +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.
413 +
414 +(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
415 +|(% 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
416 +|(% 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.......
417 +
418 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
419 +
420 +[[image:image-20220908175246-1.png]]
421 +
422 +
423 +The payload is ASCII string, representative same HEX:
424 +
425 +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:
426 +
427 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
428 +* (% style="color:red" %)Version: 0x0084=132=1.3.2
429 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
430 +* (% style="color:blue" %)Singal: 0x1e = 30
431 +* (% style="color:red" %)Mod: 0x01 = 1
432 +* Interrupt: 0x00= 0
433 +* Distance: 0x0039= 57 = 57
434 +* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
435 +* Distance,Time stamp : 00396319baf0
436 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
437 +
438 +
347 347  == 2.4  Payload Explanation and Sensor Interface ==
348 348  
349 349  
350 350  === 2.4.1  Device ID ===
351 351  
444 +
352 352  (((
353 353  By default, the Device ID equal to the last 6 bytes of IMEI.
354 354  )))
... ... @@ -355,10 +355,12 @@
355 355  
356 356  (((
357 357  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
451 +
452 +
358 358  )))
359 359  
360 360  (((
361 -**Example:**
456 +(% style="color:blue" %)**Example :**
362 362  )))
363 363  
364 364  (((
... ... @@ -366,19 +366,32 @@
366 366  )))
367 367  
368 368  (((
369 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
464 +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.
370 370  )))
371 371  
372 372  
468 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
373 373  
470 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
471 +
472 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
473 +
474 +
475 +(% style="color:blue" %)**Example :**
476 +
477 +AT+DEUI=868411056754138
478 +
479 +
480 +
374 374  === 2.4.2  Version Info ===
375 375  
483 +
376 376  (((
377 377  Specify the software version: 0x64=100, means firmware version 1.00.
378 378  )))
379 379  
380 380  (((
381 -For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
489 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
382 382  )))
383 383  
384 384  
... ... @@ -385,9 +385,6 @@
385 385  
386 386  === 2.4.3  Battery Info ===
387 387  
388 -(((
389 -Check the battery voltage for LSE01.
390 -)))
391 391  
392 392  (((
393 393  Ex1: 0x0B45 = 2885mV
... ... @@ -401,6 +401,7 @@
401 401  
402 402  === 2.4.4  Signal Strength ===
403 403  
509 +
404 404  (((
405 405  NB-IoT Network signal Strength.
406 406  )))
... ... @@ -431,65 +431,22 @@
431 431  
432 432  
433 433  
434 -=== 2.4.5  Soil Moisture ===
540 +=== 2.4.5  Distance ===
435 435  
436 -(((
437 -(((
438 -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.
439 -)))
440 -)))
441 441  
442 -(((
443 -(((
444 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
445 -)))
446 -)))
543 +Get the distance. Flat object range 280mm - 7500mm.
447 447  
448 448  (((
449 -
546 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
450 450  )))
451 451  
452 452  (((
453 -(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
454 -)))
455 -
456 -
457 -
458 -=== 2.4.6  Soil Temperature ===
459 -
460 460  (((
461 -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
551 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
462 462  )))
463 -
464 -(((
465 -**Example**:
466 466  )))
467 467  
468 468  (((
469 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
470 -)))
471 -
472 -(((
473 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
474 -)))
475 -
476 -
477 -
478 -=== 2.4.7  Soil Conductivity (EC) ===
479 -
480 -(((
481 -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).
482 -)))
483 -
484 -(((
485 -For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
486 -)))
487 -
488 -(((
489 -Generally, the EC value of irrigation water is less than 800uS / cm.
490 -)))
491 -
492 -(((
493 493  
494 494  )))
495 495  
... ... @@ -497,10 +497,11 @@
497 497  
498 498  )))
499 499  
500 -=== 2.4.8  Digital Interrupt ===
563 +=== 2.4.6  Digital Interrupt ===
501 501  
565 +
502 502  (((
503 -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.
567 +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.
504 504  )))
505 505  
506 506  (((
... ... @@ -508,7 +508,7 @@
508 508  )))
509 509  
510 510  (((
511 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
575 +(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/  (more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
512 512  )))
513 513  
514 514  
... ... @@ -531,19 +531,24 @@
531 531  
532 532  
533 533  
534 -=== 2.4.9  ​+5V Output ===
598 +=== 2.4.7  ​+5V Output ===
535 535  
600 +
536 536  (((
537 -NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
602 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
538 538  )))
539 539  
540 540  
541 541  (((
542 542  The 5V output time can be controlled by AT Command.
608 +
609 +
543 543  )))
544 544  
545 545  (((
546 546  (% style="color:blue" %)**AT+5VT=1000**
614 +
615 +
547 547  )))
548 548  
549 549  (((
... ... @@ -554,11 +554,12 @@
554 554  
555 555  == 2.5  Downlink Payload ==
556 556  
557 -By default, NSE01 prints the downlink payload to console port.
558 558  
559 -[[image:image-20220708133731-5.png]]
627 +By default, NDDS75 prints the downlink payload to console port.
560 560  
629 +[[image:image-20220709100028-1.png]]
561 561  
631 +
562 562  (((
563 563  (% style="color:blue" %)**Examples:**
564 564  )))
... ... @@ -592,7 +592,7 @@
592 592  )))
593 593  
594 594  (((
595 -If payload = 0x04FF, it will reset the NSE01
665 +If payload = 0x04FF, it will reset the NDDS75
596 596  )))
597 597  
598 598  
... ... @@ -604,78 +604,96 @@
604 604  
605 605  
606 606  
607 -== 2.6  ​LED Indicator ==
677 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
608 608  
609 -(((
610 -The NSE01 has an internal LED which is to show the status of different state.
611 611  
680 +(% style="color:blue" %)** ➢ AT Command:**
612 612  
613 -* 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)
614 -* Then the LED will be on for 1 second means device is boot normally.
615 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
616 -* For each uplink probe, LED will be on for 500ms.
617 -)))
682 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
618 618  
684 +² When min=0, and max≠0, Alarm higher than max
619 619  
686 +² When min≠0, and max=0, Alarm lower than min
620 620  
688 +² When min≠0 and max≠0, Alarm higher than max or lower than min
621 621  
622 -== 2.7  Installation in Soil ==
623 623  
624 -__**Measurement the soil surface**__
691 +(% style="color:blue" %)** Example:**
625 625  
626 -(((
627 -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]]
628 -)))
693 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
629 629  
630 -[[image:1657259653666-883.png]] ​
631 631  
632 632  
633 -(((
634 -
697 +== 2.7  Set the number of data to be uploaded and the recording time ==
635 635  
636 -(((
637 -Dig a hole with diameter > 20CM.
638 -)))
639 639  
640 -(((
641 -Horizontal insert the probe to the soil and fill the hole for long term measurement.
642 -)))
643 -)))
700 +(% style="color:blue" %)** ➢ AT Command:**
644 644  
645 -[[image:1654506665940-119.png]]
702 +* (% 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)
703 +* (% 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.
646 646  
705 +This link explains the relationship between TR, NOUD and TDC more clearly **: **[[https:~~/~~/www.processon.com/view/link/6340e606e401fd390891af87>>url:https://www.processon.com/view/link/6340e606e401fd390891af87]]
706 +
707 +== 2.8  Read or Clear cached data ==
708 +
709 +
710 +(% style="color:blue" %)** ➢ AT Command:**
711 +
712 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
713 +* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
714 +
715 +[[image:image-20220908175333-2.png]]
716 +
717 +
718 +
719 +== 2.9  ​LED Indicator ==
720 +
721 +
722 +The NDDS75 has an internal LED which is to show the status of different state.
723 +
724 +
725 +* 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)
726 +* Then the LED will be on for 1 second means device is boot normally.
727 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
728 +* For each uplink probe, LED will be on for 500ms.
729 +
647 647  (((
648 648  
649 649  )))
650 650  
651 651  
652 -== 2.8  ​Firmware Change Log ==
653 653  
736 +== 2.10  ​Firmware Change Log ==
654 654  
655 -Download URL & Firmware Change log
656 656  
657 -[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
739 +(((
740 +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]]
741 +)))
658 658  
743 +(((
744 +
745 +)))
659 659  
660 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
747 +(((
748 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
749 +)))
661 661  
662 662  
663 663  
664 -== 2.9  ​Battery Analysis ==
753 +== 2.11  ​Battery Analysis ==
665 665  
666 -=== 2.9.1  ​Battery Type ===
667 667  
756 +=== 2.11.1  ​Battery Type ===
668 668  
758 +
669 669  (((
670 -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.
760 +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.
671 671  )))
672 672  
673 -
674 674  (((
675 675  The battery is designed to last for several years depends on the actually use environment and update interval. 
676 676  )))
677 677  
678 -
679 679  (((
680 680  The battery related documents as below:
681 681  )))
... ... @@ -685,13 +685,14 @@
685 685  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
686 686  
687 687  (((
688 -[[image:image-20220708140453-6.png]]
776 +[[image:image-20220709101450-2.png]]
689 689  )))
690 690  
691 691  
692 692  
693 -=== 2.9.2  Power consumption Analyze ===
781 +=== 2.11.2  Power consumption Analyze ===
694 694  
783 +
695 695  (((
696 696  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.
697 697  )))
... ... @@ -724,12 +724,13 @@
724 724  And the Life expectation in difference case will be shown on the right.
725 725  )))
726 726  
727 -[[image:image-20220708141352-7.jpeg]]
816 +[[image:image-20220709110451-3.png]]
728 728  
729 729  
730 730  
731 -=== 2.9.3  ​Battery Note ===
820 +=== 2.11.3  ​Battery Note ===
732 732  
822 +
733 733  (((
734 734  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.
735 735  )))
... ... @@ -736,10 +736,11 @@
736 736  
737 737  
738 738  
739 -=== 2.9.4  Replace the battery ===
829 +=== 2.11.4  Replace the battery ===
740 740  
831 +
741 741  (((
742 -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).
833 +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).
743 743  )))
744 744  
745 745  
... ... @@ -746,6 +746,7 @@
746 746  
747 747  = 3. ​ Access NB-IoT Module =
748 748  
840 +
749 749  (((
750 750  Users can directly access the AT command set of the NB-IoT module.
751 751  )))
... ... @@ -752,92 +752,113 @@
752 752  
753 753  (((
754 754  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/]] 
847 +
848 +
755 755  )))
756 756  
757 -[[image:1657261278785-153.png]]
851 +[[image:1657333200519-600.png]]
758 758  
759 759  
760 760  
761 761  = 4.  Using the AT Commands =
762 762  
857 +
763 763  == 4.1  Access AT Commands ==
764 764  
765 -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/]]
766 766  
861 +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]]
767 767  
768 -AT+<CMD>?  : Help on <CMD>
769 769  
770 -AT+<CMD>         : Run <CMD>
864 +AT+<CMD>?  :  Help on <CMD>
771 771  
772 -AT+<CMD>=<value> : Set the value
866 +AT+<CMD>         :  Run <CMD>
773 773  
774 -AT+<CMD>= : Get the value
868 +AT+<CMD>=<value> :  Set the value
775 775  
870 +AT+<CMD>=?  :  Get the value
776 776  
872 +
777 777  (% style="color:#037691" %)**General Commands**(%%)      
778 778  
779 -AT  : Attention       
875 +AT  :  Attention       
780 780  
781 -AT?  : Short Help     
877 +AT?  :  Short Help     
782 782  
783 -ATZ  : MCU Reset    
879 +ATZ  :  MCU Reset    
784 784  
785 -AT+TDC  : Application Data Transmission Interval
881 +AT+TDC  :  Application Data Transmission Interval
786 786  
787 -AT+CFG  : Print all configurations
883 +AT+CFG  :  Print all configurations
788 788  
789 -AT+CFGMOD           : Working mode selection
885 +AT+CFGMOD           :  Working mode selection
790 790  
791 -AT+INTMOD            : Set the trigger interrupt mode
887 +AT+INTMOD            :  Set the trigger interrupt mode
792 792  
793 -AT+5VT  : Set extend the time of 5V power  
889 +AT+5VT  :  Set extend the time of 5V power  
794 794  
795 -AT+PRO  : Choose agreement
891 +AT+PRO  :  Choose agreement
796 796  
797 -AT+WEIGRE  : Get weight or set weight to 0
893 +AT+WEIGRE  :  Get weight or set weight to 0
798 798  
799 -AT+WEIGAP  : Get or Set the GapValue of weight
895 +AT+WEIGAP  :  Get or Set the GapValue of weight
800 800  
801 -AT+RXDL  : Extend the sending and receiving time
897 +AT+RXDL  :  Extend the sending and receiving time
802 802  
803 -AT+CNTFAC  : Get or set counting parameters
899 +AT+CNTFAC  :  Get or set counting parameters
804 804  
805 -AT+SERVADDR  : Server Address
901 +AT+SERVADDR  :  Server Address
806 806  
903 +AT+TR  :  Get or Set record time"
807 807  
905 +AT+APN     :  Get or set the APN
906 +
907 +AT+FBAND  :  Get or Set whether to automatically modify the frequency band
908 +
909 +AT+DNSCFG  : Get or Set DNS Server
910 +
911 +AT+GETSENSORVALUE   :  Returns the current sensor measurement
912 +
913 +AT+NOUD  :  Get or Set the number of data to be uploaded
914 +
915 +AT+CDP     :  Read or Clear cached data
916 +
917 +AT+LDDSALARM :  Get or Set alarm of distance
918 +
919 +
808 808  (% style="color:#037691" %)**COAP Management**      
809 809  
810 -AT+URI            : Resource parameters
922 +AT+URI            :  Resource parameters
811 811  
812 812  
813 813  (% style="color:#037691" %)**UDP Management**
814 814  
815 -AT+CFM          : Upload confirmation mode (only valid for UDP)
927 +AT+CFM          :  Upload confirmation mode (only valid for UDP)
816 816  
817 817  
818 818  (% style="color:#037691" %)**MQTT Management**
819 819  
820 -AT+CLIENT               : Get or Set MQTT client
932 +AT+CLIENT  :  Get or Set MQTT client
821 821  
822 -AT+UNAME  : Get or Set MQTT Username
934 +AT+UNAME  :  Get or Set MQTT Username
823 823  
824 -AT+PWD                  : Get or Set MQTT password
936 +AT+PWD  :  Get or Set MQTT password
825 825  
826 -AT+PUBTOPIC  : Get or Set MQTT publish topic
938 +AT+PUBTOPIC  :  Get or Set MQTT publish topic
827 827  
828 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
940 +AT+SUBTOPIC  :  Get or Set MQTT subscription topic
829 829  
830 830  
831 831  (% style="color:#037691" %)**Information**          
832 832  
833 -AT+FDR  : Factory Data Reset
945 +AT+FDR  :  Factory Data Reset
834 834  
835 -AT+PWORD  : Serial Access Password
947 +AT+PWORD  :  Serial Access Password
836 836  
837 837  
838 838  
839 839  = ​5.  FAQ =
840 840  
953 +
841 841  == 5.1 ​ How to Upgrade Firmware ==
842 842  
843 843  
... ... @@ -850,20 +850,14 @@
850 850  )))
851 851  
852 852  (((
853 -(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
966 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
854 854  )))
855 855  
856 856  
857 857  
858 -== 5.2  Can I calibrate NSE01 to different soil types? ==
859 -
860 -(((
861 -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]].
862 -)))
863 -
864 -
865 865  = 6.  Trouble Shooting =
866 866  
973 +
867 867  == 6.1  ​Connection problem when uploading firmware ==
868 868  
869 869  
... ... @@ -879,6 +879,7 @@
879 879  
880 880  == 6.2  AT Command input doesn't work ==
881 881  
989 +
882 882  (((
883 883  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.
884 884  
... ... @@ -889,7 +889,7 @@
889 889  = 7. ​ Order Info =
890 890  
891 891  
892 -Part Number**:** (% style="color:#4f81bd" %)**NSE01**
1000 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
893 893  
894 894  
895 895  (% class="wikigeneratedid" %)
... ... @@ -904,7 +904,7 @@
904 904  
905 905  (% style="color:#037691" %)**Package Includes**:
906 906  
907 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
1015 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
908 908  * External antenna x 1
909 909  )))
910 910  
... ... @@ -911,10 +911,13 @@
911 911  (((
912 912  
913 913  
1022 +
914 914  (% style="color:#037691" %)**Dimension and weight**:
915 915  
916 -* Size: 195 x 125 x 55 mm
917 -* Weight:   420g
1025 +* Device Size: 13.0 x 5 x 4.5 cm
1026 +* Device Weight: 150g
1027 +* Package Size / pcs : 15 x 12x 5.5 cm
1028 +* Weight / pcs : 220g
918 918  )))
919 919  
920 920  (((
... ... @@ -926,5 +926,6 @@
926 926  
927 927  = 9.  Support =
928 928  
1040 +
929 929  * 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.
930 930  * 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]]
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-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
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0