I found this information:
Quote:
The ea65 driver
This section describes the ea65 driver which works with the front panel VFD display on the AOpen XC Cube-AV EA65 media barebone.
EA65 front panel VFD
The AOpen XC Cube-AV is a barebone designed for using as a media center. It comes with a front panel display which is capable of displaying one line of 9 characters.
The display is internally connected to the serial port (/dev/ttyS1) with a fixed rate of 9600 baud.
The display uses 13 segments per character. That's why the driver provides no custom characters like the ones for dot matrix displays do.
The front panel furthermore has 9 keys which are illuminated by blue LEDs. The LEDs can be controlled with the backlight functions. The keys are not supported by this driver. The red LED (RECORD) can be controlled with the output command of LCDd.
Configuration in LCDd.conf
[ea65]
Brightness = BRIGHTNESS
Set the brightness for the front LEDs if backlight is switched on. Legal values for BRIGHTNESS are in the range between 0 and 1000. Values under 300 set the LEDs off. Values between 300 and 700 turn on the LEDs with half brightness. Values above 700 turn on the LEDs with full brightness. If not given, it defaults to 500.
OffBrightness = OFFBRIGHTNESS
Set the brightness for the front LEDs if backlight is switched off. Legal values for OFFBRIGHTNESS are in the range between 0 and 1000. Values under 300 set the LEDs off. Values between 300 and 700 turn on the LEDs with half brightness. Values above 700 turn on the LEDs with full brightness. If not given, it defaults to 0.
|
http://lcdproc.sourceforge.net/docs/...#ea65-features
I have already installed, but facing some troubles:
Code:
root:# LCDd -f -r 4
LCDd version 0.5.6 starting
Built on Feb 6 2013, protocol version 0.3, API version 0.5
Using Configuration File: /usr/local/etc/LCDd.conf
Set report level to 4, output to stderr
LCDd 0.5.6, LCDproc Protocol 0.3
Part of the LCDproc suite
Copyright (C) 1998-2012 William Ferrell, Selene Scriven
and many other contributors
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software Foundation,
Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
Server running in foreground
Listening for queries on 127.0.0.1:13666
Could not open driver module server/drivers/ea65.so: server/drivers/ea65.so: can
not open shared object file: No such file or directory
Driver [ea65] binding failed
Module server/drivers/ea65.so could not be loaded
Could not load driver ea65
There is no output driver
Critical error while initializing, abort.
server://mnt/linux/lcdproc
root:# /s dev
bash: /s: No such file or directory
server://mnt/linux/lcdproc
I managed to get it to this point now, after downloading a separate ea65.so from a rpm package and changing the default driver path:
Code:
root:# LCDd -f -r 4
LCDd version 0.5.6 starting
Built on Feb 6 2013, protocol version 0.3, API version 0.5
Using Configuration File: /usr/local/etc/LCDd.conf
Set report level to 4, output to stderr
LCDd 0.5.6, LCDproc Protocol 0.3
Part of the LCDproc suite
Copyright (C) 1998-2012 William Ferrell, Selene Scriven
and many other contributors
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software Foundation,
Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
Server running in foreground
Listening for queries on 127.0.0.1:13666
Key "Escape" is now reserved exclusively by client [-1]
Key "Enter" is now reserved shared by client [-1]
Key "Up" is now reserved shared by client [-1]
Key "Down" is now reserved shared by client [-1]
screenlist_switch: switched to screen [_server_screen]
Connect from host 127.0.0.1:41693 on socket 5
Client on socket 5 disconnected
Connect from host 127.0.0.1:41694 on socket 5
Client on socket 5 disconnected
I am not getting anywhere much. Today, I realized that the front panel, VFD and the remote receiver are both supposed to be plugged into the com2 as quotted from the manual:
Quote:
Display [ Command code = 34h ] - A0h + 01h + 34h + 81h + xxh
Eject [ Command code = 35h ] - A0h + 01h + 35h + 81h + xxh
Chapter Title [ Command code = 36h ] - A0h + 01h + 36h + 81h + xxh
Time [ Command code = 37h ] - A0h + 01h + 37h + 81h + xxh
Repeat [ Command code = 38h ] - A0h + 01h + 38h + 81h + xxh
STOP(on Panel) [ Command code = 80h ] - A0h + 01h + 80h + 81h + xxh
Delay time of continue sending pressed key - A0h + 01h + DCh + 81h + 8nh
ps: n = delay n * 0.1 sec (when instant ON, VFD auto set default delay time = 0.3 sec)
--- n (min) = 01h = 1 (min value of delay time = 1 * 0.1 sec = 0.1 sec)
--- n (max) = 0Fh = 15 (max value of delay time = 15 * 0.1 sec = 1.5 sec)
Example: Delay 0.5 sec - A0h + 01h + DCh + 81h + 85h
(1) Enable COM2 :
(2) Baud Rate : 9600 bps.
(3) COM2 (I/O Port address 2F8h, IRQ3).
|
I didnt unplug anything, so anything that came with the system should stay there (in place). So I changed my /etc/serial.conf file:
Code:
# These are the standard COM1 through COM4 devices
#
/dev/ttyS0 uart 16450 port 0x3F8 irq 4
/dev/ttyS1 uart 16450 port 0x2F8 irq 3 baud_base 9600
I uncommented the first two line, by intuition, the ttyS0 should be COM1, that I think is the serial port with is blue at the back of the machine. ttyS1 is COM2, and I guess is used up by the VFD and remote receiver. I then tried to examine the port COM2:
Code:
ted:$ dmesg | grep ttyS
[ 1.106170] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 1.128318] 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 18.530191] ttyS1: LSR safety check engaged!
[ 18.536995] ttyS1: LSR safety check engaged!
[ 1521.066158] ttyS1: LSR safety check engaged!
[ 1657.220468] ttyS1: LSR safety check engaged!
This doesn't look good to me, at least
http://oss.sgi.com/LDP/HOWTO/Serial-HOWTO-15.html says its bad:
Quote:
15.14 "LSR safety check engaged"
LSR is the name of a hardware register. It's claimed that this means there is no serial port at the specified address.
|
But I am gonna try it any way:
Code:
root:# cat /dev/ttyS1
cat: /dev/ttyS1: Input/output error
server://home/ted
root:# cat /dev/ttyS0
^C
ttyS1 returns input/output error, while ttyS0 seems to work fine.
Here is:
Code:
root:# cat /proc/tty/driver/serial
serinfo:1.0 driver revision:
0: uart:16450 port:000003F8 irq:4 tx:0 rx:0
1: uart:16450 port:000002F8 irq:3 tx:0 rx:0 CTS|DSR|CD|RI
2: uart:unknown port:000003E8 irq:4
3: uart:unknown port:000002E8 irq:3
I hope anyone knows anything about this.
Thanks,
Ted
