G.I.4DTV - Revision history

Administrator: 2 Versionen importiert

2025-09-28T12:26:12Z

2 Versionen importiert

← Older revision	Revision as of 13:26, 28 September 2025
(No difference)

imported>The Robman: /* G.I.4DTV */

2014-10-05T18:33:57Z

G.I.4DTV

← Older revision		Revision as of 19:33, 5 October 2014
Line 4:		Line 4:
	EFC translation: NONE		EFC translation: NONE
	This is a moderately robust protocol, but [[Spurious decodes and non-robust protocols\|spurious decodes]] are still possible.		This is a moderately robust protocol, but [[Spurious decodes and non-robust protocols\|spurious decodes]] are still possible.

			Unit (device) numbers from 0 to 7 are supported. The check sum C is a [https://en.wikipedia.org/wiki/Hamming_code Hamming Code], which can correct single bit errors. D:1:2 is encoded in the check sum. [[D encoding scheme]]

	The official (UEI) protocol executor for G.I.4DTV does not support EFC numbers. If you are creating an upgrade in KM or RM you should use OBC numbers, not EFC numbers. If you need the Hex Cmd for a KeyMove, you should use the functions sheet of KM or RM to compute it for you from the OBC and device number.		The official (UEI) protocol executor for G.I.4DTV does not support EFC numbers. If you are creating an upgrade in KM or RM you should use OBC numbers, not EFC numbers. If you need the Hex Cmd for a KeyMove, you should use the functions sheet of KM or RM to compute it for you from the OBC and device number.

	[[Category:DecodeIR]]		[[Category:DecodeIR]]

imported>The Robman: Created page with "=G.I.4DTV= UEI protocol: 00A4 IRP notation: {37.3k,992}<1,-1|1,-3>(5,-2,F:6,D:2,C:4,1,-60)+ EFC translation: NONE This is a moderately robust protocol, but [[Spurious d..."

2014-09-28T00:14:27Z

Created page with "=G.I.4DTV= UEI protocol: 00A4 IRP notation: {37.3k,992}<1,-1|1,-3>(5,-2,F:6,D:2,C:4,1,-60)+ EFC translation: NONE This is a moderately robust protocol, but [[Spurious d..."

New page

=[[G.I.4DTV]]=
UEI protocol: 00A4
IRP notation: {37.3k,992}<1,-1|1,-3>(5,-2,F:6,D:2,C:4,1,-60)+
EFC translation: NONE
This is a moderately robust protocol, but [[Spurious decodes and non-robust protocols|spurious decodes]] are still possible.

The official (UEI) protocol executor for G.I.4DTV does not support EFC numbers. If you are creating an upgrade in KM or RM you should use OBC numbers, not EFC numbers. If you need the Hex Cmd for a KeyMove, you should use the functions sheet of KM or RM to compute it for you from the OBC and device number.
[[Category:DecodeIR]]