[Diy_efi] Traction control strategy (solution offered)
Nic van der Walt
nic at unibell.co.za
Tue Apr 30 08:50:34 GMT 2002
>I'm not planning on making any TC devices, but here is how I'd
implement it,
>I'll give 2 examples.
>Both of these methods allow for cornering and can act on open diffs,
closed
>diffs, and FWD.
I agree.
>An LM339 configured as a zero crossing detector, each output going to
an IRQ
>input on an MCU.
Great! This is one way that will work well. The easiest to code also.
Calculating
time between interrupts is trivial on most micro's.
I think you might want to keep a 3 or 5 sample sliding window average of
the calculated
values to smooth out the PID filter.
When doing this you might want to be able to control engine output finer
than cutting
spark/fuel will allow. How effective will pulling back the timing be?
I'm thinking along the lines of having the traction controller do
something like simulate
knock to have the standard engine controller drop advance.
This is where we need MegaSpark with an input line that tells it how
much we want the spark
delayed!
>The A/D approach is simple, but full of unneccesary hardware and
possible problems.
And I thought nobody felt the way I did about Digital->Analog->Digital
;-)
N.
_______________________________________________
Diy_efi mailing list
Diy_efi at diy-efi.org
http://www.diy-efi.org/mailman/listinfo/diy_efi
More information about the Diy_efi
mailing list