Atlas PVR JP 1.2 (1025) extender beta testing comments

Post by **vickyg2003** » Tue Sep 04, 2007 7:00 am

Bill wrote:
Vicky, did you put the ability to set the initial devices in the extender? (they would either be saved somewhere along with the code and the RDF to match or they'd be re-used registers that are read by default at power up)

Yes, we have the ability to use initial devices in the RDF. The JP1.2 has 2 kinds of memory, quick memory that can be directly manipulated, and not so quick memory that needs to be loaded into registers. I found some unused not so quick memory to use for my device table.

Capn

DON'T BOTHER WITH THE CURRENT VERSION OF THE EXTENDER. I've made major changes in the core of the extender to get rid of the time delay. All seems to be running well, but I've run out of time to package it up (its quite a time consuming process) and I've got to get to work. I'll post it tonight.

Post by **vickyg2003** » Tue Sep 04, 2007 6:21 pm

I did update it on 9/4

Capn Trips · Post by **Capn Trips** » Wed Sep 05, 2007 4:29 pm

This version works great! No excessive latency periods, all special protocol functions seem to work. I like it. I think it can be declared "ready for prime time":D

Comment:
Your bare bones Atlas5DeviceDayPvrExtender.ir file originally had "Notes" entries for each Special Protocol and Device upgrade specifying what each one was. Those are absent from the current file.

So now I have:
(1) one Atlas URC-1054 JP1 (SA_7SA_7) running its extender (SA_71KX1) - limited by its 1K EEPROM

- works great;
(2) one Atlas URC-1055 JP1.2 (10251025) running your extender (1A251A25) - pretty darned good, certainly no memory problems - but the Power button doesn't work

;
(3) one Atlas URC-1055 JP1.3 (30003000) that I have yet to program

;
(4) and SEVEN Atlas OCAP URC-1056 JP1.3 (30333033) which I finally have a working RDF for and MUCH prefer button-wise to the others

.

Anybody out there have the time or inclination to develop an extender for the URC-1056? I'll gladly provide a couple for the person's efforts.

unclemiltie · Post by **unclemiltie** » Wed Sep 05, 2007 4:39 pm

Capn Trips wrote: (3) one Atlas URC-1055 JP1.3 (30003000) that I have yet to program :oops: ;
(4) and SEVEN Atlas OCAP URC-1056 JP1.2 (30333033) which I finally have a working RDF for and MUCH prefer button-wise to the others :eek: .

Anybody out there have the time or inclination to develop an extender for the URC-1056? I'll gladly provide a couple for the person's efforts.

Cap'n
(isn't the 30333033 a JP1.3 remote? or did I miss something)

I've been tearing through the 3033 for the past few days and am going to give a go at porting the extender that I did for the URC-9960B01 to this beast. It looks like it'll port reasonably easily.

The only JP1.3 that I have (thanks Vicky) is the 30003000 so I was going to start there, but if you're inclined to give up a 30333033 for a while, I'll be happy to start there.

PM me and we can arrrange the "loan"

Capn Trips · Post by **Capn Trips** » Wed Sep 05, 2007 4:57 pm

unclemiltie wrote: Cap'n
(isn't the 30333033 a JP1.3 remote? or did I miss something)

Of course it is. I was just conductung a little test to see who's paying attention. You pass.

(and everybody else fails

)

unclemiltie wrote: I've been tearing through the 3033 for the past few days and am going to give a go at porting the extender that I did for the URC-9960B01 to this beast. It looks like it'll port reasonably easily.

The only JP1.3 that I have (thanks Vicky) is the 30003000 so I was going to start there, but if you're inclined to give up a 30333033 for a while, I'll be happy to start there.

PM me and we can arrrange the "loan"

No problem.

Post by **vickyg2003** » Wed Sep 05, 2007 8:15 pm

Your bare bones Atlas5DeviceDayPvrExtender.ir file originally had "Notes" entries for each Special Protocol and Device upgrade specifying what each one was. Those are absent from the current file.

I added that to my checklist. Putting one of these things together is so complicated.

I did put one final version out tonight. Underquark pointed out that when I fixed the button press speed, I made the HT macros too slow. If you did a lot of device changes the macros lagged. So I fixed that and I think one more one through and we are good to go!

Robman

How do I get folders for my Atlas and my URC8820 extenders?

Capn Trips · Post by **Capn Trips** » Thu Sep 06, 2007 3:34 am

vickyg2003 wrote:
Robman

How do I get folders for my Atlas and my URC8820 extenders?

Perhaps it would be worthwhile to put all of the Atlas extenders in the same folder, so that one can see all of the variants lined up in a single list, making it (hoopefully) easier for a user to spot the differences/distinctions between them.

Capn Trips · Post by **Capn Trips** » Thu Sep 06, 2007 4:19 am

vickyg2003
I notice that the individual Special Protocol readme/help .txt files are still pretty much the same as they were WAAAY back in the old days, when IR did not have a Special Protocols tab, and one had to build ToadTog, DSM, and D/LKP sequences by a brute-force method, using hex commands in the Keymoves tab.

IR's new interface via the Special Protocols page renders those ReadMe's quite unnecessary, confusing and useless.

If you wish, I can take a shot at re-writing those to address the current capabilities of the software tools. Unless you tell me that you have already done this, but have not yet finalised/uploaded them, I will try to do this - presumably it would apply to MOST Extender-related Special Protocol functions so it may have a wider application than just the 1A251A25 extender.

(Maybe I'll just append it to the Extender FAQ sticky post.)

unclemiltie · Post by **unclemiltie** » Thu Sep 06, 2007 4:23 am

Cap'n & Vicky

Take a look at the special protocols section in the URC-9960B01 readme. I made an attempt in those to update the special's section to reflect that IR now suports specials. I'll bet that you can copy/past most of that for this new extender.

-bill

Capn Trips · Post by **Capn Trips** » Thu Sep 06, 2007 2:14 pm

vickyg2003 wrote: I did put one final version out tonight. ... I think one more one through and we are good to go!

Initial usability test indicates it works great!

I haven't really stressed it or tried to break it, but re-creating my current HT setup all works properly, quickly and reliably (so far).

PLEASE stop making new ones - it takes an hour to re-build all of my SP functions, Macros and Keymoves every time!

unclemiltie · Post by **unclemiltie** » Thu Sep 06, 2007 2:29 pm

Cap'n

you should be able to use the Extinstall-2 version from a command line to install new versions of the extender into your IR file. I tested it when I was building the new version of Extinstall with someof Vicky's early work on the extender. (this version also preserves comments from your IR file)

This doesn't work (yet) from IR since IR doesn't tell Extinstall where to go look in the file for the signature. Binky's working on that as well and should have something soon.

the syntax for the new version is:

Extinstall-2 extender.hex input.ir output.ir -signature=$EA00

(I think EA00 is right for this extender)

Post by **vickyg2003** » Thu Sep 06, 2007 3:08 pm

I notice that the individual Special Protocol readme/help .txt files are still pretty much the same as they were WAAAY back in the old days, when IR did not have a Special Protocols tab, and one had to build ToadTog, DSM, and D/LKP sequences by a brute-force method, using hex commands in the Keymoves tab.

IR's new interface via the Special Protocols page renders those ReadMe's quite unnecessary, confusing and useless.

I didn't do anything but copy them in. I found those REALLY HELPFUL when trying to write the extender, but yeah from the user point of view they are obsolete and confusing. Anything you want to write, or take from unclemilties documentation is fine with me. I want this to be useable. I find that your writing is very clear and straight forward. It wasn't that long ago that you helped me start using extenders. Your extender sticky was extremely valuable to me!

PLEASE stop making new ones - it takes an hour to re-build all of my SP functions, Macros and Keymoves every time!

I'm hoping I'm done!

It takes me more than an hour to pack up a zip file and I've had to do 2. One for the Atlas and one for the URC8820 with each change. I have 15 bullets on my check list with lots of subpoints. Since I have no attention span, and no attention to detail, this process kills me! Believe me I'm not making anymore changes unless someone finds a bug. I'm thinking this is pretty well beaten to death. I never would have discovered the speed issues on my own. Since I always to X_ and X_cancel together, I never would have discovered that flaw. And since my registers were always the right settings, I never would have discovered that pause bug. I haven't seen anything out of the ordinary. I think its solid.

Your and underquark's testing has been a great help. I think these are both ready to go!

Evan_s · Post by **Evan_s** » Sun Sep 09, 2007 11:35 am

This probably isn't specific to the 1025 extender but since it's my first try at an extender I'm not really sure =)

I'm trying to setup a LKP on 2 of my devices (DVD and CABLE). The normal press is just going to change the correct groups to that device (ie simulate default behavior on a normal remote) the LKP is going to do my macro to switch tv, receiver etc to the correct inputs all with one key press. Obviously I want this behavior to be the same across what ever device I have selected so I tried just leaving the Device Field blank but it won't let me do that.

What is the best way to setup the remote to do this LKP on this button no matter what combination the remote happens to be for the device setup? I assume that the device buttons fall into the "Other" category since nothing else would make sense.

underquark · Post by **underquark** » Sun Sep 09, 2007 12:33 pm

Is this file of any help? It's set up for the 8820 but I hope it illustrates the point. Set up a macro on the device key to allocate all the keysets. Last step of this macro calls the LKP. Think of the LKP as a fork in the road with no return. Go left (short press) and nothing new happens; go right (long press) and another macro is called which temporarily selects, say, the TV and sets up the inputs and then cancels the TV leaving you with the correct input selected and the correct device mode set up.

Capn Trips · Post by **Capn Trips** » Sun Sep 09, 2007 1:02 pm

Evan, UQ's answer is right. One of the "limitations" if you will of D/LKPs is that they are device-specific, so to make them work in a global macro I build the LKP on a phantom or shifted button somewhere (let's say your DVD setup LKP is built on DVD/xshift-phantom3), and then build a macro on DVD=DEV_DVD,xshift-phantom3 (or X_DVD, xshift-phantom3 - I'm not sure what device selection technique your extender uses).