JP1 Remotes

I must admit that the 15-100 is the one remote that I don't test vigorously since (1) I only have one of them and (2) it's a lot more work. On this extender I really only tested that it activated, loaded and processed my test advance codes that I build in on the test versions

(I have the remote load up macros, key moves, etc and then write out to the E2 area what it just did to validate that it processed stuff right)

I'll try to take a look at it but in the mean time you can always go back to your 1.02 configuration. Deactivate the extender, do a manufacturer reset on the remote, and then load up the old configuration and reactivate.

Thanks for the quick reply -- no great rush with this.

I hope my uploaded rmir's can help you.

Disclosure: I actually have three of these remotes. Two (using v102) were purchased at a considerable close-out discount, so I can safely tweak the third until any new upgrades are refined enough for everyday use. And I haven't bricked it -- yet.

Being able to select and control eight devices without resorting to arcane strings of keystrokes keeps my better half in a better mood :)

Tom

I figured out why the pause is probably not working on the 15-100. This bug will also impact the 15-13x and the Comcast 3039 remote.

On these remotes I was never able to find a routine that I rely on to do Pause in the built-in firmware so I built one myself into the extender. It didn't have a RETurn on the end so when it completed it was running into a bunch of code that went off into never-never land. That may be the issue with the labels as well, I'm not sure.

PM me with your email and I'll send you a new hex and RDF file that you can try out. If that works out for you then I'll post the updated V3.02 on the forums.



-bill

The bug in the pause also will impact the Atlas 3033 and Atlas 3000 remote.

I think I have the solution and have shared it with Thomas.