Changes for page Notes for Helium
Last modified by Edwin Chen on 2024/03/25 08:22
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -23,16 +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.ConnectData-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.A0ConnectData-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 29 30 -**Frequencies on the Helium Network** 31 - 32 32 * //The frequencies currently available are CN470/EU868/US915/AU915// 33 33 34 - 35 - 36 36 (% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]** 37 37 38 38 ... ... @@ -76,6 +76,7 @@ 76 76 [[image:image-20220615150717-3.png||height="605" width="1039"]] 77 77 78 78 76 + 79 79 == **2.4 Step 3: Install the Helium-gateway-rs** == 80 80 81 81 ... ... @@ -95,17 +95,20 @@ 95 95 96 96 //By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.// 97 97 96 + 98 98 [[image:image-20220615150903-5.png||height="592" width="1031"]] 99 99 100 100 101 -//Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.// 102 102 101 +//Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.// 102 + 103 103 [[image:image-20220615151057-6.png||height="580" width="1026"]] 104 104 105 105 106 -== **2.6 Step 5: Check Gateway Connection before onboarding** == 107 107 107 +== **2.6 Step 5: Check Gateway Connection before onboarding** == 108 108 109 + 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,10 +118,13 @@ 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 == 122 122 123 +== **2.7 Step 6: Onboarding Data-Only Hotspot** == 124 + 125 + 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 128 + 125 125 //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.// 126 126 127 127 //Below are the steps we do as per above link here.// ... ... @@ -128,7 +128,7 @@ 128 128 129 129 130 130 ((( 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 +(% 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.**// 132 132 ))) 133 133 134 134 (% class="box" %) ... ... @@ -155,13 +155,15 @@ 155 155 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+ 156 156 ))) 157 157 162 + 158 158 ((( 159 159 (% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.** 160 160 ))) 161 161 162 162 168 + 163 163 ((( 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 +(% 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.**// 165 165 ))) 166 166 167 167 (% class="box" %) ... ... @@ -194,11 +194,15 @@ 194 194 195 195 ((( 196 196 //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.**// 198 198 199 199 205 + 206 +(% 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.**// 207 + 208 + 200 200 (% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.** 201 201 211 + 202 202 //Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.// 203 203 ))) 204 204 ... ... @@ -242,7 +242,9 @@ 242 242 ))) 243 243 244 244 ((( 245 -//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**// 255 + 256 + 257 +(% style="color:blue" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**// 246 246 ))) 247 247 248 248 (% class="box" %) ... ... @@ -296,19 +296,21 @@ 296 296 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+ 297 297 ))) 298 298 311 + 299 299 ((( 300 -**Note: The add hotspot and assert location step might need some time to be effect.** 313 +(% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.** 301 301 ))) 302 302 303 303 ((( 304 304 //After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.// 305 305 319 + 306 306 307 307 ))) 308 308 309 -== **2.8 Debug Connection** == 323 +== **2.8 Debug Connection** == 310 310 311 -=== **2.8.1 Check pkt-fwd running Log** === 325 +=== **2.8.1 Check pkt-fwd running Log** === 312 312 313 313 314 314 //This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.// ... ... @@ -339,20 +339,22 @@ 339 339 ))) 340 340 341 341 342 -=== **2.8.2 Check gateway-rs Log** === 343 343 357 +=== **2.8.2 Check gateway-rs Log** === 344 344 359 + 345 345 //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.// 346 346 347 347 [[image:image-20220531175809-7.png]] 348 348 349 349 350 -**Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system. 365 +(% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.** 351 351 352 352 353 -=== **2.8.3 View the public key address and animal name** === 354 354 369 +=== **2.8.3 View the public key address and animal name** === 355 355 371 + 356 356 (% class="box" %) 357 357 ((( 358 358 ((( ... ... @@ -374,8 +374,10 @@ 374 374 Hostpot key and animal name 375 375 376 376 377 -=== **2.8.4 Backup/Restor gateway-rs key** === 378 378 394 +=== **2.8.4 Backup/Restor gateway-rs key** === 395 + 396 + 379 379 ((( 380 380 //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.// 381 381 ))) ... ... @@ -384,9 +384,9 @@ 384 384 385 385 386 386 387 -== **2.9 Forward the data to the other server** == 405 +== **2.9 Forward the data to the other server** == 388 388 389 -=== **2.9.1 Introduction** === 407 +=== **2.9.1 Introduction** === 390 390 391 391 392 392 ((( ... ... @@ -396,26 +396,29 @@ 396 396 ((( 397 397 //Users can back to the page of Semtech UDP to configure other server settings.// 398 398 417 + 399 399 400 400 ))) 401 401 402 -=== **2.9.2 Example** === 421 +=== **2.9.2 Example** === 403 403 404 404 405 405 //The following takes The Things Network as another LoRaWAN server as an example.// 406 406 407 407 408 -==== **2.9.2.1 Step 1: Back to Semtech UDP page** ==== 409 409 428 +==== (% style="color:blue" %)**Step 1: Back to Semtech UDP page**(%%) ==== 410 410 430 + 411 411 [[image:image-20220531180002-10.png]] 412 412 413 413 Back to Semtech UDP page 414 414 415 415 416 -==== **2.9.2.2 Step 2: Configure the double server forwarding** ==== 417 417 437 +==== (% style="color:blue" %)**Step 2: Configure the double server forwarding**(%%) ==== 418 418 439 + 419 419 [[image:image-20220531180048-11.png]] 420 420 421 421 ... ... @@ -422,17 +422,20 @@ 422 422 //The user can configure the secondary server and then click the button of **Save&Apply**.// 423 423 424 424 425 -== **2.10 Connect Full Hotspot to Helium** == 426 426 427 -= ** 3.UseDraginoSensorswithHelium** =447 +== **2.10 Connect Full Hotspot to Helium** == 428 428 429 429 430 -== **3.1 How to add up user's end-node with Helium console** == 431 431 451 += **3. Use Dragino Sensors with Helium** = 432 432 433 -=== **3.1.1 Step 1: Login the Helium console** === 434 434 454 +== **3.1 How to add up user's end-node with Helium console** == 435 435 456 + 457 +=== **3.1.1 Step 1: Login the Helium console** === 458 + 459 + 436 436 //User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]// 437 437 438 438 [[image:image-20220531180150-12.png]] ... ... @@ -440,9 +440,10 @@ 440 440 login Helium console 441 441 442 442 443 -=== **3.1.2 Step 2: Add up your end-node's key** === 444 444 468 +=== **3.1.2 Step 2: Add up your end-node's key** === 445 445 470 + 446 446 //User add up end-node's key from console ~-~->dervice// 447 447 448 448 [[image:image-20220531180224-13.png]] ... ... @@ -450,9 +450,10 @@ 450 450 To add a device 451 451 452 452 453 -=== **3.1.3 Step 3:Activate the end-node** === 454 454 479 +=== **3.1.3 Step 3: Activate the end-node** === 455 455 481 + 456 456 ((( 457 457 //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**// 458 458 ))) ... ... @@ -462,19 +462,21 @@ 462 462 end-node traffic. 463 463 464 464 465 -== **3.2 How to use decoder** == 466 466 467 -== =**3.2.1Step1:Userscan createdecoders on functions** ===492 +== **3.2 How to use decoder** == 468 468 494 +=== **3.2.1 Step 1: Users can create decoders on functions** === 469 469 496 + 470 470 [[image:image-20220531105325-3.png]] 471 471 472 472 Decoder. 473 473 474 474 475 -=== **3.2.2 Step 2:Add a decoder in functions and apply it to the specified label** === 476 476 503 +=== **3.2.2 Step 2: Add a decoder in functions and apply it to the specified label** === 477 477 505 + 478 478 [[image:image-20220526095629-6.png]] 479 479 480 480 ... ... @@ -483,18 +483,22 @@ 483 483 484 484 [[image:image-20220526100057-8.png||height="352" width="1133"]] 485 485 486 - 487 487 **//Add decoder complete.//** 488 488 489 -=== **3.2.3 Where is the decoder?** === 490 490 517 + 518 +=== **3.2.3 Where is the decoder?** === 519 + 520 + 491 491 [[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]] 492 492 493 493 [[image:image-20220617140118-1.png||height="550" width="883"]] 494 494 495 -== **3.3 How to send a downlink to end device from Helium** == 496 496 497 497 527 +== **3.3 How to send a downlink to end device from Helium** == 528 + 529 + 498 498 ((( 499 499 //The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~:// 500 500 ))) ... ... @@ -509,7 +509,7 @@ 509 509 510 510 (% class="box" %) 511 511 ((( 512 -01 00 00 3C ~-~-> AQAAPA== 544 +**01 00 00 3C ~-~-> AQAAPA==** 513 513 ))) 514 514 515 515 [[image:image-20220524171341-21.png]] ... ... @@ -517,11 +517,12 @@ 517 517 Downlink 518 518 519 519 520 -== **3.4 How to add integration to different IoT Servers** == 521 521 522 -== =**3.4.1TagoIO** ===553 +== **3.4 How to add integration to different IoT Servers** == 523 523 555 +=== **3.4.1 TagoIO** === 524 524 557 + 525 525 **//The steps to add integration are very simple. Please see the following process.//** 526 526 527 527 ... ... @@ -562,9 +562,10 @@ 562 562 TagoIO. 563 563 564 564 565 -=== **3.4.2 Cayenne** === 566 566 599 +=== **3.4.2 Cayenne** === 567 567 601 + 568 568 //The process of creating devices is similar to Tago.// 569 569 570 570 [[image:image-20220526101616-18.png||height="456" width="1097"]] ... ... @@ -597,11 +597,12 @@ 597 597 Cayenne. 598 598 599 599 600 -== **3.5 Trouble Shooting** == 601 601 602 -== =**3.5.1TroubletoJoinHelium** ===635 +== **3.5 Trouble Shooting** == 603 603 637 +=== **3.5.1 Trouble to Join Helium** === 604 604 639 + 605 605 ((( 606 606 **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://** 607 607 ... ... @@ -619,10 +619,11 @@ 619 619 ((( 620 620 //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)// 621 621 657 + 622 622 623 623 ))) 624 624 625 -=== **3.5.2 Packet Loss for AU915 / US915 Band** === 661 +=== **3.5.2 Packet Loss for AU915 / US915 Band** === 626 626 627 627 628 628 ((( ... ... @@ -631,10 +631,12 @@ 631 631 632 632 ((( 633 633 //The reason for this problem is that the node does not lock the channel after joining the network.// 670 + 671 + 634 634 ))) 635 635 636 636 ((( 637 -**Solution:** 675 +(% style="color:red" %)**Solution:** 638 638 639 639 640 640 ))) ... ... @@ -644,15 +644,17 @@ 644 644 ))) 645 645 646 646 * ((( 647 -//AT Command: AT+CHE// 685 +(% style="color:blue" %)**//AT Command: AT+CHE//** 648 648 ))) 649 649 650 650 * ((( 651 -//Example:**AT+CHE=2** ~/~/set channel mode to 1// 689 +//**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%) ~/~/set channel mode to 1// 652 652 ))) 653 653 654 654 * ((( 655 -//Downlink Command: 0x24// 693 +(% style="color:blue" %)**//Downlink Command: 0x24//** 694 + 695 + 656 656 ))) 657 657 658 658 ((( ... ... @@ -659,14 +659,14 @@ 659 659 //Format: Command Code (0x24) followed by 1 bytes channel value.// 660 660 ))) 661 661 702 + 662 662 ((( 663 663 //If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.// 664 664 ))) 665 665 666 666 * ((( 667 -//Example 1: Downlink Payload: **0x2402** ~/~/ set channel mode to 2// 708 +//**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2// 668 668 669 - 670 670 671 671 ))) 672 672