1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/graphlcd-base/docs/DRIVER.hd61830 Wed Feb 06 17:32:55 2008 +0000
1.3 @@ -0,0 +1,96 @@
1.4 +---------------------------------------------------------------------
1.5 +GraphLCD driver library
1.6 +
1.7 +The HD61830 driver
1.8 +---------------------------------------------------------------------
1.9 +
1.10 +Description
1.11 +-----------
1.12 +The HD61830 driver supports LC displays that use the Hitachi HD61830
1.13 +controller, connected to the parallel port of your PC.
1.14 +
1.15 +
1.16 +Wirings
1.17 +-------
1.18 +The HD61830 driver supports the following connection on a parallel
1.19 +port:
1.20 +
1.21 + printerport LCD other
1.22 + ----------- ---------- ----------
1.23 + GND (18) GND (01) GND (Ground)
1.24 + VDD (02) +5V (V Controller)
1.25 + V0 (03) +5V..-15V (Contrast)
1.26 + INIT (16) RS (04) (Register Select)
1.27 + nAUTO (14) R/W (05) (Read 1/Write 0)
1.28 + nSTRB (01) EN (06) (Enable)
1.29 + D0 (02) D0 (07) (DataBit0)
1.30 + D1 (03) D1 (08) (DataBit1)
1.31 + D2 (04) D2 (09) (DataBit2)
1.32 + D3 (05) D3 (10) (DataBit3)
1.33 + D4 (06) D4 (11) (DataBit4)
1.34 + D5 (07) D5 (12) (DataBit5)
1.35 + D6 (08) D6 (13) (DataBit6)
1.36 + D7 (09) D7 (14) (DataBit7)
1.37 + nCS (15) GND (Chip Select)
1.38 + nRES (16) +5V (Reset)
1.39 + VEE (17) -12V (V LCD)
1.40 + nDO (18) (not connected)
1.41 +
1.42 +Note: The pin numbering may vary with other displays.
1.43 +
1.44 +
1.45 +Configuration Parameters
1.46 +------------------------
1.47 +The HD61830 driver supports the following parameters in config file:
1.48 +
1.49 +Device
1.50 + Instead of using the direct output via port address (see Port), you
1.51 + can use the parport device (/dev/parportX). The advantage over the
1.52 + direct output via port address is that this works for non-root users
1.53 + also. But it's a little bit slower. The modules ppdev.o, parport.o
1.54 + and parport_pc.o must be loaded or compiled into the kernel.
1.55 +
1.56 +Port
1.57 + Sets the port address of the parallel port. If this parameter is not
1.58 + given, 0x378 is used. To use this direct output, the program that
1.59 + uses the driver library has to be started with user 'root'.
1.60 +
1.61 +Width
1.62 + Sets the horizontal size of the display. If this parameter is not
1.63 + given, a default value of 240 pixels is used.
1.64 +
1.65 +Height
1.66 + Sets the vertical size of the display. If this parameter is not
1.67 + given, a default value of 128 pixels is used.
1.68 +
1.69 +UpsideDown
1.70 + Rotates the display output by 180 degrees. This might be useful, if
1.71 + the LCD is mounted upside-down.
1.72 + Possible values: 'yes', 'no'
1.73 + Default value: 'no'
1.74 +
1.75 +Invert
1.76 + Inverts the display.
1.77 + Possible values: 'yes', 'no'
1.78 + Default value: 'no'
1.79 +
1.80 +AdjustTiming
1.81 + To get a timing that is as accurate as possible, the drivers measure
1.82 + the time for port commands (see: benchmark in syslog). You might
1.83 + decrease or increase the time to wait after port commands with this
1.84 + parameter. Normally, there is no need to change this parameter.
1.85 + Possible values: -50 <= x <= 50
1.86 + Default value: 0
1.87 +
1.88 +RefreshDisplay
1.89 + Normally, most of the drivers do not update the whole display, but
1.90 + only the areas that have changed since last update. So it might be,
1.91 + that some faulty pixels would stay a longer time. To avoid this, the
1.92 + plugin makes a complete refresh from time to time. This parameter
1.93 + defines how often a complete refresh will be done.
1.94 + e.g.: A value of 5 means, that the plugin will make a complete
1.95 + refresh on every 5th update.
1.96 + A value of 0 completely disables complete refreshs.
1.97 + Possible values: 0 <= x <= 50
1.98 + Default value: 5
1.99 +