[Lcdproc] MOU-AL202C-XR
Ray Molenkamp
rmolenkamp@matrixorbital.ca
Wed May 14 22:21:02 2008
Just grabbed a mou-vfd module off the shelf and tried
reproducing your issue. The package in the debian repository
(0.5.2) indeed has the K problem. The current CVS version
works fine though so I guess somebody already fixed your problem.
Greetings,
--Ray
> The issue is that this display has three output ports rather than 1 or
> 6, so I'd say a new display type may be in order that supports three
> ports.
> I recall trying the other display types but not having success with them.
> Also, this display is reporting a type not in the current table, so
> that should be added as well.
> How would yuo like to proceed with these changes ?
>best,
On Sat, May 10, 2008 at 9:21 AM, Peter Marschall <peter@adpm.de <mailto:peter@adpm.de>> wrote:
>/ Hi,
/>/
/>/
/>/
/>/ On Tuesday, 6. May 2008, John Novak wrote:
/>/ > I purchased the above unit recently and am running LCDProc 0.5.2 on Ubuntu
/>/ > Feisty.
/>/ >
/>/ > I have checked the unit's settings with lusb and they are correct.
/>/ >
/>/ > I'm getting data on the display, but there are three capital 'K's
/>/ > displaying at fixed locations on the screen. I can see my data appear, but
/>/ > the K's overlay them quickly and they seem to appear on all screens.
/>/ >
/>/ > The default client's data is formatted quite badly, and scrolling does not
/>/ > seem to be working properly.
/>/ >
/>/ > Have you heard of these symptoms ?
/>/
/>/ Please report what the server reports.
/>/ It is hard to guess what goes on, if one does not get all information.
/>/
/>/ The MtxOrb driver of LCdproc knows of 4 different sub-types (option "Type")
/>/ that affect the driver's behaviour.
/>/ It may be that your display is not directly supproted, but close enough to
/>/ one of the existing types.
/>/ Please try changing these settings.
/>/
/>/ If it helps, please report back what setting helped your display.
/>/
/>/ Of course, it never hurts to try out the latest nightly tar ball (you
/>/ need to complie it yourself) to see whetherthe bug is already fixed there.
/>/
/>/ Regards
/>/ Peter
/>/
/>/ --
/>/ Peter Marschall
/>/ peter@adpm.de <mailto:peter@adpm.de>
/>/ _______________________________________________
/>/ LCDproc mailing list
/>/ LCDproc@lists.omnipotent.net <mailto:LCDproc@lists.omnipotent.net>
/>/ http://lists.omnipotent.net/mailman/listinfo/lcdproc
/>/
/