NmediaPC Pro LCD

Good evening folks. I am new to this type of software but I was able to easily deploy it with little trouble using a used ASrock z77 extreme 4, i5 cpu 4 gig ram etc etc. I have all of this installed in a Norco 2U rack chassis and I happen to have an NmediaPC Pro LCD laying around and I can't help but think that this would be an awesome addition if it could be used to display rolling statistics. Here is the link for the Pro LCD.

http://www.nmediapc.com/prolcd.htm

What I would like to know is if it would be possible to have this thing made to work with pfSense. If so, would it be possible for someone to actually make a upgrade package. I don't really have much experience with Linux outside of the GUI, let alone installing drivers. On the manufacturers website is a listing for some Linux help but I don't really know what to do with it. Please Help..lol

jaspras

Theres a package "LCDproc-dev" in System -> Packages -> Available Packages"

but i dont know if it will work for you

stephenw10

This page implies there's support for it in lcdproc or at least some modified form:
https://www.mythtv.org/wiki/Nmedia_pro-lcd
Looks like you need the lis driver.

Steve

So, I have been messing around with the LCDproc server tab inside pfSense and I am not sure what I should be setting this to. It looks like there is three drop down menus that I need to select from: Com Port, Driver, and connection type. From these three drop down, I have selected a lot of different combinations and I am stumped. Firstly, is there a way to find out which com port this this is plugged into based on the pfSence port naming convention? Second, looking at the manufactures link, I see that just about all drivers included in the list for LIS driver is listed in the LCDproc so which one do I use? Lastly, connection type, I have no idea with this one what to select. I have attached a series of shots depicting the drop down menu options.

ProLCD.png_thumb

stephenw10

Ok, so USB connected comports have a capital U in the name (as indicated) so it could be either. Do you have any other USB devices connected? If niot then choose cuaU0. You can look in /dev to check.
You want the lis driver which isn't in the package. You might make it work by selecting driver type: HD4478 and connection type: LIS2. Don't really know though, more research needed.

Steve

Are you sure the LIS driver is not in there already? In the driver drop down list is most of the things mentioned in the driver list direct quoted from here: https://www.mythtv.org/wiki/Nmedia_pro-lcd
What are all these things mentioned below

The following drivers are supported:

# bayrad, CFontz, CFontz633, CFontzPacket, curses, CwLnx, ea65,
# EyeboxOne, g15, glcdlib, glk, hd44780, icp_a106, imon, imonlcd, IOWarrior,
# irman, joy, lb216, lcdm001, lcterm, lirc, lis, MD8800, ms6931, mtc_s16209x,
# MtxOrb, mx5000, NoritakeVFD, picolcd, pyramid, sed1330, sed1520, serialPOS,
# serialVFD, shuttleVFD, sli, stv5730, svga, t6963, text, tyan, ula200,
# xosd
Driver=lis

Anyhow, I did a factory default wipe on pfSense and installed only the LCD_Proc and not the DEV version. It has given me few options to mess with and a larger variation of drivers to play with. I tried quite a few in this one but still am not having any luck. I should also mention that this screen connects to a 9 pin header on the motherboard and not an actual USB port. Not sure if that matters or makes a difference as to which com port to use.

Untitled.png_thumb

stephenw10

It's not there on my box in /usr/pbi/lcdproc-amd64/local/lib/lcdproc where all the other drivers are.
It's not in the FreeBSD ports package either. Looks like it doesn't get compiled by default. There could be reason for that, like it's been replaced by lis2.

Steve

is it possible to add this driver in?

stephenw10

If you can get hold of the driver module, lis.so, from the appropriate FreeBSD version you can just copy it into pfSense. However since it isn't in the FreeBSD package either you'll have to compile it.

Steve

And this reaches the extent of my Linux knowledge. No really sure how to add or compile anything in Linux.

stephenw10

Before anyone else points it out; pfSense is built on FreeBSD, FreeBSD in not Linux. ;)

I have done this but it was a while ago. There are instructions for doing so at the lcpproc site but as I recall it was slightly tricky.

Steve

Outside of windows, I'm not very smart on different OS's. Would you mind pointing out what you did? How does BSD differ from Linux? Would you mind walking me through the setup?

stephenw10

To be honest it's such a long time ago that I'd have research it again. Also the compile box I was using at the time is now dead so I don't even have that to look at. If I have a chance I'll look into it. Wasn't that tricky as I recall.

Steve

I have been browsing there the last day or so. I appreciate the advice on all of this btw way. In reading the instructions, the terminology seems to be a point of toughness for me as mind expects troubleshooting steps that would apply to windows..lol I really don't have much experience in using UNIX based code i.e Linux and BSD. I'm definitely going to have to pick your brain while using these instructions. Just to be clear and that i'm using the correct instructions

http://lcdproc.sourceforge.net/docs/lcdproc-0-5-5-user.html

SO I was looking over this again today and I am puzzled by the labeling and began to wonder if the reason why I am having difficulties is if the port my LCD is connected to is not registered in LCDproc. So I took a photo to show this for clarification. The photo from the black screen shows where the PC says it is and the other image shows the ports recognized by LCDproc.

20150325_170533.jpg_thumb

Untitled.png_thumb

stephenw10

Interesting uftdi0. Does it create a new com port in /dev though? Compare the listing in /dev before and after you connect it.

Steve

Can you explain how to do that from pfSense? All info I have found about this display points to it being an FTDI device.

stephenw10

At the command line (console or via SSH) run:

ls /dev

Then connect the display and run that again. Do you see a new device listed?

Steve

it comes up as ugen1.3. I set the port to this and tried several driver and connection type configurations and still not working but I think now; we are finally narrowing the issue down knowing the correct port. It might be just a simple selection problem now. I'm curious why LIS is listed under connection type and and not under driver..lol

Is there any reason that you can think of as to why the service for LCDproc will not start? Under status\services, it shows LCDproc as stopped even though it is enabled.