Driver added to LCDProc package for Nexcom devices [$100]

eri-- · May 13, 2009, 4:37 PM

You need to tell it the device it has to read/write.
Usually you do with teh lcdproc package of pfsense and you have to modify the package, if you have an usb device, to list the usbdevices.

netmethods · Jun 4, 2009, 9:19 PM

I've been working with Nexcom to get this working and they provided me with a modified version of LCDProc. I was able to get LCDProc to run in 1.2.2 Dev, but it will only display the LCDProc server info and I don't know how to connect it to pfSense to manage it or display any stats.

Below are links to the version of LCDProc Nexcom sent me as well as a picture of the LCD after we got the LCDProc server running.

http://www.net-methods.com/download$/nexcom-lcdproc.zip
http://www.net-methods.com/download$/nexcom1.zip

Here is the additional notes they sent:

./configure –enable-drivers=nexcom
make
Then open the LCDd.conf and change
Driver=nexcom
driverpath =/usr/local/lib/lcdproc/ (<- the folder stored lcd driver)
make install
reboot

run server = LCDd
run client (dispaly) =lcdproc + parameter.

Then they also asked that we make sure we have this settings:

Can you make sure that the LPT port resource with command “dmesg | grep ppc0?
with Nexcom default LPT IO =378, you have to check it before install.

For our test condition = FreeBSD 7.0 with BIOS 007, and attached the .conf file which mode from this test to you.

What will it take (time/money) to get this version of LCDProc working in pfSense? I would like to be able to configure the LCD/LCM within pfSense so that I do not need to use the Dev versions of pfSense.

Thanks,

Jason

Guest · Jun 4, 2009, 11:01 PM

Any idea if they're going to submit their changes to the LCDProc software maintainers? Otherwise the usefulness of this will be somewhat limited as new versions of LCDProc won't have any support for this device.

Kudos to you for taking all this effort! I hope it works out.

netmethods · Jun 5, 2009, 7:23 AM

Is this something I can submit? They probably don't care about it, but I am more than willing to do so. They are more than willing to help as much as they can. I had to pull some teeth at nexcom, but they have been very helpful overall.

If you can point me in the right direction, I'll do what I can!

Guest · Jun 5, 2009, 2:02 PM

I could contact the maintainer for the actual LCDproc software and give them any patches they have or find out what their submission process is. If you can get the code incorporated from there, then everyone wins, not just pfSense.

netmethods · Jun 5, 2009, 2:35 PM

I emailed Nexcom and asked them for any coding they did for this. As soon as I hear back, I'll post a link to it for you to download!

In the mean time, the data in this zip file is not enough?
http://www.net-methods.com/download$/nexcom-lcdproc.zip

Thanks!

netmethods · Jun 5, 2009, 4:08 PM

To add to my last post, I do have the FreeBSD drivers for the LCD. Not sure if it will help or not at this point…

netmethods · Jun 7, 2009, 8:26 PM

I spoke with Nexcom and this is what they told me:

We only have had modified the driver for Nexcom LCD, you may found the source in
\lcdproc-nexcom0.5.3.tar\lcdproc-nexcom0.5.3\lcdproc-0.5.3\server\drivers\nexcom_lcm.

lcdproc-nexcom0.5.3.tar can be found in this zip file:
http://www.net-methods.com/download$/nexcom-lcdproc.zip

Please let me know if this is enough or if you need anything else.

Thanks!

netmethods · Jun 10, 2009, 10:51 PM

anyone now how I can move forward on this?

thanks!

netmethods · Jul 1, 2009, 4:50 PM

This issue has been resolved, Commercial support got the driver to work correctly.