rdf for OneForAll 7562 chipcode B01 sig EM60EM60 help

[Andy]

I just made one more small change to the RDF, to change the image map to:

Code: Select all

ImageMap=URC-7562.map

Which is the correct picture and also avoids a small problem on the "AV" button of the image map for URC-7560.

At the moment I'm struggling to get RM to produce an output for an upgrade to a Mitsubishi device. I don't know if this is a problem with the RDF or a bug in RM. I'll post the details on the software board.

[Andy]

Many thanks to Greg for instantly accommodating one of Rob's undocumented bits of nomenclature in the v1.14 release of RM. Thanks to Rob too for stepping in and explaining what had gone on.

Now I was able to make the upgrade that I had been stuck on. It happened to be the first upgrade I had made using the "VCR/DVD" device code, and it came up with all the buttons in the wrong places. Putting it on "TV" or "CD/Audio" gave a good result, though.

So it was fairly obvious what had gone on. Somewhere in history the [DeviceTypes] section had changed from:

Code: Select all

[DeviceTypes]
TV        = 0
Sat/Cable = 1
VCR/DVD   = 2
CD/Audio  = 3

to:

Code: Select all

[DeviceTypes]
TV        = 0
Sat/Cable = 2
VCR/DVD   = 1
CD/Audio  = 3

A very subtle change but one which apparently should have been accompanied by a change in the [ButtonMaps] section from:

Code: Select all

[ButtonMaps]
0 = ($1F, $15, $16, $17, $19, $1A, $1B, $1C, $1D, $1E), ($04, $05, $08), ($06, $07),
    $03, $18, $2F, $20, $29, $2A, $2B, $2C, $C8, $D8, $86, $87, $84, $85, $0C, $0B, $14, $0E, $10, $13, $0D, $0F, $83, $23, $24, $25, $26, $27, $28, $2D, $2E
1 = ($1F, $15, $16, $17, $19, $1A, $1B, $1C, $1D, $1E), ($04, $05, $08), ($06, $07),
    $03, $C8, $2F, $18, $20, $29, $2A, $2B, $2C, $D8, $0B, $0C, $0F, $0D, $14, $0E, $10, $13, $83, $23, $24, $25, $26, $27, $28, $2D, $2E
2= ($1F, $15, $16, $17, $19, $1A, $1B, $1C, $1D, $1E), ($04, $05, $08), ($06, $07),
    $03, $0C, $0F, $0B, $0D, $0E, $10, $18, $C8, $20, $29, $2A, $2B, $2C, $D8, $2F, $14, $13, $23, $24, $25, $26, $27, $28, $2D, $2E
3 = ($1F, $15, $16, $17, $19, $1A, $1B, $1C, $1D, $1E), ($04, $05, $08), ($06, $07),
    $03, $2F, $18, $20, $0C, $0F, $0B, $0D, $0E, $10, $D8, $29, $2A, $2B, $2C, $C8, $14, $13, $83, $23, $24, $25, $26, $27, $28, $2D, $2E

to:

Code: Select all

[ButtonMaps]
0 = ($1F, $15, $16, $17, $19, $1A, $1B, $1C, $1D, $1E), ($04, $05, $08), ($06, $07),
    $03, $18, $2F, $20, $29, $2A, $2B, $2C, $C8, $D8, $86, $87, $84, $85, $0C, $0B, $14, $0E, $10, $13, $0D, $0F, $83, $23, $24, $25, $26, $27, $28, $2D, $2E
1 = ($1F, $15, $16, $17, $19, $1A, $1B, $1C, $1D, $1E), ($04, $05, $08), ($06, $07),
    $03, $0C, $0F, $0B, $0D, $0E, $10, $18, $C8, $20, $29, $2A, $2B, $2C, $D8, $2F, $14, $13, $23, $24, $25, $26, $27, $28, $2D, $2E
2 = ($1F, $15, $16, $17, $19, $1A, $1B, $1C, $1D, $1E), ($04, $05, $08), ($06, $07),
    $03, $C8, $2F, $18, $20, $29, $2A, $2B, $2C, $D8, $0B, $0C, $0F, $0D, $14, $0E, $10, $13, $83, $23, $24, $25, $26, $27, $28, $2D, $2E
3 = ($1F, $15, $16, $17, $19, $1A, $1B, $1C, $1D, $1E), ($04, $05, $08), ($06, $07),
    $03, $2F, $18, $20, $0C, $0F, $0B, $0D, $0E, $10, $D8, $29, $2A, $2B, $2C, $C8, $14, $13, $83, $23, $24, $25, $26, $27, $28, $2D, $2E

i.e. the button maps for codes 1 and 2 have been swapped. Apparently the order in the [DeviceTypes] section matters, hence the sequence 0, 2, 1, 3. But just renumbering the button maps (and leaving them in the 0, 2, 1, 3 order) produced some very strange results. I had to physically swap them to the 0, 1, 2, 3 order for it to work properly.

So here's the link to the latest version of the RDF.

Thanks to everyone who helped along the way !

Andy

[gfb107]

DeviceType and ButtonMap indexes are important. You can't just reorder them, because they are defined inside the remote itself.

The index of the DeviceType is implied by the order listed in the DeviceTypes section, but can be overridden.

I think you could have written:

Code: Select all

[DeviceTypes]
TV        = 0,0
Sat/Cable = 2,2
VCR/DVD   = 1,1
CD/Audio  = 3,3

[The Robman]

I can confirm that the 2nd set of both items is the correct one. Also, just to re-inforce what Greg said, these settings are hard coded into the remotes themselves, all we do when we create RDFs is reverse engineer them, we don't have any control over them.