I had another productive chat with Greg Frost last night (my night, his morning)! Thanks Greg!
Greg gave me the correct syntax for the IF statement I needed to send a conditional channel-up button code when I switch to a known HD satellite channel that has an SD channel on the same Directv channel number. Greg also simplified the part of the script that pads the channel number with leading zeros. Now Mythtv is able to change channels to the correct satellite channels. My current channel_change.sh script looks like this.
Code:
#!/bin/sh
# location /usr/local/bin/channel_change.sh
REMOTE_NAME=H23
cmd="$1"
# the following section pads the channel number with leading zeros and
# fixes the problem of having double digits in a channel number - somehow.
case $cmd in
[0-9]*)
for digit in $(printf "%03d" $1 | sed -e 's/./& /g'); do
irsend SEND_ONCE $REMOTE_NAME $digit
sleep 0.5
# If things work OK with sleep 1, try this for faster channel changes:
# sleep 0.3
done
# the following section checks to see if the channel passing through the
# script is a channel where Directv has an HD and an SD channel on the
# same channel number. If it is a known HD/SD channel, a channel-up
# button is sent to get to the SD channel.
if [ "$cmd" = "355" ] || [ "$cmd" = "244" ] || [ "$cmd" = "242" ] || [ "$cmd" = "249" ] || [ "$cmd" = "202" ] ; then
irsend SEND_ONCE $REMOTE_NAME enter
sleep 0.5
irsend SEND_ONCE $REMOTE_NAME ch+
fi
;;
*)
irsend SEND_ONCE $REMOTE_NAME $cmd
;;
esac
# make this script executable ---> chmod +x channel_change.sh
# location /usr/local/bin/channel_change.sh
REMOTE_NAME=H23
cmd="$1"
# the following section pads the channel number with leading zeros and
# fixes the problem of having double digits in a channel number - somehow.
case $cmd in
[0-9]*)
for digit in $(printf "%03d" $1 | sed -e 's/./& /g'); do
irsend SEND_ONCE $REMOTE_NAME $digit
sleep 0.5
# If things work OK with sleep 1, try this for faster channel changes:
# sleep 0.3
done
# the following section checks to see if the channel passing through the
# script is a channel where Directv has an HD and an SD channel on the
# same channel number. If it is a known HD/SD channel, a channel-up
# button is sent to get to the SD channel.
if [ "$cmd" = "355" ] || [ "$cmd" = "244" ] || [ "$cmd" = "242" ] || [ "$cmd" = "249" ] || [ "$cmd" = "202" ] ; then
irsend SEND_ONCE $REMOTE_NAME enter
sleep 0.5
irsend SEND_ONCE $REMOTE_NAME ch+
fi
;;
*)
irsend SEND_ONCE $REMOTE_NAME $cmd
;;
esac
# make this script executable ---> chmod +x channel_change.sh
April 19 update:
During a recent tweak session, I found that I needed to send the ENTER button code before I did the Channel Up button to take me to the standard definition versions of the channels. After I figured that out, I was set to catch all the tv I wanted from the heavens!
Right now, I am pretty pleased. It was almost a year ago that I started trying to control the satellite receiver with Mythtv. Now the dream of perfection is reality! There is more tv I'd like to record on the satellite than I have free time to watch! Holy cow!
Important detail for Iguanaworks Serial IR transceiver users:
One of the last tweaks to get the satellite receiver to consistently receive the button codes being sent to it was to decrease the intensity of the infrared LED on the Iguanaworks IR blaster. The Iguanaworks circuit has a very small value for the LED current limiting resistor, so that the LED is bright and the signal can travel long distances. Well, apparently, it's too bright for short distances - with the LED 2-4 inches away from the satellite receiver. I found that if I used the circuit as shipped from Iguanaworks, the IR LED had to be about 6 feet or more from the satellite receiver before it could consistently read the button codes correctly! So, after I increased the value of the IR LED resistor R1 from 3 Ohms up to about 2500 Ohms, the satellite receiver had consistent, accurate reception of the sent button codes! Woooo hoooo!!
Eric