Science behind IR (Using Android instead of JP1)
Posted: Fri Nov 15, 2013 1:27 pm
With the crop of smartphones that are coming out with IR blasters, I'm curious if any of the great work done on JP1 (software / codes) can be applied. There's also IR transmitters that plug into the audio jack (i.e. looq system).
For example, I understand EFCs are UEI brand/hardware dependent, but the OBC that KM/RM generates, is the actual raw data bytes that get shifted out via IR, no?
If so, the OBC doesn't contain any information about the protocol itself (Sony20bit, device, subdevice,etc). That information that describes how to transmit the data (frequency, etc) would need to be setup ahead of time by the device containing the IR transmitter (JP1 Remote or smartphone in general).
So, is the implementation of these device protocols ultimately what makes this a difficult task for non-JP1 remotes? For example, even for a common carrier frequency of 38khz, you can't just transmit that via the audio jack (2-20khz) that has an ir led connected to it...
Would love to hear any thoughts on how this works, and how much of a leap is to go from JP1/OBC to a DIY IR transmitter.
For example, I understand EFCs are UEI brand/hardware dependent, but the OBC that KM/RM generates, is the actual raw data bytes that get shifted out via IR, no?
If so, the OBC doesn't contain any information about the protocol itself (Sony20bit, device, subdevice,etc). That information that describes how to transmit the data (frequency, etc) would need to be setup ahead of time by the device containing the IR transmitter (JP1 Remote or smartphone in general).
So, is the implementation of these device protocols ultimately what makes this a difficult task for non-JP1 remotes? For example, even for a common carrier frequency of 38khz, you can't just transmit that via the audio jack (2-20khz) that has an ir led connected to it...
Would love to hear any thoughts on how this works, and how much of a leap is to go from JP1/OBC to a DIY IR transmitter.