DeviceToggler.txt at yahoo!

Support forum for extenders. If you're having trouble getting one up and running, this is the place to come.

Moderator: Moderators

DavidEC2955
Posts: 143
Joined: Fri Sep 26, 2003 3:57 pm
Location: Kansas

_T_H_A_N_K_S_!!!!

Post by DavidEC2955 »

mtakahar wrote:
DavidEC2955 wrote:How did you come up with that figure? Where did I make my mistake??
In 15-2133, VCR/0618 = $22 $6A, TV/2004 = $17 $D4. $226A xor $17D4 = $35BE.
Get the special protocols spreadsheet in the files section in this forum. It'll calculate the value for you.

Hal
The special spreadsheet was what I was needing!!!

Now if only it would be updated to for other remotes such as the HTPro and Kameleon 6- URC6960

Not everybody needs all the fancy things that an extender can do and like in my case only wish to 'carry' the codes for other devices w/o the need for second remote.

--David
Last edited by DavidEC2955 on Mon Oct 03, 2005 6:11 pm, edited 1 time in total.
DavidEC2955
Posts: 143
Joined: Fri Sep 26, 2003 3:57 pm
Location: Kansas

Post by DavidEC2955 »

Mark Pierson wrote:
DavidEC2955 wrote:
mtakahar wrote:$226A xor $17D4 = $35BE
The instruction with the files say to use the 'XOR' command in the windows built-in calcalator....
I just tried this myself and Windows Calculator gives $35BE as the result. Perhaps your hex setup codes ($226A, $17D4) were wrong?


Who knows for sure now I was so 'brain wrecked' that I could of been entering the wrong hex codes...

Thanks!

--David
mtakahar
Expert
Posts: 281
Joined: Sun Aug 03, 2003 2:46 pm

Post by mtakahar »

DavidEC2955 wrote:Now if only it would be updated to for other remotes such as the HTPro and Kameleon 6- URC6960
I don't know much about 6960, though, the settings for URC-8910 should work on HTPro.
DavidEC2955 wrote:
Mark Pierson wrote:
DavidEC2955 wrote: The instruction with the files say to use the 'XOR' command in the windows built-in calcalator....
I just tried this myself and Windows Calculator gives $35BE as the result. Perhaps your hex setup codes ($226A, $17D4) were wrong?


Who knows for sure now I was so 'brain wrecked' that I could of been entering the wrong hex codes...
It's just that the device modes can translate to different hex values in different remote. You just grabbed the ones for an arbitrary remote in an old toggler .txt file posted on the Yahoo! site. That's not your brain that was wrong.

Hal
Post Reply