Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 115.5
edited by Xiaoling
on 2022/07/09 17:18
Change comment: There is no comment for this version
To version 60.1
edited by Xiaoling
on 2022/07/08 14:04
Change comment: Uploaded new attachment "image-20220708140453-6.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,33 +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  
45 +
46 +== 1.2 ​Features ==
47 +
48 +
44 44  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
45 -* Monitor Temperature & Humidity via SHT31
50 +* Monitor Soil Moisture
51 +* Monitor Soil Temperature
52 +* Monitor Soil Conductivity
46 46  * AT Commands to change parameters
47 47  * Uplink on periodically
48 48  * Downlink to change configure
... ... @@ -52,9 +52,6 @@
52 52  * Micro SIM card slot for NB-IoT SIM
53 53  * 8500mAh Battery for long term use
54 54  
55 -
56 -
57 -
58 58  == 1.3  Specification ==
59 59  
60 60  
... ... @@ -72,152 +72,90 @@
72 72  * - B20 @H-FDD: 800MHz
73 73  * - B28 @H-FDD: 700MHz
74 74  
75 -(% style="color:#037691" %)**Battery:**
79 +(% style="color:#037691" %)**Probe Specification:**
76 76  
81 +Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
77 77  
78 -* Li/SOCI2 un-chargeable battery
79 -* Capacity: 8500mAh
80 -* Self Discharge: <1% / Year @ 25°C
81 -* Max continuously current: 130mA
82 -* Max boost current: 2A, 1 second
83 +[[image:image-20220708101224-1.png]]
83 83  
84 84  
85 85  
86 -
87 87  == ​1.4  Applications ==
88 88  
89 -* Smart Buildings & Home Automation
90 -* Logistics and Supply Chain Management
91 -* Smart Metering
92 92  * Smart Agriculture
93 -* Smart Cities
94 -* Smart Factory
95 95  
96 96  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
97 97  ​
98 98  
99 -
100 100  == 1.5  Pin Definitions ==
101 101  
102 -N95S31B use the mother board from NBSN95 which as below.
103 103  
104 -[[image:image-20220709144723-1.png]]
97 +[[image:1657246476176-652.png]]
105 105  
106 106  
107 -=== 1.5.1 Jumper JP2 ===
108 108  
109 -Power on Device when put this jumper.
101 += 2.  Use NSE01 to communicate with IoT Server =
110 110  
111 -
112 -
113 -=== 1.5.2 BOOT MODE / SW1 ===
114 -
115 -1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
116 -
117 -2) Flash: work mode, device starts to work and send out console output for further debug
118 -
119 -
120 -
121 -=== 1.5.3 Reset Button ===
122 -
123 -Press to reboot the device.
124 -
125 -
126 -
127 -=== 1.5.4 LED ===
128 -
129 -It will flash:
130 -
131 -1. When boot the device in flash mode
132 -1. Send an uplink packet
133 -
134 -
135 -= 2.  Use N95S31B to communicate with IoT Server =
136 -
137 137  == 2.1  How it works ==
138 138  
139 139  
140 140  (((
141 -The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by N95S31B.
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.
142 142  )))
143 143  
144 144  
145 145  (((
146 -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:
147 147  )))
148 148  
149 -(((
150 -
151 -)))
115 +[[image:image-20220708101605-2.png]]
152 152  
153 -[[image:1657350248151-650.png]]
154 -
155 155  (((
156 156  
157 157  )))
158 158  
159 159  
160 -== 2.2 ​ Configure the N95S31B ==
161 161  
123 +== 2.2 ​ Configure the NSE01 ==
162 162  
163 -=== 2.2.1  Power On N95S31B ===
164 164  
165 -
166 -[[image:image-20220709150546-2.png]]
167 -
168 -
169 169  === 2.2.1 Test Requirement ===
170 170  
171 171  
172 -To use N95S31B in your city, make sure meet below requirements:
129 +To use NSE01 in your city, make sure meet below requirements:
173 173  
174 174  * Your local operator has already distributed a NB-IoT Network there.
175 -* The local NB-IoT network used the band that N95S31B supports.
132 +* The local NB-IoT network used the band that NSE01 supports.
176 176  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
177 177  
178 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
179 -
180 -N95S31B supports different communication protocol such as :
181 -
182 182  (((
183 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
184 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
185 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
186 -* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
187 -
188 -We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server.
189 -
190 -
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
191 191  )))
192 192  
193 -[[image:1657350625843-586.png]]
194 194  
140 +[[image:1657249419225-449.png]]
195 195  
196 196  
197 -=== 2.2.3  Insert SIM card ===
198 198  
199 -(((
144 +=== 2.2.2 Insert SIM card ===
145 +
200 200  Insert the NB-IoT Card get from your provider.
201 -)))
202 202  
203 -(((
204 204  User need to take out the NB-IoT module and insert the SIM card like below:
205 -)))
206 206  
207 207  
208 -[[image:1657351240556-536.png]]
151 +[[image:1657249468462-536.png]]
209 209  
210 210  
211 211  
212 -=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
155 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
213 213  
214 214  (((
215 215  (((
216 -User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below.
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.
217 217  )))
218 218  )))
219 219  
220 -[[image:1657351312545-300.png]]
221 221  
222 222  **Connection:**
223 223  
... ... @@ -237,110 +237,94 @@
237 237  * Flow Control: (% style="color:green" %)**None**
238 238  
239 239  (((
240 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
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.
241 241  )))
242 242  
243 -[[image:1657329814315-101.png]]
185 +[[image:image-20220708110657-3.png]]
244 244  
245 -(((
246 -(% style="color:red" %)Note: the valid AT Commands can be found at:  (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]
247 -)))
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/]]
248 248  
249 249  
250 250  
251 -=== 2.2.5  Use CoAP protocol to uplink data ===
191 +=== 2.2.4 Use CoAP protocol to uplink data ===
252 252  
253 253  (% 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/]]
254 254  
255 255  
256 -(((
257 257  **Use below commands:**
258 -)))
259 259  
260 -* (((
261 -(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
262 -)))
263 -* (((
264 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
265 -)))
266 -* (((
267 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
268 -)))
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
269 269  
270 -(((
271 -
272 -
273 273  For parameter description, please refer to AT command set
274 -)))
275 275  
276 -[[image:1657352146020-183.png]]
204 +[[image:1657249793983-486.png]]
277 277  
278 278  
279 -(((
280 -After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
281 -)))
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.
282 282  
283 -[[image:1657352185396-303.png]]
209 +[[image:1657249831934-534.png]]
284 284  
285 285  
286 286  
287 -=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
213 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
288 288  
215 +This feature is supported since firmware version v1.0.1
289 289  
290 -* (% 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
291 291  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
292 -* (% 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
293 293  
294 -[[image:1657352391268-297.png]]
222 +[[image:1657249864775-321.png]]
295 295  
296 296  
297 -[[image:1657352403317-397.png]]
225 +[[image:1657249930215-289.png]]
298 298  
299 299  
300 300  
301 -=== 2.2.7  Use MQTT protocol to uplink data ===
229 +=== 2.2.6 Use MQTT protocol to uplink data ===
302 302  
303 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
231 +This feature is supported since firmware version v110
304 304  
305 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
306 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
307 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
308 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
309 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
310 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
311 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
312 312  
313 -[[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
314 314  
242 +[[image:1657249978444-674.png]]
315 315  
316 -[[image:1657352645687-385.png]]
317 317  
318 -(((
319 -To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period.
320 -)))
245 +[[image:1657249990869-686.png]]
321 321  
322 322  
323 323  (((
324 -MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
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.
325 325  )))
326 326  
327 327  
328 328  
329 -=== 2.2.8  Use TCP protocol to uplink data ===
254 +=== 2.2.7 Use TCP protocol to uplink data ===
330 330  
331 331  This feature is supported since firmware version v110
332 332  
258 +
333 333  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
334 334  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
335 335  
336 -[[image:1657352898400-901.png]]
262 +[[image:1657250217799-140.png]]
337 337  
338 338  
339 -[[image:1657352914475-252.png]]
265 +[[image:1657250255956-604.png]]
340 340  
341 341  
342 342  
343 -=== 2.2.9  Change Update Interval ===
269 +=== 2.2.8 Change Update Interval ===
344 344  
345 345  User can use below command to change the (% style="color:green" %)**uplink interval**.
346 346  
... ... @@ -347,201 +347,208 @@
347 347  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
348 348  
349 349  (((
350 -
276 +(% style="color:red" %)**NOTE:**
351 351  )))
352 352  
279 +(((
280 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
281 +)))
353 353  
354 354  
284 +
355 355  == 2.3  Uplink Payload ==
356 356  
287 +In this mode, uplink payload includes in total 18 bytes
357 357  
358 -NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
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"]]
359 359  
295 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
360 360  
361 -For example:
362 362  
363 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
298 +[[image:image-20220708111918-4.png]]
364 364  
365 365  
366 -The uplink payloads are composed in  ASCII String. For example:
301 +The payload is ASCII string, representative same HEX:
367 367  
368 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
303 +0x72403155615900640c7817075e0a8c02f900 where:
369 369  
370 -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
371 371  
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
372 372  
373 -(% style="color:red" %)**NOTE:**
374 374  
375 -(% style="color:red" %)
376 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
377 -1. By default, the device will send an uplink message every 1 hour.
316 +== 2.4  Payload Explanation and Sensor Interface ==
378 378  
379 379  
319 +=== 2.4.1  Device ID ===
380 380  
381 -=== 2.3.1  Payload Analyze ===
321 +By default, the Device ID equal to the last 6 bytes of IMEI.
382 382  
383 -N95S31B uplink payload includes in total 21 bytes
323 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
384 384  
325 +**Example:**
385 385  
386 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
387 -|=(% style="width: 60px;" %)(((
388 -**Size(bytes)**
389 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1**
390 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
391 -Reserve/ Same as NBSN95 CFGMOD=1
327 +AT+DEUI=A84041F15612
392 392  
393 -No function here.
394 -)))|(% style="width:77px" %)(((
395 -[[Temperature >>||anchor="H2.4.5A0Distance"]]
329 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
396 396  
397 -By SHT31
398 -)))|(% style="width:80px" %)(((
399 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
400 400  
401 -By SHT31
402 -)))
403 403  
404 -(((
405 -(((
406 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
407 -)))
408 -)))
333 +=== 2.4.2  Version Info ===
409 409  
335 +Specify the software version: 0x64=100, means firmware version 1.00.
410 410  
411 -[[image:1657354294009-643.png]]
337 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
412 412  
413 413  
414 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
415 415  
416 -* Device ID: 0x724031607457 = 724031607457
417 -* Version: 0x006e=110=1.1.0
341 +=== 2.4.3  Battery Info ===
418 418  
419 -* BAT: 0x0ccd = 3277 mV = 3.277V
420 -* Signal: 0x1b = 27
421 -* Model: 0x01 = 1
422 -* 0x00dc000ccc= reserve, ignore in N95S31B
423 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
424 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
425 -
426 426  (((
427 -
344 +Check the battery voltage for LSE01.
428 428  )))
429 429  
430 430  (((
431 -
348 +Ex1: 0x0B45 = 2885mV
432 432  )))
433 433  
434 -
435 -=== 2.3.2  Device ID ===
436 -
437 437  (((
438 -By default, the Device ID equal to the last 6 bytes of IMEI.
352 +Ex2: 0x0B49 = 2889mV
439 439  )))
440 440  
441 -(((
442 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
443 -)))
444 444  
445 -(((
446 -**Example:**
447 -)))
448 448  
449 -(((
450 -AT+DEUI=A84041F15612
451 -)))
357 +=== 2.4.4  Signal Strength ===
452 452  
453 -(((
454 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
455 -)))
359 +NB-IoT Network signal Strength.
456 456  
361 +**Ex1: 0x1d = 29**
457 457  
363 +(% style="color:blue" %)**0**(%%)  -113dBm or less
458 458  
459 -=== 2.3.3  Version Info ===
365 +(% style="color:blue" %)**1**(%%)  -111dBm
460 460  
367 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
461 461  
462 -These bytes include the hardware and software version.
369 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
463 463  
464 -Higher byte: Specify hardware version: always 0x00 for N95S31B
371 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
465 465  
466 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
467 467  
468 468  
469 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
375 +=== 2.4.5  Soil Moisture ===
470 470  
471 471  (((
472 -
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.
473 473  )))
474 474  
381 +(((
382 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
383 +)))
475 475  
476 -=== 2.3.4  Battery Info ===
477 -
478 478  (((
479 -Ex1: 0x0B45 = 2885mV
386 +
480 480  )))
481 481  
482 482  (((
483 -Ex2: 0x0B49 = 2889mV
390 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
484 484  )))
485 485  
486 486  
487 487  
488 -=== 2.3.5  Signal Strength ===
395 +=== 2.4.6  Soil Temperature ===
489 489  
490 490  (((
491 -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
492 492  )))
493 493  
494 494  (((
495 -**Ex1: 0x1d = 29**
402 +**Example**:
496 496  )))
497 497  
498 498  (((
499 -(% style="color:blue" %)**0**(%%)  -113dBm or less
406 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
500 500  )))
501 501  
502 502  (((
503 -(% style="color:blue" %)**1**(%%)  -111dBm
410 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
504 504  )))
505 505  
413 +
414 +
415 +=== 2.4.7  Soil Conductivity (EC) ===
416 +
506 506  (((
507 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
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).
508 508  )))
509 509  
510 510  (((
511 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
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.
512 512  )))
513 513  
514 514  (((
515 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
426 +Generally, the EC value of irrigation water is less than 800uS / cm.
516 516  )))
517 517  
429 +(((
430 +
431 +)))
518 518  
433 +(((
434 +
435 +)))
519 519  
520 -=== 2.3.6  Temperature & Humidity ===
437 +=== 2.4.8  Digital Interrupt ===
521 521  
522 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
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.
523 523  
524 -[[image:image-20220709161741-3.png]]
441 +The command is:
525 525  
443 +(% 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]])**.**
526 526  
527 -Convert the read byte to decimal and divide it by ten.
528 528  
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.
529 529  
530 -**Example:**
531 531  
532 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
449 +Example:
533 533  
534 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
451 +0x(00): Normal uplink packet.
535 535  
453 +0x(01): Interrupt Uplink Packet.
536 536  
537 537  
456 +
457 +=== 2.4.9  ​+5V Output ===
458 +
459 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
460 +
461 +
462 +The 5V output time can be controlled by AT Command.
463 +
464 +(% style="color:blue" %)**AT+5VT=1000**
465 +
466 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
467 +
468 +
469 +
538 538  == 2.5  Downlink Payload ==
539 539  
540 -By default, NDDS75 prints the downlink payload to console port.
472 +By default, LSE50 prints the downlink payload to console port.
541 541  
542 -[[image:image-20220709100028-1.png]]
474 +[[image:image-20220708133731-5.png]]
543 543  
544 544  
477 +
545 545  (((
546 546  (% style="color:blue" %)**Examples:**
547 547  )))
... ... @@ -555,7 +555,7 @@
555 555  )))
556 556  
557 557  (((
558 -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.
559 559  )))
560 560  
561 561  (((
... ... @@ -575,85 +575,432 @@
575 575  )))
576 576  
577 577  (((
578 -If payload = 0x04FF, it will reset the NDDS75
511 +If payload = 0x04FF, it will reset the LSE01
579 579  )))
580 580  
581 581  
582 -* (% style="color:blue" %)**INTMOD**
515 +* (% style="color:blue" %)**CFM**
583 583  
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 +
584 584  (((
585 -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:
586 586  )))
587 587  
527 +(((
528 +
529 +)))
588 588  
531 +(((
532 +(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the network at this time.
533 +)))
589 589  
590 -== 2.5  ​Battery Analysis ==
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 +)))
591 591  
592 -=== 2.5.1  ​Battery Type ===
593 593  
540 +[[image:1654505857935-743.png]]
594 594  
542 +
543 +[[image:1654505874829-548.png]]
544 +
545 +
546 +(% style="color:blue" %)**Step 3**(%%)**:**  Create an account or log in Datacake.
547 +
548 +(% style="color:blue" %)**Step 4**(%%)**:**  Search the LSE01 and add DevEUI.
549 +
550 +
551 +[[image:1654505905236-553.png]]
552 +
553 +
554 +After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
555 +
556 +[[image:1654505925508-181.png]]
557 +
558 +
559 +
560 +== 2.7 Frequency Plans ==
561 +
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.
563 +
564 +
565 +=== 2.7.1 EU863-870 (EU868) ===
566 +
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 +
595 595  (((
596 -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.
597 597  )))
857 +)))
598 598  
859 +
860 +
861 +[[image:1654506665940-119.png]]
862 +
599 599  (((
600 -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.
601 601  )))
602 602  
603 603  (((
604 -The battery related documents as below:
868 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
605 605  )))
606 606  
607 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
608 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
609 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
610 610  
872 +== 2.10 ​Firmware Change Log ==
873 +
611 611  (((
612 -[[image:image-20220709101450-2.png]]
875 +**Firmware download link:**
613 613  )))
614 614  
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 +)))
615 615  
882 +(((
883 +
884 +)))
616 616  
617 -=== 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 +)))
618 618  
619 619  (((
620 -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 +
621 621  )))
622 622  
894 +(((
895 +**V1.0.**
896 +)))
623 623  
624 624  (((
625 -Instruction to use as below:
899 +Release
626 626  )))
627 627  
902 +
903 +== 2.11 ​Battery Analysis ==
904 +
905 +=== 2.11.1 ​Battery Type ===
906 +
628 628  (((
629 -(% 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.
630 630  )))
631 631  
911 +(((
912 +The battery is designed to last for more than 5 years for the LSN50.
913 +)))
632 632  
633 633  (((
634 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
916 +(((
917 +The battery-related documents are as below:
635 635  )))
919 +)))
636 636  
637 637  * (((
638 -Product Model
922 +[[Battery Dimension>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
639 639  )))
640 640  * (((
641 -Uplink Interval
925 +[[Lithium-Thionyl Chloride Battery  datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
642 642  )))
643 643  * (((
644 -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/]]
645 645  )))
646 646  
647 -(((
648 -And the Life expectation in difference case will be shown on the right.
649 -)))
931 + [[image:image-20220610172436-1.png]]
650 650  
651 -[[image:image-20220709110451-3.png]]
652 652  
653 653  
935 +=== 2.11.2 ​Battery Note ===
654 654  
655 -=== 2.8.3  ​Battery Note ===
656 -
657 657  (((
658 658  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.
659 659  )))
... ... @@ -660,169 +660,302 @@
660 660  
661 661  
662 662  
663 -=== 2.8.4  Replace the battery ===
943 +=== 2.11.3 Replace the battery ===
664 664  
665 665  (((
666 -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.
667 667  )))
668 668  
669 -
670 -
671 -= 3. ​ Access NB-IoT Module =
672 -
673 673  (((
674 -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.
675 675  )))
676 676  
677 677  (((
678 -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)
679 679  )))
680 680  
681 -[[image:1657333200519-600.png]]
682 682  
683 683  
959 += 3. ​Using the AT Commands =
684 684  
685 -= 4.  Using the AT Commands =
961 +== 3.1 Access AT Commands ==
686 686  
687 -== 4.1  Access AT Commands ==
688 688  
689 -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.
690 690  
966 +[[image:1654501986557-872.png||height="391" width="800"]]
691 691  
692 -AT+<CMD>?  : Help on <CMD>
693 693  
694 -AT+<CMD>         : Run <CMD>
969 +Or if you have below board, use below connection:
695 695  
696 -AT+<CMD>=<value> : Set the value
697 697  
698 -AT+<CMD>=?  : Get the value
972 +[[image:1654502005655-729.png||height="503" width="801"]]
699 699  
700 700  
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 +
701 701  (% style="color:#037691" %)**General Commands**(%%)      
702 702  
703 -AT  : Attention       
996 +(% style="background-color:#dcdcdc" %)**AT**(%%)  : Attention       
704 704  
705 -AT?  : Short Help     
998 +(% style="background-color:#dcdcdc" %)**AT?**(%%)  : Short Help     
706 706  
707 -ATZ  : MCU Reset    
1000 +(% style="background-color:#dcdcdc" %)**ATZ**(%%)  : MCU Reset    
708 708  
709 -AT+TDC  : Application Data Transmission Interval
1002 +(% style="background-color:#dcdcdc" %)**AT+TDC**(%%)  : Application Data Transmission Interval 
710 710  
711 -AT+CFG  : Print all configurations
712 712  
713 -AT+CFGMOD           : Working mode selection
1005 +(% style="color:#037691" %)**Keys, IDs and EUIs management**
714 714  
715 -AT+INTMOD            : Set the trigger interrupt mode
1007 +(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%)              : Application EUI      
716 716  
717 -AT+5VT  : Set extend the time of 5V power  
1009 +(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%)              : Application Key     
718 718  
719 -AT+PRO  : Choose agreement
1011 +(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%)            : Application Session Key
720 720  
721 -AT+WEIGRE  : Get weight or set weight to 0
1013 +(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%)              : Device Address     
722 722  
723 -AT+WEIGAP  : Get or Set the GapValue of weight
1015 +(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%)                   : Device EUI     
724 724  
725 -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) 
726 726  
727 -AT+CNTFAC  : Get or set counting parameters
1019 +(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%)          : Network Session Key Joining and sending date on LoRa network  
728 728  
729 -AT+SERVADDR  : Server Address
1021 +(% style="background-color:#dcdcdc" %)**AT+CFM**(%%)  : Confirm Mode       
730 730  
1023 +(% style="background-color:#dcdcdc" %)**AT+CFS**(%%)                     : Confirm Status       
731 731  
732 -(% style="color:#037691" %)**COAP Management**      
1025 +(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%)  : Join LoRa? Network       
733 733  
734 -AT+URI            : Resource parameters
1027 +(% style="background-color:#dcdcdc" %)**AT+NJM**(%%)  : LoRa? Network Join Mode    
735 735  
1029 +(% style="background-color:#dcdcdc" %)**AT+NJS**(%%)                     : LoRa? Network Join Status    
736 736  
737 -(% style="color:#037691" %)**UDP Management**
1031 +(% style="background-color:#dcdcdc" %)**AT+RECV**(%%)                  : Print Last Received Data in Raw Format
738 738  
739 -AT+CFM          : Upload confirmation mode (only valid for UDP)
1033 +(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%)                : Print Last Received Data in Binary Format      
740 740  
1035 +(% style="background-color:#dcdcdc" %)**AT+SEND**(%%)                  : Send Text Data      
741 741  
742 -(% style="color:#037691" %)**MQTT Management**
1037 +(% style="background-color:#dcdcdc" %)**AT+SENB**(%%)                  : Send Hexadecimal Data
743 743  
744 -AT+CLIENT               : Get or Set MQTT client
745 745  
746 -AT+UNAME  : Get or Set MQTT Username
1040 +(% style="color:#037691" %)**LoRa Network Management**
747 747  
748 -AT+PWD                  : Get or Set MQTT password
1042 +(% style="background-color:#dcdcdc" %)**AT+ADR**(%%)          : Adaptive Rate
749 749  
750 -AT+PUBTOPIC  : Get or Set MQTT publish topic
1044 +(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%)  : LoRa Class(Currently only support class A
751 751  
752 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
1046 +(% style="background-color:#dcdcdc" %)**AT+DCS**(%%)  : Duty Cycle Setting 
753 753  
1048 +(% style="background-color:#dcdcdc" %)**AT+DR**(%%)  : Data Rate (Can Only be Modified after ADR=0)     
754 754  
755 -(% style="color:#037691" %)**Information**          
1050 +(% style="background-color:#dcdcdc" %)**AT+FCD**(%%)  : Frame Counter Downlink       
756 756  
757 -AT+FDR  : Factory Data Reset
1052 +(% style="background-color:#dcdcdc" %)**AT+FCU**(%%)  : Frame Counter Uplink   
758 758  
759 -AT+PWORD  : Serial Access Password
1054 +(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%)  : Join Accept Delay1
760 760  
1056 +(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%)  : Join Accept Delay2
761 761  
1058 +(% style="background-color:#dcdcdc" %)**AT+PNM**(%%)  : Public Network Mode   
762 762  
763 -= ​5.  FAQ =
1060 +(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%)  : Receive Delay1      
764 764  
765 -== 5.1 ​ How to Upgrade Firmware ==
1062 +(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%)  : Receive Delay2      
766 766  
1064 +(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%)  : Rx2 Window Data Rate 
767 767  
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 +
768 768  (((
769 -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. ​
770 770  )))
771 771  
772 772  (((
773 -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 +
774 774  )))
775 775  
776 776  (((
777 -(% 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.
778 778  )))
779 779  
1107 +(((
1108 +
1109 +)))
780 780  
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 +)))
781 781  
782 -= 6.  Trouble Shooting =
1115 +(((
1116 +
1117 +)))
783 783  
784 -== 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 +)))
785 785  
1123 +[[image:image-20220606154726-3.png]]
786 786  
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 +
787 787  (((
788 -**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**
789 789  )))
790 790  
791 -(% class="wikigeneratedid" %)
792 792  (((
793 793  
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.
794 794  )))
795 795  
1151 +(((
1152 +
1153 +)))
796 796  
797 -== 6.2  AT Command input doesn't work ==
1155 +(((
1156 +The **AU915** band is similar. Below are the AU915 Uplink Channels.
1157 +)))
798 798  
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 +
799 799  (((
800 800  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 +)))
801 801  
802 -
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.
803 803  )))
804 804  
805 805  
806 -= 7. ​ Order Info =
1195 +(% style="color:#4f81bd" %)**Solution: **
807 807  
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:
808 808  
809 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1199 +[[image:1654500929571-736.png||height="458" width="832"]]
810 810  
811 811  
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 +
812 812  (% class="wikigeneratedid" %)
813 813  (((
814 814  
815 815  )))
816 816  
817 -= 8.  Packing Info =
1229 += 7. Packing Info =
818 818  
819 819  (((
820 820  
821 821  
822 822  (% style="color:#037691" %)**Package Includes**:
1235 +)))
823 823  
824 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
825 -* External antenna x 1
1237 +* (((
1238 +LSE01 LoRaWAN Soil Moisture & EC Sensor x 1
826 826  )))
827 827  
828 828  (((
... ... @@ -829,22 +829,24 @@
829 829  
830 830  
831 831  (% style="color:#037691" %)**Dimension and weight**:
1245 +)))
832 832  
833 -
834 -* Device Size: 13.0 x 5 x 4.5 cm
835 -* Device Weight: 150g
836 -* Package Size / pcs : 15 x 12x 5.5 cm
837 -* Weight / pcs : 220g
1247 +* (((
1248 +Device Size: cm
838 838  )))
1250 +* (((
1251 +Device Weight: g
1252 +)))
1253 +* (((
1254 +Package Size / pcs : cm
1255 +)))
1256 +* (((
1257 +Weight / pcs : g
839 839  
840 -(((
841 841  
842 -
843 -
844 -
845 845  )))
846 846  
847 -= 9.  Support =
1262 += 8. Support =
848 848  
849 849  * 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.
850 850  * 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-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
image-20220709161741-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -111.2 KB
Content