From 327ab00298e3df8c9b2f7862d2ecaec3d4b9da7e Mon Sep 17 00:00:00 2001 From: marschap Date: Tue, 3 Apr 2007 19:38:18 +0000 Subject: [PATCH] - added missing id attributes to tags to avoid xmlto warnings - a few re-wordings - a litte tagging there and there --- docs/lcdproc-user/configuration.docbook | 2 +- docs/lcdproc-user/drivers/hd44780.docbook | 336 +++++++++++--------- docs/lcdproc-user/drivers/irman.docbook | 2 +- docs/lcdproc-user/drivers/lircin.docbook | 27 +- docs/lcdproc-user/drivers/pylcd.docbook | 2 +- docs/lcdproc-user/drivers/serialPOS.docbook | 54 ++-- docs/lcdproc-user/drivers/serialVFD.docbook | 27 +- docs/lcdproc-user/drivers/t6963.docbook | 2 +- docs/lcdproc-user/how-to-obtain.docbook | 6 +- docs/lcdproc-user/introduction.docbook | 34 +- docs/lcdproc-user/running.docbook | 4 +- 11 files changed, 273 insertions(+), 223 deletions(-) diff --git a/docs/lcdproc-user/configuration.docbook b/docs/lcdproc-user/configuration.docbook index 25148c8..9608db5 100644 --- a/docs/lcdproc-user/configuration.docbook +++ b/docs/lcdproc-user/configuration.docbook @@ -19,7 +19,7 @@ your system's package manager list all the files in the LCDproc -The format of the /etc/LCDd.conf is ini-file-like. +The format of the /etc/LCDd.conf is INI-file like. diff --git a/docs/lcdproc-user/drivers/hd44780.docbook b/docs/lcdproc-user/drivers/hd44780.docbook index f16264b..b59a290 100644 --- a/docs/lcdproc-user/drivers/hd44780.docbook +++ b/docs/lcdproc-user/drivers/hd44780.docbook @@ -6,23 +6,28 @@ There are several ways of wiring up the HD44780 devices. Your choice will probably be governed largely by your ability to wire up each one and/or a desire to use the device with other programs. + The LCDproc HD44780 driver supports the following connections on a parallel port: + -4-bit -8-bit (winamp style) -extended 8-bit (LCD + LED bargraph) -serial LPT + 4-bit + 8-bit (winamp style) + extended 8-bit (LCD + LED bargraph) + serial LPT + It also supports the following connections: + -A PIC-an-LCD or LCD serializer connected to a serial port -A I2C port expander connected to an I2C port + A PIC-an-LCD or LCD serializer connected to a serial port + A I2C port expander connected to an I2C port + The driver also lets you use multiple displays as a single virtual display. For example, a 4, 2 and 1 line display can be used to form a @@ -48,41 +53,41 @@ connections. They are explaned here. All variants use the same method of obtaining power. i.e., for each LCD: - +
HD44780: Power Connections - - -LCD -pin -signal - - - - -1 -GND -(connect to any of pins 18 - 25 of you parallel port) - - -2 -+5V - - - -3 -Vadj -(contrast) - - + + + LCD + pin + signal + + + + + 1 + GND + (connect to any of pins 18 - 25 of you parallel port) + + + 2 + +5V + + + + 3 + Vadj + (contrast) + +
- -Always double check your power connection, your display will probably -NOT survive a reversely connected supply ! - + + Always double check your power connection, your display will probably + not survive a reversely connected supply ! + @@ -90,28 +95,28 @@ There are several ways to get 5V: - -Connect to a 5V line intented for disk drives (the red wire is 5V, -black is GND). - - -Get it from a joystick port (pin 1 and 9 are 5V, 4, 5 and 12 are GND). -It seems that some soundcards can use these lines for communication, -so if you want to use this first check wether it really gives a 'clean' 5V. - - -If you don't have a backlight, you can sometimes get the needed mA's -from the LPT port itself. Connect a few diodes from the data pins to -a capacitor and you have the 5V. If it's strong enough is another question... - - -Get it from the keyboard connector. I do not recommend to use this with -a backlight, as the keyboard connector is often protected with a fuse -of 100mA or 200mA. - + + Connect to a 5V line intented for disk drives (the red wire is 5V, + black is GND). + + + Get it from a joystick port (pin 1 and 9 are 5V, 4, 5 and 12 are GND). + It seems that some soundcards can use these lines for communication, + so if you want to use this first check wether it really gives a 'clean' 5V. + + + If you don't have a backlight, you can sometimes get the needed mA's + from the LPT port itself. Connect a few diodes from the data pins to + a capacitor and you have the 5V. If it's strong enough is another question... + + + Get it from the keyboard connector. I do not recommend to use this with + a backlight, as the keyboard connector is often protected with a fuse + of 100mA or 200mA. + -
+
HD44780: Connecting the contrast adjusting pin (Vadj.) Keypad -You can connect a keypad with all connection types. The maximum supported +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. @@ -147,7 +152,7 @@ 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. -
+
HD44780: Direct Keys - -HD44780: Default Keystrokes - - - -X0 -A - - -X1 -B - - -X2 -C - - -X3 -D - - - +
+ HD44780: Default Keystrokes + + + + X0 + A + + + X1 + B + + + X2 + C + + + X3 + D + + +
@@ -212,7 +217,7 @@ Using a matrix, we can connect much more keys. To simplify the drawing here, we replace all switches with an @ symbol: -
+
HD44780: Single Matrix Key -
+
HD44780: Complete Key Matrix - +
HD44780: Keypad Layout @@ -332,7 +337,7 @@ If you want to use just one return line, for example with the serialLpt wiring, it looks (completely drawn) like this: -
+
HD44780: One 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. - + + 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. + @@ -379,7 +384,7 @@ this. The extension uses one output pin, you cannot use that pin for other functions anymore. The wiring looks like this: -
+
HD44780: Backlight Wiring - -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. Therefor you should then add a resistor after -the transistor of about 10 ohm (see display documentation). - + + 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. Therefor 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's 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.) - + + If you want the backlight to light a bit while it's 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.) + @@ -446,7 +451,7 @@ extra it lights at only 1/9th. I like this. Joris.) This is originally based on "lcdtext" (by Matthias Prinke). -
+
HD44780: 4-bit Pinouts (1) @@ -505,7 +510,7 @@ wire D5 (pin 7) to the enable line (pin 6) of the third LCD. Then for displays four to seven use: -
+
HD44780: 4-bit Pinouts (2) @@ -539,7 +544,7 @@ displays four to seven use: The optional keypad can be connected as follows: -
+
HD44780: 4-bit Keypad Pinouts @@ -626,7 +631,7 @@ The optional backlight wiring should be connected to D5, pin 7. This type of connection should work with winamp. -
+
HD44780: "Winamp" wiring @@ -707,7 +712,7 @@ connected to this line. The optional keypad can be connected as follows: -
+
HD44780: "Winamp" wiring - Keypad @@ -757,7 +762,6 @@ The optional keypad can be connected as follows: INIT (16)Y9 - nACK (10) X0 @@ -815,7 +819,7 @@ winamp or ext8bit wirings, because it only sends 4 bits at a time. The LCD connections are: -
+
HD44780: "lcdtime" wiring @@ -893,7 +897,7 @@ connections. The optional keypad can be connected as follows: -
+
HD44780: "lcdtime" wiring - keypad @@ -943,7 +947,6 @@ The optional keypad can be connected as follows: nSEL (17)Y9 - nACK (10) X0 @@ -1013,7 +1016,7 @@ the shift register, a 4094. Do not forget to connect the 5V to pin 16 and GND to pin 8 of the IC. -
+
HD44780: Serial LPT wiring ('simple') -
+
HD44780: Serial LPT wiring ('complex') -
+
HD44780: Serial LPT - Keypad return lines @@ -1183,7 +1186,7 @@ If you only have 1 return line, you can buffer it with two remaining buffers from the 74HCT14: -
+
HD44780: Serial LPT - Keypad return lines buffered backlight section -
+
HD44780: Serial LPT - Backlight extra circuit + +Special config options + + +Besides the standard configuration options for hd44780 displays, the +lcd2usb connection type supports two additional options: +Contrast= to set the display's contrast and +Brightness= to set the display's brightness. +Both options expect a number in the range from 0 to 1000. + + + + +Status + + +The lcd2usb connection type has been written to support displaysi +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. +If you happen to have a 2-controller display connected to LCD2USB, +please report to the mailing list. + + + In order to make the lcd2usb connection type work with a 2-controller display + you may need to set the vSpan= config option accordingly. + + +Although the LCD2USB sports two keys, they are currently not supported by +LCDproc. Patches to fix the situation are very welcome. + + + @@ -1547,7 +1583,7 @@ If you have an I2C port available that is supported b port expander there (PCF8574P in this example). -
+
HD44780: PCF8574P port expander on I2C bus Configuration -
+
HD44780: Configuration for I<superscript>2</superscript>C with port expander -
+
HD44780: Examples of I<superscript>2</superscript>C port expander adresses Compiling -Make sure that the HD44780 files are built when you run configure. This -can be done by specifying "--enable-drivers=all" or by -"--enable-drivers=hd44780". +Make sure that the HD44780 files are built when you run ./configure. +This can be done by specifying or by including +hd44780 in the list of enabled drivers +(e.g. ). @@ -1790,8 +1827,8 @@ can be done by specifying "--enable-drivers=all" or by The above table might be outdated, when you read this. If you suspect the table above to be outdated, you might want to have a look at - server/drivers/hd44780-drivers.h - which contains the actual translation code. + server/drivers/hd44780-drivers.h in LCDproc's + source directory which contains the actual translation code. @@ -1922,16 +1959,24 @@ can be done by specifying "--enable-drivers=all" or by - vspan= + vSpan= HEIGHT ,… - For multiple combined displays: how many lines does each display have. - E.g. Vrspan=2,2 means you have two displays and + The "vertical span" when using multiple displays or multi-controller displays. + 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 means you have two displays and each has two lines. + + + The sum of the HEIGHTs must match the total height + given in Size=. @@ -1987,7 +2032,7 @@ can be done by specifying "--enable-drivers=all" or by SECONDS - Some displays (e.g. vdr-wakeup) need a message from the driver to that it + 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. @@ -2009,29 +2054,26 @@ can be done by specifying "--enable-drivers=all" or by - KeyMatrix_4_1= + DirectKey_NUM= KEY - KeyMatrix_4_2= + KeyMatrix_X_Y= KEY - - KeyMatrix_4_3= - KEY - - - KeyMatrix_4_4= - KEY - - - If you have a keypad you can assign keystrings to the keys. - See documentation for used terms and how to wire it. - For example to give directly connected key 4 the string "Enter", use: - KeyDirect_4=Enter - For matrix keys use the X and Y coordinates of the key: - KeyMatrix_1_3=Enter - + + + If you have a keypad you can assign keystrings to the keys. + See documentation for used terms and 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. + + diff --git a/docs/lcdproc-user/drivers/irman.docbook b/docs/lcdproc-user/drivers/irman.docbook index edd2aad..1a0d6f2 100644 --- a/docs/lcdproc-user/drivers/irman.docbook +++ b/docs/lcdproc-user/drivers/irman.docbook @@ -11,7 +11,7 @@ and/or clients that can handle input. The keys are mapped according to the following table: -
+
Mapping between LCDproc keys and IrMan commands diff --git a/docs/lcdproc-user/drivers/lircin.docbook b/docs/lcdproc-user/drivers/lircin.docbook index 65d11e3..a1c9f16 100644 --- a/docs/lcdproc-user/drivers/lircin.docbook +++ b/docs/lcdproc-user/drivers/lircin.docbook @@ -7,6 +7,7 @@ that works with LIRC to control the LCDproc server (LCDd) and/or clients that can handle input. + Of course you need a working LIRC setup. Refer to the LIRC project for more @@ -21,6 +22,7 @@ Basically all you need is a running lircd. And of course you have to start lircd as root. + Also, make sure that the permission of /dev/lircd are correct. @@ -45,27 +47,26 @@ Then simply run make. Configure LCDd to Use the lirc Driver -First of all you need to activate the driver by adding a Driver=lirc line +First of all you need to activate the driver by adding a Driver=lirc line to your LCDd.conf - + <filename>LCDd.conf</filename>: Activate the lirc driver + - -Driver=mtxorb -Driver=lirc - + Driver=mtxorb + Driver=lirc -This activates the mtxorb driver as the output driver and the lirc driver -as the input driver. +This activates the mtxorb driver as the output driver +and the lirc driver as the input driver. -Then you have to modify the [lirc] section of your +Then you have to modify the [lirc] section of your LCDd.conf. @@ -134,11 +135,11 @@ No matter which file you use, you have to add at least the following lines to the file: - + <filename>~/.lircrc</filename>: Specify the associations from buttons to keys for the lirc driver - + begin prog = lcdd button = 2 @@ -174,8 +175,6 @@ begin button = 0 config = Enter end - - @@ -192,7 +191,7 @@ and Enter are necessary. - + Of course you can define other keys. Those keys will not be handled by the server but sent to a client. Refer to the documentation of the client you want to use, to find out which keys are neccessary for that client. diff --git a/docs/lcdproc-user/drivers/pylcd.docbook b/docs/lcdproc-user/drivers/pylcd.docbook index 8445061..d62804f 100644 --- a/docs/lcdproc-user/drivers/pylcd.docbook +++ b/docs/lcdproc-user/drivers/pylcd.docbook @@ -78,7 +78,7 @@ 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. - + How to use the LED output from the client telnet localhost 13666 diff --git a/docs/lcdproc-user/drivers/serialPOS.docbook b/docs/lcdproc-user/drivers/serialPOS.docbook index 63bf031..5d5c8cc 100644 --- a/docs/lcdproc-user/drivers/serialPOS.docbook +++ b/docs/lcdproc-user/drivers/serialPOS.docbook @@ -5,21 +5,20 @@ This section talks about using LCDproc with a point of sale ("POS") character-display. - -The serialPOS-driver is currently working with the AEDEX emulation protocol, +The serialPOS driver is currently working with the AEDEX emulation protocol, but can be extended to work with various other protocols. -The driver should operate most character POS displays with a serial (rs232) input. +The driver should operate most character POS displays with a serial (RS-232) input. Because these displays use a standardized protocol, if the protocol is supported by your display, it should work as expected. - Feedback is welcome. +Feedback is welcome. - -
serialPOS: Emulation Protocol Status - +
+serialPOS: Emulation Protocol Status + Protocol @@ -74,7 +73,8 @@ supported by your display, it should work as expected.
-() feature not tested. + +(…): Feature not tested. @@ -82,19 +82,23 @@ supported by your display, it should work as expected. Connecting the display should consist of simply plugging it into your computer's -rs232 port. Because these displays typically support full rs232, no additional -wiring is needed. If you do not have this port (many newer computers do not), you -can use a USB to serial adapter with the appropriate driver. - - -If your display supports a "pass-through" function, but you do not have -another rs232 device connected to the pass-through port, you may experience hangs -if an improperly formatted command sneaks through. -This is because the display is waiting for the pass-through -device to accept the data and a blocking state is created within the device. -You can either connect another rs232 device, or rewire the display to send the pass- -through commands back to your computer. +RS-232 port. Because these displays typically support full RS-232, no additional +wiring is needed. If your computer does not have such a port (many newer computers don't), +you can use a USB to serial adapter with the appropriate driver. + + + + If your display supports a pass-through function, + but you do not have another RS-232 device connected to the pass-through port, + you may experience hangs if an improperly formatted command sneaks through. + This is because the display is waiting for the pass-through device to accept + the data and a blocking state is created within the device. + You can either connect another RS-232 device, or rewire the display to send the + pass-through commands back to your computer. + + + @@ -112,8 +116,8 @@ through commands back to your computer. DEVICE - Device to use in serial mode. Usual values are /dev/ttyS0 or /dev/cu.usbserial - [default: /dev/lcd]. + Device to use in serial mode. Usual values are /dev/ttyS0 or + /dev/cu.usbserial. Default is /dev/lcd. @@ -128,7 +132,7 @@ through commands back to your computer. Specifies the size of the VFD in characters. - [default: 16x2] + If not given, it defaults to 16x2. @@ -149,7 +153,7 @@ through commands back to your computer. Set the communication protocol to use with the POS display. - If not given [default AEDEX]. + If not specified it defaults to AEDEX. Currently, only AEDEX is supported. @@ -169,7 +173,7 @@ through commands back to your computer. Set the the baud rate communication with the POS display. - If not given [default 9600]. + If not given the default of 9600 is used. diff --git a/docs/lcdproc-user/drivers/serialVFD.docbook b/docs/lcdproc-user/drivers/serialVFD.docbook index 6925e68..6f000ac 100644 --- a/docs/lcdproc-user/drivers/serialVFD.docbook +++ b/docs/lcdproc-user/drivers/serialVFD.docbook @@ -14,12 +14,13 @@ It is also known to work on FUTABA VFDs. The driver should operate most of NEC, Futaba and Noritake 7x5 dot VFDs with - serial(rs232) and/or parallel interface. See the following table for testing-status. - Feedback is welcome. +serial(RS-232) and/or parallel interface. See the following table for testing-status. +Feedback is welcome. -serialVFD: Display Status - +
+serialVFD: Display Status + Display @@ -112,19 +113,21 @@ The driver should operate most of NEC, Futaba and Noritake 7x5 dot VFDs with
-() feature not tested. + +(…): Feature not tested. If your display isn't working 100% satisfactorily you can add a new device with modified hardware -commands to the driver if you want. To do that you have to add a new section to the display- +commands to the driver if you want. To do that you have to add a new section to the display Type=-switch-case in ./server/drivers/serialVFD-displays.c -and to write a new "load"function with the correct commands for the display.(Try which display-Type= -works best with your display, copy, rename and modify this function that is the easiest way I guess.) +and to write a new "load" function with the correct commands for the display. +(Try which display Type= works best with your display, +then copy, rename and modify this function to your needs - that is the easiest way I guess.) -On this page you may find pictures and datasheets of the VFDs: +On Malte Poeggel's page you may find pictures and datasheets of the VFDs: @@ -143,7 +146,7 @@ the display show everything correctly. Always cross-check with your datasheet, before connecting your display! -Displays of same manufacturer may have different pin assignments! +Different displays of even the same manufacturer may have different pin assignments! @@ -161,7 +164,7 @@ serialport. The signal has to be inverted. I use the following circuit to do that job. -
+
serialVFD: Serial Inverter Hold the display in that position where you can read - the "KD Rev 2.1" marking normally! + the KD Rev 2.1 marking normally! diff --git a/docs/lcdproc-user/drivers/t6963.docbook b/docs/lcdproc-user/drivers/t6963.docbook index 0804a59..ccfc050 100644 --- a/docs/lcdproc-user/drivers/t6963.docbook +++ b/docs/lcdproc-user/drivers/t6963.docbook @@ -10,7 +10,7 @@ displays that can often act as a screen. Connections - +
T6963 wiring schematic diff --git a/docs/lcdproc-user/how-to-obtain.docbook b/docs/lcdproc-user/how-to-obtain.docbook index 24adfc5..176e606 100644 --- a/docs/lcdproc-user/how-to-obtain.docbook +++ b/docs/lcdproc-user/how-to-obtain.docbook @@ -37,11 +37,11 @@ Internet. -Download Last Day's CVS Version of LCDproc as a Tarball +Download Yesterday's CVS Version of LCDproc as a Tarball There are nightly distributions of the CVS branches of LCDproc. You can download them from -http://lcdproc.sourceforge.net/nightly/ + @@ -114,7 +114,7 @@ which is in the unstable and testing distributions. -Provided apt-get is configured properly. You should be able to install the package running: +Provided apt-get is configured properly, you should be able to install the package running: diff --git a/docs/lcdproc-user/introduction.docbook b/docs/lcdproc-user/introduction.docbook index 7f51d09..c8b2f61 100644 --- a/docs/lcdproc-user/introduction.docbook +++ b/docs/lcdproc-user/introduction.docbook @@ -11,21 +11,22 @@ After reading this document you will be able to set up your own LCDproc'ed syste -Please note that this document is still "under construction". We hope to finish it -until the final release of LCDproc, which will probably take place in May or June 2002. +Please note that this document is still under construction". We hope to finish it +until the final release of LCDproc ⌣. If you run into any trouble feel free to write to the LCDproc mailing list. -See http://lcdproc.omnipotent.net/mail.php3 +See for details on how to subscribe to the list. -Therefore you might want to have a look at http://lcdproc.sourceforge.net/docs/, -to get the latest version of this document (, unless you want to generate it yourself from the +Therefore you might want to have a look at , +to get the latest version of this document (unless you want to generate it yourself from the docbook files in the CVS). -This document was written for LCDproc 0.4.3. At the time of writing there had already -been the "LCDproc User's Guide" written by William W. Ferrel in 1999. His version covered +This document was originally written for LCDproc 0.4.3, but has been dramatically updated since. +At the time of writing there had already been the "LCDproc User's Guide" written by +William W. Ferrel in 1999. His version covered an early version of LCDproc and therefore concentrated on Matrix Orbital displays. @@ -45,12 +46,12 @@ document. The authors of those are listed below every such document. What is LCDproc? -LCDproc is a client/server suite including drivers for all kinds of +LCDproc is a client/server suite including drivers for all kinds of nifty LCD displays. -The server 'LCDd' makes it possible to display text and other data on -an LCD display. As well LCDd can handle certain input devices. +The server LCDd makes it possible to display text and +other data on an LCD display. As well LCDd can handle certain input devices. Support for devices is added by drivers. We distinguish between output @@ -66,10 +67,10 @@ HD44780, STV5730, T6963, SED1520 and SED1330. There are input (only) drivers for LIRC and joysticks. -Clients can connect to LCDd through common sockets. +Clients can connect to LCDd through common TCP sockets. -Various clients are available. The "main" client +Various clients are available. The main client lcdproc, which is shipped with the LCDproc distribution, can display things like CPU load, system load, memory usage, uptime, and a lot more. @@ -134,10 +135,11 @@ As it is rather simple to write an LCDproc client, you can find various clients on the Internet. -Unfortunately we cannot provide a list of LCDproc clients (yet). So, have -fun searching google or -freshmeat. Simply type 'lcdproc' -for the keyword. +Unfortunately we cannot provide a list of LCDproc clients here. So, take a look at the +Clients page on LCDproc's web site +or have fun searching Google or +freshmeat. Simply use lcdproc +as the search pattern. diff --git a/docs/lcdproc-user/running.docbook b/docs/lcdproc-user/running.docbook index 8e43255..f28ac59 100644 --- a/docs/lcdproc-user/running.docbook +++ b/docs/lcdproc-user/running.docbook @@ -51,7 +51,7 @@ Running LCDd -h gives you an overview of the currently availa command line options. - + <command>LCDd -h</command> lcdproc -h gives you an overview of the currently ava command line options. - + <command>lcdproc -h</command>