Does anyone know if (how) it is possible to extract discrete codes from the ipaq Nevo software? All codes should be somewhere in the files. The only hard part is to get them out ;) I'm looking for the codes of the 0200 code library (Blaupunkt TV).

Even if you could hack the database, all it will contain will be 3 bytes that identify the manufacturer, device, and button. The code itself is only generated when it's used.

Why not just use learn the codes from the iPAQ?

That's because it is a 'strange' code. It cannot be learned correctly by a Pronto, nor by Nevo. I also wanted to use my Pronto to send these codes, Nevo already does with that device code. Too bad the UEI database is not cracked...

Is there no software which can record the strings that are sent with the IrDa port of the iPaq?

You can record them as a .wav file using an IR receiver, a couple of resistors and a soundcard or laptop with Line-In.

Once you have a .wav file, you can convert it to CCF using a freeware app I wrote.

See...

     [Link: mbx-usa.com]
     [Link: mbx-usa.com]

for details.

Do you know the carrier frequency?

This message was edited by Dave Houston on 03/16/04 17:21.

VITO oscilloscope can also save an IR signal.

Run the prog on another iPAQ and it displays the learned signal as a scope trace. Allows saving to file as .irs format.

Do not know about converting to a ccf hex code though.





This message was edited by npaisnel on 03/17/04 08:36.

Nice program! But it doesn't work for the Blaupunkt code. Like I said it's a very strange code! If you have a OFA remote, try it! You will see omly a couple of pulses. I haven't tried the audio to ccf method yet.

Some Blaupunkt TVs use an unusual IR encoding technique which is a combination of conventional pulse position modulation and FSK (frequency shift keying).

If yours is one of these -- and I suspect it is -- most learner algorithms can't handle it because it looks like it has two different carrier frequencies.

And, even if you could learn it, you could not play it back with a Pronto.

Any idea what the carrier frequencies are? They would need to be fairly far apart.

In theory the Pronto should have the same Database. Philips pays royalties to UEI for using the database. the only model that does not have it is the TS-1000 all the other models are TSU something and the U stands for universal IR database that comes from UEI

It's unclear to me who actually owns the UEI database. Here's a direct quote from an article (Feb '98 HomeToys online magazine) by Dave Rye, an X-10 VP...

"In 1988 X-10 started manufacturing universal IR remotes for Universal Electronics Inc. (UEI) under the One-For-All brand. We expanded this business to the point where we were manufacturing 1 million remotes a month. We now make remotes for Thomson (RCA/GE), Radio Shack, ourselves, and others. We have the best IR code library in the business and are one of the biggest manufacturers of IR remotes in the world."

Regarding carrier frequencies: Actually they are not that far apart as I recall. Something like 33 and 37KHz. The receiver literally decodes the bit values by digitally counting how many cycles of carrier are present in each pulse, not by analog filtering the input.

The problem is that because the two frequencies are so close, typical learners will save only a single value -- the average of the two. Thus when the learned signal is played back, no pulse will have exactly the right number of carrier cycles and the receiver rejects them all.

BTW, the UEI database belongs to UEI. They were around well before the 1988 date mentioned by Dave Rye. And on the remote control side of their business, X-10 was mostly just a contract manufacurer back then anyway.

Wow! Blaupunkt seriously wants to sell their own remotes. Doesn't the CCF format only allow one carrier frequency?

X-10 introduced their powerline control system in 1978 which was before the first IR remotes came along. TV remotes were ultrasonic until the early '80s.

per code? yes, but each code can be a different frequency

But not for alternating carrier bursts within a single code which is, I think, what has been described.