View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 8 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Fri Jun 06, 2008 3:48 pm 
Offline
Joined: Fri May 30, 2008 9:30 pm
Posts: 13
That's right. If you give me information/directions that lead directly to a working IR Blaster on my system, I will pay you $25 (via Paypal). You can find some more information about my setup and my system and some of my problems on this thread:

http://knoppmyth.net/phpBB2/viewtopic.php?t=18373&sid=2ff82a0af4b9e0d0b67bb51dc7e7d8a2
I think this has most of the information about where I am and my problems, so read it carefully, I think I'm close, but I feel very stuck.

Whoever gives the information first on either forum topic that helps me get my IR Blaster working will get the bounty. I will answer any questions you have about my setup as promptly as possible.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Jun 06, 2008 5:01 pm 
Offline
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location: Adelaide, Australia
If you meet me in #knoppmyth, on irc.freenode.net we can try to troubleshoot your problem. I go by the nick Slartybartfast


Top
 Profile  
 
 Post subject:
PostPosted: Sat Jun 07, 2008 9:45 am 
Offline
Joined: Fri May 30, 2008 9:30 pm
Posts: 13
Greg, thanks for the offer. I'm having some network issues at home right now, but once I get them worked out, I'll be looking for you.

Does KnoppMyth have an IRC Client? Does Lynx support it already?


Top
 Profile  
 
 Post subject:
PostPosted: Sat Jun 07, 2008 1:37 pm 
Offline
Joined: Fri Sep 15, 2006 12:16 pm
Posts: 292
In the interest in doing things the same way for different systems, I will
describe setting it up with a working IR receiver so that you can do it
the same way in the future if you wand to start using an IR remote
with your (serial) IR receiver.

I assume you have a standard (lirc.org or igwanaworks.com) serial
blaster on COM1.

In case you didn't know, everything in Linux is case sensitive, so make
sure you get the capitalization of everything correct.

If you don't have a preferred editor (like vi or emacs) I suggest that
you use pico to make the changes. It is real easy to use.

You will need to be logged in as root to do most of this...

This is all from memory, please post if it works or does not and I will
move it to the wiki.

First comment out (Just put a hash mark ("#") at the beginning of it)
the '/dev/ttyS0 blah blah' line at the end of /var/lib/setserial/autoserial.conf
and add this line after it:
Quote:
/dev/ttyS0 uart none
Mine wound up looking like this:
Quote:
###PORT STATE GENERATED USING AUTOSAVE-ONCE###
###AUTOSAVE-ONCE###
###AUTOSAVE-ONCE###
###AUTOSAVE###
#
# If you want to configure this file by hand, use
# dpkg-reconfigure setserial
# and change the configuration mode of the file to MANUAL. If you do not do this, this file may be overwritten automatically the next time you upgrade the
# package.
#
#/dev/ttyS0 uart 16550A port 0x03f8 irq 4 baud_base 115200 spd_normal skip_test
/dev/ttyS0 uart none
FYI you are actually supposed to tell the system that you
want to configure this manually by running this first:
Code:
dpkg-reconfigure setserial


Next, rename /etc/lirc to /etc/lirc.save and /etc/irblaster to
/etc/irblaster.save and create new lirc and irblaster directories so we
start from a blank slate:
Code:
cd /etc
mv lirc lirc.save
mv irblaster irblaster.save
mkdir lirc irblaster


Next run /usr/local/bin/lirc-reconfig.sh and select the 'rca-6n1' device
as it is a serial device and thus will set up your lirc to work with serial:
Code:
/usr/local/bin/lirc-reconfig.sh
When it asks you what kind of remote you have do NOT put in
the actual kind of remote you use with your receiver. Think about it,
you would have a remote sending the exact same codes that the
irblaster sends and when you press '1' the IR receiver will see it and make
the blaster send a '1' which the IR receiver will see as the exact same
code you just sent from the remote and it will make the blaster send '1'
over and over. You can get this kind of setup to work if you put the
blaster sender right on the satellite receiver and shield this combination
from seeing anything else, but that is outside the scope of this post and
usually requires removing the IR sender LED and putting it back on a long
wire.

Next run /usr/local/bin/irblaster.sh:
Code:
/usr/local/bin/irblaster.sh
and select your correct satellite receiver and serial COM port.

Next add the lirc.conf that you have for your receiver to the end of
/etc/lirc.conf (replace the obvious in the code below):
Code:
cat insert-the-name-of-your-lirc.conf >>/etc/lir/lircd.conf
insert-the-name-of-your-lirc.conf will usually be /etc/irblaster/irblasterd.conf

Next shutdown your mythtv frontend by pressing ESC from the home
menu and answering Yes. Then right click on the desktop and
select 'xshells -> xterm'. Then get root by running 'su' and entering your
root password. Then shutdown the backend and run mythtv-setup.
Code:
su
<enter your password>
/etc/init.d/mythtv-backend stop
mythtv-setup
Go into 'input connections' and select the connection that you want to
control the channel changing of. In the 'External channel change
command' field enter
Quote:
/etc/irblaster/channel_change.sh
Finish and get out of mythtv-setup.

Edit /etc/irblaster/channel_change.sh and remove the part of the line
that says:
Quote:
--device=/dev/irblasterd


OR If you want to you can replace the channel_change.sh this way

Save the following code into the file /etc/irblaster/channel_change.sh:
Quote:
#!/bin/bash

# Change the following line to reflect the receiver you want to control in /etc/lirc/lircd.conf
REMOTE_NAME=new-remote-name-goes-here

# cancel in case it is at a ppv that won't take channel down
#/usr/bin/irsend SEND_ONCE $REMOTE_NAME cancel
#sleep 0.5

# channel down in case it is at a pay channel that accepts only channel up or down
#/usr/bin/irsend SEND_ONCE $REMOTE_NAME down
#sleep 0.5

for digit in $(echo $1 | sed -e 's/./& /g'); do
/usr/bin/irsend SEND_ONCE $REMOTE_NAME $digit
sleep 0.5
done


...and make it executable:
Code:
chmod a+x /etc/irblaster/channel_change.sh


...and change /etc/irblaster/channel_change.sh by replacing
new-remote-name-goes-here with the name of the receiver you are
controlling in /etc/lirc/lircd.conf The line in lircd.conf will begin
with the word 'name'.

Reboot and test:
Code:
reboot


The payment for this is for you to help someone else with something that
you know about Knoppmyth, possibly later on when you are more
comfortable with it.

Cliff

_________________
R5F27 using R5F1 Nvidia drivers
HD-5500 analog from NTSC Sat Rx, with OTA DVB too
GeForce MX-440 SVideo tvout to a TV
Older dual core 3.4ghz Intel CPU
Asus P5PE-VM Motherboard
2 GB RAM
1 TB LVM2
VirtualBox
Samba


Top
 Profile  
 
 Post subject:
PostPosted: Sun Jun 08, 2008 3:30 pm 
Offline
Joined: Fri May 30, 2008 9:30 pm
Posts: 13
Thanks Cliff for the detailed directions. I tried to follow them as closely as I could, but now I'm getting this error when I test channel_change.sh 17:

Code:
/usr/bin/irsend could not connect to socket
/usr/bin/irsend Connection refused
/usr/bin/irsend could not connect to socket
/usr/bin/irsend Connection refused
/usr/bin/irsend could not connect to socket
/usr/bin/irsend Connection refused


So does that mean I'm still not connected through the serial port?


Top
 Profile  
 
 Post subject:
PostPosted: Sun Jun 08, 2008 7:14 pm 
Offline
Joined: Fri May 30, 2008 9:30 pm
Posts: 13
Case Closed! Thanks to Greg who solved all my problems on IRC. Bounty has been claimed.

Turns out it was a combined case of bad remote codes and a bad channel_change script. Also, I had to play the position of my IR Blaster to get it working consistently. Turns out that having it a little bit away from the IR Receiver on my STB was better than directly on it.

Thanks to Cliff and Greg.


Top
 Profile  
 
 Post subject: wrap up
PostPosted: Tue Jun 10, 2008 7:44 am 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
bradm81 wrote:
Case Closed! Thanks to Greg who solved all my problems on IRC. Bounty has been claimed.

Turns out it was a combined case of bad remote codes and a bad channel_change script. Also, I had to play the position of my IR Blaster to get it working consistently. Turns out that having it a little bit away from the IR Receiver on my STB was better than directly on it.

Thanks to Cliff and Greg.

Could you post the working versions of your scripts? This will help others who have the same problem in the future.

Thanks!
Eric

_________________
KnoppMyth R5.5, Asus A8N-VM CSM (nvidia 6150 onboard video), AMD Athlon 64 dual-core 4200+, two 1GB sticks DDR 400, HD-3000 HDTV card, PVR-150 card, Iguanaworks RS-232 IR receiver/transmitter, Pioneer DVR-110 DVD burner


Top
 Profile  
 
 Post subject:
PostPosted: Tue Jun 10, 2008 4:11 pm 
Offline
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location: Adelaide, Australia
In the end, I think all of the default scripts worked. It was just a matter of running lirc-reconfig and selecting a remote that was not a serial remote (to avood conflict with irblaster). Then running irblaster.sh to setup the blaster and then downloading and installing the appropriate lirc codes in /etc/irblaster/irblasterd.conf. Then making sure the positioning of the blaster allowed for reliable blasting.

The lirc codes that bradm81 requires should be selectable from the irblaster.sh menu in the next release.


Top
 Profile  
 

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


All times are UTC - 6 hours




Who is online

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