TC/Slip dash ON after curb bang (new hub/wheel/ties/univ joint)... what am I missing?

Blink (a/k/a Flash) Codes – How to. | PriusChat

 

And I'm going to guess the wiring to the given sensor of the side that was compromised is in good shape and has no visible signs of any funny business from that sensor to its plug on up to the car? I just had to ask. And I'm guessing when you assemble this new bearing into the new hub you can see the speed ring that the sensor needs to access in order to make a read on the ring?

 

Yes you can't fool that That's right I remember reading that now in your post at all the wheel speed readings were spot on that is quite strange.

 

The car will feel unloved if you don't ask it why the slip light is on.

 

SLIP/TC 43 just means you should look at the ABS code too, and 45 just means you should look at the brake code too.

ABS 42 just means you should look at the brake code too.

Brake 36 just means you should look at the ABS code too.



So we've got SLIP/TC 66 (C1290, steering angle zero point seems weird), ABS 41 (C1241, low voltage arrived at the brake hardware), and BRAKE 94 (U0073, hey I'm having trouble talking to the yaw sensor or the steering angle sensor).

Also, there was TPMS 75 (C2175, problem with either the vehicle speed signal or the RSSI signal).

None of that pertains to anything right out at the hubs, where you might be thinking after a curb bang. Maybe the bang was hard enough to jostle some electrical connection supplying the brake ECU (it's on the master cylinder).

Because the C1241 means the brake system is getting low voltage (or at least got low voltage, at some point), that's worth looking into. Inadaquate power could explain communication signals getting messed up. It's simplest to start with the aux battery voltage itself, though it's possible for C1241 to be not about that, but about some wiring or connection bringing the voltage to the brake hardware. With a scan tool, you could get the C1241 freeze frame, with an INF code giving more details of what happened, and actual voltage readings from that instant.

The vehicle speed signal is generated by the brake ECU, so if the brake ECU is unhappy, that can explain the signal not showing up at the TPMS ECU.

The yaw/acceleration sensor and the steering angle sensor are both used by the traction control. The yaw/acceleration sensor is under the center console and the steering angle sensor is just below the steering wheel on the steering column shaft.

There's a procedure for learning the yaw/acceleration zero point. You make sure the car is parked somewhere with no forward/back or side-to-side tilt, and you say "ok that's zero" and the car says "ok got it".

There's no separate procedure to learn a steering angle zero point. Every time you drive, the car looks at what the steering angle sensor is saying when you're driving with no yaw and no wheel speed differences and says "ok, that'd have to be zero steering angle". But it sets C1290 if the value is too far off to believe. That could mean the yaw zero point is mislearned, or the steering wheel wasn't put on centered, or the front alignment is messed up. (Or it might result from being unable to talk to the yaw sensor or steering angle sensor.)

That's because it didn't actually want that procedure.

That can happen if you rely on something I posted six years ago but don't skim down the same thread to see if I corrected myself five years later.

The only code that actually means it wants that procedure (C1345, linear solenoid offset learning undone) would be 66 on the brake light. You didn't have that code. You did have 66 on a different light, but that's a different code.

In that earlier post where I mentioned seeing ABS 42 and TRAC 45 when that procedure was wanted, that was before we fully understood that ABS 42 and TRAC 45 just mean "hey look at the code flashing on your brake light", and of course they would be on then because C1345 flashes out 66 on the brake light. But the only code that really told a story was that one, and you haven't got it.

 

Some OBD-II readers are simpler than others. We do have a Gen 2-specific thread that compares a bunch of them and reports which ones can see more of the codes in a Prius:

Gen2 OBD2 app review | PriusChat

So far, it seems nobody has sent mr_guy_mann a Gen 3 to test on for a similar review. But the ones that worked well in the Gen 2 thread are probably good bets.

 

Yeah, the fortune cookies listed for trouble codes in different documents (or built into scan tools) sometimes look a little different, and they are never a complete source for what the code means. The one actually in the (2010 edition) repair manual says "Low Battery Positive Voltage", but of course the full description for that code and its detection conditions clarify that the voltage is being measured at the brake hardware, not at the battery, and one of the five possible INF codes refers to a voltage too high rather than too low.

And Gen 2 also had a C1241 code for its (electrically rather different) brake system, and the fortune cookie might have been a little different, and an app like OBDLink might not have all those variations programmed in.

I focused on the voltage-too-low possibility, given the number of times (zero) I've seen anybody's C1241 turn out to be because the voltage was too high.

There's a better source than me for all that information anyway:

Toyota Service Information and Where To Find It | PriusChat