<
From version < 52.1 >
edited by Xiaoling
on 2022/07/08 11:12
To version < 57.6 >
edited by Xiaoling
on 2022/07/08 11:52
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -172,10 +172,10 @@
172 172  
173 173  In the PC, use below serial tool settings:
174 174  
175 -* Baud: (% style="color:green" %)**9600**
175 +* Baud:  (% style="color:green" %)**9600**
176 176  * Data bits:** (% style="color:green" %)8(%%)**
177 177  * Stop bits: (% style="color:green" %)**1**
178 -* Parity: (% style="color:green" %)**None**
178 +* Parity:  (% style="color:green" %)**None**
179 179  * Flow Control: (% style="color:green" %)**None**
180 180  
181 181  (((
... ... @@ -190,7 +190,7 @@
190 190  
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/index.php?title=Set_up_CoAP_Server>>url:http://wiki.dragino.com/index.php?title=Set_up_CoAP_Server]]
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/]]
194 194  
195 195  
196 196  **Use below commands:**
... ... @@ -200,7 +200,6 @@
200 200  * (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
201 201  
202 202  
203 -
204 204  For parameter description, please refer to AT command set
205 205  
206 206  [[image:1657249793983-486.png]]
... ... @@ -214,7 +214,6 @@
214 214  
215 215  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
216 216  
217 -
218 218  This feature is supported since firmware version v1.0.1
219 219  
220 220  
... ... @@ -222,51 +222,51 @@
222 222  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
223 223  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
224 224  
225 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.jpg]]
223 +[[image:1657249864775-321.png]]
226 226  
227 227  
226 +[[image:1657249930215-289.png]]
228 228  
229 229  
230 230  
231 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.jpg]]
232 -
233 -
234 234  === 2.2.6 Use MQTT protocol to uplink data ===
235 235  
236 -
237 237  This feature is supported since firmware version v110
238 238  
239 239  
240 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
241 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
242 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
243 -* (% style="color:blue" %)**AT+UNAME=UNAME            **(%%)~/~/Set the username of MQTT
244 -* (% style="color:blue" %)**AT+PWD=PWD                  **(%%)~/~/Set the password of MQTT
245 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB     **(%%)~/~/Set the sending topic of MQTT
246 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
235 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
236 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
237 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
238 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
239 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
240 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
241 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
247 247  
248 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.gif]]
243 +[[image:1657249978444-674.png]]
249 249  
250 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.jpg]]
251 251  
246 +[[image:1657249990869-686.png]]
252 252  
248 +
249 +(((
253 253  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.
251 +)))
254 254  
255 255  
254 +
256 256  === 2.2.7 Use TCP protocol to uplink data ===
257 257  
258 -
259 259  This feature is supported since firmware version v110
260 260  
261 261  
262 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
260 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
263 263  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
264 264  
265 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.jpg]]
263 +[[image:1657250217799-140.png]]
266 266  
267 267  
266 +[[image:1657250255956-604.png]]
268 268  
269 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.jpg]]
270 270  
271 271  
272 272  === 2.2.8 Change Update Interval ===
... ... @@ -273,68 +273,77 @@
273 273  
274 274  User can use below command to change the (% style="color:green" %)**uplink interval**.
275 275  
276 -**~ (% style="color:blue" %)AT+TDC=600      (%%)**(% style="color:blue" %) (%%)~/~/ Set Update Interval to 600s
274 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
277 277  
278 -
276 +(((
279 279  (% style="color:red" %)**NOTE:**
278 +)))
280 280  
280 +(((
281 281  (% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
282 +)))
282 282  
283 283  
284 284  
286 +== 2.3  Uplink Payload ==
285 285  
288 +In this mode, uplink payload includes in total 18 bytes
286 286  
290 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
291 +|=(% style="width: 50px;" %)(((
292 +**Size(bytes)**
293 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 40px;" %)**1**
294 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H"]]|(% style="width:41px" %)[[Ver>>||anchor="H"]]|(% style="width:46px" %)[[BAT>>||anchor="H"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H"]]|(% style="width:108px" %)[[Soil Moisture>>||anchor="H"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H"]]
287 287  
296 +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 -== 2.3 Uplink Payload ==
290 290  
299 +[[image:image-20220708111918-4.png]]
291 291  
292 -=== 2.3.1 MOD~=0(Default Mode) ===
293 293  
294 -LSE01 will uplink payload via LoRaWAN with below payload format
302 +The payload is ASCII string, representative same HEX:
295 295  
296 -(((
297 -Uplink payload includes in total 11 bytes.
298 -)))
304 +0x72403155615900640c7817075e0a8c02f900 where:
299 299  
300 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
301 -|(((
302 -**Size**
306 +* Device ID: 0x 724031556159 = 724031556159
307 +* Version: 0x0064=100=1.0.0
303 303  
304 -**(bytes)**
305 -)))|**2**|**2**|**2**|**2**|**2**|**1**
306 -|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
307 -Temperature
309 +* BAT: 0x0c78 = 3192 mV = 3.192V
310 +* Singal: 0x17 = 23
311 +* Soil Moisture: 0x075e= 1886 = 18.86  %
312 +* Soil Temperature:0x0a8c =2700=27 °C
313 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
314 +* Interrupt: 0x00 = 0
308 308  
309 -(Reserve, Ignore now)
310 -)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]]|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]]|(((
311 -MOD & Digital Interrupt
312 312  
313 -(Optional)
314 -)))
315 315  
316 -=== 2.3.2 MOD~=1(Original value) ===
317 317  
318 -This mode can get the original AD value of moisture and original conductivity (with temperature drift compensation).
319 +== 2.4  Payload Explanation and Sensor Interface ==
319 319  
320 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
321 -|(((
322 -**Size**
321 +=== 2.4.1  Device ID ===
323 323  
324 -**(bytes)**
325 -)))|**2**|**2**|**2**|**2**|**2**|**1**
326 -|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
327 -Temperature
323 +By default, the Device ID equal to the last 6 bytes of IMEI.
328 328  
329 -(Reserve, Ignore now)
330 -)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]](raw)|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]](raw)|(((
331 -MOD & Digital Interrupt
325 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
332 332  
333 -(Optional)
334 -)))
327 +**Example:**
335 335  
336 -=== 2.3.3 Battery Info ===
329 +AT+DEUI=A84041F15612
337 337  
331 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
332 +
333 +
334 +
335 +=== 2.4.2  Version Info ===
336 +
337 +Specify the software version: 0x64=100, means firmware version 1.00.
338 +
339 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
340 +
341 +
342 +
343 +=== 2.4.3  Battery Info ===
344 +
338 338  (((
339 339  Check the battery voltage for LSE01.
340 340  )))
... ... @@ -349,14 +349,32 @@
349 349  
350 350  
351 351  
352 -=== 2.3.4 Soil Moisture ===
359 +=== 2.4.4  Signal Strength ===
353 353  
361 +NB-IoT Network signal Strength.
362 +
363 +**Ex1: 0x1d = 29**
364 +
365 +(% style="color:blue" %)**0**(%%)  -113dBm or less
366 +
367 +(% style="color:blue" %)**1**(%%)  -111dBm
368 +
369 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
370 +
371 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
372 +
373 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
374 +
375 +
376 +
377 +=== 2.4.5  Soil Moisture ===
378 +
354 354  (((
355 355  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.
356 356  )))
357 357  
358 358  (((
359 -For example, if the data you get from the register is __0x05 0xDC__, the moisture content in the soil is
384 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
360 360  )))
361 361  
362 362  (((
... ... @@ -369,10 +369,10 @@
369 369  
370 370  
371 371  
372 -=== 2.3.5 Soil Temperature ===
397 +=== 2.4. Soil Temperature ===
373 373  
374 374  (((
375 - 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
400 + 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
376 376  )))
377 377  
378 378  (((
... ... @@ -389,7 +389,7 @@
389 389  
390 390  
391 391  
392 -=== 2.3.6 Soil Conductivity (EC) ===
417 +=== 2.4. Soil Conductivity (EC) ===
393 393  
394 394  (((
395 395  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).
... ... @@ -396,7 +396,7 @@
396 396  )))
397 397  
398 398  (((
399 -For example, if the data you get from the register is 0x00 0xC8, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
424 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
400 400  )))
401 401  
402 402  (((
... ... @@ -411,39 +411,42 @@
411 411  
412 412  )))
413 413  
414 -=== 2.3.7 MOD ===
439 +=== 2.4. Digital Interrupt ===
415 415  
416 -Firmware version at least v2.1 supports changing mode.
417 417  
418 -For example, bytes[10]=90
442 +Digital Interrupt refers to pin **GPIO_EXTI**, and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server.
419 419  
420 -mod=(bytes[10]>>7)&0x01=1.
444 +The command is:
421 421  
446 +**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]]**).**
422 422  
423 -**Downlink Command:**
424 424  
425 -If payload = 0x0A00, workmode=0
449 +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.
426 426  
427 -If** **payload =** **0x0A01, workmode=1
428 428  
452 +Example:
429 429  
454 +0x(00): Normal uplink packet.
430 430  
431 -=== 2.3.8 ​Decode payload in The Things Network ===
456 +0x(01): Interrupt Uplink Packet.
432 432  
433 -While using TTN network, you can add the payload format to decode the payload.
434 434  
435 435  
436 -[[image:1654505570700-128.png]]
437 437  
438 -(((
439 -The payload decoder function for TTN is here:
440 -)))
461 +=== 2.4.9  ​+5V Output ===
441 441  
442 -(((
443 -LSE01 TTN Payload Decoder: [[https:~~/~~/www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0>>https://www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0]]
444 -)))
445 445  
464 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling.
446 446  
466 +
467 +The 5V output time can be controlled by AT Command.
468 +
469 +**(% style="color:blue" %)AT+5VT=1000**
470 +
471 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
472 +
473 +
474 +
447 447  == 2.4 Uplink Interval ==
448 448  
449 449  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"]]
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
image-20220708111918-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +38.8 KB
Content
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0