MCE entry added to protocols.ini for RM
Posted: Mon Feb 21, 2005 12:35 pm
I just added an entry for MCE (generates the same output as RC6-6-32 but with input compatible to the new DecodeIr).
I commited that at SourceForge (which said the commit worked, but the auto email notification to Greg failed). I assume Greg will include it in the next RM release (even if he doesn't get that email).
Meanwhile, if anyone wants it, you can use this protocols.ini with the current (or earlier) version of RM.
I left the RC6-6-32 entry in protocols.ini unchanged for now, so it could be used with decodes from the older DecodeIr. The actual protocol executor those both use supports a wider range of RC6-M-32 signals. At some point I should add more input fields to that protocols.ini entry so it supports all the options in that protocol executor's fixed data. For now, I've never heard of any RC6-M-32 signals other than MCE (if you find any be sure to inform me).
I commited that at SourceForge (which said the commit worked, but the auto email notification to Greg failed). I assume Greg will include it in the next RM release (even if he doesn't get that email).
Meanwhile, if anyone wants it, you can use this protocols.ini with the current (or earlier) version of RM.
I left the RC6-6-32 entry in protocols.ini unchanged for now, so it could be used with decodes from the older DecodeIr. The actual protocol executor those both use supports a wider range of RC6-M-32 signals. At some point I should add more input fields to that protocols.ini entry so it supports all the options in that protocol executor's fixed data. For now, I've never heard of any RC6-M-32 signals other than MCE (if you find any be sure to inform me).