[Lcdproc] Re: LCDproc digest, Vol 1 #1904 - 4 msgs

[Jim Dearden]

Peter Marschall <peter@adpm.de> wrote:
> If heartbeat is the culprit, then - depending on the LCDproc version used - 
> setting Heartbeat=off in LCD.conf may help.
> It is in current CVS, but not yet in 0.5.2 or earlier versions.
>
> It might as well be that there are subtle differences in the command
> set that make this type of converter differ from the others.
>
> Unfortunately MO has such an awful lot of display types/series with
> sometimes slightly differing command sets (and even with differing
> command sets between different revisions in a series).
> This makes finding the correct commands for all situations a real chore.
>
> It might be worth trying the current CVS version.
> It contains fixes to the MtxOrb driver for some display types.
>   
I'm currently running 0.5.1. Guess I will have to delve into the 
mysteries of CVS and compiling! Oh well, learning is good for you, 
right? :-)

http://www.matrixorbital.ca/manuals/xboard/ has the manual in pdf, in 
looking at it, the command codes seems the same as the current serial 
models, but not all are implemented. It could be that the board is 
missing a command code that the driver uses. Using a terminal program in 
windows, all the commands implemented by the board work correctly. I 
wonder if the serial port in Ubuntu is defaulting to the wrong speed, 
and that this could be the problem. I'm researching "setserial" and will 
try and make sure the port speed is set correctly.

Thanks for the help!

Jim

"Ethan Dicks" <ethan.dicks@gmail.com> wrote:

I've seen the X-Board, but don't happen to have one.  My Matrix
Orbital display is a now-ancient 4x20 VFD with keyboard option (which
all works great under recent CVS versions of LCDproc).


>> > > Under Windows, using LCD Smartie, the board works fine. I'm having
>> > > problems with it under Ubuntu Fiesty Fawn, on the same system. The
>> > > symptoms are a lot of flickering on the display, with LCDd running, even
>> > > before lcdproc is started. It appears that the cursor homing is not
>> > > working quite right, sometimes the first line is mirrored on the second
>> > > line.
>>     

That sounds a little like the symptoms I was seeing with the Matrix
Orbital driver before I tracked down a minor issue with a single
incorrect command byte sent from LCDd.


> > It might as well be that there are subtle differences in the command
> > set that make this type of converter differ from the others.
>   

Entirely possible.  When I was tracking down things a few months ago,
I found a variety of brightness, contrast, and backlight commands.
They came in two or three general varieties, at least.


> > Unfortunately MO has such an awful lot of display types/series with
> > sometimes slightly differing command sets (and even with differing
> > command sets between different revisions in a series).
>   

True, unfortunately.


> > This makes finding the correct commands for all situations a real chore.
>   

All too true, unfortunately.


> > It might be worth trying the current CVS version.
> > It contains fixes to the MtxOrb driver for some display types.
>   

Yes.  That was going to be my recommendation, since that's what did it
for my VKD204 display.

If the latest CVS snapshot doesn't do it, I can see about picking up
an X-Board and assembling it.  I have a variety of displays and don't
mind having one more.  At the moment, my two favorite displays are
that Matrix Orbital VKD204 I mentioned, and a 4x40 LCD with a lcd2usb
"backpack" interface.  I've recently switched from a Linux laptop to a
MacBook Pro, so I still need to get a working USB-serial dongle to be
able to go back and use my VKD204.  The lcd2usb is working fine
(through a USB hub) so I don't anticipate a problem trying out an
X-Board.

-ethan

It might indeed be the command set, although it seems to be the 
standard, although limited one. I will try out the CVS snapshot when I 
can, I'll have to download a client and set it up. Thanks for the help!

Jim