#2 Matrix Orbital LK202-25 v1.12 Display problem.

closed
None
5
2012-04-13
2012-04-13
Roots
No

I'm not sure what’s causing this, weather it is the driver or something else? What seems to happen is whatever is on the display the start and end of text is always a character made of all black pixels the a K. Also if the same screen is displayed characters that remain unchanged seem to corrupt as well. I am running pfsense with lcdproc v0.5.5. I also get the following errors:
Apr 12 12:59:01 php: lcdproc: Start client procedure. Error counter: (0)
Apr 12 12:59:00 LCDd: MtxOrb: unable to read device serial number
Apr 12 12:59:00 LCDd: MtxOrb: unable to read device firmware revision
Apr 12 12:59:00 LCDd: MtxOrb: unable to read device type

I could use some help with this as I am a bit out of my depth! See the attachment for a picture.

Discussion

  • Roots

    Roots - 2012-04-13

    Matrix Orbital LK202-25

     
  • Markus Dolze

    Markus Dolze - 2012-04-13
    • assigned_to: nobody --> mmdolze
     
  • Markus Dolze

    Markus Dolze - 2012-04-13

    Hi,

    there may be two issues with your display:

    1. The "unable to read" error mean that LCDd does not receive anything within the 500ms time-out when trying to read those values. Is the RX line of the display connected to your PC at all?

    2. Please have a look at your LCDd.conf used by your pfsense version of LCDproc. For the MtxOrb driver please check that:

    Type=lkd

    If that doesn't work, you may try 'Type=lcd'.

    Additionally, you may try to set

    hasAdjustableBacklight=no

    This may fix the block characters.

     
  • Roots

    Roots - 2012-04-13

    Adding hasAdjustableBacklight=no removed the block characters, then adding Type=lkd removed the K's at the start and the end of the screen.

    Thanks very much mmdolze, its working a treat now.

     
  • Roots

    Roots - 2012-04-13
    • status: open --> closed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks