Thread: TatraApp is dead, here comes QCar

I may have missed a posts about this but is the application universal or Intel only?

it is universal. i run it on my intel mini as well as a power pc one.
-cheers

Any chance of adding a "Mute" button somewhere on the screen (as opposed to just volume controls)?

The mute button (as well as Volume Up/Volume Down) is there as well in newer builds.

Hi Jirka,

If I have my MM connected with UTMS or GPRS to the internet. How many data (MB's) are the weather and rss module using aproximitly? And the google maps?

The weather update is approximately 2-5 kBytes (images are stored locally, so we only download and upload XML data/requests).

I am not really sure about Google Maps, as it would depend very much on how often you zoom in/out and how far you travel. But one tile (256x256 pixels) is usually 20-30kBytes and two to three are displayed in the workarea and about 6 in the fullscreen mode. But I will check on some trips today and tomorrow and let you know.

The tracking beacon, if configured to broadcast the position every 10 seconds, generates about 80-90kBytes/hour of traffic (and this will be reduced to about half in the next release).

Is there a sign up for the beta?

We have finished the fully configurable support for Phidgets (this means both digital input and output lines which were previously not supported) and integrated it with the steering wheel controls in our Range Rover. The Space Navigator controller module is also fully configurable now. The first version of voice memo recorder is done. Several bugs causing high CPU load were also fixed.

We should release a beta build for testing during the weekend and perhaps update the open demo version next week.

And last but not least, here goes some overview about perhaps the most expected function of QCar - the navigation.

First - we are working together with Routebuddy and we will be therefore using TeleAtlas as source of map data. There will be two or three versions of the navigation:

1. Basic offline navigation - you will plan your route externally, either on a web site, thru a call center or using desktop version of Routebuddy. This route gets exported into a gpx file and loaded by the plug-in in the vehicle - either thru online sync service or you can bring it on an iPod, flash drive etc. The plug-in in the car will load the file and guide you thru the route. This version will only show the route itself (including turns), but will not be directly linked to a map (perhaps it could be projected onto a Google Maps view). This basic version will not require any map engine or maps to be installed in the car. In case of re-routing, a completely new route will have to be re-created externally.

2. Mapping navigation - this will be very similar to TomTom etc. including map display, destination entry directly in vehicle etc. It will require the mapping engine and the appropriate maps to be installed in the car computer.

3. We may also have a non-mapping version, where basic data will be installed in the car and the user will be able to enter destination internally on the car computer instead of having to download it from an external source.

Both versions will be able to record a track and use it later as route. Both will also be able to do off-road navigation.

Thats great! But will it parallel park by itself?

Just kidding, it sounds like this is a great application.