would it be hard to have an option to make the traction control cut the ignition instead of retarding timing? it could be a selectable option? i tested it this afternoon (remember i have a gen 2 busa powered t-rex www.campagnamotors.com t-rex are very traction limited so im looking foward to getting the traction control function functional! it was one of the things that motivated me to make the gen1 to 2 electronics swap) and i put the activation at 3000rpm in 2nd gear and retarded the timing 20 degrees... well to be honest it made no difference, the rear tire went in smoke when i gunned it like i tought. i need something way more agressive, only way i think it would work for me is to have it cut the spark.
no i dont have any logged data. one question i have i had the activation set at 3000 rpm and had 1800rpm-sec in 2nd gear with 20deg retard. to test it i whent over 3000 then gunned it in 2ng gear... for the code to activate do i need to gun it lower than the activation treshold? meaning if i have it activated at 3000rpm i need to gun it before 3000? or it doesent matter as long as your over the activation threshold and gun it activates?
on the gearing yes your right, but i do alot of road racing and use pretty mutch all the first 5 gears so third gear and so on my gearing is spot on. but im a drag racer at heart and im the only busa powered t-rex as i converted mine, they are all zx14powered so we have alot of grudge racing going on....lets just say that if and when i get traction control working they will be crying.
LIFE IS SHORT RIDE HARD
turning the traction control On/Off with ms0/ms1 would be great for track use too.
Better would be to use 2 diffrent traction control settings with ms0/ms1, for example for dry or wet conditions.
the implementation of traction control in ecueditor is more focused on drag racing hence being in the drag tools section. the module limits rotational acceleration of the engine. There are many more dynamics that need to be taken into consideration for effective traction control when corners and braking are involved. You really need additional sensors including front and rear wheel speed sensors and possibly a gyroscope to detect the lean angle of the bike.
www.WoolichRacing.comTune your bike to the Limit with our Advanced ECU Flashing Products
Thanks Justin for the quick reply!
Do not get me wrong - i am not complaining in any way. I want to contribute if I can and feedback is what i can do.
Still I think that even being focissed on drag racing - the 2 step should be a problem for them too as the TC kicks in on the RPM threshold and between 1st and 2nd while the bike is straight up on the starts (same for 2,3 but not so severely andfades away with setup) and my bikes power is just a fraction of what the drag bikes do. My point was that it seems to me that the algorithm calculates not the raise of rpms per second but rather the change of rpms per second. If some simple change in it could make it react if there is only a positive (not just any change) change in rpms according to the previous second that would make the system work much better and all of these symptoms go away. If like you say there is no simple solution - then it is good enough as it is either way.
I am really interested though if the drag racers do not experience these effects themselves on the drag strip.
Just had a quick look at the code as its been awhile since i have looked at it, below is the pseudo code with some comment for what its currently doing. Looks like it is only activating when it is a positive change in RPM.
if ((timer > timer_old) // If this is a new measurement
& (ECU_RPM > ACTIVATION) // and RPM is greater than Activation RPM
& (rpm_now > rpm_old)) // and current RPM is greater than last measured RPM
// Calculate the time since last measurement
// Calculate the RPM Difference since last measurement
// Work out the RPM Rate of Change
// Set RPM Rate = 0
It has been a while since I have firstly started to use the TC and quickshifter and trying to implement them for road racing.
At this point my conclusion is the following (for my current level of riding).
If you enable the TC and quickshifter together and do not want to have troubles between (hard and long ignition reatrd) shifts you have to go at least as high as 60-65ms for quickshifter (you will still get the ignition cut now and then though especially of you are not back on the seat). TC timing reard should be not more than 1 and trigger RPMS more than 2500.
The problem for me is that this makes the TC not sensitive enough for the time when you really need it with high lean angles and hard on the gas off corners.
So my question is - could you implement a modification in the code where the TC is not active(switched off temporary/on standby, whatever is easier) for "X" amount of time in miliseconds after a signal for quickshifting is present?
This way you would not have ignition cut when QS is shifting and TC can be set sensitive enough for when you trully need it (when in gear and not quickshifting). Also on my bike for example i can go as low as 38-40 ms for safe and fast shifting in each gear.
Thanks in advance if you could spare a minute.
I will post this in new features requested section of the forum.