Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 0 removed)
  • image-20220912161818-1.png

Details

Page properties

Author

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

Content

...	...	@@ -41,7 +41,6 @@
41	41
42	42	* //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
43	43
44		-
45	45	== **2.2  Step 1: Configure Frequency Band** ==
46	46
47	47
...	...	@@ -71,6 +71,7 @@
71	71	[[image:image-20220615150717-3.png||height="605" width="1039"]]
72	72
73	73
	73	+
74	74	== **2.4  Step 3: Install the Helium-gateway-rs** ==
75	75
76	76
...	...	@@ -90,9 +90,11 @@
90	90
91	91	//By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
92	92
	93	+
93	93	[[image:image-20220615150903-5.png||height="592" width="1031"]]
94	94
95	95
	97	+
96	96	//Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.//
97	97
98	98	[[image:image-20220615151057-6.png||height="580" width="1026"]]
...	...	@@ -154,6 +154,7 @@
154	154	+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
155	155	)))
156	156
	159	+
157	157	(((
158	158	(% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.**
159	159	)))
...	...	@@ -302,6 +302,7 @@
302	302	+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
303	303	)))
304	304
	308	+
305	305	(((
306	306	(% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.**
307	307	)))
...	...	@@ -358,6 +358,7 @@
358	358	(% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
359	359
360	360
	365	+
361	361	=== **2.8.3  View the public key address and animal name** ===
362	362
363	363
...	...	@@ -406,6 +406,7 @@
406	406	(((
407	407	//Users can back to the page of Semtech UDP to configure other server settings.//
408	408
	414	+
409	409
410	410	)))
411	411
...	...	@@ -434,6 +434,7 @@
434	434	//The user can configure the secondary server and then click the button of **Save&Apply**.//
435	435
436	436
	443	+
437	437	== **2.10  Connect Full Hotspot to Helium** ==
438	438
439	439
...	...	@@ -478,7 +478,13 @@
478	478	end-node traffic.
479	479
480	480
	488	+=== **3.1.4 Check Raw Payload for End Node** ===
481	481
	490	+Users can check what the end node has uplinked by checking the raw payload. as below:
	491	+
	492	+[[image:image-20220912161818-1.png]]
	493	+
	494	+
482	482	== **3.2  How to use decoder** ==
483	483
484	484	=== **3.2.1  Step 1: Users can create decoders on functions** ===
...	...	@@ -624,9 +624,31 @@
624	624
625	625	== **3.5  Trouble Shooting** ==
626	626
627		-=== **3.5.1  Trouble to Join Helium** ===
628	628
	641	+=== **3.5.1 Data-Only Hotspot is not connecting to Helium console** ===
629	629
	643	+
	644	+//**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
	645	+
	646	+
	647	+1). The hotspot does not finish the onboarding to the helium blockchain.
	648	+
	649	+ 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.
	650	+
	651	+
	652	+=== **3.5.2 End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ** ===
	653	+
	654	+
	655	+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.
	656	+
	657	+
	658	+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]]
	659	+
	660	+
	661	+
	662	+=== **3.5.3  Trouble to Join Helium** ===
	663	+
	664	+
630	630	(((
631	631	**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
632	632
...	...	@@ -644,11 +644,10 @@
644	644	(((
645	645	//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)//
646	646
647		-
648	648
649	649	)))
650	650
651		-=== **3.5.2  Packet Loss for AU915 / US915 Band** ===
	685	+=== **3.5.4  Packet Loss for AU915 / US915 Band** ===
652	652
653	653
654	654	(((
...	...	@@ -706,4 +706,12 @@
706	706
707	707	(((
708	708	//The latest firmware for end node will have this bug fixed.//
	743	+
	744	+
	745	+=== **3.5.5  ADR doesn't work in EU868 band.** ===
	746	+
	747	+See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]]
	748	+
	749	+
	750	+
709	709	)))

image-20220912161818-1.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+53.7 KB

Content