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
RemoteMaster refuses to show the "Output" tab
Moderator: Moderators
The problem seems to be in the [DigitMaps] section. There are three instances of the value 999. None of these are valid. The greatest known digit map is 172.
BTW, when you get this sort of strange behavior in RM, to get a clue as to what is going on your should close RM and look at the rmaster.err file.
BTW, when you get this sort of strange behavior in RM, to get a clue as to what is going on your should close RM and look at the rmaster.err file.
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
-
The Robman
- Site Owner
- Posts: 21888
- Joined: Fri Aug 01, 2003 9:37 am
- Location: Chicago, IL
- Contact:
IIRC, the 999 entries are there as placeholders for digitmap entires that need to be added to the master file.
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
OK, so when searching for a DigitMap that matches the digits in a device upgrade, RM should just ignore entries with 999?
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
I've just released RM v1.14 which now gracefully ignores 999 entries in the DigitMaps
Last edited by gfb107 on Sat Jan 15, 2005 4:29 pm, edited 1 time in total.
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
-
The Robman
- Site Owner
- Posts: 21888
- Joined: Fri Aug 01, 2003 9:37 am
- Location: Chicago, IL
- Contact:
That's a good idea. I had simply used 999 for want of something better to use (it's certainly better than the non-numeric ???) but having RM recognize and ignore them is a good idea.
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
Thanks
Wow, that was quick ! Thanks Greg.
That upgrade now works well. Actually, if I'm honest it threw up a further small problem in the RDF. But I think I can guess what's going on. More over on the "rdf for OneForAll 7562 chipcode B01 sig EM60EM60 help" thread later.
That upgrade now works well. Actually, if I'm honest it threw up a further small problem in the RDF. But I think I can guess what's going on. More over on the "rdf for OneForAll 7562 chipcode B01 sig EM60EM60 help" thread later.