Pronto IR Formats

Pronto IR Formats

Preamble

This article describes in detail the formats of IR code filing for Pronto and ProntoPro models (RU-890, RU-940, RU-970, TS-1000, TSU-2000, TSU-6000, RC-5000, RC-5000i, RC-5200, RC-9200, RAV-2000, USR-5). It is supposed to be interesting for:

• those, who want to clean up his IR codes — in order to find out what all the numbers in field “IR code:” mean and for troubleshooting;
• those, who want to develop an IR code converter into other driver/configuration formats — Crestron (.IR), AMX (.IRL), Xantech (.PAL), Niles (.LIN), ADI Ocelot (.LIR), RedRat2 (.TXT), Denon RC-8000 (.RCX), ProntoNeo (.NCF), ProntoNG (.PCF) etc, as a manual of most popular and complicated IMHO IR code format.

It is advisable for you to have a notion of modulated IR signals transmission [1], but I will also coin that terms for completeness. References to some concepts can be earlier than the description of theirs, so as not to touch on same concept doubly. I am not going to mention the details of realization which is not essential for the description of the format.

Acknowledgments

I would like to thank Daniel Tonks, Stewart Allen, Barry Gordon, Marcel Majoor, Steven Keyser, Bertrand Gillis, Loran Richardson, Bernard Barrier, Barry Shaw, Rob Crowe, Andrea Whitlock, those, who reply at forums — for help and support, my wife — for indulgence and star50fiveoh — for sober intolerance to this article's subject :)

Warning

Standard warning about “… your own risk” is in effect.

Buttons, signals, commands and codes

In order to avoid involving in terms, I specify them precisely:

Figure placeholder: Picture 1 — Interaction of buttons, IR signals, commands and IR codes

The button, IR signal, command and IR code are not corresponding mutually:

• the same button can produce different IR signals (see Toggle Codes);
• different IR signals can be recognized by decoder as same command (see Clean and Dirty Codes);
• the same IR signal can be encoded as a number of IR codes in different formats.

Modulated IR signal

For some reasons, mainly for simplicity and interference immunity, almost all IR signals, currently used to IR translation, have the same structure. IR transmitter includes a square-wave generator (oscillator), coder and IR LED. All the time of transfer oscillator generates square impulses with fixed (for this remote) carrier frequency; depending on pressed button (and, may be, remote mode), coder forms a code of command — sequence of conventional logical 0s and 1s; IR LED flashes this command modulated by generated impulses.

Figure placeholder: Picture 2 — IR LED replays modulated IR signal

Any modulated IR signal can be fully characterized via carrier frequency and the sequence of period amounts when emitting is on and off. For picture 2 this sequence is 6–2–4–2–4–…

Sometimes remote emits the signal all the time until the button such as VOLUME+ will released. Another way it flashes once per press, or first, once emitted signal is not the same that repeating one, followed it. So, it is convenient to suppose that in the general way IR signal consists of once part, the start emitting sequence and repeat part. For example, endless IR signal 6-2-4-2-4-6-6-3-3-12-6-3-3-12- has the once sequence 6-2-4-2-4-6 and repeat sequence 6-3-3-12: 6-2-4-2-4-6 | 6-3-3-12. All currently used IR signals can be represented either as a union of once and repeat sequences or as the only once or only repeating sequence.

Figure placeholder: Picture 3 — Cutting IR signal into once sequence and repeat sequence

Usually, IR codes, describing IR signal this way, are not so long. If learned IR code is not an air conditioner code, it can be completely go in “IR code:” field at ProntoEdit.

In the most of cases carrier frequencies are nearby 35KHz, but you will certainly be lucky enough to try a remote with 175KHz, 345KHz, 455KHz or 1.1MHz.

“Clean” and “dirty” codes

[1: “Unclean” and “clean” IR commands (Working With Prontoedit: Learning & Infrared)]

It is not necessary to replay IR signal precisely, IR receiver will “identify” received IR signal as correct command, if it looks like real command adequately, say, carrier frequency and burst pairs’s lengths differ from original IR signal less than for 10%. I.e. there is precise, original IR signal for every command, may be not replay-able for Pronto, and also many IR signals that Pronto can replay and IR receiver can recognize as that command. The codes of those signals may have different lengths, and the shortest one is “clean” code, and the all other codes are “dirty” and very “dirty”.

Reasons to prefer “clean” codes:

• IR signal of “clean” IR code is more recognizable by IR receiver
• some “dirty” IR codes can lead IR receiver astray or halt it
• “clean” code is shorter, and replay of it takes less time in macros
• you can visually check “clean” IR code’s accuracy — the lengths of every “clean” IR codes per remote are the same, except, may be, buttons like VOLUME+
• “clean” code is more convenient to analyzing, in order to guess a discrete command, absent at this remote
• using of “clean” IR codes stirs ambitions of punctual Prontoyers

The ordinal way to obtain “clean” IR code is cutting from existing one [1]. Sometimes it is useful to develop special software — generator of all concrete type IR codes — in order to “discover” all possible commands, supported by that device, including those absent at remotes.

Note: There is no difference in IR learning to Pronto standalone or to computer via Pronto, but sometimes this process is faulted due a communication error.

Toggle IR codes

[1: Why won’t my buttons work twice in a row? (Working With Prontoedit: Learning & Infrared)]

It is necessary not to mix up toggle IR codes and toggle IR commands. Toggle Command is a command with toggle function such as standby/on, see TOAD at [1]. In contrast to that, Toggle IR Code contains as minimal 1 toggle bit, see RC5 at [2].

There are many possible troubles and noises at IR transfer — sun, fluorescent lamps, interference with another IR transfer, dust, pets, household and tremor of hesitating hand, holding remote. First two troubles can be cured by signal modulation. Other problems, concerning temporary obstacle, are solved logically. Commonly they use two different IR signals per button — one for odd presses and another for even. As a rule, these codes differ in one or two logical bits (“toggle” bit or “parity”), and both of them encode the same command. When IR decoder receives IR signal such type, it ignores the same signals (or signals with the same “parity” bit) received twice, in order to avoid taking noise as double click.

Pronto IR learning procedure uses the only button pressing, and because of it Pronto can detect as toggle codes only codes of some predefined types, that look like known codes, for example, RC5. When Pronto replays these codes, it emits in turn odd and even IR signals for every type of predefined code format (and if existing, subformat). So repeating the same alias for “long button press” in macro is not effective for toggle codes; it is necessary to convert this code to format 0000 to do it.

If Pronto learns real toggle codes as ordinary, learn all codes in the same parity, and only the “blank” command (that does nothing, if it exists at remote) — in opposite parity, and give any Pronto button two actions — odd real command and even “blank” [1].

Pronto IR code filling formats

[1: Type of code (Working With Prontoedit: Learning & Infrared)]

IR codes are kept in Pronto and in CCFs in bytes (as all data), but Pronto software uses two-byte hexadecimal words delimited by spaces at IR code view (editBox): 0000 0070 0003 0002 0006 0002 0004 0002 0004 0006 0006 0003 0003 000C

I will write all sizes and offsets in 16-bit words and all numbers in hex, if not specified otherwise. First word — wFmtID — identifies IR format.

Supported formats:

• 0000 — raw oscillated code
• 0100 — raw unmodulated code
• 5000 — RC5
• 5001 — RC5x
• 6000 — RC6 Mode 0
• 7000 — predefined code of variable length
• 8000 — index to UDB
• 9000, 900A, 900B, 900C, 900D, 900E — NEC
• 9001 — basic mode YAMAHA NEC code

Figure placeholder: Picture 4 — hierarchy of Pronto IR formats

Raw formats (wFmtID = 0000 or 0100)

They are simple, basic, most commonly used formats. Almost all IR signals can be represented (exactly or cognitive) either in 0000 or 0100 format. There is no way to encode toggle IR codes at these formats, but separately, odd and even IR code can be converted from toggle form to 0000 format.

Raw oscillated code (wFmtID = 0000)

This is the format that is often implied, when they say “Pronto IR format”. It contains lengths while LED flashes and while LED is off in carrier periods (“burst pairs”) in two optional parts - once and repeat sequences.

For example, code from pic.2 and 3 will encoded in this format as 0000 0070 0003 0002 0006 0002 0004 0002 0004 0006 0006 0003 0003 000С, where:

offset	size	name	type	description	sample
0	1	wFmtID	word, ID	Format ID. Must be 0000	0000
1	1	wFrqDiv	word, positive	Carrier frequency divider	0070
2	1	nOnceSeq	word, length	Number of burst pairs at once sequence	0003
3	1	nRepeatSeq	word, length	Number of burst pairs at repeat sequence	0002
4	2*nOnceSeq	aOnceSeq	array of rBurstPair	Once sequence	0006 0002 0004 0002 0004 0006
4+2*nOnceSeq	2*nRepeatSeq	aRepeatSeq	array of rBurstPair	Repeat sequence	0006 0003 0003 000C

and rBurstPair consists of:

offset	size	name	type	description	sample
0	1	wLEDflash	word, positive	Periods when LED flashes with carrier	0006
1	1	wLEDoff	word, positive	Periods when LED is off	0002

Details:

• wFmtID: word = 0000, Format ID
• wFrqDiv: word in range 0001..FFFF, wFrqDiv = 4,145146 MHz / <signal carrier>. So wFrqDiv = 0001 corresponds to signal carrier » 4,1 MHz, and wFrqDiv =FFFF ~ 63Hz. I have measured this constant indirectly and have obtained 4,1455±0,0006 MHz, which is close enough with magical number 4,145146 [2], and far enough from 4,194304 [5], but I can’t locate quartz oscillator with this nominal at catalogues.
• nOnceSeq: word in range 0000..0100, is equal to amount of burst pairs at once sequence
• nRepeatSeq: word in range 0000..0100, is equal to amount of burst pairs at repeat sequence
• wLEDflash: word in range 0001..FFFF, is amount of carrier frequency periods when LED flashes every first half-period and turned off for the last half-period
• wLEDoff: word in range 0001..FFFF, is amount of carrier frequency periods when the LED is off

Next picture will dispel all residuary questions:

Figure placeholder: Picture 5 — correspondence between IR-signal and IR-code at format 0000

Raw unmodulated code (wFmtID = 0100)

Same structure as 0000, but LED is continuously on for the first word of the burst pair (no carrier):

Figure placeholder: Picture 6 — difference between IR signals for 0000 vs 0100

Differences:

offset	size	name	type	description	sample
0	1	wFmtID	word, ID	Format ID. Must be 0100	0100

aBurstPair consists of:

offset	size	name	type	description	sample
0	1	wLEDon	word, positive	Periods when LED is on	0006
1	1	wLEDoff	word, positive	Periods when LED is off	0002

This format completes format 0000 to universal description of all raw IR signals, but codes at format 0100 are rare – it is exposed to sun light and other IR noises. I have learned only 2 devices with these codes – noname drape drive and Dish Satellite Positioner. Nevertheless, sometimes it is useful to use IR signal without carrier, for example, for Sony Contol-S: you can replace an IR probe at RX-77 to ordinal jack, change 0000 to 0100 at IR codes, and your Sony device will be controlled by Control-S. Some other systems also support IR signals without carrier, like Crestron’s CstmFreq value = 43.

Predefined formats (wFmtID = 5000, 5001, 6000, 7000, 8000, 9000, 9001, 900A, 900B, 900C, 900D, 900E)

There are a number of additional, predefined IR formats, supported by some reasons. They can’t describe all IR signals, every type/subtype of this format represents only IR codes with specific structure, for custom “brand”. Also, we need additional data tables to replay these signals. These predefined formats are more compact than corresponding raw IR codes and, as a rule, simple and “clean”. I.e., if you learn IR as 5000 or 7000 and it is not a bug, then that and all other IR signals from this remote must be codes of this type.

Predefined formats have different structure, but for the reason of compatibility with format 0000, fields wFrqDiv, nOnceSeq, nRepeatSeq leave as dummy, so that code “looks” the same. aOnceSeq and aRepeatSeq are replaced with sCode, that consist real code info. Also, nOnceSeq and nRepeatSeq must meet the condition (nOnceSeq + nRepeatSeq) * 2 = sizeOf(sCode):

Template header:

offset	size	name	type	description	sample
0	1	wFmtID	word, ID	Format ID	5000
1	1	wFrqDiv	word, dummy	Unused word for compatibility	0000
2	1	nOnceSeq	word, dummy	Dummy code length	0000
3	1	nRepeatSeq	word, dummy	Dummy code length	0001
4	(nOnceSeq+nRepeatSeq)*2	sCode	structure	Predefined code	0000 0000

Not all of the predefined formats are supported by any Pronto model – here a table of compatibility is:

wFmtID	RU-890/940/TS-1000/RC-5000/5000i	TSU-2000	RC-5200/9200	TSU-6000/RU-970/USR-5	RAV-2000
0000, 0100, 5000, 5001, 6000, 7000	✔	✔	✔	✔	✔
8000		✔		✔	✔
9000			✔	✔	✔
9001					✔
900A–900E			✔	✔

Also, RC-3200 does not support all of this formats directly (except 0000), but RC-3200 Setup converts codes 0100, 5000, 5001 and 6000 codes into format 0000 automatically, and this feature can be used from elsewhere!

Note: 0000 format used by RC-3200 is extended by including support of unmodulated IR signals with special value of wFrqDiv = 0001.

When I describe these formats, I will translate them to format 0000, in anticipation of this converter is already exist.

Template based formats (wFmtID = 5000, 5001, 6000, 7000, 9000, 9001, 900A, 900B, 900C, 900D, 900E)

Template based formats are used for memory saving, for representing toggle IR codes, and for encoding IR signals with high carrier frequency.

Segment SYS at Pronto Firmware contains 2 tables for encoding/decoding IR codes these types:

SYS segment tables

dID	zSystem	zTemplate	zMask	dFrqDiv	bU1	dU2	dU3	dU4
00	rc5	1[01]{01}[01]%11R	5000h + {4-8}{12,9-14}	73	0	2	0	0A
01	rc6m0	H1000ftT}[01]%16R	6000h + {7-14}{15-22}	73	0	0	0	0A
02	rc5e	1 01]{01} [01]%5S[01]%12R	5001h + {4-8}{12,10-15}{15-20}	73	0	3	0	0A
03	b&o	<3[12345]*	7000h	-09	0	5	0	14
04	kenwood	rp	7000h	-09	0	2	1	14
05	pioneer	o$[01]%32[RSTUo] r[01rRSTUo]*	7000h	-04	0	4	1	14
06	ehrep	s[abcderst]%4[abcderst]*	7000h	-0C	0	4	0	14
07	ehonce	s[abcderst]%4[abcderst]*	7000h	-0C	0	4	0	14
08	grundig 16ac	P{ac} [abcd]%7r	7000h	88	0	0	0	06
09	grundig 16bd	P{bd}[abcd]%7r	7000h	88	0	0	0	06
0A	thomson1	2{12}[12]%9R	7000h	7C	0	1	0	0E
0B	thomson2	{12}{12}[12]%9[RS]	7000h	7C	0	-1	0	0F
0C	thomson3	[12]%4{12}[12]%7[RST]	7000h	7C	0	-1	0	10
0D	ferguson	s%2(01}[01]%9[RS]	7000h	-0C	1	4	0	0D
0E	telefunken	(01} {01}[01]%9[RS	7000h	-18	1	-1	0	0E
0F	echostar	T01]%5R	7000h	42	0	-1	0	07
10	saba	(01}{01}[01]%9[RS	7000h	-08	1	-1	0	0E
11	crown	2{12}[12]%9[RS]	7000h	6D	0	2	0	0E
12	seleco	2(12}[12]%9[RS	7000h	63	0	2	0	0E
13	nec1a	R	900Ah + {8-1,16-9)}{24-17,32-25}	6D	0	0	0	0E
14	nec1b	I[01]%32F	900Bh + {9-2,17-10}{25-18,33-26}	6D	0	0	0	0E
15	nec1c	R	900Ch + {8-1,16-9}{24-17,32-25} {42-35,50-43}{58-51,66-59}	6D	0	0	0	0E
16	nec1d	I[01]%32F	900Dh + {8-1,16-9}{24-17,32-25} {43-36,51-44}{59-52,67-60}	6D	0	0	0	0E
17	nec1e	I[01]%32FI[01]%32F	900Eh + {9-2,17-10}{25-18,33-26} {43-36,51-44}{59-52,67-60}	6D	0	0	0	0E
18	nec2a	I[01]%32FJR	900Ah + {8-1,16-9}{24-17,32-25}	68	0	0	0	0E
19	nec2b	I[01]%32F	900Bh + {9-2,17-10}{25-18,33-26}	68	0	0	0	0E
1A	nec2c	R	900Ch + {8-1,16-9}{24-17,32-25} {42-35,50-43}{58-51,66-59}	68	0	0	0	0E
1B	nec2d	I[01]%32F	900Dh + {8-1,16-9}{24-17,32-25} {43-36,51-44}{59-52,67-60}	68	0	0	0	0E
1C	nec2e	I[01]%32FI[01]%32F	900Eh + {9-2,17-10}{25-18,33-26} {43-36,51-44}{59-52,67-60}	68	0	0	0	0E
1D	nec	R	9000h + {8-1}{16-9}{24-17}{32-25}	6D	0	0	0	0E
*	rc6m6a-24	H1110{tT}0[01]%23R	6001h + {8-14)}{15-22}{23-30}	73	0	?	0	?
**	rc6m6a-32	H1110{tT} 1[01]%31R	6001h + {8-22}{23-30}{31-38}	73	0	?	0	?
***	yamahanec	R	?9001h + {8-1}{24-17}, + {!16-19}{132 -! 25}	?6D	0	0	0	?

dID	bCh	[i]	aBurstSeq	dID	bCh	[i]	aBurstSeq	dID	bCh	[i]	aBurstSeq
00	R	0	-0CA0	02	R	0	-0AA0	03	1	5	005B -0546
00	0	1	0020 -0020	02	S	1	-0080	04	p	0	0103 -AD01
00	1	2	-0020 0020	02	0	2	0020 -0020	04	e	1	0103 -47D5
01	H	0	0060 -0020	02	1	3	-0020 0020	04	s	2	0103 -1745
01	T	1	0020 -0020	03	R	0	005B -C422	04	r	3	1010 -040C
01	t	2	-0020 0020	03	5	1	005B -1BC0	04	0	4	0103 -0309
01	0	3	-0010 0010	03	4	2	005B -1622	04	1	5	0103 -0103
01	1	4	0010 -0010	03	3	3	005B -1083	04	s$	6	1010 -081E
01	R	5	-0BC0	03	2	4	005B -0AE4	05	r	0	227B -1160
05	R	1	022C -8FFA	0A	R	0	0006 -0857	10	S	1	0009 -58D2
05	S	2	022C -6108	0A	2	1	0006 -011A	10	0	2	0009 -0F3E
05	T	3	022C -4165	0A	1	2	0006 -00BB	10	1	3	0009 -0A2A
05	o	4	022C -31AF	0B	R	0	0010 -0857	11,12	R	0	0006 -0841
05	U	5	022C -2C13	0B	S	1	0010 -0642	11,12	S	1	0006 -065B
05	0	6	022C -0684	0B	2	2	0010 -0112	11,12	2	2	0006 -011A
05	1	7	022C -022C	0B	1	3	0010 -00B1	11,12	1	3	0006 -00BB
05	o$	8	227B -1160	0C	R	0	0010 -059D	13–1D, ***	I	0	0157 -00AB
06,07	r	0	00FC -347B	0C	S	1	0010 -0417	13–1D, ***	F	1	0016 -05E7
06,07	a	1	00FC -00FC	0C	T	2	0010 -02FB	13–1D, ***	1	2	0016 -0040
06,07	e	2	00FC -007E	0C	2	3	0010 -0099	13–1D	0	3	0016 -0015
06,07	t	3	007E -347B	0C	1	4	0010 -0044	13,15,18,1A	R	4	0157 -0055 0016 -0E3B
06,07	s	4	007E -0274	0D	R	0	0008 -4B7B	* **	H	0	0070 -0020
06,07	b	5	007E -017A	0D	S	1	0008 -3A74	* **	T?	1	0020 -0020
06,07	c	6	007E -00FC	0D	0	2	0008 -0A2B	* **	t	2	-0020 0020
06,07	d	7	007E -007E	0D	1	3	0008 -06C3	* **	0	3	-0010 0010
08,09	P	0	0019 -005A 0028	0D	s	4	0008 -0515	* **	1	4	0010 -0010
08,09	a	1	-0044 0024	0E	R	0	0008 -2BAE	*	R	5	-0AB0
08,09	b	2	-0036 0012 -000E 0012	0E	S	1	0008 -2104	**	R	5	-09B0
08,09	c	3	-0022 0012 -0022 0012	0E	0	2	0008 -05CA	10	R	0	0009 -74F3
08,09	d	4	-000E 0012 -0036 0012	0E	1	3	0008 -03D9
08,09	r	5	-07FC	0F	R	0	0019 -024C
0F	0	1	0019 -010A	0F	1	2	0019 -00AF

At the first table: dID – subformat, used at format 7000 and for connection with second table zSystem – unused string, “brand”-like description of dID zTemplate – template of logical structure of IR signal of this type (dID)

<letters> and <numbers> - are references as bCh to second table, where they (with dID) point out to a concrete aBurstSeq

| – delimits once sequence and repeat sequence parts

[<chars>] – means any of suggested characters

{<char1><char2>} – corresponds to toggle bit: at odd replaying of IR code of this type must be <char1>, at even – <char2>

%<number> - means <number> of duplicates of previous character/term

• - any number of any previously defined characters at [<chars>]

<char>$ - strange 2-byte name for char, nothing else :)

?, < - garbage that must be ignored :)

zMask – mask, correspondence between zTemplate and IR code at Fixed Size Template Based Formats. Be described at these formats. zMask is used while learning only.

Hexadecimal word is wFmtID

{<expression>} – means description of corresponded word from sCode

<number> - means index at forming String Code for corresponded bit at sCode word

<number1>-<number2> - means a range (inversed range) of these bounds – <number1>, <number1+(-)1>, …,

<number2>

!<number> – means index at String Code for logical negation of corresponded bit at sCode

dFrqDiv – carrier frequency divider. “-“ means high (>58KHz?) frequency, that is need to be analyzed (when learning) with another filter, I think, so “-“ must be ignored. bU1, dU2, dU3, dU4 – additional class/format characteristics. I suppose, they are used by recognition routine, or as additional info, like index of developer, who encodes special code for this format/subformat :), and must be ignored at replaying/converting.

At the second table:
dID – same as at the first table bCh – means index (char) from zTemplate or String Code [i] – means index to aBurstSeq from aCode (same as wCIdx) at Predefined Codes of Variable Length (7000) aBurstSeq – analogue of burst pair with variable length – from 1 to 4 words. Positive words mean time when LED flashes, negative – when LED is off.

Predefined code of variable length (wFmtID = 7000)

Structure (example: Grundig):

offset	size	name	type	description	sample
0	1	wFmtID	word, ID	Format ID = 7000	7000
1	1	wFrqDiv	word, dummy	Unused word	0088
2	1	nOnceSeq	word, dummy	Dummy length	0000
3	1	nRepeatSeq	word, dummy	Dummy length	0007
4	1	wSubFmtID	word, ID	SubFormat ID (dID)	0008
5	1	nCodeSeq	word, length	Length of aCode	000B
6	nCodeSeq	aCode	array of wCIdx	Code indexes to String Code	0010 0000 0017 0001 0001 0001 0001 0001 0001 0001 0005
6+nCodeSeq	0 or 1	wRest	word, dummy	Present if nCodeSeq is odd	0044

Condition: (nOnceSeq + nRepeatSeq) * 2 = 2 + nCodeSeq + sizeOf(wRest)

String Code selection:

• if wCIdx < 0010: use firmware table (dID, bCh, [i]) where dID = wSubFmtID and [i] = wCIdx
• if wCIdx = 0010: bCh = “1”
• if wCIdx > 0010: toggle char; odd replay uses zTemplate[wCIdx - 14], even uses zTemplate[wCIdx - 13]

Figure placeholder: Picture 8 — Forming String Code from 7000

Index to UDB (wFmtID = 8000)

Some models support an internal IR database (UDB). Others rely on software DBs.

Database availability

model	DB type	file	size
TS-1000, RU-890, RU-940	IR database at ProntoEdit	rcir.mdb (Jet)	360,448
TSU-2000, TSU-6000	UDB	UDP_int.hex	362,711
RU-970	UDB	UDP_int.hex	662,090
TSU-500	UDB as part of	TSU500.dat (Jet)	5,851,136
RU-930	UDB as part of	RU930.dat (Jet)	7,299,072
TSU-3000	UDB	UDB_TSU3000.bin	422,622
RC-5000/5000i/5200/9200	IR database at TSS	rcir.mdb (Jet)	978,944
RC-3200	—	—	—
RAV-2000	UDB	ww_udp.idb	662,090
USR-5	UDB	ww_udp.idb	661,011

Code example (Power On for Amp Yamaha, code set 1): 8000 0000 0002 0000 000a 23f0 0002 0000

Structure:

offset	size	name	type	description	sample
0	1	wFmtID	word, ID	Must be 8000	8000
1	1	wFrqDiv	word, dummy	Unused	0000
2	1	nOnceSeq	word, dummy	Dummy length	0002
3	1	nRepeatSeq	word, dummy	Dummy length	0000
4	1	wDevType	word, index	Device type (000A = Amp)	000A
5	1	wBrandCodeSet	word, index	Brand/Code Set (23F0 = Yamaha-1)	23F0
6	1	wFunction	word, index	Function (0002 = Power On)	0002
7	1	wRest	word, dummy	Padding to even words	0000

Functions and device-type enumerations follow the UDB. Not all combinations are supported across all models.

References

There are a number of articles about IR formats applied to Pronto on the internet:

1. Daniel Tonks “Unofficial Philips Pronto & Marantz RC5000 FAQ”, http://www.remotecentral.com
2. Marcel Majoor “Communicating with the Pronto”, http://home.hccnet.nl/m.majoor
3. Barry Gordon “ProntoEdit’s IR Display Format”, http://the-gordons.net:8080/, http://www.remotecentral.com/features/irdisp1.htm
4. Barry Shaw, Rob Crowe, Andrea Whitlock “Yamaha extended IR codes”, http://darius.mobius-soft.com/~andrea/
5. Stewart Allen, “The CCF file format”, http://giantlaser.com/tonto/

---

Author note: Please excuse my poor English. For questions about Pronto IR you can reach me at eoulianov@hotbox.ru, and I will try to answer more clearly :)