JP1 Remotes

Haven't tried the JVC upgrade as a standalone in the OCAP yet, but with just my Sky upgrade (includes protocol upgrade) OCAP is also scrambling buttons. With a full suite of four upgrades, including the JVC, the OCAP completely locks up. For right now, I'm focusing on the 10251025 and hope that once that is resolved, there will at least be an identified proccess to follow to troubleshoot and solve the OCAP problems.

Your Settings area also seems to be off. EA15 bit5 governs the use of the standard keymap or the alternate keymap. bit5=0 chooses the standard keymap which is listed in the RDF. Your KeyMix.IR file has FF in this byte so change EA15 in the Raw Data Tab to 40 and then click the APPLY button. Upload back into remote and test the '8' button.

You can also edit the RDF and add this to the [Settings] section. You should be using the Standard KeyMap.
KeyMap=$015.5.1.0.0 (Standard;Alternate)

I'll be adding this to the RDF's that I've uploaded.

This remote also has a channel lock(SET-973) which will lock the CH+/-,Digits buttons to the CBL device. On the right side of IR's General Tab is the Other Settings area which is where you can turn on/off this channel lock mechanism.

As for the MultiMacros, if I go into the Macros Tab and create a macro on TuneIn1 of 1;2;3 and then clone it and then click OK. It creates another identical entry. You now have two macros associated with TuneIn1.

OK, first CONTROLLED tests in on 1025, adding a single upgrade at a time:
Edit: The following testing was conducted WITHOUT applying the fix outlined in the immediately preceding post.
(A) Sharp DVD upgrade (DVD/1630) created with RM. (Last 2 bits=10)
(1) RM calls for an unnecessary protocol upgrade (00F8), when I know full well that there are built-in Setup Codes that use 00F8, so I did NOT add the Protocol upgrade, only the device upgrade (Should the rdf be reflected to include the 00F8 executor?)
(2) Upgrade works fine (one exception noted at bottom). No scrambling.
(3) Same upgrade as TV/1630 worked equally properly.

Sharp VCR upgrade (CBL/1017) created with RM. (Last 2 bits 01) Uses Sharp protocol 001C - no Protocol Upgrade called for or required:
(1) Upgrade works fine - no scrambling.
(2) Same upgrade as CD/Audio/1017 worked equally correctly.

No Setup code, neither a built-in nor an upgrade, nor keymove nor macro, operates the Power button in ANY device mode, ever! (Despite functions CLEARLY being mapped to the Power button in both RM and IR's Device upgrade display) The remote won't allow manual creation of the Power Macro as described in the manual, since the Power button never flashes like it's supposed to. Might I have a bum Power button on my (Vicky's) remote?

I acknowledge the fixes binky provides, but don't see their precise relevance:

For the 1025 JP1.2 model, the hidden upgrade area at F200 should be F2 04 F2 04 00 00

So do i have to MANUALLY check this in IR's Raw Data page every time? or is there an rdf fix?

As for

You can also edit the RDF and add this to the [Settings] section. You should be using the Standard KeyMap.
KeyMap=$015.5.1.0.0 (Standard;Alternate)

in the cases I outline immediately above, NO buttons are scrambled, so will this "fix" mess them up now? Or will it simply ensure consistemcy across various upgrades?

Great Job Binky

Capn,

Try a key move to the power key, just to see if it lights up.


You can't test the extender if you don't have a POWER key!

OK,

I have made the addition to the rdf with Keymap entry.

I have NOT made any sort of permanent change to ANYTHING regarding the "F200 should be F2 04 F2 04 00 00" business, but those data have magically changed from all "FFs" and "F2 04 F2 00 00 00" appear to be the data entered there now. I don't know what caused that change , but my upgrades WORK, so I don't care!

Bottom line - all upgrades work, including the JVC Combo one.

HOWEVER:
(1) I have a SharpDVD device upgrade that RM says requires a protocol upgrade for executor 00F8. I omitted the Protocol upgrade and it works fine;
(2) On a whim, despite the JVC Combo upgrade calling for a protocol upgrade for executor 0098, I omitted that Protocol upgrade and it works fine.Edit: OOPS! RM did NOT call for this Protocol upgrade
So the rdf's list of resident protocol executors is wrong for 00F8. Do I just add it to the rdf?

And the POWER button is DEAD, DEAD, DEAD! Neither within a device upgrade, nor via keymove, nor via macro. It NEVER illuminates ANYTHING! I really don't want to open up the remote to look for a problem, but I may have no other option.

Capn Trips wrote: HOWEVER:
(1) I have a SharpDVD device upgrade that RM says requires a protocol upgrade for executor 00F8. I omitted the Protocol upgrade and it works fine;
So the rdf's list of resident protocol executors is wrong for 00F8. Do I just add it to the rdf?

So I looked in the rdf some more and it lists protocol executor 00F8:3, which I thought meant that it is backwards-compatible with PREVIOUS 00F8 versions. However, whe selecting the SharpDVD protocol in RM, for the Atlas 1025 remote, RM requires a Protocol upgrade. Should a SECOND variant of 00F8 be added to the rdf, is RM processing something incorrectly, or is there a problem with protocols.ini?

Now if I could just solve the Sky protocol upgrade (RC6-M-20n) challenge - and fix the Power button - I'd have my starting point for testing the extender.

The problem here with Sharp DVD is that there is no entry for Sharp DVD with VariantName=3, like there is a Fujitsu with VariantName=3.

Unfotunately I don't understand the differences between Sharp DVD and Fujitsu enough to know what needs to change.

It is interesting, though, that the HCS08 protocol code for Fujitsu:3 matches exactly the code for Sharp DVD with no variant. It may just be a matter of creating a duplicate entry of Sharp DVD with variantName=3.

While we're at it, the entry for Sharp DVD:2 doesn't look right.

Just being dense, but you refer to "the entry". Where? In what file and/or document? the rdf? protocols.ini? elsewhere?

And the POWER button is DEAD, DEAD, DEAD! Neither within a device upgrade, nor via keymove, nor via macro. It NEVER illuminates ANYTHING! I really don't want to open up the remote to look for a problem, but I may have no other option.

DRAT! It takes a week for a replacement to get there, and Monday is a postal holiday! I know that there are timing issues with your coming back stateside. PM me where you want me to send the replacement.

You've uncovered a lot of issues, and Binky has come up with lots of solutions and it looks like Greg is working on your protocol issues.

Thanks everyone!

Capn Trips wrote:Just being dense, but you refer to "the entry". Where? In what file and/or document? the rdf? protocols.ini? elsewhere?

protocols.ini

As far as RM is concerned all protocol definitions exist is protocols.ini
In terms of protocols, the RDFs only contain information about which executors are pre-installed in each remote.

Capn Trips wrote:Now if I could just solve the Sky protocol upgrade (RC6-M-20n) challenge - and fix the Power button - I'd have my starting point for testing the extender.

OK, as I report HERE, I've got Sky+ working as well. The only remaining hurdle is my "Power failure"

Here is a work around for the power failure, for the extender.

Change the contents of EA1C from $03 to $15 then TV-1 will start the extender. For temporary testing you can keymove the power function to another key, in the extender FAV is just another key.

Umm... I'm really dumb here.

WHERE do I make that change? (I'm guessing in IR's Raw Data page?)

Also, for your clarity/info, the UNEXTENDED 10251025 rdf that I am using is slightly changed from that in the rdf distribution zip. I have tailored it as follows:

[Settings]
VPT Device=$017.7.8.0.0 DeviceButtons
VPT Status=$014.2.1.1.0 (Off;On)
CBL uses VPT=$018.0.1.1.0 (No;Yes)
TV uses VPT=$018.1.1.1.0 (No;Yes)
DVD uses VPT=$018.2.1.1.0 (No;Yes)
AUD uses VPT=$018.3.1.1.0 (No;Yes)
AUX uses VPT=$018.4.1.1.0 (No;Yes)
CBL Channel Control Lock=$014.3.1.1.0 (Off;On)
CBL Setup Code Lock=$016.0.1.1.0 (Off;On)
KeyMap=$015.5.1.0.0 (Standard;Alternate)

# DeviceTypes
# The order matches up with default type on DeviceButtons
# The names match up with DeviceTypeAliases

[DeviceTypes]
Cable = 0
TV = 1
DVD = 2
CD/Audio = 3
VCR = 2,2

[DeviceTypeAliases]
Cable = Cable,SAT,Video Acc
TV = TV
DVD = VCR,DVD,Tape,Laserdisc,DAT
CD/Audio = CD,Tuner,Home Auto,Misc Audio,Phono,Amp

The [Settings] section chage as discussed to fix button scrambling and th DeviceType and DeviceTypeAliases entries chaged to remove confusing duplicate displays, like "DVD/VCR/DVD/VCR" in various locations in IR.

EDIT:
The former change should be made to the extender rdf as well, right?

The latter shouldn't hurt, should it?

I just tried using Extinstall-2 in IR instead of Extinstall and it wouldn't work. Is there still a change in IR required to support Extinstall-2?

I'll just build the Extended IR file from scratch, and not convert. No biggie.