Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 67.1
edited by Xiaoling
on 2022/07/08 17:11
Change comment: Uploaded new attachment "1657271519014-786.png", version {1}
To version 115.19
edited by Xiaoling
on 2022/07/09 18:14
Change comment: There is no comment for this version

Summary

Details

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