Graham,
I think the F12x entry in Protocols.ini contains a small error.
Code: Select all
PID=01 6D
DevParms=Device:3=0,Subdevice:1=0,OBC2:8=1
DeviceTranslator=Translator(lsb,0,3,0) Translator(1,1,3) Translator(lsb,2,8,4)
CmdParms=OBC1:8=0
CmdTranslator=Translator(lsb)
FixedData=08 00
Notes=This is an extended and slightly modified version of the F12 protocol. The modification is that the lead-out gap \
between frames is only one-fifth of that of the F12 protocol. There are two extensions. The first is that the Subdevice \
value, which is either 0 or 1, needs to be specified explicitly, while in the F12 protocol it is calculated from the other \
parameters. The other extension is that there are two OBC values. The first frame and its repeats are sent with OBC1 \
given as a command parameter, but there is a final frame sent on key release with OBC2 given as a device parameter, \
which is therefore the same for all signals.
I think
Code: Select all
DeviceTranslator=Translator(lsb,0,3,0) Translator(1,1,3) Translator(lsb,2,8,4)
will never fill in the second byte of the fixed data, and it will always have the value 0, even though the default for OBC2 is 1. Instead, I think it should be
Code: Select all
DeviceTranslator=Translator(lsb,0,3,0) Translator(1,1,3) Translator(lsb,2,8,8)
BTW, the learned signals in
https://hifi-remote.com/forums/viewtopic ... 714#p146714 decode as F12x, but apparently don't actually contain a different last command, so probably this decode is triggered by the short lead-out time. I suspect F12x will still work in this situation, and the fan will just ignore the last command byte of 0.