On Aug 25, 2009, at 11:35 AM, Patrick Calhoun wrote:
> Hi all.
> I read somewhere that mceusb gen1 devices (045e:006d) can't transmit
> using lirc. Is this still correct?
> If so, can someone explain to me
> what efforts have been made in that area and maybe where we've
> become stuck?
I added support for the first-gen device to the second-gen driver. The
original driver never had any transmit support, while the second-gen
one does. I was hoping, but not expecting, that we'd add transmit
support for free, but alas, no dice. It obviously requires some amount
of change to transmit with the first-gen device, and I simply haven't
had the time or impetus to look to see what needs doing.
> In my own efforts to make it work, I've noticed that these lines of
> (drivers/lirc_mceusb/lirc_mceusb.c cvs revision 1.44) seem to totally
> BREAK transmission:
> 1170 request_packet_async(ir, ep_out, init2,
> 1171 sizeof(init2), MCEUSB_OUTBOUND);
> If I remove that statement, I get some transmission through the
> blaster/dongle. (I removed this code statement based on what usb
> sees in Windows).
> The problem is, though, if I blast to another mceusb receiver in
> I receive only the initial fraction of the transmission (and more
> importantly, the target device does not react).
> To quantify that statement:
> I'm transmitting a Panasonic space_encoded command. My lircd.conf
> snippet is at the end of this message.
> I should be transmitting 6 data bytes.
> That's 48 data bits, which is 96 ir pulse/space transmissions.
> Adding 4 bytes of ir protocol overhead for "header" and "ptrail",
> an even 100 pulses/spaces, which implies 100 bytes transmission sent
> the mceusb, (not counting the mceusb overhead of the "9f 08 06"
> command, "84" commands sent before every 4-byte pulse/space data
> and final "80" command).
> In short, mode2 gets 100 lines of output from my actual remote
> and gets only the first 40-48 lines from the lirc/mceusb trying to
> replicate those 100 lines.
> So anyone have any ideas?
Well, the first thing I was planning to do was try transmitting under
Windows while snooping the traffic to see what packets were sent, then
work from there... I got as far as plugging the thing into my laptop
briefly while booted in Windows, saw that it loaded drivers, and that
was as far as I got. If you've got snoops, feel free to hit me with
them, and I can try to make heads or tails of them.