"Worked" requires a definition here. You mean you got light, so you figure that the light that came out of the LED matched the waveform of the sound in the WAV file? To know that, you have to rig up a light sensor, amplify what it receives, and compare the waveforms of the original signal before the LED with the waveform of the light.

I can get 5V from the iPhone's jack plug for example.
What is the load, in ohms, on that jack when you are getting five volts? I know of several projectors that output 12 volt trigger voltages, but if you put a real-world relay on them to actually use them as triggers, the voltage falls to around two volts. Thus what looks like a usable output, in a test that doesn't involve the intended wiring, gives a false positive.


I'm sorry, but that sounds like "my car radio outputs fifteen watts, but I can get thirty watts if I put twins in the front seat." Better yet, "one twin walks down the street at 3 mph, but if the two twins walk together, they're going 6 mph." Going from one LED to two LEDs does not cause a sound card to be able to make waveforms with twice the frequency, which is to say half the duration. I'm trying hard not to laugh.


What's why?

And by the way, if you can't record 38 kHz with your sound card, then is that frequency maybe out of its range? The classic definition of "out of range" is "can't handle the signal." There's no reason to expect higher response on playback than on record, although it might happen.

While exploring a totally different topic, which is recording 78 rpm records, I ran across someone who plays them at 33 1/3 rpm, then uses software in the computer to multiply the sound up to the equivalent of 78 rpm. All sounds are within the normal audible range here, but this suggests that there's software out there that would allow you to make your wav files at half frequency, then double the frequency and speed through software. That has zero to do with whether a sound card or a phone could output that signal, though.

Of course you dont see the blinking but it still send the signal, this is what does matter. (BTW for some reason through a camera you can see the leds actually blinking, but this doesnt matter.) And why? Because if I can make this I dont even need a remote. Of course thereare other ways to do it, but it would take quiet long to create all the wav files with the signal for all of my remotes. Sure I could make an accessory wich records the code or decodes it(but then again, I got only a code), but it would take again much time to record all of the buttons' signal of all my remotes. So I think this is the best way to do it. And if I can use this method, others can too, and again they dont need tp waste much time with this.

It takes approximately five million Form C relays to build 64k of ram. Unfortunately, you can't do much with that these days, plus it would fill a room, plus it would take an enormous amount of power to operate, plus it would be hot, plus it would be loud, and with all of that time and energy spent building boards and soldering things together, you still wouldn't be able to do much with it.

One Iphone - $199
Two IR emitters - $50
Four hundred hours of engineering time - $4,000
Grand total - $4,249

[Link: google.com]

How do I know that it works? With the wavs I've generated manually, I was able to control my TV(turn on/off, channel+, channel-, because I created the files only for these commands. So I'm sure that it works. And what 50$ for the emitter? Yesterday I bought two 940nm IR LEDs for less than 2$!

I say for all the effort you might as well ditch the whole idea and just get up off the couch and change the channels.

We have to assume this is a smart phone because it will have to have a graphical user interface right? Why are you not using one of the several off the self products for this?.

I applaud your creativity, really.

If you wanted to make this a viable product, you certainly could. Is there a market for it? Perhaps. Would I buy it? Probably not. Would anybody on this website buy it? Probably not; we all already have universal remote controls...

Could you please explain the steps involved with creating your own .wav driver for a IR remote? I'm seriously curious how you did it.

If you explain the steps involved, we could probably shoot around some ideas for how to code it...

Why don't you just buy one of the many products that can already turn your iPhone or Ipod Touch into an IR sending device with a complete database of IR codes?

[Link: thinkflood.com] ($49)

[Link: newkinetix.com] ($55.95)

http://www.ryzmedia.com/ ($9.99)

Now if you'll excuse me, I'm going to invent some kind of a round thing that I can put on an axle so I can move stuff around easier. Any ideas what I could call it?

I'm now seeing that you want to do it, and that's that. Back when I had a corporate income, and occasionally the boss would ask "why?" I could investigate things -- on his dime -- until I knew why and could explain it. You're now doing a similar thing, but your "answer" will be a product or an approach to a product.

Go for it! Just realize that the rest of us do not need, and probably don't want, such a controller. I mean, most of the people who need controllers are not all by themselves, and if the control is built into the phone, what happens when the owner of the phone takes the phone away to go to work? The other person sits at home in silence?

So, you're going to buy a phone just for this purpose? Why bother? Lots and lots of remotes, actual remotes, already exist, so there's no need for a phone to do this.

This is what I call a "research project," meaning that there's no guarantee of any outcome (or income!) whatever, no guarantee that it can be done, no guarantee that you'll have the time or the money to complete the task.

Best of luck.

the method works fine for what he is trying to do. it has been documented already on the internet. the problem is everything is a wave file which can add up and there are no huge online dbase of the wav files. any ir dongle is typically using this method on the backend though like Redeye mini for instance.

the reason it works is because 2 mono connectors on the headphone jack are about 20kHz each. they modulate (more complicated that this. read link below) both together for 40kHz and calculate how to get 38kHz from there.

this guy explains how to do it well
[Link: rtfms.com]

just a matter of getting the proper (or close enough) wav file for your device(s). of course this is dongle based IR so it is line of sight. there is even some freeware to convert pronto to wav with this guy above who ripped it from the jp1 remote programmers.

this is typically how it is done with the dongle remotes on iphone these days.

that is the stupidest thing i have ever seen! i can appreciate the tenacity of the OP but really? it looks like you would have dozens of wave files linked to commands for equipment. so you would have to go to music and select wav files for commands? dude, do yourself a favor and buy one of the devices David referenced. if not for just the gui alone. anyway! off to work

Best post so far.

I like what this guy is doing. I give him props for trying and I am honored that he reached out to our community. Lets listen and help rather than assume and criticize. If he in fact succeeds at finding a tool to convert the files easily then building a code database and plug in remote adapter could be a money maker. Its certainly not our business model but neither is X10 and they still sell.

Give credit where credit is due.

Carry on. :)

really? the guy at rtfms has already done it. it seems sziky is just not patient enough for rtmfs to publish his source code for generating wav files. not to mention with the options that are out from $10 to $50 the biggest question is why?

I've seen that post but, this is not about that I dont want to buy a 10$ thing. I want to actually understand the method of programming an IR code to wav ,,converter". And of course I won't play them from my music library, I'll write a gui for it. I am not doing this because I can't live with my universal remote. It's about learning, and about the satisfaction, that you have done it.

We'll I applaud you as well. It read as if you were trying to assemble some half-a$$ed solution to avoid buying a working product.

Much smarter than me.

Hi,

My bad, I promised the code and never published it. That code is my second python program ever and it doesn't look good. I wanted to polish the code a bit before making it public to be less ashamed of its quality but never found time for that.

So I guess I'll publish it as is today or tomorrow. Thanks for your patience!

Andrey Mikhalchuk
(the rtfms.com guy)