Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -632,30 +632,29 @@
632	632	== **3.5  Trouble Shooting** ==
633	633
634	634
635		-=== **3.5.1 Data-Only Hotspot is not connecting to Helium console** ===
	635	+=== 3.5.1 Trouble connecting Helium Console ===
636	636
637	637
638		-//**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
	638	+//**The LPS8/LPS8N/DLOS8/DLOS8N/LG308/LG308N/LIG16/LPS8V2 has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
639	639
640	640
641		-1). The hotspot does not finish the onboarding to the helium blockchain.
	641	+1). The device does not finish the onboarding to the helium blockchain.
642	642
643	643	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.
644	644
645	645
646		-=== **3.5.2 End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ** ===
	646	+**//The sensor node is not joining the helium network, the helium console shows it is stuck in the cycle of joining-accept. The possibility is~://**
647	647
648	648
649		-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.
	649	+1). Your device is not using the region configuration, where you have to use the frequency plan that is compatible with your region.
650	650
	651	+ 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]]
651	651
652		-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]]
653	653
654	654
	655	+=== **3.5.2  Trouble to Join Helium** ===
655	655
656		-=== **3.5.3  Trouble to Join Helium** ===
657	657
658		-
659	659	(((
660	660	**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
661	661
...	...	@@ -676,7 +676,7 @@
676	676
677	677	)))
678	678
679		-=== **3.5.4  Packet Loss for AU915 / US915 Band** ===
	678	+=== **3.5.3  Packet Loss for AU915 / US915 Band** ===
680	680
681	681
682	682	(((
...	...	@@ -734,12 +734,4 @@
734	734
735	735	(((
736	736	//The latest firmware for end node will have this bug fixed.//
737		-
738		-
739		-=== **3.5.5  ADR doesn't work in EU868 band.** ===
740		-
741		-See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]]
742		-
743		-
744		-
745	745	)))