At my wit's end now. Code 13 keeps coming back on my 88 Dodge Caravan 3.0 litre! Dealer replaced the engine controller which kept the car trouble free for a few months only. Then exactly the same problem came back. It was damp but well above freezing here in Vancouver, British Columbia when the trouble started again.. Symptoms: Engine starts and runs normally for 5 seconds, then dies with Check Engine light on. Then after warmup, it runs at a high idle, maybe 1800 rpm and drives OK, unless starting on a hill, at which times it flat spots and takes a floored pedal to go but it does go. Codes are 12, 13, 55. Code 13 means "MAP sensor no change from start to run". Last week we poked around and replaced the MAP sensor with a new one. That wasn't it. Pulled the 60-pin connector from the "computer" (engine controller) and checked continuity from the MAP connector to the 60-pin connector. Then we put it back together. At the time we checked vaccum with a gauge - solid at 20 inches. Removed each vacuum line to check as well. Had the battery terminal off to reset the computer each time. It worked for about a week but Code 13 came back. Two weeks ago I looked at it again. No gunk in the newly replaced MAP vacuum hose. No opens in the three wires all the way to the 60-pin connector. Used a round file to carefully burnish the contacts in the connector. Did not worry about corrosion on the 3-month old engine controller. To check the MAP voltage, I even soldered three test points right into the cable harness near the engine controller to watch the MAP voltage. With ignition on and engine off, I can see the effect of blowing (1 volt change) and sucking (three volt change) into the vacuum port of the MAP sensor so it seems to work. With ignition on and engine on, I can see the swing in the MAP voltage from +5 to +1.5 volts from engine off to engine on. BUT even with the voltage swing, the same problem comes up: engine dies after 5 seconds and CHECK ENGINE light comes on with a Code 13 read-out. I had the big connector on and off about ten times that day. Could the code 13 be bogus and triggered by another condition? Anyone seen this kind of persistence of Code 13 before? I may have to give up so would be grateful for suggestions.