Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 65.11
edited by Xiaoling
on 2022/07/08 15:44
Change comment: There is no comment for this version
To version 115.1
edited by Xiaoling
on 2022/07/09 16:17
Change comment: Uploaded new attachment "image-20220709161741-3.png", version {1}

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
... ... @@ -87,75 +87,129 @@
87 87  * - B20 @H-FDD: 800MHz
88 88  * - B28 @H-FDD: 700MHz
89 89  
90 -Probe(% style="color:#037691" %)** Specification:**
74 +(% style="color:#037691" %)**Battery:**
91 91  
92 -Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
93 93  
94 -[[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
95 95  
96 96  
97 -
98 98  == ​1.4  Applications ==
99 99  
86 +* Smart Buildings & Home Automation
87 +* Logistics and Supply Chain Management
88 +* Smart Metering
100 100  * Smart Agriculture
90 +* Smart Cities
91 +* Smart Factory
101 101  
102 102  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
103 103  ​
104 104  
96 +
105 105  == 1.5  Pin Definitions ==
106 106  
99 +N95S31B use the mother board from NBSN95 which as below.
107 107  
108 -[[image:1657246476176-652.png]]
101 +[[image:image-20220709144723-1.png]]
109 109  
110 110  
104 +=== 1.5.1 Jumper JP2 ===
111 111  
112 -= 2.  Use NSE01 to communicate with IoT Server =
106 +Power on Device when put this jumper.
113 113  
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 +
114 114  == 2.1  How it works ==
115 115  
116 116  
117 117  (((
118 -The NSE01 is equipped with a NB-IoT module, the pre-loaded firmware in NSE01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NSE01.
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.
119 119  )))
120 120  
121 121  
122 122  (((
123 -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:
124 124  )))
125 125  
126 -[[image:image-20220708101605-2.png]]
147 +(((
148 +
149 +)))
127 127  
151 +[[image:1657350248151-650.png]]
152 +
128 128  (((
129 129  
130 130  )))
131 131  
132 132  
158 +== 2.2 ​ Configure the N95S31B ==
133 133  
134 -== 2.2 ​ Configure the NSE01 ==
135 135  
161 +=== 2.2.1  Power On N95S31B ===
136 136  
163 +
164 +[[image:image-20220709150546-2.png]]
165 +
166 +
137 137  === 2.2.1 Test Requirement ===
138 138  
139 139  
140 -(((
141 -To use NSE01 in your city, make sure meet below requirements:
142 -)))
170 +To use N95S31B in your city, make sure meet below requirements:
143 143  
144 144  * Your local operator has already distributed a NB-IoT Network there.
145 -* The local NB-IoT network used the band that NSE01 supports.
173 +* The local NB-IoT network used the band that N95S31B supports.
146 146  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
147 147  
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 +
148 148  (((
149 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NSE01 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
150 -)))
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(%%))
151 151  
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.
152 152  
153 -[[image:1657249419225-449.png]]
188 +
189 +)))
154 154  
191 +[[image:1657350625843-586.png]]
155 155  
156 156  
157 -=== 2.2.2 Insert SIM card ===
158 158  
195 +=== 2.2.3  Insert SIM card ===
196 +
159 159  (((
160 160  Insert the NB-IoT Card get from your provider.
161 161  )))
... ... @@ -165,18 +165,19 @@
165 165  )))
166 166  
167 167  
168 -[[image:1657249468462-536.png]]
206 +[[image:1657351240556-536.png]]
169 169  
170 170  
171 171  
172 -=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
210 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
173 173  
174 174  (((
175 175  (((
176 -User need to configure NSE01 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01 support AT Commands, user can use a USB to TTL adapter to connect to NSE01 and use AT Commands to configure it, as below.
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.
177 177  )))
178 178  )))
179 179  
218 +[[image:1657351312545-300.png]]
180 180  
181 181  **Connection:**
182 182  
... ... @@ -196,94 +196,110 @@
196 196  * Flow Control: (% style="color:green" %)**None**
197 197  
198 198  (((
199 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSE01. NSE01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
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.
200 200  )))
201 201  
202 -[[image:image-20220708110657-3.png]]
241 +[[image:1657329814315-101.png]]
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/]]
243 +(((
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/]]
245 +)))
205 205  
206 206  
207 207  
208 -=== 2.2.4 Use CoAP protocol to uplink data ===
249 +=== 2.2.5  Use CoAP protocol to uplink data ===
209 209  
210 210  (% 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/]]
211 211  
212 212  
254 +(((
213 213  **Use below commands:**
256 +)))
214 214  
215 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
216 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
217 -* (% 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 +)))
218 218  
268 +(((
269 +
270 +
219 219  For parameter description, please refer to AT command set
272 +)))
220 220  
221 -[[image:1657249793983-486.png]]
274 +[[image:1657352146020-183.png]]
222 222  
223 223  
224 -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 +)))
225 225  
226 -[[image:1657249831934-534.png]]
281 +[[image:1657352185396-303.png]]
227 227  
228 228  
229 229  
230 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
285 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
231 231  
232 -This feature is supported since firmware version v1.0.1
233 233  
234 -
235 -* (% 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
236 236  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
237 -* (% 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
238 238  
239 -[[image:1657249864775-321.png]]
292 +[[image:1657352391268-297.png]]
240 240  
241 241  
242 -[[image:1657249930215-289.png]]
295 +[[image:1657352403317-397.png]]
243 243  
244 244  
245 245  
246 -=== 2.2.6 Use MQTT protocol to uplink data ===
299 +=== 2.2.7  Use MQTT protocol to uplink data ===
247 247  
248 -This feature is supported since firmware version v110
301 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
249 249  
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
250 250  
251 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
252 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
253 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
254 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
255 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
256 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
257 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
311 +[[image:1657352634421-276.png]]
258 258  
259 -[[image:1657249978444-674.png]]
260 260  
314 +[[image:1657352645687-385.png]]
261 261  
262 -[[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 +)))
263 263  
264 264  
265 265  (((
266 -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.
267 267  )))
268 268  
269 269  
270 270  
271 -=== 2.2.7 Use TCP protocol to uplink data ===
327 +=== 2.2.8  Use TCP protocol to uplink data ===
272 272  
273 273  This feature is supported since firmware version v110
274 274  
275 -
276 276  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
277 277  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
278 278  
279 -[[image:1657250217799-140.png]]
334 +[[image:1657352898400-901.png]]
280 280  
281 281  
282 -[[image:1657250255956-604.png]]
337 +[[image:1657352914475-252.png]]
283 283  
284 284  
285 285  
286 -=== 2.2.8 Change Update Interval ===
341 +=== 2.2.9  Change Update Interval ===
287 287  
288 288  User can use below command to change the (% style="color:green" %)**uplink interval**.
289 289  
... ... @@ -290,158 +290,198 @@
290 290  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
291 291  
292 292  (((
293 -(% style="color:red" %)**NOTE:**
348 +
294 294  )))
295 295  
296 -(((
297 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
298 -)))
299 299  
300 300  
301 -
302 302  == 2.3  Uplink Payload ==
303 303  
304 -In this mode, uplink payload includes in total 18 bytes
305 305  
306 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
307 -|=(% style="width: 50px;" %)(((
308 -**Size(bytes)**
309 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 40px;" %)**1**
310 -|(% 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.
311 311  
312 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
313 313  
359 +For example:
314 314  
315 -[[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.
316 316  
317 317  
318 -The payload is ASCII string, representative same HEX:
364 +The uplink payloads are composed in  ASCII String. For example:
319 319  
320 -0x72403155615900640c7817075e0a8c02f900 where:
366 +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
368 +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  
371 +(% style="color:red" %)**NOTE:**
332 332  
333 -== 2.4  Payload Explanation and Sensor Interface ==
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.
334 334  
335 335  
336 -=== 2.4.1  Device ID ===
337 337  
338 -By default, the Device ID equal to the last 6 bytes of IMEI.
339 339  
340 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
380 +=== 2.3.1  Payload Analyze ===
341 341  
342 -**Example:**
382 +N95S31B uplink payload includes in total 21 bytes
343 343  
344 -AT+DEUI=A84041F15612
345 345  
346 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
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
347 347  
392 +No function here.
393 +)))|(% style="width:77px" %)(((
394 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
348 348  
396 +By SHT31
397 +)))|(% style="width:80px" %)(((
398 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
349 349  
350 -=== 2.4.2  Version Info ===
400 +By SHT31
401 +)))
351 351  
352 -Specify the software version: 0x64=100, means firmware version 1.00.
403 +(((
404 +(((
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.
406 +)))
407 +)))
353 353  
354 -For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
355 355  
410 +[[image:1657354294009-643.png]]
356 356  
357 -
358 -=== 2.4.3  Battery Info ===
359 -
360 360  (((
361 -Check the battery voltage for LSE01.
413 +The payload is ASCII string, representative same HEX:
362 362  )))
363 363  
364 364  (((
365 -Ex1: 0x0B45 = 2885mV
417 +0x72403155615900640c6c19029200 where:
366 366  )))
367 367  
368 -(((
369 -Ex2: 0x0B49 = 2889mV
420 +* (((
421 +Device ID: 0x724031556159 = 724031556159
370 370  )))
423 +* (((
424 +Version: 0x0064=100=1.0.0
425 +)))
371 371  
427 +* (((
428 +BAT: 0x0c6c = 3180 mV = 3.180V
429 +)))
430 +* (((
431 +Signal: 0x19 = 25
432 +)))
433 +* (((
434 +Distance: 0x0292= 658 mm
435 +)))
436 +* (((
437 +Interrupt: 0x00 = 0
372 372  
373 373  
374 -=== 2.4.4  Signal Strength ===
375 375  
376 -NB-IoT Network signal Strength.
441 +
442 +)))
377 377  
378 -**Ex1: 0x1d = 29**
444 +== 2.4  Payload Explanation and Sensor Interface ==
379 379  
380 -(% style="color:blue" %)**0**(%%)  -113dBm or less
381 381  
382 -(% style="color:blue" %)**1**(%%)  -111dBm
447 +=== 2.4.1  Device ID ===
383 383  
384 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
449 +(((
450 +By default, the Device ID equal to the last 6 bytes of IMEI.
451 +)))
385 385  
386 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
453 +(((
454 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
455 +)))
387 387  
388 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
457 +(((
458 +**Example:**
459 +)))
389 389  
461 +(((
462 +AT+DEUI=A84041F15612
463 +)))
390 390  
465 +(((
466 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
467 +)))
391 391  
392 -=== 2.4.5  Soil Moisture ===
393 393  
470 +
471 +=== 2.4.2  Version Info ===
472 +
394 394  (((
395 -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.
474 +Specify the software version: 0x64=100, means firmware version 1.00.
396 396  )))
397 397  
398 398  (((
399 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
478 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
400 400  )))
401 401  
481 +
482 +
483 +=== 2.4.3  Battery Info ===
484 +
402 402  (((
403 -
486 +Ex1: 0x0B45 = 2885mV
404 404  )))
405 405  
406 406  (((
407 -(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
490 +Ex2: 0x0B49 = 2889mV
408 408  )))
409 409  
410 410  
411 411  
412 -=== 2.4.6  Soil Temperature ===
495 +=== 2.4.4  Signal Strength ===
413 413  
414 414  (((
415 - 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
498 +NB-IoT Network signal Strength.
416 416  )))
417 417  
418 418  (((
419 -**Example**:
502 +**Ex1: 0x1d = 29**
420 420  )))
421 421  
422 422  (((
423 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
506 +(% style="color:blue" %)**0**(%%)  -113dBm or less
424 424  )))
425 425  
426 426  (((
427 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
510 +(% style="color:blue" %)**1**(%%)  -111dBm
428 428  )))
429 429  
513 +(((
514 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
515 +)))
430 430  
517 +(((
518 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
519 +)))
431 431  
432 -=== 2.4.7  Soil Conductivity (EC) ===
433 -
434 434  (((
435 -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).
522 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
436 436  )))
437 437  
525 +
526 +
527 +=== 2.4.5  Distance ===
528 +
529 +Get the distance. Flat object range 280mm - 7500mm.
530 +
438 438  (((
439 -For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
532 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
440 440  )))
441 441  
442 442  (((
443 -Generally, the EC value of irrigation water is less than 800uS / cm.
536 +(((
537 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
444 444  )))
539 +)))
445 445  
446 446  (((
447 447  
... ... @@ -451,44 +451,66 @@
451 451  
452 452  )))
453 453  
454 -=== 2.4.8  Digital Interrupt ===
549 +=== 2.4.6  Digital Interrupt ===
455 455  
456 -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.
551 +(((
552 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
553 +)))
457 457  
555 +(((
458 458  The command is:
557 +)))
459 459  
559 +(((
460 460  (% 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]])**.**
561 +)))
461 461  
462 462  
564 +(((
463 463  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.
566 +)))
464 464  
465 465  
569 +(((
466 466  Example:
571 +)))
467 467  
573 +(((
468 468  0x(00): Normal uplink packet.
575 +)))
469 469  
577 +(((
470 470  0x(01): Interrupt Uplink Packet.
579 +)))
471 471  
472 472  
473 473  
474 -=== 2.4.9  ​+5V Output ===
583 +=== 2.4.7  ​+5V Output ===
475 475  
476 -NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
585 +(((
586 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
587 +)))
477 477  
478 478  
590 +(((
479 479  The 5V output time can be controlled by AT Command.
592 +)))
480 480  
594 +(((
481 481  (% style="color:blue" %)**AT+5VT=1000**
596 +)))
482 482  
598 +(((
483 483  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
600 +)))
484 484  
485 485  
486 486  
487 487  == 2.5  Downlink Payload ==
488 488  
489 -By default, NSE01 prints the downlink payload to console port.
606 +By default, NDDS75 prints the downlink payload to console port.
490 490  
491 -[[image:image-20220708133731-5.png]]
608 +[[image:image-20220709100028-1.png]]
492 492  
493 493  
494 494  (((
... ... @@ -524,83 +524,69 @@
524 524  )))
525 525  
526 526  (((
527 -If payload = 0x04FF, it will reset the NSE01
644 +If payload = 0x04FF, it will reset the NDDS75
528 528  )))
529 529  
530 530  
531 531  * (% style="color:blue" %)**INTMOD**
532 532  
650 +(((
533 533  Downlink Payload: 06000003, Set AT+INTMOD=3
652 +)))
534 534  
535 535  
536 536  
537 537  == 2.6  ​LED Indicator ==
538 538  
539 -(((
540 -The NSE01 has an internal LED which is to show the status of different state.
541 541  
659 +The NDDS75 has an internal LED which is to show the status of different state.
542 542  
543 -* 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)
661 +
662 +* 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)
544 544  * Then the LED will be on for 1 second means device is boot normally.
545 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
664 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
546 546  * For each uplink probe, LED will be on for 500ms.
666 +
667 +(((
668 +
547 547  )))
548 548  
549 549  
550 550  
673 +== 2.7  ​Firmware Change Log ==
551 551  
552 -== 2.7  Installation in Soil ==
553 553  
554 -__**Measurement the soil surface**__
555 -
556 -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]]
557 -
558 -[[image:1657259653666-883.png]] ​
559 -
560 -
561 561  (((
562 -
563 -
564 -(((
565 -Dig a hole with diameter > 20CM.
677 +Download URL & Firmware Change log
566 566  )))
567 567  
568 568  (((
569 -Horizontal insert the probe to the soil and fill the hole for long term measurement.
681 +[[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/]]
570 570  )))
571 -)))
572 572  
573 -[[image:1654506665940-119.png]]
574 574  
575 575  (((
576 -
686 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
577 577  )))
578 578  
579 579  
580 -== 2.8  ​Firmware Change Log ==
581 581  
691 +== 2.8  ​Battery Analysis ==
582 582  
583 -Download URL & Firmware Change log
693 +=== 2.8.1  ​Battery Type ===
584 584  
585 -[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
586 586  
696 +(((
697 +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.
698 +)))
587 587  
588 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
589 -
590 -
591 -
592 -== 2.9  ​Battery Analysis ==
593 -
594 -=== 2.9.1  ​Battery Type ===
595 -
596 -
597 -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.
598 -
599 -
700 +(((
600 600  The battery is designed to last for several years depends on the actually use environment and update interval. 
702 +)))
601 601  
602 -
704 +(((
603 603  The battery related documents as below:
706 +)))
604 604  
605 605  * [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
606 606  * [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
... ... @@ -607,12 +607,12 @@
607 607  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
608 608  
609 609  (((
610 -[[image:image-20220708140453-6.png]]
713 +[[image:image-20220709101450-2.png]]
611 611  )))
612 612  
613 613  
614 614  
615 -=== 2.9.2  Power consumption Analyze ===
718 +=== 2.8.2  Power consumption Analyze ===
616 616  
617 617  (((
618 618  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.
... ... @@ -646,11 +646,11 @@
646 646  And the Life expectation in difference case will be shown on the right.
647 647  )))
648 648  
649 -[[image:image-20220708141352-7.jpeg]]
752 +[[image:image-20220709110451-3.png]]
650 650  
651 651  
652 652  
653 -=== 2.9.3  ​Battery Note ===
756 +=== 2.8.3  ​Battery Note ===
654 654  
655 655  (((
656 656  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.
... ... @@ -658,10 +658,10 @@
658 658  
659 659  
660 660  
661 -=== 2.9.4  Replace the battery ===
764 +=== 2.8.4  Replace the battery ===
662 662  
663 663  (((
664 -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).
767 +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).
665 665  )))
666 666  
667 667  
... ... @@ -676,7 +676,7 @@
676 676  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/]] 
677 677  )))
678 678  
679 -[[image:1657261278785-153.png]]
782 +[[image:1657333200519-600.png]]
680 680  
681 681  
682 682  
... ... @@ -684,7 +684,7 @@
684 684  
685 685  == 4.1  Access AT Commands ==
686 686  
687 -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/]]
790 +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/]]
688 688  
689 689  
690 690  AT+<CMD>?  : Help on <CMD>
... ... @@ -772,7 +772,7 @@
772 772  )))
773 773  
774 774  (((
775 -(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
878 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
776 776  )))
777 777  
778 778  
... ... @@ -782,25 +782,29 @@
782 782  == 6.1  ​Connection problem when uploading firmware ==
783 783  
784 784  
888 +(((
889 +**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]]
890 +)))
891 +
785 785  (% class="wikigeneratedid" %)
786 786  (((
787 -(% 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;"]]
894 +
788 788  )))
789 789  
790 790  
791 -
792 792  == 6.2  AT Command input doesn't work ==
793 793  
794 794  (((
795 795  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.
902 +
903 +
796 796  )))
797 797  
798 798  
799 -
800 800  = 7. ​ Order Info =
801 801  
802 802  
803 -Part Number**:** (% style="color:#4f81bd" %)**NSE01**
910 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
804 804  
805 805  
806 806  (% class="wikigeneratedid" %)
... ... @@ -815,8 +815,7 @@
815 815  
816 816  (% style="color:#037691" %)**Package Includes**:
817 817  
818 -
819 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
925 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
820 820  * External antenna x 1
821 821  )))
822 822  
... ... @@ -826,8 +826,10 @@
826 826  (% style="color:#037691" %)**Dimension and weight**:
827 827  
828 828  
829 -* Size: 195 x 125 x 55 mm
830 -* Weight:   420g
935 +* Device Size: 13.0 x 5 x 4.5 cm
936 +* Device Weight: 150g
937 +* Package Size / pcs : 15 x 12x 5.5 cm
938 +* Weight / pcs : 220g
831 831  )))
832 832  
833 833  (((
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