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