
Originally Posted by
MetroMPG
Funny: I've gotten the ABS/Traction control freakout when I was idling the car in gear on jack stands to "machine" rusty rotors. But that problem clears itself the next time you drive the car. Like within half a block.
---
I've had a ScanGauge-II plugged into this car without issue, as I did in Mirage #1 and #2. That said, the first thing I did when I saw the dash light up was yank it out after clearing the code. And then problem returned multiple times with it disconnected.
That said, it was really hot yesterday, and the SG was sitting on the dash in direct sun. That made me wonder if it got hot enough to somehow malfunction and piss off OBD-II. But I kinda doubt it. The SG looked to be working normally.
---
I'm taking the car on a ~120 km round trip today with the wheel/tire combo from Mirage #2 installed (which caused zero ECM freakouts, and which appeared to be OK last night in a brief test drive). If it's uneventful, I'll swap the smaller rear tires back on when I get home and see if that triggers it again. If it does, then I have the definitive answer.
Gotcha. I'll go with mismatched tires is causing your problems. For now.
Weird that mismatching tires would kill the power steering like that.
But a burnt out brake light bulb can make these things drive like pooh and throw abs/trac lights so anything is possible.
__________________________________________
View my fuel log 2014 Mirage SE wussie cvt edition. 1.2 automatic: 37.7 mpg (US) ... 16.0 km/L ... 6.2 L/100 km ... 45.3 mpg (Imp)