diff --git a/docs/lcdproc-user/drivers/CwLnx.docbook b/docs/lcdproc-user/drivers/CwLnx.docbook
index 9edcd7b..b13de13 100644
--- a/docs/lcdproc-user/drivers/CwLnx.docbook
+++ b/docs/lcdproc-user/drivers/CwLnx.docbook
@@ -226,7 +226,7 @@ For more information see the
- keypad_test_mode permit to test keypad assignement
+ keypad_test_mode permit to test keypad assignment
Default value is no
diff --git a/docs/lcdproc-user/drivers/ea65.docbook b/docs/lcdproc-user/drivers/ea65.docbook
index c2236b5..377281b 100644
--- a/docs/lcdproc-user/drivers/ea65.docbook
+++ b/docs/lcdproc-user/drivers/ea65.docbook
@@ -14,8 +14,8 @@
of 9 characters.
- The display is internally connected to the serial port (/dev/ttyS1)
- with a rate of 9600 baud
+ 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
@@ -25,7 +25,7 @@
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.
+ output command of LCDd.
diff --git a/docs/lcdproc-user/drivers/eyeboxone.docbook b/docs/lcdproc-user/drivers/eyeboxone.docbook
index 1c0b25c..8f755d9 100644
--- a/docs/lcdproc-user/drivers/eyeboxone.docbook
+++ b/docs/lcdproc-user/drivers/eyeboxone.docbook
@@ -9,17 +9,17 @@
Eyebox One LCD Module
Eyebox One is a small rackmounted server marketed by Rightvision
- (http://www.alcateleyebox.rightvision.com/).
+ ().
This server has an LCD module, a keypad, two graphbars and some leds.
- The LCD is a 20x4 alphanumeric modules connected via standard DB-9 cabling and
- connectors.
+ The LCD is a 20x4 alphanumeric module connected via standard DB-9 cabling and
+ connector.
I couldn't find any documentation about it.
All I know has been obtained with some reverse engineering.
- It seems that it can run only at 19,200 baud.
+ It seems that it can run only at 19.200 baud.
Sending ASCII to the module will make it simply display that text at
its current cursor position.
The module has a built-in BIOS that recognizes commands (sent by transmitting a
diff --git a/docs/lcdproc-user/drivers/hd44780.docbook b/docs/lcdproc-user/drivers/hd44780.docbook
index b59a290..78a1ff3 100644
--- a/docs/lcdproc-user/drivers/hd44780.docbook
+++ b/docs/lcdproc-user/drivers/hd44780.docbook
@@ -13,9 +13,9 @@ parallel port:
- 4-bit
- 8-bit (winamp style)
- extended 8-bit (LCD + LED bargraph)
+ 4bit
+ 8bit (winamp style)
+ extended 8bit (LCD + LED bargraph)serial LPT
@@ -55,7 +55,7 @@ All variants use the same method of obtaining power. i.e., for each LCD:
HD44780: Power Connections
-
+LCD
@@ -184,24 +184,28 @@ By default, the following keystrokes are generated by the different keys:
- HD44780: Default Keystrokes
-
+ HD44780: Direct Key Mapping
+ X0
- A
+ AX1
- B
+ BX2
- C
+ CX3
- D
+ D
+
+
+ X4
+ E
@@ -278,8 +282,8 @@ assumes this:
-HD44780: Keypad Layout
-
+HD44780: Matrix Keypad Layout
+
@@ -287,34 +291,39 @@ assumes this:
X1X2X3
+ X4Y0
- 1
- 2
- 3
- A
+ 1
+ 2
+ 3
+ A
+ EY1
- 4
- 5
- 6
- B
+ 4
+ 5
+ 6
+ B
+ FY2
- 7
- 8
- 9
- C
+ 7
+ 8
+ 9
+ C
+ GY3
- *
- 0
- #
- D
+ *
+ 0
+ #
+ D
+ H
@@ -379,8 +388,9 @@ Y3 o---|<---o o---+----o return line
A small extension allows you to switch the backlight of the display on
-and off. At the moment only the 4bit and winamp connection types support
-this. The extension uses one output pin, you cannot use that pin for other
+and off. At the moment only the 4bit 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:
@@ -444,54 +454,80 @@ The BC327 transistor has the following connections:
-
-4-bit
+
+4bit
This is originally based on "lcdtext" (by Matthias Prinke).
-
+HD44780: 4bit Pinouts (2)
+printer port
@@ -544,9 +580,9 @@ displays four to seven use:
The optional keypad can be connected as follows:
-
-HD44780: 4-bit Keypad Pinouts
-
+
+HD44780: 4bit Keypad Pinouts
+printer port
@@ -624,70 +660,104 @@ The optional backlight wiring should be connected to D5, pin 7.
-
-8-bit "Winamp"
+
+8bit "Winamp"
This type of connection should work with winamp.
-
HD44780: "Winamp" wiring - Keypad
-
+printer port
@@ -792,8 +862,8 @@ The optional backlight wiring should be connected to nSEL, pin 17.
-
-8-bit "lcdtime"
+
+8bit "lcdtime"
This is originally based on "lcdtime" (by Benjamin Tse
@@ -819,63 +889,97 @@ winamp or ext8bit wirings, because it only sends 4 bits at a time.
The LCD connections are:
-
HD44780: "lcdtime" wiring - keypad
-
+printer port
@@ -1154,7 +1258,7 @@ serialLpt wiring supports a keypad. The 3 wires version supports
HD44780: Serial LPT - Keypad return lines
-
+nACK (10)
@@ -1242,7 +1346,7 @@ that. The BL output below should be connected to the BL input in the
LIS2 from VLSystem () is a full featured USB VFD module
with four channel fan controls. This device can be accessed as a serial device with the
-help of the kernel modules ftdi_sio that map the USB port to a serial port
+help of the kernel modules ftdi_sio.ko that map the USB port to a serial port
(/dev/ttyUSBx).
@@ -1290,15 +1394,19 @@ See Pertelian X2040 "pertelian"
-The Pertelian X2040 includes an hd44780 display with enclosure and usb
-connection. In order to work with lcdproc you need usbserial and
-ftdi_sio modules loaded. Display will be available on /dev/ttyUSB0.
+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
- product
- page for more information.
+
+ X4020 product page for more information.
@@ -1311,7 +1419,8 @@ ftdi_sio modules loaded. Display will be available on /dev/ttyUSB0.
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.
+config file with the Device= setting.
+The default is /dev/lcd.
It does not support a keypad nor backlight switching.
@@ -1328,10 +1437,11 @@ by Dale Wheat.
LCD serializer device "lcdserializer"
-LCD serializer connection is technically the same of PIC-an-LCD with the same advantages,
+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 like PIC-an-LCD, it's just a project found digging on the net and freely available.
+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.
@@ -1352,22 +1462,22 @@ You have all the tools and the code to build it yourself and to customize the be
Burning the PIC
-First, you need to download the asm source for your pic and then make the hex:
-
-
-
-gpasm lcd16f84_custom.asm
-
+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
-
-
+
+
+$picprog --erase --burn --input lcd16f84.hex --pic /dev/ttyS0
+
+
@@ -1379,19 +1489,18 @@ 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.
+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 statments in the hd44780 section:
+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.
@@ -1437,7 +1546,7 @@ value to ARG1, then the value is sent to the LCD. The fourth line delays the exe
-You don't have to write the ascii values in your modification, gpasm does the translation for you, so
+You don't have to write the ASCII values in your modification, gpasm does the translation for you, so
if you want to see Booting... at startup, change the code above to look like this:
@@ -1554,7 +1663,7 @@ Both options expect a number in the range from 0 to Status
-The lcd2usb connection type has been written to support displaysi
+The lcd2usb connection type has been written to support displays
with one and two HD44780 controllers.
Owing to the lack of a 2-controller display, it has only been tested with a
1-controller display.
@@ -1584,7 +1693,7 @@ port expander there (PCF8574P in this example).
-HD44780: PCF8574P port expander on I2C bus
+HD44780: PCF8574P port expander on I2C busConfiguration
-
+HD44780: Configuration for I2C with port expander
-
+
-Device is the device file for your I2C bus (here /dev/i2c-0).
-You have to load the kernel standard module i2c-dev and
-the bus driver, but NO i2c chip modules (e.g. pcf8574)!
+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)!
-Port 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) given in port is special:
+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.
-
-HD44780: Examples of I2C port expander adresses
-
-
-
-
+
+HD44780: Examples of I2C port expander addresses
+
+
+
+ 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
+
+
+
+
+
@@ -1722,9 +1855,10 @@ This can be done by specifying or by inclu
If you are using a serial connection, you must
- set this parameter to the device your lcd is connected to. For
- example, if it's connected to the first serial port, you have to
- set Device to /dev/ttyS0. The default value is /dev/lcd.
+ 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.
@@ -1735,8 +1869,8 @@ This can be done by specifying or by inclu
4bit8bit
- serialLptwinamp
+ serialLptpicanlcdlcdserializerlos-panel
@@ -1755,7 +1889,7 @@ This can be done by specifying or by inclu
Select the type of the wiring / display connection.
-
+ ConnectionType
@@ -1764,59 +1898,59 @@ This can be done by specifying or by inclu
- 4bit
+ 4bitHD44780 4bit Wiring (default)
- 8bit
+ 8bitHD44780 8bit Wiring ("lcdtime")
- serialLpt
- HD44780 Serial LPT Wiring
-
-
- winamp
+ winampHD44780 8bit Wiring "winamp" Style
- picanlcd
+ serialLpt
+ HD44780 Serial LPT Wiring
+
+
+ picanlcdPIC-an-LCD serial device "picanlcd"
- lcdserializer
+ lcdserializerLCD serializer "lcdserializer"
- los-panel
+ los-panelLCD on Serial panel device "los-panel" ()
- vdr-lcd
+ vdr-lcdVDR LCD serial device "vdr-lcd"
- vdr-wakeup
+ vdr-wakeupVDR-Wakeup module "vdr-wakeup"
- pertelian
+ pertelianPertelian X2040 LCD display ()
- bwctusb
+ bwctusbBWCT USB device "bwctusb" ()
- lcd2usb
+ lcd2usbTim Harbaum's LCD2USB ()
- lis2
+ lis2LIS2 from VLSystem ()
- i2c
+ i2cLCD driven by PCF8574(A)/PCA9554(A) connected via I2C
@@ -1857,12 +1991,12 @@ This can be done by specifying or by inclu
- You need to set this parameter only if you don't have a standard
- hd44780 display. ea_ks0073 is the charmap for Electronic
+ You need to set this parameter only if you do not have a standard
+ HD44780 display. 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. Refer to hd44780-charset.h
- for more informations.
+ ISO-8859-1 than standard HD44780s. Refer to hd44780-charset.h
+ for more information.
@@ -1921,7 +2055,7 @@ This can be done by specifying or by inclu
Tell if you have the additional output port ("bargraph") and you want to
- be able to control it with the lcdproc OUTPUT command
+ be able to control it with the lcdproc OUTPUT command.
@@ -1936,8 +2070,9 @@ This can be done by specifying or by inclu
- Specifies if the last line is pixel addressable or it controls an
- underline effect. [default: yes (= pixel addressable); legal: yes, no]
+ 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.
@@ -2004,8 +2139,9 @@ This can be done by specifying or by inclu
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 factor to 2 or 4
- to increase the delays. Default: 1.
+ 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.
@@ -2035,7 +2171,7 @@ This can be done by specifying or by inclu
Some displays (e.g. vdr-wakeup) need a message from the driver to that it
is still alive. When set to a value bigger then 0 the character in the
upper left corner is updated every SECONDS seconds.
- Default: 0.
+ The default 0 does not cause any extra updates.
diff --git a/docs/lcdproc-user/drivers/imon.docbook b/docs/lcdproc-user/drivers/imon.docbook
index 0ae6e25..f10e97a 100644
--- a/docs/lcdproc-user/drivers/imon.docbook
+++ b/docs/lcdproc-user/drivers/imon.docbook
@@ -65,7 +65,7 @@ For further details, please consult the page and the forum at
Set the display size. The default 16x2 should be safe
- for most iif not all users, since the device seeems to be made only with
+ for most if not all users, since the device seeems to be made only with
this one size.
But who knowns …
diff --git a/docs/lcdproc-user/drivers/irman.docbook b/docs/lcdproc-user/drivers/irman.docbook
index 1a0d6f2..08b3295 100644
--- a/docs/lcdproc-user/drivers/irman.docbook
+++ b/docs/lcdproc-user/drivers/irman.docbook
@@ -51,8 +51,8 @@ The keys are mapped according to the following table:
-If you have trouble using the IrMan driver, you might try the lirc driver.
-lirc supports Irman as well.
+If you have trouble using the irman driver, you might try the lirc driver.
+lirc supports IrMan as well.
diff --git a/docs/lcdproc-user/drivers/picolcd.docbook b/docs/lcdproc-user/drivers/picolcd.docbook
index eddec8b..f3d4cd9 100644
--- a/docs/lcdproc-user/drivers/picolcd.docbook
+++ b/docs/lcdproc-user/drivers/picolcd.docbook
@@ -22,7 +22,7 @@
Using the USB LCD with this driver requires the usblcd library from Mini-box.com
- (avaiable at ).i
+ (available at ).i
The usblcd library
requires libusb and libhcd. Your distribution may or may not already provide
these libraries. The only kernel driver required is the USB host controller
@@ -42,7 +42,7 @@
splash command.
- To use the picolcd with lcdproc, add picolcd to the lcdproc configure drivers option
+ To use the picolcd with LCDproc, add picolcd to the LCDproc configure drivers option
(or use all) and then start LCDd with the "-d picolcd" option. The driver has
sane default options and the options that are user configurable are limited to mostly
simple items, like contrast and which keys to lights up.
@@ -62,7 +62,9 @@
CONTRAST
- Contrast: 0-1000. 0 is visible, and 1000 is not on my M300. Default is 0.
+ Contrast: 0-1000.
+ 0 is visible, and 1000 is not on my M300.
+ Default is 0.
@@ -90,7 +92,7 @@
- If Keylights is set, you can disable the directional pad LED by
+ If Keylights is set, you can disable the directional pad LED by
setting this value to no. Default is yes.
@@ -105,7 +107,7 @@
- If Keylights is set, you can disable the F1 LED by setting this value
+ If Keylights is set, you can disable the F1 LED by setting this value
to no. Default is yes.
@@ -120,7 +122,7 @@
- If Keylights is set, you can disable the F2 LED by setting this value
+ If Keylights is set, you can disable the F2 LED by setting this value
to no. Default is yes.
@@ -135,7 +137,7 @@
- If Keylights is set, you can disable the F3 LED by setting this value
+ If Keylights is set, you can disable the F3 LED by setting this value
to no. Default is yes.
@@ -150,7 +152,7 @@
- If Keylights is set, you can disable the F4 LED by setting this value
+ If Keylights is set, you can disable the F4 LED by setting this value
to no. Default is yes.
@@ -165,7 +167,7 @@
- If Keylights is set, you can disable the F5 LED by setting this value
+ If Keylights is set, you can disable the F5 LED by setting this value
to no. Default is yes.
diff --git a/docs/lcdproc-user/drivers/pylcd.docbook b/docs/lcdproc-user/drivers/pylcd.docbook
index d62804f..9bc03db 100644
--- a/docs/lcdproc-user/drivers/pylcd.docbook
+++ b/docs/lcdproc-user/drivers/pylcd.docbook
@@ -56,26 +56,63 @@ LEDs, similar to what the IOWarrior driver does.
-The Pyramid LC-Display exists in two different versions, with 3 and with
-9 LEDs. 2 of these LEDs can not be controlled by software but are
+The Pyramid LC displays come in two different versions, with 3 and with
+9 LEDs. Two of these LEDs can not be controlled by software but are
usually hard wired to power and HDD. The other 1 or 7 LEDs can now be
-controlled by sending an "output" command to the server. The one
-argument to the output command is a bitmask that controls the LEDs.
+controlled by sending an output command to the server.
-
-bit 0: LED3
-bit 1: LED4
-bit 2: LED5
-bit 3: LED6
-bit 4: LED7
-bit 5: LED8
-bit 6: LED9
-
+
+The argument to the output command is a bitmask that controls the LEDs
+according to the table below:
+
+
+
-There's no way of finding out whether 3 or 9 LEDs are available, so it
-is up to the software to do the right thing.
+For the LCDd server there is no way to find out
+whether 3 or 9 LEDs are available, so it is up to the client software
+to do the right thing.
diff --git a/docs/lcdproc-user/drivers/sed1330.docbook b/docs/lcdproc-user/drivers/sed1330.docbook
index 48a89db..81e4844 100644
--- a/docs/lcdproc-user/drivers/sed1330.docbook
+++ b/docs/lcdproc-user/drivers/sed1330.docbook
@@ -4,7 +4,7 @@
This section talks about using LCDproc with graphical LCD displays driven by
the EPSON/SMOS SED1330 or SED1335 LCD controllers, which may also be known by their
-new names: S1D13300 (= SED1330) and S1D13305 (SED1335).
+new names: S1D13300 (= SED1330) and S1D13305 (= SED1335).
The displays are driven in text mode using their built-in character generator.
@@ -18,74 +18,423 @@ Always consult documentation about the specific display before asuming
the connections given here are also correct for your display !
+
-ConnectionType classic ordered by LPT port pins
-
- pin LPT port
- ^RESET 1 1 ^STROBE
- D0 8 2 D0
- D1 9 3 D1
- D2 10 4 D2
- D3 11 5 D3
- D4 12 6 D4
- D5 13 7 D5
- D6 14 8 D6
- D7 15 9 D7
- 10 ^ACK
- GND 11 BUSY
- 12 PAPEREND
- 13 ^SELECT
- 14 ^LF
- 15 ^ERROR
- ^WR 3 16 ^INIT
- A0 7 17 ^SELECT_IN
- Vss 17 GND 18..25 GND
- ^RD 2 +5V
- SEL1 4 GND
- SEL2 5 GND
- ^CS 6 GND
- Vdd 16 +5V
- V0 18 potmeter
- Vlc 19 -24V (not required for G242C)
- Frame 20 GND
-]]>
-
-
-The potmeter should be connected like this on these display modules:
+The potentiometer should be connected like this on these display modules:
- Type of LCD module. Besised other things (internal setup) this configuration setting
- detrmines the size of the display in pixels.
+ Type of LCD module. Besides other things (internal setup) this configuration setting
+ determines the size of the display in pixels.
@@ -292,7 +641,7 @@ use the following circuit.
-Contrary to other drivers the character size of an LCD using the sed1330i
+Contrary to other drivers the character size of an LCD using the sed1330
driver is not given directly.
Instead it is determined by the pixel size of the display, which is derived from
the display type setting and the character cell size.
diff --git a/docs/lcdproc-user/drivers/tyan.docbook b/docs/lcdproc-user/drivers/tyan.docbook
index b91c08b..9aaedd4 100644
--- a/docs/lcdproc-user/drivers/tyan.docbook
+++ b/docs/lcdproc-user/drivers/tyan.docbook
@@ -12,7 +12,7 @@ barebones.
The LCD modules used on the front side of the Tyan GS10 and GS12 series
barebones consist of an LCD display by Winstar Display Co. LTD
-that is 16 characters wide and 2 lines. high.
+that is 16 characters wide and 2 lines high.
To the right of the display there is a 6 button keypad:
4 array buttons and two buttons labeled C and S.