• State Not Answered
  • Date
    Mickwd
  • Date
  • Replies 3 replies
  • Subscribers 185 subscribers
  • Views 9702 views
  • Users 0 members are here

Problems setting up remote Network with Ion console and problems with aRFR app

Hi,

I'm trying to set up the aRFR network on a new Ion console and I'm having isues with the settings and the aRFR app. It's a straightforward set up with a single Ion console, TP-Link TL-WR842ND wireless router at default factory settings wired from Wan port into ethernet connector on console  and Samsung Galaxy Tab 10 with aRFR app as remote device.

Firstly I've tried some of the recommendations and followed the procedures for setting up the aRFR network for the console that have been previously posted by ETC techs, on this forum and on Controlbooth forum, but  I'm still not having any success.

While there are links on the ETC site for "How to set up your Wireless Network" and "Getting started with your Eos family Console", they don't go into any detail on how to configure the Network settings in the shell area of the console. Why not a full step by step guide with images on the site or even in the Ion manual?

Secondly since I purchased  the aRFR app on my remote device a Samsung Galaxy Tab 10 ,the connect button on the aRFR app is still disabled. I can connect the Tab to the router normally in wifi but when I try in the app I just get offline. On site aRFR links it recommends pressing the refresh button and the connect button but as I said it's disabled even though I've purchased the full app. Any suggestions?

Regards,

Mick

  • 0

    First off, connect the ION to the wired/lan port on the router. The wan port is used to connect to the internet.   The next thing to do is setup addressing on the ION and on the router.   Do you have an RPU or RVI or any nodes?( If you are using the ethernet port for other etc devices then the setup gets a little more complicated.)

    I would use the settings below.

    ION

    IP:  10.101.100.102

    Subnet: 255.255.0.0

    Gateway: 10.101.1.1

     

    Setup the router like this.

    Change the default router ip to :  10.101.100.101

    Change the subnet to  255.255.0.0

    Gateway to  10.101.1.1

    Depending on how many arfr / irfr devices you want to use you could opt to use the DHCP server built into the router.

     

     

     

     

  • 0

    The "Connect" button is disabled if it cannot see the console.
    (The text above the Connect button says whether it's been purchased or not.)

    That means there's no "route" to the console, or that WiFi remotes have been disabled in the Shell.

    There are many different ways to get these working, the right method for your installation may cause problems if somebody else tried.

    Assuming the only things on your network are the Ion, the WiFi router and the tablet running aRFR, then the easiest is to connect the Ion to the WAN port of the router.

    This way you can use the factory defaults for all devices and turn on the DHCP Address Service on the Ion. (Network Services section)
    You may need to reset or power-on the WiFi router after the Ion is running. (Some routers want this, some don't)

    • The Ion factory default IP is 10.101.100.101, subnet 255.255.0.0, Gateway 10.101.100.101
    • DHCP Address Service defaults are First Address 10.101.100.102, subnet 255.255.0.0, Routed Network enabled, Gateway 10.101.1.1

    Remember to turn on "WiFi Remotes" in the Shell (Settings > RFR) and enable remotes in your show settings or it will not connect.

    This Wiki page gives step-by-step instructions.

    What versions of Ion and the aRFR are you running, and what are the IP addresses of the Ion, the WiFi router and your tablet?
    Is there anything else on the network?

  • 0 in reply to Richard

    Hi ,

    Thanks all for the replies. I think it's the conflicting views on whether to hook up into the WAN port or the Lan port that just adds to this set up being confusing too. And as has been said before there are many different ways. I reckoned it would be WAN as it's the console that is essentially the Network, well in my strighforward set up of console router and remote device. Anyway followed your recommendations Richard and it worked!!!  Wonder if the fact we updated the software to version 2 helped.



    [edited by: Mickwd at 3:51 PM (GMT -6) on Thu, Mar 28 2013]
Related

www.etcconnect.com