<
From version < 88.11 >
edited by Xiaoling
on 2022/07/23 15:11
To version < 94.1 >
edited by Edwin Chen
on 2022/09/05 20:07
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -30,8 +30,6 @@
30 30  
31 31  * //The frequencies currently available are CN470/EU868/US915/AU915//
32 32  
33 -
34 -
35 35  (% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]**
36 36  
37 37  
... ... @@ -72,6 +72,7 @@
72 72  [[image:image-20220615150717-3.png||height="605" width="1039"]]
73 73  
74 74  
73 +
75 75  == **2.4  Step 3: Install the Helium-gateway-rs** ==
76 76  
77 77  
... ... @@ -91,9 +91,11 @@
91 91  
92 92  //By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
93 93  
93 +
94 94  [[image:image-20220615150903-5.png||height="592" width="1031"]]
95 95  
96 96  
97 +
97 97  //Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.//
98 98  
99 99  [[image:image-20220615151057-6.png||height="580" width="1026"]]
... ... @@ -128,7 +128,7 @@
128 128  
129 129  
130 130  (((
131 -(% 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.**//
132 +(% 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.**//
132 132  )))
133 133  
134 134  (% class="box" %)
... ... @@ -155,6 +155,7 @@
155 155  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
156 156  )))
157 157  
159 +
158 158  (((
159 159  (% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.**
160 160  )))
... ... @@ -162,7 +162,7 @@
162 162  
163 163  
164 164  (((
165 -(% 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.**//
167 +(% 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.**//
166 166  )))
167 167  
168 168  (% class="box" %)
... ... @@ -198,7 +198,7 @@
198 198  
199 199  
200 200  
201 -(% 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.**//
203 +(% 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.**//
202 202  
203 203  
204 204  (% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.**
... ... @@ -249,7 +249,7 @@
249 249  (((
250 250  
251 251  
252 -(% style="color:red" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//
254 +(% style="color:blue" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//
253 253  )))
254 254  
255 255  (% class="box" %)
... ... @@ -303,6 +303,7 @@
303 303  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
304 304  )))
305 305  
308 +
306 306  (((
307 307  (% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.**
308 308  )))
... ... @@ -359,6 +359,7 @@
359 359  (% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
360 360  
361 361  
365 +
362 362  === **2.8.3  View the public key address and animal name** ===
363 363  
364 364  
... ... @@ -407,6 +407,7 @@
407 407  (((
408 408  //Users can back to the page of Semtech UDP to configure other server settings.//
409 409  
414 +
410 410  
411 411  )))
412 412  
... ... @@ -435,6 +435,7 @@
435 435  //The user can configure the secondary server and then click the button of **Save&Apply**.//
436 436  
437 437  
443 +
438 438  == **2.10  Connect Full Hotspot to Helium** ==
439 439  
440 440  
... ... @@ -625,9 +625,31 @@
625 625  
626 626  == **3.5  Trouble Shooting** ==
627 627  
628 -=== **3.5.1  Trouble to Join Helium** ===
629 629  
635 +=== **3.5.1 Data-Only Hotspot is not connecting to Helium console** ===
630 630  
637 +
638 +//**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
639 +
640 +
641 +1). The hotspot does not finish the onboarding to the helium blockchain.
642 +
643 + 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.
644 +
645 +
646 +=== **3.5.2 End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ** ===
647 +
648 +
649 +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.
650 +
651 +
652 +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]]
653 +
654 +
655 +
656 +=== **3.5.3  Trouble to Join Helium** ===
657 +
658 +
631 631  (((
632 632  **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
633 633  
... ... @@ -645,11 +645,10 @@
645 645  (((
646 646  //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)//
647 647  
648 -
649 649  
650 650  )))
651 651  
652 -=== **3.5.2  Packet Loss for AU915 / US915 Band** ===
679 +=== **3.5.4  Packet Loss for AU915 / US915 Band** ===
653 653  
654 654  
655 655  (((
... ... @@ -663,7 +663,7 @@
663 663  )))
664 664  
665 665  (((
666 -**Solution:**
693 +(% style="color:red" %)**Solution:**
667 667  
668 668  
669 669  )))
... ... @@ -683,8 +683,6 @@
683 683  * (((
684 684  (% style="color:blue" %)**//Downlink Command: 0x24//**
685 685  
686 -
687 -
688 688  
689 689  )))
690 690  
... ... @@ -700,7 +700,6 @@
700 700  * (((
701 701  //**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2//
702 702  
703 -
704 704  
705 705  )))
706 706  
... ... @@ -710,4 +710,12 @@
710 710  
711 711  (((
712 712  //The latest firmware for end node will have this bug fixed.//
737 +
738 +
739 +=== **3.5.5  ADR doesn't work in EU868 band.** ===
740 +
741 +See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]]
742 +
743 +
744 +
713 713  )))
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0