Fred's firmware development diary

[Fred]

I just played my first April fools joke! I wonder if there will be any further opportunities for humour later today. Fingers crossed :-)

EDIT: And it didn't back fire! :-)

[Fred]

OK, game plan, as it stands:

http://issues.freeems.org/view.php?id=549 < DONE Add tests while it's still fresh in my mind. Boring, but a good idea.
http://issues.freeems.org/view.php?id=524 < DONE Add configurable on/off outputs with hysteresis. Easy enough.
http://issues.freeems.org/view.php?id=539 < DONE Move inline hard coded stuff to config. Time consuming, may require some code change first.
http://issues.freeems.org/view.php?id=526 < DONE Ditto. Time consuming and difficult to do well, will require some code change to make robust.
http://issues.freeems.org/view.php?id=180 < DONE Closed by previous two.

In the mean time I also need to get Preston a good starting configuration/code base. This will likely create a few new issues to make generic/permanent whatever I come up with for him. I need to throw something together for Andy to test ASAP, too. If successful, that will close 518.

Then it's back to closing out 500 by cracking out the 32 channel LA and inserting a shit load of debug and tracking the little bastard down.

The above should get us close to 2/3 complete for 0.2.0, certainly over 60%, anyway: http://issues.freeems.org/roadmap_page.php?project_id=1

Once I've dealt with the above and other pressing matters in my life I'll re-evaluate what is left and post a new game plan!

Fred.

[Fred]

And before I do any of those things, I need to pay the server hosting bill for the next 12 months! Fortunately a few of you have been generous over the last 3 months, so I can actually "afford" to do that. Read afford as "it's possible" :-) Hooray for you! Thanks! (from everyone who uses this forum and other sites, not just me) :-)

[Fred]

Hmm, it did itself!

Mean while I brought OLV up to date with the latest firmware variants post limiter commit. This breaks OLV for all old log files, so use a version before my last commit for those legacy files. Use a version at or after my last commit with files from new firmware.

cde2c4df4fd27b49ee3bee8a6ea4f93e87fbd1ce and up for firmware f0eff1205a022352df161ed2b098c8b9b1172e80 and up
b13084784e9137e23e1df17b185a3df622986afd exactly for firmware 3f59fde9c4601df7be8e37a783e44357c5876ebe and older

Fred.

[Fred]

549 is resolved/fixed and roadmap percent complete is at 58%. Today is more or less over, so I likely won't do any further serious work on the other stuff, but I will spend some time thinking about them.

[Fred]

I just spent 30 minutes and wrote a quick code review guide here: viewtopic.php?f=41&t=1683

It's not perfect, but it's a solid start. I'd like others to be reviewing my code. And I'd like people to be reviewing the code of other developers, too. Code review is a big part of quality control. I always review my own as much as possible before committing and pushing, but clearly I won't notice some things that fresh eyes would.

EDIT: Code review request/volunteer thread: viewtopic.php?f=41&t=1684

Fred.

[Fred]

I've done a bunch of work on 539 today, and implemented what I hope is a temporary but good enough fix for Preston and the MIGHTY HOTEL. He's testing it right now, and I'm off to bed shortly. Will close out 539 tomorrow, and a thread to go with it. Will likely then tackle 524 and a configuration for Andy to try on the Deuce Coupe. "Preston is typing..." drum roll please...

(01:43:29) Preston: just setting up logging, then test

Premature drum roll! The suspense keeps building...

No luck :-( Will get up first thing tomorrow and keep trying. Need a solution for him, one way, or another.

Fred.

[Fred]

Hotel is up and running, perfectly adjusted, and in fine form, better than it has ever been including when it rolled off of the show room floor! Programmable ignition FTW. The code it's using isn't production quality, but it is functional and is working for him on the car nicely. I will patch the latest base firmware for him to try as testing for me when required. Until I do a proper fix, that is.

Back to the half finished sensor work tomorrow (539), and maybe a setup for Andy (524+config).

Maybe I can hit 60% complete tomorrow, fingers crossed.

Fred.

[Fred]

I'm sorry to have to do this, people, but my health is suffering. My left wrist is not a happy camper and needs a break after being worn out responding to attacks from a certain person. I'll be on the forum very little over the next week and coding only by necessity. I'll likely try to get Andy what he needs, but anything else can wait for the time being. I'll try to achieve clicky type things as my right side is fine. Sorry for any inconvenience caused! :-(

[Fred]

I decided to key in some long-standing outstanding issues this evening. If you've experienced these and agree with the direction of the content that I've created in each, please pipe up and add your support with +1 of some sort. If you have other ideas, contradictory, supportive, different, or otherwise, also pipe up :-)

http://issues.freeems.org/view.php?id=562 Determine Best Serial Port Behavioural Semantics
http://issues.freeems.org/view.php?id=567 Re-Add Datalog Polling Service But In A Clean Independent Way
http://issues.freeems.org/view.php?id=566 Determine Which, if any, of the Nag Screens should stay
http://issues.freeems.org/view.php?id=561 Determine Best Logging Semantics
http://issues.freeems.org/view.php?id=565 Store relative window placement on exit for next launch
http://issues.freeems.org/view.php?id=568 Add Optional And Configurable Inter-Char Delay To Serial
http://issues.freeems.org/view.php?id=472 Provide Get Data/Store Data Per Page

There is one big one left to add, but I'll save that for another day.

Fred.