Single device with some buttons having different protocol?
Posted: Fri Feb 10, 2006 9:47 pm
I have a question about how to create a device update
when some of the original device remote's buttons use
a different protocol than the other buttons. I can't
see any way in key-master to have some buttons use a
different protocol than the others.
I am creating a device upgrade for JVC HR-XVC18BUS
DVD/VCR Combo. This uses protocol NEC1, Device 110,
and <nothing> for SubDevice. Most of the buttons
are as shown in the example below:
Button Protocol Device SubDevice EFC
TV/Video NEC1 110 <nothing> 120
However, some of the buttons I want to map use a different
protocol and even a different set of values for Device and
SubDevice as shown below:
Button Protocol Device SubDevice EFC
Disc Menu NECx1 45 45 043
Select DVD NECx1 45 45 145
I could not figure how to deal the different protocol and
device settings for these two buttons I needed, so I just
learned these two buttons from the original remote after I
created the device upgrade in KM and IR. This works OK,
but involves a manual step after the device upgrade is
created.
Is there a better way?
Thank you,
Tom Freeland
when some of the original device remote's buttons use
a different protocol than the other buttons. I can't
see any way in key-master to have some buttons use a
different protocol than the others.
I am creating a device upgrade for JVC HR-XVC18BUS
DVD/VCR Combo. This uses protocol NEC1, Device 110,
and <nothing> for SubDevice. Most of the buttons
are as shown in the example below:
Button Protocol Device SubDevice EFC
TV/Video NEC1 110 <nothing> 120
However, some of the buttons I want to map use a different
protocol and even a different set of values for Device and
SubDevice as shown below:
Button Protocol Device SubDevice EFC
Disc Menu NECx1 45 45 043
Select DVD NECx1 45 45 145
I could not figure how to deal the different protocol and
device settings for these two buttons I needed, so I just
learned these two buttons from the original remote after I
created the device upgrade in KM and IR. This works OK,
but involves a manual step after the device upgrade is
created.
Is there a better way?
Thank you,
Tom Freeland