Changes for page Notes for Helium

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

From version < 88.4 >

edited by Xiaoling
on 2022/07/23 14:37

To version < 88.16 >

edited by Xiaoling
on 2022/07/23 15:20

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -23,16 +23,13 @@
  [[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.ConnectData-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.A0ConnectData-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//
--
--
  (% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]**
@@ -45,8 +45,6 @@
  * //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** ==
@@ -85,25 +85,28 @@
  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.//
  (((
@@ -116,10 +116,13 @@
  (% 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 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.//
@@ -126,7 +126,7 @@
  (((
--//**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.**//
++(% 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.**//
  )))
  (% class="box" %)
@@ -158,8 +158,9 @@
  )))
++
  (((
--//**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.**//
++(% 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.**//
  )))
  (% class="box" %)
@@ -192,11 +192,15 @@
  (((
  //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: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.//
  )))
@@ -240,7 +240,9 @@
  )))
  (((
--//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//
++
++
++(% style="color:blue" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//
  )))
  (% class="box" %)
@@ -295,18 +295,19 @@
  )))
  (((
--**Note: The add hotspot and assert location step might need some time to be effect.**
++(% style="color:red" %)**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.//
++
  )))
--== **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.//
@@ -337,18 +337,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.//
  [[image:image-20220531175809-7.png]]
--**Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.
++(% style="color:red" %)**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" %)
@@ -372,8 +372,10 @@
  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.//
  )))
@@ -382,9 +382,9 @@
--== **2.9 Forward the data to the other server** ==
++== **2.9  Forward the data to the other server** ==
--=== **2.9.1 Introduction** ===
++=== **2.9.1  Introduction** ===
  (((
@@ -397,23 +397,25 @@
  )))
--=== **2.9.2 Example** ===
++=== **2.9.2  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]]
@@ -420,17 +420,19 @@
  //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** ==
++=== **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]]
@@ -438,9 +438,10 @@
  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//
  [[image:image-20220531180224-13.png]]
@@ -448,9 +448,10 @@
  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**//
  )))
@@ -460,19 +460,21 @@
  end-node traffic.
--== **3.2 How to use decoder** ==
--=== **3.2.1 Step 1:Users can create decoders on functions** ===
++== **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]]
@@ -481,18 +481,22 @@
  [[image:image-20220526100057-8.png||height="352" width="1133"]]
--
  **//Add decoder complete.//**
--=== **3.2.3 Where is the decoder？** ===
++
++=== **3.2.3  Where is the decoder？** ===
++
++
  [[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** ==
++== **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~://
  )))
@@ -507,7 +507,7 @@
  (% class="box" %)
  (((
--01 00 00 3C ~-~-> AQAAPA==
++**01 00 00 3C ~-~-> AQAAPA==**
  )))
  [[image:image-20220524171341-21.png]]
@@ -515,11 +515,12 @@
  Downlink
--== **3.4 How to add integration to different IoT Servers** ==
--=== **3.4.1 TagoIO** ===
++== **3.4  How to add integration to different IoT Servers** ==
++=== **3.4.1  TagoIO** ===
++
  **//The steps to add integration are very simple. Please see the following process.//**
@@ -560,9 +560,10 @@
  TagoIO.
--=== **3.4.2 Cayenne** ===
++=== **3.4.2  Cayenne** ===
++
  //The process of creating devices is similar to Tago.//
  [[image:image-20220526101616-18.png||height="456" width="1097"]]
@@ -595,11 +595,12 @@
  Cayenne.
--== **3.5 Trouble Shooting** ==
--=== **3.5.1 Trouble to Join Helium** ===
++== **3.5  Trouble Shooting** ==
++=== **3.5.1  Trouble to Join Helium** ===
++
  (((
  **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
@@ -617,10 +617,11 @@
  (((
  //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.2 Packet Loss for AU915 / US915 Band** ===
++=== **3.5.2  Packet Loss for AU915 / US915 Band** ===
  (((
@@ -629,10 +629,12 @@
  (((
  //The reason for this problem is that the node does not lock the channel after joining the network.//
++
++
  )))
  (((
--**Solution:**
++(% style="color:red" %)**Solution:**
  )))
@@ -642,15 +642,17 @@
  )))
  * (((
--//AT Command: AT+CHE//
++(% style="color:blue" %)**//AT Command: AT+CHE//**
  )))
  * (((
--//Example:**AT+CHE=2** ~/~/set channel mode to 1//
++//**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%)   ~/~/set channel mode to 1//
  )))
  * (((
--//Downlink Command: 0x24//
++(% style="color:blue" %)**//Downlink Command: 0x24//**
++
++
  )))
  (((
@@ -657,14 +657,14 @@
  //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.//
  )))
  * (((
--//Example 1: Downlink Payload: **0x2402** ~/~/ set channel mode to 2//
++//**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%)   ~/~/ set channel mode to 2//
--
  )))

Changes for page Notes for Helium

Summary

Details

Applications

Navigation