Atlas JP1.3 Extender beta - Topic CLOSED

[unclemiltie]

Update: 2/21/08

I've corrected the link here to point to the Beta4 drop and not the Beta2 drop that everyone was linked to. hopefully this will minimize the confusion that is out there.




Update: 11/27/07

I uploaded a new version of the extender with some bug fixes in it as well as a number of touch-ups in the RDF files. This version is NOT shipped with the source and the build environment but as a hex file that can be installed into an existing environment.

This configuration is closer to what will be a "release" version of the extender so I wanted to start getting feedback on installs, etc. The Readme has been updated to reflect what is in the extender as well.

Many, many thanks to Capn' Trips, Binky and Jeff for their help in finding and fixing bugs in this extender and to Vickyg for her suggestions on how to fix some things that were confounding me.

As usual, keep those comments coming and enjoy!







This extender supports the Atlas JP1.3 remotes with signature 30003000 and 30333033. Please be aware that this is a very early extender, use of this extender should only be with those with a reasonably good knowledge of extenders.

This extender is VERY different from previous extenders in that it is "activated" once and remains active (including when the batteries are removed) until it is deactivated. A keymove to deactivate the extender but it is not mapped to any key. The key to activate the extender is TV/OK


The extender can be found at:

http://www.hifi-remote.com/forums/dload ... le_id=5328



I have done minimal debugging of this extender, primarily with the 30003000 remote. Very little debugging has been done on the 30333033 OCAP remotes, but others have done some work with that one.


As always, post any issues here and I'll try to keep after them. I'm in the middle of moving across the country so my time is limited, so be kind!


-bill

[greenough1]

I'll also be monitoring this thread for issues and attempt to help out with problems.

Unclemiltie, I see for PAUSE there was a change in where you got the pause value from, now from R03 instead of R_key (current key). Was this the magic to make it work?

Thanks for providing a new beta,
jeff

[vickyg2003]

WTG Bill! I know how time consuming this is. Its a good way to fill up your time when your waiting for your family to make the move across country.


It will be great to have so many remotes with extender capabilities.
I sure hope you find the cause of the LKP problem. LKP is one of the most useful features I've come across. I thought for sure, it would be the LED like it was in the JP1.2 Atlas. I see that didn't fix yours. Too bad.

And Jeff, I hope you are enjoying your extender programming. It is so addictive.

[speaker.guy]

Is 3A333A33 something different from 3033033??

[Capn Trips]

3A333A33 is the extender rdf sig associated with 30333033 "natural" sig.
3A003A00 is the extender rdf sig associated with 30003000 "natural" sig.

Bill was just inconsistent in his usage in the first post.

[speaker.guy]

Thank you. Have you relocated yet, or still (personally) across the pond?

[Capn Trips]

The location indicated in my profile is accurate

[vickyg2003]

Capn, have all your belongings arrived from accross the pond too?

[Capn Trips]

Yes. Intact, as well. Still driving around with UK licence plates, however.

Back to the topic at hand:

Bill,

The readme states:

INCLUDED DOCUMENTS
==================

ReadMe.txt:

(This file.) Describes overall features, usages and trouble shooting tips.

Keys.XLS:

An excel spreadsheet with all of the assigned keys and keycodes used in this extender
and in the unextended remotes.

3A00ext.IR and 3A33ext.ir

the extender in a pre-installed state into an IR file

3A0ext.hex and 3A33ext.hex

the extender in a form that can be merged with your existing IR configuration
via Extinstall (Version 2 required)

*.RDF

the RDF file, place in your RDF directory to enable IR and RM to use this
extender

As far as I can tell, the highlighted items above are not present.

As I understood from before, your bat file should create those files but one needs Visual C Run Time installed for the bat file to work, and it wouldn't work properly for me. Is there a link for a better version of that program available somewhere?

[Capn Trips]

OK, I found 2 versions of the VC++RT:

vc6redistsetup_enu.exe
and
vcredist_x86.exe

which one do I want?

[greenough1]

I can tell you which when I get home. My first attempt I chose wrong and then I couldn't build.

[Capn Trips]

Well, I've gotten it to build (the batch file runs and executes all it's supposed to) but when I upload the resulting extender IR file to my OCAP (Atlas 5-Device OCAP URC-1056B01-L Silver w/ learning and backlight, battery compartment label 1056BC1-BLS-XXX-0001-001-R, base sig 30333033), the remote is dead.

Extender will not activate (I've tried immediately pressing "OK", I've tried pressing "TV" followed by "OK" - it just doesn't activate, pressing ANY button evokes NO response. (no illumination of a device button. No signal sent).

The only exception to this is when I press a DEVICE button, the pressed device button blinks. VCR, DVD, and AUD blink ONCE, and TV and CBL blink TWICE.

I never get 4 blinks, I never get 5 blinks, and NOTHING in the remote works.

Long-press setup functions are still accessible, so I'm certain the extender is not even activating.

Additionally, there are a bunch of RM issues with the extender rdf, but I'll dwell on those later.

Has ANYBODY got this extender to load and activate in an OCAP yet? I've been trying for over a month and have had no joy!

[unclemiltie]

Try this:

I don't have the deactivate keymove in the old keymove area so you're going to have to do some fun editing:

1: change the signature back to the normal signature in the IR file, that is change 3A333A33 to 30333033. This will activate the fall-back

2: load this to the remote, then restart IR. Download from the remote. This should give you the non-extended remote.

3: add a keymove that you will find in the LST file of the extender that is thedeactivate keymove. Put it on a real key, it's the same device/protocol as activate but the data is different (I'm at work so I can't tell you what the data needs to be)

4: reload the remote

Now, press the deactivate key. You've now patched the remote back to what it should have been from its original. you can do a full reset and then shoudl have a "normal" remote.


Now, start over again to load the extender. I suspect that you may have a patched remnant of an older extender lying around in your E2 and want to start by getting rid of that.

As for the "missing files" the Readme is meant to be done with a release version of the extender that doesn't have source. Since the BAT will recreate everything but the key list, you should be OK


-bill

[Capn Trips]

What if I take a remote that has never ever ever been hooked up to a JP1 cable, nor had a 981 reset done to it? (I have several OCAP remotes that I haven't removed from the bubble-wrap yet)

What if I download from that remote, run extinstall, and upload?

Should that give me a "pure, uncontaminated" extended remote?

[Capn Trips]

Well, I did what I asked about above, and te hresults are still the same. Extender will not activate and remote does nothing, even without activating the extender.