Changes for page Notes for Helium

Last modified by Edwin Chen on 2024/03/25 08:22
<
From version < 79.1 >
edited by Kilight Cao
on 2022/06/15 15:10
To version < 101.1 >
edited by Xiaoye
on 2023/07/13 09:52
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kilight
1 +XWiki.Xiaoye
Content
... ... @@ -1,4 +1,4 @@
1 -**~ Contents:**
1 +**~ Table of Contents:**
2 2  
3 3  {{toc/}}
4 4  
... ... @@ -5,10 +5,11 @@
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 12  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.
13 13  
14 14  (((
... ... @@ -15,81 +15,90 @@
15 15  Dragino has different gateway models that support different types.
16 16  )))
17 17  
18 -(% border="1" style="background-color:#ffffcc; width:510px" %)
19 -|(% colspan="4" style="width:589px" %)(% style="color:green" %)**Dragino Hotspots for Helium**
20 -|(% style="color:green; width:132px" %)**Model**|(% style="color:green; width:126px" %)**Hotspot Types**|(% style="color:green; width:121px" %)**Mining Ability**|(% style="color:green; width:203px" %)**Configure Instruction**
19 +(% border="1" style="background-color:#f2f2f2; width:510px" %)
20 +|(% colspan="4" style="background-color:#d9e2f3; color:#0070c0; width:589px" %)**Dragino Hotspots for Helium**
21 +|(% style="color:#0070c0; width:132px" %)**Model**|(% style="color:#0070c0; width:126px" %)**Hotspot Types**|(% style="color:#0070c0; width:121px" %)**Mining Ability**|(% style="color:#0070c0; width:203px" %)**Configure Instruction**
21 21  |(% style="width:132px" %)(((
22 22  [[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]],
23 23  
24 24  [[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]]
25 -)))|(% 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="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]]
26 +)))|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 +|(% style="width:132px" %)[[HP0D>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/195-hp0d.html]]|Full Hotspot|(% 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]]
27 27  
28 -**Frequencies on the Helium Network**
29 +(% style="color:blue" %)**Frequencies on the Helium Network**
29 29  
30 -* The frequencies currently available are CN470/EU868/US915/AU915
31 +* //The frequencies currently available are CN470/EU868/US915/AU915//
31 31  
32 -**Note**: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]
33 +(% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]**
33 33  
34 34  
35 -= 2. Connect Data-Only Hotspot to Helium =
36 += 2.  Connect Data-Only Hotspot to Helium =
36 36  
37 -== 2.1 Prerequisites ==
38 +== 2.1  Prerequisites ==
38 38  
40 +
39 39  * Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
40 40  
41 -== 2.2 Step 1: Configure Frequency Band ==
43 +== 2.2  Step 1: Configure Frequency Band ==
42 42  
45 +
43 43  Each country has a requirement for frequency region. Choose the right one for your area.
44 44  
45 45  [[image:image-20220531175337-1.png]]
46 46  
47 -Select fre
48 48  
51 +== 2.3  Step 2: Download the Helium-gateway-rs ==
49 49  
50 -== 2.3 Step 2: Download the Helium-gateway-rs ==
51 51  
52 52  Click Download Helium Server and the gateway will download the Helium-gateway-rs
53 53  
54 -[[image:image-20220531175421-2.png]]
55 55  
56 -Start download the Helium-gatewayrs
57 +[[image:image-20220615150600-1.png||height="559" width="1045"]]
57 57  
58 58  
59 -[[image:image-20220531175500-3.png]]
60 +//**Start download to Helium-gateway-rs**//
60 60  
61 -Helium-gatewayrs download success
62 +[[image:image-20220615150627-2.png||height="598" width="1044"]]
62 62  
64 +//**Helium-gatewayrs download success**//
63 63  
64 -If download fails, click and download again
65 65  
66 -[[image:image-20220531175530-4.png]]
67 +//**If download fails, click and download again**//
67 67  
68 -Helium-gatewayrs download fail
69 +[[image:image-20220615150717-3.png||height="605" width="1039"]]
69 69  
70 70  
71 -== 2.4 Step 3: Install the Helium-gateway-rs ==
72 +== 2.4  Step 3: Install the Helium-gateway-rs ==
72 72  
73 -Click **Install Helium Server** to install gateway-rs.
74 74  
75 -[[image:image-20220531175610-5.png]]
75 +Click (% style="color:blue" %)**Install Helium Server**(%%) to install gateway-rs.
76 76  
77 +[[image:image-20220615150734-4.png||height="619" width="1035"]]
78 +
77 77  Install the Helium gateway-rs
78 78  
79 -**Note**: User will see the echo characters of Helium gateway-rs have been installed successfully.
80 80  
82 +(% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
81 81  
82 -== 2.5 Step 4: Save&start the Helium Server ==
83 83  
84 -Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.
85 +== 2.5  Step 4: Save&start the Helium Server ==
85 85  
86 -[[image:image-20220531175650-6.png]]
87 87  
88 -Start Helium-gateway-rs
88 +By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.
89 89  
90 90  
91 -== 2.6 Step 5: Check Gateway Connection before onboarding ==
91 +[[image:image-20220615150903-5.png||height="592" width="1031"]]
92 92  
93 +
94 +
95 +Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.
96 +
97 +[[image:image-20220615151057-6.png||height="580" width="1026"]]
98 +
99 +
100 +== 2.6  Step 5: Check Gateway Connection before onboarding ==
101 +
102 +
93 93  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.
94 94  
95 95  (((
... ... @@ -98,26 +98,33 @@
98 98  
99 99  [[image:image-20220526094537-1.png||height="395" width="1323"]]
100 100  
101 -Check if the packet is transferred via LPS8
102 102  
103 -**Note:** The hotspot is not valid for search in Helium Console before onboarding.
112 +(% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
104 104  
105 105  
106 -== 2.7 Step 6: Onboarding Data-Only Hotspot ==
115 +== 2.7  Step 6: Onboarding Data-Only Hotspot ==
107 107  
108 -(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is not necessary, and it will gain very, very small awards on HNT by data-transfer .**
109 109  
110 -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.
118 +**After the Helium Network was successfully migrated to the Solana blockchain on April 18, 2023, 9 am PST (16:00 UTC). the onboarding for data-only hotspots is not quite yet**
111 111  
112 -Below are the steps we do as per above link here.
120 +**Now the users are able to connect the helium console with a data-only hotspot without any onboarding.**
113 113  
122 +
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 +
125 +
126 +--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.--
127 +
128 +--Below are the steps we do as per above link here.--
129 +
130 +
114 114  (((
115 -~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 +(% 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.**//--
116 116  )))
117 117  
118 118  (% class="box" %)
119 119  (((
120 -[root@iZt4n22vqvm7ajogrfiif6Z helium-wallet-v1.6.4-x86-64-linux]# helium-wallet info
137 +--[root@iZt4n22vqvm7ajogrfiif6Z helium-wallet-v1.6.4-x86-64-linux]# helium-wallet info
121 121  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
122 122  ~| Key  | Value  |
123 123  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
... ... @@ -136,54 +136,65 @@
136 136  ~| DC Balance  | 0  |
137 137  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
138 138  ~| Securities Balance | 0.00000000  |
139 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
156 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+--
140 140  )))
141 141  
159 +
142 142  (((
143 -**Note**: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.
161 +(% style="color:red" %)--**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.**--
144 144  )))
145 145  
146 146  
165 +
147 147  (((
148 -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.
167 +(% 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.**//--
149 149  )))
150 150  
151 151  (% class="box" %)
152 152  (((
153 -root@123123:~~# helium_gateway add ~-~-owner 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux ~-~-payer 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux
172 +--root@123123:~~# helium_gateway add ~-~-owner 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux ~-~-payer 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux--
154 154  
155 -{
156 -(% style="color:red" %)"address": "146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm",
174 +--{
175 +(% style="color:red" %)"address": "146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm",(%%)--
157 157  
158 158  (% style="color:red" %)
159 -"fee": (% style="color:black" %)65000,
178 +--"fee": (% style="color:black" %)65000,(%%)--
160 160  
161 161  (% style="color:red" %)
162 -"mode": "dataonly",
181 +--"mode": "dataonly",--
163 163  
164 164  (% style="color:red" %)
165 -"owner": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",
184 +--"owner": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",--
166 166  
167 167  (% style="color:red" %)
168 -"payer": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",
187 +--"payer": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",--
169 169  
170 170  (% style="color:red" %)
171 -"staking fee"(% style="color:black" %): 1000000,
190 +--"staking fee"(% style="color:black" %): 1000000,(%%)--
172 172  
173 173  (% style="color: red;" %)
174 -"txn": "CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM="
193 +--"txn": "CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM="--
175 175  
176 -}
195 +--}--
177 177  )))
178 178  
179 179  (((
180 -We got the txn info from this step.
181 -\\3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step. Note, below are two commands, the command without ~-~-commit is the preview mode. Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.
199 +--//We got the txn info from this step.//--
200 +
201 +
202 +
203 +(% 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.**//--
204 +
205 +
206 +(% style="color:red" %)--**Note: below are two commands, the command without ~-~-commit is the preview mode.**--
207 +
208 +
209 +--Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.--
182 182  )))
183 183  
184 184  (% class="box" %)
185 185  (((
186 -[root@]# helium-wallet hotspots add CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM=
214 +--[root@]# helium-wallet hotspots add CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM=
187 187  Password: [hidden]
188 188  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
189 189  ~| Key  | Value  |
... ... @@ -217,16 +217,18 @@
217 217  ~| Staking fee (DC)  | 1000000  |
218 218  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
219 219  ~| Hash  | i6BQAI4Ehnd7nb8zfvegprhO2fOI1rj4UEPbAVC2sWk  |
220 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
248 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+--
221 221  )))
222 222  
223 223  (((
224 -4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.
252 +
253 +
254 +(% style="color:blue" %)--//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//--
225 225  )))
226 226  
227 227  (% class="box" %)
228 228  (((
229 -[root@]# helium-wallet hotspots assert ~-~-gateway 146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm ~-~-lat=22.706922 ~-~-lon=114.242538 ~-~-mode dataonly
259 +--[root@]# helium-wallet hotspots assert ~-~-gateway 146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm ~-~-lat=22.706922 ~-~-lon=114.242538 ~-~-mode dataonly
230 230  Password: [hidden]
231 231  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
232 232  ~| Key  | Value  |
... ... @@ -272,23 +272,25 @@
272 272  ~| Elevation  | 0  |
273 273  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
274 274  ~| Hash  | P1P8olxrzPJ1f3HWiLxcSincdF5fDLLCt2HbpYBhWwk  |
275 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
305 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+--
276 276  )))
277 277  
308 +
278 278  (((
279 -Note: The add hotspot and assert location step might need some time to be effect.
310 +(% style="color:red" %)--**Note: The add hotspot and assert location step might need some time to be effect.**--
280 280  )))
281 281  
282 282  (((
283 -After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.
314 +--After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.--
284 284  
285 285  
286 286  )))
287 287  
288 -== 2.8 Debug Connection ==
319 +== 2.8  Debug Connection ==
289 289  
290 -=== 2.8.1 Check pkt-fwd running Log ===
321 +=== 2.8.1  Check pkt-fwd running Log ===
291 291  
323 +
292 292  This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.
293 293  
294 294  (((
... ... @@ -317,19 +317,20 @@
317 317  )))
318 318  
319 319  
320 -=== 2.8.2 Check gateway-rs Log ===
352 +=== 2.8.2  Check gateway-rs Log ===
321 321  
322 -SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.
323 323  
355 +//SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
356 +
324 324  [[image:image-20220531175809-7.png]]
325 325  
326 -Helium-gatewayrs log
327 327  
328 -**Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.
360 +(% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
329 329  
330 330  
331 -=== 2.8.3 View the public key address and animal name ===
363 +=== 2.8.3  View the public key address and animal name ===
332 332  
365 +
333 333  (% class="box" %)
334 334  (((
335 335  (((
... ... @@ -351,8 +351,9 @@
351 351  Hostpot key and animal name
352 352  
353 353  
354 -=== 2.8.4 Backup/Restor gateway-rs key ===
387 +=== 2.8.4  Backup/Restor gateway-rs key ===
355 355  
389 +
356 356  (((
357 357  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.
358 358  )))
... ... @@ -359,13 +359,25 @@
359 359  
360 360  [[image:image-20220531175919-9.png]]
361 361  
362 -Backup and restore key
363 363  
397 +=== 2.8.5  How to manually download helium gateway-rs via SSH access to the gateway Linux console ===
364 364  
365 -== 2.9 Forward the data to the other server ==
366 366  
367 -=== 2.9.1 Introduction ===
400 +(% class="box infomessage" %)
401 +(((
402 +**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]]**
368 368  
404 +**opkg install helium-gateway-rs-dragino.ipk **
405 +)))
406 +
407 +[[image:image-20230320141404-1.png]]
408 +
409 +
410 +== 2.9  Forward the data to the other server ==
411 +
412 +=== 2.9.1  Introduction ===
413 +
414 +
369 369  (((
370 370  The Dragino gateway has supports the double server settings.
371 371  )))
... ... @@ -376,44 +376,52 @@
376 376  
377 377  )))
378 378  
379 -=== 2.9.2 Example ===
425 +=== 2.9.2  Example ===
380 380  
427 +
381 381  The following takes The Things Network as another LoRaWAN server as an example.
382 382  
383 383  
384 -==== 2.9.2.1 Step 1: Back to Semtech UDP page ====
385 385  
432 +==== (% style="color:blue" %)**Step 1: Back to Semtech UDP page**(%%) ====
433 +
434 +
386 386  [[image:image-20220531180002-10.png]]
387 387  
388 388  Back to Semtech UDP page
389 389  
390 390  
391 -==== 2.9.2.2 Step 2: Configure the double server forwarding ====
392 392  
441 +==== (% style="color:blue" %)**Step 2: Configure the double server forwarding**(%%) ====
442 +
443 +
393 393  [[image:image-20220531180048-11.png]]
394 394  
395 -Configure the double server
396 396  
397 -The user can configure the secondary server and then click the button of Save&Apply.
447 +The user can configure the secondary server and then click the button of (% style="color:red" %)**Save&Apply**.
398 398  
399 399  
400 -== 2.10 Connect Full Hotspot to Helium ==
450 +== 2.10  Connect Full Hotspot to Helium ==
401 401  
402 -= 3. Use Dragino Sensors with Helium =
403 403  
404 -== 3.1 How to add up user's end-node with Helium console ==
405 405  
406 -=== 3.1.1 Step 1: Login the Helium console ===
454 += 3.  Use Dragino Sensors with Helium =
407 407  
408 -User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]
456 +== 3.1  How to add up user's end-node with Helium console ==
409 409  
458 +=== 3.1.1  Step 1: Login the Helium console ===
459 +
460 +
461 +//User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
462 +
410 410  [[image:image-20220531180150-12.png]]
411 411  
412 412  login Helium console
413 413  
414 414  
415 -=== 3.1.2 Step 2: Add up your end-node's key ===
468 +=== 3.1.2  Step 2: Add up your end-node's key ===
416 416  
470 +
417 417  User add up end-node's key from console ~-~->dervice
418 418  
419 419  [[image:image-20220531180224-13.png]]
... ... @@ -421,8 +421,9 @@
421 421  To add a device
422 422  
423 423  
424 -=== 3.1.3 Step 3:Activate the end-node ===
478 +=== 3.1.3  Step 3: Activate the end-node ===
425 425  
480 +
426 426  (((
427 427  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**
428 428  )))
... ... @@ -432,17 +432,27 @@
432 432  end-node traffic.
433 433  
434 434  
435 -== 3.2 How to use decoder ==
490 +=== 3.1.4 Check Raw Payload for End Node ===
436 436  
437 -=== 3.2.1 Step 1:Users can create decoders on functions ===
438 438  
493 +Users can check what the end node has uplinked by checking the raw payload. as below:
494 +
495 +[[image:image-20220912161818-1.png]]
496 +
497 +
498 +== 3.2  How to use decoder ==
499 +
500 +=== 3.2.1  Step 1: Users can create decoders on functions ===
501 +
502 +
439 439  [[image:image-20220531105325-3.png]]
440 440  
441 441  Decoder.
442 442  
443 443  
444 -=== 3.2.2 Step 2:Add a decoder in functions and apply it to the specified label ===
508 +=== 3.2.2  Step 2: Add a decoder in functions and apply it to the specified label ===
445 445  
510 +
446 446  [[image:image-20220526095629-6.png]]
447 447  
448 448  
... ... @@ -451,13 +451,20 @@
451 451  
452 452  [[image:image-20220526100057-8.png||height="352" width="1133"]]
453 453  
454 -Decoder.
519 +**//Add decoder complete.//**
455 455  
456 -Add decoder complete.
457 457  
522 +=== 3.2.3  Where is the decoder？ ===
458 458  
459 -== 3.3 How to send a downlink to end device from Helium ==
460 460  
525 +[[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
526 +
527 +[[image:image-20220617140118-1.png||height="550" width="883"]]
528 +
529 +
530 +== 3.3  How to send a downlink to end device from Helium ==
531 +
532 +
461 461  (((
462 462  The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example:
463 463  )))
... ... @@ -472,7 +472,7 @@
472 472  
473 473  (% class="box" %)
474 474  (((
475 -01 00 00 3C ~-~-> AQAAPA==
547 +**01 00 00 3C ~-~-> AQAAPA==**
476 476  )))
477 477  
478 478  [[image:image-20220524171341-21.png]]
... ... @@ -480,53 +480,54 @@
480 480  Downlink
481 481  
482 482  
483 -== 3.4 How to add integration to different IoT Servers ==
555 +== 3.4  How to add integration to different IoT Servers ==
484 484  
485 -=== 3.4.1 TagoIO ===
557 +=== 3.4.1  TagoIO ===
486 486  
487 -The steps to add integration are very simple. Please see the following process.
488 488  
560 +**//The steps to add integration are very simple. Please see the following process.//**
561 +
562 +
489 489  [[image:image-20220526102429-23.png||height="630" width="1198"]]
490 490  
491 -TagoIO.
492 492  
493 493  
494 -Generate the authorization code and then copy it.
567 +**//Generate the authorization code and then copy it.//**
495 495  
569 +
496 496  [[image:image-20220526100452-10.png||height="314" width="1188"]]
497 497  
498 -TagoIO.
499 499  
500 500  
501 -Apply Integration to Label.
574 +//**Apply Integration to Label.**//
502 502  
576 +
503 503  [[image:image-20220526100802-13.png]]
504 504  
505 505  
506 -TagoIO.
507 507  
508 -
509 509  [[image:image-20220526100927-14.png]]
510 510  
511 -TagoIO.
512 512  
513 513  
514 -Click LoRaWAN Helium,select the device.
585 +**//Click LoRaWAN Helium,select the device.//**
515 515  
587 +
516 516  [[image:image-20220526101215-15.png||height="599" width="1117"]]
517 517  
518 -TagoIO.
519 519  
520 520  
521 -Fill in DEVEUI and create my device.
592 +**//Fill in DEVEUI and create my device.//**
522 522  
594 +
523 523  [[image:image-20220526101419-16.png]]
524 524  
525 525  TagoIO.
526 526  
527 527  
528 -=== 3.4.2 Cayenne ===
600 +=== 3.4.2  Cayenne ===
529 529  
602 +
530 530  The process of creating devices is similar to Tago.
531 531  
532 532  [[image:image-20220526101616-18.png||height="456" width="1097"]]
... ... @@ -559,12 +559,35 @@
559 559  Cayenne.
560 560  
561 561  
562 -== 3.5 Trouble Shooting ==
635 +== 3.5  Trouble Shooting ==
563 563  
564 -=== 3.5.1 Trouble to Join Helium ===
637 +=== 3.5.1  Data-Only Hotspot is not connecting to Helium console ===
565 565  
639 +
640 +//**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
641 +
642 +
643 +1). The hotspot does not finish the onboarding to the helium blockchain.
644 +
645 + 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.
646 +
647 +
648 +=== 3.5.2  End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ===
649 +
650 +
651 +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.
652 +
653 +
654 +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]]
655 +
656 +
657 +=== 3.5.3  Trouble to Join Helium ===
658 +
659 +
566 566  (((
567 -Assume the device is powered correctly. If you don't see data in Helium. The possibilities are:
661 +**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
662 +
663 +
568 568  )))
569 569  
570 570  (((
... ... @@ -581,8 +581,9 @@
581 581  
582 582  )))
583 583  
584 -=== 3.5.2 Packet Loss for AU915 / US915 Band ===
680 +=== 3.5.4  Packet Loss for AU915 / US915 Band ===
585 585  
682 +
586 586  (((
587 587  The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.
588 588  )))
... ... @@ -589,10 +589,14 @@
589 589  
590 590  (((
591 591  The reason for this problem is that the node does not lock the channel after joining the network.
689 +
690 +
592 592  )))
593 593  
594 594  (((
595 -Solution:
694 +(% style="color:red" %)**Solution:**
695 +
696 +
596 596  )))
597 597  
598 598  (((
... ... @@ -600,15 +600,17 @@
600 600  )))
601 601  
602 602  * (((
603 -AT Command: AT+CHE
704 +(% style="color:blue" %)**AT Command: AT+CHE**
604 604  )))
605 605  
606 606  * (((
607 -Example:AT+CHE=1 ~/~/set channel mode to 1
708 +**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%)  ~/~/set channel mode to 1
608 608  )))
609 609  
610 610  * (((
611 -Downlink Command: 0x24
712 +(% style="color:blue" %)**Downlink Command: 0x24**
713 +
714 +
612 612  )))
613 613  
614 614  (((
... ... @@ -615,16 +615,15 @@
615 615  Format: Command Code (0x24) followed by 1 bytes channel value.
616 616  )))
617 617  
721 +
618 618  (((
619 -If the downlink payload=2401, it means set channel mode to 1, while type code is 24.
723 +If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.
620 620  )))
621 621  
622 622  * (((
623 -Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
624 -)))
727 +**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2
625 625  
626 -* (((
627 -Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5
729 +
628 628  )))
629 629  
630 630  (((
... ... @@ -633,4 +633,13 @@
633 633  
634 634  (((
635 635  The latest firmware for end node will have this bug fixed.
738 +
739 +
740 +=== 3.5.5  ADR doesn't work in EU868 band. ===
741 +
742 +
743 +See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]]
744 +
745 +
746 +
636 636  )))
image-20220617140118-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +55.5 KB
Content
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

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0