Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual

Last modified by Mengting Qiu on 2024/04/02 16:44

From version < 27.1 >

edited by Xiaoling
on 2022/06/06 16:58

To version < 6.2 >

edited by Xiaoling
on 2022/06/06 15:36

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, 21 removed)

Details

Page properties

Content

@@ -1,6 +1,7 @@
  (% style="text-align:center" %)
  [[image:image-20220606151504-2.jpeg||height="848" width="848"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
@@ -8,40 +8,44 @@
--= 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.
--)))
--(((
--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.
--)))
--(((
++
++
++
++
++
++
++
++1. Introduction
++11. What is LoRaWAN Soil Moisture & EC Sensor
++
++The Dragino LSE01 is a **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.
++
++
++It detects **Soil Moisture**, **Soil Temperature** and **Soil Conductivity**, and uploads the value via wireless to LoRaWAN IoT Server.
++
++
  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.
--)))
--(((
--LES01 is powered by (% style="color:#4f81bd" %)**4000mA or 8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 10 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.
--)))
++LES01 is powered by **4000mA or 8500mAh Li-SOCI2 battery**, It is designed for long term use up to 10 years.
--[[image:1654503236291-817.png]]
++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:1654503265560-120.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]]
--== 1.2 Features ==
++
++*
++*1. Features
  * LoRaWAN 1.0.3 Class A
  * Ultra low power consumption
  * Monitor Soil Moisture
@@ -54,48 +54,63 @@
  * IP66 Waterproof Enclosure
  * 4000mAh or 8500mAh Battery for long term use
--== 1.3 Specification ==
++1.
++11. Specification
  Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
--[[image:image-20220606162220-5.png]]
++|**Parameter**|**Soil Moisture**|**Soil Conductivity**|**Soil Temperature**
++|**Range**|**0-100.00%**|(((
++**0-20000uS/cm**
++**(25℃)(0-20.0EC)**
++)))|**-40.00℃～85.00℃**
++|**Unit**|**V/V %,**|**uS/cm,**|**℃**
++|**Resolution**|**0.01%**|**1 uS/cm**|**0.01℃**
++|**Accuracy**|(((
++**±3% (0-53%)**
++**±5% (>53%)**
++)))|**2%FS,**|(((
++**-10℃～50℃:<0.3℃**
--== 1.4 Applications ==
++**All other: <0.6℃**
++)))
++|(((
++**Measure**
++**Method**
++)))|**FDR , with temperature &EC compensate**|**Conductivity , with temperature compensate**|**RTD, and calibrate**
++
++*
++*1. Applications
  * Smart Agriculture
--(% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
--
++1.
++11. Firmware Change log
--== 1.5 Firmware Change log ==
++**LSE01 v1.0:**
++* Release
--**LSE01 v1.0 :**  Release
++1. Configure LSE01 to connect to LoRaWAN network
++11.  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
--= 2. Configure LSE01 to connect to LoRaWAN network =
++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 >>path:#_Using_the_AT]]to set the keys in the LSE01.
--== 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
--)))
--(((
--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.UsingtheATCommands"]].
--)))
++1.
++11. Quick guide to connect to LoRaWAN server (OTAA)
--
--== 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]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.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.
@@ -105,40 +105,56 @@
  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]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]]
  **Add APP KEY and DEV EUI**
--[[image:1654504683289-357.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]]
++|(((
++
++)))
++
  **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]]
++|(((
++
++)))
++
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]]
++
++
++
++
++
  **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]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
--== 2.3 Uplink Payload ==
--=== 2.3.1 MOD~=0(Default Mode) ===
++1.
++11. Uplink Payload
++111. MOD=0(Default Mode)
  LSE01 will uplink payload via LoRaWAN with below payload format:
@@ -161,12 +161,13 @@
  (Optional)
  )))
--[[image:1654504881641-514.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
++1.
++11.
++111. MOD=1(Original value)
--=== 2.3.2 MOD~=1(Original value) ===
--
  This mode can get the original AD value of moisture and original conductivity (with temperature drift compensation).
  |(((
@@ -184,12 +184,12 @@
  (Optional)
  )))
--[[image:1654504907647-967.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]
++1.
++11.
++111. Battery Info
--
--=== 2.3.3 Battery Info ===
--
  Check the battery voltage for LSE01.
  Ex1: 0x0B45 = 2885mV
@@ -198,19 +198,21 @@
--=== 2.3.4 Soil Moisture ===
++1.
++11.
++111. 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.
--For example, if the data you get from the register is __0x05 0xDC__, the moisture content in the soil is
++For example, if the data you get from the register is 0x05 0xDC, the moisture content in the soil is
++**05DC(H) = 1500(D) /100 = 15%.**
--(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
++1.
++11.
++111. Soil Temperature
--
--=== 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
  **Example**:
@@ -220,31 +220,21 @@
  If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
++1.
++11.
++111. Soil Conductivity (EC)
--=== 2.3.6 Soil Conductivity (EC) ===
++Obtain soluble salt concentration in soil or soluble ion concentration in liquid fertilizer or planting medium,. The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000).
--(((
--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).
--)))
--
--(((
  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.
--)))
--(((
--
--)))
++1.
++11.
++111. MOD
--(((
--
--)))
--
--=== 2.3.7 MOD ===
--
  Firmware version at least v2.1 supports changing mode.
  For example, bytes[10]=90
@@ -259,13 +259,14 @@
  If** **payload =** **0x0A01,  workmode=1
++1.
++11.
++111. Decode payload in The Things Network
--=== 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]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]
  The payload decoder function for TTN is here:
@@ -272,26 +272,30 @@
  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/]]
--== 2.4 Uplink Interval ==
++1.
++11. 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:
  [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands#Change_Uplink_Interval>>url:http://wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands#Change_Uplink_Interval]]
++1.
++11. Downlink Payload
--
--== 2.5 Downlink Payload ==
--
  By default, LSE50 prints the downlink payload to console port.
--[[image:image-20220606165544-8.png]]
++|**Downlink Control Type**|**FPort**|**Type Code**|**Downlink payload size(bytes)**
++|TDC (Transmit Time Interval)|Any|01|4
++|RESET|Any|04|2
++|AT+CFM|Any|05|4
++|INTMOD|Any|06|4
++|MOD|Any|0A|2
++**Examples**
--**Examples:**
++**Set TDC**
--* **Set TDC**
--
  If the payload=0100003C, it means set the END Node’s TDC to 0x00003C=60(S), while type code is 01.
  Payload:    01 00 00 1E    TDC=30S
@@ -299,19 +299,18 @@
  Payload:    01 00 00 3C    TDC=60S
--* **Reset**
++**Reset**
  If payload = 0x04FF, it will reset the LSE01
--* **CFM**
++**CFM**
  Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0
++1.
++11. Show Data in DataCake IoT Server
--
--== 2.6 Show Data in DataCake IoT Server ==
--
  [[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:
@@ -320,10 +320,10 @@
  **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:1654505857935-743.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
--[[image:1654505874829-548.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
@@ -350,8 +350,8 @@
  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.
--1.
--11.
++1.
++11.
 . EU863-870 (EU868)
  Uplink:
@@ -382,8 +382,8 @@
 .525 - SF9BW125 (RX2 downlink only)
--1.
--11.
++1.
++11.
 . US902-928(US915)
  Used in USA, Canada and South America. Default use CHE=2
@@ -428,8 +428,8 @@
 .3 - SF12BW500(RX2 downlink only)
--1.
--11.
++1.
++11.
 . CN470-510 (CN470)
  Used in China, Default use CHE=1
@@ -474,8 +474,8 @@
 .3 - SF12BW125 (RX2 downlink only)
--1.
--11.
++1.
++11.
 . AU915-928(AU915)
  Default use CHE=2
@@ -519,8 +519,8 @@
 .3 - SF12BW500(RX2 downlink only)
--1.
--11.
++1.
++11.
 . AS920-923 & AS923-925 (AS923)
  **Default Uplink channel:**
@@ -572,8 +572,8 @@
 .2 - SF10BW125 (RX2)
--1.
--11.
++1.
++11.
 . KR920-923 (KR920)
  Default channel:
@@ -609,8 +609,8 @@
 .9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
--1.
--11.
++1.
++11.
 . IN865-867 (IN865)
  Uplink:
@@ -629,7 +629,7 @@
 .550 - SF10BW125 (RX2)
--1.
++1.
 . LED Indicator
  The LSE01 has an internal LED which is to show the status of different state.
@@ -639,7 +639,7 @@
  * Solid ON for 5 seconds once device successful Join the network.
  * Blink once when device transmit a packet.
--1.
++1.
 . Installation in Soil
  **Measurement the soil surface**
@@ -666,7 +666,7 @@
--1.
++1.
 . Firmware Change Log
  **Firmware download link:**
@@ -685,7 +685,7 @@
--1.
++1.
 . Battery Analysis
 . Battery Type
@@ -709,15 +709,15 @@
--1.
--11.
++1.
++11.
 . Battery Note
  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.
--1.
--11.
++1.
++11.
 . Replace the battery
  If Battery is lower than 2.7v, user should replace the battery of LSE01.
@@ -733,155 +733,173 @@
--= 3. Using the AT Commands =
++1. Using the AT Commands
++11. Access AT Commands
--== 3.1 Access AT Commands ==
--
--
  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.
--[[image:1654501986557-872.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
  Or if you have below board, use below connection:
--[[image:1654502005655-729.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
--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:
++In the PC, you need to set the serial baud rate to **9600** to access the serial console for LSE01. LSE01 will output system info once power on as below:
-- [[image:1654502050864-459.png]]
++ [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
  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/]]
--(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%)                   : Help on <CMD>
++AT+<CMD>?           : Help on <CMD>
--(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD> **(%%)                     : Run <CMD>
++AT+<CMD>                      : Run <CMD>
--(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=<value>**(%%)      : Set the value
++AT+<CMD>=<value>      : Set the value
--(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=?**(%%)                  : Get the value
++AT+<CMD>=?          : Get the value
--(% style="color:#037691" %)**General Commands**(%%)
++**General Commands**
--(% style="background-color:#dcdcdc" %)**AT**(%%)                   : Attention
++AT                    : Attention
--(% style="background-color:#dcdcdc" %)**AT?**(%%)                  : Short Help
++AT?                            : Short Help
--(% style="background-color:#dcdcdc" %)**ATZ**(%%)                 : MCU Reset
++ATZ                            : MCU Reset
--(% style="background-color:#dcdcdc" %)**AT+TDC**(%%)          : Application Data Transmission Interval
++AT+TDC           : Application Data Transmission Interval
--(% style="color:#037691" %)**Keys, IDs and EUIs management**
++**Keys, IDs and EUIs management**
--(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%)              : Application EUI
++AT+APPEUI              : Application EUI
--(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%)              : Application Key
++AT+APPKEY              : Application Key
--(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%)            : Application Session Key
++AT+APPSKEY            : Application Session Key
--(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%)              : Device Address
++AT+DADDR              : Device Address
--(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%)                   : Device EUI
++AT+DEUI                   : Device EUI
--(% style="background-color:#dcdcdc" %)**AT+NWKID**(%%)               : Network ID (You can enter this command change only after successful network connection)
++AT+NWKID               : Network ID (You can enter this command change only after                                         successful network connection)
--(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%)          : Network Session Key Joining and sending date on LoRa network
++AT+NWKSKEY          : Network Session Key Joining and sending date on LoRa network
--(% style="background-color:#dcdcdc" %)**AT+CFM**(%%)                   : Confirm Mode
++AT+CFM          : Confirm Mode
--(% style="background-color:#dcdcdc" %)**AT+CFS**(%%)                     : Confirm Status
++AT+CFS                     : Confirm Status
--(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%)                   : Join LoRa? Network
++AT+JOIN          : Join LoRa? Network
--(% style="background-color:#dcdcdc" %)**AT+NJM**(%%)                    : LoRa? Network Join Mode
++AT+NJM          : LoRa? Network Join Mode
--(% style="background-color:#dcdcdc" %)**AT+NJS**(%%)                     : LoRa? Network Join Status
++AT+NJS                     : LoRa? Network Join Status
--(% style="background-color:#dcdcdc" %)**AT+RECV**(%%)                  : Print Last Received Data in Raw Format
++AT+RECV                  : Print Last Received Data in Raw Format
--(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%)                : Print Last Received Data in Binary Format
++AT+RECVB                : Print Last Received Data in Binary Format
--(% style="background-color:#dcdcdc" %)**AT+SEND**(%%)                  : Send Text Data
++AT+SEND                  : Send Text Data
--(% style="background-color:#dcdcdc" %)**AT+SENB**(%%)                  : Send Hexadecimal Data
++AT+SENB                  : Send Hexadecimal Data
--(% style="color:#037691" %)**LoRa Network Management**
++**LoRa Network Management**
--(% style="background-color:#dcdcdc" %)**AT+ADR**(%%)          : Adaptive Rate
++AT+ADR          : Adaptive Rate
--(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%)      : LoRa Class(Currently only support class A
++AT+CLASS                : LoRa Class(Currently only support class A
--(% style="background-color:#dcdcdc" %)**AT+DCS**(%%)          : Duty Cycle Setting
++AT+DCS           : Duty Cycle Setting
--(% style="background-color:#dcdcdc" %)**AT+DR**(%%)            : Data Rate (Can Only be Modified after ADR=0)
++AT+DR                      : Data Rate (Can Only be Modified after ADR=0)
--(% style="background-color:#dcdcdc" %)**AT+FCD**(%%)          : Frame Counter Downlink
++AT+FCD           : Frame Counter Downlink
--(% style="background-color:#dcdcdc" %)**AT+FCU**(%%)          : Frame Counter Uplink
++AT+FCU           : Frame Counter Uplink
--(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%)      : Join Accept Delay1
++AT+JN1DL                : Join Accept Delay1
--(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%)      : Join Accept Delay2
++AT+JN2DL                : Join Accept Delay2
--(% style="background-color:#dcdcdc" %)**AT+PNM**(%%)        : Public Network Mode
++AT+PNM                   : Public Network Mode
--(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%)     : Receive Delay1
++AT+RX1DL                : Receive Delay1
--(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%)     : Receive Delay2
++AT+RX2DL                : Receive Delay2
--(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%)     : Rx2 Window Data Rate
++AT+RX2DR               : Rx2 Window Data Rate
--(% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%)     : Rx2 Window Frequency
++AT+RX2FQ               : Rx2 Window Frequency
--(% style="background-color:#dcdcdc" %)**AT+TXP**(%%)          : Transmit Power
++AT+TXP           : Transmit Power
--(% style="background-color:#dcdcdc" %)**AT+ MOD**(%%)       : Set work mode
++AT+ MOD                 : Set work mode
--(% style="color:#037691" %)**Information**
++**Information**
--(% style="background-color:#dcdcdc" %)**AT+RSSI**(%%)           : RSSI of the Last Received Packet
++AT+RSSI           : RSSI of the Last Received Packet
--(% style="background-color:#dcdcdc" %)**AT+SNR**(%%)           : SNR of the Last Received Packet
++AT+SNR           : SNR of the Last Received Packet
--(% style="background-color:#dcdcdc" %)**AT+VER**(%%)           : Image Version and Frequency Band
++AT+VER           : Image Version and Frequency Band
--(% style="background-color:#dcdcdc" %)**AT+FDR**(%%)           : Factory Data Reset
++AT+FDR           : Factory Data Reset
--(% style="background-color:#dcdcdc" %)**AT+PORT**(%%)        : Application Port
++AT+PORT                  : Application Port
--(% style="background-color:#dcdcdc" %)**AT+CHS**(%%)          : Get or Set Frequency (Unit: Hz) for Single Channel Mode
++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
++ 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? ==
++
++
++
++1. FAQ
++11. How to change the LoRa Frequency Bands/Region?
++
  You can follow the instructions for [[how to upgrade image>>path:#3ygebqi]].
  When downloading the images, choose the required image file for download.
--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.
++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.
++
  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]]
++|CHE|(% colspan="9" %)US915 Uplink Channels(125KHz,4/5,Unit:MHz,CHS=0)
++|0|(% colspan="9" %)ENABLE Channel 0-63
++|1|902.3|902.5|902.7|902.9|903.1|903.3|903.5|903.7|Channel 0-7
++|2|903.9|904.1|904.3|904.5|904.7|904.9|905.1|905.3|Channel 8-15
++|3|905.5|905.7|905.9|906.1|906.3|906.5|906.7|906.9|Channel 16-23
++|4|907.1|907.3|907.5|907.7|907.9|908.1|908.3|908.5|Channel 24-31
++|5|908.7|908.9|909.1|909.3|909.5|909.7|909.9|910.1|Channel 32-39
++|6|910.3|910.5|910.7|910.9|911.1|911.3|911.5|911.7|Channel 40-47
++|7|911.9|912.1|912.3|912.5|912.7|912.9|913.1|913.3|Channel 48-55
++|8|913.5|913.7|913.9|914.1|914.3|914.5|914.7|914.9|Channel 56-63
++|(% colspan="10" %)Channels(500KHz,4/5,Unit:MHz,CHS=0)
++| |903|904.6|906.2|907.8|909.4|911|912.6|914.2|Channel 64-71
++
  When you use the TTN network, the US915 frequency bands use are:
  * 903.9 - SF7BW125 to SF10BW125
@@ -896,15 +896,9 @@
  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**
--)))
--(% 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.
@@ -911,12 +911,25 @@
  The **AU915** band is similar. Below are the AU915 Uplink Channels.
--[[image:image-20220606154825-4.png]]
++|CHE|(% colspan="9" %)AU915 Uplink Channels(125KHz,4/5,Unit:MHz,CHS=0)
++|0|(% colspan="9" %)ENABLE Channel 0-63
++|1|915.2|915.4|915.6|915.8|916|916.2|916.4|916.6|Channel 0-7
++|2|916.8|917|917.2|917.4|917.6|917.8|918|918.2|Channel 8-15
++|3|918.4|918.6|918.8|919|919.2|919.4|919.6|919.8|Channel 16-23
++|4|920|920.2|920.4|920.6|920.8|921|921.2|921.4|Channel 24-31
++|5|921.6|921.8|922|922.2|922.4|922.6|922.8|923|Channel 32-39
++|6|923.2|923.4|923.6|923.8|924|924.2|924.4|924.6|Channel 40-47
++|7|924.8|925|925.2|925.4|925.6|925.8|926|926.2|Channel 48-55
++|8|926.4|926.6|926.8|927|927.2|927.4|927.6|927.8|Channel 56-63
++|(% colspan="10" %)Channels(500KHz,4/5,Unit:MHz,CHS=0)
++| |915.9|917.5|919.1|920.7|922.3|923.9|925.5|927.1|Channel 64-71
++
  = 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.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]] section above for details.
@@ -1004,3 +1004,4 @@
  * 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]]
++

1654501986557-872.png

Author

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

Size

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

Content

1654502005655-729.png

Author

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

Size

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

Content

1654502050864-459.png

Author

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

Size

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

Content

1654503236291-817.png

Author

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

Size

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

Content

1654503265560-120.png

Author

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

Size

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

Content

1654503992078-669.png

Author

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

Size

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

Content

1654504596150-405.png

Author

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

Size

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

Content

1654504683289-357.png

Author

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

Size

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

Content

1654504778294-788.png

Author

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

Size

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

Content

1654504881641-514.png

Author

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

Size

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

Content

1654504907647-967.png

Author

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

Size

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

Content

1654505570700-128.png

Author

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

Size

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

Content

1654505857935-743.png

Author

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

Size

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

Content

1654505874829-548.png

Author

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

Size

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

Content

1654505905236-553.png

Author

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

Size

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

Content

image-20220606154726-3.png

Author

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

Size

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

Content

image-20220606154825-4.png

Author

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

Size

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

Content

image-20220606162220-5.png

Author

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

Size

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

Content

image-20220606163732-6.jpeg

Author

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

Size

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

Content

image-20220606163915-7.png

Author

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

Size

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

Content

image-20220606165544-8.png

Author

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

Size

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

Content

Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual

Summary

Details

Applications

Navigation