Summary

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

Details

Page properties

Content

...	...	@@ -58,7 +58,6 @@
58	58
59	59	//Click Download Helium Server and the gateway will download the Helium-gateway-rs//
60	60
61		-
62	62	[[image:image-20220615150600-1.png||height="559" width="1045"]]
63	63
64	64
...	...	@@ -490,15 +490,6 @@
490	490
491	491
492	492
493		-=== **3.1.4 Check Raw Payload for End Node** ===
494		-
495		-
496		-Users can check what the end node has uplinked by checking the raw payload. as below:
497		-
498		-[[image:image-20220912161818-1.png]]
499		-
500		-
501		-
502	502	== **3.2  How to use decoder** ==
503	503
504	504	=== **3.2.1  Step 1: Users can create decoders on functions** ===
...	...	@@ -644,32 +644,9 @@
644	644
645	645	== **3.5  Trouble Shooting** ==
646	646
	637	+=== **3.5.1  Trouble to Join Helium** ===
647	647
648		-=== **3.5.1 Data-Only Hotspot is not connecting to Helium console** ===
649	649
650		-
651		-//**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
652		-
653		-
654		-1). The hotspot does not finish the onboarding to the helium blockchain.
655		-
656		- 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.
657		-
658		-
659		-
660		-=== **3.5.2 End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ** ===
661		-
662		-
663		-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.
664		-
665		-
666		-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]]
667		-
668		-
669		-
670		-=== **3.5.3  Trouble to Join Helium** ===
671		-
672		-
673	673	(((
674	674	**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
675	675
...	...	@@ -691,7 +691,7 @@
691	691
692	692	)))
693	693
694		-=== **3.5.4  Packet Loss for AU915 / US915 Band** ===
	661	+=== **3.5.2  Packet Loss for AU915 / US915 Band** ===
695	695
696	696
697	697	(((
...	...	@@ -749,14 +749,4 @@
749	749
750	750	(((
751	751	//The latest firmware for end node will have this bug fixed.//
752		-
753		-
754		-
755		-=== **3.5.5  ADR doesn't work in EU868 band.** ===
756		-
757		-
758		-See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]]
759		-
760		-
761		-
762	762	)))

image-20220912161818-1.png

Author

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

Size

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

Content