Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 108.13
edited by Xiaoling
on 2023/04/24 10:07
Change comment: There is no comment for this version
To version 57.4
edited by Xiaoling
on 2022/07/08 11:40
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,129 +81,107 @@
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
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 209  * Baud:  (% style="color:green" %)**9600**
... ... @@ -213,684 +213,1050 @@
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/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
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 -
247 -
248 -)))
249 -
250 -(((
251 251  For parameter description, please refer to AT command set
252 252  
253 -
254 -)))
204 +[[image:1657249793983-486.png]]
255 255  
256 -[[image:1657330452568-615.png]]
257 257  
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.
258 258  
209 +[[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]]
213 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
267 267  
215 +This feature is supported since firmware version v1.0.1
268 268  
269 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
270 270  
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
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
222 +[[image:1657249864775-321.png]]
275 275  
276 -[[image:1657330501006-241.png]]
277 277  
278 278  
279 -[[image:1657330533775-472.png]]
226 +[[image:1657249930215-289.png]]
280 280  
281 281  
229 +
282 282  === 2.2.6 Use MQTT protocol to uplink data ===
283 283  
232 +This feature is supported since firmware version v110
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
292 292  
235 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
236 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
237 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
238 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
239 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
240 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
241 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
242 +
293 293  [[image:1657249978444-674.png]]
294 294  
295 295  
296 -[[image:1657330723006-866.png]]
246 +[[image:1657249990869-686.png]]
297 297  
298 298  
249 +
299 299  (((
300 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 301  )))
302 302  
303 303  
255 +
304 304  === 2.2.7 Use TCP protocol to uplink data ===
305 305  
258 +This feature is supported since firmware version v110
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
309 309  
310 -[[image:image-20220709093918-1.png]]
261 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
262 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
311 311  
264 +[[image:1657250217799-140.png]]
312 312  
313 -[[image:image-20220709093918-2.png]]
314 314  
267 +[[image:1657250255956-604.png]]
315 315  
269 +
316 316  === 2.2.8 Change Update Interval ===
317 317  
318 -
319 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
274 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
322 322  
323 323  (((
324 -
325 -
326 -
327 327  (% style="color:red" %)**NOTE:**
278 +)))
328 328  
329 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
330 -
331 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
280 +(((
281 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
332 332  )))
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 337  == 2.3  Uplink Payload ==
338 338  
339 -=== 2.3.1  Before Firmware v1.3.2 ===
288 +In this mode, uplink payload includes in total 18 bytes
340 340  
290 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
291 +|=(% style="width: 50px;" %)(((
292 +**Size(bytes)**
293 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 40px;" %)**1**
294 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H"]]|(% style="width:41px" %)[[Ver>>||anchor="H"]]|(% style="width:46px" %)[[BAT>>||anchor="H"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H"]]|(% style="width:108px" %)[[Soil Moisture>>||anchor="H"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H"]]
341 341  
342 -In this mode, uplink payload includes in total 14 bytes
296 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
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"]]
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 -)))
299 +[[image:image-20220708111918-4.png]]
353 353  
354 354  
355 -[[image:1657331036973-987.png]]
302 +The payload is ASCII string, representative same HEX:
356 356  
304 +0x72403155615900640c7817075e0a8c02f900 where:
357 357  
358 -The payload is **ASCII** string, representative same HEX:
306 +* Device ID: 0x 724031556159 = 724031556159
307 +* Version: 0x0064=100=1.0.0
359 359  
360 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
309 +* BAT: 0x0c78 = 3192 mV = 3.192V
310 +* Singal: 0x17 = 23
311 +* Soil Moisture: 0x075e= 1886 = 18.86  %
312 +* Soil Temperature:0x0a8c =2700=27 °C
313 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
314 +* Interrupt: 0x00 = 0
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
318 +== 2.4  Payload Explanation and Sensor Interface ==
367 367  
368 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
320 +2.4.1  Device ID
369 369  
370 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
322 +By default, the Device ID equal to the last 6 bytes of IMEI.
371 371  
372 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
324 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
373 373  
374 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
326 +**Example:**
375 375  
376 -=== 2.3.2  Since firmware v1.3.2 ===
328 +AT+DEUI=A84041F15612
377 377  
330 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
378 378  
379 -In this mode, uplink payload includes 69 bytes in total by default.
380 380  
381 -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.
333 +2.4.2  Version Info
382 382  
383 -(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
384 -|=(% 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**
385 -|=(% 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.......
335 +Specify the software version: 0x64=100, means firmware version 1.00.
386 386  
387 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
337 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
388 388  
389 -[[image:image-20220908175246-1.png]]
390 390  
391 391  
392 -The payload is ASCII string, representative same HEX:
341 +=== 2.3.3 Battery Info ===
393 393  
394 -**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 (%%)**
343 +(((
344 +Check the battery voltage for LSE01.
345 +)))
395 395  
396 -**where:**
347 +(((
348 +Ex1: 0x0B45 = 2885mV
349 +)))
397 397  
398 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
351 +(((
352 +Ex2: 0x0B49 = 2889mV
353 +)))
399 399  
400 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
401 401  
402 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
403 403  
404 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
357 +=== 2.3.4 Soil Moisture ===
405 405  
406 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
359 +(((
360 +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.
361 +)))
407 407  
408 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
363 +(((
364 +For example, if the data you get from the register is __0x05 0xDC__, the moisture content in the soil is
365 +)))
409 409  
410 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
367 +(((
368 +
369 +)))
411 411  
412 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
371 +(((
372 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
373 +)))
413 413  
414 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
415 415  
416 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
417 417  
418 -== 2.4  Payload Explanation and Sensor Interface ==
377 +=== 2.3.5 Soil Temperature ===
419 419  
420 -=== 2.4.1  Device ID ===
379 +(((
380 + 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
381 +)))
421 421  
383 +(((
384 +**Example**:
385 +)))
422 422  
423 423  (((
424 -By default, the Device ID equal to the last 6 bytes of IMEI.
388 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
425 425  )))
426 426  
427 427  (((
428 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
392 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
393 +)))
429 429  
430 -
395 +
396 +
397 +=== 2.3.6 Soil Conductivity (EC) ===
398 +
399 +(((
400 +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).
431 431  )))
432 432  
433 433  (((
434 -(% style="color:blue" %)**Example :**
404 +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 -AT+DEUI=A84041F15612
408 +Generally, the EC value of irrigation water is less than 800uS / cm.
439 439  )))
440 440  
441 441  (((
442 -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.
412 +
443 443  )))
444 444  
415 +(((
416 +
417 +)))
445 445  
446 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
419 +=== 2.3.7 MOD ===
447 447  
448 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
421 +Firmware version at least v2.1 supports changing mode.
449 449  
450 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
423 +For example, bytes[10]=90
451 451  
425 +mod=(bytes[10]>>7)&0x01=1.
452 452  
453 -(% style="color:blue" %)**Example :**
454 454  
455 -AT+DEUI=868411056754138
428 +**Downlink Command:**
456 456  
430 +If payload = 0x0A00, workmode=0
457 457  
458 -=== 2.4.2  Version Info ===
432 +If** **payload =** **0x0A01, workmode=1
459 459  
460 460  
461 -(((
462 -Specify the software version: 0x64=100, means firmware version 1.00.
463 -)))
464 464  
465 -(((
466 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
467 -)))
436 +=== 2.3.8 ​Decode payload in The Things Network ===
468 468  
438 +While using TTN network, you can add the payload format to decode the payload.
469 469  
470 -=== 2.4.3  Battery Info ===
471 471  
441 +[[image:1654505570700-128.png]]
472 472  
473 473  (((
474 -Ex1: 0x0B45 = 2885mV
444 +The payload decoder function for TTN is here:
475 475  )))
476 476  
477 477  (((
478 -Ex2: 0x0B49 = 2889mV
448 +LSE01 TTN Payload Decoder: [[https:~~/~~/www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0>>https://www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0]]
479 479  )))
480 480  
481 481  
482 -=== 2.4.4  Signal Strength ===
452 +== 2.4 Uplink Interval ==
483 483  
454 +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"]]
484 484  
456 +
457 +
458 +== 2.5 Downlink Payload ==
459 +
460 +By default, LSE50 prints the downlink payload to console port.
461 +
462 +[[image:image-20220606165544-8.png]]
463 +
464 +
485 485  (((
486 -NB-IoT Network signal Strength.
466 +(% style="color:blue" %)**Examples:**
487 487  )))
488 488  
489 489  (((
490 -**Ex1: 0x1d = 29**
470 +
491 491  )))
492 492  
473 +* (((
474 +(% style="color:blue" %)**Set TDC**
475 +)))
476 +
493 493  (((
494 -(% style="color:blue" %)**0**(%%)  -113dBm or less
478 +If the payload=0100003C, it means set the END Node’s TDC to 0x00003C=60(S), while type code is 01.
495 495  )))
496 496  
497 497  (((
498 -(% style="color:blue" %)**1**(%%)  -111dBm
482 +Payload:    01 00 00 1E    TDC=30S
499 499  )))
500 500  
501 501  (((
502 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
486 +Payload:    01 00 00 3C    TDC=60S
503 503  )))
504 504  
505 505  (((
506 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
490 +
507 507  )))
508 508  
493 +* (((
494 +(% style="color:blue" %)**Reset**
495 +)))
496 +
509 509  (((
510 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
498 +If payload = 0x04FF, it will reset the LSE01
511 511  )))
512 512  
513 513  
514 -=== 2.4.5  Distance ===
502 +* (% style="color:blue" %)**CFM**
515 515  
504 +Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0
516 516  
517 -Get the distance. Flat object range 280mm - 7500mm.
518 518  
519 -(((
520 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
521 -)))
522 522  
508 +== 2.6 ​Show Data in DataCake IoT Server ==
509 +
523 523  (((
524 -(((
525 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
511 +[[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:
526 526  )))
527 -)))
528 528  
529 529  (((
530 530  
531 531  )))
532 532  
533 -=== 2.4.6  Digital Interrupt ===
534 -
535 -
536 536  (((
537 -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.
519 +(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the network at this time.
538 538  )))
539 539  
540 540  (((
541 -The command is:
523 +(% 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:
542 542  )))
543 543  
544 -(((
545 -(% 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]])**.**
546 -)))
547 547  
527 +[[image:1654505857935-743.png]]
548 548  
549 -(((
550 -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.
551 -)))
552 552  
530 +[[image:1654505874829-548.png]]
553 553  
554 -(((
555 -Example:
556 -)))
557 557  
558 -(((
559 -0x(00): Normal uplink packet.
560 -)))
533 +(% style="color:blue" %)**Step 3**(%%)**:**  Create an account or log in Datacake.
561 561  
562 -(((
563 -0x(01): Interrupt Uplink Packet.
564 -)))
535 +(% style="color:blue" %)**Step 4**(%%)**:**  Search the LSE01 and add DevEUI.
565 565  
566 566  
567 -=== 2.4.7  ​+5V Output ===
538 +[[image:1654505905236-553.png]]
568 568  
569 569  
570 -(((
571 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
572 -)))
541 +After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
573 573  
543 +[[image:1654505925508-181.png]]
574 574  
575 -(((
576 -The 5V output time can be controlled by AT Command.
577 577  
578 -
579 -)))
580 580  
581 -(((
582 -(% style="color:blue" %)**AT+5VT=1000**
547 +== 2.7 Frequency Plans ==
583 583  
584 -
585 -)))
549 +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.
586 586  
587 -(((
588 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
589 -)))
590 590  
552 +=== 2.7.1 EU863-870 (EU868) ===
591 591  
592 -== 2.5  Downlink Payload ==
554 +(% style="color:#037691" %)** Uplink:**
593 593  
556 +868.1 - SF7BW125 to SF12BW125
594 594  
595 -By default, NDDS75 prints the downlink payload to console port.
558 +868.3 - SF7BW125 to SF12BW125 and SF7BW250
596 596  
597 -[[image:image-20220709100028-1.png]]
560 +868.5 - SF7BW125 to SF12BW125
598 598  
562 +867.1 - SF7BW125 to SF12BW125
599 599  
564 +867.3 - SF7BW125 to SF12BW125
565 +
566 +867.5 - SF7BW125 to SF12BW125
567 +
568 +867.7 - SF7BW125 to SF12BW125
569 +
570 +867.9 - SF7BW125 to SF12BW125
571 +
572 +868.8 - FSK
573 +
574 +
575 +(% style="color:#037691" %)** Downlink:**
576 +
577 +Uplink channels 1-9 (RX1)
578 +
579 +869.525 - SF9BW125 (RX2 downlink only)
580 +
581 +
582 +
583 +=== 2.7.2 US902-928(US915) ===
584 +
585 +Used in USA, Canada and South America. Default use CHE=2
586 +
587 +(% style="color:#037691" %)**Uplink:**
588 +
589 +903.9 - SF7BW125 to SF10BW125
590 +
591 +904.1 - SF7BW125 to SF10BW125
592 +
593 +904.3 - SF7BW125 to SF10BW125
594 +
595 +904.5 - SF7BW125 to SF10BW125
596 +
597 +904.7 - SF7BW125 to SF10BW125
598 +
599 +904.9 - SF7BW125 to SF10BW125
600 +
601 +905.1 - SF7BW125 to SF10BW125
602 +
603 +905.3 - SF7BW125 to SF10BW125
604 +
605 +
606 +(% style="color:#037691" %)**Downlink:**
607 +
608 +923.3 - SF7BW500 to SF12BW500
609 +
610 +923.9 - SF7BW500 to SF12BW500
611 +
612 +924.5 - SF7BW500 to SF12BW500
613 +
614 +925.1 - SF7BW500 to SF12BW500
615 +
616 +925.7 - SF7BW500 to SF12BW500
617 +
618 +926.3 - SF7BW500 to SF12BW500
619 +
620 +926.9 - SF7BW500 to SF12BW500
621 +
622 +927.5 - SF7BW500 to SF12BW500
623 +
624 +923.3 - SF12BW500(RX2 downlink only)
625 +
626 +
627 +
628 +=== 2.7.3 CN470-510 (CN470) ===
629 +
630 +Used in China, Default use CHE=1
631 +
632 +(% style="color:#037691" %)**Uplink:**
633 +
634 +486.3 - SF7BW125 to SF12BW125
635 +
636 +486.5 - SF7BW125 to SF12BW125
637 +
638 +486.7 - SF7BW125 to SF12BW125
639 +
640 +486.9 - SF7BW125 to SF12BW125
641 +
642 +487.1 - SF7BW125 to SF12BW125
643 +
644 +487.3 - SF7BW125 to SF12BW125
645 +
646 +487.5 - SF7BW125 to SF12BW125
647 +
648 +487.7 - SF7BW125 to SF12BW125
649 +
650 +
651 +(% style="color:#037691" %)**Downlink:**
652 +
653 +506.7 - SF7BW125 to SF12BW125
654 +
655 +506.9 - SF7BW125 to SF12BW125
656 +
657 +507.1 - SF7BW125 to SF12BW125
658 +
659 +507.3 - SF7BW125 to SF12BW125
660 +
661 +507.5 - SF7BW125 to SF12BW125
662 +
663 +507.7 - SF7BW125 to SF12BW125
664 +
665 +507.9 - SF7BW125 to SF12BW125
666 +
667 +508.1 - SF7BW125 to SF12BW125
668 +
669 +505.3 - SF12BW125 (RX2 downlink only)
670 +
671 +
672 +
673 +=== 2.7.4 AU915-928(AU915) ===
674 +
675 +Default use CHE=2
676 +
677 +(% style="color:#037691" %)**Uplink:**
678 +
679 +916.8 - SF7BW125 to SF12BW125
680 +
681 +917.0 - SF7BW125 to SF12BW125
682 +
683 +917.2 - SF7BW125 to SF12BW125
684 +
685 +917.4 - SF7BW125 to SF12BW125
686 +
687 +917.6 - SF7BW125 to SF12BW125
688 +
689 +917.8 - SF7BW125 to SF12BW125
690 +
691 +918.0 - SF7BW125 to SF12BW125
692 +
693 +918.2 - SF7BW125 to SF12BW125
694 +
695 +
696 +(% style="color:#037691" %)**Downlink:**
697 +
698 +923.3 - SF7BW500 to SF12BW500
699 +
700 +923.9 - SF7BW500 to SF12BW500
701 +
702 +924.5 - SF7BW500 to SF12BW500
703 +
704 +925.1 - SF7BW500 to SF12BW500
705 +
706 +925.7 - SF7BW500 to SF12BW500
707 +
708 +926.3 - SF7BW500 to SF12BW500
709 +
710 +926.9 - SF7BW500 to SF12BW500
711 +
712 +927.5 - SF7BW500 to SF12BW500
713 +
714 +923.3 - SF12BW500(RX2 downlink only)
715 +
716 +
717 +
718 +=== 2.7.5 AS920-923 & AS923-925 (AS923) ===
719 +
720 +(% style="color:#037691" %)**Default Uplink channel:**
721 +
722 +923.2 - SF7BW125 to SF10BW125
723 +
724 +923.4 - SF7BW125 to SF10BW125
725 +
726 +
727 +(% style="color:#037691" %)**Additional Uplink Channel**:
728 +
729 +(OTAA mode, channel added by JoinAccept message)
730 +
731 +(% style="color:#037691" %)**AS920~~AS923 for Japan, Malaysia, Singapore**:
732 +
733 +922.2 - SF7BW125 to SF10BW125
734 +
735 +922.4 - SF7BW125 to SF10BW125
736 +
737 +922.6 - SF7BW125 to SF10BW125
738 +
739 +922.8 - SF7BW125 to SF10BW125
740 +
741 +923.0 - SF7BW125 to SF10BW125
742 +
743 +922.0 - SF7BW125 to SF10BW125
744 +
745 +
746 +(% style="color:#037691" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**:
747 +
748 +923.6 - SF7BW125 to SF10BW125
749 +
750 +923.8 - SF7BW125 to SF10BW125
751 +
752 +924.0 - SF7BW125 to SF10BW125
753 +
754 +924.2 - SF7BW125 to SF10BW125
755 +
756 +924.4 - SF7BW125 to SF10BW125
757 +
758 +924.6 - SF7BW125 to SF10BW125
759 +
760 +
761 +(% style="color:#037691" %)** Downlink:**
762 +
763 +Uplink channels 1-8 (RX1)
764 +
765 +923.2 - SF10BW125 (RX2)
766 +
767 +
768 +
769 +=== 2.7.6 KR920-923 (KR920) ===
770 +
771 +Default channel:
772 +
773 +922.1 - SF7BW125 to SF12BW125
774 +
775 +922.3 - SF7BW125 to SF12BW125
776 +
777 +922.5 - SF7BW125 to SF12BW125
778 +
779 +
780 +(% style="color:#037691" %)**Uplink: (OTAA mode, channel added by JoinAccept message)**
781 +
782 +922.1 - SF7BW125 to SF12BW125
783 +
784 +922.3 - SF7BW125 to SF12BW125
785 +
786 +922.5 - SF7BW125 to SF12BW125
787 +
788 +922.7 - SF7BW125 to SF12BW125
789 +
790 +922.9 - SF7BW125 to SF12BW125
791 +
792 +923.1 - SF7BW125 to SF12BW125
793 +
794 +923.3 - SF7BW125 to SF12BW125
795 +
796 +
797 +(% style="color:#037691" %)**Downlink:**
798 +
799 +Uplink channels 1-7(RX1)
800 +
801 +921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
802 +
803 +
804 +
805 +=== 2.7.7 IN865-867 (IN865) ===
806 +
807 +(% style="color:#037691" %)** Uplink:**
808 +
809 +865.0625 - SF7BW125 to SF12BW125
810 +
811 +865.4025 - SF7BW125 to SF12BW125
812 +
813 +865.9850 - SF7BW125 to SF12BW125
814 +
815 +
816 +(% style="color:#037691" %) **Downlink:**
817 +
818 +Uplink channels 1-3 (RX1)
819 +
820 +866.550 - SF10BW125 (RX2)
821 +
822 +
823 +
824 +
825 +== 2.8 LED Indicator ==
826 +
827 +The LSE01 has an internal LED which is to show the status of different state.
828 +
829 +* Blink once when device power on.
830 +* Solid ON for 5 seconds once device successful Join the network.
831 +* Blink once when device transmit a packet.
832 +
833 +== 2.9 Installation in Soil ==
834 +
835 +**Measurement the soil surface**
836 +
837 +
838 +[[image:1654506634463-199.png]] ​
839 +
600 600  (((
601 -(% style="color:blue" %)**Examples:**
841 +(((
842 +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.
602 602  )))
844 +)))
603 603  
846 +
847 +
848 +[[image:1654506665940-119.png]]
849 +
604 604  (((
605 -
851 +Dig a hole with diameter > 20CM.
606 606  )))
607 607  
608 -* (((
609 -(% style="color:blue" %)**Set TDC**
854 +(((
855 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
610 610  )))
611 611  
858 +
859 +== 2.10 ​Firmware Change Log ==
860 +
612 612  (((
613 -If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
862 +**Firmware download link:**
614 614  )))
615 615  
616 616  (((
617 -Payload:    01 00 00 1E    TDC=30S
866 +[[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/]]
618 618  )))
619 619  
620 620  (((
621 -Payload:    01 00 00 3C    TDC=60S
870 +
622 622  )))
623 623  
624 624  (((
874 +**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
875 +)))
876 +
877 +(((
625 625  
626 626  )))
627 627  
628 -* (((
629 -(% style="color:blue" %)**Reset**
881 +(((
882 +**V1.0.**
630 630  )))
631 631  
632 632  (((
633 -If payload = 0x04FF, it will reset the NDDS75
886 +Release
634 634  )))
635 635  
636 636  
637 -* (% style="color:blue" %)**INTMOD**
890 +== 2.11 ​Battery Analysis ==
638 638  
892 +=== 2.11.1 ​Battery Type ===
893 +
639 639  (((
640 -Downlink Payload: 06000003, Set AT+INTMOD=3
895 +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.
641 641  )))
642 642  
898 +(((
899 +The battery is designed to last for more than 5 years for the LSN50.
900 +)))
643 643  
644 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
902 +(((
903 +(((
904 +The battery-related documents are as below:
905 +)))
906 +)))
645 645  
908 +* (((
909 +[[Battery Dimension>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
910 +)))
911 +* (((
912 +[[Lithium-Thionyl Chloride Battery  datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
913 +)))
914 +* (((
915 +[[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/]]
916 +)))
646 646  
647 -(% style="color:blue" %)** ➢ AT Command:**
918 + [[image:image-20220610172436-1.png]]
648 648  
649 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
650 650  
651 -² When min=0, and max≠0, Alarm higher than max
652 652  
653 -² When min≠0, and max=0, Alarm lower than min
922 +=== 2.11.2 ​Battery Note ===
654 654  
655 -² When min≠0 and max≠0, Alarm higher than max or lower than min
924 +(((
925 +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.
926 +)))
656 656  
657 657  
658 -(% style="color:blue" %)** Example:**
659 659  
660 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
930 +=== 2.11.3 Replace the battery ===
661 661  
932 +(((
933 +If Battery is lower than 2.7v, user should replace the battery of LSE01.
934 +)))
662 662  
663 -== 2.7  Set the number of data to be uploaded and the recording time ==
936 +(((
937 +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.
938 +)))
664 664  
940 +(((
941 +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)
942 +)))
665 665  
666 -(% style="color:blue" %)** ➢ AT Command:**
667 667  
668 -* (% 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)
669 -* (% 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.
670 670  
671 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
946 += 3. ​Using the AT Commands =
672 672  
673 -[[image:image-20221009001114-1.png||height="687" width="955"]]
948 +== 3.1 Access AT Commands ==
674 674  
675 675  
676 -== 2.8  Read or Clear cached data ==
951 +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.
677 677  
953 +[[image:1654501986557-872.png||height="391" width="800"]]
678 678  
679 -(% style="color:blue" %)** ➢ AT Command:**
680 680  
681 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
682 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
956 +Or if you have below board, use below connection:
683 683  
684 -[[image:image-20220908175333-2.png]]
685 685  
959 +[[image:1654502005655-729.png||height="503" width="801"]]
686 686  
687 -== 2.9  ​LED Indicator ==
688 688  
689 689  
690 -The NDDS75 has an internal LED which is to show the status of different state.
963 +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:
691 691  
692 692  
693 -* 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)
694 -* Then the LED will be on for 1 second means device is boot normally.
695 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
696 -* For each uplink probe, LED will be on for 500ms.
966 + [[image:1654502050864-459.png||height="564" width="806"]]
697 697  
698 -(((
699 -
700 -)))
701 701  
969 +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]]
702 702  
703 -== 2.10  ​Firmware Change Log ==
704 704  
972 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%) : Help on <CMD>
705 705  
706 -(((
707 -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]]
708 -)))
974 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD> **(%%) : Run <CMD>
709 709  
710 -(((
711 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
712 -)))
976 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=<value>**(%%) : Set the value
713 713  
978 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=?**(%%)  : Get the value
714 714  
715 -== 2.11 Battery & Power Consumption ==
716 716  
981 +(% style="color:#037691" %)**General Commands**(%%)      
717 717  
718 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
983 +(% style="background-color:#dcdcdc" %)**AT**(%%)  : Attention       
719 719  
720 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
985 +(% style="background-color:#dcdcdc" %)**AT?**(%%)  : Short Help     
721 721  
987 +(% style="background-color:#dcdcdc" %)**ATZ**(%%)  : MCU Reset    
722 722  
723 -= 3. ​ Access NB-IoT Module =
989 +(% style="background-color:#dcdcdc" %)**AT+TDC**(%%)  : Application Data Transmission Interval 
724 724  
725 725  
726 -(((
727 -Users can directly access the AT command set of the NB-IoT module.
728 -)))
992 +(% style="color:#037691" %)**Keys, IDs and EUIs management**
729 729  
730 -(((
731 -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/]] 
994 +(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%)              : Application EUI      
732 732  
733 -
734 -)))
996 +(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%)              : Application Key     
735 735  
736 -[[image:1657333200519-600.png]]
998 +(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%)            : Application Session Key
737 737  
1000 +(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%)              : Device Address     
738 738  
739 -= 4.  Using the AT Commands =
1002 +(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%)                   : Device EUI     
740 740  
741 -== 4.1  Access AT Commands ==
1004 +(% style="background-color:#dcdcdc" %)**AT+NWKID**(%%)               : Network ID (You can enter this command change only after successful network connection) 
742 742  
1006 +(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%)          : Network Session Key Joining and sending date on LoRa network  
743 743  
744 -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]]
1008 +(% style="background-color:#dcdcdc" %)**AT+CFM**(%%)  : Confirm Mode       
745 745  
1010 +(% style="background-color:#dcdcdc" %)**AT+CFS**(%%)                     : Confirm Status       
746 746  
747 -AT+<CMD>?  :  Help on <CMD>
1012 +(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%)  : Join LoRa? Network       
748 748  
749 -AT+<CMD>         :  Run <CMD>
1014 +(% style="background-color:#dcdcdc" %)**AT+NJM**(%%)  : LoRa? Network Join Mode    
750 750  
751 -AT+<CMD>=<value> :  Set the value
1016 +(% style="background-color:#dcdcdc" %)**AT+NJS**(%%)                     : LoRa? Network Join Status    
752 752  
753 -AT+<CMD>=?  :  Get the value
1018 +(% style="background-color:#dcdcdc" %)**AT+RECV**(%%)                  : Print Last Received Data in Raw Format
754 754  
1020 +(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%)                : Print Last Received Data in Binary Format      
755 755  
756 -(% style="color:#037691" %)**General Commands**(%%)      
1022 +(% style="background-color:#dcdcdc" %)**AT+SEND**(%%)                  : Send Text Data      
757 757  
758 -AT  :  Attention       
1024 +(% style="background-color:#dcdcdc" %)**AT+SENB**(%%)                  : Send Hexadecimal Data
759 759  
760 -AT?  :  Short Help     
761 761  
762 -ATZ  :  MCU Reset    
1027 +(% style="color:#037691" %)**LoRa Network Management**
763 763  
764 -AT+TDC  :  Application Data Transmission Interval
1029 +(% style="background-color:#dcdcdc" %)**AT+ADR**(%%)          : Adaptive Rate
765 765  
766 -AT+CFG  :  Print all configurations
1031 +(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%)  : LoRa Class(Currently only support class A
767 767  
768 -AT+CFGMOD           :  Working mode selection
1033 +(% style="background-color:#dcdcdc" %)**AT+DCS**(%%)  : Duty Cycle Setting 
769 769  
770 -AT+INTMOD            :  Set the trigger interrupt mode
1035 +(% style="background-color:#dcdcdc" %)**AT+DR**(%%)  : Data Rate (Can Only be Modified after ADR=0)     
771 771  
772 -AT+5VT  :  Set extend the time of 5V power  
1037 +(% style="background-color:#dcdcdc" %)**AT+FCD**(%%)  : Frame Counter Downlink       
773 773  
774 -AT+PRO  :  Choose agreement
1039 +(% style="background-color:#dcdcdc" %)**AT+FCU**(%%)  : Frame Counter Uplink   
775 775  
776 -AT+WEIGRE  :  Get weight or set weight to 0
1041 +(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%)  : Join Accept Delay1
777 777  
778 -AT+WEIGAP  :  Get or Set the GapValue of weight
1043 +(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%)  : Join Accept Delay2
779 779  
780 -AT+RXDL  :  Extend the sending and receiving time
1045 +(% style="background-color:#dcdcdc" %)**AT+PNM**(%%)  : Public Network Mode   
781 781  
782 -AT+CNTFAC  :  Get or set counting parameters
1047 +(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%)  : Receive Delay1      
783 783  
784 -AT+SERVADDR  :  Server Address
1049 +(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%)  : Receive Delay2      
785 785  
786 -AT+TR  :  Get or Set record time"
1051 +(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%)  : Rx2 Window Data Rate 
787 787  
788 -AT+APN     :  Get or set the APN
1053 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%)  : Rx2 Window Frequency
789 789  
790 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
1055 +(% style="background-color:#dcdcdc" %)**AT+TXP**(%%)  : Transmit Power
791 791  
792 -AT+DNSCFG  : Get or Set DNS Server
1057 +(% style="background-color:#dcdcdc" %)**AT+ MOD**(%%)  : Set work mode
793 793  
794 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
795 795  
796 -AT+NOUD  :  Get or Set the number of data to be uploaded
1060 +(% style="color:#037691" %)**Information** 
797 797  
798 -AT+CDP     :  Read or Clear cached data
1062 +(% style="background-color:#dcdcdc" %)**AT+RSSI**(%%)           : RSSI of the Last Received Packet   
799 799  
800 -AT+LDDSALARM :  Get or Set alarm of distance
1064 +(% style="background-color:#dcdcdc" %)**AT+SNR**(%%)           : SNR of the Last Received Packet   
801 801  
1066 +(% style="background-color:#dcdcdc" %)**AT+VER**(%%)           : Image Version and Frequency Band       
802 802  
803 -(% style="color:#037691" %)**COAP Management**      
1068 +(% style="background-color:#dcdcdc" %)**AT+FDR**(%%)           : Factory Data Reset
804 804  
805 -AT+URI            :  Resource parameters
1070 +(% style="background-color:#dcdcdc" %)**AT+PORT**(%%)  : Application Port    
806 806  
1072 +(% style="background-color:#dcdcdc" %)**AT+CHS**(%%)  : Get or Set Frequency (Unit: Hz) for Single Channel Mode
807 807  
808 -(% style="color:#037691" %)**UDP Management**
1074 + (% style="background-color:#dcdcdc" %)**AT+CHE**(%%)  : Get or Set eight channels mode, Only for US915, AU915, CN470
809 809  
810 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
811 811  
1077 += ​4. FAQ =
812 812  
813 -(% style="color:#037691" %)**MQTT Management**
1079 +== 4.1 ​How to change the LoRa Frequency Bands/Region? ==
814 814  
815 -AT+CLIENT  :  Get or Set MQTT client
1081 +(((
1082 +You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]].
1083 +When downloading the images, choose the required image file for download. ​
1084 +)))
816 816  
817 -AT+UNAME  :  Get or Set MQTT Username
1086 +(((
1087 +
1088 +)))
818 818  
819 -AT+PWD  :  Get or Set MQTT password
1090 +(((
1091 +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.
1092 +)))
820 820  
821 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
1094 +(((
1095 +
1096 +)))
822 822  
823 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
1098 +(((
1099 +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.
1100 +)))
824 824  
1102 +(((
1103 +
1104 +)))
825 825  
826 -(% style="color:#037691" %)**Information**          
1106 +(((
1107 +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.
1108 +)))
827 827  
828 -AT+FDR  :  Factory Data Reset
1110 +[[image:image-20220606154726-3.png]]
829 829  
830 -AT+PWORD  :  Serial Access Password
831 831  
1113 +When you use the TTN network, the US915 frequency bands use are:
832 832  
833 -= ​5.  FAQ =
1115 +* 903.9 - SF7BW125 to SF10BW125
1116 +* 904.1 - SF7BW125 to SF10BW125
1117 +* 904.3 - SF7BW125 to SF10BW125
1118 +* 904.5 - SF7BW125 to SF10BW125
1119 +* 904.7 - SF7BW125 to SF10BW125
1120 +* 904.9 - SF7BW125 to SF10BW125
1121 +* 905.1 - SF7BW125 to SF10BW125
1122 +* 905.3 - SF7BW125 to SF10BW125
1123 +* 904.6 - SF8BW500
834 834  
835 -== 5.1 ​ How to Upgrade Firmware ==
1125 +(((
1126 +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:
836 836  
1128 +* (% style="color:#037691" %)**AT+CHE=2**
1129 +* (% style="color:#037691" %)**ATZ**
1130 +)))
837 837  
838 838  (((
839 -User can upgrade the firmware for 1) bug fix, 2) new feature release.
1133 +
1134 +
1135 +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.
840 840  )))
841 841  
842 842  (((
843 -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]]
1139 +
844 844  )))
845 845  
846 846  (((
847 -(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
1143 +The **AU915** band is similar. Below are the AU915 Uplink Channels.
848 848  )))
849 849  
1146 +[[image:image-20220606154825-4.png]]
850 850  
851 -= 6.  Trouble Shooting =
852 852  
853 -== 6.1  ​Connection problem when uploading firmware ==
1149 +== 4.2 ​Can I calibrate LSE01 to different soil types? ==
854 854  
1151 +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]].
855 855  
856 -(((
857 -**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]]
858 -)))
859 859  
860 -(% class="wikigeneratedid" %)
1154 += 5. Trouble Shooting =
1155 +
1156 +== 5.1 ​Why I can't join TTN in US915 / AU915 bands? ==
1157 +
1158 +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.
1159 +
1160 +
1161 +== 5.2 AT Command input doesn't work ==
1162 +
861 861  (((
862 -
1164 +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.
863 863  )))
864 864  
865 -== 6.2  AT Command input doesn't work ==
866 866  
1168 +== 5.3 Device rejoin in at the second uplink packet ==
867 867  
1170 +(% style="color:#4f81bd" %)**Issue describe as below:**
1171 +
1172 +[[image:1654500909990-784.png]]
1173 +
1174 +
1175 +(% style="color:#4f81bd" %)**Cause for this issue:**
1176 +
868 868  (((
869 -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.
1178 +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.
870 870  )))
871 871  
872 872  
873 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
1182 +(% style="color:#4f81bd" %)**Solution: **
874 874  
1184 +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:
875 875  
876 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
1186 +[[image:1654500929571-736.png||height="458" width="832"]]
877 877  
878 878  
879 -= 7. ​ Order Info =
1189 += 6. ​Order Info =
880 880  
881 881  
882 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1192 +Part Number**:** (% style="color:#4f81bd" %)**LSE01-XX-YY**
883 883  
884 884  
885 -= 8.  Packing Info =
1195 +(% style="color:#4f81bd" %)**XX**(%%)**:** The default frequency band
886 886  
1197 +* (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band
1198 +* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
1199 +* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
1200 +* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
1201 +* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
1202 +* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
1203 +* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1204 +* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1205 +
1206 +(% style="color:#4f81bd" %)**YY**(%%)**: **Battery Option
1207 +
1208 +* (% style="color:red" %)**4**(%%): 4000mAh battery
1209 +* (% style="color:red" %)**8**(%%): 8500mAh battery
1210 +
1211 +(% class="wikigeneratedid" %)
887 887  (((
888 888  
1214 +)))
889 889  
1216 += 7. Packing Info =
1217 +
1218 +(((
1219 +
1220 +
890 890  (% style="color:#037691" %)**Package Includes**:
1222 +)))
891 891  
892 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
893 -* External antenna x 1
1224 +* (((
1225 +LSE01 LoRaWAN Soil Moisture & EC Sensor x 1
894 894  )))
895 895  
896 896  (((
... ... @@ -897,22 +897,24 @@
897 897  
898 898  
899 899  (% style="color:#037691" %)**Dimension and weight**:
1232 +)))
900 900  
901 -* Device Size: 13.0 x 5 x 4.5 cm
902 -* Device Weight: 150g
903 -* Package Size / pcs : 15 x 12x 5.5 cm
904 -* Weight / pcs : 220g
1234 +* (((
1235 +Device Size: cm
905 905  )))
1237 +* (((
1238 +Device Weight: g
1239 +)))
1240 +* (((
1241 +Package Size / pcs : cm
1242 +)))
1243 +* (((
1244 +Weight / pcs : g
906 906  
907 -(((
908 908  
909 -
910 -
911 911  )))
912 912  
913 -= 9.  Support =
1249 += 8. Support =
914 914  
915 -
916 916  * 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.
917 -
918 918  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
1657259653666-883.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -344.4 KB
Content
1657260785982-288.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.2 KB
Content
1657261119050-993.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
1657261278785-153.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
1657271519014-786.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -71.5 KB
Content
1657327959271-447.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.3 KB
Content
1657328609906-564.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -492.6 KB
Content
1657328659945-416.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
1657328756309-230.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.5 KB
Content
1657328884227-504.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -483.6 KB
Content
1657329814315-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -85.3 KB
Content
1657330452568-615.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -71.3 KB
Content
1657330472797-498.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -68.9 KB
Content
1657330501006-241.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -119.2 KB
Content
1657330533775-472.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -74.9 KB
Content
1657330723006-866.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -74.1 KB
Content
1657331036973-987.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -83.8 KB
Content
1657332990863-496.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.2 KB
Content
1657333200519-600.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
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