Changes for page Notes for Helium

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

From version < 1.16 >

edited by Xiaoling
on 2022/05/16 16:23

To version < 2.1 >

edited by Xiaoye
on 2022/05/24 10:54

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Author

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

Content

@@ -1,4 +1,4 @@
--**Contents:**
++**~     Contents:**
  {{toc/}}
@@ -9,13 +9,15 @@
  There are three types of hotspots that can connect to Helium. They are full-hotspot, light hotspot and 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.
++)))
  (% border="1" style="background-color:#ffffcc; width:785.989px" %)
  |(% colspan="4" style="width:783px" %)(% style="color:green" %)**Dragino Hotspots for Helium**
  |(% style="color:green; width:203px" %)**Model**|(% style="color:green; width:162px" %)**Hotspot Types**|(% style="color:green; width:134px" %)**Mining Ability**|(% style="color:green; width:250px" %)**Configure Instruction**
  |(% style="width:203px" %)[[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:162px" %)**Data-Only Hotspot**|(% style="width:134px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]]|(% style="width:250px" %)[[Data-Only Hotspot Instruction>>url:https://wiki.dragino.com/index.php/Notes_for_Helium#Connect_Data-Only_Hotspot_to_Helium]]
--|(% style="width:203px" %)[[HP0D>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/195-hp0d.html]]|(% style="color:#4f81bd; width:162px" %)**Full Hotspo**t|(% style="width:134px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/full-hotspots]]|(% style="color:green; width:250px" %)Full Hotspot Instruction-Not Finish
++|(% style="width:203px" %)[[HP0D>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/195-hp0d.html]]|(% style="color:#4f81bd; width:162px" %)**Full Hotspo**t|(% style="width:134px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/full-hotspots]]|(% style="color:green; width:250px" %)
  **Frequencies on the Helium Network**
@@ -123,7 +123,9 @@
  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
  )))
++(((
  **Note**: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.
++)))
  (((
@@ -202,7 +202,9 @@
  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
  )))
++(((
 . Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.
++)))
  (% class="box" %)
  (((
@@ -255,7 +255,9 @@
  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
  )))
++(((
  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.
@@ -326,7 +326,9 @@
  === 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.
++)))
  [[image:https://wiki.dragino.com/images/thumb/e/ef/Backup_and_restore_key.png/600px-Backup_and_restore_key.png||height="343" width="600"]]
@@ -336,9 +336,13 @@
  === 2.9.1 Introduction ===
++(((
  The Dragino gateway has supports the double server settings.
++)))
++(((
  Users can back to the page of Semtech UDP to configure other server settings.
++)))
  === 2.9.2 Example ===
@@ -382,7 +382,9 @@
  === 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**
++)))
  [[image:https://wiki.dragino.com/images/thumb/4/45/End-node_traffic.png/600px-End-node_traffic.png||height="239" width="600"]]
@@ -412,22 +412,29 @@
  Add decoder complete.
--
  == 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 Downlink command comes from this link：[[https:~~/~~/wiki.dragino.com/index.php?title=End_Device_Downlink_Command>>url:https://wiki.dragino.com/index.php?title=End_Device_Downlink_Command]]
++)))
++(((
  Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
++)))
++(% class="box" %)
++(((
 00 00 3C ~-~-> AQAAPA==
++)))
  [[image:https://wiki.dragino.com/images/thumb/c/c5/Helium_downlink.png/600px-Helium_downlink.png||height="360" width="600"]]
  Downlink
--
  == 3.4 How to add integration to different IoT Servers ==
  === 3.4.1 TagoIO ===
@@ -498,39 +498,72 @@
  === 3.5.1 Trouble to Join Helium ===
++(((
  Assume the device is powered correctly. If you don't see data in Helium. The possibilities are:
++)))
++(((
 ) 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)
++)))
++(((
 ) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)
++)))
++(((
 ) 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 ===
++(((
  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.
++)))
++(((
  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.
++)))
--* AT Command: AT+CHE
++* (((
++AT Command: AT+CHE
++)))
--* Example:AT+CHE=1 ~/~/set channel mode to 1
++* (((
++Example:AT+CHE=1 ~/~/set channel mode to 1
++)))
--* Downlink Command: 0x24
++* (((
++Downlink Command: 0x24
++)))
++(((
  Format: Command Code (0x24) followed by 1 bytes channel value.
++)))
++(((
  If the downlink payload=2401, it means set channel mode to 1, while type code is 24.
++)))
--* Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
++* (((
++Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
++)))
--* Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5
++* (((
++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.
++)))
++(((
  The latest firmware for end node will have this bug fixed.
++)))

Changes for page Notes for Helium

Summary

Details

Applications

Navigation