LCDProc 0.5.4-dev

stephenw10

I think in fact we already have that somewhere I remember reading the code.
A quick search shows that there was some discussion on this on the pfSense mailing list:
http://www.mail-archive.com/support@pfsense.com/msg20822.html

I think there is a good chance that this could be persuaded to work with lcdproc. However currently there are a number of drivers and options that are not selectable via the package. In order to test them you would have to stop the lcdproc service and then edit /usr/local/etc/LCDd.conf appropriately. Each time you restart or sync the packge this will be overwritten but it can easily be incorporated if you find a working combination.

Currently if you select HD44780 as the driver it automatically selects USB2LCD as the connection type, which is obviously not right for you.
See: http://lcdproc.sourceforge.net/docs/current-user.html#hd44780-howto

Edit: Looking at the data sheet for the sc2002d it has a parallel interface so it's likely you have some serial-parallel converter somewhere.

Steve

ezyclie

This thread brought me to this thread:
http://forum.pfsense.org/index.php/topic,49481.0.html

I am getting issue with my SureElec LCD with this error:

May 16 23:40:15 	LCDd: LCDd version 0.5.5 starting
May 16 23:40:15 	LCDd: Using Configuration File: /usr/local/etc/LCDd.conf
May 16 23:40:15 	LCDd: Listening for queries on 127.0.0.1:13666
May 16 23:40:15 	LCDd: SureElec: failed to configure port (Inappropriate ioctl for device)
May 16 23:40:15 	LCDd: Driver [SureElec] init failed, return code -1
May 16 23:40:15 	LCDd: Could not load driver SureElec
May 16 23:40:15 	LCDd: There is no output driver
May 16 23:40:15 	LCDd: Critical error while initializing, abort.
May 16 23:40:16 	php: lcdproc: Start client procedure. Error counter: (0)

and this config:

[server]
DriverPath=/usr/local/lib/lcdproc/
Driver=SureElec
Bind=127.0.0.1
Port=13666
ReportLevel=3
ReportToSyslog=yes
User=nobody
Foreground=no
ServerScreen=no
GoodBye="Thanks for using"
GoodBye="    pfSense     "
WaitTime=5
ToggleRotateKey=Enter
PrevScreenKey=Left
NextScreenKey=Right
ScrollUpKey=Up
ScrollDownKey=Down
[menu]
MenuKey=Escape
EnterKey=Enter
UpKey=Up
DownKey=Down
[SureElec]
driverpath =/usr/local/lib/lcdproc/
Device=/dev/ugen0.2
Size=20x4
Edition=3
Contrast=200
Brightness=480

ezyclie

May 30 00:26:59 	LCDd: Client on socket 13 disconnected
May 30 00:26:59 	LCDd: sock_send: socket write error
May 30 00:27:00 	LCDd: Server shutting down on SIGTERM
May 30 00:27:01 	LCDd: LCDd version 0.5.5 starting
May 30 00:27:01 	LCDd: Using Configuration File: /usr/local/etc/LCDd.conf
May 30 00:27:01 	LCDd: Listening for queries on 127.0.0.1:13666

I keeps getting the error above every 5-15 minutes and my LCD shows "LCDproc Server" only… it stops to show my screens after that error.

Brak

I've been working on hardware that is the bigger version of the Watchguard Firebox LCDs (Lanner LCM, etc). I set lcdproc-dev to 20x2 mode, but the screens appear to run in 16x4 mode even tho the options screen and "Next/Prev" popups appear in the extra eight "blank" spots at times. Are the SDECLCDs screens hard-coded at 16x4? I've also had to edit lcdproc.inc to change the button mapping, (Up and Down just need reversed) this should solve the Firebox X Core-e issue? Can we get a GUI to modify key mappings in LCD-proc dev?

Also, how would one go about converting the SDECLCD(x86 ONLY) to be x86-64bit capable? I would like to get these LCM drivers fully working, but I'm a total lame when it comes to freebsd C programming. I have hardware that needs 64bit OS to be fully utilized, and would love for lcdproc to be running on them.

Also, my menu system isn't completely dead, it's just a total hack-job since it takes some lcdproc-dev file edits to get LCDExec starting and stopping properly, but I've made progress. The menu system is seriously over-rated, i get messages constantly from people wanting to get the scripts, but I fear that they aren't ready for anyone except those who I know what hardware/configurations they use. Last thing we need is the Restore/Backup/ResetToDefault menu bricking boxes. ::)

stephenw10

The X-Core-e buttons should be correctly mapped in the current package.
Fmertz has just updated the driver to include detection on the box type and mapping for the XTM5 but I haven't had a chance to test it yet.

Steve

acro-ii

OK All, question for the minds. I have another box I am working on. Ti has an Intel D2500CCE motherboard and a CrystalFontz CFA633-YYB-KS LCD. The Intel serial header uses what Crystal Fontz calls an "alternate rs-232 pin assignment". I loaded windows 7 on the box, and used Crystal Fontz's utility, and the LCD is working correctly on Com 2 @ 19200.

When I load pfSense 2.01 and LCDproc-dev, I CANNOT get the LCD to function. I am picking com 2 alternate /dev/cuau1. I have also tried just com 2. Any helpful ideas? Maybe it is because of the "alternate pinout"???

The documentation shows standard as pin 2 Rx, pin 3 Tx, and pin 5 ground. The alternate, that I am using is pin 2 Tx, pin 3 ground, and pin 6 Rx.

I don't know what to try next.
SOMEBODY HELP!
Thanks

fmertz

@Brak:

Are the SDECLCDs screens hard-coded at 16x4?

I've also had to edit lcdproc.inc to change the button mapping, (Up and Down just need reversed) this should solve the Firebox X Core-e issue?

Also, how would one go about converting the SDECLCD(x86 ONLY) to be x86-64bit capable?

The driver is hard coded for 20x2. This is the max the driver will allow, and will clip anything outside of this window.

Not sure what is up with the buttons. AFAIK, the code supports all versions of the Fireboxes (with the XTM pending release). With the exception of the XTM, all key codes are unique, and all key codes reported on this forum have been incorporated in the code.

A 64bit binary of the driver is here (rename it to sdeclcd.so):

https://github.com/downloads/fmertz/sdeclcd/sdeclcd64.so

Do you have a 64bit version of LCDd already? You can check with "file LCDd".

Also, does this Lanner box have the same LEDs as the Fireboxes? The code I am working on incorporates control for the LEDs, based on the specifics reported on this forum, i.e. ICH model, specific GPIO pin, etc.

Brak

@fmertz:

@Brak:

Are the SDECLCDs screens hard-coded at 16x4?

I've also had to edit lcdproc.inc to change the button mapping, (Up and Down just need reversed) this should solve the Firebox X Core-e issue?

Also, how would one go about converting the SDECLCD(x86 ONLY) to be x86-64bit capable?

The driver is hard coded for 20x2. This is the max the driver will allow, and will clip anything outside of this window.

Not sure what is up with the buttons. AFAIK, the code supports all versions of the Fireboxes (with the XTM pending release). With the exception of the XTM, all key codes are unique, and all key codes reported on this forum have been incorporated in the code.

A 64bit binary of the driver is here (rename it to sdeclcd.so):

https://github.com/downloads/fmertz/sdeclcd/sdeclcd64.so

Do you have a 64bit version of LCDd already? You can check with "file LCDd".

Also, does this Lanner box have the same LEDs as the Fireboxes? The code I am working on incorporates control for the LEDs, based on the specifics reported on this forum, i.e. ICH model, specific GPIO pin, etc.

I will try this as soon as I get home.

As for the LED, the unit does have one. that said, I used the writeio commands that Stephen made, and it locked up the NICs and crashed the box, clearly a different GPIO then?

fmertz

@Brak:

As for the LED, the unit does have one. that said, I used the writeio commands that Stephen made, and it locked up the NICs and crashed the box, clearly a different GPIO then?

Well, the exact way the GPIO is interfaced depends on what model Intel Southbridge (ICH) you have (the port numbers vary). Even then, each Firebox series has a specific hard wiring of LED to GPIO pins. For all we know, Lanner models could be wired differently, or even have a different ICH altogether…

When you say 1 LED, do you mean 1 location (with maybe 2 colors) or actually just 1 LED? Fireboxes have 1 location, but it can light up red or green.

The latest (test) code (32bit) is here, with all LED and buttons coded in (source not released, yet):

https://github.com/downloads/fmertz/sdeclcd/sdeclcd.so

Brak

@fmertz:

@Brak:

As for the LED, the unit does have one. that said, I used the writeio commands that Stephen made, and it locked up the NICs and crashed the box, clearly a different GPIO then?

Well, the exact way the GPIO is interfaced depends on what model Intel Southbridge (ICH) you have (the port numbers vary). Even then, each Firebox series has a specific hard wiring of LED to GPIO pins. For all we know, Lanner models could be wired differently, or even have a different ICH altogether…

When you say 1 LED, do you mean 1 location (with maybe 2 colors) or actually just 1 LED? Fireboxes have 1 location, but it can light up red or green.

The latest (test) code (32bit) is here, with all LED and buttons coded in (source not released, yet):

https://github.com/downloads/fmertz/sdeclcd/sdeclcd.so

Yes, I meant one location with 2 LEDs like the Firebox. I have the sample source code from Lanner themselves that powers the LEDs apparently, do you want me to send you them so you can reverse engineer it?

Building a 64bit lanner unit as I type this…

Brak

That 64bit driver appears to work well, awesome!

Just testing things right now, only issue I see is that it's still 16x4 screens instead of 20x2, but I know you didn't change any code

fmertz

@Brak:

Yes, I meant one location with 2 LEDs like the Firebox. I have the sample source code from Lanner themselves that powers the LEDs apparently, do you want me to send you them so you can reverse engineer it?

Sure, I'll have a look.

fmertz

@Brak:

That 64bit driver appears to work well, awesome!

Just testing things right now, only issue I see is that it's still 16x4 screens instead of 20x2, but I know you didn't change any code

Good news!

When you say 16 instead of 20, do you mean that it uses the first 16 characters out of 20, or that each character is wider so that only 16 show on the whole width? If 16 out of 20, maybe lcdproc (the client) thinks this is only 16 wide, somehow. You can test with the binary lcdproc that comes with the project (even running on another machine) to be sure…

Brak

@fmertz:

@Brak:

That 64bit driver appears to work well, awesome!

Just testing things right now, only issue I see is that it's still 16x4 screens instead of 20x2, but I know you didn't change any code

Good news!

When you say 16 instead of 20, do you mean that it uses the first 16 characters out of 20, or that each character is wider so that only 16 show on the whole width? If 16 out of 20, maybe lcdproc (the client) thinks this is only 16 wide, somehow. You can test with the binary lcdproc that comes with the project (even running on another machine) to be sure…

Code from Lanner (includes LED, LCM, the software reset button (a pin hole on the units), and the physical LAN bypass feature):

http://mc.zsnnet.org/hosted/LannerLCMsamples.zip

As for what I mean on the character stuff, the LCD is 20x2, but the lcdproc status screens only use it like it's a 16x2 LCD. Something is writing to the 8 extra characters tho, since I sometimes see "Next" or "Prev" pop up in the extra spaces when i press a key button. LCDexec with my menu system also seems to be limited to writing to a 16x2. The Lanner-LCM driver you compiled for me a while back does use the full 20x2. Maybe there is some left over hard-coded 16x2 left in SDECLCD?

fmertz

@Brak:

Code from Lanner (includes LED, LCM, the software reset button (a pin hole on the units), and the physical LAN bypass feature):

http://mc.zsnnet.org/hosted/LannerLCMsamples.zip

Does this work (as root)?

https://github.com/downloads/fmertz/sdeclcd/a.out

It should cycle the LEDs (Green, Yellow, then Dark as per the code). I ported the code to FreeBSD (seems to be DOS and Linux initially).

In short, it looks like the LEDs are interfaces off of the SuperIO. The code mentions the board number. Is it this?

http://www.scribd.com/doc/39794230/Spec-FW-7565

Looks like there is an ICH8 Southbridge, and a Winbond W83627THG SuperIO…

Brak

I'll have to try it when I get home from work, but yeah, that is the proper board/unit number I believe.

I had no clue they were board specific, what lanner sent me seemed generic. I guess there really won't be an easy way of getting the LEDs working for all models until we get the samples from everything - if it's even worth it.

Why can't these LEDs be easy and be part of the LCD/button stuff. :-\

fmertz

@Brak:

Why can't these LEDs be easy and be part of the LCD/button stuff. :-\

That is what I am working on. This way, at least, the interface to the LEDs is captured in code as part of the driver. Now, whether we will have a client to turn them on/off is another matter…

acro-ii

Nobody has an idea about my cfa633 and the alternate rs232 pinout issue???

stephenw10

It seems very odd that it isn't wired in a standard manner. But if that is the case it would be a hardware only solution. I don't believe you can change the serial port pins in software (like you can with a parallel connected display).
If it is working under windows then it should be possible to have it function under lcdproc - with the correct driver. ;)

Steve

robi

Is there any chance to have the glcdlib driver also included with the LCDproc package?

It would allow us to use this very good priced graphic LCD screen with pfSense. This is a small digital photo frame which has an open alternative firmware called dpf-ax, allowing it to be used as graphical USB display. LCDProc's glcdlib driver actually translates the textual info in graphical format for displays like this.

linkdelight1.jpg_thumb