Puffwagon

I haven't really played with them much. I did change something years ago in hp tuners but it was so long ago I can't remember what happened. It should be fairly easy to tune in the driveway. Once it's warmed up, it'll speed things up while tuning to send it into closed loop after 5 seconds, so you're not waiting around for it each time you reflash.

Go into the editor and type O2 bias into the search bar.

Always good when stuff works out.

Ignore decel fuel data.

If you wanted to be safe, pull 4 degrees of timing from the whole borderline knock map. Make the entire base fuel table 0.82 up to 3000rpm and 0.75 from 3000rpm onward. Put 5 litres of E85 into a full tank of 98 for extra protection. The knock sensors should do their thing anyway, if they are functional. This is a very basic way of approaching it and I don't recommend anyone tune like this. That being said if you're gonna go drifting in an untuned car this is better than nothing by a long shot. I assume you already changed the tmap and correlating tune variables.

Is it tuned with PCMTec?

I've spoken to pcmtec support and they are currently fixing the error message I mentioned. I also told Scott about the missing zf parameters so I think there will be a fix for that coming fairly soon.

Ok I've sent the editor logs and the tec file. Worth noting it happens with every file, not just the one I was referring to. I use 2 laptops for tuning and the older one doesn't display the zf parameters. Old is Toshiba Satellite L300 and new one a Acer Nitro 5 2018 model.

I just did a full read of my 2006 territory and could not see the zf parameters on my laptop. I emailed the file to myself and opened it on my desktop and the zf parameters were there. Somewhat unrelated I got a fatal error when opening anything on my laptop that said I could save the file but not edit it.

Nah mate you do you

Did you change auF0296 to -5psi?

Eh I wasn't going to say anything but you guys were overthinking it by a nautical mile. It's a very simple thing to do once you know how.

Fair enough, I see the logic and playing with the pid controls will probably help fine tune it after the wgdc table and other setting are correct. Leave the underboost value over 80% to keep it spooling as quick as it used to. The overboost value can be doubled (still a negative number obviously) or slightly more as it's got a very slim margin to start with. This may be the majority of your issue. Get the wgdc table slightly under the boost level you want to run, it works better that way. I've done all those mods you've done and have never had to back off the underboost duty. In any case there's nothing wrong with playing with stuff to work it out yourself, it's encouraged providing you kinda know what you're doing, which you do.

That will make it spool up slowly and isn't how you should fix it. Yeah it works but there are better ways to do it that don't involve touching the underboost value or the pid control. Try other stuff, you're very close and I'm sure you will get it working properly eventually.

In my experience virtual dyno lines up with a real dyno with 6 smoothing.

Changing the shift points is what you should be doing but usually a rev limit change by a few hundred rpm does the trick. A quick and easy way to change the shift points is to go through all the shift maps except 27, and change the whole map by a percentage. It's not the perfect way of doing it but it'll give you an idea of what the box is going to do. You'll find this stuff in "ZF Shift \Lock Schedule" Edit: That's where it is in the zf6 file, I haven't looked at the 5 speed file to confirm.

Sure, I would. I only suggested it to avoid hitting the limiter in auto mode, not to use more rpm in day to day use. When you're flooring it you should be shifting manually and with practice you won't hit the limiter. Hitting the limiter is asking for an oil pump failure so take care to avoid it where possible.

Raise the rev limiter by 200rpm.

Yep no worries

I've had this happen plenty of times but not much lately. It seems to happen when the logger has been running for a long time and also when saving runs but not restarting the logger. Anyhow that's my anecdotal version, I'd have to get logging again to see if I can replicate it. Should be a couple of weeks 😉

You posted two images from hp tuners, both of the axis in the second image has been changed. There isn't any point going into the who, how and why of it. Just multiply the hp tuners X axis by 7.56 and copy those numbers to the pcmtec X axis. Change the pcmtec Y axis to suit the second hp tuners image. Then put the numbers you want into the table.

Two degrees of knock retard shown in the log.

You've changed the scaling in hp tuners so apply that same scaling to pcmtec. Then chuck in the numbers in the table that you want to trial, they are the same value in both programs so the only difference here is scaling.

You can let them go to 2.0 on 98 before it's too much.