Reading his initial timeline, the vehicle DID work properly after the collision. I get what you're saying, but there's no causality shown here. It could be water damage but no one has shown any kind of likelihood for that. It could be that the windshield installer screwed something up under the hood. It could be a rodent. It could be just random deterioration of something. If I were the insurance company I would want to establish that this was covered damage before I paid.I think I'd politely let Safeco (decent company, btw) know in no uncertain terms that your van had NONE of these problems with the MIL or this actuator before the collision, regardless of whether your wife backed into somebody, lightning struck the car, or whatever. The point is, the vehicle has not worked properly since the collision, and "I'm paying you my hard earned $$ in premiums. This is one of the reasons we carry insurance" is pretty much how I'd word it to them, calmly of course.
I repair motorcycles. If I flush someone's brakes and an ABS sensor fails while the bike is in my shop it's awkward but it's not anything I did. Even if I flush the brakes and a hose goes bad or debris clogs the ABS module it's not on me; it's a pre-existing fault rooted in lack of previous maintenance. And if I flush those brakes and a fork seal starts leaking on the test ride, it's completely unrelated.
If I saw communication issues between many different modules, I wouldn't be assuming that replacing a certain module would fix the issue unless the issues all went away when that one module was removed.
Does that mean he can't run tests on the skid module? If the skid control module isn't working because (for instance) it's not receiving steering angle info from the BCM, then it's not a bad skid module. I don't know these particular systems so I can't say.1) Skid control actuator won't function. A new one is 1 thousand.
2) Can’t run tests.