Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual

Last modified by Bei Jinggeng on 2024/05/31 09:53

From version < 35.10 >

edited by Xiaoling
on 2022/06/14 14:04

To version < 45.4 >

edited by Xiaoling
on 2022/07/08 10:36

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 4 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--LSE01-LoRaWAN Soil Moisture & EC Sensor User Manual
++NSE01 - NB-IoT Soil Moisture & EC Sensor User Manual

Content

@@ -3,9 +3,7 @@
--**Table of Contents:**
--{{toc/}}
@@ -12,65 +12,85 @@
--= 1. Introduction =
--== 1.1 What is LoRaWAN Soil Moisture & EC Sensor ==
++**Table of Contents:**
++
++
++
++
++
++= 1.  Introduction =
++
++== 1.1  What is LoRaWAN Soil Moisture & EC Sensor ==
++
  (((
--The Dragino LSE01 is a (% style="color:#4f81bd" %)**LoRaWAN Soil Moisture & EC Sensor**(%%) for IoT of Agriculture. It is designed to measure the soil moisture of saline-alkali soil and loamy soil. The soil sensor uses FDR method to calculate the soil moisture with the compensation from soil temperature and conductivity. It also has been calibrated in factory for Mineral soil type.
--)))
++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.
--(((
--It detects (% style="color:#4f81bd" %)**Soil Moisture**(%%), (% style="color:#4f81bd" %)**Soil Temperature**(%%) and (% style="color:#4f81bd" %)**Soil Conductivity**(%%), and uploads the value via wireless to LoRaWAN IoT Server.
--)))
++It can detect (% style="color:blue" %)**Soil Moisture, Soil Temperature and Soil Conductivity**(%%), and upload its value to the server wirelessly.
--(((
--The LoRa wireless technology used in LES01 allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption.
--)))
++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.
--(((
--LES01 is powered by (% style="color:#4f81bd" %)**4000mA or 8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 10 years.
--)))
++NSE01 are powered by (% style="color:blue" %)**8500mAh Li-SOCI2**(%%) batteries, which can be used for up to 5 years.
--(((
--Each LES01 is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect after power on.
++
  )))
--
  [[image:1654503236291-817.png]]
--[[image:1654503265560-120.png]]
++[[image:1657245163077-232.png]]
  == 1.2 Features ==
--* LoRaWAN 1.0.3 Class A
--* Ultra low power consumption
++
++* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
  * Monitor Soil Moisture
  * Monitor Soil Temperature
  * Monitor Soil Conductivity
--* Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
  * AT Commands to change parameters
  * Uplink on periodically
  * Downlink to change configure
  * IP66 Waterproof Enclosure
--* 4000mAh or 8500mAh Battery for long term use
++* Ultra-Low Power consumption
++* AT Commands to change parameters
++* Micro SIM card slot for NB-IoT SIM
++* 8500mAh Battery for long term use
--== 1.3 Specification ==
++== 1.3  Specification ==
++
++(% style="color:#037691" %)**Common DC Characteristics:**
++
++* Supply Voltage: 2.1v ~~ 3.6v
++* Operating Temperature: -40 ~~ 85°C
++
++
++(% style="color:#037691" %)**NB-IoT Spec:**
++
++* - B1 @H-FDD: 2100MHz
++* - B3 @H-FDD: 1800MHz
++* - B8 @H-FDD: 900MHz
++* - B5 @H-FDD: 850MHz
++* - B20 @H-FDD: 800MHz
++* - B28 @H-FDD: 700MHz
++
++
++(% style="color:#037691" %)**Probe Specification:**
++
  Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
--[[image:image-20220606162220-5.png]]
++[[image:image-20220708101224-1.png]]
--== 1.4 Applications ==
++== 1.4  Applications ==
  * Smart Agriculture
@@ -77,73 +77,214 @@
  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
--== 1.5 Firmware Change log ==
++== 1.5  Pin Definitions ==
--**LSE01 v1.0 :**  Release
++[[image:1657246476176-652.png]]
--= 2. Configure LSE01 to connect to LoRaWAN network =
++= 2.  Use NSE01 to communicate with IoT Server =
--== 2.1 How it works ==
++== 2.1  How it works ==
++
  (((
--The LSE01 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LSE0150. It will automatically join the network via OTAA and start to send the sensor value
++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.
  )))
++
  (((
--In case you can’t set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H3.200BUsingtheATCommands"]].
++The diagram below shows the working flow in default firmware of NSE01:
  )))
++[[image:image-20220708101605-2.png]]
++(((
++
++)))
--== 2.2 Quick guide to connect to LoRaWAN server (OTAA) ==
--Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LG308>>url:http://www.dragino.com/products/lora/item/140-lg308.html]]  as a LoRaWAN gateway in this example.
++== 2.2  Configure the NSE01 ==
--[[image:1654503992078-669.png]]
++=== 2.2.1  Test Requirement ===
--The LG308 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server.
++To use NSE01 in your city, make sure meet below requirements:
++* Your local operator has already distributed a NB-IoT Network there.
++* The local NB-IoT network used the band that NSE01 supports.
++* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
--(% style="color:blue" %)**Step 1**(%%):  Create a device in TTN with the OTAA keys from LSE01.
--Each LSE01 is shipped with a sticker with the default device EUI as below:
++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
--[[image:image-20220606163732-6.jpeg]]
--You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.gif]]
--**Add APP EUI in the application**
--[[image:1654504596150-405.png]]
++1.
++11.
++111. Insert SIM card
++Insert the NB-IoT Card get from your provider.
--**Add APP KEY and DEV EUI**
++User need to take out the NB-IoT module and insert the SIM card like below:
--[[image:1654504683289-357.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.gif]]
--(% style="color:blue" %)**Step 2**(%%): Power on LSE01
++1.
++11.
++111. Connect USB – TTL to NSE01 to configure it
--Put a Jumper on JP2 to power on the device. ( The Jumper must be in FLASH position).
++User need to configure NSE01 via serial port to set the **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.
--[[image:image-20220606163915-7.png]]
--(% style="color:blue" %)**Step 3**(%%)**:** The LSE01 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel.
--[[image:1654504778294-788.png]]
++Connection:
++USB TTL GND <~-~-~-~-> GND
++USB TTL TXD <~-~-~-~-> UART_RXD
++USB TTL RXD <~-~-~-~-> UART_TXD
++
++
++
++In the PC, use below serial tool settings:
++
++* Baud: **9600**
++* Data bits:** 8**
++* Stop bits: **1**
++* Parity: **None**
++* Flow Control: **None**
++
++
++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 **password: 12345678** to access AT Command input.
++
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.jpg]]
++
++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/]]
++
++
++1.
++11.
++111. Use CoAP protocol to uplink data
++
++
++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]]
++
++
++Use below commands:
++
++* **AT+PRO=1**    ~/~/ Set to use CoAP protocol to uplink
++* **AT+SERVADDR=120.24.4.116,5683   **~/~/ to set CoAP server address and port
++* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0"       **~/~/Set COAP resource path
++
++
++For parameter description, please refer to AT command set
++
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.jpg]]
++
++
++After configure the server address and **reset the device** (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server.
++
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.jpg]]
++
++1.
++11.
++111. Use UDP protocol to uplink data(Default protocol)
++
++
++This feature is supported since firmware version v1.0.1
++
++
++* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
++* **AT+SERVADDR=120.24.4.116,5601   **~/~/ to set UDP server address and port
++* **AT+CFM=1       **~/~/If the server does not respond, this command is unnecessary
++
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.jpg]]
++
++
++
++
++
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.jpg]]
++
++
++1.
++11.
++111. Use MQTT protocol to uplink data
++
++
++This feature is supported since firmware version v110
++
++
++* **AT+PRO=3   **                                            ~/~/Set to use MQTT protocol to uplink
++* **AT+SERVADDR=120.24.4.116,1883   **~/~/Set MQTT server address and port
++* **AT+CLIENT=CLIENT                              **~/~/Set up the CLIENT of MQTT
++* **AT+UNAME=UNAME                           **~/~/Set the username of MQTT
++* **AT+PWD=PWD                                      **~/~/Set the password of MQTT
++* **AT+PUBTOPIC=NSE01_PUB             **~/~/Set the sending topic of MQTT
++* **AT+SUBTOPIC=NSE01_SUB                 **~/~/Set the subscription topic of MQTT
++
++
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.gif]]
++
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.jpg]]
++
++
++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.
++
++
++1.
++11.
++111. Use TCP protocol to uplink data
++
++
++This feature is supported since firmware version v110
++
++
++* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
++* **AT+SERVADDR=120.24.4.116,5600   **~/~/ to set TCP server address and port
++
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.jpg]]
++
++
++
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.jpg]]
++
++
++1.
++11.
++111. Change Update Interval
++
++User can use below command to change the **uplink interval**.
++
++**~         AT+TDC=600      **~/~/ Set Update Interval to 600s
++
++
++**NOTE:**
++
++1. By default, the device will send an uplink message every 1 hour.
++
++
++
++
++
++
++
  == 2.3 Uplink Payload ==
@@ -171,10 +171,6 @@
  (Optional)
  )))
--
--
--
--
  === 2.3.2 MOD~=1(Original value) ===
  This mode can get the original AD value of moisture and original conductivity (with temperature drift compensation).
@@ -195,10 +195,6 @@
  (Optional)
  )))
--
--
--
--
  === 2.3.3 Battery Info ===
  (((
@@ -306,11 +306,10 @@
  )))
  (((
--LSE01 TTN Payload Decoder: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Payload_Decoder/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Payload_Decoder/]]
++LSE01 TTN Payload Decoder: [[https:~~/~~/www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0>>https://www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0]]
  )))
--
  == 2.4 Uplink Interval ==
  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"]]
@@ -325,7 +325,7 @@
  (((
--**Examples:**
++(% style="color:blue" %)**Examples:**
  )))
  (((
@@ -333,7 +333,7 @@
  )))
  * (((
--**Set TDC**
++(% style="color:blue" %)**Set TDC**
  )))
  (((
@@ -353,7 +353,7 @@
  )))
  * (((
--**Reset**
++(% style="color:blue" %)**Reset**
  )))
  (((
@@ -361,7 +361,7 @@
  )))
--* **CFM**
++* (% style="color:blue" %)**CFM**
  Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0
@@ -378,11 +378,11 @@
  )))
  (((
--**Step 1**: Be sure that your device is programmed and properly connected to the network at this time.
++(% style="color:blue" %)**Step 1**(%%):   Be sure that your device is programmed and properly connected to the network at this time.
  )))
  (((
--**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:
++(% 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:
  )))
@@ -391,11 +391,12 @@
  [[image:1654505874829-548.png]]
--Step 3: Create an account or log in Datacake.
--Step 4: Search the LSE01 and add DevEUI.
++(% style="color:blue" %)**Step 3**(%%)**:**   Create an account or log in Datacake.
++(% style="color:blue" %)**Step 4**(%%)**:**   Search the LSE01 and add DevEUI.
++
  [[image:1654505905236-553.png]]
@@ -705,6 +705,7 @@
  )))
++
  [[image:1654506665940-119.png]]
  (((
@@ -766,13 +766,13 @@
  )))
  * (((
--[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
++[[Battery Dimension>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
  )))
  * (((
--[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
++[[Lithium-Thionyl Chloride Battery  datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
  )))
  * (((
--[[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC_1520_datasheet.jpg]], [[Tech Spec>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC1520%20Technical%20Specification20171123.pdf]]
++[[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/]]
  )))
   [[image:image-20220610172436-1.png]]
@@ -826,7 +826,7 @@
   [[image:1654502050864-459.png||height="564" width="806"]]
--Below are the available commands, a more detailed AT Command manual can be found at [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/]]: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/]]
++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]]
  (% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%)                   : Help on <CMD>
@@ -984,19 +984,14 @@
  (((
  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:
--)))
--(% class="box infomessage" %)
--(((
--**AT+CHE=2**
++* (% style="color:#037691" %)**AT+CHE=2**
++* (% style="color:#037691" %)**ATZ**
  )))
--(% class="box infomessage" %)
  (((
--**ATZ**
--)))
++
--(((
  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.
  )))
@@ -1011,18 +1011,22 @@
  [[image:image-20220606154825-4.png]]
++== 4.2 Can I calibrate LSE01 to different soil types? ==
++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]].
++
++
  = 5. Trouble Shooting =
--== 5.1 Why I can’t join TTN in US915 / AU915 bands? ==
++== 5.1 Why I can't join TTN in US915 / AU915 bands? ==
--It is due to channel mapping. Please see the [[Eight Channel Mode>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]] section above for details.
++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.
--== 5.2 AT Command input doesn’t work ==
++== 5.2 AT Command input doesn't work ==
  (((
--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.
++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.
  )))

1657245163077-232.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+81.0 KB

Content

1657246476176-652.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+492.6 KB

Content

image-20220708101224-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+22.2 KB

Content

image-20220708101605-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+87.5 KB

Content

Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual

Summary

Details

Applications

Navigation