Roland@pcmtec

This is fantastic guys. Good old R&D and putting it up to share helps everyone get better results. If you guys think you have it categorically figured out I'll sticky a howto post on it as its a common question. I've never actually had access to a ZF 6 speed to do any testing on these gearboxes so I haven't been able to weigh in at all.

Old thread I see!

Some of the workshops might be willing to sell you a base file or do a remote tune. https://www.pcmtec.com/workshops

We replied to your support ticket. When you were running your low boost tune with 0% duty cycle, you were seeing boost creep to 18psi by redline. Either the gate is not working properly or the spring preload/base pressure is too high. If you get boost creep to 18psi on 0% duty cycle, you'll never be able to control a flat desired boost at this level, it will always spike. Then your high boost run, the extra DC brings the turbo to 18psi sooner, but it cannot drop it below 18psi at redline. You've also disabled the overboost action (WG OL OBOOST) as its reporting false. However the DTC warning (no action associated to it) is showing true WG OBOOST, hence even though overboost is occurring its not reducing the duty cycle to 0, however even if you did fix this as per the first log it would unlikely drop the boost by any measurable amount. This is also why your desired boost drops dramatically. So there are several issues, one which is mechanical and then another which is tune related (eg the overboost not dropping duty cycle to 0%). It might not be obvious if you are using the compare function (as it will show the axis of your file, not his) but he has boost by gear enabled. So whilst what you said is true with the standard boost tables, with boost by gear its not.

Put the tune back to stock to rule out a mechanical issue in the first instance.

In BF/FG you can use "rapid packet" logging which allows 16 items to be logged at high speed (they are broadcast so we don't have to keep asking for the values). When logging more than 16x items they are logged at single poll rate. Eg the editor asks for a value, it gets that value, it asks for the next value, it gets that value. So there is a lot of overhead. The more items you have to request, the more time before you wrap around and start again, hence a slower update rate. Anything that is selected as "high priority" is logged as rapid packet (if its a available). You can select high priority via right clicking. We also sniff various broadcast packets eg ECT and RPM from standard canbus messages, these are "Free" and we don't have to use a rapid packet entry or a single rate poll slot for these. BA lacks rapid packet mode, it also lacks many of the broadcast messages that we sniff and finally the single rate polls are also slightly slower. So all round the logging is much slower on a BA. What should you remove? Anything that you aren't interested in logging. Eg if you are looking at LTFT, you probably don't need to log spark values and vice versa.

Looking at that log your poll rate is very low (as its a BA with no rapid packet). I recommend removing some items that you don't need from the layout to increase the resolution.

OBD MX (or other ELM327 with speed selection) is needed for the low speed busses. Tactrix works for the high speed can only. @Billcan you confirm if the ABS programming can be done via HS can? I haven't done it in a while.

I think even if they x10 their prices, people would happily pay for it. Imagine how much better it would be with that extra income as well, it would buy them extra devs/support people. Some people pay $10k for scan tools, so I think $70 for a life long license is seriously under valuing what they offer.

Most of them are professional scan tool packages with 5 figure yearly subscription costs and come with physical hardware. I honestly don't know how the Forscan guys do it for the pittance they charge.

Thanks for posting a follow up with what you did. This really helps others out when they are searching. To make it more aggressive set your min spark to -25 and set the blk spark at your limit to step change to this. Or you can set up the torque reduction to use spark retard and do this automatically (a little more complicated). Read the torque requestors launch control thread for a full walk through of how the reduction layers work. Datalog your spark when doing this to confirm.

Make sure you replaced the alternator with a smart alternator if it was originally one and vice versa if not. If you installed a smart alternator in a BA then you can apparently tie the LIN line (or maybe some other line?) to ground and it will function as a non smart alternator. The opposite is not true I don't believe.

Could you include your tec file and a data log showing torque source and throttle source in it.

Might need to give us some more information...

Thats exactly how I'd recommend doing it. Use 5v as on so if it fails by losing power it goes to 0v fail safe.

Enable show name and rename that field as well. Fairly sure that is enabled in the public build.

The top link still works for me. It's a very simple test program, its not really very inspirational imo. We use WPF and devexpress controls for most things which let you build fairly powerful graphics fairly easily.

Go have a look in the engine bay....

The logging names got updated yesterday I believe. We also have a new default layout file for the ZF which will go out in the next update.

Set the RPM higher for the enable setpoint or put it in a multi tune and only enable that tune when you are racing. That way for every day driving it doesn't get in the way. Also set the TPS enable threshold higher so it only kicks in at proper WOT.

If you are still running the IMRC you should remove it like on a turbo as that will cause you grief.

They do. They just have different IDs as the resolution is different in a BA eg auF0060 (BA) instead of auF0061 (BF)

He is saying if you have to modify the base fuel table to say 0.5 lambda and you have 0.8 measured at the tail pipe then your SD is most likely out. If your SD is out then your load is lower than it should be and hence you'll be getting less torque reduction and less trans pressure than you should.

Put 0.5 in your base fuel table. If it doesn't get richer you have a fuel pump issue.

PLEASE CHECK THIS The amount of times this happens is absurd.