Pcm is not communicating

Thank you very much for helping me. The fuse was bad all fixed thank you.

First I have a 2002 Ford Windstar SE van, with a 3.8 liter motor. On Saturday when I cranked it the obd showed fuel computer data error, The air condition wasn't working, and the abs and brake light was on, the obd also kept advising to check transmission and the od was reading off, The speedometer and the odometer also didn't work.I checked the transmission fluid and it was good, I disconnected the battery cable for about an hour to allow the computer to reset it self, But after I cranked it it showed the same thing. Also when driving the van the overdrive is still working

Dear Maddawg

I also have the exact same problems with my 2002 Windstar. I called a Ford dealer, and they want $105 per module to diagnose (3 locations $315). They quoted a new pcm at $600 + $200 for labor. I don't have $1200 to blow on this van. However, if you can find a low cost certified mechanic, I found a place to buy pcms for $80 - $200. I have to have Ford diagnose the pcm for sure - I'll pay the $105 for the pcm only.

Does anyone have a solution?

I have the same problem with mine. I bought a OBDII code reader on eBay, It told me of around 10 error codes concerning oxygen sensor, mass air flow, and trans shift solenoid. With this reader I can only delete the error codes not reset them. I am sure there cant be as much wrong as the error codes say
there is.
If I only knew how to reset the computer in the van.

I had that problem with another ford, but similar pcm. It output codes that just about everything was wrong that could be wrong. No way every sensor in the whole car could be out. Buried deeply in all those codes was 'computer'. Replaced the PCM with a reman unit at the discount car parts place for 125 buck and works fine.

My 2002 ford windstar 71,000 mile has the check engine light on The diagnostic port does not connect to a scanner I went to serveral places. Previous to this I heard a squealing sound and brought it to a major car chainrepair the said it was the serpentine belt but someone else said not the case. Has anyone run into this problem. I am thinking to check the fuses. Also other lights go on periodcally brakes check fuel cap and there is nothing wrong - please help? Thank you

Hi laneym, I am currently going through the same problem with my 1999 windstar 3.0. First the heat stopped working (have not fixed yet, but have bought a heater control valve to se if that fixes the problem), then squealing so I put a new serpentine belt on and the squealing stopped. Now I am going through a check engine light on with vibrations and my diagnostic port does not work (AutoZone says I have a short or something somewhere in my dash). Plus my ABS light comes on every now and then, but not very often.

Did you find out what was the problem with your Windstar? Mine may be similiar to yours.

Any help would be much appreciated

I have a 99 Winstar v6 3.8 with ABS TC.

Daughter was driving and the engine lost power ( no noises just no power ) comupter display said Charge System Data Error, Fuel Computer Data Error.

Fuel on the rail, No spark, Replaced Crank Postion Sensor and Cam Position Sensor, still no spark, engine just rotates.

Code Scanner cannot communicate, all fuses, diodes and relays under the hood test good.

Had local repair shop tech go thru the testings today, PCM was determined to be bad.

Dealership wants over $600. For new PCM.

Local parts shops list reman'd for $150 to $250,
but no available stock.

In the Rochester NY area, any suggestions for used parts or reman parts houses for hard to get parts ( any where )?

Thanks.

Plugged in an OBD II scanner to check error -- can't read error code (already checked all fuses -- all are ok -- included cigerette lighter)

Has anyone ever had this problem? My engine light is on, but the dealer cannot read the codes. Same thing at Autozone. No error or any communication with the reader. Currently at 83K.

Any suggestions where to start looking?

I'm all set - someone on another forum answered pretty quick. It was fuse #17.