I got all of the EFCs and the Protocol ID (RECS80, device 5) from IR using
the learning keys of the 8800.
KM does not list this Protocol ID, please help.
RECS80
Moderator: Moderators
You could use Remote Master instead of KM. It has support for two versions of RECS80 (UEI protocols 0045 and 0068).
The Readme_DecodeIR.txt file gives some hints on figuring out which version of RECS80 is a better fit for your learned signals.
If you must use KM rather than RM, you can directly specify the pid (once you decide whether its 0045 or 0068) instead of specifying "RECS80".
When you directly specify the pid, only EFC values from the decode should work for pid 0045, but I don't think either EFC or OBC are right for 0068. I may have time to investigate further later.
The Readme_DecodeIR.txt file gives some hints on figuring out which version of RECS80 is a better fit for your learned signals.
If you must use KM rather than RM, you can directly specify the pid (once you decide whether its 0045 or 0068) instead of specifying "RECS80".
When you directly specify the pid, only EFC values from the decode should work for pid 0045, but I don't think either EFC or OBC are right for 0068. I may have time to investigate further later.
RM computes fixed data of 40 for the device number of 5 and I think RM is correct.
KM for pid:0045 does not know how to translate from device number to fixed data. You can force a fixed data value of 40 by puting 40h in the Dev/Parm1 field.
The European models of OFA remote have a few cable tuner setup codes that are pid:0045 with fixed data of 40, so I think that is the likely correct combination for your sat receiver.
KM for pid:0045 does not know how to translate from device number to fixed data. You can force a fixed data value of 40 by puting 40h in the Dev/Parm1 field.
The European models of OFA remote have a few cable tuner setup codes that are pid:0045 with fixed data of 40, so I think that is the likely correct combination for your sat receiver.