Changes for page Notes for Helium

Last modified by Edwin Chen on 2024/03/25 08:22
<
From version < 88.17 >
edited by Xiaoling
on 2022/08/10 17:11
To version < 99.8 >
edited by Xiaoling
on 2023/04/21 16:47
>
Change comment: There is no comment for this version

Summary

Details

Page properties
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 Hotspot|(% 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,31 +33,28 @@
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  
44 +== 2.2  Step 1: Configure Frequency Band ==
45 45  
46 46  
47 -== **2.2  Step 1: Configure Frequency Band** ==
48 -
49 -
50 50  //Each country has a requirement for frequency region. Choose the right one for your area.//
51 51  
52 52  [[image:image-20220531175337-1.png]]
53 53  
54 54  
52 +== 2.3  Step 2: Download the Helium-gateway-rs ==
55 55  
56 -== **2.3  Step 2: Download the Helium-gateway-rs** ==
57 57  
58 -
59 59  //Click Download Helium Server and the gateway will download the Helium-gateway-rs//
60 60  
57 +
61 61  [[image:image-20220615150600-1.png||height="559" width="1045"]]
62 62  
63 63  
... ... @@ -73,10 +73,9 @@
73 73  [[image:image-20220615150717-3.png||height="605" width="1039"]]
74 74  
75 75  
73 +== 2.4  Step 3: Install the Helium-gateway-rs ==
76 76  
77 -== **2.4  Step 3: Install the Helium-gateway-rs** ==
78 78  
79 -
80 80  //Click **Install Helium Server** to install gateway-rs.//
81 81  
82 82  [[image:image-20220615150734-4.png||height="619" width="1035"]]
... ... @@ -87,10 +87,9 @@
87 87  (% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
88 88  
89 89  
86 +== 2.5  Step 4: Save&start the Helium Server ==
90 90  
91 -== **2.5  Step 4: Save&start the Helium Server** ==
92 92  
93 -
94 94  //By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
95 95  
96 96  
... ... @@ -103,10 +103,9 @@
103 103  [[image:image-20220615151057-6.png||height="580" width="1026"]]
104 104  
105 105  
101 +== 2.6  Step 5: Check Gateway Connection before onboarding ==
106 106  
107 -== **2.6  Step 5: Check Gateway Connection before onboarding** ==
108 108  
109 -
110 110  //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.//
111 111  
112 112  (((
... ... @@ -119,10 +119,9 @@
119 119  (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
120 120  
121 121  
116 +== 2.7  Step 6: Onboarding Data-Only Hotspot ==
122 122  
123 -== **2.7  Step 6: Onboarding Data-Only Hotspot** ==
124 124  
125 -
126 126  (% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**
127 127  
128 128  
... ... @@ -316,13 +316,12 @@
316 316  (((
317 317  //After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//
318 318  
319 -
320 320  
321 321  )))
322 322  
323 -== **2.8  Debug Connection** ==
315 +== 2.8  Debug Connection ==
324 324  
325 -=== **2.8.1  Check pkt-fwd running Log** ===
317 +=== 2.8.1  Check pkt-fwd running Log ===
326 326  
327 327  
328 328  //This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
... ... @@ -353,10 +353,9 @@
353 353  )))
354 354  
355 355  
348 +=== 2.8.2  Check gateway-rs Log ===
356 356  
357 -=== **2.8.2  Check gateway-rs Log** ===
358 358  
359 -
360 360  //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
361 361  
362 362  [[image:image-20220531175809-7.png]]
... ... @@ -365,10 +365,9 @@
365 365  (% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
366 366  
367 367  
359 +=== 2.8.3  View the public key address and animal name ===
368 368  
369 -=== **2.8.3  View the public key address and animal name** ===
370 370  
371 -
372 372  (% class="box" %)
373 373  (((
374 374  (((
... ... @@ -390,10 +390,9 @@
390 390  Hostpot key and animal name
391 391  
392 392  
383 +=== 2.8.4  Backup/Restor gateway-rs key ===
393 393  
394 -=== **2.8.4  Backup/Restor gateway-rs key** ===
395 395  
396 -
397 397  (((
398 398  //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.//
399 399  )))
... ... @@ -401,12 +401,24 @@
401 401  [[image:image-20220531175919-9.png]]
402 402  
403 403  
393 +=== 2.8.5  How to manually download helium gateway-rs via SSH access to the gateway Linux console ===
404 404  
405 -== **2.9  Forward the data to the other server** ==
406 406  
407 -=== **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]]
408 408  
400 +opkg install helium-gateway-rs-dragino.ipk
401 +)))
409 409  
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 +
410 410  (((
411 411  //The Dragino gateway has supports the double server settings.//
412 412  )))
... ... @@ -414,11 +414,10 @@
414 414  (((
415 415  //Users can back to the page of Semtech UDP to configure other server settings.//
416 416  
417 -
418 418  
419 419  )))
420 420  
421 -=== **2.9.2  Example** ===
421 +=== 2.9.2  Example ===
422 422  
423 423  
424 424  //The following takes The Things Network as another LoRaWAN server as an example.//
... ... @@ -443,20 +443,17 @@
443 443  //The user can configure the secondary server and then click the button of **Save&Apply**.//
444 444  
445 445  
446 +== 2.10  Connect Full Hotspot to Helium ==
446 446  
447 -== **2.10  Connect Full Hotspot to Helium** ==
448 448  
449 449  
450 += 3.  Use Dragino Sensors with Helium =
450 450  
451 -= **3.  Use Dragino Sensors with Helium** =
452 +== 3.1  How to add up user's end-node with Helium console ==
452 452  
454 +=== 3.1.1  Step 1: Login the Helium console ===
453 453  
454 -== **3.1  How to add up user's end-node with Helium console** ==
455 455  
456 -
457 -=== **3.1.1  Step 1: Login the Helium console** ===
458 -
459 -
460 460  //User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
461 461  
462 462  [[image:image-20220531180150-12.png]]
... ... @@ -464,10 +464,9 @@
464 464  login Helium console
465 465  
466 466  
464 +=== 3.1.2  Step 2: Add up your end-node's key ===
467 467  
468 -=== **3.1.2  Step 2: Add up your end-node's key** ===
469 469  
470 -
471 471  //User add up end-node's key from console ~-~->dervice//
472 472  
473 473  [[image:image-20220531180224-13.png]]
... ... @@ -475,10 +475,9 @@
475 475  To add a device
476 476  
477 477  
474 +=== 3.1.3  Step 3: Activate the end-node ===
478 478  
479 -=== **3.1.3  Step 3: Activate the end-node** ===
480 480  
481 -
482 482  (((
483 483  //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**//
484 484  )))
... ... @@ -488,21 +488,27 @@
488 488  end-node traffic.
489 489  
490 490  
486 +=== 3.1.4 Check Raw Payload for End Node ===
491 491  
492 -== **3.2  How to use decoder** ==
493 493  
494 -=== **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:
495 495  
491 +[[image:image-20220912161818-1.png]]
496 496  
493 +
494 +== 3.2  How to use decoder ==
495 +
496 +=== 3.2.1  Step 1: Users can create decoders on functions ===
497 +
498 +
497 497  [[image:image-20220531105325-3.png]]
498 498  
499 499  Decoder.
500 500  
501 501  
504 +=== 3.2.2  Step 2: Add a decoder in functions and apply it to the specified label ===
502 502  
503 -=== **3.2.2  Step 2: Add a decoder in functions and apply it to the specified label** ===
504 504  
505 -
506 506  [[image:image-20220526095629-6.png]]
507 507  
508 508  
... ... @@ -514,19 +514,17 @@
514 514  **//Add decoder complete.//**
515 515  
516 516  
518 +=== 3.2.3  Where is the decoder？ ===
517 517  
518 -=== **3.2.3  Where is the decoder？** ===
519 519  
520 -
521 521  [[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
522 522  
523 523  [[image:image-20220617140118-1.png||height="550" width="883"]]
524 524  
525 525  
526 +== 3.3  How to send a downlink to end device from Helium ==
526 526  
527 -== **3.3  How to send a downlink to end device from Helium** ==
528 528  
529 -
530 530  (((
531 531  //The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://
532 532  )))
... ... @@ -549,12 +549,11 @@
549 549  Downlink
550 550  
551 551  
551 +== 3.4  How to add integration to different IoT Servers ==
552 552  
553 -== **3.4  How to add integration to different IoT Servers** ==
553 +=== 3.4.1  TagoIO ===
554 554  
555 -=== **3.4.1  TagoIO** ===
556 556  
557 -
558 558  **//The steps to add integration are very simple. Please see the following process.//**
559 559  
560 560  
... ... @@ -595,10 +595,9 @@
595 595  TagoIO.
596 596  
597 597  
596 +=== 3.4.2  Cayenne ===
598 598  
599 -=== **3.4.2  Cayenne** ===
600 600  
601 -
602 602  //The process of creating devices is similar to Tago.//
603 603  
604 604  [[image:image-20220526101616-18.png||height="456" width="1097"]]
... ... @@ -631,12 +631,31 @@
631 631  Cayenne.
632 632  
633 633  
631 +== 3.5  Trouble Shooting ==
634 634  
635 -== **3.5  Trouble Shooting** ==
633 +=== 3.5.1  Data-Only Hotspot is not connecting to Helium console ===
636 636  
637 -=== **3.5.1  Trouble to Join Helium** ===
638 638  
636 +//**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
639 639  
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 +
640 640  (((
641 641  **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
642 642  
... ... @@ -654,11 +654,10 @@
654 654  (((
655 655  //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)//
656 656  
657 -
658 658  
659 659  )))
660 660  
661 -=== **3.5.2  Packet Loss for AU915 / US915 Band** ===
676 +=== 3.5.4  Packet Loss for AU915 / US915 Band ===
662 662  
663 663  
664 664  (((
... ... @@ -716,4 +716,13 @@
716 716  
717 717  (((
718 718  //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 +
719 719  )))
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