LCDproc development and user support list

Text archives Help


[Lcdproc] lcdproc v0.5.3 - ConnectionType=ftdi not being recognized


Chronological Thread 
  • From: santanu at hep.phy.cam.ac.uk (Santanu Das)
  • Subject: [Lcdproc] lcdproc v0.5.3 - ConnectionType=ftdi not being recognized
  • Date: Thu, 21 Oct 2010 10:49:23 +0100

Hi Markus,

Many thanks for replying. I almost started giving up on my hope that
it'll work on Linux someday; I posted my problem a few other forums, no
one replied so far.

It's a Moneual 320B case
(http://www.moneual.com/index.php?option=com_content&view=article&id=105&Itemid=90),

which comes with a FTDI basedVL System VFD/IR panel. This is exactly the
one described here:


http://www.missingremote.com/index.php?option=com_content&task=view&id=4948&Itemid=1&limit=1&limitstart=3

The panel is connected via USB. I'm all new in the IR/VFD business (IR
part is working by the way) so, I'm giving you as much as info I
possibly can to get you a better picture.
This is all my USB devices:

root at htpc:~# lsusb
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 005: ID 050d:016a Belkin Components Bluetooth Mini Dongle
Bus 006 Device 004: ID 0a5c:4503 Broadcom Corp.
Bus 006 Device 003: ID 0a5c:4502 Broadcom Corp.
Bus 006 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub
(part of BCM2046 Bluetooth)
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0403:6001 Future Technology Devices International,
Ltd FT232 USB-Serial (UART) IC
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 05e3:0722 Genesys Logic, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub



The one is listed as "Bus 003 Device 002" is the one I believe. and
it's listed here as well:

root at htpc:~# ls -l /dev/serial/by-id/
total 0
lrwxrwxrwx 1 root root 13 2010-10-21 10:07
usb-FTDI_FT232R_USB_UART_A600dyfH-if00-port0 -> ../../ttyUSB0

and this is in the dmesg for FTDI:

root at htpc:~# dmesg | grep -i ftdi
[ 13.246151] USB Serial support registered for FTDI USB Serial Device
[ 13.246232] ftdi_sio 3-1:1.0: FTDI USB Serial Device converter detected
[ 13.248007] usb 3-1: FTDI USB Serial Device converter now attached to
ttyUSB0
[ 13.248072] usbcore: registered new interface driver ftdi_sio
[ 13.248074] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver


Right after seding my mail to the list, I un-installed the apt-get
installed lcdproc and complied from the source this way:

# cd lcdproc-0.5.3
# aclocal&& autoconf&& automake
# ./configure --enable-drivers=hd44780
# make
# make install


and here is my LCDd.conf file, which is in use at the moment:

# cat /usr/local/etc/LCDd.conf
[server]
Driver=hd44780
Bind=127.0.0.1
Port=13666
WaitTime=5
User=nobody
ServerScreen=no
DriverPath=/usr/local/lib/lcdproc/

GoodBye="Thanks for using"
GoodBye=" LCDproc!"

ToggleRotateKey=Enter
PrevScreenKey=Left
NextScreenKey=Right

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

[hd44780]
ConnectionType=ftdi
Device=/dev/ttyUSB0
Speed=57600
Keypad=yes
Contrast=0
Backlight=no
OutputPort=no
Size=14x1
Charmap=hd44780_default
DelayBus=true

KeyMatrix_4_1=Enter
KeyMatrix_4_2=Up
KeyMatrix_4_3=Down
KeyMatrix_4_4=Escape

HaveFans=n
TemperatureScale=f
FanOn=120
FanOff=110
FanMinSpeed=140
FanOn=120
FanOff=110
FanMinSpeed=140



Now, if I run LCDd with '-r 5', this is what I get:

root at htpc:/usr/local/etc# date&& LCDd -f -r 5 -s 0
Thu Oct 21 10:47:05 BST 2010
LCDd version 0.5.3 starting
Built on Oct 21 2010, protocol version 0.3, API version 0.5
Using Configuration File: /usr/local/etc/LCDd.conf
Set report level to 5, output to stderr
LCDd 0.5.3, LCDproc Protocol 0.3
Part of the LCDproc suite
Copyright (C) 1998-2009 William Ferrell, Scott Scriven
and many other contributors

This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public Licenseroot at
htpc:/usr/local/etc# date&& LCDd -f -r 5 -s 0
Thu Oct 21 10:47:05 BST 2010
LCDd version 0.5.3 starting
Built on Oct 21 2010, protocol version 0.3, API version 0.5
Using Configuration File: /usr/local/etc/LCDd.conf
Set report level to 5, output to stderr
LCDd 0.5.3, LCDproc Protocol 0.3
Part of the LCDproc suite
Copyright (C) 1998-2009 William Ferrell, Scott Scriven
and many other contributors

This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software Foundation,
Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.

Server running in foreground
Listening for queries on 127.0.0.1:13666
screenlist_init()
driver_load(name="hd44780", filename="/usr/local/lib/lcdproc/hd44780.so")
hd44780: unknown ConnectionType: ftdi
Driver [hd44780] init failed, return code -1
Module /usr/local/lib/lcdproc/hd44780.so could not be loaded
Could not load driver hd44780
There is no output driver
Critical error while initializing, abort.

along with this program; if not, write to the Free Software Foundation,
Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.

Server running in foreground
Listening for queries on 127.0.0.1:13666
screenlist_init()
driver_load(name="hd44780", filename="/usr/local/lib/lcdproc/hd44780.so")
hd44780: unknown ConnectionType: ftdi
Driver [hd44780] init failed, return code -1
Module /usr/local/lib/lcdproc/hd44780.so could not be loaded
Could not load driver hd44780
There is no output driver
Critical error while initializing, abort.




Sorry, for this very long writing, but I didn't actually know what
exactly to give you. Hope, you are seeing what I'm missing.

Cheers,
Santanu



On 21/10/10 06:31, Markus Dolze wrote:
> On 21.10.2010 02:59, Santanu Das wrote:
>> Hi there,
>>
>> I just apt-get [re]installed lcdproc, which essentially installed
>> v0.5.3 but if I use
>> */ConnectionType=ftdi/* for *hd44780*, I get unknown connection error:
>>
>> Server running in foreground
>> Listening for queries on 127.0.0.1:13666
>> screenlist_init()
>> driver_load(name="hd44780", filename="/usr/lib/lcdproc/hd44780.so")
>> hd44780: unknown ConnectionType: ftdi
>> Driver [hd44780] init failed, return code -1
>> Module /usr/lib/lcdproc/hd44780.so could not be loaded
>> Could not load driver hd44780
>> There is no output driver
>> Critical error while initializing, abort.
>> Does any one know what am I missing? Thanks in advance for your help.
>>
>> Cheers,
>> Santanu
>
> Hello Santau,
>
> first of all: Can you tell us how the Mplay VFD is connected to your
> computer? What type of cable is it? Does this device appear in your
> computers config? If it is connected by USB you should see some USB
> device in your system config.
>
> Related to your second message: running LCDd with '-r 5' will produce
> a lot of debug output. In your case LCDd did start up and you saw the
> debug output for the default server screen.
>
> The FTDI connection type requires the use of libusb and libftdi.
> Lcdproc must be compiled with these installed to be able to make use
> of them. As I don't know how the Ubuntu package makers configured
> lcdproc, I suggest you compile lcdproc from source yourself.
>
> Regards,
> Markus
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.omnipotent.net/pipermail/lcdproc/attachments/20101021/8c661d5d/attachment-0001.htm>




Archive powered by MHonArc 2.6.18.

Top of page