lirc_mceusb2 not transmitting

View: New views
6 Messages — Rating Filter:   Alert me  

lirc_mceusb2 not transmitting

by Russ Dill-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I have a couple of TopSeed IR devices that came with MCE remotes:

ID 1784:0008 TopSeed Technology Corp.

The device has two IR blaster ports, an IR receiver inside, and two
other LEDs. Neither one seems to be sending codes. The devices do
receive codes just fine. I issue the following command for testing:

while true; do irsend SEND_ONCE K12K-C5 TVPOWER; done

lirc doesn't indicate any errors, but a digital camera doesn't show
any flashing on the IR blaster. None of the visible LEDs inside the
device flash either. I'm using the 1.44 version of the driver and the
2.6.25 kernel from debian.

I've tried all combinations of SET_TRANSMITTERS before issuing irsend
to no effect (1, 2, and 1 2)

Jul 16 20:19:54 icarus kernel: [ 5619.203115] lirc_mceusb2: Philips
eHome USB IR Transceiver and Microsoft MCE 2005 Remote Control driver
for LIRC $
Jul 16 20:19:54 icarus kernel: [ 5619.203115] lirc_mceusb2: Daniel
Melander <lirc@...>, Martin Blatter
<martin_a_blatter@...>
Jul 16 20:19:54 icarus kernel: [ 5619.203115] lirc_mceusb2: debug mode enabled
Jul 16 20:19:54 icarus kernel: [ 5619.205552] lirc_mceusb2: usb probe called
Jul 16 20:19:54 icarus kernel: [ 5619.379746] usb 1-9: reset full
speed USB device using ohci_hcd and address 6
Jul 16 20:19:54 icarus kernel: [ 6066.370256] lirc_mceusb2: acceptable
outbound endpoint found
Jul 16 20:19:54 icarus kernel: [ 6066.370256] lirc_mceusb2: acceptable
inbound endpoint found
Jul 16 20:19:54 icarus kernel: [ 6066.370256] lirc_dev:
lirc_register_plugin: sample_rate: 0
Jul 16 20:19:54 icarus kernel: [ 6066.377846] lirc_mceusb2[6]: Topseed
Technology Corp. eHome Infrared Transceiver on usb1:6
Jul 16 20:19:54 icarus kernel: [ 6066.377852] lirc_mceusb2[6]: receive
request called (size=0x20)
Jul 16 20:19:54 icarus kernel: [ 6066.377857] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377859] lirc_mceusb2[6]: receive
request called (size=0x20)
Jul 16 20:19:54 icarus kernel: [ 6066.377861] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377863] lirc_mceusb2[6]: receive
request called (size=0x5)
Jul 16 20:19:54 icarus kernel: [ 6066.377866] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377868] lirc_mceusb2[6]: receive
request called (size=0x20)
Jul 16 20:19:54 icarus kernel: [ 6066.377870] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377872] lirc_mceusb2[6]: receive
request called (size=0x2)
Jul 16 20:19:54 icarus kernel: [ 6066.377874] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377875] lirc_mceusb2[6]: receive
request called (size=0x20)
Jul 16 20:19:54 icarus kernel: [ 6066.377878] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377903] usbcore: registered new
interface driver lirc_mceusb2
Jul 16 20:19:58 icarus kernel: [ 5623.466063] lirc_mceusb2[6]: set use inc
Jul 16 20:20:00 icarus kernel: [ 5625.514527] lirc_mceusb2[6]:
SET_CARRIER requesting 38000 Hz
Jul 16 20:20:00 icarus kernel: [ 5625.514527] lirc_mceusb2[6]: receive
request called (size=0x4)
Jul 16 20:20:00 icarus kernel: [ 5625.514527] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:20:00 icarus kernel: [ 5625.514527] lirc_mceusb2[6]: receive
request called (size=0x59)
Jul 16 20:20:00 icarus kernel: [ 5625.514527] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:20:11 icarus kernel: [ 6083.753299] lirc_mceusb2[6]: receive
request called (size=0x59)
Jul 16 20:20:11 icarus kernel: [ 6083.753299] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:20:19 icarus kernel: [ 6091.918940] lirc_mceusb2:
SET_TRANSMITTERS mask=3
Jul 16 20:20:24 icarus kernel: [ 6097.700302] lirc_mceusb2[6]: receive
request called (size=0x59)
Jul 16 20:20:24 icarus kernel: [ 6097.700302] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:26:59 icarus kernel: [ 6534.626486] lirc_mceusb2:
SET_TRANSMITTERS mask=2
Jul 16 20:27:23 icarus kernel: [ 6070.913278] lirc_mceusb2[6]: receive
request called (size=0x59)
Jul 16 20:27:23 icarus kernel: [ 6070.913289] lirc_mceusb2[6]: receive
request complete (res=0)

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

lirc_mceusb2 not transmitting

by Russ Dill-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I have a couple of TopSeed IR devices that came with MCE remotes:

ID 1784:0008 TopSeed Technology Corp.

The device has two IR blaster ports, an IR receiver inside, and two
other LEDs. Neither one seems to be sending codes. The devices do
receive codes just fine. I issue the following command for testing:

while true; do irsend SEND_ONCE K12K-C5 TVPOWER; done

lirc doesn't indicate any errors, but a digital camera doesn't show
any flashing on the IR blaster. None of the visible LEDs inside the
device flash either. I'm using the 1.44 version of the driver and the
2.6.25 kernel from debian.

I've tried all combinations of SET_TRANSMITTERS before issuing irsend
to no effect (1, 2, and 1 2)

Jul 16 20:19:54 icarus kernel: [ 5619.203115] lirc_mceusb2: Philips
eHome USB IR Transceiver and Microsoft MCE 2005 Remote Control driver
for LIRC $
Jul 16 20:19:54 icarus kernel: [ 5619.203115] lirc_mceusb2: Daniel
Melander <lirc@...>, Martin Blatter
<martin_a_blatter@...>
Jul 16 20:19:54 icarus kernel: [ 5619.203115] lirc_mceusb2: debug mode enabled
Jul 16 20:19:54 icarus kernel: [ 5619.205552] lirc_mceusb2: usb probe called
Jul 16 20:19:54 icarus kernel: [ 5619.379746] usb 1-9: reset full
speed USB device using ohci_hcd and address 6
Jul 16 20:19:54 icarus kernel: [ 6066.370256] lirc_mceusb2: acceptable
outbound endpoint found
Jul 16 20:19:54 icarus kernel: [ 6066.370256] lirc_mceusb2: acceptable
inbound endpoint found
Jul 16 20:19:54 icarus kernel: [ 6066.370256] lirc_dev:
lirc_register_plugin: sample_rate: 0
Jul 16 20:19:54 icarus kernel: [ 6066.377846] lirc_mceusb2[6]: Topseed
Technology Corp. eHome Infrared Transceiver on usb1:6
Jul 16 20:19:54 icarus kernel: [ 6066.377852] lirc_mceusb2[6]: receive
request called (size=0x20)
Jul 16 20:19:54 icarus kernel: [ 6066.377857] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377859] lirc_mceusb2[6]: receive
request called (size=0x20)
Jul 16 20:19:54 icarus kernel: [ 6066.377861] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377863] lirc_mceusb2[6]: receive
request called (size=0x5)
Jul 16 20:19:54 icarus kernel: [ 6066.377866] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377868] lirc_mceusb2[6]: receive
request called (size=0x20)
Jul 16 20:19:54 icarus kernel: [ 6066.377870] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377872] lirc_mceusb2[6]: receive
request called (size=0x2)
Jul 16 20:19:54 icarus kernel: [ 6066.377874] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377875] lirc_mceusb2[6]: receive
request called (size=0x20)
Jul 16 20:19:54 icarus kernel: [ 6066.377878] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377903] usbcore: registered new
interface driver lirc_mceusb2
Jul 16 20:19:58 icarus kernel: [ 5623.466063] lirc_mceusb2[6]: set use inc
Jul 16 20:20:00 icarus kernel: [ 5625.514527] lirc_mceusb2[6]:
SET_CARRIER requesting 38000 Hz
Jul 16 20:20:00 icarus kernel: [ 5625.514527] lirc_mceusb2[6]: receive
request called (size=0x4)
Jul 16 20:20:00 icarus kernel: [ 5625.514527] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:20:00 icarus kernel: [ 5625.514527] lirc_mceusb2[6]: receive
request called (size=0x59)
Jul 16 20:20:00 icarus kernel: [ 5625.514527] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:20:11 icarus kernel: [ 6083.753299] lirc_mceusb2[6]: receive
request called (size=0x59)
Jul 16 20:20:11 icarus kernel: [ 6083.753299] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:20:19 icarus kernel: [ 6091.918940] lirc_mceusb2:
SET_TRANSMITTERS mask=3
Jul 16 20:20:24 icarus kernel: [ 6097.700302] lirc_mceusb2[6]: receive
request called (size=0x59)
Jul 16 20:20:24 icarus kernel: [ 6097.700302] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:26:59 icarus kernel: [ 6534.626486] lirc_mceusb2:
SET_TRANSMITTERS mask=2
Jul 16 20:27:23 icarus kernel: [ 6070.913278] lirc_mceusb2[6]: receive
request called (size=0x59)
Jul 16 20:27:23 icarus kernel: [ 6070.913289] lirc_mceusb2[6]: receive
request complete (res=0)

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

Re: lirc_mceusb2 not transmitting

by Matt Nelson-4 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

This is what I have used and it works great for me:

 irsend SET_TRANSMITTERS 2
 irsend --count=4 SEND_ONCE YAMAHA_RECEIVER POWER_ON

I don't know if you found out yet or not, but the set transmitters does the following:

1 - use transmitter 1
2 - use transmitter 2
1 2 - use transmitter 1 and 2

the "--count" tells the transmitter how many times to send the signal.  I found that my yamaha receiver had about a 50/50 chance of turning on unless I turned this to about 4.  Set it to high and it will turn your device on, and then off again, but to low and some devices are stupid and need to be slapped in the face to actually wake up and recognize the signal.

Hope this helps.

On Thu, Jul 17, 2008 at 11:27 PM, Russ Dill <russ.dill@...> wrote:
I have a couple of TopSeed IR devices that came with MCE remotes:

ID 1784:0008 TopSeed Technology Corp.

The device has two IR blaster ports, an IR receiver inside, and two
other LEDs. Neither one seems to be sending codes. The devices do
receive codes just fine. I issue the following command for testing:

while true; do irsend SEND_ONCE K12K-C5 TVPOWER; done

lirc doesn't indicate any errors, but a digital camera doesn't show
any flashing on the IR blaster. None of the visible LEDs inside the
device flash either. I'm using the 1.44 version of the driver and the
2.6.25 kernel from debian.

I've tried all combinations of SET_TRANSMITTERS before issuing irsend
to no effect (1, 2, and 1 2)

Jul 16 20:19:54 icarus kernel: [ 5619.203115] lirc_mceusb2: Philips
eHome USB IR Transceiver and Microsoft MCE 2005 Remote Control driver
for LIRC $
Jul 16 20:19:54 icarus kernel: [ 5619.203115] lirc_mceusb2: Daniel
Melander <lirc@...>, Martin Blatter
<martin_a_blatter@...>
Jul 16 20:19:54 icarus kernel: [ 5619.203115] lirc_mceusb2: debug mode enabled
Jul 16 20:19:54 icarus kernel: [ 5619.205552] lirc_mceusb2: usb probe called
Jul 16 20:19:54 icarus kernel: [ 5619.379746] usb 1-9: reset full
speed USB device using ohci_hcd and address 6
Jul 16 20:19:54 icarus kernel: [ 6066.370256] lirc_mceusb2: acceptable
outbound endpoint found
Jul 16 20:19:54 icarus kernel: [ 6066.370256] lirc_mceusb2: acceptable
inbound endpoint found
Jul 16 20:19:54 icarus kernel: [ 6066.370256] lirc_dev:
lirc_register_plugin: sample_rate: 0
Jul 16 20:19:54 icarus kernel: [ 6066.377846] lirc_mceusb2[6]: Topseed
Technology Corp. eHome Infrared Transceiver on usb1:6
Jul 16 20:19:54 icarus kernel: [ 6066.377852] lirc_mceusb2[6]: receive
request called (size=0x20)
Jul 16 20:19:54 icarus kernel: [ 6066.377857] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377859] lirc_mceusb2[6]: receive
request called (size=0x20)
Jul 16 20:19:54 icarus kernel: [ 6066.377861] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377863] lirc_mceusb2[6]: receive
request called (size=0x5)
Jul 16 20:19:54 icarus kernel: [ 6066.377866] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377868] lirc_mceusb2[6]: receive
request called (size=0x20)
Jul 16 20:19:54 icarus kernel: [ 6066.377870] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377872] lirc_mceusb2[6]: receive
request called (size=0x2)
Jul 16 20:19:54 icarus kernel: [ 6066.377874] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377875] lirc_mceusb2[6]: receive
request called (size=0x20)
Jul 16 20:19:54 icarus kernel: [ 6066.377878] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:19:54 icarus kernel: [ 6066.377903] usbcore: registered new
interface driver lirc_mceusb2
Jul 16 20:19:58 icarus kernel: [ 5623.466063] lirc_mceusb2[6]: set use inc
Jul 16 20:20:00 icarus kernel: [ 5625.514527] lirc_mceusb2[6]:
SET_CARRIER requesting 38000 Hz
Jul 16 20:20:00 icarus kernel: [ 5625.514527] lirc_mceusb2[6]: receive
request called (size=0x4)
Jul 16 20:20:00 icarus kernel: [ 5625.514527] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:20:00 icarus kernel: [ 5625.514527] lirc_mceusb2[6]: receive
request called (size=0x59)
Jul 16 20:20:00 icarus kernel: [ 5625.514527] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:20:11 icarus kernel: [ 6083.753299] lirc_mceusb2[6]: receive
request called (size=0x59)
Jul 16 20:20:11 icarus kernel: [ 6083.753299] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:20:19 icarus kernel: [ 6091.918940] lirc_mceusb2:
SET_TRANSMITTERS mask=3
Jul 16 20:20:24 icarus kernel: [ 6097.700302] lirc_mceusb2[6]: receive
request called (size=0x59)
Jul 16 20:20:24 icarus kernel: [ 6097.700302] lirc_mceusb2[6]: receive
request complete (res=0)
Jul 16 20:26:59 icarus kernel: [ 6534.626486] lirc_mceusb2:
SET_TRANSMITTERS mask=2
Jul 16 20:27:23 icarus kernel: [ 6070.913278] lirc_mceusb2[6]: receive
request called (size=0x59)
Jul 16 20:27:23 icarus kernel: [ 6070.913289] lirc_mceusb2[6]: receive
request complete (res=0)

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

Parent Message unknown Re: lirc_mceusb2 not transmitting

by Russ Dill-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

> When you tested the blaster feature did you connect the two IR blaster LEDs
> to the external IR blaster ports?

Yup, and one of them mounted on the TV IR receiver. I've used a serial
transmitter before, I'm upgrading to the USB one for the auto resume
feature.

> The MCE unit usually does not have any blasters built into the unit since it
> would lead to a conflict if one would like to control different devices
> using the same IR protocol. However at least on the original Microsoft unit
> there is a normal visible led flashing the signal when transmitting. You
> should also know that the range of the blaster LEDs is very limited, usually
> only 10-20 millimeters.

Like I said, there are 2 LED's inside the unit in addition to the
receiver. One of them does flash when receiving codes from a remote.

> Also another thing you could try is to make lirc send the same command
> several times in a row. Many device only responds when they see the ircode a
> second or a third time.
>
> For instance to send your TVPOWER command 5 times just append it to the end
> och irsend like this
>
> irsend SEND_ONCE K12K-C5 TVPOWER TVPOWER TVPOWER TVPOWER TVPOWER
>
>
> There is also the SEND_START and SEND_STOP commands to send the signal
> continuously for some time. A while loop like the one you have in your
> example may work but usually is to slow and breaks the protocols intended
> repetition space between commands.

Tried all of those, and along with SEND_ONCE --count=... No response
from the TV, and no visible flashing using a digital camera (which
does pick up flashing from remotes and from my serial blaster)

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

Re: lirc_mceusb2 not transmitting

by Yashka Oreza :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Russ Dill-2 wrote:
Like I said, there are 2 LED's inside the unit in addition to the
receiver. One of them does flash when receiving codes from a remote.
On mine, that's just a red LED for humans to look at.

Russ Dill-2 wrote:
Tried all of those, and along with SEND_ONCE --count=... No response
from the TV, and no visible flashing using a digital camera (which
does pick up flashing from remotes and from my serial blaster)
Same here. I found this message:
http://www.nabble.com/IR-blasting-with-Topseed-transeiver-(0x1784,-0x0008)-td17684577.html
Which would seem to indicate that the mceusb2 driver doesn't support transmitting on this class of device yet.

Re: lirc_mceusb2 not transmitting

by Russ Dill-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Sun, Aug 17, 2008 at 11:18 AM, Yashka Oreza <yashka@...> wrote:

>
>
>
> Russ Dill-2 wrote:
>>
>> Like I said, there are 2 LED's inside the unit in addition to the
>> receiver. One of them does flash when receiving codes from a remote.
>>
>
> On mine, that's just a red LED for humans to look at.
>
>
> Russ Dill-2 wrote:
>>
>> Tried all of those, and along with SEND_ONCE --count=... No response
>> from the TV, and no visible flashing using a digital camera (which
>> does pick up flashing from remotes and from my serial blaster)
>>
>
> Same here. I found this message:
> http://www.nabble.com/IR-blasting-with-Topseed-transeiver-(0x1784,-0x0008)-td17684577.html
> Which would seem to indicate that the mceusb2 driver doesn't support
> transmitting on this class of device yet.
> --
> View this message in context: http://www.nabble.com/lirc_mceusb2-not-transmitting-tp18550121p19022059.html
> Sent from the LIRC mailing list archive at Nabble.com.
>

I'd really like to get this working as I have two of them. Does anyone
have anything to tweak or try?

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
LightInTheBox - Buy quality products at wholesale price