From: Daniel M <ra...@us...> - 2006-08-16 11:03:16
|
Hi, I have been working on adding transmitter support to the lirc_mceusb2 driver. As of now it actually sends ir commands out through the emitters. But I still cannot get my TV (or any other device) to recognize the signal correctly. When looked through an oscilloscope even the timings of the signal looks the same as the signal(RC5) my original TV remote sends out. All this has started med to wonder if the problem is with the emitters (which are just regular red leds) and not the driver it self. Does anyone know if there is a known "emitter" problem with the mce devices even when used with the Microsoft driver? Since i don't have a Windows MCE machine to test with, I can not check my self if this is a "hardware" fault or not. All i know is that the output from the driver and device looks correct. /Daniel M |
From: Maciek K. <ma...@ph...> - 2006-08-16 17:18:19
|
* Daniel M <ra...@us...> [060816 07:15]: > I have been working on adding transmitter support to the lirc_mceusb2 dri= ver. As of now it actually sends ir commands out through the emitters. But = I still cannot get my TV (or any other device) to recognize the signal corr= ectly. When looked through an oscilloscope even the timings of the signal l= ooks the same as the signal(RC5) my original TV remote sends out.=20 >=20 > All this has started med to wonder if the problem is with the emitters (w= hich are just regular red leds) and not the driver it self. >=20 > Does anyone know if there is a known "emitter" problem with the mce devic= es even when used with the Microsoft driver? >=20 > Since i don't have a Windows MCE machine to test with, I can not check my= self if this is a "hardware" fault or not. All i know is that the output f= rom the driver and device looks correct. You could use a second IR receiver and a scope to verify that the IR signals sent by the mce transmitter look the same as the once by the remote. This would give you an apples to apples comparison at the hardware signal level.= =20 |
From: Jerome H. <rj...@gm...> - 2006-08-16 19:25:03
|
Maybe I mis-undestood something here, but did you say that the emitters were just normal red LEDs? I'm not sure about the receiver in the device you are trying to control, but all the ones I deal with are pretty good at ignoring visible light. The only time I use "normal" LEDs is to give me a visual indication that my transmitter is working instead of having to hook up my o-scope. On 8/16/06, Maciek Klimkowski <ma...@ph...> wrote: > > * Daniel M <ra...@us...> [060816 07:15]: > > I have been working on adding transmitter support to the lirc_mceusb2 > driver. As of now it actually sends ir commands out through the emitters. > But I still cannot get my TV (or any other device) to recognize the signal > correctly. When looked through an oscilloscope even the timings of the > signal looks the same as the signal(RC5) my original TV remote sends out. > > > > All this has started med to wonder if the problem is with the emitters > (which are just regular red leds) and not the driver it self. > > > > Does anyone know if there is a known "emitter" problem with the mce > devices even when used with the Microsoft driver? > > > > Since i don't have a Windows MCE machine to test with, I can not check > my self if this is a "hardware" fault or not. All i know is that the output > from the driver and device looks correct. > > You could use a second IR receiver and a scope to verify that the IR > signals > sent by the mce transmitter look the same as the once by the remote. This > would give you an apples to apples comparison at the hardware signal > level. > > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.3 (GNU/Linux) > > iD8DBQFE41X6noMa3N/wLiURAnDwAKD31x/x2jwpEbIQxXADkLtHtYEPdACfamXg > 4d91l7ejlSumFDR52qDrNk4= > =mi8k > -----END PGP SIGNATURE----- > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > |
From: Daniel M <ra...@us...> - 2006-08-16 21:56:10
|
Hi again, The driver seems to work know, I think the problem is the mce hardware itself and the regular red led emitters that Microsoft ships with this device. They will just not work together with some ir receivers since they are made to reject as much visible light as they possibly can. Anyway, what is the normal way to get things included in the lirc cvs tree, I only have anonymous access. To whom should I send it to and in what format. /Daniel M On Wed, 16 Aug 2006 14:24:57 -0500, "Jerome Hanby" <rj...@gm...> wrote: > Maybe I mis-undestood something here, but did you say that the emitters > were > just normal red LEDs? I'm not sure about the receiver in the device you > are > trying to control, but all the ones I deal with are pretty good at > ignoring > visible light. The only time I use "normal" LEDs is to give me a visual > indication that my transmitter is working instead of having to hook up my > o-scope. > > On 8/16/06, Maciek Klimkowski <ma...@ph...> wrote: >> >> * Daniel M <ra...@us...> [060816 07:15]: >> > I have been working on adding transmitter support to the lirc_mceusb2 >> driver. As of now it actually sends ir commands out through the > emitters. >> But I still cannot get my TV (or any other device) to recognize the > signal >> correctly. When looked through an oscilloscope even the timings of the >> signal looks the same as the signal(RC5) my original TV remote sends > out. >> > >> > All this has started med to wonder if the problem is with the emitters >> (which are just regular red leds) and not the driver it self. >> > >> > Does anyone know if there is a known "emitter" problem with the mce >> devices even when used with the Microsoft driver? >> > >> > Since i don't have a Windows MCE machine to test with, I can not check >> my self if this is a "hardware" fault or not. All i know is that the > output >> from the driver and device looks correct. >> >> You could use a second IR receiver and a scope to verify that the IR >> signals >> sent by the mce transmitter look the same as the once by the remote. > This >> would give you an apples to apples comparison at the hardware signal >> level. >> >> >> >> >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.3 (GNU/Linux) >> >> iD8DBQFE41X6noMa3N/wLiURAnDwAKD31x/x2jwpEbIQxXADkLtHtYEPdACfamXg >> 4d91l7ejlSumFDR52qDrNk4= >> =mi8k >> -----END PGP SIGNATURE----- >> >> >> > ------------------------------------------------------------------------- >> Using Tomcat but need to do more? Need to support web services, > security? >> Get stuff done quickly with pre-integrated technology to make your job >> easier >> Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >> >> > > |
From: <li...@ba...> - 2006-08-17 02:27:18
|
Hi! Daniel M "ra...@us..." wrote: [...] > Anyway, what is the normal way to get things included in the lirc cvs tree, > I only have anonymous access. To whom should I send it to and in what > format. Please send your patch to Martin Blatter for review. After that send it to me. I prefer to get a diff to latest CVS version. Christoph |
From: Steven E. <mai...@st...> - 2006-09-05 03:58:10
|
Daniel M wrote: > Hi again, > > > > The driver seems to work know, I think the problem is the mce hardware itself and the regular red led emitters that Microsoft ships with this device. They will just not work together with some ir receivers since they are made to reject as much visible light as they possibly can. > > How is your progress going and is there anything we can test at this stage. Very happy to be a beta tester for this. Steve |
From: Allan S. <Dib...@pe...> - 2006-08-18 15:11:53
|
Daniel M wrote: > Hi, > > > > I have been working on adding transmitter support to the lirc_mceusb2 driver. As of now it actually sends ir commands out through the emitters. But I still cannot get my TV (or any other device) to recognize the signal correctly. When looked through an oscilloscope even the timings of the signal looks the same as the signal(RC5) my original TV remote sends out. > Great news! > All this has started med to wonder if the problem is with the emitters (which are just regular red leds) and not the driver it self. > > > > Does anyone know if there is a known "emitter" problem with the mce devices even when used with the Microsoft driver? >From looking at the emitters previously, I recall that they are not just red LEDs. There are actually 2 LEDs in one package. However, they are *extremely* short range / low power - On the order of 5cm or so. Is there any chance of a copy of the patch? :) Cheers, Allan. |
From: Mario L. <mar...@gm...> - 2006-09-08 04:58:39
|
On Fri, 2006-08-18 at 16:11 +0100, Allan Stirling wrote: > Daniel M wrote: > > Hi, > >=20 > >=20 > >=20 > > I have been working on adding transmitter support to the lirc_mceusb2 d= river. As of now it actually sends ir commands out through the emitters. Bu= t I still cannot get my TV (or any other device) to recognize the signal co= rrectly. When looked through an oscilloscope even the timings of the signal= looks the same as the signal(RC5) my original TV remote sends out.=20 > >=20 > Great news! >=20 > > All this has started med to wonder if the problem is with the emitters = (which are just regular red leds) and not the driver it self. > >=20 > >=20 > >=20 > > Does anyone know if there is a known "emitter" problem with the mce dev= ices even when used with the Microsoft driver? >=20 > >From looking at the emitters previously, I recall that they > are not just red LEDs. There are actually 2 LEDs in one > package. However, they are *extremely* short range / low > power - On the order of 5cm or so. >=20 > Is there any chance of a copy of the patch? :) >=20 > Cheers, >=20 > Allan. >=20 This is quite exciting to hear. Has this made it into CVS yet? I couldn't connect to the CVS server for some reason, and I didn't see the patch posted to the mailing list. |