EOS + RFR = :-(

As of right now, plugging and RFR directly into the console (without using the basestation) does not work.

This will be fixed in 1.4.2 when we add networking capability to the RFR.

Plugging the remote in through USB can only be used to charge the device.

-D

Yes, when I took those photos it was plugged into the console, but I only plugged it in there after I was having similar problems over wireless.  I have seen all of those same screens when using the RFR over the wireless connection.

 This is actually the second RFR we have recieved and both have had this (the first went back because it would shut off randomly)

I've been meaning to contact tech support about a very similar problem for a little while now!

I think I've isolated my problem to either battery charger inside the unit:  once I simply swapped out the rechargeables for a pair of Duracell Procells, my problems, which had been occuring whether I plugged the unit directly into the console or used the wall charger, appeared to cease...

Maybe yes?

I've had to replace both RFR.  In 1, 2 buttons stopped backlighting, and the other appeared to have a loose batter connection (it wouldn't wake up after going to "sleep" mode.  And now the USB charging cable has glitched.  Flex the cable and the unit charges.  Flex it again and the power doesn't get to the RFR.  (ETC: I've contacted my local rep on this). 

I've had more issues than I wanted with the Ion and remotes, but the ETC crew has fixed them, and (tried to) keep me happy.  GREAT customer service, unlike the manufacturer of my previous consoles.

doc_blume:

As of right now, plugging and RFR directly into the console (without using the basestation) does not work.

This will be fixed in 1.4.2 when we add networking capability to the RFR.

Plugging the remote in through USB can only be used to charge the device.

-D

Yeah! No more dragging the base around every time I have to move the console. It seems silly, but one less trip between the booth and the tech table is nice!

I had that same problem just last week. I turned it off and on, after the third time it come on without problems. I chalked it up to the fact that neither the console nor the RFR had been used in a couple of months.

What software version are you running?

I have the remote on stage and the basestation plugged into the console, i have had the screens you showed but usually i would just switch the remote off then back on and would get a better signal.

We are also on version 1.4.2?

When you get the problem occuring have you got a red light on the basestation appearing instead of the usual green?

I get insanely garbled screens sometimes when turning it on - usually when the battery is low, but sometimes even after charging overnight, it takes between 4 and 10 powercycles to get the RFR to come back to life.  There are some definite graphical errors - sometimes the battery continues to 'charge' for hours after unplugging it from the USB cable.  I think a good rule of thumb is don't let the battery run all the way down.  It makes it very unhappy.

 When the software for the RFR is updated, how will we update it?  Plug it into the console directly?  Any idea on when the RFR will be updated?  I'd give my left eye for Address access in Live.  No one seems to understand how often we bring up Addresses and not just Channels. 

doc_blume:

As of right now, plugging and RFR directly into the console (without using the basestation) does not work.

This will be fixed in 1.4.2 when we add networking capability to the RFR.

I am curious if this did make it in 1.4.2. I dont remember seeing it in the release notes (that doesnt mean its not there though!). 

Brian, networked RFR didn't make it into 1.4.2.... still needed a bit of work.  It's pretty close, though, so we are planning a release (1.4.3) largely to support it.  

Thanks for checking.

a