SteveCo
1000 Posts Club!
I had the battery go flat the other day (likely my fault), so disconnected it to recharge overnight. When I reconnected the battery, the car was showing a fault message about the suspension.

Everything else appeared normal, but when driving the car it was like riding in a unladen 5 ton truck - it was stiff to the point of jarring your fillings loose. Changing drive modes made no difference, the ride was the same.
So I would guess if the computer doesn't have direction otherwise, it defaults to full firm mode on the shocks - and a truly firm setting it is! It appears that either KIA or aftermarket ECU tuners would have the capability to stiffen up the shock settings substantially - the firmness in the car's Sport mode isn't even close to what I experienced.
As for the error, I checked the fuses and they all appeared fine - including the one for the suspension. All it took was a simple 5 minute drive through the service bay at the dealer this morning - they hooked up a tablet to the OBDII port under the dash and reset the computer, and everything was back to normal. They did say they'd never seen this particular error before - but I wasn't surprised about that.

Everything else appeared normal, but when driving the car it was like riding in a unladen 5 ton truck - it was stiff to the point of jarring your fillings loose. Changing drive modes made no difference, the ride was the same.
So I would guess if the computer doesn't have direction otherwise, it defaults to full firm mode on the shocks - and a truly firm setting it is! It appears that either KIA or aftermarket ECU tuners would have the capability to stiffen up the shock settings substantially - the firmness in the car's Sport mode isn't even close to what I experienced.
As for the error, I checked the fuses and they all appeared fine - including the one for the suspension. All it took was a simple 5 minute drive through the service bay at the dealer this morning - they hooked up a tablet to the OBDII port under the dash and reset the computer, and everything was back to normal. They did say they'd never seen this particular error before - but I wasn't surprised about that.
Last edited: