Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 118.3
edited by Xiaoling
on 2022/07/12 17:19
Change comment: There is no comment for this version
To version 65.19
edited by Xiaoling
on 2022/07/08 15:55
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 +NSE01 - NB-IoT Soil Moisture & EC Sensor User Manual
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:1657348034241-728.png||height="470" width="470"]]
2 +[[image:image-20220606151504-2.jpeg||height="554" width="554"]]
3 3  
4 4  
5 5  
... ... @@ -7,6 +7,10 @@
7 7  
8 8  
9 9  
10 +
11 +
12 +
13 +
10 10  **Table of Contents:**
11 11  
12 12  {{toc/}}
... ... @@ -15,41 +15,38 @@
15 15  
16 16  
17 17  
22 +
23 +
18 18  = 1.  Introduction =
19 19  
20 -== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
26 +== 1.1 ​ What is LoRaWAN Soil Moisture & EC Sensor ==
21 21  
22 22  (((
23 23  
24 24  
25 25  (((
26 -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*.
32 +Dragino NSE01 is an (% style="color:blue" %)**NB-IOT soil moisture & EC sensor**(%%) for agricultural IoT. Used to measure the soil moisture of saline-alkali soil and loam. The soil sensor uses the FDR method to calculate soil moisture and compensates it with soil temperature and electrical conductivity. It has also been calibrated for mineral soil types at the factory.
27 27  )))
28 28  
29 29  (((
30 -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.
36 +It can detect (% style="color:blue" %)**Soil Moisture, Soil Temperature and Soil Conductivity**(%%), and upload its value to the server wirelessly.
31 31  )))
32 32  
33 33  (((
34 -N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
40 +The wireless technology used in NSE01 allows the device to send data at a low data rate and reach ultra-long distances, providing ultra-long-distance spread spectrum Communication.
35 35  )))
36 36  
37 37  (((
38 -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).
44 +NSE01 are powered by (% style="color:blue" %)**8500mAh Li-SOCI2**(%%) batteries, which can be used for up to 5 years.  
39 39  )))
40 40  
41 -(((
42 42  
43 43  )))
44 44  
45 -(((
46 -~* make sure you have NB-IoT coverage locally.
47 -)))
50 +[[image:1654503236291-817.png]]
48 48  
49 -
50 -)))
51 51  
52 -[[image:1657348284168-431.png]]
53 +[[image:1657245163077-232.png]]
53 53  
54 54  
55 55  
... ... @@ -56,7 +56,9 @@
56 56  == 1.2 ​ Features ==
57 57  
58 58  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
59 -* Monitor Temperature & Humidity via SHT31
60 +* Monitor Soil Moisture
61 +* Monitor Soil Temperature
62 +* Monitor Soil Conductivity
60 60  * AT Commands to change parameters
61 61  * Uplink on periodically
62 62  * Downlink to change configure
... ... @@ -66,8 +66,6 @@
66 66  * Micro SIM card slot for NB-IoT SIM
67 67  * 8500mAh Battery for long term use
68 68  
69 -
70 -
71 71  == 1.3  Specification ==
72 72  
73 73  
... ... @@ -85,154 +85,75 @@
85 85  * - B20 @H-FDD: 800MHz
86 86  * - B28 @H-FDD: 700MHz
87 87  
88 -(% style="color:#037691" %)**Battery:**
89 +Probe(% style="color:#037691" %)** Specification:**
89 89  
90 -* Li/SOCI2 un-chargeable battery
91 -* Capacity: 8500mAh
92 -* Self Discharge: <1% / Year @ 25°C
93 -* Max continuously current: 130mA
94 -* Max boost current: 2A, 1 second
91 +Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
95 95  
93 +[[image:image-20220708101224-1.png]]
96 96  
97 97  
96 +
98 98  == ​1.4  Applications ==
99 99  
100 -* Smart Buildings & Home Automation
101 -* Logistics and Supply Chain Management
102 -* Smart Metering
103 103  * Smart Agriculture
104 -* Smart Cities
105 -* Smart Factory
106 106  
107 107  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
108 108  ​
109 109  
104 +== 1.5  Pin Definitions ==
110 110  
111 -== 1.5  Pin Definitions & Switch ==
112 112  
113 -N95S31B use the mother board from NBSN95 which as below.
107 +[[image:1657246476176-652.png]]
114 114  
115 -[[image:image-20220709144723-1.png]]
116 116  
117 117  
118 -=== 1.5.1 Jumper JP2 ===
111 += 2.  Use NSE01 to communicate with IoT Server =
119 119  
120 -Power on Device when put this jumper.
121 -
122 -
123 -
124 -=== 1.5.2 BOOT MODE / SW1 ===
125 -
126 -(((
127 -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.
128 -)))
129 -
130 -(((
131 -2) Flash: work mode, device starts to work and send out console output for further debug
132 -)))
133 -
134 -
135 -
136 -=== 1.5.3 Reset Button ===
137 -
138 -Press to reboot the device.
139 -
140 -
141 -
142 -=== 1.5.4 LED ===
143 -
144 -It will flash:
145 -
146 -1. When boot the device in flash mode
147 -1. Send an uplink packet
148 -
149 -
150 -= 2.  Use N95S31B to communicate with IoT Server =
151 -
152 152  == 2.1  How it works ==
153 153  
154 154  
155 155  (((
156 -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.
117 +The NSE01 is equipped with a NB-IoT module, the pre-loaded firmware in NSE01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NSE01.
157 157  )))
158 158  
159 159  
160 160  (((
161 -The diagram below shows the working flow in default firmware of N95S31B:
122 +The diagram below shows the working flow in default firmware of NSE01:
162 162  )))
163 163  
164 -(((
165 -
166 -)))
125 +[[image:image-20220708101605-2.png]]
167 167  
168 -[[image:1657520100595-569.png]]
169 -
170 170  (((
171 171  
172 172  )))
173 173  
174 174  
175 -== 2.2 ​ Configure the N95S31B ==
176 176  
133 +== 2.2 ​ Configure the NSE01 ==
177 177  
178 -=== 2.2.1  Power On N95S31B ===
179 179  
180 -
181 -[[image:image-20220709150546-2.png]]
182 -
183 -
184 184  === 2.2.1 Test Requirement ===
185 185  
186 186  
187 187  (((
188 -To use N95S31B in your city, make sure meet below requirements:
140 +To use NSE01 in your city, make sure meet below requirements:
189 189  )))
190 190  
191 -* (((
192 -Your local operator has already distributed a NB-IoT Network there.
193 -)))
194 -* (((
195 -The local NB-IoT network used the band that N95S31B supports.
196 -)))
197 -* (((
198 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
199 -)))
143 +* Your local operator has already distributed a NB-IoT Network there.
144 +* The local NB-IoT network used the band that NSE01 supports.
145 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
200 200  
201 201  (((
202 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
148 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NSE01 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
203 203  )))
204 204  
205 -(((
206 -N95S31B supports different communication protocol such as :
207 -)))
208 208  
209 -(((
210 -* (((
211 -CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
212 -)))
213 -* (((
214 -raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
215 -)))
216 -* (((
217 -MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
218 -)))
219 -* (((
220 -TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
221 -)))
152 +[[image:1657249419225-449.png]]
222 222  
223 -(((
224 -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.
225 -)))
226 226  
227 -
228 -)))
229 229  
230 -[[image:1657350625843-586.png]]
156 +=== 2.2.2 Insert SIM card ===
231 231  
232 -
233 -
234 -=== 2.2.3  Insert SIM card ===
235 -
236 236  (((
237 237  Insert the NB-IoT Card get from your provider.
238 238  )))
... ... @@ -242,19 +242,18 @@
242 242  )))
243 243  
244 244  
245 -[[image:1657351240556-536.png]]
167 +[[image:1657249468462-536.png]]
246 246  
247 247  
248 248  
249 -=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
171 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
250 250  
251 251  (((
252 252  (((
253 -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 NSE01 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01 support AT Commands, user can use a USB to TTL adapter to connect to NSE01 and use AT Commands to configure it, as below.
254 254  )))
255 255  )))
256 256  
257 -[[image:1657351312545-300.png]]
258 258  
259 259  **Connection:**
260 260  
... ... @@ -274,110 +274,96 @@
274 274  * Flow Control: (% style="color:green" %)**None**
275 275  
276 276  (((
277 -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.
198 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSE01. NSE01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
278 278  )))
279 279  
280 -[[image:1657329814315-101.png]]
201 +[[image:image-20220708110657-3.png]]
281 281  
282 282  (((
283 -(% 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/]]
204 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
284 284  )))
285 285  
286 286  
287 287  
288 -=== 2.2.5  Use CoAP protocol to uplink data ===
209 +=== 2.2.4 Use CoAP protocol to uplink data ===
289 289  
290 290  (% 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/]]
291 291  
292 292  
293 -(((
294 294  **Use below commands:**
295 -)))
296 296  
297 -* (((
298 -(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
299 -)))
300 -* (((
301 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
302 -)))
303 -* (((
304 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
305 -)))
216 +* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
217 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
218 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
306 306  
307 -(((
308 -
309 -
310 310  For parameter description, please refer to AT command set
311 -)))
312 312  
313 -[[image:1657352146020-183.png]]
222 +[[image:1657249793983-486.png]]
314 314  
315 315  
316 -(((
317 -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.
318 -)))
225 +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.
319 319  
320 -[[image:1657352185396-303.png]]
227 +[[image:1657249831934-534.png]]
321 321  
322 322  
323 323  
324 -=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
231 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
325 325  
233 +This feature is supported since firmware version v1.0.1
326 326  
327 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
235 +
236 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
328 328  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
329 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
238 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
330 330  
331 -[[image:1657352391268-297.png]]
240 +[[image:1657249864775-321.png]]
332 332  
333 333  
334 -[[image:1657352403317-397.png]]
243 +[[image:1657249930215-289.png]]
335 335  
336 336  
337 337  
338 -=== 2.2.7  Use MQTT protocol to uplink data ===
247 +=== 2.2.6 Use MQTT protocol to uplink data ===
339 339  
340 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
249 +This feature is supported since firmware version v110
341 341  
342 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
343 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
344 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
345 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
346 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
347 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
348 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
349 349  
350 -[[image:1657352634421-276.png]]
252 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
253 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
254 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
255 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
256 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
257 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
258 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
351 351  
260 +[[image:1657249978444-674.png]]
352 352  
353 -[[image:1657352645687-385.png]]
354 354  
355 -(((
356 -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.
357 -)))
263 +[[image:1657249990869-686.png]]
358 358  
359 359  
360 360  (((
361 -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.
267 +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.
362 362  )))
363 363  
364 364  
365 365  
366 -=== 2.2.8  Use TCP protocol to uplink data ===
272 +=== 2.2.7 Use TCP protocol to uplink data ===
367 367  
368 368  This feature is supported since firmware version v110
369 369  
276 +
370 370  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
371 371  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
372 372  
373 -[[image:1657352898400-901.png]]
280 +[[image:1657250217799-140.png]]
374 374  
375 375  
376 -[[image:1657352914475-252.png]]
283 +[[image:1657250255956-604.png]]
377 377  
378 378  
379 379  
380 -=== 2.2.9  Change Update Interval ===
287 +=== 2.2.8 Change Update Interval ===
381 381  
382 382  User can use below command to change the (% style="color:green" %)**uplink interval**.
383 383  
... ... @@ -384,155 +384,193 @@
384 384  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
385 385  
386 386  (((
387 -
294 +(% style="color:red" %)**NOTE:**
388 388  )))
389 389  
297 +(((
298 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
299 +)))
390 390  
391 391  
302 +
392 392  == 2.3  Uplink Payload ==
393 393  
305 +In this mode, uplink payload includes in total 18 bytes
394 394  
307 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
308 +|=(% style="width: 60px;" %)(((
309 +**Size(bytes)**
310 +)))|=(% 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**
311 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:108px" %)[[Soil Moisture>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H2.4.6A0SoilTemperature"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H2.4.7A0SoilConductivity28EC29"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]
312 +
395 395  (((
396 -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.
314 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
397 397  )))
398 398  
399 399  
318 +[[image:image-20220708111918-4.png]]
319 +
320 +
321 +The payload is ASCII string, representative same HEX:
322 +
323 +0x72403155615900640c7817075e0a8c02f900 where:
324 +
325 +* Device ID: 0x 724031556159 = 724031556159
326 +* Version: 0x0064=100=1.0.0
327 +
328 +* BAT: 0x0c78 = 3192 mV = 3.192V
329 +* Singal: 0x17 = 23
330 +* Soil Moisture: 0x075e= 1886 = 18.86  %
331 +* Soil Temperature:0x0a8c =2700=27 °C
332 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
333 +* Interrupt: 0x00 = 0
334 +
335 +
336 +
337 +
338 +== 2.4  Payload Explanation and Sensor Interface ==
339 +
340 +
341 +=== 2.4.1  Device ID ===
342 +
400 400  (((
401 -For example:
344 +By default, the Device ID equal to the last 6 bytes of IMEI.
402 402  )))
403 403  
404 404  (((
405 - (% 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.
348 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
406 406  )))
407 407  
408 -
409 409  (((
410 -The uplink payloads are composed in  ASCII String. For example:
352 +**Example:**
411 411  )))
412 412  
413 413  (((
414 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
356 +AT+DEUI=A84041F15612
415 415  )))
416 416  
417 417  (((
418 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
360 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
419 419  )))
420 420  
421 421  
364 +
365 +=== 2.4.2  Version Info ===
366 +
422 422  (((
423 -(% style="color:red" %)**NOTE:**
368 +Specify the software version: 0x64=100, means firmware version 1.00.
424 424  )))
425 425  
426 -(% style="color:red" %)
427 -1. (((
428 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
371 +(((
372 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
429 429  )))
430 -1. (((
431 -By default, the device will send an uplink message every 1 hour.
432 -)))
433 433  
434 -=== 2.3.1  Payload Analyze ===
435 435  
436 -N95S31B uplink payload includes in total 21 bytes
437 437  
377 +=== 2.4.3  Battery Info ===
438 438  
439 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
440 -|=(% style="width: 60px;" %)(((
441 -**Size(bytes)**
442 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**
443 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
444 444  (((
445 -Reserve/ Same as NBSN95 CFGMOD=1
380 +Check the battery voltage for LSE01.
446 446  )))
447 447  
448 448  (((
449 -No function here.
384 +Ex1: 0x0B45 = 2885mV
450 450  )))
451 -)))|(% style="width:77px" %)(((
386 +
452 452  (((
453 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
388 +Ex2: 0x0B49 = 2889mV
454 454  )))
455 455  
391 +
392 +
393 +=== 2.4.4  Signal Strength ===
394 +
456 456  (((
457 -By SHT31
396 +NB-IoT Network signal Strength.
458 458  )))
459 -)))|(% style="width:80px" %)(((
398 +
460 460  (((
461 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
400 +**Ex1: 0x1d = 29**
462 462  )))
463 463  
464 464  (((
465 -By SHT31
404 +(% style="color:blue" %)**0**(%%)  -113dBm or less
466 466  )))
406 +
407 +(((
408 +(% style="color:blue" %)**1**(%%)  -111dBm
467 467  )))
468 468  
469 469  (((
412 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
413 +)))
414 +
470 470  (((
471 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
416 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
472 472  )))
418 +
419 +(((
420 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
473 473  )))
474 474  
475 475  
476 -[[image:1657354294009-643.png]]
477 477  
425 +=== 2.4.5  Soil Moisture ===
478 478  
479 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
427 +(((
428 +(((
429 +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.
430 +)))
431 +)))
480 480  
481 -* Device ID: 0x724031607457 = 724031607457
482 -* Version: 0x006e=110=1.1.0
433 +(((
434 +(((
435 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
436 +)))
437 +)))
483 483  
484 -* BAT: 0x0ccd = 3277 mV = 3.277V
485 -* Signal: 0x1b = 27
486 -* Model: 0x01 = 1
487 -* 0x00dc000ccc= reserve, ignore in N95S31B
488 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
489 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
490 -
491 491  (((
492 492  
493 493  )))
494 494  
495 495  (((
496 -
444 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
497 497  )))
498 498  
499 499  
500 -=== 2.3.2  Device ID ===
501 501  
502 -(((
503 -By default, the Device ID equal to the last 6 bytes of IMEI.
504 -)))
449 +=== 2.4.6  Soil Temperature ===
505 505  
506 506  (((
507 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
452 +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
508 508  )))
509 509  
510 510  (((
511 -**Example:**
456 +**Example**:
512 512  )))
513 513  
514 514  (((
515 -AT+DEUI=A84041F15612
460 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
516 516  )))
517 517  
518 518  (((
519 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
464 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
520 520  )))
521 521  
522 522  
523 523  
524 -=== 2.3.3  Version Info ===
469 +=== 2.4.7  Soil Conductivity (EC) ===
525 525  
526 526  (((
527 -These bytes include the hardware and software version.
472 +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).
528 528  )))
529 529  
530 530  (((
531 -Higher byte: Specify hardware version: always 0x00 for N95S31B
476 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
532 532  )))
533 533  
534 534  (((
535 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
480 +Generally, the EC value of irrigation water is less than 800uS / cm.
536 536  )))
537 537  
538 538  (((
... ... @@ -540,83 +540,71 @@
540 540  )))
541 541  
542 542  (((
543 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
488 +
544 544  )))
545 545  
491 +=== 2.4.8  Digital Interrupt ===
492 +
546 546  (((
547 -
494 +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.
548 548  )))
549 549  
550 -
551 -=== 2.3.4  Battery Info ===
552 -
553 553  (((
554 -Ex1: 0x0B45 = 2885mV
498 +The command is:
555 555  )))
556 556  
557 557  (((
558 -Ex2: 0x0B49 = 2889mV
502 +(% 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]])**.**
559 559  )))
560 560  
561 561  
506 +(((
507 +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.
508 +)))
562 562  
563 -=== 2.3.5  Signal Strength ===
564 564  
565 565  (((
566 -NB-IoT Network signal Strength.
512 +Example:
567 567  )))
568 568  
569 569  (((
570 -**Ex1: 0x1d = 29**
516 +0x(00): Normal uplink packet.
571 571  )))
572 572  
573 573  (((
574 -(% style="color:blue" %)**0**(%%)  -113dBm or less
520 +0x(01): Interrupt Uplink Packet.
575 575  )))
576 576  
523 +
524 +
525 +=== 2.4.9  ​+5V Output ===
526 +
577 577  (((
578 -(% style="color:blue" %)**1**(%%)  -111dBm
528 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
579 579  )))
580 580  
531 +
581 581  (((
582 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
533 +The 5V output time can be controlled by AT Command.
583 583  )))
584 584  
585 585  (((
586 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
537 +(% style="color:blue" %)**AT+5VT=1000**
587 587  )))
588 588  
589 589  (((
590 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
541 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
591 591  )))
592 592  
593 593  
594 594  
595 -=== 2.3.6  Temperature & Humidity ===
546 +== 2.5  Downlink Payload ==
596 596  
597 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
548 +By default, NSE01 prints the downlink payload to console port.
598 598  
599 -[[image:image-20220709161741-3.png]]
550 +[[image:image-20220708133731-5.png]]
600 600  
601 601  
602 -Convert the read byte to decimal and divide it by ten.
603 -
604 -
605 -**Example:**
606 -
607 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
608 -
609 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
610 -
611 -
612 -
613 -== 2.4  Downlink Payload ==
614 -
615 -By default, NDDS75 prints the downlink payload to console port.
616 -
617 -[[image:image-20220709100028-1.png]]
618 -
619 -
620 620  (((
621 621  (% style="color:blue" %)**Examples:**
622 622  )))
... ... @@ -650,7 +650,7 @@
650 650  )))
651 651  
652 652  (((
653 -If payload = 0x04FF, it will reset the NDDS75
586 +If payload = 0x04FF, it will reset the NSE01
654 654  )))
655 655  
656 656  
... ... @@ -662,19 +662,78 @@
662 662  
663 663  
664 664  
665 -== 2.5  ​Battery Analysis ==
598 +== 2.6  ​LED Indicator ==
666 666  
667 -=== 2.5.1  ​Battery Type ===
600 +(((
601 +The NSE01 has an internal LED which is to show the status of different state.
668 668  
669 669  
604 +* 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)
605 +* Then the LED will be on for 1 second means device is boot normally.
606 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
607 +* For each uplink probe, LED will be on for 500ms.
608 +)))
609 +
610 +
611 +
612 +
613 +== 2.7  Installation in Soil ==
614 +
615 +__**Measurement the soil surface**__
616 +
670 670  (((
671 -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.
618 +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]]
672 672  )))
673 673  
621 +[[image:1657259653666-883.png]] ​
622 +
623 +
674 674  (((
625 +
626 +
627 +(((
628 +Dig a hole with diameter > 20CM.
629 +)))
630 +
631 +(((
632 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
633 +)))
634 +)))
635 +
636 +[[image:1654506665940-119.png]]
637 +
638 +(((
639 +
640 +)))
641 +
642 +
643 +== 2.8  ​Firmware Change Log ==
644 +
645 +
646 +Download URL & Firmware Change log
647 +
648 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
649 +
650 +
651 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
652 +
653 +
654 +
655 +== 2.9  ​Battery Analysis ==
656 +
657 +=== 2.9.1  ​Battery Type ===
658 +
659 +
660 +(((
661 +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.
662 +)))
663 +
664 +
665 +(((
675 675  The battery is designed to last for several years depends on the actually use environment and update interval. 
676 676  )))
677 677  
669 +
678 678  (((
679 679  The battery related documents as below:
680 680  )))
... ... @@ -684,40 +684,61 @@
684 684  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
685 685  
686 686  (((
687 -[[image:image-20220709101450-2.png]]
679 +[[image:image-20220708140453-6.png]]
688 688  )))
689 689  
690 690  
691 691  
692 -=== 2.5.2  Power consumption Analyze ===
684 +=== 2.9.2  Power consumption Analyze ===
693 693  
694 694  (((
695 -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.
687 +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.
696 696  )))
697 697  
690 +
698 698  (((
699 -
692 +Instruction to use as below:
700 700  )))
701 701  
695 +(((
696 +(% 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/]]
697 +)))
702 702  
703 -=== 2.5.3  ​Battery Note ===
704 704  
705 705  (((
706 -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.
701 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
707 707  )))
708 708  
704 +* (((
705 +Product Model
706 +)))
707 +* (((
708 +Uplink Interval
709 +)))
710 +* (((
711 +Working Mode
712 +)))
709 709  
714 +(((
715 +And the Life expectation in difference case will be shown on the right.
716 +)))
710 710  
711 -=== 2.5.4  Replace the battery ===
718 +[[image:image-20220708141352-7.jpeg]]
712 712  
713 713  
721 +
722 +=== 2.9.3  ​Battery Note ===
723 +
714 714  (((
715 -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.
725 +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.
716 716  )))
717 717  
718 718  
729 +
730 +=== 2.9.4  Replace the battery ===
731 +
719 719  (((
720 -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).
733 +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).
721 721  )))
722 722  
723 723  
... ... @@ -732,7 +732,7 @@
732 732  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/]] 
733 733  )))
734 734  
735 -[[image:1657333200519-600.png]]
748 +[[image:1657261278785-153.png]]
736 736  
737 737  
738 738  
... ... @@ -740,7 +740,7 @@
740 740  
741 741  == 4.1  Access AT Commands ==
742 742  
743 -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/]]
756 +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/]]
744 744  
745 745  
746 746  AT+<CMD>?  : Help on <CMD>
... ... @@ -828,12 +828,8 @@
828 828  )))
829 829  
830 830  (((
831 -
832 -
833 -(((
834 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
844 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
835 835  )))
836 -)))
837 837  
838 838  
839 839  
... ... @@ -842,29 +842,25 @@
842 842  == 6.1  ​Connection problem when uploading firmware ==
843 843  
844 844  
845 -(((
846 -**Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
847 -)))
848 -
849 849  (% class="wikigeneratedid" %)
850 850  (((
851 -
856 +(% style="font-size:14px" %)**Please see: **(%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting||style="background-color: rgb(255, 255, 255); font-size: 14px;"]]
852 852  )))
853 853  
854 854  
860 +
855 855  == 6.2  AT Command input doesn't work ==
856 856  
857 857  (((
858 858  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.
859 -
860 -
861 861  )))
862 862  
863 863  
868 +
864 864  = 7. ​ Order Info =
865 865  
866 866  
867 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
872 +Part Number**:** (% style="color:#4f81bd" %)**NSE01**
868 868  
869 869  
870 870  (% class="wikigeneratedid" %)
... ... @@ -879,7 +879,8 @@
879 879  
880 880  (% style="color:#037691" %)**Package Includes**:
881 881  
882 -* N95S31B NB-IoT Temperature and Humidity Sensor
887 +
888 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
883 883  * External antenna x 1
884 884  )))
885 885  
... ... @@ -888,10 +888,9 @@
888 888  
889 889  (% style="color:#037691" %)**Dimension and weight**:
890 890  
891 -* Device Size: 13.0 x 5 x 4.5 cm
892 -* Device Weight: 150g
893 -* Package Size / pcs : 14.0 x 8x 5 cm
894 -* Weight / pcs : 180g
897 +
898 +* Size: 195 x 125 x 55 mm
899 +* Weight:   420g
895 895  )))
896 896  
897 897  (((
1657271519014-786.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -71.5 KB
Content
1657327959271-447.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.3 KB
Content
1657328609906-564.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -492.6 KB
Content
1657328659945-416.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
1657328756309-230.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.5 KB
Content
1657328884227-504.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -483.6 KB
Content
1657329814315-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -85.3 KB
Content
1657330452568-615.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -71.3 KB
Content
1657330472797-498.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -68.9 KB
Content
1657330501006-241.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -119.2 KB
Content
1657330533775-472.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -74.9 KB
Content
1657330723006-866.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -74.1 KB
Content
1657331036973-987.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -83.8 KB
Content
1657332990863-496.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.2 KB
Content
1657333200519-600.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
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
1657520100595-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
image-20220709084038-1.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -72.0 KB
Content
image-20220709084137-2.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -72.0 KB
Content
image-20220709084207-3.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -72.0 KB
Content
image-20220709084458-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -199.5 KB
Content
image-20220709085040-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -200.4 KB
Content
image-20220709092052-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -247.3 KB
Content
image-20220709093918-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -42.2 KB
Content
image-20220709093918-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -61.9 KB
Content
image-20220709100028-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.8 KB
Content
image-20220709101450-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.5 KB
Content
image-20220709110451-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -611.5 KB
Content
image-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