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