Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Edwin
	1	+XWiki.Xiaoye

Content

...	...	@@ -41,6 +41,7 @@
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	+
44	44	== **2.2  Step 1: Configure Frequency Band** ==
45	45
46	46
...	...	@@ -485,12 +485,7 @@
485	485	end-node traffic.
486	486
487	487
488		-=== **3.1.4 Check Raw Payload for End Node** ===
489	489
490		-Users can check what the end node has uplinked by checking the raw payload. as below:
491		-
492		-
493		-
494	494	== **3.2  How to use decoder** ==
495	495
496	496	=== **3.2.1  Step 1: Users can create decoders on functions** ===
...	...	@@ -636,31 +636,9 @@
636	636
637	637	== **3.5  Trouble Shooting** ==
638	638
	635	+=== **3.5.1  Trouble to Join Helium** ===
639	639
640		-=== **3.5.1 Data-Only Hotspot is not connecting to Helium console** ===
641	641
642		-
643		-//**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
644		-
645		-
646		-1). The hotspot does not finish the onboarding to the helium blockchain.
647		-
648		- 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.
649		-
650		-
651		-=== **3.5.2 End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ** ===
652		-
653		-
654		-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.
655		-
656		-
657		-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]]
658		-
659		-
660		-
661		-=== **3.5.3  Trouble to Join Helium** ===
662		-
663		-
664	664	(((
665	665	**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
666	666
...	...	@@ -678,10 +678,17 @@
678	678	(((
679	679	//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)//
680	680
	655	+4) Your gateway is not onboarding to the helium explore, after 23 versions, the data-only hotspot(Gateway) is requested onboarding to helium explore. ~-~-> Please refer to [[Step 2.7>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Helium/#H2.7A0Step6:OnboardingData-OnlyHotspot]] to do it.
	656	+
	657	+5). You have to use the frequency plan that is compatible with your region.
	658	+
	659	+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]]
	660	+
	661	+
681	681
682	682	)))
683	683
684		-=== **3.5.4  Packet Loss for AU915 / US915 Band** ===
	665	+=== **3.5.2  Packet Loss for AU915 / US915 Band** ===
685	685
686	686
687	687	(((
...	...	@@ -739,12 +739,4 @@
739	739
740	740	(((
741	741	//The latest firmware for end node will have this bug fixed.//
742		-
743		-
744		-=== **3.5.5  ADR doesn't work in EU868 band.** ===
745		-
746		-See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]]
747		-
748		-
749		-
750	750	)))