Changes for page Notes for Helium

Last modified by Edwin Chen on 2024/03/25 08:22
<
From version < 88.7 >
edited by Xiaoling
on 2022/07/23 14:52
To version < 83.1 >
edited by Kilight Cao
on 2022/06/15 15:37
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Kilight
Content
... ... @@ -1,4 +1,4 @@
1 -**~ Table of Contents:**
1 +**~ Contents:**
2 2  
3 3  {{toc/}}
4 4  
... ... @@ -5,11 +5,10 @@
5 5  
6 6  
7 7  
8 -= **1.  Use Dragino Gateways/Hotspots with Helium** =
8 += **1. Use Dragino Gateways/Hotspots with Helium** =
9 9  
10 -== **1.1  Support Models** ==
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 Hotspot to 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  Step 1: Configure Frequency Band** ==
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  Step 3: Install the Helium-gateway-rs** ==
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-Only Hotspot** ==
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  Debug Connection** ==
298 +== **2.8 Debug Connection** ==
316 316  
317 -=== **2.8.1  Check pkt-fwd running Log** ===
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  View the public key address and animal name** ===
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  Forward the data to the other server** ==
376 +== **2.9 Forward the data to the other server** ==
397 397  
398 -=== **2.9.1  Introduction** ===
378 +=== **2.9.1 Introduction** ===
399 399  
400 400  
401 401  (((
... ... @@ -408,22 +408,21 @@
408 408  
409 409  )))
410 410  
411 -=== **2.9.2  Example** ===
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  
426 -==== (% style="color:blue" %)**Step 2: Configure the double server forwarding**(%%) ====
405 +==== **2.9.2.2 Step 2: Configure the double server forwarding** ====
427 427  
428 428  
429 429  [[image:image-20220531180048-11.png]]
... ... @@ -496,12 +496,7 @@
496 496  
497 497  **//Add decoder complete.//**
498 498  
499 -=== **3.2.3 Where is the decoder？** ===
500 500  
501 -[[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
502 -
503 -[[image:image-20220617140118-1.png||height="550" width="883"]]
504 -
505 505  == **3.3 How to send a downlink to end device from Helium** ==
506 506  
507 507  
... ... @@ -658,7 +658,7 @@
658 658  )))
659 659  
660 660  * (((
661 -//Example:**AT+CHE=2** ~/~/set channel mode to 1//
635 +//Example:AT+CHE=1 ~/~/set channel mode to 1//
662 662  )))
663 663  
664 664  * (((
... ... @@ -670,12 +670,15 @@
670 670  )))
671 671  
672 672  (((
673 -//If the downlink payload=0x2402, it means set channel mode to use 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.//
674 674  )))
675 675  
676 676  * (((
677 -//Example 1: Downlink Payload: **0x2402** ~/~/ set channel mode to 2//
651 +//Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1//
652 +)))
678 678  
654 +* (((
655 +//Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5//
679 679  
680 680  
681 681  )))
image-20220617140118-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -55.5 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0