Page 99 of 100

Re: Fred's firmware development diary

Posted: Sun Jul 09, 2017 12:03 pm
by Fred
Well, from the 1st of May to the 3rd of July I did nothing much except read and study and figure stuff out, nothing to do with engine control.

From the 3rd of July into the future, much less money available for buying car parts so a real focus on using what I already have and developing the project at full steam.

The rest of July is pretty packed with BMW destruction and Suzuki resurrection and other car repairs and chores, too, but by mid October I want things in better shape, therefore:

August, September and October are firmware and software months. Hard core. By Mid October I want a lot of the really good latent code finalised and permanent in use.

LOTS and lots to do, but very motivated to put things in a good place before then. Very. The most in the world. #CombOver

Will try to get some evening work in this week, too, despite hacking on the BMW.

Re: Fred's firmware development diary

Posted: Tue Oct 17, 2017 5:57 pm
by Fred
Hello from America! North America. Southern North America, in particular!

If you'd like to meet me and you're within Florida or adjacent states, send me a PM and I'll furnish you with the necessary details.

I'm currently back where this video was filmed for the first time about 8 years after I did what you see: https://www.youtube.com/watch?v=RTbmQDKL03Q

Incidentally, 1st of January next year marks 10 years of FreeEMS. Good times, not so good, riches, poorness, a lot of life changes, and some great automotive experiences with some amazing people, as a result. So consider this trip something of a celebration of that, a bit in advance. Hard core FreeEMSers are welcome to pay me a visit in NZ closer to the 10 year mark, if they wish. PM for details, if genuinely interested.

:-)

Re: Fred's firmware development diary

Posted: Sun Dec 31, 2017 9:25 pm
by Fred
Today marks 10 years of FreeEMS! I was celebrating it last night with a wine that I'm failing to upload a photograph of right now: https://twitter.com/FredCookeNZ/status/ ... 6008118272

Image

EDIT: Added link and pic





Thanks for your part in this, and to those no longer reading/gone, thanks to you for yours, too. It's been one hell of a ride, and it's not over yet. Onward and upward.

Cheers!

Re: Fred's firmware development diary

Posted: Thu Feb 15, 2018 11:32 am
by Fred
Rob and I got stuck in this evening over a couple of beers (him) and a small Lagavulin (me) and progressed some of the "latent code" toward finalisation.

More work to do this week coming during the evenings, however it was a solid start and some techniques to deal with the issues were developed.

Goal is to push all latent work into the future and put some spit and polish on as much of it as possible, before next year.

Ideally that'll be all current major blocks of work that are semi-usable and reasonably well tested will be available in their final forms, and hopefully more besides.

PS, I need another bottle of that wine, it was YUM. Any takers? :-D

Re: Fred's firmware development diary

Posted: Thu Feb 22, 2018 11:26 am
by Fred
And a week to the day, another good session on the same issue, and more progress made.

Resolution made to push it further, hopefully to the end within 1 week and 40 minutes.

Pushing steadily toward the latent code realisation goal. Feeling positive.

Re: Fred's firmware development diary

Posted: Thu Mar 22, 2018 1:24 am
by Fred
Skipped a month of madness there:

* Engine swapped one of my cars and installed FreeEMS on it, now daily driving dog food on the final code version, without all the swanky new features etc.
* Changed out the bad differential in another car for a locking variety from a welded variety that damaged itself

But last night got some solid work done with Rob once again.

And even continued on it after he left!

More soon.

Re: Fred's firmware development diary

Posted: Wed Mar 28, 2018 12:28 pm
by Fred
And more work and we got a result, one branch fully rebased onto another, raised in quality, and the test build suite runs with the usual all-but-one passing level. Win.

Next up: Improve the base we rebased onto more and rebase onto it again, much much much more easily.
And/Or
Next up: Improve what we rebased onto that base making it more coherent, complete, quality, and concise in history

Use resulting stable final code variant on my Volvo 240 sedan for more up to date dog fooding. Currently running that base branch, only, and no plans to use any more recent code without finishing it first.

#DogFooding

Re: Fred's firmware development diary

Posted: Thu Apr 05, 2018 8:15 pm
by Fred
Last night Rob and I:

* Went through the special repo last night and cleared out all the marker branches etc leaving only the good stuff.
* Then split the good stuff into actual good stuff and notes about good stuff.
* Rechecked the base good stuff and validated that it's all good.
* Read all the notes on the bad stuff and decided it was time for bed.

But it's prepared and ready for further work to make things better and move forward exposing latent code to those in need.

Including me - I'm dogfooding on the Volvo - which means no unfinished code on that car - which means finishing code off in order to enjoy it - which means others can also enjoy it.

Re: Fred's firmware development diary

Posted: Thu Apr 26, 2018 8:59 pm
by Fred
Last night Rob and I got some decoder development done, with a bit more to come this weekend. The goal is to sell the hardware, but not until we're done developing for it: RB30E distributor.

Turns out that either the old variant or the current variant have/had a couple of minor issues with them. One resolved last night, one yet to be resolved, but narrowed down.

https://twitter.com/FredCookeNZ/status/ ... 2187358209
https://twitter.com/FredCookeNZ/status/ ... 5900704768

Image

Image

Image

Image

Re: Fred's firmware development diary

Posted: Sat May 12, 2018 12:20 pm
by Fred
Sat here alone tonight and worked my way through the various subtle issues. In the end, the code is a bit better for everyone as a result. And we have a new decoder dialed in and ready for use if anyone should happen to need it:

"RB30E-decoder-trying-to-provoke-sync-issues-final-cut-success.png"

Image