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