Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 65.9
edited by Xiaoling
on 2022/07/08 15:38
Change comment: There is no comment for this version
To version 115.34
edited by Xiaoling
on 2022/07/11 09:30
Change comment: There is no comment for this version

Summary

Details

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