LCDProc 0.5.4-dev

fireman039

hehe! yes, I was thinking about it and suggesting to use the decimal values… you got it before me!

so, we understood how it works... the matter now is: what do we do with this 4 green-red-orange leds?

Hello,

With the led's we can report the statut of Wan and Lan, 1 led can de assigned to load of the system (ON if load = xx) and one for CPU= xx

This led can be used to act as an "alarm" report status.

Regards

Cino

great work mdima! Now I need to get bigger display. Using a 20x2 right now but its built into the case I'm using.

mdima

@DaHak:

great work, thanks!
it is possible to add the driver for the ax89063 Display?
It is used e.g. by NA-820 (http://axiomtek.com/products/ViewProduct.asp?view=429)
it would be great for me :-)
thanks!

Hi, there are a couple of drivers around for that display, but it is not included in the LCDProc distribution. We could add it as an "external driver" like the nexcom driver.

Can you compile it on FreeBSD (x86)? In this case I could just add the file you send me (ax89063.so) and add the option to use it in the code…

Ciao,
Michele

mdima

@fireman039:

With the led's we can report the statut of Wan and Lan, 1 led can de assigned to load of the system (ON if load = xx) and one for CPU= xx
This led can be used to act as an "alarm" report status.
Regards

yes, I agree!
but the number of NICs can really vary, belive me… I would use:

a led for nics status (if one nic is unplugged gets red, if it's plugged gets green)
a led for carp status (off=no carp, green=at least one ip in master, red=at least one ip in backup)
a led for cpu (green < 50%, orange >50 && <70, red >70%)
a led for what?

DaHak

@mdima:

Hi, there are a couple of drivers around for that display, but it is not included in the LCDProc distribution. We could add it as an "external driver" like the nexcom driver.

Can you compile it on FreeBSD (x86)? In this case I could just add the file you send me (ax89063.so) and add the option to use it in the code…

Ciao,
Michele

Unfortunately, I can not compile because I'ḿ to stupid to do this :-) and I have no experience in OpenBSD too :-/

thanks

mdima

@Cino:

great work mdima! Now I need to get bigger display. Using a 20x2 right now but its built into the case I'm using.

Thanks a lot! Hope to get more users and feedback in order to pass this work from "-dev" to the production package!

mdima

@DaHak:

Unfortunately, I can not compile because I'ḿ to stupid to do this :-) and I have no experience in OpenBSD too :-/
thanks

come on, then I was stupid too till the last month, because I never did it before… :D also, I don't have that vm anymore... and, just to demonstrate how few experience I have, it is FreeBSD, not OpenBSD! (hope I did not hurt anyone with that).

anyway, I hope someone that reads this message after the loud laugh, maybe can get a compiled version... if not I will recreate the vm and try do to it...

fireman039

@mdima:

@fireman039:

With the led's we can report the statut of Wan and Lan, 1 led can de assigned to load of the system (ON if load = xx) and one for CPU= xx
This led can be used to act as an "alarm" report status.
Regards

yes, I agree!
but the number of NICs can really vary, belive me… I would use:

a led for nics status (if one nic is unplugged gets red, if it's plugged gets green)

a led for carp status (off=no carp, green=at least one ip in master, red=at least one ip in backup)

a led for cpu (green < 50%, orange >50 && <70, red >70%)

a led for what?

-a led for DynDns status is possible ?

marcelloc

-a led for DynDns status is possible ?

A led for all services running ok isn't better?

mdima

@marcelloc:

-a led for DynDns status is possible ?

A led for all services running ok isn't better?

could be… as more "general" we stay, as better it is...

the funny thing is that I don't have any led on my panels, so it will be a mess to develop/debug... :D

mdima

Ah, one thing.

Yesterday I solved a problem that was dragging since a lot of time. Now when you change the program's settings or reinstall the package it is not necessary anymore to make sure the lcdproc service is stopped.
In this case the service is stopped and eventually restarted.

I invite all the people using lcdproc-dev to reinstall the package (I didn't create a new version, I will do it when there will be something more to update).

Thanks,
Michele

fireman039

@mdima:

@marcelloc:

-a led for DynDns status is possible ?

A led for all services running ok isn't better?

could be… as more "general" we stay, as better it is...

the funny thing is that I don't have any led on my panels, so it will be a mess to develop/debug... :D

Ok, you are right, the status of gateway could be be better ?
and I understand it's not easy develo with display with no led.

Another request 8)
It's possible to add an option to turn OFF the backlight ? (autotimer) and should be ON if one key of LCD is pressed ?

Regards

mdima

@fireman039:

Ok, you are right, the status of gateway could be be better ?
and I understand it's not easy develo with display with no led.

yes… today is my last day before my "winter break", I will work on it on my return in January. Another funny thing is that the update to 2.0.1 was released today, also this will wait for my return! :D

@fireman039:

Another request 8)
It's possible to add an option to turn OFF the backlight ? (autotimer) and should be ON if one key of LCD is pressed ?

AFAIK it's not possible… it is possible to turn off the backlight, but not to set a "stand-by" mode...

fireman039

The Winter break is only in two days Grrrrr:' >:(

I do the update 2.01 few minutes ago….

For backlight, it's not possible to send "a command" when we press a key ? to turn backlight on :'(

mdima

@fireman039:

The Winter break is only in two days Grrrrr:' >:(
I do the update 2.01 few minutes ago….
For backlight, it's not possible to send "a command" when we press a key ? :'(

AFAIK unfortunately not… I was double-checking the documentation:
http://lcdproc.sourceforge.net/docs/lcdproc-0-5-5-user.html#server-section

jpsb

Cool update!

Works fine with my U204FB-A1 - from http://www.lcdmodkit.com

Driver -USB2LCD
Controller - HD44780

Thanks for a great update

JPSB

–------------------------------------
PFSense 2.0.1
alix2d13
4Gb CF-card
MiniPCI vpn1411 encryption accelerator
U204FB-A1 20x4 Display
19'' DualRack System 1U

PFsense 2.0.1
Asus Hummibird AtomD525
4Gb Ram
250Gb HD
U204FB-A1 20x4 Display
19" Rack 1.5U

mdima

@jpsb:

Cool update!
Works fine with my U204FB-A1 - from http://www.lcdmodkit.com
Driver -USB2LCD
Controller - HD44780
Thanks for a great update

Hi JPSB, you are welcome, thank you for reporting us!

Only one thing I don't understand: are you using the driver "HD44780" in the package setup page or you have installed the driver "usb2lcd" by yourself?

Thanks,
Michele

jpsb

Hi

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.

JPSB

joe_cowboy

Not trying to go off toppic but if anybody wants to try this tweak for the LCDproc setup.

Added: com port speed select, brightness and contrast. Also made it to where you can type default in the field or leave it blank for contrast and brightness to set to default values
Fixed: com1 to /dev/cuau0 and com2 to /dev/cuau1

Also, not all drivers support brightness contrast so will be skipped if not supported. Same with com speed.

put the files lcdproc.inc.txt and lcdproc.xml.txt into the pkg directory:
/usr/local/pkg/

Remove the .txt extension before putting into directory.

Let me know if you want it tweaked…

lcdproc.inc.txt
lcdproc.xml.txt

treffnix

Nice work.

but i have some trouble with the [pyramid] driver.

on pfsense 1.23 it works fine. so i was sure that the display was ok.

i got the follow erros in the system log:

Dec 30 12:37:27 LCDd: LCDd version 0.5.4 starting
Dec 30 12:37:27 LCDd: Using Configuration File: /usr/local/etc/LCDd.conf
Dec 30 12:37:27 LCDd: Listening for queries on 127.0.0.1:13666
Dec 30 12:37:27 LCDd: pyramid: reading TTY failed: Inappropriate ioctl for device
Dec 30 12:37:27 LCDd: Driver [pyramid] init failed, return code -1
Dec 30 12:37:27 LCDd: Could not load driver pyramid
Dec 30 12:37:27 LCDd: There is no output driver
Dec 30 12:37:27 LCDd: Critical error while initializing, abort.

someone knows a idea?