Reality: nice audio!
The AutoPC uses a pure digital path for sound processing. The analog output of the tuner radio signal is digitized with a 20-bit A/D (i.e., analog/digital) converter. When playing CD's, as shown in Figure A, the data is read off of the CD and passed to a 24-bit DSP (digital signal processor) for all signal contouring and processing. The data is then sent to a 20-bit D/A converter and analog audio is then fed to the line level out and amplifiers.

FIGURE A

The AutoPC has a nice, if small, user interface. Here, it's playing a disk.

Vision: speech-driven user interface
Let me talk to the AutoPC and have it talk back. Keep my attention, as a driver, focused on the road with my hands on the wheel. Help me to drive more safely even if I'm just using the audio features of the product.

Reality: semi-speechless
For many key features you can command the AutoPC with speech and it will talk back. However, there are many more tasks that can't be done with speech.

Vision: GPS with navigation software
A GPS (i.e., Global Positioning System) with navigation software is a natural feature in a car. Being able to obtain an answer to the question "Where am I?" when you ask, is a great safety and convenience feature. Since stand-alone navigation systems run around $3,000, this functionality in the AutoPC could be the feature that sells the product to many people.

Reality: GPS essentials
The AutoPC comes with a driving directions application, shown in Figure B, that is okay for getting you from point A to point B but it doesn't use the GPS except to obtain your starting location. A full feature navigation system for the AutoPC called Odyssey that gives the AutoPC full use of the GPS can be purchased from Infogation at http://www.infogation.com. .

FIGURE B

Where do you want to go today?

Vision: address book with phone integration
I wanted the AutoPC to be able to dial the phone. I wanted it to recognize the sound of a a person's name or dial when their phone number was being spoken. I wanted it to provide hands-free functionality through the existing speakers in the car and the AutoPC's microphone. Also, I wanted to tie this into the navigation system so I could just tell the system to direct me to "Josh's house". Plus, having access to the location and phone numbers of various points of interest would be valuable. With the integrated navigation system, you'd be able to direct the AutoPC to find the nearest ATM machine, gas station, or hospital.

Reality: address this a little more
Much of this functionality is available for the AutoPC today, as shown in Figure C, except for that fact that phone manufacturers have yet to come out publicly with interface kits for the AutoPC. Infogation's Odyssey doesn't integrate the address book quite as seamlessly as the vision but they do work together.

FIGURE C

Who do you want to call today?

Vision: link to my engine's on-board computer
There's a diagnostic connector under my dashboard for my engine's computer. I thought the AutoPC should be able to talk to that computer through the diagnostic link. Since the on-board diagnostic link was standardized by federal law in 1996 model year vehicles (the Society of Automotive Engineers standard is referred to as OBD II), this standardization would make it much more practical to design a link between the car's computer and the AutoPC. It would be great if, when my engine was having trouble, the AutoPC was able to tell me what was wrong with it, providing at least basic information about which subsystem or sensor was failing. The AutoPC should also be able to get vehicle speed, engine temperature, outside air temperature, RPM, and door switch information from the engine computer. Power accessory features like windows, door locks, and seat position should also be able to be controlled. There should be some sort of gatekeeper between the two devices to prevent one device harming the other.