adjat84th
Veteran Member
Usually I wouldn't bother logging anything unless you're able to do it in 4th gear (even 3rd would be ok). The load just isn't there in 1st gear to get much meaningful data, and it happens very quickly. That said, obviously you want to fix that large gap between requested and actual rail pressure when you start pushing the pedal down. Also, don't worry about lambda until you're able to do fully floored 3rd/4th gear pulls.Quick and dirty log pulled. Only pulled in 1st gear on a very local street, trying to not annoy the neighbors. I added lambda and tried to record multiple runs, so I think the log is a mess. As before, at part throttle, it doesn't trigger limp mode. The last pull definitely triggered it, but much higher up than I expect, now somewhere near 4k. What isn't clear to me is why it triggered- suddenly the actual fuel rail pressure and the lambda begin dropping, but that's before there's a spike in the nominal quantity. The ITT keeps rising, though- is that normal for there to be a lag? Looking at the timestamps it's less time than I expected, so I guess that's normal. I tried to use a steady throttle application to avoid creating transients.
Log #828882
I wouldn't jump to any conclusion about a hardware issue until you've gotten some updated files to try out, it's very easy to think you have an issue when it's actually in the tuning so just wait till you have new files.
As for the 2700bar rail sensor (stock CUAA sensor BTW), you don't need it at the moment and would only be an additional variable thrown into the troubleshooting process. It's not the "adaptation" for it, it's about knowing where the map lives in the ECU to change the linearization values. The stocker measures 2200bar at 5v, whereas the CUAA reads 2700bar at 5v. The only purpose that it serves as an upgrade, is to be able to push up the rail pressure thus injecting more fuel for the same injection duration.
