Difference between revisions of "Futaba"
m (→User experience) |
m (→Configure mythfrontend to use the VCD: -> typo) |
||
Line 116: | Line 116: | ||
Note: MythDora 4 also errors as openSUSE 10.3 and the same solution works. Instead of adding the lines to /etc/init.d/boot.local you need to add them to /etc/init.d/rc.local - I also add /usr/local/sbin/LCDd to the bottom of rc.local to ensure it is running at startup. | Note: MythDora 4 also errors as openSUSE 10.3 and the same solution works. Instead of adding the lines to /etc/init.d/boot.local you need to add them to /etc/init.d/rc.local - I also add /usr/local/sbin/LCDd to the bottom of rc.local to ensure it is running at startup. | ||
− | ==== Configure mythfrontend to use the | + | ==== Configure mythfrontend to use the VFD ==== |
The [[mythlcdserver|mythlcdserver]] is started automatically when configured in mythfrontend. | The [[mythlcdserver|mythlcdserver]] is started automatically when configured in mythfrontend. |
Revision as of 19:51, 13 May 2008
Contents
Introduction
Futaba Corporation is recognized as a world leader in the manufacturing of flat panel Vacuum Fluorescent Displays (VFD), VFD modules, field emission displays (FED) and industrial and hobby radio control systems. The world comes into contact with Futaba products every day in applications such as:
- Electronic readouts on automotive instrumentation
- Appliance Controls
- Audio/video equipment
- Home Entertainment
- Business machines
- Point-of-sale terminals
- Industrial process controllers
- Test/measurement equipment
- Remote controls for industrial, commercial and hobby industry
Futaba dm-140gink Demo
The Futaba DM-140GINK Demo is an OEM device from Futaba.
The following machines have the DM-140GINK build in: MSI_Media_Live, Hiper HMC-2K53A, FIC Spectra....(please add)
The DM-140GINK includes is a combined device with the following functions:
- a VFD
- a Wireless Network Interface (801.11 B/G usb device Ralink chipset RT2571WF )
- Front Panel Keys
The module is a controlled by a Weltrend WT65F5 USB Micro controller.
Wireless NIC
The DM-140GINK includes a 801.11 B/G usb device Ralink chipset RT2571WF
The rt2x00 driver is included in the kernel >= 2.6.24 and support the built in WLAN but some users reported that the throughput is better using ndiswrapper.
- NDISwrapper
- Native driver (if not supported by your kernel)
Quick installation notes for Native driver
make and make install
USB subsystem must be up and running
Add "alias wlan* rt73" to modprobe.conf
Edit /etc/network/interfaces
# The wireless network interface allow-hotplug wlan0 iface wlan0 inet dhcp pre-up ifconfig wlan0 up pre-up iwconfig wlan0 essid qwerty pre-up iwconfig wlan0 channel 11 pre-up iwconfig wlan0 key xxxxxxxxxxxxxxxxxxxxxxxx pre-up ifconfig wlan0 up
Run ifup wlan0 and you should be up and running!
Note, you can only use channel 1 - 11!
VFD
The current LCDproc 0.5.2 does not have support for the dm140 in the package. Henrik Larsson created this rpm with a driver for the dm140. Henlar: Here is a LCDproc working with dm140 v0.2 have the dm140_char() fixed. It is not bug free but it works. LCDProc 0.5.2 version with Henlar dm140 driver v0.2
Quick howto:
tar xvf lcdproc-0.5.2-henlar-v0.2.tar.gz cd lcdprov-0.5.2/ ./configure --enable-drivers=dm140 make sudo make install edit /usr/local/etc/LCDd.conf
- Change the driver to dm140
- Change the driver path from server/drivers to /usr/local/lib/lcdproc
- Check so the dm140.so file is copied to the directory /usr/local/lib/lcdproc/ also. If not, copy! You will find it in ./server/drivers. Make sure you spelled --enable-drivers with a 's' at the end!
Fire it up with:
LCDd
or troubleshoot
/usr/local/sbin/LCDd -c /usr/local/sbin/LCDd.conf -d dm140 -r 5
If you want it running in foreground add -f and if you want lots of scrolling text add -r 4. This will show all calls to dm140_functions.
- Note
openSUSE 10.3 may receive the following error message when fire-up lcdproc.
Driver [dm140] init failed, return code < 0 Module /usr/local/lib/lcdproc/dm140.so could not be loaded Could not load driver dm140 There is no output driver
You need to create the devices:
mkdir /dev/usb mknod /dev/usb/hiddev0 c 180 96 mknod /dev/usb/hiddev1 c 180 97 mknod /dev/usb/hiddev2 c 180 98 mknod /dev/usb/hiddev3 c 180 99 mknod /dev/usb/hiddev4 c 180 100 mknod /dev/usb/hiddev5 c 180 101 mknod /dev/usb/hiddev6 c 180 102 mknod /dev/usb/hiddev7 c 180 103 mknod /dev/usb/hiddev8 c 180 104 mknod /dev/usb/hiddev9 c 180 105 mknod /dev/usb/hiddev10 c 180 106 mknod /dev/usb/hiddev11 c 180 107 mknod /dev/usb/hiddev12 c 180 108 mknod /dev/usb/hiddev13 c 180 109 mknod /dev/usb/hiddev14 c 180 110 mknod /dev/usb/hiddev15 c 180 111
I added these lines to /etc/init.d/boot.local
Note: MythDora 4 also errors as openSUSE 10.3 and the same solution works. Instead of adding the lines to /etc/init.d/boot.local you need to add them to /etc/init.d/rc.local - I also add /usr/local/sbin/LCDd to the bottom of rc.local to ensure it is running at startup.
Configure mythfrontend to use the VFD
The mythlcdserver is started automatically when configured in mythfrontend.
You can find the setup options in Utilities/Setup->Setup->Appearance->LCD device display Check the Enable LCD device.
- Additional technical info
Links to info on the VFD:
http://www.mythtv.org/wiki/index.php/Hiper_HMC-2K53A
http://article.gmane.org/gmane.comp.sysutils.lcdproc/11769/match=pluto
http://article.gmane.org/gmane.comp.sysutils.lcdproc/11742/match=msi+media+live
http://www.gossamer-threads.com/lists/mythtv/users/284040?page=last
ePG3231 is an 8-bit RISC MCU that is Mentioned in Japanese PDF documentation
specification of the DM140GINK (GP112x16 = 18x2) VFD
ZIP file of Source Code, Tools, Schematics, Docs, and Pictures.
- Pluto module source code
The Pluto guys seems to have this device working and deb file is available: http://plutohome.com/support/index.php?section=packageDownload&pkid=619
Since the site above seems unwilling to send the source code I downloaded it off their development-build;
-Media_Live_LCDButtons.src.tar.bz2
The Pluto dev-site will allow you to download additional source-code since there most likely are dependencies to other modules; deb.plutohome.com
Front panel keys
Incomplete, needs to be expanded. Please help to fill the gaps or discuss the issue on the talk page
Using the keys in mythTV
Tip: Moosylog : Nov 2007: I don't have the device, but have put some new info on the Talk:Futaba page that needs to be tested. It seems possible but you need to remap the keys to other values. Can you please test this and update this section of the wiki.
Here is a list of the front panel buttons
The 'xev' command gives us the following information about the keys:
AudioStop KeyRelease event, serial 31, synthetic NO, window 0x3a00001,
root 0x155, subw 0x0, time 3605380776, (618,-283), root:(622,278), state 0x10, keycode 164 (keysym 0x1008ff15, XF86AudioStop), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
AudioPlay KeyRelease event, serial 31, synthetic NO, window 0x3a00001,
root 0x155, subw 0x0, time 3605429259, (475,-185), root:(479,376), state 0x10, keycode 162 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
AudioPrev KeyRelease event, serial 31, synthetic NO, window 0x3a00001,
root 0x155, subw 0x0, time 3605485494, (385,-356), root:(389,205), state 0x10, keycode 144 (keysym 0x1008ff16, XF86AudioPrev), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
REWIND - NoSymbol
KeyRelease event, serial 31, synthetic NO, window 0x3a00001,
root 0x155, subw 0x0, time 3605520543, (323,-517), root:(327,44), state 0x10, keycode 152 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
FORWARD - NoSymbol KeyRelease event, serial 31, synthetic NO, window 0x3a00001,
root 0x155, subw 0x0, time 3605540560, (550,-95), root:(554,466), state 0x10, keycode 180 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
XF86AudioNext KeyRelease event, serial 31, synthetic NO, window 0x3a00001,
root 0x155, subw 0x0, time 3605557994, (353,-462), root:(357,99), state 0x10, keycode 153 (keysym 0x1008ff17, XF86AudioNext), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
Create ~/.Xmodmap
keycode 164 = XF86AudioStop keycode 162 = XF86AudioPlay keycode 144 = XF86AudioPrev keycode 153 = XF86AudioNext
(not sure how the other 2 are called - NoSymbol?) available symbols: cat /usr/share/X11/XKeysymDB
More information on .Xmodmap in Multimediakeys HOWTO.
Use the keys in Gnome/KDE
In Gnome, there's one place where you can define keyboard shortcuts for various predefined actions (opening the home folder, launching your default web browser) by just pressing the key combination.
If you want to add keyboard shortcuts for other commands, you press Alt-F2 and type gconf-editor to open the Configuration Editor, then navigate to Apps > Metacity. Within Metacity, you define the command in Keybinding Commands and define the keyboard shortcut in Global Keybindings.
The advantage to the Configuration Editor approach is that you can define a keyboard shortcut for just about any command you can think of. The disadvantage is that you have to type out the keyboard shortcut. You can't just press Control-Shift-A. You have to type <Control><Shift>a Free Image Hosting at www.ImageShack.us
KDE also has two places to define keyboard shortcuts, but they're both traditional point-and-click environments.
Keyboard shortcuts for custom commands are defined within the menu editor—so the disadvantage to KDE's approach is that you have to have a menu item (yes—it appears in the menu) for every command you create a shortcut for.
You don't have to type out the shortcut, though—you can just press it—this goes for both the predefined commands and the menu items.
Bluetooth
The Bluetooth module appears to be a standard HCI over USB interface. No special driver is required to operate the device. Tested with Mythbuntu 7.10 and MSI Media Live.
User experience
Moosylog : Oct 2007: Had a MSI_Media_Live for a few weeks in my house. Installed openSUSE 10.3(32) and started this page. Got the wireless and VFD working, no time to complete the keys section of the wiki. (please finish).
Hans_B :Nov 2007: Also using openSUSE 10.3(32), VFD works, using ndiswrapper for wireless.
Ritola : Apr 2008: Installed Fedora 8 on Hiper HMC-2K53A. Works: WFD, Keys with ~/.Xmodmap. Not using: Bluetooth, WiFi.