Alfa Romeo Forum banner

ECU monitoring

12K views 122 replies 12 participants last post by  bazza 
G
#1 ·
Dear alfistis!!!
Is there a way to monitor the ECU of our cars using for example a laptop and the appropriate set of program-wire-adaptor :confused: .
As several friends of mine have VW group cars they use the VAG-COM :eek: which consists of a wire-adaptor for connecting the laptop with the ECU and a program that translates the signal from the ECU. Note that THIS IS NOT some kind of hacking the car's ECU as there is a slot in the passenger-cabin for this purpose. If anyone knows something similar to this for Alfas please share with us!!!!!!!
 
#52 ·
MR T

Although the scantools hardware & software also looks good, there is one slight problem - that ELM procesor chip - is only sold in the US, and was hard to get hold of. The scantools hardware does the signal conversion, as opposed to the andywhittaker hardware (link on 1st page) which allows the level shifting, etc to be done in the software.

I found another link last night & forgot to add it here, i'll see if my lazy arsed bro is up yet, he can get it off my machine for me..
 
#54 ·
Didn't realise that the Andy Whitlaker hardware will work with that software I was using last night. 7 quid for the circuit board and 8.50 for the connector. Depending on parts I should be able make it up fairly cheap. I'll make sure that I can get the software to work first.
 
#55 ·
I d/l the software, it loaded up ok. Played around with the example log file, looks like it reports back pretty comprehensive info!

Also the VAG-COM software looks like it may work too!
 
#56 ·
The VAG-COM software carried out the handshake with the connector last night only the vehicle explorer wouldn't work. VAG-COM is only designed for those VW thingies.

The principes for the connectors are straight forward after reading the other site about delaying the pulse.

I'd be happier getting the current stuff working first before bashing on and buying the connector.

After looking at them all this looks to be the way forward for future programming.

Have fun
 
#57 ·
Ok T - what do you mean the current stuff?

From your comments, I assume you are using the obd-2.com software?
But what are you using for the interface? have you just stuck the K-line straight into your com port?!
 
#58 ·
I using the obd-2 connector as well, as purchased by my mate. The difference over the andy W one is this connector covers everything. I don't have a clue about the price though. I guess the Andy W will be the cheepest if it will run with the obd-2 software.

This is why I want to get the obd-2 software running with it's own connector first.
 
#60 ·
bad news! - No OBDII connector for me. I removed the lower part of the dash under the steering column to reveal the fuse/realy box, millions of small connectors but no 16pin connector.
The diagnostic sockets I have found are:

Right of passengers airbag behind easily removable blank dash.
3 pin connector:
pin 2: black
pin 3: white/red
T3 - Airbag ECU connector

Nearside strut
3 pin connector:
pin 1: blue/white
pin 2: black
pin 3: white/red
T8 - ABS ECU connector

Offside strut:
3 pin connector:
pin 2: black
pin 3: white/yellow
T1 - Bosch ECU connector

So it would appear, no OBDII for 145's, even though it has the M1.5.5 ecu the same as 156/gtv which do have the OBDII connector
 
#61 ·
Guys

I have been following this thread for some time now, not wanting to post my findings, discouraging you guys from further investigating the matter. I posted a similar thread a while back, hoping our former tech guru Numan could help me out, to no avail.

Since you guys seem to have given up, and shot the idea dead, let me burry it.

I have successfully read live data and erased fault codes on a Honda with a Hyundai tester. ( Had to do it as the Honda tester hadn't been upgraded at the time) The Honda Accord is E-OBD compliant and so is most Hyundais.

Since my 156 have the 16 pin OBD connector my hopes were high as I connected the Hyundai Hi-Scan tester to the Alfa. Well, it couldn't establish communication. I tried both E-OBD and OBD2. As you may have found out, but not mentioned in this thread, OBD-2 is made for cars sold in the US market. E-OBD became compulsory within the EU from MY2001 ( If my memory serves me right)

Where do we take it from here, if I can be of any assistance, let me know ( I'm no rocket scientist, mind you )

Cheers

Hoygaard
 
#62 ·
Hoygard

The project is under way my friend!
My old man has a VW passat (2002) with obdII
The obdII connector has been ordered and all parts for an interface he already has. It is under construction, and when it is working will look at tranpsorting the projec to my alfa.

My problem is that I dont have an OBDII connector, but have seperate connectors - each one with its own K-line. on OBDII you can chain many devices with the K-line, so you just have a single diag line. I also have info on some of the wake up codes, etc for the Motronic ECU.
It is looking promising, just not ready to rig the hware up yet...give it a couple of weeks, I'll see what I find.
I also have info on the data packet structure for various different protocols, so if it fails I will try feeding it myself, then capture & try and debug what I get back...
 
#64 ·
Well OK, so no need to remove the rosetinted spectacles yet. The idea behind OBD2 was that any testing equipment should be able to read DTC's and live data from any vehicle sold in the US. Now, I'm guessing here!! Any tester should try to establish communication via all three protocols then, no ???

What buggers me the most, I had the chance to "nick" the interface from the official AR-FIAT-Lancia tester a few years back along with the Software. Right now, I could punch my face in. BTW, the Fiat group tester is made from a HP PC.

Cheers

Hoygaard
 
#65 ·
Hoygaard - you are a fool for not taking that machine man! wink
Shame, that would have been nice!

And as for the OBD2 - yes it would make sense for all scanners to read all obd2 - but manufacturer specific ones I wouldn't have thought would work. Some aftermarey diy interfaces support all 3 protocols, some just 1.

I know the EXAMINER is made by HP - my dad used to work for HP - I've forced him to get intouch with old contacts to see what can be dug up :D wink

Give it time...the secret will be out soon!
 
#66 ·
<blockquote><font size="1" face="Verdana, Helvetica, sans-serif">quote:<hr /><font size="1" face="Verdana, Helvetica, sans-serif">Originally posted by ajcarter:
<strong>Hoygard

The project is under way my friend!
My old man has a VW passat (2002) with obdII
The obdII connector has been ordered and all parts for an interface he already has. It is under construction, and when it is working will look at tranpsorting the projec to my alfa.

My problem is that I dont have an OBDII connector, but have seperate connectors - each one with its own K-line. on OBDII you can chain many devices with the K-line, so you just have a single diag line. I also have info on some of the wake up codes, etc for the Motronic ECU.
It is looking promising, just not ready to rig the hware up yet...give it a couple of weeks, I'll see what I find.
I also have info on the data packet structure for various different protocols, so if it fails I will try feeding it myself, then capture & try and debug what I get back...</strong><hr /></blockquote><font size="1" face="Verdana, Helvetica, sans-serif">And I thought the first page of this thread was making my head hurt. :rolleyes: laughing
Oops. I wasn't supposed to be posting here any more, was I? :eek:
 
#68 ·
The attitude I want to hear boys, "If it can be done then we will do it". I still haven't had more time to play with the interface on the laptop. I could maybe see a problem with the later stuff like the bosch ME but not with the M1.5.5. As soon as I get it working I will be on the diy Palm software case.
 
#69 ·
<blockquote><font size="1" face="Verdana, Helvetica, sans-serif">quote:<hr /><font size="1" face="Verdana, Helvetica, sans-serif">Originally posted by Hoygaard:
<strong>Guys

I have been following this thread for some time now, not wanting to post my findings, discouraging you guys from further investigating the matter. I posted a similar thread a while back, hoping our former tech guru Numan could help me out, to no avail.

Since you guys seem to have given up, and shot the idea dead, let me burry it.

I have successfully read live data and erased fault codes on a Honda with a Hyundai tester. ( Had to do it as the Honda tester hadn't been upgraded at the time) The Honda Accord is E-OBD compliant and so is most Hyundais.

Since my 156 have the 16 pin OBD connector my hopes were high as I connected the Hyundai Hi-Scan tester to the Alfa. Well, it couldn't establish communication. I tried both E-OBD and OBD2. As you may have found out, but not mentioned in this thread, OBD-2 is made for cars sold in the US market. E-OBD became compulsory within the EU from MY2001 ( If my memory serves me right)

Where do we take it from here, if I can be of any assistance, let me know ( I'm no rocket scientist, mind you )

Cheers

Hoygaard</strong><hr /></blockquote><font size="1" face="Verdana, Helvetica, sans-serif">Do you know what is the difference between EOBD and OBD-II?
 
#71 ·
My connector arrived yesterday (3 pin type), and an OBDII connector should be arriving today.
I am going to build interface at the weekend, prove it works with OBDII connector (my dad's VW) then give it a bash on my 145.
Will post the findings.....
 
#70 ·
My connector arrived yesterday (3 pin type), and an OBDII connector should be arriving today.
I am going to build interface at the weekend, prove it works with OBDII connector (my dad's VW) then give it a bash on my 145.
Will post the findings.....
 
#74 ·
<blockquote><font size="1" face="Verdana, Helvetica, sans-serif">quote:<hr /><font size="1" face="Verdana, Helvetica, sans-serif">Originally posted by Hoygaard:
<strong>Boris,
The 147 is EOBD compliant :)

Hoygaard</strong><hr /></blockquote><font size="1" face="Verdana, Helvetica, sans-serif">I know, that is the reason for asking :)
 
#75 ·
Was playing about with the interface yesterday on my dad's 01 Passat TDI (OBDII compliant)
The interface used an rs232 chip, found the schematic from andywhitaker.com on one of the additional diagrams.
Used the VAG-COM software (found a crack to register it to get full functionality as well wink )

Plugged it in, worked fine with ignition on - could retrieve VIN no, loads of data - it read all the engine monitoring values but as the engine was not running, rpm, speed, air flow, etc stayed constant.

As soon as the engine was started, it lost connection. Switch it off - fine again. I had to enrol the help of my dad and a scope for this one - too much noise was being created and the signal was not properly grounding, anyway a few components later and it was sorted - it works :D

was reporting back all the info you'd expect, then went for a drive to log all the data, seems pretty comprehensive. The VAG-COM software won't work on the alfa's - the protocol the VAG's use is KWP2000 - the alfa's will use 9141-2 I think.
I tried the interface with the software from obd-2.com and could not get it to work - after further investigation I think that software needs its own interface - perhaps it acts as a dongle.

I could not find any other generic (free) software which would work with a standard interface other than the VAG-COM software.
I haven't tried this with mine (still waiting for my connector to come) but know it won't work - wrong protocol.

I am now investigating the ELM chip from www.scantool.net
This looks more universal as the ELM chip converts to ASCII, should be easier if you have to program something too.

EOBD is more advanced than OBDII, but uses similar protocols. Also OBDIII is in design stage....
 
#76 ·
AJ, did you make up a circuit on a breadboard or stripboard or what? How about posting a pic up here to shock and awe us electronicaly minded people.
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top