View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 37 posts ] 
Go to page Previous  1, 2, 3  Next

Print view Previous topic   Next topic  
Author Message
Search for:
 Post subject:
PostPosted: Mon Jun 09, 2008 4:07 pm 
Offline
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location: Adelaide, Australia
What is the exact model of your receiver and/or remote. You may be able to download a lircd.conf file that (presumably) worked for someone else from http://lirc.sourceforge.net/remotes/


Top
 Profile  
 
 Post subject: Sony
PostPosted: Mon Jun 09, 2008 4:20 pm 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
Greg Frost wrote:
What is the exact model of your receiver and/or remote. You may be able to download a lircd.conf file that (presumably) worked for someone else from http://lirc.sourceforge.net/remotes/

Thanks for further feedback. Several weeks ago, I looked on the LIRC website (same location as you quoted) for the Sony remote and found no match. I just looked again - nothing. Here is the info on the receiver and remote:
Quote:
# brand: Sony DSS
# model no. of remote control: RM-Y130
# devices being controlled by this remote: Sony SAT-A2 DSS receiver


Do you see symptoms of the IR codes being wrong?
You saw that I do not get the same set of codes from IRRECORD every time I run it?
Does IRRECORD have a known quirk that needs to be worked around?

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: Mon Jun 09, 2008 9:47 pm 
Offline
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location: Adelaide, Australia
It is of concern that you get different codes when you use irrecord.
Do you have a joysitck? I found that when I had a joystick module loaded, and the frontend ran (and connected to the joystic device), the lirc timing got all screwed up.

Try recording your codes with as little running as possible (stop myth front and back ends, and mysql) and see if you can get a consistent resullt.

You may also want to look at the sequences it is receiving using xmode2.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Jun 09, 2008 10:03 pm 
Offline
Joined: Fri Sep 15, 2006 12:16 pm
Posts: 292
Logs in one of your previous posts had an error message that said 'ATSC'
yet your comment was that it was recording on a PVR-150. Is it possible
that you have an ATSC (high def) schedules direct lineup connected to a
PVR-150 (standard def) that is causing some problems?

Cliff


Top
 Profile  
 
 Post subject: ATSC vs. NTSC
PostPosted: Tue Jun 10, 2008 7:50 am 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
cliffsjunk wrote:
Logs in one of your previous posts had an error message that said 'ATSC'
yet your comment was that it was recording on a PVR-150. Is it possible
that you have an ATSC (high def) schedules direct lineup connected to a
PVR-150 (standard def) that is causing some problems?

Cliff

For now, the satellite receiver isn't getting or isn't responding to IR channel change commands. It makes sense to tackle this issue first.

For now, the PVR-150 card is recording the output of the satellite receiver ok. I simply have to leave it on 24/7 and pre-set to the channel I want to record from. I think the ATSC message stems from the Setup window setting where you tell Mythtv what video type you are recording. I set it to ATSC because for the first 2 years of operation, all I had was an ATSC tuner card in the machine. Now, I've added the PVR-150 (NTSC) card. I don't know if there is provision in Mythtv, to seletct BOTH ATSC and NTSC.

From what I've seen of Mythtv version 0.21, there is no ATSC choice in the Setup any more. You have to chose NTSC. So, it seems Mythtv doesn't really care what choice is in there. It records NTSC OK when you have ATSC selected. It will probably record ATSC OK if you have NTSC selected.

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


Last edited by neutron68 on Tue Jun 10, 2008 3:02 pm, edited 1 time in total.


Top
 Profile  
 
 Post subject: IRRECORD
PostPosted: Tue Jun 10, 2008 8:47 am 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
Greg Frost wrote:
It is of concern that you get different codes when you use irrecord.
Do you have a joysitck? I found that when I had a joystick module loaded, and the frontend ran (and connected to the joystic device), the lirc timing got all screwed up.

Try recording your codes with as little running as possible (stop myth front and back ends, and mysql) and see if you can get a consistent resullt.

You may also want to look at the sequences it is receiving using xmode2.

Hi Greg,

No, I don't have a joystick attached and I did not compile any special code for a joystick. Are there any commands you would like me to issue to reveal what daemons are running, etc.?

When I ran IRRECORD, I had to stop the lirc daemon, but I don't think I stopped the Mythtv backend and I know I didn't stop mysql. I can try that.

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: coming back to this
PostPosted: Sun Feb 08, 2009 3:05 pm 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
I am coming back to this after taking a long break from it.

I never was able to have the Sony satellite receiver correctly receive the remote control button codes from Mythtv. In the fall, the Sony receiver got retired and replaced with a Directv H23 satellite receiver, so I am kinda starting over with the IR sender process.

I'm still running R5F27 at this time. I've added in the codes for the new remote and tried it out. The satellite receiver does see button codes, but they don't appear to be correct. The receiver only seems to register 1 valid number code and no more. For example, if the channel is 355, then the receiver may get a number 3 and no other numbers. At that point, the receiver takes that number 3 and changes channels to channel 3.

I'm not sure what link in the process is bad. Is it my scripts? Is it the time delays in the scirpts? Is it my IR sender? Is there a way to record the codes coming out of the IR sender (Iguanaworks RS-232 IR sender/receiver)?

Here is the setup process I went through to get where I am now.

As before, I stopped all the LIRC processes and used "IRRECORD -d /dev/lirc0" to capture the button codes from the new HD reciever remote control. I pasted those codes into my /etc/lirc/lircd.conf file. Here is the relavant section of that file:
Code:
# brand:                       Directv (Hughes)
# model no. of remote control:  H23
# devices being controlled by this remote:  Directv H23
#

begin remote

  name   H23
  flags RAW_CODES
  eps            30
  aeps          100

  ptrail        706
  repeat     0     0
  gap    29914

      begin raw_codes

          name 1
             6085    1108    1311    1088     707     492
              707     490     708     491     710     491
              707    1091     708     490     708    1088
              709

          name 2
             6084    1109    1307    1091     684     514
              708     491     683     515     709     491
             1309     490     706     492    1308     489
              705

          name 3
             6111    1081    1311    1089     708     490
              707     491     710     491     707     491
             1307    1090     707     493    1308    1086
              708

          name 4
             6112    1081    1311    1088     708     490
              708     491     683     515     710    1089
              708     492     708     490    1308    1087
              707

          name 5
             6084    1109    1310    1089     707     491
              708     491     707     490     711    1088
              707    1092     707    1091     707     489
              708

          name 6
             6111    1085    1308    1088     708     491
              710     490     707     491     708    1091
             1308     488     710    1088     709    1088
              709

          name 7
             6112    1084    1309    1088     707     491
              710     491     707     490     709    1090
             1285    1112     707    1092    1307     489
              707

          name 8
             6087    1108    1309    1088     708     491
              709     491     707     491    1308     491
              707     490     709    1090    1309     488
              707

          name 9
             6110    1083    1309    1088     710     491
              707     490     708     491    1308     490
              708    1091     708    1090    1309    1086
              682

          name 0
             6109    1087    1307    1088     709     490
              708     490     708    1091     707     491
              710    1089     707    1091    1308     488
              708

          name enter
             6109    1084    1310    1089     707     490
              684     515     708    1091     708     490
             1308    1091    1307     492     707     488
              708

          name dash
             6109    1086    1306    1089     710     490
              708     491     708    1090     708     491
             1308     490     708    1090    1284    1111
              707

          name select
             6085    1109    1308    1088     708     493
              708     490    1308     491     708    1090
              681    1118    1308    1088    1308     489
              707

          name ch+
             6111    1082    1310    1088     708     491
              707     491     709     492    1307    1089
              710    1089    1307     491    1308     486
              686

          name ch-
             6109    1085    1307    1091     706     492
              684     515     708     490    1308    1091
             1308     491    1305     490    1309    1088
              683

          name exit
             6085    1108    1284    1115     708     490
              710     488    1309     490     683    1116
             1308     490    1308    1088    1309    1088
              705

          name power
             6084    1109    1283    1116     683     515
              707     491     708    1090     708     490
              709     492     706    1093     705    1089
              683

      end raw_codes

end remote

Does that part look normal?

Next, I have the /usr/local/bin/change1.sh script which is called when a channel change is to be sent to the satellite receiver. Here is how that looks:
Code:
#!/bin/bash
# Uncomment this for debugging
#set -vx
     
# This is the device number of the PVR-150 card, change this number to proper number for your card(s)
# If the card is /dev/video0, then the device number will be zero.
DEVICE="1"

exec >>/var/log/mythtv/changer$DEVICE.log 2>&1
echo "Called as: $0 $*"

FREQ_TBL="us-bcast" # Possibly "us-cable", "us-cable-hrc", "us-bcast"...
BRIGHTNESS=128 # Picture brightness, actually the black level. [0 - 255]
HUE=0          # Hue or color balance. [-128 - 127]
SATURATION=64  # Picture color saturation or chroma gain. [0 - 127]
CONTRAST=64    # Picture contrast or luma gain. [0 - 127]
VOLUME=60928   # Overall audio volume. [0 - 65535]

export HOME=/home/mythtv
echo "Setting channel to $1"

# CHANGE LINE BELOW TO THE CURRENT LOCATION/NAME
# OF YOUR EXISTING CHANNEL-CHANGE SCRIPT!
# MINE IS "/usr/local/bin/channel_change.sh". LEAVE THE $1

/usr/local/bin/channel_change.sh $1

(nohup /usr/local/bin/delayed_settings.sh $DEVICE \
                                          $BRIGHTNESS \
                                          $HUE \
                                          $SATURATION \
                                          $CONTRAST \
                                          $VOLUME & exit) &
exit 0

Then, there is the /usr/local/bin/channel_change.sh script which is called by the previous script to send the channel numbers via the IR sender. Here is how that looks:
Code:
#!/bin/bash
# location /usr/local/bin/channel_change.sh
 
REMOTE_NAME=H23

# send the digits one at a time
for digit in $(echo $1 | sed -e 's/./& /g'); do
#   sleep 0.3
   /usr/bin/irsend SEND_ONCE $REMOTE_NAME $digit
   sleep 1
done

# make this script executable ---> chmod +x channel_change.sh

Do you see anything obviously wrong with my scripts? I need several more sets of eyes looking over my setup.

Help is greatly appreciated!
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: Sun Feb 08, 2009 8:11 pm 
Offline
Joined: Wed Mar 07, 2007 9:51 am
Posts: 173
Location: Uniontown, PA
It sounds like the digits are sent too slowly, so change the number in the 'sleep' line in the change sctipt. The 0.3 setting that you have commented out may work.

Tinker with the setting until it catches all the digits.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Feb 09, 2009 1:55 am 
Offline
Joined: Sat Aug 19, 2006 11:53 pm
Posts: 39
Location: Monterey, CA USA
I may be way off, but I once had a similar problem w/my DirecTV receiver. It would not change to double digit numbers like yours, ie 355, where the 55 part wouldn't work.

Here's my script, and you can see the added change to fix it in the middle. I found it here in the forums and it's worked great. Hope it helps.

Code:
#!/bin/sh

REMOTE_NAME=directivo
cmd="$1"

case $cmd in
    [0-9]*)

#the section below was added to fix not changing to double digits
if [ $1 -lt 10 ] ; then
  sleep 0.2
  /usr/bin/irsend --device=/dev/irblasterd SEND_ONCE $REMOTE_NAME 0
  sleep 0.5
fi

if [ $1 -lt 100 ] ; then
  sleep 0.2
  /usr/bin/irsend --device=/dev/irblasterd SEND_ONCE $REMOTE_NAME 0
  sleep 0.5
fi
#the section above was added to fix not changing to double digits

    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

_________________
R5F27 combined backend/frontend
Nvidia 6200 graphics card
Intel P4 1.8, 768Meg PC133, Seagate 300GB & 500GB (PATA) in LVM
Hauppauge PVR150
Iguana Works serial IR transceiver


Top
 Profile  
 
 Post subject: could you explain a bit?
PostPosted: Tue Feb 10, 2009 11:55 pm 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
Hi Ghede,

I'm not fluent in bash scripts. Most of what I've done in Linux has been to mimic what I see others doing - not always knowing what every line of code does...

I see the familiar digit send routine tucked inside your script. I'm not sure why the rest of the code is around it, though.

Can you explain why the cmd="$1" is needed and what it does?
What is the "case $cmd" statement doing?
What is being sent with the line "irsend SEND_ONCE $REMOTE_NAME $cmd "?

Clarification appreciated,
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: Wed Feb 11, 2009 1:15 am 
Offline
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location: Adelaide, Australia
cmd=$1
Simply places the first argument passed to the script into the variable cmd

case $cmd is a statement that directs execution to one section or another based on the value of $cmd. If $cmd is purely numeric, it runs the first section which pads the numbers sent with zeroes so that there are always three digits sent. Otherwise it runs the second section which passes the first argument to the script directly to irsend.

For example, this allows you to call:
channel_change.sh 3
which will send 0 0 3
channel_change.sh 203
which will send 2 0 3
or channel_change.sh volup
which will send volup


Top
 Profile  
 
PostPosted: Sun Feb 15, 2009 6:55 pm 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
For those who are following along, Greg and I had an IRC chat this weekend and diagnosed my problems down to the LIRC codes in my /etc/lirc/lircd.conf file. Some of the number button codes were off by enough that the satellite receiver didn't recognize them at all.

I just tried a search outside the lirc.org website and found a posting of H23 codes here:
http://www.linuxquestions.org/questions/linux-software-2/lircd.conf-file-for-directv-h23-high-def-receiver-700927/?posted=1#post3444703

I'm going to give these a try. If his codes work for me, I'll stop there.

If not, I am going to have to re-record the LIRC codes for this remote to try and get a more consistant set of timing numbers.

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: I'm farther!
PostPosted: Wed Feb 18, 2009 12:20 am 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
Well, I'm farther along! Thanks for all the suggestions and education thus far!

I've got all the number buttons being recognized by the satellite receiver (using my own IRRECORD files) and I used the double digit fix script that was posted above. All these things are helping.

When I select Watch TV in the Mythtv menu, the starting channel that I have entered in the Mythtv setup is sent to the satellite receiver and it responds correctly. Right now it is set to 355.

While in Watch TV, I enter channel numbers with the Mythtv remote and the Directv receiver seems to be ignoring the FIRST number that is sent. So, if I send a 356, all it sees is the 56. If I send 355, all it sees is the 55.

If I exit Watch TV and then select Watch TV again, Mythtv sends the channel code for the last channel that was entered into the Mythtv remote, and the satellite receiver correctly receives all 3 numbers!

So, in certain situations, the channel changing works, and in others it does not. I'm not sure what to make of this?
If all that is wrong is changing satellite channels in Watch TV mode, I can live with that.

I do have one last how-to question. In the channel_changing.sh script, is there a way I can send a channel-up button command CONDITIONAL on specific channel numbers? For example, on Directv, channel 355 has a HD version and a Standard Definition version - both with channel 355. If you send 355 to the satellite receiver, you get the HD version (which has the wrong aspect ratio for the PVR-150 card). If you do a channel-up after you are on 355, then you are taken to the Standard Definition version of 355 - which is what I'd like to record.

So, is there a way I can modify the channel_changing.sh script to detect that specific channels (like 355) have passed through the script, and then have it send a channel-up command afterwards?

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: Wed Feb 18, 2009 8:53 pm 
Offline
Joined: Sat Aug 19, 2006 11:53 pm
Posts: 39
Location: Monterey, CA USA
Try this... try removing the HD channels from your line-up. Using Schedule's Direct? What I've done in the past is to modify the Schedule's Direct line-up at their site and then remove the unwanted channels from the database either directly or using MythWeb.

_________________
R5F27 combined backend/frontend
Nvidia 6200 graphics card
Intel P4 1.8, 768Meg PC133, Seagate 300GB & 500GB (PATA) in LVM
Hauppauge PVR150
Iguana Works serial IR transceiver


Top
 Profile  
 
 Post subject: that would work IF...
PostPosted: Wed Feb 18, 2009 9:36 pm 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
ghede wrote:
Try this... try removing the HD channels from your line-up. Using Schedule's Direct? What I've done in the past is to modify the Schedule's Direct line-up at their site and then remove the unwanted channels from the database either directly or using MythWeb.

I think your idea would work IF the HD channels had different channel numbers than the SD channels. This is Directv's BAD. They have pairs of HD and SD channels with the SAME channel number. (example: CNBC HD is 355 and CNBC SD is also 355). Since we are sending channel numbers to the sat receiver, there is no way for the sat receiver to know which channel we want (HD or SD), unless I can send the channel-up button to switch from HD to SD. See what I've got to tackle?

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  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 37 posts ] 
Go to page Previous  1, 2, 3  Next



All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 13 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:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu