JP1 Remotes

I upgraded to V2.04 today and started from scratch. I have everything setup and I DO NOT have the issue with loss of control over CBL power. At least with some preliminary testing.

The changes between 2.03 and 2.04 were minor, as far as I can tell. I'll keep testing and see what happens.

For now, there's no debugging to do on my account. I'm very happy as I really like the layout of the Atlas remotes.

Best,
jeff

All

One of the features that I built into the 15-100 extender that I posted yesterday was a "Long press setup" that would deactivate the extender.

I'm wondering if people think that this is worth back porting this to the Atlas remote? how this works is the remote looks at the shift/setup key (whatever you have defined it as) and if it is a short press, the extender works as it does today. If this is a long press, the extender is deactivated as if you used the Deactivate keymove.

Is this interesting?

What's the duration? Is it variable? In any case, it would be a nice addition.

One kink though is the backlit atlas. I'd rather see setup LKP toggle the backlight. The way you have it implemented now is fine, but moving it back to the setup would be more intuitive.

dave

I can do that. What I did on the 15-100 is I put a toggle in the settings that asked the user what they want the long press to do. On the 15-100 it can either put the remote into clock-set mode or deactivate.

The only issue on the Atlas is that I may not have enough code space for both.

I could have sworn that all of my atlases are backlite. But I noticed (last night) that the backlighting was not working. Sort of taking the remote apart, how can I tell if it's capable of backlighting? Is there something in the extender (v2.04) that would disable/enable backlighting?

Thanks and I'm really enjoying this extender.

Best,
jeff

"I could have sworn that all of my atlases are backlite. But I noticed (last night) that the backlighting was not working. Sort of taking the remote apart, how can I tell if it's capable of backlighting?"

Buttons are translucent (very light gray) on a backlit capable remote, solid (almost black) in a non backlit one.

All of the buttons are translucent on all of the ones I've got. Ok. Just checked the manual (RTFM). Pressing setup twice within one second is the toggle for it on or off.

I can't seem to keep backlighting turned on when running the extender. I disable the extender and activate it and it works. Then reactivate the extender and it works. Any keypresses, though, disable the backlighting.

Unclemiltie, any ideas on how to preserve the backlighting setting in the extender?

Best,
jeff

Jeff,

Bill already has backlight control in the extender, but it doesn't use the setup button. The version with backlight control has a TV: 1105 device. If you have that device, just make a key move using TV 1105 with an EFC of 00000 using whatever key you like. That key will toggle the backlight. I put mine on a phantom key and used an LKP macro on my Source button to call it.

My earlier post was just asking Bill if he could implement it in a different way, but he probably doesn't have room to do it. The way he has it now works fine.

Thanks. That did the trick.

mdavej wrote:Jeff,

Bill already has backlight control in the extender, but it doesn't use the setup button. The version with backlight control has a TV: 1105 device. If you have that device, just make a key move using TV 1105 with an EFC of 00000 using whatever key you like. That key will toggle the backlight. I put mine on a phantom key and used an LKP macro on my Source button to call it.

My earlier post was just asking Bill if he could implement it in a different way, but he probably doesn't have room to do it. The way he has it now works fine.

FYI - you can also take out the batteries and put them back in while holding down setup to get backlight back on.

xnappo

greenough1 wrote:I can't seem to keep backlighting turned on when running the extender. I disable the extender and activate it and it works. Then reactivate the extender and it works. Any keypresses, though, disable the backlighting.

Using my modified backlight protocol that implements a "discrete on" for the backlight (See this post.):

mr_d_p_gumby wrote:Bill: I experienced some minor problems with the backlight. I had set up an LKP on each device button, and the DVD & CBL button would turn off the backlight. I got around this by calling a discrete-on keymove (no-blink) in each path of the LKP.

I took a look last week and it looks like I'll be able to implement the long-press setup (whatever key you have it defined as) to do either toggle the backlight or deactivate the extender. This option will be a load-time option in the IR setup panel (as I did for clock set or deactivate in the 15-100)

I'm a bit stretched for time these days.... I did get a contract job that is taking a good bit of time (yea, something to pay the bills), taxes need to get done and my son has soccer tournaments every weekend this month...Argh!

The code is a bit more complicated than the 15-100, it had a "check this key for long press" entry point that made it easy, the Atlas doesn't have this, but I think I know how to do it and I think that it'll fit. now all I need is some time to code it up and play.

BTW, I tried out the 15-100 in my configuration for my HT system for the past few weeks and have to say I'm going back to the backlit Atlas. That remote really does grow on you.

mr_d_p_gumby wrote: Using my modified backlight protocol that implements a "discrete on" for the backlight (See this post.):

Mike, Sorry that I missed your post linked above with the discrete on backlight protocol. I implemented something similar last night, since I had trouble using a keymove to keep the backlight toggle set.

I created a toadtog for the backlight (the backlight toggle is assigned via keymove to an unused key). I force it on through both the long and short sides of my LKPs. This seems to work.

Best,
jeff

2.04 (I think) included Mike's backlight protocol by default. You should not have to do anything if you are using that version. The Readme has also been updated to reflect the new backlight protocol contributed by Mike.

When I open my OCAP Extender file with IR, I get a conflict at fixed data address 01FF. I am currently using the 2.05 version of the OCAP Extender RDF. I'm not sure whether I built this IR file with this version or with a previous one.

Is the fixed data entry in the RDF required? If it seems likely that this IR file was built using a previous extender RDF, does that mean that I basically have to rebuild my entire IR file from scratch? ...or can I just accept the fixed data and save the new file and all will be well?