Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 65.10
edited by Xiaoling
on 2022/07/08 15:43
Change comment: There is no comment for this version
To version 115.3
edited by Xiaoling
on 2022/07/09 16:59
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,42 @@
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  
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
45 +* Monitor Temperature & Humidity via SHT31
63 63  * AT Commands to change parameters
64 64  * Uplink on periodically
65 65  * Downlink to change configure
... ... @@ -70,6 +70,8 @@
70 70  * 8500mAh Battery for long term use
71 71  
72 72  
56 +
57 +
73 73  == 1.3  Specification ==
74 74  
75 75  
... ... @@ -87,92 +87,152 @@
87 87  * - B20 @H-FDD: 800MHz
88 88  * - B28 @H-FDD: 700MHz
89 89  
90 -Probe(% style="color:#037691" %)** Specification:**
75 +(% 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]]
78 +* Li/SOCI2 un-chargeable battery
79 +* Capacity: 8500mAh
80 +* Self Discharge: <1% / Year @ 25°C
81 +* Max continuously current: 130mA
82 +* Max boost current: 2A, 1 second
95 95  
96 96  
97 97  
86 +
98 98  == ​1.4  Applications ==
99 99  
89 +* Smart Buildings & Home Automation
90 +* Logistics and Supply Chain Management
91 +* Smart Metering
100 100  * Smart Agriculture
93 +* Smart Cities
94 +* Smart Factory
101 101  
102 102  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
103 103  ​
104 104  
99 +
105 105  == 1.5  Pin Definitions ==
106 106  
102 +N95S31B use the mother board from NBSN95 which as below.
107 107  
108 -[[image:1657246476176-652.png]]
104 +[[image:image-20220709144723-1.png]]
109 109  
110 110  
107 +=== 1.5.1 Jumper JP2 ===
111 111  
112 -= 2.  Use NSE01 to communicate with IoT Server =
109 +Power on Device when put this jumper.
113 113  
111 +
112 +
113 +=== 1.5.2 BOOT MODE / SW1 ===
114 +
115 +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.
116 +
117 +2) Flash: work mode, device starts to work and send out console output for further debug
118 +
119 +
120 +
121 +=== 1.5.3 Reset Button ===
122 +
123 +Press to reboot the device.
124 +
125 +
126 +
127 +=== 1.5.4 LED ===
128 +
129 +It will flash:
130 +
131 +1. When boot the device in flash mode
132 +1. Send an uplink packet
133 +
134 +
135 += 2.  Use N95S31B to communicate with IoT Server =
136 +
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.
141 +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:
146 +The diagram below shows the working flow in default firmware of N95S31B:
124 124  )))
125 125  
126 -[[image:image-20220708101605-2.png]]
149 +(((
150 +
151 +)))
127 127  
153 +[[image:1657350248151-650.png]]
154 +
128 128  (((
129 129  
130 130  )))
131 131  
132 132  
160 +== 2.2 ​ Configure the N95S31B ==
133 133  
134 -== 2.2 ​ Configure the NSE01 ==
135 135  
163 +=== 2.2.1  Power On N95S31B ===
136 136  
165 +
166 +[[image:image-20220709150546-2.png]]
167 +
168 +
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 -)))
172 +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.
175 +* 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  
178 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
179 +
180 +N95S31B supports different communication protocol such as :
181 +
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 -)))
183 +* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
184 +* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
185 +* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
186 +* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
151 151  
188 +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]]
190 +
191 +)))
154 154  
193 +[[image:1657350625843-586.png]]
155 155  
156 156  
157 -=== 2.2.2 Insert SIM card ===
158 158  
197 +=== 2.2.3  Insert SIM card ===
198 +
199 +(((
159 159  Insert the NB-IoT Card get from your provider.
201 +)))
160 160  
203 +(((
161 161  User need to take out the NB-IoT module and insert the SIM card like below:
205 +)))
162 162  
163 163  
164 -[[image:1657249468462-536.png]]
208 +[[image:1657351240556-536.png]]
165 165  
166 166  
167 167  
168 -=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
212 +=== 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.
216 +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  
220 +[[image:1657351312545-300.png]]
176 176  
177 177  **Connection:**
178 178  
... ... @@ -192,94 +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.
240 +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]]
243 +[[image:1657329814315-101.png]]
199 199  
200 -(% 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/]]
245 +(((
246 +(% 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/]]
247 +)))
201 201  
202 202  
203 203  
204 -=== 2.2.4 Use CoAP protocol to uplink data ===
251 +=== 2.2.5  Use CoAP protocol to uplink data ===
205 205  
206 206  (% 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/]]
207 207  
208 208  
256 +(((
209 209  **Use below commands:**
258 +)))
210 210  
211 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
212 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
213 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
260 +* (((
261 +(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
262 +)))
263 +* (((
264 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
265 +)))
266 +* (((
267 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
268 +)))
214 214  
270 +(((
271 +
272 +
215 215  For parameter description, please refer to AT command set
274 +)))
216 216  
217 -[[image:1657249793983-486.png]]
276 +[[image:1657352146020-183.png]]
218 218  
219 219  
220 -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.
279 +(((
280 +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.
281 +)))
221 221  
222 -[[image:1657249831934-534.png]]
283 +[[image:1657352185396-303.png]]
223 223  
224 224  
225 225  
226 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
287 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
227 227  
228 -This feature is supported since firmware version v1.0.1
229 229  
230 -
231 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
290 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
232 232  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
233 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
292 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
234 234  
235 -[[image:1657249864775-321.png]]
294 +[[image:1657352391268-297.png]]
236 236  
237 237  
238 -[[image:1657249930215-289.png]]
297 +[[image:1657352403317-397.png]]
239 239  
240 240  
241 241  
242 -=== 2.2.6 Use MQTT protocol to uplink data ===
301 +=== 2.2.7  Use MQTT protocol to uplink data ===
243 243  
244 -This feature is supported since firmware version v110
303 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
245 245  
305 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
306 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
307 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
308 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
309 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
310 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
311 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
246 246  
247 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
248 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
249 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
250 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
251 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
252 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
253 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
313 +[[image:1657352634421-276.png]]
254 254  
255 -[[image:1657249978444-674.png]]
256 256  
316 +[[image:1657352645687-385.png]]
257 257  
258 -[[image:1657249990869-686.png]]
318 +(((
319 +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.
320 +)))
259 259  
260 260  
261 261  (((
262 -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.
324 +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.
263 263  )))
264 264  
265 265  
266 266  
267 -=== 2.2.7 Use TCP protocol to uplink data ===
329 +=== 2.2.8  Use TCP protocol to uplink data ===
268 268  
269 269  This feature is supported since firmware version v110
270 270  
271 -
272 272  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
273 273  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
274 274  
275 -[[image:1657250217799-140.png]]
336 +[[image:1657352898400-901.png]]
276 276  
277 277  
278 -[[image:1657250255956-604.png]]
339 +[[image:1657352914475-252.png]]
279 279  
280 280  
281 281  
282 -=== 2.2.8 Change Update Interval ===
343 +=== 2.2.9  Change Update Interval ===
283 283  
284 284  User can use below command to change the (% style="color:green" %)**uplink interval**.
285 285  
... ... @@ -286,205 +286,199 @@
286 286  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
287 287  
288 288  (((
289 -(% style="color:red" %)**NOTE:**
350 +
290 290  )))
291 291  
292 -(((
293 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
294 -)))
295 295  
296 296  
297 -
298 298  == 2.3  Uplink Payload ==
299 299  
300 -In this mode, uplink payload includes in total 18 bytes
301 301  
302 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
303 -|=(% style="width: 50px;" %)(((
304 -**Size(bytes)**
305 -)))|=(% 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**
306 -|(% 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"]]
358 +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.
307 307  
308 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
309 309  
361 +For example:
310 310  
311 -[[image:image-20220708111918-4.png]]
363 + (% 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.
312 312  
313 313  
314 -The payload is ASCII string, representative same HEX:
366 +The uplink payloads are composed in  ASCII String. For example:
315 315  
316 -0x72403155615900640c7817075e0a8c02f900 where:
368 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
317 317  
318 -* Device ID: 0x 724031556159 = 724031556159
319 -* Version: 0x0064=100=1.0.0
370 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
320 320  
321 -* BAT: 0x0c78 = 3192 mV = 3.192V
322 -* Singal: 0x17 = 23
323 -* Soil Moisture: 0x075e= 1886 = 18.86  %
324 -* Soil Temperature:0x0a8c =2700=27 °C
325 -* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
326 -* Interrupt: 0x00 = 0
327 327  
373 +(% style="color:red" %)**NOTE:**
328 328  
329 -== 2.4  Payload Explanation and Sensor Interface ==
375 +(% style="color:red" %)
376 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
377 +1. By default, the device will send an uplink message every 1 hour.
330 330  
331 331  
332 -=== 2.4.1  Device ID ===
333 333  
334 -By default, the Device ID equal to the last 6 bytes of IMEI.
381 +=== 2.3.1  Payload Analyze ===
335 335  
336 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
383 +N95S31B uplink payload includes in total 21 bytes
337 337  
338 -**Example:**
339 339  
340 -AT+DEUI=A84041F15612
386 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
387 +|=(% style="width: 60px;" %)(((
388 +**Size(bytes)**
389 +)))|=(% 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**
390 +|(% 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" %)(((
391 +Reserve/ Same as NBSN95 CFGMOD=1
341 341  
342 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
393 +No function here.
394 +)))|(% style="width:77px" %)(((
395 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
343 343  
397 +By SHT31
398 +)))|(% style="width:80px" %)(((
399 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
344 344  
401 +By SHT31
402 +)))
345 345  
346 -=== 2.4.2  Version Info ===
404 +(((
405 +(((
406 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
407 +)))
408 +)))
347 347  
348 -Specify the software version: 0x64=100, means firmware version 1.00.
349 349  
350 -For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
411 +[[image:1657354294009-643.png]]
351 351  
352 352  
414 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
353 353  
354 -=== 2.4.3  Battery Info ===
416 +* Device ID: 0x724031607457 = 724031607457
417 +* Version: 0x006e=110=1.1.0
355 355  
419 +* BAT: 0x0ccd = 3277 mV = 3.277V
420 +* Signal: 0x1b = 27
421 +* Model: 0x01 = 1
422 +* 0x00dc000ccc= reserve, ignore in N95S31B
423 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
424 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
425 +
356 356  (((
357 -Check the battery voltage for LSE01.
427 +
358 358  )))
359 359  
360 360  (((
361 -Ex1: 0x0B45 = 2885mV
431 +
362 362  )))
363 363  
434 +
435 +=== 2.3.2  Device ID ===
436 +
364 364  (((
365 -Ex2: 0x0B49 = 2889mV
438 +By default, the Device ID equal to the last 6 bytes of IMEI.
366 366  )))
367 367  
441 +(((
442 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
443 +)))
368 368  
445 +(((
446 +**Example:**
447 +)))
369 369  
370 -=== 2.4.4  Signal Strength ===
449 +(((
450 +AT+DEUI=A84041F15612
451 +)))
371 371  
372 -NB-IoT Network signal Strength.
453 +(((
454 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
455 +)))
373 373  
374 -**Ex1: 0x1d = 29**
375 375  
376 -(% style="color:blue" %)**0**(%%)  -113dBm or less
377 377  
378 -(% style="color:blue" %)**1**(%%)  -111dBm
459 +=== 2.3.3  Version Info ===
379 379  
380 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
381 381  
382 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
462 +These bytes include the hardware and software version.
383 383  
384 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
464 +Higher byte: Specify hardware version: always 0x00 for N95S31B
385 385  
466 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
386 386  
387 387  
388 -=== 2.4.5  Soil Moisture ===
469 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
389 389  
390 390  (((
391 -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.
472 +
392 392  )))
393 393  
394 -(((
395 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
396 -)))
397 397  
476 +=== 2.3.4  Battery Info ===
477 +
398 398  (((
399 -
479 +Ex1: 0x0B45 = 2885mV
400 400  )))
401 401  
402 402  (((
403 -(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
483 +Ex2: 0x0B49 = 2889mV
404 404  )))
405 405  
406 406  
407 407  
408 -=== 2.4.6  Soil Temperature ===
488 +=== 2.3.5  Signal Strength ===
409 409  
410 410  (((
411 - 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
491 +NB-IoT Network signal Strength.
412 412  )))
413 413  
414 414  (((
415 -**Example**:
495 +**Ex1: 0x1d = 29**
416 416  )))
417 417  
418 418  (((
419 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
499 +(% style="color:blue" %)**0**(%%)  -113dBm or less
420 420  )))
421 421  
422 422  (((
423 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
503 +(% style="color:blue" %)**1**(%%)  -111dBm
424 424  )))
425 425  
426 -
427 -
428 -=== 2.4.7  Soil Conductivity (EC) ===
429 -
430 430  (((
431 -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).
507 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
432 432  )))
433 433  
434 434  (((
435 -For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
511 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
436 436  )))
437 437  
438 438  (((
439 -Generally, the EC value of irrigation water is less than 800uS / cm.
515 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
440 440  )))
441 441  
442 -(((
443 -
444 -)))
445 445  
446 -(((
447 -
448 -)))
449 449  
450 -=== 2.4.8  Digital Interrupt ===
520 +=== 2.3.6  Temperature & Humidity ===
451 451  
452 -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.
522 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
453 453  
454 -The command is:
524 +[[image:image-20220709161741-3.png]]
455 455  
456 -(% 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]])**.**
457 457  
527 +Convert the read byte to decimal and divide it by ten.
458 458  
459 -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.
460 460  
530 +**Example:**
461 461  
462 -Example:
532 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
463 463  
464 -0x(00): Normal uplink packet.
534 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
465 465  
466 -0x(01): Interrupt Uplink Packet.
467 467  
468 468  
469 -
470 -=== 2.4.9  ​+5V Output ===
471 -
472 -NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
473 -
474 -
475 -The 5V output time can be controlled by AT Command.
476 -
477 -(% style="color:blue" %)**AT+5VT=1000**
478 -
479 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
480 -
481 -
482 -
483 483  == 2.5  Downlink Payload ==
484 484  
485 -By default, NSE01 prints the downlink payload to console port.
540 +By default, NDDS75 prints the downlink payload to console port.
486 486  
487 -[[image:image-20220708133731-5.png]]
542 +[[image:image-20220709100028-1.png]]
488 488  
489 489  
490 490  (((
... ... @@ -520,83 +520,69 @@
520 520  )))
521 521  
522 522  (((
523 -If payload = 0x04FF, it will reset the NSE01
578 +If payload = 0x04FF, it will reset the NDDS75
524 524  )))
525 525  
526 526  
527 527  * (% style="color:blue" %)**INTMOD**
528 528  
584 +(((
529 529  Downlink Payload: 06000003, Set AT+INTMOD=3
586 +)))
530 530  
531 531  
532 532  
533 533  == 2.6  ​LED Indicator ==
534 534  
535 -(((
536 -The NSE01 has an internal LED which is to show the status of different state.
537 537  
593 +The NDDS75 has an internal LED which is to show the status of different state.
538 538  
539 -* 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)
595 +
596 +* 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)
540 540  * Then the LED will be on for 1 second means device is boot normally.
541 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
598 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
542 542  * For each uplink probe, LED will be on for 500ms.
600 +
601 +(((
602 +
543 543  )))
544 544  
545 545  
546 546  
607 +== 2.7  ​Firmware Change Log ==
547 547  
548 -== 2.7  Installation in Soil ==
549 549  
550 -__**Measurement the soil surface**__
551 -
552 -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]]
553 -
554 -[[image:1657259653666-883.png]] ​
555 -
556 -
557 557  (((
558 -
559 -
560 -(((
561 -Dig a hole with diameter > 20CM.
611 +Download URL & Firmware Change log
562 562  )))
563 563  
564 564  (((
565 -Horizontal insert the probe to the soil and fill the hole for long term measurement.
615 +[[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/]]
566 566  )))
567 -)))
568 568  
569 -[[image:1654506665940-119.png]]
570 570  
571 571  (((
572 -
620 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
573 573  )))
574 574  
575 575  
576 -== 2.8  ​Firmware Change Log ==
577 577  
625 +== 2.8  ​Battery Analysis ==
578 578  
579 -Download URL & Firmware Change log
627 +=== 2.8.1  ​Battery Type ===
580 580  
581 -[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
582 582  
630 +(((
631 +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.
632 +)))
583 583  
584 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
585 -
586 -
587 -
588 -== 2.9  ​Battery Analysis ==
589 -
590 -=== 2.9.1  ​Battery Type ===
591 -
592 -
593 -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.
594 -
595 -
634 +(((
596 596  The battery is designed to last for several years depends on the actually use environment and update interval. 
636 +)))
597 597  
598 -
638 +(((
599 599  The battery related documents as below:
640 +)))
600 600  
601 601  * [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
602 602  * [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
... ... @@ -603,12 +603,12 @@
603 603  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
604 604  
605 605  (((
606 -[[image:image-20220708140453-6.png]]
647 +[[image:image-20220709101450-2.png]]
607 607  )))
608 608  
609 609  
610 610  
611 -=== 2.9.2  Power consumption Analyze ===
652 +=== 2.8.2  Power consumption Analyze ===
612 612  
613 613  (((
614 614  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.
... ... @@ -642,11 +642,11 @@
642 642  And the Life expectation in difference case will be shown on the right.
643 643  )))
644 644  
645 -[[image:image-20220708141352-7.jpeg]]
686 +[[image:image-20220709110451-3.png]]
646 646  
647 647  
648 648  
649 -=== 2.9.3  ​Battery Note ===
690 +=== 2.8.3  ​Battery Note ===
650 650  
651 651  (((
652 652  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.
... ... @@ -654,10 +654,10 @@
654 654  
655 655  
656 656  
657 -=== 2.9.4  Replace the battery ===
698 +=== 2.8.4  Replace the battery ===
658 658  
659 659  (((
660 -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).
701 +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).
661 661  )))
662 662  
663 663  
... ... @@ -672,7 +672,7 @@
672 672  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/]] 
673 673  )))
674 674  
675 -[[image:1657261278785-153.png]]
716 +[[image:1657333200519-600.png]]
676 676  
677 677  
678 678  
... ... @@ -680,7 +680,7 @@
680 680  
681 681  == 4.1  Access AT Commands ==
682 682  
683 -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/]]
724 +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/]]
684 684  
685 685  
686 686  AT+<CMD>?  : Help on <CMD>
... ... @@ -768,7 +768,7 @@
768 768  )))
769 769  
770 770  (((
771 -(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
812 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
772 772  )))
773 773  
774 774  
... ... @@ -778,25 +778,29 @@
778 778  == 6.1  ​Connection problem when uploading firmware ==
779 779  
780 780  
822 +(((
823 +**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]]
824 +)))
825 +
781 781  (% class="wikigeneratedid" %)
782 782  (((
783 -(% 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;"]]
828 +
784 784  )))
785 785  
786 786  
787 -
788 788  == 6.2  AT Command input doesn't work ==
789 789  
790 790  (((
791 791  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.
836 +
837 +
792 792  )))
793 793  
794 794  
795 -
796 796  = 7. ​ Order Info =
797 797  
798 798  
799 -Part Number**:** (% style="color:#4f81bd" %)**NSE01**
844 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
800 800  
801 801  
802 802  (% class="wikigeneratedid" %)
... ... @@ -811,8 +811,7 @@
811 811  
812 812  (% style="color:#037691" %)**Package Includes**:
813 813  
814 -
815 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
859 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
816 816  * External antenna x 1
817 817  )))
818 818  
... ... @@ -822,8 +822,10 @@
822 822  (% style="color:#037691" %)**Dimension and weight**:
823 823  
824 824  
825 -* Size: 195 x 125 x 55 mm
826 -* Weight:   420g
869 +* Device Size: 13.0 x 5 x 4.5 cm
870 +* Device Weight: 150g
871 +* Package Size / pcs : 15 x 12x 5.5 cm
872 +* Weight / pcs : 220g
827 827  )))
828 828  
829 829  (((
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