[Diy_efi] Data logging on a neon
Oolan Zimmer
ozimmer at softhome.net
Sat Oct 23 05:47:58 GMT 2004
This is a multi-part message in MIME format.
--===============72507395128339858==
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0035_01C4B897.A7C38E40"
This is a multi-part message in MIME format.
------=_NextPart_000_0035_01C4B897.A7C38E40
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Data logging on a neonThat really depends on what you want to do. There =
are data logging solutions that range from $100 or so up to Ferrari =
prices.
If you're trying to find mechanical problems and don't want to change =
the tune of the ECU, there are inexpensive ways of reading data from the =
OBDII datastream. That only gives you maybe 2 updates/second, though, =
so it's not fine-grained enough to setup an engine tune. You're also =
limited to the stock sensors. If all you're trying to do is give your =
car enough octane to make sure it's not pulling timing, this is all you =
need. =20
If you're trying to improve on-track driver performance but not set up =
the engine or chassis, a 6-8 channel data logger logging at 20-40 =
samples/second and a few special sensors should be enough to reveal =
everything you never realized you were doing. If you can do some of the =
work yourself, like putting together a harness and tapping into stock =
sensors, you can probably manage to get it done with less than $1000. =
If you can do a lot of the stuff yourself (like write embedded software, =
design and assemble PC boards, etc.), you can probably get in under half =
that for parts but with those skills the value of your time spent doing =
it all would probably exceed what you'd spend for the mostly-complete =
solution. You can also gather less data (but still enough to draw some =
conclusions about your driving) with some cheaper solutions.
If you're trying to change your fuel map and need your air to fuel =
ratio, you need a wide band oxygen sensor. These days, many wide band =
sensor controllers also do some data logging, and that may be all you =
need.
If you're trying to design a new suspension or a first-time setup of a =
standalone ECU (with no base map), then the sky's the limit. Really =
looking at raw knock sensor data and trying to determine if the ECU is =
detecting knock correctly falls in this category. =20
Regards,
Oolan Zimmer
ozimmer at softhome.net
----- Original Message -----=20
From: Frank Clements=20
To: diy_efi at diy-efi.org=20
Sent: Friday, October 22, 2004 9:59 PM
Subject: [Diy_efi] Data logging on a neon
Is there any way that I can cheaply run data logging to a PC on a 98 =
neon dohc? I'm mostly interested in knock sensor readings, timing =
changes and O2 readings. =20
Is their a mod I can do to the ecu to add this somehow? I'm not =
beyond opening it up and modifying the components on the pcb. Sorry if =
this has already been covered.
Thanks.=20
Frank=20
------=_NextPart_000_0035_01C4B897.A7C38E40
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Data logging on a neon</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4134.100" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>That really depends on what you want to =
do. =20
There are data logging solutions that range from $100 or so up to =
Ferrari=20
prices.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>If you're trying to find mechanical =
problems and=20
don't want to change the tune of the ECU, there are inexpensive ways of =
reading=20
data from the OBDII datastream. That only gives you maybe 2=20
updates/second, though, so it's not fine-grained enough to setup an =
engine=20
tune. You're also limited to the stock sensors. If all =
you're=20
trying to do is give your car enough octane to make sure it's not =
pulling=20
timing, this is all you need. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>If you're trying to improve on-track =
driver=20
performance but not set up the engine or chassis, a 6-8 channel data =
logger=20
logging at 20-40 samples/second and a few special sensors should be =
enough to=20
reveal everything you never realized you were doing. If you can do =
some of=20
the work yourself, like putting together a harness and tapping into =
stock=20
sensors, you can probably manage to get it done with less than =
$1000. If you can do a lot of the stuff yourself (like write =
embedded=20
software, design and assemble PC boards, etc.), you can probably get in =
under=20
half that for parts but with those skills the value of your time spent=20
doing it all would probably exceed what you'd spend for the=20
mostly-complete solution. You can also gather less data (but still =
enough=20
to draw some conclusions about your driving) with some cheaper=20
solutions.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV><FONT face=3DArial =
size=3D2>
<DIV><FONT face=3DArial size=3D2>If you're trying to change your =
fuel map and=20
need your air to fuel ratio, you need a wide band oxygen sensor. =
These=20
days, many wide band sensor controllers also do some data logging, and =
that may=20
be all you need.</FONT></DIV>
<DIV> </DIV>
<DIV>If you're trying to design a new suspension or a first-time setup =
of a=20
standalone ECU (with no base map), then the sky's the limit. =
Really=20
looking at raw knock sensor data and trying to determine if the ECU is =
detecting=20
knock correctly falls in this category. </FONT><FONT face=3DArial=20
size=3D2></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Oolan Zimmer</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"mailto:ozimmer at softhome.net">ozimmer at softhome.net</A></FONT></DIV=
>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Dfrankc at corp.ptd.net =
href=3D"mailto:frankc at corp.ptd.net">Frank=20
Clements</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Ddiy_efi at diy-efi.org=20
href=3D"mailto:diy_efi at diy-efi.org">diy_efi at diy-efi.org</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Friday, October 22, 2004 =
9:59=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Diy_efi] Data logging =
on a=20
neon</DIV>
<DIV><BR></DIV><!-- Converted from text/rtf format -->
<P><FONT face=3DArial size=3D2>Is there any way that I can cheaply run =
data=20
logging to a PC on a 98 neon dohc? I'm mostly interested in =
knock sensor=20
readings, timing changes and O2 readings. </FONT></P>
<P><FONT face=3DArial size=3D2>Is their a mod I can do to the ecu to =
add this=20
somehow? I'm not beyond opening it up and modifying the =
components on=20
the pcb. Sorry if this has already been covered.</FONT></P>
<P><FONT face=3DArial size=3D2>Thanks.</FONT> </P>
<P><FONT face=3DArial size=3D2>Frank</FONT> =
</P></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0035_01C4B897.A7C38E40--
--===============72507395128339858==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
diy_efi mailing list
diy_efi at diy-efi.org
http://lists.diy-efi.org/mailman/listinfo/diy_efi
--===============72507395128339858==--
More information about the Diy_efi
mailing list