Changes for page Notes for Helium

Last modified by Edwin Chen on 2024/03/25 08:22
<
From version < 90.1 >
edited by Xiaoye
on 2022/08/17 10:28
To version < 99.7 >
edited by Xiaoling
on 2023/04/21 16:46
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoye
1 +XWiki.Xiaoling
Content
... ... @@ -5,26 +5,26 @@
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 12  
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.//
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  (((
16 -//Dragino has different gateway models that support different types.//
16 +Dragino has different gateway models that support different types.
17 17  )))
18 18  
19 -(% border="1" style="background-color:#ffffcc; width:510px" %)
20 -|(% colspan="4" style="width:589px" %)(% style="color:green" %)**Dragino Hotspots for Helium**
21 -|(% style="color:green; width:132px" %)**Model**|(% style="color:green; width:126px" %)**Hotspot Types**|(% style="color:green; width:121px" %)**Mining Ability**|(% style="color:green; width:203px" %)**Configure Instruction**
19 +(% border="1" style="background-color:#f2f2f2; width:510px" %)
20 +|(% colspan="4" style="width:589px;background-color:#D9E2F3;color:#0070C0" %)**Dragino Hotspots for Helium**
21 +|(% style="color:#0070C0; width:132px" %)**Model**|(% style="color:#0070C0; width:126px" %)**Hotspot Types**|(% style="color:#0070C0; width:121px" %)**Mining Ability**|(% style="color:#0070C0; width:203px" %)**Configure Instruction**
22 22  |(% style="width:132px" %)(((
23 23  [[LPS8>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]], [[DLOS8>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]],
24 24  
25 25  [[LG308>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]],[[LIG16>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]]
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.A0ConnectData-OnlyHotspottoHelium"]]
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]]
26 +)))|(% 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.A0ConnectData-OnlyHotspottoHelium"]]
27 +|(% style="width:132px" %)[[HP0D>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/195-hp0d.html]]|(% 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 29  (% style="color:blue" %)**Frequencies on the Helium Network**
30 30  
... ... @@ -33,16 +33,15 @@
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  
36 += 2.  Connect Data-Only Hotspot to Helium =
36 36  
37 -= **2.  Connect Data-Only Hotspot to Helium** =
38 +== 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 44  
45 -== **2.2  Step 1: Configure Frequency Band** ==
44 +== 2.2  Step 1: Configure Frequency Band ==
46 46  
47 47  
48 48  //Each country has a requirement for frequency region. Choose the right one for your area.//
... ... @@ -50,12 +50,12 @@
50 50  [[image:image-20220531175337-1.png]]
51 51  
52 52  
52 +== 2.3  Step 2: Download the Helium-gateway-rs ==
53 53  
54 -== **2.3  Step 2: Download the Helium-gateway-rs** ==
55 55  
56 -
57 57  //Click Download Helium Server and the gateway will download the Helium-gateway-rs//
58 58  
57 +
59 59  [[image:image-20220615150600-1.png||height="559" width="1045"]]
60 60  
61 61  
... ... @@ -71,10 +71,9 @@
71 71  [[image:image-20220615150717-3.png||height="605" width="1039"]]
72 72  
73 73  
73 +== 2.4  Step 3: Install the Helium-gateway-rs ==
74 74  
75 -== **2.4  Step 3: Install the Helium-gateway-rs** ==
76 76  
77 -
78 78  //Click **Install Helium Server** to install gateway-rs.//
79 79  
80 80  [[image:image-20220615150734-4.png||height="619" width="1035"]]
... ... @@ -85,10 +85,9 @@
85 85  (% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
86 86  
87 87  
86 +== 2.5  Step 4: Save&start the Helium Server ==
88 88  
89 -== **2.5  Step 4: Save&start the Helium Server** ==
90 90  
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  
94 94  
... ... @@ -101,10 +101,9 @@
101 101  [[image:image-20220615151057-6.png||height="580" width="1026"]]
102 102  
103 103  
101 +== 2.6  Step 5: Check Gateway Connection before onboarding ==
104 104  
105 -== **2.6  Step 5: Check Gateway Connection before onboarding** ==
106 106  
107 -
108 108  //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.//
109 109  
110 110  (((
... ... @@ -117,10 +117,9 @@
117 117  (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
118 118  
119 119  
116 +== 2.7  Step 6: Onboarding Data-Only Hotspot ==
120 120  
121 -== **2.7  Step 6: Onboarding Data-Only Hotspot** ==
122 122  
123 -
124 124  (% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**
125 125  
126 126  
... ... @@ -314,13 +314,12 @@
314 314  (((
315 315  //After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//
316 316  
317 -
318 318  
319 319  )))
320 320  
321 -== **2.8  Debug Connection** ==
315 +== 2.8  Debug Connection ==
322 322  
323 -=== **2.8.1  Check pkt-fwd running Log** ===
317 +=== 2.8.1  Check pkt-fwd running Log ===
324 324  
325 325  
326 326  //This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
... ... @@ -351,10 +351,9 @@
351 351  )))
352 352  
353 353  
348 +=== 2.8.2  Check gateway-rs Log ===
354 354  
355 -=== **2.8.2  Check gateway-rs Log** ===
356 356  
357 -
358 358  //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
359 359  
360 360  [[image:image-20220531175809-7.png]]
... ... @@ -363,10 +363,9 @@
363 363  (% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
364 364  
365 365  
359 +=== 2.8.3  View the public key address and animal name ===
366 366  
367 -=== **2.8.3  View the public key address and animal name** ===
368 368  
369 -
370 370  (% class="box" %)
371 371  (((
372 372  (((
... ... @@ -388,10 +388,9 @@
388 388  Hostpot key and animal name
389 389  
390 390  
383 +=== 2.8.4  Backup/Restor gateway-rs key ===
391 391  
392 -=== **2.8.4  Backup/Restor gateway-rs key** ===
393 393  
394 -
395 395  (((
396 396  //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.//
397 397  )))
... ... @@ -399,12 +399,24 @@
399 399  [[image:image-20220531175919-9.png]]
400 400  
401 401  
393 +=== 2.8.5  How to manually download helium gateway-rs via SSH access to the gateway Linux console ===
402 402  
403 -== **2.9  Forward the data to the other server** ==
404 404  
405 -=== **2.9.1  Introduction** ===
396 +(% class="box infomessage" %)
397 +(((
398 +cd /tmp;wget -O helium-gateway-rs-dragino.ipk [[https:~~/~~/github.com/helium/gateway-rs/releases/download/v1.0.0-alpha.33/helium-gateway-v1.0.0-alpha.33-dragino.ipk>>https://github.com/helium/gateway-rs/releases/download/v1.0.0-alpha.33/helium-gateway-v1.0.0-alpha.33-dragino.ipk]]
406 406  
400 +opkg install helium-gateway-rs-dragino.ipk
401 +)))
407 407  
403 +[[image:image-20230320141404-1.png]]
404 +
405 +
406 +== 2.9  Forward the data to the other server ==
407 +
408 +=== 2.9.1  Introduction ===
409 +
410 +
408 408  (((
409 409  //The Dragino gateway has supports the double server settings.//
410 410  )))
... ... @@ -412,11 +412,10 @@
412 412  (((
413 413  //Users can back to the page of Semtech UDP to configure other server settings.//
414 414  
415 -
416 416  
417 417  )))
418 418  
419 -=== **2.9.2  Example** ===
421 +=== 2.9.2  Example ===
420 420  
421 421  
422 422  //The following takes The Things Network as another LoRaWAN server as an example.//
... ... @@ -441,20 +441,17 @@
441 441  //The user can configure the secondary server and then click the button of **Save&Apply**.//
442 442  
443 443  
446 +== 2.10  Connect Full Hotspot to Helium ==
444 444  
445 -== **2.10  Connect Full Hotspot to Helium** ==
446 446  
447 447  
450 += 3.  Use Dragino Sensors with Helium =
448 448  
449 -= **3.  Use Dragino Sensors with Helium** =
452 +== 3.1  How to add up user's end-node with Helium console ==
450 450  
454 +=== 3.1.1  Step 1: Login the Helium console ===
451 451  
452 -== **3.1  How to add up user's end-node with Helium console** ==
453 453  
454 -
455 -=== **3.1.1  Step 1: Login the Helium console** ===
456 -
457 -
458 458  //User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
459 459  
460 460  [[image:image-20220531180150-12.png]]
... ... @@ -462,10 +462,9 @@
462 462  login Helium console
463 463  
464 464  
464 +=== 3.1.2  Step 2: Add up your end-node's key ===
465 465  
466 -=== **3.1.2  Step 2: Add up your end-node's key** ===
467 467  
468 -
469 469  //User add up end-node's key from console ~-~->dervice//
470 470  
471 471  [[image:image-20220531180224-13.png]]
... ... @@ -473,10 +473,9 @@
473 473  To add a device
474 474  
475 475  
474 +=== 3.1.3  Step 3: Activate the end-node ===
476 476  
477 -=== **3.1.3  Step 3: Activate the end-node** ===
478 478  
479 -
480 480  (((
481 481  //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**//
482 482  )))
... ... @@ -486,21 +486,27 @@
486 486  end-node traffic.
487 487  
488 488  
486 +=== 3.1.4 Check Raw Payload for End Node ===
489 489  
490 -== **3.2  How to use decoder** ==
491 491  
492 -=== **3.2.1  Step 1: Users can create decoders on functions** ===
489 +Users can check what the end node has uplinked by checking the raw payload. as below:
493 493  
491 +[[image:image-20220912161818-1.png]]
494 494  
493 +
494 +== 3.2  How to use decoder ==
495 +
496 +=== 3.2.1  Step 1: Users can create decoders on functions ===
497 +
498 +
495 495  [[image:image-20220531105325-3.png]]
496 496  
497 497  Decoder.
498 498  
499 499  
504 +=== 3.2.2  Step 2: Add a decoder in functions and apply it to the specified label ===
500 500  
501 -=== **3.2.2  Step 2: Add a decoder in functions and apply it to the specified label** ===
502 502  
503 -
504 504  [[image:image-20220526095629-6.png]]
505 505  
506 506  
... ... @@ -512,19 +512,17 @@
512 512  **//Add decoder complete.//**
513 513  
514 514  
518 +=== 3.2.3  Where is the decoder？ ===
515 515  
516 -=== **3.2.3  Where is the decoder？** ===
517 517  
518 -
519 519  [[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
520 520  
521 521  [[image:image-20220617140118-1.png||height="550" width="883"]]
522 522  
523 523  
526 +== 3.3  How to send a downlink to end device from Helium ==
524 524  
525 -== **3.3  How to send a downlink to end device from Helium** ==
526 526  
527 -
528 528  (((
529 529  //The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://
530 530  )))
... ... @@ -547,12 +547,11 @@
547 547  Downlink
548 548  
549 549  
551 +== 3.4  How to add integration to different IoT Servers ==
550 550  
551 -== **3.4  How to add integration to different IoT Servers** ==
553 +=== 3.4.1  TagoIO ===
552 552  
553 -=== **3.4.1  TagoIO** ===
554 554  
555 -
556 556  **//The steps to add integration are very simple. Please see the following process.//**
557 557  
558 558  
... ... @@ -593,10 +593,9 @@
593 593  TagoIO.
594 594  
595 595  
596 +=== 3.4.2  Cayenne ===
596 596  
597 -=== **3.4.2  Cayenne** ===
598 598  
599 -
600 600  //The process of creating devices is similar to Tago.//
601 601  
602 602  [[image:image-20220526101616-18.png||height="456" width="1097"]]
... ... @@ -629,12 +629,31 @@
629 629  Cayenne.
630 630  
631 631  
631 +== 3.5  Trouble Shooting ==
632 632  
633 -== **3.5  Trouble Shooting** ==
633 +=== 3.5.1  Data-Only Hotspot is not connecting to Helium console ===
634 634  
635 -=== **3.5.1  Trouble to Join Helium** ===
636 636  
636 +//**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
637 637  
638 +
639 +1). The hotspot does not finish the onboarding to the helium blockchain.
640 +
641 + 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.
642 +
643 +
644 +=== 3.5.2  End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ===
645 +
646 +
647 +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.
648 +
649 +
650 +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]]
651 +
652 +
653 +=== 3.5.3  Trouble to Join Helium ===
654 +
655 +
638 638  (((
639 639  **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
640 640  
... ... @@ -652,17 +652,10 @@
652 652  (((
653 653  //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)//
654 654  
655 -4) Your gateway is not onboarding to the helium explore, after 23 versions, the data-only hotspot(Gateway) is requested onboarding to helium explore. ~-~-> Please refer to [[Step 2.7>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Helium/#H2.7A0Step6:OnboardingData-OnlyHotspot]] to do it.
656 -
657 -5). You have to use the frequency plan that is compatible with your region.
658 -
659 -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]]
660 -
661 -
662 662  
663 663  )))
664 664  
665 -=== **3.5.2  Packet Loss for AU915 / US915 Band** ===
676 +=== 3.5.4  Packet Loss for AU915 / US915 Band ===
666 666  
667 667  
668 668  (((
... ... @@ -720,4 +720,13 @@
720 720  
721 721  (((
722 722  //The latest firmware for end node will have this bug fixed.//
734 +
735 +
736 +=== 3.5.5  ADR doesn't work in EU868 band. ===
737 +
738 +
739 +See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]]
740 +
741 +
742 +
723 723  )))
image-20220912161818-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +53.7 KB
Content
image-20230320141404-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +57.8 KB
Content

Applications

Navigation

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