Changes for page Notes for Helium

Last modified by Edwin Chen on 2024/03/25 08:22
<
From version < 99.2 >
edited by Xiaoling
on 2023/03/23 17:20
To version < 102.1 >
edited by Kilight Cao
on 2023/11/20 11:36
>
Change comment: Uploaded new attachment "image-20231120113632-1.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Kilight
Content
... ... @@ -10,21 +10,21 @@
10 10  == 1.1  Support Models ==
11 11  
12 12  
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.//
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.
14 14  
15 15  (((
16 -//Dragino has different gateway models that support different types.//
16 +Dragino has different gateway models that support different types.
17 17  )))
18 18  
19 -(% border="1" style="background-color:#ffffcc; width:510px" %)
20 -|(% colspan="4" style="width:589px" %)(% style="color:green" %)**Dragino Hotspots for Helium**
21 -|(% 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**
22 22  |(% style="width:132px" %)(((
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.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]]
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]]
28 28  
29 29  (% style="color:blue" %)**Frequencies on the Helium Network**
30 30  
... ... @@ -38,14 +38,12 @@
38 38  == 2.1  Prerequisites ==
39 39  
40 40  
41 -* //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/]]
42 42  
43 -
44 -
45 45  == 2.2  Step 1: Configure Frequency Band ==
46 46  
47 47  
48 -//Each country has a requirement for frequency region. Choose the right one for your area.//
46 +Each country has a requirement for frequency region. Choose the right one for your area.
49 49  
50 50  [[image:image-20220531175337-1.png]]
51 51  
... ... @@ -53,7 +53,7 @@
53 53  == 2.3  Step 2: Download the Helium-gateway-rs ==
54 54  
55 55  
56 -//Click Download Helium Server and the gateway will download the Helium-gateway-rs//
54 +Click Download Helium Server and the gateway will download the Helium-gateway-rs
57 57  
58 58  
59 59  [[image:image-20220615150600-1.png||height="559" width="1045"]]
... ... @@ -74,7 +74,7 @@
74 74  == 2.4  Step 3: Install the Helium-gateway-rs ==
75 75  
76 76  
77 -//Click **Install Helium Server** to install gateway-rs.//
75 +Click (% style="color:blue" %)**Install Helium Server**(%%) to install gateway-rs.
78 78  
79 79  [[image:image-20220615150734-4.png||height="619" width="1035"]]
80 80  
... ... @@ -87,7 +87,7 @@
87 87  == 2.5  Step 4: Save&start the Helium Server ==
88 88  
89 89  
90 -//By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
88 +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  
93 93  [[image:image-20220615150903-5.png||height="592" width="1031"]]
... ... @@ -94,7 +94,7 @@
94 94  
95 95  
96 96  
97 -//Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.//
95 +Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.
98 98  
99 99  [[image:image-20220615151057-6.png||height="580" width="1026"]]
100 100  
... ... @@ -102,10 +102,10 @@
102 102  == 2.6  Step 5: Check Gateway Connection before onboarding ==
103 103  
104 104  
105 -//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.//
103 +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.
106 106  
107 107  (((
108 -//Check end device event from [[Helium Console>>url:https://staging-console.helium.wtf/]], We can see the LGT92 data arrived Helium via our hotspot.//
106 +Check end device event from [[Helium Console>>url:https://staging-console.helium.wtf/]], We can see the LGT92 data arrived Helium via our hotspot.
109 109  )))
110 110  
111 111  [[image:image-20220526094537-1.png||height="395" width="1323"]]
... ... @@ -117,21 +117,26 @@
117 117  == 2.7  Step 6: Onboarding Data-Only Hotspot ==
118 118  
119 119  
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 .**
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**
121 121  
120 +**Now the users are able to connect the helium console with a data-only hotspot without any onboarding.**
122 122  
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 -//Below are the steps we do as per above link here.//
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 .**--
126 126  
127 127  
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 +
128 128  (((
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.**//
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.**//--
130 130  )))
131 131  
132 132  (% class="box" %)
133 133  (((
134 -[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
135 135  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
136 136  ~| Key  | Value  |
137 137  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
... ... @@ -150,65 +150,65 @@
150 150  ~| DC Balance  | 0  |
151 151  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
152 152  ~| Securities Balance | 0.00000000  |
153 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
156 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+--
154 154  )))
155 155  
156 156  
157 157  (((
158 -(% style="color:red" %)**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.**--
159 159  )))
160 160  
161 161  
162 162  
163 163  (((
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.**//
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.**//--
165 165  )))
166 166  
167 167  (% class="box" %)
168 168  (((
169 -root@123123:~~# helium_gateway add ~-~-owner 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux ~-~-payer 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux
172 +--root@123123:~~# helium_gateway add ~-~-owner 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux ~-~-payer 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux--
170 170  
171 -{
172 -(% style="color:red" %)"address": "146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm",
174 +--{
175 +(% style="color:red" %)"address": "146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm",(%%)--
173 173  
174 174  (% style="color:red" %)
175 -"fee": (% style="color:black" %)65000,
178 +--"fee": (% style="color:black" %)65000,(%%)--
176 176  
177 177  (% style="color:red" %)
178 -"mode": "dataonly",
181 +--"mode": "dataonly",--
179 179  
180 180  (% style="color:red" %)
181 -"owner": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",
184 +--"owner": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",--
182 182  
183 183  (% style="color:red" %)
184 -"payer": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",
187 +--"payer": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",--
185 185  
186 186  (% style="color:red" %)
187 -"staking fee"(% style="color:black" %): 1000000,
190 +--"staking fee"(% style="color:black" %): 1000000,(%%)--
188 188  
189 189  (% style="color: red;" %)
190 -"txn": "CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM="
193 +--"txn": "CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM="--
191 191  
192 -}
195 +--}--
193 193  )))
194 194  
195 195  (((
196 -//We got the txn info from this step.//
199 +--//We got the txn info from this step.//--
197 197  
198 198  
199 199  
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.**//
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.**//--
201 201  
202 202  
203 -(% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.**
206 +(% style="color:red" %)--**Note: below are two commands, the command without ~-~-commit is the preview mode.**--
204 204  
205 205  
206 -//Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.//
209 +--Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.--
207 207  )))
208 208  
209 209  (% class="box" %)
210 210  (((
211 -[root@]# helium-wallet hotspots add CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM=
214 +--[root@]# helium-wallet hotspots add CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM=
212 212  Password: [hidden]
213 213  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
214 214  ~| Key  | Value  |
... ... @@ -242,18 +242,18 @@
242 242  ~| Staking fee (DC)  | 1000000  |
243 243  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
244 244  ~| Hash  | i6BQAI4Ehnd7nb8zfvegprhO2fOI1rj4UEPbAVC2sWk  |
245 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
248 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+--
246 246  )))
247 247  
248 248  (((
249 249  
250 250  
251 -(% style="color:blue" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//
254 +(% style="color:blue" %)--//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//--
252 252  )))
253 253  
254 254  (% class="box" %)
255 255  (((
256 -[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
257 257  Password: [hidden]
258 258  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
259 259  ~| Key  | Value  |
... ... @@ -299,16 +299,16 @@
299 299  ~| Elevation  | 0  |
300 300  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
301 301  ~| Hash  | P1P8olxrzPJ1f3HWiLxcSincdF5fDLLCt2HbpYBhWwk  |
302 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
305 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+--
303 303  )))
304 304  
305 305  
306 306  (((
307 -(% style="color:red" %)**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.**--
308 308  )))
309 309  
310 310  (((
311 -//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.--
312 312  
313 313  
314 314  )))
... ... @@ -318,10 +318,10 @@
318 318  === 2.8.1  Check pkt-fwd running Log ===
319 319  
320 320  
321 -//This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
324 +This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.
322 322  
323 323  (((
324 -//Below logs shows the gateway receive two LoRaWAN packets.//
327 +Below logs shows the gateway receive two LoRaWAN packets.
325 325  )))
326 326  
327 327  (% class="box" %)
... ... @@ -385,7 +385,7 @@
385 385  
386 386  
387 387  (((
388 -//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.//
391 +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.
389 389  )))
390 390  
391 391  [[image:image-20220531175919-9.png]]
... ... @@ -396,9 +396,9 @@
396 396  
397 397  (% class="box infomessage" %)
398 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]]
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]]**
400 400  
401 -opkg install helium-gateway-rs-dragino.ipk
404 +**opkg install helium-gateway-rs-dragino.ipk **
402 402  )))
403 403  
404 404  [[image:image-20230320141404-1.png]]
... ... @@ -410,11 +410,11 @@
410 410  
411 411  
412 412  (((
413 -//The Dragino gateway has supports the double server settings.//
416 +The Dragino gateway has supports the double server settings.
414 414  )))
415 415  
416 416  (((
417 -//Users can back to the page of Semtech UDP to configure other server settings.//
420 +Users can back to the page of Semtech UDP to configure other server settings.
418 418  
419 419  
420 420  )))
... ... @@ -422,7 +422,7 @@
422 422  === 2.9.2  Example ===
423 423  
424 424  
425 -//The following takes The Things Network as another LoRaWAN server as an example.//
428 +The following takes The Things Network as another LoRaWAN server as an example.
426 426  
427 427  
428 428  
... ... @@ -441,7 +441,7 @@
441 441  [[image:image-20220531180048-11.png]]
442 442  
443 443  
444 -//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**.
445 445  
446 446  
447 447  == 2.10  Connect Full Hotspot to Helium ==
... ... @@ -465,7 +465,7 @@
465 465  === 3.1.2  Step 2: Add up your end-node's key ===
466 466  
467 467  
468 -//User add up end-node's key from console ~-~->dervice//
471 +User add up end-node's key from console ~-~->dervice
469 469  
470 470  [[image:image-20220531180224-13.png]]
471 471  
... ... @@ -476,7 +476,7 @@
476 476  
477 477  
478 478  (((
479 -//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**//
482 +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**
480 480  )))
481 481  
482 482  [[image:image-20220531105239-2.png]]
... ... @@ -528,15 +528,15 @@
528 528  
529 529  
530 530  (((
531 -//The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://
534 +The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example:
532 532  )))
533 533  
534 534  (((
535 -//The Downlink command comes from this link：[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]//
538 +The Downlink command comes from this link：[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]
536 536  )))
537 537  
538 538  (((
539 -//Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds//
542 +Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
540 540  )))
541 541  
542 542  (% class="box" %)
... ... @@ -597,7 +597,7 @@
597 597  === 3.4.2  Cayenne ===
598 598  
599 599  
600 -//The process of creating devices is similar to Tago.//
603 +The process of creating devices is similar to Tago.
601 601  
602 602  [[image:image-20220526101616-18.png||height="456" width="1097"]]
603 603  
... ... @@ -642,7 +642,7 @@
642 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 643  
644 644  
645 -=== 3.5.2  End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ===
648 +=== 3.5.2  End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ===
646 646  
647 647  
648 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.
... ... @@ -661,15 +661,15 @@
661 661  )))
662 662  
663 663  (((
664 -//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)//
667 +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)
665 665  )))
666 666  
667 667  (((
668 -//2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)//
671 +2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)
669 669  )))
670 670  
671 671  (((
672 -//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)//
675 +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)
673 673  
674 674  
675 675  )))
... ... @@ -678,11 +678,11 @@
678 678  
679 679  
680 680  (((
681 -//The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.//
684 +The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.
682 682  )))
683 683  
684 684  (((
685 -//The reason for this problem is that the node does not lock the channel after joining the network.//
688 +The reason for this problem is that the node does not lock the channel after joining the network.
686 686  
687 687  
688 688  )))
... ... @@ -694,44 +694,44 @@
694 694  )))
695 695  
696 696  (((
697 -//(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.//
700 +(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.
698 698  )))
699 699  
700 700  * (((
701 -(% style="color:blue" %)**//AT Command: AT+CHE//**
704 +(% style="color:blue" %)**AT Command: AT+CHE**
702 702  )))
703 703  
704 704  * (((
705 -//**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%)  ~/~/set channel mode to 1//
708 +**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%)  ~/~/set channel mode to 1
706 706  )))
707 707  
708 708  * (((
709 -(% style="color:blue" %)**//Downlink Command: 0x24//**
712 +(% style="color:blue" %)**Downlink Command: 0x24**
710 710  
711 711  
712 712  )))
713 713  
714 714  (((
715 -//Format: Command Code (0x24) followed by 1 bytes channel value.//
718 +Format: Command Code (0x24) followed by 1 bytes channel value.
716 716  )))
717 717  
718 718  
719 719  (((
720 -//If the downlink payload=0x2402, it means set channel mode to use sub-band 2, 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.
721 721  )))
722 722  
723 723  * (((
724 -//**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2//
727 +**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2
725 725  
726 726  
727 727  )))
728 728  
729 729  (((
730 -//(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.//
733 +(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.
731 731  )))
732 732  
733 733  (((
734 -//The latest firmware for end node will have this bug fixed.//
737 +The latest firmware for end node will have this bug fixed.
735 735  
736 736  
737 737  === 3.5.5  ADR doesn't work in EU868 band. ===
image-20231120113632-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +36.7 KB
Content

Applications

Navigation

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