| Author |
Message |
|
ripley
|
 Posted: Mon Feb 06, 2006 9:50 pm |
|
|
Joined: Wed Dec 28, 2005 8:43 am
Posts: 8
Location:
San Antonio
|
|
Sorry for not writing earlier. I've been busy using it! Yes it's working based on the last instructions for correcting a few scripts and installing the firmware.
Thank you one and all!
Now, to read and learn more about this nifty package.
Marc
_________________
Man, I thought I was confused but I've learned enough to see that I really have no clue.
|
|
| Top |
|
 |
|
ed3120
|
Posted: Tue Mar 14, 2006 6:36 pm |
|
|
Joined: Sun Dec 04, 2005 1:44 pm
Posts: 403
Location:
Central NJ
|
|
I set this up with a PVR150 and /usr/local/bin/chan_change.sh works perfectly from a prompt, but when I change channels in Myth, the IR blaster keeps changing my Comcast box to weird arbitrary channels.
Yes, I have "/usr/local/bin/chan_change.sh" in quotes as my channel change command and yes I did CHMOD 755 the file. I've tried it from a prompt as use mythtv and I could change the channel properly.
What config could I have wrong in Myth?
Do I need to put anything specific in these config boxes?
Preset tuner to channel: ____
Starting channel: ______
_________________
Currently running: R5.5, HD5000 x 2, PVR150, Athlon 64 3000+, Chaintech VNF4, 1GB RAM, 2 x 250GB in LVM, MSI NX6200TC -> AA 9A60 -> HDTV
|
|
| Top |
|
|
|
tjc
|
Posted: Tue Mar 14, 2006 7:20 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Sorry my psychic remote viewing seems to be out of whack at the moment, just how did you have that PVR card hooked up to the cable box again? 
|
|
| Top |
|
|
|
ed3120
|
Posted: Tue Mar 14, 2006 8:30 pm |
|
|
Joined: Sun Dec 04, 2005 1:44 pm
Posts: 403
Location:
Central NJ
|
Damn, my telepathic skills must not be working tonight. 
The comcast cable box connects to the input of the PVR150 via SVIDEO. The IRBlaster on the PVR150 is taped to the IR receiver on the Comcast box.
_________________
Currently running: R5.5, HD5000 x 2, PVR150, Athlon 64 3000+, Chaintech VNF4, 1GB RAM, 2 x 250GB in LVM, MSI NX6200TC -> AA 9A60 -> HDTV
|
|
| Top |
|
|
|
tjc
|
Posted: Tue Mar 14, 2006 9:30 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
Then, no, you don't need anything in either of those fields. The first one is for the case where you're feeding a signal generated on channel 3 or 4 by the cable box into the tuner of your TV card. Using S-Video bypasses the tuner however. The second one is just to set the tuner to some known starting channel. You can put your favorite channel in there, and that way MythTV will default to that when you reboot the box (unless something else overrides it).
|
|
| Top |
|
|
|
Dinki
|
Posted: Tue Mar 21, 2006 2:45 pm |
|
|
Joined: Fri Dec 26, 2003 2:25 pm
Posts: 244
|
I am running r5v30.2 using a PVR150. I followed all the steps by the letter as outlined. When I get to this part:
j0ly wrote: Check everything is working so far:Quote: modprobe lirc_dev debug=1 && modprobe lirc_pvr150 debug=1 and check the syslog output file to see if it loaded ok Quote: nano /var/log/syslog The output should be at the bottom of the syslog, pgdown till you see it, it should look something like this: Quote: Aug 28 02:09:11 soapbox kernel: lirc_pvr150: chip found with RX and TX
Aug 28 02:09:11 soapbox kernel: ivtv: i2c attach [client=Hauppauge PVR150 IR RX,
ok]
Aug 28 02:09:11 soapbox kernel: ivtv: i2c attach [client=Hauppauge PVR150 IR TX,
ok]
Aug 28 02:09:11 soapbox kernel: lirc_dev: lirc_register_plugin: sample_rate: 0
Aug 28 02:09:11 soapbox udev[5221]: creating device node ‘/dev/lirc0′
Aug 28 02:09:11 soapbox kernel: lirc_pvr150: firmware of size 20927 loaded
Aug 28 02:09:11 soapbox kernel: lirc_pvr150: 575 codesets loaded
Aug 28 02:09:11 soapbox kernel: lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version 1.3.0
My output looks like this instead:
Code: Mar 21 14:24:53 mythtv kernel: lirc_dev: IR Remote Control driver registered, at major 61
Mar 21 14:24:53 mythtv kernel: lirc_pvr150: probe 0x70 @ ivtv i2c driver #0: yes
Mar 21 14:24:53 mythtv kernel: lirc_pvr150: probe 0x71 @ ivtv i2c driver #0: yes
Mar 21 14:24:53 mythtv kernel: lirc_pvr150: chip found with RX and TX
Mar 21 14:24:53 mythtv kernel: ivtv: i2c attach to card #0 ok [client=Hauppauge PVR150 IR RX, addr=71]
Mar 21 14:24:53 mythtv kernel: ivtv: i2c attach to card #0 ok [client=Hauppauge PVR150 IR TX, addr=70]
Mar 21 14:24:53 mythtv kernel: lirc_dev: lirc_register_plugin: sample_rate: 0
Mar 21 14:24:53 mythtv kernel: lirc_dev: plugin lirc_pvr150 registered at minor number = 0
Mar 21 14:24:53 mythtv kernel: lirc_pvr150: poll thread started
Mar 21 14:24:54 mythtv kernel: lirc_pvr150: firmware of size 209327 loaded
Mar 21 14:24:54 mythtv kernel: lirc_pvr150: 575 codesets loaded
Mar 21 14:24:54 mythtv kernel: lirc_pvr150: 01 60 00 01 bf<7>lirc_pvr150: 05 02 00 22 1a<7>lirc_pvr150: 09 fe 06 0e 43<7>lirc_pvr150: 0d 98 2e 56 53<7>lirc_pvr150: 11 6e 99 94 5d<7>lirc_pvr150: 15 46 70 30 6a<7>lirc_pvr150: 19 be 6e a3 56<7>lirc_pvr150: 1d ab 4d 0d 67<7>lirc_pvr150: 21 a6 72 0d 0f<7>lirc_pvr150: 25 ee 68 fa 47<7>lirc_pvr150: 29 fa 36 01 0f<7>lirc_pvr150: 2d 8b 7b fb 6c<7>lirc_pvr150: 31 b2 74 ef 05<7>lirc_pvr150: 35 bd 63 af 35<7>lirc_pvr150: 39 fb 5d 22 2a<7>lirc_pvr150: 3d 38 58 49 31<7>lirc_pvr150: 41 50 6b fd 5f<7>lirc_pvr150: 45 5e 02 f0 1f<7>lirc_pvr150: 49 48 67 84 66<7>lirc_pvr150: 4d b5 08 66 23<7>lirc_pvr150: 51 b3 6c 1e 2d<7>lirc_pvr150: 55 99 1d e8 62<7>lirc_pvr150: 59 e6 0a 45 39<7>lirc_pvr150: 5d 67 6c 9f 76<7>lirc_pvr150: 61 00 00 00 76<6>lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version 1.3.0
Mar 21 14:24:54 mythtv kernel: lirc_pvr150: probe 0x70 @ ivtv i2c driver #1: no
Mar 21 14:24:54 mythtv kernel: lirc_pvr150: probe 0x71 @ ivtv i2c driver #1: no
Mar 21 14:24:54 mythtv kernel: lirc_pvr150: ivtv i2c driver #1: no devices found
Mar 21 14:24:54 mythtv kernel: lirc_pvr150: poll thread ended
Any ideas on what's going on?
|
|
| Top |
|
|
|
Rsx024
|
Posted: Mon Mar 27, 2006 4:51 pm |
|
|
Joined: Mon Mar 06, 2006 2:14 pm
Posts: 43
|
|
will this guided work with r5b7?
|
|
| Top |
|
|
|
ed3120
|
Posted: Sat Jan 06, 2007 8:54 pm |
|
|
Joined: Sun Dec 04, 2005 1:44 pm
Posts: 403
Location:
Central NJ
|
|
Are there any scripts to automate this?
_________________
Currently running: R5.5, HD5000 x 2, PVR150, Athlon 64 3000+, Chaintech VNF4, 1GB RAM, 2 x 250GB in LVM, MSI NX6200TC -> AA 9A60 -> HDTV
|
|
| Top |
|
|
|
cecil
|
Posted: Sun Jan 07, 2007 4:57 am |
|
 |
| Site Admin |
Joined: Fri Sep 19, 2003 6:37 pm
Posts: 2659
Location:
Whittier, Ca
|
|
The 150's remote and blaster have been working out the box for some time now. If you have a 150 w/ a USB, I don't know the status of this...
|
|
| Top |
|
|
|
nesredep
|
Posted: Sun Jan 14, 2007 1:01 pm |
|
|
Joined: Sun Oct 29, 2006 11:38 pm
Posts: 6
|
cecil wrote: The 150's remote and blaster have been working out the box for some time now. If you have a 150 w/ a USB, I don't know the status of this...
Seems like the only way you can input the type of settop box is by answering "yes" to "do you have a serial ir blaster". Is that the correct thing to do when you have the combined remote/blaster plugged into a PVR150? If not, which script needs changing to identify the type of settop box?
John
|
|
| Top |
|
|
|
Greg Frost
|
Posted: Sun Jan 14, 2007 2:25 pm |
|
|
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location:
Adelaide, Australia
|
nesredep wrote: cecil wrote: The 150's remote and blaster have been working out the box for some time now. If you have a 150 w/ a USB, I don't know the status of this... Seems like the only way you can input the type of settop box is by answering "yes" to "do you have a serial ir blaster". Is that the correct thing to do when you have the combined remote/blaster plugged into a PVR150? If not, which script needs changing to identify the type of settop box? John That wont work. Look in /usr/local/share/knoppmyth/remotes/irblaster. If there is a directory for your STB, append the irblasterd.conf from that directory to /etc/lirc/lircd.conf
If that works, let me know and I'll look at including this step in the lirc-config.sh script.
|
|
| Top |
|
|
|
nesredep
|
Posted: Sun Jan 14, 2007 4:18 pm |
|
|
Joined: Sun Oct 29, 2006 11:38 pm
Posts: 6
|
Greg Frost wrote: That wont work. Look in /usr/local/share/knoppmyth/remotes/irblaster. If there is a directory for your STB, append the irblasterd.conf from that directory to /etc/lirc/lircd.conf
If that works, let me know and I'll look at including this step in the lirc-config.sh script.
Didn't seem to work. My STB is in the list (the Explorer 2000). Just to be sure (after all my uninformed tinkering) I did a fresh install of R5E50.
I used cat ..../irblasterd.conf >> .....lircd.conf to paste the files together.
I don't have the settop box right at this moment, so I judged it as "not working" by looking for red flashes from the LED (and not seeing any).
When I type irsend SEND_ONCE blaster 0_78_KEY_POWER I do get red light flashing from the transmitter.
Feels like the answer is very close--any suggestions of what else I can try or check?
John
|
|
| Top |
|
|
|
Marshallaw
|
Posted: Sun Mar 18, 2007 1:09 pm |
|
|
Joined: Wed Feb 28, 2007 10:31 am
Posts: 9
|
|
Ok,
I used the scrip, found the IR, setup the chan_change.sh...everything works great except for the "0" input. I have all the other digits working just not that one..any ideas?
|
|
| Top |
|
|
|
Marshallaw
|
Posted: Sun Mar 18, 2007 1:11 pm |
|
|
Joined: Wed Feb 28, 2007 10:31 am
Posts: 9
|
|
Ok,
I used the scrip, found the IR, setup the chan_change.sh...everything works great except for the "0" input. I have all the other digits working just not that one..any ideas?
|
|
| Top |
|
|
|
Marshallaw
|
Posted: Mon Mar 19, 2007 12:31 pm |
|
|
Joined: Wed Feb 28, 2007 10:31 am
Posts: 9
|
|
Forget my last post, I was able to get "0" to work by adding KEY_$digit and making sure that my naming convention under lircd.conf was name KEY_0 etc.
Thanks for the most useful tutorial!!
|
|
| Top |
|
|
View unanswered posts
View active topics
KnoppMyth 
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register