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