Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 108.10
edited by Xiaoling
on 2023/04/04 12:01
Change comment: There is no comment for this version
To version 44.1
edited by Xiaoling
on 2022/07/08 10:14
Change comment: Uploaded new attachment "1657246476176-652.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDDS75 NB-IoT Distance Detect Sensor User Manual
1 +NSE01 - NB-IoT Soil Moisture & EC Sensor User Manual
Content
... ... @@ -1,960 +1,1100 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20220709085040-1.png||height="542" width="524"]]
2 +[[image:image-20220606151504-2.jpeg||height="554" width="554"]]
3 3  
4 4  
5 5  
6 6  
7 7  
8 -**Table of Contents:**
9 9  
10 -{{toc/}}
11 11  
12 12  
13 13  
14 14  
15 15  
14 +**Table of Contents:**
16 16  
17 -= 1.  Introduction =
18 18  
19 19  
20 -== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
21 21  
22 -(((
23 -
24 24  
25 -(((
26 -(((
27 -The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
28 -)))
29 29  
30 -(((
31 -The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
32 -)))
21 += 1. Introduction =
33 33  
34 -(((
35 -NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
36 -)))
23 +== 1.1 ​What is LoRaWAN Soil Moisture & EC Sensor ==
37 37  
38 38  (((
39 -NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
40 -)))
26 +
41 41  
42 -(((
43 -NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
44 -)))
28 +Dragino NSE01 is an **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.
45 45  
46 -(((
47 -To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
48 -)))
49 -)))
30 +It can detect **Soil Moisture, Soil Temperature and Soil Conductivity**, and upload its value to the server wirelessly.
50 50  
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.
33 +
34 +NSE01 are powered by **8500mAh Li-SOCI2** batteries, which can be used for up to 5 years.
35 +
51 51  
52 52  )))
53 53  
54 -[[image:1657327959271-447.png]]
39 +[[image:1654503236291-817.png]]
55 55  
56 56  
42 +[[image:1657245163077-232.png]]
57 57  
58 -== 1.2 ​ Features ==
59 59  
60 60  
61 -* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
46 +== 1.2 ​Features ==
47 +
48 +* LoRaWAN 1.0.3 Class A
62 62  * Ultra low power consumption
63 -* Distance Detection by Ultrasonic technology
64 -* Flat object range 280mm - 7500mm
65 -* Accuracy: ±(1cm+S*0.3%) (S: Distance)
66 -* Cable Length: 25cm
50 +* Monitor Soil Moisture
51 +* Monitor Soil Temperature
52 +* Monitor Soil Conductivity
53 +* Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
67 67  * AT Commands to change parameters
68 68  * Uplink on periodically
69 69  * Downlink to change configure
70 70  * IP66 Waterproof Enclosure
71 -* Micro SIM card slot for NB-IoT SIM
72 -* 8500mAh Battery for long term use
58 +* 4000mAh or 8500mAh Battery for long term use
73 73  
74 -== 1.3  Specification ==
60 +== 1.3 Specification ==
75 75  
62 +Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
76 76  
77 -(% style="color:#037691" %)**Common DC Characteristics:**
64 +[[image:image-20220606162220-5.png]]
78 78  
79 -* Supply Voltage: 2.1v ~~ 3.6v
80 -* Operating Temperature: -40 ~~ 85°C
81 81  
82 -(% style="color:#037691" %)**NB-IoT Spec:**
83 83  
84 -* B1 @H-FDD: 2100MHz
85 -* B3 @H-FDD: 1800MHz
86 -* B8 @H-FDD: 900MHz
87 -* B5 @H-FDD: 850MHz
88 -* B20 @H-FDD: 800MHz
89 -* B28 @H-FDD: 700MHz
68 +== ​1.4 Applications ==
90 90  
91 -(% style="color:#037691" %)**Battery:**
70 +* Smart Agriculture
92 92  
93 -* Li/SOCI2 un-chargeable battery
94 -* Capacity: 8500mAh
95 -* Self Discharge: <1% / Year @ 25°C
96 -* Max continuously current: 130mA
97 -* Max boost current: 2A, 1 second
72 +(% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
73 +​
98 98  
99 -(% style="color:#037691" %)**Power Consumption**
75 +== 1.5 Firmware Change log ==
100 100  
101 -* STOP Mode: 10uA @ 3.3v
102 -* Max transmit power: 350mA@3.3v
103 103  
104 -== ​1.4  Applications ==
78 +**LSE01 v1.0 :**  Release
105 105  
106 106  
107 -* Smart Buildings & Home Automation
108 -* Logistics and Supply Chain Management
109 -* Smart Metering
110 -* Smart Agriculture
111 -* Smart Cities
112 -* Smart Factory
113 113  
114 -(% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
115 -​
82 += 2. Configure LSE01 to connect to LoRaWAN network =
116 116  
84 +== 2.1 How it works ==
117 117  
86 +(((
87 +The LSE01 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LSE0150. It will automatically join the network via OTAA and start to send the sensor value
88 +)))
118 118  
119 -== 1.5  Pin Definitions ==
90 +(((
91 +In case you can’t set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H3.200BUsingtheATCommands"]].
92 +)))
120 120  
121 121  
122 -[[image:1657328609906-564.png]]
123 123  
96 +== 2.2 ​Quick guide to connect to LoRaWAN server (OTAA) ==
124 124  
98 +Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LG308>>url:http://www.dragino.com/products/lora/item/140-lg308.html]] as a LoRaWAN gateway in this example.
125 125  
126 -= 2.  Use NDDS75 to communicate with IoT Server =
127 127  
101 +[[image:1654503992078-669.png]]
128 128  
129 -== 2.1  How it works ==
130 130  
104 +The LG308 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server.
131 131  
106 +
107 +(% style="color:blue" %)**Step 1**(%%):  Create a device in TTN with the OTAA keys from LSE01.
108 +
109 +Each LSE01 is shipped with a sticker with the default device EUI as below:
110 +
111 +[[image:image-20220606163732-6.jpeg]]
112 +
113 +You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
114 +
115 +**Add APP EUI in the application**
116 +
117 +
118 +[[image:1654504596150-405.png]]
119 +
120 +
121 +
122 +**Add APP KEY and DEV EUI**
123 +
124 +[[image:1654504683289-357.png]]
125 +
126 +
127 +
128 +(% style="color:blue" %)**Step 2**(%%): Power on LSE01
129 +
130 +
131 +Put a Jumper on JP2 to power on the device. ( The Jumper must be in FLASH position).
132 +
133 +[[image:image-20220606163915-7.png]]
134 +
135 +
136 +(% style="color:blue" %)**Step 3**(%%)**:** The LSE01 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel.
137 +
138 +[[image:1654504778294-788.png]]
139 +
140 +
141 +
142 +== 2.3 Uplink Payload ==
143 +
144 +
145 +=== 2.3.1 MOD~=0(Default Mode) ===
146 +
147 +LSE01 will uplink payload via LoRaWAN with below payload format: 
148 +
132 132  (((
133 -The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 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 NDDS75.
150 +Uplink payload includes in total 11 bytes.
134 134  )))
135 135  
153 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
154 +|(((
155 +**Size**
136 136  
137 -(((
138 -The diagram below shows the working flow in default firmware of NDDS75:
157 +**(bytes)**
158 +)))|**2**|**2**|**2**|**2**|**2**|**1**
159 +|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
160 +Temperature
161 +
162 +(Reserve, Ignore now)
163 +)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]]|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]]|(((
164 +MOD & Digital Interrupt
165 +
166 +(Optional)
139 139  )))
140 140  
141 -(((
142 -
169 +=== 2.3.2 MOD~=1(Original value) ===
170 +
171 +This mode can get the original AD value of moisture and original conductivity (with temperature drift compensation).
172 +
173 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
174 +|(((
175 +**Size**
176 +
177 +**(bytes)**
178 +)))|**2**|**2**|**2**|**2**|**2**|**1**
179 +|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
180 +Temperature
181 +
182 +(Reserve, Ignore now)
183 +)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]](raw)|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]](raw)|(((
184 +MOD & Digital Interrupt
185 +
186 +(Optional)
143 143  )))
144 144  
145 -[[image:1657328659945-416.png]]
189 +=== 2.3.3 Battery Info ===
146 146  
147 147  (((
148 -
192 +Check the battery voltage for LSE01.
149 149  )))
150 150  
195 +(((
196 +Ex1: 0x0B45 = 2885mV
197 +)))
151 151  
152 -== 2.2 ​ Configure the NDDS75 ==
199 +(((
200 +Ex2: 0x0B49 = 2889mV
201 +)))
153 153  
154 154  
155 -=== 2.2.1 Test Requirement ===
156 156  
205 +=== 2.3.4 Soil Moisture ===
157 157  
158 158  (((
159 -To use NDDS75 in your city, make sure meet below requirements:
208 +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.
160 160  )))
161 161  
162 -* Your local operator has already distributed a NB-IoT Network there.
163 -* The local NB-IoT network used the band that NDDS75 supports.
164 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
211 +(((
212 +For example, if the data you get from the register is __0x05 0xDC__, the moisture content in the soil is
213 +)))
165 165  
166 166  (((
167 -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.
216 +
168 168  )))
169 169  
219 +(((
220 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
221 +)))
170 170  
171 -[[image:1657328756309-230.png]]
172 172  
173 173  
225 +=== 2.3.5 Soil Temperature ===
174 174  
175 -=== 2.2.2 Insert SIM card ===
227 +(((
228 + 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
229 +)))
176 176  
231 +(((
232 +**Example**:
233 +)))
177 177  
178 178  (((
179 -Insert the NB-IoT Card get from your provider.
236 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
180 180  )))
181 181  
182 182  (((
183 -User need to take out the NB-IoT module and insert the SIM card like below:
240 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
184 184  )))
185 185  
186 186  
187 -[[image:1657328884227-504.png]]
188 188  
245 +=== 2.3.6 Soil Conductivity (EC) ===
189 189  
247 +(((
248 +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).
249 +)))
190 190  
191 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
251 +(((
252 +For example, if the data you get from the register is 0x00 0xC8, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
253 +)))
192 192  
255 +(((
256 +Generally, the EC value of irrigation water is less than 800uS / cm.
257 +)))
193 193  
194 194  (((
260 +
261 +)))
262 +
195 195  (((
196 -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.
264 +
197 197  )))
198 -)))
199 199  
200 -[[image:image-20220709092052-2.png]]
267 +=== 2.3.7 MOD ===
201 201  
269 +Firmware version at least v2.1 supports changing mode.
202 202  
203 -(% style="color:blue" %)**Connection:**
271 +For example, bytes[10]=90
204 204  
205 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
273 +mod=(bytes[10]>>7)&0x01=1.
206 206  
207 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
208 208  
209 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
276 +**Downlink Command:**
210 210  
278 +If payload = 0x0A00, workmode=0
211 211  
212 -In the PC, use below serial tool settings:
280 +If** **payload =** **0x0A01, workmode=1
213 213  
214 -* Baud:  (% style="color:green" %)**9600**
215 -* Data bits:** (% style="color:green" %)8(%%)**
216 -* Stop bits: (% style="color:green" %)**1**
217 -* Parity:  (% style="color:green" %)**None**
218 -* Flow Control: (% style="color:green" %)**None**
219 219  
220 -(((
221 -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.
222 -)))
223 223  
224 -[[image:1657329814315-101.png]]
284 +=== 2.3.8 ​Decode payload in The Things Network ===
225 225  
286 +While using TTN network, you can add the payload format to decode the payload.
226 226  
288 +
289 +[[image:1654505570700-128.png]]
290 +
227 227  (((
228 -(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]**
292 +The payload decoder function for TTN is here:
229 229  )))
230 230  
295 +(((
296 +LSE01 TTN Payload Decoder: [[https:~~/~~/www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0>>https://www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0]]
297 +)))
231 231  
232 232  
233 -=== 2.2.4 Use CoAP protocol to uplink data ===
300 +== 2.4 Uplink Interval ==
234 234  
302 +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"]]
235 235  
236 -(% 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/]]**
237 237  
238 238  
306 +== 2.5 Downlink Payload ==
307 +
308 +By default, LSE50 prints the downlink payload to console port.
309 +
310 +[[image:image-20220606165544-8.png]]
311 +
312 +
239 239  (((
240 -**Use below commands:**
314 +(% style="color:blue" %)**Examples:**
241 241  )))
242 242  
243 -* (((
244 -(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
317 +(((
318 +
245 245  )))
320 +
246 246  * (((
247 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
322 +(% style="color:blue" %)**Set TDC**
248 248  )))
249 -* (((
250 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
251 251  
325 +(((
326 +If the payload=0100003C, it means set the END Node’s TDC to 0x00003C=60(S), while type code is 01.
327 +)))
252 252  
253 -
329 +(((
330 +Payload:    01 00 00 1E    TDC=30S
254 254  )))
255 255  
256 256  (((
257 -For parameter description, please refer to AT command set
334 +Payload:    01 00 00 3C    TDC=60S
335 +)))
258 258  
337 +(((
259 259  
260 260  )))
261 261  
262 -[[image:1657330452568-615.png]]
341 +* (((
342 +(% style="color:blue" %)**Reset**
343 +)))
263 263  
345 +(((
346 +If payload = 0x04FF, it will reset the LSE01
347 +)))
264 264  
265 265  
350 +* (% style="color:blue" %)**CFM**
351 +
352 +Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0
353 +
354 +
355 +
356 +== 2.6 ​Show Data in DataCake IoT Server ==
357 +
266 266  (((
267 -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.
359 +[[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:
360 +)))
268 268  
362 +(((
269 269  
270 270  )))
271 271  
272 -[[image:1657330472797-498.png]]
366 +(((
367 +(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the network at this time.
368 +)))
273 273  
370 +(((
371 +(% 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:
372 +)))
274 274  
275 275  
276 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
375 +[[image:1654505857935-743.png]]
277 277  
278 278  
279 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
280 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
281 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
378 +[[image:1654505874829-548.png]]
282 282  
283 -[[image:1657330501006-241.png]]
284 284  
381 +(% style="color:blue" %)**Step 3**(%%)**:**  Create an account or log in Datacake.
285 285  
286 -[[image:1657330533775-472.png]]
383 +(% style="color:blue" %)**Step 4**(%%)**:**  Search the LSE01 and add DevEUI.
287 287  
288 288  
386 +[[image:1654505905236-553.png]]
289 289  
290 -=== 2.2.6 Use MQTT protocol to uplink data ===
291 291  
389 +After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
292 292  
293 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
294 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
295 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
296 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
297 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
298 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
299 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
391 +[[image:1654505925508-181.png]]
300 300  
301 -[[image:1657249978444-674.png]]
302 302  
303 303  
304 -[[image:1657330723006-866.png]]
395 +== 2.7 Frequency Plans ==
305 305  
397 +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.
306 306  
307 -(((
308 -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.
309 -)))
310 310  
400 +=== 2.7.1 EU863-870 (EU868) ===
311 311  
402 +(% style="color:#037691" %)** Uplink:**
312 312  
313 -=== 2.2.7 Use TCP protocol to uplink data ===
404 +868.1 - SF7BW125 to SF12BW125
314 314  
406 +868.3 - SF7BW125 to SF12BW125 and SF7BW250
315 315  
316 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
317 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
408 +868.5 - SF7BW125 to SF12BW125
318 318  
319 -[[image:image-20220709093918-1.png]]
410 +867.1 - SF7BW125 to SF12BW125
320 320  
412 +867.3 - SF7BW125 to SF12BW125
321 321  
322 -[[image:image-20220709093918-2.png]]
414 +867.5 - SF7BW125 to SF12BW125
323 323  
416 +867.7 - SF7BW125 to SF12BW125
324 324  
418 +867.9 - SF7BW125 to SF12BW125
325 325  
326 -=== 2.2.8 Change Update Interval ===
420 +868.8 - FSK
327 327  
328 328  
329 -User can use below command to change the (% style="color:green" %)**uplink interval**.
423 +(% style="color:#037691" %)** Downlink:**
330 330  
331 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
425 +Uplink channels 1-9 (RX1)
332 332  
333 -(((
334 -
427 +869.525 - SF9BW125 (RX2 downlink only)
335 335  
336 336  
337 -(% style="color:red" %)**NOTE:**
338 338  
339 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
431 +=== 2.7.2 US902-928(US915) ===
340 340  
341 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
342 -)))
433 +Used in USA, Canada and South America. Default use CHE=2
343 343  
344 -(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
435 +(% style="color:#037691" %)**Uplink:**
345 345  
437 +903.9 - SF7BW125 to SF10BW125
346 346  
439 +904.1 - SF7BW125 to SF10BW125
347 347  
348 -== 2.3  Uplink Payload ==
441 +904.3 - SF7BW125 to SF10BW125
349 349  
443 +904.5 - SF7BW125 to SF10BW125
350 350  
351 -=== 2.3.1  Before Firmware v1.3.2 ===
445 +904.7 - SF7BW125 to SF10BW125
352 352  
447 +904.9 - SF7BW125 to SF10BW125
353 353  
354 -In this mode, uplink payload includes in total 14 bytes
449 +905.1 - SF7BW125 to SF10BW125
355 355  
356 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
357 -|=(% style="width: 60px;" %)(((
358 -**Size(bytes)**
359 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
360 -|(% 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"]]
451 +905.3 - SF7BW125 to SF10BW125
361 361  
362 -(((
363 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
364 -)))
365 365  
454 +(% style="color:#037691" %)**Downlink:**
366 366  
367 -[[image:1657331036973-987.png]]
456 +923.3 - SF7BW500 to SF12BW500
368 368  
458 +923.9 - SF7BW500 to SF12BW500
369 369  
460 +924.5 - SF7BW500 to SF12BW500
370 370  
371 -The payload is **ASCII** string, representative same HEX:
462 +925.1 - SF7BW500 to SF12BW500
372 372  
373 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
464 +925.7 - SF7BW500 to SF12BW500
374 374  
375 -**where :**
466 +926.3 - SF7BW500 to SF12BW500
376 376  
377 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
468 +926.9 - SF7BW500 to SF12BW500
378 378  
379 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
470 +927.5 - SF7BW500 to SF12BW500
380 380  
381 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
472 +923.3 - SF12BW500(RX2 downlink only)
382 382  
383 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
384 384  
385 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
386 386  
387 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
476 +=== 2.7.3 CN470-510 (CN470) ===
388 388  
389 -=== 2.3.2  Since firmware v1.3.2 ===
478 +Used in China, Default use CHE=1
390 390  
480 +(% style="color:#037691" %)**Uplink:**
391 391  
392 -In this mode, uplink payload includes 69 bytes in total by default.
482 +486.3 - SF7BW125 to SF12BW125
393 393  
394 -Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
484 +486.5 - SF7BW125 to SF12BW125
395 395  
396 -(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
397 -|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:70px" %)**4**|(% style="width:40px" %)**2**|(% style="width:60px" %)**4**
398 -|=(% style="width: 95px;" %)**Value**|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp.......
486 +486.7 - SF7BW125 to SF12BW125
399 399  
400 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
488 +486.9 - SF7BW125 to SF12BW125
401 401  
402 -[[image:image-20220908175246-1.png]]
490 +487.1 - SF7BW125 to SF12BW125
403 403  
492 +487.3 - SF7BW125 to SF12BW125
404 404  
405 -The payload is ASCII string, representative same HEX:
494 +487.5 - SF7BW125 to SF12BW125
406 406  
407 -**0x (% style="color:red" %)f867787050213317 (% style="color:blue" %)0084 (% style="color:green" %)0cf4 (% style="color:#00b0f0" %)1e (% style="color:#7030a0" %)01 (% style="color:#d60093" %)00(% style="color:#a14d07" %) 0039 (% style="color:#0020b0" %)6315537b (% style="color:#663300" %)00396319baf0 00396319ba3c 00396319b988 00396319b8d4 00396319b820 00396319b76c 00396319b6b8 00396319b604 (%%)**
496 +487.7 - SF7BW125 to SF12BW125
408 408  
409 -**where:**
410 410  
411 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
499 +(% style="color:#037691" %)**Downlink:**
412 412  
413 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
501 +506.7 - SF7BW125 to SF12BW125
414 414  
415 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
503 +506.9 - SF7BW125 to SF12BW125
416 416  
417 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
505 +507.1 - SF7BW125 to SF12BW125
418 418  
419 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
507 +507.3 - SF7BW125 to SF12BW125
420 420  
421 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
509 +507.5 - SF7BW125 to SF12BW125
422 422  
423 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
511 +507.7 - SF7BW125 to SF12BW125
424 424  
425 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
513 +507.9 - SF7BW125 to SF12BW125
426 426  
427 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
515 +508.1 - SF7BW125 to SF12BW125
428 428  
429 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
517 +505.3 - SF12BW125 (RX2 downlink only)
430 430  
431 -== 2.4  Payload Explanation and Sensor Interface ==
432 432  
433 433  
434 -=== 2.4.1  Device ID ===
521 +=== 2.7.4 AU915-928(AU915) ===
435 435  
523 +Default use CHE=2
436 436  
437 -(((
438 -By default, the Device ID equal to the last 6 bytes of IMEI.
439 -)))
525 +(% style="color:#037691" %)**Uplink:**
440 440  
441 -(((
442 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
527 +916.8 - SF7BW125 to SF12BW125
443 443  
444 -
445 -)))
529 +917.0 - SF7BW125 to SF12BW125
446 446  
447 -(((
448 -(% style="color:blue" %)**Example :**
449 -)))
531 +917.2 - SF7BW125 to SF12BW125
450 450  
451 -(((
452 -AT+DEUI=A84041F15612
453 -)))
533 +917.4 - SF7BW125 to SF12BW125
454 454  
455 -(((
456 -The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
457 -)))
535 +917.6 - SF7BW125 to SF12BW125
458 458  
537 +917.8 - SF7BW125 to SF12BW125
459 459  
460 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
539 +918.0 - SF7BW125 to SF12BW125
461 461  
462 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
541 +918.2 - SF7BW125 to SF12BW125
463 463  
464 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
465 465  
544 +(% style="color:#037691" %)**Downlink:**
466 466  
467 -(% style="color:blue" %)**Example :**
546 +923.3 - SF7BW500 to SF12BW500
468 468  
469 -AT+DEUI=868411056754138
548 +923.9 - SF7BW500 to SF12BW500
470 470  
550 +924.5 - SF7BW500 to SF12BW500
471 471  
552 +925.1 - SF7BW500 to SF12BW500
472 472  
473 -=== 2.4.2  Version Info ===
554 +925.7 - SF7BW500 to SF12BW500
474 474  
556 +926.3 - SF7BW500 to SF12BW500
475 475  
476 -(((
477 -Specify the software version: 0x64=100, means firmware version 1.00.
478 -)))
558 +926.9 - SF7BW500 to SF12BW500
479 479  
480 -(((
481 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
482 -)))
560 +927.5 - SF7BW500 to SF12BW500
483 483  
562 +923.3 - SF12BW500(RX2 downlink only)
484 484  
485 485  
486 -=== 2.4.3  Battery Info ===
487 487  
566 +=== 2.7.5 AS920-923 & AS923-925 (AS923) ===
488 488  
489 -(((
490 -Ex1: 0x0B45 = 2885mV
491 -)))
568 +(% style="color:#037691" %)**Default Uplink channel:**
492 492  
493 -(((
494 -Ex2: 0x0B49 = 2889mV
495 -)))
570 +923.2 - SF7BW125 to SF10BW125
496 496  
572 +923.4 - SF7BW125 to SF10BW125
497 497  
498 498  
499 -=== 2.4.4  Signal Strength ===
575 +(% style="color:#037691" %)**Additional Uplink Channel**:
500 500  
577 +(OTAA mode, channel added by JoinAccept message)
501 501  
502 -(((
503 -NB-IoT Network signal Strength.
504 -)))
579 +(% style="color:#037691" %)**AS920~~AS923 for Japan, Malaysia, Singapore**:
505 505  
506 -(((
507 -**Ex1: 0x1d = 29**
508 -)))
581 +922.2 - SF7BW125 to SF10BW125
509 509  
510 -(((
511 -(% style="color:blue" %)**0**(%%)  -113dBm or less
512 -)))
583 +922.4 - SF7BW125 to SF10BW125
513 513  
514 -(((
515 -(% style="color:blue" %)**1**(%%)  -111dBm
516 -)))
585 +922.6 - SF7BW125 to SF10BW125
517 517  
518 -(((
519 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
520 -)))
587 +922.8 - SF7BW125 to SF10BW125
521 521  
522 -(((
523 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
524 -)))
589 +923.0 - SF7BW125 to SF10BW125
525 525  
526 -(((
527 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
528 -)))
591 +922.0 - SF7BW125 to SF10BW125
529 529  
530 530  
594 +(% style="color:#037691" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**:
531 531  
532 -=== 2.4.5  Distance ===
596 +923.6 - SF7BW125 to SF10BW125
533 533  
598 +923.8 - SF7BW125 to SF10BW125
534 534  
535 -Get the distance. Flat object range 280mm - 7500mm.
600 +924.0 - SF7BW125 to SF10BW125
536 536  
537 -(((
538 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
539 -)))
602 +924.2 - SF7BW125 to SF10BW125
540 540  
541 -(((
542 -(((
543 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
544 -)))
545 -)))
604 +924.4 - SF7BW125 to SF10BW125
546 546  
547 -(((
548 -
549 -)))
606 +924.6 - SF7BW125 to SF10BW125
550 550  
551 -(((
552 -
553 -)))
554 554  
555 -=== 2.4.6  Digital Interrupt ===
609 +(% style="color:#037691" %)** Downlink:**
556 556  
611 +Uplink channels 1-8 (RX1)
557 557  
558 -(((
559 -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.
560 -)))
613 +923.2 - SF10BW125 (RX2)
561 561  
562 -(((
563 -The command is:
564 -)))
565 565  
566 -(((
567 -(% 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]])**.**
568 -)))
569 569  
617 +=== 2.7.6 KR920-923 (KR920) ===
570 570  
571 -(((
572 -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.
573 -)))
619 +Default channel:
574 574  
621 +922.1 - SF7BW125 to SF12BW125
575 575  
576 -(((
577 -Example:
578 -)))
623 +922.3 - SF7BW125 to SF12BW125
579 579  
580 -(((
581 -0x(00): Normal uplink packet.
582 -)))
625 +922.5 - SF7BW125 to SF12BW125
583 583  
584 -(((
585 -0x(01): Interrupt Uplink Packet.
586 -)))
587 587  
628 +(% style="color:#037691" %)**Uplink: (OTAA mode, channel added by JoinAccept message)**
588 588  
630 +922.1 - SF7BW125 to SF12BW125
589 589  
590 -=== 2.4.7  ​+5V Output ===
632 +922.3 - SF7BW125 to SF12BW125
591 591  
634 +922.5 - SF7BW125 to SF12BW125
592 592  
593 -(((
594 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
595 -)))
636 +922.7 - SF7BW125 to SF12BW125
596 596  
638 +922.9 - SF7BW125 to SF12BW125
597 597  
598 -(((
599 -The 5V output time can be controlled by AT Command.
640 +923.1 - SF7BW125 to SF12BW125
600 600  
601 -
602 -)))
642 +923.3 - SF7BW125 to SF12BW125
603 603  
604 -(((
605 -(% style="color:blue" %)**AT+5VT=1000**
606 606  
607 -
608 -)))
645 +(% style="color:#037691" %)**Downlink:**
609 609  
610 -(((
611 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
612 -)))
647 +Uplink channels 1-7(RX1)
613 613  
649 +921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
614 614  
615 615  
616 -== 2.5  Downlink Payload ==
617 617  
653 +=== 2.7.7 IN865-867 (IN865) ===
618 618  
619 -By default, NDDS75 prints the downlink payload to console port.
655 +(% style="color:#037691" %)** Uplink:**
620 620  
621 -[[image:image-20220709100028-1.png]]
657 +865.0625 - SF7BW125 to SF12BW125
622 622  
659 +865.4025 - SF7BW125 to SF12BW125
623 623  
661 +865.9850 - SF7BW125 to SF12BW125
662 +
663 +
664 +(% style="color:#037691" %) **Downlink:**
665 +
666 +Uplink channels 1-3 (RX1)
667 +
668 +866.550 - SF10BW125 (RX2)
669 +
670 +
671 +
672 +
673 +== 2.8 LED Indicator ==
674 +
675 +The LSE01 has an internal LED which is to show the status of different state.
676 +
677 +* Blink once when device power on.
678 +* Solid ON for 5 seconds once device successful Join the network.
679 +* Blink once when device transmit a packet.
680 +
681 +== 2.9 Installation in Soil ==
682 +
683 +**Measurement the soil surface**
684 +
685 +
686 +[[image:1654506634463-199.png]] ​
687 +
624 624  (((
625 -(% style="color:blue" %)**Examples:**
689 +(((
690 +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.
626 626  )))
692 +)))
627 627  
694 +
695 +
696 +[[image:1654506665940-119.png]]
697 +
628 628  (((
629 -
699 +Dig a hole with diameter > 20CM.
630 630  )))
631 631  
632 -* (((
633 -(% style="color:blue" %)**Set TDC**
702 +(((
703 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
634 634  )))
635 635  
706 +
707 +== 2.10 ​Firmware Change Log ==
708 +
636 636  (((
637 -If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
710 +**Firmware download link:**
638 638  )))
639 639  
640 640  (((
641 -Payload:    01 00 00 1E    TDC=30S
714 +[[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/]]
642 642  )))
643 643  
644 644  (((
645 -Payload:    01 00 00 3C    TDC=60S
718 +
646 646  )))
647 647  
648 648  (((
722 +**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
723 +)))
724 +
725 +(((
649 649  
650 650  )))
651 651  
652 -* (((
653 -(% style="color:blue" %)**Reset**
729 +(((
730 +**V1.0.**
654 654  )))
655 655  
656 656  (((
657 -If payload = 0x04FF, it will reset the NDDS75
734 +Release
658 658  )))
659 659  
660 660  
661 -* (% style="color:blue" %)**INTMOD**
738 +== 2.11 ​Battery Analysis ==
662 662  
740 +=== 2.11.1 ​Battery Type ===
741 +
663 663  (((
664 -Downlink Payload: 06000003, Set AT+INTMOD=3
743 +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.
665 665  )))
666 666  
746 +(((
747 +The battery is designed to last for more than 5 years for the LSN50.
748 +)))
667 667  
750 +(((
751 +(((
752 +The battery-related documents are as below:
753 +)))
754 +)))
668 668  
669 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
756 +* (((
757 +[[Battery Dimension>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
758 +)))
759 +* (((
760 +[[Lithium-Thionyl Chloride Battery  datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
761 +)))
762 +* (((
763 +[[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/]]
764 +)))
670 670  
766 + [[image:image-20220610172436-1.png]]
671 671  
672 -(% style="color:blue" %)** ➢ AT Command:**
673 673  
674 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
675 675  
676 -² When min=0, and max≠0, Alarm higher than max
770 +=== 2.11.2 ​Battery Note ===
677 677  
678 -² When min≠0, and max=0, Alarm lower than min
772 +(((
773 +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.
774 +)))
679 679  
680 -² When min≠0 and max≠0, Alarm higher than max or lower than min
681 681  
682 682  
683 -(% style="color:blue" %)** Example:**
778 +=== 2.11.3 Replace the battery ===
684 684  
685 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
780 +(((
781 +If Battery is lower than 2.7v, user should replace the battery of LSE01.
782 +)))
686 686  
784 +(((
785 +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.
786 +)))
687 687  
788 +(((
789 +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)
790 +)))
688 688  
689 -== 2.7  Set the number of data to be uploaded and the recording time ==
690 690  
691 691  
692 -(% style="color:blue" %)** ➢ AT Command:**
794 += 3. ​Using the AT Commands =
693 693  
694 -* (% style="color:#037691" %)** AT+TR=900** (%%) ~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
695 -* (% style="color:#037691" %)** AT+NOUD=8**             (%%) ~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
796 +== 3.1 Access AT Commands ==
696 696  
697 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
698 698  
699 -[[image:image-20221009001114-1.png||height="687" width="955"]]
799 +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.
700 700  
801 +[[image:1654501986557-872.png||height="391" width="800"]]
701 701  
702 702  
703 -== 2.8  Read or Clear cached data ==
804 +Or if you have below board, use below connection:
704 704  
705 705  
706 -(% style="color:blue" %)** ➢ AT Command:**
807 +[[image:1654502005655-729.png||height="503" width="801"]]
707 707  
708 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
709 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
710 710  
711 -[[image:image-20220908175333-2.png]]
712 712  
811 +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:
713 713  
714 714  
715 -== 2.9  ​LED Indicator ==
814 + [[image:1654502050864-459.png||height="564" width="806"]]
716 716  
717 717  
718 -The NDDS75 has an internal LED which is to show the status of different state.
817 +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]]
719 719  
720 720  
721 -* 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)
722 -* Then the LED will be on for 1 second means device is boot normally.
723 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
724 -* For each uplink probe, LED will be on for 500ms.
820 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%) : Help on <CMD>
725 725  
726 -(((
727 -
728 -)))
822 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD> **(%%) : Run <CMD>
729 729  
824 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=<value>**(%%) : Set the value
730 730  
826 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=?**(%%)  : Get the value
731 731  
732 -== 2.10  ​Firmware Change Log ==
733 733  
829 +(% style="color:#037691" %)**General Commands**(%%)      
734 734  
735 -(((
736 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]]
737 -)))
831 +(% style="background-color:#dcdcdc" %)**AT**(%%)  : Attention       
738 738  
739 -(((
740 -
741 -)))
833 +(% style="background-color:#dcdcdc" %)**AT?**(%%)  : Short Help     
742 742  
743 -(((
744 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
745 -)))
835 +(% style="background-color:#dcdcdc" %)**ATZ**(%%)  : MCU Reset    
746 746  
837 +(% style="background-color:#dcdcdc" %)**AT+TDC**(%%)  : Application Data Transmission Interval 
747 747  
748 748  
749 -== 2.11 Battery & Power Consumption ==
840 +(% style="color:#037691" %)**Keys, IDs and EUIs management**
750 750  
842 +(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%)              : Application EUI      
751 751  
752 -PS-LB-NA uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
844 +(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%)              : Application Key     
753 753  
754 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
846 +(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%)            : Application Session Key
755 755  
756 -= 3. ​ Access NB-IoT Module =
848 +(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%)              : Device Address     
757 757  
850 +(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%)                   : Device EUI     
758 758  
759 -(((
760 -Users can directly access the AT command set of the NB-IoT module.
761 -)))
852 +(% style="background-color:#dcdcdc" %)**AT+NWKID**(%%)               : Network ID (You can enter this command change only after successful network connection) 
762 762  
763 -(((
764 -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/]] 
854 +(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%)          : Network Session Key Joining and sending date on LoRa network  
765 765  
766 -
767 -)))
856 +(% style="background-color:#dcdcdc" %)**AT+CFM**(%%)  : Confirm Mode       
768 768  
769 -[[image:1657333200519-600.png]]
858 +(% style="background-color:#dcdcdc" %)**AT+CFS**(%%)                     : Confirm Status       
770 770  
860 +(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%)  : Join LoRa? Network       
771 771  
862 +(% style="background-color:#dcdcdc" %)**AT+NJM**(%%)  : LoRa? Network Join Mode    
772 772  
773 -= 4.  Using the AT Commands =
864 +(% style="background-color:#dcdcdc" %)**AT+NJS**(%%)                     : LoRa? Network Join Status    
774 774  
866 +(% style="background-color:#dcdcdc" %)**AT+RECV**(%%)                  : Print Last Received Data in Raw Format
775 775  
776 -== 4.1  Access AT Commands ==
868 +(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%)                : Print Last Received Data in Binary Format      
777 777  
870 +(% style="background-color:#dcdcdc" %)**AT+SEND**(%%)                  : Send Text Data      
778 778  
779 -See this link for detail:  [[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]
872 +(% style="background-color:#dcdcdc" %)**AT+SENB**(%%)                  : Send Hexadecimal Data
780 780  
781 781  
782 -AT+<CMD>?  :  Help on <CMD>
875 +(% style="color:#037691" %)**LoRa Network Management**
783 783  
784 -AT+<CMD>         :  Run <CMD>
877 +(% style="background-color:#dcdcdc" %)**AT+ADR**(%%)          : Adaptive Rate
785 785  
786 -AT+<CMD>=<value> :  Set the value
879 +(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%)  : LoRa Class(Currently only support class A
787 787  
788 -AT+<CMD>=?  :  Get the value
881 +(% style="background-color:#dcdcdc" %)**AT+DCS**(%%)  : Duty Cycle Setting 
789 789  
883 +(% style="background-color:#dcdcdc" %)**AT+DR**(%%)  : Data Rate (Can Only be Modified after ADR=0)     
790 790  
791 -(% style="color:#037691" %)**General Commands**(%%)      
885 +(% style="background-color:#dcdcdc" %)**AT+FCD**(%%)  : Frame Counter Downlink       
792 792  
793 -AT  :  Attention       
887 +(% style="background-color:#dcdcdc" %)**AT+FCU**(%%)  : Frame Counter Uplink   
794 794  
795 -AT?  :  Short Help     
889 +(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%)  : Join Accept Delay1
796 796  
797 -ATZ  :  MCU Reset    
891 +(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%)  : Join Accept Delay2
798 798  
799 -AT+TDC  :  Application Data Transmission Interval
893 +(% style="background-color:#dcdcdc" %)**AT+PNM**(%%)  : Public Network Mode   
800 800  
801 -AT+CFG  :  Print all configurations
895 +(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%)  : Receive Delay1      
802 802  
803 -AT+CFGMOD           :  Working mode selection
897 +(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%)  : Receive Delay2      
804 804  
805 -AT+INTMOD            :  Set the trigger interrupt mode
899 +(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%)  : Rx2 Window Data Rate 
806 806  
807 -AT+5VT  :  Set extend the time of 5V power  
901 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%)  : Rx2 Window Frequency
808 808  
809 -AT+PRO  :  Choose agreement
903 +(% style="background-color:#dcdcdc" %)**AT+TXP**(%%)  : Transmit Power
810 810  
811 -AT+WEIGRE  :  Get weight or set weight to 0
905 +(% style="background-color:#dcdcdc" %)**AT+ MOD**(%%)  : Set work mode
812 812  
813 -AT+WEIGAP  :  Get or Set the GapValue of weight
814 814  
815 -AT+RXDL  :  Extend the sending and receiving time
908 +(% style="color:#037691" %)**Information** 
816 816  
817 -AT+CNTFAC  :  Get or set counting parameters
910 +(% style="background-color:#dcdcdc" %)**AT+RSSI**(%%)           : RSSI of the Last Received Packet   
818 818  
819 -AT+SERVADDR  :  Server Address
912 +(% style="background-color:#dcdcdc" %)**AT+SNR**(%%)           : SNR of the Last Received Packet   
820 820  
821 -AT+TR  :  Get or Set record time"
914 +(% style="background-color:#dcdcdc" %)**AT+VER**(%%)           : Image Version and Frequency Band       
822 822  
823 -AT+APN     :  Get or set the APN
916 +(% style="background-color:#dcdcdc" %)**AT+FDR**(%%)           : Factory Data Reset
824 824  
825 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
918 +(% style="background-color:#dcdcdc" %)**AT+PORT**(%%)  : Application Port    
826 826  
827 -AT+DNSCFG  : Get or Set DNS Server
920 +(% style="background-color:#dcdcdc" %)**AT+CHS**(%%)  : Get or Set Frequency (Unit: Hz) for Single Channel Mode
828 828  
829 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
922 + (% style="background-color:#dcdcdc" %)**AT+CHE**(%%)  : Get or Set eight channels mode, Only for US915, AU915, CN470
830 830  
831 -AT+NOUD  :  Get or Set the number of data to be uploaded
832 832  
833 -AT+CDP     :  Read or Clear cached data
925 += ​4. FAQ =
834 834  
835 -AT+LDDSALARM :  Get or Set alarm of distance
927 +== 4.1 ​How to change the LoRa Frequency Bands/Region? ==
836 836  
929 +(((
930 +You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]].
931 +When downloading the images, choose the required image file for download. ​
932 +)))
837 837  
838 -(% style="color:#037691" %)**COAP Management**      
934 +(((
935 +
936 +)))
839 839  
840 -AT+URI            :  Resource parameters
938 +(((
939 +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.
940 +)))
841 841  
942 +(((
943 +
944 +)))
842 842  
843 -(% style="color:#037691" %)**UDP Management**
946 +(((
947 +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.
948 +)))
844 844  
845 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
950 +(((
951 +
952 +)))
846 846  
954 +(((
955 +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.
956 +)))
847 847  
848 -(% style="color:#037691" %)**MQTT Management**
958 +[[image:image-20220606154726-3.png]]
849 849  
850 -AT+CLIENT  :  Get or Set MQTT client
851 851  
852 -AT+UNAME  :  Get or Set MQTT Username
961 +When you use the TTN network, the US915 frequency bands use are:
853 853  
854 -AT+PWD  :  Get or Set MQTT password
963 +* 903.9 - SF7BW125 to SF10BW125
964 +* 904.1 - SF7BW125 to SF10BW125
965 +* 904.3 - SF7BW125 to SF10BW125
966 +* 904.5 - SF7BW125 to SF10BW125
967 +* 904.7 - SF7BW125 to SF10BW125
968 +* 904.9 - SF7BW125 to SF10BW125
969 +* 905.1 - SF7BW125 to SF10BW125
970 +* 905.3 - SF7BW125 to SF10BW125
971 +* 904.6 - SF8BW500
855 855  
856 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
973 +(((
974 +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:
857 857  
858 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
976 +* (% style="color:#037691" %)**AT+CHE=2**
977 +* (% style="color:#037691" %)**ATZ**
978 +)))
859 859  
980 +(((
981 +
860 860  
861 -(% style="color:#037691" %)**Information**          
983 +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.
984 +)))
862 862  
863 -AT+FDR  :  Factory Data Reset
986 +(((
987 +
988 +)))
864 864  
865 -AT+PWORD  :  Serial Access Password
990 +(((
991 +The **AU915** band is similar. Below are the AU915 Uplink Channels.
992 +)))
866 866  
994 +[[image:image-20220606154825-4.png]]
867 867  
868 868  
869 -= ​5.  FAQ =
997 +== 4.2 ​Can I calibrate LSE01 to different soil types? ==
870 870  
999 +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]].
871 871  
872 -== 5.1 ​ How to Upgrade Firmware ==
873 873  
1002 += 5. Trouble Shooting =
874 874  
875 -(((
876 -User can upgrade the firmware for 1) bug fix, 2) new feature release.
877 -)))
1004 +== 5.1 ​Why I can't join TTN in US915 / AU915 bands? ==
878 878  
879 -(((
880 -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]]
881 -)))
1006 +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.
882 882  
1008 +
1009 +== 5.2 AT Command input doesn't work ==
1010 +
883 883  (((
884 -(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
1012 +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.
885 885  )))
886 886  
887 887  
1016 +== 5.3 Device rejoin in at the second uplink packet ==
888 888  
889 -= 6.  Trouble Shooting =
1018 +(% style="color:#4f81bd" %)**Issue describe as below:**
890 890  
1020 +[[image:1654500909990-784.png]]
891 891  
892 -== 6.1  ​Connection problem when uploading firmware ==
893 893  
1023 +(% style="color:#4f81bd" %)**Cause for this issue:**
894 894  
895 895  (((
896 -**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]]
1026 +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.
897 897  )))
898 898  
899 -(% class="wikigeneratedid" %)
900 -(((
901 -
902 -)))
903 903  
1030 +(% style="color:#4f81bd" %)**Solution: **
904 904  
905 -== 6.2  AT Command input doesn't work ==
1032 +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:
906 906  
1034 +[[image:1654500929571-736.png||height="458" width="832"]]
907 907  
908 -(((
909 -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.
910 910  
911 -
912 -)))
1037 += 6. ​Order Info =
913 913  
914 914  
915 -= 7. ​ Order Info =
1040 +Part Number**:** (% style="color:#4f81bd" %)**LSE01-XX-YY**
916 916  
917 917  
918 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1043 +(% style="color:#4f81bd" %)**XX**(%%)**:** The default frequency band
919 919  
1045 +* (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band
1046 +* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
1047 +* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
1048 +* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
1049 +* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
1050 +* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
1051 +* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1052 +* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
920 920  
1054 +(% style="color:#4f81bd" %)**YY**(%%)**: **Battery Option
1055 +
1056 +* (% style="color:red" %)**4**(%%): 4000mAh battery
1057 +* (% style="color:red" %)**8**(%%): 8500mAh battery
1058 +
921 921  (% class="wikigeneratedid" %)
922 922  (((
923 923  
924 924  )))
925 925  
926 -= 8.  Packing Info =
1064 += 7. Packing Info =
927 927  
928 928  (((
929 929  
930 930  
931 931  (% style="color:#037691" %)**Package Includes**:
1070 +)))
932 932  
933 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
934 -* External antenna x 1
1072 +* (((
1073 +LSE01 LoRaWAN Soil Moisture & EC Sensor x 1
935 935  )))
936 936  
937 937  (((
938 938  
939 939  
940 -
941 941  (% style="color:#037691" %)**Dimension and weight**:
1080 +)))
942 942  
943 -* Device Size: 13.0 x 5 x 4.5 cm
944 -* Device Weight: 150g
945 -* Package Size / pcs : 15 x 12x 5.5 cm
946 -* Weight / pcs : 220g
1082 +* (((
1083 +Device Size: cm
947 947  )))
1085 +* (((
1086 +Device Weight: g
1087 +)))
1088 +* (((
1089 +Package Size / pcs : cm
1090 +)))
1091 +* (((
1092 +Weight / pcs : g
948 948  
949 -(((
950 950  
951 -
952 -
953 -
954 954  )))
955 955  
956 -= 9.  Support =
1097 += 8. Support =
957 957  
958 -
959 959  * 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.
960 960  * 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]]
1657249419225-449.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -81.0 KB
Content
1657249468462-536.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -483.6 KB
Content
1657249793983-486.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -85.8 KB
Content
1657249831934-534.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -72.5 KB
Content
1657249864775-321.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -87.0 KB
Content
1657249930215-289.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.3 KB
Content
1657249978444-674.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -139.5 KB
Content
1657249990869-686.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -96.9 KB
Content
1657250217799-140.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.7 KB
Content
1657250255956-604.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -99.0 KB
Content
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
image-20220708101605-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -87.5 KB
Content
image-20220708110657-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -251.7 KB
Content
image-20220708111918-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -38.8 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-20220908175246-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -31.1 KB
Content
image-20221009001114-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content