LCDProc 0.5.4-dev

scratchi

Hello

I have a Nexcom NSA3110 and NSA5130 both of which have the same LCD assembly. The display works great on both but I can't get the keypad to work. Are the drivers for the keypad seperate from the LCD? Has anyone gotten the keypad for the Nexcom to work? Any help would be appreciated.

Thank you

fmertz

@scratchi:

I have a Nexcom NSA3110 and NSA5130 both of which have the same LCD assembly. The display works great.

What driver/connection combination are you using? I assume this is with the lcdproc-dev package in pfSense…

mdima

scratchi,
try to change the menu section of the lcdproc.conf file using the following data:

# If you have a keypad you can assign keystrings to the keys.
 # See documentation for used terms and how to wire it.
 # For example to give directly connected key 4 the string “Enter”, use:
 # KeyDirect_4=Enter
 # For matrix keys use the X and Y coordinates of the key:
 # KeyMatrix_1_3=Enter
 KeyMatrix_4_1=Enter
 KeyMatrix_4_2=Up
 KeyMatrix_4_3=Down
 KeyMatrix_4_4=Escape

this is the only information I found on the nexcom.so driver. Unfortunately the nexcom driver is not in the official release of LCDProc, so it's hard to know what is its code and if it respects all the LCDProc directives…

Ciao,
Michele

easyhugo

@mdima:

@Brak:

Truthfully, I'm not sure. The driver is for 0.5.2, and that's what I've used it with. I didn't seem to be able to get 0.5.4-dev working with it, but I don't know enough about the package to be able to get it working.

I would assume tho it would be better to call it the "Lanner LCM" driver/port since it's neither the HD44780 spec nor the LCM-162 spec (at least the comments on the patch make it seem that way.)

well, if the driver is for 0.5.2 I don't think it will work for 0.5.4. But if someone could compile it for 0.5.4 I could integrate with the name you just told…

Ciao,
Michele

hi guys
are these good news for me and my allnet fw8888 ore not???
my eforts to intergrad these driver (lcmserver) stops very quickly

thx max

acro-ii

I really hate to bring up a topic that has been asked before, but I am going to anyway. ::)

I have a portwell NAR 5060, that has the MTB134 (aka EZIO-100) lcd in it. Is there anyone that can get this thing to work with LCDPROC? I see Mikrotek RouterOS supports it, as well as Untangle. There has to be someone who can convert it over.
Pretty please!!!

acro-ii

Here is a .pdf from portwell with all the data on the EZIO. Maybe someone could use it to make a lcdproc driver for it??????

http://www.google.com/url?sa=t&rct=j&q=portwell%20lcd%20driver&source=web&cd=9&ved=0CHAQFjAI&url=http%3A%2F%2F71.131.159.28%2FCA_Manual%2FEZIO%2FEZIO-FINAL.PDF&ei=AQ17T-3aIIWlsALsjvWLAw&usg=AFQjCNHHh2ioBfzM7w9g0CJ4q_CFI9-nFw

stephenw10

That link doesn't offer much but this does:
http://lists.omnipotent.net/pipermail/lcdproc/2004-January/008494.html :)
Looks like it was never updated for 0.5X though and didn't meet the requirements to be included in lcdproc. Would be a good place to start for someone who knows what they're doing! ;)

Steve

acro-ii

I already had the link you posted, but just found this. I thought the command functions, as well as the sample c style control program might offer some info.

gabi

I have a advantech appliance with an lcd on serial 2x16 but i do not know how to configure lcdproc
if someone can help me with this lcd
I posted an archive from their website

thanks

p.s: please delete extension .txt

lcm100_advantech.tgz.png

stephenw10

Using the .txt extension causes the file to be corrupted, use .png instead.

Steve

gabi

ok ..
now it is ok

stephenw10

The LCM-100 appears to be virtually identical to the early version EZIO/MTB-134. As such no driver exists for lcdproc 0.5X. Yet. :(

Steve

gabi

thanks….I will use it under linux
but i have another appliance fwa9106 with sample code in attach

iio_sample_code.tgz.png

defor

Perhaps I'm not searching for the right thing, but is there any way to keep the backlight on?
I'm using a firebox X-series and it works great with the new dev driver, but considering the rest of the rack never disables the backlights on the status lcd's I'd prefer to be able to read the traffic monitor at a glance, without waking it up.

stephenw10

The backlight on the firebox LCD is deliberately always on a timer. This is because at least some of the boxes have an LCD with a limited backlight life and most of these boxes have already seen thousands of hours use. There are quite a few reports of failed backlights on the x-core thread.
I'm in favour of allowing users to take the risk as long as they have the facts. The current driver does not have the option though.

Steve

defor

gotcha- even a few minutes timeout would be a nice option instead of the hard-set one, but I understand :D

Macom2007

Any news / progress on the 4 Leds of the CFA635 ?

Topper727

I have been trying to get the right setup to get my Pertelian x2040 to work

: dmesg | grep usb
usbus0: <ohci (generic)="" usb="" controller="">on ohci0
usbus0: 12Mbps Full Speed USB v1.0
ugen0.1: <(0x1166)> at usbus0
uhub0: <(0x1166) OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
Root mount waiting for: usbus0
ugen0.2: <ftdi>at usbus0
Root mount waiting for: usbus0
uftdi0: <ft245r usb="" fifo="">on usbus0
ugen0.2: <ftdi>at usbus0 (disconnected)
ugen0.2: <ftdi>at usbus0
uftdi0: <ft245r usb="" fifo="">on usbus0

I am not sure where I go wrong. I tried alot of things and searched the web for an answer.. Nothing clear yet.
All I get is
"php: lcdproc: Start client procedure. Error counter: (0)"
"php: lcdproc: Failed to connect to LCDd process Operation timed out (60)"

I would love to get this working. Any help would be so appreciated. Even a direction in way of how to setup the LCDd.conf file would help.

LCDd.conf.txt</ft245r></ftdi></ftdi></ft245r></ftdi></ohci>

Roots0

I'm having trouble with my Matrix Orbital LK202-25 V1.12

It seems to be setting some pixels to all black. And also always the first and last proceeded by a K: Have a look at the attached image:

I also get this from systemlog:
Apr 12 12:59:01 php: lcdproc: Start client procedure. Error counter: (0)
Apr 12 12:59:00 LCDd: MtxOrb: unable to read device serial number
Apr 12 12:59:00 LCDd: MtxOrb: unable to read device firmware revision
Apr 12 12:59:00 LCDd: MtxOrb: unable to read device type

phpfKgZkkAM.jpg_thumb

stephenw10

@Topper727:

I would love to get this working. Any help would be so appreciated. Even a direction in way of how to setup the LCDd.conf file would help.

Are you using the package or just configuring LCDd.conf for testing purposes? Usually the package generates the lcdd.conf file automatically.

FTDI is a usb to serial interface. To get this working you probably want to direct LCDd to use the usb connected serial port not the USB port directly.
Look in /dev/ without the USB connected. Now connect the USB and look in /dev/ again. You should see some new serial devices have appeared. A 'U' in the name implies they are USB connected.
Use serial port and whatever device appeared in the conf.

Steve

Edit: Actually there appears to be special support for that LCD in lcdproc 0.5. Set driver type to hd44780 and connection type to pertelian. Set the port to whatever new serial port you found. You will have to do this manually at the moment because the lcdproc-dev package only supports lcd2usb as a connection type currently. Also your setting will be overwritten at boot! :-\