I've recently installed R5B7 using the 'auto-install'. I ran the irblaster configuration script during install which did not suceed as it failed to connect to the COM2 port to which my ir blaster hardware is connected.
Everything works now but the irblaster. I posted the install problem the the 'Install' forum which was promptly deleted
but not before someone answered that there is a current issue with the irblaster configuration script (used by the installer) in R5B7 and that they are working on it. In any case I am using the following in the /etc/irblaster directory:
the hardware.conf file:
Quote:
# /etc/irblaster/hardware.conf
#
# Author: Greg Frost
# The COM Port used by the IRBlaster. Set it to "COM1" "COM2" or "".
IRBLASTER_SERIAL_PORT="COM2"
# Set this to the lirc device that will be used by lirc_serial. In my case
# it is /dev/lirc. I have a USB remote, so my remote does not use the
# /dev/lirc device, so it is used by lirc_serial for my ir blaster. If you
# have a remote that uses /dev/lirc, the blaster may user /dev/lirc1. Not
# sure.
IRBLASTER_DEVICE="/dev/lirc"
#
# Author: Greg Frost
# The COM Port used by the IRBlaster. Set it to "COM1" "COM2" or "".
IRBLASTER_SERIAL_PORT="COM2"
# Set this to the lirc device that will be used by lirc_serial. In my case
# it is /dev/lirc. I have a USB remote, so my remote does not use the
# /dev/lirc device, so it is used by lirc_serial for my ir blaster. If you
# have a remote that uses /dev/lirc, the blaster may user /dev/lirc1. Not
# sure.
IRBLASTER_DEVICE="/dev/lirc"
the change_chan.sh file:
Quote:
#!/bin/bash
echo "changing to $1"
REMOTE_NAME=DCT2000
for digit in $(echo $1 | sed -e 's/./& /g'); do
sleep 0.2
/usr/bin/irsend --device=/dev/irblaster SEND_ONCE $REMOTE_NAME $digit
sleep 0.5
done
echo "changing to $1"
REMOTE_NAME=DCT2000
for digit in $(echo $1 | sed -e 's/./& /g'); do
sleep 0.2
/usr/bin/irsend --device=/dev/irblaster SEND_ONCE $REMOTE_NAME $digit
sleep 0.5
done
the irblasterd.conf file:
Quote:
#
# this config file was automatically generated
# using lirc-0.6.6(serial) on Fri Mar 28 22:46:44 2003
#
# contributed by shane bradley
#
#
#
# brand: Motorola
# model no. of remote control: DCT2000
# devices being controlled by this remote:
#
begin remote
name DCT2000
bits 16
flags SPACE_ENC|CONST_LENGTH
eps 30
aeps 100
header 9036 4424
one 556 2185
zero 556 4424
ptrail 556
gap 100025
toggle_bit 0
begin codes
HELP 0x000000000000B3F2
POWER 0x000000000000AFF9
MUTE 0x0000000000000FF7
PAGE+ 0x000000000000A3F3
PAGE- 0x00000000000023FB
LOCK 0x00000000000097F6
EXIT 0x000000000000B7F4
AUP 0x000000000000D3F6
ADOWN 0x00000000000053FE
ALEFT 0x00000000000093F1
ARIGHT 0x00000000000013F9
OK 0x00000000000077F8
GUIDE 0x000000000000F3F4
MENU 0x00000000000067F9
VOL+ 0x0000000000004FF3
VOL- 0x0000000000008FFB
LAST 0x00000000000037FC
FAV 0x00000000000057FA
CH+ 0x0000000000002FF5
CH- 0x000000000000CFFD
A 0x00000000000017FE
B 0x0000000000001BF1
C 0x000000000000EBF9
1 0x0000000000007FF0
2 0x000000000000BFF8
3 0x0000000000003FF4
4 0x000000000000DFFC
5 0x0000000000005FF2
6 0x0000000000009FFA
7 0x0000000000001FF6
8 0x000000000000EFFE
9 0x0000000000006FF1
0 0x000000000000FFFF
BYPASS 0x000000000000D7F2
MUSIC 0x000000000000F7F0
STOP 0x00000000000063FD
PAUSE 0x00000000000007FF
PLAY 0x000000000000E3F5
REW 0x00000000000087F7
REC 0x00000000000073FC
FFWD 0x00000000000047FB
end codes
end remote
# this config file was automatically generated
# using lirc-0.6.6(serial) on Fri Mar 28 22:46:44 2003
#
# contributed by shane bradley
#
#
#
# brand: Motorola
# model no. of remote control: DCT2000
# devices being controlled by this remote:
#
begin remote
name DCT2000
bits 16
flags SPACE_ENC|CONST_LENGTH
eps 30
aeps 100
header 9036 4424
one 556 2185
zero 556 4424
ptrail 556
gap 100025
toggle_bit 0
begin codes
HELP 0x000000000000B3F2
POWER 0x000000000000AFF9
MUTE 0x0000000000000FF7
PAGE+ 0x000000000000A3F3
PAGE- 0x00000000000023FB
LOCK 0x00000000000097F6
EXIT 0x000000000000B7F4
AUP 0x000000000000D3F6
ADOWN 0x00000000000053FE
ALEFT 0x00000000000093F1
ARIGHT 0x00000000000013F9
OK 0x00000000000077F8
GUIDE 0x000000000000F3F4
MENU 0x00000000000067F9
VOL+ 0x0000000000004FF3
VOL- 0x0000000000008FFB
LAST 0x00000000000037FC
FAV 0x00000000000057FA
CH+ 0x0000000000002FF5
CH- 0x000000000000CFFD
A 0x00000000000017FE
B 0x0000000000001BF1
C 0x000000000000EBF9
1 0x0000000000007FF0
2 0x000000000000BFF8
3 0x0000000000003FF4
4 0x000000000000DFFC
5 0x0000000000005FF2
6 0x0000000000009FFA
7 0x0000000000001FF6
8 0x000000000000EFFE
9 0x0000000000006FF1
0 0x000000000000FFFF
BYPASS 0x000000000000D7F2
MUSIC 0x000000000000F7F0
STOP 0x00000000000063FD
PAUSE 0x00000000000007FF
PLAY 0x000000000000E3F5
REW 0x00000000000087F7
REC 0x00000000000073FC
FFWD 0x00000000000047FB
end codes
end remote
I know my ir blaster hardware is working as I used it successfully for more than a year with an R4xx distro. irblaster seems to load ok yet when I run
/etc/irblaster/change_chan.sh 2 the first time, it gives no error but will not "blast" the channel change. when I run the command the second time it gives me errors such as:
Quote:
changing to 4
/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
I think I have 2 options at this point:
a. get irblaster working
b. forget irblaster and use myth-ledxmit (see http://losdos.dyndns.org:8080/public/my ... _LIRC.html)
My question is can irblaster be made to work? I've seen in some threads that the order in which lirc and irblaster loads is significant so I made lirc's order number 19 and irblaster's 20 (in /etc/rc5.d).
Where should I look now? How do I verify that the irblaster is properly installed in the first place?