0
\$\begingroup\$

I have a vehicle stereo deck that has an IR receiver input (+) and a steering wheel control module that has an IR emitter LED (+/-). The steering wheel control module, "translates" (using a mapping created during programming) the button presses on the steering wheel to an IR output -- the idea being that you can still control aftermarket stereos equipped with IR receiver LEDs with the steering wheel controls (which are normally proprietary to the vehicle make).

Unfortunately the aftermarket stereo I purchased does not have an IR receiver LED built into it, so it cannot be controlled purely by IR. However, the aftermarket stereo does have an IR-in (+) wire, just no IR receiver LED attached to it. At this stage of the explanation, the setup looks like this:

Pre-Change Diagram

Of course I'd like to actually have steering wheel controls for my aftermarket stereo, so I'm wondering how to connect this all together without having to buy and hookup an IR receiver LED (which honestly I don't even know if it's that easy to do given the lack of documentation for this stereo). Can I just cut off the IR Emitter LED from the steering wheel control module, isolate the IR Out (-), and hook the IR Out (+) directly to the aftermarket stereo's IR In (+)? Like so:

Post-Change Diagram (Yellow and orange illustrate the changes I'm proposing.)

My instincts tell me it seems too simple...

\$\endgroup\$
  • 1
    \$\begingroup\$ I wouldn't count on it. \$\endgroup\$ – immibis Apr 26 at 4:18
  • \$\begingroup\$ You must recognize what the interface is for each end. Is it xx kHz Carrier + data on Tx ? \$\endgroup\$ – Sunnyskyguy EE75 May 3 at 23:08
  • \$\begingroup\$ @SunnyskyguyEE75 I do not know. The stereo deck came with no technical specifications except a sticker on the top of it (which doesn't indicate anything useful for the IR wire). I've emailed their support numerous times and there's only one person that answers me and she knows even less than I do! Anyway to identify that? I have a couple DMMs and an Arduino with lots of spare parts, if that helps. \$\endgroup\$ – Nick Betcher May 3 at 23:32
  • \$\begingroup\$ This is a question on an undocumented consumer product, and thereby off-topic here as a matter of policy. \$\endgroup\$ – Chris Stratton May 3 at 23:40
  • \$\begingroup\$ Find out from Auto forum for your vehicle the carrier frequency used and get the matching Sharp-Vishay IR Rx. 38kHz is most common, cheap to buy on speculation... digikey.ca/products/en/sensors-transducers/… \$\endgroup\$ – Sunnyskyguy EE75 May 3 at 23:50
1
+100
\$\begingroup\$

Your instincts are correct!

I work on LOTs of televisions and smaller 5 to 7 inch displays. I often see an IR Input marking where an IR receiver actually is installed and its demodulated output ends up on the IR Input line. Without getting too long here, the 99.99% answer to your question is - NO! While IR remote controls 'seem' very simple, I mean you press a button and your done, there is a LOT more to what is going on that we imagine.

An IR "message" from one device to another is a form of a language, with lots and lots of variations.

The following is for -most- remotes... Quickly - Nearly ALL IR messages are sent on a modulated carrier of 36Khz to 40Khz. I have worked with some much lower and much higher, just most are. An old RCA model was modulated, but a different frequency for each key... (that was a mess).

In order for the receiver to "tune in" to the message that is about to arrive a long pulse is sent. This pulse is followed by a short blank, or no IR is sent, and then sometimes this pulse is repeated a time or two.

The data part of a transmission varies by model and company, but here is an example. Then the remote (well, transmitter) sends 8 bits of data followed by the same 8 bits inverted. This first byte is the "family" byte, then another 8 bits and its inverted form and these are called the command byte. Then another.... well, up to 6 bytes of data and 6 inverted bytes and THEN a stop bit or two.

Bits are represented by a short pulse followed by a long pulse, or the other way around, or they use a NRZI format or well the sky is the limit...

So if you can imagine with all of this going on, you are probably .000000000001% likely to have them work the way you would like.

Keep in mind the modulation of most remotes is 33% ON time (duty cycle), but there are a few receivers that will not work at close range with more than 5% duty cycle (Magnovox was an example).

And not to forget the amount of current that is pushed through the IR diode to get the best performance, Vishay was the one I used, with the duty cycle reduced I had a very small current limiting resistor in series with it and got perfect performance from 25 meters.

Granted, the input impedance of the receiver circuit is decent, so that is unlikely to cause any issues, but without a ground reference who knows what sort of 'Oh Crap' stuff may happen.

Oh yes, an easy, simple fix.... Nope!

\$\endgroup\$
  • \$\begingroup\$ While you look at the right details, your conclusion is misleading - most likely all it would actually take would be wire in a 59-cent receiver module which performs the demodulation. Of course we can't actually know - which is why the question is off topic here \$\endgroup\$ – Chris Stratton May 4 at 17:03
0
\$\begingroup\$

does not have an IR receiver LED

This is a mistake in terminology. While LEDs can with extreme care be used to make poor receivers, generally phototransistors are used.

In your case you probably want an IR receiver module (like a tssop-xxxx), this will be drastically simpler than trying to accomplish a wired connection, which would require that you first remove the modulation, possibly deal with circuit voltage differences, high side vs. low side drive, and an unknowable assortment of issues in your undocumented consumer product.

\$\endgroup\$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.