Skip to Content

Changes for page Notes for Helium

Last modified by Edwin Chen on 2024/03/25 08:22
From version 88.6
edited by Xiaoling
on 2022/07/23 14:38
Change comment: There is no comment for this version
To version 88.7
edited by Xiaoling
on 2022/07/23 14:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -30,7 +30,6 @@
30 30  
31 31  * //The frequencies currently available are CN470/EU868/US915/AU915//
32 32  
33 -
34 34  (% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]**
35 35  
36 36  
... ... @@ -42,8 +42,6 @@
42 42  
43 43  * //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
44 44  
45 -
46 -
47 47  == **2.2  Step 1: Configure Frequency Band** ==
48 48  
49 49  
... ... @@ -116,10 +116,13 @@
116 116  (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
117 117  
118 118  
119 -== 2.7 Step 6: Onboarding Data-Only Hotspot ==
120 120  
117 +== **2.7  Step 6: Onboarding Data-Only Hotspot** ==
118 +
119 +
121 121  (% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**
122 122  
122 +
123 123  //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.//
124 124  
125 125  //Below are the steps we do as per above link here.//
... ... @@ -126,7 +126,7 @@
126 126  
127 127  
128 128  (((
129 -//**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: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.**//
130 130  )))
131 131  
132 132  (% class="box" %)
... ... @@ -158,8 +158,9 @@
158 158  )))
159 159  
160 160  
161 +
161 161  (((
162 -//**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.**//
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.**//
163 163  )))
164 164  
165 165  (% class="box" %)
... ... @@ -192,11 +192,15 @@
192 192  
193 193  (((
194 194  //We got the txn info from this step.//
195 -\\//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**//
196 196  
197 197  
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 +
201 +
198 198  (% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.**
199 199  
204 +
200 200  //Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.//
201 201  )))
202 202  
... ... @@ -240,7 +240,9 @@
240 240  )))
241 241  
242 242  (((
243 -//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//
248 +
249 +
250 +(% style="color:red" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//
244 244  )))
245 245  
246 246  (% class="box" %)
... ... @@ -295,18 +295,19 @@
295 295  )))
296 296  
297 297  (((
298 -**Note: The add hotspot and assert location step might need some time to be effect.**
305 +(% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.**
299 299  )))
300 300  
301 301  (((
302 302  //After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//
303 303  
311 +
304 304  
305 305  )))
306 306  
307 -== **2.8 Debug Connection** ==
315 +== **2.8  Debug Connection** ==
308 308  
309 -=== **2.8.1 Check pkt-fwd running Log** ===
317 +=== **2.8.1  Check pkt-fwd running Log** ===
310 310  
311 311  
312 312  //This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
... ... @@ -337,18 +337,19 @@
337 337  )))
338 338  
339 339  
340 -=== **2.8.2 Check gateway-rs Log** ===
341 341  
349 +=== **2.8.2  Check gateway-rs Log** ===
342 342  
351 +
343 343  //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
344 344  
345 345  [[image:image-20220531175809-7.png]]
346 346  
347 347  
348 -**Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.
357 +(% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
349 349  
350 350  
351 -=== **2.8.3 View the public key address and animal name** ===
360 +=== **2.8.3  View the public key address and animal name** ===
352 352  
353 353  
354 354  (% class="box" %)
... ... @@ -372,8 +372,10 @@
372 372  Hostpot key and animal name
373 373  
374 374  
375 -=== **2.8.4 Backup/Restor gateway-rs key** ===
376 376  
385 +=== **2.8.4  Backup/Restor gateway-rs key** ===
386 +
387 +
377 377  (((
378 378  //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.//
379 379  )))
... ... @@ -382,9 +382,9 @@
382 382  
383 383  
384 384  
385 -== **2.9 Forward the data to the other server** ==
396 +== **2.9  Forward the data to the other server** ==
386 386  
387 -=== **2.9.1 Introduction** ===
398 +=== **2.9.1  Introduction** ===
388 388  
389 389  
390 390  (((
... ... @@ -397,21 +397,22 @@
397 397  
398 398  )))
399 399  
400 -=== **2.9.2 Example** ===
411 +=== **2.9.2  Example** ===
401 401  
402 402  
403 403  //The following takes The Things Network as another LoRaWAN server as an example.//
404 404  
405 405  
406 -==== **2.9.2.1 Step 1: Back to Semtech UDP page** ====
407 407  
418 +==== (% style="color:blue" %)**Step 1: Back to Semtech UDP page**(%%) ====
408 408  
420 +
409 409  [[image:image-20220531180002-10.png]]
410 410  
411 411  Back to Semtech UDP page
412 412  
413 413  
414 -==== **2.9.2.2 Step 2: Configure the double server forwarding** ====
426 +==== (% style="color:blue" %)**Step 2: Configure the double server forwarding**(%%) ====
415 415  
416 416  
417 417  [[image:image-20220531180048-11.png]]