(variable resistor)
.------.
Vcc ---| 10k |--- GND
`---^--'
/|
|
Vlc
]]>
<title>Keypad</title> You can connect a keypad with most connection types. The maximum supported number of keys differs per type. There are several ways to connect the keys to the input pins. <title>Direct Keys</title> If you connect a key like sketched below, then you can only connect one key per input pin. It is a simple solution if you need only few keys. <title>HD44780: Direct Keys</title> O 5V
|
|
-
| | 10k
| |
-
|
+-----------o input (X)
|
|
o
\
o
|
|
=== GND
]]>
By default, the following keystrokes are generated by the different keys: <title>HD44780: Direct Key Mapping</title> key index mapped string X1 A X2 B X3 C X4 D X5 EYou can change the mapping using the KeyDirect_NUM configuration option, where NUM is the subscript to the X in the table above.
<title>Matrix Keys</title> Using a matrix, we can connect much more keys. To simplify the drawing here, we replace all switches with an @ symbol: <title>HD44780: Single Matrix Key</title> X line
|
|
Y line ---+--------- | | | o | = --@-- \ | | o | | | +---+ | |
]]>
We connect the matrix of keys like this: <title>HD44780: Complete Key Matrix</title> Y1 o---|<---@--@--@ | | | Y2 o---|<---@--@--@ | | | Y3 o---|<---@--@--@ | | | Y4 o---|<---@--@--@ O 5V | | | | diodes | | | ___ | 1N4148 +----------||---+ | | | ___ | | +-------||---+ | | | ___ | | | +----|___|---+ resistors 22k | | | o o o X1 X2 X3]]>
As you can see, you need 1 resistor per X line, and 1 diode per Y line. By default, lcdproc will presume that you have a keypad with a layout like a telephone connected, with X and Y lines connected as show. To be more precise, it assumes this mapping: <title>HD44780: Matrix Keypad Layout</title> X1 X2 X3 X4 X5 Y1 1 2 3 A E Y2 4 5 6 B F Y3 7 8 9 C G Y4 * 0 # D H O 5V
|
.-.
| | 4k7 or 22k
diodes | |
1N4148 '-'
___ |
Y1 o---|<---o o---+ ___ | Y2 o---|<---o o---+ ___ | Y3 o---|<---o o---+ ___ | Y4 o---|<---o o---+----o return line
]]>
If the driver generates keypresses without that you actually press a key, it might be that the unconnected input lines are picking up electromagnetic waves from the air. In that case connect the unconnected input lines (pin 10, 11, 12, 13 and 15 of the LPT) to VCC = 5V. <title>Backlight</title> A small extension allows you to switch the backlight of the display on and off. At the moment only the4bit and winamp
connection types support this.
The extension uses one output pin, you cannot use that pin for other
functions anymore. The wiring looks like this:
<title>HD44780: Backlight Wiring</title>
O 5V
___ |
+---|___|---+
LPT Sub-D connector | 4k7 |
| |e
___ | b |/
BL pin o------------|___|---+---------|
1k |
BC327 |c
| LCD connector
|
+--------o 15 backlight
+--------o 16 GND backlight
|
=== GND
Note: 4k7 means 4,7 kOhm. The BC327 transistor has the following connections:
_____
| |
|BC327|
|_____|
| | |
| | |
| | |
c b e
]]>
Sometimes the backlight connections are not on the 'main' connector, but on the side. If that is the case, there is usually NO RESISTOR present to limit the current through the LEDs. Therefore you should then add a resistor after the transistor of about 10 ohm (see display documentation). If you want the backlight to light a bit while it is "switched off", you can add a resistor bypassing the transistor from e to c, with a value of, say 47ohm or 22ohm. (My 4x20 has an internal resistor of 6ohm, so with 47 ohm extra it lights at only 1/9th. I like this. Joris.) <title>4bit</title> This wiring is originally based on "lcdtext" (by Matthias Prinke). <title>HD44780: 4bit Pinouts (1)</title> printer port <-> LCD name pin name pin GND VEE 1 +5V VCC 2 (contrast adjustment) VLC 3 D4 6 RS 4 GND RW 5 D6 8 EN 6 D0 2 D4 11 D1 3 D5 12 D2 4 D6 13 D3 5 D7 144bit connection type supports more than one display connected
to the same parallel port.
If you want to connect more than one display, then wire the all the displays to the
parallel port according to the scheme above with the exception of the EN
(pin 6) line of the LCDs.
For the second and further displays, you can find the wiring for the EN
(pin 6) line in the table below.
<title>HD44780: 4bit Pinouts (2)</title>
printer port
<->
LCD
name
pin
name
pin
D7
9
EN2
6 of 2nd display
D5
7
EN3
6 of 3rd display
STR
1
EN4
6 of 4th display
LF
14
EN5
6 of 5th display
INIT
16
EN6
6 of 6th display
SEL
17
EN7
6 of 7th display
IC1
-----------
| 4094 |
5V | shift reg | display
O | | keys
| 1| |4
+----|STR Q0|--------------------o 11 D4 Y1
| | |5
Data | 2| Q1|--------------------o 12 D5 Y2
D3 5 o-------------------------|D |6 | | Q2|--------------------o 13 D6 Y3 | 3| |7 D4 6 o-------------------------|CK Q3|--------------------o 14 D7 Y4 | | |14 | 15| Q4|--------------------o Y5 +----|OE |13 | Q5|--------------------o 4 RS Y6 | |12 | Q6|--------------------o Y7 | |11 | Q7|--------------------o Y8 | |9 | QS|-- +--o 5 RW | __|10 | | QS|-- === | | -----------
D2 4 o----------------------------------------------------------o 6 EN
D7 9 o----------------------------------------------------------o 6 EN2 (2nd LCD)
5V O-----+--------+-------------------------------+-----o 2 VCC
| | |
| | |
|100n O 16 .-.
--- IC1 | |<---o 3 Vlcd
--- O 8 | |10k
| | '-'
GND | | | 18..25 o-----------+--------+-----------------------+-------+-----o 1 GND | === GND
]]>
The second possible wiring is with 2 output lines. This one is a bit more complex. If you do not understand the schematic, do not build it. <title>HD44780: Serial LPT wiring ('complex')</title> IC2
-----------
| 74HCT164 |
| shift reg | display
| | keys
Data 1| |3
D3 5 o---------------------+---|D Q0|--------------------o 11 D4 Y1 | | |4 | 2| Q1|--------------------o 12 D5 Y2 +---|D |5 | Q2|--------------------o 13 D6 Y3 | |6 | Q3|--------------------o 14 D7 Y4 | |10 Clock 8| Q4|--------------------o Y5 D4 6 o-------------------------|CK |11 | Q5|--------------------o 4 RS Y6 ___ 9|\ 8 9|_ |12 +--||--+----| >o----|R Q6|--------------------o Y7 | 22k | |/ | |13 | --- IC1 | Q7|---+ +--o 5 RW | --- | | | 5V | | |100p ----------- | O === | | | | | === | .-. | | | |22k +--------------------------------------+ | | | '-' | ___ 11|\ 10 | 5|\ 6 +--||--+----| >o-------------------||-----+----| >o--o 6 EN 22k | |/ 22p |/ --- IC1 IC1 --- |22p | IC1=74HCT14 (6x Schmitt trigger inverter) ===
5V O--+-------+------+------+-----------------------+-----o 2 VCC
| | | | 13|\ 12 |
| | | +---| >o- |
|100n O 14 O 14 |/ .-.
--- IC1 IC2 | |<---o 3 Vlcd
--- O 7 O 7 1|\ 2 3|\ 4 | |10k
| | | +--| >o- +--| >o- '-'
GND | | | | |/ | |/ | 18..25 o------+-------+------+-------+----------+-----+-----+-----o 1 GND | === GND
]]>
<title>Serial LPT Keypad</title> To understand this part of the serialLpt documentation, you also need to read the keypad section in this document. serialLpt wiring supports a keypad. The 3 wires version supports 8 keys, or if you use multiple return lines up to 8 x 5 = 40 lines. The 2 wires version supports 7 keys, or with multiple return lines 7 x 5 = 35 keys. <title>HD44780: Serial LPT - Keypad return lines</title> printer port <-> keypad name pin pin nACK 10 X1 BUSY 11 X2 PAPEREND 12 X3 SELIN 13 X4 nFAULT 15 X5 1|\ 2 13|\ 12 ___
keypad o-----| >o------| >o---|___|---+---o input pin on LPT port return |/ |/ 220E | IC1 IC1 --- --- 1nF | ===
]]>
<title>Serial LPT Backlight</title> Also a backlight is supported. You will also need a port from the 74HCT14 for that. The BL output below should be connected to the BL input in the backlight section <title>HD44780: Serial LPT - Backlight extra circuit</title> ___ 3|\ 4
Data o-----|___|--+----| >o----o BL output
LPT-D3 470k | |/ --- IC1 --- |100nF | ===
]]>
<title>spi</title> This connection type drives a LCD in serial mode (supported on Hitachi HD66712, Samsung KS0073 and KS0074 (and clones) controllers) connected to some Linux SPI device. This connection type is currently only supported on Linux. It is strongly recommended to use a SPI implementation with hardware support, e.g. on the Raspberry Pi. As the SPI communication to the display cannot drive a backlight switch, this connection type features a BacklightDevice option that can use a GPIO pin exposed via sysfs (see eLinux GPIO). <title>FTDI FT2232D USB chip "ftdi"</title> You can use a FTDI FT2232D dual channel USB <-> parallel FIFO chip to connect a display via the USB bus. The chip is switched to bitbang mode and drives both channels as outputs to control the display in 8bit mode. <title>HD44780: 8bit FTDI</title> FTDI chip <-> LCD name pin name pin ADBUS0 24 D0 7 ADBUS1 23 D1 8 ADBUS2 22 D2 9 ADBUS3 21 D3 10 ADBUS4 20 D4 11 ADBUS5 19 D5 12 ADBUS6 18 D6 13 ADBUS7 17 D7 14 BDBUS0 40 RS 4 BDBUS1 39 RW 5 BDBUS2 38 EN 6 BDBUS3 37 BL Backlight (optional)The backlight line is driven high when the backlight is on. Therefore the standard backlight circuit () will not work. Use the following instead.
<title>hd44780/ftdi: Backlight Wiring</title> +--------o 16 GND backlight
|
small resistor .-.
10 - 47 ohm | |
depending on | |
display '-'
|
|c
___ b |/
BL pin o------------|___|-------------|
4k7 |\
BC547 |e
|
=== GND
]]>
Alternatively you can use a single channel FTDI FT245BM USB <-> parallel FIFO chip and use the display in its 4 bit mode. <title>HD44780: 4bit FTDI</title> FTDI chip <-> LCD name pin name pin D0 25 D4 11 D1 24 D5 12 D2 23 D6 13 D3 22 D7 14 D4 21 EN 6 D5 20 RS 4 D6 19 RW 5 D7 18 BL Backlight (optional)The LoS-Panel is a DIY device built using an Atmel ATtiny2313 and supports the following features: Drives displays with one controller. Switchable backlight. One 4x4 matrix keypad and 4 direct keys.
The direct keys are reported as a fifth column of a matrix keypad to LCDd. Column and rows are reported reverse (column 1 / row 1 is in the lower right corner) to LCDd which expects (1/1) to be the upper left corner. You have to take this into account when configuring keys. See for more information on this device. <title>VDR LCD serial device "vdr-lcd"</title> … to be documented … Please address Matteo Pillon for further information. <title>VDR-Wakeup module "vdr-wakeup"</title> The VDR-Wake module by Frank Jepsen is a serial IO extension module for the famous Linux-based VDR that allows to connect an LCD to it and supports LCDproc. See (German) for more information on VDR-Wakeup. <title>Pertelian X2040 "pertelian"</title> The Pertelian X2040 includes an HD44780 display with enclosure and USB connection.In order to work with LCDproc in Linux you need the usbserial.ko and ftdi_sio.ko kernel modules loaded. The display will then be available on a serial port /dev/ttyUSBx.
See the X4020 product page for more information. <title>PIC-an-LCD serial device "picanlcd"</title> The PIC-an-LCD module is also supported. It is not connected to the LPT port but to a serial port, which saves you from a lot of potential problems. To use it, specify the device to which you have connected the module in the config file with the Device setting. The default is /dev/lcd. It does not support a keypad nor backlight switching. As of 2012 these devices are not sold anymore. Search the Internet Archive for a copy of if you need the manual. <title>LCD serializer device "lcdserializer"</title> LCD serializer connection is technically the same as PIC-an-LCD with the same advantages, it uses the serial port making things really simple. Unlike PIC-an-LCD LCD serializer is not a commercial product. it's just a project found digging on the net and freely available. You have all the tools and the code to build it yourself and to customize the behaviour of the device. <title>What you need</title> Some electronic knowledge and familiarity with the soldering iron A PIC16F84 (I used PIC16F84A) or PIC16C54 JDM PIC programmer gputils and picprog installed on your GNU/Linux box <title>Burning the PIC</title> First, you need to download the ASM source for your PIC and then make the hex: $ gpasm lcd16f84_custom.asm Now the binary is ready to be flashed to the PIC. Connect the programmer with the PIC installed and issue the following command to see it burning ;-): $ picprog --erase --burn --input lcd16f84.hex --pic /dev/ttyS0 <title>Running lcdproc</title> It's time to build the operating circuit, remember this driver uses a baud rate of 9600, so JP2 need to be closed. Now power on the board. You should see OK on the LCD screen. Otherwise double-check all the connections. Change LCDd.conf to include the following statements in the[hd44780] section:
ConnectionType=lcdserializer
Device=/dev/ttyS0
Finally, start the daemon and relax watching lcdproc running.
<title>BWCT USB LCD module "bwctusb"</title>
The BWCT USB LCD module, sold by Bernd Walter Computing Technology
() is a little board
that can be piggy-packed to a HD44780 display and connects that to USB.
The board, driven by the bwctusb connection type,
does neither support a keypad for input, nor more than one single-controller
display, nor does it allow setting the backlight or brightness.
But you can set the display's contrast using software
(see the Contrast configuration parameter).
<title>Special configuration options</title>
If there is more than one BWCT USB module connected to the system,
the SerialNumber configuration parameter allows
selecting which display is used in LCDd.
<title>Till Harbaum's "lcd2usb"</title>
LCD2USB
is a cheap but powerful do-it-yourself interface to connect HD44780
based displays via USB, consisting of easily available parts only.
The device supports software adjustable contrast and backlight
as well as dual controller displays (required for 4*27 and 4*40).
It is based upon an Atmel AVR Mega8 CPU with a pure software implementation
of the USB protocol for the Atmel AVR microcontroller series.
The whole interface incl. the hardware layout is under a GPL like license.
This means that you can take these schematics and use it as a basis
for your own interface e.g. for a graphic LCD.
Two keys can be connected to the LCD2USB interface board.
They can generate three key events that can be mapped to key names using
the DirectKey_1 to DirectKey_3 commands:
one for each key and the third if the keys are pressed simultaneously.
With this 3-key setup, menus can be used (see example below).
This driver supports the original LCD2USB interface board as described above
as well as compatible devices like those sold by Lcdmod Kit
or those developed by Malte Pöggel.
<title>Special configuration options</title>
Besides the standard configuration options for hd44780 displays, the
lcd2usb connection type supports three additional options:
Contrast to set the display's contrast,
Brightness to set the display's brightness when the backlight is switched on and
OffBrightness to set the display's brightness when is backlight is switched off.
All three options expect a number in the range from 0 to 1000.
<title>HD44780: Configuration for LCD2USB</title>
[hd44780]
ConnectionType=lcd2usb
Contrast=850
Brightness=800
OffBrightness=0
Keypad=yes
Backlight=yes
Size=20x2
KeyDirect_1=Enter
KeyDirect_2=Down
KeyDirect_3=Escape
]]>
In order to make the lcd2usb connection type work with a 2-controller display
you may need to set the vSpan config option accordingly.
<title>Dick Streefland's "USBtiny"</title>
USBtiny
is a software implementation of the USB low-speed protocol for
the Atmel ATtiny microcontrollers. It is also the name of a 'reference
circuit' using the ATtiny2313.
The reference circuit features an IR receiver for remote controls and a LCD.
Due to hardware limitations of the ATtiny2313 the LCD does not have switchable
backlight, adjustable contrast, any keys, nor does it support displays with
more than one controller. If you want these features and do not require the
IR receiver we recommend to take a look at the LCD2USB
device.
LCDproc does not make use of the IR receiver. 3rd party software is required
to make it do anything, e.g. LIRC.
<title>USS-720 USB-to-IEEE 1284 Bridge (Belkin F5U002) "uss720"</title>
The USS-720 USB-to-IEEE 1284 Bridge is a fully featured USB to parallel chip that is used
in most (but not all) Belkin F5U002 USB Parallel Printer Adapters. Because these adapters are
inexpensive and readily available on the second-hand market, they provide an excellent solution
for users who want to experiment with a parallel port but only have USB ports on their computers.
Because the chip acts as a parallel port, the driver maintains the same features and wiring as
the 8-bit "winamp" driver. However, because most USB Parallel Printer Adapters use a centronics
printer connector, be sure to convert the pin numbering of the parallel port pins in the "winamp"
wiring to the pin numbering of the centronics port. Many tables are available on the internet
that illustrate how the pin numbering differs between the two.
<title>Special configuration options</title>
Because several manufacturers used the USS720 chip in their USB Parallel Printer Adapters, the
VendorID and ProductID options are configurable in the
LCDd.conf file.
Not all Belkin F5U002 USB Parallel Printer Adapters used the USS720 chip. Look for the dark grey
adapters with the removable USB cable for best results.
<title>I2C with Port-Expander</title>
If you have an I2C port available that is supported by your kernel
(through /dev/i2c*), you can add a I2C
port expander there (PCF8574P in this example).
<title>HD44780: PCF8574P port expander on I2C bus</title>
<title>Configuration</title>
<title>HD44780: Configuration for I2C with port expander</title>
If your port expander has different wiring you can re-assign the pins in the config file
<title>HD44780: Configuration for I2C with port expander
Alternative Wiring</title>
<title>HD44780: Configuration for I2C with port expander
alternative config</title>
The Device configuration setting denotes the device file
of your I2C bus (here /dev/i2c-0).
You have to load the kernel standard module i2c-dev.ko and
the bus driver, but no I2C
chip modules (e.g. pcf8574.ko)!
The Port config option contains the I2C
address of the I2C port expander
(here 0x20, the PCF8574 from the example above, with all address bits set to 0).
Bit 8 of the address (normally 0 in I2C addresses) has a special meaning: It tells the driver to treat the device as PCA9554 or similar, a device that needs a 2-byte command, and it will be stripped off the address.
<title>HD44780: Examples of I2C port expander addresses</title> Port value Meaning 0x20…0x27 PCF8574 with A[012]=0…7 0x38…0x3f PCF8574A with A[012]=0…7 0xa0…0xa7 PCA9554 with A[012]=0…7 0xa0…0xa7 PCA9554A with A[012]=0…7| buttons | | ^ | | | | | _________ ___________ ____________ | | | | | | | | | | | | | | | | | | | LCD | | | SPI | ENC28J60 | | UTP cable | | HD44780 |<--- | ATmega168 | <---> | ethernet |<========+------> PC running | | | | | | controller | | | LCDproc | | | | | | | | | | || || || | | | | | | | | | | | beeper | | |___________________________________________| | ethlcd AC Adapter
]]>
The device is "visible" to LCDproc just like any other HD44780 device. The difference is the wiring - instead of connecting the display directly to PC (via serial/parallel/usb port), it is connected via ethernet and the communication is done over TCP connection. The main feature is - that to power and control the LCD is needed single UTP cable. To use the driver, specify the device IP address or hostname, on which the ethlcd device is accessible by setting in config file the Device value. The default is ethlcd. <title>USBLCD adapter</title> The USBLCD adapter from Adams IT Services () is a small interface board which allows you to connect an alphanumerical display module based on the HD44780 or compatible controller to the USB. The display will be powered by the USB. It features a switchable backlight (on or off) and can be used with 16x2, 16x4 or 20x4 displays. Theusblcd connection type communicates with a kernel
driver by using a device file /dev/usb/lcdx.
The kernel driver providing this device currently only exists for Linux kernels
newer than 2.4.20-pre7.
As of 2007 these device are not sold anymore. This driver has been ported from
lcdproc 0.4.5 to support existing users.
<title>USB-4-all controller</title>
The USB-4-all controller board from Sprut ()
is a small interface board which allows you to connect different hardware to the USB.
The subdriver for LCDproc supports dual HD44780 displays and a 4x4 keypad as well as
software adjustable contrast and brightness (backlight).
<title>HD44780: USB-4-all - Display connection</title>
USB-4-all
LCD1
LCD2
name
pin
name
name
RB7
28
D7
D7
RB6
27
D6
D6
RB5
26
D5
D5
RB4
25
D4
D4
RB3
24
R/W
R/W
RB2
23
RS
RS
RB0
21
EN
RC0
11
EN
+---> LCD 16 (- Backlight)
|
=== GND
]]>
<title>HD44780: USB-4-all contrast control</title> LCD 3 (Contrast) |c 680R | ___ b |/ |+ RC2 o------|___|------| npn --- 10uF 22k |\ --- |e | | | | | === === GND ]]> <title>Raspberry Pi</title>This connection type supports a LCD connected to the GPIO header P1 on a Raspberry Pi. Displays with one or two controllers are supported.
It supports a switchable backlight connected to pin P1-11 by default. Use the switch circuit as described in .
The signal level on the GPIO pins is 3.3 V and they are said not to be 5 V tolerant. Therefore the R/W pin of the display must be wired to GND to prevent 5V logic appearing on the GPIO pins. For the same reason the backlight cicuit from must not be used. Powering a LCD that uses 5 V from pin P1-02 will work. Powering a LCD from 3.3 V (pin P1-01) will only work if it is designed for 3.3 V operation. <title>HD44780: Default pin mapping for Raspberry Pi</title> Connector <-> LCD Pin Name Pin Number Name Pin GPIO18 P1-12 D7 14 GPIO23 P1-16 D6 13 GPIO24 P1-18 D5 12 GPIO25 P1-22 D4 11 GPIO08 P1-24 EN 6 GPIO07 P1-26 RS 4 GND P1-06 RW 5 GPIO22 P1-15 EN2 Second controller (optional) GPIO17 P1-11 BL Backlight (optional)GPIO07 and GPIO08 used for RS and EN signal are also used by the SPI bus. If you loaded the SPI driver you will need to assign them to a different GPIO, e.g. GPIO04 and GPIO22.
When using a display with two controllers the vspan option has to be configured as well (e.g. vspan=2,2 for a 40x4 display).
<title>Special Raspberry Pi configuration options</title>This connection driver can be configured to use other pins than the one described in the table above. Using the pin_ configuration option, any LCD pin can be assigned to any GPIO pin.
The values for the pin_ configuration option are the number part from the GPIO signal name, not the pin number from the header connector! To find out which signal is routed to which connector pin refer to the RPi Low-level peripherals description.The connection driver contains a check for possible signal names. You will receive an error message if you try to assign a pin to a signal that is not available on connector P1 or P5.
<title>HD44780: Alternate configuration for Raspberry Pi GPIO pins</title> pin_D4=25 pin_D5=24 pin_D6=23 pin_D7=18 pin_EN=8 pin_RS=7 pin_BL=17]]>
<title>Adafruit Pi Plate</title> The Adafruit RGB Positive 16x2 LCD+Keypad for Raspberry Pi (aka Pi Plate, see ()) combines a 16x2 Character LCD, up to 3 backlight pins AND 5 keypad pins using only the two I2C pins on the Rasperry Pi. Note that this connection type drives all RGB pins of the backlight at the same time, resulting in a white backlight. You will need to modify the source code if you want to have some other color. <title>HD44780: Configuration example for Pi Plate connection type</title> Keypad=yes KeyDirect_1=Enter KeyDirect_2=Up KeyDirect_3=Down KeyDirect_4=Left KeyDirect_5=Right ]]> <title>PiFace Control and Display</title> The PiFace Control and Display for Raspberry Pi from OpenLX SP Ltd combines a 16x2 Character LCD and navigation buttons using the SPI bus on the Rasperry Pi. The PiFace Control and Display features a IR receiver, which LCDproc does not make use of. You have to setup and use LIRC for that. See Setting up PiFace Control And Display to use a remote. <title>HD44780: Configuration example for PiFace Control and Display connection type</title> Keypad=yes KeyMatrix_1_1=Left KeyMatrix_1_2=Down KeyMatrix_1_3=Up KeyMatrix_1_4=Right KeyMatrix_1_5=Escape KeyMatrix_1_6=Enter KeyMatrix_1_7=Left KeyMatrix_1_8=Right ]]> <title>Compiling</title> Make sure that the HD44780 files are built when you run ./configure. This can be done by specifying --enable-drivers=all or by includinghd44780 in the list of enabled drivers
(e.g. --enable-drivers=hd44780).
<title>Configuration in LCDd.conf</title>
<title>[hd44780]</title>
Port =
PORT
For parallel connections, specify the address of the parallel port the LCD is connected to.
Common values for PORT are 0x278,
0x378 and 0x3BC.
If not given, the default is 0x378.
For I2C connection types this sets the slave
address.
Device =
DEVICE
If you are using a serial or I2C connection,
you need to set this parameter to the device your LCD is connected to.
For example, if the display is connected to the first serial port,
you have to set it to /dev/ttyS0.
The default value is /dev/lcd.
ConnectionType =
{
4bit |
8bit |
serialLpt |
winamp |
picanlcd |
lcdserializer |
los-panel |
vdr-lcd |
vdr-wakeup |
pertelian |
lis2 |
mplay |
usblcd |
bwctusb |
lcd2usb |
usbtiny |
uss720 |
usb4all |
ftdi |
i2c |
piplate |
spi |
pifacecad |
ethlcd |
raspberrypi
}
Select the type of the wiring / display connection. See also
().
Speed =
BITRATE
For a serial connection, set to the serial port bitrate. To use
the default value for the chosen interface, just set to 0.
CharMap =
{
hd44780_default |
hd44780_euro |
ea_ks0073 |
sed12780f_0b |
hd44780_koi8_r |
hd44780_cp1251 |
hd44780_8859_5 |
upd16314 |
weh001602a_1 |
none
}
Set the character mapping depending on the display you have:
The default, hd44780_default, is for "classic"
HD44780 displays.
hd44780_euro is for displays with a ROM mask
supporting the european charset (ROM code A02).
ea_ks0073 is the charmap for Electronic
Assembly's KS0073 based displays. These devices have a richer
charset, including many icons and many more characters of the
ISO-8859-1 than standard HD44780s.
sed12780f_0b is for some SED 1278 displays.
The none charmap does not translate any characters.
It displays the characters the display controllers actually has
stored in its CGROM for that position instead. This setting is
intended for debugging purpose.
You only need to set this parameter if you have a non-standard
HD44780 display or charmap.
If LCDproc was configured with '--enable-extra-charmaps' option the
following character mappings are available, too:
hd44780_koi8_r maps input from a client in
Russian KOI8-R to displays with a ROM mask supporting the european
charset (ROM code A02).
hd44780_cp1251 maps input from a client in
Russian CP1251 (Windows-1251) to displays with a ROM mask supporting
the european charset (ROM code A02).
hd44780_8859_5 maps input from a client in
Russian ISO 8859-5 to displays with a ROM mask supporting the european
charset (ROM code A02).
upd16314 is for displays with a Nec uPD16314
vacuum fluorescent display (VFD) controller with ROM code 002
character set. If your display has ROM code 001 character set you
may use the hd44780_euro charmap instead.
weh001602a_1 is for displays such as the
WINSTAR WEH001602A OLED display with bank font 1 (Western Europe I)
selected. Clients should use ISO 8859-1.
See server/drivers/hd44780-charset.h
in LCDproc's source directory for the actual
mappings.
FontBank =
For some displays such as the WINSTAR WEH001602A, set the
font bank to be used. Font banks are the followings
0: English/Japanese
1: Western Europe I
2: English/Rusian
3: Western Europe II
Keypad = ¶meters.yesnodef;
Tell whether you have a keypad connected.
You may also need to configure the keypad layout further on in this file.
Brightness =
BRIGHTNESS
Set the initial brightness when the backlight is on
for the lcd2usb connection type.
Legal values are 0 - 1000,
with 800 being the default.
OffBrightness =
BRIGHTNESS
Set the initial off-brightness, i.e. the brightness when the backlight is off,
for the lcd2usb connection type.
The legal range is 0 - 1000.
If not given, it defaults to 300.
Contrast =
CONTRAST
Set the initial contrast for the bwctusb and
lcd2usb connection types.
Legal values for CONTRAST are
0 - 1000.
If not given, it defaults to 500 which may
be too low or too high for the selected connection type.
So, if the screen is blank or dark, please try playing with
the contrast a bit.
Backlight = ¶meters.yesnodef;
Specify if you have a switchable backlight.
OutputPort = ¶meters.yesnodef;
Tell if you have the additional output port ("bargraph") and you want to
be able to control it with the lcdproc OUTPUT command.
Lastline = ¶meters.yesdefno;
Specifies whether the lowest pixel line of a character is pixel addressable
or if it controls an underline effect.
The default is yes, meaning a pixel addressable last pixel line.
Size = ¶meters.size;
Specifies the size of the LCD.
Default: 20x4
In case of multiple combined displays, this should be the total size.
vSpan =
HEIGHT
,…
The "vertical span" when using the driver with multi-controller displays
or with multiple displays that are treated as a single virtual display.
It is a comma separated list of the heights of each display.
In multi-controller displays it lists the number of lines each controller
is responsible for.
E.g. vSpan=2,2,1 means you have three physical displays, the first
two having two lines each, and the third having one line, that together form
a virtual display that is 5 lines high.
The sum of the HEIGHTs must match the total height
given in Size=.
ExtendedMode = ¶meters.yesnodef;
If you have a KS0073 or an other 'almost HD44780-compatible', set this
flag to get into extended,4-line linear addressing mode.
LineAddress =
ADDR
If the next line of your display doesn't start 0x20 higher in
DDRAM you can override the default value of the ExtendedMode with this parameter.
DelayMult =
DELAY
If your display is slow and cannot keep up with the flow of data from
LCDd, garbage can appear on the LCDd. Set this delay multiplier to
2 or 4 to increase the delays.
The default is 1 for a non-multiplied delay.
DelayBus = ¶meters.yesdefno;
You can reduce the inserted delays by setting this to no.
On fast PCs it is possible your LCD does not respond correctly.
Default: yes.
KeepAliveDisplay =
SECONDS
Some displays (e.g. vdr-wakeup) need a message from the driver to
indicate that it is still alive.
When set to a value greater than 0 the character in the
upper left corner is updated every SECONDS seconds.
The default 0 does not cause any extra updates.
RefreshDisplay =
SECONDS
If you experience occasional garbage on your display you can use this
option as workaround. If set to a value greater than 0 it forces a
full screen refresh every SECONDS seconds.
Default: 0.
KeyDirect_NUM =
KEY
KeyMatrix_X_Y =
KEY
If you have a keypad you can assign keystrings to the keys.
See the keypad section
for used terms and the section on the specific connection type how to
wire it.
To map, for example, the directly connected key 4
to the string Enter, use KeyDirect_4=Enter.
For matrix keys use the X and
Y coordinates of the key;
e.g. KeyMatrix_1_3=Enter.
VendorID =
VENDORID
USB vendor ID to look for in certain USB connection types.
When using an FTDI chip with connection type ftdi, the default value is
0x4003.
When using a USS720 chip with connection type uss720, the default value is
0x1293.
ProductID =
PRODUCTID
USB product ID to look for in certain USB connection types.
When using an FTDI chip with connection type ftdi, the default value is
0x6001.
When using a USS720 chip with connection type uss720, the default value is
0x0002.
SerialNumber =
SERIALNO
Serial number of the USB device to look for with
connection type bwctusb.
If not given, the first BWCT USB module found will be used.
<title>Miscellanea</title>
This text has originally been taken from a message by Bill Farrow
bfarrow@arrow.bsee.swin.edu.au.
Updated February 2000, Benjamin Tse blt@ComPorts.com
Updated October 2001, Joris Robijn joris@robijn.net
Converted to Docbook March 2002, Rene Wagner reenoo@gmx.de
Updated April 2002, Rene Wagner reenoo@gmx.de
Updated and extended April 2006 to November 2007, Peter Marschall peter@adpm.de