Atlas JP1.3 Extender beta - Topic CLOSED

greenough1 · Post by **greenough1** » Mon Nov 12, 2007 7:57 pm

Hi Capn,
My atlas 1056 has 1056BC1-BLX-XXX-0001-001-R under the battery cover, so it's nearly the same as yours. I've not tried the new extender version, but had some luck wiht the previous beta.

I just got home from work, need to get dinner and do some other tasks. Then I'll spend some time with the new extender version and my remote. Maybe 3 hours from now...

Best,
jeff

Capn Trips · Post by **Capn Trips** » Mon Nov 12, 2007 8:07 pm

1056BC1-BLS-XXX-0001-001-R (Silver backlit learner)
1056BC1-BLX-XXX-0001-001-R (Black backlit learner) and
1056BG1-XXX-XXX-0001-001-R (Black non-backlit non-learner)

All behave EXACTLY the same way!

I have a URC-1055 30003000 to which the extender uploads and activates properly and seemingly works. I've not done much testing, just converted the downloaded IR file with extinstall and re-uploaded it and activated the extender (got th 4 blinks) and tested to see if a few keys work.

I have NEVER gotten the extender in any of the pre-beta versions over the past few months to activate in any of my OCAPs.

greenough1 · Post by **greenough1** » Mon Nov 12, 2007 8:45 pm

The previous version (the one before this version) would load and I could activate it in my remote. LDKP and Pause were broken (Unclemiltie fixed the later). Keyset selection worked and DSM worked.

Again, I need a couple of hours and I'll take a look.
Best,
jeff

greenough1 · Post by **greenough1** » Tue Nov 13, 2007 12:19 am

Ok. The new version will not activate in my 1056 remote (3033).
I've uploaded my v0.1 that you could download and test. Get it here

To activate it, press TV+OK. I've keymoved the de-activate to TV+FAV.

I'll take a look and compare back with the previous version to see if I can see why it won't activate.

Best,
jeff

unclemiltie · Post by **unclemiltie** » Tue Nov 13, 2007 12:24 am

all right, I now see that this will not deactivate on my 1056 OCAP (Silver, learner) I get the same symptoms as Cap'n.

I'm going to have to look into this. Meanwhile, keep playing with the 30003000 remotes.

greenough1 · Post by **greenough1** » Tue Nov 13, 2007 12:55 am

Where is ee_start defined? There's an offset of 1E between the two extenders at the top of the extender main.

Capn Trips · Post by **Capn Trips** » Tue Nov 13, 2007 11:35 am

unclemiltie wrote:all right, I now see that this will not deactivate on my 1056 OCAP (Silver, learner) I get the same symptoms as Cap'n.

Finally, somebody believes me!

greenough1 · Post by **greenough1** » Tue Nov 13, 2007 11:46 am

Didn't I just post above also that I couldn't activate the extender in my 1056 remote also? I believe you too!

Capn, did you try and upload, activate then deactivate the version I uploaded and linked?

jeff

Capn Trips · Post by **Capn Trips** » Tue Nov 13, 2007 2:20 pm

Not yet. Last night was too late. Today, working - not home yet. I suspect the rdf's have something to do with these difficulties, as well. I will shortly document what I perceive as problems that have to be rdf-related in RM.

greenough1 · Post by **greenough1** » Tue Nov 13, 2007 2:37 pm

I tried to manually "diff" the rdf's and could find no differences, but I might have missed something. (can anyone recommend a good windows tool set for diff'ing?)

I haven't fully gotten up to speed on the extender source, but did see, looking at the listing (asm processed source) that the entries between the old and the new version was off by 1E, and I don't know where ee_start is defined, which is the probably causing the offset.

I even tried to rebuild the new extender (probably we should call it v0.2 and the old one v0.1?) with all the debugging flags on and the default macros and the offset persisted and the inability to activate was present.

jeff

Capn Trips · Post by **Capn Trips** » Tue Nov 13, 2007 5:03 pm

In addition to the fact that I cannot actually test the extender in a remote, there are software-interface issues that are present, that are annoying/disconcerting at the very least, and perhaps may contribute to the other problems being seen at the worst. So in an effort to document what I have seen in RM and IR, here is my list to date.

Atlas URC-1056 (OCAP) remote extender comments:

(1) need to modify the extender rdf name to have an underscore between (Black) and (Silver): allows for separate line items in the RM dropdown remote lists
a. current: 3A333A33 (Atlas OCAP URC-1056 JP1.3 (Black) (Silver) extender).rdf;
b. correct: 3A333A33 (Atlas OCAP URC-1056 JP1.3 (Black)_(Silver) extender).rdf

(2) Some device types appear twice in the “Device Type” dropdown list on all pages in RM;
a. In the [DeviceTypeAliases] section of the RDF I would delete the last line:
Code: Select all
```
VCR      = VCR,DVD,Tape,Laserdisc,DAT
```
to correct this. The [DeviceType] section already identifies the VCR Device Type as a type 2, which maps it to the DVD entry, which is:
Code: Select all
```
DVD      = VCR,DVD,Tape,Laserdisc,DAT
```
so I'm pretty sure that VCR entry is unnecessary.

(3) Questions/inconsistencies with “Buttons”:
a. “ButtonF1” appears on the “Buttons” sheet in RM, but NOT on the “Layout” sheet (as distinguished from “F1” which is fine). Should it appear as a phantom below the remote image? How do we get it to do that? Alternatively, how do get it to NOT appear on the "Buttons" sheet;
b. “DiscreteOff” appears on the “Buttons” sheet in RM, but NOT on the “Layout” sheet (just like “ButtonF1);
c. “DeActivate” appears on the “Buttons” sheet in RM, but NOT on the “Layout” sheet;
d. “DiscreteOn” appears both on the “Buttons” sheet in RM as well as on the “Layout” sheet (in the phantom buttons section).
NOTE 1: Oddly, “DiscreteOn” and "ButtonF1" appear within the buttonmap for CBL device type (no asterisk); I would suggest that "DiscreteOn" and "DiscreteOff" should behave the same and "ButtonF1" should be somehow hidden in RM - if it's present in the buttonmap but useless.
NOTE 2: “DiscreteOn”, “DiscreteOff” and “DeActivate” all appear in IR as available buttons.
Code: Select all
```
Button	RM’s “Buttons” sheet	RM’s “Layout” sheet	   IR       RM's CBL ButtonMap
ButtonF1	     Yes	                  No	           No               Yes
DiscreteOn	   Yes	                 Yes	           Yes              Yes
DiscreteOff     Yes	                  No	           Yes               No
DeActivate      Yes	                  No	           Yes               No
```
(4) X-shifted capability is NOT available in RM nor IR:
a. No “xshift” column available on the “Buttons” sheet;
b. “xshift” selection is greyed-out on the “Layout” sheet;
c. In IR.exe, no “xshift”-ed selections are available in Keymoves, Macros, or Special Protocols “Add” pop-up windows.

Mark Pierson · Post by **Mark Pierson** » Tue Nov 13, 2007 5:51 pm

Capn Trips wrote:(3) Questions/inconsistencies with “Buttons”:
a. “ButtonF1” appears on the “Buttons” sheet in RM, but NOT on the “Layout” sheet (as distinguished from “F1” which is fine). Should it appear as a phantom below the remote image? How do we get it to do that? Alternatively, how do get it to NOT appear on the "Buttons" sheet;
b. “DiscreteOff” appears on the “Buttons” sheet in RM, but NOT on the “Layout” sheet (just like “ButtonF1);
c. “DeActivate” appears on the “Buttons” sheet in RM, but NOT on the “Layout” sheet;
d. “DiscreteOn” appears both on the “Buttons” sheet in RM as well as on the “Layout” sheet (in the phantom buttons section).
NOTE 1: Oddly, “DiscreteOn” and "ButtonF1" appear within the buttonmap for CBL device type (no asterisk); I would suggest that "DiscreteOn" and "DiscreteOff" should behave the same and "ButtonF1" should be somehow hidden in RM - if it's present in the buttonmap but useless.
NOTE 2: “DiscreteOn”, “DiscreteOff” and “DeActivate” all appear in IR as available buttons.
Code: Select all
Button	RM’s “Buttons” sheet	RM’s “Layout” sheet	   IR       RM's CBL ButtonMap
ButtonF1	     Yes	                  No	           No               Yes
DiscreteOn	   Yes	                 Yes	           Yes              Yes
DiscreteOff     Yes	                  No	           Yes               No
DeActivate      Yes	                  No	           Yes               No

The "ButtonF1" issue has to do with the fact that it's referenced in the CBL device keymap. KM/RM have to allow for it due to the way functions are bound to buttons positionally based on the key map.

It's not on the Layout tab because there's no physical button on the remote. It's not in the [Buttons] section of the RDF, so it doesn't appear as a phantom either. This keeps it off the Buttons tab as well.

The issue with the other three buttons seem to be connected to the fact that they are listed is the RDF as:

DeActivate=$C6:XShiftBind
DiscreteOn=$40:ShiftBind
DiscreteOff=$80:XShiftBind

"DeActivate" and "DiscreteOff" are XShiftBind while "DiscreteOn" is ShiftBind.

Unfortunately, I'm not up to date on what all the binding options are in an RDF, so I'm not sure what the fix is.

Capn Trips · Post by **Capn Trips** » Tue Nov 13, 2007 9:15 pm

greenough1 wrote:Didn't I just post above also that I couldn't activate the extender in my 1056 remote also? I believe you too!

Capn, did you try and upload, activate then deactivate the version I uploaded and linked?

jeff

No testing time tonight, but I uploaded the linked IR image and it seems to correctly activate and deactivate.

A first for my OCAPs!

But that is the extent of my testing for tonight. I have not explored anything within IR, nor tried to add any of my upgrades, special functions, etc.

But since I used the same rdf as with Bill's latest extender distro, it appears to be something in the extender itself, rather than in the rdf, right?

(although I still think there is work to be done with the rdf, as outlined a few posts above)

greenough1 · Post by **greenough1** » Tue Nov 13, 2007 9:33 pm

Capn Trips wrote:No testing time tonight, but I uploaded the linked IR image and it seems to correctly activate and deactivate. A first for my OCAPs!

I knew it would activate and deactivate!

I see Bill's fix to Pause in v0.2, so I'll add that to v0.1 and see if that fixes it.

I wouldn't do too much more testing with that version. Bill says the LDKP is broken. DSM seems to work and keyset selection. That's about as far as I got.

Capn Trips wrote: But since I used the same rdf as with Bill's latest extender distro, it appears to be something in the extender itself, rather than in the rdf, right?

(although I still think there is work to be done with the rdf, as outlined a few posts above)

Right, I'm thinking like you the issues are in the extender code, not the rdf. More testing and debugging...

Best,
jeff

unclemiltie · Post by **unclemiltie** » Tue Nov 13, 2007 11:31 pm

Cap'n

I think I found the issue with the OCAP activation. The "activate" protocol was never executing because some of the data after the setup area in the E2 area wasn't "right"

I have a new version that puts the "correct" data in there by default in the extender build. Until I understand it (it has something to do with multimacro) we'll have to live with the data in the extender source.

Anyway, I just was able to activate and deactivate the extender on my silver URC-1056 OCAP (1056BG1) so this should help you.

I've updated the original file on the download section. The only real difference is the ASM source.

All else:

I realize that there are issues with the RDF, so please keep the comments coming.

-bill