Changes for page Notes for Helium

Last modified by Edwin Chen on 2024/03/25 08:22
<
From version < 93.1 >
edited by Edwin Chen
on 2022/09/05 18:02
To version < 99.3 >
edited by Xiaoling
on 2023/03/23 17:20
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -5,9 +5,9 @@
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 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.//
... ... @@ -33,28 +33,29 @@
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 -== **2.2  Step 1: Configure Frequency Band** ==
45 45  
46 46  
45 +== 2.2  Step 1: Configure Frequency Band ==
46 +
47 +
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  
53 +== 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 58  [[image:image-20220615150600-1.png||height="559" width="1045"]]
59 59  
60 60  
... ... @@ -70,10 +70,9 @@
70 70  [[image:image-20220615150717-3.png||height="605" width="1039"]]
71 71  
72 72  
74 +== 2.4  Step 3: Install the Helium-gateway-rs ==
73 73  
74 -== **2.4  Step 3: Install the Helium-gateway-rs** ==
75 75  
76 -
77 77  //Click **Install Helium Server** to install gateway-rs.//
78 78  
79 79  [[image:image-20220615150734-4.png||height="619" width="1035"]]
... ... @@ -84,10 +84,9 @@
84 84  (% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
85 85  
86 86  
87 +== 2.5  Step 4: Save&start the Helium Server ==
87 87  
88 -== **2.5  Step 4: Save&start the Helium Server** ==
89 89  
90 -
91 91  //By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
92 92  
93 93  
... ... @@ -100,10 +100,9 @@
100 100  [[image:image-20220615151057-6.png||height="580" width="1026"]]
101 101  
102 102  
102 +== 2.6  Step 5: Check Gateway Connection before onboarding ==
103 103  
104 -== **2.6  Step 5: Check Gateway Connection before onboarding** ==
105 105  
106 -
107 107  //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.//
108 108  
109 109  (((
... ... @@ -116,10 +116,9 @@
116 116  (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
117 117  
118 118  
117 +== 2.7  Step 6: Onboarding Data-Only Hotspot ==
119 119  
120 -== **2.7  Step 6: Onboarding Data-Only Hotspot** ==
121 121  
122 -
123 123  (% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**
124 124  
125 125  
... ... @@ -313,13 +313,12 @@
313 313  (((
314 314  //After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//
315 315  
316 -
317 317  
318 318  )))
319 319  
320 -== **2.8  Debug Connection** ==
316 +== 2.8  Debug Connection ==
321 321  
322 -=== **2.8.1  Check pkt-fwd running Log** ===
318 +=== 2.8.1  Check pkt-fwd running Log ===
323 323  
324 324  
325 325  //This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
... ... @@ -350,10 +350,9 @@
350 350  )))
351 351  
352 352  
349 +=== 2.8.2  Check gateway-rs Log ===
353 353  
354 -=== **2.8.2  Check gateway-rs Log** ===
355 355  
356 -
357 357  //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
358 358  
359 359  [[image:image-20220531175809-7.png]]
... ... @@ -362,10 +362,9 @@
362 362  (% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
363 363  
364 364  
360 +=== 2.8.3  View the public key address and animal name ===
365 365  
366 -=== **2.8.3  View the public key address and animal name** ===
367 367  
368 -
369 369  (% class="box" %)
370 370  (((
371 371  (((
... ... @@ -387,10 +387,9 @@
387 387  Hostpot key and animal name
388 388  
389 389  
384 +=== 2.8.4  Backup/Restor gateway-rs key ===
390 390  
391 -=== **2.8.4  Backup/Restor gateway-rs key** ===
392 392  
393 -
394 394  (((
395 395  //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.//
396 396  )))
... ... @@ -398,12 +398,24 @@
398 398  [[image:image-20220531175919-9.png]]
399 399  
400 400  
394 +=== 2.8.5  How to manually download helium gateway-rs via SSH access to the gateway Linux console ===
401 401  
402 -== **2.9  Forward the data to the other server** ==
403 403  
404 -=== **2.9.1  Introduction** ===
397 +(% class="box infomessage" %)
398 +(((
399 +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]]
405 405  
401 +opkg install helium-gateway-rs-dragino.ipk
402 +)))
406 406  
404 +[[image:image-20230320141404-1.png]]
405 +
406 +
407 +== 2.9  Forward the data to the other server ==
408 +
409 +=== 2.9.1  Introduction ===
410 +
411 +
407 407  (((
408 408  //The Dragino gateway has supports the double server settings.//
409 409  )))
... ... @@ -411,11 +411,10 @@
411 411  (((
412 412  //Users can back to the page of Semtech UDP to configure other server settings.//
413 413  
414 -
415 415  
416 416  )))
417 417  
418 -=== **2.9.2  Example** ===
422 +=== 2.9.2  Example ===
419 419  
420 420  
421 421  //The following takes The Things Network as another LoRaWAN server as an example.//
... ... @@ -440,20 +440,17 @@
440 440  //The user can configure the secondary server and then click the button of **Save&Apply**.//
441 441  
442 442  
447 +== 2.10  Connect Full Hotspot to Helium ==
443 443  
444 -== **2.10  Connect Full Hotspot to Helium** ==
445 445  
446 446  
451 += 3.  Use Dragino Sensors with Helium =
447 447  
448 -= **3.  Use Dragino Sensors with Helium** =
453 +== 3.1  How to add up user's end-node with Helium console ==
449 449  
455 +=== 3.1.1  Step 1: Login the Helium console ===
450 450  
451 -== **3.1  How to add up user's end-node with Helium console** ==
452 452  
453 -
454 -=== **3.1.1  Step 1: Login the Helium console** ===
455 -
456 -
457 457  //User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
458 458  
459 459  [[image:image-20220531180150-12.png]]
... ... @@ -461,10 +461,9 @@
461 461  login Helium console
462 462  
463 463  
465 +=== 3.1.2  Step 2: Add up your end-node's key ===
464 464  
465 -=== **3.1.2  Step 2: Add up your end-node's key** ===
466 466  
467 -
468 468  //User add up end-node's key from console ~-~->dervice//
469 469  
470 470  [[image:image-20220531180224-13.png]]
... ... @@ -472,10 +472,9 @@
472 472  To add a device
473 473  
474 474  
475 +=== 3.1.3  Step 3: Activate the end-node ===
475 475  
476 -=== **3.1.3  Step 3: Activate the end-node** ===
477 477  
478 -
479 479  (((
480 480  //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**//
481 481  )))
... ... @@ -485,21 +485,27 @@
485 485  end-node traffic.
486 486  
487 487  
487 +=== 3.1.4 Check Raw Payload for End Node ===
488 488  
489 -== **3.2  How to use decoder** ==
490 490  
491 -=== **3.2.1  Step 1: Users can create decoders on functions** ===
490 +Users can check what the end node has uplinked by checking the raw payload. as below:
492 492  
492 +[[image:image-20220912161818-1.png]]
493 493  
494 +
495 +== 3.2  How to use decoder ==
496 +
497 +=== 3.2.1  Step 1: Users can create decoders on functions ===
498 +
499 +
494 494  [[image:image-20220531105325-3.png]]
495 495  
496 496  Decoder.
497 497  
498 498  
505 +=== 3.2.2  Step 2: Add a decoder in functions and apply it to the specified label ===
499 499  
500 -=== **3.2.2  Step 2: Add a decoder in functions and apply it to the specified label** ===
501 501  
502 -
503 503  [[image:image-20220526095629-6.png]]
504 504  
505 505  
... ... @@ -511,19 +511,17 @@
511 511  **//Add decoder complete.//**
512 512  
513 513  
519 +=== 3.2.3  Where is the decoder？ ===
514 514  
515 -=== **3.2.3  Where is the decoder？** ===
516 516  
517 -
518 518  [[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
519 519  
520 520  [[image:image-20220617140118-1.png||height="550" width="883"]]
521 521  
522 522  
527 +== 3.3  How to send a downlink to end device from Helium ==
523 523  
524 -== **3.3  How to send a downlink to end device from Helium** ==
525 525  
526 -
527 527  (((
528 528  //The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://
529 529  )))
... ... @@ -546,12 +546,11 @@
546 546  Downlink
547 547  
548 548  
552 +== 3.4  How to add integration to different IoT Servers ==
549 549  
550 -== **3.4  How to add integration to different IoT Servers** ==
554 +=== 3.4.1  TagoIO ===
551 551  
552 -=== **3.4.1  TagoIO** ===
553 553  
554 -
555 555  **//The steps to add integration are very simple. Please see the following process.//**
556 556  
557 557  
... ... @@ -592,10 +592,9 @@
592 592  TagoIO.
593 593  
594 594  
597 +=== 3.4.2  Cayenne ===
595 595  
596 -=== **3.4.2  Cayenne** ===
597 597  
598 -
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,13 +628,11 @@
628 628  Cayenne.
629 629  
630 630  
632 +== 3.5  Trouble Shooting ==
631 631  
632 -== **3.5  Trouble Shooting** ==
634 +=== 3.5.1  Data-Only Hotspot is not connecting to Helium console ===
633 633  
634 634  
635 -=== **3.5.1 Data-Only Hotspot is not connecting to Helium console** ===
636 -
637 -
638 638  //**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
639 639  
640 640  
... ... @@ -643,7 +643,7 @@
643 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 644  
645 645  
646 -=== **3.5.2 End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ** ===
645 +=== 3.5.2  End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ===
647 647  
648 648  
649 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.
... ... @@ -652,10 +652,9 @@
652 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 653  
654 654  
654 +=== 3.5.3  Trouble to Join Helium ===
655 655  
656 -=== **3.5.3  Trouble to Join Helium** ===
657 657  
658 -
659 659  (((
660 660  **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
661 661  
... ... @@ -676,7 +676,7 @@
676 676  
677 677  )))
678 678  
679 -=== **3.5.4  Packet Loss for AU915 / US915 Band** ===
677 +=== 3.5.4  Packet Loss for AU915 / US915 Band ===
680 680  
681 681  
682 682  (((
... ... @@ -734,4 +734,13 @@
734 734  
735 735  (((
736 736  //The latest firmware for end node will have this bug fixed.//
735 +
736 +
737 +=== 3.5.5  ADR doesn't work in EU868 band. ===
738 +
739 +
740 +See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]]
741 +
742 +
743 +
737 737  )))
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