Mark Pierson wrote:However, if I recall correctly, the bigger problem is that most PC IR ports are not simple IR but rather IRDA which really not useable for things such as remote control.
Many years ago I managed to get the detailed documentation on the IRDA chip that my employer was using in some hand held computers. The manufacturer of the IRDA chips didn't want to release the documentation to low volume customers, only to major BIOS writing companies, because they thought only BIOS developers should have that info. One of my coworkers managed to get it despite that.
That IRDA chip had a number of non IRDA modes, in which it could be kludged to send and receive ordinary remote control signals, and I did so.
That was all long ago and all the details would be different now. But I expect IRDA chips still have non IRDA modes that could be used.
I'm actually rather surprised that there aren't easy to find and use software to do this. The Linux folks seem to be fairly good at extracting documentation from chip manufacturers that initially prefer to tell only Microsoft and maybe a few BIOS vendors. I'm sure you also would need to know a bit more than I do about bypassing whatever Windows drivers and features get in the way of your taking over the IRDA subsystem. But many people clearly know how to do that.
I'd bet it is all possible. But I have never had the time for the major investigation project to find out how. As I said before, the most likely freeware group to work on such things is LIRC.
Mark Pierson wrote:Think about it, if it were that easy, there'd be a ton of software out there to do it. Heck, even Mr. Gates might be trying to sell you it (or bundling it in Windows as another one of those "must have" features.
For commercial vendors, I think needing a little extra hardware is a marketing advantage. Various trivial hardware designs with bundled software are available (at outrageous prices) to capture remote signals. If those vendors know how to skip the hardware, they probably wouldn't do it because it reduces what you can reasonably charge and makes it hard to prevent piracy.
jorge garcia wrote:There are Palm pilots, watches, or other such devices that DO LEARN KEYS from any remote you put in front of it, and at the same time these devices connect to the computer´s IR port with no problem at all, for synch, file transfers, etc.
Meaning the people who programmed that did have access to the detailed specs of the IRDA subsystems built into those devices (and how to bypass any OS IRDA software that might be in the way). So they can program them to receive remote control signals. Then they can talk to a PC with correct IRDA (not need to kludge the PC's IRDA support).
jorge garcia wrote:to learn and interpret (obc,efc, hex) any keys from any remote, and avoiding the hassle of the 25 key learning maximum that many URC remotes have.
Exactly what CaptureIR does!
Immediate decodes (protocol, device, obc, efc, etc.) a moment after you release the button, and instantly ready to receive the next. No 25 key limit, not second step (upload and decode results), also large adjustable limit on the max captured signal duration, so you can decode macros and the obscure protocols that are too long for a learning remote to learn.
Yes, it would be better if it used the IRDA port instead of an external IR sensor whose parts cost a few dollars. But I don't have time to research IRDA chips.