Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 67.2
edited by Xiaoling
on 2022/07/08 18:09
Change comment: There is no comment for this version
To version 115.20
edited by Xiaoling
on 2022/07/09 18:15
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:1657271519014-786.png]]
2 +[[image:1657348034241-728.png||height="470" width="470"]]
3 3  
4 4  
5 5  
... ... @@ -7,54 +7,43 @@
7 7  
8 8  
9 9  
10 -
11 -
12 -
13 13  **Table of Contents:**
14 14  
12 +{{toc/}}
15 15  
16 16  
17 17  
18 18  
19 19  
20 -
21 21  = 1.  Introduction =
22 22  
23 -== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
20 +== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
24 24  
25 25  (((
26 26  
27 27  
28 -The Dragino NDDS75 is a **NB-IOT Distance Detection Sensor** for Internet of Things solution. It is used to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses **ultrasonic sensing technology** for **distance measurement**, and temperature compensation is performed internally to improve the reliability of data. The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc.
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*.
29 29  
30 -It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server.
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.
31 31  
32 -**NarrowBand-Internet of Things (NB-IoT)** is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
29 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
33 33  
34 -NDDS75 is powered by 8**500mA Li-SOCI2 battery**; It is designed for long term use up to 5 years*.
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).
35 35  
36 -~* Actually lifetime depends on network coverage and uplink interval and other factors
37 37  
38 -(((
39 -
40 -)))
34 +~* make sure you have NB-IoT coverage locally.
41 41  
42 42  
43 43  )))
44 44  
45 -[[image:1654503236291-817.png]]
39 +[[image:1657348284168-431.png]]
46 46  
47 47  
48 -[[image:1657245163077-232.png]]
49 49  
50 -
51 -
52 52  == 1.2 ​ Features ==
53 53  
54 54  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
55 -* Monitor Soil Moisture
56 -* Monitor Soil Temperature
57 -* Monitor Soil Conductivity
46 +* Monitor Temperature & Humidity via SHT31
58 58  * AT Commands to change parameters
59 59  * Uplink on periodically
60 60  * Downlink to change configure
... ... @@ -65,7 +65,6 @@
65 65  * 8500mAh Battery for long term use
66 66  
67 67  
68 -
69 69  == 1.3  Specification ==
70 70  
71 71  
... ... @@ -83,75 +83,127 @@
83 83  * - B20 @H-FDD: 800MHz
84 84  * - B28 @H-FDD: 700MHz
85 85  
86 -Probe(% style="color:#037691" %)** Specification:**
74 +(% style="color:#037691" %)**Battery:**
87 87  
88 -Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
89 89  
90 -[[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
91 91  
92 92  
93 -
94 94  == ​1.4  Applications ==
95 95  
86 +* Smart Buildings & Home Automation
87 +* Logistics and Supply Chain Management
88 +* Smart Metering
96 96  * Smart Agriculture
90 +* Smart Cities
91 +* Smart Factory
97 97  
98 98  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
99 99  ​
100 100  
96 +
101 101  == 1.5  Pin Definitions ==
102 102  
99 +N95S31B use the mother board from NBSN95 which as below.
103 103  
104 -[[image:1657246476176-652.png]]
101 +[[image:image-20220709144723-1.png]]
105 105  
106 106  
104 +=== 1.5.1 Jumper JP2 ===
107 107  
108 -= 2.  Use NSE01 to communicate with IoT Server =
106 +Power on Device when put this jumper.
109 109  
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 +
110 110  == 2.1  How it works ==
111 111  
112 112  
113 113  (((
114 -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.
115 115  )))
116 116  
117 117  
118 118  (((
119 -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:
120 120  )))
121 121  
122 -[[image:image-20220708101605-2.png]]
145 +(((
146 +
147 +)))
123 123  
149 +[[image:1657350248151-650.png]]
150 +
124 124  (((
125 125  
126 126  )))
127 127  
128 128  
156 +== 2.2 ​ Configure the N95S31B ==
129 129  
130 -== 2.2 ​ Configure the NSE01 ==
131 131  
159 +=== 2.2.1  Power On N95S31B ===
132 132  
161 +
162 +[[image:image-20220709150546-2.png]]
163 +
164 +
133 133  === 2.2.1 Test Requirement ===
134 134  
135 135  
136 -(((
137 -To use NSE01 in your city, make sure meet below requirements:
138 -)))
168 +To use N95S31B in your city, make sure meet below requirements:
139 139  
140 140  * Your local operator has already distributed a NB-IoT Network there.
141 -* The local NB-IoT network used the band that NSE01 supports.
171 +* The local NB-IoT network used the band that N95S31B supports.
142 142  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
143 143  
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 +
144 144  (((
145 -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
146 -)))
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(%%))
147 147  
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.
148 148  
149 -[[image:1657249419225-449.png]]
186 +
187 +)))
150 150  
189 +[[image:1657350625843-586.png]]
151 151  
152 152  
153 -=== 2.2.2 Insert SIM card ===
154 154  
193 +=== 2.2.3  Insert SIM card ===
194 +
155 155  (((
156 156  Insert the NB-IoT Card get from your provider.
157 157  )))
... ... @@ -161,18 +161,19 @@
161 161  )))
162 162  
163 163  
164 -[[image:1657249468462-536.png]]
204 +[[image:1657351240556-536.png]]
165 165  
166 166  
167 167  
168 -=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
208 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
169 169  
170 170  (((
171 171  (((
172 -User need to configure NSE01 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01 support AT Commands, user can use a USB to TTL adapter to connect to NSE01 and use AT Commands to configure it, as below.
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.
173 173  )))
174 174  )))
175 175  
216 +[[image:1657351312545-300.png]]
176 176  
177 177  **Connection:**
178 178  
... ... @@ -192,96 +192,110 @@
192 192  * Flow Control: (% style="color:green" %)**None**
193 193  
194 194  (((
195 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSE01. NSE01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
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.
196 196  )))
197 197  
198 -[[image:image-20220708110657-3.png]]
239 +[[image:1657329814315-101.png]]
199 199  
200 200  (((
201 -(% 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/]]
202 202  )))
203 203  
204 204  
205 205  
206 -=== 2.2.4 Use CoAP protocol to uplink data ===
247 +=== 2.2.5  Use CoAP protocol to uplink data ===
207 207  
208 208  (% 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/]]
209 209  
210 210  
252 +(((
211 211  **Use below commands:**
254 +)))
212 212  
213 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
214 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
215 -* (% 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 +)))
216 216  
266 +(((
267 +
268 +
217 217  For parameter description, please refer to AT command set
270 +)))
218 218  
219 -[[image:1657249793983-486.png]]
272 +[[image:1657352146020-183.png]]
220 220  
221 221  
222 -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 +)))
223 223  
224 -[[image:1657249831934-534.png]]
279 +[[image:1657352185396-303.png]]
225 225  
226 226  
227 227  
228 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
283 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
229 229  
230 -This feature is supported since firmware version v1.0.1
231 231  
232 -
233 -* (% 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
234 234  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
235 -* (% 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
236 236  
237 -[[image:1657249864775-321.png]]
290 +[[image:1657352391268-297.png]]
238 238  
239 239  
240 -[[image:1657249930215-289.png]]
293 +[[image:1657352403317-397.png]]
241 241  
242 242  
243 243  
244 -=== 2.2.6 Use MQTT protocol to uplink data ===
297 +=== 2.2.7  Use MQTT protocol to uplink data ===
245 245  
246 -This feature is supported since firmware version v110
299 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
247 247  
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
248 248  
249 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
250 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
251 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
252 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
253 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
254 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
255 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
309 +[[image:1657352634421-276.png]]
256 256  
257 -[[image:1657249978444-674.png]]
258 258  
312 +[[image:1657352645687-385.png]]
259 259  
260 -[[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 +)))
261 261  
262 262  
263 263  (((
264 -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.
265 265  )))
266 266  
267 267  
268 268  
269 -=== 2.2.7 Use TCP protocol to uplink data ===
325 +=== 2.2.8  Use TCP protocol to uplink data ===
270 270  
271 271  This feature is supported since firmware version v110
272 272  
273 -
274 274  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
275 275  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
276 276  
277 -[[image:1657250217799-140.png]]
332 +[[image:1657352898400-901.png]]
278 278  
279 279  
280 -[[image:1657250255956-604.png]]
335 +[[image:1657352914475-252.png]]
281 281  
282 282  
283 283  
284 -=== 2.2.8 Change Update Interval ===
339 +=== 2.2.9  Change Update Interval ===
285 285  
286 286  User can use below command to change the (% style="color:green" %)**uplink interval**.
287 287  
... ... @@ -288,264 +288,199 @@
288 288  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
289 289  
290 290  (((
291 -(% style="color:red" %)**NOTE:**
346 +
292 292  )))
293 293  
294 -(((
295 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
296 -)))
297 297  
298 298  
299 -
300 300  == 2.3  Uplink Payload ==
301 301  
302 -In this mode, uplink payload includes in total 18 bytes
303 303  
304 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
305 -|=(% style="width: 60px;" %)(((
306 -**Size(bytes)**
307 -)))|=(% 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**
308 -|(% 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.
309 309  
310 -(((
311 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
312 -)))
313 313  
357 +For example:
314 314  
315 -[[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.
316 316  
317 317  
318 -The payload is ASCII string, representative same HEX:
362 +The uplink payloads are composed in  ASCII String. For example:
319 319  
320 -0x72403155615900640c7817075e0a8c02f900 where:
364 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
321 321  
322 -* Device ID: 0x 724031556159 = 724031556159
323 -* Version: 0x0064=100=1.0.0
366 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
324 324  
325 -* BAT: 0x0c78 = 3192 mV = 3.192V
326 -* Singal: 0x17 = 23
327 -* Soil Moisture: 0x075e= 1886 = 18.86  %
328 -* Soil Temperature:0x0a8c =2700=27 °C
329 -* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
330 -* Interrupt: 0x00 = 0
331 331  
369 +(% style="color:red" %)**NOTE:**
332 332  
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.
333 333  
334 -== 2.4  Payload Explanation and Sensor Interface ==
375 +=== 2.3.1  Payload Analyze ===
335 335  
377 +N95S31B uplink payload includes in total 21 bytes
336 336  
337 -=== 2.4.1  Device ID ===
338 338  
339 -(((
340 -By default, the Device ID equal to the last 6 bytes of IMEI.
341 -)))
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: 55px;" %)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
342 342  
343 -(((
344 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
345 -)))
387 +No function here.
388 +)))|(% style="width:77px" %)(((
389 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
346 346  
347 -(((
348 -**Example:**
349 -)))
391 +By SHT31
392 +)))|(% style="width:80px" %)(((
393 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
350 350  
351 -(((
352 -AT+DEUI=A84041F15612
395 +By SHT31
353 353  )))
354 354  
355 355  (((
356 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
399 +(((
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.
357 357  )))
402 +)))
358 358  
359 359  
405 +[[image:1657354294009-643.png]]
360 360  
361 -=== 2.4.2  Version Info ===
362 362  
363 -(((
364 -Specify the software version: 0x64=100, means firmware version 1.00.
365 -)))
408 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
366 366  
367 -(((
368 -For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
369 -)))
410 +* Device ID: 0x724031607457 = 724031607457
411 +* Version: 0x006e=110=1.1.0
370 370  
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
371 371  
372 -
373 -=== 2.4.3  Battery Info ===
374 -
375 375  (((
376 -Check the battery voltage for LSE01.
421 +
377 377  )))
378 378  
379 379  (((
380 -Ex1: 0x0B45 = 2885mV
425 +
381 381  )))
382 382  
383 -(((
384 -Ex2: 0x0B49 = 2889mV
385 -)))
386 386  
429 +=== 2.3.2  Device ID ===
387 387  
388 -
389 -=== 2.4.4  Signal Strength ===
390 -
391 391  (((
392 -NB-IoT Network signal Strength.
432 +By default, the Device ID equal to the last 6 bytes of IMEI.
393 393  )))
394 394  
395 395  (((
396 -**Ex1: 0x1d = 29**
436 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
397 397  )))
398 398  
399 399  (((
400 -(% style="color:blue" %)**0**(%%)  -113dBm or less
440 +**Example:**
401 401  )))
402 402  
403 403  (((
404 -(% style="color:blue" %)**1**(%%)  -111dBm
444 +AT+DEUI=A84041F15612
405 405  )))
406 406  
407 407  (((
408 -(% 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.
409 409  )))
410 410  
411 -(((
412 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
413 -)))
414 414  
415 -(((
416 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
417 -)))
418 418  
453 +=== 2.3.3  Version Info ===
419 419  
420 420  
421 -=== 2.4.5  Soil Moisture ===
456 +These bytes include the hardware and software version.
422 422  
423 -(((
424 -(((
425 -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.
426 -)))
427 -)))
458 +Higher byte: Specify hardware version: always 0x00 for N95S31B
428 428  
429 -(((
430 -(((
431 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
432 -)))
433 -)))
460 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
434 434  
462 +
463 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
464 +
435 435  (((
436 436  
437 437  )))
438 438  
439 -(((
440 -(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
441 -)))
442 442  
470 +=== 2.3.4  Battery Info ===
443 443  
444 -
445 -=== 2.4.6  Soil Temperature ===
446 -
447 447  (((
448 -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
449 449  )))
450 450  
451 451  (((
452 -**Example**:
477 +Ex2: 0x0B49 = 2889mV
453 453  )))
454 454  
455 -(((
456 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
457 -)))
458 458  
459 -(((
460 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
461 -)))
462 462  
482 +=== 2.3.5  Signal Strength ===
463 463  
464 -
465 -=== 2.4.7  Soil Conductivity (EC) ===
466 -
467 467  (((
468 -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.
469 469  )))
470 470  
471 471  (((
472 -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**
473 473  )))
474 474  
475 475  (((
476 -Generally, the EC value of irrigation water is less than 800uS / cm.
493 +(% style="color:blue" %)**0**(%%)  -113dBm or less
477 477  )))
478 478  
479 479  (((
480 -
497 +(% style="color:blue" %)**1**(%%)  -111dBm
481 481  )))
482 482  
483 483  (((
484 -
501 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
485 485  )))
486 486  
487 -=== 2.4.8  Digital Interrupt ===
488 -
489 489  (((
490 -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
491 491  )))
492 492  
493 493  (((
494 -The command is:
509 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
495 495  )))
496 496  
497 -(((
498 -(% 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]])**.**
499 -)))
500 500  
501 501  
502 -(((
503 -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.
504 -)))
514 +=== 2.3.6  Temperature & Humidity ===
505 505  
516 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
506 506  
507 -(((
508 -Example:
509 -)))
518 +[[image:image-20220709161741-3.png]]
510 510  
511 -(((
512 -0x(00): Normal uplink packet.
513 -)))
514 514  
515 -(((
516 -0x(01): Interrupt Uplink Packet.
517 -)))
521 +Convert the read byte to decimal and divide it by ten.
518 518  
519 519  
524 +**Example:**
520 520  
521 -=== 2.4.9  ​+5V Output ===
526 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
522 522  
523 -(((
524 -NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
525 -)))
528 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
526 526  
527 527  
528 -(((
529 -The 5V output time can be controlled by AT Command.
530 -)))
531 531  
532 -(((
533 -(% style="color:blue" %)**AT+5VT=1000**
534 -)))
532 +== 2.4  Downlink Payload ==
535 535  
536 -(((
537 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
538 -)))
534 +By default, NDDS75 prints the downlink payload to console port.
539 539  
536 +[[image:image-20220709100028-1.png]]
540 540  
541 541  
542 -== 2.5  Downlink Payload ==
543 -
544 -By default, NSE01 prints the downlink payload to console port.
545 -
546 -[[image:image-20220708133731-5.png]]
547 -
548 -
549 549  (((
550 550  (% style="color:blue" %)**Examples:**
551 551  )))
... ... @@ -579,7 +579,7 @@
579 579  )))
580 580  
581 581  (((
582 -If payload = 0x04FF, it will reset the NSE01
572 +If payload = 0x04FF, it will reset the NDDS75
583 583  )))
584 584  
585 585  
... ... @@ -591,78 +591,19 @@
591 591  
592 592  
593 593  
594 -== 2.6  ​LED Indicator ==
584 +== 2.5  ​Battery Analysis ==
595 595  
596 -(((
597 -The NSE01 has an internal LED which is to show the status of different state.
586 +=== 2.5.1  ​Battery Type ===
598 598  
599 599  
600 -* 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)
601 -* Then the LED will be on for 1 second means device is boot normally.
602 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
603 -* For each uplink probe, LED will be on for 500ms.
604 -)))
605 -
606 -
607 -
608 -
609 -== 2.7  Installation in Soil ==
610 -
611 -__**Measurement the soil surface**__
612 -
613 613  (((
614 -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.
615 615  )))
616 616  
617 -[[image:1657259653666-883.png]] ​
618 -
619 -
620 620  (((
621 -
622 -
623 -(((
624 -Dig a hole with diameter > 20CM.
625 -)))
626 -
627 -(((
628 -Horizontal insert the probe to the soil and fill the hole for long term measurement.
629 -)))
630 -)))
631 -
632 -[[image:1654506665940-119.png]]
633 -
634 -(((
635 -
636 -)))
637 -
638 -
639 -== 2.8  ​Firmware Change Log ==
640 -
641 -
642 -Download URL & Firmware Change log
643 -
644 -[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
645 -
646 -
647 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
648 -
649 -
650 -
651 -== 2.9  ​Battery Analysis ==
652 -
653 -=== 2.9.1  ​Battery Type ===
654 -
655 -
656 -(((
657 -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.
658 -)))
659 -
660 -
661 -(((
662 662  The battery is designed to last for several years depends on the actually use environment and update interval. 
663 663  )))
664 664  
665 -
666 666  (((
667 667  The battery related documents as below:
668 668  )))
... ... @@ -672,61 +672,40 @@
672 672  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
673 673  
674 674  (((
675 -[[image:image-20220708140453-6.png]]
606 +[[image:image-20220709101450-2.png]]
676 676  )))
677 677  
678 678  
679 679  
680 -=== 2.9.2  Power consumption Analyze ===
611 +=== 2.5.2  Power consumption Analyze ===
681 681  
682 682  (((
683 -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.
684 684  )))
685 685  
686 -
687 687  (((
688 -Instruction to use as below:
618 +
689 689  )))
690 690  
691 -(((
692 -(% 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/]]
693 -)))
694 694  
622 +=== 2.5.3  ​Battery Note ===
695 695  
696 696  (((
697 -(% 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.
698 698  )))
699 699  
700 -* (((
701 -Product Model
702 -)))
703 -* (((
704 -Uplink Interval
705 -)))
706 -* (((
707 -Working Mode
708 -)))
709 709  
710 -(((
711 -And the Life expectation in difference case will be shown on the right.
712 -)))
713 713  
714 -[[image:image-20220708141352-7.jpeg]]
630 +=== 2.5.4  Replace the battery ===
715 715  
716 716  
717 -
718 -=== 2.9.3  ​Battery Note ===
719 -
720 720  (((
721 -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.
722 722  )))
723 723  
724 724  
725 -
726 -=== 2.9.4  Replace the battery ===
727 -
728 728  (((
729 -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).
730 730  )))
731 731  
732 732  
... ... @@ -741,7 +741,7 @@
741 741  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/]] 
742 742  )))
743 743  
744 -[[image:1657261278785-153.png]]
654 +[[image:1657333200519-600.png]]
745 745  
746 746  
747 747  
... ... @@ -749,7 +749,7 @@
749 749  
750 750  == 4.1  Access AT Commands ==
751 751  
752 -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/]]
753 753  
754 754  
755 755  AT+<CMD>?  : Help on <CMD>
... ... @@ -837,18 +837,13 @@
837 837  )))
838 838  
839 839  (((
840 -(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
841 -)))
750 +
842 842  
843 -
844 -
845 -== 5.2  Can I calibrate NSE01 to different soil types? ==
846 -
847 -(((
848 -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.
849 849  )))
850 850  
851 851  
756 +
852 852  = 6.  Trouble Shooting =
853 853  
854 854  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -876,7 +876,7 @@
876 876  = 7. ​ Order Info =
877 877  
878 878  
879 -Part Number**:** (% style="color:#4f81bd" %)**NSE01**
784 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
880 880  
881 881  
882 882  (% class="wikigeneratedid" %)
... ... @@ -891,7 +891,7 @@
891 891  
892 892  (% style="color:#037691" %)**Package Includes**:
893 893  
894 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
799 +* N95S31B NB-IoT Temperature and Humidity Sensor
895 895  * External antenna x 1
896 896  )))
897 897  
... ... @@ -900,8 +900,10 @@
900 900  
901 901  (% style="color:#037691" %)**Dimension and weight**:
902 902  
903 -* Size: 195 x 125 x 55 mm
904 -* 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
905 905  )))
906 906  
907 907  (((
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