JP1 Remotes

Sure, I'm glad it worked!

ok..., I now remember this:

In addition to the eeprom size in the RDF, you also have to change the shift key patch address and the device button addresses.

You can get those values for your version of extender by looking at the values of Shift_Key_patch and DevSetup_patch in the listing file ...

The 1K extender will work with 2K, but it can't use the extra memory.

I'll have to check the code and try to remember which vars need to be changed because it's been a long time since I wrote it.

I'll try to post it in a few days.

Everything in the range $40 and above will have conflicting counter part if it's shifted. Here, $C0 (Shift-Phantom4) can be considered as either $80 + $40 (Shift-Phantom4) or $C0 + $00 (XShift-Key0). There's no right or wrong in interpreting it in the rest of other cases, though, in this particular ...

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.

$226A xor $17D4 = $35BE
The instruction with the files say to use the 'XOR' command in the windows built-in ...

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

But when I try to add a second toggle such as:

SAT/CBL SHIFT-2 <N/A> VCR 1102 $05 $BE 74363

This should shift between my DirectTivo[set up code:0618/$5A$6A] and my U.S.Digital HDTV Receiver [set up code: 2004/$5F $D4]

I can toggle out of the MAIN device but the second device does not work ...

After making the modifications to .asm file and assembling it, take the values of ee_main, Shift_Key_patch DevSetup_patch from .lst file generated from .asm, then modify the .rdf with those valus. Replace $(ee_main-1), etc. with manually calculated hexadecimal values.

XXX is the boundary of the ...

The failure rate is still a bit too high on a single processor system,

After tweaking your code and getting some disappointing results, I did some basic timing tests.

A single call to the porttalk routine inportb takes over 5 microseconds on my very fast computer. That makes the raw sampling ...

andyross wrote:On the 6012 v3.3 (actually being used on an 8811), is it possible to eliminate the backlight blinking off while pressing a key?

I think v2 keeps the backlight on while pressing a button.

Hal

1) I first tried editing the Makefile to replace the two occurances of javac with ${JDKPATH}/bin/javac
That seems to work. Since the Makefile needs to be given JDKPATH anyway, isn't it more robust to depend just on JDKPATH and not PATH for that?
Good point. I'll do that, too.

Or is there ...

mr_d_p_gumby wrote:I know that some of them don't work as intended even when used within their extender (i.e., they provide very short delay times because the LED blink routine is still disabled).

I believe this problem is specific to the extenders for LCD remotes that do not have the LED blinking routine.

Hal

I've done more testing related to the point John raised regarding minimum operating voltage for the IR probe. Apparently John was exactly right in his concern that we were operating below the manufacturer's spec. I finally found a combination laptop and probe that confirms that. The failure mode is ...

1) Have TV power turn on/off both the TV and the Receiver

This calls for the macro feature that doesn't exist in the remote.

You don't need the extender if you only need to turn on/off only EITHER one.

Hal

According to what I've read here and in the old Yahoo! group, at least the Sony one seems to be similar to Sony 15 with just higher carrier frequency. (An upgrade:
http://groups.yahoo.com/group/jp1/files/3.%20Device%20Codes/Audio/Sony_STRDA90ESG_Test2_Final.txt)

The 1-shot may not need to be ...