Went to a mechanic they still don’t know what’s wrong (1984 Bronco 2 v6)

[Dirtman]

I didn't think the carbed 2.8 had an IAT sensor. It does have a very crude computer though so I don't know. But in any case I really don't think that would be causing the issue with it not starting after getting hot. That is a classic symptom of a bad TFI module.

 

[19Walt93]

The part is an ACT- air charge temperature sensor and I agree it wouldn't cause a no start. Put it back in, though.

 

[MadMax_636]

I bought this thing about a month ago and I was driving it and it just stopped working, it was a distributor cap that broke so I got it fixed, but now it doesn’t make it for more than a 20 minute drive without dying, i would drive And it would work fine then i would stop and if I stopped for a while it would shut off and won’t turn back on and if it did it would have almost no power and it would come in little sputs and then die out again ... if I let it sit for a day or two then it cranks up again just fine. It seems to be a problem when the engine gets a little hot but my gauge seems to be working fine

UPDATE:
Now it won’t turn on at all going to replace the tfi module then see if it changes anything

Switch it to Duraspark w/GM ignition module.

I had the same issue with it not starting or running for very long.

 

[85_Ranger4x4]

"A half trained monkey could figure it out with google in less than 5 minutes. If they cant figure out google can-bus is way out of their league." That's a cheap shot, google can come up with all kinds of info that may or may not fix the problem.

I googled "1984 Bronco II Dies Randomly" First reply on the first hit called out the TFI module.

1984 brono II dies randomly - Google Search

www.google.com

Charging an hour (or whatever) of diag and sending it on its way didn't fix the problem either.

I would think alldata or whatever would touch on it too. The typically crappy Chiltons manual for our '96 F-250 has an ignition troubleshooting section for the TFI system. IMO they didn't even try.

I literally do this for a living for trouble things that come in the shop, we repair 1930's to present farm equipment.

 

[MikeG]

"If a packet hits a pocket on a socket on a port....."

Yeah being a mechanic is different than say the 1930s.... but you still have to understand how the parts work together, and how to logically debug, as well as measure and test individual components. I would guess most mechanic 'training' these days isn't much of a step above off-shore tech support - read a code and order a replacement part, done, move to the next vehicle.

I've had vehicles go to "mechanics" and later figured out they were just GUESSING what was wrong, no logical decision tree or testing anything along the way.

Computers are no different, if you don't understand the fundamentals and especially if you don't isolate variables and TEST things, then no, you're just guessing. Or reading the tech support script.....