JP1 Remotes

Hi Capn,
I've not upgraded to 2.05 and am still at 2.04. After at least 3 full rebuilds, I'm disinclined to do a full rebuild again if not necessary. Hopefully Bill will be around soon and comment on your issue.

2.04 is rock stable. I've replaced all the remotes throughout the house with the black backlite 1056 3033/3A33 and everyone couldn't be happier. I even found a use for the green and red buttons - all on and all off master macros.

Best,
jeff

Capn Trips wrote: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?

What this means is that the extender that you are using is not the same version as the RDF that you are using.

The extender saves the version as two hex digits at $1FE ($7FE in IR) and the fixed data in the RDF tries to match up with the version.

What changed in 2.05 was:

Support for IR 8 pause calculations in seconds instead of hex values
fix for device combiner from Binky (RDF only)
versioning support in the RDF


So the 2.04 extenderSHOULD work with the 2.05 RDF.

BTW, 2.10 is coming.... This will implement what I did for the 15-100 in a long-press of the setup key will deactivate the extender. (on the backlight version it can be changed to toggle the backlight) I've done the coding but haven't had a chance to load it into a remote and make sure I didn't break anything.

2.10 will require a rebuild, but if you don't care about long-press-setup to deactivate, you can ignore it.

I've uploaded 3 rdf's for the v2.04 extender where I've added the setup code verification stuff. this is for the 3A333A33 and the 3A003A00 remotes.

This feature works with IR v8.00 latest beta works great and saves time consuming debugging issues when you have upgrades with setup codes that are the same as native setup codes!

Here's the LINK

Best,
jeff

I've built a new version of the extender but have not had time to test it. If anyone is interested, PM me and I'll send it to you for testing.

This version has:

long press setup to deactivate
optional long press setup to toggle backlight on OCAP

IR8 setup code validation
IR8 extender version display

This version requires IR 8, beta 9 at least

If I can get some testers then I'll be able to release this sooner, otherwise it'll have to wait until I get through all of the stuff that I'm working on including rebuilds of all of the JP1.3 remotes

Bill,

Can you please take a look at this post?

gfb107 wrote:More clues definitely helps.

A big part of your problem Capn, is an error in the RDFs for URC-1056 extenders:

Code: Select all

EepromSize=$1400
...
AdvCodeAddr=$0C00..$19FF
...
BaseAddr=$0600

Note that the AdvCodeAddr specifies the end address is $19FF, which is beyond the EEPROM size of $1400. This is partially caused by an quirk in the way addresses must be specified in the RDF. All addresses must be relative to the start of the EEPROM area, so it is a common mistake to put the absolute address used by the extender in the RDF, forgetting to subtract the BaseAddr. In this case $19FF-$0600=$13FF

Try using

Code: Select all

AdvCodeAddr=$0C00..$13FF

.

That should improve things significantly.

The extender writer should also double check the AdvCodeAddr and UpgradeAddr entries.

Greg is correct, the way that the JP1.3 RDF's work is that they add those numbers to the base address and even though the "real" address of the end of the E2 area in the JP1.3 remotes is $19FF, the RDF should say $13FF

Just checked and alll of the Atlas remotes have this issue. Easy change for those of you who use the extenders. I will make the change in the distribution.


PS

I know that I said that I would be releasing V2.10 last week but haven't done so yet. It's on my list of things to do. Traveling again this week, but maybe this weekend. (I hope)


-bill

No pressure, Bill.

We all have real lives to lead (well, MOST of us, Rob!) and I feel guilty that I have not tested the extender more extensively, that I have not tested the XSight Touch more thoroughly - all on my "intend to get around to it" list.

All efforts, large and small are appreciated ...



....and undercompensated!

unclemiltie wrote:Greg is correct, the way that the JP1.3 RDF's work is that they add those numbers to the base address and even though the "real" address of the end of the E2 area in the JP1.3 remotes is $19FF, the RDF should say $13FF

Thanks bill - is C000 the correct start? And thanks Capn and Greg for chasing this down. This had been causing problems for me that I had thought were something else.

xnappo

See base topic, Version 2.10 has been released

A few things. Using 2.10.

1. It looks like X_Cancel is missing from the RDF provided (I was told this in my thread here: http://www.hifi-remote.com/forums/viewtopic.php?t=11013)
2. Regarding toggling the backlight, is there any way to add an option for long key press duration for the setup button? Through trial and error it seems to take 4 seconds to get it to toggle reliably. 1 or 2 seconds would be more ideal to me.
3. Again regarding toggling the backlight, is there any way to add visual indication that the toggle has happened, like a blinking of the blacklight for instance? Some method of notifying the user that they don't have to hold the button down anymore (i.e. they've passed the lkp threshold). Currently there is no indication until you actually release the setup button.
4. As was also discussed in the thread mentioned above, I'm just curious if it is technically possible to add phantom device support due to the limitations of device multiplexing (in particular, the fact that key moves are shared between the multiplexed devices). It's not super critical to me because I got everything working that I wanted to, but my IR file would be a lot less complex if I could have used a phantom device rather than multiplexing.

Thanks so much for developing this extender. Despite a lot of time invested in figuring out how to get the remote to do everything I wanted, I accomplished what I wanted and I'm sure I'll be very pleased to use this new remote from now on. Without the extender that wouldn't be possible since I have more than 5 devices.[/list]

TheShanMan wrote:A few things. Using 2.10.

1. It looks like X_Cancel is missing from the RDF provided (I was told this in my thread here: http://www.hifi-remote.com/forums/viewtopic.php?t=11013)
2. Regarding toggling the backlight, is there any way to add an option for long key press duration for the setup button? Through trial and error it seems to take 4 seconds to get it to toggle reliably. 1 or 2 seconds would be more ideal to me.
3. Again regarding toggling the backlight, is there any way to add visual indication that the toggle has happened, like a blinking of the blacklight for instance? Some method of notifying the user that they don't have to hold the button down anymore (i.e. they've passed the lkp threshold). Currently there is no indication until you actually release the setup button.
4. As was also discussed in the thread mentioned above, I'm just curious if it is technically possible to add phantom device support due to the limitations of device multiplexing (in particular, the fact that key moves are shared between the multiplexed devices). It's not super critical to me because I got everything working that I wanted to, but my IR file would be a lot less complex if I could have used a phantom device rather than multiplexing.

Thanks so much for developing this extender. Despite a lot of time invested in figuring out how to get the remote to do everything I wanted, I accomplished what I wanted and I'm sure I'll be very pleased to use this new remote from now on. Without the extender that wouldn't be possible since I have more than 5 devices.[/list]

1: X_Cancel is in the extender, I must have killed it in the RDF when I was doing some cleanup. I'll re-issue 2.10 with this fix, but in the mean time, you can put it in the RDF. It's one after the last pseudo key. (mdavej says that I made this mistake when I released 2.03, go figure that it took this long for someone to catch it)

2: since I am using the built-in long-press detection, I'm stuck with the timing in the remote. The Atlas extender is tight on memory, in fact I think I had to do a bit of squeezing to get this part in, so doing my own check for long press really isn't possible.

3: good suggestion, Again, I'm using the built-in routine to check for long press, but I think it comes back after a timeout and I could blink or turn the backlight on. I've got to think about that one.


4: I tried at one point to re-allocate some of the E2 setup area to add a couple of phantom devices and the remote crashed in a pretty bad way. I will admit that once that happened, I didn't try to hunt down what was going on, but there are several spots in the remote where the number of devices are hard coded and I'm sure that's where I got hurt. Right now, I'd say that phantom devices are not going to happen, but hey you never know.....


Finally, thanks for the kind words about the extender. I really don't know how I got into wasting so much time on my remotes!

Out of all my suggestions, the indication of toggling the backlight is definitely what I'd like to see the most, so I'm glad to hear that you might be able to at least do that one. Thanks again!

no changes to the extender, just re-released the package with new RDF's that include X_Cancel


if you've fixed your RDF's, no need to download again.

-bill

Well, I finally had a few consecutive minutes this weekend and tried to set up my Atlas OCAP (URC-1056) using all of the latest tools. IR 8.01 Dev build 2 and Bill's extender v 2.10. Confirmed all of the right RDF's were in the right folder and wanted to make a clean build.
(1) Did a 981 reset;
(2) Downloaded into IR;
(3) Ran Extinstall for the 1056 v. 2.10;
(3a) noticed that all of the Devices were reset to CBL 0000 (Is that supposed to happen?)
(4) Added one upgrade (for my Sharp LCD TV - a pretty standard one);
(4a) assigned random device codes for the others (selected from the Device Code selctor, so presumably they are in the library and would not cause any problems/lockups)
(5) Uploaded config to the remote - all upload indications were normal;
(6) PROBLEM: Cannot activate the extender!
(a) If I press OK, nothing happens;
(b) If I press "TV", it blinks twice - AND the TV Power toggle signal is sent! And I have NOTHING programmed to that button aside from the default device-selection macro!
(c) If I press "CBL" it blinks twice;
(d) If I press any other button, nothing happens. No lights, no IR signal, nothing.

What's going on? Why can I not even activate the extender? I cannot see any mistakes in my process. I got so desperate that I even read the README, and it shed no light on a possible process foul by me. And are all of the device settings supposed to reset after running extinstall?

So I'm violating my first rule here by NOT including an IR file for you to look at (because I'm at work and do not have that file with me, and cannot recreate it because I cannot load any of the executable programs onto my computer here (no extninstall capability)). That's why I described the process in such detail.

Will post with files tonight, but in the interim, any ideas? Has anybody successfully run this combination of JP1 tools?

Here's the subject IR file. Can someone with an OCAP please test it just to see if you can activate the extender?

And if not, help figure out what's wrong?