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 ((( ... ... @@ -33,15 +33,14 @@ 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 44 -== **2.2 42 +== **2.2 Step 1: Configure Frequency Band** == 45 45 46 46 47 47 //Each country has a requirement for frequency region. Choose the right one for your area.// ... ... @@ -49,10 +49,9 @@ 49 49 [[image:image-20220531175337-1.png]] 50 50 51 51 50 +== **2.3 Step 2: Download the Helium-gateway-rs** == 52 52 53 -== **2.3 Step 2: Download the Helium-gateway-rs** == 54 54 55 - 56 56 //Click Download Helium Server and the gateway will download the Helium-gateway-rs// 57 57 58 58 [[image:image-20220615150600-1.png||height="559" width="1045"]] ... ... @@ -70,7 +70,7 @@ 70 70 [[image:image-20220615150717-3.png||height="605" width="1039"]] 71 71 72 72 73 -== **2.4 70 +== **2.4 Step 3: Install the Helium-gateway-rs** == 74 74 75 75 76 76 //Click **Install Helium Server** to install gateway-rs.// ... ... @@ -79,28 +79,25 @@ 79 79 80 80 Install the Helium gateway-rs 81 81 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 82 +== **2.5 Step 4: Save&start the Helium Server** == 86 86 87 -== **2.5 Step 4: Save&start the Helium Server** == 88 88 89 - 90 90 //By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.// 91 91 92 92 [[image:image-20220615150903-5.png||height="592" width="1031"]] 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.//90 +//Click **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 95 +== **2.6 Step 5: Check Gateway Connection before onboarding** == 100 100 101 -== **2.6 Step 5: Check Gateway Connection before onboarding** == 102 102 103 - 104 104 //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.// 105 105 106 106 ((( ... ... @@ -113,13 +113,10 @@ 113 113 (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.** 114 114 115 115 110 +== 2.7 Step 6: Onboarding Data-Only Hotspot == 116 116 117 -= =**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 .** 118 118 119 - 120 -(% 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 - 122 - 123 123 //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 125 125 //Below are the steps we do as per above link here.// ... ... @@ -126,7 +126,7 @@ 126 126 127 127 128 128 ((( 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.**//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.**// 130 130 ))) 131 131 132 132 (% class="box" %) ... ... @@ -158,9 +158,8 @@ 158 158 ))) 159 159 160 160 161 - 162 162 ((( 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.**//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.**// 164 164 ))) 165 165 166 166 (% class="box" %) ... ... @@ -193,15 +193,11 @@ 193 193 194 194 ((( 195 195 //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.**// 196 196 197 197 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 - 202 202 (% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.** 203 203 204 - 205 205 //Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.// 206 206 ))) 207 207 ... ... @@ -245,9 +245,7 @@ 245 245 ))) 246 246 247 247 ((( 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.**// 234 +//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**// 251 251 ))) 252 252 253 253 (% class="box" %) ... ... @@ -302,19 +302,18 @@ 302 302 ))) 303 303 304 304 ((( 305 - (% 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.** 306 306 ))) 307 307 308 308 ((( 309 309 //After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.// 310 310 311 - 312 312 313 313 ))) 314 314 315 -== **2.8 298 +== **2.8 Debug Connection** == 316 316 317 -=== **2.8.1 300 +=== **2.8.1 Check pkt-fwd running Log** === 318 318 319 319 320 320 //This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.// ... ... @@ -345,19 +345,18 @@ 345 345 ))) 346 346 347 347 331 +=== **2.8.2 Check gateway-rs Log** === 348 348 349 -=== **2.8.2 Check gateway-rs Log** === 350 350 351 - 352 352 //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.// 353 353 354 354 [[image:image-20220531175809-7.png]] 355 355 356 356 357 - (% 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. 358 358 359 359 360 -=== **2.8.3 342 +=== **2.8.3 View the public key address and animal name** === 361 361 362 362 363 363 (% class="box" %) ... ... @@ -381,10 +381,8 @@ 381 381 Hostpot key and animal name 382 382 383 383 366 +=== **2.8.4 Backup/Restor gateway-rs key** === 384 384 385 -=== **2.8.4 Backup/Restor gateway-rs key** === 386 - 387 - 388 388 ((( 389 389 //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.// 390 390 ))) ... ... @@ -393,9 +393,9 @@ 393 393 394 394 395 395 396 -== **2.9 376 +== **2.9 Forward the data to the other server** == 397 397 398 -=== **2.9.1 378 +=== **2.9.1 Introduction** === 399 399 400 400 401 401 ((( ... ... @@ -408,25 +408,23 @@ 408 408 409 409 ))) 410 410 411 -=== **2.9.2 391 +=== **2.9.2 Example** === 412 412 413 413 414 414 //The following takes The Things Network as another LoRaWAN server as an example.// 415 415 416 416 397 +==== **2.9.2.1 Step 1: Back to Semtech UDP page** ==== 417 417 418 -==== (% style="color:blue" %)**Step 1: Back to Semtech UDP page**(%%) ==== 419 419 420 - 421 421 [[image:image-20220531180002-10.png]] 422 422 423 423 Back to Semtech UDP page 424 424 425 425 405 +==== **2.9.2.2 Step 2: Configure the double server forwarding** ==== 426 426 427 -==== (% style="color:blue" %)**Step 2: Configure the double server forwarding**(%%) ==== 428 428 429 - 430 430 [[image:image-20220531180048-11.png]] 431 431 432 432 ... ... @@ -433,19 +433,17 @@ 433 433 //The user can configure the secondary server and then click the button of **Save&Apply**.// 434 434 435 435 436 -== **2.10 414 +== **2.10 Connect Full Hotspot to Helium** == 437 437 416 += **3. Use Dragino Sensors with Helium** = 438 438 439 439 440 -= **3. UseDraginoSensorswith Helium** =419 +== **3.1 How to add up user's end-node with Helium console** == 441 441 442 442 443 -== **3.1 Howto add upuser'send-node with Helium console** ==422 +=== **3.1.1 Step 1: Login the Helium console** === 444 444 445 445 446 -=== **3.1.1 Step 1: Login the Helium console** === 447 - 448 - 449 449 //User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]// 450 450 451 451 [[image:image-20220531180150-12.png]] ... ... @@ -453,10 +453,9 @@ 453 453 login Helium console 454 454 455 455 432 +=== **3.1.2 Step 2: Add up your end-node's key** === 456 456 457 -=== **3.1.2 Step 2: Add up your end-node's key** === 458 458 459 - 460 460 //User add up end-node's key from console ~-~->dervice// 461 461 462 462 [[image:image-20220531180224-13.png]] ... ... @@ -464,10 +464,9 @@ 464 464 To add a device 465 465 466 466 442 +=== **3.1.3 Step 3:Activate the end-node** === 467 467 468 -=== **3.1.3 Step 3: Activate the end-node** === 469 469 470 - 471 471 ((( 472 472 //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**// 473 473 ))) ... ... @@ -477,21 +477,19 @@ 477 477 end-node traffic. 478 478 479 479 454 +== **3.2 How to use decoder** == 480 480 481 -== **3.2 Howtouse decoder** ==456 +=== **3.2.1 Step 1:Users can create decoders on functions** === 482 482 483 -=== **3.2.1 Step 1: Users can create decoders on functions** === 484 484 485 - 486 486 [[image:image-20220531105325-3.png]] 487 487 488 488 Decoder. 489 489 490 490 464 +=== **3.2.2 Step 2:Add a decoder in functions and apply it to the specified label** === 491 491 492 -=== **3.2.2 Step 2: Add a decoder in functions and apply it to the specified label** === 493 493 494 - 495 495 [[image:image-20220526095629-6.png]] 496 496 497 497 ... ... @@ -500,22 +500,13 @@ 500 500 501 501 [[image:image-20220526100057-8.png||height="352" width="1133"]] 502 502 475 + 503 503 **//Add decoder complete.//** 504 504 505 505 479 +== **3.3 How to send a downlink to end device from Helium** == 506 506 507 -=== **3.2.3 Where is the decoder?** === 508 508 509 - 510 -[[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]] 511 - 512 -[[image:image-20220617140118-1.png||height="550" width="883"]] 513 - 514 - 515 - 516 -== **3.3 How to send a downlink to end device from Helium** == 517 - 518 - 519 519 ((( 520 520 //The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~:// 521 521 ))) ... ... @@ -530,7 +530,7 @@ 530 530 531 531 (% class="box" %) 532 532 ((( 533 - **01 00 00 3C ~-~-> AQAAPA==**496 +01 00 00 3C ~-~-> AQAAPA== 534 534 ))) 535 535 536 536 [[image:image-20220524171341-21.png]] ... ... @@ -538,12 +538,11 @@ 538 538 Downlink 539 539 540 540 504 +== **3.4 How to add integration to different IoT Servers** == 541 541 542 -== **3.4 How toadd integration to differentIoT Servers** ==506 +=== **3.4.1 TagoIO** === 543 543 544 -=== **3.4.1 TagoIO** === 545 545 546 - 547 547 **//The steps to add integration are very simple. Please see the following process.//** 548 548 549 549 ... ... @@ -584,10 +584,9 @@ 584 584 TagoIO. 585 585 586 586 549 +=== **3.4.2 Cayenne** === 587 587 588 -=== **3.4.2 Cayenne** === 589 589 590 - 591 591 //The process of creating devices is similar to Tago.// 592 592 593 593 [[image:image-20220526101616-18.png||height="456" width="1097"]] ... ... @@ -620,12 +620,11 @@ 620 620 Cayenne. 621 621 622 622 584 +== **3.5 Trouble Shooting** == 623 623 624 -== **3.5 Shooting** ==586 +=== **3.5.1 Trouble to Join Helium** === 625 625 626 -=== **3.5.1 Trouble to Join Helium** === 627 627 628 - 629 629 ((( 630 630 **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://** 631 631 ... ... @@ -643,11 +643,10 @@ 643 643 ((( 644 644 //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)// 645 645 646 - 647 647 648 648 ))) 649 649 650 -=== **3.5.2 609 +=== **3.5.2 Packet Loss for AU915 / US915 Band** === 651 651 652 652 653 653 ((( ... ... @@ -656,8 +656,6 @@ 656 656 657 657 ((( 658 658 //The reason for this problem is that the node does not lock the channel after joining the network.// 659 - 660 - 661 661 ))) 662 662 663 663 ((( ... ... @@ -671,19 +671,15 @@ 671 671 ))) 672 672 673 673 * ((( 674 - (% style="color:blue" %)**//AT Command: AT+CHE//**631 +//AT Command: AT+CHE// 675 675 ))) 676 676 677 677 * ((( 678 -// **Example:** (% style="color:#037691" %)**AT+CHE=2**(%%)635 +//Example:AT+CHE=1 ~/~/set channel mode to 1// 679 679 ))) 680 680 681 681 * ((( 682 -(% style="color:blue" %)**//Downlink Command: 0x24//** 683 - 684 - 685 - 686 - 639 +//Downlink Command: 0x24// 687 687 ))) 688 688 689 689 ((( ... ... @@ -690,14 +690,16 @@ 690 690 //Format: Command Code (0x24) followed by 1 bytes channel value.// 691 691 ))) 692 692 693 - 694 694 ((( 695 -//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.// 696 696 ))) 697 697 698 698 * ((( 699 -//**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 +))) 700 700 654 +* ((( 655 +//Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5// 701 701 702 702 703 703 )))
- image-20220617140118-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -55.5 KB - Content