The Robman: 1 revision imported

2025-11-02T18:52:25Z

1 revision imported

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

The Robman: Created page with "===RC5x=== UEI protocol: 00F2 IRP notation: {36k,msb,889}<1,-1|-1,1>(1:1,~S:1:6,T:1,D:5,-4,S:6,F:6,^114m)+ EFC translation: NONE The official (UEI) protocol executor fo..."

2014-09-29T13:49:38Z

Created page with "===RC5x=== UEI protocol: 00F2 IRP notation: {36k,msb,889}<1,-1|-1,1>(1:1,~S:1:6,T:1,D:5,-4,S:6,F:6,^114m)+ EFC translation: NONE The official (UEI) protocol executor fo..."

New page

===[[RC5x]]===
UEI protocol: 00F2
IRP notation: {36k,msb,889}<1,-1|-1,1>(1:1,~S:1:6,T:1,D:5,-4,S:6,F:6,^114m)+
EFC translation: NONE
The official (UEI) protocol executor for RC5x 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 subdevice number.

In the functions sheet in KM you must put the subdevice number in the byte2 column, which KM calls "unit code".

What we call "Device" is really the "System". What we call Subdevice is really the "Command". What we call "OBC" is really the "Data". If you are using ProntoEdit to create the [[RC5]] signals directly, that GUI uses that correct (System, Command and Data) Philips terminology.

RC5x - Revision history

The Robman: 1 revision imported

The Robman: Created page with "===RC5x=== UEI protocol: 00F2 IRP notation: {36k,msb,889}<1,-1|-1,1>(1:1,~S:1:6,T:1,D:5,-4,S:6,F:6,^114m)+ EFC translation: NONE The official (UEI) protocol executor fo..."