New Holland ENG 3274 – Engine ECU: Fuel Low Pressure Sensor Dynamic Plausibility Test - Above Map

The engine control system has detected that the reading from the fuel low-pressure sensor is dynamically implausible because it is registering a pressure value that is higher than the expected parameters (the "map" value) for the current engine operating conditions.

• T8.xxx Series
• CR9090
• CX8080 Elevation
• CX8090 Elevation
• Magnum 235 - 340 (Series 4)

1. 1

   Connect a diagnostic tool (e.g., CNH EST) to read the live data from the Fuel Low Pressure Sensor

2. 2

   Perform an idle test: start the engine and compare the diagnostic tool pressure reading to a manual mechanical pressure gauge installed in the low-pressure fuel circuit

3. 3

   Perform a full speed test: increase engine speed to maximum and record readings (low-side fuel pressure should be a minimum of 5 bar / 72 psi)

4. 4

   Visually inspect the fuel system for excessive air bubbles while running tests, as air can cause erratic pressure spikes

5. 5

   Inspect the wiring harness and connector at the fuel low-pressure sensor for any shorts to voltage that could artificially drive the sensor signal high

1. 1

   Analyze the Test Results

   If the mechanical gauge shows normal pressure but the diagnostic tool shows an abnormally high reading (above the map), the Fuel Low Pressure Sensor has failed internally and must be replaced. If the mechanical gauge also shows abnormally high pressure, the sensor is working correctly. You must inspect the fuel return lines for kinks/restrictions or check the low-pressure fuel regulator/pump for a mechanical failure causing a pressure spike.

2. 2

   Replace the Sensor

   If the sensor is deemed faulty, depressurize the fuel system, disconnect the electrical harness, and unthread the old sensor. Install the new sensor and torque to OEM specifications.

3. 3

   Clear Codes

   Reconnect the diagnostic tool and clear the ENG 3274 fault code from the EDC memory.

4. 4

   Verify Repair

   Run the engine through a full operating cycle (idle to full throttle) to ensure the code does not return and the live data matches expected map values.