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

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

From 44.2 to 44.1 From 65.15 to 65.14

From version 65.14

edited by Xiaoling
on 2022/07/08 15:51

Change comment: There is no comment for this version

To version 44.2

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 20 removed)

Details

Page properties

Content

@@ -13,14 +13,11 @@
  **Table of Contents:**
--{{toc/}}
--
--
  = 1.  Introduction =
  == 1.1  What is LoRaWAN Soil Moisture & EC Sensor ==
@@ -28,21 +28,13 @@
  (((
--(((
  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 can detect (% style="color:blue" %)**Soil Moisture, Soil Temperature and Soil Conductivity**(%%), and upload its value to the server wirelessly.
--)))
--(((
  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.
--)))
--(((
  NSE01 are powered by (% style="color:blue" %)**8500mAh Li-SOCI2**(%%) batteries, which can be used for up to 5 years.
--)))
  )))
@@ -54,8 +54,9 @@
--== 1.2  Features ==
++== 1.2 Features ==
++
  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
  * Monitor Soil Moisture
  * Monitor Soil Temperature
@@ -69,6 +69,8 @@
  * Micro SIM card slot for NB-IoT SIM
  * 8500mAh Battery for long term use
++
++
  == 1.3  Specification ==
@@ -77,6 +77,7 @@
  * Supply Voltage: 2.1v ~~ 3.6v
  * Operating Temperature: -40 ~~ 85°C
++
  (% style="color:#037691" %)**NB-IoT Spec:**
  * - B1 @H-FDD: 2100MHz
@@ -86,8 +86,9 @@
  * - B20 @H-FDD: 800MHz
  * - B28 @H-FDD: 700MHz
--Probe(% style="color:#037691" %)** Specification:**
++(% 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-20220708101224-1.png]]
@@ -108,753 +108,998 @@
--= 2.  Use NSE01 to communicate with IoT Server =
++= 2. Configure LSE01 to connect to LoRaWAN network =
--== 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"]].
  )))
++
++== 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.
++
++
++[[image:1654503992078-669.png]]
++
++
++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.
++
++
++(% 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:
++
++[[image:image-20220606163732-6.jpeg]]
++
++You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
++
++**Add APP EUI in the application**
++
++
++[[image:1654504596150-405.png]]
++
++
++
++**Add APP KEY and DEV EUI**
++
++[[image:1654504683289-357.png]]
++
++
++
++(% style="color:blue" %)**Step 2**(%%): Power on LSE01
++
++
++Put a Jumper on JP2 to power on the device. ( The Jumper must be in FLASH position).
++
++[[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]]
++
++
++
++== 2.3 Uplink Payload ==
++
++
++=== 2.3.1 MOD~=0(Default Mode) ===
++
++LSE01 will uplink payload via LoRaWAN with below payload format:
++
  (((
--The diagram below shows the working flow in default firmware of NSE01:
++Uplink payload includes in total 11 bytes.
  )))
--[[image:image-20220708101605-2.png]]
++(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
++|(((
++**Size**
++**(bytes)**
++)))|**2**|**2**|**2**|**2**|**2**|**1**
++|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
++Temperature
++
++(Reserve, Ignore now)
++)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]]|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]]|(((
++MOD & Digital Interrupt
++
++(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).
++
++(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
++|(((
++**Size**
++
++**(bytes)**
++)))|**2**|**2**|**2**|**2**|**2**|**1**
++|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
++Temperature
++
++(Reserve, Ignore now)
++)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]](raw)|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]](raw)|(((
++MOD & Digital Interrupt
++
++(Optional)
++)))
++
++=== 2.3.3 Battery Info ===
++
  (((
--
++Check the battery voltage for LSE01.
  )))
++(((
++Ex1: 0x0B45 = 2885mV
++)))
++(((
++Ex2: 0x0B49 = 2889mV
++)))
--== 2.2  Configure the NSE01 ==
--=== 2.2.1  Test Requirement ===
++=== 2.3.4 Soil Moisture ===
++(((
++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.
++)))
  (((
--To use NSE01 in your city, make sure meet below requirements:
++For example, if the data you get from the register is __0x05 0xDC__, the moisture content in the soil is
  )))
--* 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.
++(((
++
++)))
  (((
--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
++(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
  )))
--[[image:1657249419225-449.png]]
++=== 2.3.5 Soil Temperature ===
++(((
++ 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
++)))
--=== 2.2.2  Insert SIM card ===
++(((
++**Example**:
++)))
  (((
--Insert the NB-IoT Card get from your provider.
++If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
  )))
  (((
--User need to take out the NB-IoT module and insert the SIM card like below:
++If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
  )))
--[[image:1657249468462-536.png]]
++=== 2.3.6 Soil Conductivity (EC) ===
++(((
++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).
++)))
--=== 2.2.3  Connect USB – TTL to NSE01 to configure it ===
++(((
++For example, if the data you get from the register is 0x00 0xC8, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
++)))
  (((
++Generally, the EC value of irrigation water is less than 800uS / cm.
++)))
++
  (((
--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.
++
  )))
++
++(((
++
  )))
++=== 2.3.7 MOD ===
--**Connection:**
++Firmware version at least v2.1 supports changing mode.
-- (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
++For example, bytes[10]=90
-- (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
++mod=(bytes[10]>>7)&0x01=1.
-- (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
++**Downlink Command:**
--In the PC, use below serial tool settings:
++If payload = 0x0A00,  workmode=0
--* Baud:       (% style="color:green" %)**9600**
--* Data bits:** (% style="color:green" %)8(%%)**
--* Stop bits: (% style="color:green" %)**1**
--* Parity:      (% style="color:green" %)**None**
--* Flow Control: (% style="color:green" %)**None**
++If** **payload =** **0x0A01,  workmode=1
++
++
++=== 2.3.8 Decode payload in The Things Network ===
++
++While using TTN network, you can add the payload format to decode the payload.
++
++
++[[image:1654505570700-128.png]]
++
  (((
--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.
++The payload decoder function for TTN is here:
  )))
--[[image:image-20220708110657-3.png]]
++(((
++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"]]
++
++
++
++== 2.5 Downlink Payload ==
++
++By default, LSE50 prints the downlink payload to console port.
++
++[[image:image-20220606165544-8.png]]
++
++
  (((
--(% 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/]]
++(% style="color:blue" %)**Examples:**
  )))
++(((
++
++)))
++* (((
++(% style="color:blue" %)**Set TDC**
++)))
--=== 2.2.4  Use CoAP protocol to uplink data ===
++(((
++If the payload=0100003C, it means set the END Node’s TDC to 0x00003C=60(S), while type code is 01.
++)))
--(% 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/]]
++(((
++Payload:    01 00 00 1E    TDC=30S
++)))
++(((
++Payload:    01 00 00 3C    TDC=60S
++)))
--**Use below commands:**
++(((
++
++)))
--* (% style="color:blue" %)**AT+PRO=1**  (%%)                                             ~/~/ Set to use CoAP protocol to uplink
--* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   **  (%%)~/~/ to set CoAP server address and port
--* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%)      ~/~/Set COAP resource path
++* (((
++(% style="color:blue" %)**Reset**
++)))
--For parameter description, please refer to AT command set
++(((
++If payload = 0x04FF, it will reset the LSE01
++)))
--[[image:1657249793983-486.png]]
++* (% style="color:blue" %)**CFM**
--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.
++Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0
--[[image:1657249831934-534.png]]
++== 2.6 Show Data in DataCake IoT Server ==
--=== 2.2.5  Use UDP protocol to uplink data(Default protocol) ===
++(((
++[[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:
++)))
--This feature is supported since firmware version v1.0.1
++(((
++
++)))
++(((
++(% style="color:blue" %)**Step 1**(%%):   Be sure that your device is programmed and properly connected to the network at this time.
++)))
--* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
--* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   **  (%%) ~/~/ to set UDP server address and port
--* (% style="color:blue" %)**AT+CFM=1       **   (%%) ~/~/If the server does not respond, this command is unnecessary
++(((
++(% 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:
++)))
--[[image:1657249864775-321.png]]
++[[image:1654505857935-743.png]]
--[[image:1657249930215-289.png]]
++[[image:1654505874829-548.png]]
--=== 2.2.6  Use MQTT protocol to uplink data ===
++(% style="color:blue" %)**Step 3**(%%)**:**   Create an account or log in Datacake.
--This feature is supported since firmware version v110
++(% style="color:blue" %)**Step 4**(%%)**:**   Search the LSE01 and add DevEUI.
--* (% style="color:blue" %)**AT+PRO=3   **       (%%)                                       ~/~/Set to use MQTT protocol to uplink
--* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   **   (%%)   ~/~/Set MQTT server address and port
--* (% style="color:blue" %)**AT+CLIENT=CLIENT       **                           (%%)~/~/Set up the CLIENT of MQTT
--* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
--* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
--* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
--* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%)          ~/~/Set the subscription topic of MQTT
++[[image:1654505905236-553.png]]
--[[image:1657249978444-674.png]]
++After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
--[[image:1657249990869-686.png]]
++[[image:1654505925508-181.png]]
--(((
--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.
--)))
++== 2.7 Frequency Plans ==
++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.
--=== 2.2.7  Use TCP protocol to uplink data ===
--This feature is supported since firmware version v110
++=== 2.7.1 EU863-870 (EU868) ===
++(% style="color:#037691" %)** Uplink:**
--* (% style="color:blue" %)**AT+PRO=4   ** (%%)                                          ~/~/ Set to use TCP protocol to uplink
--* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
++868.1 - SF7BW125 to SF12BW125
--[[image:1657250217799-140.png]]
++868.3 - SF7BW125 to SF12BW125 and SF7BW250
++868.5 - SF7BW125 to SF12BW125
--[[image:1657250255956-604.png]]
++867.1 - SF7BW125 to SF12BW125
++867.3 - SF7BW125 to SF12BW125
++867.5 - SF7BW125 to SF12BW125
--=== 2.2.8  Change Update Interval ===
++867.7 - SF7BW125 to SF12BW125
--User can use below command to change the (% style="color:green" %)**uplink interval**.
++867.9 - SF7BW125 to SF12BW125
--* (% style="color:blue" %)**AT+TDC=600      **  (%%)~/~/ Set Update Interval to 600s
++868.8 - FSK
--(((
--(% style="color:red" %)**NOTE:**
--)))
--(((
--(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
--)))
++(% style="color:#037691" %)** Downlink:**
++Uplink channels 1-9 (RX1)
++869.525 - SF9BW125 (RX2 downlink only)
--== 2.3  Uplink Payload ==
--In this mode, uplink payload includes in total 18 bytes
--(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
--|=(% style="width: 60px;" %)(((
--**Size(bytes)**
--)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 50px;" %)**1**
--|(% 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:108px" %)[[Soil Moisture>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H2.4.6A0SoilTemperature"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H2.4.7A0SoilConductivity28EC29"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]
++=== 2.7.2 US902-928(US915) ===
--(((
--If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
--)))
++Used in USA, Canada and South America. Default use CHE=2
++(% style="color:#037691" %)**Uplink:**
--[[image:image-20220708111918-4.png]]
++903.9 - SF7BW125 to SF10BW125
++904.1 - SF7BW125 to SF10BW125
--The payload is ASCII string, representative same HEX:
++904.3 - SF7BW125 to SF10BW125
--0x72403155615900640c7817075e0a8c02f900 where:
++904.5 - SF7BW125 to SF10BW125
--* Device ID: 0x 724031556159 = 724031556159
--* Version: 0x0064=100=1.0.0
++904.7 - SF7BW125 to SF10BW125
--* BAT: 0x0c78 = 3192 mV = 3.192V
--* Singal: 0x17 = 23
--* Soil Moisture: 0x075e= 1886 = 18.86  %
--* Soil Temperature:0x0a8c =2700=27 °C
--* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
--* Interrupt: 0x00 = 0
++904.9 - SF7BW125 to SF10BW125
++905.1 - SF7BW125 to SF10BW125
++905.3 - SF7BW125 to SF10BW125
--== 2.4  Payload Explanation and Sensor Interface ==
++(% style="color:#037691" %)**Downlink:**
++923.3 - SF7BW500 to SF12BW500
--=== 2.4.1  Device ID ===
++923.9 - SF7BW500 to SF12BW500
--(((
--By default, the Device ID equal to the last 6 bytes of IMEI.
--)))
++924.5 - SF7BW500 to SF12BW500
--(((
--User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
--)))
++925.1 - SF7BW500 to SF12BW500
--(((
--**Example:**
--)))
++925.7 - SF7BW500 to SF12BW500
--(((
--AT+DEUI=A84041F15612
--)))
++926.3 - SF7BW500 to SF12BW500
--(((
--The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
--)))
++926.9 - SF7BW500 to SF12BW500
++927.5 - SF7BW500 to SF12BW500
++923.3 - SF12BW500(RX2 downlink only)
--=== 2.4.2  Version Info ===
--(((
--Specify the software version: 0x64=100, means firmware version 1.00.
--)))
--(((
--For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
--)))
++=== 2.7.3 CN470-510 (CN470) ===
++Used in China, Default use CHE=1
++(% style="color:#037691" %)**Uplink:**
--=== 2.4.3  Battery Info ===
++486.3 - SF7BW125 to SF12BW125
--(((
--Check the battery voltage for LSE01.
--)))
++486.5 - SF7BW125 to SF12BW125
--(((
--Ex1: 0x0B45 = 2885mV
--)))
++486.7 - SF7BW125 to SF12BW125
--(((
--Ex2: 0x0B49 = 2889mV
--)))
++486.9 - SF7BW125 to SF12BW125
++487.1 - SF7BW125 to SF12BW125
++487.3 - SF7BW125 to SF12BW125
--=== 2.4.4  Signal Strength ===
++487.5 - SF7BW125 to SF12BW125
--(((
--NB-IoT Network signal Strength.
--)))
++487.7 - SF7BW125 to SF12BW125
--(((
--**Ex1: 0x1d = 29**
--)))
--(((
--(% style="color:blue" %)**0**(%%)        -113dBm or less
--)))
++(% style="color:#037691" %)**Downlink:**
--(((
--(% style="color:blue" %)**1**(%%)        -111dBm
--)))
++506.7 - SF7BW125 to SF12BW125
--(((
--(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
--)))
++506.9 - SF7BW125 to SF12BW125
--(((
--(% style="color:blue" %)**31**  (%%)    -51dBm or greater
--)))
++507.1 - SF7BW125 to SF12BW125
--(((
--(% style="color:blue" %)**99**   (%%)   Not known or not detectable
--)))
++507.3 - SF7BW125 to SF12BW125
++507.5 - SF7BW125 to SF12BW125
++507.7 - SF7BW125 to SF12BW125
--=== 2.4.5  Soil Moisture ===
++507.9 - SF7BW125 to SF12BW125
--(((
--(((
--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.
--)))
--)))
++508.1 - SF7BW125 to SF12BW125
--(((
--(((
--For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
--)))
--)))
++505.3 - SF12BW125 (RX2 downlink only)
--(((
--
--)))
--(((
--(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
--)))
++=== 2.7.4 AU915-928(AU915) ===
++Default use CHE=2
--=== 2.4.6  Soil Temperature ===
++(% style="color:#037691" %)**Uplink:**
--(((
--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
--)))
++916.8 - SF7BW125 to SF12BW125
--(((
--**Example**:
--)))
++917.0 - SF7BW125 to SF12BW125
--(((
--If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
--)))
++917.2 - SF7BW125 to SF12BW125
--(((
--If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
--)))
++917.4 - SF7BW125 to SF12BW125
++917.6 - SF7BW125 to SF12BW125
++917.8 - SF7BW125 to SF12BW125
--=== 2.4.7  Soil Conductivity (EC) ===
++918.0 - SF7BW125 to SF12BW125
--(((
--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).
--)))
++918.2 - SF7BW125 to SF12BW125
--(((
--For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
--)))
--(((
--Generally, the EC value of irrigation water is less than 800uS / cm.
--)))
++(% style="color:#037691" %)**Downlink:**
--(((
--
--)))
++923.3 - SF7BW500 to SF12BW500
--(((
--
--)))
++923.9 - SF7BW500 to SF12BW500
--=== 2.4.8  Digital Interrupt ===
++924.5 - SF7BW500 to SF12BW500
--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.
++925.1 - SF7BW500 to SF12BW500
--The command is:
++925.7 - SF7BW500 to SF12BW500
--(% 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]])**.**
++926.3 - SF7BW500 to SF12BW500
++926.9 - SF7BW500 to SF12BW500
--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.
++927.5 - SF7BW500 to SF12BW500
++923.3 - SF12BW500(RX2 downlink only)
--Example:
--0x(00): Normal uplink packet.
--0x(01): Interrupt Uplink Packet.
++=== 2.7.5 AS920-923 & AS923-925 (AS923) ===
++(% style="color:#037691" %)**Default Uplink channel:**
++923.2 - SF7BW125 to SF10BW125
--=== 2.4.9  +5V Output ===
++923.4 - SF7BW125 to SF10BW125
--NSE01 will enable +5V output before all sampling and disable the +5v after all sampling.
++(% style="color:#037691" %)**Additional Uplink Channel**:
--The 5V output time can be controlled by AT Command.
++(OTAA mode, channel added by JoinAccept message)
--(% style="color:blue" %)**AT+5VT=1000**
++(% style="color:#037691" %)**AS920~~AS923 for Japan, Malaysia, Singapore**:
--Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
++922.2 - SF7BW125 to SF10BW125
++922.4 - SF7BW125 to SF10BW125
++922.6 - SF7BW125 to SF10BW125
--== 2.5  Downlink Payload ==
++922.8 - SF7BW125 to SF10BW125
--By default, NSE01 prints the downlink payload to console port.
++923.0 - SF7BW125 to SF10BW125
--[[image:image-20220708133731-5.png]]
++922.0 - SF7BW125 to SF10BW125
--(((
--(% style="color:blue" %)**Examples:**
--)))
++(% style="color:#037691" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**:
--(((
--
--)))
++923.6 - SF7BW125 to SF10BW125
--* (((
--(% style="color:blue" %)**Set TDC**
--)))
++923.8 - SF7BW125 to SF10BW125
--(((
--If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
--)))
++924.0 - SF7BW125 to SF10BW125
--(((
--Payload:    01 00 00 1E    TDC=30S
--)))
++924.2 - SF7BW125 to SF10BW125
--(((
--Payload:    01 00 00 3C    TDC=60S
--)))
++924.4 - SF7BW125 to SF10BW125
--(((
--
--)))
++924.6 - SF7BW125 to SF10BW125
--* (((
--(% style="color:blue" %)**Reset**
--)))
--(((
--If payload = 0x04FF, it will reset the NSE01
--)))
++(% style="color:#037691" %)** Downlink:**
++Uplink channels 1-8 (RX1)
--* (% style="color:blue" %)**INTMOD**
++923.2 - SF10BW125 (RX2)
--Downlink Payload: 06000003, Set AT+INTMOD=3
++=== 2.7.6 KR920-923 (KR920) ===
--== 2.6  LED Indicator ==
++Default channel:
--(((
--The NSE01 has an internal LED which is to show the status of different state.
++922.1 - SF7BW125 to SF12BW125
++922.3 - SF7BW125 to SF12BW125
--* 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)
--* Then the LED will be on for 1 second means device is boot normally.
--* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
--* For each uplink probe, LED will be on for 500ms.
--)))
++922.5 - SF7BW125 to SF12BW125
++(% style="color:#037691" %)**Uplink: (OTAA mode, channel added by JoinAccept message)**
++922.1 - SF7BW125 to SF12BW125
--== 2.7  Installation in Soil ==
++922.3 - SF7BW125 to SF12BW125
--__**Measurement the soil surface**__
++922.5 - SF7BW125 to SF12BW125
--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]]
++922.7 - SF7BW125 to SF12BW125
--[[image:1657259653666-883.png]]
++922.9 - SF7BW125 to SF12BW125
++923.1 - SF7BW125 to SF12BW125
--(((
--
++923.3 - SF7BW125 to SF12BW125
--(((
--Dig a hole with diameter > 20CM.
--)))
--(((
--Horizontal insert the probe to the soil and fill the hole for long term measurement.
--)))
--)))
++(% style="color:#037691" %)**Downlink:**
--[[image:1654506665940-119.png]]
++Uplink channels 1-7(RX1)
--(((
--
--)))
++921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
--== 2.8  Firmware Change Log ==
++=== 2.7.7 IN865-867 (IN865) ===
--Download URL & Firmware Change log
++(% style="color:#037691" %)** Uplink:**
--[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
++865.0625 - SF7BW125 to SF12BW125
++865.4025 - SF7BW125 to SF12BW125
--Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
++865.9850 - SF7BW125 to SF12BW125
++(% style="color:#037691" %) **Downlink:**
--== 2.9  Battery Analysis ==
++Uplink channels 1-3 (RX1)
--=== 2.9.1  Battery Type ===
++866.550 - SF10BW125 (RX2)
--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.
--The battery is designed to last for several years depends on the actually use environment and update interval.
++== 2.8 LED Indicator ==
++The LSE01 has an internal LED which is to show the status of different state.
--The battery related documents as below:
++* Blink once when device power on.
++* Solid ON for 5 seconds once device successful Join the network.
++* Blink once when device transmit a packet.
--* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
--* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
--* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
++== 2.9 Installation in Soil ==
++**Measurement the soil surface**
++
++
++[[image:1654506634463-199.png]]
++
  (((
--[[image:image-20220708140453-6.png]]
++(((
++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.
  )))
++)))
--=== 2.9.2  Power consumption Analyze ===
++[[image:1654506665940-119.png]]
  (((
--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.
++Dig a hole with diameter > 20CM.
  )))
++(((
++Horizontal insert the probe to the soil and fill the hole for long term measurement.
++)))
++
++== 2.10 Firmware Change Log ==
++
  (((
--Instruction to use as below:
++**Firmware download link:**
  )))
  (((
--(% 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/]]
++[[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/]]
  )))
++(((
++
++)))
  (((
--(% style="color:blue" %)**Step 2: **(%%) Open it and choose
++**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
  )))
--* (((
--Product Model
++(((
++
  )))
--* (((
--Uplink Interval
++
++(((
++**V1.0.**
  )))
--* (((
--Working Mode
--)))
  (((
--And the Life expectation in difference case will be shown on the right.
++Release
  )))
--[[image:image-20220708141352-7.jpeg]]
++== 2.11 Battery Analysis ==
++=== 2.11.1 Battery Type ===
--=== 2.9.3  Battery Note ===
++(((
++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.
++)))
  (((
--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.
++The battery is designed to last for more than 5 years for the LSN50.
  )))
++(((
++(((
++The battery-related documents are as below:
++)))
++)))
++* (((
++[[Battery Dimension>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
++)))
++* (((
++[[Lithium-Thionyl Chloride Battery  datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
++)))
++* (((
++[[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/]]
++)))
--=== 2.9.4  Replace the battery ===
++ [[image:image-20220610172436-1.png]]
++
++
++=== 2.11.2 Battery Note ===
++
  (((
--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).
++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.
  )))
--= 3.  Access NB-IoT Module =
++=== 2.11.3 Replace the battery ===
  (((
--Users can directly access the AT command set of the NB-IoT module.
++If Battery is lower than 2.7v, user should replace the battery of LSE01.
  )))
  (((
--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/]]
++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.
  )))
--[[image:1657261278785-153.png]]
++(((
++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)
++)))
--= 4.  Using the AT Commands =
++= 3. Using the AT Commands =
--== 4.1  Access AT Commands ==
++== 3.1 Access AT Commands ==
--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/]]
++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.
--AT+<CMD>?                    : Help on <CMD>
++[[image:1654501986557-872.png||height="391" width="800"]]
--AT+<CMD>                      : Run <CMD>
--AT+<CMD>=<value>      : Set the value
++Or if you have below board, use below connection:
--AT+<CMD>=?                  : Get the value
++[[image:1654502005655-729.png||height="503" width="801"]]
++
++
++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:
++
++
++ [[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>>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>
++
++(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD> **(%%)                     : Run <CMD>
++
++(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=<value>**(%%)      : Set the value
++
++(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=?**(%%)                  : Get the value
++
++
  (% style="color:#037691" %)**General Commands**(%%)
--AT                            : Attention
++(% style="background-color:#dcdcdc" %)**AT**(%%)                   : Attention
--AT?                           : Short Help
++(% style="background-color:#dcdcdc" %)**AT?**(%%)                  : Short Help
--ATZ                          : MCU Reset
++(% style="background-color:#dcdcdc" %)**ATZ**(%%)                 : MCU Reset
--AT+TDC                   : Application Data Transmission Interval
++(% style="background-color:#dcdcdc" %)**AT+TDC**(%%)          : Application Data Transmission Interval
--AT+CFG                   : Print all configurations
--AT+CFGMOD           : Working mode selection
++(% style="color:#037691" %)**Keys, IDs and EUIs management**
--AT+INTMOD            : Set the trigger interrupt mode
++(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%)              : Application EUI
--AT+5VT                     : Set extend the time of 5V power
++(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%)              : Application Key
--AT+PRO                    : Choose agreement
++(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%)            : Application Session Key
--AT+WEIGRE              : Get weight or set weight to 0
++(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%)              : Device Address
--AT+WEIGAP              : Get or Set the GapValue of weight
++(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%)                   : Device EUI
--AT+RXDL                   : Extend the sending and receiving time
++(% style="background-color:#dcdcdc" %)**AT+NWKID**(%%)               : Network ID (You can enter this command change only after successful network connection)
--AT+CNTFAC              : Get or set counting parameters
++(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%)          : Network Session Key Joining and sending date on LoRa network
--AT+SERVADDR          : Server Address
++(% style="background-color:#dcdcdc" %)**AT+CFM**(%%)                   : Confirm Mode
++(% style="background-color:#dcdcdc" %)**AT+CFS**(%%)                     : Confirm Status
--(% style="color:#037691" %)**COAP Management**
++(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%)                   : Join LoRa? Network
--AT+URI            : Resource parameters
++(% style="background-color:#dcdcdc" %)**AT+NJM**(%%)                    : LoRa? Network Join Mode
++(% style="background-color:#dcdcdc" %)**AT+NJS**(%%)                     : LoRa? Network Join Status
--(% style="color:#037691" %)**UDP Management**
++(% style="background-color:#dcdcdc" %)**AT+RECV**(%%)                  : Print Last Received Data in Raw Format
--AT+CFM          : Upload confirmation mode (only valid for UDP)
++(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%)                : Print Last Received Data in Binary Format
++(% style="background-color:#dcdcdc" %)**AT+SEND**(%%)                  : Send Text Data
--(% style="color:#037691" %)**MQTT Management**
++(% style="background-color:#dcdcdc" %)**AT+SENB**(%%)                  : Send Hexadecimal Data
--AT+CLIENT               : Get or Set MQTT client
--AT+UNAME             : Get or Set MQTT Username
++(% style="color:#037691" %)**LoRa Network Management**
--AT+PWD                  : Get or Set MQTT password
++(% style="background-color:#dcdcdc" %)**AT+ADR**(%%)          : Adaptive Rate
--AT+PUBTOPIC          : Get or Set MQTT publish topic
++(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%)      : LoRa Class(Currently only support class A
--AT+SUBTOPIC          : Get or Set MQTT subscription topic
++(% style="background-color:#dcdcdc" %)**AT+DCS**(%%)          : Duty Cycle Setting
++(% style="background-color:#dcdcdc" %)**AT+DR**(%%)            : Data Rate (Can Only be Modified after ADR=0)
--(% style="color:#037691" %)**Information**
++(% style="background-color:#dcdcdc" %)**AT+FCD**(%%)          : Frame Counter Downlink
--AT+FDR              : Factory Data Reset
++(% style="background-color:#dcdcdc" %)**AT+FCU**(%%)          : Frame Counter Uplink
--AT+PWORD       : Serial Access Password
++(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%)      : Join Accept Delay1
++(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%)      : Join Accept Delay2
++(% style="background-color:#dcdcdc" %)**AT+PNM**(%%)        : Public Network Mode
--= 5.  FAQ =
++(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%)     : Receive Delay1
--== 5.1  How to Upgrade Firmware ==
++(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%)     : Receive Delay2
++(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%)     : Rx2 Window Data Rate
++(% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%)     : Rx2 Window Frequency
++
++(% style="background-color:#dcdcdc" %)**AT+TXP**(%%)          : Transmit Power
++
++(% style="background-color:#dcdcdc" %)**AT+ MOD**(%%)       : Set work mode
++
++
++(% style="color:#037691" %)**Information**
++
++(% style="background-color:#dcdcdc" %)**AT+RSSI**(%%)           : RSSI of the Last Received Packet
++
++(% style="background-color:#dcdcdc" %)**AT+SNR**(%%)           : SNR of the Last Received Packet
++
++(% style="background-color:#dcdcdc" %)**AT+VER**(%%)           : Image Version and Frequency Band
++
++(% style="background-color:#dcdcdc" %)**AT+FDR**(%%)           : Factory Data Reset
++
++(% style="background-color:#dcdcdc" %)**AT+PORT**(%%)        : Application Port
++
++(% style="background-color:#dcdcdc" %)**AT+CHS**(%%)          : Get or Set Frequency (Unit: Hz) for Single Channel Mode
++
++ (% style="background-color:#dcdcdc" %)**AT+CHE**(%%)         : Get or Set eight channels mode, Only for US915, AU915, CN470
++
++
++= 4. FAQ =
++
++== 4.1 How to change the LoRa Frequency Bands/Region? ==
++
  (((
--User can upgrade the firmware for 1) bug fix, 2) new feature release.
++You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]].
++When downloading the images, choose the required image file for download.
  )))
  (((
--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]]
++
  )))
  (((
--(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
++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.
  )))
++(((
++
++)))
++(((
++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.
++)))
--= 6.  Trouble Shooting =
++(((
++
++)))
--== 6.1  Connection problem when uploading firmware ==
++(((
++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.
++)))
++[[image:image-20220606154726-3.png]]
--(% class="wikigeneratedid" %)
++
++When you use the TTN network, the US915 frequency bands use are:
++
++* 903.9 - SF7BW125 to SF10BW125
++* 904.1 - SF7BW125 to SF10BW125
++* 904.3 - SF7BW125 to SF10BW125
++* 904.5 - SF7BW125 to SF10BW125
++* 904.7 - SF7BW125 to SF10BW125
++* 904.9 - SF7BW125 to SF10BW125
++* 905.1 - SF7BW125 to SF10BW125
++* 905.3 - SF7BW125 to SF10BW125
++* 904.6 - SF8BW500
++
  (((
--(% style="font-size:14px" %)**Please see: **(%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting||style="background-color: rgb(255, 255, 255); font-size: 14px;"]]
++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:
++
++* (% style="color:#037691" %)**AT+CHE=2**
++* (% style="color:#037691" %)**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.
++)))
--== 6.2  AT Command input doesn't work ==
++(((
++
++)))
  (((
++The **AU915** band is similar. Below are the AU915 Uplink Channels.
++)))
++
++[[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? ==
++
++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 ==
++
++(((
  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.
  )))
++== 5.3 Device rejoin in at the second uplink packet ==
--= 7.  Order Info =
++(% style="color:#4f81bd" %)**Issue describe as below:**
++[[image:1654500909990-784.png]]
--Part Number**:** (% style="color:#4f81bd" %)**NSE01**
++(% style="color:#4f81bd" %)**Cause for this issue:**
++(((
++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.
++)))
++
++
++(% style="color:#4f81bd" %)**Solution: **
++
++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:
++
++[[image:1654500929571-736.png||height="458" width="832"]]
++
++
++= 6. Order Info =
++
++
++Part Number**:** (% style="color:#4f81bd" %)**LSE01-XX-YY**
++
++
++(% style="color:#4f81bd" %)**XX**(%%)**:** The default frequency band
++
++* (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band
++* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
++* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
++* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
++* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
++* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
++* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
++* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
++
++(% style="color:#4f81bd" %)**YY**(%%)**: **Battery Option
++
++* (% style="color:red" %)**4**(%%): 4000mAh battery
++* (% style="color:red" %)**8**(%%): 8500mAh battery
++
  (% class="wikigeneratedid" %)
  (((
  )))
--= 8.  Packing Info =
++= 7. Packing Info =
  (((
  (% style="color:#037691" %)**Package Includes**:
++)))
--
--* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
--* External antenna x 1
++* (((
++LSE01 LoRaWAN Soil Moisture & EC Sensor x 1
  )))
  (((
@@ -861,20 +861,24 @@
  (% style="color:#037691" %)**Dimension and weight**:
++)))
--
--* Size: 195 x 125 x 55 mm
--* Weight:   420g
++* (((
++Device Size: cm
  )))
++* (((
++Device Weight: g
++)))
++* (((
++Package Size / pcs : cm
++)))
++* (((
++Weight / pcs : g
--(((
--
--
--
  )))
--= 9.  Support =
++= 8. Support =
  * 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.
  * 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]]

1657249419225-449.png

Author

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

Size

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

Content

1657249468462-536.png

Author

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

Size

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

Content

1657249793983-486.png

Author

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

Size

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

Content

1657249831934-534.png

Author

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

Size

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

Content

1657249864775-321.png

Author

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

Size

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

Content

1657249930215-289.png

Author

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

Size

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

Content

1657249978444-674.png

Author

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

Size

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

Content

1657249990869-686.png

Author

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

Size

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

Content

1657250217799-140.png

Author

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

Size

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

Content

1657250255956-604.png

Author

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

Size

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

Content

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

image-20220708101605-2.png

Author

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

Size

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

Content

image-20220708110657-3.png

Author

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

Size

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

Content

image-20220708111918-4.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-38.8 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

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

Summary

Details

Applications

Navigation