Changes for page Notes for Helium

Last modified by Edwin Chen on 2024/03/25 08:22

From version < 99.4 >

edited by Xiaoling
on 2023/04/21 16:42

To version < 82.1 >

edited by Kilight Cao
on 2022/06/15 15:31

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Author

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

Content

@@ -1,4 +1,4 @@
--**~     Table of Contents:**
++**~     Contents:**
  {{toc/}}
@@ -5,18 +5,17 @@
--= 1.  Use Dragino Gateways/Hotspots with Helium =
++= **1. Use Dragino Gateways/Hotspots with Helium** =
--== 1.1  Support Models ==
++== **1.1 Support Models** ==
++//There are three types of hotspots that can connect to Helium. They are (% style="color:#4f81bd" %)**full-hotspot**(%%), (% style="color:#4f81bd" %)**light hotspot** (%%)and (% style="color:#4f81bd" %)**data-only hotspot**(%%). Definition of these three types of hotspots can be found here: [[of Helium Hotspots>>url:https://docs.helium.com/mine-hnt%7CTypes]]. Different hotspots support different mining abilities.//
--There are three types of hotspots that can connect to Helium. They are (% style="color:#4f81bd" %)**full-hotspot**(%%), (% style="color:#4f81bd" %)**light hotspot** (%%)and (% style="color:#4f81bd" %)**data-only hotspot**(%%). Definition of these three types of hotspots can be found here: [[of Helium Hotspots>>url:https://docs.helium.com/mine-hnt%7CTypes]]. Different hotspots support different mining abilities.
--
  (((
--Dragino has different gateway models that support different types.
++//Dragino has different gateway models that support different types.//
  )))
--(% border="1" style="background-color:#f2f2f2; width:510px" %)
++(% border="1" style="background-color:#ffffcc; width:510px" %)
  |(% colspan="4" style="width:589px" %)(% style="color:green" %)**Dragino Hotspots for Helium**
  |(% style="color:green; width:132px" %)**Model**|(% style="color:green; width:126px" %)**Hotspot Types**|(% style="color:green; width:121px" %)**Mining Ability**|(% style="color:green; width:203px" %)**Configure Instruction**
  |(% style="width:132px" %)(((
@@ -23,10 +23,10 @@
  [[LPS8>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]], [[DLOS8>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]],
  [[LG308>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]],[[LIG16>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]]
--)))|(% style="color:#4f81bd; width:126px" %)**Data-Only Hotspot**|(% style="width:121px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]]|(% style="width:203px" %)[[Data-Only Hotspot Instruction>>||anchor="H2.A0ConnectData-OnlyHotspottoHelium"]]
++)))|(% style="color:#4f81bd; width:126px" %)**Data-Only Hotspot**|(% style="width:121px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]]|(% style="width:203px" %)[[Data-Only Hotspot Instruction>>||anchor="H2.ConnectData-OnlyHotspottoHelium"]]
  |(% style="width:132px" %)[[HP0D>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/195-hp0d.html]]|(% style="color:#4f81bd; width:126px" %)**Full Hotspo**t|(% style="width:121px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/full-hotspots]]|(% style="color:green; width:203px" %)[[Full Hotspot Instuction-Not Finish>>doc:Main.User Manual for All Gateway models.HP0D.WebHome]]
--(% style="color:blue" %)**Frequencies on the Helium Network**
++**Frequencies on the Helium Network**
  * //The frequencies currently available are CN470/EU868/US915/AU915//
@@ -33,33 +33,31 @@
  (% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]**
--= 2.  Connect Data-Only Hotspot to Helium =
++= **2. Connect Data-Only Hotspot to Helium** =
--== 2.1  Prerequisites ==
++== **2.1 Prerequisites** ==
  * //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
++== **2.2 Step 1: Configure Frequency Band** ==
--== 2.2  Step 1: Configure Frequency Band ==
--
  //Each country has a requirement for frequency region. Choose the right one for your area.//
  [[image:image-20220531175337-1.png]]
--== 2.3  Step 2: Download the Helium-gateway-rs ==
++== **2.3 Step 2: Download the Helium-gateway-rs** ==
  //Click Download Helium Server and the gateway will download the Helium-gateway-rs//
--
  [[image:image-20220615150600-1.png||height="559" width="1045"]]
--
  //**Start download to Helium-gateway-rs**//
++
  [[image:image-20220615150627-2.png||height="598" width="1044"]]
  //**Helium-gatewayrs download success**//
@@ -70,7 +70,7 @@
  [[image:image-20220615150717-3.png||height="605" width="1039"]]
--== 2.4  Step 3: Install the Helium-gateway-rs ==
++== **2.4 Step 3: Install the Helium-gateway-rs** ==
  //Click **Install Helium Server** to install gateway-rs.//
@@ -79,26 +79,23 @@
  Install the Helium gateway-rs
--
  (% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
--== 2.5  Step 4: Save&start the Helium Server ==
++== **2.5 Step 4: Save&start the Helium Server** ==
  //By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
--
  [[image:image-20220615150903-5.png||height="592" width="1031"]]
++//Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.//
--//Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.//
--
  [[image:image-20220615151057-6.png||height="580" width="1026"]]
--== 2.6  Step 5: Check Gateway Connection before onboarding ==
++== **2.6 Step 5: Check Gateway Connection before onboarding** ==
  //A hotspot can transfer data to Helium after finishing step4. We can add a device to Helium and see if the device can join Helium. For example, we add an LGT92 sensor and see below info.//
@@ -113,12 +113,10 @@
  (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
--== 2.7  Step 6: Onboarding Data-Only Hotspot ==
++== 2.7 Step 6: Onboarding Data-Only Hotspot ==
++(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is not necessary, and it will gain very, very small awards on HNT by data-transfer .**
--(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**
--
--
  //User can refer [[this link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]] for how to onboarding a data-only hotspot. After onboarding the data-only hotspot, user can see the hotspot on Helium Console.//
  //Below are the steps we do as per above link here.//
@@ -125,7 +125,7 @@
  (((
--(% style="color:blue" %)//**1. Set up Helium-Wallet in my computer. [[https:~~/~~/docs.helium.com/wallets/cli-wallet>>url:https://docs.helium.com/wallets/cli-wallet]]. and funds this wallet. From this step, we got the wallet info as below.**//
++**~1. Set up Helium-Wallet in my computer. [[https:~~/~~/docs.helium.com/wallets/cli-wallet>>url:https://docs.helium.com/wallets/cli-wallet]]. and funds this wallet. From this step, we got the wallet info as below.**
  )))
  (% class="box" %)
@@ -152,15 +152,13 @@
  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
  )))
--
  (((
  (% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.**
  )))
--
  (((
--(% style="color:blue" %)//**2. Get txn. In the data-only hotspot. run below command to add a hotspot, owner is the owner wallet of this hotspot, payer is the payer to pay transaction cost.**//
++**2. Get txn. In the data-only hotspot. run below command to add a hotspot, owner is the owner wallet of this hotspot, payer is the payer to pay transaction cost.**
  )))
  (% class="box" %)
@@ -192,17 +192,13 @@
  )))
  (((
--//We got the txn info from this step.//
++We got the txn info from this step.
++\\**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**
++(% style="color:red" %)Note: below are two commands, the command without ~-~-commit is the preview mode.**
--(% style="color:blue" %)//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**//
--
--
--(% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.**
--
--
--//Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.//
++Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.
  )))
  (% class="box" %)
@@ -245,9 +245,7 @@
  )))
  (((
--
--
--(% style="color:blue" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//
++4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.
  )))
  (% class="box" %)
@@ -301,26 +301,24 @@
  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
  )))
--
  (((
--(% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.**
++Note: The add hotspot and assert location step might need some time to be effect.
  )))
  (((
--//After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//
++After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.
  )))
--== 2.8  Debug Connection ==
++== 2.8 Debug Connection ==
--=== 2.8.1  Check pkt-fwd running Log ===
++=== 2.8.1 Check pkt-fwd running Log ===
++This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.
--//This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
--
  (((
--//Below logs shows the gateway receive two LoRaWAN packets.//
++Below logs shows the gateway receive two LoRaWAN packets.
  )))
  (% class="box" %)
@@ -345,20 +345,19 @@
  )))
--=== 2.8.2  Check gateway-rs Log ===
++=== 2.8.2 Check gateway-rs Log ===
++SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.
--//SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
--
  [[image:image-20220531175809-7.png]]
++Helium-gatewayrs log
--(% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
++**Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.
--=== 2.8.3  View the public key address and animal name ===
++=== 2.8.3 View the public key address and animal name ===
--
  (% class="box" %)
  (((
  (((
@@ -380,102 +380,80 @@
  Hostpot key and animal name
--=== 2.8.4  Backup/Restor gateway-rs key ===
++=== 2.8.4 Backup/Restor gateway-rs key ===
--
  (((
--//For the date-only hotspots, the key is the only unique identifier, the users can backup the key by the button of Download. And once the uses upgrade the gateway or the gateway lose the key, the gateway-rs will generate a new key for which the data-only hotspot is the new unit. so if the user would restore to last time which can upload your backup key to the gateway by the button of upload.//
++For the date-only hotspots, the key is the only unique identifier, the users can backup the key by the button of Download. And once the uses upgrade the gateway or the gateway lose the key, the gateway-rs will generate a new key for which the data-only hotspot is the new unit. so if the user would restore to last time which can upload your backup key to the gateway by the button of upload.
  )))
  [[image:image-20220531175919-9.png]]
++Backup and restore key
--=== 2.8.5  How to manually download helium gateway-rs via SSH access to the gateway Linux console ===
++== 2.9 Forward the data to the other server ==
--(% class="box infomessage" %)
--(((
--cd /tmp;wget -O helium-gateway-rs-dragino.ipk [[https:~~/~~/github.com/helium/gateway-rs/releases/download/v1.0.0-alpha.33/helium-gateway-v1.0.0-alpha.33-dragino.ipk>>https://github.com/helium/gateway-rs/releases/download/v1.0.0-alpha.33/helium-gateway-v1.0.0-alpha.33-dragino.ipk]]
++=== 2.9.1 Introduction ===
--opkg install helium-gateway-rs-dragino.ipk
--)))
--
--[[image:image-20230320141404-1.png]]
--
--
--== 2.9  Forward the data to the other server ==
--
--=== 2.9.1  Introduction ===
--
--
  (((
--//The Dragino gateway has supports the double server settings.//
++The Dragino gateway has supports the double server settings.
  )))
  (((
--//Users can back to the page of Semtech UDP to configure other server settings.//
++Users can back to the page of Semtech UDP to configure other server settings.
  )))
--=== 2.9.2  Example ===
++=== 2.9.2 Example ===
++The following takes The Things Network as another LoRaWAN server as an example.
--//The following takes The Things Network as another LoRaWAN server as an example.//
++==== 2.9.2.1 Step 1: Back to Semtech UDP page ====
--
--==== (% style="color:blue" %)**Step 1: Back to Semtech UDP page**(%%) ====
--
--
  [[image:image-20220531180002-10.png]]
  Back to Semtech UDP page
++==== 2.9.2.2 Step 2: Configure the double server forwarding ====
--==== (% style="color:blue" %)**Step 2: Configure the double server forwarding**(%%) ====
--
--
  [[image:image-20220531180048-11.png]]
++Configure the double server
--//The user can configure the secondary server and then click the button of **Save&Apply**.//
++The user can configure the secondary server and then click the button of Save&Apply.
--== 2.10  Connect Full Hotspot to Helium ==
++== 2.10 Connect Full Hotspot to Helium ==
++= 3. Use Dragino Sensors with Helium =
++== 3.1 How to add up user's end-node with Helium console ==
--= 3.  Use Dragino Sensors with Helium =
++=== 3.1.1 Step 1: Login the Helium console ===
--== 3.1  How to add up user's end-node with Helium console ==
++User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]
--=== 3.1.1  Step 1: Login the Helium console ===
--
--
--//User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
--
  [[image:image-20220531180150-12.png]]
  login Helium console
--=== 3.1.2  Step 2: Add up your end-node's key ===
++=== 3.1.2 Step 2: Add up your end-node's key ===
++User add up end-node's key from console ~-~->dervice
--//User add up end-node's key from console ~-~->dervice//
--
  [[image:image-20220531180224-13.png]]
  To add a device
--=== 3.1.3  Step 3: Activate the end-node ===
++=== 3.1.3 Step 3:Activate the end-node ===
--
  (((
--//Users can activate the end-node with OTAA in which the end-node will Join the network from the Helium server **Eventually you will see traffic**//
++Users can activate the end-node with OTAA in which the end-node will Join the network from the Helium server **Eventually you will see traffic**
  )))
  [[image:image-20220531105239-2.png]]
@@ -483,27 +483,17 @@
  end-node traffic.
--=== 3.1.4 Check Raw Payload for End Node ===
++== 3.2 How to use decoder ==
++=== 3.2.1 Step 1:Users can create decoders on functions ===
--Users can check what the end node has uplinked by checking the raw payload. as below:
--
--[[image:image-20220912161818-1.png]]
--
--
--== 3.2  How to use decoder ==
--
--=== 3.2.1  Step 1: Users can create decoders on functions ===
--
--
  [[image:image-20220531105325-3.png]]
  Decoder.
--=== 3.2.2  Step 2: Add a decoder in functions and apply it to the specified label ===
++=== 3.2.2 Step 2:Add a decoder in functions and apply it to the specified label ===
--
  [[image:image-20220526095629-6.png]]
@@ -512,35 +512,28 @@
  [[image:image-20220526100057-8.png||height="352" width="1133"]]
--**//Add decoder complete.//**
++Decoder.
++Add decoder complete.
--=== 3.2.3  Where is the decoder？ ===
++== 3.3 How to send a downlink to end device from Helium ==
--[[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
--
--[[image:image-20220617140118-1.png||height="550" width="883"]]
--
--
--== 3.3  How to send a downlink to end device from Helium ==
--
--
  (((
--//The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://
++The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example:
  )))
  (((
--//The Downlink command comes from this link：[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]//
++The Downlink command comes from this link：[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]
  )))
  (((
--//Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds//
++Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
  )))
  (% class="box" %)
  (((
--**01 00 00 3C ~-~-> AQAAPA==**
++01 00 00 3C ~-~-> AQAAPA==
  )))
  [[image:image-20220524171341-21.png]]
@@ -548,56 +548,55 @@
  Downlink
--== 3.4  How to add integration to different IoT Servers ==
++== 3.4 How to add integration to different IoT Servers ==
--=== 3.4.1  TagoIO ===
++=== 3.4.1 TagoIO ===
++The steps to add integration are very simple. Please see the following process.
--**//The steps to add integration are very simple. Please see the following process.//**
--
--
  [[image:image-20220526102429-23.png||height="630" width="1198"]]
++TagoIO.
--**//Generate the authorization code and then copy it.//**
++Generate the authorization code and then copy it.
--
  [[image:image-20220526100452-10.png||height="314" width="1188"]]
++TagoIO.
--//**Apply Integration to Label.**//
++Apply Integration to Label.
--
  [[image:image-20220526100802-13.png]]
++TagoIO.
++
  [[image:image-20220526100927-14.png]]
++TagoIO.
--**//Click LoRaWAN Helium,select the device.//**
++Click LoRaWAN Helium,select the device.
--
  [[image:image-20220526101215-15.png||height="599" width="1117"]]
++TagoIO.
--**//Fill in DEVEUI and create my device.//**
++Fill in DEVEUI and create my device.
--
  [[image:image-20220526101419-16.png]]
  TagoIO.
--=== 3.4.2  Cayenne ===
++=== 3.4.2 Cayenne ===
++The process of creating devices is similar to Tago.
--//The process of creating devices is similar to Tago.//
--
  [[image:image-20220526101616-18.png||height="456" width="1097"]]
  Cayenne.
@@ -628,116 +628,78 @@
  Cayenne.
--== 3.5  Trouble Shooting ==
++== 3.5 Trouble Shooting ==
--=== 3.5.1  Data-Only Hotspot is not connecting to Helium console ===
++=== 3.5.1 Trouble to Join Helium ===
--
--//**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
--
--
--1). The hotspot does not finish the onboarding to the helium blockchain.
--
--    after the 23 version of the gateway-rs, Helium requests the user to onboarding the devices to the blockchain, otherwise, your devices can't connect to the helium console. ~-~--> Please refer to [[Step 2.7>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Helium/#H2.7A0Step6:OnboardingData-OnlyHotspot]] to do it.
--
--
--=== 3.5.2  End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ===
--
--
--Make sure your blockchain region is the same as your hotspot settings. For example, as below, the blockchain is CN region, and software is configure to EU. The hotspot is able to get the OTAA Join Request from End Device on EU region. but due to block chain is CN region, Server will send the Join -Accept in CN region, so end device can't get the OTAA Join Accept.
--
--
--For example, if you are in USA, you have to use the US915 frequency plan. More frequency plans details on the helium network: [[https:~~/~~/docs.helium.com/lorawan-on-helium/frequency-plans>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans]]
--
--
--=== 3.5.3  Trouble to Join Helium ===
--
--
  (((
--**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
--
--
++Assume the device is powered correctly. If you don't see data in Helium. The possibilities are:
  )))
  (((
--//1) You are out of Helium Gateway coverage. (If you have other end nodes, you can check whether they work and what is the signal strength you see in the platform)//
++1) You are out of Helium Gateway coverage. (If you have other end nodes, you can check whether they work and what is the signal strength you see in the platform)
  )))
  (((
--//2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)//
++2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)
  )))
  (((
--//3) You have input the wrong keys into Helium Platform ( You can send us the screenshots for the keys and Dragino support team can check for you)//
++3) You have input the wrong keys into Helium Platform ( You can send us the screenshots for the keys and Dragino support team can check for you)
  )))
--=== 3.5.4  Packet Loss for AU915 / US915 Band ===
++=== 3.5.2 Packet Loss for AU915 / US915 Band ===
--
  (((
--//The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.//
++The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.
  )))
  (((
--//The reason for this problem is that the node does not lock the channel after joining the network.//
--
--
++The reason for this problem is that the node does not lock the channel after joining the network.
  )))
  (((
--(% style="color:red" %)**Solution:**
--
--
++Solution:
  )))
  (((
--//(1) If the user does not have a device to upgrade the firmware, you can use the AT+CHE command or the downlink command to set the channel. It is best to turn off the adaptive rate (ADR).Reset the device after setting the channel.//
++(1) If the user does not have a device to upgrade the firmware, you can use the AT+CHE command or the downlink command to set the channel. It is best to turn off the adaptive rate (ADR).Reset the device after setting the channel.
  )))
  * (((
--(% style="color:blue" %)**//AT Command: AT+CHE//**
++AT Command: AT+CHE
  )))
  * (((
--//**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%)   ~/~/set channel mode to 1//
++Example:AT+CHE=1 ~/~/set channel mode to 1
  )))
  * (((
--(% style="color:blue" %)**//Downlink Command: 0x24//**
--
--
++Downlink Command: 0x24
  )))
  (((
--//Format: Command Code (0x24) followed by 1 bytes channel value.//
++Format: Command Code (0x24) followed by 1 bytes channel value.
  )))
--
  (((
--//If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.//
++If the downlink payload=2401, it means set channel mode to 1, while type code is 24.
  )))
  * (((
--//**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%)   ~/~/ set channel mode to 2//
++Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
++)))
--
++* (((
++Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5
  )))
  (((
--//(2) If the user has a device to upgrade the firmware, it is better to upgrade the device to the latest version. The latest version has fixed the problem that the AU915/US915 frequency does not lock the channel.//
++(2) If the user has a device to upgrade the firmware, it is better to upgrade the device to the latest version. The latest version has fixed the problem that the AU915/US915 frequency does not lock the channel.
  )))
  (((
--//The latest firmware for end node will have this bug fixed.//
--
--
--=== 3.5.5  ADR doesn't work in EU868 band. ===
--
--
--See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]]
--
--
--
++The latest firmware for end node will have this bug fixed.
  )))

image-20220617140118-1.png

Author

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

Size

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

Content

image-20220912161818-1.png

Author

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

Size

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

Content

image-20230320141404-1.png

Author

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

Size

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

Content

Changes for page Notes for Helium

Summary

Details

Applications

Navigation