I am having trouble with some Pronto codes. For example (from Zenith) there are alternating columns of "0000" in the code. This "0000" is suposed to be the LED on time, but this would seem that the LED comes on for 0 periods of the carrier frequency.

How to I convert these kinds of codes to a list of LED on and LED off times?

0000 0067 0000 0010 0000 00CC 0000 0014 0000 00A3 0000 00CC 0000 00CC 0000 0014 0000 00A4 0000 00CB 0000 0014 0000 00A4 0000 00CC 0000 0014 0000 00A3 0000 0014 0000 00A4 0000 0BAA

Thanks

This looks like a Sony Code. Are you sure it is for a Zenith?

If you have a code that does not work or need codes for a particular make/model of equipment, it is best to post what you need and somebody will likely come to the rescue.

If you are working on a research project, etc...

In the Classic Pronto Files Section, under User Documentation, there is a file (Word Document) By Barry Gordon entitled "Pronto Hex IR Format". Have you seen this document? It will give you a better understanding of the Pronto Hex IR Format.

Yep. Question is what person or what software delivered such a silly signal. And how/if it can be "repaired".

The latest version of IrScrutinizer (1.1.1) will, when fed with such "silly" signals, will offer to replace the 0 by another number. Doing so (using almost any small number), the signal is identified (by DecodeIr really) as "protocol = Zenith, device = 5, subdevice = 0, obc = 17".
 

Thanks for the help Barf. Much appreciated. ;-)

Thanks guys... I found these codes (with the zeros) on remote control central's website at: [Link: remotecentral.com].

Here is a list of the manufacturers with the same problem:

aethra
ampro
akai
anthem
apti
audio internaltional
audio request
barco
biAmp
btx
canon
chiro
chisholm
christie Digital
ctx
digital projection
HITAHI
KLOSS
lutron
onkyo
RCA
samsung (vcr)
sony
zenith

Thanks

Interesting... The problem is hardly some manufacturers, but rather with some captures. It would be interesting to find out what software (or what persons) are producing that sort of meaningless signals. After all, it is strictly speaking nothing but a redundant way of specifying a long silence... And I think that most software like PE will barf on it too -- have not tried though.

Did you have a look at Barry's Document?

Yes. I am familiar with that (15 years old) document. It does not attach any particular semantic meaning to duration of zero length.

FWIW, here is how I explain the Pronto Hex notations, somewhat more concisely.