Changes for page Notes for Helium

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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Xiaoye
Content
... ... @@ -5,18 +5,18 @@
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:#f2f2f2; width:510px" %)
19 +(% border="1" style="background-color:#ffffcc; width:510px" %)
20 20  |(% colspan="4" style="width:589px" %)(% style="color:green" %)**Dragino Hotspots for Helium**
21 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**
22 22  |(% style="width:132px" %)(((
... ... @@ -33,28 +33,30 @@
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 =
37 37  
38 -== 2.1  Prerequisites ==
37 += **2.  Connect Data-Only Hotspot to Helium** =
39 39  
39 +== **2.1  Prerequisites** ==
40 40  
41 +
41 41  * //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
42 42  
43 43  
44 -== 2.2  Step 1: Configure Frequency Band ==
45 45  
46 +== **2.2  Step 1: Configure Frequency Band** ==
46 46  
48 +
47 47  //Each country has a requirement for frequency region. Choose the right one for your area.//
48 48  
49 49  [[image:image-20220531175337-1.png]]
50 50  
51 51  
52 -== 2.3  Step 2: Download the Helium-gateway-rs ==
53 53  
55 +== **2.3  Step 2: Download the Helium-gateway-rs** ==
54 54  
57 +
55 55  //Click Download Helium Server and the gateway will download the Helium-gateway-rs//
56 56  
57 -
58 58  [[image:image-20220615150600-1.png||height="559" width="1045"]]
59 59  
60 60  
... ... @@ -70,9 +70,10 @@
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 ==
74 74  
76 +== **2.4  Step 3: Install the Helium-gateway-rs** ==
75 75  
78 +
76 76  //Click **Install Helium Server** to install gateway-rs.//
77 77  
78 78  [[image:image-20220615150734-4.png||height="619" width="1035"]]
... ... @@ -83,9 +83,10 @@
83 83  (% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
84 84  
85 85  
86 -== 2.5  Step 4: Save&start the Helium Server ==
87 87  
90 +== **2.5  Step 4: Save&start the Helium Server** ==
88 88  
92 +
89 89  //By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
90 90  
91 91  
... ... @@ -98,9 +98,10 @@
98 98  [[image:image-20220615151057-6.png||height="580" width="1026"]]
99 99  
100 100  
101 -== 2.6  Step 5: Check Gateway Connection before onboarding ==
102 102  
106 +== **2.6  Step 5: Check Gateway Connection before onboarding** ==
103 103  
108 +
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,9 +113,10 @@
113 113  (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
114 114  
115 115  
116 -== 2.7  Step 6: Onboarding Data-Only Hotspot ==
117 117  
122 +== **2.7  Step 6: Onboarding Data-Only Hotspot** ==
118 118  
124 +
119 119  (% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**
120 120  
121 121  
... ... @@ -309,12 +309,13 @@
309 309  (((
310 310  //After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//
311 311  
318 +
312 312  
313 313  )))
314 314  
315 -== 2.8  Debug Connection ==
322 +== **2.8  Debug Connection** ==
316 316  
317 -=== 2.8.1  Check pkt-fwd running Log ===
324 +=== **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,9 +345,10 @@
345 345  )))
346 346  
347 347  
348 -=== 2.8.2  Check gateway-rs Log ===
349 349  
356 +=== **2.8.2  Check gateway-rs Log** ===
350 350  
358 +
351 351  //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
352 352  
353 353  [[image:image-20220531175809-7.png]]
... ... @@ -356,9 +356,10 @@
356 356  (% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
357 357  
358 358  
359 -=== 2.8.3  View the public key address and animal name ===
360 360  
368 +=== **2.8.3  View the public key address and animal name** ===
361 361  
370 +
362 362  (% class="box" %)
363 363  (((
364 364  (((
... ... @@ -380,9 +380,10 @@
380 380  Hostpot key and animal name
381 381  
382 382  
383 -=== 2.8.4  Backup/Restor gateway-rs key ===
384 384  
393 +=== **2.8.4  Backup/Restor gateway-rs key** ===
385 385  
395 +
386 386  (((
387 387  //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.//
388 388  )))
... ... @@ -390,24 +390,12 @@
390 390  [[image:image-20220531175919-9.png]]
391 391  
392 392  
393 -=== 2.8.5  How to manually download helium gateway-rs via SSH access to the gateway Linux console ===
394 394  
404 +== **2.9  Forward the data to the other server** ==
395 395  
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 +=== **2.9.1  Introduction** ===
399 399  
400 -opkg install helium-gateway-rs-dragino.ipk
401 -)))
402 402  
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 -
411 411  (((
412 412  //The Dragino gateway has supports the double server settings.//
413 413  )))
... ... @@ -415,10 +415,11 @@
415 415  (((
416 416  //Users can back to the page of Semtech UDP to configure other server settings.//
417 417  
416 +
418 418  
419 419  )))
420 420  
421 -=== 2.9.2  Example ===
420 +=== **2.9.2  Example** ===
422 422  
423 423  
424 424  //The following takes The Things Network as another LoRaWAN server as an example.//
... ... @@ -443,17 +443,20 @@
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 ==
447 447  
446 +== **2.10  Connect Full Hotspot to Helium** ==
448 448  
449 449  
450 -= 3.  Use Dragino Sensors with Helium =
451 451  
452 -== 3.1  How to add up user's end-node with Helium console ==
450 += **3.  Use Dragino Sensors with Helium** =
453 453  
454 -=== 3.1.1  Step 1: Login the Helium console ===
455 455  
453 +== **3.1  How to add up user's end-node with Helium console** ==
456 456  
455 +
456 +=== **3.1.1  Step 1: Login the Helium console** ===
457 +
458 +
457 457  //User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
458 458  
459 459  [[image:image-20220531180150-12.png]]
... ... @@ -461,9 +461,10 @@
461 461  login Helium console
462 462  
463 463  
464 -=== 3.1.2  Step 2: Add up your end-node's key ===
465 465  
467 +=== **3.1.2  Step 2: Add up your end-node's key** ===
466 466  
469 +
467 467  //User add up end-node's key from console ~-~->dervice//
468 468  
469 469  [[image:image-20220531180224-13.png]]
... ... @@ -471,9 +471,10 @@
471 471  To add a device
472 472  
473 473  
474 -=== 3.1.3  Step 3: Activate the end-node ===
475 475  
478 +=== **3.1.3  Step 3: Activate the end-node** ===
476 476  
480 +
477 477  (((
478 478  //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**//
479 479  )))
... ... @@ -483,27 +483,21 @@
483 483  end-node traffic.
484 484  
485 485  
486 -=== 3.1.4 Check Raw Payload for End Node ===
487 487  
491 +== **3.2  How to use decoder** ==
488 488  
489 -Users can check what the end node has uplinked by checking the raw payload. as below:
493 +=== **3.2.1  Step 1: Users can create decoders on functions** ===
490 490  
491 -[[image:image-20220912161818-1.png]]
492 492  
493 -
494 -== 3.2  How to use decoder ==
495 -
496 -=== 3.2.1  Step 1: Users can create decoders on functions ===
497 -
498 -
499 499  [[image:image-20220531105325-3.png]]
500 500  
501 501  Decoder.
502 502  
503 503  
504 -=== 3.2.2  Step 2: Add a decoder in functions and apply it to the specified label ===
505 505  
502 +=== **3.2.2  Step 2: Add a decoder in functions and apply it to the specified label** ===
506 506  
504 +
507 507  [[image:image-20220526095629-6.png]]
508 508  
509 509  
... ... @@ -515,17 +515,19 @@
515 515  **//Add decoder complete.//**
516 516  
517 517  
518 -=== 3.2.3  Where is the decoder？ ===
519 519  
517 +=== **3.2.3  Where is the decoder？** ===
520 520  
519 +
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 ==
527 527  
526 +== **3.3  How to send a downlink to end device from Helium** ==
528 528  
528 +
529 529  (((
530 530  //The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://
531 531  )))
... ... @@ -548,11 +548,12 @@
548 548  Downlink
549 549  
550 550  
551 -== 3.4  How to add integration to different IoT Servers ==
552 552  
553 -=== 3.4.1  TagoIO ===
552 +== **3.4  How to add integration to different IoT Servers** ==
554 554  
554 +=== **3.4.1  TagoIO** ===
555 555  
556 +
556 556  **//The steps to add integration are very simple. Please see the following process.//**
557 557  
558 558  
... ... @@ -593,9 +593,10 @@
593 593  TagoIO.
594 594  
595 595  
596 -=== 3.4.2  Cayenne ===
597 597  
598 +=== **3.4.2  Cayenne** ===
598 598  
600 +
599 599  //The process of creating devices is similar to Tago.//
600 600  
601 601  [[image:image-20220526101616-18.png||height="456" width="1097"]]
... ... @@ -628,31 +628,12 @@
628 628  Cayenne.
629 629  
630 630  
631 -== 3.5  Trouble Shooting ==
632 632  
633 -=== 3.5.1  Data-Only Hotspot is not connecting to Helium console ===
634 +== **3.5  Trouble Shooting** ==
634 634  
636 +=== **3.5.1  Trouble to Join Helium** ===
635 635  
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 -
656 656  (((
657 657  **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
658 658  
... ... @@ -670,10 +670,17 @@
670 670  (((
671 671  //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)//
672 672  
656 +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 part 2.7 to do it.
657 +
658 +5). You have to use the frequency plan that is compatible with your region.
659 +
660 +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]]
661 +
662 +
673 673  
674 674  )))
675 675  
676 -=== 3.5.4  Packet Loss for AU915 / US915 Band ===
666 +=== **3.5.2  Packet Loss for AU915 / US915 Band** ===
677 677  
678 678  
679 679  (((
... ... @@ -731,13 +731,4 @@
731 731  
732 732  (((
733 733  //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 -
743 743  )))
image-20220912161818-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -53.7 KB
Content
image-20230320141404-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -57.8 KB
Content

Applications

Navigation

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