Changes for page Notes for Helium
Last modified by Edwin Chen on 2024/03/25 08:22
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Kilight1 +XWiki.Xiaoling - Content
-
... ... @@ -5,26 +5,26 @@ 5 5 6 6 7 7 8 -= 1. Use Dragino Gateways/Hotspots with Helium = 8 += **1. Use Dragino Gateways/Hotspots with Helium** = 9 9 10 -== 1.1 Support Models == 10 +== **1.1 Support Models** == 11 11 12 12 13 -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. 13 +//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.// 14 14 15 15 ((( 16 -Dragino has different gateway models that support different types. 16 +//Dragino has different gateway models that support different types.// 17 17 ))) 18 18 19 -(% border="1" style="background-color:#f 2f2f2; width:510px" %)20 -|(% colspan="4" style=" background-color:#d9e2f3; color:#0070c0;width:589px" %)**Dragino Hotspots for Helium**21 -|(% style="color: #0070c0; width:132px" %)**Model**|(% style="color:#0070c0; width:126px" %)**Hotspot Types**|(% style="color:#0070c0; width:121px" %)**Mining Ability**|(% style="color:#0070c0; width:203px" %)**Configure Instruction**19 +(% border="1" style="background-color:#ffffcc; width:510px" %) 20 +|(% colspan="4" style="width:589px" %)(% style="color:green" %)**Dragino Hotspots for Helium** 21 +|(% 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** 22 22 |(% style="width:132px" %)((( 23 23 [[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]], 24 24 25 25 [[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]] 26 -)))|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"]] 27 -|(% style="width:132px" %)[[HP0D>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/195-hp0d.html]]|Full Hotspot|(% 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]] 26 +)))|(% 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"]] 27 +|(% 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]] 28 28 29 29 (% style="color:blue" %)**Frequencies on the Helium Network** 30 30 ... ... @@ -33,27 +33,32 @@ 33 33 (% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]** 34 34 35 35 36 -= 2. Connect Data-Only Hotspot to Helium = 37 37 38 -= =2.1Prerequisites==37 += **2. Connect Data-Only Hotspot to Helium** = 39 39 39 +== **2.1 Prerequisites** == 40 40 41 -* Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]] 42 42 43 - ==2.2Step1:Configurequency Band ==42 +* //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]// 44 44 45 45 46 -Each country has a requirement for frequency region. Choose the right one for your area. 47 47 46 + 47 +== **2.2 Step 1: Configure Frequency Band** == 48 + 49 + 50 +//Each country has a requirement for frequency region. Choose the right one for your area.// 51 + 48 48 [[image:image-20220531175337-1.png]] 49 49 50 50 51 -== 2.3 Step 2: Download the Helium-gateway-rs == 52 52 56 +== **2.3 Step 2: Download the Helium-gateway-rs** == 53 53 54 -Click Download Helium Server and the gateway will download the Helium-gateway-rs 55 55 59 +//Click Download Helium Server and the gateway will download the Helium-gateway-rs// 56 56 61 + 57 57 [[image:image-20220615150600-1.png||height="559" width="1045"]] 58 58 59 59 ... ... @@ -69,11 +69,12 @@ 69 69 [[image:image-20220615150717-3.png||height="605" width="1039"]] 70 70 71 71 72 -== 2.4 Step 3: Install the Helium-gateway-rs == 73 73 78 +== **2.4 Step 3: Install the Helium-gateway-rs** == 74 74 75 -Click (% style="color:blue" %)**Install Helium Server**(%%) to install gateway-rs. 76 76 81 +//Click **Install Helium Server** to install gateway-rs.// 82 + 77 77 [[image:image-20220615150734-4.png||height="619" width="1035"]] 78 78 79 79 Install the Helium gateway-rs ... ... @@ -82,28 +82,30 @@ 82 82 (% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.** 83 83 84 84 85 -== 2.5 Step 4: Save&start the Helium Server == 86 86 92 +== **2.5 Step 4: Save&start the Helium Server** == 87 87 88 -By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region. 89 89 95 +//By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.// 90 90 97 + 91 91 [[image:image-20220615150903-5.png||height="592" width="1031"]] 92 92 93 93 94 94 95 -Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status. 102 +//Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.// 96 96 97 97 [[image:image-20220615151057-6.png||height="580" width="1026"]] 98 98 99 99 100 -== 2.6 Step 5: Check Gateway Connection before onboarding == 101 101 108 +== **2.6 Step 5: Check Gateway Connection before onboarding** == 102 102 103 -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. 104 104 111 +//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.// 112 + 105 105 ((( 106 -Check end device event from [[Helium Console>>url:https://staging-console.helium.wtf/]], We can see the LGT92 data arrived Helium via our hotspot. 114 +//Check end device event from [[Helium Console>>url:https://staging-console.helium.wtf/]], We can see the LGT92 data arrived Helium via our hotspot.// 107 107 ))) 108 108 109 109 [[image:image-20220526094537-1.png||height="395" width="1323"]] ... ... @@ -112,29 +112,25 @@ 112 112 (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.** 113 113 114 114 115 -== 2.7 Step 6: Onboarding Data-Only Hotspot == 116 116 124 +== **2.7 Step 6: Onboarding Data-Only Hotspot** == 117 117 118 -**After the Helium Network was successfully migrated to the Solana blockchain on April 18, 2023, 9 am PST (16:00 UTC). the onboarding for data-only hotspots is not quite yet** 119 119 120 -**No wtheusersareabletoconnect theheliumconsolewithadata-onlyhotspotwithoutanyonboarding.**127 +(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .** 121 121 122 122 123 - (%style="color:red" %)--**Note:Onboarding aData-Only hotspotis necessaryforownlinktowork.otherwise,thedownlinkmessagefor LoRa won't work.**--130 +//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.// 124 124 132 +//Below are the steps we do as per above link here.// 125 125 126 ---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.-- 127 127 128 ---Below are the steps we do as per above link here.-- 129 - 130 - 131 131 ((( 132 -(% 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.**//--136 +(% 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.**// 133 133 ))) 134 134 135 135 (% class="box" %) 136 136 ((( 137 - --[root@iZt4n22vqvm7ajogrfiif6Z helium-wallet-v1.6.4-x86-64-linux]# helium-wallet info141 +[root@iZt4n22vqvm7ajogrfiif6Z helium-wallet-v1.6.4-x86-64-linux]# helium-wallet info 138 138 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+ 139 139 ~| Key | Value | 140 140 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+ ... ... @@ -153,65 +153,65 @@ 153 153 ~| DC Balance | 0 | 154 154 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+ 155 155 ~| Securities Balance | 0.00000000 | 156 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+ --160 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+ 157 157 ))) 158 158 159 159 160 160 ((( 161 -(% style="color:red" %) --**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.**--165 +(% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.** 162 162 ))) 163 163 164 164 165 165 166 166 ((( 167 -(% 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.**//--171 +(% 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.**// 168 168 ))) 169 169 170 170 (% class="box" %) 171 171 ((( 172 - --root@123123:~~# helium_gateway add ~-~-owner 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux ~-~-payer 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux--176 +root@123123:~~# helium_gateway add ~-~-owner 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux ~-~-payer 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux 173 173 174 - --{175 -(% style="color:red" %)"address": "146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm", (%%)--178 +{ 179 +(% style="color:red" %)"address": "146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm", 176 176 177 177 (% style="color:red" %) 178 - --"fee": (% style="color:black" %)65000,(%%)--182 +"fee": (% style="color:black" %)65000, 179 179 180 180 (% style="color:red" %) 181 - --"mode": "dataonly",--185 +"mode": "dataonly", 182 182 183 183 (% style="color:red" %) 184 - --"owner": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",--188 +"owner": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux", 185 185 186 186 (% style="color:red" %) 187 - --"payer": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",--191 +"payer": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux", 188 188 189 189 (% style="color:red" %) 190 - --"staking fee"(% style="color:black" %): 1000000,(%%)--194 +"staking fee"(% style="color:black" %): 1000000, 191 191 192 192 (% style="color: red;" %) 193 - --"txn": "CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM="--197 +"txn": "CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM=" 194 194 195 - --}--199 +} 196 196 ))) 197 197 198 198 ((( 199 - --//We got the txn info from this step.//--203 +//We got the txn info from this step.// 200 200 201 201 202 202 203 -(% 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.**//--207 +(% 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.**// 204 204 205 205 206 -(% style="color:red" %) --**Note: below are two commands, the command without ~-~-commit is the preview mode.**--210 +(% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.** 207 207 208 208 209 - --Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.--213 +//Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.// 210 210 ))) 211 211 212 212 (% class="box" %) 213 213 ((( 214 - --[root@]# helium-wallet hotspots add CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM=218 +[root@]# helium-wallet hotspots add CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM= 215 215 Password: [hidden] 216 216 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+ 217 217 ~| Key | Value | ... ... @@ -245,18 +245,18 @@ 245 245 ~| Staking fee (DC) | 1000000 | 246 246 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+ 247 247 ~| Hash | i6BQAI4Ehnd7nb8zfvegprhO2fOI1rj4UEPbAVC2sWk | 248 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+ --252 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+ 249 249 ))) 250 250 251 251 ((( 252 252 253 253 254 -(% style="color:blue" %) --//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//--258 +(% style="color:blue" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**// 255 255 ))) 256 256 257 257 (% class="box" %) 258 258 ((( 259 - --[root@]# helium-wallet hotspots assert ~-~-gateway 146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm ~-~-lat=22.706922 ~-~-lon=114.242538 ~-~-mode dataonly263 +[root@]# helium-wallet hotspots assert ~-~-gateway 146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm ~-~-lat=22.706922 ~-~-lon=114.242538 ~-~-mode dataonly 260 260 Password: [hidden] 261 261 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+ 262 262 ~| Key | Value | ... ... @@ -302,29 +302,30 @@ 302 302 ~| Elevation | 0 | 303 303 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+ 304 304 ~| Hash | P1P8olxrzPJ1f3HWiLxcSincdF5fDLLCt2HbpYBhWwk | 305 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+ --309 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+ 306 306 ))) 307 307 308 308 309 309 ((( 310 -(% style="color:red" %) --**Note: The add hotspot and assert location step might need some time to be effect.**--314 +(% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.** 311 311 ))) 312 312 313 313 ((( 314 - --After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.--318 +//After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.// 315 315 320 + 316 316 317 317 ))) 318 318 319 -== 2.8 Debug Connection == 324 +== **2.8 Debug Connection** == 320 320 321 -=== 2.8.1 Check pkt-fwd running Log === 326 +=== **2.8.1 Check pkt-fwd running Log** === 322 322 323 323 324 -This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors. 329 +//This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.// 325 325 326 326 ((( 327 -Below logs shows the gateway receive two LoRaWAN packets. 332 +//Below logs shows the gateway receive two LoRaWAN packets.// 328 328 ))) 329 329 330 330 (% class="box" %) ... ... @@ -349,9 +349,10 @@ 349 349 ))) 350 350 351 351 352 -=== 2.8.2 Check gateway-rs Log === 353 353 358 +=== **2.8.2 Check gateway-rs Log** === 354 354 360 + 355 355 //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.// 356 356 357 357 [[image:image-20220531175809-7.png]] ... ... @@ -360,9 +360,10 @@ 360 360 (% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.** 361 361 362 362 363 -=== 2.8.3 View the public key address and animal name === 364 364 370 +=== **2.8.3 View the public key address and animal name** === 365 365 372 + 366 366 (% class="box" %) 367 367 ((( 368 368 ((( ... ... @@ -384,48 +384,38 @@ 384 384 Hostpot key and animal name 385 385 386 386 387 -=== 2.8.4 Backup/Restor gateway-rs key === 388 388 395 +=== **2.8.4 Backup/Restor gateway-rs key** === 389 389 397 + 390 390 ((( 391 -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. 399 +//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.// 392 392 ))) 393 393 394 394 [[image:image-20220531175919-9.png]] 395 395 396 396 397 -=== 2.8.5 How to manually download helium gateway-rs via SSH access to the gateway Linux console === 398 398 406 +== **2.9 Forward the data to the other server** == 399 399 400 -(% class="box infomessage" %) 401 -((( 402 -**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]]** 408 +=== **2.9.1 Introduction** === 403 403 404 -**opkg install helium-gateway-rs-dragino.ipk ** 405 -))) 406 406 407 -[[image:image-20230320141404-1.png]] 408 - 409 - 410 -== 2.9 Forward the data to the other server == 411 - 412 -=== 2.9.1 Introduction === 413 - 414 - 415 415 ((( 416 -The Dragino gateway has supports the double server settings. 412 +//The Dragino gateway has supports the double server settings.// 417 417 ))) 418 418 419 419 ((( 420 -Users can back to the page of Semtech UDP to configure other server settings. 416 +//Users can back to the page of Semtech UDP to configure other server settings.// 421 421 418 + 422 422 423 423 ))) 424 424 425 -=== 2.9.2 Example === 422 +=== **2.9.2 Example** === 426 426 427 427 428 -The following takes The Things Network as another LoRaWAN server as an example. 425 +//The following takes The Things Network as another LoRaWAN server as an example.// 429 429 430 430 431 431 ... ... @@ -444,20 +444,23 @@ 444 444 [[image:image-20220531180048-11.png]] 445 445 446 446 447 -The user can configure the secondary server and then click the button of (% style="color:red" %)**Save&Apply**.444 +//The user can configure the secondary server and then click the button of **Save&Apply**.// 448 448 449 449 450 -== 2.10 Connect Full Hotspot to Helium == 451 451 448 +== **2.10 Connect Full Hotspot to Helium** == 452 452 453 453 454 -= 3. Use Dragino Sensors with Helium = 455 455 456 -= =3.1How to add up user'send-nodewith Heliumconsole==452 += **3. Use Dragino Sensors with Helium** = 457 457 458 -=== 3.1.1 Step 1: Login the Helium console === 459 459 455 +== **3.1 How to add up user's end-node with Helium console** == 460 460 457 + 458 +=== **3.1.1 Step 1: Login the Helium console** === 459 + 460 + 461 461 //User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]// 462 462 463 463 [[image:image-20220531180150-12.png]] ... ... @@ -465,21 +465,23 @@ 465 465 login Helium console 466 466 467 467 468 -=== 3.1.2 Step 2: Add up your end-node's key === 469 469 469 +=== **3.1.2 Step 2: Add up your end-node's key** === 470 470 471 -User add up end-node's key from console ~-~->dervice 472 472 472 +//User add up end-node's key from console ~-~->dervice// 473 + 473 473 [[image:image-20220531180224-13.png]] 474 474 475 475 To add a device 476 476 477 477 478 -=== 3.1.3 Step 3: Activate the end-node === 479 479 480 +=== **3.1.3 Step 3: Activate the end-node** === 480 480 482 + 481 481 ((( 482 -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** 484 +//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**// 483 483 ))) 484 484 485 485 [[image:image-20220531105239-2.png]] ... ... @@ -487,27 +487,30 @@ 487 487 end-node traffic. 488 488 489 489 490 -=== 3.1.4 Check Raw Payload for End Node === 491 491 493 +=== **3.1.4 Check Raw Payload for End Node** === 492 492 495 + 493 493 Users can check what the end node has uplinked by checking the raw payload. as below: 494 494 495 495 [[image:image-20220912161818-1.png]] 496 496 497 497 498 -== 3.2 How to use decoder == 499 499 500 -== =3.2.1Step1: Userscan createdecoderson functions===502 +== **3.2 How to use decoder** == 501 501 504 +=== **3.2.1 Step 1: Users can create decoders on functions** === 502 502 506 + 503 503 [[image:image-20220531105325-3.png]] 504 504 505 505 Decoder. 506 506 507 507 508 -=== 3.2.2 Step 2: Add a decoder in functions and apply it to the specified label === 509 509 513 +=== **3.2.2 Step 2: Add a decoder in functions and apply it to the specified label** === 510 510 515 + 511 511 [[image:image-20220526095629-6.png]] 512 512 513 513 ... ... @@ -519,27 +519,29 @@ 519 519 **//Add decoder complete.//** 520 520 521 521 522 -=== 3.2.3 Where is the decoder? === 523 523 528 +=== **3.2.3 Where is the decoder?** === 524 524 530 + 525 525 [[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]] 526 526 527 527 [[image:image-20220617140118-1.png||height="550" width="883"]] 528 528 529 529 530 -== 3.3 How to send a downlink to end device from Helium == 531 531 537 +== **3.3 How to send a downlink to end device from Helium** == 532 532 539 + 533 533 ((( 534 -The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example: 541 +//The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~:// 535 535 ))) 536 536 537 537 ((( 538 -The Downlink command comes from this link:[[End Device Downlink Command>>End Device AT Commands and Downlink Command]] 545 +//The Downlink command comes from this link:[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]// 539 539 ))) 540 540 541 541 ((( 542 -Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds 549 +//Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds// 543 543 ))) 544 544 545 545 (% class="box" %) ... ... @@ -552,11 +552,12 @@ 552 552 Downlink 553 553 554 554 555 -== 3.4 How to add integration to different IoT Servers == 556 556 557 -== =3.4.1TagoIO===563 +== **3.4 How to add integration to different IoT Servers** == 558 558 565 +=== **3.4.1 TagoIO** === 559 559 567 + 560 560 **//The steps to add integration are very simple. Please see the following process.//** 561 561 562 562 ... ... @@ -597,11 +597,12 @@ 597 597 TagoIO. 598 598 599 599 600 -=== 3.4.2 Cayenne === 601 601 609 +=== **3.4.2 Cayenne** === 602 602 603 -The process of creating devices is similar to Tago. 604 604 612 +//The process of creating devices is similar to Tago.// 613 + 605 605 [[image:image-20220526101616-18.png||height="456" width="1097"]] 606 606 607 607 Cayenne. ... ... @@ -632,11 +632,13 @@ 632 632 Cayenne. 633 633 634 634 635 -== 3.5 Trouble Shooting == 636 636 637 -== =3.5.1Data-OnlyHotspotsnot connectingto Helium console===645 +== **3.5 Trouble Shooting** == 638 638 639 639 648 +=== **3.5.1 Data-Only Hotspot is not connecting to Helium console** === 649 + 650 + 640 640 //**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**// 641 641 642 642 ... ... @@ -645,9 +645,10 @@ 645 645 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. 646 646 647 647 648 -=== 3.5.2 End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. === 649 649 660 +=== **3.5.2 End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ** === 650 650 662 + 651 651 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. 652 652 653 653 ... ... @@ -654,9 +654,10 @@ 654 654 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]] 655 655 656 656 657 -=== 3.5.3 Trouble to Join Helium === 658 658 670 +=== **3.5.3 Trouble to Join Helium** === 659 659 672 + 660 660 ((( 661 661 **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://** 662 662 ... ... @@ -664,28 +664,29 @@ 664 664 ))) 665 665 666 666 ((( 667 -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) 680 +//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)// 668 668 ))) 669 669 670 670 ((( 671 -2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches) 684 +//2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)// 672 672 ))) 673 673 674 674 ((( 675 -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) 688 +//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)// 676 676 690 + 677 677 678 678 ))) 679 679 680 -=== 3.5.4 Packet Loss for AU915 / US915 Band === 694 +=== **3.5.4 Packet Loss for AU915 / US915 Band** === 681 681 682 682 683 683 ((( 684 -The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different. 698 +//The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.// 685 685 ))) 686 686 687 687 ((( 688 -The reason for this problem is that the node does not lock the channel after joining the network. 702 +//The reason for this problem is that the node does not lock the channel after joining the network.// 689 689 690 690 691 691 ))) ... ... @@ -697,49 +697,50 @@ 697 697 ))) 698 698 699 699 ((( 700 -(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. 714 +//(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.// 701 701 ))) 702 702 703 703 * ((( 704 -(% style="color:blue" %)**AT Command: AT+CHE** 718 +(% style="color:blue" %)**//AT Command: AT+CHE//** 705 705 ))) 706 706 707 707 * ((( 708 -**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%) ~/~/set channel mode to 1 722 +//**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%) ~/~/set channel mode to 1// 709 709 ))) 710 710 711 711 * ((( 712 -(% style="color:blue" %)**Downlink Command: 0x24** 726 +(% style="color:blue" %)**//Downlink Command: 0x24//** 713 713 714 714 715 715 ))) 716 716 717 717 ((( 718 -Format: Command Code (0x24) followed by 1 bytes channel value. 732 +//Format: Command Code (0x24) followed by 1 bytes channel value.// 719 719 ))) 720 720 721 721 722 722 ((( 723 -If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24. 737 +//If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.// 724 724 ))) 725 725 726 726 * ((( 727 -**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2 741 +//**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2// 728 728 729 729 730 730 ))) 731 731 732 732 ((( 733 -(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. 747 +//(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.// 734 734 ))) 735 735 736 736 ((( 737 -The latest firmware for end node will have this bug fixed. 751 +//The latest firmware for end node will have this bug fixed.// 738 738 739 739 740 -=== 3.5.5 ADR doesn't work in EU868 band. === 741 741 755 +=== **3.5.5 ADR doesn't work in EU868 band.** === 742 742 757 + 743 743 See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]] 744 744 745 745
- image-20230320141404-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -57.8 KB - Content
- image-20231120113632-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -36.7 KB - Content