lirc-list
|
From: Matthew Hatch <matthew@az...> - 2010-10-01 05:22:52
Attachments:
signature.asc
|
So my new mceusb arrived today and I couldn't wait to get it all set up on my server / mythtv backend. usb 5-2: new full speed USB device using ohci_hcd and address 7 usb 5-2: New USB device found, idVendor=0471, idProduct=060c usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 5-2: Product: BB+ Dongle(e.d) usb 5-2: Manufacturer: usb 5-2: SerialNumber: A@... usb 5-2: reset full speed USB device using ohci_hcd and address 7 lirc_dev: lirc_register_driver: sample_rate: 0 lirc_mceusb[7]: BB+ Dongle(e.d) on usb5:7 After some tinkering with lircd, I got it working to where I can send channel-change requests through the transmitters (the appropriate channel blinks and all). The trouble is that the IR extenders that came with this thing seem to be too weak to be of any use. I put the LED directly over the receiver window on the device, and it does nothing. Putting the irsend command in a continuous loop and moving the LED around shows that it *kinda* works, but it's usually in a position that I cannot affix it in. So, the question: Is there an option somewhere (I'm guessing no) that can boost the output to this LED (or make it light up longer than a simple blip), or would simply replacing the extender LED with a bigger one work here? Has anyone had an experience like this? What solution did you use? As is, an example command that I'm using to send is: irsend SEND_ONCE DTA100 KEY_1 I'm really frustrated. It's like I get soooooo close to getting this thing working, and something always wants to try my patience. (sigh) -- Matthew Hatch |
|
From: <lirc@ba...> - 2010-10-01 06:48:22
|
Hi! Matthew Hatch "matthew@..." wrote: > So my new mceusb arrived today and I couldn't wait to get it all set up > on my server / mythtv backend. [...] > After some tinkering with lircd, I got it working to where I can send > channel-change requests through the transmitters (the appropriate [...] > So, the question: Is there an option somewhere (I'm guessing no) that > can boost the output to this LED (or make it light up longer than a > simple blip), or would simply replacing the extender LED with a bigger > one work here? Has anyone had an experience like this? What solution > did you use? > > As is, an example command that I'm using to send is: > > irsend SEND_ONCE DTA100 KEY_1 > > I'm really frustrated. It's like I get soooooo close to getting this > thing working, and something always wants to try my patience. How does your config file look like? Have you tried this one: http://lirc.sourceforge.net/remotes/motorola/DTA100 Christoph |
|
From: Matthew Hatch <matthew@az...> - 2010-10-01 15:41:54
Attachments:
signature.asc
|
Hi! On 10/01/2010 12:47 AM, Christoph Bartelmus wrote: <snip> > How does your config file look like? > Have you tried this one: > http://lirc.sourceforge.net/remotes/motorola/DTA100 My config matches that exactly, with the exception of the remote name, which I shortened for usability. Using 'irw' and the original remote for the DTA100, I've confirmed that the config is indeed correct. I've also tried using the supplementary IR receiver you can plug into the back of the DTA, but I only get marginally better results using that (some codes get recognized, but a lot are missed altogether). It's the same story -- I have to strategically position the transmitter in such a way that would be impossible (or just very difficult) to permanently mount. I'm thinking it's just a couple of very much underpowered transmitters, so I'm guessing I'll need to somehow acquire (or build) new ones that will work with the USB base unit... -- Matthew Hatch |
|
From: Jarod Wilson <jarod@wi...> - 2010-10-01 23:38:27
|
On Fri, Oct 1, 2010 at 11:41 AM, Matthew Hatch <matthew@...> wrote: > Hi! > > On 10/01/2010 12:47 AM, Christoph Bartelmus wrote: > > <snip> >> How does your config file look like? >> Have you tried this one: >> http://lirc.sourceforge.net/remotes/motorola/DTA100 > > My config matches that exactly, with the exception of the remote name, > which I shortened for usability. > > Using 'irw' and the original remote for the DTA100, I've confirmed that > the config is indeed correct. I've also tried using the supplementary > IR receiver you can plug into the back of the DTA, but I only get > marginally better results using that (some codes get recognized, but a > lot are missed altogether). It's the same story -- I have to > strategically position the transmitter in such a way that would be > impossible (or just very difficult) to permanently mount. > > I'm thinking it's just a couple of very much underpowered transmitters, > so I'm guessing I'll need to somehow acquire (or build) new ones that > will work with the USB base unit... My own moto gear required adding "min_repeat 2" to lircd.conf to get channel changes to work consistently. -- Jarod Wilson jarod@... |
|
From: Matthew Hatch <matthew@az...> - 2010-10-02 05:05:06
Attachments:
signature.asc
|
On 10/01/2010 05:38 PM, Jarod Wilson wrote: <snip> > My own moto gear required adding "min_repeat 2" to lircd.conf to get > channel changes to work consistently. I played around with that value, and it didn't do much at first. After further experimentation, it turns out that the LED may actually be *over* powering the receiver rather than being underpowered as originally thought. I moved it about two inches away and it's working pretty good now, with one exception: When I press 1 on the remote, irw reports 'KEY_1' was pressed. The cable device also displays a 1 on the screen at the same time (as you would expect). When irsend sends KEY_1 to either of the transmitters, the cable device (either one -- I have two of them) displays a 0 on the screen. It doesn't matter if I set a min_repeat value, or move the device around, or even change the order of the digits (ie: channel 14, 41, 11 call come through as 04, 40, 00). I cannot get it to register a 1. I'm doing an irrecord on the remote instead of using the config from lirc just to see if it detects anything differently, but this is really odd... |
|
From: <lirc@ba...> - 2010-10-06 20:21:38
|
Hi! Matthew Hatch "matthew@..." wrote: > On 10/01/2010 05:38 PM, Jarod Wilson wrote: > <snip> >> My own moto gear required adding "min_repeat 2" to lircd.conf to get >> channel changes to work consistently. > I played around with that value, and it didn't do much at first. After > further experimentation, it turns out that the LED may actually be > *over* powering the receiver rather than being underpowered as > originally thought. I moved it about two inches away and it's working > pretty good now, with one exception: > > When I press 1 on the remote, irw reports 'KEY_1' was pressed. The > cable device also displays a 1 on the screen at the same time (as you > would expect). When irsend sends KEY_1 to either of the transmitters, > the cable device (either one -- I have two of them) displays a 0 on the > screen. It doesn't matter if I set a min_repeat value, or move the > device around, or even change the order of the digits (ie: channel 14, > 41, 11 call come through as 04, 40, 00). I cannot get it to register a 1. > > I'm doing an irrecord on the remote instead of using the config from > lirc just to see if it detects anything differently, but this is really > odd... The values in the config file might me slightly off. You can try e.g. using "zero 210 750" instead of the original values. Or "zero 290 670". Christoph |
|
From: Matthew Hatch <matthew@az...> - 2010-10-08 19:52:12
Attachments:
signature.asc
|
On 10/06/2010 02:20 PM, Christoph Bartelmus wrote: > The values in the config file might me slightly off. > You can try e.g. using "zero 210 750" instead of the original values. > Or "zero 290 670". Brilliant! 'zero 210 750' seems to work great! I'll do some more testing on this, but it looks like I'm finally in business. Thanks, everyone! -- Matthew Hatch |