View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 3 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Mon Sep 06, 2010 9:45 am 
Offline
Joined: Sat Sep 04, 2010 4:44 pm
Posts: 2
Has any one gotten this to work?

Is there a how to?

_________________
Linhes 6.03
MSI K7N2 Delta2
AMD XP2800
512 Ram
1.5 TB
PNY Verto Gforce 6200 AGP
Hauppauge PVR 150 with remote control and blaster
Hauppauge PVR 500


Top
 Profile  
 
 Post subject:
PostPosted: Thu Sep 09, 2010 9:52 pm 
Offline
Joined: Sat Sep 04, 2010 4:44 pm
Posts: 2
The pvr150 works fine, the remote works but not the blaster


Ok this is what I have for my chnge_chan.sh

Code:
#!/bin/sh
REMOTE_NAME= pace_dc50x
cmd="$1"

case $cmd in
       [0-9]*)
           for digit in $(echo $1 | sed -e 's/./& /g'); do
              irsend SEND_ONCE $REMOTE_NAME $digit
              sleep  0.3
           # If things work OK with sleep 1, try this for faster channel changes:
           # sleep 0.3
       done
           ;;

      *)
              irsend SEND_ONCE $REMOTE_NAME $cmd
                                       ;;
    esac
#    /usr/bin/fix_audio.sh &


and in my /etc/lircd.conf

Code:
include "/usr/MythVantage/templates/transmit/pace_dc50x/lircd.conf"
include "/usr/MythVantage/templates/remotes/hauppauge-blaster/lircd.conf"


my systemconfig IR settings

Code:
#IR settings
Remotetype="hauppauge-blaster"
ReceiverType="Hauppauge"
HDHRlirc_device="No devices found"
HostLircWait=""
ReceiverSerialport="ttyS0"
HostTransmitproto_1="pace_dc50x"
HostTransmitproto_2="none"
HostTransmitproto_3="none"
HostTransmitproto_4="none"
HostBlasterType="pvr150"
HostSerialPort_blasterlirc=""
Hostnumblaster="1"
rootSSH="1"


and my lirc log files
Code:
Sep  9 19:54:47 backend lircd: lircd(default) ready
Sep  9 19:55:03 backend lircd: accepted new client on /dev/lircd
Sep  9 19:55:05 backend lircd: accepted new client on /dev/lircd
Sep  9 19:55:05 backend lircd: accepted new client on /dev/lircd
Sep  9 19:55:05 backend lircd: removed client
Sep  9 19:55:05 backend lircd: accepted new client on /dev/lircd
Sep  9 19:55:05 backend lircd: removed client
Sep  9 19:55:13 backend lircd: accepted new client on /dev/lircd
Sep  9 19:55:19 backend lircd: accepted new client on /dev/lircd
Sep  9 19:55:19 backend lircd: removed client
Sep  9 19:55:19 backend lircd: accepted new client on /dev/lircd
Sep  9 19:55:19 backend lircd: removed client
Sep  9 19:55:28 backend lircd: accepted new client on /dev/lircd
Sep  9 19:55:28 backend lircd: removed client
Sep  9 19:55:28 backend lircd: accepted new client on /dev/lircd
Sep  9 19:55:28 backend lircd: removed client
Sep  9 19:55:33 backend lircd: accepted new client on /dev/lircd
Sep  9 19:55:33 backend lircd: removed client
Sep  9 19:55:33 backend lircd: accepted new client on /dev/lircd
Sep  9 19:55:33 backend lircd: removed client
Sep  9 19:55:49 backend lircd: accepted new client on /dev/lircd
Sep  9 19:55:49 backend lircd: removed client
Sep  9 19:55:49 backend lircd: accepted new client on /dev/lircd
Sep  9 19:55:49 backend lircd: removed client


but I don't get any out put at the blaster when viewing though a digital camera
Any help would be greatly appreciated [/code]

_________________
Linhes 6.03
MSI K7N2 Delta2
AMD XP2800
512 Ram
1.5 TB
PNY Verto Gforce 6200 AGP
Hauppauge PVR 150 with remote control and blaster
Hauppauge PVR 500


Top
 Profile  
 
 Post subject:
PostPosted: Sat Sep 11, 2010 8:44 pm 
Offline
Joined: Sun Nov 13, 2005 5:56 pm
Posts: 97
This is something I spent a long time wrestling with in LinHES. I didn't want to deal deal with the new (to me) and unfamiliar RUNSV startup system. I thought I solved it a couple of times only to still find problems. First, I found I had too many init scripts going. There was an irblaster startup in /etc/init.d as well as /etc/sv. The point is too make sure you have only one startup for lirc (my term for the main remote) and for the blaster. Check /etc/init.d, /etc/sv, and /etc/runit. Checking the runit folder means going thru the 1, 1.local, and 2 scripts. I used only the /etc/sv system for initializing the two. Now I found problems in the scripts. They are both called 'run' and are located under irblaster and lircd since this is how RUNSV works. In the lircd script there is a section that goes:

Code:
    if [ -n "$serial_port" ]
    then
        #/dev/ttyS0 (COM1), port 0x3f8, irq 4
        #/dev/ttyS1 (COM2), port 0x2f8, irq 3
        #/dev/ttyS2 (COM3), port 0x3e8, irq 4
        #/dev/ttyS3 (COM4), port 0x2e8, irq 3

        case $serial_port in
        ttyS0)
               FLAGS="io=0x3f8  irq=4"
               ;;
        ttyS1)
               FLAGS="io=0x2f8  irq=3"
               ;;
        ttyS2)
               FLAGS="io=0x3e8  irq=4"
               ;;
        ttyS3)
               FLAGS="io=0x2e8  irq=3"
               ;;
        esac
        /usr/bin/setserial /dev/$serial_port uart none
        sleep 0.5
        /sbin/modprobe lirc_serial $FLAGS
        sleep 0.5
    fi

It interferes with my irblaster/run script that has (for all intents and purposes) has the the same action. By the time it runs things get messed up. It takes too long to be more specific but the point is I changed the test statement from 'if [ -n "$serial_port" ]' to 'if [ 0 ]' in order to skip the whole thing. I also added the statement 'sv start lircd || exit 1' as the first statement of irblaster/run. This has the lircd/run execute first since the irblaster/run was written in such a way that it expects to run after. I found it in some RUNSV reference. That pretty much got things on track. I assume that you know about shell scripting so that you can go thru these scripts to see the details.

My /etc/systemconfig IR section looks like this. I edited it by hand. The Systemconfig section in the front end does stuff I don't understand or care for.

Code:
#IR settings
Remotetype="hauppauge-silver"
ReceiverType="Hauppauge"
HDHRlirc_device="No devices found"
HostLircWait=""
ReceiverSerialport=""
HostTransmitproto_1=""
HostTransmitproto_2=""
HostTransmitproto_3=""
HostTransmitproto_4=""
HostBlasterType=""
HostSerialPort_blasterlirc=""
Hostnumblaster="1"
rootSSH="0"


The parameter HostSerialPort_blasterlirc that is set to null in the /etc/systemconfig file is set in the file /etc/irblaster/hardware.conf thusly:

Code:
# /etc/irblaster/hardware.conf
#
#  Author: Greg Frost

# The COM Port used by the IRBlaster. Set it to COM1 COM2 or "".
IRBLASTER_SERIAL_PORT=COM1

The file is sourced by the /irblaster/run script.

You want to check a few things when running. I do a 'lsmod | sort | less' and look for these modules:
Code:
lirc_dev               13492  2 lirc_serial,lirc_i2c
lirc_i2c               10756  1
lirc_serial            14740  0

I do a 'ls -l /dev/lirc*' and expect to see:
Code:
lrwxrwxrwx 1 root root     5 2010-09-11 19:30 /dev/lirc -> lirc0
crw-rw---- 1 root root 61, 0 2010-09-11 19:30 /dev/lirc0
crw-rw---- 1 root root 61, 1 2010-09-11 19:30 /dev/lirc1
srw-rw-rw- 1 root root     0 2010-09-11 19:30 /dev/lircd

Then a 'ls -l /dev/irbl*' and expect:
Code:
crw-r--r-- 1 root root 61, 1 2010-09-11 19:30 /dev/irblaster
srw-rw-rw- 1 root root     0 2010-09-11 19:30 /dev/irblasterd

Note the regular remote lirc is a major 61 and minor 0 while the blaster is 61 and 1.

And, of course, check for the processes. There should be one for lircd and one for irblaster. Check the parameters point to the correct files and devices.

I realize the post is rather high level but the details are too many. I trust this can set you on the road to success.

-sparks-


Top
 Profile  
 

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


All times are UTC - 6 hours




Who is online

Users browsing this forum: Bing [Bot] and 3 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