Irda & W2k

[Mark F]

I've not heard of ANYONE getting IRDA to work with a consumer electronics remote controller. If someone has a setup working, please post the details. Thanks.

The UIRT (http://people.a2000.nl/rwvgesse/FixFrame.htm?Uirt.htm) has gotten a lot of attention on this thread (http://www.girder.nl/phpBB/viewtopic.php?topic=409&forum=3) recently.

[Ingo]

I've had it kind of working some time ago, but it was neither reliable nor farreaching. I had to directly point the IR emitter at it from a distance of around 2m at max. The other problem was that the IRDA receiver had to point at my remote controller within an angle of around 5°, which is quite impractical.... And even with all this, it was never realy stable....

[goldi]

Hi,

I try to use girder with an Irda on W2k. Communication with my mobile phone works good (default Win2k Irda driver).

I also tried to use the 2 lines in the msport.inf file like it works on Win98, but this didn't help unfortunately.

who can help me?
thanx.

[JpL]

Hi,

First of all, IrDA and remote control protocol are not strictly compatible. It is why recognition is not accurate.

I am working on the IrDA plugin for my remote control. I have rewrited the main loop and the match funtion, and I am quite happy with this version. Anyway, I must do some other modifications to improve it.

I am thinking about releasing my version, but I have some problems:

1/ It works with _my_ remote control (an AIWA with sub-carrier at 40 Khz and pulse coded). May be it is not so accurate with other remote control, and need to do some improvment. What about blank or shift coded remote control? What about different sub-carrier? May be some user can help me by sending raw log from their IrDA/remote control (with serialwtacher for example)?

2/ Due to complex tuning of this module, I thing that it could be great to have a more elaborate learning process. I am thinking about to ask the user to press all remote buttons, ten time each for exemple, long or short time, etc, and to choose between optimistic behavior or pessimistic, and that's all. But I am not very good in user interface, and I need for help to do this.

So, I am ready to write this stuff, but only if it is usefull for people.

Bye,
Jp.

[nynamja]

I can't do anything with Girder on Win2K Service Pack 2. This is quite annoying. As I read the troubleshooting guides for Girder and the internal IrDA device. But there is no info on the help files. Could someone help me? I want to use the IrDA device in my Dell Inspiron 8100 notebook to control winamp. I will be using a Bang & Olufsen Beolink 7000 remote control with two-way communication so the IrDA is very clear since it can both receive and transmit signals back to my remote control for realtime data. Someone please help me. Thank you.

-Chris

P.S. Does anyone know where I can purchase or build an external ir device (serial) that will receive and transfer data? Just in case IrDA doesn't work. Oh, by the way, Bang & Olufsen remote controls use 455KHz instead of the usual 40KHz that most remotes use.

[nuanda]

I've got IrDA working with my Pronto universal remote by doing the following:
1) in bios enable IrDA on COM2
2) Windows (ME in this case) loads virtual drivers.
3) Disable the new drivers in your current hardware profile. (This assumes that you will not need to use IrDA for data transfer)*
4) Add a new serial port(COM2)in hardware, the IrDA receiver is now connected to COM2.
5) Set the Serial port COM2 to no flow control.
6) In Girder, select the IRDA input device and set it to Com2.

Although this works the results are not great. As someone else mentioned, you have to get pretty close with almost no angle for it to work.

* it is possible to make the IrDA drivers work alongside the serial port by setting the IrDA driver to use the same resources as the serial port (IRQ3, 2h..something)