Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users
mceusb IR-Blaster question
 

Index | Next | Previous | View Flat


jbhuber at judahnet

May 1, 2012, 6:25 AM


Views: 1313
Permalink
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 [at] rajidae>, Martin Blatter
<martin_a_blatter [at] yahoo>, Dan Conti <dconti [at] acm>
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


--

Subject User Time
mceusb IR-Blaster question jbhuber at judahnet May 1, 2012, 6:25 AM
    Re: mceusb IR-Blaster question eric at lisaneric May 1, 2012, 6:40 AM
    Re: mceusb IR-Blaster question sicrb25 at bigpond May 1, 2012, 3:51 PM
    Re: mceusb IR-Blaster question gary.buhrmaster at gmail May 1, 2012, 5:13 PM
    Re: mceusb IR-Blaster question eric at lisaneric May 1, 2012, 5:34 PM
    Re: mceusb IR-Blaster question sicrb25 at bigpond May 1, 2012, 5:36 PM
    Re: mceusb IR-Blaster question bc-mythtv at comcast May 2, 2012, 7:53 AM
        Re: mceusb IR-Blaster question sicrb25 at bigpond May 2, 2012, 3:40 PM

  Index | Next | Previous | View Flat
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.