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.8
edited by Xiaoling
on 2022/07/08 11:55
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,87 +213,70 @@
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  
225 +[[image:1657249930215-289.png]]
278 278  
279 -[[image:1657330533775-472.png]]
280 280  
281 281  
282 282  === 2.2.6 Use MQTT protocol to uplink data ===
283 283  
231 +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  
234 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
235 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
236 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
237 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
238 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
239 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
240 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
241 +
293 293  [[image:1657249978444-674.png]]
294 294  
295 295  
296 -[[image:1657330723006-866.png]]
245 +[[image:1657249990869-686.png]]
297 297  
298 298  
299 299  (((
... ... @@ -301,302 +301,238 @@
301 301  )))
302 302  
303 303  
253 +
304 304  === 2.2.7 Use TCP protocol to uplink data ===
305 305  
256 +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]]
259 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
260 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
311 311  
262 +[[image:1657250217799-140.png]]
312 312  
313 -[[image:image-20220709093918-2.png]]
314 314  
265 +[[image:1657250255956-604.png]]
315 315  
316 -=== 2.2.8 Change Update Interval ===
317 317  
318 318  
269 +=== 2.2.8 Change Update Interval ===
270 +
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
273 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
322 322  
323 323  (((
324 -
325 -
326 -
327 327  (% style="color:red" %)**NOTE:**
277 +)))
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:**
279 +(((
280 +(% 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 ===
287 +In this mode, uplink payload includes in total 18 bytes
340 340  
341 -
342 -In this mode, uplink payload includes in total 14 bytes
343 -
344 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
345 -|=(% style="width: 60px;" %)(((
289 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
290 +|=(% style="width: 50px;" %)(((
346 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"]]
292 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 40px;" %)**1**
293 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H"]]|(% style="width:41px" %)[[Ver>>||anchor="H"]]|(% style="width:46px" %)[[BAT>>||anchor="H"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H"]]|(% style="width:108px" %)[[Soil Moisture>>||anchor="H"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H"]]
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 -)))
295 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
353 353  
354 354  
355 -[[image:1657331036973-987.png]]
298 +[[image:image-20220708111918-4.png]]
356 356  
357 357  
358 -The payload is **ASCII** string, representative same HEX:
301 +The payload is ASCII string, representative same HEX:
359 359  
360 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
303 +0x72403155615900640c7817075e0a8c02f900 where:
361 361  
362 -**where :**
305 +* Device ID: 0x 724031556159 = 724031556159
306 +* Version: 0x0064=100=1.0.0
363 363  
364 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
308 +* BAT: 0x0c78 = 3192 mV = 3.192V
309 +* Singal: 0x17 = 23
310 +* Soil Moisture: 0x075e= 1886 = 18.86  %
311 +* Soil Temperature:0x0a8c =2700=27 °C
312 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
313 +* Interrupt: 0x00 = 0
365 365  
366 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
367 367  
368 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
316 +== 2.4  Payload Explanation and Sensor Interface ==
369 369  
370 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
371 371  
372 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
319 +=== 2.4.1  Device ID ===
373 373  
374 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
321 +By default, the Device ID equal to the last 6 bytes of IMEI.
375 375  
376 -=== 2.3.2  Since firmware v1.3.2 ===
323 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
377 377  
325 +**Example:**
378 378  
379 -In this mode, uplink payload includes 69 bytes in total by default.
327 +AT+DEUI=A84041F15612
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.
329 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
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.......
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.
388 388  
389 -[[image:image-20220908175246-1.png]]
333 +=== 2.4.2  Version Info ===
390 390  
335 +Specify the software version: 0x64=100, means firmware version 1.00.
391 391  
392 -The payload is ASCII string, representative same HEX:
337 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
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 (%%)**
395 395  
396 -**where:**
397 397  
398 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
341 +=== 2.4.3  Battery Info ===
399 399  
400 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
401 -
402 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
403 -
404 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
405 -
406 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
407 -
408 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
409 -
410 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
411 -
412 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
413 -
414 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
415 -
416 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
417 -
418 -== 2.4  Payload Explanation and Sensor Interface ==
419 -
420 -=== 2.4.1  Device ID ===
421 -
422 -
423 423  (((
424 -By default, the Device ID equal to the last 6 bytes of IMEI.
344 +Check the battery voltage for LSE01.
425 425  )))
426 426  
427 427  (((
428 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
429 -
430 -
348 +Ex1: 0x0B45 = 2885mV
431 431  )))
432 432  
433 433  (((
434 -(% style="color:blue" %)**Example :**
352 +Ex2: 0x0B49 = 2889mV
435 435  )))
436 436  
437 -(((
438 -AT+DEUI=A84041F15612
439 -)))
440 440  
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.
443 -)))
444 444  
357 +=== 2.4.4  Signal Strength ===
445 445  
446 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
359 +NB-IoT Network signal Strength.
447 447  
448 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
361 +**Ex1: 0x1d = 29**
449 449  
450 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
363 +(% style="color:blue" %)**0**(%%)  -113dBm or less
451 451  
365 +(% style="color:blue" %)**1**(%%)  -111dBm
452 452  
453 -(% style="color:blue" %)**Example :**
367 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
454 454  
455 -AT+DEUI=868411056754138
369 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
456 456  
371 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
457 457  
458 -=== 2.4.2  Version Info ===
459 459  
460 460  
375 +=== 2.4.5  Soil Moisture ===
376 +
461 461  (((
462 -Specify the software version: 0x64=100, means firmware version 1.00.
378 +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.
463 463  )))
464 464  
465 465  (((
466 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
382 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
467 467  )))
468 468  
469 -
470 -=== 2.4.3  Battery Info ===
471 -
472 -
473 473  (((
474 -Ex1: 0x0B45 = 2885mV
386 +
475 475  )))
476 476  
477 477  (((
478 -Ex2: 0x0B49 = 2889mV
390 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
479 479  )))
480 480  
481 481  
482 -=== 2.4.4  Signal Strength ===
483 483  
395 +=== 2.4.6  Soil Temperature ===
484 484  
485 485  (((
486 -NB-IoT Network signal Strength.
398 + 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
487 487  )))
488 488  
489 489  (((
490 -**Ex1: 0x1d = 29**
402 +**Example**:
491 491  )))
492 492  
493 493  (((
494 -(% style="color:blue" %)**0**(%%)  -113dBm or less
406 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
495 495  )))
496 496  
497 497  (((
498 -(% style="color:blue" %)**1**(%%)  -111dBm
410 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
499 499  )))
500 500  
501 -(((
502 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
503 -)))
504 504  
414 +
415 +=== 2.4.7  Soil Conductivity (EC) ===
416 +
505 505  (((
506 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
418 +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).
507 507  )))
508 508  
509 509  (((
510 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
422 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
511 511  )))
512 512  
513 -
514 -=== 2.4.5  Distance ===
515 -
516 -
517 -Get the distance. Flat object range 280mm - 7500mm.
518 -
519 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
426 +Generally, the EC value of irrigation water is less than 800uS / cm.
521 521  )))
522 522  
523 523  (((
524 -(((
525 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
430 +
526 526  )))
527 -)))
528 528  
529 529  (((
530 530  
531 531  )))
532 532  
533 -=== 2.4.6  Digital Interrupt ===
437 +=== 2.4.8  Digital Interrupt ===
534 534  
439 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server.
535 535  
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.
538 -)))
539 -
540 -(((
541 541  The command is:
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 -)))
443 +(% 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]])**.**
547 547  
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 -)))
446 +The lower four bits of this data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H"]] for the hardware and software set up.
552 552  
553 553  
554 -(((
555 555  Example:
556 -)))
557 557  
558 -(((
559 559  0x(00): Normal uplink packet.
560 -)))
561 561  
562 -(((
563 563  0x(01): Interrupt Uplink Packet.
564 -)))
565 565  
566 566  
567 -=== 2.4.7  ​+5V Output ===
568 568  
569 569  
570 -(((
571 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
572 -)))
458 +=== 2.4.9  ​+5V Output ===
573 573  
574 574  
575 -(((
576 -The 5V output time can be controlled by AT Command.
461 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
577 577  
578 -
579 -)))
580 580  
581 -(((
464 +The 5V output time can be controlled by AT Command.
465 +
582 582  (% style="color:blue" %)**AT+5VT=1000**
583 583  
584 -
585 -)))
586 -
587 -(((
588 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  
591 591  
592 -== 2.5  Downlink Payload ==
593 593  
472 +== 2.4 Uplink Interval ==
594 594  
595 -By default, NDDS75 prints the downlink payload to console port.
474 +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"]]
596 596  
597 -[[image:image-20220709100028-1.png]]
598 598  
599 599  
478 +== 2.5 Downlink Payload ==
479 +
480 +By default, LSE50 prints the downlink payload to console port.
481 +
482 +[[image:image-20220606165544-8.png]]
483 +
484 +
600 600  (((
601 601  (% style="color:blue" %)**Examples:**
602 602  )))
... ... @@ -610,7 +610,7 @@
610 610  )))
611 611  
612 612  (((
613 -If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
498 +If the payload=0100003C, it means set the END Node’s TDC to 0x00003C=60(S), while type code is 01.
614 614  )))
615 615  
616 616  (((
... ... @@ -630,267 +630,734 @@
630 630  )))
631 631  
632 632  (((
633 -If payload = 0x04FF, it will reset the NDDS75
518 +If payload = 0x04FF, it will reset the LSE01
634 634  )))
635 635  
636 636  
637 -* (% style="color:blue" %)**INTMOD**
522 +* (% style="color:blue" %)**CFM**
638 638  
524 +Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0
525 +
526 +
527 +
528 +== 2.6 ​Show Data in DataCake IoT Server ==
529 +
639 639  (((
640 -Downlink Payload: 06000003, Set AT+INTMOD=3
531 +[[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:
641 641  )))
642 642  
534 +(((
535 +
536 +)))
643 643  
644 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
538 +(((
539 +(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the network at this time.
540 +)))
645 645  
542 +(((
543 +(% 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:
544 +)))
646 646  
647 -(% style="color:blue" %)** ➢ AT Command:**
648 648  
649 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
547 +[[image:1654505857935-743.png]]
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
550 +[[image:1654505874829-548.png]]
654 654  
655 -² When min≠0 and max≠0, Alarm higher than max or lower than min
656 656  
553 +(% style="color:blue" %)**Step 3**(%%)**:**  Create an account or log in Datacake.
657 657  
658 -(% style="color:blue" %)** Example:**
555 +(% style="color:blue" %)**Step 4**(%%)**:**  Search the LSE01 and add DevEUI.
659 659  
660 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
661 661  
558 +[[image:1654505905236-553.png]]
662 662  
663 -== 2.7  Set the number of data to be uploaded and the recording time ==
664 664  
561 +After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
665 665  
666 -(% style="color:blue" %)** ➢ AT Command:**
563 +[[image:1654505925508-181.png]]
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**:**
672 672  
673 -[[image:image-20221009001114-1.png||height="687" width="955"]]
567 +== 2.7 Frequency Plans ==
674 674  
569 +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.
675 675  
676 -== 2.8  Read or Clear cached data ==
677 677  
572 +=== 2.7.1 EU863-870 (EU868) ===
678 678  
679 -(% style="color:blue" %)** ➢ AT Command:**
574 +(% style="color:#037691" %)** Uplink:**
680 680  
681 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
682 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
576 +868.1 - SF7BW125 to SF12BW125
683 683  
684 -[[image:image-20220908175333-2.png]]
578 +868.3 - SF7BW125 to SF12BW125 and SF7BW250
685 685  
580 +868.5 - SF7BW125 to SF12BW125
686 686  
687 -== 2.9  ​LED Indicator ==
582 +867.1 - SF7BW125 to SF12BW125
688 688  
584 +867.3 - SF7BW125 to SF12BW125
689 689  
690 -The NDDS75 has an internal LED which is to show the status of different state.
586 +867.5 - SF7BW125 to SF12BW125
691 691  
588 +867.7 - SF7BW125 to SF12BW125
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.
590 +867.9 - SF7BW125 to SF12BW125
697 697  
592 +868.8 - FSK
593 +
594 +
595 +(% style="color:#037691" %)** Downlink:**
596 +
597 +Uplink channels 1-9 (RX1)
598 +
599 +869.525 - SF9BW125 (RX2 downlink only)
600 +
601 +
602 +
603 +=== 2.7.2 US902-928(US915) ===
604 +
605 +Used in USA, Canada and South America. Default use CHE=2
606 +
607 +(% style="color:#037691" %)**Uplink:**
608 +
609 +903.9 - SF7BW125 to SF10BW125
610 +
611 +904.1 - SF7BW125 to SF10BW125
612 +
613 +904.3 - SF7BW125 to SF10BW125
614 +
615 +904.5 - SF7BW125 to SF10BW125
616 +
617 +904.7 - SF7BW125 to SF10BW125
618 +
619 +904.9 - SF7BW125 to SF10BW125
620 +
621 +905.1 - SF7BW125 to SF10BW125
622 +
623 +905.3 - SF7BW125 to SF10BW125
624 +
625 +
626 +(% style="color:#037691" %)**Downlink:**
627 +
628 +923.3 - SF7BW500 to SF12BW500
629 +
630 +923.9 - SF7BW500 to SF12BW500
631 +
632 +924.5 - SF7BW500 to SF12BW500
633 +
634 +925.1 - SF7BW500 to SF12BW500
635 +
636 +925.7 - SF7BW500 to SF12BW500
637 +
638 +926.3 - SF7BW500 to SF12BW500
639 +
640 +926.9 - SF7BW500 to SF12BW500
641 +
642 +927.5 - SF7BW500 to SF12BW500
643 +
644 +923.3 - SF12BW500(RX2 downlink only)
645 +
646 +
647 +
648 +=== 2.7.3 CN470-510 (CN470) ===
649 +
650 +Used in China, Default use CHE=1
651 +
652 +(% style="color:#037691" %)**Uplink:**
653 +
654 +486.3 - SF7BW125 to SF12BW125
655 +
656 +486.5 - SF7BW125 to SF12BW125
657 +
658 +486.7 - SF7BW125 to SF12BW125
659 +
660 +486.9 - SF7BW125 to SF12BW125
661 +
662 +487.1 - SF7BW125 to SF12BW125
663 +
664 +487.3 - SF7BW125 to SF12BW125
665 +
666 +487.5 - SF7BW125 to SF12BW125
667 +
668 +487.7 - SF7BW125 to SF12BW125
669 +
670 +
671 +(% style="color:#037691" %)**Downlink:**
672 +
673 +506.7 - SF7BW125 to SF12BW125
674 +
675 +506.9 - SF7BW125 to SF12BW125
676 +
677 +507.1 - SF7BW125 to SF12BW125
678 +
679 +507.3 - SF7BW125 to SF12BW125
680 +
681 +507.5 - SF7BW125 to SF12BW125
682 +
683 +507.7 - SF7BW125 to SF12BW125
684 +
685 +507.9 - SF7BW125 to SF12BW125
686 +
687 +508.1 - SF7BW125 to SF12BW125
688 +
689 +505.3 - SF12BW125 (RX2 downlink only)
690 +
691 +
692 +
693 +=== 2.7.4 AU915-928(AU915) ===
694 +
695 +Default use CHE=2
696 +
697 +(% style="color:#037691" %)**Uplink:**
698 +
699 +916.8 - SF7BW125 to SF12BW125
700 +
701 +917.0 - SF7BW125 to SF12BW125
702 +
703 +917.2 - SF7BW125 to SF12BW125
704 +
705 +917.4 - SF7BW125 to SF12BW125
706 +
707 +917.6 - SF7BW125 to SF12BW125
708 +
709 +917.8 - SF7BW125 to SF12BW125
710 +
711 +918.0 - SF7BW125 to SF12BW125
712 +
713 +918.2 - SF7BW125 to SF12BW125
714 +
715 +
716 +(% style="color:#037691" %)**Downlink:**
717 +
718 +923.3 - SF7BW500 to SF12BW500
719 +
720 +923.9 - SF7BW500 to SF12BW500
721 +
722 +924.5 - SF7BW500 to SF12BW500
723 +
724 +925.1 - SF7BW500 to SF12BW500
725 +
726 +925.7 - SF7BW500 to SF12BW500
727 +
728 +926.3 - SF7BW500 to SF12BW500
729 +
730 +926.9 - SF7BW500 to SF12BW500
731 +
732 +927.5 - SF7BW500 to SF12BW500
733 +
734 +923.3 - SF12BW500(RX2 downlink only)
735 +
736 +
737 +
738 +=== 2.7.5 AS920-923 & AS923-925 (AS923) ===
739 +
740 +(% style="color:#037691" %)**Default Uplink channel:**
741 +
742 +923.2 - SF7BW125 to SF10BW125
743 +
744 +923.4 - SF7BW125 to SF10BW125
745 +
746 +
747 +(% style="color:#037691" %)**Additional Uplink Channel**:
748 +
749 +(OTAA mode, channel added by JoinAccept message)
750 +
751 +(% style="color:#037691" %)**AS920~~AS923 for Japan, Malaysia, Singapore**:
752 +
753 +922.2 - SF7BW125 to SF10BW125
754 +
755 +922.4 - SF7BW125 to SF10BW125
756 +
757 +922.6 - SF7BW125 to SF10BW125
758 +
759 +922.8 - SF7BW125 to SF10BW125
760 +
761 +923.0 - SF7BW125 to SF10BW125
762 +
763 +922.0 - SF7BW125 to SF10BW125
764 +
765 +
766 +(% style="color:#037691" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**:
767 +
768 +923.6 - SF7BW125 to SF10BW125
769 +
770 +923.8 - SF7BW125 to SF10BW125
771 +
772 +924.0 - SF7BW125 to SF10BW125
773 +
774 +924.2 - SF7BW125 to SF10BW125
775 +
776 +924.4 - SF7BW125 to SF10BW125
777 +
778 +924.6 - SF7BW125 to SF10BW125
779 +
780 +
781 +(% style="color:#037691" %)** Downlink:**
782 +
783 +Uplink channels 1-8 (RX1)
784 +
785 +923.2 - SF10BW125 (RX2)
786 +
787 +
788 +
789 +=== 2.7.6 KR920-923 (KR920) ===
790 +
791 +Default channel:
792 +
793 +922.1 - SF7BW125 to SF12BW125
794 +
795 +922.3 - SF7BW125 to SF12BW125
796 +
797 +922.5 - SF7BW125 to SF12BW125
798 +
799 +
800 +(% style="color:#037691" %)**Uplink: (OTAA mode, channel added by JoinAccept message)**
801 +
802 +922.1 - SF7BW125 to SF12BW125
803 +
804 +922.3 - SF7BW125 to SF12BW125
805 +
806 +922.5 - SF7BW125 to SF12BW125
807 +
808 +922.7 - SF7BW125 to SF12BW125
809 +
810 +922.9 - SF7BW125 to SF12BW125
811 +
812 +923.1 - SF7BW125 to SF12BW125
813 +
814 +923.3 - SF7BW125 to SF12BW125
815 +
816 +
817 +(% style="color:#037691" %)**Downlink:**
818 +
819 +Uplink channels 1-7(RX1)
820 +
821 +921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
822 +
823 +
824 +
825 +=== 2.7.7 IN865-867 (IN865) ===
826 +
827 +(% style="color:#037691" %)** Uplink:**
828 +
829 +865.0625 - SF7BW125 to SF12BW125
830 +
831 +865.4025 - SF7BW125 to SF12BW125
832 +
833 +865.9850 - SF7BW125 to SF12BW125
834 +
835 +
836 +(% style="color:#037691" %) **Downlink:**
837 +
838 +Uplink channels 1-3 (RX1)
839 +
840 +866.550 - SF10BW125 (RX2)
841 +
842 +
843 +
844 +
845 +== 2.8 LED Indicator ==
846 +
847 +The LSE01 has an internal LED which is to show the status of different state.
848 +
849 +* Blink once when device power on.
850 +* Solid ON for 5 seconds once device successful Join the network.
851 +* Blink once when device transmit a packet.
852 +
853 +== 2.9 Installation in Soil ==
854 +
855 +**Measurement the soil surface**
856 +
857 +
858 +[[image:1654506634463-199.png]] ​
859 +
698 698  (((
861 +(((
862 +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.
863 +)))
864 +)))
865 +
866 +
867 +
868 +[[image:1654506665940-119.png]]
869 +
870 +(((
871 +Dig a hole with diameter > 20CM.
872 +)))
873 +
874 +(((
875 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
876 +)))
877 +
878 +
879 +== 2.10 ​Firmware Change Log ==
880 +
881 +(((
882 +**Firmware download link:**
883 +)))
884 +
885 +(((
886 +[[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/]]
887 +)))
888 +
889 +(((
699 699  
700 700  )))
701 701  
893 +(((
894 +**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
895 +)))
702 702  
703 -== 2.10  ​Firmware Change Log ==
897 +(((
898 +
899 +)))
704 704  
901 +(((
902 +**V1.0.**
903 +)))
705 705  
706 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]]
906 +Release
708 708  )))
709 709  
909 +
910 +== 2.11 ​Battery Analysis ==
911 +
912 +=== 2.11.1 ​Battery Type ===
913 +
710 710  (((
711 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
915 +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.
712 712  )))
713 713  
918 +(((
919 +The battery is designed to last for more than 5 years for the LSN50.
920 +)))
714 714  
715 -== 2.11 Battery & Power Consumption ==
922 +(((
923 +(((
924 +The battery-related documents are as below:
925 +)))
926 +)))
716 716  
928 +* (((
929 +[[Battery Dimension>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
930 +)))
931 +* (((
932 +[[Lithium-Thionyl Chloride Battery  datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
933 +)))
934 +* (((
935 +[[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/]]
936 +)))
717 717  
718 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
938 + [[image:image-20220610172436-1.png]]
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/]] .
721 721  
722 722  
723 -= 3. ​ Access NB-IoT Module =
942 +=== 2.11.2 ​Battery Note ===
724 724  
944 +(((
945 +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.
946 +)))
725 725  
948 +
949 +
950 +=== 2.11.3 Replace the battery ===
951 +
726 726  (((
727 -Users can directly access the AT command set of the NB-IoT module.
953 +If Battery is lower than 2.7v, user should replace the battery of LSE01.
728 728  )))
729 729  
730 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/]] 
957 +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.
958 +)))
732 732  
733 -
960 +(((
961 +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)
734 734  )))
735 735  
736 -[[image:1657333200519-600.png]]
737 737  
738 738  
739 -= 4.  Using the AT Commands =
966 += 3. ​Using the AT Commands =
740 740  
741 -== 4.1  Access AT Commands ==
968 +== 3.1 Access AT Commands ==
742 742  
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]]
971 +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.
745 745  
973 +[[image:1654501986557-872.png||height="391" width="800"]]
746 746  
747 -AT+<CMD>?  :  Help on <CMD>
748 748  
749 -AT+<CMD>         :  Run <CMD>
976 +Or if you have below board, use below connection:
750 750  
751 -AT+<CMD>=<value> :  Set the value
752 752  
753 -AT+<CMD>=?  :  Get the value
979 +[[image:1654502005655-729.png||height="503" width="801"]]
754 754  
755 755  
982 +
983 +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:
984 +
985 +
986 + [[image:1654502050864-459.png||height="564" width="806"]]
987 +
988 +
989 +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]]
990 +
991 +
992 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%) : Help on <CMD>
993 +
994 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD> **(%%) : Run <CMD>
995 +
996 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=<value>**(%%) : Set the value
997 +
998 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=?**(%%)  : Get the value
999 +
1000 +
756 756  (% style="color:#037691" %)**General Commands**(%%)      
757 757  
758 -AT  :  Attention       
1003 +(% style="background-color:#dcdcdc" %)**AT**(%%)  : Attention       
759 759  
760 -AT?  :  Short Help     
1005 +(% style="background-color:#dcdcdc" %)**AT?**(%%)  : Short Help     
761 761  
762 -ATZ  :  MCU Reset    
1007 +(% style="background-color:#dcdcdc" %)**ATZ**(%%)  : MCU Reset    
763 763  
764 -AT+TDC  :  Application Data Transmission Interval
1009 +(% style="background-color:#dcdcdc" %)**AT+TDC**(%%)  : Application Data Transmission Interval 
765 765  
766 -AT+CFG  :  Print all configurations
767 767  
768 -AT+CFGMOD           :  Working mode selection
1012 +(% style="color:#037691" %)**Keys, IDs and EUIs management**
769 769  
770 -AT+INTMOD            :  Set the trigger interrupt mode
1014 +(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%)              : Application EUI      
771 771  
772 -AT+5VT  :  Set extend the time of 5V power  
1016 +(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%)              : Application Key     
773 773  
774 -AT+PRO  :  Choose agreement
1018 +(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%)            : Application Session Key
775 775  
776 -AT+WEIGRE  :  Get weight or set weight to 0
1020 +(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%)              : Device Address     
777 777  
778 -AT+WEIGAP  :  Get or Set the GapValue of weight
1022 +(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%)                   : Device EUI     
779 779  
780 -AT+RXDL  :  Extend the sending and receiving time
1024 +(% style="background-color:#dcdcdc" %)**AT+NWKID**(%%)               : Network ID (You can enter this command change only after successful network connection) 
781 781  
782 -AT+CNTFAC  :  Get or set counting parameters
1026 +(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%)          : Network Session Key Joining and sending date on LoRa network  
783 783  
784 -AT+SERVADDR  :  Server Address
1028 +(% style="background-color:#dcdcdc" %)**AT+CFM**(%%)  : Confirm Mode       
785 785  
786 -AT+TR  :  Get or Set record time"
1030 +(% style="background-color:#dcdcdc" %)**AT+CFS**(%%)                     : Confirm Status       
787 787  
788 -AT+APN     :  Get or set the APN
1032 +(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%)  : Join LoRa? Network       
789 789  
790 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
1034 +(% style="background-color:#dcdcdc" %)**AT+NJM**(%%)  : LoRa? Network Join Mode    
791 791  
792 -AT+DNSCFG  : Get or Set DNS Server
1036 +(% style="background-color:#dcdcdc" %)**AT+NJS**(%%)                     : LoRa? Network Join Status    
793 793  
794 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
1038 +(% style="background-color:#dcdcdc" %)**AT+RECV**(%%)                  : Print Last Received Data in Raw Format
795 795  
796 -AT+NOUD  :  Get or Set the number of data to be uploaded
1040 +(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%)                : Print Last Received Data in Binary Format      
797 797  
798 -AT+CDP     :  Read or Clear cached data
1042 +(% style="background-color:#dcdcdc" %)**AT+SEND**(%%)                  : Send Text Data      
799 799  
800 -AT+LDDSALARM :  Get or Set alarm of distance
1044 +(% style="background-color:#dcdcdc" %)**AT+SENB**(%%)                  : Send Hexadecimal Data
801 801  
802 802  
803 -(% style="color:#037691" %)**COAP Management**      
1047 +(% style="color:#037691" %)**LoRa Network Management**
804 804  
805 -AT+URI            :  Resource parameters
1049 +(% style="background-color:#dcdcdc" %)**AT+ADR**(%%)          : Adaptive Rate
806 806  
1051 +(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%)  : LoRa Class(Currently only support class A
807 807  
808 -(% style="color:#037691" %)**UDP Management**
1053 +(% style="background-color:#dcdcdc" %)**AT+DCS**(%%)  : Duty Cycle Setting 
809 809  
810 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
1055 +(% style="background-color:#dcdcdc" %)**AT+DR**(%%)  : Data Rate (Can Only be Modified after ADR=0)     
811 811  
1057 +(% style="background-color:#dcdcdc" %)**AT+FCD**(%%)  : Frame Counter Downlink       
812 812  
813 -(% style="color:#037691" %)**MQTT Management**
1059 +(% style="background-color:#dcdcdc" %)**AT+FCU**(%%)  : Frame Counter Uplink   
814 814  
815 -AT+CLIENT  :  Get or Set MQTT client
1061 +(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%)  : Join Accept Delay1
816 816  
817 -AT+UNAME  :  Get or Set MQTT Username
1063 +(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%)  : Join Accept Delay2
818 818  
819 -AT+PWD  :  Get or Set MQTT password
1065 +(% style="background-color:#dcdcdc" %)**AT+PNM**(%%)  : Public Network Mode   
820 820  
821 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
1067 +(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%)  : Receive Delay1      
822 822  
823 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
1069 +(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%)  : Receive Delay2      
824 824  
1071 +(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%)  : Rx2 Window Data Rate 
825 825  
826 -(% style="color:#037691" %)**Information**          
1073 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%)  : Rx2 Window Frequency
827 827  
828 -AT+FDR  :  Factory Data Reset
1075 +(% style="background-color:#dcdcdc" %)**AT+TXP**(%%)  : Transmit Power
829 829  
830 -AT+PWORD  :  Serial Access Password
1077 +(% style="background-color:#dcdcdc" %)**AT+ MOD**(%%)  : Set work mode
831 831  
832 832  
833 -= ​5.  FAQ =
1080 +(% style="color:#037691" %)**Information** 
834 834  
835 -== 5.1 ​ How to Upgrade Firmware ==
1082 +(% style="background-color:#dcdcdc" %)**AT+RSSI**(%%)           : RSSI of the Last Received Packet   
836 836  
1084 +(% style="background-color:#dcdcdc" %)**AT+SNR**(%%)           : SNR of the Last Received Packet   
837 837  
1086 +(% style="background-color:#dcdcdc" %)**AT+VER**(%%)           : Image Version and Frequency Band       
1087 +
1088 +(% style="background-color:#dcdcdc" %)**AT+FDR**(%%)           : Factory Data Reset
1089 +
1090 +(% style="background-color:#dcdcdc" %)**AT+PORT**(%%)  : Application Port    
1091 +
1092 +(% style="background-color:#dcdcdc" %)**AT+CHS**(%%)  : Get or Set Frequency (Unit: Hz) for Single Channel Mode
1093 +
1094 + (% style="background-color:#dcdcdc" %)**AT+CHE**(%%)  : Get or Set eight channels mode, Only for US915, AU915, CN470
1095 +
1096 +
1097 += ​4. FAQ =
1098 +
1099 +== 4.1 ​How to change the LoRa Frequency Bands/Region? ==
1100 +
838 838  (((
839 -User can upgrade the firmware for 1) bug fix, 2) new feature release.
1102 +You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]].
1103 +When downloading the images, choose the required image file for download. ​
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]]
1107 +
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.**
1111 +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.
848 848  )))
849 849  
1114 +(((
1115 +
1116 +)))
850 850  
851 -= 6.  Trouble Shooting =
1118 +(((
1119 +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.
1120 +)))
852 852  
853 -== 6.1  ​Connection problem when uploading firmware ==
1122 +(((
1123 +
1124 +)))
854 854  
1126 +(((
1127 +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.
1128 +)))
855 855  
1130 +[[image:image-20220606154726-3.png]]
1131 +
1132 +
1133 +When you use the TTN network, the US915 frequency bands use are:
1134 +
1135 +* 903.9 - SF7BW125 to SF10BW125
1136 +* 904.1 - SF7BW125 to SF10BW125
1137 +* 904.3 - SF7BW125 to SF10BW125
1138 +* 904.5 - SF7BW125 to SF10BW125
1139 +* 904.7 - SF7BW125 to SF10BW125
1140 +* 904.9 - SF7BW125 to SF10BW125
1141 +* 905.1 - SF7BW125 to SF10BW125
1142 +* 905.3 - SF7BW125 to SF10BW125
1143 +* 904.6 - SF8BW500
1144 +
856 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]]
1146 +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:
1147 +
1148 +* (% style="color:#037691" %)**AT+CHE=2**
1149 +* (% style="color:#037691" %)**ATZ**
858 858  )))
859 859  
860 -(% class="wikigeneratedid" %)
861 861  (((
862 862  
1154 +
1155 +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.
863 863  )))
864 864  
865 -== 6.2  AT Command input doesn't work ==
1158 +(((
1159 +
1160 +)))
866 866  
1162 +(((
1163 +The **AU915** band is similar. Below are the AU915 Uplink Channels.
1164 +)))
867 867  
1166 +[[image:image-20220606154825-4.png]]
1167 +
1168 +
1169 +== 4.2 ​Can I calibrate LSE01 to different soil types? ==
1170 +
1171 +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]].
1172 +
1173 +
1174 += 5. Trouble Shooting =
1175 +
1176 +== 5.1 ​Why I can't join TTN in US915 / AU915 bands? ==
1177 +
1178 +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.
1179 +
1180 +
1181 +== 5.2 AT Command input doesn't work ==
1182 +
868 868  (((
869 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.
870 870  )))
871 871  
872 872  
873 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
1188 +== 5.3 Device rejoin in at the second uplink packet ==
874 874  
1190 +(% style="color:#4f81bd" %)**Issue describe 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]]//**.
1192 +[[image:1654500909990-784.png]]
877 877  
878 878  
879 -= 7. ​ Order Info =
1195 +(% style="color:#4f81bd" %)**Cause for this issue:**
880 880  
1197 +(((
1198 +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.
1199 +)))
881 881  
882 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
883 883  
1202 +(% style="color:#4f81bd" %)**Solution: **
884 884  
885 -= 8.  Packing Info =
1204 +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:
886 886  
1206 +[[image:1654500929571-736.png||height="458" width="832"]]
1207 +
1208 +
1209 += 6. ​Order Info =
1210 +
1211 +
1212 +Part Number**:** (% style="color:#4f81bd" %)**LSE01-XX-YY**
1213 +
1214 +
1215 +(% style="color:#4f81bd" %)**XX**(%%)**:** The default frequency band
1216 +
1217 +* (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band
1218 +* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
1219 +* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
1220 +* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
1221 +* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
1222 +* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
1223 +* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1224 +* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1225 +
1226 +(% style="color:#4f81bd" %)**YY**(%%)**: **Battery Option
1227 +
1228 +* (% style="color:red" %)**4**(%%): 4000mAh battery
1229 +* (% style="color:red" %)**8**(%%): 8500mAh battery
1230 +
1231 +(% class="wikigeneratedid" %)
887 887  (((
888 888  
1234 +)))
889 889  
1236 += 7. Packing Info =
1237 +
1238 +(((
1239 +
1240 +
890 890  (% style="color:#037691" %)**Package Includes**:
1242 +)))
891 891  
892 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
893 -* External antenna x 1
1244 +* (((
1245 +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**:
1252 +)))
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
1254 +* (((
1255 +Device Size: cm
905 905  )))
1257 +* (((
1258 +Device Weight: g
1259 +)))
1260 +* (((
1261 +Package Size / pcs : cm
1262 +)))
1263 +* (((
1264 +Weight / pcs : g
906 906  
907 -(((
908 908  
909 -
910 -
911 911  )))
912 912  
913 -= 9.  Support =
1269 += 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