Changes for page Notes for Helium
Last modified by Edwin Chen on 2024/03/25 08:22
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.Xiao ye1 +XWiki.Xiaoling - Content
-
... ... @@ -23,13 +23,16 @@ 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** 30 30 30 +**Frequencies on the Helium Network** 31 + 31 31 * //The frequencies currently available are CN470/EU868/US915/AU915// 32 32 34 + 35 + 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 ... ... @@ -43,6 +43,7 @@ 43 43 44 44 45 45 49 + 46 46 == **2.2 Step 1: Configure Frequency Band** == 47 47 48 48 ... ... @@ -72,7 +72,6 @@ 72 72 [[image:image-20220615150717-3.png||height="605" width="1039"]] 73 73 74 74 75 - 76 76 == **2.4 Step 3: Install the Helium-gateway-rs** == 77 77 78 78 ... ... @@ -92,20 +92,17 @@ 92 92 93 93 //By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.// 94 94 95 - 96 96 [[image:image-20220615150903-5.png||height="592" width="1031"]] 97 97 98 98 101 +//Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.// 99 99 100 -//Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.// 101 - 102 102 [[image:image-20220615151057-6.png||height="580" width="1026"]] 103 103 104 104 106 +== **2.6 Step 5: Check Gateway Connection before onboarding** == 105 105 106 -== **2.6 Step 5: Check Gateway Connection before onboarding** == 107 107 108 - 109 109 //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.// 110 110 111 111 ((( ... ... @@ -118,13 +118,10 @@ 118 118 (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.** 119 119 120 120 121 +== 2.7 Step 6: Onboarding Data-Only Hotspot == 121 121 122 -== **2.7 Step 6: Onboarding Data-Only Hotspot** == 123 - 124 - 125 125 (% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .** 126 126 127 - 128 128 //User can refer [[this link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]] for how to onboarding a data-only hotspot. After onboarding the data-only hotspot, user can see the hotspot on Helium Console.// 129 129 130 130 //Below are the steps we do as per above link here.// ... ... @@ -131,7 +131,7 @@ 131 131 132 132 133 133 ((( 134 - (% style="color:blue" %)//**1. Set up Helium-Wallet in my computer. [[https:~~/~~/docs.helium.com/wallets/cli-wallet>>url:https://docs.helium.com/wallets/cli-wallet]]. and funds this wallet. From this step, we got the wallet info as below.**//131 +//**1. Set up Helium-Wallet in my computer. [[https:~~/~~/docs.helium.com/wallets/cli-wallet>>url:https://docs.helium.com/wallets/cli-wallet]]. and funds this wallet. From this step, we got the wallet info as below.**// 135 135 ))) 136 136 137 137 (% class="box" %) ... ... @@ -158,15 +158,13 @@ 158 158 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+ 159 159 ))) 160 160 161 - 162 162 ((( 163 163 (% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.** 164 164 ))) 165 165 166 166 167 - 168 168 ((( 169 - (% style="color:blue" %)//**2. Get txn. In the data-only hotspot. run below command to add a hotspot, owner is the owner wallet of this hotspot, payer is the payer to pay transaction cost.**//164 +//**2. Get txn. In the data-only hotspot. run below command to add a hotspot, owner is the owner wallet of this hotspot, payer is the payer to pay transaction cost.**// 170 170 ))) 171 171 172 172 (% class="box" %) ... ... @@ -199,15 +199,11 @@ 199 199 200 200 ((( 201 201 //We got the txn info from this step.// 197 +\\//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**// 202 202 203 203 204 - 205 -(% style="color:blue" %)//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**// 206 - 207 - 208 208 (% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.** 209 209 210 - 211 211 //Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.// 212 212 ))) 213 213 ... ... @@ -251,9 +251,7 @@ 251 251 ))) 252 252 253 253 ((( 254 - 255 - 256 -(% style="color:blue" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**// 245 +//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**// 257 257 ))) 258 258 259 259 (% class="box" %) ... ... @@ -307,21 +307,19 @@ 307 307 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+ 308 308 ))) 309 309 310 - 311 311 ((( 312 - (% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.**300 +**Note: The add hotspot and assert location step might need some time to be effect.** 313 313 ))) 314 314 315 315 ((( 316 316 //After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.// 317 317 318 - 319 319 320 320 ))) 321 321 322 -== **2.8 309 +== **2.8 Debug Connection** == 323 323 324 -=== **2.8.1 311 +=== **2.8.1 Check pkt-fwd running Log** === 325 325 326 326 327 327 //This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.// ... ... @@ -352,22 +352,20 @@ 352 352 ))) 353 353 354 354 342 +=== **2.8.2 Check gateway-rs Log** === 355 355 356 -=== **2.8.2 Check gateway-rs Log** === 357 357 358 - 359 359 //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.// 360 360 361 361 [[image:image-20220531175809-7.png]] 362 362 363 363 364 - (% style="color:red" %)**Note**:**logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**350 +**Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system. 365 365 366 366 353 +=== **2.8.3 View the public key address and animal name** === 367 367 368 -=== **2.8.3 View the public key address and animal name** === 369 369 370 - 371 371 (% class="box" %) 372 372 ((( 373 373 ((( ... ... @@ -389,10 +389,8 @@ 389 389 Hostpot key and animal name 390 390 391 391 377 +=== **2.8.4 Backup/Restor gateway-rs key** === 392 392 393 -=== **2.8.4 Backup/Restor gateway-rs key** === 394 - 395 - 396 396 ((( 397 397 //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.// 398 398 ))) ... ... @@ -401,9 +401,9 @@ 401 401 402 402 403 403 404 -== **2.9 387 +== **2.9 Forward the data to the other server** == 405 405 406 -=== **2.9.1 389 +=== **2.9.1 Introduction** === 407 407 408 408 409 409 ((( ... ... @@ -413,29 +413,26 @@ 413 413 ((( 414 414 //Users can back to the page of Semtech UDP to configure other server settings.// 415 415 416 - 417 417 418 418 ))) 419 419 420 -=== **2.9.2 402 +=== **2.9.2 Example** === 421 421 422 422 423 423 //The following takes The Things Network as another LoRaWAN server as an example.// 424 424 425 425 408 +==== **2.9.2.1 Step 1: Back to Semtech UDP page** ==== 426 426 427 -==== (% style="color:blue" %)**Step 1: Back to Semtech UDP page**(%%) ==== 428 428 429 - 430 430 [[image:image-20220531180002-10.png]] 431 431 432 432 Back to Semtech UDP page 433 433 434 434 416 +==== **2.9.2.2 Step 2: Configure the double server forwarding** ==== 435 435 436 -==== (% style="color:blue" %)**Step 2: Configure the double server forwarding**(%%) ==== 437 437 438 - 439 439 [[image:image-20220531180048-11.png]] 440 440 441 441 ... ... @@ -442,20 +442,17 @@ 442 442 //The user can configure the secondary server and then click the button of **Save&Apply**.// 443 443 444 444 425 +== **2.10 Connect Full Hotspot to Helium** == 445 445 446 -= =**2.10ConnectFull HotspottoHelium** ==427 += **3. Use Dragino Sensors with Helium** = 447 447 448 448 430 +== **3.1 How to add up user's end-node with Helium console** == 449 449 450 -= **3. Use Dragino Sensors with Helium** = 451 451 433 +=== **3.1.1 Step 1: Login the Helium console** === 452 452 453 -== **3.1 How to add up user's end-node with Helium console** == 454 454 455 - 456 -=== **3.1.1 Step 1: Login the Helium console** === 457 - 458 - 459 459 //User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]// 460 460 461 461 [[image:image-20220531180150-12.png]] ... ... @@ -463,10 +463,9 @@ 463 463 login Helium console 464 464 465 465 443 +=== **3.1.2 Step 2: Add up your end-node's key** === 466 466 467 -=== **3.1.2 Step 2: Add up your end-node's key** === 468 468 469 - 470 470 //User add up end-node's key from console ~-~->dervice// 471 471 472 472 [[image:image-20220531180224-13.png]] ... ... @@ -474,10 +474,9 @@ 474 474 To add a device 475 475 476 476 453 +=== **3.1.3 Step 3:Activate the end-node** === 477 477 478 -=== **3.1.3 Step 3: Activate the end-node** === 479 479 480 - 481 481 ((( 482 482 //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**// 483 483 ))) ... ... @@ -487,21 +487,19 @@ 487 487 end-node traffic. 488 488 489 489 465 +== **3.2 How to use decoder** == 490 490 491 -== **3.2 Howtouse decoder** ==467 +=== **3.2.1 Step 1:Users can create decoders on functions** === 492 492 493 -=== **3.2.1 Step 1: Users can create decoders on functions** === 494 494 495 - 496 496 [[image:image-20220531105325-3.png]] 497 497 498 498 Decoder. 499 499 500 500 475 +=== **3.2.2 Step 2:Add a decoder in functions and apply it to the specified label** === 501 501 502 -=== **3.2.2 Step 2: Add a decoder in functions and apply it to the specified label** === 503 503 504 - 505 505 [[image:image-20220526095629-6.png]] 506 506 507 507 ... ... @@ -510,22 +510,18 @@ 510 510 511 511 [[image:image-20220526100057-8.png||height="352" width="1133"]] 512 512 486 + 513 513 **//Add decoder complete.//** 514 514 489 +=== **3.2.3 Where is the decoder?** === 515 515 516 - 517 -=== **3.2.3 Where is the decoder?** === 518 - 519 - 520 520 [[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]] 521 521 522 522 [[image:image-20220617140118-1.png||height="550" width="883"]] 523 523 495 +== **3.3 How to send a downlink to end device from Helium** == 524 524 525 525 526 -== **3.3 How to send a downlink to end device from Helium** == 527 - 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 ))) ... ... @@ -540,7 +540,7 @@ 540 540 541 541 (% class="box" %) 542 542 ((( 543 - **01 00 00 3C ~-~-> AQAAPA==**512 +01 00 00 3C ~-~-> AQAAPA== 544 544 ))) 545 545 546 546 [[image:image-20220524171341-21.png]] ... ... @@ -548,12 +548,11 @@ 548 548 Downlink 549 549 550 550 520 +== **3.4 How to add integration to different IoT Servers** == 551 551 552 -== **3.4 How toadd integration to differentIoT Servers** ==522 +=== **3.4.1 TagoIO** === 553 553 554 -=== **3.4.1 TagoIO** === 555 555 556 - 557 557 **//The steps to add integration are very simple. Please see the following process.//** 558 558 559 559 ... ... @@ -594,10 +594,9 @@ 594 594 TagoIO. 595 595 596 596 565 +=== **3.4.2 Cayenne** === 597 597 598 -=== **3.4.2 Cayenne** === 599 599 600 - 601 601 //The process of creating devices is similar to Tago.// 602 602 603 603 [[image:image-20220526101616-18.png||height="456" width="1097"]] ... ... @@ -630,12 +630,11 @@ 630 630 Cayenne. 631 631 632 632 600 +== **3.5 Trouble Shooting** == 633 633 634 -== **3.5 Shooting** ==602 +=== **3.5.1 Trouble to Join Helium** === 635 635 636 -=== **3.5.1 Trouble to Join Helium** === 637 637 638 - 639 639 ((( 640 640 **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://** 641 641 ... ... @@ -653,17 +653,10 @@ 653 653 ((( 654 654 //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)// 655 655 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 - 663 663 664 664 ))) 665 665 666 -=== **3.5.2 625 +=== **3.5.2 Packet Loss for AU915 / US915 Band** === 667 667 668 668 669 669 ((( ... ... @@ -672,12 +672,10 @@ 672 672 673 673 ((( 674 674 //The reason for this problem is that the node does not lock the channel after joining the network.// 675 - 676 - 677 677 ))) 678 678 679 679 ((( 680 - (% style="color:red" %)**Solution:**637 +**Solution:** 681 681 682 682 683 683 ))) ... ... @@ -687,17 +687,15 @@ 687 687 ))) 688 688 689 689 * ((( 690 - (% style="color:blue" %)**//AT Command: AT+CHE//**647 +//AT Command: AT+CHE// 691 691 ))) 692 692 693 693 * ((( 694 -// **Example:(% style="color:#037691" %)**AT+CHE=2**(%%)651 +//Example:**AT+CHE=2** ~/~/set channel mode to 1// 695 695 ))) 696 696 697 697 * ((( 698 -(% style="color:blue" %)**//Downlink Command: 0x24//** 699 - 700 - 655 +//Downlink Command: 0x24// 701 701 ))) 702 702 703 703 ((( ... ... @@ -704,14 +704,14 @@ 704 704 //Format: Command Code (0x24) followed by 1 bytes channel value.// 705 705 ))) 706 706 707 - 708 708 ((( 709 709 //If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.// 710 710 ))) 711 711 712 712 * ((( 713 -// **Example 1**: Downlink Payload:(% style="color:#037691" %)**0x2402**(%%)~/~/ set channel mode to 2//667 +//Example 1: Downlink Payload: **0x2402** ~/~/ set channel mode to 2// 714 714 669 + 715 715 716 716 ))) 717 717