View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 14 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Sat May 19, 2007 9:42 pm 
Offline
Joined: Sat Jan 20, 2007 12:30 pm
Posts: 9
The ir blaster attached to my pvr150 is killing me (trying to control a dish 322).

I followed the instructions here:

http://knoppmythwiki.org/index.php?page=PVR150withSetTopBox

using the codeset indicated here:

http://www.blushingpenguin.com/mark/lmilk/IRcodesets.html

The relevant parts of /etc/lircd.conf are at the bottom of this post.

When I run:
Code:
irsend SEND_ONCE blaster POWER


The blaster flickers, but nothing happens. I tried a few different codes, (channel up, channel down etc) same thing (flicker but no response).

A couple of quick questions...where does lircd.conf really belong? I have a copy in /etc and /etc/lirc. Which one is being used?

Does anybody see anything wrong with my configuration? I'm really frustrated, but very close to solving this.

Ok, here is the relevant section from lircd.conf:


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
2156003328
name 1
2156003329
name 2
2156003330
name 3
2156003331
name 4
2156003332
name 5
2156003333
name 6
2156003334
name 7
2156003335
name 8
2156003336
name 9
2156003337
name POWER
2156003338
name CH_UP
2156003343
name CH_DOWN
2156003344
name CH_PREVIOUS
2156003347
name DISPLAY
2156003349
name EXIT
2156003352
name GUIDE
2156003355
name MENU
2156003375
name MUP
2156003376
name MDOWN
2156003377
name MLEFT
2156003378
name MRIGHT
2156003379
end raw_codes

end remote


Last edited by sameat on Tue May 22, 2007 10:36 pm, edited 1 time in total.


Top
 Profile  
 
 Post subject:
PostPosted: Sun May 20, 2007 7:18 am 
Offline
Joined: Mon May 02, 2005 9:00 am
Posts: 172
It should be using /etc/lirc/lircd.conf

I did have a problem with one of my boxes (StarChoice). The remote that came with the receiver was set to id 1 instead of 0 in the software on the set top box itself. This is if you have two set top boxes in the same room and want to control them seperately. I changed mine back to id 0 and then my lirc codes for my box started working. I'm not sure if you need to restart lirc after editing lircd.conf to get the irsend command to work but it shouldn't hurt.

Code:
/etc/init.d/lirc restart


Hope this helps.


Top
 Profile  
 
 Post subject:
PostPosted: Sun May 20, 2007 9:36 am 
Offline
Joined: Sat Jan 20, 2007 12:30 pm
Posts: 9
Thanks. I changed the lircd in /etc into a symbolic link to /etc/lirc/lircd.conf, and everything seems to be working.

I also switched back to the lircd.conf that includes codes for all known stb's and ran the sendpower script [url](http://www.blushingpenguin.com/mark/lmi ... _power_new[/url]

but none of the codesets work.

I also tried
Code:
irsend SEND_START blaster 1_130_KEY_POWER

and tried the blaster in all kinds of positions while it was flickering. No go.

The Remote ID is set to 1 on the 322, which I assume is the default. When my 2 year old finishes Blues Clues, I'll try all 6 remote ID's to see what happens.

Hope is fading fast. I feel like I am on the verge of solving this, but I can't get the final detail. I am considering ordering a separate blaster, but given that this one seems to be operating fine (except for the result), I'm not too hopeful about that.

Thanks for the quick response...I'll post the results of changing the Remote ID changes here.


Top
 Profile  
 
 Post subject:
PostPosted: Sun May 20, 2007 10:34 am 
Offline
Joined: Sat Jan 20, 2007 12:30 pm
Posts: 9
Tried all 16 "remote ids" on the stb. No go.

I am going to have to shelve this project for a while now. My family is tired of me messing with the tv. In a few weeks, I'll try to set it all up in Windows (since it is supposedly supported) and see if this is a hardware problem.

Thanks again for the response. This is disappointing, but I'm sure I'll get it after a break.


Top
 Profile  
 
 Post subject:
PostPosted: Mon May 21, 2007 8:20 am 
Offline
Joined: Sat Jan 20, 2007 12:30 pm
Posts: 9
I keep replying to my own post.

I had a few minutes, so I threw the pvr150 in a windows box, attached the blaster, and tried to set it up. It scanned all the codes it has for Dish to no avail.

I have a call in to Hauppauge tech support, but I am also going to order a different ir blaster. Does anybody know of a blaster that works well with Knoppmyth and the Dish 322?


Top
 Profile  
 
 Post subject:
PostPosted: Mon May 21, 2007 9:31 am 
Offline
Joined: Mon May 02, 2005 9:00 am
Posts: 172
When you say the blaster flickers is it fairly bright? I did have a problem with my cable when I didn't get it plugged in all the way. It would flicker but not nearly as bright as it should have been. There should be a piece of the plastic cut off the connector so you can seat it properly without hitting the slot of your case. If it's flashing brightly the blaster should be fine and I'd worry more about the codes.


Top
 Profile  
 
 Post subject:
PostPosted: Mon May 21, 2007 10:25 am 
Offline
Joined: Sat Dec 24, 2005 11:33 am
Posts: 400
Location: Kitsap Peninsula, Wa., United States
Sameat,
I concur with Chunter2 as far as having the blaster plugged into the socket correctly.

I personally have 2 Dish 301/311 recievers and a dish 322. You are aware that the 322 has two units in it. TV1 is IR controlled and TV2 is UHF controlled. ( I haven't figured out how to control that UHF unit yet) anyway, the 322 responds to exaclty the same set of codes as a 301/311. Besides the IR Blasters I can use any of the IR remotes for the Dish to control any of the boxes.

The little blaster emitter the "Stick on" thing has to be attached directly to your infrared window on the reciever.

I don't have access to my mythbox right now, I could give you my codeset in /etc/lirc/lircd.conf

As I remember I had to use codeset 1_28 just like it says in the wiki article. I cut and pasted the one I wanted into a lircd.conf file

Those steps on that Wiki just flat worked.

I don't see that you mentioned which version of knoppmyth you are using. I am on R5C7.

Hope this is helpful.

_________________
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
 Profile  
 
 Post subject:
PostPosted: Mon May 21, 2007 4:56 pm 
Offline
Joined: Sat Jan 20, 2007 12:30 pm
Posts: 9
Thanks for the responses.

I wouldn't say it is flickering brightly, but I can see it without difficulty.

I say the notch in the mini jack and tried to spin it around, and it didn't seem to pull out at all in the un-notched section. I might trim it back a little more as it is a pretty tight fit.

I hate to change too many things at one time, so once I change that and do a little testing, I'll experiment with different codes. The 322 is listed with a separate code here:
[url]
http://www.blushingpenguin.com/mark/lmi ... esets.html
[/url]
but that doesn't have to be gospel.

I'd love to see the working lircd.conf if you can post it bigbro. Even just the working power code would be great. If I am all of this stuff correctly, it should be:

Code:
name Power
    2149318666


if I am using raw codes. Is that right?

Thanks again for the time to answer my post. I know I can get this with a little help. :)

By the way, it's R5F1.


Last edited by sameat on Tue May 22, 2007 3:41 pm, edited 1 time in total.


Top
 Profile  
 
 Post subject:
PostPosted: Mon May 21, 2007 6:23 pm 
Offline
Joined: Sat Dec 24, 2005 11:33 am
Posts: 400
Location: Kitsap Peninsula, Wa., United States
Earlier today when I checked some of my instructions I was in fact using that set of codes listed on the Wiki for PVR150withSetTopBox

That is the correct Powerup code. It matches what my notes say I installed since I installed that from the wiki.
My lircd.conf

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 KEY_POWER
    2149318666
    name KEY_CH_UP
    2149318671
    name KEY_CH_DOWN
    2149318672
    name KEY_MUTE
    2149318673
    name KEY_VOL_DOWN
    2149318674
    name CH_PREVIOUS
    2149318675
    name KEY_VOL_UP
    2149318676
    name KEY_DISPLAY
    2149318677
    name KEY_EXIT
    2149318680
    name KEY_GUIDE
    2149318683
    name KEY_SELECT
    2149318686
    name KEY_AV
    2149318697
    name KEY_ENTER
    2149318699
    name KEY_MENU
    2149318703
    name KEY_MUP
    2149318704
    name KEY_MDOWN
    2149318705
    name KEY_MLEFT
    2149318706
    name KEY_MRIGHT
    2149318707
   end raw_codes

end remote

begin remote

  name  Hauppauge
  bits           13
  flags SHIFT_ENC
  eps            30
  aeps          100

  one           950   830
  zero          950   830
  plead         960
  gap          89584
  repeat_bit      2

      begin codes
          TV                       0x000000000000100F
          RADIO                    0x000000000000100C
          FULL_SCREEN              0x000000000000102E
          CH+                      0x0000000000001020
          CH-                      0x0000000000001021
          VOL-                     0x0000000000001011
          VOL+                     0x0000000000001010
          MUTE                     0x000000000000100D
          SOURCE                   0x0000000000001022
          1                        0x0000000000001001
          2                        0x0000000000001002
          3                        0x0000000000001003
          4                        0x0000000000001004
          5                        0x0000000000001005
          6                        0x0000000000001006
          7                        0x0000000000001007
          8                        0x0000000000001008
          9                        0x0000000000001009
          0                        0x0000000000001000
          RESERVED                 0x000000000000101E
          MINIMIZE                 0x0000000000001026
      end codes

end remote




Two things I remember, when you install new firmware and I have also seen this through a reboot the Hauppauge IR blaster gets finicky. I usually perform a shutdown for a few minutes. Has something to do with how it drains out of memory.

once install at steps 1-3 it gives you the steps to manually test it.

did you catch my note about the change_channel script at the bottom. I can't recall if when you copy it over it does it correctly.

For reference here is that script I had a copy of it on my windoze box.

Copy this or compare it to your change_channel script

I think they have you put it in /usr/local/bin as change_channel
make sure you can execute it and it should work.

Code:
#!/usr/bin/perl

# make sure to set this string to
# the corresponding remote in /etc/lircd.conf
$remote_name = "blaster";

# Let's assume you don't need to press enter after you punch in a
# channel number. Change this to 1 if your cable box expects you press
# enter after each command
$needs_enter = 0;

# Change this to point to your rc executable
$rc_command = "/usr/local/bin/irsend";

# This subroutine actually sends the signal to the cable box
sub change_SIGNAL {
    my($SIGNAL) = @_;
    system ("$rc_command SEND_ONCE $remote_name $SIGNAL");
}

$SIGNAL=$ARGV[0];
open F, ">> /var/log/channel.log";
print F "channel changing $SIGNAL\n";
close F;
print "channel changing $SIGNAL\n";

# Checks if $SIGNAL begins with a digit
# If it detects that the string is made up of digits, then it puts
# spaces between the digits.  Ex. 1234 becomes 1 2 3 4
if ( $SIGNAL =~ /^\d+$/ )
{
    my $length = length($SIGNAL);
    my $counter = 0;
    my $temp;

    while( $counter < $length )
    {
        $temp .= substr($SIGNAL,$counter,1) ." ";
        $counter++;
    }

    change_SIGNAL($temp);
}
else
{
    # argument we passed was not made up of digits, so it must be a
    # command that does something other than channel changing on the
    # cable box
    change_SIGNAL($SIGNAL);
}

# Do we need to send enter
if ( $needs_enter )
{
    system ("$rc_command SEND_ONCE $remote_name ENTER");
}



In following your link to the Code list site, I don't even see where they have referenced Code set 1_28 as the proper one for Dishnetwork 301/311 Could be they have changed the format as to how those are called out somewhere else.

Hope this helps.

_________________
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
 Profile  
 
 Post subject:
PostPosted: Tue May 22, 2007 7:19 am 
Offline
Joined: Tue Oct 25, 2005 7:04 am
Posts: 58
Location: Victoria, BC
I'm using the same "blaster" codes as bigbro (which are different from the ones listed in the first post). They work for all models of Dish/Expressvu receivers that I have.

Another note on the 322 - I have a 3100 receiver (which I think is the same as a Dish 301) and the sensitivity of its infrared receiver is *very* low. In order to make it work reliably, I have attached the IR LED directly to the IR recv'r inside the sat recv'r. Without doing that - it's hit and miss to get working.

The other recv'rs I've got (2700, 4700, 5100 [501] etc...) work fine with the IR blaster LED taped on the front panel.


Top
 Profile  
 
 Post subject:
PostPosted: Tue May 22, 2007 11:59 am 
Offline
Joined: Sat Jan 20, 2007 12:30 pm
Posts: 9
RobtheGob:

Thanks for the response. I have found that the codes that you and bigbro posted work. Thanks to both of you.

Unfortunately, I have to remove the emitter from it's little plastic case and touch it to the receiver to get it to work. I thought maybe the connection to the pvr150 was not tight enough, so I hacked away part of the case to make room for a good tight connection.

There is no way I can seat the minijack and more firmly. There are no longer any obstructions. Still only getting intermittent responses to the blaster.

What do you mean when you say that you attached the led " inside the sat recv'r". Did you actually remove the little window on the receiver? I'm considering doing that, but am a little concerned about damaging the receiver.

Thanks again for the assist. I'm getting closer all the time.


Top
 Profile  
 
 Post subject:
PostPosted: Tue May 22, 2007 5:57 pm 
Offline
Joined: Sat Dec 24, 2005 11:33 am
Posts: 400
Location: Kitsap Peninsula, Wa., United States
Glad the codes worked.

On all 3 of my Receivers the little emitter has a smooth side and a little bit rough side, the smooth side as I remember had a double sided tape stuck to it, I just peeled the other side off so it was now sticky and then attached that directly to the right most and center LED's in the 3 LED receiver window. I made sure the emitter section was directly over the Center LED type IR Receiver.

They just worked from there.

It is kind of a hokey setup but it works for such a short range emitter. The only thing I have noticed on one of my units, the Cats can get on top of it. Every now and then they dislodge the little emitter ever so slightly, when that happens the channel change is erratic. I go in an just push it back up tight against the plastic window and everything works again.

Of course the best solution to this problem is to mount the receiver where my critters can't sleep on it. They like the warmth.

Regards.


Top
 Profile  
 
 Post subject:
PostPosted: Tue May 22, 2007 10:53 pm 
Offline
Joined: Sat Jan 20, 2007 12:30 pm
Posts: 9
Thanks a ton for all of the help...everything is working now.

A couple of observations:

-Ignore anything you see that says that you need the 1_130 codeset for a dish 322. That is just wrong. 1_28 works fine.

-I had to change the location of irsend in the change channel script (it was the only change I made from bigbro's above)

-I modded my equipment a little to get this done. One end or the other was just too weak, so I made some changes to the stb that allowed me to place the pvr150 blaster inside the stb. I don't think I'd recommend this as a general rule (it was a lot of work, and my wife was not thrilled), but it was the only way I could get it to work consistently.

My critters are human (I have 1 yo and a 2 yo), so I will probably have to move the stb before long...it's in the exact wrong place. If I can get everybody on board for watching TV through myth, I'll just hide the stb. :)

Thanks again to everybody who contributed. It was a little bit of a challenge, but well worth it.


Top
 Profile  
 
 Post subject:
PostPosted: Wed May 23, 2007 7:28 am 
Offline
Joined: Tue Oct 25, 2005 7:04 am
Posts: 58
Location: Victoria, BC
I found that since the 3100 recv'r was so insensitive, I had to make a "direct" connection between the emitter and the recv'r, inside the sat recv'r.

I ended up taking a short section of BIC pen and found that the inside diameter was just about exactly right to cover both parts. I then stuck it all together and taped it.

I still occasionally get mis-fires, but it is about as good as it can get with that sat recv'r. The other models that I have work fine.

I'm glad you got it working. A MythTV working properly is incredible!


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 14 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 9 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

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu