Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Bei
	1	+XWiki.Xiaoling

Content

...	...	@@ -1,4 +1,4 @@
1		-**~ Contents:**
	1	+**~ Table of Contents:**
2	2
3	3	{{toc/}}
4	4
...	...	@@ -5,10 +5,11 @@
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	12	//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	13
14	14	(((
...	...	@@ -32,14 +32,15 @@
32	32	(% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]**
33	33
34	34
35		-= **2. Connect Data-Only Hotspot to Helium** =
36	36
37		-== **2.1 Prerequisites** ==
	37	+= **2.  Connect Data-Only Hotspot to Helium** =
38	38
	39	+== **2.1  Prerequisites** ==
39	39
	41	+
40	40	* //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
41	41
42		-== **2.2 Step 1: Configure Frequency Band** ==
	44	+== **2.2  Step 1: Configure Frequency Band** ==
43	43
44	44
45	45	//Each country has a requirement for frequency region. Choose the right one for your area.//
...	...	@@ -47,9 +47,10 @@
47	47	[[image:image-20220531175337-1.png]]
48	48
49	49
50		-== **2.3 Step 2: Download the Helium-gateway-rs** ==
51	51
	53	+== **2.3  Step 2: Download the Helium-gateway-rs** ==
52	52
	55	+
53	53	//Click Download Helium Server and the gateway will download the Helium-gateway-rs//
54	54
55	55	[[image:image-20220615150600-1.png||height="559" width="1045"]]
...	...	@@ -67,7 +67,7 @@
67	67	[[image:image-20220615150717-3.png||height="605" width="1039"]]
68	68
69	69
70		-== **2.4 Step 3: Install the Helium-gateway-rs** ==
	73	+== **2.4  Step 3: Install the Helium-gateway-rs** ==
71	71
72	72
73	73	//Click **Install Helium Server** to install gateway-rs.//
...	...	@@ -76,25 +76,28 @@
76	76
77	77	Install the Helium gateway-rs
78	78
	82	+
79	79	(% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
80	80
81	81
82		-== **2.5 Step 4: Save&start the Helium Server** ==
83	83
	87	+== **2.5  Step 4: Save&start the Helium Server** ==
84	84
	89	+
85	85	//By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
86	86
87	87	[[image:image-20220615150903-5.png||height="592" width="1031"]]
88	88
89	89
90		-//Click **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.//
91	91
92	92	[[image:image-20220615151057-6.png||height="580" width="1026"]]
93	93
94	94
95		-== **2.6 Step 5: Check Gateway Connection before onboarding** ==
96	96
	101	+== **2.6  Step 5: Check Gateway Connection before onboarding** ==
97	97
	103	+
98	98	//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.//
99	99
100	100	(((
...	...	@@ -107,10 +107,13 @@
107	107	(% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
108	108
109	109
110		-== 2.7 Step 6: Onboarding Data-Only Hotspot ==
111	111
112		-(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is not necessary, and it will gain very, very small awards on HNT by data-transfer .**
	117	+== **2.7  Step 6: Onboarding Data-Only Hotspot** ==
113	113
	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 .**
	121	+
	122	+
114	114	//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.//
115	115
116	116	//Below are the steps we do as per above link here.//
...	...	@@ -117,7 +117,7 @@
117	117
118	118
119	119	(((
120		-//**1. Set up Helium-Wallet in my computer. [[https:~~/~~/docs.helium.com/wallets/cli-wallet>>url:https://docs.helium.com/wallets/cli-wallet]]. and funds this wallet. From this step, we got the wallet info as below.**//
	129	+(% style="color:red" %)//**1. Set up Helium-Wallet in my computer. [[https:~~/~~/docs.helium.com/wallets/cli-wallet>>url:https://docs.helium.com/wallets/cli-wallet]]. and funds this wallet. From this step, we got the wallet info as below.**//
121	121	)))
122	122
123	123	(% class="box" %)
...	...	@@ -149,8 +149,9 @@
149	149	)))
150	150
151	151
	161	+
152	152	(((
153		-//**2. Get txn. In the data-only hotspot. run below command to add a hotspot, owner is the owner wallet of this hotspot, payer is the payer to pay transaction cost.**//
	163	+(% style="color:red" %)//**2. Get txn. In the data-only hotspot. run below command to add a hotspot, owner is the owner wallet of this hotspot, payer is the payer to pay transaction cost.**//
154	154	)))
155	155
156	156	(% class="box" %)
...	...	@@ -183,11 +183,15 @@
183	183
184	184	(((
185	185	//We got the txn info from this step.//
186		-\\//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**//
187	187
188	188
	198	+
	199	+(% style="color:red" %)//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**//
	200	+
	201	+
189	189	(% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.**
190	190
	204	+
191	191	//Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.//
192	192	)))
193	193
...	...	@@ -231,7 +231,9 @@
231	231	)))
232	232
233	233	(((
234		-//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//
	248	+
	249	+
	250	+(% style="color:red" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//
235	235	)))
236	236
237	237	(% class="box" %)
...	...	@@ -286,18 +286,19 @@
286	286	)))
287	287
288	288	(((
289		-**Note: The add hotspot and assert location step might need some time to be effect.**
	305	+(% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.**
290	290	)))
291	291
292	292	(((
293	293	//After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//
294	294
	311	+
295	295
296	296	)))
297	297
298		-== **2.8 Debug Connection** ==
	315	+== **2.8  Debug Connection** ==
299	299
300		-=== **2.8.1 Check pkt-fwd running Log** ===
	317	+=== **2.8.1  Check pkt-fwd running Log** ===
301	301
302	302
303	303	//This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
...	...	@@ -328,18 +328,19 @@
328	328	)))
329	329
330	330
331		-=== **2.8.2 Check gateway-rs Log** ===
332	332
	349	+=== **2.8.2  Check gateway-rs Log** ===
333	333
	351	+
334	334	//SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
335	335
336	336	[[image:image-20220531175809-7.png]]
337	337
338	338
339		-**Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.
	357	+(% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
340	340
341	341
342		-=== **2.8.3 View the public key address and animal name** ===
	360	+=== **2.8.3  View the public key address and animal name** ===
343	343
344	344
345	345	(% class="box" %)
...	...	@@ -363,8 +363,10 @@
363	363	Hostpot key and animal name
364	364
365	365
366		-=== **2.8.4 Backup/Restor gateway-rs key** ===
367	367
	385	+=== **2.8.4  Backup/Restor gateway-rs key** ===
	386	+
	387	+
368	368	(((
369	369	//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.//
370	370	)))
...	...	@@ -373,9 +373,9 @@
373	373
374	374
375	375
376		-== **2.9 Forward the data to the other server** ==
	396	+== **2.9  Forward the data to the other server** ==
377	377
378		-=== **2.9.1 Introduction** ===
	398	+=== **2.9.1  Introduction** ===
379	379
380	380
381	381	(((
...	...	@@ -388,21 +388,22 @@
388	388
389	389	)))
390	390
391		-=== **2.9.2 Example** ===
	411	+=== **2.9.2  Example** ===
392	392
393	393
394	394	//The following takes The Things Network as another LoRaWAN server as an example.//
395	395
396	396
397		-==== **2.9.2.1 Step 1: Back to Semtech UDP page** ====
398	398
	418	+==== (% style="color:blue" %)**Step 1: Back to Semtech UDP page**(%%) ====
399	399
	420	+
400	400	[[image:image-20220531180002-10.png]]
401	401
402	402	Back to Semtech UDP page
403	403
404	404
405		-==== **2.9.2.2 Step 2: Configure the double server forwarding** ====
	426	+==== (% style="color:blue" %)**Step 2: Configure the double server forwarding**(%%) ====
406	406
407	407
408	408	[[image:image-20220531180048-11.png]]
...	...	@@ -475,7 +475,12 @@
475	475
476	476	**//Add decoder complete.//**
477	477
	499	+=== **3.2.3 Where is the decoder？** ===
478	478
	501	+[[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
	502	+
	503	+[[image:image-20220617140118-1.png||height="550" width="883"]]
	504	+
479	479	== **3.3 How to send a downlink to end device from Helium** ==
480	480
481	481
...	...	@@ -632,7 +632,7 @@
632	632	)))
633	633
634	634	* (((
635		-//Example:AT+CHE=1 ~/~/set channel mode to 1//
	661	+//Example:**AT+CHE=2** ~/~/set channel mode to 1//
636	636	)))
637	637
638	638	* (((
...	...	@@ -644,15 +644,12 @@
644	644	)))
645	645
646	646	(((
647		-//If the downlink payload=2401, it means set channel mode to 1, while type code is 24.//
	673	+//If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.//
648	648	)))
649	649
650	650	* (((
651		-//Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1//
652		-)))
	677	+//Example 1: Downlink Payload: **0x2402** ~/~/ set channel mode to 2//
653	653
654		-* (((
655		-//Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5//
656	656
657	657
658	658	)))