
So seemed to be that open loop was fine and closed loop was not. Sometimes it would hesitate or stall at idle (different than what you described), sometimes feathering the gas, sometimes at cruise, never at WOT.

Symptoms were very similar to what you mentioned above, the only exception being that idle was not exempt from issues. Allowed a mechanic to throw parts at it for a little while before saying screw it, I'm going to diagnose properly and fix it myself. I have spent months working on a very similar issue in my 95 RMW w/ 165k. If your diaphragm reverts to its original position (closed). Then put your finger on the vacuum opening releasing the diaphragm. Though the openings, stick your thumbs in and push the diaphragm back. A super simple test that ever body can do, in a matter of minutes. Making the problem get worse and worse.Ĭonclusion: This problem is one that could throw the best mechanic for a loop, and can get quite expensive and frustrating to fix. So, as soon as the EGR kicks in, it creates a top end vacuum leak (lean fuel mixture) and throwers the CPU out of wack, as it's trying to compensate by dumping more fuel until the leak gets so bad that the CPU can no longer compensate. That is why it passed the vacuum test as it was done on idle. The problem is that the EGR is only solicited in a closed loop environment, and under partial throttle. It I due to a defective EGR valve at the diaphragm. But oddly enough, It passes.Īnswer: It is a vacuum problem. Bad compression? Does not smoke, idles fine and still beats the pants off of a civic. Bad fuel pump?! Idles fine and still runs like a demon at wot. If you can start your car no problem on super damp mornings, then no.

Many people will go for the bad opti and wiring. Troubleshooting: Ok, so not many leads to go on. When hot (closed loop) it will start to stutter/hesitate when feathering the throttle at light acceleration and on highway (cruise). Which btw is no longer supported.Symptoms: Fuel efficiency decrease. Been there and done that with the Alex Peper OBD2 diagnostic package. Running a Group Purchase here is a labor of love. I am willing to bet TC would participate in a group purchase, but I can only guess. You may want to trade the hours you've spent on this for a licensed copy of his OBD1 Tuner. If there is a COM problem and you are running XP or even Win7 you might need to change a couple of comm port parameters.
#Datamaster obd1 software windows 10#
All of my software has worked fine on all these OS's up to including now my Windows 10 laptop.

If so what operating system ( XP, Win7 etc? ). Just curious atlantadan, if you are using a straight up RS-232 port. If you are using an FTDI chipset USB converter, the EEHack website has a recommended tweak for you here: Most every implementation that used any sort of a USB adapter that 'converted' it to RS-232 had some subtle issues IF it connected at all. it has been pretty straight forward to get connected when you are using a genuine RS-232 port on a laptop (or desktop). I have been using TunerCat and DataMaster OBD1 for 12 years or more. The EEHacks website at: fbodytech ? 94-95 GM LT1 Tuning/Hacking Website says they need B-Body owners to validate their communications.
