Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 114.2
edited by Xiaoling
on 2022/07/09 16:12
Change comment: There is no comment for this version
To version 59.1
edited by Xiaoling
on 2022/07/08 13:54
Change comment: Uploaded new attachment "1657259653666-883.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -N95S31B NB-IoT Temperature & Humidity Sensor User Manual
1 +NSE01 - NB-IoT Soil Moisture & EC Sensor User Manual
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:1657348034241-728.png||height="470" width="470"]]
2 +[[image:image-20220606151504-2.jpeg||height="554" width="554"]]
3 3  
4 4  
5 5  
... ... @@ -7,6 +7,10 @@
7 7  
8 8  
9 9  
10 +
11 +
12 +
13 +
10 10  **Table of Contents:**
11 11  
12 12  
... ... @@ -16,34 +16,36 @@
16 16  
17 17  = 1.  Introduction =
18 18  
19 -== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
23 +== 1.1 ​ What is LoRaWAN Soil Moisture & EC Sensor ==
20 20  
21 21  (((
22 22  
23 23  
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*.
28 +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.
25 25  
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.
30 +It can detect (% style="color:blue" %)**Soil Moisture, Soil Temperature and Soil Conductivity**(%%), and upload its value to the server wirelessly.
27 27  
28 -N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
32 +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.
29 29  
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).
34 +NSE01 are powered by (% style="color:blue" %)**8500mAh Li-SOCI2**(%%) batteries, which can be used for up to 5 years.  
31 31  
32 -
33 -~* make sure you have NB-IoT coverage locally.
34 -
35 35  
36 36  )))
37 37  
38 -[[image:1657348284168-431.png]]
39 +[[image:1654503236291-817.png]]
39 39  
40 40  
42 +[[image:1657245163077-232.png]]
41 41  
42 -== 1.2 ​ Features ==
43 43  
44 44  
46 +== 1.2 ​Features ==
47 +
48 +
45 45  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
46 -* Monitor Temperature & Humidity via SHT31
50 +* Monitor Soil Moisture
51 +* Monitor Soil Temperature
52 +* Monitor Soil Conductivity
47 47  * AT Commands to change parameters
48 48  * Uplink on periodically
49 49  * Downlink to change configure
... ... @@ -53,7 +53,6 @@
53 53  * Micro SIM card slot for NB-IoT SIM
54 54  * 8500mAh Battery for long term use
55 55  
56 -
57 57  == 1.3  Specification ==
58 58  
59 59  
... ... @@ -71,151 +71,90 @@
71 71  * - B20 @H-FDD: 800MHz
72 72  * - B28 @H-FDD: 700MHz
73 73  
74 -(% style="color:#037691" %)**Battery:**
79 +(% style="color:#037691" %)**Probe Specification:**
75 75  
81 +Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
76 76  
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
83 +[[image:image-20220708101224-1.png]]
82 82  
83 83  
86 +
84 84  == ​1.4  Applications ==
85 85  
86 -* Smart Buildings & Home Automation
87 -* Logistics and Supply Chain Management
88 -* Smart Metering
89 89  * Smart Agriculture
90 -* Smart Cities
91 -* Smart Factory
92 92  
93 93  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
94 94  ​
95 95  
96 -
97 97  == 1.5  Pin Definitions ==
98 98  
99 -N95S31B use the mother board from NBSN95 which as below.
100 100  
101 -[[image:image-20220709144723-1.png]]
97 +[[image:1657246476176-652.png]]
102 102  
103 103  
104 -=== 1.5.1 Jumper JP2 ===
105 105  
106 -Power on Device when put this jumper.
101 += 2.  Use NSE01 to communicate with IoT Server =
107 107  
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 -
135 135  == 2.1  How it works ==
136 136  
137 137  
138 138  (((
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.
107 +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.
140 140  )))
141 141  
142 142  
143 143  (((
144 -The diagram below shows the working flow in default firmware of N95S31B:
112 +The diagram below shows the working flow in default firmware of NSE01:
145 145  )))
146 146  
147 -(((
148 -
149 -)))
115 +[[image:image-20220708101605-2.png]]
150 150  
151 -[[image:1657350248151-650.png]]
152 -
153 153  (((
154 154  
155 155  )))
156 156  
157 157  
158 -== 2.2 ​ Configure the N95S31B ==
159 159  
123 +== 2.2 ​ Configure the NSE01 ==
160 160  
161 -=== 2.2.1  Power On N95S31B ===
162 162  
163 -
164 -[[image:image-20220709150546-2.png]]
165 -
166 -
167 167  === 2.2.1 Test Requirement ===
168 168  
169 169  
170 -To use N95S31B in your city, make sure meet below requirements:
129 +To use NSE01 in your city, make sure meet below requirements:
171 171  
172 172  * Your local operator has already distributed a NB-IoT Network there.
173 -* The local NB-IoT network used the band that N95S31B supports.
132 +* The local NB-IoT network used the band that NSE01 supports.
174 174  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
175 175  
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 -
180 180  (((
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(%%))
185 -
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.
187 -
188 -
136 +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
189 189  )))
190 190  
191 -[[image:1657350625843-586.png]]
192 192  
140 +[[image:1657249419225-449.png]]
193 193  
194 194  
195 -=== 2.2.3  Insert SIM card ===
196 196  
197 -(((
144 +=== 2.2.2 Insert SIM card ===
145 +
198 198  Insert the NB-IoT Card get from your provider.
199 -)))
200 200  
201 -(((
202 202  User need to take out the NB-IoT module and insert the SIM card like below:
203 -)))
204 204  
205 205  
206 -[[image:1657351240556-536.png]]
151 +[[image:1657249468462-536.png]]
207 207  
208 208  
209 209  
210 -=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
155 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
211 211  
212 212  (((
213 213  (((
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.
159 +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.
215 215  )))
216 216  )))
217 217  
218 -[[image:1657351312545-300.png]]
219 219  
220 220  **Connection:**
221 221  
... ... @@ -235,110 +235,94 @@
235 235  * Flow Control: (% style="color:green" %)**None**
236 236  
237 237  (((
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.
182 +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.
239 239  )))
240 240  
241 -[[image:1657329814315-101.png]]
185 +[[image:image-20220708110657-3.png]]
242 242  
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 -)))
187 +(% 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/]]
246 246  
247 247  
248 248  
249 -=== 2.2.5  Use CoAP protocol to uplink data ===
191 +=== 2.2.4 Use CoAP protocol to uplink data ===
250 250  
251 251  (% 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/]]
252 252  
253 253  
254 -(((
255 255  **Use below commands:**
256 -)))
257 257  
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 -)))
198 +* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
199 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
200 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
267 267  
268 -(((
269 -
270 -
271 271  For parameter description, please refer to AT command set
272 -)))
273 273  
274 -[[image:1657352146020-183.png]]
204 +[[image:1657249793983-486.png]]
275 275  
276 276  
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 -)))
207 +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.
280 280  
281 -[[image:1657352185396-303.png]]
209 +[[image:1657249831934-534.png]]
282 282  
283 283  
284 284  
285 -=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
213 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
286 286  
215 +This feature is supported since firmware version v1.0.1
287 287  
288 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
217 +
218 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
289 289  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
290 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
220 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
291 291  
292 -[[image:1657352391268-297.png]]
222 +[[image:1657249864775-321.png]]
293 293  
294 294  
295 -[[image:1657352403317-397.png]]
225 +[[image:1657249930215-289.png]]
296 296  
297 297  
298 298  
299 -=== 2.2.7  Use MQTT protocol to uplink data ===
229 +=== 2.2.6 Use MQTT protocol to uplink data ===
300 300  
301 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
231 +This feature is supported since firmware version v110
302 302  
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
310 310  
311 -[[image:1657352634421-276.png]]
234 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
235 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
236 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
237 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
238 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
239 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
240 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
312 312  
242 +[[image:1657249978444-674.png]]
313 313  
314 -[[image:1657352645687-385.png]]
315 315  
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 -)))
245 +[[image:1657249990869-686.png]]
319 319  
320 320  
321 321  (((
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.
249 +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.
323 323  )))
324 324  
325 325  
326 326  
327 -=== 2.2.8  Use TCP protocol to uplink data ===
254 +=== 2.2.7 Use TCP protocol to uplink data ===
328 328  
329 329  This feature is supported since firmware version v110
330 330  
258 +
331 331  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
332 332  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
333 333  
334 -[[image:1657352898400-901.png]]
262 +[[image:1657250217799-140.png]]
335 335  
336 336  
337 -[[image:1657352914475-252.png]]
265 +[[image:1657250255956-604.png]]
338 338  
339 339  
340 340  
341 -=== 2.2.9  Change Update Interval ===
269 +=== 2.2.8 Change Update Interval ===
342 342  
343 343  User can use below command to change the (% style="color:green" %)**uplink interval**.
344 344  
... ... @@ -345,198 +345,158 @@
345 345  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
346 346  
347 347  (((
348 -
276 +(% style="color:red" %)**NOTE:**
349 349  )))
350 350  
279 +(((
280 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
281 +)))
351 351  
352 352  
284 +
353 353  == 2.3  Uplink Payload ==
354 354  
287 +In this mode, uplink payload includes in total 18 bytes
355 355  
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.
289 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
290 +|=(% style="width: 50px;" %)(((
291 +**Size(bytes)**
292 +)))|=(% 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**
293 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H"]]|(% style="width:41px" %)[[Ver>>||anchor="H"]]|(% style="width:46px" %)[[BAT>>||anchor="H"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H"]]|(% style="width:108px" %)[[Soil Moisture>>||anchor="H"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H"]]
357 357  
295 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
358 358  
359 -For example:
360 360  
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.
298 +[[image:image-20220708111918-4.png]]
362 362  
363 363  
364 -The uplink payloads are composed in  ASCII String. For example:
301 +The payload is ASCII string, representative same HEX:
365 365  
366 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
303 +0x72403155615900640c7817075e0a8c02f900 where:
367 367  
368 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
305 +* Device ID: 0x 724031556159 = 724031556159
306 +* Version: 0x0064=100=1.0.0
369 369  
308 +* BAT: 0x0c78 = 3192 mV = 3.192V
309 +* Singal: 0x17 = 23
310 +* Soil Moisture: 0x075e= 1886 = 18.86  %
311 +* Soil Temperature:0x0a8c =2700=27 °C
312 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
313 +* Interrupt: 0x00 = 0
370 370  
371 -(% style="color:red" %)**NOTE:**
372 372  
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.
316 +== 2.4  Payload Explanation and Sensor Interface ==
376 376  
377 377  
319 +=== 2.4.1  Device ID ===
378 378  
321 +By default, the Device ID equal to the last 6 bytes of IMEI.
379 379  
380 -=== 2.3.1  Payload Analyze ===
323 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
381 381  
382 -N95S31B uplink payload includes in total 21 bytes
325 +**Example:**
383 383  
327 +AT+DEUI=A84041F15612
384 384  
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
329 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
391 391  
392 -No function here.
393 -)))|(% style="width:77px" %)(((
394 -[[Temperature >>||anchor="H2.4.5A0Distance"]]
395 395  
396 -By SHT31
397 -)))|(% style="width:80px" %)(((
398 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
399 399  
400 -By SHT31
401 -)))
333 +=== 2.4.2  Version Info ===
402 402  
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 -)))
335 +Specify the software version: 0x64=100, means firmware version 1.00.
408 408  
337 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
409 409  
410 -[[image:1657354294009-643.png]]
411 411  
340 +
341 +=== 2.4.3  Battery Info ===
342 +
412 412  (((
413 -The payload is ASCII string, representative same HEX:
344 +Check the battery voltage for LSE01.
414 414  )))
415 415  
416 416  (((
417 -0x72403155615900640c6c19029200 where:
348 +Ex1: 0x0B45 = 2885mV
418 418  )))
419 419  
420 -* (((
421 -Device ID: 0x724031556159 = 724031556159
351 +(((
352 +Ex2: 0x0B49 = 2889mV
422 422  )))
423 -* (((
424 -Version: 0x0064=100=1.0.0
425 -)))
426 426  
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
438 438  
439 439  
357 +=== 2.4.4  Signal Strength ===
440 440  
441 -
442 -)))
359 +NB-IoT Network signal Strength.
443 443  
444 -== 2.4  Payload Explanation and Sensor Interface ==
361 +**Ex1: 0x1d = 29**
445 445  
363 +(% style="color:blue" %)**0**(%%)  -113dBm or less
446 446  
447 -=== 2.4.1  Device ID ===
365 +(% style="color:blue" %)**1**(%%)  -111dBm
448 448  
449 -(((
450 -By default, the Device ID equal to the last 6 bytes of IMEI.
451 -)))
367 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
452 452  
453 -(((
454 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
455 -)))
369 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
456 456  
457 -(((
458 -**Example:**
459 -)))
371 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
460 460  
461 -(((
462 -AT+DEUI=A84041F15612
463 -)))
464 464  
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 -)))
468 468  
375 +=== 2.4.5  Soil Moisture ===
469 469  
470 -
471 -=== 2.4.2  Version Info ===
472 -
473 473  (((
474 -Specify the software version: 0x64=100, means firmware version 1.00.
378 +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.
475 475  )))
476 476  
477 477  (((
478 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
382 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
479 479  )))
480 480  
481 -
482 -
483 -=== 2.4.3  Battery Info ===
484 -
485 485  (((
486 -Ex1: 0x0B45 = 2885mV
386 +
487 487  )))
488 488  
489 489  (((
490 -Ex2: 0x0B49 = 2889mV
390 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
491 491  )))
492 492  
493 493  
494 494  
495 -=== 2.4.4  Signal Strength ===
395 +=== 2.4.6  Soil Temperature ===
496 496  
497 497  (((
498 -NB-IoT Network signal Strength.
398 + 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
499 499  )))
500 500  
501 501  (((
502 -**Ex1: 0x1d = 29**
402 +**Example**:
503 503  )))
504 504  
505 505  (((
506 -(% style="color:blue" %)**0**(%%)  -113dBm or less
406 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
507 507  )))
508 508  
509 509  (((
510 -(% style="color:blue" %)**1**(%%)  -111dBm
410 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
511 511  )))
512 512  
513 -(((
514 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
515 -)))
516 516  
517 -(((
518 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
519 -)))
520 520  
415 +=== 2.4.7  Soil Conductivity (EC) ===
416 +
521 521  (((
522 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
418 +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).
523 523  )))
524 524  
525 -
526 -
527 -=== 2.4.5  Distance ===
528 -
529 -Get the distance. Flat object range 280mm - 7500mm.
530 -
531 531  (((
532 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
422 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
533 533  )))
534 534  
535 535  (((
536 -(((
537 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
426 +Generally, the EC value of irrigation water is less than 800uS / cm.
538 538  )))
539 -)))
540 540  
541 541  (((
542 542  
... ... @@ -546,68 +546,47 @@
546 546  
547 547  )))
548 548  
549 -=== 2.4.6  Digital Interrupt ===
437 +=== 2.4.8  Digital Interrupt ===
550 550  
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 -)))
439 +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.
554 554  
555 -(((
556 556  The command is:
557 -)))
558 558  
559 -(((
560 560  (% 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 -)))
562 562  
563 563  
564 -(((
565 -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 -)))
446 +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.
567 567  
568 568  
569 -(((
570 570  Example:
571 -)))
572 572  
573 -(((
574 574  0x(00): Normal uplink packet.
575 -)))
576 576  
577 -(((
578 578  0x(01): Interrupt Uplink Packet.
579 -)))
580 580  
581 581  
582 582  
583 -=== 2.4.7  ​+5V Output ===
457 +=== 2.4.9  ​+5V Output ===
584 584  
585 -(((
586 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
587 -)))
459 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
588 588  
589 589  
590 -(((
591 591  The 5V output time can be controlled by AT Command.
592 -)))
593 593  
594 -(((
595 595  (% style="color:blue" %)**AT+5VT=1000**
596 -)))
597 597  
598 -(((
599 599  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
600 -)))
601 601  
602 602  
603 603  
604 604  == 2.5  Downlink Payload ==
605 605  
606 -By default, NDDS75 prints the downlink payload to console port.
472 +By default, LSE50 prints the downlink payload to console port.
607 607  
608 -[[image:image-20220709100028-1.png]]
474 +[[image:image-20220708133731-5.png]]
609 609  
610 610  
477 +
611 611  (((
612 612  (% style="color:blue" %)**Examples:**
613 613  )))
... ... @@ -621,7 +621,7 @@
621 621  )))
622 622  
623 623  (((
624 -If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
491 +If the payload=0100003C, it means set the END Node’s TDC to 0x00003C=60(S), while type code is 01.
625 625  )))
626 626  
627 627  (((
... ... @@ -641,120 +641,432 @@
641 641  )))
642 642  
643 643  (((
644 -If payload = 0x04FF, it will reset the NDDS75
511 +If payload = 0x04FF, it will reset the LSE01
645 645  )))
646 646  
647 647  
648 -* (% style="color:blue" %)**INTMOD**
515 +* (% style="color:blue" %)**CFM**
649 649  
517 +Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0
518 +
519 +
520 +
521 +== 2.6 ​Show Data in DataCake IoT Server ==
522 +
650 650  (((
651 -Downlink Payload: 06000003, Set AT+INTMOD=3
524 +[[DATACAKE>>url:https://datacake.co/]] provides a human friendly interface to show the sensor data, once we have data in TTN, we can use [[DATACAKE>>url:https://datacake.co/]] to connect to TTN and see the data in DATACAKE. Below are the steps:
652 652  )))
653 653  
527 +(((
528 +
529 +)))
654 654  
531 +(((
532 +(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the network at this time.
533 +)))
655 655  
656 -== 2.6  ​LED Indicator ==
535 +(((
536 +(% style="color:blue" %)**Step 2**(%%):  To configure the Application to forward data to DATACAKE you will need to add integration. To add the DATACAKE integration, perform the following steps:
537 +)))
657 657  
658 658  
659 -The NDDS75 has an internal LED which is to show the status of different state.
540 +[[image:1654505857935-743.png]]
660 660  
661 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)
663 -* Then the LED will be on for 1 second means device is boot normally.
664 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
665 -* For each uplink probe, LED will be on for 500ms.
543 +[[image:1654505874829-548.png]]
666 666  
667 -(((
668 -
669 -)))
670 670  
546 +(% style="color:blue" %)**Step 3**(%%)**:**  Create an account or log in Datacake.
671 671  
548 +(% style="color:blue" %)**Step 4**(%%)**:**  Search the LSE01 and add DevEUI.
672 672  
673 -== 2.7  ​Firmware Change Log ==
674 674  
551 +[[image:1654505905236-553.png]]
675 675  
676 -(((
677 -Download URL & Firmware Change log
678 -)))
679 679  
680 -(((
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/]]
682 -)))
554 +After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
683 683  
556 +[[image:1654505925508-181.png]]
684 684  
685 -(((
686 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
687 -)))
688 688  
689 689  
560 +== 2.7 Frequency Plans ==
690 690  
691 -== 2.8  ​Battery Analysis ==
562 +The LSE01 uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets.
692 692  
693 -=== 2.8.1  ​Battery Type ===
694 694  
565 +=== 2.7.1 EU863-870 (EU868) ===
695 695  
567 +(% style="color:#037691" %)** Uplink:**
568 +
569 +868.1 - SF7BW125 to SF12BW125
570 +
571 +868.3 - SF7BW125 to SF12BW125 and SF7BW250
572 +
573 +868.5 - SF7BW125 to SF12BW125
574 +
575 +867.1 - SF7BW125 to SF12BW125
576 +
577 +867.3 - SF7BW125 to SF12BW125
578 +
579 +867.5 - SF7BW125 to SF12BW125
580 +
581 +867.7 - SF7BW125 to SF12BW125
582 +
583 +867.9 - SF7BW125 to SF12BW125
584 +
585 +868.8 - FSK
586 +
587 +
588 +(% style="color:#037691" %)** Downlink:**
589 +
590 +Uplink channels 1-9 (RX1)
591 +
592 +869.525 - SF9BW125 (RX2 downlink only)
593 +
594 +
595 +
596 +=== 2.7.2 US902-928(US915) ===
597 +
598 +Used in USA, Canada and South America. Default use CHE=2
599 +
600 +(% style="color:#037691" %)**Uplink:**
601 +
602 +903.9 - SF7BW125 to SF10BW125
603 +
604 +904.1 - SF7BW125 to SF10BW125
605 +
606 +904.3 - SF7BW125 to SF10BW125
607 +
608 +904.5 - SF7BW125 to SF10BW125
609 +
610 +904.7 - SF7BW125 to SF10BW125
611 +
612 +904.9 - SF7BW125 to SF10BW125
613 +
614 +905.1 - SF7BW125 to SF10BW125
615 +
616 +905.3 - SF7BW125 to SF10BW125
617 +
618 +
619 +(% style="color:#037691" %)**Downlink:**
620 +
621 +923.3 - SF7BW500 to SF12BW500
622 +
623 +923.9 - SF7BW500 to SF12BW500
624 +
625 +924.5 - SF7BW500 to SF12BW500
626 +
627 +925.1 - SF7BW500 to SF12BW500
628 +
629 +925.7 - SF7BW500 to SF12BW500
630 +
631 +926.3 - SF7BW500 to SF12BW500
632 +
633 +926.9 - SF7BW500 to SF12BW500
634 +
635 +927.5 - SF7BW500 to SF12BW500
636 +
637 +923.3 - SF12BW500(RX2 downlink only)
638 +
639 +
640 +
641 +=== 2.7.3 CN470-510 (CN470) ===
642 +
643 +Used in China, Default use CHE=1
644 +
645 +(% style="color:#037691" %)**Uplink:**
646 +
647 +486.3 - SF7BW125 to SF12BW125
648 +
649 +486.5 - SF7BW125 to SF12BW125
650 +
651 +486.7 - SF7BW125 to SF12BW125
652 +
653 +486.9 - SF7BW125 to SF12BW125
654 +
655 +487.1 - SF7BW125 to SF12BW125
656 +
657 +487.3 - SF7BW125 to SF12BW125
658 +
659 +487.5 - SF7BW125 to SF12BW125
660 +
661 +487.7 - SF7BW125 to SF12BW125
662 +
663 +
664 +(% style="color:#037691" %)**Downlink:**
665 +
666 +506.7 - SF7BW125 to SF12BW125
667 +
668 +506.9 - SF7BW125 to SF12BW125
669 +
670 +507.1 - SF7BW125 to SF12BW125
671 +
672 +507.3 - SF7BW125 to SF12BW125
673 +
674 +507.5 - SF7BW125 to SF12BW125
675 +
676 +507.7 - SF7BW125 to SF12BW125
677 +
678 +507.9 - SF7BW125 to SF12BW125
679 +
680 +508.1 - SF7BW125 to SF12BW125
681 +
682 +505.3 - SF12BW125 (RX2 downlink only)
683 +
684 +
685 +
686 +=== 2.7.4 AU915-928(AU915) ===
687 +
688 +Default use CHE=2
689 +
690 +(% style="color:#037691" %)**Uplink:**
691 +
692 +916.8 - SF7BW125 to SF12BW125
693 +
694 +917.0 - SF7BW125 to SF12BW125
695 +
696 +917.2 - SF7BW125 to SF12BW125
697 +
698 +917.4 - SF7BW125 to SF12BW125
699 +
700 +917.6 - SF7BW125 to SF12BW125
701 +
702 +917.8 - SF7BW125 to SF12BW125
703 +
704 +918.0 - SF7BW125 to SF12BW125
705 +
706 +918.2 - SF7BW125 to SF12BW125
707 +
708 +
709 +(% style="color:#037691" %)**Downlink:**
710 +
711 +923.3 - SF7BW500 to SF12BW500
712 +
713 +923.9 - SF7BW500 to SF12BW500
714 +
715 +924.5 - SF7BW500 to SF12BW500
716 +
717 +925.1 - SF7BW500 to SF12BW500
718 +
719 +925.7 - SF7BW500 to SF12BW500
720 +
721 +926.3 - SF7BW500 to SF12BW500
722 +
723 +926.9 - SF7BW500 to SF12BW500
724 +
725 +927.5 - SF7BW500 to SF12BW500
726 +
727 +923.3 - SF12BW500(RX2 downlink only)
728 +
729 +
730 +
731 +=== 2.7.5 AS920-923 & AS923-925 (AS923) ===
732 +
733 +(% style="color:#037691" %)**Default Uplink channel:**
734 +
735 +923.2 - SF7BW125 to SF10BW125
736 +
737 +923.4 - SF7BW125 to SF10BW125
738 +
739 +
740 +(% style="color:#037691" %)**Additional Uplink Channel**:
741 +
742 +(OTAA mode, channel added by JoinAccept message)
743 +
744 +(% style="color:#037691" %)**AS920~~AS923 for Japan, Malaysia, Singapore**:
745 +
746 +922.2 - SF7BW125 to SF10BW125
747 +
748 +922.4 - SF7BW125 to SF10BW125
749 +
750 +922.6 - SF7BW125 to SF10BW125
751 +
752 +922.8 - SF7BW125 to SF10BW125
753 +
754 +923.0 - SF7BW125 to SF10BW125
755 +
756 +922.0 - SF7BW125 to SF10BW125
757 +
758 +
759 +(% style="color:#037691" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**:
760 +
761 +923.6 - SF7BW125 to SF10BW125
762 +
763 +923.8 - SF7BW125 to SF10BW125
764 +
765 +924.0 - SF7BW125 to SF10BW125
766 +
767 +924.2 - SF7BW125 to SF10BW125
768 +
769 +924.4 - SF7BW125 to SF10BW125
770 +
771 +924.6 - SF7BW125 to SF10BW125
772 +
773 +
774 +(% style="color:#037691" %)** Downlink:**
775 +
776 +Uplink channels 1-8 (RX1)
777 +
778 +923.2 - SF10BW125 (RX2)
779 +
780 +
781 +
782 +=== 2.7.6 KR920-923 (KR920) ===
783 +
784 +Default channel:
785 +
786 +922.1 - SF7BW125 to SF12BW125
787 +
788 +922.3 - SF7BW125 to SF12BW125
789 +
790 +922.5 - SF7BW125 to SF12BW125
791 +
792 +
793 +(% style="color:#037691" %)**Uplink: (OTAA mode, channel added by JoinAccept message)**
794 +
795 +922.1 - SF7BW125 to SF12BW125
796 +
797 +922.3 - SF7BW125 to SF12BW125
798 +
799 +922.5 - SF7BW125 to SF12BW125
800 +
801 +922.7 - SF7BW125 to SF12BW125
802 +
803 +922.9 - SF7BW125 to SF12BW125
804 +
805 +923.1 - SF7BW125 to SF12BW125
806 +
807 +923.3 - SF7BW125 to SF12BW125
808 +
809 +
810 +(% style="color:#037691" %)**Downlink:**
811 +
812 +Uplink channels 1-7(RX1)
813 +
814 +921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
815 +
816 +
817 +
818 +=== 2.7.7 IN865-867 (IN865) ===
819 +
820 +(% style="color:#037691" %)** Uplink:**
821 +
822 +865.0625 - SF7BW125 to SF12BW125
823 +
824 +865.4025 - SF7BW125 to SF12BW125
825 +
826 +865.9850 - SF7BW125 to SF12BW125
827 +
828 +
829 +(% style="color:#037691" %) **Downlink:**
830 +
831 +Uplink channels 1-3 (RX1)
832 +
833 +866.550 - SF10BW125 (RX2)
834 +
835 +
836 +
837 +
838 +== 2.8 LED Indicator ==
839 +
840 +The LSE01 has an internal LED which is to show the status of different state.
841 +
842 +* Blink once when device power on.
843 +* Solid ON for 5 seconds once device successful Join the network.
844 +* Blink once when device transmit a packet.
845 +
846 +== 2.9 Installation in Soil ==
847 +
848 +**Measurement the soil surface**
849 +
850 +
851 +[[image:1654506634463-199.png]] ​
852 +
696 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.
854 +(((
855 +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.
698 698  )))
857 +)))
699 699  
859 +
860 +
861 +[[image:1654506665940-119.png]]
862 +
700 700  (((
701 -The battery is designed to last for several years depends on the actually use environment and update interval. 
864 +Dig a hole with diameter > 20CM.
702 702  )))
703 703  
704 704  (((
705 -The battery related documents as below:
868 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
706 706  )))
707 707  
708 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
709 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
710 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
711 711  
872 +== 2.10 ​Firmware Change Log ==
873 +
712 712  (((
713 -[[image:image-20220709101450-2.png]]
875 +**Firmware download link:**
714 714  )))
715 715  
878 +(((
879 +[[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/]]
880 +)))
716 716  
882 +(((
883 +
884 +)))
717 717  
718 -=== 2.8.2  Power consumption Analyze ===
886 +(((
887 +**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
888 +)))
719 719  
720 720  (((
721 -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.
891 +
722 722  )))
723 723  
894 +(((
895 +**V1.0.**
896 +)))
724 724  
725 725  (((
726 -Instruction to use as below:
899 +Release
727 727  )))
728 728  
902 +
903 +== 2.11 ​Battery Analysis ==
904 +
905 +=== 2.11.1 ​Battery Type ===
906 +
729 729  (((
730 -(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
908 +The LSE01 battery is a combination of a 4000mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-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.
731 731  )))
732 732  
911 +(((
912 +The battery is designed to last for more than 5 years for the LSN50.
913 +)))
733 733  
734 734  (((
735 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
916 +(((
917 +The battery-related documents are as below:
736 736  )))
919 +)))
737 737  
738 738  * (((
739 -Product Model
922 +[[Battery Dimension>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
740 740  )))
741 741  * (((
742 -Uplink Interval
925 +[[Lithium-Thionyl Chloride Battery  datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
743 743  )))
744 744  * (((
745 -Working Mode
928 +[[Lithium-ion Battery-Capacitor datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]], [[Tech Spec>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]]
746 746  )))
747 747  
748 -(((
749 -And the Life expectation in difference case will be shown on the right.
750 -)))
931 + [[image:image-20220610172436-1.png]]
751 751  
752 -[[image:image-20220709110451-3.png]]
753 753  
754 754  
935 +=== 2.11.2 ​Battery Note ===
755 755  
756 -=== 2.8.3  ​Battery Note ===
757 -
758 758  (((
759 759  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.
760 760  )))
... ... @@ -761,169 +761,302 @@
761 761  
762 762  
763 763  
764 -=== 2.8.4  Replace the battery ===
943 +=== 2.11.3 Replace the battery ===
765 765  
766 766  (((
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).
946 +If Battery is lower than 2.7v, user should replace the battery of LSE01.
768 768  )))
769 769  
770 -
771 -
772 -= 3. ​ Access NB-IoT Module =
773 -
774 774  (((
775 -Users can directly access the AT command set of the NB-IoT module.
950 +You can change the battery in the LSE01.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won’t be voltage drop between battery and main board.
776 776  )))
777 777  
778 778  (((
779 -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/]] 
954 +The default battery pack of LSE01 includes a ER18505 plus super capacitor. If user can’t find this pack locally, they can find ER18505 or equivalence, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes)
780 780  )))
781 781  
782 -[[image:1657333200519-600.png]]
783 783  
784 784  
959 += 3. ​Using the AT Commands =
785 785  
786 -= 4.  Using the AT Commands =
961 +== 3.1 Access AT Commands ==
787 787  
788 -== 4.1  Access AT Commands ==
789 789  
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/]]
964 +LSE01 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LSE01 for using AT command, as below.
791 791  
966 +[[image:1654501986557-872.png||height="391" width="800"]]
792 792  
793 -AT+<CMD>?  : Help on <CMD>
794 794  
795 -AT+<CMD>         : Run <CMD>
969 +Or if you have below board, use below connection:
796 796  
797 -AT+<CMD>=<value> : Set the value
798 798  
799 -AT+<CMD>=?  : Get the value
972 +[[image:1654502005655-729.png||height="503" width="801"]]
800 800  
801 801  
975 +
976 +In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LSE01. LSE01 will output system info once power on as below:
977 +
978 +
979 + [[image:1654502050864-459.png||height="564" width="806"]]
980 +
981 +
982 +Below are the available commands, a more detailed AT Command manual can be found at [[AT Command Manual>>https://www.dropbox.com/sh/qr6vproz4z4kzjz/AAAD48h3OyWrU1hq_Cqm8jIwa?dl=0]]: [[https:~~/~~/www.dropbox.com/sh/qr6vproz4z4kzjz/AAAD48h3OyWrU1hq_Cqm8jIwa?dl=0>>https://www.dropbox.com/sh/qr6vproz4z4kzjz/AAAD48h3OyWrU1hq_Cqm8jIwa?dl=0]]
983 +
984 +
985 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%) : Help on <CMD>
986 +
987 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD> **(%%) : Run <CMD>
988 +
989 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=<value>**(%%) : Set the value
990 +
991 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=?**(%%)  : Get the value
992 +
993 +
802 802  (% style="color:#037691" %)**General Commands**(%%)      
803 803  
804 -AT  : Attention       
996 +(% style="background-color:#dcdcdc" %)**AT**(%%)  : Attention       
805 805  
806 -AT?  : Short Help     
998 +(% style="background-color:#dcdcdc" %)**AT?**(%%)  : Short Help     
807 807  
808 -ATZ  : MCU Reset    
1000 +(% style="background-color:#dcdcdc" %)**ATZ**(%%)  : MCU Reset    
809 809  
810 -AT+TDC  : Application Data Transmission Interval
1002 +(% style="background-color:#dcdcdc" %)**AT+TDC**(%%)  : Application Data Transmission Interval 
811 811  
812 -AT+CFG  : Print all configurations
813 813  
814 -AT+CFGMOD           : Working mode selection
1005 +(% style="color:#037691" %)**Keys, IDs and EUIs management**
815 815  
816 -AT+INTMOD            : Set the trigger interrupt mode
1007 +(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%)              : Application EUI      
817 817  
818 -AT+5VT  : Set extend the time of 5V power  
1009 +(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%)              : Application Key     
819 819  
820 -AT+PRO  : Choose agreement
1011 +(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%)            : Application Session Key
821 821  
822 -AT+WEIGRE  : Get weight or set weight to 0
1013 +(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%)              : Device Address     
823 823  
824 -AT+WEIGAP  : Get or Set the GapValue of weight
1015 +(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%)                   : Device EUI     
825 825  
826 -AT+RXDL  : Extend the sending and receiving time
1017 +(% style="background-color:#dcdcdc" %)**AT+NWKID**(%%)               : Network ID (You can enter this command change only after successful network connection) 
827 827  
828 -AT+CNTFAC  : Get or set counting parameters
1019 +(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%)          : Network Session Key Joining and sending date on LoRa network  
829 829  
830 -AT+SERVADDR  : Server Address
1021 +(% style="background-color:#dcdcdc" %)**AT+CFM**(%%)  : Confirm Mode       
831 831  
1023 +(% style="background-color:#dcdcdc" %)**AT+CFS**(%%)                     : Confirm Status       
832 832  
833 -(% style="color:#037691" %)**COAP Management**      
1025 +(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%)  : Join LoRa? Network       
834 834  
835 -AT+URI            : Resource parameters
1027 +(% style="background-color:#dcdcdc" %)**AT+NJM**(%%)  : LoRa? Network Join Mode    
836 836  
1029 +(% style="background-color:#dcdcdc" %)**AT+NJS**(%%)                     : LoRa? Network Join Status    
837 837  
838 -(% style="color:#037691" %)**UDP Management**
1031 +(% style="background-color:#dcdcdc" %)**AT+RECV**(%%)                  : Print Last Received Data in Raw Format
839 839  
840 -AT+CFM          : Upload confirmation mode (only valid for UDP)
1033 +(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%)                : Print Last Received Data in Binary Format      
841 841  
1035 +(% style="background-color:#dcdcdc" %)**AT+SEND**(%%)                  : Send Text Data      
842 842  
843 -(% style="color:#037691" %)**MQTT Management**
1037 +(% style="background-color:#dcdcdc" %)**AT+SENB**(%%)                  : Send Hexadecimal Data
844 844  
845 -AT+CLIENT               : Get or Set MQTT client
846 846  
847 -AT+UNAME  : Get or Set MQTT Username
1040 +(% style="color:#037691" %)**LoRa Network Management**
848 848  
849 -AT+PWD                  : Get or Set MQTT password
1042 +(% style="background-color:#dcdcdc" %)**AT+ADR**(%%)          : Adaptive Rate
850 850  
851 -AT+PUBTOPIC  : Get or Set MQTT publish topic
1044 +(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%)  : LoRa Class(Currently only support class A
852 852  
853 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
1046 +(% style="background-color:#dcdcdc" %)**AT+DCS**(%%)  : Duty Cycle Setting 
854 854  
1048 +(% style="background-color:#dcdcdc" %)**AT+DR**(%%)  : Data Rate (Can Only be Modified after ADR=0)     
855 855  
856 -(% style="color:#037691" %)**Information**          
1050 +(% style="background-color:#dcdcdc" %)**AT+FCD**(%%)  : Frame Counter Downlink       
857 857  
858 -AT+FDR  : Factory Data Reset
1052 +(% style="background-color:#dcdcdc" %)**AT+FCU**(%%)  : Frame Counter Uplink   
859 859  
860 -AT+PWORD  : Serial Access Password
1054 +(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%)  : Join Accept Delay1
861 861  
1056 +(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%)  : Join Accept Delay2
862 862  
1058 +(% style="background-color:#dcdcdc" %)**AT+PNM**(%%)  : Public Network Mode   
863 863  
864 -= ​5.  FAQ =
1060 +(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%)  : Receive Delay1      
865 865  
866 -== 5.1 ​ How to Upgrade Firmware ==
1062 +(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%)  : Receive Delay2      
867 867  
1064 +(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%)  : Rx2 Window Data Rate 
868 868  
1066 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%)  : Rx2 Window Frequency
1067 +
1068 +(% style="background-color:#dcdcdc" %)**AT+TXP**(%%)  : Transmit Power
1069 +
1070 +(% style="background-color:#dcdcdc" %)**AT+ MOD**(%%)  : Set work mode
1071 +
1072 +
1073 +(% style="color:#037691" %)**Information** 
1074 +
1075 +(% style="background-color:#dcdcdc" %)**AT+RSSI**(%%)           : RSSI of the Last Received Packet   
1076 +
1077 +(% style="background-color:#dcdcdc" %)**AT+SNR**(%%)           : SNR of the Last Received Packet   
1078 +
1079 +(% style="background-color:#dcdcdc" %)**AT+VER**(%%)           : Image Version and Frequency Band       
1080 +
1081 +(% style="background-color:#dcdcdc" %)**AT+FDR**(%%)           : Factory Data Reset
1082 +
1083 +(% style="background-color:#dcdcdc" %)**AT+PORT**(%%)  : Application Port    
1084 +
1085 +(% style="background-color:#dcdcdc" %)**AT+CHS**(%%)  : Get or Set Frequency (Unit: Hz) for Single Channel Mode
1086 +
1087 + (% style="background-color:#dcdcdc" %)**AT+CHE**(%%)  : Get or Set eight channels mode, Only for US915, AU915, CN470
1088 +
1089 +
1090 += ​4. FAQ =
1091 +
1092 +== 4.1 ​How to change the LoRa Frequency Bands/Region? ==
1093 +
869 869  (((
870 -User can upgrade the firmware for 1) bug fix, 2) new feature release.
1095 +You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]].
1096 +When downloading the images, choose the required image file for download. ​
871 871  )))
872 872  
873 873  (((
874 -Please see this link for how to upgrade:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
1100 +
875 875  )))
876 876  
877 877  (((
878 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
1104 +How to set up LSE01 to work in 8 channel mode By default, the frequency bands US915, AU915, CN470 work in 72 frequencies. Many gateways are 8 channel gateways, and in this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies.
879 879  )))
880 880  
1107 +(((
1108 +
1109 +)))
881 881  
1111 +(((
1112 +You can configure the end node to work in 8 channel mode by using the AT+CHE command. The 500kHz channels are always included for OTAA.
1113 +)))
882 882  
883 -= 6.  Trouble Shooting =
1115 +(((
1116 +
1117 +)))
884 884  
885 -== 6.1  ​Connection problem when uploading firmware ==
1119 +(((
1120 +For example, in **US915** band, the frequency table is as below. By default, the end node will use all channels (0~~71) for OTAA Join process. After the OTAA Join, the end node will use these all channels (0~~71) to send uplink packets.
1121 +)))
886 886  
1123 +[[image:image-20220606154726-3.png]]
887 887  
1125 +
1126 +When you use the TTN network, the US915 frequency bands use are:
1127 +
1128 +* 903.9 - SF7BW125 to SF10BW125
1129 +* 904.1 - SF7BW125 to SF10BW125
1130 +* 904.3 - SF7BW125 to SF10BW125
1131 +* 904.5 - SF7BW125 to SF10BW125
1132 +* 904.7 - SF7BW125 to SF10BW125
1133 +* 904.9 - SF7BW125 to SF10BW125
1134 +* 905.1 - SF7BW125 to SF10BW125
1135 +* 905.3 - SF7BW125 to SF10BW125
1136 +* 904.6 - SF8BW500
1137 +
888 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]]
1139 +Because the end node is now hopping in 72 frequency, it makes it difficult for the devices to Join the TTN network and uplink data. To solve this issue, you can access the device via the AT commands and run:
1140 +
1141 +* (% style="color:#037691" %)**AT+CHE=2**
1142 +* (% style="color:#037691" %)**ATZ**
890 890  )))
891 891  
892 -(% class="wikigeneratedid" %)
893 893  (((
894 894  
1147 +
1148 +to set the end node to work in 8 channel mode. The device will work in Channel 8-15 & 64-71 for OTAA, and channel 8-15 for Uplink.
895 895  )))
896 896  
1151 +(((
1152 +
1153 +)))
897 897  
898 -== 6.2  AT Command input doesn't work ==
1155 +(((
1156 +The **AU915** band is similar. Below are the AU915 Uplink Channels.
1157 +)))
899 899  
1159 +[[image:image-20220606154825-4.png]]
1160 +
1161 +
1162 +== 4.2 ​Can I calibrate LSE01 to different soil types? ==
1163 +
1164 +LSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/&file=Calibrate_to_other_Soil_20220605.pdf]].
1165 +
1166 +
1167 += 5. Trouble Shooting =
1168 +
1169 +== 5.1 ​Why I can't join TTN in US915 / AU915 bands? ==
1170 +
1171 +It is due to channel mapping. Please see the [[Eight Channel Mode>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.19EightChannelMode"]] section above for details.
1172 +
1173 +
1174 +== 5.2 AT Command input doesn't work ==
1175 +
900 900  (((
901 901  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.
1178 +)))
902 902  
903 -
1180 +
1181 +== 5.3 Device rejoin in at the second uplink packet ==
1182 +
1183 +(% style="color:#4f81bd" %)**Issue describe as below:**
1184 +
1185 +[[image:1654500909990-784.png]]
1186 +
1187 +
1188 +(% style="color:#4f81bd" %)**Cause for this issue:**
1189 +
1190 +(((
1191 +The fuse on LSE01 is not large enough, some of the soil probe require large current up to 5v 800mA, in a short pulse. When this happen, it cause the device reboot so user see rejoin.
904 904  )))
905 905  
906 906  
907 -= 7. ​ Order Info =
1195 +(% style="color:#4f81bd" %)**Solution: **
908 908  
1197 +All new shipped LSE01 after 2020-May-30 will have this to fix. For the customer who see this issue, please bypass the fuse as below:
909 909  
910 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1199 +[[image:1654500929571-736.png||height="458" width="832"]]
911 911  
912 912  
1202 += 6. ​Order Info =
1203 +
1204 +
1205 +Part Number**:** (% style="color:#4f81bd" %)**LSE01-XX-YY**
1206 +
1207 +
1208 +(% style="color:#4f81bd" %)**XX**(%%)**:** The default frequency band
1209 +
1210 +* (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band
1211 +* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
1212 +* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
1213 +* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
1214 +* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
1215 +* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
1216 +* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1217 +* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1218 +
1219 +(% style="color:#4f81bd" %)**YY**(%%)**: **Battery Option
1220 +
1221 +* (% style="color:red" %)**4**(%%): 4000mAh battery
1222 +* (% style="color:red" %)**8**(%%): 8500mAh battery
1223 +
913 913  (% class="wikigeneratedid" %)
914 914  (((
915 915  
916 916  )))
917 917  
918 -= 8.  Packing Info =
1229 += 7. Packing Info =
919 919  
920 920  (((
921 921  
922 922  
923 923  (% style="color:#037691" %)**Package Includes**:
1235 +)))
924 924  
925 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
926 -* External antenna x 1
1237 +* (((
1238 +LSE01 LoRaWAN Soil Moisture & EC Sensor x 1
927 927  )))
928 928  
929 929  (((
... ... @@ -930,22 +930,24 @@
930 930  
931 931  
932 932  (% style="color:#037691" %)**Dimension and weight**:
1245 +)))
933 933  
934 -
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
1247 +* (((
1248 +Device Size: cm
939 939  )))
1250 +* (((
1251 +Device Weight: g
1252 +)))
1253 +* (((
1254 +Package Size / pcs : cm
1255 +)))
1256 +* (((
1257 +Weight / pcs : g
940 940  
941 -(((
942 942  
943 -
944 -
945 -
946 946  )))
947 947  
948 -= 9.  Support =
1262 += 8. Support =
949 949  
950 950  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
951 951  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
1657260785982-288.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.2 KB
Content
1657261119050-993.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
1657261278785-153.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
1657271519014-786.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -71.5 KB
Content
1657327959271-447.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.3 KB
Content
1657328609906-564.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -492.6 KB
Content
1657328659945-416.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
1657328756309-230.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.5 KB
Content
1657328884227-504.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -483.6 KB
Content
1657329814315-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -85.3 KB
Content
1657330452568-615.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -71.3 KB
Content
1657330472797-498.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -68.9 KB
Content
1657330501006-241.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -119.2 KB
Content
1657330533775-472.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -74.9 KB
Content
1657330723006-866.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -74.1 KB
Content
1657331036973-987.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -83.8 KB
Content
1657332990863-496.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.2 KB
Content
1657333200519-600.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
1657348034241-728.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -127.8 KB
Content
1657348284168-431.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -93.5 KB
Content
1657350248151-650.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
1657350625843-586.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -93.3 KB
Content
1657351240556-536.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -483.6 KB
Content
1657351312545-300.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -675.8 KB
Content
1657352146020-183.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -264.0 KB
Content
1657352185396-303.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.3 KB
Content
1657352391268-297.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -238.0 KB
Content
1657352403317-397.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -547.7 KB
Content
1657352634421-276.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -163.6 KB
Content
1657352645687-385.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -214.7 KB
Content
1657352898400-901.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -144.8 KB
Content
1657352914475-252.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -157.0 KB
Content
1657354294009-643.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -214.7 KB
Content
image-20220708140453-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -132.7 KB
Content
image-20220708141352-7.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -102.7 KB
Content
image-20220709084038-1.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -72.0 KB
Content
image-20220709084137-2.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -72.0 KB
Content
image-20220709084207-3.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -72.0 KB
Content
image-20220709084458-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -199.5 KB
Content
image-20220709085040-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -200.4 KB
Content
image-20220709092052-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -247.3 KB
Content
image-20220709093918-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -42.2 KB
Content
image-20220709093918-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -61.9 KB
Content
image-20220709100028-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.8 KB
Content
image-20220709101450-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.5 KB
Content
image-20220709110451-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -611.5 KB
Content
image-20220709144723-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -413.1 KB
Content
image-20220709150546-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -333.5 KB
Content