The Robman: 1 revision imported

2025-11-02T18:41:17Z

1 revision imported

← Older revision	Revision as of 18:41, 2 November 2025
(No difference)

The Robman: Created page with "===JVC and JVC{2}=== UEI protocol: 0034 IRP notation: {38k,525}<1,-1|1,-3>(16,-8,(D:8,F:8,1,-45)+) EFC translation: LSB comp JVC{2} indicates a JVC signal ..."

2014-09-28T00:16:49Z

Created page with "===JVC and JVC{2}=== UEI protocol: 0034 IRP notation: {38k,525}<1,-1|1,-3>(16,-8,(D:8,F:8,1,-45)+) EFC translation: LSB comp JVC{2} indicates a JVC signal ..."

New page

===[[JVC and JVC2|JVC and JVC{2}]]===
UEI protocol: 0034
IRP notation: {38k,525}<1,-1|1,-3>(16,-8,(D:8,F:8,1,-45)+)
EFC translation: LSB comp
JVC{2} indicates a JVC signal from which the lead-in is missing. The JVC protocol has lead-in on only the first frame, so it is quite easy to have it missing from a learned signal. So when JVC{2} is correct, it means the same as JVC. But JVC{2} is not robust, so spurious decodes are likely. It is also very similar in structure and timing to Mitsubishi protocol, so that DecodeIr has difficulty distinguishing one from the other. The device number, OBC and EFC are all encoded the same way between the two. So if you have JVC{2} decodes that you have reason to suspect should actually be Mitsubishi, you can try using them as [[Mitsubishi]] without changing the numbers. However, true [[Mitsubishi]] signals will not misdecode as JVC, just as JVC{2}. So if some of the signals for your device decode as JVC and others as JVC{2}, you should trust all those decodes and not try [[Mitsubishi]].

JVC and JVC2 - Revision history

The Robman: 1 revision imported

The Robman: Created page with "===JVC and JVC{2}=== UEI protocol: 0034 IRP notation: {38k,525}<1,-1|1,-3>(16,-8,(D:8,F:8,1,-45)+) EFC translation: LSB comp JVC{2} indicates a JVC signal ..."