Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -56,7 +56,6 @@
56	56
57	57	//Click Download Helium Server and the gateway will download the Helium-gateway-rs//
58	58
59		-
60	60	[[image:image-20220615150600-1.png||height="559" width="1045"]]
61	61
62	62
...	...	@@ -400,19 +400,7 @@
400	400	[[image:image-20220531175919-9.png]]
401	401
402	402
403		-=== **2.8.5  How to manually download helium gateway-rs via SSH access to the gateway Linux console** ===
404	404
405		-
406		-(% class="box infomessage" %)
407		-(((
408		-cd /tmp;wget -O helium-gateway-rs-dragino.ipk [[https:~~/~~/github.com/helium/gateway-rs/releases/download/v1.0.0-alpha.33/helium-gateway-v1.0.0-alpha.33-dragino.ipk>>https://github.com/helium/gateway-rs/releases/download/v1.0.0-alpha.33/helium-gateway-v1.0.0-alpha.33-dragino.ipk]]
409		-
410		-opkg install helium-gateway-rs-dragino.ipk
411		-)))
412		-
413		-[[image:image-20230320141404-1.png]]
414		-
415		-
416	416	== **2.9  Forward the data to the other server** ==
417	417
418	418	=== **2.9.1  Introduction** ===
...	...	@@ -500,15 +500,6 @@
500	500
501	501
502	502
503		-=== **3.1.4 Check Raw Payload for End Node** ===
504		-
505		-
506		-Users can check what the end node has uplinked by checking the raw payload. as below:
507		-
508		-[[image:image-20220912161818-1.png]]
509		-
510		-
511		-
512	512	== **3.2  How to use decoder** ==
513	513
514	514	=== **3.2.1  Step 1: Users can create decoders on functions** ===
...	...	@@ -654,32 +654,9 @@
654	654
655	655	== **3.5  Trouble Shooting** ==
656	656
	635	+=== **3.5.1  Trouble to Join Helium** ===
657	657
658		-=== **3.5.1 Data-Only Hotspot is not connecting to Helium console** ===
659	659
660		-
661		-//**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
662		-
663		-
664		-1). The hotspot does not finish the onboarding to the helium blockchain.
665		-
666		- 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.
667		-
668		-
669		-
670		-=== **3.5.2 End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ** ===
671		-
672		-
673		-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.
674		-
675		-
676		-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]]
677		-
678		-
679		-
680		-=== **3.5.3  Trouble to Join Helium** ===
681		-
682		-
683	683	(((
684	684	**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
685	685
...	...	@@ -697,11 +697,17 @@
697	697	(((
698	698	//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)//
699	699
	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.
700	700
	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	+
701	701
702	702	)))
703	703
704		-=== **3.5.4  Packet Loss for AU915 / US915 Band** ===
	665	+=== **3.5.2  Packet Loss for AU915 / US915 Band** ===
705	705
706	706
707	707	(((
...	...	@@ -759,14 +759,4 @@
759	759
760	760	(((
761	761	//The latest firmware for end node will have this bug fixed.//
762		-
763		-
764		-
765		-=== **3.5.5  ADR doesn't work in EU868 band.** ===
766		-
767		-
768		-See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]]
769		-
770		-
771		-
772	772	)))

image-20220912161818-1.png

Author

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

Size

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

Content

image-20230320141404-1.png

Author

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

Size

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

Content