LinHES Forums • View topic - PVR 150 IR Blaster Walkthrough (yes working!)

Board index KnoppMyth Hints & Tips

All times are UTC - 6 hours

PVR 150 IR Blaster Walkthrough (yes working!)

Page 5 of 8

[ 107 posts ]

Go to page Previous 1, 2, 3, 4, 5, 6, 7, 8 Next

Print view

Previous topic Next topic

Author

Message

mihanson

Post subject:

Posted: Mon Jan 09, 2006 3:04 pm

Joined: Sun Sep 25, 2005 3:50 pm

Posts: 1013

Location: Los Angeles

I forgot to mention that I tired:

Code:

# modprobe lirc_i2c

but that didn't help.

_________________
Mike
My Hardware Profile

Top

mihanson

Post subject:

Posted: Tue Jan 10, 2006 12:24 pm

Joined: Sun Sep 25, 2005 3:50 pm

Posts: 1013

Location: Los Angeles

I'm my own hero

I figured out that I was not setting up my pcHDTV HD-3000 first, like one is supposed to. So, I fixed my issue by setting up the HD-3000 with the backend stopped, reboot, then set up the PVR-150 with the backend running. Seemd to do the trick. I upgraded to R5A30 in the process as well. I have the same problem others are having with the remote, but I can use my keyboard to change channels, etc until I get around to setting up the crontab workaround.

_________________
Mike
My Hardware Profile

Top

aspain

Post subject:

Posted: Sat Jan 14, 2006 9:01 pm

Joined: Fri May 06, 2005 6:31 am

Posts: 79

Location: Spain

When I test irsend, I receive this error :
irsend SEND_ONCE blaster 0_41_KEY_POWER
irsend: command failed: SEND_ONCE blaster 0_41_KEY_POWER
irsend: hardware does not support sending

I use the lircd.conf include in : /etc/lircd.conf

Should I use my lircd.conf ?
http://pages.videotron.com/aspain/mytht ... lircd.conf

I use R5A26
And my receiver is a SA2000 (Scientific Atlanta 2000)

Top

xmorph

Post subject: Almost Working....

Posted: Mon Jan 16, 2006 10:47 am

Joined: Mon Jan 16, 2006 10:31 am

Posts: 18

Location: Calgary Alberta Canada

Hey guys, I love this community - I really do.

Here's where I'm at:

Installed Knoppmyth R5A30.1
Hooked everything up to my Star Choice Sat Reciever

I went to follow the install instructions at the begining of this guide and realized that this needs to be updated as most of the steps are already incorporated into R5A30.1 - which was a nice suprize indeed

I setup my lircd.conf with the proper reciever info - Here it is:

Code:

#
# this config file was automatically generated
# using lirc-0.5.5pre8 on Sun Apr 18 11:43:45 1999
#
# contributed by Jens Leuschner <leuschner@gmx.net>
#
# brand: Hauppauge
# model:
# supported devices: WinTV primo; WinTV pci; WinTV radio
#
# This config file will work with both homebrew receivers and
# original Hauppauge TV cards !!!
#
# This File was Modified by Me on Jan 15 2006 to help include
# support for the PVR-150 IR Blaster - Configured for use with a StarChoice
# Satellite reciever ONLY!

begin remote

name blaster
bits 32
flags RAW_CODES
eps 0
aeps 0
plead 0
gap 333333
repeat_bit 0

begin raw_codes
name 0
2149253120
name 1

2149253121
name 2
2149253122
name 3
2149253123
name 4
2149253124
name 5
2149253125
name 6
2149253126
name 7
2149253127
name 8
2149253128
name 9
2149253129
name POWER
2149253130
name CH_UP
2149253135
name CH_DOWN
2149253136
name CH_PREVIOUS
2149253139
name GUIDE
2149253147
name AV
2149253161
name ENTER
2149253163
end raw_codes

end remote

# this config file was automatically generated
# using lirc-0.7.0(any) on Sun Nov 28 20:25:09 2004
#
# contributed by
#
# brand: Hauppauge 350
# Created: G.J. Werler (The Netherlands)
# Project: Mythtv Fedora Pundit-R www.mythtvportal.com
# Date: 2004/11/28
# model no. of remote control: Hauppauge A415-HPG
# devices being controlled by this remote: PVR-350
#

begin remote

name Hauppauge_350
bits 13
flags RC5|CONST_LENGTH
eps 30
aeps 100

one 969 811
zero 969 811
plead 1097
gap 114605
toggle_bit 2


begin codes
Go 0x00000000000017BB
Power 0x00000000000017BD
TV 0x000000000000179C
Videos 0x0000000000001798
Music 0x0000000000001799
Pictures 0x000000000000179A
Guide 0x000000000000179B
Radio 0x000000000000178C
Up 0x0000000000001794
Left 0x0000000000001796
Left 0x0000000000001796
Right 0x0000000000001797
Down 0x0000000000001795
OK 0x00000000000017A5
Back/Exit 0x000000000000179F
Menu/i 0x000000000000178D
Vol+ 0x0000000000001790
Vol- 0x0000000000001791
Prev.Ch 0x0000000000001792
Mute 0x000000000000178F
Ch+ 0x00000000000017A0
Ch- 0x00000000000017A1
Record 0x00000000000017B7
Stop 0x00000000000017B6
Rewind 0x00000000000017B2
Play 0x00000000000017B5
Forward 0x00000000000017B4
Replay/SkipBackward 0x00000000000017A4
Pause 0x00000000000017B0
SkipForward 0x000000000000179E
1 0x0000000000001781
2 0x0000000000001782
3 0x0000000000001783
4 0x0000000000001784
5 0x0000000000001785
6 0x0000000000001786
7 0x0000000000001787
8 0x0000000000001788
9 0x0000000000001789
Asterix 0x000000000000178A
0 0x0000000000001780
# 0x000000000000178E
Red 0x000000000000178B
Green 0x00000000000017AE
Yellow 0x00000000000017B8
Blue 0x00000000000017A9
end codes

end remote

I can run:

Code:

/usr/local/bin/chan_change.sh 300

and everything comes out good. The IR Blaster lights up, my reciever changes channels everything is happy happy happy.

I have added

Code:

/usr/local/bin/chan_change.sh

into the setup section of step 4 in MythTV.

I try using my remote.... then I get nothing. I try to change chanels by inputting "3,0,0" and everything freezes for a few seconds, the IR Blaster dosn't light up and it just goes back to the channel it was on. I try using the Chanel Up/Down button and I get the same thing.... Any suggestions?

irsend is in both /usr/local/bin/ and /usr/bin/

**EDIT** Updated Info!

I rebooted and took a look in /var/log/syslog/ and I see the following:

Code:

Jan 16 09:59:29 mythtv lircd-0.7.2pvr150[2722]: accepted new client on /dev/lircd
Jan 16 09:59:29 mythtv lircd-0.7.2pvr150[2722]: error processing command: SEND_ONCE blaster 5
Jan 16 09:59:29 mythtv lircd-0.7.2pvr150[2722]: unknown remote: "blaster"
Jan 16 09:59:29 mythtv lircd-0.7.2pvr150[2722]: removed client
Jan 16 09:59:29 mythtv lircd-0.7.2pvr150[2722]: accepted new client on /dev/lircd
Jan 16 09:59:29 mythtv lircd-0.7.2pvr150[2722]: error processing command: SEND_ONCE blaster 0
Jan 16 09:59:29 mythtv lircd-0.7.2pvr150[2722]: unknown remote: "blaster"
Jan 16 09:59:29 mythtv lircd-0.7.2pvr150[2722]: removed client
Jan 16 09:59:29 mythtv lircd-0.7.2pvr150[2722]: accepted new client on /dev/lircd
Jan 16 09:59:29 mythtv lircd-0.7.2pvr150[2722]: error processing command: SEND_ONCE blaster 0
Jan 16 09:59:29 mythtv lircd-0.7.2pvr150[2722]: unknown remote: "blaster"
Jan 16 09:59:29 mythtv lircd-0.7.2pvr150[2722]: removed client

MythTV is trying to change the reciever to Channel 500 on startup as thats what I set it up to do..... but I'm getting this error. Anyone throw me a bone?

_________________
P4 2.8 GHZ
2 gig DDR RAM
Nvidia FX5200
2 x 160 gig PATA HD
PVR 150 (With IR Blaster)
Starchoice Satellite (Canada)

Top

mihanson

Post subject:

Posted: Mon Jan 16, 2006 11:07 am

Joined: Sun Sep 25, 2005 3:50 pm

Posts: 1013

Location: Los Angeles

Quote:

I have added Code:
/usr/local/bin/chan_change.sh
into the setup section of step 4 in MythTV.

I believe this should be in "quotes." It should look like this in your MythTV setup field:

Code:

"/usr/local/bin/chan_change.sh"

Did you set the permissions on the file to allow user mythtv to execute?

Code:

# chmod 755 /usr/local/bin/chan_change.sh

_________________
Mike
My Hardware Profile

Top

xmorph

Post subject:

Posted: Mon Jan 16, 2006 11:21 am

Joined: Mon Jan 16, 2006 10:31 am

Posts: 18

Location: Calgary Alberta Canada

hmmm... I wondered about the qoutes. I'll try that again tonight when I get home. Yes the permissions were set properly on that script. Hopefully I can get this going, it's the only thing I was waiting for

And that shitty windows PVR Software I was using was really grating on my nerves. :roll:

_________________
P4 2.8 GHZ
2 gig DDR RAM
Nvidia FX5200
2 x 160 gig PATA HD
PVR 150 (With IR Blaster)
Starchoice Satellite (Canada)

Top

xmorph

Post subject: wewt!

Posted: Mon Jan 16, 2006 7:38 pm

Joined: Mon Jan 16, 2006 10:31 am

Posts: 18

Location: Calgary Alberta Canada

Good stuff that fixed it, thanks guys!

_________________
P4 2.8 GHZ
2 gig DDR RAM
Nvidia FX5200
2 x 160 gig PATA HD
PVR 150 (With IR Blaster)
Starchoice Satellite (Canada)

Top

j0ly

Post subject:

Posted: Wed Jan 18, 2006 11:31 pm

Joined: Sat Feb 05, 2005 3:26 pm

Posts: 121

Location: Calgary, Alberta - Canada!

awesome to hear people have it working fine! im really happy for you guys, and im happy this is working for so many people... i have yet to upgrade to 30.1, so ill be doing that on the weekend, and seeing how well it works on my setup, will report if there is any problems.

Top

xmorph

Post subject:

Posted: Thu Jan 19, 2006 4:12 pm

Joined: Mon Jan 16, 2006 10:31 am

Posts: 18

Location: Calgary Alberta Canada

Hey Joly,

when you upgrade to 30.1 make sure you also upgrade ivtv to 0.4.2 afterwards, it has a bunch of fixes for the pvr-150 in the newest version released a few days ago.

I have mine running, and I'm not getting lockups on the remote any more.

_________________
P4 2.8 GHZ
2 gig DDR RAM
Nvidia FX5200
2 x 160 gig PATA HD
PVR 150 (With IR Blaster)
Starchoice Satellite (Canada)

Top

Dan The Man

Post subject:

Posted: Tue Jan 24, 2006 3:52 pm

Joined: Tue Jan 24, 2006 3:31 pm

Posts: 1

I'm new to these forums and a relative newbie to linux. I realize this forum is for KnoppMyth users, but hopefully you will be kind to a FC4 user

I followed the steps listed in this post and can not seem to get the blaster to work with my new pvr 150. The receiver/remote are working ok. Hopefully someone on here can help.

I began with the lircd.conf file provided by Mark at http://www.blushingpenguin.com/mark/blog/?p=24. I then ran the send_power_new script. The good news is that the led blinks. The bad news is that I get an irsend: timeout error. I used "lircd -n" so I could see the output and it gave

Code:

# lircd -n
 lircd: lircd(hauppauge_pvr150) ready
 lircd: accepted new client on /dev/lircd
 lircd: write failed
 lircd: Bad address
 lircd: error processing command: send_once blaster 0_0_key_power
 lircd: transmission failed
 lircd: removed client

I also looked at dmesg and it gives the following set of messages:

Code:

$dmesg
   lirc_pvr150: i2c_master_recv failed with 1
   lirc_pvr150: sending to the IR transmitter chip failed, trying reset
   lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version 1.3.0
   lirc_pvr150: i2c_master_recv failed with 1
   lirc_pvr150: sending to the IR transmitter chip failed, trying reset
   lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version 1.3.0
   lirc_pvr150: IR TX chip never got ready: last i2c_master_send failed with -121
   lirc_pvr150: sending to the IR transmitter chip failed, trying reset
   lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version 1.3.0
   lirc_pvr150: i2c_master_recv failed with 1
   lirc_pvr150: sending to the IR transmitter chip failed, trying reset
   lirc_pvr150: unable to send to the IR chip after 3 resets, giving up
   lirc_pvr150: i2c_master_send failed with -121
   lirc_pvr150: polling the IR receiver chip failed, trying reset

I did find that some of the power codes did turn the cable box on and off, but because of the timeout error, the signal got sent multiple times and the receiver would power off and then back on again. I tried sending just a channel number, but the same thing occurred and it got confused. For example 0_85_key_4 sent the receiver 44 (pause) 4.

--------------------------------------------------------------------------
I know that my cable box is a motorola dct2000 series, so I figured I would just try loading that remote into the lircd.conf file.
Here is the results of trying irsend with the dct2000 remote:

Code:

$ irsend send_once "dct2000" "POWER"
   irsend: command failed: send_once dct2000 POWER
   irsend: transmission failed

and again here is the lircd output (note that the problem is now a "protocol error" instead of a "bad address".

Code:

# lircd -n
   lircd: lircd(hauppauge_pvr150) ready
   lircd: accepted new client on /dev/lircd
   lircd: write failed
   lircd: Protocol error
   lircd: error processing command: send_once dct2000 Power
   lircd: transmission failed
   lircd: removed client

and the dmesg

Code:

$ dmesg
   lirc_pvr150: failed to get data for code 0, key 9036 -- check lircd.conf entries

I had no indication that the led was blinking. This makes me wonder if the remote needs to be included somewhere when compiling the lirc_pvr150 module?

------------------------------------------------------------------------
Just to see if any remote could send, I tried using the greyHauppauge remote found here http://wilsonet.com/mythtv/lircd-g3.conf.txt to send a power command. It seemingly worked, although I still did not observe the led blinking (could it have just been too fast?).

Code:

$irsend send_once "grayHauppauge" "Power"
//NO OUTPUT

# lircd -n
   lircd: lircd(hauppauge_pvr150) ready
   lircd: accepted new client on /dev/lircd
   lircd: removed client
//APPEARS TO HAVE WORKED FINE

$dmesg
//NO NEW LINES

------------------------------------------------------------------------
At this point I put the original lircd.conf file back and tried to send with the three hauppauge remotes that are in it. All three failed with the "protocol error" and the dmesg was similar to when i tried the dct2000, but the key was slightly different:

Code:

lirc_pvr150: failed to get data for code 0, key 960 -- check lircd.conf entries (for the hauppauge)
lirc_pvr150: failed to get data for code 0, key 1097 -- check lircd.conf entries (for the hauppauge_pvr)
lirc_pvr150: failed to get data for code 0, key 1097 -- check lircd.conf entries (for the hauppauge_350)

I noticed the key is the number listed as "plead", for the dct2000 it is the first number listed after "header"

------------------------------------------------------------------------
In case it helps anyone, here is the output from my dmesg about the loading of ivtv and lirc_pvr150

Code:

ivtv:  ==================== START INIT IVTV ====================
ivtv:  version 0.4.2 (tagged release) loading
ivtv:  Linux version: 2.6.14-1.1656_FC4 686 REGPARM 4KSTACKS gcc-4.0
ivtv:  In case of problems please include the debug info between
ivtv:  the START INIT IVTV and END INIT IVTV lines, along with
ivtv:  any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected WinTV PVR 150 card (cx23416 based)
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
tveeprom 1-0050: Hauppauge model 26132, rev C599, serial# 8911766
tveeprom 1-0050: tuner model is TCL 2002N 5H (idx 99, type 50)
tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 1-0050: audio processor is CX25841 (idx 35)
tveeprom 1-0050: decoder processor is CX25841 (idx 28)
tveeprom 1-0050: has no radio, has IR remote
cx25840 1-0044: ivtv driver
cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 1-0044: loaded v4l-cx25840.fw firmware (13353 bytes)
ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
wm8775 1-001b: ivtv driver
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02040024
ivtv0 warning: Encoder Firmware can be buggy, use version 0x02040011 or 0x02050032.
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner: type set to 50 (TCL 2002N) by ivtv i2c driver #0
ivtv0: Initialized WinTV PVR 150, card #0
ivtv:  ====================  END INIT IVTV  ====================
lirc_dev: IR Remote Control driver registered, at major 61
lirc_pvr150: bt878 #0 [sw]: no devices found
lirc_pvr150: chip found with RX and TX
ivtv0: i2c attach to card #0 ok [client=Hauppauge PVR150 IR RX, addr=71]
ivtv0: i2c attach to card #0 ok [client=Hauppauge PVR150 IR TX, addr=70]
lirc_dev: lirc_register_plugin: sample_rate: 0
lirc_pvr150: firmware of size 229018 loaded
lirc_pvr150: 608 codesets loaded
lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version 1.3.0

Top

ripley

Post subject: Messed up and cant explain myself

Posted: Sat Feb 04, 2006 12:02 pm

Joined: Wed Dec 28, 2005 8:43 am

Posts: 8

Location: San Antonio

I messed something up.
I had irsend working and edited the lircd.conf for my specific Dish Receiver. I also created the channel change script and made it executable. After this, I tried irsend again reflecting the changes but it did not recognize them. Since the pre change "irsend SEND_ONCE blaster 1_28_KEY_POWER" still was working , I assumed I needed to restart the system in order to load the changed configuration.

After reboot all IR stopped working and the PVR 150's stopped working altogether. I checked the syslog and found that two firmware files seemed to be missing or were now needed where not needed before. They are firmware v4l-cx25840.fw & v4l-cx2341x-enc.fw.

What in the world did I do wrong? I'll dig around and try to find these two files and load them where they should be "hotplug/firmware". Any hints?

Did I miss a step? Man I was soooo close!

_________________
Man, I thought I was confused but I've learned enough to see that I really have no clue.

Top

j0ly

Post subject:

Posted: Sat Feb 04, 2006 12:06 pm

Joined: Sat Feb 05, 2005 3:26 pm

Posts: 121

Location: Calgary, Alberta - Canada!

nope. if you upgraded to ivtv4.2.0 then this is correct, you need to put the firmware in a new location, and rename them...

read here for more info

http://www.ivtvdriver.org/index.php/Fir ... e_Firmware

- Scott

Top

tjc

Post subject:

Posted: Sat Feb 04, 2006 12:41 pm

Joined: Thu Mar 25, 2004 11:00 am

Posts: 9551

Location: Arlington, MA

There is a more streamlined set of steps on the CompileIvtv page on the wiki.
http://www.knoppmythwiki.org/index.php?page=CompileIvtv

Top

j0ly

Post subject:

Posted: Sat Feb 04, 2006 12:43 pm

Joined: Sat Feb 05, 2005 3:26 pm

Posts: 121

Location: Calgary, Alberta - Canada!

nice!

Top

bigbro

Post subject: I have experienced similar Firmware problems.

Posted: Sat Feb 04, 2006 2:29 pm

Joined: Sat Dec 24, 2005 11:33 am

Posts: 400

Location: Kitsap Peninsula, Wa., United States

I have attempted this upgrade twice since building my pvr. Both occasions I came to the same point as described here:

Quote:

After reboot all IR stopped working and the PVR 150's stopped working altogether. I checked the syslog and found that two firmware files seemed to be missing or were now needed where not needed before. They are firmware v4l-cx25840.fw & v4l-cx2341x-enc.fw.

In research over at IVTV they seem to be discussing an issue with HotPlug not being Ready at the time it is needed by the IVTV. They have taken some steps to change how the Card gets the firmware listed. So far I have not tried that being a Noob and not completely understanding what they were doing.

So since my Wife has already found "My New Toy" very useful. I have returned it to the IVTV .4.0 setup. I have a decent Wireless M$ keyboard and mouse that I can work with until I get the remote fully functional.

Just wanted to reflect my experience here. Hoping we can soon find a fix as I don't belive my setup is the only one.

Andy

_________________
KnoppMyth R5.5
MBE: AMD64 3400+, K8N Neo4 Plat., 1Gig, Asus Extreme N6200, 320G pata, 2x320Gsata, 750Gsata, PVR-150 Retail w/Blaster
SBE: AMD XP2000, GA 7ZMMH, 1 Gig, XFX 256M 6200, 20 Gig, PVR-150 Retail w/Blaster
SBE: AMD Dur1800, 512M, PVR500

Top

Page 5 of 8

[ 107 posts ]

Go to page Previous 1, 2, 3, 4, 5, 6, 7, 8 Next

Board index KnoppMyth Hints & Tips

All times are UTC - 6 hours

Who is online

Users browsing this forum: No registered users and 8 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum