(T) 6F/16F Cinque/Sei ECU Reader Project

Ok, here is a shiney nice new thread for this

Hi Jon,

Depending on how willing the ECU is to divulge data, and how much of a pig it is to read we are looking at a few possibilities (in ascending order of complexity):

1. Fault code only - (I'd settle for this!) it would give us a code which we could presumably then translate into the source of the problem. This is the least resource intensive in terms of hardware, software or microcontroller or CPU speed.

2. Snapshot of engine parameters. If accessible, this would allow the registers which store the various sensor values to be read. These values would/could be updated fairly frequently.

3. Full, real-time data out. I suppose this is the 'Holy Grail' - if the ECU has this capability, this would allow a (hopefully low-lag) mirror of what the ECU is seeing and doing. Goes without saying the most resource-intensive hardware/software, not to mention any signal processsing *shudder.

These are of course speculative, if anyone knows what data-out capabilities, services or facilities these ECUs provide - post!

So to get back to your question, if we are looking at anything above option 1 (which I don't think necessitates a PC to do) - yeah, in theory, the software could be made to data-log, save peak values, show performance stats, and much more. It just depends on what you wanna do with the data out (and how long you wanna spend looking for missing semi-colons....)

My mate had a turbo'd Brookie Capri, which the previous owner designed and built a home-brew boost controller for, which took sensor readings and did all sorts of clever things! Incidentally - if anyone knows who now owns this car (Reggy started E666 *** ) Can't remember the rest (LOL - Capri of the devil!). I think my mate regrets selling it somewhat....

Anyway, so yeah, it all hinges on what is accessible through the data port.

Cheers, Jamie

Its very easy to get the ECU to spit out data.. All you have to is initialise communications, switch to an obscure baud rate then tell it what you want to see, it'll then spit the data out at you within a short time period (300msec timeout i think for parameters).

To read fault codes....well thats the seemingly easiest part. The ECU has 6 different error memories (3 RAM, 3 EEPROM) that it writes to dependant on the state of the error (eg: transient / permanent). What I want to do is be able to poll all of these memories independently (each bit of each memory corresponds to a different error) - as Ive had problems with transient errors not appearing when Ive gone for ECU Diag scans, and so the reader hasnt picked it up - but it would have been in the E2PROM memory, but their reader must only scan the RAM (blanked at each start-up and only written to when errors present).

Engine Parameters.....Theres a riduiculous amount of data that can be had out of it...the 16F ECU doc will detail all. Its all in the form of Hexadecimal numbers and all it needs in terms of formatting is feeding into equations (theyre given in the Tech Doc).

In terms of S/W structure, I was thinking integrate it into a series of self-contained modules to limit the amount of data recieved / sent so the CPU isnt over worked (my target system is a PII 300)

This thread has a wealth of technical data, and the coupe uses a similar ECU to the Cinq.

http://www.fccuk.org/ubbthreads/show...fpart=all&vc=1

I emailed barnacle about adding the cinq to the software, and he said it should be possible - but he was in Kiev at the time. I don't know if hes since got back to me as i can't seem to get into my uni email account!

Heres the the document that Tom translated for those who want it.

The software is available from different companies. All you have to do is acquire it and go to your local RR to set it up properly.

elaborate?

This is what real tuning is about.

I try to find a solution to make it easier in the region of £2.95. Did not work yet.

Who said tuning was involved?
I just want to be able to get ECU data and find error codes. Admittedly, the Data may well be used to tune the engine (via remapping), but theres no way it can be tuned directly through a computer, as its not OBD-II Compliant.

Once we have some way of getting the data for analysis purposes the fun can start.

Actually that is what you have to do! It is not me who invented ECUs. It does not matter whether you can do a real time tuning or not. If you want to get the best out of it or even want to go save you have to do it. Or why do you think that new cars on average require about 12000 man hours to programm an ECU that it can be considered safe for daily usage? I am not talking out of my backside. I have seen it too often.
And don't worry I have no time to show off. Believe me it did hurt when reality struck me at many a times.

I'm quite sure that you're right the rational approach says that its too difficult, but as I found out in developing my chip. The challenge and satisfaction in doing it is part of the reward, and everyone benefits as a result. Thats why people can buy a good remap for £40 rather than £200. Why discourage people from having a go at developing something new. You never know they may find a better way and everyone benefits.

All the best to the project, If I can help I will!!!

Regards,
Michael

Erm...am I the only person here who cant even remotely understand how ECU tuning has anything to do with our goals? We only want data out!. O-U-T Spells OUT!! Opposite of IN!!!

Thanks for your support Mick, I was hoping that the final product could help develop better chips by being able to collect car specific data

LOL. No, I'm with you!

I'd love to be able to get an air/fuel curve, would help no end!
But I'd settle for just fualt reading coz that'd be extremely useful.

Jon.

I looked on the coup site and saw the diagrams for the interface kit. Not sure if any would work with the 16F ECU. but if you can find a suitable schematic my mate that helped with the chip can almost certainly make up the interfaces,
Regards,
Mick