Summary

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

Details

Page properties

Author

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

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
...	...	@@ -55,6 +55,7 @@
55	55
56	56	//Click Download Helium Server and the gateway will download the Helium-gateway-rs//
57	57
	59	+
58	58	[[image:image-20220615150600-1.png||height="559" width="1045"]]
59	59
60	60
...	...	@@ -398,7 +398,19 @@
398	398	[[image:image-20220531175919-9.png]]
399	399
400	400
	403	+=== **2.8.5  How to manually download helium gateway-rs via SSH access to the gateway Linux console** ===
401	401
	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	+
402	402	== **2.9  Forward the data to the other server** ==
403	403
404	404	=== **2.9.1  Introduction** ===
...	...	@@ -486,6 +486,15 @@
486	486
487	487
488	488
	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	+
489	489	== **3.2  How to use decoder** ==
490	490
491	491	=== **3.2.1  Step 1: Users can create decoders on functions** ===
...	...	@@ -632,29 +632,31 @@
632	632	== **3.5  Trouble Shooting** ==
633	633
634	634
635		-=== 3.5.1 Trouble connecting Helium Console ===
	658	+=== **3.5.1 Data-Only Hotspot is not connecting to Helium console** ===
636	636
637	637
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:**//
	661	+//**The Data-only hotspot 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 device does not finish the onboarding to the helium blockchain.
	664	+1). The hotspot does not finish the onboarding to the helium blockchain.
642	642
643		- after the 23 version of the gateway-rs, Helium requests the user to onboarding the devices to the blockchain, otherwise, your devices are not connecting 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.
	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.
644	644
645	645
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
	670	+=== **3.5.2 End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ** ===
648	648
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]]
	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.
652	652
653	653
	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]]
654	654
655		-=== **3.5.2  Trouble to Join Helium** ===
656	656
657	657
	680	+=== **3.5.3  Trouble to Join Helium** ===
	681	+
	682	+
658	658	(((
659	659	**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
660	660
...	...	@@ -672,10 +672,11 @@
672	672	(((
673	673	//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)//
674	674
	700	+
675	675
676	676	)))
677	677
678		-=== **3.5.3  Packet Loss for AU915 / US915 Band** ===
	704	+=== **3.5.4  Packet Loss for AU915 / US915 Band** ===
679	679
680	680
681	681	(((
...	...	@@ -733,4 +733,14 @@
733	733
734	734	(((
735	735	//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	+
736	736	)))

image-20220912161818-1.png

Author

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

Size

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

Content

image-20230320141404-1.png

Author

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

Size

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

Content