Intermittent No-Move Complaint on a Series-Hybrid Bus Driveline
A series-hybrid transit bus intermittently refuses to move from a stop. The driver reports that after a long regen braking event on a downhill route, the bus will not accelerate for several seconds; the dash shows a driveline warning, then it clears and the bus drives normally. The bus has an electric drive motor coupled to a reduction gearbox and a final drive. There is no conventional transmission. The shop has retrieved an intermittent DTC for 'motor overspeed / torque derate' and a second code for 'inverter over-temperature.' Coolant level is correct. The reduction gearbox oil was changed recently to a non-OEM fluid by a subcontractor. The complaint happens more often on hot days and after long downhill runs.
1. Connect the symptoms and codes into a coherent failure story, and explain why the gearbox oil matters here.
Read the worked answer
Failure story:
- Long downhill regen events push energy back through the drive motor and inverter. If the inverter or motor cooling is marginal, the inverter over-temperature code sets and the controller derates torque - which the driver experiences as 'won't move' after the downhill run.
- The 'motor overspeed / torque derate' code can set during regen if the controller sees motor speed above the expected band for the commanded condition - often a speed-sensor or ratio mismatch issue rather than a true overspeed.
- The reduction gearbox oil matters because the wrong (non-OEM) fluid changes friction and heat transfer in the gearbox. Wrong fluid can increase drag and heat, and if the gearbox has an integral oil circuit or temperature sensor, it can push the system into derate sooner. It also affects the gearbox's contribution to the total driveline drag the controller sees.
Judgement: this is a thermal/derate and configuration problem, not a 'transmission won't engage' problem. The intermittent no-move is the controller protecting hardware, not a mechanical failure to transmit torque.
Do not chase the gearbox as the primary fault until cooling and fluid are corrected.
2. List the diagnostic steps you would take, in order, and state what result at each step would change your direction.
Read the worked answer
Ordered steps:
- Download freeze-frame data for both codes - motor speed, inverter temperature, coolant temperature, gearbox temperature, and derate flag at the moment of the event. If inverter temp is at the derate threshold, focus on cooling. If motor speed is the trigger, focus on speed sensing/ratio.
- Verify inverter and motor cooling - coolant flow, radiator fan operation, pump, and any coolant-to-oil heat exchanger. A restricted heat exchanger explains hot-day and downhill recurrence.
- Replace the non-OEM gearbox oil with the correct fluid and verify the level per OEM procedure. If gearbox temperature drops and derate events stop, the fluid was a contributor.
- Check motor speed sensor and resolver signal quality and the gearbox/final-drive ratio parameter in the controller. A ratio parameter mismatch explains a false overspeed code.
- Road test a repeated downhill regen cycle with a scan tool logging, and confirm no derate flag sets.
Judgement: fix cooling and fluid first because they are cheap, verifiable, and match the hot-day pattern. Only pursue speed-sensor or controller replacement if freeze-frame data points there. Avoid replacing the motor or inverter on an intermittent code without freeze-frame evidence.