Tim D

Could you include all knock data and FCut and ICut in the log please? It looks like the knock threshold is being exceeded in places so I expect that knock control is pulling timing?

Thanks, that's great, I will give it a go...

Hi all, I set up Launch Control on my Subaru Impreza STI and configured it to disable at 25 mph. This works perfectly. However, my Vehicle Speed Sensor appears to have an intermittent fault, meaning that the reported speed sometimes drops to 0 mph. If this happens during a launch, the car gets stuck in launch mode. Is there an alternative way to disable launch mode (as a quick fix until I can fix the speed sensor)?

Excellent, thanks for the speedy reply Adam, much appreciated.

Hi all, I've been trying to fine tune a weird problem with idle control on my Subaru Impreza STI (EJ257) and noticed that the vehicle speed (LF Wheel Speed) as seen by the ECU doesn't return to 0 mph very nicely. It sort of hangs around 4-6 mph, then drops to 0 mph at the last minute, usually after coming to a standstill. I think this is detrimental to the transition to idle control. I looked at datalogs from 4+ years ago and these also show similar effects when coming to a standstill, so I am wondering how precise the indicated speed should be? I've attached a screenshot of a datalog showing this behaviour (I came to a standstill very smoothly, not as depicted in log): Happy to post logs etc, but wanted to know how good it should be, I'm assuming what I am seeing is sub standard? Any info/tips would be greatly appreciated.

Out of interest, did your new cable have a ferrite bead (the bulge in the cable!) and your old cable not have this? I'm interested in how significant this is?

It looks like your are reaching the MAP Limit which is causing Fuel Cut to kick in (to protect the engine). IMO, you should either reduce the boost target so that you don't reach the Map Limit or If the engine can handle more boost, increase the MAP Limit.

Thanks for your help, that worked perfectly.

Thanks Wanderer, thanks Adam, The engine has recently been rebuilt, so I guess this is pointing towards Adam's response. I had a quick look in PCLink, should I use Cam Angle Test to measure and fix this?

Hi all, Please could someone have a look at this datalog of my 2007 Subaru Impreza (EJ257), it shows the LH inlet cam following the target position nicely, but the RH inlet cam seems to stick when returning to low RPM. Does this look like a mechanical problem? Here's my tune and log files https://drive.google.com/file/d/1_2xjmL4tqKDDjRRaazbYCyisHcrCuHOQ/view?usp=sharing https://drive.google.com/file/d/18IJacWlOX1kb1Xx30rFBh6uxh54VSj6q/view?usp=sharing Thanks in advance

I had a couple of ideas on this, should be pretty quick to prove/disprove: You mentioned "logging a lot of parameters at high frequency", could you try removing most of the parameters just to see if it has an effect? My logic being, if there is a lot of interference, USB might cope better with less data being transmitted, hence pointing towards comms probs? Is your laptop graphics driver up to date, or has it recently updated itself and maybe introduced a problem? I know that graphics card/drivers have the potential to crash a laptop...

I noticed that AP is around 0.8% at idle and AP/TP lockout is 0.5%, meaning that ignition idle control is never activating, you could try setting this to 1%. Also, the Idle Ignition Table should have a value of 25 degrees at 0 error to match the ignition timing at idle. It currently has 10 degrees. You could try 0 degrees at -500 rpm error, 25 at 0 rpm error and 30 at +500 rpm error. I think this will help...

Thanks Adam, that has completely fixed it!

Hi techies... Something that has been posted by many people in the past... My laptop (Asus GL552V) takes a long time (>1 minute) to connect to the ECU. It was ok some time back, not sure what has changed! I've tried: Updating display drivers Display scaling set to 100% Updating all other drivers Power plan set to High Performance Run CCleaner Pro Defrag Run PCLink.exe as administrator Always have laptop plugged into charger See YouTube clip showing 1 minute from ignition on/start before showing as Online. I usually have to wait for the connection speed to ramp up too. Please can someone recommend some ideas that I might have overlooked?

Pete, great tip, thank you. Like you, I have also tried using conditional filters for overrun fuel cut but found it much better to turn it off like you mentioned. Maybe Lambda takes a while to stabilise after the overrun fuel cut has re-enbled? The strange thing is, I've had great results from using mixture map in the past, so I think I need to do it again and scrutinise the datalog before accepting the corrections. I have seen 'flat lines' in my datalogs in the past where USB comms appear to momentarily freeze, maybe that was happening and I didn't spot it?