|
 |
|
08-10-2008, 03:43 PM
|
#16
|
|
Newbie
Join Date: Feb 2006
Posts: 18
|
I know I'm reviving an old thread but, I'm very curious as to how this project turned out. Were you able to complete it?
|
|
|
|
Sponsored links
|
|
Advertisement
|
|
08-10-2008, 06:45 PM
|
#17
|
|
Newbie
Join Date: Sep 2007
Posts: 20
|
No, I haven't completed it. I had to put it off for several months due to work and family commitments. My plan was to pick it up in August, which I have.
Recently I've soldered all of the hookup wire to the amp. I've also drilled and filed the openings on the amp case. Today I blew away LinuxICE and replaced it with Ubuntu 8.04. Right now I'm toying with Via's beta Unichrome driver for the CN700 on Ubuntu 8.04 and getting the touchscreen going.
I'm also playing around with Elisa as a front end.
|
|
|
09-01-2008, 01:01 PM
|
#18
|
|
Newbie
Join Date: Sep 2007
Posts: 20
|
Before I moved all of the PC components to the case, I wanted to make sure the case can actually fit in the dash:
Like a glove.
I'm going to mount the touchscreen to the case, but for this dry run I'm simply placing it in front of the case and allowing the dash kit hold it in place:
I'm not altering the touchscreen bezel for now, I'm just fitting it in as-is. I don't want to commit to the EBY701 just yet; I may upgrade to a daylight readable screen.
|
|
|
09-01-2008, 02:30 PM
|
#19
|
|
Newbie
Join Date: Sep 2007
Posts: 20
|
Here are some of the tweaks to Ubuntu 8.04 I needed to make in order to support some of my hardware.
For the touchscreen interface I created a udev rule to create a consistent symbolic link to the associated USB event. To do this I created a file named "69-touchscreen.rules" and placed it in /etc/udev/rules.d:
Code:
# Evtouch udev.rules
#
# Because Evtouch can't autoprobe devices we assume that we only
# Have one device so we can make it like this :)
#
# List here your touchscreen, check if it works and send it to lifebook_AT_conan_DOT_de
# Name can be found in /proc/bus/input/devices ('cat /proc/bus/input/devices')
#
# These are the touchscreens supported by kernel's "usbtouchscreen" module
# eGalax Inc. USB TouchController)
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="3823", ATTRS{idProduct}=="0001", SYMLINK+="input/evtouch_event"
# eGalax Inc. USB TouchController)
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="3823", ATTRS{idProduct}=="0002", SYMLINK+="input/evtouch_event"
# eGalax Inc. USB TouchController)
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="0123", ATTRS{idProduct}=="0001", SYMLINK+="input/evtouch_event"
# eGalax Inc. USB TouchController)
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="0123", ATTRS{idProduct}=="0001", SYMLINK+="input/evtouch_event"
# eGalax Inc. USB TouchController)
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="0eef", ATTRS{idProduct}=="0001", SYMLINK+="input/evtouch_event"
# eGalax Inc. USB TouchController)
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="0eef", ATTRS{idProduct}=="0002", SYMLINK+="input/evtouch_event"
# eGalax Inc. USB TouchController)
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="1234", ATTRS{idProduct}=="0001", SYMLINK+="input/evtouch_event"
# eGalax Inc. USB TouchController)
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="1234", ATTRS{idProduct}=="0002", SYMLINK+="input/evtouch_event"
# eTurboTouch
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="1234", ATTRS{idProduct}=="5678", SYMLINK+="input/evtouch_event"
# PanJit Touchset
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="134C", ATTRS{idProduct}=="0001", SYMLINK+="input/evtouch_event"
# PanJit Touchset
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="134C", ATTRS{idProduct}=="0002", SYMLINK+="input/evtouch_event"
# PanJit Touchset
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="134C", ATTRS{idProduct}=="0003", SYMLINK+="input/evtouch_event"
# PanJit Touchset
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="134C", ATTRS{idProduct}=="0004", SYMLINK+="input/evtouch_event"
# 3M Microtouch EX II
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="0596", ATTRS{idProduct}=="0001", SYMLINK+="input/evtouch_event"
# ITM Touchscreens
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="F9E9", SYMLINK+="input/evtouch_event"
# Gunze AHL61
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="0637", ATTRS{idProduct}=="0001", SYMLINK+="input/evtouch_event"
# DMC TSC-10/25
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="0AFA", ATTRS{idProduct}=="03E8", SYMLINK+="input/evtouch_event"
# Lifebook B-Series
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{name}=="LBPS/2 Fujitsu Lifebook TouchScreen", SYMLINK+="input/evtouch_event"
# Elo Touchscreen
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="04e7", ATTRS{idProduct}=="0020", SYMLINK+="input/evtouch_event"
Next, I installed the evtouch driver for the xserver:
Code:
$ sudo apt-get install xserver-xorg-input-evtouch
Lastly, I calibrated the touchscreen. None of the calibration utilities worked well for me, so I simply captured the raw output while I swiped my finger in each direction. Looking at the capture, I could see the coordinates for the edges of the screen. Here's my complete xorg.conf:
Code:
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection
Section "InputDevice"
Identifier "touchscreen"
Driver "evtouch"
Option "Device" "/dev/input/evtouch_event"
Option "DeviceName" "touchscreen"
Option "ReportingMode" "Raw"
Option "MinX" "101"
Option "MinY" "139"
Option "MaxX" "1953"
Option "MaxY" "1872"
Option "SwapX" "True"
Option "Emulate3Buttons"
Option "Emulate3Timeout" "50"
Option "SendCoreEvents" "True"
# Behaviour
Option "longtouched_action" "down"
Option "longtouched_button" "3"
Option "maybetapped_action" "click"
Option "maybetapped_button" "1"
Option "touched_drag" "1"
Option "oneandahalftap_button" "0"
Option "TapTimer" "30"
Option "LongtouchTimer" "500"
Option "MoveLimit" "10"
EndSection
Section "Device"
Identifier "Configured Video Device"
EndSection
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Configured Mouse"
InputDevice "touchscreen"
EndSection
#Section "Module"
# Load "glx"
# Load "dri"
# Load "extmod"
#EndSection
#
#Section "DRI"
# Group 0
# Mode 0666
#EndSection
The WiFi card was easy. Here's my /etc/network/interfaces (with the encryption key and SSID replaced with x's):
Code:
auto lo
iface lo inet loopback
auto ath0
iface ath0 inet dhcp
wireless-essid xxxxxxxx
wireless-key xxxxxxxxxx
iface eth0 inet dhcp
For GPS support I installed gpsd:
Code:
$ sudo apt-get install gpsd gpsd-clients
To configure gpsd, I determined its device path by looking in the dmesg output for the Prolific USB serial driver assignment. In my case it was ttyUSB0. To pass this info to the gpsd daemon, I edited /etc/defaults/gpsd:
Code:
# Default settings for gpsd. This file is sourced from
# /etc/init.d/gpsd.
START_DAEMON="true"
DAEMON_OPTS=""
DEVICES="/dev/ttyUSB0"
Until I find/make a frontend that's ready for real use, I'm going to use the GNOME desktop with a very simple layout. Here's how I have it set up:
For now, I'm going to use Rhythmbox for music and podcasts. It's not too touchscreen friendly, but it'll work for now. I'd like to use Elisa, but I'm running into
this issue. Instead of spending time working with the VIA graphics drivers, I decided to wait it out. I saw some good news on this subject on Slashdot this morning.
|
|
|
09-02-2008, 08:39 PM
|
#20
|
|
Newbie
Join Date: Sep 2007
Posts: 20
|
I forgot to mention two utilities I installed to make the interface a little more touchscreen friendly. The first one is "unclutter." It allows you to configure a timeout for the mouse cursor to disappear. It's in the Ubuntu repos:
Code:
$ sudo apt-get install unclutter
The second one is a Firefox addon called Grab and Drag. It lets you scroll by grabbing the page instead of the scroll bar...like the iPhone. It even has momentum settings, so you can give the page a push and let it scroll on its own.
I've been asked where my friend got the logos for the skin mockup. I copied them here for convenience.
|
|
|
09-07-2008, 09:07 PM
|
#21
|
|
Newbie
Join Date: Sep 2007
Posts: 20
|
|
|
|
09-16-2008, 08:58 PM
|
#22
|
|
Newbie
Join Date: Sep 2007
Posts: 20
|
I tweaked the desktop theme, increasing the font. It helps out with Rhythmbox and the touchscreen:
I've been messing around with virtual keyboards. I like matchbox-keyboard and Florence. They both detect when an input box gains focus and automatically pop up. Unfortunately, they require the Accessibility feature to be turned on, which causes this bug on Rhythmbox. So I ended up using xvkbd:
It doesn't come up automatically, so I added the icon on the top panel. The default layout for xvkbd needed to be changed to be more useful with the touchscreen. To get the layout in the screenshot, I added the following to my .Xdefaults:
Code:
xvkbd.windowGeometry: 780x280+10+300
xvkbd.compact: true
xvkbd.modalKeytop: true
xvkbd.*Alt_R.width: 1
xvkbd.*Meta_R.width: 1
xvkbd.*Caps_Lock.width: 45
xvkbd.*Multi_key.width: 1
xvkbd.*Shift_R.width: 75
xvkbd.*Control_L.width: 30
xvkbd.*Alt_L.width: 30
xvkbd.*Meta_L.width: 30
xvkbd.*Focus.internalWidth: 0
xvkbd.*Focus.bitmap: /usr/include/X11/bitmaps/target
xvkbd.NormalKeys: \
F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 Delete \n\
Escape 1 2 3 4 5 6 7 8 9 0 - = \\ ` \n\
Tab q w e r t y u i o p [ ] BackSpace \n\
Caps_Lock a s d f g h j k l ; ' Return \n\
Shift_L z x c v b n m , . / Multi_key Shift_R \n\
MainMenu Control_L Alt_L Meta_L space Left Right Up Down Focus \n\
xvkbd.ShiftKeys: \
F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 Delete \n\
Escape ! @ # $ % ^ & * ( ) _ + | ~ \n\
Tab Q W E R T Y U I O P { } BackSpace \n\
Caps_Lock A S D F G H J K L : \" Return \n\
Shift_L Z X C V B N M < > ? Multi_key Shift_R \n\
MainMenu Control_L Alt_L Meta_L space Left Right Up Down Focus \n\
xvkbd.KeyLabels: \
F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 Del \n\
Esc !\n1 @\n2 #\n3 $\n4 %\n5 ^\n6 &\n7 *\n8 (\n9 )\n0 _\n- +\n= |\n\\ ~\n` \n\
Tab Q W E R T Y U I O P {\n[ }\n] Back \n\
Caps A S D F G H J K L :\n; \"\n' Return \n\
Shift Z X C V B N M <\n, >\n. ?\n/ Com\npose Shift \n\
MainMenu Ctrl Alt Meta space left right up down Focus \n\
xvkbd.NormalKeyLabels: \
F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 Del \n\
Esc 1 2 3 4 5 6 7 8 9 0 - = \\ ` \n\
Tab q w e r t y u i o p [ ] Back \n\
Caps a s d f g h j k l ; ' Return \n\
Shift z x c v b n m , . / Comp Shift \n\
MainMenu Ctrl Alt Meta space left right up down Focus \n\
xvkbd.ShiftKeyLabels: \
F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 Del \n\
Esc ! @ # $ % ^ & * ( ) _ + | ~ \n\
Tab Q W E R T Y U I O P { } Back \n\
Caps A S D F G H J K L : \" Return \n\
Shift Z X C V B N M < > ? Comp Shift \n\
MainMenu Ctrl Alt Meta space left right up down Focus \n\
Last edited by mrob; 09-20-2008 at 07:26 AM.
Reason: Fixed the keyboard layout
|
|
|
09-21-2008, 08:45 PM
|
#23
|
|
Newbie
Join Date: Sep 2007
Posts: 20
|
I did a test fit of the motherboard in the case. It's a snug fit, but it will work. I just need to come up with a mount for the disk drive.
The Amp9 has a home:
I put together a case for the vallet switch and a remote turn on override. I'll keep this in my glove compartment:
On the back there's a connection for the remote turn on, line in, and mic in:
All that's left is to get a mount for the disk drive, move everything to the case, and mount the screen. I may complete the install next weekend.
|
|
|
|
Sponsored links
|
|
Advertisement
|
|
10-06-2008, 07:53 AM
|
#24
|
|
Newbie
Join Date: Sep 2007
Posts: 20
|
I installed the PC this weekend. It took the whole weekend. The biggest snag I ran into was ground loop noise. I couldn't get rid of it, so I caved and got a ground loop isolator...which did the trick. I took it for a spin and all worked fine. I really need to replace Rhythmbox as my media player though. It has everything I need, but it's just not great with the touchscreen.
This morning I realized that I'll have to reroute the cables, because when I kicked on the car's ventilation fan, I could hear interference through the speakers.
|
|
|
12-15-2008, 06:29 PM
|
#25
|
|
Newbie
Join Date: Dec 2008
Posts: 2
|
great project mrob!
I'm embarking on a same project, but I'm using the Atom-based motherboard, and running centrafuse instead of Linux
Just wondering, with the AMP9 amp, what's the power output to 4 Ohm loads? Also, how are you powering your tweeters? Is it true that the amp (the low profile kit) can be fed directly from the battery's 12V?
|
|
|
12-17-2008, 09:41 AM
|
#26
|
|
Newbie
Join Date: Sep 2007
Posts: 20
|
I'm simply powering all four stock speakers directly with the AMP9. I tied the inputs to make it two channels. It's plenty loud for me...much louder than the stock amp/radio. Yes, the amp can be powered directly from the battery.
Regarding the power, the amp is based on the Tripath TAA4100A chip. You can see the spec sheet here. I've been very happy with the amp.
|
|
|
12-17-2008, 10:06 AM
|
#27
|
|
Constant Bitrate
Join Date: Aug 2006
Location: DFW
Posts: 153
|
Amazing DIY on that amp9... i'm in awe.
|
|
|
12-17-2008, 10:06 AM
|
#28
|
|
Newbie
Join Date: Dec 2008
Posts: 2
|
Ahh.. that's good to know.
so you only get four inputs to the speakers, and that they are connected to each of the output of your AMP9, correct? That would mean the tweeters are already taken care of by some built-in crossover.
It's so good to be able to discuss with someone who's working on the same thing.
I'm currently troubled by the enclosure, not sure if I want to stuff it in the double DIN slot or should I route it somewhere else. As you have mentioned in previous posts, the depth of the DIN slot is only 6.75" ?
|
|
|
12-17-2008, 10:16 AM
|
#29
|
|
Hey, you're trying for the goal by going the other way around, you're crazzzyyyy!
Join Date: Jul 2007
Location: Miami
Posts: 4,169
|
Quote: Originally Posted by Kalenth 
Amazing DIY on that amp9... i'm in awe.
I agree, i was lazy and bought motorcycle amps....
Do have a question.... why not go with Windows and a Front End that has better features?
__________________
HiJack ZX1 CFSC
CAR PC ITEMS [ 35%]
INSTALL OF MULTI PC SYSTEM [ 35%]
BUG WORKOUT [ 0%]
INTERIOR MODS [ 45%]
HiJackZX1 Work Log
HiJackZX1 Website!
Please build up my REP.
|
|
|
12-17-2008, 10:56 AM
|
#30
|
|
Newbie
Join Date: Sep 2007
Posts: 20
|
Quote: Originally Posted by HiJackZX1 
Do have a question.... why not go with Windows and a Front End that has better features?
The main reason is that I love to tinker...and Linux is *much* better for tinkering. I took on the project not just to have an entertainment system, but something I can always hack...at any level. Otherwise I would have simply picked up a commercial device.
I don't have a problem with Windows (I use it more than I use Linux). But for my purposes here, Windows is not a good fit.
I'm currently in the process of making my own front end...so I'm just using Rhythmbox until it's done.
|
|
|
|
Sponsored links
|
|
Advertisement
|
|
| Thread Tools |
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 09:56 PM.
| |