lcd4linux-users — lcd4linux users

[lcd4linux] New LCD4Linux Homepage with Wiki!

[Michael R. <re...@eu...>]

Hi there!

Exciting things happen!

With many thanks to Sam and Xavier, we ported the whole LCD4Linux 
homepage on SourceForge to a new location, using Trac and a Wiki.

Visit http://lcd4linux.bulix.org and enjoy!

Please consider the SourceForge Homepage outdated! All information about 
the new upcoming release 0.10 can be found in the Wiki!

Note that the Wiki is open to the public, so all of you (especially the 
development crew) are invited to contribute! (you know, YOU write the 
documentation, for I write the code :-)

Unfortuenately, not all documentation has been adopted to the new 
LCD4Linux-0.10, but we make good progress. The main changes are 
documented, and one driver (HD44780, the most common one).

I think we reached a state where I can release LCD4Linux-0.10.0-RC1, 
which will be done in a few hours.


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://members.eunet.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] PPP plugin - high load

[Michael R. <re...@eu...>]

Hi Zsolt,

>>But the PPP plugin should be considered obsolete. Use the netdev-plugin
>>instead, and specify 'ppp' as a device.

> Thank you, I change my config file. The netdev_plugin worked fast.
Fine!

> I have one more question. As I mentioned I cleaned up some unneded parts
> from config file (etc: MySQL, pop3, etc).
> During start the lcd4linux process i get some error messages on stderr:
> 
> i2c_sensors: unable to autodetect i2c sensors!
> [MySQL] no 'Plugin:MySQL:database' entry from
> /etc/lcd4linux/lcd4linux.conf, specify one
> 
> Should I write back these widgets to config file to eliminate this error
> or is there any other way to do it?

Just ignore these errors for the moment. They will go away as soon as we 
have plugin-autoloading (which menas a plugin is not staically compiled 
into lcd4linux, but will be loaded dynamically at first usage)

bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://members.eunet.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] HD44780 lcd n/w

[Michael R. <re...@eu...>]

Hi SImon,

> any idea why i dont see anything in stderrr window when i run Xterm?..

How do you start it? If you just run 'lcd4linux', all output goes to 
syslog anyway. If you use the '-F' option, there should be stdout and 
stderr output!


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://members.eunet.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] PPP plugin - high load

[Michael R. <re...@eu...>]

Hi Zsolt,

> I tried to switch to a new lcd4linux. I checked out source from cvs at
> 30/12/2004. I cleaned the sample config file to include used lines only.
> I display only a few things like system date/time, uptime, network
> traffic. I would like to display ppp traffic but when I insert the ppp
> widget to the default layout, system load grows up quickly.
> I didn't change anything in the sample config around ppp widget.
> What should I do to eliminate this high load?

You are right, the PPP plugin is far from optimal regarding CPU usage. I 
don't remember exactly, but I think the system call is quite cpu-intensive.

But the PPP plugin should be considered obsolete. Use the netdev-plugin 
instead, and specify 'ppp' as a device.

Example: netdev('ppp0', 'Rx_bytes', 500)

This plugin parses /proc/net/dev, and is quite fast!

HTH, Michael

-- 
Michael Reinelt <re...@eu...>
http://members.eunet.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

[lcd4linux] PPP plugin - high load

[Zsiros Z. <zs...@ma...>]

Hi,

I tried to switch to a new lcd4linux. I checked out source from cvs at
30/12/2004. I cleaned the sample config file to include used lines only.
I display only a few things like system date/time, uptime, network
traffic. I would like to display ppp traffic but when I insert the ppp
widget to the default layout, system load grows up quickly.
I didn't change anything in the sample config around ppp widget.
What should I do to eliminate this high load?

Zsolt

Re: [lcd4linux] Problems with T6963C

[Michael R. <re...@eu...>]

Hi Juergen,

>>But my question was: Is the lower half handled correctly by lcd4linux? I 
>>doubt so...
> 
> Yes, the lower half is handled correctly -> when i put some text
> there, the snow is gone on the pixels where the characters are. 
Strange. Very strange. Rows > 63 should not work with the old code.

>>I just changed the code in CVS. Could you please check out and try? 
>>(Maybe you have to wait a few hours until the anonymous CVS is in sync 
>>again)
> 
> I've checked out the source but nothing changes. Do you need some
> debug output or anything else? 

There's been a change to drv_T6963.c. Please double-check if you have 
revision 1.13 of this file...


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://members.eunet.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] Problems with T6963C

[Juergen D. <li...@ka...>]

Hi Michael,

* On Wed, 22 Dec 2004 at 14:39 +0100, Michael Reinelt wrote:
> >>Will the text in the lower half be displayed correctly?
> >
> >Yes, it will, graphics also too. I have also tested the display with
> >the graphlcd-plugin from the Linux-VDR project and it works
> >correctly. So i think, the wireing and so is ok :)
> Yes, I think so, too.
> But my question was: Is the lower half handled correctly by lcd4linux? I=
=20
> doubt so...

Oh, ok .. now i unterstand what you mean :)=20
Yes, the lower half is handled correctly -> when i put some text
there, the snow is gone on the pixels where the characters are.=20

[...]
> I just changed the code in CVS. Could you please check out and try?=20
> (Maybe you have to wait a few hours until the anonymous CVS is in sync=20
> again)

I've checked out the source but nothing changes. Do you need some
debug output or anything else?=20

Thanks, Happy Christmas=20
--=20
/j<r>d

You have an unusual magnetic personality.  Don't walk too close to
metal objects which are not fastened down.

Re: [lcd4linux] HD44780 lcd n/w

[Simon C. <sim...@ho...>]

hi Michael thanks for your reply ..i tried the edited .conf as you said to 
no avail...when i power up the board no apparent change in lcd ...i will try 
rebuilding again i tried lcdsmartie still no go ...will keep you 
posted..thanks
any idea why i dont see anything in stderrr window when i run Xterm?..

>From: Michael Reinelt <re...@eu...>
>To: Simon Clare <sim...@ho...>
>CC: lcd...@li...
>Subject: Re: [lcd4linux] HD44780 lcd n/w
>Date: Wed, 22 Dec 2004 14:21:50 +0100
>
>Hi Simon,
>
>>small problem i have a REDHAT 9  2.4.20-8
>>i got the source got it going but my lcd will not work got xterm to work 
>>(no entries in stderr?)
>>and got the X11 too work great...
>
>>#lcd4linux -Fvv
>[...]
>>wiring: [DISPLAY:RS]<==>[PARPORT:AUTOFD]
>>wiring: [display :rw ]<==>[parport:gnd]
>>wiring: [display:enable]<==>[parport:strobe]
>>wiring: [display:enable2]<==>[parport:select]
>>wiring: [display:gpo]<==>[parport:init]
>looks good...
>
>>heres lcd4linux.conf
>[...]
>>Wire.RW "GND"               #RW (pin 5 lcd hardwired to ground)
>>Wire.RS "AUTOFD"           #RS  (pin 4 lcd to pin 14 DB-25 "Autofd")
>>Wire.ENABLE "STROBE"     #E (pin 6 lcd to pin 1 DB-25 "strobe")
>>Wire.GPO "INIT
>looks good, too, but just to be sure, you should add/modify these two 
>lines:
>Wire.ENABLE2 "GND"
>Wire.GPO "GND"
>
>>the data lines (DB0........DB7 on the display,DB1 ....DB8 on the parrallel 
>>port)are connected directly
>>RS pin 4 lcd to pin 14 "autofd"
>>RW hardwired to gnd
>>E pin 6 lcd to pin 1 DB-25
>looks correct, too.
>
>so your wiring seems to be ok. You did double-check, did you?
>
>Does the display work with some other software? (lcdproc, or windows..)
>
>What happens on the display a) if you connect power to it, and b) when you 
>start lcd4linux?
>
>Hmmm.... maybe you're facing the problem that the display requires 5V on 
>the data lines, but your parport provides only 3.3V?
>
>bye, Michael
>
>--
>Michael Reinelt <re...@eu...>
>http://members.eunet.at/reinelt
>GPG-Key 0xDF13BA50
>ICQ #288386781
>
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now. 
>http://productguide.itmanagersjournal.com/
>_______________________________________________
>Lcd4linux-users mailing list
>Lcd...@li...
>https://lists.sourceforge.net/lists/listinfo/lcd4linux-users

Re: [lcd4linux] Problems with T6963C

[Michael R. <re...@eu...>]

Hi Juergen,

>>Will the text in the lower half be displayed correctly?
> 
> Yes, it will, graphics also too. I have also tested the display with
> the graphlcd-plugin from the Linux-VDR project and it works
> correctly. So i think, the wireing and so is ok :)
Yes, I think so, too.
But my question was: Is the lower half handled correctly by lcd4linux? I 
doubt so...

>>Looking into the code of drv_T6963.c, looks like the internal memory 
>>layout is deivided into upper and lower half, having two different 
>>memory starting addresses. But this has never been coded out, because I 
>>don't have such a nice display :-(
>>
>>If you want to be my tester, I'll try to integrate this code...
> 
> Fine, of course. I can give you an shell account on a workstation of
> me, where i can connect the lcd if you need. Else say what you need
> :-)
No, I need someone who as "optical" access to the display :-)

I just changed the code in CVS. Could you please check out and try? 
(Maybe you have to wait a few hours until the anonymous CVS is in sync 
again)


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://members.eunet.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

[lcd4linux] Re: =?ISO-8859-1?Q?R=E9f=2E_=3A_LIS_=28Lost_In_Space=29?= =?ISO-8859-1?Q?_Display?=

[Michael R. <re...@eu...>]

Hi Patrick,

>  found this datasheet from 'community' and google search according to 
> "UPD16314GJ" criteria

Looks good, but will not be of much help. This is the LCD controller, 
but I'm shure there's another microcontroller (the PICxyz you mentioned) 
which controls the serial port. What I need for adopting a driver is the 
serial protocol. These protocols differ *a lot* from the LCD 
controller's protocol, because this uC tries to do a lot of work and 
provide sort of a "high level" interface.

I'm afraif if you don't find any documentation we will fail here...

Is there any software out there which uses this display? You could use 
this software, but don't connect a display to the serial port, but a 
sniffer which records the data going over the serial bus....

bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://members.eunet.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] HD44780 lcd n/w

[Michael R. <re...@eu...>]

Hi Simon,

> small problem i have a REDHAT 9  2.4.20-8
> i got the source got it going but my lcd will not work got xterm to work 
> (no entries in stderr?)
> and got the X11 too work great...

> #lcd4linux -Fvv
[...]
> wiring: [DISPLAY:RS]<==>[PARPORT:AUTOFD]
> wiring: [display :rw ]<==>[parport:gnd]
> wiring: [display:enable]<==>[parport:strobe]
> wiring: [display:enable2]<==>[parport:select]
> wiring: [display:gpo]<==>[parport:init]
looks good...

> heres lcd4linux.conf
[...]
> Wire.RW "GND"               #RW (pin 5 lcd hardwired to ground)
> Wire.RS "AUTOFD"           #RS  (pin 4 lcd to pin 14 DB-25 "Autofd")
> Wire.ENABLE "STROBE"     #E (pin 6 lcd to pin 1 DB-25 "strobe")
> Wire.GPO "INIT
looks good, too, but just to be sure, you should add/modify these two lines:
Wire.ENABLE2 "GND"
Wire.GPO "GND"

> the data lines (DB0........DB7 on the display,DB1 ....DB8 on the 
> parrallel port)are connected directly
> RS pin 4 lcd to pin 14 "autofd"
> RW hardwired to gnd
> E pin 6 lcd to pin 1 DB-25
looks correct, too.

so your wiring seems to be ok. You did double-check, did you?

Does the display work with some other software? (lcdproc, or windows..)

What happens on the display a) if you connect power to it, and b) when 
you start lcd4linux?

Hmmm.... maybe you're facing the problem that the display requires 5V on 
the data lines, but your parport provides only 3.3V?

bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://members.eunet.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

[lcd4linux] Re: lcd4linux

[Michael R. <re...@eu...>]

Hi there,

>> The wiring entries in lcd4linux.conf should be:
>>
>> Wire.RW       "GND"
>> Wire.RS       "INIT"
>> Wire.ENABLE   "STROBE"
>> Wire.ENABLE2  "GND"
>> Wire.GPO      "GND"

> thanks, it workz!!
Fine!

> can you make a GUI for this amaizing stuff? (like jalcds clean & useful)
No, I'm afraid I don't want to. I'm focussing on the internals of 
lcd4linux. If you or someone wants to create a GUI (mainly for 
creating/modifying the lcd4linux.conf), you're welcome!

bye, michael

-- 
Michael Reinelt <re...@eu...>
http://members.eunet.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] Nexcom - HD44780

[Michael R. <re...@eu...>]

Hi Wayne,

> I am having problems setting up lcd4linux with my new nexcom machine. Maybe
> there is somebody out there that it has worked with. I have the model 1045
> which uses (as far as I know) the HD44780 driver. It looks like the machine
> on the frontpage of the lcd4linux site.
> 
> I dont see anything though on the display. I have heard that I must specify
> "LCM-162" as a "Model". How would i do this .. i tried adding the line model
> "LCM-162" to the config but this didnt work. I am running kernel 2.6.7.

Support for the LCM-162 is in CVS aka 0.10 only. So you have to get the 
CVS version.

HTH, Michael

-- 
Michael Reinelt <re...@eu...>
http://members.eunet.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

[lcd4linux] HD44780 lcd n/w

[Simon C. <sim...@ho...>]

hi all
small problem i have a REDHAT 9  2.4.20-8
i got the source got it going but my lcd will not work got xterm to work (no 
entries in stderr?)
and got the X11 too work great...

#lcd4linux -Fvv
version 0.9.11 starting
lcd4linux.c: initialising driver HD44780
HD:44780: controlling 0 GPOs
wiring: using display with 1 controllers
wiring: using 8 bit mode
wiring: [DISPLAY:RS]<==>[PARPORT:AUTOFD]
wiring: [display :rw ]<==>[parport:gnd]
wiring: [display:enable]<==>[parport:strobe]
wiring: [display:enable2]<==>[parport:select]
wiring: [display:gpo]<==>[parport:init]
udelay.c: cpu supports time stamp counter
udelay.c: cpu runs at 800.055000 mhz
udelay.c: using tsc delay loop,801 ticks per microsecond
parport.c using raw port 0x378
processor.c: Display: 4 rows, 20 columns, 5x8 pixels, 0 icons, 0 gpos
processor.c: ====================
processor.c: Timings:
processor.c: 500 msec text updates
processor.c: 100 msec bar  updates
processor.c: 100 msec icon updates
processor.c: 100 msec GPO updates
processor.c: -------------------------------
processor.c: 100 msec data collection
processor.c: 100 msec data processing
processor.c: =================
processor.c: Row1: ** %o %v **
processor.c: Row2: %p CPU %r MB RAM
processor.c: Row3: BUSY %cb%% $r 10cs+cb
processor.c: Row4: LOAD%1l%L$r10L1
lcd4linux.c:  starting main loop
system.c: open(/proc/loadavg)=3
system.c: open (/proc/stat)=4
system.c: uname(sysname)=Linux
system.c: uname(release)=2.4.20-8
system.c: uname(machine)=i686
system.c: sizeof(/proc/kcore)=135454720 bytes

i tried a 2x16 which had been working with a small pic micrcontroller and a 
new 4x20 also a hd44780

heres lcd4linux.conf

Display HD44780
Port 0x378
Size 20x4
Bits 8
Wire.RW "GND"               #RW (pin 5 lcd hardwired to ground)
Wire.RS "AUTOFD"           #RS  (pin 4 lcd to pin 14 DB-25 "Autofd")
Wire.ENABLE "STROBE"     #E (pin 6 lcd to pin 1 DB-25 "strobe")
Wire.GPO "INIT
Row1 "** %o %v **"
Row2 "%p CPU %r MB RAM "
Row3 "BUSY %cb%% $r 10cs+cb"
Row4 "LOAD%1L%L$r10L1    "


the data lines (DB0........DB7 on the display,DB1 ....DB8 on the parrallel 
port)are connected directly
RS pin 4 lcd to pin 14 "autofd"
RW hardwired to gnd
E pin 6 lcd to pin 1 DB-25

hope this can shed some light
thanks
Simon Clare

Re: [lcd4linux] parallel port access problem (re-post from LEAF mailing list)

[Kevin K. <sup...@gm...>]

talked through a few things Michael - turns out the modules were
loading in the wrong order, switched the load order to parport.o,
parport_pc.o, and lastly ppdev.o and it's working now.

thanks a lot, appreciate the help - great package, looks great, i'll
be playing with the configuration options for a while.




On Tue, 21 Dec 2004 22:10:43 +0100, Michael Reinelt <re...@eu...> wrote:
> Hi there,
> 
> > Michael Reinelt wrote:
> >
> >> - as a quick hack, you could try to specify "Port 0x378" in your
> >> lcd4linux.conf. Then it will not use ppdev, but raw port i/o (which is
> >> ugly, but if it works... who cares :-)
> >
> > no, that will not work on a LEAF box - raw I/O is not allowed from
> > userspace on the LEAF kernels (part of the grsecurity patches we apply).
> 
> Oh, silly me - now I remember....
> 
> bye, Michael
> 
> --
> Michael Reinelt <re...@eu...>
> http://members.eunet.at/reinelt
> GPG-Key 0xDF13BA50
> ICQ #288386781
>

Re: [lcd4linux] parallel port access problem (re-post from LEAF mailing list)

[Michael R. <re...@eu...>]

Hi there,

> Michael Reinelt wrote:
> 
>> - as a quick hack, you could try to specify "Port 0x378" in your 
>> lcd4linux.conf. Then it will not use ppdev, but raw port i/o (which is 
>> ugly, but if it works... who cares :-)
> 
> no, that will not work on a LEAF box - raw I/O is not allowed from 
> userspace on the LEAF kernels (part of the grsecurity patches we apply).

Oh, silly me - now I remember....

bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://members.eunet.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] parallel port access problem (re-post from LEAF mailing list)

[Kevin K. <sup...@gm...>]

As Martin said, i'm blocked from directly accessing the port - that's
why i'm onto the parport type access.

I neglected to mention that i'm really not familiar with linux that
much and have only learned as much as required to setup and use this
LEAF box.

i'd really love some direction as to how to check how exactly the
parport device should be accessed.  if i look under /dev/ i see
parport0, parport1, etc. up to parport3.  i believe leaf does not use
the subdirectory system for parport devices like some other linux
distributions (i'm always up for being corrected, though)..

i'm not sure what you mean by major/minor number of /dev/parport0 -
please direct me as to how to provide more information on this front.

is there a way to check and see that the parallel port is actually
configured and ready for use? how do i know if i'm just not calling it
properly with the port specification of /dev/parport0 ?

i greatly appreciate the help, i'd love to sort this out but i don't
know enough about it to move ahead any farther on my own.


On Tue, 21 Dec 2004 10:55:37 +0100, Martin Hejl <ma...@he...> wrote:
> Hi Michael,
> 
> Michael Reinelt wrote:
> > - as a quick hack, you could try to specify "Port 0x378" in your
> > lcd4linux.conf. Then it will not use ppdev, but raw port i/o (which is
> > ugly, but if it works... who cares :-)
> no, that will not work on a LEAF box - raw I/O is not allowed from
> userspace on the LEAF kernels (part of the grsecurity patches we apply).
> 
> Martin
>

[lcd4linux] Nexcom - HD44780

[Wayne W. <wa...@wa...>]

Hi 

I am having problems setting up lcd4linux with my new nexcom machine. Maybe
there is somebody out there that it has worked with. I have the model 1045
which uses (as far as I know) the HD44780 driver. It looks like the machine
on the frontpage of the lcd4linux site.

I dont see anything though on the display. I have heard that I must specify
"LCM-162" as a "Model". How would i do this .. i tried adding the line model
"LCM-162" to the config but this didnt work. I am running kernel 2.6.7.

My config looks like this :

Display HD44780
Port /dev/parports/0
Size 16x2
Delay 503
Bits 4
Row1 "Test1"
Row2 "Test2"

If I run the command : 
server lcd4linux # /usr/bin/lcd4linux -f /etc/lcd4linux/lcd4linux.conf  -Fvv
Version 0.9.11 starting
lcd4linux.c: initializing driver HD44780
HD44780: controlling 0 GPO's
wiring: using display with 1 controllers
wiring: using 4 bit mode
wiring: [DISPLAY:RS]<==>[PARPORT:DB4]
wiring: [DISPLAY:RW]<==>[PARPORT:DB5]
wiring: [DISPLAY:ENABLE]<==>[PARPORT:DB6]
wiring: [DISPLAY:ENABLE2]<==>[PARPORT:DB7]
wiring: [DISPLAY:GPO]<==>[PARPORT:GND]
udelay.c: CPU supports Time Stamp Counter
udelay.c: CPU runs at 1993.732000 MHz
udelay.c: using TSC delay loop, 1994 ticks per microsecond
parport.c: using ppdev /dev/parports/0
processor.c: Display: 2 rows, 16 columns, 5x8 pixels, 0 icons, 0 GPOs
processor.c: ========================
processor.c: Timings:
processor.c: 500 msec Text updates
processor.c: 100 msec Bar  updates
processor.c: 100 msec Icon updates
processor.c: 100 msec GPO  updates
processor.c: ------------------------
processor.c: 100 msec data collection
processor.c: 100 msec data processing
processor.c: ========================
processor.c: Row1: Busy
processor.c: Row2: Load
lcd4linux.c: starting main loop
lcd4linux.c: got signal 2
lcd4linux.c: leaving main loop



Any help is much appreciated 

Thanks
Wayne Wilson

Re: [lcd4linux] parallel port access problem (re-post from LEAF mailing list)

[Martin H. <ma...@he...>]

Hi Michael,

Michael Reinelt wrote:
> - as a quick hack, you could try to specify "Port 0x378" in your 
> lcd4linux.conf. Then it will not use ppdev, but raw port i/o (which is 
> ugly, but if it works... who cares :-)
no, that will not work on a LEAF box - raw I/O is not allowed from 
userspace on the LEAF kernels (part of the grsecurity patches we apply).

Martin

[lcd4linux] Re: lcd4linux

[Michael R. <re...@eu...>]

Hi Spuds,

sorry for the delay, I've been too busy....

> Please help me to start my lcd! 
> I have a HD44780 display with this wireing:
> 
> Data/instruction signal - RS	parallel port pin 16
> Chip enable signal - E		parallel port pin 1
> data bit 0 - DB0			parallel port pin 2
> data bit 1 - DB1			parallel port pin 3
> data bit 2 - DB2			parallel port pin 4
> data bit 3 - DB3			parallel port pin 5
> data bit 4 - DB4			parallel port pin 6 
> data bit 5 - DB5			parallel port pin 7
> data bit 6 - DB6			parallel port pin 8
> data bit 7 - DB7			parallel port pin 9
> Led anode - LED+			4.2V
> Led cathode - LED-			ground
> Ground - Vss				ground
> Supply voltage for logic - Vdd	5V
> Input voltage for LCD - V0	ground
> Read/Write mode - R/W		ground

The wiring entries in lcd4linux.conf should be:

Wire.RW       "GND"
Wire.RS       "INIT"
Wire.ENABLE   "STROBE"
Wire.ENABLE2  "GND"
Wire.GPO      "GND"


HTH, Michael

-- 
Michael Reinelt <re...@eu...>
http://members.eunet.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] parallel port access problem (re-post from LEAF mailing list)

[Michael R. <re...@eu...>]

Hi Kevin,

> i posted this yesterday on the leaf mailing list, was hoping to get a
> fix soon and it's not had any hits yet, so i'm re-posting - hope
> that's not a problem.
No. it is not.

> the lcd4linux module can't gain access to the parallel port.
> i'm using bering-uClibc, 2.1 on a EPIA 5000 mini-itx motherboard.
> 
> on startup i'm loading the ppdev.o, parport.o, and parport_pc.o
> modules and the messages file under /var/log shows "parport0: PC-style
> at 0x378 [PCSPP(,...)]" on boot-up.
> 
> however, when i run the lcd4linux module - after everything
> initializes and it goes to set up the parallel port i get:
> parport.c: using ppdev /dev/parport0
> parport: open(/dev/parport0) failed: No such device
> HD44780: could not initialize parallel port!
> 
> any assistance would be appreciated, i'm not sure why it says there's
> no device parport0, since it seems to initialize properly on boot-up.

Hmmm...

- is there a /dev/parport0 device file? (or is it called /dev/parport/0)?

- what's the major/minor number of /dev/parport0?

- as a quick hack, you could try to specify "Port 0x378" in your 
lcd4linux.conf. Then it will not use ppdev, but raw port i/o (which is 
ugly, but if it works... who cares :-)


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://members.eunet.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

[lcd4linux] LIS (Lost In Space) Display

[Michael R. <re...@eu...>]

Hi Patrick,

> Dear Sir,
> i am following your suggestion of posting an email to you for unknown LCD.
> I got one.
> LIS (Lost In Space) from VL Systems model: 
> http://www.vlsys.co.kr/en/product/indicator/lcdred.html
>  
> it works fine with Windows but i wanted it installed on my REDHAT 9.1 
> system.
> i could not make it run..
> and my C knowledges are a bit far away..
>  
> do you have any clue to make your software running..

Well, I'm sure it's possible to use it with lcd4linux.

But I'd need more information: from their website, I can't even find out 
how it's connected (Parallel port, USB, ...)

Do you have something like a data sheet or a detailed description of the 
display?

bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://members.eunet.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

[lcd4linux] parallel port access problem (re-post from LEAF mailing list)

[Kevin K. <sup...@gm...>]

i posted this yesterday on the leaf mailing list, was hoping to get a
fix soon and it's not had any hits yet, so i'm re-posting - hope
that's not a problem.

anyway, to the problem:

the lcd4linux module can't gain access to the parallel port.
i'm using bering-uClibc, 2.1 on a EPIA 5000 mini-itx motherboard.

on startup i'm loading the ppdev.o, parport.o, and parport_pc.o
modules and the messages file under /var/log shows "parport0: PC-style
at 0x378 [PCSPP(,...)]" on boot-up.

however, when i run the lcd4linux module - after everything
initializes and it goes to set up the parallel port i get:
parport.c: using ppdev /dev/parport0
parport: open(/dev/parport0) failed: No such device
HD44780: could not initialize parallel port!

any assistance would be appreciated, i'm not sure why it says there's
no device parport0, since it seems to initialize properly on boot-up.

thanks,

kevin.

Re: [lcd4linux] Problems with T6963C

[Michael R. <re...@eu...>]

Hi Juergen,

> My probleme is, that only the upper half is working properly; the
> lower half can also be used but there is something like a snow shower.
> If I put some text to this area the snow is gone. Does somebody have
> the same problem? 
Will the text in the lower half be displayed correctly?

Looking into the code of drv_T6963.c, looks like the internal memory 
layout is deivided into upper and lower half, having two different 
memory starting addresses. But this has never been coded out, because I 
don't have such a nice display :-(

If you want to be my tester, I'll try to integrate this code...

> Another question is, if it is planed to support larger fonts? For my
> display i think a 8x16 font would be better to read from far away.
Feel free to provide a font file for 8x16, and I'll integrate it into 
lcd4linux. It should look similar to the font-6x8.h


bye, michael

-- 
Michael Reinelt <re...@eu...>
http://members.eunet.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] Strange characters on HD44780 OLED display

[Michael R. <re...@eu...>]

Hi STefan,

sorry for the delay, I'm too busy at the moment...

> My 20x2 OLED works fine on my firend's Windows box but when I run it
> on my Linux machine with LCD4Linux (and lcdproc) the characters are
> misplaced and other "bad" characters are mixed in.
Looks like aeither a wiring or a timing fault.

> I have used this wiring
> http://www.fractronics.com/lcdcontrast.gif
Their web site seems to be unavailable at the moment, so I can't check 
your wiring. Can you send me a wiring description or a diagram?

> but I don't know it it's a 4-bit, 8-bit or Winamp. What I _do_ know
> is that the Winamp wiring example shown on
I'm pretty shure that it's 8-bit (otherwise you won't use control lines 
of your parport, but data lines only.

> When I run it the display show the following:

> -------------------- 
> * LCD4Linu| 0.=.51

> --------------------

This should be the startup splash screen, but with destroyed chars.

bye, michael


-- 
Michael Reinelt <re...@eu...>
http://members.eunet.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781