[jpnovak]

It sounds like you just want the data. The MS systems will certainly provide you with the data. The challenge is that the MS2 will not data log on its own - you have to request the data either from a laptop (via tuning software) or a stand alone box. I built a stand-alone DAQ system for my track car since I could not have a laptop. I use a micro controller that interfaces with the MS2 ECU and contains a 3-axis accelerometer, 10Hz GPS and writes the data to an SD card for external analysis. There are still about 5 channels of open analog inputs. So, room to grow.

The challenge for you will be interfacing with the older engine. The AFR is easy with a stand alone WBO2. TPS will not readily adapt to the carbs. RPM can be pulled from points signal or the tach. additional temperature and pressure sensors can be added. Engine load would be measured by Manifold Pressure (MAP) but this would require drilling manifolds for hose connections.

Most of these variables above are part of the data package from any stand-alone EFI.

If it were me, I would make a list of all your must-have run-time variables and a list of would like to have data variables. Then figure out the best system that will cross as many off the list as possible.

Crunching numbers can be fun but frustrating. It is best if you can have your DAQ crunch as many as possible. Meaning, Let it calibrate voltage signals, etc. Much easier than running a Macro in Excel or using any other number crunching program.