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,17 +49,16 @@ 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"]] 59 59 60 - 61 61 //**Start download to Helium-gateway-rs**// 62 62 59 + 63 63 [[image:image-20220615150627-2.png||height="598" width="1044"]] 64 64 65 65 //**Helium-gatewayrs download success**// ... ... @@ -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" %) ... ... @@ -192,17 +192,13 @@ 192 192 ))) 193 193 194 194 ((( 195 -//We got the txn info from this step.// 185 +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 189 +(% style="color:red" %)Note: below are two commands, the command without ~-~-commit is the preview mode.** 198 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 -(% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.** 203 - 204 - 205 -//Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.// 191 +Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain. 206 206 ))) 207 207 208 208 (% class="box" %) ... ... @@ -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,25 +302,23 @@ 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 - //After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//293 +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 302 +This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors. 319 319 320 -//This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.// 321 - 322 322 ((( 323 - //Below logs shows the gateway receive two LoRaWAN packets.//305 +Below logs shows the gateway receive two LoRaWAN packets. 324 324 ))) 325 325 326 326 (% class="box" %) ... ... @@ -345,21 +345,19 @@ 345 345 ))) 346 346 347 347 330 +=== 2.8.2 Check gateway-rs Log === 348 348 349 - ===**2.8.2Checkgateway-rsLog**===332 +SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log. 350 350 351 - 352 -//SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.// 353 - 354 354 [[image:image-20220531175809-7.png]] 355 355 336 +Helium-gatewayrs log 356 356 357 - (% style="color:red" %)**Note**:**logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**338 +**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**===341 +=== 2.8.3 View the public key address and animal name === 361 361 362 - 363 363 (% class="box" %) 364 364 ((( 365 365 ((( ... ... @@ -381,90 +381,80 @@ 381 381 Hostpot key and animal name 382 382 383 383 364 +=== 2.8.4 Backup/Restor gateway-rs key === 384 384 385 -=== **2.8.4 Backup/Restor gateway-rs key** === 386 - 387 - 388 388 ((( 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.//367 +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 ))) 391 391 392 392 [[image:image-20220531175919-9.png]] 393 393 372 +Backup and restore key 394 394 395 395 396 -== **2.9**==375 +== 2.9 Forward the data to the other server == 397 397 398 -=== **2.9.1**===377 +=== 2.9.1 Introduction === 399 399 400 - 401 401 ((( 402 - //The Dragino gateway has supports the double server settings.//380 +The Dragino gateway has supports the double server settings. 403 403 ))) 404 404 405 405 ((( 406 - //Users can back to the page of Semtech UDP to configure other server settings.//384 +Users can back to the page of Semtech UDP to configure other server settings. 407 407 408 408 409 409 ))) 410 410 411 -=== **2.9.2**===389 +=== 2.9.2 Example === 412 412 391 +The following takes The Things Network as another LoRaWAN server as an example. 413 413 414 -//The following takes The Things Network as another LoRaWAN server as an example.// 415 415 394 +==== 2.9.2.1 Step 1: Back to Semtech UDP page ==== 416 416 417 - 418 -==== (% style="color:blue" %)**Step 1: Back to Semtech UDP page**(%%) ==== 419 - 420 - 421 421 [[image:image-20220531180002-10.png]] 422 422 423 423 Back to Semtech UDP page 424 424 425 425 426 -==== (%style="color:blue" %)**Step 2: Configure the double server forwarding**(%%)====401 +==== 2.9.2.2 Step 2: Configure the double server forwarding ==== 427 427 428 - 429 429 [[image:image-20220531180048-11.png]] 430 430 405 +Configure the double server 431 431 432 - //The user can configure the secondary server and then click the button of**Save&Apply**.//407 +The user can configure the secondary server and then click the button of Save&Apply. 433 433 434 434 435 -== **2.10 Connect Full Hotspot to Helium**==410 +== 2.10 Connect Full Hotspot to Helium == 436 436 437 -= **3. Use Dragino Sensors with Helium**=412 += 3. Use Dragino Sensors with Helium = 438 438 414 +== 3.1 How to add up user's end-node with Helium console == 439 439 440 -== **3.1Howto add upuser'send-node with Helium console**==416 +=== 3.1.1 Step 1: Login the Helium console === 441 441 418 +User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]] 442 442 443 -=== **3.1.1 Step 1: Login the Helium console** === 444 - 445 - 446 -//User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]// 447 - 448 448 [[image:image-20220531180150-12.png]] 449 449 450 450 login Helium console 451 451 452 452 453 -=== **3.1.2 Step 2: Add up your end-node's key**===425 +=== 3.1.2 Step 2: Add up your end-node's key === 454 454 427 +User add up end-node's key from console ~-~->dervice 455 455 456 -//User add up end-node's key from console ~-~->dervice// 457 - 458 458 [[image:image-20220531180224-13.png]] 459 459 460 460 To add a device 461 461 462 462 463 -=== **3.1.3 Step 3:Activate the end-node**===434 +=== 3.1.3 Step 3:Activate the end-node === 464 464 465 - 466 466 ((( 467 - //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**//437 +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** 468 468 ))) 469 469 470 470 [[image:image-20220531105239-2.png]] ... ... @@ -472,19 +472,17 @@ 472 472 end-node traffic. 473 473 474 474 475 -== **3.2 How to use decoder**==445 +== 3.2 How to use decoder == 476 476 477 -=== **3.2.1 Step 1:Users can create decoders on functions**===447 +=== 3.2.1 Step 1:Users can create decoders on functions === 478 478 479 - 480 480 [[image:image-20220531105325-3.png]] 481 481 482 482 Decoder. 483 483 484 484 485 -=== **3.2.2 Step 2:Add a decoder in functions and apply it to the specified label**===454 +=== 3.2.2 Step 2:Add a decoder in functions and apply it to the specified label === 486 486 487 - 488 488 [[image:image-20220526095629-6.png]] 489 489 490 490 ... ... @@ -493,28 +493,23 @@ 493 493 494 494 [[image:image-20220526100057-8.png||height="352" width="1133"]] 495 495 464 +Decoder. 496 496 497 - **//Add decoder complete.//**466 +Add decoder complete. 498 498 499 -=== **3.2.3 Where is the decoder?** === 500 500 501 - [[console-decoders/Draginoatmaster·helium/console-decoders· GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]469 +== 3.3 How to send a downlink to end device from Helium == 502 502 503 -[[image:image-20220617140118-1.png||height="550" width="883"]] 504 - 505 -== **3.3 How to send a downlink to end device from Helium** == 506 - 507 - 508 508 ((( 509 - //The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://472 +The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example: 510 510 ))) 511 511 512 512 ((( 513 - //The Downlink command comes from this link:[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]//476 +The Downlink command comes from this link:[[End Device Downlink Command>>End Device AT Commands and Downlink Command]] 514 514 ))) 515 515 516 516 ((( 517 - //Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds//480 +Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds 518 518 ))) 519 519 520 520 (% class="box" %) ... ... @@ -527,56 +527,55 @@ 527 527 Downlink 528 528 529 529 530 -== **3.4 How to add integration to different IoT Servers**==493 +== 3.4 How to add integration to different IoT Servers == 531 531 532 -=== **3.4.1 TagoIO**===495 +=== 3.4.1 TagoIO === 533 533 497 +The steps to add integration are very simple. Please see the following process. 534 534 535 -**//The steps to add integration are very simple. Please see the following process.//** 536 - 537 - 538 538 [[image:image-20220526102429-23.png||height="630" width="1198"]] 539 539 501 +TagoIO. 540 540 541 541 542 - **//Generate the authorization code and then copy it.//**504 +Generate the authorization code and then copy it. 543 543 544 - 545 545 [[image:image-20220526100452-10.png||height="314" width="1188"]] 546 546 508 +TagoIO. 547 547 548 548 549 - //**Apply Integration to Label.**//511 +Apply Integration to Label. 550 550 551 - 552 552 [[image:image-20220526100802-13.png]] 553 553 554 554 516 +TagoIO. 555 555 518 + 556 556 [[image:image-20220526100927-14.png]] 557 557 521 +TagoIO. 558 558 559 559 560 - **//Click LoRaWAN Helium,select the device.//**524 +Click LoRaWAN Helium,select the device. 561 561 562 - 563 563 [[image:image-20220526101215-15.png||height="599" width="1117"]] 564 564 528 +TagoIO. 565 565 566 566 567 - **//Fill in DEVEUI and create my device.//**531 +Fill in DEVEUI and create my device. 568 568 569 - 570 570 [[image:image-20220526101419-16.png]] 571 571 572 572 TagoIO. 573 573 574 574 575 -=== **3.4.2 Cayenne**===538 +=== 3.4.2 Cayenne === 576 576 540 +The process of creating devices is similar to Tago. 577 577 578 -//The process of creating devices is similar to Tago.// 579 - 580 580 [[image:image-20220526101616-18.png||height="456" width="1097"]] 581 581 582 582 Cayenne. ... ... @@ -607,83 +607,78 @@ 607 607 Cayenne. 608 608 609 609 610 -== **3.5 Trouble Shooting**==572 +== 3.5 Trouble Shooting == 611 611 612 -=== **3.5.1 Trouble to Join Helium**===574 +=== 3.5.1 Trouble to Join Helium === 613 613 614 - 615 615 ((( 616 -**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://** 617 - 618 - 577 +Assume the device is powered correctly. If you don't see data in Helium. The possibilities are: 619 619 ))) 620 620 621 621 ((( 622 - //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)//581 +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) 623 623 ))) 624 624 625 625 ((( 626 - //2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)//585 +2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches) 627 627 ))) 628 628 629 629 ((( 630 - //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)//589 +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) 631 631 632 632 633 633 ))) 634 634 635 -=== **3.5.2 Packet Loss for AU915 / US915 Band**===594 +=== 3.5.2 Packet Loss for AU915 / US915 Band === 636 636 637 - 638 638 ((( 639 - //The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.//597 +The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different. 640 640 ))) 641 641 642 642 ((( 643 - //The reason for this problem is that the node does not lock the channel after joining the network.//601 +The reason for this problem is that the node does not lock the channel after joining the network. 644 644 ))) 645 645 646 646 ((( 647 -**Solution:** 648 - 649 - 605 +Solution: 650 650 ))) 651 651 652 652 ((( 653 - //(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.//609 +(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. 654 654 ))) 655 655 656 656 * ((( 657 - //AT Command: AT+CHE//613 +AT Command: AT+CHE 658 658 ))) 659 659 660 660 * ((( 661 - //Example:**AT+CHE=2**~/~/set channel mode to 1//617 +Example:AT+CHE=1 ~/~/set channel mode to 1 662 662 ))) 663 663 664 664 * ((( 665 - //Downlink Command: 0x24//621 +Downlink Command: 0x24 666 666 ))) 667 667 668 668 ((( 669 - //Format: Command Code (0x24) followed by 1 bytes channel value.//625 +Format: Command Code (0x24) followed by 1 bytes channel value. 670 670 ))) 671 671 672 672 ((( 673 - //If the downlink payload=0x2402, it means set channel mode touse sub-band 2, while type code is 24.//629 +If the downlink payload=2401, it means set channel mode to 1, while type code is 24. 674 674 ))) 675 675 676 676 * ((( 677 -//Example 1: Downlink Payload: **0x2402** ~/~/ set channel mode to 2// 633 +Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1 634 +))) 678 678 679 - 680 - 636 +* ((( 637 +Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5 681 681 ))) 682 682 683 683 ((( 684 - //(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.//641 +(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. 685 685 ))) 686 686 687 687 ((( 688 - //The latest firmware for end node will have this bug fixed.//645 +The latest firmware for end node will have this bug fixed. 689 689 )))
- image-20220617140118-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -55.5 KB - Content