LCDProc 0.5.4-dev

mdima

Good job on adding the server deamon interface changes. Looks good and like the drop down % on the brightness and contrast. I used the drop down for brightness and contrast works great because could not use default. So, perfect. Keep up the good work.
-Joe Cowboy

Hi Joe Cowboy,
glad you liked it! Actually was your idea, I just needed a while to think about it and to find out on how to make it safe for all the drivers…

Ciao,
Michele

jpsb

@mdima:

@jpsb:

I just use the HD44780 in the driver list, and by connecting the display, the system log shows "LCD2USB device found"
The display is a little slow, and works best by refresh frequency on 5 or 10 sec.

Hi JPSB,
mmhhh… seems strange... how many screens you have active? Did you have the same problem also with the previous version?

Thanks,
Michele

Hi Michele

Yes I had the same problem with last version.
I only have "Interface Traffic" and "Load" running.
But the new version with options to change contrast, etc. makes the display is running perfectly.
I have not had any luck getting the new driver "hd44780 Fast" to run.
But as I said, it runs perfectly with the other changes.
So once again, many thanks for a fantastic job.

See my youtube video of the display:
http://www.youtube.com/watch?v=moL-x1HpPew&feature=autoplay&list=ULmoL-x1HpPew&lf=mfu_in_order&playnext=46

mdima

Hi jpsb,
this is awesome! I remove the "hd44780 Fast" driver, since it's useless.

Thank you for the feedback!

AFAIK there's only 1 thing missing as new feature: the "output" commands to control the optional LEDs on the panel (some models have). I just need 2-3h of relax one evening to do that.

Michele

Brak

Any chance you guys could look into the EZIO-100 driver? I think this LCD is very common on OEM hardware appliances, Portwell (Used by UntangleAppliances.com for example I believe), Lanner and a few others.

This guy made a driver for LCDProc 4.5.X I think, so it would need updated. http://lists.omnipotent.net/pipermail/lcdproc/2004-January/008494.html

I wanted to maybe get one of the Lanner systems ( http://www.leitechnology.com/6-GbE-Port-1U-Rackmount-Network-Appliance-FW-7565E.htm ), but the LCD would be useless unless there is a driver. :(

fmertz

@mdima:

I just updated the package to version 0.6. The only change was to integrate the sdeclcd driver.

I released the code for the driver here:

https://github.com/fmertz/sdeclcd/tree/sdec

Firebox users, just install the lcdproc-dev package, pick the sdeclcd driver and a port, and you should be good to go.

mdima: for this driver we need the following configuration for the buttons. The resulting LCDd.conf should be:


PrevScreenKey=Down
NextScreenKey=Up

[menu]
MenuKey=Left
EnterKey=Right
UpKey=Up
DownKey=Down

Taking a step back, lcdproc can use a number of keys (up, down, left, right, Enter, Menu, Next and Prev). Each driver has between 0 and 6 buttons. Depending on the particulars of each setup, some buttons have to do more than one key. As the Firebox setups has the buttons organized visually as a diamond, Menu can be Left and Enter can be Right. Updating the package to have this resulting LCDd.conf would bring the package support for the SDEc LCD driver to a 100%. Thanks to stephenw10 for documenting this issue.

fmertz

@Brak:

Any chance you guys could look into the EZIO-100 driver?

Post a bounty and send me some hardware ;)

Brak

@fmertz:

@Brak:

Any chance you guys could look into the EZIO-100 driver?

Post a bounty and send me some hardware ;)

Haha, might not be too far fetched of an idea need be…

Brak

Using my firebox, I was trying this out. Seem to work fine with the menu edits. One issue I am having is getting LCDExec working. Is it supposed to launch on it's own? I added the lcdexec.conf file, but I don't believe the process is ever launching.

If I make my own rc.d script to start it, it works fine.

Also, any modifications I make to LCDd.conf gets wiped at reboot, what am I doing wrong?

mdima

@fmertz:

mdima: for this driver we need the following configuration for the buttons. The resulting LCDd.conf should be:

fmertz: consider it done in a couple of days!

Ciao,
Michele

mdima

@Brak:

Using my firebox, I was trying this out. Seem to work fine with the menu edits. One issue I am having is getting LCDExec working. Is it supposed to launch on it's own? I added the lcdexec.conf file, but I don't believe the process is ever launching.
If I make my own rc.d script to start it, it works fine.
Also, any modifications I make to LCDd.conf gets wiped at reboot, what am I doing wrong?

Hi Brak,
lcdexex is not run at all, the package use its own client to interact with LCDproc. Sorry about the question, why do you need it to run?

The file LCDd.conf gets refreshed every time the package gets a "resync" command, so I think also when the box is restarted. If you need to make some permanent change to LCDd.conf you need to modify the lcdproc.inc file in order to let it write the LCDd.conf file every time with the changes you need.
If the changes you need are related to the menu (see previous post), just consider it done in a couple of days.

Ciao,
Michele

stephenw10

Great work Michele, thanks for all you've done. :)

I have to get a post in this thread so I don't miss updates!

Steve

mdima

@stephenw10:

Great work Michele, thanks for all you've done. :)

I have to get a post in this thread so I don't miss updates!

Steve

Thanks a lot! I just released a new update, I summarize the changes:

Removed driver "HD44780 fast" since the problem why this fork was created has been solved in a different way
Set the custom Keys and Menu section for the "sdelcd" driver (fmertz: I wait for your feedback!)
Added the Blacklight setting. Now it is possible to optionally turn the blacklight on, off or (default) to leave it managed by the panel
Added the "output led" support for the "CFontz633" driver. This is totally to test since my panel doesn't have any output led, worked almost blind (fireman039: I wait for your feedback! Consider that I was working almost blind on this, to test it I need one of that panels in my office)

The changes are published on the version "LCDproc 0.5.4 pkg v. 0.7". Soon it will be available for the update… (thanks to Chris, Jim, Ermal and all the others members of the stuff that approve my pull requests).

Thanks to all,
Michele

Brak

@mdima:

Hi Brak,
lcdexex is not run at all, the package use its own client to interact with LCDproc. Sorry about the question, why do you need it to run?

I use a menu I made that runs in LCDExec, it does like reboot commands and stuff. I can't get it to cleanly start up with this package.

mdima

@Brak:

@mdima:

Hi Brak,
lcdexex is not run at all, the package use its own client to interact with LCDproc. Sorry about the question, why do you need it to run?

I use a menu I made that runs in LCDExec, it does like reboot commands and stuff. I can't get it to cleanly start up with this package.

Hi Brak,
did it work with the previous version of LCDproc? (I mean, not LCDproc-dev) Just to understand if it's something I made that interfers with your menu.

Can I have your lcdd.conf? Just to look which are the changes you need for your menu to work…

Thanks,
Michele

stephenw10

Just to report that the Firebox keypad now works great, as expected, and the driver file seems to be correct also.
Tested on the X-Core-E box.

The package version is still reported as 0.6 in package manager but as 0.7 in Services: LCDProc.
It's still listed as 0.6 in pkg_config.8.xml.

Thanks again. :)

Steve

mdima

stephenw10, great, thanks for the feedback!!

Michele

fmertz

@mdima:

The changes are published on the version "LCDproc 0.5.4 pkg v. 0.7".

Michele,

Just to throw it out there: any reason to settle on lcdproc-0.5.4? Seems like lcdproc-0.5.5 has been out for a couple of months. Maybe before you commit to merging this -dev package to make it official, we could upgrade to the latest and test among ourselves. I have no specific need to upgrade, just trying to get folks to benefits of the latest version. As usual, I'll be happy to provide a 0.5.5 binary of the SDEC driver if needed.

mdima

@fmertz:

@mdima:

The changes are published on the version "LCDproc 0.5.4 pkg v. 0.7".

Michele,

Just to throw it out there: any reason to settle on lcdproc-0.5.4? Seems like lcdproc-0.5.5 has been out for a couple of months. Maybe before you commit to merging this -dev package to make it official, we could upgrade to the latest and test among ourselves. I have no specific need to upgrade, just trying to get folks to benefits of the latest version. As usual, I'll be happy to provide a 0.5.5 binary of the SDEC driver if needed.

you're right! I've just seen that lcdproc-0.5.5 is available in the package directory (http://files.pfsense.org/packages/8/All/), it was uploaded on the 20th of December… on the next release I will use that binaries, at a first sight it should have the same drivers than 0.5.4, so there should not be any change in the package itself...

After that, we can see if we need a new compiled version for the sdelcd driver or not!

Ciao,
Michele

fmertz

@stephenw10:

Tested on the X-Core-E box.

Just offering a suggestion up for a vote: For folks running pfSense on the Watchguard Firebox, would it be better if the driver entry in the web interface was called "Watchguard Firebox w/ SDEC LCD" instead of "sdeclcd"? It seems like the average person might not know (or need to care) that the LCD is from SDEC. Besides, the driver is kind of hard-coded for that implementation already. Just a thought.

mdima

@fmertz:

@stephenw10:

Tested on the X-Core-E box.

Just offering a suggestion up for a vote: For folks running pfSense on the Watchguard Firebox, would it be better if the driver entry in the web interface was called "Watchguard Firebox w/ SDEC LCD" instead of "sdeclcd"? It seems like the average person might not know (or need to care) that the LCD is from SDEC. Besides, the driver is kind of hard-coded for that implementation already. Just a thought.

I don't know if Watchguard is the only company that use that panel… maybe something like:
"sdeclcd (Watchguard Firebox w/ SDEC LCD, etc)"
would be better, what do you think?
The same could be for all the other panels... would be a little mess to keep them updated.