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, 1 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Kilight - Content
-
... ... @@ -1,4 +1,4 @@ 1 -**~ Table ofContents:**1 +**~ Contents:** 2 2 3 3 {{toc/}} 4 4 ... ... @@ -5,11 +5,10 @@ 5 5 6 6 7 7 8 -= **1. 8 += **1. Use Dragino Gateways/Hotspots with Helium** = 9 9 10 -== **1.1 10 +== **1.1 Support Models** == 11 11 12 - 13 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 ((( ... ... @@ -23,10 +23,10 @@ 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 -)))|(% 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"]]25 +)))|(% 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 - (% style="color:blue" %)**Frequencies on the Helium Network**28 +**Frequencies on the Helium Network** 30 30 31 31 * //The frequencies currently available are CN470/EU868/US915/AU915// 32 32 ... ... @@ -33,36 +33,31 @@ 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 35 += **2. Connect Data-Only Hotspot to Helium** = 36 36 37 -= **2. Connect Data-Only Hotspotto Helium** =37 +== **2.1 Prerequisites** == 38 38 39 -== **2.1 Prerequisites** == 40 40 41 - 42 42 * //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]// 43 43 42 +== **2.2 Step 1: Configure Frequency Band** == 44 44 45 45 46 - 47 -== **2.2 Step 1: Configure Frequency Band** == 48 - 49 - 50 50 //Each country has a requirement for frequency region. Choose the right one for your area.// 51 51 52 52 [[image:image-20220531175337-1.png]] 53 53 54 54 50 +== **2.3 Step 2: Download the Helium-gateway-rs** == 55 55 56 -== **2.3 Step 2: Download the Helium-gateway-rs** == 57 57 58 - 59 59 //Click Download Helium Server and the gateway will download the Helium-gateway-rs// 60 60 61 61 [[image:image-20220615150600-1.png||height="559" width="1045"]] 62 62 63 - 64 64 //**Start download to Helium-gateway-rs**// 65 65 59 + 66 66 [[image:image-20220615150627-2.png||height="598" width="1044"]] 67 67 68 68 //**Helium-gatewayrs download success**// ... ... @@ -73,10 +73,9 @@ 73 73 [[image:image-20220615150717-3.png||height="605" width="1039"]] 74 74 75 75 70 +== **2.4 Step 3: Install the Helium-gateway-rs** == 76 76 77 -== **2.4 Step 3: Install the Helium-gateway-rs** == 78 78 79 - 80 80 //Click **Install Helium Server** to install gateway-rs.// 81 81 82 82 [[image:image-20220615150734-4.png||height="619" width="1035"]] ... ... @@ -83,30 +83,25 @@ 83 83 84 84 Install the Helium gateway-rs 85 85 86 - 87 87 (% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.** 88 88 89 89 82 +== **2.5 Step 4: Save&start the Helium Server** == 90 90 91 -== **2.5 Step 4: Save&start the Helium Server** == 92 92 93 - 94 94 //By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.// 95 95 96 - 97 97 [[image:image-20220615150903-5.png||height="592" width="1031"]] 98 98 99 99 90 +//Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.// 100 100 101 -//Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.// 102 - 103 103 [[image:image-20220615151057-6.png||height="580" width="1026"]] 104 104 105 105 95 +== **2.6 Step 5: Check Gateway Connection before onboarding** == 106 106 107 -== **2.6 Step 5: Check Gateway Connection before onboarding** == 108 108 109 - 110 110 //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.// 111 111 112 112 ((( ... ... @@ -119,13 +119,10 @@ 119 119 (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.** 120 120 121 121 110 +== 2.7 Step 6: Onboarding Data-Only Hotspot == 122 122 123 -= =**2.7 Step 6: Onboarding Data-OnlyHotspot**==112 +(% 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 .** 124 124 125 - 126 -(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .** 127 - 128 - 129 129 //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.// 130 130 131 131 //Below are the steps we do as per above link here.// ... ... @@ -132,7 +132,7 @@ 132 132 133 133 134 134 ((( 135 - (% 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.**//120 +//**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 136 ))) 137 137 138 138 (% class="box" %) ... ... @@ -159,15 +159,13 @@ 159 159 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+ 160 160 ))) 161 161 162 - 163 163 ((( 164 164 (% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.** 165 165 ))) 166 166 167 167 168 - 169 169 ((( 170 - (% 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.**//153 +//**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 171 ))) 172 172 173 173 (% class="box" %) ... ... @@ -200,15 +200,11 @@ 200 200 201 201 ((( 202 202 //We got the txn info from this step.// 186 +\\//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**// 203 203 204 204 205 - 206 -(% 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 - 208 - 209 209 (% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.** 210 210 211 - 212 212 //Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.// 213 213 ))) 214 214 ... ... @@ -252,9 +252,7 @@ 252 252 ))) 253 253 254 254 ((( 255 - 256 - 257 -(% style="color:blue" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**// 234 +//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**// 258 258 ))) 259 259 260 260 (% class="box" %) ... ... @@ -308,21 +308,19 @@ 308 308 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+ 309 309 ))) 310 310 311 - 312 312 ((( 313 - (% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.**289 +**Note: The add hotspot and assert location step might need some time to be effect.** 314 314 ))) 315 315 316 316 ((( 317 317 //After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.// 318 318 319 - 320 320 321 321 ))) 322 322 323 -== **2.8 298 +== **2.8 Debug Connection** == 324 324 325 -=== **2.8.1 300 +=== **2.8.1 Check pkt-fwd running Log** === 326 326 327 327 328 328 //This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.// ... ... @@ -353,22 +353,20 @@ 353 353 ))) 354 354 355 355 331 +=== **2.8.2 Check gateway-rs Log** === 356 356 357 -=== **2.8.2 Check gateway-rs Log** === 358 358 359 - 360 360 //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.// 361 361 362 362 [[image:image-20220531175809-7.png]] 363 363 364 364 365 - (% style="color:red" %)**Note**:**logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**339 +**Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system. 366 366 367 367 342 +=== **2.8.3 View the public key address and animal name** === 368 368 369 -=== **2.8.3 View the public key address and animal name** === 370 370 371 - 372 372 (% class="box" %) 373 373 ((( 374 374 ((( ... ... @@ -390,10 +390,8 @@ 390 390 Hostpot key and animal name 391 391 392 392 366 +=== **2.8.4 Backup/Restor gateway-rs key** === 393 393 394 -=== **2.8.4 Backup/Restor gateway-rs key** === 395 - 396 - 397 397 ((( 398 398 //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 399 ))) ... ... @@ -402,9 +402,9 @@ 402 402 403 403 404 404 405 -== **2.9 376 +== **2.9 Forward the data to the other server** == 406 406 407 -=== **2.9.1 378 +=== **2.9.1 Introduction** === 408 408 409 409 410 410 ((( ... ... @@ -414,29 +414,26 @@ 414 414 ((( 415 415 //Users can back to the page of Semtech UDP to configure other server settings.// 416 416 417 - 418 418 419 419 ))) 420 420 421 -=== **2.9.2 391 +=== **2.9.2 Example** === 422 422 423 423 424 424 //The following takes The Things Network as another LoRaWAN server as an example.// 425 425 426 426 397 +==== **2.9.2.1 Step 1: Back to Semtech UDP page** ==== 427 427 428 -==== (% style="color:blue" %)**Step 1: Back to Semtech UDP page**(%%) ==== 429 429 430 - 431 431 [[image:image-20220531180002-10.png]] 432 432 433 433 Back to Semtech UDP page 434 434 435 435 405 +==== **2.9.2.2 Step 2: Configure the double server forwarding** ==== 436 436 437 -==== (% style="color:blue" %)**Step 2: Configure the double server forwarding**(%%) ==== 438 438 439 - 440 440 [[image:image-20220531180048-11.png]] 441 441 442 442 ... ... @@ -443,20 +443,17 @@ 443 443 //The user can configure the secondary server and then click the button of **Save&Apply**.// 444 444 445 445 414 +== **2.10 Connect Full Hotspot to Helium** == 446 446 447 -= =**2.10ConnectFull HotspottoHelium** ==416 += **3. Use Dragino Sensors with Helium** = 448 448 449 449 419 +== **3.1 How to add up user's end-node with Helium console** == 450 450 451 -= **3. Use Dragino Sensors with Helium** = 452 452 422 +=== **3.1.1 Step 1: Login the Helium console** === 453 453 454 -== **3.1 How to add up user's end-node with Helium console** == 455 455 456 - 457 -=== **3.1.1 Step 1: Login the Helium console** === 458 - 459 - 460 460 //User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]// 461 461 462 462 [[image:image-20220531180150-12.png]] ... ... @@ -464,10 +464,9 @@ 464 464 login Helium console 465 465 466 466 432 +=== **3.1.2 Step 2: Add up your end-node's key** === 467 467 468 -=== **3.1.2 Step 2: Add up your end-node's key** === 469 469 470 - 471 471 //User add up end-node's key from console ~-~->dervice// 472 472 473 473 [[image:image-20220531180224-13.png]] ... ... @@ -475,10 +475,9 @@ 475 475 To add a device 476 476 477 477 442 +=== **3.1.3 Step 3:Activate the end-node** === 478 478 479 -=== **3.1.3 Step 3: Activate the end-node** === 480 480 481 - 482 482 ((( 483 483 //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 484 ))) ... ... @@ -488,21 +488,19 @@ 488 488 end-node traffic. 489 489 490 490 454 +== **3.2 How to use decoder** == 491 491 492 -== **3.2 Howtouse decoder** ==456 +=== **3.2.1 Step 1:Users can create decoders on functions** === 493 493 494 -=== **3.2.1 Step 1: Users can create decoders on functions** === 495 495 496 - 497 497 [[image:image-20220531105325-3.png]] 498 498 499 499 Decoder. 500 500 501 501 464 +=== **3.2.2 Step 2:Add a decoder in functions and apply it to the specified label** === 502 502 503 -=== **3.2.2 Step 2: Add a decoder in functions and apply it to the specified label** === 504 504 505 - 506 506 [[image:image-20220526095629-6.png]] 507 507 508 508 ... ... @@ -511,22 +511,13 @@ 511 511 512 512 [[image:image-20220526100057-8.png||height="352" width="1133"]] 513 513 475 + 514 514 **//Add decoder complete.//** 515 515 516 516 479 +== **3.3 How to send a downlink to end device from Helium** == 517 517 518 -=== **3.2.3 Where is the decoder?** === 519 519 520 - 521 -[[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]] 522 - 523 -[[image:image-20220617140118-1.png||height="550" width="883"]] 524 - 525 - 526 - 527 -== **3.3 How to send a downlink to end device from Helium** == 528 - 529 - 530 530 ((( 531 531 //The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~:// 532 532 ))) ... ... @@ -541,7 +541,7 @@ 541 541 542 542 (% class="box" %) 543 543 ((( 544 - **01 00 00 3C ~-~-> AQAAPA==**496 +01 00 00 3C ~-~-> AQAAPA== 545 545 ))) 546 546 547 547 [[image:image-20220524171341-21.png]] ... ... @@ -549,12 +549,11 @@ 549 549 Downlink 550 550 551 551 504 +== **3.4 How to add integration to different IoT Servers** == 552 552 553 -== **3.4 How toadd integration to differentIoT Servers** ==506 +=== **3.4.1 TagoIO** === 554 554 555 -=== **3.4.1 TagoIO** === 556 556 557 - 558 558 **//The steps to add integration are very simple. Please see the following process.//** 559 559 560 560 ... ... @@ -595,10 +595,9 @@ 595 595 TagoIO. 596 596 597 597 549 +=== **3.4.2 Cayenne** === 598 598 599 -=== **3.4.2 Cayenne** === 600 600 601 - 602 602 //The process of creating devices is similar to Tago.// 603 603 604 604 [[image:image-20220526101616-18.png||height="456" width="1097"]] ... ... @@ -631,12 +631,11 @@ 631 631 Cayenne. 632 632 633 633 584 +== **3.5 Trouble Shooting** == 634 634 635 -== **3.5 Shooting** ==586 +=== **3.5.1 Trouble to Join Helium** === 636 636 637 -=== **3.5.1 Trouble to Join Helium** === 638 638 639 - 640 640 ((( 641 641 **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://** 642 642 ... ... @@ -654,11 +654,10 @@ 654 654 ((( 655 655 //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)// 656 656 657 - 658 658 659 659 ))) 660 660 661 -=== **3.5.2 609 +=== **3.5.2 Packet Loss for AU915 / US915 Band** === 662 662 663 663 664 664 ((( ... ... @@ -667,12 +667,10 @@ 667 667 668 668 ((( 669 669 //The reason for this problem is that the node does not lock the channel after joining the network.// 670 - 671 - 672 672 ))) 673 673 674 674 ((( 675 - (% style="color:red" %)**Solution:**621 +**Solution:** 676 676 677 677 678 678 ))) ... ... @@ -682,17 +682,15 @@ 682 682 ))) 683 683 684 684 * ((( 685 - (% style="color:blue" %)**//AT Command: AT+CHE//**631 +//AT Command: AT+CHE// 686 686 ))) 687 687 688 688 * ((( 689 -// **Example:** (% style="color:#037691" %)**AT+CHE=2**(%%)635 +//Example:AT+CHE=1 ~/~/set channel mode to 1// 690 690 ))) 691 691 692 692 * ((( 693 -(% style="color:blue" %)**//Downlink Command: 0x24//** 694 - 695 - 639 +//Downlink Command: 0x24// 696 696 ))) 697 697 698 698 ((( ... ... @@ -699,14 +699,17 @@ 699 699 //Format: Command Code (0x24) followed by 1 bytes channel value.// 700 700 ))) 701 701 702 - 703 703 ((( 704 -//If the downlink payload= 0x2402, it means set channel mode touse sub-band 2, while type code is 24.//647 +//If the downlink payload=2401, it means set channel mode to 1, while type code is 24.// 705 705 ))) 706 706 707 707 * ((( 708 -//**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2// 651 +//Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1// 652 +))) 709 709 654 +* ((( 655 +//Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5// 656 + 710 710 711 711 ))) 712 712
- image-20220617140118-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -55.5 KB - Content