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)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.Xiaoling - Content
-
... ... @@ -41,6 +41,7 @@ 41 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 + 44 44 == **2.2 Step 1: Configure Frequency Band** == 45 45 46 46 ... ... @@ -70,7 +70,6 @@ 70 70 [[image:image-20220615150717-3.png||height="605" width="1039"]] 71 71 72 72 73 - 74 74 == **2.4 Step 3: Install the Helium-gateway-rs** == 75 75 76 76 ... ... @@ -90,11 +90,9 @@ 90 90 91 91 //By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.// 92 92 93 - 94 94 [[image:image-20220615150903-5.png||height="592" width="1031"]] 95 95 96 96 97 - 98 98 //Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.// 99 99 100 100 [[image:image-20220615151057-6.png||height="580" width="1026"]] ... ... @@ -156,7 +156,6 @@ 156 156 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+ 157 157 ))) 158 158 159 - 160 160 ((( 161 161 (% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.** 162 162 ))) ... ... @@ -305,7 +305,6 @@ 305 305 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+ 306 306 ))) 307 307 308 - 309 309 ((( 310 310 (% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.** 311 311 ))) ... ... @@ -362,7 +362,6 @@ 362 362 (% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.** 363 363 364 364 365 - 366 366 === **2.8.3 View the public key address and animal name** === 367 367 368 368 ... ... @@ -411,7 +411,6 @@ 411 411 ((( 412 412 //Users can back to the page of Semtech UDP to configure other server settings.// 413 413 414 - 415 415 416 416 ))) 417 417 ... ... @@ -440,7 +440,6 @@ 440 440 //The user can configure the secondary server and then click the button of **Save&Apply**.// 441 441 442 442 443 - 444 444 == **2.10 Connect Full Hotspot to Helium** == 445 445 446 446 ... ... @@ -485,12 +485,7 @@ 485 485 end-node traffic. 486 486 487 487 488 -=== **3.1.4 Check Raw Payload for End Node** === 489 489 490 -Users can check what the end node has uplinked by checking the raw payload. as below: 491 - 492 - 493 - 494 494 == **3.2 How to use decoder** == 495 495 496 496 === **3.2.1 Step 1: Users can create decoders on functions** === ... ... @@ -636,31 +636,9 @@ 636 636 637 637 == **3.5 Trouble Shooting** == 638 638 627 +=== **3.5.1 Trouble to Join Helium** === 639 639 640 -=== **3.5.1 Data-Only Hotspot is not connecting to Helium console** === 641 641 642 - 643 -//**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**// 644 - 645 - 646 -1). The hotspot does not finish the onboarding to the helium blockchain. 647 - 648 - after the 23 version of the gateway-rs, Helium requests the user to onboarding the devices to the blockchain, otherwise, your devices can't connect to the helium console. ~-~--> Please refer to [[Step 2.7>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Helium/#H2.7A0Step6:OnboardingData-OnlyHotspot]] to do it. 649 - 650 - 651 -=== **3.5.2 End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ** === 652 - 653 - 654 -Make sure your blockchain region is the same as your hotspot settings. For example, as below, the blockchain is CN region, and software is configure to EU. The hotspot is able to get the OTAA Join Request from End Device on EU region. but due to block chain is CN region, Server will send the Join -Accept in CN region, so end device can't get the OTAA Join Accept. 655 - 656 - 657 -For example, if you are in USA, you have to use the US915 frequency plan. More frequency plans details on the helium network: [[https:~~/~~/docs.helium.com/lorawan-on-helium/frequency-plans>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans]] 658 - 659 - 660 - 661 -=== **3.5.3 Trouble to Join Helium** === 662 - 663 - 664 664 ((( 665 665 **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://** 666 666 ... ... @@ -678,10 +678,11 @@ 678 678 ((( 679 679 //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)// 680 680 647 + 681 681 682 682 ))) 683 683 684 -=== **3.5. 4Packet Loss for AU915 / US915 Band** ===651 +=== **3.5.2 Packet Loss for AU915 / US915 Band** === 685 685 686 686 687 687 ((( ... ... @@ -739,12 +739,4 @@ 739 739 740 740 ((( 741 741 //The latest firmware for end node will have this bug fixed.// 742 - 743 - 744 -=== **3.5.5 ADR doesn't work in EU868 band.** === 745 - 746 -See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]] 747 - 748 - 749 - 750 750 )))