| Machine | John Deere 1270G (harvester) |
|---|---|
| ECU | John Deere Phoenix L33 |
| Solution | Stage 1 + AdBlue/SCR off* |
| Read / write | OBD |
The situation
A harvester like the 1270G works under load all day: the engine drives the hydraulics for crane and harvester head, and both pull hard at the same moment when a heavy stem is felled and processed. Usable torque in that situation decides how smoothly the head feeds and how many cubic metres the shift ends with.
The second factor is availability. Out in the stand, an AdBlue fault is more than a warning light – the derate strategy can cut power far from the next workshop and the next DEF supply.
What we did
The Phoenix L33 belongs to the current generation of John Deere engine controllers. On this machine it was read via OBD and the file developed for the exact software version – the ECU stayed in the machine, no bench work.
- Stage 1: injection quantity, rail pressure and boost adjusted within the limits of the stock hardware – more torque in the rpm range where the hydraulic pumps work.
- AdBlue/SCR: dosing and level monitoring deactivated in software, related DTCs and the derate strategy handled.
Checksum corrected and the file written back via OBD.
The result
More pull at the head when crane and feed work at the same time, no AdBlue warnings and no derate interrupting the shift. For the contractor this means a harvester that is set by the timber, not by the after-treatment. Files for the Phoenix L33 are developed from the original read of each machine – the software version decides what the file looks like.
Need a file for this machine?
Byte Performance develops files individually for engine, ECU and software version. Dealers get access to the full database, dealer pricing and direct engineer support. Become a dealer or ask about a machine.
* Emission-related solutions (DPF, EGR, AdBlue/SCR) are intended for off-road, agricultural, export and motorsport use only, where permitted by local law. The operator is responsible for legal use in their market.
