Roland@pcmtec

Is the intake and exhaust wired back to front? Try locking the cams in software and see if they do what you tell them to.

Have you put a completely stock tune in the car? Do you have a spare pcm? Also have you checked the cam timing itself hasn't skipped a tooth? Standard valve springs? You've tested everything id recommend otherwise.

Ok just for reference the on condition is rpm > rpm setpoint AND map > map_sp it then latches on until rpm drops below the setpoint. So this means it will stay on during decel which may be undesirable. From what we can tell only one customer has ever used this feature in the 4 years it has existed. So we want to minimise support if it doesn't do what people want.

If anyone has recently done this with the MAP setpoint could you please let us know what your use case was and if it all worked correctly? We are trying to determine if anyone is actually using this feature and if it should remain in the software.

If anyone has recently done this with the MAP setpoint could you please let us know what your use case was and if it all worked correctly? We are trying to determine if anyone is actually using this feature and if it should remain in the software.

Use a matching pcm + tcm from the strategy list. I suspect you'll have dsc, ABS and cluster errors though. Much easier to swap all modules and looms over.

Another one. If you could upload a datalog showed the fuel trim errors and you got the following result. It would be immediately obvious that you don't actually have a fuel injector slope problem. But (in this extreme example probably bad data or mechanical failure). But more than like your speed density slope and map is out. This is always a chicken and egg problem. However if you could somehow determine if the error data is purely a function of injector slopes/breakpoints/offsets you could say. Hey use these settings to fix it. If you had a graph like he one below, you could go "Hey this actually needs a speed density recalculation" to fix your problem. You could then spit out new SD tables instead. The way to determine if the error is a function of injector slopes is fairly easy, you just look at the standard deviation on the scatter plot of the LTFT. if its wild and all over the place, you know the LTFT error is actually related to a 4th or 5th variable (probably map pressure and cam angle) in which case it could come up with a solution for retuning the map/map offset tables and ALSO the injector slopes. You could then plot the problem cells (with a high SD against) map pressure and cam angle to validate this as well. This is something I tried to do here, but once again ran out of time. The main issue is the whole thing was quite technical, if you can bundle it up into a simple program where it says "log x,y,z" follow the the following dyno run. Then input the data, you could effectively get factory level fuel trims and steady state open loop lambda all automatically without having to be an engineer to understand what is going on. You can then try and figure out a function for your LTFT error term, ensure its actually a function of what you are trying to optimise then provide a solution. http://www.hptuners.com/forum/showthread.php?58174-Custom-graphing-software-for-logging-fuel-trims-and-recalculating-speed-density-maps here was an example where the LTFT error was actually not an injector slope issue (Which I was chasing my tail trying to correct) and was due to map slope offset. Kudos to actually building a working app. I look forward to seeing updates!

Great work. Things that I would love to see. An exaggerated annotated zoom for the low/high slope to make the changes really obvious Some way to take a histogram like below and annotate it: Then have your tool auto suggest corrections to the injector slopes. It could be iterative and have filtering (eg avoid transients, bad data rates, high standard deviation etc due to a random extra digit in a speed density table). Then have a big red magic "Fix my injectors" button. People would pay to use that button if it worked well or at least got them in the ball park. Some example of problems, and things it could potentially fix: Linear WOT error. Change high slope. Error around the deadtime/low slope, suggest deadtime/breakpoint/high slope changes to try and attempt to keep the WOT fueling consistent. Error around the breakpoint only, suggest breakpoint/low/high slope changes to fix the error in this zone only. Similar to what we were doing manually in this thread. Automating this would save tuners thousands of hours, I'm sure people would pay you for this service if its simple to use. Happy to help provide you anything you need to help get it there. Also if it works well, we would definitely push people to use it.

License is per user and pcm. They will have to relicense it. An option is to buy one car workshop edition and they can use your account to tune the car assuming they are comfortable with that.

Use a manual calibration, then compare and copy over the idle airflow and dashpot from the auto file so you get the same throttle behaviour. (there is more than just this, but this is where I would start) Or do the reverse, take the original auto file and compare it to a manual disabling the various system switches and codes to effectively make it a manual car. Depending on which version of pcmtec you have you may not be able to see all the differences so the second option may be easier. Comparing an auto to manual file in the calibration list will give you some clues and help you get started. There are a few people on here who may have already done this who can assist.

Thanks for posting this up! I'm sure it will help others.

Read all the howto guides then start changing things one at a time, datalog, see what happened etc. There are guides and threads on both the items you asked. Do a search and read everything you can!

They both activate simultaneously. The cruise part of the map should have stock timing to ensure turning cruise on and off doesn't make the car buck around. Check out the video again re the other question. It is normal.

Log torque source and check out boost and map pressure. Probably hitting overboost. Make sure you don't pop the motor. These cuts and limits are there for a reason when stock. Pegging the tmap with overboost and tmap overpressure turned off is a great way to blow up a motor.

Coolant sensor (cht depending on the car) failing will cause vct to stop working and it will get stuck in cold start mode. Commonly left unplugged or crushed when swapping the motor. See this all the time.

Did you read the file back out of the car and see things were 0? On a failing pcm if you read it back out you'll get a checksum error with often large chunks of the file zerod. This happens with the old ba PCMs when the flash fails to commit after a write. You'd only see this after doing a read though, most of the time it will give an error when doing the prior write as well in this scenario. If this is the case I highly recommend not doing any further writes as eventually it will fail completely and you will need to replace the pcm. If you didn't do a read then I don't really see how anything in the stock file could be zerod without you doing it. If you send everything in to support we can investigate it further.

Ba doesnt support rapid packet so you really have to cut down the number of channels you log. The logging rate in your logs makes it too hard to see what is going on.

I'm not on a pc could you post a screenshot. Does it instantly go to 30deg error? Or does it happen slowly? What it you hit 299 rel and hold it there? How much boost do you get and what happens?

It's public as in you can download someone's software that they spent a lot of time on and didn't charge a cent for. Most people do this once or twice and get jaded. Don't underestimate the value of your time. If it takes you months to figure out you should charge for your time. Undercharging discourages all the other smart people out there from having a crack and innovating.

Exhaust cam error means a hardware issue. If it's software you won't see an error and it will simply command 0 deg. Otherwise check oil pressure, big heavy valve springs and high boost will give you grief as well, especially on an old ba that probably has gummed up oil feeds to the VCT actuator. Drop boost and try again when the oil is cold, if the problem goes away it's most likely an oil supply issue.

The best way to mitigate expensive fuel costs is to drive less. I do less than 10,000kms a year so I do childcare dropoff and pick up in my e85 mustang Lol. I don't even think twice when fuel costs go up as I only fill up once every 3+ weeks. It averages 31L/100km as my average speed is 22kph. Catch the train, work from home if you can etc etc.

No. It is the same as bf just with the extra tables discussed in this guide.

People still tune carbies. The industry will shrink but it will still be around for another 20 years. I think porsche with their synthetic fuel and also ethanol as a by product will be what keeps these cars running.

Post a new thread with your tune file including what you have tried and a datalog. If you are an end user (eg you don't own the software) then you need to contact your tuner, the multi tune on its own does nothing, it all depends what the tuner has set it up to do. They have to specifically set up the tune to do this if it's what you want.

Thanks for putting your spare time into helping answer questions Bill. We really appreciate it.