Summary

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

Details

Page properties

Content

...	...	@@ -58,6 +58,7 @@
58	58
59	59	//Click Download Helium Server and the gateway will download the Helium-gateway-rs//
60	60
	61	+
61	61	[[image:image-20220615150600-1.png||height="559" width="1045"]]
62	62
63	63
...	...	@@ -489,6 +489,15 @@
489	489
490	490
491	491
	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	+
492	492	== **3.2  How to use decoder** ==
493	493
494	494	=== **3.2.1  Step 1: Users can create decoders on functions** ===
...	...	@@ -634,9 +634,32 @@
634	634
635	635	== **3.5  Trouble Shooting** ==
636	636
637		-=== **3.5.1  Trouble to Join Helium** ===
638	638
	648	+=== **3.5.1 Data-Only Hotspot is not connecting to Helium console** ===
639	639
	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	+
640	640	(((
641	641	**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
642	642
...	...	@@ -658,7 +658,7 @@
658	658
659	659	)))
660	660
661		-=== **3.5.2  Packet Loss for AU915 / US915 Band** ===
	694	+=== **3.5.4  Packet Loss for AU915 / US915 Band** ===
662	662
663	663
664	664	(((
...	...	@@ -716,4 +716,14 @@
716	716
717	717	(((
718	718	//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	+
719	719	)))

image-20220912161818-1.png

Author

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

Size

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

Content