ECU disconnected?

[Beatty, Robert]

-----Original Message-----
From: bludodger at att.net [mailto:bludodger at att.net]


I have been told (by PO) that the ECU was
disconnected by a tech. early in its life (some annoying
electrical miscommunication-go figure). Believe it or
not, I think
it was an audi tech. that did this. How do you think the
tech. would have disconnected the unit?- would just
pulling the relay do it? Do you think it is even worth
trying to get the ECU up and running? Have you ever
heard of similar situation with the ECU being
deactivated? I am pretty sure something is quirky with
the ECU---for instance the car does not run through the
autocheck blinking of all the different warning signs
when first turned on...it just reads OK. Funny enough,
the temp and oil autocheck do work though when there is
a "real problem" with the car. Does this make sense?

-
Blu
'88 80q--175,000mi.

I'm not 100% sure as this is an 80 instead of a type 44(5000/100/200), but
if the car runs then the ECU is most likely connected.  A type 44 would not
run at all with out it.  Rough idle is most COMMONLY caused by either a
vacuum leak of some sort or problem with plugs/wires/cap&rotor.  If you have
verfied all your hoses are in decent shape, no holes ect ect, then the next
thing to do is check your ignition system.  How new are the plugs and wires?
If they are old, replace them.  That very well could be your whole problem.
I had a rough idle problem with my 200tqa that was getting progressively
worse and I knew I had old wires, so as soon as I got around to it, I
replaced them and the stumble was gone.

As far as your Autocheck goes, if it goes to OK then everything is OK.  At
least, as far as its concerned.

Rob
86 5ktq
89 200tqa


>
>
> bludodger at att.net wrote:
> >
> > I am trying to solve my rough idle problems and have a
> > few questions. There is a distinct clicking (sounds
> > electrical) coming from what seems like the throttle
> > body when the car is at idle. It happens intermittently
> > and is quite clear (although I can't see the part that
> > is causing it). Is this a normal occurrence? Could the
> > clicking lead me to the solution?
>