Skip to Content

Changes for page Notes for Helium

Last modified by Edwin Chen on 2024/03/25 08:22
From version 88.12
edited by Xiaoling
on 2022/07/23 15:12
Change comment: There is no comment for this version
To version 88.7
edited by Xiaoling
on 2022/07/23 14:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -23,15 +23,13 @@
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"]]
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.ConnectData-OnlyHotspottoHelium"]]
27 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]]
28 28  
29 -(% style="color:blue" %)**Frequencies on the Helium Network**
29 +**Frequencies on the Helium Network**
30 30  
31 31  * //The frequencies currently available are CN470/EU868/US915/AU915//
32 32  
33 -
34 -
35 35  (% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]**
36 36  
37 37  
... ... @@ -43,9 +43,6 @@
43 43  
44 44  * //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
45 45  
46 -
47 -
48 -
49 49  == **2.2  Step 1: Configure Frequency Band** ==
50 50  
51 51  
... ... @@ -428,7 +428,6 @@
428 428  Back to Semtech UDP page
429 429  
430 430  
431 -
432 432  ==== (% style="color:blue" %)**Step 2: Configure the double server forwarding**(%%) ====
433 433  
434 434  
... ... @@ -438,19 +438,17 @@
438 438  //The user can configure the secondary server and then click the button of **Save&Apply**.//
439 439  
440 440  
441 -== **2.10  Connect Full Hotspot to Helium** ==
435 +== **2.10 Connect Full Hotspot to Helium** ==
442 442  
437 += **3. Use Dragino Sensors with Helium** =
443 443  
444 444  
445 -= **3.  Use Dragino Sensors with Helium** =
440 +== **3.1 How to add up user's end-node with Helium console** ==
446 446  
447 447  
448 -== **3.1  How to add up user's end-node with Helium console** ==
443 +=== **3.1.1 Step 1: Login the Helium console** ===
449 449  
450 450  
451 -=== **3.1.1  Step 1: Login the Helium console** ===
452 -
453 -
454 454  //User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
455 455  
456 456  [[image:image-20220531180150-12.png]]
... ... @@ -458,10 +458,9 @@
458 458  login Helium console
459 459  
460 460  
453 +=== **3.1.2 Step 2: Add up your end-node's key** ===
461 461  
462 -=== **3.1.2  Step 2: Add up your end-node's key** ===
463 463  
464 -
465 465  //User add up end-node's key from console ~-~->dervice//
466 466  
467 467  [[image:image-20220531180224-13.png]]
... ... @@ -469,10 +469,9 @@
469 469  To add a device
470 470  
471 471  
463 +=== **3.1.3 Step 3:Activate the end-node** ===
472 472  
473 -=== **3.1.3  Step 3: Activate the end-node** ===
474 474  
475 -
476 476  (((
477 477  //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**//
478 478  )))
... ... @@ -482,21 +482,19 @@
482 482  end-node traffic.
483 483  
484 484  
475 +== **3.2 How to use decoder** ==
485 485  
486 -== **3.2  How to use decoder** ==
477 +=== **3.2.1 Step 1:Users can create decoders on functions** ===
487 487  
488 -=== **3.2.1  Step 1: Users can create decoders on functions** ===
489 489  
490 -
491 491  [[image:image-20220531105325-3.png]]
492 492  
493 493  Decoder.
494 494  
495 495  
485 +=== **3.2.2 Step 2:Add a decoder in functions and apply it to the specified label** ===
496 496  
497 -=== **3.2.2  Step 2: Add a decoder in functions and apply it to the specified label** ===
498 498  
499 -
500 500  [[image:image-20220526095629-6.png]]
501 501  
502 502  
... ... @@ -505,22 +505,18 @@
505 505  
506 506  [[image:image-20220526100057-8.png||height="352" width="1133"]]
507 507  
496 +
508 508  **//Add decoder complete.//**
509 509  
499 +=== **3.2.3 Where is the decoder？** ===
510 510  
511 -
512 -=== **3.2.3  Where is the decoder？** ===
513 -
514 -
515 515  [[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
516 516  
517 517  [[image:image-20220617140118-1.png||height="550" width="883"]]
518 518  
505 +== **3.3 How to send a downlink to end device from Helium** ==
519 519  
520 520  
521 -== **3.3  How to send a downlink to end device from Helium** ==
522 -
523 -
524 524  (((
525 525  //The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://
526 526  )))
... ... @@ -535,7 +535,7 @@
535 535  
536 536  (% class="box" %)
537 537  (((
538 -**01 00 00 3C ~-~-> AQAAPA==**
522 +01 00 00 3C ~-~-> AQAAPA==
539 539  )))
540 540  
541 541  [[image:image-20220524171341-21.png]]
... ... @@ -543,12 +543,11 @@
543 543  Downlink
544 544  
545 545  
530 +== **3.4 How to add integration to different IoT Servers** ==
546 546  
547 -== **3.4  How to add integration to different IoT Servers** ==
532 +=== **3.4.1 TagoIO** ===
548 548  
549 -=== **3.4.1  TagoIO** ===
550 550  
551 -
552 552  **//The steps to add integration are very simple. Please see the following process.//**
553 553  
554 554  
... ... @@ -589,10 +589,9 @@
589 589  TagoIO.
590 590  
591 591  
575 +=== **3.4.2 Cayenne** ===
592 592  
593 -=== **3.4.2  Cayenne** ===
594 594  
595 -
596 596  //The process of creating devices is similar to Tago.//
597 597  
598 598  [[image:image-20220526101616-18.png||height="456" width="1097"]]
... ... @@ -625,12 +625,11 @@
625 625  Cayenne.
626 626  
627 627  
610 +== **3.5 Trouble Shooting** ==
628 628  
629 -== **3.5  Trouble Shooting** ==
612 +=== **3.5.1 Trouble to Join Helium** ===
630 630  
631 -=== **3.5.1  Trouble to Join Helium** ===
632 632  
633 -
634 634  (((
635 635  **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
636 636  
... ... @@ -648,11 +648,10 @@
648 648  (((
649 649  //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)//
650 650  
651 -
652 652  
653 653  )))
654 654  
655 -=== **3.5.2  Packet Loss for AU915 / US915 Band** ===
635 +=== **3.5.2 Packet Loss for AU915 / US915 Band** ===
656 656  
657 657  
658 658  (((
... ... @@ -661,8 +661,6 @@
661 661  
662 662  (((
663 663  //The reason for this problem is that the node does not lock the channel after joining the network.//
664 -
665 -
666 666  )))
667 667  
668 668  (((
... ... @@ -676,19 +676,15 @@
676 676  )))
677 677  
678 678  * (((
679 -(% style="color:blue" %)**//AT Command: AT+CHE//**
657 +//AT Command: AT+CHE//
680 680  )))
681 681  
682 682  * (((
683 -//**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%)  ~/~/set channel mode to 1//
661 +//Example:**AT+CHE=2** ~/~/set channel mode to 1//
684 684  )))
685 685  
686 686  * (((
687 -(% style="color:blue" %)**//Downlink Command: 0x24//**
688 -
689 -
690 -
691 -
665 +//Downlink Command: 0x24//
692 692  )))
693 693  
694 694  (((
... ... @@ -695,13 +695,12 @@
695 695  //Format: Command Code (0x24) followed by 1 bytes channel value.//
696 696  )))
697 697  
698 -
699 699  (((
700 700  //If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.//
701 701  )))
702 702  
703 703  * (((
704 -//**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2//
677 +//Example 1: Downlink Payload: **0x2402** ~/~/ set channel mode to 2//
705 705  
706 706  
707 707