The instructions for installing the IR blaster suggest that you should be able to see the light (http://www.blushingpenguin.com/mark/blog/?p=24) when executing the send_power_now (and you see the echo on screen) to find the key_code. I don't see the light (no pun intended )

Before I send this back to Hauppauge, does everyone that uses this "see" the blinking blaster? Most remotes you can't see the light coming from them. :lo

What version of Myth are you installing? If it is the lastest version, R5E50, then you are not alone. I just installed the version from scratch and my PVR150 IR receiver works like a charm with the silver remote but the blaster will not work at all. The blaster worked fine with some minor tweaking with ver R5D1. I'm going to start a new thread to try to come up with a procedure to get the blaster to work with set top boxes.

As for the light, I cut mine off and stole a regular led from an old remote I had kicking around. A regular LED will light up so you know if you are sucessful in getting it to work and works %100 better then the one that is installed with the PVR150. If you ever got to a point where you do not have to trouble shoot the blaster, you could install an IR LED (which you could salvage from the same remote you took the red LED from) which works even better.[/img]

Here's what I did to get the IR remote and IR blaster of a PVR-150 non MCE working in R5E50. This is the one where the IR receiver and IR blaster use what looks like a head phone jack to plug into the PVR card. I've had problems where I couldn't push the connector in all the way because the metal from the case was in the way. I think the new cables come with part of the plastic cut on an angle so that it seats right.

During installation when picking the remote I chose 17 for Hauppauge and then d for PVR-150 w/ transmitter and receiver. When the install finishes I was able to use the remote in the frontend. I then had to edit my /etc/lirc/lircd.conf file and change the names corresponded to my receivers (set top box) codes. eg. change "name 1_27_KEY_1" to "name 1". I did this for all the 1_27_KEY_* lines. I then changed the /usr/local/bin/change-channel-lirc.sh script. Change the line REMOTE_NAME="can't remember" to REMOTE_NAME=blaster. The blaster name comes from the lircd.conf file. I was then able to do sh change-channel-lirc.sh 300 and my IR blaster would flash.

Hope this helps.

First question is how did you know that 1_27_KEY_* referred to your set top box? How did you aquire that info?

The box I'm using is the Motorla DCT2524.

Second,



So after deleting the 1_27_KEY_* parts did your file look like this when you completed the changes?



The rest of the file is there too; it's just too huge to paste!

I discovered (by using the send_power_now script) that my code is 1_28. It worked very well. And - I can definately see the light blink.

But since it's not working, did you start with the lircd.conf file from Step 2 (http://knoppmythwiki.org/index.php?page ... hSetTopBox) Where would you add the 1_28_Key? Can you post your lircd.conf and tell us what your key was?
begin raw_codes
name 0
2149318656
name 1
2149318657
name 2
2149318658
name 3
2149318659
etc...

Or did you start with this style from (http://www.blushingpenguin.com/mark/lmilk/lircd.conf)

name 1_0_KEY_0
2147483648
name 1_0_KEY_1
2147483649
name 1_0_KEY_2
2147483650
name 1_0_KEY_3
2147483651
name 1_0_KEY_4
2147483652
name 1_0_KEY_5
2147483653
name 1_0_KEY_6
2147483654
name 1_0_KEY_7

I started with the file from the install. The file has the codes for I'm guessing most set top boxes. If the send_power_now script gave you 1_28 then go edit out the 1_28_KEY_ part in the lircd.conf file. Make sure it's the only group of codes that you edited in the blaster section. So your section should look like this.
I forgot to say you need to restart lirc to get the changes to work but I think you already figured that out. Try out the change-channel-lirc.sh script with some channel after it and you should see the blaster flash. Hopefully I'm making sense.

I've been following this thread with great interest because I have the same problem. So far, I read that you have the LED blinking because YOU manually ran a script file. But I don't actually see anybody saying that they got this to happen by pushing the buttons on a Hauppauge remote!

I am getting the impression that nowhere in the Knoppmyth system does any program segment ever call on the change-channel-lirc.sh script. Or am I wrong?!?!?

I notice people in other threads talking about change-channel and channel_change and various permutations so it's easy to imagine that somewhere there was a slipup.

Can anybody confirm that this latest Knoppmyth actually calls on this channel script when the viewer pushes the buttons on the remote?

John

My install is KnoppMyth R5D1

If you have a Hauppauge PVR-150 (like me), it's actually pretty straightforward to follow:
http://www.blushingpenguin.com/mark/lmilk/lircd.conf
- it directs you to a file you can download (send_power_now). When you type this from the terminal (as root; ie [code]su[/code] then [code]password[/code]), it steps through about 600 key codes, echos which key code is being sent, waits for a second and sends the next.
- Once you find the key code that turns your settop box off, then you go into the lircd.conf file and delete all the (non-28 in my case) other codes, as well as the 1_key_28 lines (I haven't confirmed this yet).

If you have a homebrew style blaster, it's most likely a serial blaster. That is, it plugs into your com port (mine plugs into a small phono jack in the pvr-150 card). The directions to follow are a bit different, and I'm not the best one to ask.

We're talking about the IR blaster which has nothing to do "directly" with the remote. It's a little IR transmitter (tear drop shape) that you stick on the front of your set top box. You need to place it right over the IR receiver that's inside the box itself. The remote only works with the IR receiver that plugs into the card in your PC. It's the round grey thing that has a little dark plastic "IR receiver" in the middle. The way the change-channel-lirc.sh script works is you add it in the mythtv-setup. There's an "external channel change script" box that you need to enter

So the way it works is mythtv receives the key presses from your remote. If your in the watch tv section when you type in the numbers to change a channel myth sends those numbers off to the change-channel-lirc.sh script which then sends the right codes out to the IR blaster stuck on the front of your set top box. If you have the guide up and have jump to channel set in the frontend setup you can press the numbers on your remote and it will jump to that channel in the guide. The numbers you've pressed in this case don't get sent to the script and the channel doesn't get changed. If you've set the frontend to change to the selected channel when pressing enter instead of bringing up the record menu myth figures out what channel is selected and sends the right numbers off to the script which then changes the channel on your set top box. Hopefully this clears things up, but if not just let us know.

I'm using R5E50, and my blaster is the Hauppauge blaster that comes with PVR150. I understand about modifying the config file (codes), but my question is:
What actually fires off the change-channel script???
I can do it manually from a terminal window, and the irblaster light flashes.
However, when running the mythtv frontend, I press buttons on the remote and I can "browse" channels on the monitor. BUT...no matter what I press, the light in the blaster never blinks. So what is it that actually calls the change-channel script? Is something missing in the R5E50 setup?

John

I think I understand all that. I have exactly the same blaster setup that you have. It was your earlier message that got my attention. You ended by saying that when you typed the change-channel script with 300, you could get the light to flash.

Ok, I can also get the light to flash by typing the script name. HOWEVER, I can't get the light to flash by changing channels with the remote. I gather you can.

I assume that if I'm watching a channel on the monitor, and I push UP-arrow, UP-arrow, and I see the different channels with program info, and I see "browsing" on the screen, THEN....when I hit the Ok button on the remote, the light on the blaster should flash so that the STB will change to the selected channel. You're using R5E50, and that happens for you?

As for the change-channel script, the only change is setting the remote name to blaster? (With or without quotes?) I appreciate any help!

John

You need to add the script to your backend setup. Run

from the shell and add the script to the Input connections section where you associate an input to a listing. There's a box to put the script in once you choose the input. That should be all you're missing.



Without the quotes. You'll find the name 'blaster' in your lircd.conf file.

The names in the two files have to match.

Yes, that was what I was missing. I was going crazy trying to figure out what fired off the script. My thanks for turning on the light bulb for me--thanks to all.

John

Can't figure out why this appears to be working, but no light blinking:

root@mythtv:/usr/local/bin# change_channel 200
channel changing 200

1. The change_channel script is unchanged from the instructions, and is in /usr/local/bin
2. I think my lircd.conf file (below) is correct and permissions wide open

root@mythtv:/etc# ls -alt lircd.conf
lrwxrwxrwx 1 root root 20 Jan 13 14:39 lircd.conf -> /etc/lirc/lircd.conf

3. The send_power_new makes the light blink

My lircd.conf file in /etc:
[code]
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
2149318656
name 1
2149318657
name 2
2149318658
name 3
2149318659
name 4
2149318660
name 5
2149318661
name 6
2149318662
name 7
2149318663
name 8
2149318664
name 9
2149318665
name POWER
2149318666
name CH_UP
2149318671
name CH_DOWN
2149318672
name MUTE
2149318673
name VOL_DOWN
2149318674
name CH_PREVIOUS
2149318675
name VOL_UP
2149318676
name DISPLAY
2149318677
name EXIT
2149318680
name GUIDE
2149318683
name SELECT
2149318686
name AV
2149318697
name ENTER
2149318699
name MENU
2149318703
name MUP
2149318704
name MDOWN
2149318705
name MLEFT
2149318706
name MRIGHT
2149318707
end raw_codes
end remote

begin remote
[b]name Hauppauge_350[/b]
bits 13
flags RC5|CONST_LENGTH
eps 30
aeps 100

one 969 811
zero 969 811
plead 1097
gap 114605
# gap 200000
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
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
[/code]









[b][/b]

Can't figure out why this appears to be working, but no light blinking:

root@mythtv:/usr/local/bin# change_channel 200
channel changing 200

1. The change_channel script is unchanged from the instructions, and is in /usr/local/bin
2. I think my lircd.conf file (below) is correct and permissions wide open

root@mythtv:/etc# ls -alt lircd.conf
lrwxrwxrwx 1 root root 20 Jan 13 14:39 lircd.conf -> /etc/lirc/lircd.conf

3. The send_power_new makes the light blink

My lircd.conf file in /etc:
[code]
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
2149318656
name 1
2149318657
name 2
2149318658
name 3
2149318659
name 4
2149318660
name 5
2149318661
name 6
2149318662
name 7
2149318663
name 8
2149318664
name 9
2149318665
name POWER
2149318666
name CH_UP
2149318671
name CH_DOWN
2149318672
name MUTE
2149318673
name VOL_DOWN
2149318674
name CH_PREVIOUS
2149318675
name VOL_UP
2149318676
name DISPLAY
2149318677
name EXIT
2149318680
name GUIDE
2149318683
name SELECT
2149318686
name AV
2149318697
name ENTER
2149318699
name MENU
2149318703
name MUP
2149318704
name MDOWN
2149318705
name MLEFT
2149318706
name MRIGHT
2149318707
end raw_codes
end remote

begin remote
[b]name Hauppauge_350[/b]
bits 13
flags RC5|CONST_LENGTH
eps 30
aeps 100

one 969 811
zero 969 811
plead 1097
gap 114605
# gap 200000
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
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
[/code]