January 18, 20251 yr When I am a little more familiar with how github works and confident that my changes haven't ruined anything I will
January 18, 20251 yr Author 2 hours ago, wabamad said: When I am a little more familiar with how github works and confident that my changes haven't ruined anything I will I can look at your commits on your repo and copy them across if that is easier.
January 18, 20251 yr 8 hours ago, wabamad said: I tried my hand at fixing some things and I seem to have gotten it working much better for my screen. I'm not sure what you are using for hardware but I can try to make it work for you if you are willing to test it. Hi @wabamad, Thanks for the generous offer. That's a good looking LCD display you have. Unfortunately, my LCD panel is an ICP A125 with just two lines of 16 5x7 pixel characters, which is stock on the QNAP TS-853A. On top of that, it communicates at a liesurely 1200baud, leading to ugly things like time displays with colons that blink out of sync with second changes. In the end, I took a simpler route that lets me know if the system is booting, the array has been started, or the array has been stopped. I just manually write to the display using a couple of scripts called from the User Scripts plugin: LCD_Array_Start: #!/bin/bash # Define command to clear LCD LCD_Clear="\x4D\x0D" # Define commands to send 16 character lines. LCD_Line0="\x4D\x0C\x00\x10" LCD_Line1="\x4D\x0C\x01\x10" # Define 16 character strings Stringx="1234567890123456" StringA=" Unraid-QNAP " StringB=" Ready " # Set the baud rate to 1200 stty -F /dev/ttyS1 1200 printf $LCD_Clear > /dev/ttyS1 printf "$LCD_Line0%s", "$StringA" > /dev/ttyS1 printf "$LCD_Line1%s", "$StringB" > /dev/ttyS1 LCD_Array_Stop: #!/bin/bash # Define command to clear LCD LCD_Clear="\x4D\x0D" # Define commands to send 16 character lines. LCD_Line0="\x4D\x0C\x00\x10" LCD_Line1="\x4D\x0C\x01\x10" # Define 16 character strings Stringx="1234567890123456" StringA=" Unraid-QNAP " StringB=" Array Stopped " # Set the baud rate to 1200 stty -F /dev/ttyS1 1200 printf $LCD_Clear > /dev/ttyS1 printf "$LCD_Line0%s", "$StringA" > /dev/ttyS1 printf "$LCD_Line1%s", "$StringB" > /dev/ttyS1 That's really all of the info I need when I happen to walk by the NAS in the laundry room. Thanks again for the offer of help and for sharing the nice display you've got going. -- Miss_Sissy
January 18, 20251 yr 8 hours ago, SimonF said: I can look at your commits on your repo and copy them across if that is easier. I did make some changes inside the lcdproc tar to get screen selection working properly and get rid of the screen flashing. lcdproc.conf to be specific. I made a mess of my repo figuring out how git works and deleted a bunch of old tars and screwed around trying to get the makepkg script working (I had no luck lol). This is new to me but I am trying. Inside the directory working the lcdproc tar is extracted and the edits to lcdproc.conf to get screen selection working properly have been done as well as commenting out the load settings that make the screen flash and some changes for iface (interestingly i could not get bond0 to work as an interface, didn't dig very deep into that). If this is something that you are going to continue I am willing to help or test in any way I am able. Edited January 18, 20251 yr by wabamad Clarity and extra information
January 18, 20251 yr 2 hours ago, Miss_Sissy said: In the end, I took a simpler route that lets me know if the system is booting, the array has been started, or the array has been stopped. I just manually write to the display using a couple of scripts called from the User Scripts plugin: Looks good! Simple and effective. From a quick google search that display may work with the icp a106 lcdproc driver.
January 18, 20251 yr 55 minutes ago, wabamad said: Looks good! Simple and effective. From a quick google search that display may work with the icp a106 lcdproc driver. Thanks. I probably won't even look at the display more than once every few weeks, and then just in passing because I happen to be in the laundry room where my primary 3D printer lives. The ICP A125 does work with the ICP A106 driver and that's the one I used when I set up LCD Manager. My issue wasn't the panel driver, which worked fine. It was displays that didn't fit on the tiny 16x2 format. Most of the preconfigured displays seem to be formatted for LCD panels at least 20 characters wide, so I was ending up with things like time displays with missing seconds and screen titles and host names that continually scrolled. This is not a criticism of @SimonF's LCD Manager plugin. It's not his fault that QNAP put a 16x2, 1200 baud display in my NAS; I would not expect him to tailor his displays for something that pitiful. With a list of available system status variables, I could printf my own displays. Let me pass in two strings of 16 characters formatted however I want. But, really, I'm fine with what I have put together now.
February 6, 20251 yr @SimonF any luck getting it to show booting and array starting and such before its fully up and running?
March 15, 20251 yr Author 43 minutes ago, Tuomio said: Hi @SimonF, would it be possible to add imonlcd driver to the next release? The module should is included in /lib/lcdproc. https://lcdproc.sourceforge.net/docs/lcdproc-0-5-5-user.html#imonlcd-howto Do you know which version of the device you have?
March 15, 20251 yr Quote 1 hour ago, SimonF said: The module should is included in /lib/lcdproc. https://lcdproc.sourceforge.net/docs/lcdproc-0-5-5-user.html#imonlcd-howto Do you know which version of the device you have? Thanks for the quick reply and apologies, I need to check my vision! It's there and lcdproc also working nicely. I have an old Antec case with iMon 96x16 pixel display (also with fixed symbols around the display). Thanks again for your work on this. Nice to have the display again in practical use also with Unraid.
September 15, 2025Sep 15 Hi SimonF,I'm a dummy, and I wanted to use a LCD like this :LEXTRONICAfficheur LCD rétroéclairé COMLCD20X4 4x20 caractèresAfficheur LCD rétroéclairé COMLCD20X4 alphanumérique, 4x20 caractères, contrôleur intégré, connecteur 16 broches, rétroéclairage +5Vcc.Is it possible to use with your App ?Is it possible to use a USB module to use with it ?Thanks again ;) Edited September 15, 2025Sep 15 by PicPoc
September 15, 2025Sep 15 Author 11 minutes ago, PicPoc said:Hi SimonF,I'm a dummy, and I wanted to use a LCD like this :LEXTRONICAfficheur LCD rétroéclairé COMLCD20X4 4x20 caractèresAfficheur LCD rétroéclairé COMLCD20X4 alphanumérique, 4x20 caractères, contrôleur intégré, connecteur 16 broches, rétroéclairage +5Vcc.Is it possible to use with your App ?Is it possible to use a USB module to use with it ?Thanks again ;)Have a look here to see if that is supported. http://lcdproc.omnipotent.net/hardware.php3
September 17, 2025Sep 17 Sorry, ich kann nur auf DeutschIch habe ein "altes" Display gefunden "siehe bild" Funtioniert das auch unter dem LCD Manager in Unraid ?Gruß Andreas
December 7, 2025Dec 7 Author 3 hours ago, Sonesmj said:Any progress on readynas displays?Do you know the requirements as I don't have any hardware to test.
May 15May 15 On 12/7/2025 at 7:13 PM, SimonF said:Do you know the requirements as I don't have any hardware to test.Ich habe ein paar Bilder des Display und des Tastenfeldes des ReadyNAS 426 gemacht. Ich hoffe du kannst damit etwas anfangen?I took a few pictures of the display and keypad on the ReadyNAS 426. I hope you can make use of them?Display 426:2832ALBCP1711206-18-AF12Laut Google-suche soll es eventuell ein OLED-Display sein.According to a Google search, it might possibly be an OLED display.Eventuell/Possibly: "Graphic Monochrome 12832 LCD Display with AIP315 IC (Interface 6800) Model No. RG12232C1"Tastenfeld (Keypad):ETON ET856 94V-0
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.