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