Mailing List Archive

mceusb IR-Blaster question
Folks,

Feeling a but dumb on this one, thought I would ask for
advice on the ir-blaster side of this thing.

I have a mceusb
IR-Receiver and Blaster which I am using with lirc v0.8.7-88 rpms from
atrpms :

Bus 001 Device 007: ID 0471:060c Philips (or NXP) Consumer
Infrared Transceiver (HP)

I am trying to use the ir-blaster side of
this to control a Pioneer Voyager 3000 STB from Brighthouse.

The
device works fine for input, and when I do irsend, it says it sent (and
logs) the information, I can see the little light flash, however it
doesn't actually do anything on my STB.

May 1 09:16:51 moses kernel:
lirc_dev: IR Remote Control driver registered, major 61
May 1 09:16:59
moses kernel: lirc_mceusb: Windows Media Center Edition USB IR
Transceiver driver for LIRC 1.90
May 1 09:16:59 moses kernel:
lirc_mceusb: Daniel Melander <lirc@rajidae.se>, Martin Blatter
<martin_a_blatter@yahoo.com>, Dan Conti <dconti@acm.wwu.edu>
May 1
09:16:59 moses kernel: lirc_dev: lirc_register_driver: sample_rate:
0
May 1 09:19:27 moses kernel: usbcore: registered new interface driver
lirc_mceusb
May 1 09:19:27 moses kernel: lirc_mceusb[7]: tx data: 00 ff
aa (length=3)
May 1 09:19:27 moses kernel: Device reset requested
May 1
09:19:27 moses kernel: lirc_mceusb[7]: tx data: ff 0b (length=2)
May 1
09:19:27 moses kernel: Get hw/sw rev?
May 1 09:19:27 moses kernel:
lirc_mceusb[7]: tx data: ff 18 (length=2)
May 1 09:19:27 moses kernel:
Unknown command 0xff 0x18
May 1 09:19:27 moses kernel: lirc_mceusb[7]:
rx data: ff fe (length=2)
May 1 09:19:27 moses kernel: Previous command
not supported
May 1 09:19:27 moses kernel: lirc_mceusb[7]: tx data: 9f
05 (length=2)
May 1 09:19:27 moses kernel: Unknown command 0x9f 0x05
May
1 09:19:27 moses kernel: lirc_mceusb[7]: rx data: ff fe (length=2)
May 1
09:19:27 moses kernel: Previous command not supported
May 1 09:19:27
moses kernel: lirc_mceusb[7]: tx data: 9f 07 (length=2)
May 1 09:19:27
moses kernel: Get carrier mode and freq
May 1 09:19:27 moses kernel:
lirc_mceusb[7]: rx data: 9f 04 00 fa (length=4)
May 1 09:19:27 moses
kernel: Resp to 9f 05 of 0x00 0xfa
May 1 09:19:27 moses kernel:
lirc_mceusb[7]: tx data: 9f 13 (length=2)
May 1 09:19:27 moses kernel:
Get transmit blaster mask
May 1 09:19:27 moses kernel: lirc_mceusb[7]:
rx data: 9f 06 01 41 (length=4)
May 1 09:19:27 moses kernel: Got carrier
mode and freq of 0x01 0x41
May 1 09:19:27 moses kernel: lirc_mceusb[7]:
tx data: 9f 0d (length=2)
May 1 09:19:27 moses kernel: Get receive
timeout
May 1 09:19:27 moses kernel: lirc_mceusb[7]: rx data: 9f 08 03
(length=3)
May 1 09:19:27 moses kernel: Got transmit blaster mask of
0x03
May 1 09:19:27 moses kernel: lirc_mceusb[7]: tx data: 9f 15
(length=2)
May 1 09:19:27 moses kernel: Get receive sensor
May 1
09:19:27 moses kernel: lirc_mceusb[7]: rx data: 9f 0c 07 d0
(length=4)
May 1 09:19:27 moses kernel: Got receive timeout of 1000
ms
May 1 09:19:27 moses kernel: lirc_mceusb[7]: rx data: 9f 14 01
(length=3)
May 1 09:19:27 moses kernel: Got long-range receive sensor in
use
May 1 09:21:02 moses kernel: lirc_i2c: chip 0x0 found @ 0x18
(Hauppauge IR)
May 1 09:21:02 moses kernel: lirc_dev:
lirc_register_driver: sample_rate: 10

_START-UP LIRCD_

May 1
09:21:10 moses lircd-0.8.7[9636]: lircd(default) ready, using
/var/run/lirc/lircd
May 1 09:21:10 moses lircd-0.8.7[9636]: accepted new
client on /var/run/lirc/lircd
May 1 09:21:20 moses lircd-0.8.7[9636]:
accepted new client on /var/run/lirc/lircd

When I issue the irsend
command to hit the power button for example (irsend SEND_ONCE mceusb
Power) I see this in the logs:

May 1 09:21:20 moses kernel:
lirc_mceusb[7]: tx data: 9f 06 01 41 (length=4)
May 1 09:21:20 moses
kernel: Request carrier mode and freq of 0x01 0x41
May 1 09:21:20 moses
kernel: lirc_mceusb[7]: rx data: 9f 06 01 41 (length=4)
May 1 09:21:20
moses kernel: Got carrier mode and freq of 0x01 0x41
May 1 09:21:20
moses kernel: lirc_mceusb[7]: tx data: 9f 08 03 84 b5 11 88 08 84 88 08
88 11 84 88 11 9a 11 84 88 08 88 08 84 88 08 88 08 84 88 08 88
(length=88)
May 1 09:21:20 moses kernel: Request transmit blaster mask
of 0x03
May 1 09:21:20 moses lircd-0.8.7[9636]: removed client

So the
hardware appears to be working, yet nothing I "send" has any effect on
the STB.

Question, how does irsend know what freq's, protocols, etc to
send ? I mean, just like you have to "program" a remote to work with
different equipment, isn't there something you have to do to get irsend
to know "how" it should speak to this STB ?

Thanks in Advance,

Jim


--
Re: mceusb IR-Blaster question [ In reply to ]
On Tue, May 1, 2012 at 9:25 AM, jbhuber <jbhuber@judahnet.net> wrote:
> I am trying to use the ir-blaster side of this to control a Pioneer Voyager
> 3000 STB from Brighthouse.

Start by looking here:

http://lirc.sourceforge.net/remotes/pioneer/

You need to add one of these remote definitions to your remote
configuration file after your mceusb configuration.

> When I  issue the irsend command to hit the power button for example (irsend
> SEND_ONCE mceusb Power) I see this in the logs:

You don't want to send mceusb signals. You want to send pioneer
signals, so it should be something like:

irsend SEND_ONCE Pioneer_VXX2910 power

if you use the VXX2910 configuration file.

I have no idea which exact configuration file is the right one for
your particular model STB.

Eric
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: mceusb IR-Blaster question [ In reply to ]
Alternatively, us irrecord with lirc stopped and the /etc/lirc* device to make a new remote file and send it to the lirc list.

-rF

On 01/05/2012, at 11:40 PM, Eric Sharkey wrote:

> On Tue, May 1, 2012 at 9:25 AM, jbhuber <jbhuber@judahnet.net> wrote:
>> I am trying to use the ir-blaster side of this to control a Pioneer Voyager
>> 3000 STB from Brighthouse.
>
> Start by looking here:
>
> http://lirc.sourceforge.net/remotes/pioneer/
>
> You need to add one of these remote definitions to your remote
> configuration file after your mceusb configuration.
>
>> When I issue the irsend command to hit the power button for example (irsend
>> SEND_ONCE mceusb Power) I see this in the logs:
>
> You don't want to send mceusb signals. You want to send pioneer
> signals, so it should be something like:
>
> irsend SEND_ONCE Pioneer_VXX2910 power
>
> if you use the VXX2910 configuration file.
>
> I have no idea which exact configuration file is the right one for
> your particular model STB.
>
> Eric
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: mceusb IR-Blaster question [ In reply to ]
On Tue, May 1, 2012 at 1:40 PM, Eric Sharkey <eric@lisaneric.org> wrote:
....
> I have no idea which exact configuration file is the right one for
> your particular model STB.

One configuration file that explicitly mentions the Voyager 3000
(although on TWC) can be found at:

http://lirc.sourceforge.net/remotes/time_warner_cable/UR4-P360

And, just as with Eric, I have no idea if that is the correct
configuration file for your STB.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: mceusb IR-Blaster question [ In reply to ]
On 5/1/12, Richard Ferrara <sicrb25@bigpond.net.au> wrote:
> Alternatively, us irrecord with lirc stopped and the /etc/lirc* device to
> make a new remote file and send it to the lirc list.

Does that actually work? I didn't think most mceusb hardware was
capable of receiving arbitrary remote codes and sending them to the
host computer.

Eric
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: mceusb IR-Blaster question [ In reply to ]
Mine works.

On 02/05/2012, at 10:34 AM, Eric Sharkey wrote:

> On 5/1/12, Richard Ferrara <sicrb25@bigpond.net.au> wrote:
>> Alternatively, us irrecord with lirc stopped and the /etc/lirc* device to
>> make a new remote file and send it to the lirc list.
>
> Does that actually work? I didn't think most mceusb hardware was
> capable of receiving arbitrary remote codes and sending them to the
> host computer.
>
> Eric
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: mceusb IR-Blaster question [ In reply to ]
On 2012-05-01 20:34, Eric Sharkey wrote:
> On 5/1/12, Richard Ferrara <sicrb25@bigpond.net.au> wrote:
>> Alternatively, us irrecord with lirc stopped and the /etc/lirc* device to
>> make a new remote file and send it to the lirc list.
>
> Does that actually work? I didn't think most mceusb hardware was
> capable of receiving arbitrary remote codes and sending them to the
> host computer.

It does if it's a true mceusb receiver. See (and maybe more of this thread):

http://www.gossamer-threads.com/lists/mythtv/users/456660#456660
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: mceusb IR-Blaster question [ In reply to ]
Bus 005 Device 002: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 16
idVendor 0x0471 Philips (or NXP)
idProduct 0x0815 eHome Infrared Receiver
bcdDevice 0.00
iManufacturer 1 Philips
iProduct 2 eHome Infrared Transceiver
iSerial 3 PH00HSjb
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 0

On 03/05/2012, at 12:53 AM, Boleslaw Ciesielski wrote:

> On 2012-05-01 20:34, Eric Sharkey wrote:
>> On 5/1/12, Richard Ferrara <sicrb25@bigpond.net.au> wrote:
>>> Alternatively, us irrecord with lirc stopped and the /etc/lirc* device to
>>> make a new remote file and send it to the lirc list.
>>
>> Does that actually work? I didn't think most mceusb hardware was
>> capable of receiving arbitrary remote codes and sending them to the
>> host computer.
>
> It does if it's a true mceusb receiver. See (and maybe more of this thread):
>
> http://www.gossamer-threads.com/lists/mythtv/users/456660#456660
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users