JP1 Remotes

I've just uploaded V2.10 of the extender for the Atlas remotes here:

This version includes:

- Full support for IR 8 including IR version display, setup code checking and pause values
- bug fix on end of Advance code area in RDF
- bug fix on macro searching that caused odd errors
- new feature that enables long-press of setup to deactivate the extender
- optional long-press on backlit OCAP to toggle backlight


Edit: updated to V2.12

fix bug in LDKP processing in all JP1.3 extenders

dload.php?action=file&file_id=6597

Edit: updated to V2.13

fix bug in processing of PIP keyset


https://www.hifi-remote.com/forums/dload ... le_id=9800

Is this different than the version i've been testing?

There is also still a

*** rewrite this section ***

in the nested macro section of the readme.

While not a fan/user of extenders, I have followed your adventures, and may I offer sincere congratulations on release of the product, and thanks to you and all who have contributed to its successful completion!

Maybe some day...

Evan

The only difference between 0.08 and 1.00 is that the version number was changed. So, as long as you're using 0.08 then no change


speaker.guy

The initial topic got something 15K views and nearly 250 replies. I'm amazed at the interest in that remote! it'll be interesting to see how the extender does when people who are "afraid" of beta's start to use it.

OK thanks. I'll double check but I'm pretty sure that is what you emailed me to test.

All

in releasing the extender for the Radio Shack 15-13x I found a bug in the code when a ToadTog has an "empty" side (ie: when on, do nothing, etc) that the toggle won't get set/cleared/toggled.

I've fixed this in the RS extender and will release a new version of the Atlas extender when I get a few minutes to sit down and make the change to the code in the Atlas.


I've also found a way to hide away the special protocol code somewhere else so that it doesn't take upgrade space. I'll implement that as well when I do the new version for the Atlas remotes.

hopefully in a few days, but I want to make sure that the dust settles on what I did for the RS remotes before I go and do surgery on the Atlas extender

-bill

thanks for your continuing updates unclemiltie. everything is working great.

edit: I'm trying out the new version (with the new rdfs) and get this error on startup in ir:

"There is a conflict at fixed data address $0200. Do you want to replace the existing data witht he fixed data?"

anything I should be worried about? Should I click yes or no?

edit2: also I get "Bad checksum at address $0200. Expected $9B $64 but found $4B $4E" when trying to load my old extended ir files.

hmmmm. I'll take a look at it. All I changed was the location of one JR in the code and rebuilt, so this is weird.

I just finished major surgery on the RS 15-13x extender tonight, I'm in the process of uploading it. When I get a chance, I'll take a look at the Atlas and see what I did wrong.

Took a quick look before I head off to bed....

The data at $200 (actually $800) is the private area of the remote. I touched nothing in that area and the builds of the assembled list files verify that nothing got hit there. This is really confusing.

Also, the only thing I did to the RDF's was to change the version numbers.

So, can you revert back to the old extender version and let me know if you are still having this issue. If you are, send me an email (I think you know my home email) with the V1.00 IR file and the V1.01 IR file and I'll take a look.

-bill

it works fine with the old rdf. I took a look and it seems this section is different:

(old):

[Checksums]
^$008:$00A..$01A
^$400:$402..$BFF

[Settings]
Shift Keycode =$0AB.7.8.2.0
XShift Keycode =$0B5.7.8.2.0

(new):

[Checksums]
^$008:$00A..$01A
^$200:$202..$3FF
^$400:$402..$BFF

[Settings]
Shift Keycode =$0A6.7.8.2.0
XShift Keycode =$0B0.7.8.2.0

and a bunch of button names seem to be different.

I dont know how the checksum creeped into the 30003000 remote RDF since the private area does not have a checksum. (the 30333033 does have a checksum)

I will upload a new version in a minute, but if you just want to edit the RDF, remove:

^$200:$202..$3FF

and all should be good

Bill,

I believe that when you updated the extender rdfs, you missed a change from the Atlas DVR 3033 to the OCAP. It's calling the wrong image files in RM. I believe that you need to change the line:

ImageMap=Atlas-5-PVR-Day.map; to

ImageMap=Atlas OCAP Black.map,Atlas OCAP Silver.map

The Cap'n

OOPS! Even more problems with the new extender rdf.

The following button issues have appeared:
(1) In RM, the Settings button is gone, and button3F has appeared;
(2) In IR, the SETTINGS button is gone, and Key63 and Key241 have appeared (at least for the CBL device type. For a TV Device Type, only the Key63 is present.

HAAALLLLLP!

Well, it looks like the extender rdf is again missing a line:
In the [Buttons] section,after:

x2:D[green]=$3D,

but before the Phantoms begin, I believe that you've lost:

"device button":SETTINGS=$3F,

However, I STILL cannot fathom the mystery ButtonF1 that appears in RM and the Key241 that appears in IR in certain Device Types, although those have been around since the beginning of this remote!

grrr... I hate stupid mistakes. This is the second one in the update.