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