hello Jirka
starting from when one can buy or test this Qcar?
I would like mine carmac update over if am Qcar driven out ?
bye
Those images show the display in what we call "work area" - of course the modules for which it makes sense can and do go fullscreen. I will send you a pm regarding the testing.
hello Jirka
starting from when one can buy or test this Qcar?
I would like mine carmac update over if am Qcar driven out ?
bye
Good news, bad news...
Good: we have a very first, but working piece of OBD code. It can read most of the standard and some proprietary stuff like engine rpm, speed, error codes, battery voltage etc. It works with ELM chip-based OBD adapters and should be compatible with ISO/SAE/CAN-based OBD. We have tested it on a Range Rover and a Saab 9-5 yesterday.
Bad: we cannot read the total distance driven using OBD, which is rather unfortunate as this info is needed for various calculations. We may be able to do this using raw CAN communication for some vehicles, but is pretty likely a special hardware will be needed on most cars to read and store the pulses from the distance/speed sensor.
There are also few other issues with fuel flow-related calculations, but we should be able to address these one way or another.
jirka, would you say that the primary media functionality is working as you would like? just curious. keep up the good work.
replicant
Audi A4 (flickr pics)
- Music player: Done
- Movie player: Done
- AM/FM tuner (HQCT): 80% (what remains is basically GUI, tuner control is done)
- XM/Sirius: 20% (some stuff done, but I will have to finish these when I am in the US and have access to both the hardware and the service).
- Camera photo import: Done
- Picture browser: 10%
Right now, the priority is to finalize OBD, navigation and online services.
jirka, excellent work! i was just curious where the project was in the timeline in terms of commonly used features in a front end. can't wait to see more screenshots, etc.
replicant
Audi A4 (flickr pics)
Yes. We actually have two modules to do this, depending on the hardware configuration - one uses HQCT and the other one does this using CoreAudio (intended primarily for use with FireWave).
any chance the obd interface/engine could support plugins for other/variant protocols? I drive a 95 nissan which uses CONSULT as its main diagnostics protocol. I maybe be wrong, but I don't think it is OBDI or OBDII compliant.
OBD II questions
Nissan Consult cables
I've purchased two copies of Consultan from eric pooch the creator. If you want one of the licenses for research I would be happy to oblige.
thoughts?
I would be very happy to purchase a copy of this software for a reasonable price given this feature was at least supported, if not implemented immediately.
-ikon
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.I've purchased two copies of Consultan from eric pooch the creator. If you want one of the licenses for research I would be happy to oblige.
Bookmarks