Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 115.14
edited by Xiaoling
on 2022/07/09 17:55
Change comment: There is no comment for this version
To version 90.2
edited by Xiaoling
on 2022/07/09 09:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -N95S31B NB-IoT Temperature & Humidity Sensor User Manual
1 +NDDS75 NB-IoT Distance Detect Sensor User Manual
Content
... ... @@ -1,61 +1,60 @@
1 1  (% style="text-align:center" %)
2 -[[image:1657348034241-728.png||height="470" width="470"]]
2 +[[image:image-20220709085040-1.png||height="542" width="524"]]
3 3  
4 4  
5 5  
6 6  
7 7  
8 -
9 -
10 10  **Table of Contents:**
11 11  
12 -{{toc/}}
13 13  
14 14  
15 15  
16 16  
17 17  
15 +
18 18  = 1.  Introduction =
19 19  
20 -== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
18 +== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
21 21  
22 22  (((
23 23  
24 24  
25 -The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*.
23 +(((
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 +)))
26 26  
27 -The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use.
28 -
29 -N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
30 -
31 -N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report).
32 -
33 -
34 -~* make sure you have NB-IoT coverage locally.
35 -
36 36  
37 37  )))
38 38  
39 -[[image:1657348284168-431.png]]
35 +[[image:1654503236291-817.png]]
40 40  
41 41  
38 +[[image:1657327959271-447.png]]
42 42  
40 +
41 +
43 43  == 1.2 ​ Features ==
44 44  
44 +
45 45  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
46 -* Monitor Temperature & Humidity via SHT31
46 +* Ultra low power consumption
47 +* Distance Detection by Ultrasonic technology
48 +* Flat object range 280mm - 7500mm
49 +* Accuracy: ±(1cm+S*0.3%) (S: Distance)
50 +* Cable Length: 25cm
47 47  * AT Commands to change parameters
48 48  * Uplink on periodically
49 49  * Downlink to change configure
50 50  * IP66 Waterproof Enclosure
51 -* Ultra-Low Power consumption
52 -* AT Commands to change parameters
53 53  * Micro SIM card slot for NB-IoT SIM
54 54  * 8500mAh Battery for long term use
55 55  
56 -
57 -
58 -
59 59  == 1.3  Specification ==
60 60  
61 61  
... ... @@ -75,7 +75,6 @@
75 75  
76 76  (% style="color:#037691" %)**Battery:**
77 77  
78 -
79 79  * Li/SOCI2 un-chargeable battery
80 80  * Capacity: 8500mAh
81 81  * Self Discharge: <1% / Year @ 25°C
... ... @@ -82,7 +82,10 @@
82 82  * Max continuously current: 130mA
83 83  * Max boost current: 2A, 1 second
84 84  
83 +(% style="color:#037691" %)**Power Consumption**
85 85  
85 +* STOP Mode: 10uA @ 3.3v
86 +* Max transmit power: 350mA@3.3v
86 86  
87 87  
88 88  == ​1.4  Applications ==
... ... @@ -98,53 +98,25 @@
98 98  ​
99 99  
100 100  
102 +
101 101  == 1.5  Pin Definitions ==
102 102  
103 -N95S31B use the mother board from NBSN95 which as below.
104 104  
105 -[[image:image-20220709144723-1.png]]
106 +[[image:1657328609906-564.png]]
106 106  
107 107  
108 -=== 1.5.1 Jumper JP2 ===
109 109  
110 -Power on Device when put this jumper.
110 += 2.  Use NDDS75 to communicate with IoT Server =
111 111  
112 -
113 -
114 -=== 1.5.2 BOOT MODE / SW1 ===
115 -
116 -1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
117 -
118 -2) Flash: work mode, device starts to work and send out console output for further debug
119 -
120 -
121 -
122 -=== 1.5.3 Reset Button ===
123 -
124 -Press to reboot the device.
125 -
126 -
127 -
128 -=== 1.5.4 LED ===
129 -
130 -It will flash:
131 -
132 -1. When boot the device in flash mode
133 -1. Send an uplink packet
134 -
135 -
136 -= 2.  Use N95S31B to communicate with IoT Server =
137 -
138 138  == 2.1  How it works ==
139 139  
140 -
141 141  (((
142 -The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B 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 N95S31B.
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.
143 143  )))
144 144  
145 145  
146 146  (((
147 -The diagram below shows the working flow in default firmware of N95S31B:
120 +The diagram below shows the working flow in default firmware of NDDS75:
148 148  )))
149 149  
150 150  (((
... ... @@ -151,7 +151,7 @@
151 151  
152 152  )))
153 153  
154 -[[image:1657350248151-650.png]]
127 +[[image:1657328659945-416.png]]
155 155  
156 156  (((
157 157  
... ... @@ -158,45 +158,30 @@
158 158  )))
159 159  
160 160  
161 -== 2.2 ​ Configure the N95S31B ==
134 +== 2.2 ​ Configure the NDDS75 ==
162 162  
163 163  
164 -=== 2.2.1  Power On N95S31B ===
165 -
166 -
167 -[[image:image-20220709150546-2.png]]
168 -
169 -
170 170  === 2.2.1 Test Requirement ===
171 171  
139 +(((
140 +To use NDDS75 in your city, make sure meet below requirements:
141 +)))
172 172  
173 -To use N95S31B in your city, make sure meet below requirements:
174 -
175 175  * Your local operator has already distributed a NB-IoT Network there.
176 -* The local NB-IoT network used the band that N95S31B supports.
144 +* The local NB-IoT network used the band that NSE01 supports.
177 177  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
178 178  
179 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
180 -
181 -N95S31B supports different communication protocol such as :
182 -
183 183  (((
184 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
185 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
186 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
187 -* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
188 -
189 -We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server.
190 -
191 -
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
192 192  )))
193 193  
194 -[[image:1657350625843-586.png]]
195 195  
152 +[[image:1657328756309-230.png]]
196 196  
197 197  
198 -=== 2.2.3  Insert SIM card ===
199 199  
156 +=== 2.2.2 Insert SIM card ===
157 +
200 200  (((
201 201  Insert the NB-IoT Card get from your provider.
202 202  )))
... ... @@ -206,19 +206,19 @@
206 206  )))
207 207  
208 208  
209 -[[image:1657351240556-536.png]]
167 +[[image:1657328884227-504.png]]
210 210  
211 211  
212 212  
213 -=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
171 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
214 214  
215 215  (((
216 216  (((
217 -User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below.
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.
218 218  )))
219 219  )))
220 220  
221 -[[image:1657351312545-300.png]]
179 +[[image:image-20220709092052-2.png]]
222 222  
223 223  **Connection:**
224 224  
... ... @@ -238,110 +238,90 @@
238 238  * Flow Control: (% style="color:green" %)**None**
239 239  
240 240  (((
241 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
199 +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.
242 242  )))
243 243  
244 244  [[image:1657329814315-101.png]]
245 245  
246 246  (((
247 -(% style="color:red" %)Note: the valid AT Commands can be found at:  (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]
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/]]
248 248  )))
249 249  
250 250  
251 251  
252 -=== 2.2.5  Use CoAP protocol to uplink data ===
210 +=== 2.2.4 Use CoAP protocol to uplink data ===
253 253  
254 254  (% 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/]]
255 255  
256 256  
257 -(((
258 258  **Use below commands:**
259 -)))
260 260  
261 -* (((
262 -(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
263 -)))
264 -* (((
265 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
266 -)))
267 -* (((
268 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
269 -)))
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
270 270  
271 -(((
272 -
273 -
274 274  For parameter description, please refer to AT command set
275 -)))
276 276  
277 -[[image:1657352146020-183.png]]
223 +[[image:1657330452568-615.png]]
278 278  
279 279  
280 -(((
281 281  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.
282 -)))
283 283  
284 -[[image:1657352185396-303.png]]
228 +[[image:1657330472797-498.png]]
285 285  
286 286  
287 287  
288 -=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
232 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
289 289  
290 290  
291 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
235 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
292 292  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
293 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
237 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
294 294  
295 -[[image:1657352391268-297.png]]
239 +[[image:1657330501006-241.png]]
296 296  
297 297  
298 -[[image:1657352403317-397.png]]
242 +[[image:1657330533775-472.png]]
299 299  
300 300  
301 301  
302 -=== 2.2.7  Use MQTT protocol to uplink data ===
246 +=== 2.2.6 Use MQTT protocol to uplink data ===
303 303  
304 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
305 305  
306 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
307 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
308 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
309 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
310 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
311 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
312 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
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
313 313  
314 -[[image:1657352634421-276.png]]
257 +[[image:1657249978444-674.png]]
315 315  
316 316  
317 -[[image:1657352645687-385.png]]
260 +[[image:1657330723006-866.png]]
318 318  
319 -(((
320 -To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period.
321 -)))
322 322  
323 -
324 324  (((
325 -MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
264 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
326 326  )))
327 327  
328 328  
329 329  
330 -=== 2.2.8  Use TCP protocol to uplink data ===
269 +=== 2.2.7 Use TCP protocol to uplink data ===
331 331  
332 -This feature is supported since firmware version v110
333 333  
334 334  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
335 335  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
336 336  
337 -[[image:1657352898400-901.png]]
275 +[[image:image-20220709093918-1.png]]
338 338  
339 339  
340 -[[image:1657352914475-252.png]]
278 +[[image:image-20220709093918-2.png]]
341 341  
342 342  
343 343  
344 -=== 2.2.9  Change Update Interval ===
282 +=== 2.2.8 Change Update Interval ===
345 345  
346 346  User can use below command to change the (% style="color:green" %)**uplink interval**.
347 347  
... ... @@ -348,201 +348,279 @@
348 348  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
349 349  
350 350  (((
351 -
289 +(% style="color:red" %)**NOTE:**
352 352  )))
353 353  
292 +(((
293 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
294 +)))
354 354  
355 355  
297 +
356 356  == 2.3  Uplink Payload ==
357 357  
300 +In this mode, uplink payload includes in total 14 bytes
358 358  
359 -NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
360 360  
303 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
304 +|=(% style="width: 60px;" %)(((
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"]]
361 361  
362 -For example:
309 +(((
310 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
311 +)))
363 363  
364 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
365 365  
314 +[[image:1657331036973-987.png]]
366 366  
367 -The uplink payloads are composed in  ASCII String. For example:
316 +(((
317 +The payload is ASCII string, representative same HEX:
318 +)))
368 368  
369 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
320 +(((
321 +0x72403155615900640c6c19029200 where:
322 +)))
370 370  
371 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
324 +* (((
325 +Device ID: 0x724031556159 = 724031556159
326 +)))
327 +* (((
328 +Version: 0x0064=100=1.0.0
329 +)))
372 372  
331 +* (((
332 +BAT: 0x0c6c = 3180 mV = 3.180V
333 +)))
334 +* (((
335 +Signal: 0x19 = 25
336 +)))
337 +* (((
338 +Distance: 0x0292= 658 mm
339 +)))
340 +* (((
341 +Interrupt: 0x00 = 0
342 +)))
373 373  
374 -(% style="color:red" %)**NOTE:**
375 375  
376 -(% style="color:red" %)
377 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
378 -1. By default, the device will send an uplink message every 1 hour.
379 379  
380 380  
347 +== 2.4  Payload Explanation and Sensor Interface ==
381 381  
382 -=== 2.3.1  Payload Analyze ===
383 383  
384 -N95S31B uplink payload includes in total 21 bytes
350 +=== 2.4.1  Device ID ===
385 385  
352 +(((
353 +By default, the Device ID equal to the last 6 bytes of IMEI.
354 +)))
386 386  
387 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
388 -|=(% style="width: 60px;" %)(((
389 -**Size(bytes)**
390 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1**
391 -|(% 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:123px" %)MOD 0X01|(% style="width:99px" %)(((
392 -Reserve/ Same as NBSN95 CFGMOD=1
356 +(((
357 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
358 +)))
393 393  
394 -No function here.
395 -)))|(% style="width:77px" %)(((
396 -[[Temperature >>||anchor="H2.4.5A0Distance"]]
360 +(((
361 +**Example:**
362 +)))
397 397  
398 -By SHT31
399 -)))|(% style="width:80px" %)(((
400 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
401 -
402 -By SHT31
364 +(((
365 +AT+DEUI=A84041F15612
403 403  )))
404 404  
405 405  (((
406 -(((
407 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
369 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
408 408  )))
409 -)))
410 410  
411 411  
412 -[[image:1657354294009-643.png]]
413 413  
374 +=== 2.4.2  Version Info ===
414 414  
415 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
376 +(((
377 +Specify the software version: 0x64=100, means firmware version 1.00.
378 +)))
416 416  
417 -* Device ID: 0x724031607457 = 724031607457
418 -* Version: 0x006e=110=1.1.0
380 +(((
381 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
382 +)))
419 419  
420 -* BAT: 0x0ccd = 3277 mV = 3.277V
421 -* Signal: 0x1b = 27
422 -* Model: 0x01 = 1
423 -* 0x00dc000ccc= reserve, ignore in N95S31B
424 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
425 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
426 426  
385 +
386 +=== 2.4.3  Battery Info ===
387 +
427 427  (((
428 -
389 +Check the battery voltage for LSE01.
429 429  )))
430 430  
431 431  (((
432 -
393 +Ex1: 0x0B45 = 2885mV
433 433  )))
434 434  
396 +(((
397 +Ex2: 0x0B49 = 2889mV
398 +)))
435 435  
436 -=== 2.3.2  Device ID ===
437 437  
401 +
402 +=== 2.4.4  Signal Strength ===
403 +
438 438  (((
439 -By default, the Device ID equal to the last 6 bytes of IMEI.
405 +NB-IoT Network signal Strength.
440 440  )))
441 441  
442 442  (((
443 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
409 +**Ex1: 0x1d = 29**
444 444  )))
445 445  
446 446  (((
447 -**Example:**
413 +(% style="color:blue" %)**0**(%%)  -113dBm or less
448 448  )))
449 449  
450 450  (((
451 -AT+DEUI=A84041F15612
417 +(% style="color:blue" %)**1**(%%)  -111dBm
452 452  )))
453 453  
454 454  (((
455 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
421 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
456 456  )))
457 457  
424 +(((
425 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
426 +)))
458 458  
428 +(((
429 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
430 +)))
459 459  
460 -=== 2.3.3  Version Info ===
461 461  
462 462  
463 -These bytes include the hardware and software version.
434 +=== 2.4.5  Soil Moisture ===
464 464  
465 -Higher byte: Specify hardware version: always 0x00 for N95S31B
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 +)))
466 466  
467 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
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 +)))
468 468  
469 -
470 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
471 -
472 472  (((
473 473  
474 474  )))
475 475  
452 +(((
453 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
454 +)))
476 476  
477 -=== 2.3.4  Battery Info ===
478 478  
457 +
458 +=== 2.4.6  Soil Temperature ===
459 +
479 479  (((
480 -Ex1: 0x0B45 = 2885mV
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
481 481  )))
482 482  
483 483  (((
484 -Ex2: 0x0B49 = 2889mV
465 +**Example**:
485 485  )))
486 486  
468 +(((
469 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
470 +)))
487 487  
472 +(((
473 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
474 +)))
488 488  
489 -=== 2.3.5  Signal Strength ===
490 490  
477 +
478 +=== 2.4.7  Soil Conductivity (EC) ===
479 +
491 491  (((
492 -NB-IoT Network signal Strength.
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).
493 493  )))
494 494  
495 495  (((
496 -**Ex1: 0x1d = 29**
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.
497 497  )))
498 498  
499 499  (((
500 -(% style="color:blue" %)**0**(%%)  -113dBm or less
489 +Generally, the EC value of irrigation water is less than 800uS / cm.
501 501  )))
502 502  
503 503  (((
504 -(% style="color:blue" %)**1**(%%)  -111dBm
493 +
505 505  )))
506 506  
507 507  (((
508 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
497 +
509 509  )))
510 510  
500 +=== 2.4.8  Digital Interrupt ===
501 +
511 511  (((
512 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
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.
513 513  )))
514 514  
515 515  (((
516 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
507 +The command is:
517 517  )))
518 518  
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]])**.**
512 +)))
519 519  
520 520  
521 -=== 2.3.6  Temperature & Humidity ===
515 +(((
516 +The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
517 +)))
522 522  
523 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
524 524  
525 -[[image:image-20220709161741-3.png]]
520 +(((
521 +Example:
522 +)))
526 526  
524 +(((
525 +0x(00): Normal uplink packet.
526 +)))
527 527  
528 -Convert the read byte to decimal and divide it by ten.
528 +(((
529 +0x(01): Interrupt Uplink Packet.
530 +)))
529 529  
530 530  
531 -**Example:**
532 532  
533 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
534 +=== 2.4.9  ​+5V Output ===
534 534  
535 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
536 +(((
537 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
538 +)))
536 536  
537 537  
541 +(((
542 +The 5V output time can be controlled by AT Command.
543 +)))
538 538  
539 -== 2.4  Downlink Payload ==
545 +(((
546 +(% style="color:blue" %)**AT+5VT=1000**
547 +)))
540 540  
541 -By default, NDDS75 prints the downlink payload to console port.
549 +(((
550 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
551 +)))
542 542  
543 -[[image:image-20220709100028-1.png]]
544 544  
545 545  
555 +== 2.5  Downlink Payload ==
556 +
557 +By default, NSE01 prints the downlink payload to console port.
558 +
559 +[[image:image-20220708133731-5.png]]
560 +
561 +
546 546  (((
547 547  (% style="color:blue" %)**Examples:**
548 548  )))
... ... @@ -576,7 +576,7 @@
576 576  )))
577 577  
578 578  (((
579 -If payload = 0x04FF, it will reset the NDDS75
595 +If payload = 0x04FF, it will reset the NSE01
580 580  )))
581 581  
582 582  
... ... @@ -588,19 +588,78 @@
588 588  
589 589  
590 590  
591 -== 2.5  ​Battery Analysis ==
607 +== 2.6  ​LED Indicator ==
592 592  
593 -=== 2.5.1  ​Battery Type ===
609 +(((
610 +The NSE01 has an internal LED which is to show the status of different state.
594 594  
595 595  
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 +)))
618 +
619 +
620 +
621 +
622 +== 2.7  Installation in Soil ==
623 +
624 +__**Measurement the soil surface**__
625 +
596 596  (((
597 -The N95S31B 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.
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]]
598 598  )))
599 599  
630 +[[image:1657259653666-883.png]] ​
631 +
632 +
600 600  (((
634 +
635 +
636 +(((
637 +Dig a hole with diameter > 20CM.
638 +)))
639 +
640 +(((
641 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
642 +)))
643 +)))
644 +
645 +[[image:1654506665940-119.png]]
646 +
647 +(((
648 +
649 +)))
650 +
651 +
652 +== 2.8  ​Firmware Change Log ==
653 +
654 +
655 +Download URL & Firmware Change log
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/]]
658 +
659 +
660 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
661 +
662 +
663 +
664 +== 2.9  ​Battery Analysis ==
665 +
666 +=== 2.9.1  ​Battery Type ===
667 +
668 +
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.
671 +)))
672 +
673 +
674 +(((
601 601  The battery is designed to last for several years depends on the actually use environment and update interval. 
602 602  )))
603 603  
678 +
604 604  (((
605 605  The battery related documents as below:
606 606  )))
... ... @@ -610,40 +610,61 @@
610 610  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
611 611  
612 612  (((
613 -[[image:image-20220709101450-2.png]]
688 +[[image:image-20220708140453-6.png]]
614 614  )))
615 615  
616 616  
617 617  
618 -=== 2.5.2  Power consumption Analyze ===
693 +=== 2.9.2  Power consumption Analyze ===
619 619  
620 620  (((
621 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
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.
622 622  )))
623 623  
699 +
624 624  (((
625 -
701 +Instruction to use as below:
626 626  )))
627 627  
704 +(((
705 +(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
706 +)))
628 628  
629 -=== 2.5.3  ​Battery Note ===
630 630  
631 631  (((
632 -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 uplink data, then the battery life may be decreased.
710 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
633 633  )))
634 634  
713 +* (((
714 +Product Model
715 +)))
716 +* (((
717 +Uplink Interval
718 +)))
719 +* (((
720 +Working Mode
721 +)))
635 635  
723 +(((
724 +And the Life expectation in difference case will be shown on the right.
725 +)))
636 636  
637 -=== 2.5.4  Replace the battery ===
727 +[[image:image-20220708141352-7.jpeg]]
638 638  
639 639  
730 +
731 +=== 2.9.3  ​Battery Note ===
732 +
640 640  (((
641 -You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
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.
642 642  )))
643 643  
644 644  
738 +
739 +=== 2.9.4  Replace the battery ===
740 +
645 645  (((
646 -The default battery pack of N95S31B 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).
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).
647 647  )))
648 648  
649 649  
... ... @@ -658,7 +658,7 @@
658 658  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/]] 
659 659  )))
660 660  
661 -[[image:1657333200519-600.png]]
757 +[[image:1657261278785-153.png]]
662 662  
663 663  
664 664  
... ... @@ -666,7 +666,7 @@
666 666  
667 667  == 4.1  Access AT Commands ==
668 668  
669 -See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]
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/]]
670 670  
671 671  
672 672  AT+<CMD>?  : Help on <CMD>
... ... @@ -754,13 +754,18 @@
754 754  )))
755 755  
756 756  (((
757 -
758 -
759 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
853 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
760 760  )))
761 761  
762 762  
763 763  
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 +
764 764  = 6.  Trouble Shooting =
765 765  
766 766  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -788,7 +788,7 @@
788 788  = 7. ​ Order Info =
789 789  
790 790  
791 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
892 +Part Number**:** (% style="color:#4f81bd" %)**NSE01**
792 792  
793 793  
794 794  (% class="wikigeneratedid" %)
... ... @@ -803,7 +803,7 @@
803 803  
804 804  (% style="color:#037691" %)**Package Includes**:
805 805  
806 -* N95S31B NB-IoT Temperature and Humidity Sensor
907 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
807 807  * External antenna x 1
808 808  )))
809 809  
... ... @@ -812,10 +812,8 @@
812 812  
813 813  (% style="color:#037691" %)**Dimension and weight**:
814 814  
815 -* Device Size: 13.0 x 5 x 4.5 cm
816 -* Device Weight: 150g
817 -* Package Size / pcs : 14.0 x 8x 5 cm
818 -* Weight / pcs : 180g
916 +* Size: 195 x 125 x 55 mm
917 +* Weight:   420g
819 819  )))
820 820  
821 821  (((
1657332990863-496.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.2 KB
Content
1657333200519-600.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
1657348034241-728.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -127.8 KB
Content
1657348284168-431.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -93.5 KB
Content
1657350248151-650.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
1657350625843-586.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -93.3 KB
Content
1657351240556-536.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -483.6 KB
Content
1657351312545-300.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -675.8 KB
Content
1657352146020-183.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -264.0 KB
Content
1657352185396-303.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.3 KB
Content
1657352391268-297.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -238.0 KB
Content
1657352403317-397.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -547.7 KB
Content
1657352634421-276.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -163.6 KB
Content
1657352645687-385.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -214.7 KB
Content
1657352898400-901.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -144.8 KB
Content
1657352914475-252.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -157.0 KB
Content
1657354294009-643.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -214.7 KB
Content
image-20220709100028-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.8 KB
Content
image-20220709101450-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.5 KB
Content
image-20220709110451-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -611.5 KB
Content
image-20220709144723-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -413.1 KB
Content
image-20220709150546-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -333.5 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -111.2 KB
Content