JP1 Remotes

speaker guy

there is nothing that is different from provider to provider on the remotes that have the same signatures other than what is in the area from $600-$1A00 (and more specifically what is in the private area) I have verified this with a number of remotes.

That said some of the stuff in the private area may be what is going on. I need to spend some time on this and get back to you guys.

vickyg2003 wrote:Jeff, I believe its the AllBind that is preventing your keys from being in the DSM dropdown list.

Thanks Vicky, that fixed it.

I made Binky's replacement and LKP didn't work; I didn't get a chance to try an debug it.

Best,
jeff

speaker.guy wrote:

Capn Trips wrote:So there appears to be something hard-coded in the non-writable area of the Flash-ROM that (a) controls this behaviour, and (b) may vary from provider to provider.

Did I suggest that?

Not the way I read it. Perhaps I misunderstood. Here's what you suggested:

speaker.guy wrote:
F1, On Demand, and F2 have some hidden macros to control specific cable functions depending on the cable provider. They may still be loaded, and would surely leave the remote in cable mode after execution.....

You specifically talked about macros, and this (imho) is not macro behavior. I suppose the "hidden" part is correct, but the "macros" part was what caught my notice and didn't seem to fit the symptoms. Sorry I was so thick.

I looked at the code in the remote again around register uses and think that there are conflicts with the registers that I was using for the device table in the extender. This may have been the culprit for the mysterious device change isseus that people have experienced. I've moved register assignments around from RB0 to RA0 to hopefully fix this issue.

I've also incorporated Binky's suggested LDKP fixes

Finally some of the RDF chagnes suggested in this thread have been adopted as well. I hope I got them all.

A new version has been uploaded to replace the original at the beginning of this thread. This has been labeled V0.02 to avoid confusion.

Hi unclemiltie,
I've downloaded and built it.

There's still an issue with LKP. I've uploaded my IR file HERE.

Is the problem trying to put LKP on a device key? Generally I would think not, but if you edit the IR file linked above and change the LKP macro for TV to be on say the "A" button, it executes. If put on "TV" key, it doesn't execute.

Best,
jeff

Great progress, Bill. Happy to read this.

Rats! I'm away from home for the long weekend and can't test anything (aside from software compatibility). Hopefully Jeff will find all of the remaining few issues and Bill will have them ironed out by the time I emerge from the I-95 parking lot Sunday night!

I certainly like the rdf in RM much better now - suddenly, we have a bunch of phantoms!

But DiscreteON and DiscreteOFF still don't show up on the Layout tab in RM, just on the Buttons tab.

Although this is v 0.02, am I correct that you did not update the rdf to reflect this? (an oversight, I presume)

yes, an oversight. I didn't rename the RDF files for this version

By the way, a couple of thoughts on keys, etc:

1: The Discrete On/Off key assignments in the extender are "Shift-00" and "Xshift-00" which maybe is why they don't show up in the list of keys. This is a question for greg or someone who is an RM expert

2: on the buttonF1, etc keys. These are, unfortunately, in the list of valid keys for a device and thus they show up. Another question for an RM expert is, can we make it so that RM ignores keys in those lists unless there is a name assigned to it. These "phantom" keys are used inside the remote but they really don't exist.


-bill

greenough1 wrote:There's still an issue with LKP. I've uploaded my IR file HERE.

Is the problem trying to put LKP on a device key? Generally I would think not, but if you edit the IR file linked above and change the LKP macro for TV to be on say the "A" button, it executes. If put on "TV" key, it doesn't execute.

Any thoughts on this?

I'll download and look at your IR tonight, sorry I forgot about your issue.

Do you have another Macro or something else defined for that key? (I'll see that when I download tonight)

Hi,
There's no other macro defined on the TV key, so some search precedence seems unlikely. As I wrote above, if you redefine the LKP for the TV key to be on the A key the LKP macro works. It doesn't seem to execute at all if left on TV. I didn't test it on other device keys but assume it would fail similarly.

Best,
jeff

Thanks for the background. I don't quite understand what is going on here since the extender treats all of the keys alike, ie: the only thing that happens to device keys is that macros or keymoves are applied to them.

Anyway, let me take a look and see if I can find something else.


-bill

Jeff

Maybe I'm missing something but in the IR that I downloaded there is a macro on TV. In the raw data the macro starts at $1279 and is defined as M_TV,P_TV,C_TV,V_TV,T_TV,O_TV

There is also no LKP defined for the TV button, so I must be missing something or you uploaded the wrong file?


Like I said before, all of the buttons are treated the same in the extender. The first thing I do is search the Advance code table for the button, if I find it I then do:

if a macro, execute it and stop looking
if a keymove (including the specials) is it for the current device
if so execute it and stop looking
if not, continue searching

So, when I find a macro in memory that is bound to a key that has a keymove later in memory, the macro will execute. IR doesn't check for such stuff, so you have to be careful when crafting your macros, keymoves and special protocols.


OH by the way, can you tell me which remote this came out of? If I have to load it into my remote it would be helpful (although I only have a Silver OCAP with signature 30333033 so hopefully that's what you have!)

-bill

unclemiltie wrote:Jeff

Maybe I'm missing something but in the IR that I downloaded there is a macro on TV. In the raw data the macro starts at $1279 and is defined as M_TV,P_TV,C_TV,V_TV,T_TV,O_TV

There is also no LKP defined for the TV button, so I must be missing something or you uploaded the wrong file?

I just re-downloaded it to check. It's the correct file. Look on the special protocol tab of IR. That's where the LKP is defined - 4th line down. The short side is the DSM on the 3rd link

unclemiltie wrote: Like I said before, all of the buttons are treated the same in the extender. The first thing I do is search the Advance code table for the button, if I find it I then do:

if a macro, execute it and stop looking
if a keymove (including the specials) is it for the current device
if so execute it and stop looking
if not, continue searching

So, when I find a macro in memory that is bound to a key that has a keymove later in memory, the macro will execute. IR doesn't check for such stuff, so you have to be careful when crafting your macros, keymoves and special protocols.

This might be it. In my extended 8811 and 8910, I have keyset selections defined as macros on the device button way (like I'm doing here) but I also had the DSM which duplicates the macro for the short side and the more complicated macro for the long side.
Can you elaborate a bit more about how to be careful with this extender not to fall in the trap I'm in? Is it as simple as deleting the macro that's defined on the TV key in the macro tab?

unclemiltie wrote: OH by the way, can you tell me which remote this came out of? If I have to load it into my remote it would be helpful (although I only have a Silver OCAP with signature 30333033 so hopefully that's what you have!)

The IR file came out of my 1056 OCAP sig 30333033 (black, backlit, learner.