@Kruz: +1 to that, Kruz. Good tech to have in-pocket, but it's not a end-all to the "slip slidin' away" (to paraphrase a famous singer). I usually read Code, but I dont remember that one. Got a magazine date, so's I can read it, please? That's an important peice of data, thanks...
Unless I missed something the OP was talking about when TC and ABS don't save your butt
Thanks, Kruz. It's a different view of the same subject.
@Privateer: Thanks for chiming in, glad to see you're still around these parts. I remember that story you relate, I've read that before around here. That was a skilled peice of work...
@Grn: There's something to your link between input parameter changing (engine torque response curves .vs throttle position, mapped in SW, for example), and TC/ABS behavior change, I'm convinced of it. One peice of data that convinced me was, earlier last year, Motorcycle Magazine did a "shoot-out" with european super sports, and the Ducati team provided a Panagali (sp wrong). But, Ducati insisted that the tires remain what they provided, instead of being swapped for "for-same" tires as the other models in the shoot-out (to eliminate a comaro difference).
Otherwise, Ducati said "no way". It was keep the rubber we give you, or find another cycle.
The reason they gave? It changed the TC response mapping. So, yeah, you're headed in the right direction there.
@Rook:
ABS should reduce brake power to optimum where (sic) traction is regained.
I agree with this assessment, in the situation you describe.
Again, if ABS comes on, you're left with either laying the bike down on purpose or taking your chances standing the bike up for better traction, possibly leaving the road on two wheels.
I agree with this, too. But, I have not read about, or spoke with, anyone who actually had ABS responses engage while leaned over, and with braking. Even Privateer has only spoken about straight line response.
The rule for throttle in a corner is opposite that of the brake. I am always ON the throttle at least a crack as I enter a corner and then increase throughout.
Agreed, very good.
TC would reduce the throttle in a situation where I would be getting off the throttle anyway.
I'm not so sure about this, tho. I would argue that, TC will "feather" the response, whether it's a "throttle on", or "throttle off".
That is, (depending on the setting, and I believe Grn gave a good description), that if TC were to detect and engage on a "throttle open" input, the response would likely be to "feather" that input, perform some engine management function to cut power (until the *system* determines that the total response (user and engine et al) no longer causes the "error detector" to detect.) In my opinion, the same would be true for a "throttle off" response, but the output to engine management might not be what you expect. It might actually "feather" your chop...
In any case, it will prolly do the "right thing" under the conditions it detects.
Otherwise, Heaven Forbid!, the Software would be in error!
Rook, let me add here, I really enjoyed your well thought out replies. You could write a book with that kind of attention to detail. Thanks...
... and now, we are back to my first points. Do these system (ABS and / or TC) provide system output when there's no inputs.
I am going to correct myself from yesterday. After thinking about this some more, I would like to change my opinion.
My original statements were based on an assumption: That only *user inputs* were in view. Throttle, brake, lean angle, etc. Anything an OP could modify.
That view falls apart when considering that the systems have system response maps in software (and likely firmware too), that account for more inputs that just the user's controls. I'm taking about the rest of the "world" the system monitors: wheel spin, accelerometer output changes not originating from user inputs, (and what else? I'm sure there's more).
So, based on the writeups, I'll change my mind, and now believe these systems will provide output during times of no *user* input changes. The reason they will do this? They will be responding to "world" changes that they detect, and can affect, *if instructed to do so* by their code. (The SW has to be "right", they only do what they're instructed).
If a wheel slip is detected by ABS, during steady-state user input's, and the ABS processor SW says "ABS commanded to engage front brake, duty cycle response 10 msec per cycle, over 0.5 sec absolute time", then that's what will engage (given the ABS system can do it, mebbe it's broke right?).
Last point: During my original example, I slipped on a patch of sand and managed to recover. ABS would still not have saved me if I had more lateral acceleration going into the corner (going too fast, OK). It (ABS) can not provide traction where there is none. Same for TC.
I also suspect (but cant prove) that it would not have engaged anyway. Why? Because the whel spin rate did not change, there was no "world" input differential that it would detect.
This is what I get for being a SW guy...
* Last updated by: mebgardner on 1/31/2013 @ 8:42 AM *
2012 Blue ZX-14R, Cox rad guard, Skene Design P3 Lighting, Knight Design 1" lowering pegs, Grip Puppies, BrakeAway, Cortech Sport tailbag, GSG MotoTech Frame sliders, Stebel Compact horn.