Skip to Content

Changes for page Notes for Helium

Last modified by Xiaoling on 2025/07/31 17:59
From version 104.2
edited by Xiaoling
on 2025/07/31 17:50
Change comment: There is no comment for this version
To version 99.6
edited by Xiaoling
on 2023/04/21 16:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,11 +17,15 @@
17 17  )))
18 18  
19 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 Instruon**
22 -|(% style="width:132px" %)[[DLOS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/225-dlos8n.html]], [[LPS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], [[LG308N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/229-lg308n.html]],[[LIG16>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]]|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"]]
23 -|(% 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]]
20 +|(% colspan="4" style="width:589px;background-color:#D9E2F3;color:#0070C0" %)**Dragino Hotspots for Helium**
21 +|(% style="color:#0070C0; width:132px" %)**Model**|(% style="color:green; width:126px" %)**Hotspot Types**|(% style="color:green; width:121px" %)**Mining Ability**|(% style="color:green; width:203px" %)**Configure Instruction**
22 +|(% style="width:132px" %)(((
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 +[[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.A0ConnectData-OnlyHotspottoHelium"]]
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 +
25 25  (% style="color:blue" %)**Frequencies on the Helium Network**
26 26  
27 27  * //The frequencies currently available are CN470/EU868/US915/AU915//
... ... @@ -34,12 +34,13 @@
34 34  == 2.1  Prerequisites ==
35 35  
36 36  
37 -* Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
41 +* //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
38 38  
43 +
39 39  == 2.2  Step 1: Configure Frequency Band ==
40 40  
41 41  
42 -Each country has a requirement for frequency region. Choose the right one for your area.
47 +//Each country has a requirement for frequency region. Choose the right one for your area.//
43 43  
44 44  [[image:image-20220531175337-1.png]]
45 45  
... ... @@ -47,7 +47,7 @@
47 47  == 2.3  Step 2: Download the Helium-gateway-rs ==
48 48  
49 49  
50 -Click Download Helium Server and the gateway will download the Helium-gateway-rs
55 +//Click Download Helium Server and the gateway will download the Helium-gateway-rs//
51 51  
52 52  
53 53  [[image:image-20220615150600-1.png||height="559" width="1045"]]
... ... @@ -68,7 +68,7 @@
68 68  == 2.4  Step 3: Install the Helium-gateway-rs ==
69 69  
70 70  
71 -Click (% style="color:blue" %)**Install Helium Server**(%%) to install gateway-rs.
76 +//Click **Install Helium Server** to install gateway-rs.//
72 72  
73 73  [[image:image-20220615150734-4.png||height="619" width="1035"]]
74 74  
... ... @@ -81,7 +81,7 @@
81 81  == 2.5  Step 4: Save&start the Helium Server ==
82 82  
83 83  
84 -By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.
89 +//By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
85 85  
86 86  
87 87  [[image:image-20220615150903-5.png||height="592" width="1031"]]
... ... @@ -88,7 +88,7 @@
88 88  
89 89  
90 90  
91 -Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.
96 +//Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.//
92 92  
93 93  [[image:image-20220615151057-6.png||height="580" width="1026"]]
94 94  
... ... @@ -96,10 +96,10 @@
96 96  == 2.6  Step 5: Check Gateway Connection before onboarding ==
97 97  
98 98  
99 -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.
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.//
100 100  
101 101  (((
102 -Check end device event from [[Helium Console>>url:https://staging-console.helium.wtf/]], We can see the LGT92 data arrived Helium via our hotspot.
107 +//Check end device event from [[Helium Console>>url:https://staging-console.helium.wtf/]], We can see the LGT92 data arrived Helium via our hotspot.//
103 103  )))
104 104  
105 105  [[image:image-20220526094537-1.png||height="395" width="1323"]]
... ... @@ -111,26 +111,21 @@
111 111  == 2.7  Step 6: Onboarding Data-Only Hotspot ==
112 112  
113 113  
114 -**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**
119 +(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**
115 115  
116 -**Now the users are able to connect the helium console with a data-only hotspot without any onboarding.**
117 117  
122 +//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 118  
119 -(% 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 +//Below are the steps we do as per above link here.//
120 120  
121 121  
122 ---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.--
123 -
124 ---Below are the steps we do as per above link here.--
125 -
126 -
127 127  (((
128 -(% 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.**//--
128 +(% 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.**//
129 129  )))
130 130  
131 131  (% class="box" %)
132 132  (((
133 ---[root@iZt4n22vqvm7ajogrfiif6Z helium-wallet-v1.6.4-x86-64-linux]# helium-wallet info
133 +[root@iZt4n22vqvm7ajogrfiif6Z helium-wallet-v1.6.4-x86-64-linux]# helium-wallet info
134 134  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
135 135  ~| Key  | Value  |
136 136  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
... ... @@ -140,7 +140,7 @@
140 140  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
141 141  ~| Type  | ed25519  |
142 142  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
143 -~| Sharded  | (% style="color:purple" %)false (%%) ~|
143 +~| Sharded  | (% style="color:purple" %)false (%%) |
144 144  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
145 145  ~| PwHash  | Argon2id13  |
146 146  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
... ... @@ -149,65 +149,65 @@
149 149  ~| DC Balance  | 0  |
150 150  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
151 151  ~| Securities Balance | 0.00000000  |
152 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+--
152 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
153 153  )))
154 154  
155 155  
156 156  (((
157 -(% style="color:red" %)--**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.**--
157 +(% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.**
158 158  )))
159 159  
160 160  
161 161  
162 162  (((
163 -(% 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.**//--
163 +(% 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" %)
167 167  (((
168 ---root@123123:~~# helium_gateway add ~-~-owner 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux ~-~-payer 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux--
168 +root@123123:~~# helium_gateway add ~-~-owner 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux ~-~-payer 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux
169 169  
170 ---{
171 -(% style="color:red" %)"address": "146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm",(%%)--
170 +{
171 +(% style="color:red" %)"address": "146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm",
172 172  
173 173  (% style="color:red" %)
174 ---"fee": (% style="color:black" %)65000,(%%)--
174 +"fee": (% style="color:black" %)65000,
175 175  
176 176  (% style="color:red" %)
177 ---"mode": "dataonly",--
177 +"mode": "dataonly",
178 178  
179 179  (% style="color:red" %)
180 ---"owner": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",--
180 +"owner": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",
181 181  
182 182  (% style="color:red" %)
183 ---"payer": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",--
183 +"payer": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",
184 184  
185 185  (% style="color:red" %)
186 ---"staking fee"(% style="color:black" %): 1000000,(%%)--
186 +"staking fee"(% style="color:black" %): 1000000,
187 187  
188 188  (% style="color: red;" %)
189 ---"txn": "CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM="--
189 +"txn": "CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM="
190 190  
191 ---}--
191 +}
192 192  )))
193 193  
194 194  (((
195 ---//We got the txn info from this step.//--
195 +//We got the txn info from this step.//
196 196  
197 197  
198 198  
199 -(% 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.**//--
199 +(% 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 -(% style="color:red" %)--**Note: below are two commands, the command without ~-~-commit is the preview mode.**--
202 +(% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.**
203 203  
204 204  
205 ---Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.--
205 +//Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.//
206 206  )))
207 207  
208 208  (% class="box" %)
209 209  (((
210 ---[root@]# helium-wallet hotspots add CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM=
210 +[root@]# helium-wallet hotspots add CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM=
211 211  Password: [hidden]
212 212  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
213 213  ~| Key  | Value  |
... ... @@ -241,18 +241,18 @@
241 241  ~| Staking fee (DC)  | 1000000  |
242 242  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
243 243  ~| Hash  | i6BQAI4Ehnd7nb8zfvegprhO2fOI1rj4UEPbAVC2sWk  |
244 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+--
244 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
245 245  )))
246 246  
247 247  (((
248 248  
249 249  
250 -(% style="color:blue" %)--//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//--
250 +(% 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" %)
254 254  (((
255 ---[root@]# helium-wallet hotspots assert ~-~-gateway 146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm ~-~-lat=22.706922 ~-~-lon=114.242538 ~-~-mode dataonly
255 +[root@]# helium-wallet hotspots assert ~-~-gateway 146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm ~-~-lat=22.706922 ~-~-lon=114.242538 ~-~-mode dataonly
256 256  Password: [hidden]
257 257  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
258 258  ~| Key  | Value  |
... ... @@ -298,16 +298,16 @@
298 298  ~| Elevation  | 0  |
299 299  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
300 300  ~| Hash  | P1P8olxrzPJ1f3HWiLxcSincdF5fDLLCt2HbpYBhWwk  |
301 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+--
301 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
302 302  )))
303 303  
304 304  
305 305  (((
306 -(% style="color:red" %)--**Note: The add hotspot and assert location step might need some time to be effect.**--
306 +(% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.**
307 307  )))
308 308  
309 309  (((
310 ---After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.--
310 +//After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//
311 311  
312 312  
313 313  )))
... ... @@ -317,10 +317,10 @@
317 317  === 2.8.1  Check pkt-fwd running Log ===
318 318  
319 319  
320 -This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.
320 +//This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
321 321  
322 322  (((
323 -Below logs shows the gateway receive two LoRaWAN packets.
323 +//Below logs shows the gateway receive two LoRaWAN packets.//
324 324  )))
325 325  
326 326  (% class="box" %)
... ... @@ -384,7 +384,7 @@
384 384  
385 385  
386 386  (((
387 -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.
387 +//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.//
388 388  )))
389 389  
390 390  [[image:image-20220531175919-9.png]]
... ... @@ -395,12 +395,12 @@
395 395  
396 396  (% class="box infomessage" %)
397 397  (((
398 -**cd /tmp;wget -O helium-gateway-rs-dragino.ipk [[https:~~/~~/www.dragino.com/downloads/downloads/LoRa_Gateway/3rd-software/helium/gateway-rs/data-only/gateway-rs-latest.ipk>>https://www.dragino.com/downloads/downloads/LoRa_Gateway/3rd-software/helium/gateway-rs/data-only/gateway-rs-latest.ipk]]**
398 +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  
400 -**opkg install helium-gateway-rs-dragino.ipk **
400 +opkg install helium-gateway-rs-dragino.ipk
401 401  )))
402 402  
403 -[[image:image-20231120113632-1.png||height="255" width="1365"]]
403 +[[image:image-20230320141404-1.png]]
404 404  
405 405  
406 406  == 2.9  Forward the data to the other server ==
... ... @@ -409,11 +409,11 @@
409 409  
410 410  
411 411  (((
412 -The Dragino gateway has supports the double server settings.
412 +//The Dragino gateway has supports the double server settings.//
413 413  )))
414 414  
415 415  (((
416 -Users can back to the page of Semtech UDP to configure other server settings.
416 +//Users can back to the page of Semtech UDP to configure other server settings.//
417 417  
418 418  
419 419  )))
... ... @@ -421,7 +421,7 @@
421 421  === 2.9.2  Example ===
422 422  
423 423  
424 -The following takes The Things Network as another LoRaWAN server as an example.
424 +//The following takes The Things Network as another LoRaWAN server as an example.//
425 425  
426 426  
427 427  
... ... @@ -440,7 +440,7 @@
440 440  [[image:image-20220531180048-11.png]]
441 441  
442 442  
443 -The user can configure the secondary server and then click the button of (% style="color:red" %)**Save&Apply**.
443 +//The user can configure the secondary server and then click the button of **Save&Apply**.//
444 444  
445 445  
446 446  == 2.10  Connect Full Hotspot to Helium ==
... ... @@ -464,7 +464,7 @@
464 464  === 3.1.2  Step 2: Add up your end-node's key ===
465 465  
466 466  
467 -User add up end-node's key from console ~-~->dervice
467 +//User add up end-node's key from console ~-~->dervice//
468 468  
469 469  [[image:image-20220531180224-13.png]]
470 470  
... ... @@ -475,7 +475,7 @@
475 475  
476 476  
477 477  (((
478 -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**
478 +//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**//
479 479  )))
480 480  
481 481  [[image:image-20220531105239-2.png]]
... ... @@ -525,12 +525,19 @@
525 525  
526 526  == 3.3  How to send a downlink to end device from Helium ==
527 527  
528 -The Helium server needs to convert to Base64 (**[[HEX to Base64 Online Tool>>https://base64.guru/converter/encode/hex]]**) format when sending the downlink command. Please refer to the following example:
529 529  
530 -The Downlink command comes from this link：[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]
529 +(((
530 +//The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://
531 +)))
531 531  
532 -Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
533 +(((
534 +//The Downlink command comes from this link：[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]//
535 +)))
533 533  
537 +(((
538 +//Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds//
539 +)))
540 +
534 534  (% class="box" %)
535 535  (((
536 536  **01 00 00 3C ~-~-> AQAAPA==**
... ... @@ -589,7 +589,7 @@
589 589  === 3.4.2  Cayenne ===
590 590  
591 591  
592 -The process of creating devices is similar to Tago.
599 +//The process of creating devices is similar to Tago.//
593 593  
594 594  [[image:image-20220526101616-18.png||height="456" width="1097"]]
595 595  
... ... @@ -653,15 +653,15 @@
653 653  )))
654 654  
655 655  (((
656 -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)
663 +//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)//
657 657  )))
658 658  
659 659  (((
660 -2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)
667 +//2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)//
661 661  )))
662 662  
663 663  (((
664 -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)
671 +//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)//
665 665  
666 666  
667 667  )))
... ... @@ -670,11 +670,11 @@
670 670  
671 671  
672 672  (((
673 -The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.
680 +//The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.//
674 674  )))
675 675  
676 676  (((
677 -The reason for this problem is that the node does not lock the channel after joining the network.
684 +//The reason for this problem is that the node does not lock the channel after joining the network.//
678 678  
679 679  
680 680  )))
... ... @@ -686,45 +686,44 @@
686 686  )))
687 687  
688 688  (((
689 -(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.
696 +//(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.//
690 690  )))
691 691  
692 692  * (((
693 -(% style="color:blue" %)**AT Command: AT+CHE**
700 +(% style="color:blue" %)**//AT Command: AT+CHE//**
694 694  )))
695 695  
696 696  * (((
697 -**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%)  ~/~/set channel mode to 1
704 +//**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%)  ~/~/set channel mode to 1//
698 698  )))
699 699  
700 700  * (((
701 -(% style="color:blue" %)**Downlink Command: 0x24**
708 +(% style="color:blue" %)**//Downlink Command: 0x24//**
702 702  
703 703  
704 704  )))
705 705  
706 706  (((
707 -Format: Command Code (0x24) followed by 1 bytes channel value.
714 +//Format: Command Code (0x24) followed by 1 bytes channel value.//
708 708  )))
709 709  
710 710  
711 -
712 712  (((
713 -If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.
719 +//If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.//
714 714  )))
715 715  
716 716  * (((
717 -**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2
723 +//**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2//
718 718  
719 719  
720 720  )))
721 721  
722 722  (((
723 -(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.
729 +//(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.//
724 724  )))
725 725  
726 726  (((
727 -The latest firmware for end node will have this bug fixed.
733 +//The latest firmware for end node will have this bug fixed.//
728 728  
729 729  
730 730  === 3.5.5  ADR doesn't work in EU868 band. ===
image-20231120113632-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -36.7 KB
Content