Page 1 of 1

Selecting VCR or TV toggles power - how to stop this? RCU810

Posted: Sat Oct 11, 2003 4:49 pm
by ryanosman
factory internal setup codes, no keymoves or anything like that... take remote new out of box, set up TV and VCR and AMP, watch a movie, switch to AMP to adjust surround settings, push VCR1 button to go back to movie, and VCR shuts off. Why? I have tried moving keys onto the device key & it doesn't work. (can move a key onto other buttons, but not device button.

Posted: Sat Oct 11, 2003 5:35 pm
by jamesgammel
You can't keymove to a device key. The 810 has a "cool" feature, there's a "hidden" key tied to the device keys with the power codes. That works ok if the power function is a discrete on, but as you found out, if it's a toggle code, it just keep cycling on/off with every device key press. You can program "power" (hopefully a discrete "on") to that "device key" (I think that's what the named it, if not, something close) in KM if you make an upgrade code. You might be able to use IR and keymove a "nothing" efc to it if you don't have discrete on and off commands for a device. Hopefully someone who knows more about the 810 can give you a solution, I'm sure your not the only one who's experienced this dilemna.

Jim

Posted: Sat Oct 11, 2003 5:39 pm
by The Robman
This implies that they programmed the POWER function to the device button for the VCR code that you are using. The only way to fix it is to create a new upgrade for the VCR that doesn't include a function on the device button.

If you mention what setup code you are using, I'm sure someone can create a KM file for you that replicates what the built in code looks like, which you can use as a starting point.

When you post the setup code, be sure to mention if you are quoting the code as it appears in the RCA manual, as these codes are all offset by 17 (eg, the VCR/0060 code would appear in the RCA manual as VCR/0077).

Everyone here knows the codes by their regular numbers, not the RCA numbers.

Posted: Sat Oct 11, 2003 8:59 pm
by Lenroc
The Robman wrote: When you post the setup code, be sure to mention if you are quoting the code as it appears in the RCA manual, as these codes are all offset by 17 (eg, the VCR/0060 code would appear in the RCA manual as VCR/0087).
Just for completeness, do you mean that the codes are offset by 27, that VCR/0060 would actually be VCR/0077, or that there's some other trick that I'm just missing?

Posted: Sat Oct 11, 2003 9:42 pm
by The Robman
Lenroc wrote:Just for completeness, do you mean that the codes are offset by 27, that VCR/0060 would actually be VCR/0077, or that there's some other trick that I'm just missing?
Nah, my bad for typing too quick, the 17 is correct, it was the 0087 that was wrong. The RCA version of VCR/0060 would be VCR/0077

Posted: Sun Oct 12, 2003 10:21 am
by ryanosman
Thanks again for all your help guys.

For anyone else who runs into this problem, I think the solution is to realize that creating an entire ungrade in KM (set of EFCs for your VCR or whatever [probably already in your remote anyways so it won't take a lot of memory in your remote] mapped to your choice of buttons on your particular remote, and downloaded into the remote) is not really that big of a chore. I did that. Honestly, I was planning on doing that anyways, but wanted the remote up & 90% functional quickly to impress the wife - before long I realized that that was evolving into a mistake. Doing the upgrades the long (proper/thorough) way only took a couple hours. Now every button on the remote does what I want it to do, and as I think of improvements (or the wife complains :wink: ), implementing them is as easy as dragging stuff around the KM spreadsheet.

Posted: Sun Oct 12, 2003 12:07 pm
by Mark Pierson
ryanosman wrote:creating an entire ungrade in KM (set of EFCs for your VCR or whatever [probably already in your remote anyways so it won't take a lot of memory in your remote]
Remember that the built-in setup codes are burned into the firmware of the remote. Whether you use them or not doesn't have any effect on the available EEPROM memory that JP1 uses. Device upgrades ARE stored in the EEPROM and therefore do use several bytes of memory. The advantage to upgrades is that they can be customized, and most times cut down on the number of key moves required (which also consume EEPROM memory at 5 or 6 bytes each) to get a particular device functioning to ones liking.
implementing them is as easy as dragging stuff around the KM spreadsheet.
Just a word of caution. KM (actually Excel) doesn't support drag & drop. Even the normal copy & paste can wreak havoc with KM (again, an Excel "limitation"). The best way to move data around in KM is to copy it, and then use Paste Special..., Values to get the data where you want it.