Re: [mythtv-users] MyIRBlaster - Myth Issues Only??

2005-10-26 Thread David Ellis

Solved.

I inserted a sleep command in the changechannel script BEFORE I send the 
command.


sleep .5

Its possibly a thread contention issue of some sort? Anyway experiment with 
different sleep options to get the best configuration for your setup.


David
- Original Message - 
From: "David Ellis" <[EMAIL PROTECTED]>

To: "Discussion about mythtv" 
Sent: Wednesday, October 26, 2005 1:22 PM
Subject: Re: [mythtv-users] MyIRBlaster - Myth Issues Only??


I'm having a similiar issue with a USB connected blaster..so I'm 
pretty sure its not related to the serial line speed or configuration.


What I've noticed is it only pops up if the same blaster is used to 
receive the command as send the command.


Symptoms:
1) recording is 100% reliable (thank you lord)
2) changing channels is 25% reliable
3) Using previous channel to flip back and forth is reliable.

I'm going to experiment with inserting sleep settings to see if it helps.

David
- Original Message - 
From: "George Nassas" <[EMAIL PROTECTED]>

To: "Discussion about mythtv" 
Sent: Wednesday, October 26, 2005 1:19 PM
Subject: Re: [mythtv-users] MyIRBlaster - Myth Issues Only??



On 26-Oct-05, at 1:08 PM, Scott S. wrote:


Has anyone seen this? Or have any other ideas on a fix? Any help would
be great.


I haven't seen this problem with mine but I remember when I was setting
up a modem I had a heck of a time getting the serial connection to work
reliably. One thought I have is when you test it through the command
line are you the same user as the myth backend? I remember that being a
factor for some reason, you may have to add the backend user to the
dialout group or whoever owns the serial port. Or, do the channel
change through a script that explicitly sets the line parameters before
running the channel change script.

- George








___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users



___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] MyIRBlaster - Myth Issues Only??

2005-10-26 Thread Robert Denier
I had a lot of trouble changing channels reliably since I moved to dish
network 301 receivers from a 5xx series.  Someone suggested that the gap
value in the file may have to be changed and that it was cpu/serial port
dependent.  

I kept changing it and figured it was a lost cause at one point, and was
about to order a MyBlaster, but then I decided to change it some more
and eventually ended up with something that seems ok.  I started with a
gap of 175000 and ended with 40 in /etc/ledxmitd.conf.

I tossed together this script to zap and restore things to try different
gap values.  I'm sure someone could clean it up if they cared to do
so...

#!/bin/bash
modprobe -r ledxmit_serial
modprobe -r ledxmit_dev
PID=$(ps -A | grep ledxm | egrep -o "[0-9]{3,5}")
echo "Found PID=[$PID]"
if [[ "$PID" != "" ]]
then
echo "Killing existing instance of ledxmit..."
kill -s 9 $PID
fi

/bin/echo "Starting ledxmit stuff..."
setserial /dev/ttyS0 uart none
update-modules
modprobe ledxmit_serial
nice -n -20 /usr/local/lirc-ledxmit/sbin/ledxmit-ledxmitd



For reference that is an AMD XP 2000+ (Technically it is actually an AMD
MP 1900+ running as a 2000+.) with an nforce 2 motherboard.

It seems that the normal way of entering remote codes from an unknown
remote will determine the value of the gap, but, unfortunately, dish
network receivers run at 56kHz(?) and my IR receiver doesn't pick up
them, so I was stuck working from a premade file and guessing.

-Robert

On Wed, 2005-10-26 at 13:19 -0400, George Nassas wrote:
> On 26-Oct-05, at 1:08 PM, Scott S. wrote:
> 
> > Has anyone seen this? Or have any other ideas on a fix? Any help would 
> > be great.
> 
> I haven't seen this problem with mine but I remember when I was setting 
> up a modem I had a heck of a time getting the serial connection to work 
> reliably. One thought I have is when you test it through the command 
> line are you the same user as the myth backend? I remember that being a 
> factor for some reason, you may have to add the backend user to the 
> dialout group or whoever owns the serial port. Or, do the channel 
> change through a script that explicitly sets the line parameters before 
> running the channel change script.
> 
> - George
> 
> ___
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] MyIRBlaster - Myth Issues Only??

2005-10-26 Thread David Ellis
I'm having a similiar issue with a USB connected blaster..so I'm pretty 
sure its not related to the serial line speed or configuration.


What I've noticed is it only pops up if the same blaster is used to receive 
the command as send the command.


Symptoms:
1) recording is 100% reliable (thank you lord)
2) changing channels is 25% reliable
3) Using previous channel to flip back and forth is reliable.

I'm going to experiment with inserting sleep settings to see if it helps.

David
- Original Message - 
From: "George Nassas" <[EMAIL PROTECTED]>

To: "Discussion about mythtv" 
Sent: Wednesday, October 26, 2005 1:19 PM
Subject: Re: [mythtv-users] MyIRBlaster - Myth Issues Only??



On 26-Oct-05, at 1:08 PM, Scott S. wrote:


Has anyone seen this? Or have any other ideas on a fix? Any help would
be great.


I haven't seen this problem with mine but I remember when I was setting
up a modem I had a heck of a time getting the serial connection to work
reliably. One thought I have is when you test it through the command
line are you the same user as the myth backend? I remember that being a
factor for some reason, you may have to add the backend user to the
dialout group or whoever owns the serial port. Or, do the channel
change through a script that explicitly sets the line parameters before
running the channel change script.

- George








___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] MyIRBlaster - Myth Issues Only??

2005-10-26 Thread George Nassas

On 26-Oct-05, at 1:08 PM, Scott S. wrote:

Has anyone seen this? Or have any other ideas on a fix? Any help would 
be great.


I haven't seen this problem with mine but I remember when I was setting 
up a modem I had a heck of a time getting the serial connection to work 
reliably. One thought I have is when you test it through the command 
line are you the same user as the myth backend? I remember that being a 
factor for some reason, you may have to add the backend user to the 
dialout group or whoever owns the serial port. Or, do the channel 
change through a script that explicitly sets the line parameters before 
running the channel change script.


- George

___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


[mythtv-users] MyIRBlaster - Myth Issues Only??

2005-10-26 Thread Scott S.

Hello,

   I've recently switch TV providers (because the company I work for is 
offering TV services now) and we have Amino AmiNet110's for set top 
boxes. I'm using a MyBlaster, the serial one from my tv store (mytvsore 
dot com). I use the MyBlaster.pl that you can download for use with the 
MyBlaster and I've found that is I run the MyBlaster.pl from the command 
prompt it changes the channel great, but when I am in Myth and it tries 
to change the channel using the same script it fails the majority of the 
time. There's typically three things could happen when it fails, one is 
it could do nothing. It's rare but it's happened a couple of times), 
another is that it misses a digit (usually at the beginning or middle of 
the channel number), and the third is that it may repeat a number (for 
instance 8 turns into 88). I'm not sure why this would happen in just 
Myth. I've used TVtime and XawTV to test the channel changing from the 
command line, and that works flawlessly, changing the channel while Myth 
is running and watching live TV also works flawlessly. It only fails 
when Myth itself tries to change  the channel with the MyBlaster.pl script.


I've played around with the timing in the MyBlaster.pl script and have 
re trained the MyBlaster with the IR codes over a dozen times, nothing 
seems to change how it acts tho, it works from the command line great 
but acts really weird when Myth goes to change the channel. The other 
thing I have done is made my own channelchange.pl and had it call the 
MyBlaster script to send the raw IR code to the MyBlaster script, that 
hasn't helped either though. Has anyone seen this? Or have any other 
ideas on a fix? Any help would be great.


Thank You,

Scott

___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users