Roland@pcmtec

No and no plans to add it. Would be considerable effort and no one would pay for it from the research we did. We would have to charge $1k per car instead of $150 to make it worth while and basically every workshop said they wouldn't use it.

If you haven't changed the tune and it has started happening on its own it sounds like a mechanical fault. It should kill the injectors if the ect error becomes large, the pcm is good at that.

The cruise control torque requestors, don't change any of them from stock. Jsut make sure the "cruise speed control" torque requestors are all stock. There like 4 of them, just search for "torque request" and you'll find them in the navigator. If you want exact parameters to check go through the torque requestor thread and check all of them against stock Have you flashed a stock file back into the car to check? What are your throttle errors whilst logging?

Yes do not mess with the cruise control torque requester settings as this can screw up the cruise control. Also messing with the torque tables and spark retard/torque ratios will possibly mess up cruise control as well.

All done.

Ok then there must be something else happening. I can see that there is a history entry for -27 for that item, however we don't log who or when it occured so I'm a bit stumped why it is there. The fact we have not seen this before means there must be some rare edge case for this to happen. I'm guessing it has something to do with the fact that it was originally SCT tuned (and hence no stock history is available). If you have other files can you send them along with a description of which auF and how to reproduce it, I will continue digging to see if I can find out how that history item got there. Can you confirm that opening,saving,closing, reopening resolves the issue?

It appears this value was actually set to -27 at some point. I tried with a test account that was not licensed to view the file and it did indeed show -27. My best guess is this parameter was accidentally edited when the file was unlicensed. I'm not sure how so I'm going to go through your log files to confirm this theory. Did you ever send the file to any other pcmtec users? If they edited it and sent it back this might be possible. The work around for this is easy though. Simply open the 98 tune, save it, close it, this resync's the ui/compare history with the binary within the file. Then open the e85 tune, then load the 98 tune as a compare file. We have added some changes to 1.21 to ensure this kind of scenario is not possible, eg after licensing it auto saves the file so that you can't end up with something that is out of sync.

Ok so in our latest build (1.21) this issue seems to be resolved, however I'm not sure actually why it was resolved just yet. Unfortunately 1.21 is still a few weeks away from being released. I will see if there is a work around for 1.11 that I can give you in the mean time.

Good news is I can reproduce what you reported. Leave it with us and I'll figure out what is going on.

Can you send them again just in case? I will test now and report back.

We are working on a new wizard that will actually let you pick and choose what tables go into the flex tune. This will be released with the cruise control multi tune functionality.

Yes it is possible, the PCM you have may no have a boost controller output available though. We can't give you instructions or support on how to do this (as there are many calibrations and different combinations), but lots of tuners use our software to do this.

Can you send us both files and instructions on how to reproduce the comparison error? Screenshots will be very useful as well as this is the first we have heard of this occurring.

Providing the files have been licensed and saved at least once. Or if you have the workshop version of the software you've used the "populate unlicensed file" function and then saved the file. If the table sizes are different (possible depending on what options have been used, some tables will not compare as their IDs change) If you email both files to us at support@pcmtec.com I can try myself and let you know the reason.

Gear shifts are done in oss, if you change the diff it shouldn't affect these. Going to a lower ratio should also slow the speed it revs down mean in g less chance of hitting redline. Doing the opposite will do what you described though.

Maybe. You might need to reprogram the ABS module if that happens. You could also try what is written in this post.

You'll get a permanent ABS/DSC fault and your ABS won't work. Can also mean your cruise control stops working.

Be ware that there might be module mismatches causing all sorts of dramas if you just blindly flash in a different operating system. You may need to modify quite a few things (or nothing) depending on the differences in your vehicle and the operating system you flash in.

You will need professional.

You can come do my car next. I haven't even got a spare minute to do that yet!

We have a beta version with analog inputs working (as seen in the video) but there are just small features we need before we send it out. Otherwise we will get flooded with questions about things we already know are not complete, so we are just going to wait until it is more polished.

When it's done.

No they are a proprietary device. J2534 is an open SAE standard.

How did you go?

How did you go in the end?