Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 102.3
edited by Xiaoling
on 2022/07/09 15:09
Change comment: There is no comment for this version
To version 57.6
edited by Xiaoling
on 2022/07/08 11:52
Change comment: There is no comment for this version

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,8 +53,6 @@
53 53  * Micro SIM card slot for NB-IoT SIM
54 54  * 8500mAh Battery for long term use
55 55  
56 -
57 -
58 58  == 1.3  Specification ==
59 59  
60 60  
... ... @@ -72,159 +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 86  == ​1.4  Applications ==
87 87  
88 -* Smart Buildings & Home Automation
89 -* Logistics and Supply Chain Management
90 -* Smart Metering
91 91  * Smart Agriculture
92 -* Smart Cities
93 -* Smart Factory
94 94  
95 95  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
96 96  ​
97 97  
98 -
99 99  == 1.5  Pin Definitions ==
100 100  
101 -N95S31B use the mother board from NBSN95 which as below.
102 102  
103 -[[image:image-20220709144723-1.png]]
97 +[[image:1657246476176-652.png]]
104 104  
105 105  
106 -=== 1.5.1 Jumper JP2 ===
107 107  
108 -Power on Device when put this jumper.
101 += 2.  Use NSE01 to communicate with IoT Server =
109 109  
110 -
111 -
112 -=== 1.5.2 BOOT MODE / SW1 ===
113 -
114 -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.
115 -
116 -2) Flash: work mode, device starts to work and send out console output for further debug
117 -
118 -
119 -
120 -=== 1.5.3 Reset Button ===
121 -
122 -Press to reboot the device.
123 -
124 -
125 -
126 -=== 1.5.4 LED ===
127 -
128 -It will flash:
129 -
130 -1. When boot the device in flash mode
131 -1. Send an uplink packet
132 -
133 -
134 -
135 -
136 -= 2.  Use N95S31B to communicate with IoT Server =
137 -
138 138  == 2.1  How it works ==
139 139  
140 140  
141 141  (((
142 -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.
143 143  )))
144 144  
145 145  
146 146  (((
147 -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:
148 148  )))
149 149  
150 -(((
151 -
152 -)))
115 +[[image:image-20220708101605-2.png]]
153 153  
154 -[[image:1657350248151-650.png]]
155 -
156 156  (((
157 157  
158 158  )))
159 159  
160 160  
161 -== 2.2 ​ Configure the N95S31B ==
162 162  
123 +== 2.2 ​ Configure the NSE01 ==
163 163  
164 -=== 2.2.1  Power On N95S31B ===
165 165  
166 -
167 -[[image:image-20220709150546-2.png]]
168 -
169 -
170 170  === 2.2.1 Test Requirement ===
171 171  
172 172  
173 -To use N95S31B in your city, make sure meet below requirements:
129 +To use NSE01 in your city, make sure meet below requirements:
174 174  
175 175  * Your local operator has already distributed a NB-IoT Network there.
176 -* The local NB-IoT network used the band that N95S31B supports.
132 +* The local NB-IoT network used the band that NSE01 supports.
177 177  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
178 178  
179 -
180 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
181 -
182 -N95S31B supports different communication protocol such as :
183 -
184 184  (((
185 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
186 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
187 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
188 -* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
189 -
190 -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.
191 -
192 -
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
193 193  )))
194 194  
195 -(((
196 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 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
197 -)))
198 198  
140 +[[image:1657249419225-449.png]]
199 199  
200 -[[image:1657328756309-230.png]]
201 201  
202 202  
203 -
204 204  === 2.2.2 Insert SIM card ===
205 205  
206 -(((
207 207  Insert the NB-IoT Card get from your provider.
208 -)))
209 209  
210 -(((
211 211  User need to take out the NB-IoT module and insert the SIM card like below:
212 -)))
213 213  
214 214  
215 -[[image:1657328884227-504.png]]
151 +[[image:1657249468462-536.png]]
216 216  
217 217  
218 218  
219 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
155 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
220 220  
221 221  (((
222 222  (((
223 -User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 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.
224 224  )))
225 225  )))
226 226  
227 -[[image:image-20220709092052-2.png]]
228 228  
229 229  **Connection:**
230 230  
... ... @@ -244,14 +244,12 @@
244 244  * Flow Control: (% style="color:green" %)**None**
245 245  
246 246  (((
247 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 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.
248 248  )))
249 249  
250 -[[image:1657329814315-101.png]]
185 +[[image:image-20220708110657-3.png]]
251 251  
252 -(((
253 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
254 -)))
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/]]
255 255  
256 256  
257 257  
... ... @@ -260,64 +260,57 @@
260 260  (% 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/]]
261 261  
262 262  
263 -(((
264 264  **Use below commands:**
265 -)))
266 266  
267 -* (((
268 -(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
269 -)))
270 -* (((
271 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
272 -)))
273 -* (((
274 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
275 -)))
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
276 276  
277 -(((
202 +
278 278  For parameter description, please refer to AT command set
279 -)))
280 280  
281 -[[image:1657330452568-615.png]]
205 +[[image:1657249793983-486.png]]
282 282  
283 283  
284 -(((
285 -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.
286 -)))
208 +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.
287 287  
288 -[[image:1657330472797-498.png]]
210 +[[image:1657249831934-534.png]]
289 289  
290 290  
291 291  
292 292  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
293 293  
216 +This feature is supported since firmware version v1.0.1
294 294  
295 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
218 +
219 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
296 296  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
297 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
221 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
298 298  
299 -[[image:1657330501006-241.png]]
223 +[[image:1657249864775-321.png]]
300 300  
301 301  
302 -[[image:1657330533775-472.png]]
226 +[[image:1657249930215-289.png]]
303 303  
304 304  
305 305  
306 306  === 2.2.6 Use MQTT protocol to uplink data ===
307 307  
232 +This feature is supported since firmware version v110
308 308  
309 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
310 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
311 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
312 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
313 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
314 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
315 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
316 316  
235 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
236 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
237 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
238 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
239 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
240 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
241 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
242 +
317 317  [[image:1657249978444-674.png]]
318 318  
319 319  
320 -[[image:1657330723006-866.png]]
246 +[[image:1657249990869-686.png]]
321 321  
322 322  
323 323  (((
... ... @@ -328,14 +328,16 @@
328 328  
329 329  === 2.2.7 Use TCP protocol to uplink data ===
330 330  
257 +This feature is supported since firmware version v110
331 331  
259 +
332 332  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
333 333  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
334 334  
335 -[[image:image-20220709093918-1.png]]
263 +[[image:1657250217799-140.png]]
336 336  
337 337  
338 -[[image:image-20220709093918-2.png]]
266 +[[image:1657250255956-604.png]]
339 339  
340 340  
341 341  
... ... @@ -357,90 +357,58 @@
357 357  
358 358  == 2.3  Uplink Payload ==
359 359  
360 -In this mode, uplink payload includes in total 14 bytes
288 +In this mode, uplink payload includes in total 18 bytes
361 361  
362 -
363 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
364 -|=(% style="width: 60px;" %)(((
290 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
291 +|=(% style="width: 50px;" %)(((
365 365  **Size(bytes)**
366 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
367 -|(% 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:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
293 +)))|=(% 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**
294 +|(% 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"]]
368 368  
369 -(((
370 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
371 -)))
296 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
372 372  
373 373  
374 -[[image:1657331036973-987.png]]
299 +[[image:image-20220708111918-4.png]]
375 375  
376 -(((
301 +
377 377  The payload is ASCII string, representative same HEX:
378 -)))
379 379  
380 -(((
381 -0x72403155615900640c6c19029200 where:
382 -)))
304 +0x72403155615900640c7817075e0a8c02f900 where:
383 383  
384 -* (((
385 -Device ID: 0x724031556159 = 724031556159
386 -)))
387 -* (((
388 -Version: 0x0064=100=1.0.0
389 -)))
306 +* Device ID: 0x 724031556159 = 724031556159
307 +* Version: 0x0064=100=1.0.0
390 390  
391 -* (((
392 -BAT: 0x0c6c = 3180 mV = 3.180V
393 -)))
394 -* (((
395 -Signal: 0x19 = 25
396 -)))
397 -* (((
398 -Distance: 0x0292= 658 mm
399 -)))
400 -* (((
401 -Interrupt: 0x00 = 0
309 +* BAT: 0x0c78 = 3192 mV = 3.192V
310 +* Singal: 0x17 = 23
311 +* Soil Moisture: 0x075e= 1886 = 18.86  %
312 +* Soil Temperature:0x0a8c =2700=27 °C
313 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
314 +* Interrupt: 0x00 = 0
402 402  
403 403  
404 404  
405 -
406 -)))
407 407  
408 408  == 2.4  Payload Explanation and Sensor Interface ==
409 409  
410 -
411 411  === 2.4.1  Device ID ===
412 412  
413 -(((
414 414  By default, the Device ID equal to the last 6 bytes of IMEI.
415 -)))
416 416  
417 -(((
418 418  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
419 -)))
420 420  
421 -(((
422 422  **Example:**
423 -)))
424 424  
425 -(((
426 426  AT+DEUI=A84041F15612
427 -)))
428 428  
429 -(((
430 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
431 -)))
331 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
432 432  
433 433  
434 434  
435 435  === 2.4.2  Version Info ===
436 436  
437 -(((
438 438  Specify the software version: 0x64=100, means firmware version 1.00.
439 -)))
440 440  
441 -(((
442 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
443 -)))
339 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
444 444  
445 445  
446 446  
... ... @@ -447,6 +447,10 @@
447 447  === 2.4.3  Battery Info ===
448 448  
449 449  (((
346 +Check the battery voltage for LSE01.
347 +)))
348 +
349 +(((
450 450  Ex1: 0x0B45 = 2885mV
451 451  )))
452 452  
... ... @@ -458,49 +458,31 @@
458 458  
459 459  === 2.4.4  Signal Strength ===
460 460  
461 -(((
462 462  NB-IoT Network signal Strength.
463 -)))
464 464  
465 -(((
466 466  **Ex1: 0x1d = 29**
467 -)))
468 468  
469 -(((
470 470  (% style="color:blue" %)**0**(%%)  -113dBm or less
471 -)))
472 472  
473 -(((
474 474  (% style="color:blue" %)**1**(%%)  -111dBm
475 -)))
476 476  
477 -(((
478 478  (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
479 -)))
480 480  
481 -(((
482 482  (% style="color:blue" %)**31**  (%%) -51dBm or greater
483 -)))
484 484  
485 -(((
486 486  (% style="color:blue" %)**99**   (%%) Not known or not detectable
487 -)))
488 488  
489 489  
490 490  
491 -=== 2.4.5  Distance ===
377 +=== 2.4.5  Soil Moisture ===
492 492  
493 -Get the distance. Flat object range 280mm - 7500mm.
494 -
495 495  (((
496 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
380 +Get the moisture content of the soil. The value range of the register is 0-10000(Decimal), divide this value by 100 to get the percentage of moisture in the soil.
497 497  )))
498 498  
499 499  (((
500 -(((
501 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
384 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
502 502  )))
503 -)))
504 504  
505 505  (((
506 506  
... ... @@ -507,71 +507,102 @@
507 507  )))
508 508  
509 509  (((
510 -
392 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
511 511  )))
512 512  
513 -=== 2.4.6  Digital Interrupt ===
514 514  
396 +
397 +=== 2.4.6  Soil Temperature ===
398 +
515 515  (((
516 -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.
400 + Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is __**0x09 0xEC**__, the temperature content in the soil is
517 517  )))
518 518  
519 519  (((
520 -The command is:
404 +**Example**:
521 521  )))
522 522  
523 523  (((
524 -(% 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]])**.**
408 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
525 525  )))
526 526  
411 +(((
412 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
413 +)))
527 527  
415 +
416 +
417 +=== 2.4.7  Soil Conductivity (EC) ===
418 +
528 528  (((
529 -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.
420 +Obtain (% style="color:#4f81bd" %)**__soluble salt concentration__**(%%) in soil or (% style="color:#4f81bd" %)**__soluble ion concentration in liquid fertilizer__**(%%) or (% style="color:#4f81bd" %)**__planting medium__**(%%). The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000).
530 530  )))
531 531  
423 +(((
424 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
425 +)))
532 532  
533 533  (((
534 -Example:
428 +Generally, the EC value of irrigation water is less than 800uS / cm.
535 535  )))
536 536  
537 537  (((
538 -0x(00): Normal uplink packet.
432 +
539 539  )))
540 540  
541 541  (((
542 -0x(01): Interrupt Uplink Packet.
436 +
543 543  )))
544 544  
439 +=== 2.4.8  Digital Interrupt ===
545 545  
546 546  
547 -=== 2.4.7  ​+5V Output ===
442 +Digital Interrupt refers to pin **GPIO_EXTI**, and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server.
548 548  
549 -(((
550 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
551 -)))
444 +The command is:
552 552  
446 +**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]]**).**
553 553  
554 -(((
448 +
449 +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.
450 +
451 +
452 +Example:
453 +
454 +0x(00): Normal uplink packet.
455 +
456 +0x(01): Interrupt Uplink Packet.
457 +
458 +
459 +
460 +
461 +=== 2.4.9  ​+5V Output ===
462 +
463 +
464 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling.
465 +
466 +
555 555  The 5V output time can be controlled by AT Command.
556 -)))
557 557  
558 -(((
559 -(% style="color:blue" %)**AT+5VT=1000**
560 -)))
469 +**(% style="color:blue" %)AT+5VT=1000**
561 561  
562 -(((
563 563  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
564 -)))
565 565  
566 566  
567 567  
568 -== 2.5  Downlink Payload ==
475 +== 2.4 Uplink Interval ==
569 569  
570 -By default, NDDS75 prints the downlink payload to console port.
477 +The LSE01 by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]]
571 571  
572 -[[image:image-20220709100028-1.png]]
573 573  
574 574  
481 +== 2.5 Downlink Payload ==
482 +
483 +By default, LSE50 prints the downlink payload to console port.
484 +
485 +[[image:image-20220606165544-8.png]]
486 +
487 +
575 575  (((
576 576  (% style="color:blue" %)**Examples:**
577 577  )))
... ... @@ -585,7 +585,7 @@
585 585  )))
586 586  
587 587  (((
588 -If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
501 +If the payload=0100003C, it means set the END Node’s TDC to 0x00003C=60(S), while type code is 01.
589 589  )))
590 590  
591 591  (((
... ... @@ -605,120 +605,432 @@
605 605  )))
606 606  
607 607  (((
608 -If payload = 0x04FF, it will reset the NDDS75
521 +If payload = 0x04FF, it will reset the LSE01
609 609  )))
610 610  
611 611  
612 -* (% style="color:blue" %)**INTMOD**
525 +* (% style="color:blue" %)**CFM**
613 613  
527 +Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0
528 +
529 +
530 +
531 +== 2.6 ​Show Data in DataCake IoT Server ==
532 +
614 614  (((
615 -Downlink Payload: 06000003, Set AT+INTMOD=3
534 +[[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:
616 616  )))
617 617  
537 +(((
538 +
539 +)))
618 618  
541 +(((
542 +(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the network at this time.
543 +)))
619 619  
620 -== 2.6  ​LED Indicator ==
545 +(((
546 +(% 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:
547 +)))
621 621  
622 622  
623 -The NDDS75 has an internal LED which is to show the status of different state.
550 +[[image:1654505857935-743.png]]
624 624  
625 625  
626 -* 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)
627 -* Then the LED will be on for 1 second means device is boot normally.
628 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
629 -* For each uplink probe, LED will be on for 500ms.
553 +[[image:1654505874829-548.png]]
630 630  
631 -(((
632 -
633 -)))
634 634  
556 +(% style="color:blue" %)**Step 3**(%%)**:**  Create an account or log in Datacake.
635 635  
558 +(% style="color:blue" %)**Step 4**(%%)**:**  Search the LSE01 and add DevEUI.
636 636  
637 -== 2.7  ​Firmware Change Log ==
638 638  
561 +[[image:1654505905236-553.png]]
639 639  
640 -(((
641 -Download URL & Firmware Change log
642 -)))
643 643  
644 -(((
645 -[[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/]]
646 -)))
564 +After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
647 647  
566 +[[image:1654505925508-181.png]]
648 648  
649 -(((
650 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
651 -)))
652 652  
653 653  
570 +== 2.7 Frequency Plans ==
654 654  
655 -== 2.8  ​Battery Analysis ==
572 +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.
656 656  
657 -=== 2.8.1  ​Battery Type ===
658 658  
575 +=== 2.7.1 EU863-870 (EU868) ===
659 659  
577 +(% style="color:#037691" %)** Uplink:**
578 +
579 +868.1 - SF7BW125 to SF12BW125
580 +
581 +868.3 - SF7BW125 to SF12BW125 and SF7BW250
582 +
583 +868.5 - SF7BW125 to SF12BW125
584 +
585 +867.1 - SF7BW125 to SF12BW125
586 +
587 +867.3 - SF7BW125 to SF12BW125
588 +
589 +867.5 - SF7BW125 to SF12BW125
590 +
591 +867.7 - SF7BW125 to SF12BW125
592 +
593 +867.9 - SF7BW125 to SF12BW125
594 +
595 +868.8 - FSK
596 +
597 +
598 +(% style="color:#037691" %)** Downlink:**
599 +
600 +Uplink channels 1-9 (RX1)
601 +
602 +869.525 - SF9BW125 (RX2 downlink only)
603 +
604 +
605 +
606 +=== 2.7.2 US902-928(US915) ===
607 +
608 +Used in USA, Canada and South America. Default use CHE=2
609 +
610 +(% style="color:#037691" %)**Uplink:**
611 +
612 +903.9 - SF7BW125 to SF10BW125
613 +
614 +904.1 - SF7BW125 to SF10BW125
615 +
616 +904.3 - SF7BW125 to SF10BW125
617 +
618 +904.5 - SF7BW125 to SF10BW125
619 +
620 +904.7 - SF7BW125 to SF10BW125
621 +
622 +904.9 - SF7BW125 to SF10BW125
623 +
624 +905.1 - SF7BW125 to SF10BW125
625 +
626 +905.3 - SF7BW125 to SF10BW125
627 +
628 +
629 +(% style="color:#037691" %)**Downlink:**
630 +
631 +923.3 - SF7BW500 to SF12BW500
632 +
633 +923.9 - SF7BW500 to SF12BW500
634 +
635 +924.5 - SF7BW500 to SF12BW500
636 +
637 +925.1 - SF7BW500 to SF12BW500
638 +
639 +925.7 - SF7BW500 to SF12BW500
640 +
641 +926.3 - SF7BW500 to SF12BW500
642 +
643 +926.9 - SF7BW500 to SF12BW500
644 +
645 +927.5 - SF7BW500 to SF12BW500
646 +
647 +923.3 - SF12BW500(RX2 downlink only)
648 +
649 +
650 +
651 +=== 2.7.3 CN470-510 (CN470) ===
652 +
653 +Used in China, Default use CHE=1
654 +
655 +(% style="color:#037691" %)**Uplink:**
656 +
657 +486.3 - SF7BW125 to SF12BW125
658 +
659 +486.5 - SF7BW125 to SF12BW125
660 +
661 +486.7 - SF7BW125 to SF12BW125
662 +
663 +486.9 - SF7BW125 to SF12BW125
664 +
665 +487.1 - SF7BW125 to SF12BW125
666 +
667 +487.3 - SF7BW125 to SF12BW125
668 +
669 +487.5 - SF7BW125 to SF12BW125
670 +
671 +487.7 - SF7BW125 to SF12BW125
672 +
673 +
674 +(% style="color:#037691" %)**Downlink:**
675 +
676 +506.7 - SF7BW125 to SF12BW125
677 +
678 +506.9 - SF7BW125 to SF12BW125
679 +
680 +507.1 - SF7BW125 to SF12BW125
681 +
682 +507.3 - SF7BW125 to SF12BW125
683 +
684 +507.5 - SF7BW125 to SF12BW125
685 +
686 +507.7 - SF7BW125 to SF12BW125
687 +
688 +507.9 - SF7BW125 to SF12BW125
689 +
690 +508.1 - SF7BW125 to SF12BW125
691 +
692 +505.3 - SF12BW125 (RX2 downlink only)
693 +
694 +
695 +
696 +=== 2.7.4 AU915-928(AU915) ===
697 +
698 +Default use CHE=2
699 +
700 +(% style="color:#037691" %)**Uplink:**
701 +
702 +916.8 - SF7BW125 to SF12BW125
703 +
704 +917.0 - SF7BW125 to SF12BW125
705 +
706 +917.2 - SF7BW125 to SF12BW125
707 +
708 +917.4 - SF7BW125 to SF12BW125
709 +
710 +917.6 - SF7BW125 to SF12BW125
711 +
712 +917.8 - SF7BW125 to SF12BW125
713 +
714 +918.0 - SF7BW125 to SF12BW125
715 +
716 +918.2 - SF7BW125 to SF12BW125
717 +
718 +
719 +(% style="color:#037691" %)**Downlink:**
720 +
721 +923.3 - SF7BW500 to SF12BW500
722 +
723 +923.9 - SF7BW500 to SF12BW500
724 +
725 +924.5 - SF7BW500 to SF12BW500
726 +
727 +925.1 - SF7BW500 to SF12BW500
728 +
729 +925.7 - SF7BW500 to SF12BW500
730 +
731 +926.3 - SF7BW500 to SF12BW500
732 +
733 +926.9 - SF7BW500 to SF12BW500
734 +
735 +927.5 - SF7BW500 to SF12BW500
736 +
737 +923.3 - SF12BW500(RX2 downlink only)
738 +
739 +
740 +
741 +=== 2.7.5 AS920-923 & AS923-925 (AS923) ===
742 +
743 +(% style="color:#037691" %)**Default Uplink channel:**
744 +
745 +923.2 - SF7BW125 to SF10BW125
746 +
747 +923.4 - SF7BW125 to SF10BW125
748 +
749 +
750 +(% style="color:#037691" %)**Additional Uplink Channel**:
751 +
752 +(OTAA mode, channel added by JoinAccept message)
753 +
754 +(% style="color:#037691" %)**AS920~~AS923 for Japan, Malaysia, Singapore**:
755 +
756 +922.2 - SF7BW125 to SF10BW125
757 +
758 +922.4 - SF7BW125 to SF10BW125
759 +
760 +922.6 - SF7BW125 to SF10BW125
761 +
762 +922.8 - SF7BW125 to SF10BW125
763 +
764 +923.0 - SF7BW125 to SF10BW125
765 +
766 +922.0 - SF7BW125 to SF10BW125
767 +
768 +
769 +(% style="color:#037691" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**:
770 +
771 +923.6 - SF7BW125 to SF10BW125
772 +
773 +923.8 - SF7BW125 to SF10BW125
774 +
775 +924.0 - SF7BW125 to SF10BW125
776 +
777 +924.2 - SF7BW125 to SF10BW125
778 +
779 +924.4 - SF7BW125 to SF10BW125
780 +
781 +924.6 - SF7BW125 to SF10BW125
782 +
783 +
784 +(% style="color:#037691" %)** Downlink:**
785 +
786 +Uplink channels 1-8 (RX1)
787 +
788 +923.2 - SF10BW125 (RX2)
789 +
790 +
791 +
792 +=== 2.7.6 KR920-923 (KR920) ===
793 +
794 +Default channel:
795 +
796 +922.1 - SF7BW125 to SF12BW125
797 +
798 +922.3 - SF7BW125 to SF12BW125
799 +
800 +922.5 - SF7BW125 to SF12BW125
801 +
802 +
803 +(% style="color:#037691" %)**Uplink: (OTAA mode, channel added by JoinAccept message)**
804 +
805 +922.1 - SF7BW125 to SF12BW125
806 +
807 +922.3 - SF7BW125 to SF12BW125
808 +
809 +922.5 - SF7BW125 to SF12BW125
810 +
811 +922.7 - SF7BW125 to SF12BW125
812 +
813 +922.9 - SF7BW125 to SF12BW125
814 +
815 +923.1 - SF7BW125 to SF12BW125
816 +
817 +923.3 - SF7BW125 to SF12BW125
818 +
819 +
820 +(% style="color:#037691" %)**Downlink:**
821 +
822 +Uplink channels 1-7(RX1)
823 +
824 +921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
825 +
826 +
827 +
828 +=== 2.7.7 IN865-867 (IN865) ===
829 +
830 +(% style="color:#037691" %)** Uplink:**
831 +
832 +865.0625 - SF7BW125 to SF12BW125
833 +
834 +865.4025 - SF7BW125 to SF12BW125
835 +
836 +865.9850 - SF7BW125 to SF12BW125
837 +
838 +
839 +(% style="color:#037691" %) **Downlink:**
840 +
841 +Uplink channels 1-3 (RX1)
842 +
843 +866.550 - SF10BW125 (RX2)
844 +
845 +
846 +
847 +
848 +== 2.8 LED Indicator ==
849 +
850 +The LSE01 has an internal LED which is to show the status of different state.
851 +
852 +* Blink once when device power on.
853 +* Solid ON for 5 seconds once device successful Join the network.
854 +* Blink once when device transmit a packet.
855 +
856 +== 2.9 Installation in Soil ==
857 +
858 +**Measurement the soil surface**
859 +
860 +
861 +[[image:1654506634463-199.png]] ​
862 +
660 660  (((
661 -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.
864 +(((
865 +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.
662 662  )))
867 +)))
663 663  
869 +
870 +
871 +[[image:1654506665940-119.png]]
872 +
664 664  (((
665 -The battery is designed to last for several years depends on the actually use environment and update interval. 
874 +Dig a hole with diameter > 20CM.
666 666  )))
667 667  
668 668  (((
669 -The battery related documents as below:
878 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
670 670  )))
671 671  
672 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
673 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
674 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
675 675  
882 +== 2.10 ​Firmware Change Log ==
883 +
676 676  (((
677 -[[image:image-20220709101450-2.png]]
885 +**Firmware download link:**
678 678  )))
679 679  
888 +(((
889 +[[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/]]
890 +)))
680 680  
892 +(((
893 +
894 +)))
681 681  
682 -=== 2.8.2  Power consumption Analyze ===
896 +(((
897 +**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
898 +)))
683 683  
684 684  (((
685 -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.
901 +
686 686  )))
687 687  
904 +(((
905 +**V1.0.**
906 +)))
688 688  
689 689  (((
690 -Instruction to use as below:
909 +Release
691 691  )))
692 692  
912 +
913 +== 2.11 ​Battery Analysis ==
914 +
915 +=== 2.11.1 ​Battery Type ===
916 +
693 693  (((
694 -(% 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/]]
918 +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.
695 695  )))
696 696  
921 +(((
922 +The battery is designed to last for more than 5 years for the LSN50.
923 +)))
697 697  
698 698  (((
699 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
926 +(((
927 +The battery-related documents are as below:
700 700  )))
929 +)))
701 701  
702 702  * (((
703 -Product Model
932 +[[Battery Dimension>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
704 704  )))
705 705  * (((
706 -Uplink Interval
935 +[[Lithium-Thionyl Chloride Battery  datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
707 707  )))
708 708  * (((
709 -Working Mode
938 +[[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/]]
710 710  )))
711 711  
712 -(((
713 -And the Life expectation in difference case will be shown on the right.
714 -)))
941 + [[image:image-20220610172436-1.png]]
715 715  
716 -[[image:image-20220709110451-3.png]]
717 717  
718 718  
945 +=== 2.11.2 ​Battery Note ===
719 719  
720 -=== 2.8.3  ​Battery Note ===
721 -
722 722  (((
723 723  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.
724 724  )))
... ... @@ -725,169 +725,302 @@
725 725  
726 726  
727 727  
728 -=== 2.8.4  Replace the battery ===
953 +=== 2.11.3 Replace the battery ===
729 729  
730 730  (((
731 -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).
956 +If Battery is lower than 2.7v, user should replace the battery of LSE01.
732 732  )))
733 733  
734 -
735 -
736 -= 3. ​ Access NB-IoT Module =
737 -
738 738  (((
739 -Users can directly access the AT command set of the NB-IoT module.
960 +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.
740 740  )))
741 741  
742 742  (((
743 -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/]] 
964 +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)
744 744  )))
745 745  
746 -[[image:1657333200519-600.png]]
747 747  
748 748  
969 += 3. ​Using the AT Commands =
749 749  
750 -= 4.  Using the AT Commands =
971 +== 3.1 Access AT Commands ==
751 751  
752 -== 4.1  Access AT Commands ==
753 753  
754 -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/]]
974 +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.
755 755  
976 +[[image:1654501986557-872.png||height="391" width="800"]]
756 756  
757 -AT+<CMD>?  : Help on <CMD>
758 758  
759 -AT+<CMD>         : Run <CMD>
979 +Or if you have below board, use below connection:
760 760  
761 -AT+<CMD>=<value> : Set the value
762 762  
763 -AT+<CMD>=?  : Get the value
982 +[[image:1654502005655-729.png||height="503" width="801"]]
764 764  
765 765  
985 +
986 +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:
987 +
988 +
989 + [[image:1654502050864-459.png||height="564" width="806"]]
990 +
991 +
992 +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]]
993 +
994 +
995 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%) : Help on <CMD>
996 +
997 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD> **(%%) : Run <CMD>
998 +
999 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=<value>**(%%) : Set the value
1000 +
1001 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=?**(%%)  : Get the value
1002 +
1003 +
766 766  (% style="color:#037691" %)**General Commands**(%%)      
767 767  
768 -AT  : Attention       
1006 +(% style="background-color:#dcdcdc" %)**AT**(%%)  : Attention       
769 769  
770 -AT?  : Short Help     
1008 +(% style="background-color:#dcdcdc" %)**AT?**(%%)  : Short Help     
771 771  
772 -ATZ  : MCU Reset    
1010 +(% style="background-color:#dcdcdc" %)**ATZ**(%%)  : MCU Reset    
773 773  
774 -AT+TDC  : Application Data Transmission Interval
1012 +(% style="background-color:#dcdcdc" %)**AT+TDC**(%%)  : Application Data Transmission Interval 
775 775  
776 -AT+CFG  : Print all configurations
777 777  
778 -AT+CFGMOD           : Working mode selection
1015 +(% style="color:#037691" %)**Keys, IDs and EUIs management**
779 779  
780 -AT+INTMOD            : Set the trigger interrupt mode
1017 +(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%)              : Application EUI      
781 781  
782 -AT+5VT  : Set extend the time of 5V power  
1019 +(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%)              : Application Key     
783 783  
784 -AT+PRO  : Choose agreement
1021 +(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%)            : Application Session Key
785 785  
786 -AT+WEIGRE  : Get weight or set weight to 0
1023 +(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%)              : Device Address     
787 787  
788 -AT+WEIGAP  : Get or Set the GapValue of weight
1025 +(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%)                   : Device EUI     
789 789  
790 -AT+RXDL  : Extend the sending and receiving time
1027 +(% style="background-color:#dcdcdc" %)**AT+NWKID**(%%)               : Network ID (You can enter this command change only after successful network connection) 
791 791  
792 -AT+CNTFAC  : Get or set counting parameters
1029 +(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%)          : Network Session Key Joining and sending date on LoRa network  
793 793  
794 -AT+SERVADDR  : Server Address
1031 +(% style="background-color:#dcdcdc" %)**AT+CFM**(%%)  : Confirm Mode       
795 795  
1033 +(% style="background-color:#dcdcdc" %)**AT+CFS**(%%)                     : Confirm Status       
796 796  
797 -(% style="color:#037691" %)**COAP Management**      
1035 +(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%)  : Join LoRa? Network       
798 798  
799 -AT+URI            : Resource parameters
1037 +(% style="background-color:#dcdcdc" %)**AT+NJM**(%%)  : LoRa? Network Join Mode    
800 800  
1039 +(% style="background-color:#dcdcdc" %)**AT+NJS**(%%)                     : LoRa? Network Join Status    
801 801  
802 -(% style="color:#037691" %)**UDP Management**
1041 +(% style="background-color:#dcdcdc" %)**AT+RECV**(%%)                  : Print Last Received Data in Raw Format
803 803  
804 -AT+CFM          : Upload confirmation mode (only valid for UDP)
1043 +(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%)                : Print Last Received Data in Binary Format      
805 805  
1045 +(% style="background-color:#dcdcdc" %)**AT+SEND**(%%)                  : Send Text Data      
806 806  
807 -(% style="color:#037691" %)**MQTT Management**
1047 +(% style="background-color:#dcdcdc" %)**AT+SENB**(%%)                  : Send Hexadecimal Data
808 808  
809 -AT+CLIENT               : Get or Set MQTT client
810 810  
811 -AT+UNAME  : Get or Set MQTT Username
1050 +(% style="color:#037691" %)**LoRa Network Management**
812 812  
813 -AT+PWD                  : Get or Set MQTT password
1052 +(% style="background-color:#dcdcdc" %)**AT+ADR**(%%)          : Adaptive Rate
814 814  
815 -AT+PUBTOPIC  : Get or Set MQTT publish topic
1054 +(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%)  : LoRa Class(Currently only support class A
816 816  
817 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
1056 +(% style="background-color:#dcdcdc" %)**AT+DCS**(%%)  : Duty Cycle Setting 
818 818  
1058 +(% style="background-color:#dcdcdc" %)**AT+DR**(%%)  : Data Rate (Can Only be Modified after ADR=0)     
819 819  
820 -(% style="color:#037691" %)**Information**          
1060 +(% style="background-color:#dcdcdc" %)**AT+FCD**(%%)  : Frame Counter Downlink       
821 821  
822 -AT+FDR  : Factory Data Reset
1062 +(% style="background-color:#dcdcdc" %)**AT+FCU**(%%)  : Frame Counter Uplink   
823 823  
824 -AT+PWORD  : Serial Access Password
1064 +(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%)  : Join Accept Delay1
825 825  
1066 +(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%)  : Join Accept Delay2
826 826  
1068 +(% style="background-color:#dcdcdc" %)**AT+PNM**(%%)  : Public Network Mode   
827 827  
828 -= ​5.  FAQ =
1070 +(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%)  : Receive Delay1      
829 829  
830 -== 5.1 ​ How to Upgrade Firmware ==
1072 +(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%)  : Receive Delay2      
831 831  
1074 +(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%)  : Rx2 Window Data Rate 
832 832  
1076 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%)  : Rx2 Window Frequency
1077 +
1078 +(% style="background-color:#dcdcdc" %)**AT+TXP**(%%)  : Transmit Power
1079 +
1080 +(% style="background-color:#dcdcdc" %)**AT+ MOD**(%%)  : Set work mode
1081 +
1082 +
1083 +(% style="color:#037691" %)**Information** 
1084 +
1085 +(% style="background-color:#dcdcdc" %)**AT+RSSI**(%%)           : RSSI of the Last Received Packet   
1086 +
1087 +(% style="background-color:#dcdcdc" %)**AT+SNR**(%%)           : SNR of the Last Received Packet   
1088 +
1089 +(% style="background-color:#dcdcdc" %)**AT+VER**(%%)           : Image Version and Frequency Band       
1090 +
1091 +(% style="background-color:#dcdcdc" %)**AT+FDR**(%%)           : Factory Data Reset
1092 +
1093 +(% style="background-color:#dcdcdc" %)**AT+PORT**(%%)  : Application Port    
1094 +
1095 +(% style="background-color:#dcdcdc" %)**AT+CHS**(%%)  : Get or Set Frequency (Unit: Hz) for Single Channel Mode
1096 +
1097 + (% style="background-color:#dcdcdc" %)**AT+CHE**(%%)  : Get or Set eight channels mode, Only for US915, AU915, CN470
1098 +
1099 +
1100 += ​4. FAQ =
1101 +
1102 +== 4.1 ​How to change the LoRa Frequency Bands/Region? ==
1103 +
833 833  (((
834 -User can upgrade the firmware for 1) bug fix, 2) new feature release.
1105 +You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]].
1106 +When downloading the images, choose the required image file for download. ​
835 835  )))
836 836  
837 837  (((
838 -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]]
1110 +
839 839  )))
840 840  
841 841  (((
842 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
1114 +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.
843 843  )))
844 844  
1117 +(((
1118 +
1119 +)))
845 845  
1121 +(((
1122 +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.
1123 +)))
846 846  
847 -= 6.  Trouble Shooting =
1125 +(((
1126 +
1127 +)))
848 848  
849 -== 6.1  ​Connection problem when uploading firmware ==
1129 +(((
1130 +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.
1131 +)))
850 850  
1133 +[[image:image-20220606154726-3.png]]
851 851  
1135 +
1136 +When you use the TTN network, the US915 frequency bands use are:
1137 +
1138 +* 903.9 - SF7BW125 to SF10BW125
1139 +* 904.1 - SF7BW125 to SF10BW125
1140 +* 904.3 - SF7BW125 to SF10BW125
1141 +* 904.5 - SF7BW125 to SF10BW125
1142 +* 904.7 - SF7BW125 to SF10BW125
1143 +* 904.9 - SF7BW125 to SF10BW125
1144 +* 905.1 - SF7BW125 to SF10BW125
1145 +* 905.3 - SF7BW125 to SF10BW125
1146 +* 904.6 - SF8BW500
1147 +
852 852  (((
853 -**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]]
1149 +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:
1150 +
1151 +* (% style="color:#037691" %)**AT+CHE=2**
1152 +* (% style="color:#037691" %)**ATZ**
854 854  )))
855 855  
856 -(% class="wikigeneratedid" %)
857 857  (((
858 858  
1157 +
1158 +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.
859 859  )))
860 860  
1161 +(((
1162 +
1163 +)))
861 861  
862 -== 6.2  AT Command input doesn't work ==
1165 +(((
1166 +The **AU915** band is similar. Below are the AU915 Uplink Channels.
1167 +)))
863 863  
1169 +[[image:image-20220606154825-4.png]]
1170 +
1171 +
1172 +== 4.2 ​Can I calibrate LSE01 to different soil types? ==
1173 +
1174 +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]].
1175 +
1176 +
1177 += 5. Trouble Shooting =
1178 +
1179 +== 5.1 ​Why I can't join TTN in US915 / AU915 bands? ==
1180 +
1181 +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.
1182 +
1183 +
1184 +== 5.2 AT Command input doesn't work ==
1185 +
864 864  (((
865 865  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.
1188 +)))
866 866  
867 -
1190 +
1191 +== 5.3 Device rejoin in at the second uplink packet ==
1192 +
1193 +(% style="color:#4f81bd" %)**Issue describe as below:**
1194 +
1195 +[[image:1654500909990-784.png]]
1196 +
1197 +
1198 +(% style="color:#4f81bd" %)**Cause for this issue:**
1199 +
1200 +(((
1201 +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.
868 868  )))
869 869  
870 870  
871 -= 7. ​ Order Info =
1205 +(% style="color:#4f81bd" %)**Solution: **
872 872  
1207 +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:
873 873  
874 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1209 +[[image:1654500929571-736.png||height="458" width="832"]]
875 875  
876 876  
1212 += 6. ​Order Info =
1213 +
1214 +
1215 +Part Number**:** (% style="color:#4f81bd" %)**LSE01-XX-YY**
1216 +
1217 +
1218 +(% style="color:#4f81bd" %)**XX**(%%)**:** The default frequency band
1219 +
1220 +* (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band
1221 +* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
1222 +* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
1223 +* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
1224 +* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
1225 +* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
1226 +* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1227 +* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1228 +
1229 +(% style="color:#4f81bd" %)**YY**(%%)**: **Battery Option
1230 +
1231 +* (% style="color:red" %)**4**(%%): 4000mAh battery
1232 +* (% style="color:red" %)**8**(%%): 8500mAh battery
1233 +
877 877  (% class="wikigeneratedid" %)
878 878  (((
879 879  
880 880  )))
881 881  
882 -= 8.  Packing Info =
1239 += 7. Packing Info =
883 883  
884 884  (((
885 885  
886 886  
887 887  (% style="color:#037691" %)**Package Includes**:
1245 +)))
888 888  
889 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
890 -* External antenna x 1
1247 +* (((
1248 +LSE01 LoRaWAN Soil Moisture & EC Sensor x 1
891 891  )))
892 892  
893 893  (((
... ... @@ -894,22 +894,24 @@
894 894  
895 895  
896 896  (% style="color:#037691" %)**Dimension and weight**:
1255 +)))
897 897  
898 -
899 -* Device Size: 13.0 x 5 x 4.5 cm
900 -* Device Weight: 150g
901 -* Package Size / pcs : 15 x 12x 5.5 cm
902 -* Weight / pcs : 220g
1257 +* (((
1258 +Device Size: cm
903 903  )))
1260 +* (((
1261 +Device Weight: g
1262 +)))
1263 +* (((
1264 +Package Size / pcs : cm
1265 +)))
1266 +* (((
1267 +Weight / pcs : g
904 904  
905 -(((
906 906  
907 -
908 -
909 -
910 910  )))
911 911  
912 -= 9.  Support =
1272 += 8. Support =
913 913  
914 914  * 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.
915 915  * 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]]
1657259653666-883.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -344.4 KB
Content
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
image-20220708133731-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.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