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
-
... ... @@ -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" %)Full Hotspot Inst ruction-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" %)[[Full Hotspot Instuction-Not Finish>>http://8.211.40.43/xwiki/bin/view/Main/User%20Manual%20for%20All%20Gateway%20models/HP0D/]] 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. ... ... @@ -300,12 +300,26 @@ 300 300 301 301 Helium-gatewayrs log 302 302 303 -Note: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system. 311 +**Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system. 304 304 305 305 === 2.8.3 View the public key address and animal name === 306 306 307 -{{{root@123123:~# helium_gateway key info { "address": "13KmbKLdpDfECx19kB2nX4suSzz3GskA4JVqKHAKiJ89kuyJx8T", "name": "great-mint-lizard" }}}} 315 +(% class="box" %) 316 +((( 317 +((( 318 +((( 319 +{{{root@123123:~# helium_gateway key info }}} 320 +{ 321 +))) 322 +))) 308 308 324 +((( 325 +(% style="color:red" %){{{"address": "13KmbKLdpDfECx19kB2nX4suSzz3GskA4JVqKHAKiJ89kuyJx8T",}}} 326 +{{{"name": "great-mint-lizard"}}}(%%) 327 +(% style="color:black" %)} 328 +))) 329 +))) 330 + 309 309 [[image:https://wiki.dragino.com/images/thumb/c/ce/Hostpot_key_and_animal_name.png/600px-Hostpot_key_and_animal_name.png||height="323" width="600"]] 310 310 311 311 Hostpot key and animal name ... ... @@ -312,7 +312,9 @@ 312 312 313 313 === 2.8.4 Backup/Restor gateway-rs key === 314 314 337 +((( 315 315 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 +))) 316 316 317 317 [[image:https://wiki.dragino.com/images/thumb/e/ef/Backup_and_restore_key.png/600px-Backup_and_restore_key.png||height="343" width="600"]] 318 318 ... ... @@ -322,9 +322,13 @@ 322 322 323 323 === 2.9.1 Introduction === 324 324 349 +((( 325 325 The Dragino gateway has supports the double server settings. 351 +))) 326 326 353 +((( 327 327 Users can back to the page of Semtech UDP to configure other server settings. 355 +))) 328 328 329 329 === 2.9.2 Example === 330 330 ... ... @@ -368,7 +368,9 @@ 368 368 369 369 === 3.1.3 Step 3:Activate the end-node === 370 370 399 +((( 371 371 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 +))) 372 372 373 373 [[image:https://wiki.dragino.com/images/thumb/4/45/End-node_traffic.png/600px-End-node_traffic.png||height="239" width="600"]] 374 374 ... ... @@ -398,22 +398,29 @@ 398 398 399 399 Add decoder complete. 400 400 401 - 402 402 == 3.3 How to send a downlink to end device from Helium == 403 403 433 +((( 404 404 The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example: 435 +))) 405 405 437 +((( 406 406 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 +))) 407 407 441 +((( 408 408 Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds 443 +))) 409 409 445 +(% class="box" %) 446 +((( 410 410 01 00 00 3C ~-~-> AQAAPA== 448 +))) 411 411 412 412 [[image:https://wiki.dragino.com/images/thumb/c/c5/Helium_downlink.png/600px-Helium_downlink.png||height="360" width="600"]] 413 413 414 414 Downlink 415 415 416 - 417 417 == 3.4 How to add integration to different IoT Servers == 418 418 419 419 === 3.4.1 TagoIO === ... ... @@ -484,39 +484,72 @@ 484 484 485 485 === 3.5.1 Trouble to Join Helium === 486 486 524 +((( 487 487 Assume the device is powered correctly. If you don't see data in Helium. The possibilities are: 526 +))) 488 488 528 +((( 489 489 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 +))) 490 490 532 +((( 491 491 2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches) 534 +))) 492 492 536 +((( 493 493 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 +))) 494 494 495 - 496 496 === 3.5.2 Packet Loss for AU915 / US915 Band === 497 497 542 +((( 498 498 The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different. 544 +))) 499 499 546 +((( 500 500 The reason for this problem is that the node does not lock the channel after joining the network. 548 +))) 501 501 550 +((( 502 502 Solution: 552 +))) 503 503 554 +((( 504 504 (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 +))) 505 505 506 -* AT Command: AT+CHE 558 +* ((( 559 +AT Command: AT+CHE 560 +))) 507 507 508 -* Example:AT+CHE=1 ~/~/set channel mode to 1 562 +* ((( 563 +Example:AT+CHE=1 ~/~/set channel mode to 1 564 +))) 509 509 510 -* Downlink Command: 0x24 566 +* ((( 567 +Downlink Command: 0x24 568 +))) 511 511 570 +((( 512 512 Format: Command Code (0x24) followed by 1 bytes channel value. 572 +))) 513 513 574 +((( 514 514 If the downlink payload=2401, it means set channel mode to 1, while type code is 24. 576 +))) 515 515 516 -* Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1 578 +* ((( 579 +Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1 580 +))) 517 517 518 -* Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5 582 +* ((( 583 +Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5 584 +))) 519 519 586 +((( 520 520 (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 +))) 521 521 590 +((( 522 522 The latest firmware for end node will have this bug fixed. 592 +)))