Fault Code 34: Weak Battery Voltage Supply

J1587: MID 130 PID 168 FMI 14

J1939: SA 3 SPN 168 FMI 14

Overview

Fault Code 34 sets Active if battery voltage to the TECU falls below 9 volts for more than 10 seconds.

Detection

The TECU monitors the battery voltage supplied to the TECU after completing the power-up sequence. Fault Code 34 sets Active if battery voltage to the TECU falls below 9 volts for more than 10 seconds. Fault Code 33, Low Battery Voltage Supply, represents a more severe drop in battery voltage than Fault Code 34.

Conditions to Set Fault Code Active

FMI 14 – Special Instructions: TECU monitors the battery voltage of the vehicle. If the voltage falls below 9 volts for more than 10 seconds, the fault sets Active.

Fallback

FMI 14

  • Engine may not crank.
  • Transmission may not engage a gear from neutral.
  • Transmission may not attempt to shift.
  • Until the fault becomes Inactive, driver may have to shut off engine with transmission in gear.

Conditions to Set Fault Code Inactive

FMI 14: Battery voltage stays at 9 volts or greater for at least 20 seconds.

Possible Causes

FMI 14

  • Vehicle Power Supply
    • Wiring shorted to ground, shorted to power or open
    • Bent, spread, corroded or loose terminals
    • In-line fuse corrosion, loose connection or blown fuse
  • Vehicle Batteries
    • Internal failure
  • Vehicle Charging System
    • Charging system failed
  • TECU
    • Internal failure

Component Identification

_Graphics/LineArt/TRTS0940_FC33-34-37_ID1.png

1. 38-Way Vehicle Harness Connector

2. Transmission Electronic Control Unit (TECU)

Fault Code 34: Troubleshooting

A
Purpose:Inspect the batteries, in-line fuse and power and ground supplies to the TECU.
  1. Key off.

    Notice
    Notice
    Allow TECU to perform a complete power-down sequence before proceeding.
  2. Measure voltage across all batteries. Record voltage in the table.

  3. Inspect Starter, battery terminals and transmission 30-amp In-line Fuse Holder Connections for corrosion, loose terminals and bent or spread pins.

  • If any issue is found with connectors, refer to OEM guidelines for repair or replacement of Vehicle Harness wiring. Go to Step V

  • If corrosion or other damage is visible at the battery terminals, refer to OEM guidelines for repair or replacement of batteries. Go to Step V

  • If no issues are found, Go to Step B

Battery Voltage
B
Purpose:Load test each vehicle battery.
  1. Key off.

  2. Load test each vehicle battery per OEM specifications. Record reading(s) in table.

  • If all batteries pass the Load Test, Go to Step C

  • If any battery does not pass the Load Test, refer to OEM guidelines for repair or replacement of batteries. Go to Step V

BatteryVoltage DropLoad Test Status (Pass/Fail)
1
2
3
4
5
C
Purpose:Check for Active or Inactive fault codes.
  1. Record the transmission fault codes, FMIs, occurrences, and timestamps from the Service Activity Report created during the Diagnostic Procedure.

D
Purpose:Use Product Diagnostic (PD) Mode to locate intermittent failures.
  1. Set parking brake and chock wheels.

  2. Place transmission in PD Mode. See more about Product Diagnostic (PD) Mode.

    Note: Transmission does not enter PD Mode when Active fault codes exist.

    _Common/_Graphics/PD_GearDisplay.png
  3. Wiggle wiring and connectors of the Vehicle Harness from the batteries to the TECU. Look for signs of pinched or chafed wiring. Verify all connections are clean and tight.

  4. Exit PD Mode by powering down.

    Notice
    Allow 2–3 minutes for the TECU to perform a complete power-down sequence before proceeding.
  • If any fault sets Active while wiggling the Vehicle Harness, refer to OEM guidelines for repair or replacement of Vehicle Harness wiring. Go to Step V

  • If no fault codes set Active, Go to Step E

E
Purpose:Verify continuity of battery supply to TECU.
  1. Key off.

  2. Disconnect 38-Way Vehicle Harness Connector from TECU.

  3. Inspect connector body for corrosion, damage, loose, spread or bent terminals.

  4. Disconnect Battery Positive (+) and Negative (-) connections.

  5. Measure resistance between 38-Way Connector Pin 38 and Battery Positive (+) connection. Record reading(s) in table.

    _Graphics/LineArt/TRTS0940_FC34_VPin38andBatteryPlus.png
  6. Measure resistance between 38-Way Connector Pin 36 and Battery Negative (-) connection. Record reading(s) in table.

    _Graphics/LineArt/TRTS0940_FC34_VPin36andBatteryGround.png
  7. Compare reading(s) in table.

  • If readings are in range, no problem was identified. Test complete. If additional troubleshooting is required, contact the OEM for additional diagnosis of the Vehicle Power Supply Harness. Go to Step V

  • If readings are out of range, repair or replace damaged wiring per OEM guidelines. Go to Step V

PinsResistance RangeResistance
38 to Battery Positive (+)0.0–0.3 ohms
36 to Battery Negative (-)0.0–0.3 ohms
F
Purpose:Verify battery voltage at the TECU.
  1. Key off.

  2. Disconnect 38-Way Vehicle Harness Connector from TECU.

  3. Inspect connector body for corrosion, damage, loose, spread or bent terminals.

  4. Key on with engine off.

  5. Measure voltage between 38-Way Connector Pin 38 and Pin 36. Record reading(s) in table.

    _Graphics/LineArt/TRTS0940_FC34_VPin36andPin38.png
  6. Compare reading(s) in table.

  • If readings are in range, Go to Step G

  • If readings are out of range, refer to OEM guidelines for repair or replacement of 38-Way Vehicle Harness. Go to Step V

PinsVoltage RangeVoltage
38 to 36Within 1.2 V of Battery Voltage (Step A)
G
Purpose:Verify fault code status.
  1. Key off.

  2. Reconnect all connectors and verify that all components are properly installed.

  3. Key on with engine off.

  4. Connect ServiceRanger and check fault codes.

V
Purpose:Verify repair.
  1. Key off.

  2. Reconnect all connectors and verify that all components are properly installed.

  3. Key on with engine off.

  4. Clear fault codes using ServiceRanger.

  5. Drive vehicle and attempt to reset the code or duplicate the previous complaint.

  6. Check for fault codes using ServiceRanger.