Changes for page Notes for Helium
Last modified by Edwin Chen on 2024/03/25 08:22
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -26,16 +26,14 @@ 26 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.ConnectData-OnlyHotspottoHelium"]] 27 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 - 30 30 **Frequencies on the Helium Network** 31 31 32 32 * //The frequencies currently available are CN470/EU868/US915/AU915// 33 33 34 - 35 - 36 36 (% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]** 37 37 38 38 36 + 39 39 = **2. Connect Data-Only Hotspot to Helium** = 40 40 41 41 == **2.1 Prerequisites** == ... ... @@ -43,7 +43,7 @@ 43 43 44 44 * //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]// 45 45 46 -== **2.2 Step 1: Configure Frequency Band** == 44 +== **2.2 Step 1: Configure Frequency Band** == 47 47 48 48 49 49 //Each country has a requirement for frequency region. Choose the right one for your area.// ... ... @@ -51,9 +51,10 @@ 51 51 [[image:image-20220531175337-1.png]] 52 52 53 53 54 -== **2.3 Step 2: Download the Helium-gateway-rs** == 55 55 53 +== **2.3 Step 2: Download the Helium-gateway-rs** == 56 56 55 + 57 57 //Click Download Helium Server and the gateway will download the Helium-gateway-rs// 58 58 59 59 [[image:image-20220615150600-1.png||height="559" width="1045"]] ... ... @@ -71,7 +71,7 @@ 71 71 [[image:image-20220615150717-3.png||height="605" width="1039"]] 72 72 73 73 74 -== **2.4 Step 3: Install the Helium-gateway-rs** == 73 +== **2.4 Step 3: Install the Helium-gateway-rs** == 75 75 76 76 77 77 //Click **Install Helium Server** to install gateway-rs.// ... ... @@ -80,25 +80,28 @@ 80 80 81 81 Install the Helium gateway-rs 82 82 82 + 83 83 (% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.** 84 84 85 85 86 -== **2.5 Step 4: Save&start the Helium Server** == 87 87 87 +== **2.5 Step 4: Save&start the Helium Server** == 88 88 89 + 89 89 //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 91 91 [[image:image-20220615150903-5.png||height="592" width="1031"]] 92 92 93 93 94 -//Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.// 95 +//Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.// 95 95 96 96 [[image:image-20220615151057-6.png||height="580" width="1026"]] 97 97 98 98 99 -== **2.6 Step 5: Check Gateway Connection before onboarding** == 100 100 101 +== **2.6 Step 5: Check Gateway Connection before onboarding** == 101 101 103 + 102 102 //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.// 103 103 104 104 ((( ... ... @@ -111,10 +111,13 @@ 111 111 (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.** 112 112 113 113 114 -== 2.7 Step 6: Onboarding Data-Only Hotspot == 115 115 117 +== **2.7 Step 6: Onboarding Data-Only Hotspot** == 118 + 119 + 116 116 (% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .** 117 117 122 + 118 118 //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.// 119 119 120 120 //Below are the steps we do as per above link here.// ... ... @@ -121,7 +121,7 @@ 121 121 122 122 123 123 ((( 124 -//**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.**// 129 +(% style="color:red" %)//**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.**// 125 125 ))) 126 126 127 127 (% class="box" %) ... ... @@ -153,8 +153,9 @@ 153 153 ))) 154 154 155 155 161 + 156 156 ((( 157 -//**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.**// 163 +(% style="color:red" %)//**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.**// 158 158 ))) 159 159 160 160 (% class="box" %) ... ... @@ -187,11 +187,15 @@ 187 187 188 188 ((( 189 189 //We got the txn info from this step.// 190 -\\//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**// 191 191 192 192 198 + 199 +(% style="color:red" %)//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**// 200 + 201 + 193 193 (% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.** 194 194 204 + 195 195 //Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.// 196 196 ))) 197 197 ... ... @@ -235,7 +235,9 @@ 235 235 ))) 236 236 237 237 ((( 238 -//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**// 248 + 249 + 250 +(% style="color:red" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**// 239 239 ))) 240 240 241 241 (% class="box" %) ... ... @@ -290,18 +290,19 @@ 290 290 ))) 291 291 292 292 ((( 293 -**Note: The add hotspot and assert location step might need some time to be effect.** 305 +(% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.** 294 294 ))) 295 295 296 296 ((( 297 297 //After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.// 298 298 311 + 299 299 300 300 ))) 301 301 302 -== **2.8 Debug Connection** == 315 +== **2.8 Debug Connection** == 303 303 304 -=== **2.8.1 Check pkt-fwd running Log** === 317 +=== **2.8.1 Check pkt-fwd running Log** === 305 305 306 306 307 307 //This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.// ... ... @@ -332,18 +332,19 @@ 332 332 ))) 333 333 334 334 335 -=== **2.8.2 Check gateway-rs Log** === 336 336 349 +=== **2.8.2 Check gateway-rs Log** === 337 337 351 + 338 338 //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.// 339 339 340 340 [[image:image-20220531175809-7.png]] 341 341 342 342 343 -**Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system. 357 +(% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.** 344 344 345 345 346 -=== **2.8.3 View the public key address and animal name** === 360 +=== **2.8.3 View the public key address and animal name** === 347 347 348 348 349 349 (% class="box" %) ... ... @@ -367,8 +367,10 @@ 367 367 Hostpot key and animal name 368 368 369 369 370 -=== **2.8.4 Backup/Restor gateway-rs key** === 371 371 385 +=== **2.8.4 Backup/Restor gateway-rs key** === 386 + 387 + 372 372 ((( 373 373 //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.// 374 374 ))) ... ... @@ -377,9 +377,9 @@ 377 377 378 378 379 379 380 -== **2.9 Forward the data to the other server** == 396 +== **2.9 Forward the data to the other server** == 381 381 382 -=== **2.9.1 Introduction** === 398 +=== **2.9.1 Introduction** === 383 383 384 384 385 385 ((( ... ... @@ -392,21 +392,22 @@ 392 392 393 393 ))) 394 394 395 -=== **2.9.2 Example** === 411 +=== **2.9.2 Example** === 396 396 397 397 398 398 //The following takes The Things Network as another LoRaWAN server as an example.// 399 399 400 400 401 -==== **2.9.2.1 Step 1: Back to Semtech UDP page** ==== 402 402 418 +==== (% style="color:blue" %)**Step 1: Back to Semtech UDP page**(%%) ==== 403 403 420 + 404 404 [[image:image-20220531180002-10.png]] 405 405 406 406 Back to Semtech UDP page 407 407 408 408 409 -==== ** 2.9.2.2Step 2: Configure the double server forwarding** ====426 +==== (% style="color:blue" %)**Step 2: Configure the double server forwarding**(%%) ==== 410 410 411 411 412 412 [[image:image-20220531180048-11.png]]