Alfa Romeo Forum banner

1 - 9 of 9 Posts

·
Registered
Joined
·
1,369 Posts
Discussion Starter · #1 ·
Guys,

as some of you know I've replaced my 156 with a 159 but left the 156 standing too long and it now refuses to start...
After an ECU reset it will run fine but shuts down after say 15mins with various alarms, requiring pushing back home! it still feels fine when its running :confused: its random, it only shuts down on test drives! not when I drive it.

So:

how do I read the fault codes? tried to find a guide but have come up empty...

have a laptop, win7 64bit
OBD-II blue vagcom cable, which I've seen some people say they use (no switches on it)
multiecuscan free.
have set the cable to COM1 in the device manager

I launch multiecuscan
connect USB, connect to car.
turn key to MAR(ON)
click connect:
multiecuscan says unable to connect to ECU

Help needed, maybe a guide can be written off the back of this?

*car is a 1.6 petrol 156 2002 interior facelift, I just need to read the codes so I can replace the parts it thinks are wrong, I've never seen a fault like this either?!
 

·
Registered
Joined
·
937 Posts
You may need to 'up' the Latency time, it should be in the settings, I can't remember off hand, its either in the settings in MES or on device manager when you select the COM port (e.g. COM1, 2, 3 so on)

Sure its not just down to the battery, whats the voltage like after left all night?
 

·
Registered
Joined
·
30,262 Posts
Is it sure, that FREE version supports your ECU?
The ME7.3.1 ECU (which his 1.6TS will have) is supported by the free version.
 

·
Registered
Joined
·
1,369 Posts
Discussion Starter · #6 ·
the battery is fine, new, leave it disconnected while its out of action.

I'm at work so can't really read the user guide. hmm, actually...
The guide looked very generic though.
I just have too much on, I might have to fork up and pay an 'electrical specialist' to pop over and read the codes, then hopefully fix it with someone else! more £££ for a car I need to sell
 

·
Registered
Joined
·
1,369 Posts
Discussion Starter · #7 ·
aie... another weekend, and a couple of free hours...

So, I have checked that .NET framework 3.5 is on my laptop.
the vagcom kkl 409.1 cable does light up.
I've set latency to 1.

when scanning, the cable does now report back and pass the tests, with a max of 3ms difference!
BUT that's the only progress I've made!
Still can't connect to car! :cry: I think it says no response from ECU
I have had no luck googling this either, still googling, close to tears! this car should run fine, its tidier than my 159! when its working!
 

·
Registered
Joined
·
1,369 Posts
Discussion Starter · #9 ·
yes, the dash is lit up with my warning messages on the info screen and the flashing engine light.
there is currently a lot of clicking coming from the engine bay, whatever the fault is it causes constant electrical clicking, almost in time to the rapid blinking engine light.
and other random noises, such as occasional short buzzes from the ac unit (I think)

*I know the cable works, used to use it on the 2002 vw bora.
*its a non-switching cable, I have not soldered anything, I only want to access the ECU fault/error codes. not AC/Airbag ect.
maybe I should see if it works with the 159 2.4...
 
1 - 9 of 9 Posts
Top