What's up with the arfr

Hi Dan,

Sorry for the confusion -- this is normal behavior for the test version -- it will disconnect from the console every 10 minutes, requiring you to exit and start it up again, and then after 5 days, the option to connect will be disabled.

From the application description on the Android Market:

Download the free tryout version of this application and verify that it runs on your specific Android device. In tryout mode, the software will disconnect every 10 minutes, and after 5 days, the option to connect will be disabled. You will then have to buy the full version. To be able to buy the update, you need to run Android 2.2 or later due to current limitations in the Google purchasing service.

More information on aRFR is also found on the wiki here: http://community.etcconnect.com/wikis/products/arfr-product-page.aspx

Thanks!

Hans,

A few questions on the aRFR:

1) When is the final version going to be released?

2) After following the steps to setup my aRFR, I am still unable to connect to my console on either my tablet (Toshiba Thrive) or phone (Motorola Atrix). I have the console running through an ethernet switch and to my wireless router. I have both my devices set to the network the console is on, and have double checked physical connections as well as IP addresses. Are there any other setting specific to my Congo (other then enabling remote in system settings and enabling DHCP) that I should look for?

Thanks!

hi jeremy.

i'm not on a congo, so i can't help you with question no. 2, but for question 1: the final version has been released about a week ago. that's what's available from the android market.

greetings from switzerland, ueli

Howdy Jaeiden, what version of Congo are you running? what are the IP Addresses and Subnet Masks of: 1.)Congo, 2.) 2nd Congo (if applicable) , 3.)router, 4.)wireless access point (if different from router), 5.)android device. are these all static devices,? with congo in the aRFR app the passwd entry is left blank. what other devices are in your network? what network protocols are being used?

Are u still running Beta Software? After a certain amount of time, the beta stops working. please go online to Android Marketplace and get the released app. has the aRFR app ever worked for u?

Corey,

Thanks for getting back to me. We are currently running the beta version of 6.1 on the Congo. As for the Android app, I just downloaded it on Saturday, so I am assuming this is the official release.

I am using a Toshiba Thrive Tablet running Android 3.1.31.5.011. I do not have any way of changing the IP settings on this device.

The router/wireless point is a Linksys with an IP of 192.168.1.1 and an Subnet mask of 255.255.255.0

The Congo is running version Congo 6.1.1.1.0.59 Beta. Its IP is set to automatic and DHCP is enabled and is 169.254.64.148. When I first tried it I had the IP setting fixed to 10.101.81.101 and DHCP was not enabled. I set the aRFR to this setting as well. Its Subnet mask is set to 255.255.0

Thanks again

 

 

Jeremy,

I don't know Congo but I have set up the aRFR with EOS.  It looks like your Congo is set up to serve DHCP addresses to other devices and is also set up to get its own address via DCHP.  It shouldn't be set up to do both. The 169.254.64.148 address is a link-local address that the console chooses when it is not served an address by another device.

My suggestion is to set the Congo back to the static IP 10.101.81.101.  Turn off DHCP on the Congo unless you need it to serve addresses for other ETC products on your lighting network (nodes, gateways, etc.)

Is the network cable from the Congo (or your lighting network) going into the router's WAN port or LAN port?  It should be in to the WAN port.  Set your router's WAN IP address to a compatible 10.xxx.xxx.xxx address (like 10.101.124.101) with a subnet mask of 255.255.0.0.

On the router, set the LAN side to 192.168.1.1, subnet 255.255.255.0, DCHP on, and give it an address range of 192.168.1.101-150.

Now the tablet should get its address (in the 192.168.1.101-150 range) from the router, the router will route the connection to the 10.xxx.xxx.xxx address space that the Congo can communicate with, and all should work.

If you have questions about the appropriate IP addresses for ETC products, see the Wiki page at

http://community.etcconnect.com/wikis/products/knowledgebase-etc-network-ip-addresses.aspx

Hope this helps-

-Todd

 

 

 

Jeremy,

I don't know Congo but I have set up the aRFR with EOS.  It looks like your Congo is set up to serve DHCP addresses to other devices and is also set up to get its own address via DCHP.  It shouldn't be set up to do both. The 169.254.64.148 address is a link-local address that the console chooses when it is not served an address by another device.

My suggestion is to set the Congo back to the static IP 10.101.81.101.  Turn off DHCP on the Congo unless you need it to serve addresses for other ETC products on your lighting network (nodes, gateways, etc.)

Is the network cable from the Congo (or your lighting network) going into the router's WAN port or LAN port?  It should be in to the WAN port.  Set your router's WAN IP address to a compatible 10.xxx.xxx.xxx address (like 10.101.124.101) with a subnet mask of 255.255.0.0.

On the router, set the LAN side to 192.168.1.1, subnet 255.255.255.0, DCHP on, and give it an address range of 192.168.1.101-150.

Now the tablet should get its address (in the 192.168.1.101-150 range) from the router, the router will route the connection to the 10.xxx.xxx.xxx address space that the Congo can communicate with, and all should work.

If you have questions about the appropriate IP addresses for ETC products, see the Wiki page at

http://community.etcconnect.com/wikis/products/knowledgebase-etc-network-ip-addresses.aspx

Hope this helps-

-Todd