What's the cheapest method for datalog (afr, knock,...) ?
#17
Evolved Member
iTrader: (6)
There are two ways to log boost with Innovate products if you do not want to get an LMA-3
1. LM-1+LMA-2+ 3-3.5 Bar Map Sensor
2. LC-1+SSI-4+3-3.5 Bar Map Sensor
Last edited by nj1266; Dec 26, 2006 at 08:23 AM.
#21
Evolved Member
iTrader: (6)
This is incorrect info. It creates the impression that all you have to do is connect ZT2 to Logworks and it will work. It does not work that way. You need the proper plug-ins in logworks for it to accept data from ZT2. To my knowledge, there are no such plug-ins for ZT2 in Logworks.
#22
Account Disabled
iTrader: (465)
This is incorrect info. It creates the impression that all you have to do is connect ZT2 to Logworks and it will work. It does not work that way. You need the proper plug-ins in logworks for it to accept data from ZT2. To my knowledge, there are no such plug-ins for ZT2 in Logworks.
Lets assume that it is more trouble than its worth to use Logworks with ZEITRONIX.
ZEITRONIX ($274) + MJ Mitsulogger ($0) integration underway
ZEITRONIX ($274) + Evo4mad's Evoscan ($25) integration underway (concurrent logging currently available)
#23
Evolved Member
iTrader: (6)
Other loggers can accept data from Innovate products IF those logging devices use the SDK packet that Innovate give away.
Second, You will need PLUG-INs to make Logworks accept data from another source like ZT2, for example.
Before the Tactrix cable plug-ins were added to Logoworks, Logworks would not accept data from the Tactrix cable.
You cannot simple plug ZT2 data output into Logworks and expect it to work.
Second, You will need PLUG-INs to make Logworks accept data from another source like ZT2, for example.
Before the Tactrix cable plug-ins were added to Logoworks, Logworks would not accept data from the Tactrix cable.
You cannot simple plug ZT2 data output into Logworks and expect it to work.
#26
He also expressed some interest in the LogWorks plug-in architecture. So I told him he would be welcome to get early releases of all the LW3 SDK features (many of which are in LW2 but undocumented - which is how the tactrix plug in runs).
I'm a little confused about 'EvoScan being implemented...' comments above. According to the web site, LM-1 and LC-1 support are already in. I know that we answered some questions about LC-1 serial output from Evo4mad on our forum back in September.
One comment I have about the setups being bandied about - you need to be careful about MAP sensors. In the LMA-3 (and our DL-32) we use both a high resolution ADC and a configurable input amp for the sensor. That is how we support all the modes of absolute and relative pressure.
If you are just using most MAP sensors into a standard 0-5 logging input, you need to make sure that the logging system can handle non standard min and max voltages and let you build a non-linear voltage->pressure table. The sensors are virtually never linear, seldom reach rails, and almost always have a slight DC offset from their data sheet.
I know that you can correct for this on all our input sources (LM-1, SSI-4, LMA-3, etc.) and I am sure that some other vendors and loggers allow this as well. But if your system of choice does not, you'll save a lot of grief by spending a little more and getting something that already converts sensor input to a linear, calibrated scale. For example, you could take the analog output from our LMA-3 into a sytem that only offers fixed, linear, 0-5V sampling.
-jjf
Thread
Thread Starter
Forum
Replies
Last Post
seahawks12th
General Engine Management / Tuning Forum
41
Jun 15, 2009 01:05 PM
cityhugo
Evo Engine / Turbo / Drivetrain
7
Apr 23, 2004 09:19 PM