JP1 Remotes

I put the $F1 in the RDF. I added a phantom4=$71 entry into the RDF and IR7 does display it as Shifted-phantom4 in the device upgrade button list. However, I can't get RM to display it. RM displays as ButtonF1 and has a column for Function and Shift so it looks like it is treating it as a regular button. If I add phantom5=$F1, RM is not treating it like a regular button. I'm not sure what else to do though.

You won't have to split the DeviceTypes up with one being VCR and the other being DVD in order to get VCR/DVD in the drop-down lists. When IR7 sees a duplicate like VCR/DVD, it won't add that entry into the list.

OK, looks like I'll have to give it a try. Where can I get the best version of this RDF?

AFAIK there are only 2 30333033 rdf's currently:

One 30333033 rdf is in the current rdf distro file. I guess it was built by binky for the FOURTH variant of the Atlas URC-1055.

The second one is the mod of the first I tried to make (linked in the first post of this thread) in which I attempted to modify that previous one for the Atlas OCAP URC 1056. It basically required re-naming some buttons. I tried to make some "cosmetic" changes for RM readability, as well. That's the one which I apparently screwed up.

I'm waiting for Binky's version of the OCAP 30333033 rdf .

The latest 30333033 RDF is here at https://www.hifi-remote.com/forums/dload ... le_id=4502

Capn can post his OCAP specific version when he's finished with it.

One more question, binky, the 30333033 RDF in the distribution zip has this entrywhereas your new one does not. In fairness, I somehow removed that line also when I tried to tailor the rdf for the OCAP remote )

Is the new one correct in this regard? (and if so, is it possible for me to comprehend why?)

I was wrong. Button $F1 is not a shifted button, although it is an unshiftable button. In RM, unless otherwise specified in the RDF to match the behavior of the remote, shifted buttons have button codes in the range $80..$BF. Shiftable buttons have button codes in the range $00-$3F.

HERE is the updated rdf.

It works, so long as one DOWNLOADS FROM the remote first. If you simply go to IR's File>New>Select dropdown and select this rdf and build your tailored IR file from scratch, and upload it, no buttons work.

If you DOWNLOAD from the remote first (after a 981 reset), then it selects this same rdf, and after adding upgrades and personalising the setup and uploading it back to the remote, everything works like a charm - so far.

I've looked at the Raw Data tabs and the difference is at addresses 0800-0803. The NON-working file (built from scratch) has:
01 FE 53 52
whilst the WORKING one (downloaded and modified) has:
00 FF FF FF

I guess there's a fixed data thing somewhere that's goofy.

How do force those values into IR via the rdf?

To add what Greg has said

the button maps are stored deep in the remote in the order that must match the RDF. The reason it must match is that when the remote is interpreting the key bitmap for upgrades it works through this list in order. So if you remove one, all of the buttons after that will be scrambled.

As for the $F1, it is in there. It's an usual key value since ALL of the Samsung-processor based remotes that I've seen have never had a key value of greater than $3F (except the remapped values in the Kameleon's but that's another topic for another day)


-bill

I removed the [FixedData] section because that area 0800-09FF(RDF $0200-03FF) seemed to vary between cable companies. On the Atlas5 30333033, the first two bytes are a checksum follwed by $53 $52 and then a 4 byte number and then the E2 Settings+KMM area from 0608-07FF.

binky123 wrote:I removed the [FixedData] section because that area 0800-09FF(RDF $0200-03FF) seemed to vary between cable companies. On the Atlas5 30333033, the first two bytes are a checksum follwed by $53 $52 and then a 4 byte number and then the E2 Settings+KMM area from 0608-07FF.

OK, so may I conclude that this condition forces a requirement/limitation where one cannot reliably build an upgrade from scratch (File>New), but should ALWAYS start with a download from the remote, to get the correct data populating those fields?

Yes, I think that is the case. There are some SETUP commands that can copy the Settings+KeyMoveMacro area(0608+) over to (0808+). Whether
that is sufficient to build a correct private area, I don't know.

Another reason to use your initial download as the base is the Settings area bits may have some significance which isn't reflected in the RDF(i.e. the Standard or Alternate KeyMap).

I have updated the rdf, maps and images to include both versions of the Atlas OCAP remote, the Black (URC-1056) and the Silver (URC-1056BC).

Again I offer two choices of map/image sizes. Only put ONE of the two sets in your images folder.

Nils, I recommend the "Normal" folder files for your ultimate future update of the Maps and Images zip file.

Gee! I was on a cruise for a month and missed this entire discussion.I have been thru all this a number of times, and this discussion is a great help in understanding/ working the issue....