Engine: 1GD-FTV
Evidence scope: engine family verified by Toyota; emissions and calibration vary by market/model year
ENGINE FAMILY DOSSIER
Toyota/Lexus GD-FTV Engine Family
GD-FTV family fuel architecture, cylinder layout, displacement class, application scope and measurement-led diagnostic framework.
What concrete information can you get from this page?
Verified application example: 1GD-FTV
VERIFIED FACTModel / system fact
Toyota explicitly names the 2026 Japan-market Hilux engine as a 2.8-litre direct-injection clean diesel 1GD-FTV and pairs it with a six-speed automatic.
FAULT SEPARATIONWhen a symptom appears
For low rail pressure, capture low-side supply, rail target/actual and injector corrections at the same load.
FIRST MEASUREMENTBefore replacing parts
Where the service procedure permits, verify electronic fuel data with an independent low-side measurement.
Primary source: Toyota Global – 2026 Hilux Japan, 1GD-FTV
Engine identity
- Manufacturer group
- Toyota/Lexus
- Engine family
- GD-FTV
- Fuel / energy architecture
- Turbo diesel
- Cylinder layout
- 4
- Displacement class
- 2393-2755 cc
- Vehicle scope
- pickup suv van
GD-FTV; diesel_turbo; 4 cylinder/layout; 2393-2755 cc class
What to verify before ordering parts
- Do not treat the family name and sub-code as identical; separate production period and market variant.
- Emissions level, turbo/injection hardware and sensor/actuator generation can vary inside one family.
- Transmission, hybrid system, ECU software and vehicle class can change the service procedure.
Diagnostic approach
Narrow faults by combining mechanical condition, air/fuel flow, pressure, temperature, lubrication, electrical supply and ECU commands rather than using the DTC label alone. Comparing loaded live data with idle measurements is particularly valuable for intermittent and performance faults.
Diesel / heavy-duty chain
Treat common-rail pressure, low-pressure supply, turbo air path, EGR, DPF/SCR and engine protection/derate behaviour as one interacting chain. Aftertreatment faults can affect torque request and field performance.
Measurement sequence
- Confirm exact engine code and application by VIN/model year/market.
- Check power supply and ECU communication.
- Capture air, fuel/energy, temperature and lubrication data at the same load.
- Compare commanded values with physical result.
- Verify under the same load after repair.
Source-verified powertrain relationships
No curated engine-transmission relationship is present in the source graph for this family yet. Exact fitment is not inferred.
OEM EVIDENCE DOSSIER
Verified technical facts and application boundary
- Toyota explicitly names the 2026 Japan-market Hilux engine as a 2.8-litre direct-injection clean diesel 1GD-FTV and pairs it with a six-speed automatic. [S1]
- Toyota lists 1GD-FTV in Land Cruiser 250 as a 2.8-litre inline-four direct-injection turbo with Direct Shift-8AT. [S2]
- Toyota Europe’s 2.8 GD technical description documents common-rail injection, variable-nozzle turbo, water-cooled EGR and SCR architecture; those emissions details are scoped to the cited European application. [S3]
Verified application matches
The matches below are published only within the stated market, model-year and evidence scope. Fitment is not extrapolated to uncited variants.
System architecture and component relationships
- Diagnostic layers include low/high-pressure common rail, VNT air path, EGR, DPF/SCR and engine torque management.
- Because emissions hardware can vary by market, do not assume SCR/DPF equipment before VIN/market confirmation.
- For automatic-transmission complaints, separate engine derate/torque limiting from gearbox ratio/slip evidence.
DTC / SPN-FMI / symptom discrimination map
- For low rail pressure, capture low-side supply, rail target/actual and injector corrections at the same load.
- For low boost, combine VNT command, boost target/actual, MAF and air-path leak/restriction tests.
- For aftertreatment faults, confirm the actual vehicle equipment first, then sequence EGT/differential-pressure/NOx/urea data only for the installed system.
Measurement and diagnostic strategy
- Where the service procedure permits, verify electronic fuel data with an independent low-side measurement.
- Capture battery/cranking voltage and ECU supply drop so low voltage is not mistaken for a fuel-system fault.
- After repair, recheck rail/boost deviation and derate state at comparable engine temperature and load.
Exact pinouts, torque values, pressure thresholds or service limits are published only when explicitly verified by the applicable OEM service source.
Evidence provenance and primary sources
- Toyota Global – 2026 Hilux Japan, 1GD-FTV · OEM-primary · 2026-08-15
- Toyota Global – Land Cruiser 250, 1GD-FTV · OEM-primary · 2026-08-15
- Toyota Europe – New Land Cruiser 2.8 GD technical description · OEM-primary · 2026-08-15
Architecture evidence package
- Fuel path is separated into low-side supply → high-pressure pump → rail → injectors; air path into MAF/MAP → turbo control → intake manifold.
- On turbo-petrol architecture, load calculation, boost target/actual, lambda/fuel trim, ignition and knock control are compared in the same event window.
Live data to capture for this family
- Freeze frame: first/last fault time, RPM, load, vehicle speed, system voltage, core temperatures and companion DTCs.
- Live data: rail target/actual, low-side supply where supported, MAF/MAP, boost target/actual, EGR command/feedback.
- Aftertreatment: DPF differential pressure, soot/ash calculations, EGT chain, NOx in/out and SCR/DEF dosing enable.
- Live data: calculated load, MAP/boost target-actual, throttle angle, lambda/O2, STFT/LTFT, ignition advance and knock retard.
Engine measurement chain
- 1) Match vehicle/generation/market/powertrain/driveline identity to the source record; family name alone is not fitment evidence.
- 2) Preserve freeze frame and companion DTCs before clearing; make the first-fault condition reproducible.
- 3) Verify power/ground and network communication under load; do not decide from key-on static measurement alone.
- 4) Compare commanded air/fuel/pressure with an independent physical result; separate sensor bias from real performance loss.
- 6) After repair, recreate the same load/temperature and verify DTC state, live-data deviation and user symptom together.
This section is an architecture-safe diagnostic layer derived from family identity; application-specific OEM limits are shown only when a verified evidence dossier exists.
Engine root-cause split
- If rail pressure is low, separate low-side supply from high-pressure generation: when physical low-side supply is healthy but rail cannot follow target, regulation/pump/injector-leakage branches gain weight.
- For low boost, do not jump to turbo replacement: separate MAF/MAP plausibility, charge leak, VGT/wastegate command and exhaust backpressure at the same load point.
- On lean/misfire/boost complaints, align fuel trim, lambda, ignition retard and boost deviation on one time base to separate air leak, fuel-delivery and ignition causes.
Related technical centers
Sources & freshness
Sources & freshness
Exact technical values, prices and failure rates are not invented without verified vehicle/manufacturer evidence.