Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 45.6 >
edited by Xiaoling
on 2022/07/08 10:57
To version < 64.4 >
edited by Xiaoling
on 2022/07/08 14:44
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -59,8 +59,6 @@
59 59  * Micro SIM card slot for NB-IoT SIM
60 60  * 8500mAh Battery for long term use
61 61  
62 -
63 -
64 64  == 1.3  Specification ==
65 65  
66 66  
... ... @@ -69,7 +69,6 @@
69 69  * Supply Voltage: 2.1v ~~ 3.6v
70 70  * Operating Temperature: -40 ~~ 85°C
71 71  
72 -
73 73  (% style="color:#037691" %)**NB-IoT Spec:**
74 74  
75 75  * - B1 @H-FDD: 2100MHz
... ... @@ -79,7 +79,6 @@
79 79  * - B20 @H-FDD: 800MHz
80 80  * - B28 @H-FDD: 700MHz
81 81  
82 -
83 83  (% style="color:#037691" %)**Probe Specification:**
84 84  
85 85  Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
... ... @@ -126,6 +126,7 @@
126 126  
127 127  == 2.2 ​ Configure the NSE01 ==
128 128  
125 +
129 129  === 2.2.1 Test Requirement ===
130 130  
131 131  
... ... @@ -135,11 +135,12 @@
135 135  * The local NB-IoT network used the band that NSE01 supports.
136 136  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
137 137  
138 -
135 +(((
139 139  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
137 +)))
140 140  
141 141  
142 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.gif]]
140 +[[image:1657249419225-449.png]]
143 143  
144 144  
145 145  
... ... @@ -147,23 +147,24 @@
147 147  
148 148  Insert the NB-IoT Card get from your provider.
149 149  
150 -
151 151  User need to take out the NB-IoT module and insert the SIM card like below:
152 152  
153 153  
154 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.gif]]
151 +[[image:1657249468462-536.png]]
155 155  
156 156  
154 +
157 157  === 2.2.3 Connect USB – TTL to NSE01 to configure it ===
158 158  
157 +(((
158 +(((
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.
160 +)))
161 +)))
159 159  
160 -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.
161 161  
164 +**Connection:**
162 162  
163 -
164 -
165 -Connection:
166 -
167 167   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
168 168  
169 169   (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
... ... @@ -171,181 +171,175 @@
171 171   (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
172 172  
173 173  
174 -
175 175  In the PC, use below serial tool settings:
176 176  
177 -* Baud: ** (% style="background-color:green" %)9600**(%%)
178 -* Data bits:** (% style="background-color:green" %)8**(%%)
179 -* Stop bits: **(% style="background-color:green" %)1**(%%)
180 -* Parity: **(% style="background-color:green" %)None**(%%)
181 -* Flow Control: **(% style="background-color:green" %)None**
175 +* Baud:  (% style="color:green" %)**9600**
176 +* Data bits:** (% style="color:green" %)8(%%)**
177 +* Stop bits: (% style="color:green" %)**1**
178 +* Parity:  (% style="color:green" %)**None**
179 +* Flow Control: (% style="color:green" %)**None**
182 182  
181 +(((
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.
183 +)))
183 183  
184 -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="background-color:green" %)password: 12345678**(%%) to access AT Command input.
185 +[[image:image-20220708110657-3.png]]
185 185  
186 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.jpg]]
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/]]
187 187  
188 -Note: the valid AT Commands can be found at:
189 189  
190 -[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
191 191  
191 +=== 2.2.4 Use CoAP protocol to uplink data ===
192 192  
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/]]
193 193  
194 -=== 2.2.4 Use CoAP protocol to uplink data === 
195 195  
196 +**Use below commands:**
196 196  
197 -(% style="background-color:red" %)Note: if you don’t have CoAP server, you can refer this link to set up one:
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
198 198  
199 -[[http:~~/~~/wiki.dragino.com/index.php?title=Set_up_CoAP_Server>>url:http://wiki.dragino.com/index.php?title=Set_up_CoAP_Server]]
202 +For parameter description, please refer to AT command set
200 200  
204 +[[image:1657249793983-486.png]]
201 201  
202 -Use below commands:
203 203  
204 -* **(% style="color:blue" %)AT+PRO=1**  (%%)  ~/~/ Set to use CoAP protocol to uplink
205 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
206 -* **(% style="color:blue" %)AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%)      ~/~/Set COAP resource path
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.
207 207  
209 +[[image:1657249831934-534.png]]
208 208  
209 -For parameter description, please refer to AT command set
210 210  
211 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.jpg]]
212 212  
213 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
213 213  
214 -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.
215 +This feature is supported since firmware version v1.0.1
215 215  
216 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.jpg]]
217 217  
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
218 218  
219 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
222 +[[image:1657249864775-321.png]]
220 220  
221 221  
222 -This feature is supported since firmware version v1.0.1
225 +[[image:1657249930215-289.png]]
223 223  
224 224  
225 -* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
226 -* **AT+SERVADDR=120.24.4.116,5601   **~/~/ to set UDP server address and port
227 -* **AT+CFM=1       **~/~/If the server does not respond, this command is unnecessary
228 228  
229 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.jpg]]
229 +=== 2.2.6 Use MQTT protocol to uplink data ===
230 230  
231 +This feature is supported since firmware version v110
231 231  
232 232  
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
233 233  
242 +[[image:1657249978444-674.png]]
234 234  
235 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.jpg]]
236 236  
245 +[[image:1657249990869-686.png]]
237 237  
238 -1.
239 -11.
240 -111. Use MQTT protocol to uplink data
241 241  
248 +(((
249 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
250 +)))
242 242  
243 -This feature is supported since firmware version v110
244 244  
245 245  
246 -* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
247 -* **AT+SERVADDR=120.24.4.116,1883   **~/~/Set MQTT server address and port
248 -* **AT+CLIENT=CLIENT **~/~/Set up the CLIENT of MQTT
249 -* **AT+UNAME=UNAME                           **~/~/Set the username of MQTT
250 -* **AT+PWD=PWD                                      **~/~/Set the password of MQTT
251 -* **AT+PUBTOPIC=NSE01_PUB   **~/~/Set the sending topic of MQTT
252 -* **AT+SUBTOPIC=NSE01_SUB    **~/~/Set the subscription topic of MQTT
254 +=== 2.2.7 Use TCP protocol to uplink data ===
253 253  
256 +This feature is supported since firmware version v110
254 254  
255 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.gif]]
256 256  
257 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.jpg]]
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
258 258  
262 +[[image:1657250217799-140.png]]
259 259  
260 -MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
261 261  
265 +[[image:1657250255956-604.png]]
262 262  
263 -1.
264 -11.
265 -111. Use TCP protocol to uplink data
266 266  
267 267  
268 -This feature is supported since firmware version v110
269 +=== 2.2.8 Change Update Interval ===
269 269  
271 +User can use below command to change the (% style="color:green" %)**uplink interval**.
270 270  
271 -* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
272 -* **AT+SERVADDR=120.24.4.116,5600   **~/~/ to set TCP server address and port
273 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
273 273  
274 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.jpg]]
275 +(((
276 +(% style="color:red" %)**NOTE:**
277 +)))
275 275  
279 +(((
280 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
281 +)))
276 276  
277 277  
278 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.jpg]]
279 279  
285 +== 2.3  Uplink Payload ==
280 280  
281 -1.
282 -11.
283 -111. Change Update Interval
287 +In this mode, uplink payload includes in total 18 bytes
284 284  
285 -User can use below command to change the **uplink interval**.
289 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
290 +|=(% style="width: 50px;" %)(((
291 +**Size(bytes)**
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"]]
286 286  
287 -**~ AT+TDC=600      **~/~/ Set Update Interval to 600s
295 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
288 288  
289 289  
290 -**NOTE:**
298 +[[image:image-20220708111918-4.png]]
291 291  
292 -1. By default, the device will send an uplink message every 1 hour.
293 293  
301 +The payload is ASCII string, representative same HEX:
294 294  
303 +0x72403155615900640c7817075e0a8c02f900 where:
295 295  
305 +* Device ID: 0x 724031556159 = 724031556159
306 +* Version: 0x0064=100=1.0.0
296 296  
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
297 297  
315 +== 2.4  Payload Explanation and Sensor Interface ==
298 298  
299 299  
300 -== 2.3 Uplink Payload ==
318 +=== 2.4.1  Device ID ===
301 301  
320 +By default, the Device ID equal to the last 6 bytes of IMEI.
302 302  
303 -=== 2.3.1 MOD~=0(Default Mode) ===
322 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
304 304  
305 -LSE01 will uplink payload via LoRaWAN with below payload format: 
324 +**Example:**
306 306  
307 -(((
308 -Uplink payload includes in total 11 bytes.
309 -)))
326 +AT+DEUI=A84041F15612
310 310  
311 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
312 -|(((
313 -**Size**
328 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
314 314  
315 -**(bytes)**
316 -)))|**2**|**2**|**2**|**2**|**2**|**1**
317 -|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
318 -Temperature
319 319  
320 -(Reserve, Ignore now)
321 -)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]]|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]]|(((
322 -MOD & Digital Interrupt
323 323  
324 -(Optional)
325 -)))
332 +=== 2.4.2  Version Info ===
326 326  
327 -=== 2.3.2 MOD~=1(Original value) ===
334 +Specify the software version: 0x64=100, means firmware version 1.00.
328 328  
329 -This mode can get the original AD value of moisture and original conductivity (with temperature drift compensation).
336 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
330 330  
331 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
332 -|(((
333 -**Size**
334 334  
335 -**(bytes)**
336 -)))|**2**|**2**|**2**|**2**|**2**|**1**
337 -|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
338 -Temperature
339 339  
340 -(Reserve, Ignore now)
341 -)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]](raw)|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]](raw)|(((
342 -MOD & Digital Interrupt
340 +=== 2.4.3  Battery Info ===
343 343  
344 -(Optional)
345 -)))
346 -
347 -=== 2.3.3 Battery Info ===
348 -
349 349  (((
350 350  Check the battery voltage for LSE01.
351 351  )))
... ... @@ -360,14 +360,32 @@
360 360  
361 361  
362 362  
363 -=== 2.3.4 Soil Moisture ===
356 +=== 2.4.4  Signal Strength ===
364 364  
358 +NB-IoT Network signal Strength.
359 +
360 +**Ex1: 0x1d = 29**
361 +
362 +(% style="color:blue" %)**0**(%%)  -113dBm or less
363 +
364 +(% style="color:blue" %)**1**(%%)  -111dBm
365 +
366 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
367 +
368 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
369 +
370 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
371 +
372 +
373 +
374 +=== 2.4.5  Soil Moisture ===
375 +
365 365  (((
366 366  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.
367 367  )))
368 368  
369 369  (((
370 -For example, if the data you get from the register is __0x05 0xDC__, the moisture content in the soil is
381 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
371 371  )))
372 372  
373 373  (((
... ... @@ -380,10 +380,10 @@
380 380  
381 381  
382 382  
383 -=== 2.3.5 Soil Temperature ===
394 +=== 2.4.6  Soil Temperature ===
384 384  
385 385  (((
386 - 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
397 + Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is __**0x09 0xEC**__, the temperature content in the soil is
387 387  )))
388 388  
389 389  (((
... ... @@ -400,7 +400,7 @@
400 400  
401 401  
402 402  
403 -=== 2.3.6 Soil Conductivity (EC) ===
414 +=== 2.4.7  Soil Conductivity (EC) ===
404 404  
405 405  (((
406 406  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).
... ... @@ -407,7 +407,7 @@
407 407  )))
408 408  
409 409  (((
410 -For example, if the data you get from the register is 0x00 0xC8, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
421 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
411 411  )))
412 412  
413 413  (((
... ... @@ -422,52 +422,46 @@
422 422  
423 423  )))
424 424  
425 -=== 2.3.7 MOD ===
436 +=== 2.4.8  Digital Interrupt ===
426 426  
427 -Firmware version at least v2.1 supports changing mode.
438 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server.
428 428  
429 -For example, bytes[10]=90
440 +The command is:
430 430  
431 -mod=(bytes[10]>>7)&0x01=1.
442 +(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
432 432  
433 433  
434 -**Downlink Command:**
445 +The lower four bits of this data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H"]] for the hardware and software set up.
435 435  
436 -If payload = 0x0A00, workmode=0
437 437  
438 -If** **payload =** **0x0A01, workmode=1
448 +Example:
439 439  
450 +0x(00): Normal uplink packet.
440 440  
452 +0x(01): Interrupt Uplink Packet.
441 441  
442 -=== 2.3.8 ​Decode payload in The Things Network ===
443 443  
444 -While using TTN network, you can add the payload format to decode the payload.
445 445  
456 +=== 2.4.9  ​+5V Output ===
446 446  
447 -[[image:1654505570700-128.png]]
458 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
448 448  
449 -(((
450 -The payload decoder function for TTN is here:
451 -)))
452 452  
453 -(((
454 -LSE01 TTN Payload Decoder: [[https:~~/~~/www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0>>https://www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0]]
455 -)))
461 +The 5V output time can be controlled by AT Command.
456 456  
463 +(% style="color:blue" %)**AT+5VT=1000**
457 457  
458 -== 2.4 Uplink Interval ==
465 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
459 459  
460 -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"]]
461 461  
462 462  
469 +== 2.5  Downlink Payload ==
463 463  
464 -== 2.5 Downlink Payload ==
471 +By default, NSE01 prints the downlink payload to console port.
465 465  
466 -By default, LSE50 prints the downlink payload to console port.
473 +[[image:image-20220708133731-5.png]]
467 467  
468 -[[image:image-20220606165544-8.png]]
469 469  
470 -
471 471  (((
472 472  (% style="color:blue" %)**Examples:**
473 473  )))
... ... @@ -481,7 +481,7 @@
481 481  )))
482 482  
483 483  (((
484 -If the payload=0100003C, it means set the END Node’s TDC to 0x00003C=60(S), while type code is 01.
489 +If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
485 485  )))
486 486  
487 487  (((
... ... @@ -501,662 +501,262 @@
501 501  )))
502 502  
503 503  (((
504 -If payload = 0x04FF, it will reset the LSE01
509 +If payload = 0x04FF, it will reset the NSE01
505 505  )))
506 506  
507 507  
508 -* (% style="color:blue" %)**CFM**
513 +* (% style="color:blue" %)**INTMOD**
509 509  
510 -Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0
515 +Downlink Payload: 06000003, Set AT+INTMOD=3
511 511  
512 512  
513 513  
514 -== 2.6 ​Show Data in DataCake IoT Server ==
519 +== 2.6  ​LED Indicator ==
515 515  
516 516  (((
517 -[[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:
518 -)))
522 +The NSE01 has an internal LED which is to show the status of different state.
519 519  
520 -(((
521 -
522 -)))
523 523  
524 -(((
525 -(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the network at this time.
525 +* When power on, NSE01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
526 +* Then the LED will be on for 1 second means device is boot normally.
527 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
528 +* For each uplink probe, LED will be on for 500ms.
526 526  )))
527 527  
528 -(((
529 -(% 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:
530 -)))
531 531  
532 532  
533 -[[image:1654505857935-743.png]]
534 534  
534 +== 2.7  Installation in Soil ==
535 535  
536 -[[image:1654505874829-548.png]]
536 +__**Measurement the soil surface**__
537 537  
538 +Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]]
538 538  
539 -(% style="color:blue" %)**Step 3**(%%)**:**  Create an account or log in Datacake.
540 +[[image:1657259653666-883.png]] ​
540 540  
541 -(% style="color:blue" %)**Step 4**(%%)**:**  Search the LSE01 and add DevEUI.
542 542  
543 +(((
544 +
543 543  
544 -[[image:1654505905236-553.png]]
546 +(((
547 +Dig a hole with diameter > 20CM.
548 +)))
545 545  
550 +(((
551 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
552 +)))
553 +)))
546 546  
547 -After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
555 +[[image:1654506665940-119.png]]
548 548  
549 -[[image:1654505925508-181.png]]
557 +(((
558 +
559 +)))
550 550  
551 551  
562 +== 2.8  ​Firmware Change Log ==
552 552  
553 -== 2.7 Frequency Plans ==
554 554  
555 -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.
565 +Download URL & Firmware Change log
556 556  
567 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
557 557  
558 -=== 2.7.1 EU863-870 (EU868) ===
559 559  
560 -(% style="color:#037691" %)** Uplink:**
570 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H"]]
561 561  
562 -868.1 - SF7BW125 to SF12BW125
563 563  
564 -868.3 - SF7BW125 to SF12BW125 and SF7BW250
565 565  
566 -868.5 - SF7BW125 to SF12BW125
574 +== 2.9  ​Battery Analysis ==
567 567  
568 -867.1 - SF7BW125 to SF12BW125
576 +=== 2.9.1  ​Battery Type ===
569 569  
570 -867.3 - SF7BW125 to SF12BW125
571 571  
572 -867.5 - SF7BW125 to SF12BW125
579 +The NSE01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
573 573  
574 -867.7 - SF7BW125 to SF12BW125
575 575  
576 -867.9 - SF7BW125 to SF12BW125
582 +The battery is designed to last for several years depends on the actually use environment and update interval. 
577 577  
578 -868.8 - FSK
579 579  
585 +The battery related documents as below:
580 580  
581 -(% style="color:#037691" %)** Downlink:**
587 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
588 +* [[Lithium-Thionyl Chloride Battery>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]][[ datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
589 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
582 582  
583 -Uplink channels 1-9 (RX1)
584 -
585 -869.525 - SF9BW125 (RX2 downlink only)
586 -
587 -
588 -
589 -=== 2.7.2 US902-928(US915) ===
590 -
591 -Used in USA, Canada and South America. Default use CHE=2
592 -
593 -(% style="color:#037691" %)**Uplink:**
594 -
595 -903.9 - SF7BW125 to SF10BW125
596 -
597 -904.1 - SF7BW125 to SF10BW125
598 -
599 -904.3 - SF7BW125 to SF10BW125
600 -
601 -904.5 - SF7BW125 to SF10BW125
602 -
603 -904.7 - SF7BW125 to SF10BW125
604 -
605 -904.9 - SF7BW125 to SF10BW125
606 -
607 -905.1 - SF7BW125 to SF10BW125
608 -
609 -905.3 - SF7BW125 to SF10BW125
610 -
611 -
612 -(% style="color:#037691" %)**Downlink:**
613 -
614 -923.3 - SF7BW500 to SF12BW500
615 -
616 -923.9 - SF7BW500 to SF12BW500
617 -
618 -924.5 - SF7BW500 to SF12BW500
619 -
620 -925.1 - SF7BW500 to SF12BW500
621 -
622 -925.7 - SF7BW500 to SF12BW500
623 -
624 -926.3 - SF7BW500 to SF12BW500
625 -
626 -926.9 - SF7BW500 to SF12BW500
627 -
628 -927.5 - SF7BW500 to SF12BW500
629 -
630 -923.3 - SF12BW500(RX2 downlink only)
631 -
632 -
633 -
634 -=== 2.7.3 CN470-510 (CN470) ===
635 -
636 -Used in China, Default use CHE=1
637 -
638 -(% style="color:#037691" %)**Uplink:**
639 -
640 -486.3 - SF7BW125 to SF12BW125
641 -
642 -486.5 - SF7BW125 to SF12BW125
643 -
644 -486.7 - SF7BW125 to SF12BW125
645 -
646 -486.9 - SF7BW125 to SF12BW125
647 -
648 -487.1 - SF7BW125 to SF12BW125
649 -
650 -487.3 - SF7BW125 to SF12BW125
651 -
652 -487.5 - SF7BW125 to SF12BW125
653 -
654 -487.7 - SF7BW125 to SF12BW125
655 -
656 -
657 -(% style="color:#037691" %)**Downlink:**
658 -
659 -506.7 - SF7BW125 to SF12BW125
660 -
661 -506.9 - SF7BW125 to SF12BW125
662 -
663 -507.1 - SF7BW125 to SF12BW125
664 -
665 -507.3 - SF7BW125 to SF12BW125
666 -
667 -507.5 - SF7BW125 to SF12BW125
668 -
669 -507.7 - SF7BW125 to SF12BW125
670 -
671 -507.9 - SF7BW125 to SF12BW125
672 -
673 -508.1 - SF7BW125 to SF12BW125
674 -
675 -505.3 - SF12BW125 (RX2 downlink only)
676 -
677 -
678 -
679 -=== 2.7.4 AU915-928(AU915) ===
680 -
681 -Default use CHE=2
682 -
683 -(% style="color:#037691" %)**Uplink:**
684 -
685 -916.8 - SF7BW125 to SF12BW125
686 -
687 -917.0 - SF7BW125 to SF12BW125
688 -
689 -917.2 - SF7BW125 to SF12BW125
690 -
691 -917.4 - SF7BW125 to SF12BW125
692 -
693 -917.6 - SF7BW125 to SF12BW125
694 -
695 -917.8 - SF7BW125 to SF12BW125
696 -
697 -918.0 - SF7BW125 to SF12BW125
698 -
699 -918.2 - SF7BW125 to SF12BW125
700 -
701 -
702 -(% style="color:#037691" %)**Downlink:**
703 -
704 -923.3 - SF7BW500 to SF12BW500
705 -
706 -923.9 - SF7BW500 to SF12BW500
707 -
708 -924.5 - SF7BW500 to SF12BW500
709 -
710 -925.1 - SF7BW500 to SF12BW500
711 -
712 -925.7 - SF7BW500 to SF12BW500
713 -
714 -926.3 - SF7BW500 to SF12BW500
715 -
716 -926.9 - SF7BW500 to SF12BW500
717 -
718 -927.5 - SF7BW500 to SF12BW500
719 -
720 -923.3 - SF12BW500(RX2 downlink only)
721 -
722 -
723 -
724 -=== 2.7.5 AS920-923 & AS923-925 (AS923) ===
725 -
726 -(% style="color:#037691" %)**Default Uplink channel:**
727 -
728 -923.2 - SF7BW125 to SF10BW125
729 -
730 -923.4 - SF7BW125 to SF10BW125
731 -
732 -
733 -(% style="color:#037691" %)**Additional Uplink Channel**:
734 -
735 -(OTAA mode, channel added by JoinAccept message)
736 -
737 -(% style="color:#037691" %)**AS920~~AS923 for Japan, Malaysia, Singapore**:
738 -
739 -922.2 - SF7BW125 to SF10BW125
740 -
741 -922.4 - SF7BW125 to SF10BW125
742 -
743 -922.6 - SF7BW125 to SF10BW125
744 -
745 -922.8 - SF7BW125 to SF10BW125
746 -
747 -923.0 - SF7BW125 to SF10BW125
748 -
749 -922.0 - SF7BW125 to SF10BW125
750 -
751 -
752 -(% style="color:#037691" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**:
753 -
754 -923.6 - SF7BW125 to SF10BW125
755 -
756 -923.8 - SF7BW125 to SF10BW125
757 -
758 -924.0 - SF7BW125 to SF10BW125
759 -
760 -924.2 - SF7BW125 to SF10BW125
761 -
762 -924.4 - SF7BW125 to SF10BW125
763 -
764 -924.6 - SF7BW125 to SF10BW125
765 -
766 -
767 -(% style="color:#037691" %)** Downlink:**
768 -
769 -Uplink channels 1-8 (RX1)
770 -
771 -923.2 - SF10BW125 (RX2)
772 -
773 -
774 -
775 -=== 2.7.6 KR920-923 (KR920) ===
776 -
777 -Default channel:
778 -
779 -922.1 - SF7BW125 to SF12BW125
780 -
781 -922.3 - SF7BW125 to SF12BW125
782 -
783 -922.5 - SF7BW125 to SF12BW125
784 -
785 -
786 -(% style="color:#037691" %)**Uplink: (OTAA mode, channel added by JoinAccept message)**
787 -
788 -922.1 - SF7BW125 to SF12BW125
789 -
790 -922.3 - SF7BW125 to SF12BW125
791 -
792 -922.5 - SF7BW125 to SF12BW125
793 -
794 -922.7 - SF7BW125 to SF12BW125
795 -
796 -922.9 - SF7BW125 to SF12BW125
797 -
798 -923.1 - SF7BW125 to SF12BW125
799 -
800 -923.3 - SF7BW125 to SF12BW125
801 -
802 -
803 -(% style="color:#037691" %)**Downlink:**
804 -
805 -Uplink channels 1-7(RX1)
806 -
807 -921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
808 -
809 -
810 -
811 -=== 2.7.7 IN865-867 (IN865) ===
812 -
813 -(% style="color:#037691" %)** Uplink:**
814 -
815 -865.0625 - SF7BW125 to SF12BW125
816 -
817 -865.4025 - SF7BW125 to SF12BW125
818 -
819 -865.9850 - SF7BW125 to SF12BW125
820 -
821 -
822 -(% style="color:#037691" %) **Downlink:**
823 -
824 -Uplink channels 1-3 (RX1)
825 -
826 -866.550 - SF10BW125 (RX2)
827 -
828 -
829 -
830 -
831 -== 2.8 LED Indicator ==
832 -
833 -The LSE01 has an internal LED which is to show the status of different state.
834 -
835 -* Blink once when device power on.
836 -* Solid ON for 5 seconds once device successful Join the network.
837 -* Blink once when device transmit a packet.
838 -
839 -== 2.9 Installation in Soil ==
840 -
841 -**Measurement the soil surface**
842 -
843 -
844 -[[image:1654506634463-199.png]] ​
845 -
846 846  (((
847 -(((
848 -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.
592 +[[image:image-20220708140453-6.png]]
849 849  )))
850 -)))
851 851  
852 852  
853 853  
854 -[[image:1654506665940-119.png]]
597 +=== 2.9.2  Power consumption Analyze ===
855 855  
856 856  (((
857 -Dig a hole with diameter > 20CM.
600 +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.
858 858  )))
859 859  
860 -(((
861 -Horizontal insert the probe to the soil and fill the hole for long term measurement.
862 -)))
863 863  
864 -
865 -== 2.10 ​Firmware Change Log ==
866 -
867 867  (((
868 -**Firmware download link:**
605 +Instruction to use as below:
869 869  )))
870 870  
871 871  (((
872 -[[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/]]
609 +(% 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/]]
873 873  )))
874 874  
875 -(((
876 -
877 -)))
878 878  
879 879  (((
880 -**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
614 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
881 881  )))
882 882  
883 -(((
884 -
617 +* (((
618 +Product Model
885 885  )))
886 -
887 -(((
888 -**V1.0.**
620 +* (((
621 +Uplink Interval
889 889  )))
623 +* (((
624 +Working Mode
625 +)))
890 890  
891 891  (((
892 -Release
628 +And the Life expectation in difference case will be shown on the right.
893 893  )))
894 894  
631 +[[image:image-20220708141352-7.jpeg]]
895 895  
896 -== 2.11 ​Battery Analysis ==
897 897  
898 -=== 2.11.1 ​Battery Type ===
899 899  
900 -(((
901 -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.
902 -)))
635 +=== 2.9.3  ​Battery Note ===
903 903  
904 904  (((
905 -The battery is designed to last for more than 5 years for the LSN50.
638 +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.
906 906  )))
907 907  
908 -(((
909 -(((
910 -The battery-related documents are as below:
911 -)))
912 -)))
913 913  
914 -* (((
915 -[[Battery Dimension>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
916 -)))
917 -* (((
918 -[[Lithium-Thionyl Chloride Battery  datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
919 -)))
920 -* (((
921 -[[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/]]
922 -)))
923 923  
924 - [[image:image-20220610172436-1.png]]
643 +=== 2.9.4  Replace the battery ===
925 925  
926 -
927 -
928 -=== 2.11.2 ​Battery Note ===
929 -
930 930  (((
931 -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.
646 +The default battery pack of NSE01 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
932 932  )))
933 933  
934 934  
935 935  
936 -=== 2.11.3 Replace the battery ===
651 += 3. ​ Access NB-IoT Module =
937 937  
938 938  (((
939 -If Battery is lower than 2.7v, user should replace the battery of LSE01.
654 +Users can directly access the AT command set of the NB-IoT module.
940 940  )))
941 941  
942 942  (((
943 -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.
658 +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/]] 
944 944  )))
945 945  
946 -(((
947 -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)
948 -)))
661 +[[image:1657261278785-153.png]]
949 949  
950 950  
951 951  
952 -= 3. ​Using the AT Commands =
665 += 4.  Using the AT Commands =
953 953  
954 -== 3.1 Access AT Commands ==
667 +== 4.1  Access AT Commands ==
955 955  
669 +See this link for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
956 956  
957 -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.
958 958  
959 -[[image:1654501986557-872.png||height="391" width="800"]]
672 +AT+<CMD>?  : Help on <CMD>
960 960  
674 +AT+<CMD>         : Run <CMD>
961 961  
962 -Or if you have below board, use below connection:
676 +AT+<CMD>=<value> : Set the value
963 963  
678 +AT+<CMD>=?  : Get the value
964 964  
965 -[[image:1654502005655-729.png||height="503" width="801"]]
966 966  
967 -
968 -
969 -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:
970 -
971 -
972 - [[image:1654502050864-459.png||height="564" width="806"]]
973 -
974 -
975 -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]]
976 -
977 -
978 -(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%) : Help on <CMD>
979 -
980 -(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD> **(%%) : Run <CMD>
981 -
982 -(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=<value>**(%%) : Set the value
983 -
984 -(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=?**(%%)  : Get the value
985 -
986 -
987 987  (% style="color:#037691" %)**General Commands**(%%)      
988 988  
989 -(% style="background-color:#dcdcdc" %)**AT**(%%)  : Attention       
683 +AT  : Attention       
990 990  
991 -(% style="background-color:#dcdcdc" %)**AT?**(%%)  : Short Help     
685 +AT?  : Short Help     
992 992  
993 -(% style="background-color:#dcdcdc" %)**ATZ**(%%)  : MCU Reset    
687 +ATZ  : MCU Reset    
994 994  
995 -(% style="background-color:#dcdcdc" %)**AT+TDC**(%%)  : Application Data Transmission Interval 
689 +AT+TDC  : Application Data Transmission Interval
996 996  
691 +AT+CFG  : Print all configurations
997 997  
998 -(% style="color:#037691" %)**Keys, IDs and EUIs management**
693 +AT+CFGMOD           : Working mode selection
999 999  
1000 -(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%)              : Application EUI      
695 +AT+INTMOD            : Set the trigger interrupt mode
1001 1001  
1002 -(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%)              : Application Key     
697 +AT+5VT  : Set extend the time of 5V power  
1003 1003  
1004 -(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%)            : Application Session Key
699 +AT+PRO  : Choose agreement
1005 1005  
1006 -(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%)              : Device Address     
701 +AT+WEIGRE  : Get weight or set weight to 0
1007 1007  
1008 -(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%)                   : Device EUI     
703 +AT+WEIGAP  : Get or Set the GapValue of weight
1009 1009  
1010 -(% style="background-color:#dcdcdc" %)**AT+NWKID**(%%)               : Network ID (You can enter this command change only after successful network connection) 
705 +AT+RXDL  : Extend the sending and receiving time
1011 1011  
1012 -(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%)          : Network Session Key Joining and sending date on LoRa network  
707 +AT+CNTFAC  : Get or set counting parameters
1013 1013  
1014 -(% style="background-color:#dcdcdc" %)**AT+CFM**(%%)  : Confirm Mode       
709 +AT+SERVADDR  : Server Address
1015 1015  
1016 -(% style="background-color:#dcdcdc" %)**AT+CFS**(%%)                     : Confirm Status       
1017 1017  
1018 -(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%)  : Join LoRa? Network       
712 +(% style="color:#037691" %)**COAP Management**      
1019 1019  
1020 -(% style="background-color:#dcdcdc" %)**AT+NJM**(%%)  : LoRa? Network Join Mode    
714 +AT+URI            : Resource parameters
1021 1021  
1022 -(% style="background-color:#dcdcdc" %)**AT+NJS**(%%)                     : LoRa? Network Join Status    
1023 1023  
1024 -(% style="background-color:#dcdcdc" %)**AT+RECV**(%%)                  : Print Last Received Data in Raw Format
717 +(% style="color:#037691" %)**UDP Management**
1025 1025  
1026 -(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%)                : Print Last Received Data in Binary Format      
719 +AT+CFM          : Upload confirmation mode (only valid for UDP)
1027 1027  
1028 -(% style="background-color:#dcdcdc" %)**AT+SEND**(%%)                  : Send Text Data      
1029 1029  
1030 -(% style="background-color:#dcdcdc" %)**AT+SENB**(%%)                  : Send Hexadecimal Data
722 +(% style="color:#037691" %)**MQTT Management**
1031 1031  
724 +AT+CLIENT               : Get or Set MQTT client
1032 1032  
1033 -(% style="color:#037691" %)**LoRa Network Management**
726 +AT+UNAME  : Get or Set MQTT Username
1034 1034  
1035 -(% style="background-color:#dcdcdc" %)**AT+ADR**(%%)          : Adaptive Rate
728 +AT+PWD                  : Get or Set MQTT password
1036 1036  
1037 -(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%)  : LoRa Class(Currently only support class A
730 +AT+PUBTOPIC  : Get or Set MQTT publish topic
1038 1038  
1039 -(% style="background-color:#dcdcdc" %)**AT+DCS**(%%)  : Duty Cycle Setting 
732 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
1040 1040  
1041 -(% style="background-color:#dcdcdc" %)**AT+DR**(%%)  : Data Rate (Can Only be Modified after ADR=0)     
1042 1042  
1043 -(% style="background-color:#dcdcdc" %)**AT+FCD**(%%)  : Frame Counter Downlink       
735 +(% style="color:#037691" %)**Information**          
1044 1044  
1045 -(% style="background-color:#dcdcdc" %)**AT+FCU**(%%)  : Frame Counter Uplink   
737 +AT+FDR  : Factory Data Reset
1046 1046  
1047 -(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%)  : Join Accept Delay1
739 +AT+PWORD  : Serial Access Password
1048 1048  
1049 -(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%)  : Join Accept Delay2
1050 1050  
1051 -(% style="background-color:#dcdcdc" %)**AT+PNM**(%%)  : Public Network Mode   
1052 1052  
1053 -(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%)  : Receive Delay1      
743 += ​5.  FAQ =
1054 1054  
1055 -(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%)  : Receive Delay2      
745 +== 5.1 ​ How to Upgrade Firmware ==
1056 1056  
1057 -(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%)  : Rx2 Window Data Rate 
1058 1058  
1059 -(% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%)  : Rx2 Window Frequency
1060 -
1061 -(% style="background-color:#dcdcdc" %)**AT+TXP**(%%)  : Transmit Power
1062 -
1063 -(% style="background-color:#dcdcdc" %)**AT+ MOD**(%%)  : Set work mode
1064 -
1065 -
1066 -(% style="color:#037691" %)**Information** 
1067 -
1068 -(% style="background-color:#dcdcdc" %)**AT+RSSI**(%%)           : RSSI of the Last Received Packet   
1069 -
1070 -(% style="background-color:#dcdcdc" %)**AT+SNR**(%%)           : SNR of the Last Received Packet   
1071 -
1072 -(% style="background-color:#dcdcdc" %)**AT+VER**(%%)           : Image Version and Frequency Band       
1073 -
1074 -(% style="background-color:#dcdcdc" %)**AT+FDR**(%%)           : Factory Data Reset
1075 -
1076 -(% style="background-color:#dcdcdc" %)**AT+PORT**(%%)  : Application Port    
1077 -
1078 -(% style="background-color:#dcdcdc" %)**AT+CHS**(%%)  : Get or Set Frequency (Unit: Hz) for Single Channel Mode
1079 -
1080 - (% style="background-color:#dcdcdc" %)**AT+CHE**(%%)  : Get or Set eight channels mode, Only for US915, AU915, CN470
1081 -
1082 -
1083 -= ​4. FAQ =
1084 -
1085 -== 4.1 ​How to change the LoRa Frequency Bands/Region? ==
1086 -
1087 1087  (((
1088 -You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]].
1089 -When downloading the images, choose the required image file for download. ​
749 +User can upgrade the firmware for 1) bug fix, 2) new feature release.
1090 1090  )))
1091 1091  
1092 1092  (((
1093 -
753 +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]]
1094 1094  )))
1095 1095  
1096 1096  (((
1097 -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.
757 +Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
1098 1098  )))
1099 1099  
1100 -(((
1101 -
1102 -)))
1103 1103  
1104 1104  (((
1105 -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.
1106 -)))
1107 -
1108 -(((
1109 1109  
1110 1110  )))
1111 1111  
1112 -(((
1113 -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.
1114 -)))
1115 -
1116 -[[image:image-20220606154726-3.png]]
1117 -
1118 -
1119 -When you use the TTN network, the US915 frequency bands use are:
1120 -
1121 -* 903.9 - SF7BW125 to SF10BW125
1122 -* 904.1 - SF7BW125 to SF10BW125
1123 -* 904.3 - SF7BW125 to SF10BW125
1124 -* 904.5 - SF7BW125 to SF10BW125
1125 -* 904.7 - SF7BW125 to SF10BW125
1126 -* 904.9 - SF7BW125 to SF10BW125
1127 -* 905.1 - SF7BW125 to SF10BW125
1128 -* 905.3 - SF7BW125 to SF10BW125
1129 -* 904.6 - SF8BW500
1130 -
1131 -(((
1132 -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:
1133 -
1134 -* (% style="color:#037691" %)**AT+CHE=2**
1135 -* (% style="color:#037691" %)**ATZ**
1136 -)))
1137 -
1138 -(((
1139 -
1140 -
1141 -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.
1142 -)))
1143 -
1144 -(((
1145 -
1146 -)))
1147 -
1148 -(((
1149 -The **AU915** band is similar. Below are the AU915 Uplink Channels.
1150 -)))
1151 -
1152 -[[image:image-20220606154825-4.png]]
1153 -
1154 -
1155 -== 4.2 ​Can I calibrate LSE01 to different soil types? ==
1156 -
1157 -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]].
1158 -
1159 -
1160 1160  = 5. Trouble Shooting =
1161 1161  
1162 1162  == 5.1 ​Why I can't join TTN in US915 / AU915 bands? ==
1657249419225-449.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +81.0 KB
Content
1657249468462-536.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +483.6 KB
Content
1657249793983-486.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.8 KB
Content
1657249831934-534.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +72.5 KB
Content
1657249864775-321.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +87.0 KB
Content
1657249930215-289.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.3 KB
Content
1657249978444-674.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +139.5 KB
Content
1657249990869-686.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +96.9 KB
Content
1657250217799-140.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.7 KB
Content
1657250255956-604.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +99.0 KB
Content
1657259653666-883.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +344.4 KB
Content
1657260785982-288.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.2 KB
Content
1657261119050-993.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
1657261278785-153.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
image-20220708110657-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +251.7 KB
Content
image-20220708111918-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +38.8 KB
Content
image-20220708133731-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +8.7 KB
Content
image-20220708140453-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +132.7 KB
Content
image-20220708141352-7.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +102.7 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0