traction control spark cut reaction can't see it in data log

[swifty35]

Question is there a way you can see how much spark cut % when traction control activates? E.g I know I can see how much timing is retarded (traction: timing retard in data log drop down box) as the slip start to happen but I am not seeing an option to see what spark cut % when the slip occurs

[jsmcortina]

Not currently no.
If you datalog slipxtime you can see where on the curves it will be.

James

[swifty35]

When useing spark cut traction control should I set spark cut over 30%cut or would that be to harsh on the motor? Because without seeing the % of cut the ecu used to reduce power I'm not sure how high to set the %cut

[jsmcortina]

Did you see what I just posted?

James

[swifty35]

So your saying if using the slipxtime curve it would high light on the spark cut%

[jsmcortina]

So your saying if using the slipxtime curve it would high light on the spark cut%

I wasn't saying it would highlight it, I was saying you could look at the curve in TunerStudio and see what cut it was going to use. Not quite as elegant, but you should be able to work it out.

James

[swifty35]

O ok, how would I convert the slipxtime numbers seen on the data logs to slip% on the tuner studio reaction slip%xtime? E.g if the log shows 230 slip would that be 23%slipx0.01sec in the tuner studio reaction section?

[jsmcortina]

It's the same number.

James

[swifty35]

O ok so basically if the data log shows 100 on the slip%xtime it is 100% slip correct? And 230 is 230% slip etc correct?

[Speedy_G]

O ok so basically if the data log shows 100 on the slip%xtime it is 100% slip correct? And 230 is 230% slip etc correct?

No SLIP is not transmitted. (You will have to calculate it in MegalogViewer with the vss_1ms and vss_2ms values)
Spark Retard is not transmitted; Spark Cut is not transmitted, Add Fuel is not transmitted and so on.

Only Slip*Time, which is the current slip value multiplied with the slip counter (time since slip is detected)


There were aready a few threads about this.
As you arent really able to tune your traction control without all those parameters in the datalog.
This is why i modified the firmware for me.

[jsmcortina]

Spark Retard is not transmitted;

Not true.

Code: Select all

   entry = tc_retard,       "SPK: Traction retard",   float,  "%.1f"

As you arent really able to tune your traction control without all those parameters in the datalog.

Others have managed to get race-winning results ok.

James

[swifty35]

O ok.Thanks for the info guys. I see some traction control devices have a per gear slip range so you could set different slip in different gears has anyone thought of doing an update with this feature?

[swifty35]

O ok so about two nights ago I tested the traction controllers vss slip with with a vss slip of 6%.in the reaction table is like this

10. 20. 30. 30 spark cut %
20. 25. 30. 50 slip %

The other night the car moved from the launch control smooth and now tonight now same settings the spark cut feels harsh, is there a setting way that I can try that would make it a smooth action?

[jsmcortina]

The axis of the curve isn't slip%. It is slip*time. So perhaps you just have it coming in too early. e.g. try 10x larger numbers for slip*time.

James

[swifty35]

O ok so for example try 200 250 500 700 slipxtime? What about my slip % of 6% should I increase that? I used the 6% from the recent diyautotune article on traction control

[jsmcortina]

You'll need to experiment and review datalogs.

James

[swifty35]

So James to clarify if the data log tc slipxtime shows 200 slip that is basically 200 slipx0.01 in the reaction section?

[swifty35]

My setback is I guess fully understanding the formula used to determine slip especially in the logs

[jsmcortina]

So James to clarify if the data log tc slipxtime shows 200 slip that is basically 200 slipx0.01 in the reaction section?

Yes, the number logged is the number used to lookup from that axis.

James

[swifty35]

Ok cool. Question thoe James last night I also tested the time based timing retard from launch and I find when I use it with the clutch switch it sometimes activates and sometimes it shows it didn't turn on although I came off the clutch on launch