Fred's firmware development diary

[Fred]

Testing in just a few hours now :-)

[Fred]

http://www.diyefi.org/forum/viewtopic.php?f=41&t=774

Testing complete, next thing is that RPM bug, need to nail that.

Fred.

[Fred]

Everything compiles again, and some things are better than they were, BUT, the bad news is that the RPM calc is not the only thing wrong. The period that the capture code is recording jumps around - noise. I'm going to have to do a bit of wiring I think as I'm not sure I can code up noise filtering and sync maintenance in the time frame required.

On the brighter side, it does rev up and work under load in a sort of intermitttent miss sort of way.

IE, the reason it doesn't run right is not the bodgy code, it's the fact that it's not getting a clean set of pulses to do injection on. Bugger, yet yay at the same time.

2 hours work in walmart winchester virginia and we are making some progress. 1:15am time to pull out the sleeping bag and get some shut eye before tomorrow's carpark breakfast LOL.

Fred.

[Fred]

I upgraded the ground the other night in Asheville and the ADC values stabilised - good. The RPM values *seemed* to stabilise too but not well enough to be good/run. What I should do is put the pin echo stuff in and put a scope on the output so I can see how the noise that it actually sees looks. It goes rich where the noise is due to starting too many pulses of fuel that it shouldn't be.

Some software noise filtering could do the trick, and if I can't solve it with hardware, then I'll start writing that code, I guess.

Not much time left now, fingers crossed for a good result - current result is pretty damn good. Need to take a new video ;-)

Fred.

[Fred]

More bugs solved, closer to full success. This interfacing with Aaron is weeding out all the little issues, great stuff :-)

I have just discovered that my relay switch is causing resets of the cpu, so i'll rewire that soon.

Otherwise, aarons stufff is usable, with the exception of the white box which vanished! :-)

I can't wait till he fixes it and polishes it later tonight, might go out and tune the car ;-)

Fred.

[Fred]

It idles! :-)



Despite the VE values everywhere else being all wrong :-) The were wrong for some specific testing and will be circa 80% by default soon. Point being, it idled fine :-) and as soon as i touched the gas, of course it went uber lean and died, perfect.

Fred.

[Fred]

Things to do before release of the FreeEMS 0.1.0 code base :

generalise table contents
generalise various settings eg injector size
check nippon denso to ensure the math still works on jimstim
review code changes and make multiple clean commits
fix up versioning
make windows makefile work
check and merge different local private git repos
place all generalised files in subdirectories

to be editted...

Fred.

[Fred]

I pick up my box of goodies from a friend tomorrow - inside is my PC with my git repos on it. Once I have this I can start working on readying the code for release 0.1.0 which is yet to be named!!! Head to the lounge and give us your suggestions in the naming thread there!

Fred.

[Fred]

I setup the box the other day, but didn't have a working mouse to use, so was out of luck for a few days there...

I just fired it up and found that the box has no further commits over and above the ones on github. What this means is that I'm free to work on my EEE to bring the code up to release spec merging some work from the eee copy that I didn't use and some work from my US adventures into one final codebase to rule them all (and go forward from).

More progress soon! :-)

Fred.

[Fred]

I've ironed out the existing work and started genericising a few things that I wanted changed before pushing/releasing. It is less than a days work away from being released, I'd say. However given how close to xmas we are, that may take a week or two to happen. I'll probably take my PC away on new years though, so if I can find a connection out there to do things from, I will :-)

Fred.