I'm interested in data acquisition in general. I do a bit of that in real life, as a job. Years ago I started building a system for my Honda to do that. It was based on a PC specifically made for the automotive environment and had a National Instruments analog and digital I/O card in it. I had the basic hardware assembled and was well into the software before LeMons came along and ruined everything.
Last winter I build an Arduino-based module to monitor the gauges in the Tinyvette, our race car. It works nicely and now I'm working on another module that will monitor fuel flow rates. Not only would that information be useful, but it could keep us from running out of gas. The current fuel gauge setup is nearly useless in a high-G environment.
Of course, there's the RaceCapture option. My reasons for not going that route before now have been:
- Cost, it's already difficult to fund even a LeMons race car.
- Confusion, I can't figure out exactly which RaceCapture product or products I would need.
- I like to build my own things, when not too impractical.
Here's what I'd really like to do. (Keep in mind this is an old car, pre-OBDII, pre-DOS, pre-CP/M)
- Monitor the gauges and if any are in the "bad" alert the driver using a shift light.
- Monitor the fuel flow rate sensor (pulse output) and once xx gallons have been used alert the driver.
- Push button to reset the fuel level monitor.
- Relay all the above info to me in the pits.
- GPS, speed, lateral Gs, lap times, and all that would be fun, too, but are a lower priority for me at the moment, although I figure these will be the things that will most interest my drivers.
Mike