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