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 ((( ... ... @@ -26,46 +26,38 @@ 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 35 += **2. Connect Data-Only Hotspot to Helium** = 39 39 40 -= **2. Connect Data-Only Hotspotto Helium** =37 +== **2.1 Prerequisites** == 41 41 42 -== **2.1 Prerequisites** == 43 43 44 - 45 45 * //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]// 46 46 42 +== **2.2 Step 1: Configure Frequency Band** == 47 47 48 48 49 - 50 -== **2.2 Step 1: Configure Frequency Band** == 51 - 52 - 53 53 //Each country has a requirement for frequency region. Choose the right one for your area.// 54 54 55 55 [[image:image-20220531175337-1.png]] 56 56 57 57 50 +== **2.3 Step 2: Download the Helium-gateway-rs** == 58 58 59 -== **2.3 Step 2: Download the Helium-gateway-rs** == 60 60 61 - 62 62 //Click Download Helium Server and the gateway will download the Helium-gateway-rs// 63 63 64 64 [[image:image-20220615150600-1.png||height="559" width="1045"]] 65 65 66 - 67 67 //**Start download to Helium-gateway-rs**// 68 68 59 + 69 69 [[image:image-20220615150627-2.png||height="598" width="1044"]] 70 70 71 71 //**Helium-gatewayrs download success**// ... ... @@ -76,7 +76,7 @@ 76 76 [[image:image-20220615150717-3.png||height="605" width="1039"]] 77 77 78 78 79 -== **2.4 70 +== **2.4 Step 3: Install the Helium-gateway-rs** == 80 80 81 81 82 82 //Click **Install Helium Server** to install gateway-rs.// ... ... @@ -85,14 +85,12 @@ 85 85 86 86 Install the Helium gateway-rs 87 87 88 - 89 89 (% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.** 90 90 91 91 82 +== **2.5 Step 4: Save&start the Helium Server** == 92 92 93 -== **2.5 Step 4: Save&start the Helium Server** == 94 94 95 - 96 96 //By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.// 97 97 98 98 [[image:image-20220615150903-5.png||height="592" width="1031"]] ... ... @@ -120,7 +120,7 @@ 120 120 121 121 == 2.7 Step 6: Onboarding Data-Only Hotspot == 122 122 123 -(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlinktowork.otherwise,thedownlink messageforLoRa won'twork.**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 125 //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.// 126 126 ... ... @@ -128,7 +128,7 @@ 128 128 129 129 130 130 ((( 131 - //**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.** 132 132 ))) 133 133 134 134 (% class="box" %) ... ... @@ -161,7 +161,7 @@ 161 161 162 162 163 163 ((( 164 - //**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.** 165 165 ))) 166 166 167 167 (% class="box" %) ... ... @@ -193,13 +193,13 @@ 193 193 ))) 194 194 195 195 ((( 196 - //We got the txn info from this step.//197 -\\ //**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above 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.** 198 198 199 199 200 -(% style="color:red" %) **Note: below are two commands, the command without ~-~-commit is the preview mode.**189 +(% style="color:red" %)Note: below are two commands, the command without ~-~-commit is the preview mode.** 201 201 202 - //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. 203 203 ))) 204 204 205 205 (% class="box" %) ... ... @@ -242,7 +242,7 @@ 242 242 ))) 243 243 244 244 ((( 245 - //**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. 246 246 ))) 247 247 248 248 (% class="box" %) ... ... @@ -297,24 +297,23 @@ 297 297 ))) 298 298 299 299 ((( 300 - **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. 301 301 ))) 302 302 303 303 ((( 304 - //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. 305 305 306 306 307 307 ))) 308 308 309 -== **2.8 Debug Connection**==298 +== 2.8 Debug Connection == 310 310 311 -=== **2.8.1 Check pkt-fwd running Log**===300 +=== 2.8.1 Check pkt-fwd running Log === 312 312 302 +This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors. 313 313 314 -//This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.// 315 - 316 316 ((( 317 - //Below logs shows the gateway receive two LoRaWAN packets.//305 +Below logs shows the gateway receive two LoRaWAN packets. 318 318 ))) 319 319 320 320 (% class="box" %) ... ... @@ -339,20 +339,19 @@ 339 339 ))) 340 340 341 341 342 -=== **2.8.2 Check gateway-rs Log**===330 +=== 2.8.2 Check gateway-rs Log === 343 343 332 +SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log. 344 344 345 -//SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.// 346 - 347 347 [[image:image-20220531175809-7.png]] 348 348 336 +Helium-gatewayrs log 349 349 350 350 **Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system. 351 351 352 352 353 -=== **2.8.3 View the public key address and animal name**===341 +=== 2.8.3 View the public key address and animal name === 354 354 355 - 356 356 (% class="box" %) 357 357 ((( 358 358 ((( ... ... @@ -374,87 +374,80 @@ 374 374 Hostpot key and animal name 375 375 376 376 377 -=== **2.8.4 Backup/Restor gateway-rs key**===364 +=== 2.8.4 Backup/Restor gateway-rs key === 378 378 379 379 ((( 380 - //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. 381 381 ))) 382 382 383 383 [[image:image-20220531175919-9.png]] 384 384 372 +Backup and restore key 385 385 386 386 387 -== **2.9 Forward the data to the other server**==375 +== 2.9 Forward the data to the other server == 388 388 389 -=== **2.9.1 Introduction**===377 +=== 2.9.1 Introduction === 390 390 391 - 392 392 ((( 393 - //The Dragino gateway has supports the double server settings.//380 +The Dragino gateway has supports the double server settings. 394 394 ))) 395 395 396 396 ((( 397 - //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. 398 398 399 399 400 400 ))) 401 401 402 -=== **2.9.2 Example**===389 +=== 2.9.2 Example === 403 403 391 +The following takes The Things Network as another LoRaWAN server as an example. 404 404 405 -//The following takes The Things Network as another LoRaWAN server as an example.// 406 406 394 +==== 2.9.2.1 Step 1: Back to Semtech UDP page ==== 407 407 408 -==== **2.9.2.1 Step 1: Back to Semtech UDP page** ==== 409 - 410 - 411 411 [[image:image-20220531180002-10.png]] 412 412 413 413 Back to Semtech UDP page 414 414 415 415 416 -==== **2.9.2.2 Step 2: Configure the double server forwarding**====401 +==== 2.9.2.2 Step 2: Configure the double server forwarding ==== 417 417 418 - 419 419 [[image:image-20220531180048-11.png]] 420 420 405 +Configure the double server 421 421 422 - //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. 423 423 424 424 425 -== **2.10 Connect Full Hotspot to Helium**==410 +== 2.10 Connect Full Hotspot to Helium == 426 426 427 -= **3. Use Dragino Sensors with Helium**=412 += 3. Use Dragino Sensors with Helium = 428 428 414 +== 3.1 How to add up user's end-node with Helium console == 429 429 430 -== **3.1Howto add upuser'send-node with Helium console**==416 +=== 3.1.1 Step 1: Login the Helium console === 431 431 418 +User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]] 432 432 433 -=== **3.1.1 Step 1: Login the Helium console** === 434 - 435 - 436 -//User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]// 437 - 438 438 [[image:image-20220531180150-12.png]] 439 439 440 440 login Helium console 441 441 442 442 443 -=== **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 === 444 444 427 +User add up end-node's key from console ~-~->dervice 445 445 446 -//User add up end-node's key from console ~-~->dervice// 447 - 448 448 [[image:image-20220531180224-13.png]] 449 449 450 450 To add a device 451 451 452 452 453 -=== **3.1.3 Step 3:Activate the end-node**===434 +=== 3.1.3 Step 3:Activate the end-node === 454 454 455 - 456 456 ((( 457 - //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** 458 458 ))) 459 459 460 460 [[image:image-20220531105239-2.png]] ... ... @@ -462,19 +462,17 @@ 462 462 end-node traffic. 463 463 464 464 465 -== **3.2 How to use decoder**==445 +== 3.2 How to use decoder == 466 466 467 -=== **3.2.1 Step 1:Users can create decoders on functions**===447 +=== 3.2.1 Step 1:Users can create decoders on functions === 468 468 469 - 470 470 [[image:image-20220531105325-3.png]] 471 471 472 472 Decoder. 473 473 474 474 475 -=== **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 === 476 476 477 - 478 478 [[image:image-20220526095629-6.png]] 479 479 480 480 ... ... @@ -483,28 +483,23 @@ 483 483 484 484 [[image:image-20220526100057-8.png||height="352" width="1133"]] 485 485 464 +Decoder. 486 486 487 - **//Add decoder complete.//**466 +Add decoder complete. 488 488 489 -=== **3.2.3 Where is the decoder?** === 490 490 491 - [[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 == 492 492 493 -[[image:image-20220617140118-1.png||height="550" width="883"]] 494 - 495 -== **3.3 How to send a downlink to end device from Helium** == 496 - 497 - 498 498 ((( 499 - //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: 500 500 ))) 501 501 502 502 ((( 503 - //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]] 504 504 ))) 505 505 506 506 ((( 507 - //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 508 508 ))) 509 509 510 510 (% class="box" %) ... ... @@ -517,56 +517,55 @@ 517 517 Downlink 518 518 519 519 520 -== **3.4 How to add integration to different IoT Servers**==493 +== 3.4 How to add integration to different IoT Servers == 521 521 522 -=== **3.4.1 TagoIO**===495 +=== 3.4.1 TagoIO === 523 523 497 +The steps to add integration are very simple. Please see the following process. 524 524 525 -**//The steps to add integration are very simple. Please see the following process.//** 526 - 527 - 528 528 [[image:image-20220526102429-23.png||height="630" width="1198"]] 529 529 501 +TagoIO. 530 530 531 531 532 - **//Generate the authorization code and then copy it.//**504 +Generate the authorization code and then copy it. 533 533 534 - 535 535 [[image:image-20220526100452-10.png||height="314" width="1188"]] 536 536 508 +TagoIO. 537 537 538 538 539 - //**Apply Integration to Label.**//511 +Apply Integration to Label. 540 540 541 - 542 542 [[image:image-20220526100802-13.png]] 543 543 544 544 516 +TagoIO. 545 545 518 + 546 546 [[image:image-20220526100927-14.png]] 547 547 521 +TagoIO. 548 548 549 549 550 - **//Click LoRaWAN Helium,select the device.//**524 +Click LoRaWAN Helium,select the device. 551 551 552 - 553 553 [[image:image-20220526101215-15.png||height="599" width="1117"]] 554 554 528 +TagoIO. 555 555 556 556 557 - **//Fill in DEVEUI and create my device.//**531 +Fill in DEVEUI and create my device. 558 558 559 - 560 560 [[image:image-20220526101419-16.png]] 561 561 562 562 TagoIO. 563 563 564 564 565 -=== **3.4.2 Cayenne**===538 +=== 3.4.2 Cayenne === 566 566 540 +The process of creating devices is similar to Tago. 567 567 568 -//The process of creating devices is similar to Tago.// 569 - 570 570 [[image:image-20220526101616-18.png||height="456" width="1097"]] 571 571 572 572 Cayenne. ... ... @@ -597,83 +597,78 @@ 597 597 Cayenne. 598 598 599 599 600 -== **3.5 Trouble Shooting**==572 +== 3.5 Trouble Shooting == 601 601 602 -=== **3.5.1 Trouble to Join Helium**===574 +=== 3.5.1 Trouble to Join Helium === 603 603 604 - 605 605 ((( 606 -**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://** 607 - 608 - 577 +Assume the device is powered correctly. If you don't see data in Helium. The possibilities are: 609 609 ))) 610 610 611 611 ((( 612 - //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) 613 613 ))) 614 614 615 615 ((( 616 - //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) 617 617 ))) 618 618 619 619 ((( 620 - //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) 621 621 622 622 623 623 ))) 624 624 625 -=== **3.5.2 Packet Loss for AU915 / US915 Band**===594 +=== 3.5.2 Packet Loss for AU915 / US915 Band === 626 626 627 - 628 628 ((( 629 - //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. 630 630 ))) 631 631 632 632 ((( 633 - //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. 634 634 ))) 635 635 636 636 ((( 637 -**Solution:** 638 - 639 - 605 +Solution: 640 640 ))) 641 641 642 642 ((( 643 - //(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. 644 644 ))) 645 645 646 646 * ((( 647 - //AT Command: AT+CHE//613 +AT Command: AT+CHE 648 648 ))) 649 649 650 650 * ((( 651 - //Example:**AT+CHE=2**~/~/set channel mode to 1//617 +Example:AT+CHE=1 ~/~/set channel mode to 1 652 652 ))) 653 653 654 654 * ((( 655 - //Downlink Command: 0x24//621 +Downlink Command: 0x24 656 656 ))) 657 657 658 658 ((( 659 - //Format: Command Code (0x24) followed by 1 bytes channel value.//625 +Format: Command Code (0x24) followed by 1 bytes channel value. 660 660 ))) 661 661 662 662 ((( 663 - //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. 664 664 ))) 665 665 666 666 * ((( 667 -//Example 1: Downlink Payload: **0x2402** ~/~/ set channel mode to 2// 633 +Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1 634 +))) 668 668 669 - 670 - 636 +* ((( 637 +Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5 671 671 ))) 672 672 673 673 ((( 674 - //(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. 675 675 ))) 676 676 677 677 ((( 678 - //The latest firmware for end node will have this bug fixed.//645 +The latest firmware for end node will have this bug fixed. 679 679 )))
- image-20220617140118-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -55.5 KB - Content