[Diy_efi] Datalogging with knock sensor
efi at dyakron.com
Fri Nov 24 07:30:12 CST 2006
you mention the SyTy code and slow ECM logging. The Typical rate I've seen
from a 7749 SyTy ECM is around 4 frames per second. Are you using a 7749?
Also, which logging software are you using?
The logs should allow you to roughly determine at which MAP & RPM
your spark knock occurs. Close anyway..
At 07:22 PM 11/23/2006 -0600, you wrote:
> I've been playing with my new 'toy' which is a wideband datalogger. My
> AFR is now very close (after some logging and tweaking) and I want to
> start tweaking the spark timing. When I started this project I copied
> and pasted in a "stock" 2-bar sy/ty spark map into my ECM and it runs
> quite well. However, there are a few pingy spots at part throttle.
> My ECM does not have a knock sensor and this function is disabled in
> the calibration. (I do plan to use this feature eventually.)
> I was thinking about getting an appropriate knock sensor and interface
> box (the thing between the ECM and knock sensor) for my engine
> block. Then logging it with MAP and RPM to look for the areas with
> detonation; so I know where to edit the table in the ECM. My ECM has the
> old slow ALDL which is poor for real-time logging.
> Has anyone any experience with this?
> Thanks for any ideas!
More information about the Diy_efi