Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -485,13 +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		-[[image:image-20220912161818-1.png]]
493		-
494		-
495	495	== **3.2  How to use decoder** ==
496	496
497	497	=== **3.2.1  Step 1: Users can create decoders on functions** ===
...	...	@@ -638,30 +638,29 @@
638	638	== **3.5  Trouble Shooting** ==
639	639
640	640
641		-=== **3.5.1 Data-Only Hotspot is not connecting to Helium console** ===
	635	+=== 3.5.1 Trouble connecting Helium Console ===
642	642
643	643
644		-//**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:**//
645	645
646	646
647		-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.
648	648
649	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	650
651	651
652		-=== **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~://**
653	653
654	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.
	649	+1). Your device is not using the region configuration, where you have to use the frequency plan that is compatible with your region.
656	656
	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]]
657	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	659
660	660
	655	+=== **3.5.2  Trouble to Join Helium** ===
661	661
662		-=== **3.5.3  Trouble to Join Helium** ===
663	663
664		-
665	665	(((
666	666	**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
667	667
...	...	@@ -682,7 +682,7 @@
682	682
683	683	)))
684	684
685		-=== **3.5.4  Packet Loss for AU915 / US915 Band** ===
	678	+=== **3.5.3  Packet Loss for AU915 / US915 Band** ===
686	686
687	687
688	688	(((
...	...	@@ -740,12 +740,4 @@
740	740
741	741	(((
742	742	//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		-
751	751	)))

image-20220912161818-1.png

Author

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

Size

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

Content