<
From version < 88.7 >
edited by Xiaoling
on 2022/07/23 14:52
To version < 99.2 >
edited by Xiaoling
on 2023/03/23 17:20
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -5,9 +5,9 @@
5 5  
6 6  
7 7  
8 -= **1.  Use Dragino Gateways/Hotspots with Helium** =
8 += 1.  Use Dragino Gateways/Hotspots with Helium =
9 9  
10 -== **1.1  Support Models** ==
10 +== 1.1  Support Models ==
11 11  
12 12  
13 13  //There are three types of hotspots that can connect to Helium. They are (% style="color:#4f81bd" %)**full-hotspot**(%%), (% style="color:#4f81bd" %)**light hotspot** (%%)and (% style="color:#4f81bd" %)**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.//
... ... @@ -23,10 +23,10 @@
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 -**Frequencies on the Helium Network**
29 +(% style="color:blue" %)**Frequencies on the Helium Network**
30 30  
31 31  * //The frequencies currently available are CN470/EU868/US915/AU915//
32 32  
... ... @@ -33,28 +33,29 @@
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  
36 += 2.  Connect Data-Only Hotspot to Helium =
36 36  
37 -= **2.  Connect Data-Only Hotspot to Helium** =
38 +== 2.1  Prerequisites ==
38 38  
39 -== **2.1  Prerequisites** ==
40 40  
41 -
42 42  * //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
43 43  
44 -== **2.2  Step 1: Configure Frequency Band** ==
45 45  
46 46  
45 +== 2.2  Step 1: Configure Frequency Band ==
46 +
47 +
47 47  //Each country has a requirement for frequency region. Choose the right one for your area.//
48 48  
49 49  [[image:image-20220531175337-1.png]]
50 50  
51 51  
53 +== 2.3  Step 2: Download the Helium-gateway-rs ==
52 52  
53 -== **2.3  Step 2: Download the Helium-gateway-rs** ==
54 54  
55 -
56 56  //Click Download Helium Server and the gateway will download the Helium-gateway-rs//
57 57  
58 +
58 58  [[image:image-20220615150600-1.png||height="559" width="1045"]]
59 59  
60 60  
... ... @@ -70,7 +70,7 @@
70 70  [[image:image-20220615150717-3.png||height="605" width="1039"]]
71 71  
72 72  
73 -== **2.4  Step 3: Install the Helium-gateway-rs** ==
74 +== 2.4  Step 3: Install the Helium-gateway-rs ==
74 74  
75 75  
76 76  //Click **Install Helium Server** to install gateway-rs.//
... ... @@ -83,24 +83,24 @@
83 83  (% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
84 84  
85 85  
87 +== 2.5  Step 4: Save&start the Helium Server ==
86 86  
87 -== **2.5  Step 4: Save&start the Helium Server** ==
88 88  
89 -
90 90  //By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
91 91  
92 +
92 92  [[image:image-20220615150903-5.png||height="592" width="1031"]]
93 93  
94 94  
96 +
95 95  //Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.//
96 96  
97 97  [[image:image-20220615151057-6.png||height="580" width="1026"]]
98 98  
99 99  
102 +== 2.6  Step 5: Check Gateway Connection before onboarding ==
100 100  
101 -== **2.6  Step 5: Check Gateway Connection before onboarding** ==
102 102  
103 -
104 104  //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.//
105 105  
106 106  (((
... ... @@ -113,10 +113,9 @@
113 113  (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
114 114  
115 115  
117 +== 2.7  Step 6: Onboarding Data-Only Hotspot ==
116 116  
117 -== **2.7  Step 6: Onboarding Data-Only Hotspot** ==
118 118  
119 -
120 120  (% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**
121 121  
122 122  
... ... @@ -126,7 +126,7 @@
126 126  
127 127  
128 128  (((
129 -(% style="color:red" %)//**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.**//
129 +(% 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.**//
130 130  )))
131 131  
132 132  (% class="box" %)
... ... @@ -153,6 +153,7 @@
153 153  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
154 154  )))
155 155  
156 +
156 156  (((
157 157  (% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.**
158 158  )))
... ... @@ -160,7 +160,7 @@
160 160  
161 161  
162 162  (((
163 -(% style="color:red" %)//**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 +(% 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 164  )))
165 165  
166 166  (% class="box" %)
... ... @@ -196,7 +196,7 @@
196 196  
197 197  
198 198  
199 -(% style="color:red" %)//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**//
200 +(% 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.**//
200 200  
201 201  
202 202  (% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.**
... ... @@ -247,7 +247,7 @@
247 247  (((
248 248  
249 249  
250 -(% style="color:red" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//
251 +(% style="color:blue" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//
251 251  )))
252 252  
253 253  (% class="box" %)
... ... @@ -301,6 +301,7 @@
301 301  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
302 302  )))
303 303  
305 +
304 304  (((
305 305  (% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.**
306 306  )))
... ... @@ -308,13 +308,12 @@
308 308  (((
309 309  //After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//
310 310  
311 -
312 312  
313 313  )))
314 314  
315 -== **2.8  Debug Connection** ==
316 +== 2.8  Debug Connection ==
316 316  
317 -=== **2.8.1  Check pkt-fwd running Log** ===
318 +=== 2.8.1  Check pkt-fwd running Log ===
318 318  
319 319  
320 320  //This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
... ... @@ -345,10 +345,9 @@
345 345  )))
346 346  
347 347  
349 +=== 2.8.2  Check gateway-rs Log ===
348 348  
349 -=== **2.8.2  Check gateway-rs Log** ===
350 350  
351 -
352 352  //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
353 353  
354 354  [[image:image-20220531175809-7.png]]
... ... @@ -357,7 +357,7 @@
357 357  (% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
358 358  
359 359  
360 -=== **2.8.3  View the public key address and animal name** ===
360 +=== 2.8.3  View the public key address and animal name ===
361 361  
362 362  
363 363  (% class="box" %)
... ... @@ -381,10 +381,9 @@
381 381  Hostpot key and animal name
382 382  
383 383  
384 +=== 2.8.4  Backup/Restor gateway-rs key ===
384 384  
385 -=== **2.8.4  Backup/Restor gateway-rs key** ===
386 386  
387 -
388 388  (((
389 389  //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.//
390 390  )))
... ... @@ -392,12 +392,24 @@
392 392  [[image:image-20220531175919-9.png]]
393 393  
394 394  
394 +=== 2.8.5  How to manually download helium gateway-rs via SSH access to the gateway Linux console ===
395 395  
396 -== **2.9  Forward the data to the other server** ==
397 397  
398 -=== **2.9.1  Introduction** ===
397 +(% class="box infomessage" %)
398 +(((
399 +cd /tmp;wget -O helium-gateway-rs-dragino.ipk [[https:~~/~~/github.com/helium/gateway-rs/releases/download/v1.0.0-alpha.33/helium-gateway-v1.0.0-alpha.33-dragino.ipk>>https://github.com/helium/gateway-rs/releases/download/v1.0.0-alpha.33/helium-gateway-v1.0.0-alpha.33-dragino.ipk]]
399 399  
401 +opkg install helium-gateway-rs-dragino.ipk
402 +)))
400 400  
404 +[[image:image-20230320141404-1.png]]
405 +
406 +
407 +== 2.9  Forward the data to the other server ==
408 +
409 +=== 2.9.1  Introduction ===
410 +
411 +
401 401  (((
402 402  //The Dragino gateway has supports the double server settings.//
403 403  )))
... ... @@ -408,7 +408,7 @@
408 408  
409 409  )))
410 410  
411 -=== **2.9.2  Example** ===
422 +=== 2.9.2  Example ===
412 412  
413 413  
414 414  //The following takes The Things Network as another LoRaWAN server as an example.//
... ... @@ -423,6 +423,7 @@
423 423  Back to Semtech UDP page
424 424  
425 425  
437 +
426 426  ==== (% style="color:blue" %)**Step 2: Configure the double server forwarding**(%%) ====
427 427  
428 428  
... ... @@ -432,15 +432,15 @@
432 432  //The user can configure the secondary server and then click the button of **Save&Apply**.//
433 433  
434 434  
435 -== **2.10 Connect Full Hotspot to Helium** ==
447 +== 2.10  Connect Full Hotspot to Helium ==
436 436  
437 -= **3. Use Dragino Sensors with Helium** =
438 438  
439 439  
440 -== **3.1 How to add up user's end-node with Helium console** ==
451 += 3.  Use Dragino Sensors with Helium =
441 441  
453 +== 3.1  How to add up user's end-node with Helium console ==
442 442  
443 -=== **3.1.1 Step 1: Login the Helium console** ===
455 +=== 3.1.1  Step 1: Login the Helium console ===
444 444  
445 445  
446 446  //User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
... ... @@ -450,7 +450,7 @@
450 450  login Helium console
451 451  
452 452  
453 -=== **3.1.2 Step 2: Add up your end-node's key** ===
465 +=== 3.1.2  Step 2: Add up your end-node's key ===
454 454  
455 455  
456 456  //User add up end-node's key from console ~-~->dervice//
... ... @@ -460,7 +460,7 @@
460 460  To add a device
461 461  
462 462  
463 -=== **3.1.3 Step 3:Activate the end-node** ===
475 +=== 3.1.3  Step 3: Activate the end-node ===
464 464  
465 465  
466 466  (((
... ... @@ -472,17 +472,25 @@
472 472  end-node traffic.
473 473  
474 474  
475 -== **3.2 How to use decoder** ==
487 +=== 3.1.4 Check Raw Payload for End Node ===
476 476  
477 -=== **3.2.1 Step 1:Users can create decoders on functions** ===
478 478  
490 +Users can check what the end node has uplinked by checking the raw payload. as below:
479 479  
492 +[[image:image-20220912161818-1.png]]
493 +
494 +
495 +== 3.2  How to use decoder ==
496 +
497 +=== 3.2.1  Step 1: Users can create decoders on functions ===
498 +
499 +
480 480  [[image:image-20220531105325-3.png]]
481 481  
482 482  Decoder.
483 483  
484 484  
485 -=== **3.2.2 Step 2:Add a decoder in functions and apply it to the specified label** ===
505 +=== 3.2.2  Step 2: Add a decoder in functions and apply it to the specified label ===
486 486  
487 487  
488 488  [[image:image-20220526095629-6.png]]
... ... @@ -493,18 +493,20 @@
493 493  
494 494  [[image:image-20220526100057-8.png||height="352" width="1133"]]
495 495  
496 -
497 497  **//Add decoder complete.//**
498 498  
499 -=== **3.2.3 Where is the decoder?** ===
500 500  
519 +=== 3.2.3  Where is the decoder? ===
520 +
521 +
501 501  [[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
502 502  
503 503  [[image:image-20220617140118-1.png||height="550" width="883"]]
504 504  
505 -== **3.3 How to send a downlink to end device from Helium** ==
506 506  
527 +== 3.3  How to send a downlink to end device from Helium ==
507 507  
529 +
508 508  (((
509 509  //The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://
510 510  )))
... ... @@ -519,7 +519,7 @@
519 519  
520 520  (% class="box" %)
521 521  (((
522 -01 00 00 3C ~-~-> AQAAPA==
544 +**01 00 00 3C ~-~-> AQAAPA==**
523 523  )))
524 524  
525 525  [[image:image-20220524171341-21.png]]
... ... @@ -527,9 +527,9 @@
527 527  Downlink
528 528  
529 529  
530 -== **3.4 How to add integration to different IoT Servers** ==
552 +== 3.4  How to add integration to different IoT Servers ==
531 531  
532 -=== **3.4.1 TagoIO** ===
554 +=== 3.4.1  TagoIO ===
533 533  
534 534  
535 535  **//The steps to add integration are very simple. Please see the following process.//**
... ... @@ -572,7 +572,7 @@
572 572  TagoIO.
573 573  
574 574  
575 -=== **3.4.2 Cayenne** ===
597 +=== 3.4.2  Cayenne ===
576 576  
577 577  
578 578  //The process of creating devices is similar to Tago.//
... ... @@ -607,11 +607,31 @@
607 607  Cayenne.
608 608  
609 609  
610 -== **3.5 Trouble Shooting** ==
632 +== 3.5  Trouble Shooting ==
611 611  
612 -=== **3.5.1 Trouble to Join Helium** ===
634 +=== 3.5.1  Data-Only Hotspot is not connecting to Helium console ===
613 613  
614 614  
637 +//**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
638 +
639 +
640 +1). The hotspot does not finish the onboarding to the helium blockchain.
641 +
642 + after the 23 version of the gateway-rs, Helium requests the user to onboarding the devices to the blockchain, otherwise, your devices can't connect to the helium console. ~-~--> Please refer to [[Step 2.7>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Helium/#H2.7A0Step6:OnboardingData-OnlyHotspot]] to do it.
643 +
644 +
645 +=== 3.5.2  End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ===
646 +
647 +
648 +Make sure your blockchain region is the same as your hotspot settings. For example, as below, the blockchain is CN region, and software is configure to EU. The hotspot is able to get the OTAA Join Request from End Device on EU region. but due to block chain is CN region, Server will send the Join -Accept in CN region, so end device can't get the OTAA Join Accept.
649 +
650 +
651 +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]]
652 +
653 +
654 +=== 3.5.3  Trouble to Join Helium ===
655 +
656 +
615 615  (((
616 616  **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
617 617  
... ... @@ -632,7 +632,7 @@
632 632  
633 633  )))
634 634  
635 -=== **3.5.2 Packet Loss for AU915 / US915 Band** ===
677 +=== 3.5. Packet Loss for AU915 / US915 Band ===
636 636  
637 637  
638 638  (((
... ... @@ -641,10 +641,12 @@
641 641  
642 642  (((
643 643  //The reason for this problem is that the node does not lock the channel after joining the network.//
686 +
687 +
644 644  )))
645 645  
646 646  (((
647 -**Solution:**
691 +(% style="color:red" %)**Solution:**
648 648  
649 649  
650 650  )))
... ... @@ -654,15 +654,17 @@
654 654  )))
655 655  
656 656  * (((
657 -//AT Command: AT+CHE//
701 +(% style="color:blue" %)**//AT Command: AT+CHE//**
658 658  )))
659 659  
660 660  * (((
661 -//Example:**AT+CHE=2** ~/~/set channel mode to 1//
705 +//**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%)  ~/~/set channel mode to 1//
662 662  )))
663 663  
664 664  * (((
665 -//Downlink Command: 0x24//
709 +(% style="color:blue" %)**//Downlink Command: 0x24//**
710 +
711 +
666 666  )))
667 667  
668 668  (((
... ... @@ -669,14 +669,14 @@
669 669  //Format: Command Code (0x24) followed by 1 bytes channel value.//
670 670  )))
671 671  
718 +
672 672  (((
673 673  //If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.//
674 674  )))
675 675  
676 676  * (((
677 -//Example 1: Downlink Payload: **0x2402** ~/~/ set channel mode to 2//
724 +//**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2//
678 678  
679 -
680 680  
681 681  )))
682 682  
... ... @@ -686,4 +686,13 @@
686 686  
687 687  (((
688 688  //The latest firmware for end node will have this bug fixed.//
735 +
736 +
737 +=== 3.5.5  ADR doesn't work in EU868 band. ===
738 +
739 +
740 +See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]]
741 +
742 +
743 +
689 689  )))
image-20220912161818-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +53.7 KB
Content
image-20230320141404-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +57.8 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0