This is form the MAF converter V3 thread. I decided to simplify things a little in there and move it to its own home!
bmwman, did you remember the datalogger that you were building... after this MAF conversion, the datalogger will be next thing? tell me yeah!
great progresses with maf, though.
Yeah a datalogger is still in the works. There are 2 i want to mess with. One will capture all the real-time data off the car and interface with a PC. The other will be an economy-logger. It will get trip miles/mileage, average mileage, average speed, lifetime mileage/speed/distance, etc. That will have a little LCD display in the car. This is after I finish this, and work out the last couple bugs in the 1-touch windows though. So much to do, so little time....!
hope that you'll start building it before the end of the year:D
Remember, it should read at least RPM, MAF/AFM/MAP voltage, throttle %, AFR from our innovate LC1s:p, inj dwell...
so I'll use it to tune my future (but soon) turbo build...
I know...
How many samples per second would you like to see with this? If it is going to have ANYTHING to do with RPM and ignition timing / injector duty cycle, it is going to be limited to about 5 per second (per channel).
I WANT to do:
RPM
mass/volume flow
intake air temp
ambient air temp
ignition advance (no plans for dwell)
injector duty cycle
throttle position
AFR from a wideband
coolant temperature
vehicle speed (maybe)
Maybe is better if we talk about this in the old thread... if we find it:D
You're saying that the number for each channel, e.g.for RPM, will be refreshed 5 times per second, so 5 Hz (Hertz)?
(sorry if I seem stupid, but it's hard to understand all technical words in another language that I never speak, I'm Italian...)
If that, I don't think that it's too bad, but 10 will be better... but I see dataloggers of 25 Hz... Innovate's one is 10-15 Hz
How much channels you're able to connect to your future datalog, there is a limit?
Channels you wrote are the same that I want, maybe I need a MAP, so manifold pressure too...(it's easy, it output in volts...).
Maybe we should add oil pressure and temperature, as optional inputs?
In importance order;):
RPM
throttle position
AFR from a wideband
mass/volume flow, and manifold pressure (for turbos:D)
injector duty cycle
ignition advance (no plans for dwell)
oil temp
oil pressure
intake air temp
coolant temperature
vehicle speed
ambient air temp
with all these things, mapping a piggyback will be very easy...
I have a Power CommanderIII that I'll use for control fueling (when the turbo is ready), I'll wire it with a MAP, so I'll modify the opening time of injectors every 250rpms, and I will use 36# inj with stock ecu + piggyback... a datalog like your can make things easier for all people that going into custom setups, like turbo or supercharger, or for maniac people that want see all parameters of engine...
All will be wonderful, if we will be able to put all those channels into Innovate Logworks software...:eek:
Oil pressure is tough. It would require the user to do some scary things to their motor to get there, and if I were to design a product that was sellable, I could not require users to do things they are not keen on. The MAP would be a similar deal, but i could always make it an option.
I CAN have it do much faster rates, say 25Hz, but I will need to really work on that. The missing-tooth wheel on the main pulley has its advantages and its drawbacks in this regard. It gets tricky to have the logger outputs timed properly when the crank pulley rotates at less than 25Hz such as at lower RPM's. While this is not really the range most people care about, it would be good to have it working properly.
As with anything, as complexity and functionality increase, so does cost.
ok, so remove from your mind oil pressure and temp. MAP is only a voltage, from 0 to 5v usually... I need only to log the voltage...
The issue is not with the hardware with the MAP / oil pressure thing. The issue is the installation. Even doing a MAP requires you to drill a hole somewhere after the throttle body (or maybe TEE in with the FPR vacuum line). If I were to design a product that people were not afraid to buy, it could not require too much crazy workmanship...and the hard part about designing a system like this is that it cannot be produced at a reasonable cost without a large quantity. And making a custom solution for one or 2 people is $$$$$! I will do my best though to make a feature-rich product at a fair price for the community. I certainly do not like saying "NO" to potential buyers, but I do like being honest and realistic. I know I know, I will never make it in business thinking like this lol.
As a follow-up...
I do not want to sound like I am quitting on some features out of laziness. That is not the case. I love developing this stuff. My experience in business so far is such that I have learned that I cannot wait until a design is 100% perfect to release a product. If I did that, it would NEVER come out. I want to get it good enough to meet 65% of the customer's needs for now as a basis.
Once I do that, I can build from there to start helping the other 35%. As soon as I really have a chance, I will get on this again. I have been getting a lot of projects done due to some injuries to my ribs and overworked tendons in my left foot's arch. After a month or so R&R, they are about healed and I am itching to get back out there & break myself again lol. I will need to find a place for this project next to my health-maintenance. I am also planning to shoot for a job switch where I will be doing this kind of stuff for an employer (not automobile related). I might pick up some new tricks there.
The other good news is that I am becoming decent at Visual Basic. As practice, I am working on (almost done with) a data logging/plotting app for some data feeds on projects at work right now. This is very useful practice for the software front-end for this logger.
Topic: Data Logger Development Discussion (Read 2437 times)