<
From version < 98.1 >
edited by Kilight Cao
on 2023/03/20 14:14
To version < 103.1 >
edited by Kilight Cao
on 2023/11/20 11:36
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -5,26 +5,26 @@
5 5  
6 6  
7 7  
8 -= **1.  Use Dragino Gateways/Hotspots with Helium** =
8 += 1.  Use Dragino Gateways/Hotspots with Helium =
9 9  
10 -== **1.1  Support Models** ==
10 +== 1.1  Support Models ==
11 11  
12 12  
13 -//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  
... ... @@ -33,32 +33,27 @@
33 33  (% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]**
34 34  
35 35  
36 += 2.  Connect Data-Only Hotspot to Helium =
36 36  
37 -= **2.  Connect Data-Only Hotspot to Helium** =
38 +== 2.1  Prerequisites ==
38 38  
39 -== **2.1  Prerequisites** ==
40 40  
41 +* Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
41 41  
42 -* //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
43 +== 2.2  Step 1: Configure Frequency Band ==
43 43  
44 44  
46 +Each country has a requirement for frequency region. Choose the right one for your area.
45 45  
46 -
47 -== **2.2  Step 1: Configure Frequency Band** ==
48 -
49 -
50 -//Each country has a requirement for frequency region. Choose the right one for your area.//
51 -
52 52  [[image:image-20220531175337-1.png]]
53 53  
54 54  
51 +== 2.3  Step 2: Download the Helium-gateway-rs ==
55 55  
56 -== **2.3  Step 2: Download the Helium-gateway-rs** ==
57 57  
54 +Click Download Helium Server and the gateway will download the Helium-gateway-rs
58 58  
59 -//Click Download Helium Server and the gateway will download the Helium-gateway-rs//
60 60  
61 -
62 62  [[image:image-20220615150600-1.png||height="559" width="1045"]]
63 63  
64 64  
... ... @@ -74,12 +74,11 @@
74 74  [[image:image-20220615150717-3.png||height="605" width="1039"]]
75 75  
76 76  
72 +== 2.4  Step 3: Install the Helium-gateway-rs ==
77 77  
78 -== **2.4  Step 3: Install the Helium-gateway-rs** ==
79 79  
75 +Click (% style="color:blue" %)**Install Helium Server**(%%) to install gateway-rs.
80 80  
81 -//Click **Install Helium Server** to install gateway-rs.//
82 -
83 83  [[image:image-20220615150734-4.png||height="619" width="1035"]]
84 84  
85 85  Install the Helium gateway-rs
... ... @@ -88,30 +88,28 @@
88 88  (% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
89 89  
90 90  
85 +== 2.5  Step 4: Save&start the Helium Server ==
91 91  
92 -== **2.5  Step 4: Save&start the Helium Server** ==
93 93  
88 +By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.
94 94  
95 -//By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
96 96  
97 -
98 98  [[image:image-20220615150903-5.png||height="592" width="1031"]]
99 99  
100 100  
101 101  
102 -//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.
103 103  
104 104  [[image:image-20220615151057-6.png||height="580" width="1026"]]
105 105  
106 106  
100 +== 2.6  Step 5: Check Gateway Connection before onboarding ==
107 107  
108 -== **2.6  Step 5: Check Gateway Connection before onboarding** ==
109 109  
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.
110 110  
111 -//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.//
112 -
113 113  (((
114 -//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.
115 115  )))
116 116  
117 117  [[image:image-20220526094537-1.png||height="395" width="1323"]]
... ... @@ -120,25 +120,29 @@
120 120  (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
121 121  
122 122  
115 +== 2.7  Step 6: Onboarding Data-Only Hotspot ==
123 123  
124 -== **2.7  Step 6: Onboarding Data-Only Hotspot** ==
125 125  
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**
126 126  
127 -(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**
120 +**Now the users are able to connect the helium console with a data-only hotspot without any onboarding.**
128 128  
129 129  
130 -//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 +(% style="color:red" %)--**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**--
131 131  
132 -//Below are the steps we do as per above link here.//
133 133  
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.--
134 134  
128 +--Below are the steps we do as per above link here.--
129 +
130 +
135 135  (((
136 -(% 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.**//--
137 137  )))
138 138  
139 139  (% class="box" %)
140 140  (((
141 -[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
142 142  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
143 143  ~| Key  | Value  |
144 144  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
... ... @@ -157,65 +157,65 @@
157 157  ~| DC Balance  | 0  |
158 158  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
159 159  ~| Securities Balance | 0.00000000  |
160 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
156 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+--
161 161  )))
162 162  
163 163  
164 164  (((
165 -(% 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.**--
166 166  )))
167 167  
168 168  
169 169  
170 170  (((
171 -(% 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.**//--
172 172  )))
173 173  
174 174  (% class="box" %)
175 175  (((
176 -root@123123:~~# helium_gateway add ~-~-owner 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux ~-~-payer 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux
172 +--root@123123:~~# helium_gateway add ~-~-owner 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux ~-~-payer 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux--
177 177  
178 -{
179 -(% style="color:red" %)"address": "146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm",
174 +--{
175 +(% style="color:red" %)"address": "146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm",(%%)--
180 180  
181 181  (% style="color:red" %)
182 -"fee": (% style="color:black" %)65000,
178 +--"fee": (% style="color:black" %)65000,(%%)--
183 183  
184 184  (% style="color:red" %)
185 -"mode": "dataonly",
181 +--"mode": "dataonly",--
186 186  
187 187  (% style="color:red" %)
188 -"owner": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",
184 +--"owner": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",--
189 189  
190 190  (% style="color:red" %)
191 -"payer": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",
187 +--"payer": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",--
192 192  
193 193  (% style="color:red" %)
194 -"staking fee"(% style="color:black" %): 1000000,
190 +--"staking fee"(% style="color:black" %): 1000000,(%%)--
195 195  
196 196  (% style="color: red;" %)
197 -"txn": "CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM="
193 +--"txn": "CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM="--
198 198  
199 -}
195 +--}--
200 200  )))
201 201  
202 202  (((
203 -//We got the txn info from this step.//
199 +--//We got the txn info from this step.//--
204 204  
205 205  
206 206  
207 -(% 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.**//--
208 208  
209 209  
210 -(% 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.**--
211 211  
212 212  
213 -//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.--
214 214  )))
215 215  
216 216  (% class="box" %)
217 217  (((
218 -[root@]# helium-wallet hotspots add CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM=
214 +--[root@]# helium-wallet hotspots add CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM=
219 219  Password: [hidden]
220 220  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
221 221  ~| Key  | Value  |
... ... @@ -249,18 +249,18 @@
249 249  ~| Staking fee (DC)  | 1000000  |
250 250  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
251 251  ~| Hash  | i6BQAI4Ehnd7nb8zfvegprhO2fOI1rj4UEPbAVC2sWk  |
252 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
248 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+--
253 253  )))
254 254  
255 255  (((
256 256  
257 257  
258 -(% 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.**//--
259 259  )))
260 260  
261 261  (% class="box" %)
262 262  (((
263 -[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
264 264  Password: [hidden]
265 265  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
266 266  ~| Key  | Value  |
... ... @@ -306,30 +306,29 @@
306 306  ~| Elevation  | 0  |
307 307  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
308 308  ~| Hash  | P1P8olxrzPJ1f3HWiLxcSincdF5fDLLCt2HbpYBhWwk  |
309 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
305 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+--
310 310  )))
311 311  
312 312  
313 313  (((
314 -(% 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.**--
315 315  )))
316 316  
317 317  (((
318 -//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.--
319 319  
320 -
321 321  
322 322  )))
323 323  
324 -== **2.8  Debug Connection** ==
319 +== 2.8  Debug Connection ==
325 325  
326 -=== **2.8.1  Check pkt-fwd running Log** ===
321 +=== 2.8.1  Check pkt-fwd running Log ===
327 327  
328 328  
329 -//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.
330 330  
331 331  (((
332 -//Below logs shows the gateway receive two LoRaWAN packets.//
327 +Below logs shows the gateway receive two LoRaWAN packets.
333 333  )))
334 334  
335 335  (% class="box" %)
... ... @@ -354,10 +354,9 @@
354 354  )))
355 355  
356 356  
352 +=== 2.8.2  Check gateway-rs Log ===
357 357  
358 -=== **2.8.2  Check gateway-rs Log** ===
359 359  
360 -
361 361  //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
362 362  
363 363  [[image:image-20220531175809-7.png]]
... ... @@ -366,10 +366,9 @@
366 366  (% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
367 367  
368 368  
363 +=== 2.8.3  View the public key address and animal name ===
369 369  
370 -=== **2.8.3  View the public key address and animal name** ===
371 371  
372 -
373 373  (% class="box" %)
374 374  (((
375 375  (((
... ... @@ -391,38 +391,48 @@
391 391  Hostpot key and animal name
392 392  
393 393  
387 +=== 2.8.4  Backup/Restor gateway-rs key ===
394 394  
395 -=== **2.8.4  Backup/Restor gateway-rs key** ===
396 396  
397 -
398 398  (((
399 -//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.
400 400  )))
401 401  
402 402  [[image:image-20220531175919-9.png]]
403 403  
404 404  
397 +=== 2.8.5  How to manually download helium gateway-rs via SSH access to the gateway Linux console ===
405 405  
406 -== **2.9  Forward the data to the other server** ==
407 407  
408 -=== **2.9.1  Introduction** ===
400 +(% class="box infomessage" %)
401 +(((
402 +**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]]**
409 409  
404 +**opkg install helium-gateway-rs-dragino.ipk **
405 +)))
410 410  
407 +[[image:image-20231120113632-1.png||height="255" width="1365"]]
408 +
409 +
410 +== 2.9  Forward the data to the other server ==
411 +
412 +=== 2.9.1  Introduction ===
413 +
414 +
411 411  (((
412 -//The Dragino gateway has supports the double server settings.//
416 +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.//
420 +Users can back to the page of Semtech UDP to configure other server settings.
417 417  
418 -
419 419  
420 420  )))
421 421  
422 -=== **2.9.2  Example** ===
425 +=== 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,23 +441,20 @@
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  
450 +== 2.10  Connect Full Hotspot to Helium ==
447 447  
448 -== **2.10  Connect Full Hotspot to Helium** ==
449 449  
450 450  
454 += 3.  Use Dragino Sensors with Helium =
451 451  
452 -= **3.  Use Dragino Sensors with Helium** =
456 +== 3.1  How to add up user's end-node with Helium console ==
453 453  
458 +=== 3.1.1  Step 1: Login the Helium console ===
454 454  
455 -== **3.1  How to add up user's end-node with Helium console** ==
456 456  
457 -
458 -=== **3.1.1  Step 1: Login the Helium console** ===
459 -
460 -
461 461  //User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
462 462  
463 463  [[image:image-20220531180150-12.png]]
... ... @@ -465,23 +465,21 @@
465 465  login Helium console
466 466  
467 467  
468 +=== 3.1.2  Step 2: Add up your end-node's key ===
468 468  
469 -=== **3.1.2  Step 2: Add up your end-node's key** ===
470 470  
471 +User add up end-node's key from console ~-~->dervice
471 471  
472 -//User add up end-node's key from console ~-~->dervice//
473 -
474 474  [[image:image-20220531180224-13.png]]
475 475  
476 476  To add a device
477 477  
478 478  
478 +=== 3.1.3  Step 3: Activate the end-node ===
479 479  
480 -=== **3.1.3  Step 3: Activate the end-node** ===
481 481  
482 -
483 483  (((
484 -//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**
485 485  )))
486 486  
487 487  [[image:image-20220531105239-2.png]]
... ... @@ -489,30 +489,27 @@
489 489  end-node traffic.
490 490  
491 491  
490 +=== 3.1.4 Check Raw Payload for End Node ===
492 492  
493 -=== **3.1.4 Check Raw Payload for End Node** ===
494 494  
495 -
496 496  Users can check what the end node has uplinked by checking the raw payload. as below:
497 497  
498 498  [[image:image-20220912161818-1.png]]
499 499  
500 500  
498 +== 3.2  How to use decoder ==
501 501  
502 -== **3.2  How to use decoder** ==
500 +=== 3.2.1  Step 1: Users can create decoders on functions ===
503 503  
504 -=== **3.2.1  Step 1: Users can create decoders on functions** ===
505 505  
506 -
507 507  [[image:image-20220531105325-3.png]]
508 508  
509 509  Decoder.
510 510  
511 511  
508 +=== 3.2.2  Step 2: Add a decoder in functions and apply it to the specified label ===
512 512  
513 -=== **3.2.2  Step 2: Add a decoder in functions and apply it to the specified label** ===
514 514  
515 -
516 516  [[image:image-20220526095629-6.png]]
517 517  
518 518  
... ... @@ -524,29 +524,27 @@
524 524  **//Add decoder complete.//**
525 525  
526 526  
522 +=== 3.2.3  Where is the decoder? ===
527 527  
528 -=== **3.2.3  Where is the decoder?** ===
529 529  
530 -
531 531  [[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
532 532  
533 533  [[image:image-20220617140118-1.png||height="550" width="883"]]
534 534  
535 535  
530 +== 3.3  How to send a downlink to end device from Helium ==
536 536  
537 -== **3.3  How to send a downlink to end device from Helium** ==
538 538  
539 -
540 540  (((
541 -//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:
542 542  )))
543 543  
544 544  (((
545 -//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]]
546 546  )))
547 547  
548 548  (((
549 -//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
550 550  )))
551 551  
552 552  (% class="box" %)
... ... @@ -559,12 +559,11 @@
559 559  Downlink
560 560  
561 561  
555 +== 3.4  How to add integration to different IoT Servers ==
562 562  
563 -== **3.4  How to add integration to different IoT Servers** ==
557 +=== 3.4.1  TagoIO ===
564 564  
565 -=== **3.4.1  TagoIO** ===
566 566  
567 -
568 568  **//The steps to add integration are very simple. Please see the following process.//**
569 569  
570 570  
... ... @@ -605,12 +605,11 @@
605 605  TagoIO.
606 606  
607 607  
600 +=== 3.4.2  Cayenne ===
608 608  
609 -=== **3.4.2  Cayenne** ===
610 610  
603 +The process of creating devices is similar to Tago.
611 611  
612 -//The process of creating devices is similar to Tago.//
613 -
614 614  [[image:image-20220526101616-18.png||height="456" width="1097"]]
615 615  
616 616  Cayenne.
... ... @@ -641,13 +641,11 @@
641 641  Cayenne.
642 642  
643 643  
635 +== 3.5  Trouble Shooting ==
644 644  
645 -== **3.5  Trouble Shooting** ==
637 +=== 3.5.1  Data-Only Hotspot is not connecting to Helium console ===
646 646  
647 647  
648 -=== **3.5.1 Data-Only Hotspot is not connecting to Helium console** ===
649 -
650 -
651 651  //**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
652 652  
653 653  
... ... @@ -656,10 +656,9 @@
656 656   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.
657 657  
658 658  
648 +=== 3.5.2  End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ===
659 659  
660 -=== **3.5.2 End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ** ===
661 661  
662 -
663 663  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.
664 664  
665 665  
... ... @@ -666,10 +666,9 @@
666 666  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]]
667 667  
668 668  
657 +=== 3.5.3  Trouble to Join Helium ===
669 669  
670 -=== **3.5.3  Trouble to Join Helium** ===
671 671  
672 -
673 673  (((
674 674  **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
675 675  
... ... @@ -677,29 +677,28 @@
677 677  )))
678 678  
679 679  (((
680 -//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)
681 681  )))
682 682  
683 683  (((
684 -//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)
685 685  )))
686 686  
687 687  (((
688 -//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)
689 689  
690 -
691 691  
692 692  )))
693 693  
694 -=== **3.5.4  Packet Loss for AU915 / US915 Band** ===
680 +=== 3.5.4  Packet Loss for AU915 / US915 Band ===
695 695  
696 696  
697 697  (((
698 -//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.
699 699  )))
700 700  
701 701  (((
702 -//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.
703 703  
704 704  
705 705  )))
... ... @@ -711,50 +711,49 @@
711 711  )))
712 712  
713 713  (((
714 -//(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.
715 715  )))
716 716  
717 717  * (((
718 -(% style="color:blue" %)**//AT Command: AT+CHE//**
704 +(% style="color:blue" %)**AT Command: AT+CHE**
719 719  )))
720 720  
721 721  * (((
722 -//**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
723 723  )))
724 724  
725 725  * (((
726 -(% style="color:blue" %)**//Downlink Command: 0x24//**
712 +(% style="color:blue" %)**Downlink Command: 0x24**
727 727  
728 728  
729 729  )))
730 730  
731 731  (((
732 -//Format: Command Code (0x24) followed by 1 bytes channel value.//
718 +Format: Command Code (0x24) followed by 1 bytes channel value.
733 733  )))
734 734  
735 735  
736 736  (((
737 -//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.
738 738  )))
739 739  
740 740  * (((
741 -//**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
742 742  
743 743  
744 744  )))
745 745  
746 746  (((
747 -//(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.
748 748  )))
749 749  
750 750  (((
751 -//The latest firmware for end node will have this bug fixed.//
737 +The latest firmware for end node will have this bug fixed.
752 752  
753 753  
740 +=== 3.5.5  ADR doesn't work in EU868 band. ===
754 754  
755 -=== **3.5.5  ADR doesn't work in EU868 band.** ===
756 756  
757 -
758 758  See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]]
759 759  
760 760  
image-20231120113632-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +36.7 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0