Thread: TatraApp is dead, here comes QCar

Originally Posted by Jirka Jirout

Yes. The code that actually communicates with hardware is a plug-in and there can be more plug-ins, depending on hardware/protocol you use. We plan to prepare plug-ins for raw CAN communication with VW and GM vehicles, proprietary protocol of my Tatra and we are trying to figure out the old Volvo 480. However at this moment, I cannot promise support for any particular protocol. While it is very easy to write the plug-in, it is very time-consuming to analyze the protocols if documentation is not available. And of course for each protocol we need at least one vehicle for testing.


I can have a look at this, just pm me. But no promises. On the other hand, I can give you documentation of our API and a sample plugin project (XCode/Cocoa). Then you could try to write the data-parsing code yourself.

check your PM's

Update please!?!?

Originally Posted by joesan

Update please!?!?

The update is that we have another two cars installed (a V480 and a Range Rover). On the software side, there has been some progress too:

- NMEA GPS connector module - Done
- OBD connector module - Done
- Weather module - Done
- Sound control module (balance, volume) - Done
- Airport module (incl. position logging) - Done
- Stop watch (incl. flyback reset and 2 lap times) module - Done
- Tracking module (in-car) - Done
- Mail connector (POP3) - Done

- Image browser plug-in - 90% (missing thumbnail browser)
- RSS reader module - 90%
- HQCT tuner plug-in - 90% (some RDS stuff still missing)
- Tracking module (server part) - 50%
- Messaging reader - 75% (some GUI not finalized)
- Mail connector (IMAP4) - 10% (kind of works, but crashes, does not handle folders etc.)

Planned, but coding not yet started:
- Voice memo recorder
- Phone integration (we scrapped what we had and are looking at a different option).

On the application side, we are still playing around with standardization of the icons and speech support - it works, but we are still not happy with it :-(

We are also preparing few things with phidgets for cars, where interfacing with original sensors etc. is impossible or too expensive.

Our site should be up probably by end of next week, when it is, it will contain more information, screenshots, probably also some end-user documentation.

That's looking good, Jirka. I like your modular approach to the system and the clean graphics.

One thing I'd like to ask - will you be supporting any non-bluetooth protocols for controlling the phone. I'd like a wired solution as I find bluetooth a little too flakey and too much of a draw on the battery. Ideally I'd like to clone my sim and leave it permanently attached to the mini but that might be a pipe dream.

Keep up the good work!

Originally Posted by joesan

One thing I'd like to ask - will you be supporting any non-bluetooth protocols for controlling the phone. I'd like a wired solution as I find bluetooth a little too flakey and too much of a draw on the battery. Ideally I'd like to clone my sim and leave it permanently attached to the mini but that might be a pipe dream.

Since the module handling the user interface and the module handling the communication with particular phone are separate bundles, it is possible to write a plug-in, that will talk to the phone over a wired connection. As a matter of fact, I am using my GB060 GSM/GPS box exactly this way. What phone exactly did you have in mind? If it is not too obscure and uses protocols that can be used by other phones too, we may implement this.

Jirka - the iphone off course!

No seriously I think either the Motorola Razr or the LG Chocolate (I have both0. I guess the Moto would be easier or at least more standard?

Wow this looks great. i think you have made a lot of firsts here in the ways of mac-car intigration, specifically with ODBII. Out of curiosity what features will be involving phidgets? Keep up the great work I can't wait to see screenshots!

-Ben

The phidgets will be mostly used for customized installs and special functions, typically when some data (i.e. temperature) cannot be read from OBD etc.

In my V480, I will have the following:
- 2 x 20 char LCD with 8/8/8 controller
- 3 temperature sensors
- voltage sensor
- current sensor (50A)
- RFID sensor + tags

I will also use two analog inputs for water and oil temperature (small adapter to car's built-in temperature sensors).

As for the digital inputs and outputs, I plant to use one output to control the central lock, maybe some lights, I do not know yet.