richardpalinkas

No problem. Always glad to help

I did also notice when you close a compare file, the program freezes briefly but comes good in a sec. Might be a little glitch

Since the new update, the compare view is not working for the torque management settings, as in last version you could see current, stock and compare settings side by side, now it only shows the one table and you have to select from the drop down menu which view you want to see

So just make sure you stop data logging when flashing? Thanks mate

Has anyone used an obd port double adaptor without any issues? I have my sct x4 plugged into one port, am I able to flash with the the other port without causing any issues to the sct x4? So I can log and flash without the need to constantly unplug one obd plug and swapping them all the time?

so do you need to put a resistor in place so that it does not go over 3.8v or is running up to 5v ok?

In the custom os file, what is automatic two step configuration, and how are the 2 options different between each other?

when wiring in the switch into the circuit a37, is that to ground or to a 5v source? and if its to a 5v source, where are you getting the source voltage from?

Well that can't be correct. The abs sensors would be going nuts thinking your rear end is faster than the front. Most vehicles have maybe 2% tollerance before the abs sensors realise there is an issue and shut down the abs module from working.

The rears are way too big for the front. Do you mean 275/35/19?

If it's plug and play, it shouldn't have any effect of the tune file itself. Should revert back to stock after you remove it. Maybe try clearing KAM and see if this helps

can see towards the end where it drops down to 500rpm. and the test 2 actually stalls at the end of the log. if you see what could be causing it, please do let me know so i can better understand what im looking at datalog_ghost_cam.csv ghost_cam_test_2.csv

Yea can upload a log for you to look at

Just experimenting with ghost cams etc, seems as though when the idle dips too low, engine stumbles and causes idle rpm to drop below idle setpoint. Eg, if my desired idle is 850rpm, when pulling up to a stop, the idle dips back down to 500rpm, before correcting itself. I've tried altering idle airflow to help, but can't seem to get it where it behaves in a drivable fashion, as the more idle airflow I add, the more idle hang I get, which delays the issue, but is not recitfying it

Ok. So desired idle spark is at 60, according to the idle spark desired table, however spark is usually stable around 15 degrees. So which table needs to be modified to say increase the idle spark to say 20 degrees?

Which spark table is responsible for idle spark?

That would be an interesting concept

what table or scalar are you referring to in regards to this?

Is it possible with further development to allow the standard ecu to flash in real time? Or is that just not possible at all?

Auf11982 is not available to edit in professional level

Just discussing the best way to tune the lower load tables for spark advance? For my case, haedjr5, fg turbo on E85, I understand that E85 allows the spark to advance towards MBT without knock, but with our ecu not being adjustable in real time, tuning via torque optimisation is difficult, what is the best practice to tune the lower load on E85?

Can this be done to a standard box also? And would there be any benefit of doing this to a standard transmission?

Thanks for that explanation. My car is tuned to open loop, and I'm logging exactly what my desired boost table is, so it might be a good idea if I re enable closed loop boost control

Is there any benefit in running boost in open loop compared to closed loop? Vehicle is an FG running 20psi on E85. And reverting a tune from open loop to closed loop, is it best to run the standard settings regarding boost control as in the pid values?

Just checked my file. Fuel base is .805 lambda. Running about 12 degrees to 13 timing.