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 ling1 +XWiki.Xiaoye - Content
-
... ... @@ -1,4 +1,4 @@ 1 -**Contents:** 1 +**~ Contents:** 2 2 3 3 {{toc/}} 4 4 ... ... @@ -9,13 +9,15 @@ 9 9 10 10 There are three types of hotspots that can connect to Helium. They are full-hotspot, light hotspot and 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. 11 11 12 +((( 12 12 Dragino has different gateway models that support different types. 14 +))) 13 13 14 14 (% border="1" style="background-color:#ffffcc; width:785.989px" %) 15 15 |(% colspan="4" style="width:783px" %)(% style="color:green" %)**Dragino Hotspots for Helium** 16 16 |(% style="color:green; width:203px" %)**Model**|(% style="color:green; width:162px" %)**Hotspot Types**|(% style="color:green; width:134px" %)**Mining Ability**|(% style="color:green; width:250px" %)**Configure Instruction** 17 17 |(% style="width:203px" %)[[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]],[[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]]|(% style="color:#4f81bd; width:162px" %)**Data-Only Hotspot**|(% style="width:134px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]]|(% style="width:250px" %)[[Data-Only Hotspot Instruction>>url:https://wiki.dragino.com/index.php/Notes_for_Helium#Connect_Data-Only_Hotspot_to_Helium]] 18 -|(% style="width:203px" %)[[HP0D>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/195-hp0d.html]]|(% style="color:#4f81bd; width:162px" %)**Full Hotspo**t|(% style="width:134px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/full-hotspots]]|(% style="color:green; width:250px" %) FullHotspot Instruction-Not Finish20 +|(% style="width:203px" %)[[HP0D>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/195-hp0d.html]]|(% style="color:#4f81bd; width:162px" %)**Full Hotspo**t|(% style="width:134px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/full-hotspots]]|(% style="color:green; width:250px" %) 19 19 20 20 **Frequencies on the Helium Network** 21 21 ... ... @@ -123,7 +123,9 @@ 123 123 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+ 124 124 ))) 125 125 128 +((( 126 126 **Note**: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance. 130 +))) 127 127 128 128 129 129 ((( ... ... @@ -202,7 +202,9 @@ 202 202 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+ 203 203 ))) 204 204 209 +((( 205 205 4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2. 211 +))) 206 206 207 207 (% class="box" %) 208 208 ((( ... ... @@ -255,7 +255,9 @@ 255 255 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+ 256 256 ))) 257 257 264 +((( 258 258 Note: The add hotspot and assert location step might need some time to be effect. 266 +))) 259 259 260 260 ((( 261 261 After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain. ... ... @@ -326,7 +326,9 @@ 326 326 327 327 === 2.8.4 Backup/Restor gateway-rs key === 328 328 337 +((( 329 329 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. 339 +))) 330 330 331 331 [[image:https://wiki.dragino.com/images/thumb/e/ef/Backup_and_restore_key.png/600px-Backup_and_restore_key.png||height="343" width="600"]] 332 332 ... ... @@ -336,9 +336,13 @@ 336 336 337 337 === 2.9.1 Introduction === 338 338 349 +((( 339 339 The Dragino gateway has supports the double server settings. 351 +))) 340 340 353 +((( 341 341 Users can back to the page of Semtech UDP to configure other server settings. 355 +))) 342 342 343 343 === 2.9.2 Example === 344 344 ... ... @@ -382,7 +382,9 @@ 382 382 383 383 === 3.1.3 Step 3:Activate the end-node === 384 384 399 +((( 385 385 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** 401 +))) 386 386 387 387 [[image:https://wiki.dragino.com/images/thumb/4/45/End-node_traffic.png/600px-End-node_traffic.png||height="239" width="600"]] 388 388 ... ... @@ -412,22 +412,29 @@ 412 412 413 413 Add decoder complete. 414 414 415 - 416 416 == 3.3 How to send a downlink to end device from Helium == 417 417 433 +((( 418 418 The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example: 435 +))) 419 419 437 +((( 420 420 The Downlink command comes from this link:[[https:~~/~~/wiki.dragino.com/index.php?title=End_Device_Downlink_Command>>url:https://wiki.dragino.com/index.php?title=End_Device_Downlink_Command]] 439 +))) 421 421 441 +((( 422 422 Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds 443 +))) 423 423 445 +(% class="box" %) 446 +((( 424 424 01 00 00 3C ~-~-> AQAAPA== 448 +))) 425 425 426 426 [[image:https://wiki.dragino.com/images/thumb/c/c5/Helium_downlink.png/600px-Helium_downlink.png||height="360" width="600"]] 427 427 428 428 Downlink 429 429 430 - 431 431 == 3.4 How to add integration to different IoT Servers == 432 432 433 433 === 3.4.1 TagoIO === ... ... @@ -498,39 +498,72 @@ 498 498 499 499 === 3.5.1 Trouble to Join Helium === 500 500 524 +((( 501 501 Assume the device is powered correctly. If you don't see data in Helium. The possibilities are: 526 +))) 502 502 528 +((( 503 503 1) You are out of Helium Gateway coverage. (If you have other end nodes, you can check whether they work and what is the signal strength you see in the platform) 530 +))) 504 504 532 +((( 505 505 2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches) 534 +))) 506 506 536 +((( 507 507 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) 538 +))) 508 508 509 - 510 510 === 3.5.2 Packet Loss for AU915 / US915 Band === 511 511 542 +((( 512 512 The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different. 544 +))) 513 513 546 +((( 514 514 The reason for this problem is that the node does not lock the channel after joining the network. 548 +))) 515 515 550 +((( 516 516 Solution: 552 +))) 517 517 554 +((( 518 518 (1)If the user does not have a device to upgrade the firmware, you can use the AT+CHE command or the downlink command to set the channel. It is best to turn off the adaptive rate (ADR).Reset the device after setting the channel. 556 +))) 519 519 520 -* AT Command: AT+CHE 558 +* ((( 559 +AT Command: AT+CHE 560 +))) 521 521 522 -* Example:AT+CHE=1 ~/~/set channel mode to 1 562 +* ((( 563 +Example:AT+CHE=1 ~/~/set channel mode to 1 564 +))) 523 523 524 -* Downlink Command: 0x24 566 +* ((( 567 +Downlink Command: 0x24 568 +))) 525 525 570 +((( 526 526 Format: Command Code (0x24) followed by 1 bytes channel value. 572 +))) 527 527 574 +((( 528 528 If the downlink payload=2401, it means set channel mode to 1, while type code is 24. 576 +))) 529 529 530 -* Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1 578 +* ((( 579 +Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1 580 +))) 531 531 532 -* Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5 582 +* ((( 583 +Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5 584 +))) 533 533 586 +((( 534 534 (2)If the user has a device to upgrade the firmware, it is better to upgrade the device to the latest version. The latest version has fixed the problem that the AU915/US915 frequency does not lock the channel. 588 +))) 535 535 590 +((( 536 536 The latest firmware for end node will have this bug fixed. 592 +)))