Quote:
Originally posted by Grumpy
It's pretty much dead, it's intent was to be the basis of a group effort to develope some really nice code, but to date, no one's wanted to actually do any of the heavy lifting, so it's pretty much just died. |
Thats not 100% true. I've been on a learning curve with $60 for about 10 months now. With two entirely different engines, i'm learning a lot abotu the $60 fueling and timing functions.
As far as "adding to $60", a lot of us just are not at that point yet. I need to get my setup stable before I can start tinkering with experimental things.
A few months ago you told me you were ripping out all of the 'non functioning' code. Have you finished that yet? If so i'd like to get a copy, so I can patch my constant/table changes in.
I think $60 has a future because it's a well documented baseline. some things I'd like to see changed are:
1) Full wideband support for closed loop - not just datalogging but narrowband replacement
2) Additional IAT input for logging
3) Triggered output for things like NOS, alky injection, air
injection for emissions folks, etc.
And some other things in my notebook that i've throught of over the months.
Part of the problem is the code.. You take a person like me who spends all day writing things in C, then I sit down and look at the assembler and its just. fugly
It's also hard to get people involved in projects like this. Things such as megasquirt are gaining popularity.
Theres a project that I've considered working on a few times.. Involves a big engine written in C. I can do 90% of the coding for the timing, fueling, etc. It's the hardware interaction I just can't do.
-- Joe
on the $58 to see the list of recommended changes to get you in the ball park.
