Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 108.2
edited by Xiaoling
on 2022/10/15 09:58
Change comment: There is no comment for this version
To version 63.2
edited by Xiaoling
on 2022/07/08 14:18
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 +NSE01 - NB-IoT Soil Moisture & EC Sensor User Manual
Content
... ... @@ -1,73 +1,61 @@
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 (% style="color:blue" %)**NB-IOT soil moisture & EC sensor**(%%) for agricultural IoT. Used to measure the soil moisture of saline-alkali soil and loam. The soil sensor uses the FDR method to calculate soil moisture and compensates it with soil temperature and electrical conductivity. It has also been calibrated for mineral soil types at the factory.
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 (% style="color:blue" %)**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 (% style="color:blue" %)**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  
46 +== 1.2 ​Features ==
47 +
48 +
61 61  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
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
67 67  * AT Commands to change parameters
68 68  * Uplink on periodically
69 69  * Downlink to change configure
70 70  * IP66 Waterproof Enclosure
57 +* Ultra-Low Power consumption
58 +* AT Commands to change parameters
71 71  * Micro SIM card slot for NB-IoT SIM
72 72  * 8500mAh Battery for long term use
73 73  
... ... @@ -88,128 +88,100 @@
88 88  * - B20 @H-FDD: 800MHz
89 89  * - B28 @H-FDD: 700MHz
90 90  
91 -(% style="color:#037691" %)**Battery:**
79 +(% style="color:#037691" %)**Probe Specification:**
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
81 +Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
98 98  
99 -(% style="color:#037691" %)**Power Consumption**
83 +[[image:image-20220708101224-1.png]]
100 100  
101 -* STOP Mode: 10uA @ 3.3v
102 -* Max transmit power: 350mA@3.3v
103 103  
86 +
104 104  == ​1.4  Applications ==
105 105  
106 -
107 -* Smart Buildings & Home Automation
108 -* Logistics and Supply Chain Management
109 -* Smart Metering
110 110  * Smart Agriculture
111 -* Smart Cities
112 -* Smart Factory
113 113  
114 114  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
115 115  ​
116 116  
117 -
118 -
119 -
120 120  == 1.5  Pin Definitions ==
121 121  
122 122  
123 -[[image:1657328609906-564.png]]
97 +[[image:1657246476176-652.png]]
124 124  
125 125  
126 126  
127 -= 2.  Use NDDS75 to communicate with IoT Server =
101 += 2.  Use NSE01 to communicate with IoT Server =
128 128  
129 -
130 130  == 2.1  How it works ==
131 131  
132 132  
133 133  (((
134 -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.
107 +The NSE01 is equipped with a NB-IoT module, the pre-loaded firmware in NSE01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NSE01.
135 135  )))
136 136  
137 137  
138 138  (((
139 -The diagram below shows the working flow in default firmware of NDDS75:
112 +The diagram below shows the working flow in default firmware of NSE01:
140 140  )))
141 141  
142 -(((
143 -
144 -)))
115 +[[image:image-20220708101605-2.png]]
145 145  
146 -[[image:1657328659945-416.png]]
147 -
148 148  (((
149 149  
150 150  )))
151 151  
152 152  
153 -== 2.2 ​ Configure the NDDS75 ==
154 154  
123 +== 2.2 ​ Configure the NSE01 ==
155 155  
125 +
156 156  === 2.2.1 Test Requirement ===
157 157  
158 158  
159 -(((
160 -To use NDDS75 in your city, make sure meet below requirements:
161 -)))
129 +To use NSE01 in your city, make sure meet below requirements:
162 162  
163 163  * Your local operator has already distributed a NB-IoT Network there.
164 -* The local NB-IoT network used the band that NDDS75 supports.
132 +* The local NB-IoT network used the band that NSE01 supports.
165 165  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
166 166  
167 167  (((
168 -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.
136 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NSE01 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
169 169  )))
170 170  
171 171  
172 -[[image:1657328756309-230.png]]
140 +[[image:1657249419225-449.png]]
173 173  
174 174  
175 175  
176 176  === 2.2.2 Insert SIM card ===
177 177  
178 -
179 -(((
180 180  Insert the NB-IoT Card get from your provider.
181 -)))
182 182  
183 -(((
184 184  User need to take out the NB-IoT module and insert the SIM card like below:
185 -)))
186 186  
187 187  
188 -[[image:1657328884227-504.png]]
151 +[[image:1657249468462-536.png]]
189 189  
190 190  
191 191  
192 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
155 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
193 193  
194 -
195 195  (((
196 196  (((
197 -User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
159 +User need to configure NSE01 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01 support AT Commands, user can use a USB to TTL adapter to connect to NSE01 and use AT Commands to configure it, as below.
198 198  )))
199 199  )))
200 200  
201 -[[image:image-20220709092052-2.png]]
202 202  
164 +**Connection:**
203 203  
204 -(% style="color:blue" %)**Connection:**
166 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
205 205  
206 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
168 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
207 207  
208 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
170 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
209 209  
210 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
211 211  
212 -
213 213  In the PC, use below serial tool settings:
214 214  
215 215  * Baud:  (% style="color:green" %)**9600**
... ... @@ -219,90 +219,70 @@
219 219  * Flow Control: (% style="color:green" %)**None**
220 220  
221 221  (((
222 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
182 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSE01. NSE01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
223 223  )))
224 224  
225 -[[image:1657329814315-101.png]]
185 +[[image:image-20220708110657-3.png]]
226 226  
187 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
227 227  
228 -(((
229 -(% 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]]**
230 -)))
231 231  
232 232  
233 -
234 234  === 2.2.4 Use CoAP protocol to uplink data ===
235 235  
193 +(% 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/]]
236 236  
237 -(% 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/]]**
238 238  
239 -
240 -(((
241 241  **Use below commands:**
242 -)))
243 243  
244 -* (((
245 -(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
246 -)))
247 -* (((
248 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
249 -)))
250 -* (((
251 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
198 +* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
199 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
200 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
252 252  
253 -
254 -
255 -)))
256 -
257 -(((
258 258  For parameter description, please refer to AT command set
259 259  
260 -
261 -)))
204 +[[image:1657249793983-486.png]]
262 262  
263 -[[image:1657330452568-615.png]]
264 264  
207 +After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server.
265 265  
209 +[[image:1657249831934-534.png]]
266 266  
267 -(((
268 -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.
269 269  
270 -
271 -)))
272 272  
273 -[[image:1657330472797-498.png]]
274 -
275 -
276 -
277 277  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
278 278  
215 +This feature is supported since firmware version v1.0.1
279 279  
280 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
281 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
282 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
283 283  
284 -[[image:1657330501006-241.png]]
218 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
219 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
220 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
285 285  
222 +[[image:1657249864775-321.png]]
286 286  
287 -[[image:1657330533775-472.png]]
288 288  
225 +[[image:1657249930215-289.png]]
289 289  
290 290  
228 +
291 291  === 2.2.6 Use MQTT protocol to uplink data ===
292 292  
231 +This feature is supported since firmware version v110
293 293  
294 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
295 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
296 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
297 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
298 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
299 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
300 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
301 301  
234 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
235 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
236 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
237 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
238 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
239 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
240 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
241 +
302 302  [[image:1657249978444-674.png]]
303 303  
304 304  
305 -[[image:1657330723006-866.png]]
245 +[[image:1657249990869-686.png]]
306 306  
307 307  
308 308  (((
... ... @@ -313,243 +313,177 @@
313 313  
314 314  === 2.2.7 Use TCP protocol to uplink data ===
315 315  
256 +This feature is supported since firmware version v110
316 316  
317 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
318 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
319 319  
320 -[[image:image-20220709093918-1.png]]
259 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
260 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
321 321  
262 +[[image:1657250217799-140.png]]
322 322  
323 -[[image:image-20220709093918-2.png]]
324 324  
265 +[[image:1657250255956-604.png]]
325 325  
326 326  
268 +
327 327  === 2.2.8 Change Update Interval ===
328 328  
329 -
330 330  User can use below command to change the (% style="color:green" %)**uplink interval**.
331 331  
332 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
273 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
333 333  
334 334  (((
335 -
336 -
337 -
338 338  (% style="color:red" %)**NOTE:**
277 +)))
339 339  
340 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
341 -
342 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
279 +(((
280 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
343 343  )))
344 344  
345 -(% 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).**
346 346  
347 347  
348 -
349 349  == 2.3  Uplink Payload ==
350 350  
287 +In this mode, uplink payload includes in total 18 bytes
351 351  
352 -=== 2.3.1  Before Firmware v1.3.2 ===
353 -
354 -
355 -In this mode, uplink payload includes in total 14 bytes
356 -
357 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
358 -|=(% style="width: 60px;" %)(((
289 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
290 +|=(% style="width: 50px;" %)(((
359 359  **Size(bytes)**
360 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
361 -|(% 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"]]
292 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 40px;" %)**1**
293 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H"]]|(% style="width:41px" %)[[Ver>>||anchor="H"]]|(% style="width:46px" %)[[BAT>>||anchor="H"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H"]]|(% style="width:108px" %)[[Soil Moisture>>||anchor="H"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H"]]
362 362  
363 -(((
364 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
365 -)))
295 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
366 366  
367 367  
368 -[[image:1657331036973-987.png]]
298 +[[image:image-20220708111918-4.png]]
369 369  
370 370  
371 -
372 -The payload is **ASCII** string, representative same HEX:
373 -
374 -(% style="background-color:yellow" %)**0x724031556159 0064 0c6c 19 0292 00 **
375 -
376 -**where :**
377 -
378 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
379 -
380 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
381 -
382 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
383 -
384 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
385 -
386 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
387 -
388 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
389 -
390 -
391 -
392 -
393 -=== **2.3.2  Since firmware v1.3.2** ===
394 -
395 -
396 -In this mode, uplink payload includes 69 bytes in total by default.
397 -
398 -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.
399 -
400 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
401 -|(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4
402 -|(% 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.......
403 -
404 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
405 -
406 -[[image:image-20220908175246-1.png]]
407 -
408 -
409 409  The payload is ASCII string, representative same HEX:
410 410  
411 -**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 (%%)**
303 +0x72403155615900640c7817075e0a8c02f900 where:
412 412  
413 -**where:**
305 +* Device ID: 0x 724031556159 = 724031556159
306 +* Version: 0x0064=100=1.0.0
414 414  
415 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
308 +* BAT: 0x0c78 = 3192 mV = 3.192V
309 +* Singal: 0x17 = 23
310 +* Soil Moisture: 0x075e= 1886 = 18.86  %
311 +* Soil Temperature:0x0a8c =2700=27 °C
312 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
313 +* Interrupt: 0x00 = 0
416 416  
417 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
315 +== 2.4  Payload Explanation and Sensor Interface ==
418 418  
419 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
420 420  
421 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
318 +=== 2.4.1  Device ID ===
422 422  
423 -* (% style="color:#037691" %)**Mod:**(%%)**  **0x01 = 1
320 +By default, the Device ID equal to the last 6 bytes of IMEI.
424 424  
425 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
322 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
426 426  
427 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
324 +**Example:**
428 428  
429 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
326 +AT+DEUI=A84041F15612
430 430  
431 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
328 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
432 432  
433 -* (% style="color:#037691" %) **8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
434 434  
435 435  
332 +=== 2.4.2  Version Info ===
436 436  
334 +Specify the software version: 0x64=100, means firmware version 1.00.
437 437  
438 -== 2.4  Payload Explanation and Sensor Interface ==
336 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
439 439  
440 440  
441 -=== 2.4.1  Device ID ===
442 442  
340 +=== 2.4.3  Battery Info ===
443 443  
444 444  (((
445 -By default, the Device ID equal to the last 6 bytes of IMEI.
343 +Check the battery voltage for LSE01.
446 446  )))
447 447  
448 448  (((
449 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
450 -
451 -
347 +Ex1: 0x0B45 = 2885mV
452 452  )))
453 453  
454 454  (((
455 -(% style="color:blue" %)**Example :**
351 +Ex2: 0x0B49 = 2889mV
456 456  )))
457 457  
458 -(((
459 -AT+DEUI=A84041F15612
460 -)))
461 461  
462 -(((
463 -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.
464 -)))
465 465  
356 +=== 2.4.4  Signal Strength ===
466 466  
467 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
358 +NB-IoT Network signal Strength.
468 468  
469 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
360 +**Ex1: 0x1d = 29**
470 470  
471 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
362 +(% style="color:blue" %)**0**(%%)  -113dBm or less
472 472  
364 +(% style="color:blue" %)**1**(%%)  -111dBm
473 473  
474 -(% style="color:blue" %)**Example :**
366 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
475 475  
476 -AT+DEUI=868411056754138
368 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
477 477  
370 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
478 478  
479 479  
480 -=== 2.4.2  Version Info ===
481 481  
374 +=== 2.4.5  Soil Moisture ===
482 482  
483 483  (((
484 -Specify the software version: 0x64=100, means firmware version 1.00.
377 +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.
485 485  )))
486 486  
487 487  (((
488 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
381 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
489 489  )))
490 490  
491 -
492 -
493 -=== 2.4.3  Battery Info ===
494 -
495 -
496 496  (((
497 -Ex1: 0x0B45 = 2885mV
385 +
498 498  )))
499 499  
500 500  (((
501 -Ex2: 0x0B49 = 2889mV
389 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
502 502  )))
503 503  
504 504  
505 505  
506 -=== 2.4.4  Signal Strength ===
394 +=== 2.4.6  Soil Temperature ===
507 507  
508 -
509 509  (((
510 -NB-IoT Network signal Strength.
397 + 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
511 511  )))
512 512  
513 513  (((
514 -**Ex1: 0x1d = 29**
401 +**Example**:
515 515  )))
516 516  
517 517  (((
518 -(% style="color:blue" %)**0**(%%)  -113dBm or less
405 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
519 519  )))
520 520  
521 521  (((
522 -(% style="color:blue" %)**1**(%%)  -111dBm
409 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
523 523  )))
524 524  
525 -(((
526 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
527 -)))
528 528  
529 -(((
530 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
531 -)))
532 532  
414 +=== 2.4.7  Soil Conductivity (EC) ===
415 +
533 533  (((
534 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
417 +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).
535 535  )))
536 536  
537 -
538 -
539 -=== 2.4.5  Distance ===
540 -
541 -
542 -Get the distance. Flat object range 280mm - 7500mm.
543 -
544 544  (((
545 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
421 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
546 546  )))
547 547  
548 548  (((
549 -(((
550 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
425 +Generally, the EC value of irrigation water is less than 800uS / cm.
551 551  )))
552 -)))
553 553  
554 554  (((
555 555  
... ... @@ -559,73 +559,45 @@
559 559  
560 560  )))
561 561  
562 -=== 2.4.6  Digital Interrupt ===
436 +=== 2.4.8  Digital Interrupt ===
563 563  
438 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server.
564 564  
565 -(((
566 -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.
567 -)))
568 -
569 -(((
570 570  The command is:
571 -)))
572 572  
573 -(((
574 -(% 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]])**.**
575 -)))
442 +(% 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]])**.**
576 576  
577 577  
578 -(((
579 -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.
580 -)))
445 +The lower four bits of this data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H"]] for the hardware and software set up.
581 581  
582 582  
583 -(((
584 584  Example:
585 -)))
586 586  
587 -(((
588 588  0x(00): Normal uplink packet.
589 -)))
590 590  
591 -(((
592 592  0x(01): Interrupt Uplink Packet.
593 -)))
594 594  
595 595  
596 596  
597 -=== 2.4.7  ​+5V Output ===
456 +=== 2.4.9  ​+5V Output ===
598 598  
458 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
599 599  
600 -(((
601 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
602 -)))
603 603  
604 -
605 -(((
606 606  The 5V output time can be controlled by AT Command.
607 607  
608 -
609 -)))
610 -
611 -(((
612 612  (% style="color:blue" %)**AT+5VT=1000**
613 613  
614 -
615 -)))
616 -
617 -(((
618 618  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
619 -)))
620 620  
621 621  
622 622  
623 623  == 2.5  Downlink Payload ==
624 624  
471 +By default, NSE01 prints the downlink payload to console port.
625 625  
626 -By default, NDDS75 prints the downlink payload to console port.
473 +[[image:image-20220708133731-5.png]]
627 627  
628 -[[image:image-20220709100028-1.png]]
629 629  
630 630  
631 631  (((
... ... @@ -661,129 +661,96 @@
661 661  )))
662 662  
663 663  (((
664 -If payload = 0x04FF, it will reset the NDDS75
510 +If payload = 0x04FF, it will reset the NSE01
665 665  )))
666 666  
667 667  
668 668  * (% style="color:blue" %)**INTMOD**
669 669  
670 -(((
671 671  Downlink Payload: 06000003, Set AT+INTMOD=3
672 -)))
673 673  
674 674  
675 675  
676 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
520 +== 2.6  ​LED Indicator ==
677 677  
522 +(((
523 +The NSE01 has an internal LED which is to show the status of different state.
678 678  
679 -(% style="color:blue" %)** ➢ AT Command:**
680 680  
681 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
526 +* When power on, NSE01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
527 +* Then the LED will be on for 1 second means device is boot normally.
528 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
529 +* For each uplink probe, LED will be on for 500ms.
530 +)))
682 682  
683 -² When min=0, and max≠0, Alarm higher than max
684 684  
685 -² When min≠0, and max=0, Alarm lower than min
686 686  
687 -² When min≠0 and max≠0, Alarm higher than max or lower than min
688 688  
535 +== 2.7  Installation in Soil ==
689 689  
690 -(% style="color:blue" %)** Example:**
537 +__**Measurement the soil surface**__
691 691  
692 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
539 +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. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]]
693 693  
541 +[[image:1657259653666-883.png]] ​
694 694  
695 695  
696 -== 2.7  Set the number of data to be uploaded and the recording time ==
544 +(((
545 +
697 697  
547 +(((
548 +Dig a hole with diameter > 20CM.
549 +)))
698 698  
699 -(% style="color:blue" %)** ➢ AT Command:**
551 +(((
552 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
553 +)))
554 +)))
700 700  
701 -* (% 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)
702 -* (% 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.
556 +[[image:1654506665940-119.png]]
703 703  
704 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
705 -
706 -[[image:image-20221009001114-1.png||height="687" width="955"]]
707 -
708 -
709 -
710 -== 2.8  Read or Clear cached data ==
711 -
712 -
713 -(% style="color:blue" %)** ➢ AT Command:**
714 -
715 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
716 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
717 -
718 -[[image:image-20220908175333-2.png]]
719 -
720 -
721 -
722 -== 2.9  ​LED Indicator ==
723 -
724 -
725 -The NDDS75 has an internal LED which is to show the status of different state.
726 -
727 -
728 -* 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)
729 -* Then the LED will be on for 1 second means device is boot normally.
730 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
731 -* For each uplink probe, LED will be on for 500ms.
732 -
733 733  (((
734 734  
735 735  )))
736 736  
737 737  
563 +== 2.8  ​Firmware Change Log ==
738 738  
739 -== 2.10  ​Firmware Change Log ==
740 740  
566 +Download URL & Firmware Change log
741 741  
742 -(((
743 -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]]
744 -)))
568 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
745 745  
746 -(((
747 -
748 -)))
749 749  
750 -(((
751 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
752 -)))
571 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H"]]
753 753  
754 754  
755 755  
756 -== 2.11  ​Battery Analysis ==
575 +== 2.9  ​Battery Analysis ==
757 757  
577 +=== 2.9.1  ​Battery Type ===
758 758  
759 -=== 2.11.1  ​Battery Type ===
760 760  
580 +The NSE01 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.
761 761  
762 -(((
763 -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.
764 -)))
765 765  
766 -(((
767 767  The battery is designed to last for several years depends on the actually use environment and update interval. 
768 -)))
769 769  
770 -(((
585 +
771 771  The battery related documents as below:
772 -)))
773 773  
774 774  * [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
775 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
589 +* [[Lithium-Thionyl Chloride Battery>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]][[ datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
776 776  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
777 777  
778 778  (((
779 -[[image:image-20220709101450-2.png]]
593 +[[image:image-20220708140453-6.png]]
780 780  )))
781 781  
782 782  
783 783  
784 -=== 2.11.2  Power consumption Analyze ===
598 +=== 2.9.2  Power consumption Analyze ===
785 785  
786 -
787 787  (((
788 788  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.
789 789  )))
... ... @@ -816,13 +816,12 @@
816 816  And the Life expectation in difference case will be shown on the right.
817 817  )))
818 818  
819 -[[image:image-20220709110451-3.png]]
632 +[[image:image-20220708141352-7.jpeg]]
820 820  
821 821  
822 822  
823 -=== 2.11.3  ​Battery Note ===
636 +=== 2.9.3  ​Battery Note ===
824 824  
825 -
826 826  (((
827 827  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.
828 828  )))
... ... @@ -829,11 +829,10 @@
829 829  
830 830  
831 831  
832 -=== 2.11.4  Replace the battery ===
644 +=== 2.9.4  Replace the battery ===
833 833  
834 -
835 835  (((
836 -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).
647 +The default battery pack of NSE01 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).
837 837  )))
838 838  
839 839  
... ... @@ -840,206 +840,322 @@
840 840  
841 841  = 3. ​ Access NB-IoT Module =
842 842  
843 -
844 844  (((
845 845  Users can directly access the AT command set of the NB-IoT module.
846 846  )))
847 847  
848 848  (((
849 -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/]] 
850 -
851 -
659 +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/]]
852 852  )))
853 853  
854 -[[image:1657333200519-600.png]]
662 +[[image:1657261119050-993.png]]
855 855  
664 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.jpg]]
856 856  
857 857  
858 -= 4.  Using the AT Commands =
859 859  
668 +== 3.1 Access AT Commands ==
860 860  
861 -== 4.1  Access AT Commands ==
862 862  
671 +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.
863 863  
864 -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]]
673 +[[image:1654501986557-872.png||height="391" width="800"]]
865 865  
866 866  
867 -AT+<CMD>?  :  Help on <CMD>
676 +Or if you have below board, use below connection:
868 868  
869 -AT+<CMD>         :  Run <CMD>
870 870  
871 -AT+<CMD>=<value> :  Set the value
679 +[[image:1654502005655-729.png||height="503" width="801"]]
872 872  
873 -AT+<CMD>=?  :  Get the value
874 874  
875 875  
683 +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:
684 +
685 +
686 + [[image:1654502050864-459.png||height="564" width="806"]]
687 +
688 +
689 +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]]
690 +
691 +
692 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%) : Help on <CMD>
693 +
694 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD> **(%%) : Run <CMD>
695 +
696 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=<value>**(%%) : Set the value
697 +
698 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=?**(%%)  : Get the value
699 +
700 +
876 876  (% style="color:#037691" %)**General Commands**(%%)      
877 877  
878 -AT  :  Attention       
703 +(% style="background-color:#dcdcdc" %)**AT**(%%)  : Attention       
879 879  
880 -AT?  :  Short Help     
705 +(% style="background-color:#dcdcdc" %)**AT?**(%%)  : Short Help     
881 881  
882 -ATZ  :  MCU Reset    
707 +(% style="background-color:#dcdcdc" %)**ATZ**(%%)  : MCU Reset    
883 883  
884 -AT+TDC  :  Application Data Transmission Interval
709 +(% style="background-color:#dcdcdc" %)**AT+TDC**(%%)  : Application Data Transmission Interval 
885 885  
886 -AT+CFG  :  Print all configurations
887 887  
888 -AT+CFGMOD           :  Working mode selection
712 +(% style="color:#037691" %)**Keys, IDs and EUIs management**
889 889  
890 -AT+INTMOD            :  Set the trigger interrupt mode
714 +(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%)              : Application EUI      
891 891  
892 -AT+5VT  :  Set extend the time of 5V power  
716 +(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%)              : Application Key     
893 893  
894 -AT+PRO  :  Choose agreement
718 +(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%)            : Application Session Key
895 895  
896 -AT+WEIGRE  :  Get weight or set weight to 0
720 +(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%)              : Device Address     
897 897  
898 -AT+WEIGAP  :  Get or Set the GapValue of weight
722 +(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%)                   : Device EUI     
899 899  
900 -AT+RXDL  :  Extend the sending and receiving time
724 +(% style="background-color:#dcdcdc" %)**AT+NWKID**(%%)               : Network ID (You can enter this command change only after successful network connection) 
901 901  
902 -AT+CNTFAC  :  Get or set counting parameters
726 +(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%)          : Network Session Key Joining and sending date on LoRa network  
903 903  
904 -AT+SERVADDR  :  Server Address
728 +(% style="background-color:#dcdcdc" %)**AT+CFM**(%%)  : Confirm Mode       
905 905  
906 -AT+TR  :  Get or Set record time"
730 +(% style="background-color:#dcdcdc" %)**AT+CFS**(%%)                     : Confirm Status       
907 907  
908 -AT+APN     :  Get or set the APN
732 +(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%)  : Join LoRa? Network       
909 909  
910 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
734 +(% style="background-color:#dcdcdc" %)**AT+NJM**(%%)  : LoRa? Network Join Mode    
911 911  
912 -AT+DNSCFG  : Get or Set DNS Server
736 +(% style="background-color:#dcdcdc" %)**AT+NJS**(%%)                     : LoRa? Network Join Status    
913 913  
914 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
738 +(% style="background-color:#dcdcdc" %)**AT+RECV**(%%)                  : Print Last Received Data in Raw Format
915 915  
916 -AT+NOUD  :  Get or Set the number of data to be uploaded
740 +(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%)                : Print Last Received Data in Binary Format      
917 917  
918 -AT+CDP     :  Read or Clear cached data
742 +(% style="background-color:#dcdcdc" %)**AT+SEND**(%%)                  : Send Text Data      
919 919  
920 -AT+LDDSALARM :  Get or Set alarm of distance
744 +(% style="background-color:#dcdcdc" %)**AT+SENB**(%%)                  : Send Hexadecimal Data
921 921  
922 922  
923 -(% style="color:#037691" %)**COAP Management**      
747 +(% style="color:#037691" %)**LoRa Network Management**
924 924  
925 -AT+URI            :  Resource parameters
749 +(% style="background-color:#dcdcdc" %)**AT+ADR**(%%)          : Adaptive Rate
926 926  
751 +(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%)  : LoRa Class(Currently only support class A
927 927  
928 -(% style="color:#037691" %)**UDP Management**
753 +(% style="background-color:#dcdcdc" %)**AT+DCS**(%%)  : Duty Cycle Setting 
929 929  
930 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
755 +(% style="background-color:#dcdcdc" %)**AT+DR**(%%)  : Data Rate (Can Only be Modified after ADR=0)     
931 931  
757 +(% style="background-color:#dcdcdc" %)**AT+FCD**(%%)  : Frame Counter Downlink       
932 932  
933 -(% style="color:#037691" %)**MQTT Management**
759 +(% style="background-color:#dcdcdc" %)**AT+FCU**(%%)  : Frame Counter Uplink   
934 934  
935 -AT+CLIENT  :  Get or Set MQTT client
761 +(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%)  : Join Accept Delay1
936 936  
937 -AT+UNAME  :  Get or Set MQTT Username
763 +(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%)  : Join Accept Delay2
938 938  
939 -AT+PWD  :  Get or Set MQTT password
765 +(% style="background-color:#dcdcdc" %)**AT+PNM**(%%)  : Public Network Mode   
940 940  
941 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
767 +(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%)  : Receive Delay1      
942 942  
943 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
769 +(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%)  : Receive Delay2      
944 944  
771 +(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%)  : Rx2 Window Data Rate 
945 945  
946 -(% style="color:#037691" %)**Information**          
773 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%)  : Rx2 Window Frequency
947 947  
948 -AT+FDR  :  Factory Data Reset
775 +(% style="background-color:#dcdcdc" %)**AT+TXP**(%%)  : Transmit Power
949 949  
950 -AT+PWORD  :  Serial Access Password
777 +(% style="background-color:#dcdcdc" %)**AT+ MOD**(%%)  : Set work mode
951 951  
952 952  
780 +(% style="color:#037691" %)**Information** 
953 953  
954 -= ​5.  FAQ =
782 +(% style="background-color:#dcdcdc" %)**AT+RSSI**(%%)           : RSSI of the Last Received Packet   
955 955  
784 +(% style="background-color:#dcdcdc" %)**AT+SNR**(%%)           : SNR of the Last Received Packet   
956 956  
957 -== 5.1 ​ How to Upgrade Firmware ==
786 +(% style="background-color:#dcdcdc" %)**AT+VER**(%%)           : Image Version and Frequency Band       
958 958  
788 +(% style="background-color:#dcdcdc" %)**AT+FDR**(%%)           : Factory Data Reset
959 959  
790 +(% style="background-color:#dcdcdc" %)**AT+PORT**(%%)  : Application Port    
791 +
792 +(% style="background-color:#dcdcdc" %)**AT+CHS**(%%)  : Get or Set Frequency (Unit: Hz) for Single Channel Mode
793 +
794 + (% style="background-color:#dcdcdc" %)**AT+CHE**(%%)  : Get or Set eight channels mode, Only for US915, AU915, CN470
795 +
796 +
797 += ​4. FAQ =
798 +
799 +== 4.1 ​How to change the LoRa Frequency Bands/Region? ==
800 +
960 960  (((
961 -User can upgrade the firmware for 1) bug fix, 2) new feature release.
802 +You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]].
803 +When downloading the images, choose the required image file for download. ​
962 962  )))
963 963  
964 964  (((
965 -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]]
807 +
966 966  )))
967 967  
968 968  (((
969 -(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
811 +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.
970 970  )))
971 971  
814 +(((
815 +
816 +)))
972 972  
818 +(((
819 +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.
820 +)))
973 973  
974 -= 6.  Trouble Shooting =
822 +(((
823 +
824 +)))
975 975  
826 +(((
827 +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.
828 +)))
976 976  
977 -== 6.1  ​Connection problem when uploading firmware ==
830 +[[image:image-20220606154726-3.png]]
978 978  
979 979  
833 +When you use the TTN network, the US915 frequency bands use are:
834 +
835 +* 903.9 - SF7BW125 to SF10BW125
836 +* 904.1 - SF7BW125 to SF10BW125
837 +* 904.3 - SF7BW125 to SF10BW125
838 +* 904.5 - SF7BW125 to SF10BW125
839 +* 904.7 - SF7BW125 to SF10BW125
840 +* 904.9 - SF7BW125 to SF10BW125
841 +* 905.1 - SF7BW125 to SF10BW125
842 +* 905.3 - SF7BW125 to SF10BW125
843 +* 904.6 - SF8BW500
844 +
980 980  (((
981 -**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]]
846 +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:
847 +
848 +* (% style="color:#037691" %)**AT+CHE=2**
849 +* (% style="color:#037691" %)**ATZ**
982 982  )))
983 983  
984 -(% class="wikigeneratedid" %)
985 985  (((
986 986  
854 +
855 +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.
987 987  )))
988 988  
858 +(((
859 +
860 +)))
989 989  
990 -== 6.2  AT Command input doesn't work ==
862 +(((
863 +The **AU915** band is similar. Below are the AU915 Uplink Channels.
864 +)))
991 991  
866 +[[image:image-20220606154825-4.png]]
992 992  
868 +
869 +== 4.2 ​Can I calibrate LSE01 to different soil types? ==
870 +
871 +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]].
872 +
873 +
874 += 5. Trouble Shooting =
875 +
876 +== 5.1 ​Why I can't join TTN in US915 / AU915 bands? ==
877 +
878 +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.
879 +
880 +
881 +== 5.2 AT Command input doesn't work ==
882 +
993 993  (((
994 994  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 +)))
995 995  
996 -
887 +
888 +== 5.3 Device rejoin in at the second uplink packet ==
889 +
890 +(% style="color:#4f81bd" %)**Issue describe as below:**
891 +
892 +[[image:1654500909990-784.png]]
893 +
894 +
895 +(% style="color:#4f81bd" %)**Cause for this issue:**
896 +
897 +(((
898 +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.
997 997  )))
998 998  
999 999  
1000 -= 7. ​ Order Info =
902 +(% style="color:#4f81bd" %)**Solution: **
1001 1001  
904 +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:
1002 1002  
1003 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
906 +[[image:1654500929571-736.png||height="458" width="832"]]
1004 1004  
1005 1005  
909 += 6. ​Order Info =
910 +
911 +
912 +Part Number**:** (% style="color:#4f81bd" %)**LSE01-XX-YY**
913 +
914 +
915 +(% style="color:#4f81bd" %)**XX**(%%)**:** The default frequency band
916 +
917 +* (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band
918 +* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
919 +* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
920 +* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
921 +* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
922 +* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
923 +* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
924 +* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
925 +
926 +(% style="color:#4f81bd" %)**YY**(%%)**: **Battery Option
927 +
928 +* (% style="color:red" %)**4**(%%): 4000mAh battery
929 +* (% style="color:red" %)**8**(%%): 8500mAh battery
930 +
1006 1006  (% class="wikigeneratedid" %)
1007 1007  (((
1008 1008  
1009 1009  )))
1010 1010  
1011 -= 8.  Packing Info =
936 += 7. Packing Info =
1012 1012  
1013 1013  (((
1014 1014  
1015 1015  
1016 1016  (% style="color:#037691" %)**Package Includes**:
942 +)))
1017 1017  
1018 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
1019 -* External antenna x 1
944 +* (((
945 +LSE01 LoRaWAN Soil Moisture & EC Sensor x 1
1020 1020  )))
1021 1021  
1022 1022  (((
1023 1023  
1024 1024  
1025 -
1026 1026  (% style="color:#037691" %)**Dimension and weight**:
952 +)))
1027 1027  
1028 -* Device Size: 13.0 x 5 x 4.5 cm
1029 -* Device Weight: 150g
1030 -* Package Size / pcs : 15 x 12x 5.5 cm
1031 -* Weight / pcs : 220g
954 +* (((
955 +Device Size: cm
1032 1032  )))
957 +* (((
958 +Device Weight: g
959 +)))
960 +* (((
961 +Package Size / pcs : cm
962 +)))
963 +* (((
964 +Weight / pcs : g
1033 1033  
1034 -(((
1035 1035  
1036 -
1037 -
1038 -
1039 1039  )))
1040 1040  
1041 -= 9.  Support =
969 += 8. Support =
1042 1042  
1043 -
1044 1044  * 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.
1045 1045  * 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]]
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-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