RemoteMaster refuses to show the "Output" tab
Posted: Sat Jan 15, 2005 5:35 am
Along the route to the present RDF for the URC-7501-B01 I often got into this situation with two-byte protocols, but now I'm seeing it with the simple Mitsubishi protocol.
Here's the upgrade file I have. Clicking on the "Output" tab shows either the previously-selected tab or else a complete blank (i.e. without the windows that show the output code). I guess this is RM's way of saying "I can't produce an output with what you have fed me".
But it made an exactly equivalent upgrade successfully for my 7544, so I have to assume that RM (v1.12 or 1.13) takes exception (rightly or wrongly) to something in the 7562 RDF (note that this is the B01 one posted in the RDF files section, not one from the published collection).
I'd be really grateful if anyone could confirm whether this is a remaining problem with the RDF, or a problem in RM.
Clues so far: If I undefine all the buttons and start from scratch, it seems to be the "2" key that starts the problem. And the function codes for the number keys aren't in a totally obvious sequence. I was trying to work out how the number keys are represented in the upgrade code - I can see they aren't just listed in successive bytes like the later keys.
many thanks
Andy
Here's the upgrade file I have. Clicking on the "Output" tab shows either the previously-selected tab or else a complete blank (i.e. without the windows that show the output code). I guess this is RM's way of saying "I can't produce an output with what you have fed me".
But it made an exactly equivalent upgrade successfully for my 7544, so I have to assume that RM (v1.12 or 1.13) takes exception (rightly or wrongly) to something in the 7562 RDF (note that this is the B01 one posted in the RDF files section, not one from the published collection).
I'd be really grateful if anyone could confirm whether this is a remaining problem with the RDF, or a problem in RM.
Clues so far: If I undefine all the buttons and start from scratch, it seems to be the "2" key that starts the problem. And the function codes for the number keys aren't in a totally obvious sequence. I was trying to work out how the number keys are represented in the upgrade code - I can see they aren't just listed in successive bytes like the later keys.
many thanks
Andy