JP1 Remotes

Hello All,

I'm looking for insight on a macros programming issue, with ONE Atlas 1056 remote.

I have three Atlas 1056s set up for our living room system. On all three I had a macros programmed on "A" & "D" to A=watch VCR, D=from VCR back to TV. I had to reprogram the macros due to "D" sometimes being hit when scrolling on "Page Down". So, I moved these macros functions to "B" and "C" (DVR buttons).

The problem now: For general TV viewing, function key "Cable" is used, and for two of the three reprogrammed remotes, simply press "B" and everything goes to VCR viewing. However, on one remote, from "Cable" the macros will not respond! If I press "VCR" function key, the macros works! The problem here is the family will never figure this out!

I've cleared the key several times, each time verifying the key is clear, then reprorammed the macros, identical to the other two remotes, and the same issue occurs....? Returning back to "TV viewing" is no problem.

Again, for some reason, the macros will not respond when the "Cable" function key is in use? Any suggestions or comments?

Any help is greatly appreciated!!!

Please upload your .ir file, along with the RDF and MAP file you are using.

Thanks,
xnappo

It's my understanding that the Atlas OCAP 1056 is really only a good general purpose remote with an extender installed. The stock behavior is highly CBL mode centric and exhibits a lot of odd behavior (like switching into CBL mode unexpectedly).

xnappo wrote:Please upload your .ir file, along with the RDF and MAP file you are using.

Thanks,
xnappo

First, thanks for the help, but unfortunately these macros were manually entered. I haven't made the plunge into ful JP1 programming. Though, looks like it's getting time to do that!

gfb107 wrote:It's my understanding that the Atlas OCAP 1056 is really only a good general purpose remote with an extender installed. The stock behavior is highly CBL mode centric and exhibits a lot of odd behavior (like switching into CBL mode unexpectedly).

I'm now seeing that issue. As I said, this is only one remote doing this, the other two are fine. Also, for fun I programmed the same macros function into "A", and it works fine (from "Cable" function)...????

Somehow "B" is not reading the Cable mode. I'm wondering if it is solely a mechanical key issue. Though "B" does work fine from "VCR" mode.

bizwiz41 wrote:
Somehow "B" is not reading the Cable mode. I'm wondering if it is solely a mechanical key issue. Though "B" does work fine from "VCR" mode.

To you get them all from the same place? My guess is that the one not working is pre-programmed for a different cable system than the others.

xnappo

The problem now: For general TV viewing, function key "Cable" is used, and for two of the three reprogrammed remotes, simply press "B" and everything goes to VCR viewing. However, on one remote, from "Cable" the macros will not respond! If I press "VCR" function key, the macros works! The problem here is the family will never figure this out!

This sounds like there is a keymove on B. Your remote will check for keymoves before searching for macros. If a keymove is found, the macro will not execute.

I think Vicky is right. So to clear the suspected keymove:
1. Press Cable
2. Press Setup until two blinks.
3. Enter 994
4. Press button B twice
Should get two blinks.

And the macro should run in cable mode.

3FG wrote:I think Vicky is right. So to clear the suspected keymove:
1. Press Cable
2. Press Setup until two blinks.
3. Enter 994
4. Press button B twice
Should get two blinks.

And the macro should run in cable mode.

Thanks Vicky & 3FG!

Vicky was correct, and the prescribed fix worked. I'm not sure how a key move got onto this key, but it was the issue.

Thanks again, and I learned something today!

For my education, what is the priority, or sequence a key looks for when depressed?

bizwiz41 wrote:

Vicky was correct, and the prescribed fix worked.

Oh good. I just made a dumb arithmetic error in another post, so this makes me feel good.

For my education, what is the priority, or sequence a key looks for when depressed?

If memory serves me correctly its (LKM), learning, keymove, macro, and then it searches for the setup code, first in the upgrade area, and if not found there it will search the built-in library for the setup code. Most remotes unshift the key to when executing the setup code. This lends itself to shift-cloaking.

Shift-cloaking:
If you have a keymove on Play, and you have a macro that calls Shift-play, setup-code-play will be executed, instead of the keymoved-play.

bizwiz41 wrote:I'm not sure how a key move got onto this key, but it was the issue.

Most cable providers have their remotes pre-programmed with not only the upgrades for whatever Cable box it is to operate, but also with some pre-planned keymoves and/or macros, which vary depending on which provider is providing. Since all Atlas remotes are pre-programmed for SOME Cable or Satellite provider, but not necessarily the SAME one it is perfectly reasonable that one of your Atlases has different programming "out-of-the-box" than another. Even if they all have "TimeWarner" silkscreend on them, Time Warner in Long Island will not have the same programming as Time Warner in Dubuque.

Capn Trips wrote:

bizwiz41 wrote:I'm not sure how a key move got onto this key, but it was the issue.

Most cable providers have their remotes pre-programmed with not only the upgrades for whatever Cable box it is to operate, but also with some pre-planned keymoves and/or macros, which vary depending on which provider is providing. Since all Atlas remotes are pre-programmed for SOME Cable or Satellite provider, but not necessarily the SAME one it is perfectly reasonable that one of your Atlases has different programming "out-of-the-box" than another. Even if they all have "TimeWarner" silkscreend on them, Time Warner in Long Island will not have the same programming as Time Warner in Dubuque.

Thanks for the education; I'm still learning all about this science! I think you nailed it with the different providers set up. This would explain why only one of three had the issue.

P.S. Can you recommend an extender that would work with both the Atlas and Comcast remotes? I'm learning I need to further "error proof" all the remotes for the family! Time to learn full JP1 programming and set up, as it looks like discrete codes are needed!

Each remote with a different signature has to have its own extender developed and they are not interchangeable among different remotes. In general (except a few rare exceptions) if an extender has been developed for a remote, there is only one extender.

The Atlas OCAP has a very good extender. I'm not very familiar with the Comcast remotes, but at least some of them have extenders, as well (vicky?)

Go to the file section, and there is an extender area where all of the extenders are kept. You can find the ones for any remotes you have there. If there is not one there, then it does not exist.

Also, in the extender forum, there is a FAQ you might want to read.

Capn Trips wrote:Each remote with a different signature has to have its own extender developed and they are not interchangeable among different remotes. In general (except a few rare exceptions) if an extender has been developed for a remote, there is only one extender.

The Atlas OCAP has a very good extender. I'm not very familiar with the Comcast remotes, but at least some of them have extenders, as well (vicky?)

Both the Comcast 1067 and 1067Bx3 remotes have an extender, but neither of them has any learning memory to exploit. The 1067Bx3 has a lot more memory than the 1067, so the 1067 extender has to go through a two stage install. These remotes really need to have an extender to be useful.

bizwiz41 wrote: P.S. Can you recommend an extender that would work with both the Atlas and Comcast remotes? I'm learning I need to further "error proof" all the remotes for the family! Time to learn full JP1 programming and set up, as it looks like discrete codes are needed!

the extender for the Comcast 1067BX3 (JP1.3 Comcast remote with the "red" OK button") is identical in function the Atlas extender, it was a direct port of the code.

As Vicky said, there is no learning memory to use for more upgrades, so it is a bit more limited. But from using it and programming your remote they are essentially the same.