Help identify lcd display on Smoothwall SWG700 [Edit: Portwell EZIO]

fmertz · Apr 30, 2017, 3:29 AM

OK, I attached a 64bit FreeBSD 10 driver. Let me know.

stephenw10 · Apr 30, 2017, 11:02 AM

It works! :D ….mostly.

The display looks correct.

The driver initialises the display correctly from power off.

The keypad doesn't work.

I should note I've never seen the keypad work on this hardware, the original OS was not bootable. It may be broken for all I know though it looks in good condition.

Not sure how to test that directly....

Steve

My LCDd.conf for reference:

[server]
DriverPath=/usr/local/lib/lcdproc/
Driver=hd44780
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

[menu]
MenuKey=Escape
EnterKey=Enter
UpKey=Up
DownKey=Down

[hd44780]
driverpath=/usr/local/lib/lcdproc/
ConnectionType=ezio
Device=/dev/cuau1
Keypad=yes
Size=16x2
KeyMatrix_4_1=Enter
KeyMatrix_4_2=Up
KeyMatrix_4_3=Down
KeyMatrix_4_4=Escape
Speed=2400

fmertz · Apr 30, 2017, 1:45 PM

You can test this keypad "manually".

Create a background process to read from the device.```
cat < /dev/cuau1 > nil.dat &


Then, send xFEx06 to the device.```
printf "\376\006" > /dev/cuau1

The keypad status comes back in hex: xFDx4n. No key pressed is x4F. F is binary 1111. Each key pressed makes a bit go to 0, so:

Escape is x4E
Up is x4D
Enter is x4B
Down is x47

So, press one of the keys, then send the command xFEx06. Press another key, then send the sequence. Once done with all keys, check nil.dat with```
od -x nil.dat

stephenw10 · Apr 30, 2017, 2:09 PM

Hmm, nothing coming back at all. I would expect to get back 0x4f every time if the keypad was disconnected for example.

Port somehow open write only?

stephenw10 · Apr 30, 2017, 2:17 PM

Hmm set the port speed manually and initialised the display…. still nothing coming back

Sending

printf "\376\010" > /dev/cuau1

Does correctly clear the display so commands are reaching the module as expected.

fmertz · Apr 30, 2017, 2:24 PM

The spec is here:

http://drivers.portwell.com/CA_Manual/EZIO/EZIO-FINAL.PDF

There is a picture of that ribbon cable for the keypad.

Could also be that the serial cable is somehow not connected right.

stephenw10 · Apr 30, 2017, 2:35 PM

I don't believe it's a problem with the ribbon cable as I expect to see 0x4f sent even if the keypad is disconnected. It could be the serial cable…. I don't think the display sends anything else we can check that with. Hmm...

A second tester could help here.

Steve

fmertz · Apr 30, 2017, 2:38 PM

There is another thing, too. There is a "watchdog timeout" for custom characters if you do not send all 8 bitmaps. See Note 3 in the spec.

Send xFEx40. See if xFDx0E comes back…

stephenw10 · Apr 30, 2017, 5:56 PM

Nothing from that either. I'll have to pull it out when I have time and check it.

Steve

fmertz · May 1, 2017, 8:55 PM

I started a separate thread here. Hopefully we can get a tester or two.

https://forum.pfsense.org/index.php?topic=129820.0

serlogo · Aug 2, 2017, 10:09 AM

hi fmertz,
is it possible to take 2.1.5 x64 and x32 eizo 300 driver.

please save me…

stephenw10 · Aug 15, 2017, 8:47 PM

Upgrade! ;)

Really is there any reason you're still running 2.1.5?

You could compile the driver against FreeBSD 8.3 with some effort I expect.

Steve

Wuebit · Oct 4, 2017, 10:57 AM

Thanks works Perfect! ;)

x2rl · Jun 10, 2018, 11:28 AM

@stephenw10 Can you reupload than hex file please think the forum movement killed it. Thanks

stephenw10 · Jun 10, 2018, 12:52 PM

Sure here you go.

But you can use fmertz's driver directly now via lcdproc if you want.
See: https://forum.netgate.com/topic/115071/ezio-driver-for-lcdproc

Steve

pfsense.hex.txt