Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 95.5
edited by Xiaoling
on 2022/07/09 10:58
Change comment: There is no comment for this version
To version 32.11
edited by Xiaoling
on 2022/06/07 11:39
Change comment: There is no comment for this version

Summary

Details

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