<
From version < 104.1
edited by Edwin Chen
on 2024/03/25 08:22
To version < 93.1 >
edited by Edwin Chen
on 2022/09/05 18:02
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:#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**
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**
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 -)))|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]]
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 28  
29 29  (% style="color:blue" %)**Frequencies on the Helium Network**
30 30  
... ... @@ -33,26 +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 =
37 37  
38 -== 2.1  Prerequisites ==
37 += **2.  Connect Data-Only Hotspot to Helium** =
39 39  
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/]]
42 42  
43 -== 2.2  Step 1: Configure Frequency Band ==
42 +* //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
44 44  
44 +== **2.2  Step 1: Configure Frequency Band** ==
45 45  
46 -Each country has a requirement for frequency region. Choose the right one for your area.
47 47  
47 +//Each country has a requirement for frequency region. Choose the right one for your area.//
48 +
48 48  [[image:image-20220531175337-1.png]]
49 49  
50 50  
51 -== 2.3  Step 2: Download the Helium-gateway-rs ==
52 52  
53 +== **2.3  Step 2: Download the Helium-gateway-rs** ==
53 53  
54 -Click Download Helium Server and the gateway will download the Helium-gateway-rs
55 55  
56 +//Click Download Helium Server and the gateway will download the Helium-gateway-rs//
56 56  
57 57  [[image:image-20220615150600-1.png||height="559" width="1045"]]
58 58  
... ... @@ -69,11 +69,12 @@
69 69  [[image:image-20220615150717-3.png||height="605" width="1039"]]
70 70  
71 71  
72 -== 2.4  Step 3: Install the Helium-gateway-rs ==
73 73  
74 +== **2.4  Step 3: Install the Helium-gateway-rs** ==
74 74  
75 -Click (% style="color:blue" %)**Install Helium Server**(%%) to install gateway-rs.
76 76  
77 +//Click **Install Helium Server** to install gateway-rs.//
78 +
77 77  [[image:image-20220615150734-4.png||height="619" width="1035"]]
78 78  
79 79  Install the Helium gateway-rs
... ... @@ -82,28 +82,30 @@
82 82  (% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
83 83  
84 84  
85 -== 2.5  Step 4: Save&start the Helium Server ==
86 86  
88 +== **2.5  Step 4: Save&start the Helium Server** ==
87 87  
88 -By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.
89 89  
91 +//By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
90 90  
93 +
91 91  [[image:image-20220615150903-5.png||height="592" width="1031"]]
92 92  
93 93  
94 94  
95 -Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.
98 +//Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.//
96 96  
97 97  [[image:image-20220615151057-6.png||height="580" width="1026"]]
98 98  
99 99  
100 -== 2.6  Step 5: Check Gateway Connection before onboarding ==
101 101  
104 +== **2.6  Step 5: Check Gateway Connection before onboarding** ==
102 102  
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.
104 104  
107 +//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.//
108 +
105 105  (((
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.
110 +//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 107  )))
108 108  
109 109  [[image:image-20220526094537-1.png||height="395" width="1323"]]
... ... @@ -112,29 +112,25 @@
112 112  (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
113 113  
114 114  
115 -== 2.7  Step 6: Onboarding Data-Only Hotspot ==
116 116  
120 +== **2.7  Step 6: Onboarding Data-Only Hotspot** ==
117 117  
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**
119 119  
120 -**Now the users are able to connect the helium console with a data-only hotspot without any onboarding.**
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 .**
121 121  
122 122  
123 -(% style="color:red" %)--**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**--
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.//
124 124  
128 +//Below are the steps we do as per above link here.//
125 125  
126 ---User can refer [[this link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]] for how to onboarding a data-only hotspot. After onboarding the data-only hotspot, user can see the hotspot on Helium Console.--
127 127  
128 ---Below are the steps we do as per above link here.--
129 -
130 -
131 131  (((
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.**//--
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.**//
133 133  )))
134 134  
135 135  (% class="box" %)
136 136  (((
137 ---[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
138 138  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
139 139  ~| Key  | Value  |
140 140  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
... ... @@ -153,65 +153,65 @@
153 153  ~| DC Balance  | 0  |
154 154  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
155 155  ~| Securities Balance | 0.00000000  |
156 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+--
156 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
157 157  )))
158 158  
159 159  
160 160  (((
161 -(% 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.**
162 162  )))
163 163  
164 164  
165 165  
166 166  (((
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.**//--
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.**//
168 168  )))
169 169  
170 170  (% class="box" %)
171 171  (((
172 ---root@123123:~~# helium_gateway add ~-~-owner 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux ~-~-payer 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux--
172 +root@123123:~~# helium_gateway add ~-~-owner 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux ~-~-payer 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux
173 173  
174 ---{
175 -(% style="color:red" %)"address": "146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm",(%%)--
174 +{
175 +(% style="color:red" %)"address": "146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm",
176 176  
177 177  (% style="color:red" %)
178 ---"fee": (% style="color:black" %)65000,(%%)--
178 +"fee": (% style="color:black" %)65000,
179 179  
180 180  (% style="color:red" %)
181 ---"mode": "dataonly",--
181 +"mode": "dataonly",
182 182  
183 183  (% style="color:red" %)
184 ---"owner": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",--
184 +"owner": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",
185 185  
186 186  (% style="color:red" %)
187 ---"payer": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",--
187 +"payer": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux",
188 188  
189 189  (% style="color:red" %)
190 ---"staking fee"(% style="color:black" %): 1000000,(%%)--
190 +"staking fee"(% style="color:black" %): 1000000,
191 191  
192 192  (% style="color: red;" %)
193 ---"txn": "CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM="--
193 +"txn": "CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM="
194 194  
195 ---}--
195 +}
196 196  )))
197 197  
198 198  (((
199 ---//We got the txn info from this step.//--
199 +//We got the txn info from this step.//
200 200  
201 201  
202 202  
203 -(% style="color:blue" %)--//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**//--
203 +(% style="color:blue" %)//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**//
204 204  
205 205  
206 -(% 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.**
207 207  
208 208  
209 ---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.//
210 210  )))
211 211  
212 212  (% class="box" %)
213 213  (((
214 ---[root@]# helium-wallet hotspots add CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM=
214 +[root@]# helium-wallet hotspots add CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM=
215 215  Password: [hidden]
216 216  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
217 217  ~| Key  | Value  |
... ... @@ -245,18 +245,18 @@
245 245  ~| Staking fee (DC)  | 1000000  |
246 246  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
247 247  ~| Hash  | i6BQAI4Ehnd7nb8zfvegprhO2fOI1rj4UEPbAVC2sWk  |
248 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+--
248 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
249 249  )))
250 250  
251 251  (((
252 252  
253 253  
254 -(% 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.**//
255 255  )))
256 256  
257 257  (% class="box" %)
258 258  (((
259 ---[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
260 260  Password: [hidden]
261 261  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
262 262  ~| Key  | Value  |
... ... @@ -302,29 +302,30 @@
302 302  ~| Elevation  | 0  |
303 303  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
304 304  ~| Hash  | P1P8olxrzPJ1f3HWiLxcSincdF5fDLLCt2HbpYBhWwk  |
305 -+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+--
305 ++~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
306 306  )))
307 307  
308 308  
309 309  (((
310 -(% 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.**
311 311  )))
312 312  
313 313  (((
314 ---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.//
315 315  
316 +
316 316  
317 317  )))
318 318  
319 -== 2.8  Debug Connection ==
320 +== **2.8  Debug Connection** ==
320 320  
321 -=== 2.8.1  Check pkt-fwd running Log ===
322 +=== **2.8.1  Check pkt-fwd running Log** ===
322 322  
323 323  
324 -This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.
325 +//This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
325 325  
326 326  (((
327 -Below logs shows the gateway receive two LoRaWAN packets.
328 +//Below logs shows the gateway receive two LoRaWAN packets.//
328 328  )))
329 329  
330 330  (% class="box" %)
... ... @@ -349,9 +349,10 @@
349 349  )))
350 350  
351 351  
352 -=== 2.8.2  Check gateway-rs Log ===
353 353  
354 +=== **2.8.2  Check gateway-rs Log** ===
354 354  
356 +
355 355  //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
356 356  
357 357  [[image:image-20220531175809-7.png]]
... ... @@ -360,9 +360,10 @@
360 360  (% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
361 361  
362 362  
363 -=== 2.8.3  View the public key address and animal name ===
364 364  
366 +=== **2.8.3  View the public key address and animal name** ===
365 365  
368 +
366 366  (% class="box" %)
367 367  (((
368 368  (((
... ... @@ -384,48 +384,38 @@
384 384  Hostpot key and animal name
385 385  
386 386  
387 -=== 2.8.4  Backup/Restor gateway-rs key ===
388 388  
391 +=== **2.8.4  Backup/Restor gateway-rs key** ===
389 389  
393 +
390 390  (((
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.
395 +//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.//
392 392  )))
393 393  
394 394  [[image:image-20220531175919-9.png]]
395 395  
396 396  
397 -=== 2.8.5  How to manually download helium gateway-rs via SSH access to the gateway Linux console ===
398 398  
402 +== **2.9  Forward the data to the other server** ==
399 399  
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]]**
404 +=== **2.9.1  Introduction** ===
403 403  
404 -**opkg install helium-gateway-rs-dragino.ipk **
405 -)))
406 406  
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 -
415 415  (((
416 -The Dragino gateway has supports the double server settings.
408 +//The Dragino gateway has supports the double server settings.//
417 417  )))
418 418  
419 419  (((
420 -Users can back to the page of Semtech UDP to configure other server settings.
412 +//Users can back to the page of Semtech UDP to configure other server settings.//
421 421  
414 +
422 422  
423 423  )))
424 424  
425 -=== 2.9.2  Example ===
418 +=== **2.9.2  Example** ===
426 426  
427 427  
428 -The following takes The Things Network as another LoRaWAN server as an example.
421 +//The following takes The Things Network as another LoRaWAN server as an example.//
429 429  
430 430  
431 431  
... ... @@ -444,20 +444,23 @@
444 444  [[image:image-20220531180048-11.png]]
445 445  
446 446  
447 -The user can configure the secondary server and then click the button of (% style="color:red" %)**Save&Apply**.
440 +//The user can configure the secondary server and then click the button of **Save&Apply**.//
448 448  
449 449  
450 -== 2.10  Connect Full Hotspot to Helium ==
451 451  
444 +== **2.10  Connect Full Hotspot to Helium** ==
452 452  
453 453  
454 -= 3.  Use Dragino Sensors with Helium =
455 455  
456 -== 3.1  How to add up user's end-node with Helium console ==
448 += **3.  Use Dragino Sensors with Helium** =
457 457  
458 -=== 3.1.1  Step 1: Login the Helium console ===
459 459  
451 +== **3.1  How to add up user's end-node with Helium console** ==
460 460  
453 +
454 +=== **3.1.1  Step 1: Login the Helium console** ===
455 +
456 +
461 461  //User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
462 462  
463 463  [[image:image-20220531180150-12.png]]
... ... @@ -465,21 +465,23 @@
465 465  login Helium console
466 466  
467 467  
468 -=== 3.1.2  Step 2: Add up your end-node's key ===
469 469  
465 +=== **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
472 472  
468 +//User add up end-node's key from console ~-~->dervice//
469 +
473 473  [[image:image-20220531180224-13.png]]
474 474  
475 475  To add a device
476 476  
477 477  
478 -=== 3.1.3  Step 3: Activate the end-node ===
479 479  
476 +=== **3.1.3  Step 3: Activate the end-node** ===
480 480  
478 +
481 481  (((
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 +//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**//
483 483  )))
484 484  
485 485  [[image:image-20220531105239-2.png]]
... ... @@ -487,27 +487,21 @@
487 487  end-node traffic.
488 488  
489 489  
490 -=== 3.1.4 Check Raw Payload for End Node ===
491 491  
489 +== **3.2  How to use decoder** ==
492 492  
493 -Users can check what the end node has uplinked by checking the raw payload. as below:
491 +=== **3.2.1  Step 1: Users can create decoders on functions** ===
494 494  
495 -[[image:image-20220912161818-1.png]]
496 496  
497 -
498 -== 3.2  How to use decoder ==
499 -
500 -=== 3.2.1  Step 1: Users can create decoders on functions ===
501 -
502 -
503 503  [[image:image-20220531105325-3.png]]
504 504  
505 505  Decoder.
506 506  
507 507  
508 -=== 3.2.2  Step 2: Add a decoder in functions and apply it to the specified label ===
509 509  
500 +=== **3.2.2  Step 2: Add a decoder in functions and apply it to the specified label** ===
510 510  
502 +
511 511  [[image:image-20220526095629-6.png]]
512 512  
513 513  
... ... @@ -519,22 +519,31 @@
519 519  **//Add decoder complete.//**
520 520  
521 521  
522 -=== 3.2.3  Where is the decoder? ===
523 523  
515 +=== **3.2.3  Where is the decoder?** ===
524 524  
517 +
525 525  [[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
526 526  
527 527  [[image:image-20220617140118-1.png||height="550" width="883"]]
528 528  
529 529  
530 -== 3.3  How to send a downlink to end device from Helium ==
531 531  
532 -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:
524 +== **3.3  How to send a downlink to end device from Helium** ==
533 533  
534 -The Downlink command comes from this link:[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]
535 535  
536 -Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
527 +(((
528 +//The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://
529 +)))
537 537  
531 +(((
532 +//The Downlink command comes from this link:[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]//
533 +)))
534 +
535 +(((
536 +//Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds//
537 +)))
538 +
538 538  (% class="box" %)
539 539  (((
540 540  **01 00 00 3C ~-~-> AQAAPA==**
... ... @@ -545,11 +545,12 @@
545 545  Downlink
546 546  
547 547  
548 -== 3.4  How to add integration to different IoT Servers ==
549 549  
550 -=== 3.4.1  TagoIO ===
550 +== **3.4  How to add integration to different IoT Servers** ==
551 551  
552 +=== **3.4.1  TagoIO** ===
552 552  
554 +
553 553  **//The steps to add integration are very simple. Please see the following process.//**
554 554  
555 555  
... ... @@ -590,11 +590,12 @@
590 590  TagoIO.
591 591  
592 592  
593 -=== 3.4.2  Cayenne ===
594 594  
596 +=== **3.4.2  Cayenne** ===
595 595  
596 -The process of creating devices is similar to Tago.
597 597  
599 +//The process of creating devices is similar to Tago.//
600 +
598 598  [[image:image-20220526101616-18.png||height="456" width="1097"]]
599 599  
600 600  Cayenne.
... ... @@ -625,11 +625,13 @@
625 625  Cayenne.
626 626  
627 627  
628 -== 3.5  Trouble Shooting ==
629 629  
630 -=== 3.5.1  Data-Only Hotspot is not connecting to Helium console ===
632 +== **3.5  Trouble Shooting** ==
631 631  
632 632  
635 +=== **3.5.1 Data-Only Hotspot is not connecting to Helium console** ===
636 +
637 +
633 633  //**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
634 634  
635 635  
... ... @@ -638,7 +638,7 @@
638 638   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.
639 639  
640 640  
641 -=== 3.5.2  End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ===
646 +=== **3.5.2 End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ** ===
642 642  
643 643  
644 644  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.
... ... @@ -647,9 +647,10 @@
647 647  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]]
648 648  
649 649  
650 -=== 3.5.3  Trouble to Join Helium ===
651 651  
656 +=== **3.5.3  Trouble to Join Helium** ===
652 652  
658 +
653 653  (((
654 654  **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
655 655  
... ... @@ -657,28 +657,28 @@
657 657  )))
658 658  
659 659  (((
660 -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)
666 +//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)//
661 661  )))
662 662  
663 663  (((
664 -2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)
670 +//2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)//
665 665  )))
666 666  
667 667  (((
668 -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)
674 +//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)//
669 669  
670 670  
671 671  )))
672 672  
673 -=== 3.5.4  Packet Loss for AU915 / US915 Band ===
679 +=== **3.5.4  Packet Loss for AU915 / US915 Band** ===
674 674  
675 675  
676 676  (((
677 -The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.
683 +//The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.//
678 678  )))
679 679  
680 680  (((
681 -The reason for this problem is that the node does not lock the channel after joining the network.
687 +//The reason for this problem is that the node does not lock the channel after joining the network.//
682 682  
683 683  
684 684  )))
... ... @@ -690,51 +690,42 @@
690 690  )))
691 691  
692 692  (((
693 -(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.
699 +//(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.//
694 694  )))
695 695  
696 696  * (((
697 -(% style="color:blue" %)**AT Command: AT+CHE**
703 +(% style="color:blue" %)**//AT Command: AT+CHE//**
698 698  )))
699 699  
700 700  * (((
701 -**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%)  ~/~/set channel mode to 1
707 +//**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%)  ~/~/set channel mode to 1//
702 702  )))
703 703  
704 704  * (((
705 -(% style="color:blue" %)**Downlink Command: 0x24**
711 +(% style="color:blue" %)**//Downlink Command: 0x24//**
706 706  
707 707  
708 708  )))
709 709  
710 710  (((
711 -Format: Command Code (0x24) followed by 1 bytes channel value.
717 +//Format: Command Code (0x24) followed by 1 bytes channel value.//
712 712  )))
713 713  
714 714  
715 715  (((
716 -If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.
722 +//If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.//
717 717  )))
718 718  
719 719  * (((
720 -**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2
726 +//**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2//
721 721  
722 722  
723 723  )))
724 724  
725 725  (((
726 -(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.
732 +//(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.//
727 727  )))
728 728  
729 729  (((
730 -The latest firmware for end node will have this bug fixed.
731 -
732 -
733 -=== 3.5.5  ADR doesn't work in EU868 band. ===
734 -
735 -
736 -See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]]
737 -
738 -
739 -
736 +//The latest firmware for end node will have this bug fixed.//
740 740  )))
image-20220912161818-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -53.7 KB
Content
image-20230320141404-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -57.8 KB
Content
image-20231120113632-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -36.7 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0