Anyone figure out how to get live engine data from a 512tr

Hi,
since this is a 2.7 motronic, I have only been able to access fault codes.
its a single wire comms, so doesnt seem to adhere to any standards like OBD 1, etc.

but consider this, if you can retrieve fault codes, by sending it a series of pulses, I would suspect, there is a sequence of pulses needed to retrieve other data..
that is the unknown.

if someone can wireshark (packet sniff) an SD1, youll have your coded sequence needed to simulate it on any computer device.
now who can/wants do that

unless there is some other interface plug that I am not aware of, that the SD1 plugs into??

 

I think this motronic 2.7 from bosch is also in other cars and the failure codes would be the same?

here you can find a little:
https://www.ferrarichat.com/forum/threads/motronic-2-7-malfunction.383255/
https://www.***********.com/threads/motronic-2-7-information.20426/ replace the **** with f e r r a r i l i f e, without the sapces between the letters. don´t know why I can not edit those *****???
http://www.bxproject.co.uk/phpBB3/viewtopic.php?t=1468

you may use google and will find a lot more

 

Failure code for the 512tr, are in the wsm.

what this thread is about is getting sensor data from the computer.. monitor in real time what the ecu is doing with its inputs from engine sensors, tps, water temp, etc

 

have not read all the links I posted here. was only overlooking a little. I think you only want to know how to read the failure codes?

do you have in australia an official bosch distributor? I think this one could help you, when he is long time in business.

for this I think you need someone programming those ecu´s. try to find a tuner manipulating those ecu´s.
but for what you like to know what wii happen in the ecu? like to change something because of higher rpm or other pistons inside and change the ignition timing?

 

I don’t think changing anything in the ecu..
Just data monitoring..

 

there used to be this guy, back in the days of "news groups" where he cracked bosch ecus off BMWs.. I did ask at the time, if they can share the findings.
I guess people want to protect their IPs, and make money off it.
Annoying, but understandable..

"where is the sharing of love in this world" lol.

 

I suspect you wont be getting what you want, like the modern ECU/aftermarket software..
the 2.7 is old tech, serial comms.. and as we know, serial is pretty slow..
so you may be able to monitor engine at idle, but anything on the move, it wont be able to keep up with the data refresh

Seriously, if my 2.7s ever go bang, I am going with after market Haltec/Motec.. they are seriously so good and flexible these days, you would wonder why you never made the switch.
and this is just me playing around on my Formula Ford race car, that runs Motec...

 

I owned a repair shop back in the eighties to the nineties- back when fuel injection was in it's infancy, and on-board diagnostics was not even available. As an independent shop, I didn't have the support of the car manufacturers, but still had to have the ability to troubleshoot electronics issues in cars. I started using lab scopes on cars very early on to aid in troubleshooting, By 1990 I had a shop very close to a company in Oregon- Tektronixs that manufacture all types of oscilloscopes, and rapidly had several of their engineers as customers. I was provided the latest and greatest scopes, probes- anything I needed. The key was to get patterns from known good cars, so that when a car with issues came in, I had a library of patterns to compare with. The CIS cars didn't lend themselves to this as much as the full electronic injection cars. Although the frequency valve used was a real source of information as well as the oxygen sensors. I have three older Testarossa's with CIS injection, but I think the 512 IS full electronic. A scope hooked to the injector wiring can tell you a wealth of information.

Thirty years ago before OBD, the lab scope was a very valuable tool. Tek came out with a four channel scope, that was designed to be used by mechanics, that could go right in the car for checks in driving conditions. It unfortunately was a POS. BUT the only way to make the lab scope work, was to constantly test different cars and understand what you're looking at- voltage changes over time. Don't know what you're trying to figure out on your 512, but just giving you a thought on how it was done with a VERY generic tool. Used lab scopes are a bargain. Under the hood of a car, there's a lot of NOISE that shows up on a scope, and you have to use it enough and get the settings right so that you're looking at the actual signal, and NOT a bunch of spurious waveforms being picked up from the ignition.
The more I used it the better I got at figuring out problems. It's NOT like hooking up a scanner and having the problem literally spelled out.

 

before OBD I also was working with only a 2 cannel scope and found with this problems. but you have to know how the pattern has to look when all is ok to see what is not ok. but it is long time ago ( even only 30 year ) and I nearly forgot all
and now retired and all what has nothing to do with ferrari or renault 5 turbo I gave away and still sorting out when I be back in germany again

 

Getting me in trouble ehhh???? LOL


Yeah can be done I did my 348 with the 2.7 motronic which I believe is the same as the 512 but uses 2 of them
I used the Moates Ostrich emulator with a breakout plug for the ECU chip, your going to need to write a few control files. This will allow you to see "real time" whats going on.
Again you need to piggyback it to the chip socket, take a drive see what moves in the code then figure out what it does. Do this for everything you want to read, RPM, engine temp, throttle position, fuel, spark etc.
Pain in the butt, yes and very time consuming
Have moved on from this as I lost interest after I mad poo in my pantalonies
I may have a dump file from the 512 somewhere I remember playing with one way long ago..
Anyway good Luck

 

do you piggy back on the CPU or the EPROM?
the EPROM would be easier as you can appreciate

is there no way to get control via the serial line?
sure via direct over chip will be real time, but the SD1 talks over the serial line, and to mimic that would be neater..

 

I used the eprom

SD1 is proprietary and I'm sure some companies have reverse engineered it. It's a pay to play game here for sure. I must have had 40-50 hours into it @ $200 hr. What I'm saying is get an old SD1 or perhaps a Leonardo that will save you tons of time.
Or just do component testing 1 by 1 until you find what you need. These old cars are very simple.

Good Luck