DIYEFI.org Forum

I think it would be really nice to track FreeEMS usage in a detailed way. Currently this is only in my mind, or where ever I happen to post it. I'd like to keep a permanent and visible record of most key attributes.

First draft of fields required:

Name of owner
Name of builder
Name of installer
Location, city, country
Contact email (kept private)

Type of hardware (DIY+TA, DIY+Other, Puma Spin 1, etc. enum style, add them as people design them.)
Type of engine (mine this from somewhere online or free form?)
Make of vehicle
Model of vehicle
Cylinder count (auto derived from engine?)
Level of control (Fuel, Ignition, both)
Type of config for fuel if installed
Type of config for ignition if installed
Previous versions/history of aspects that can change as a car is developed.

Placing, automatic, as entered, but overrideable by force by me to correct inaccuracies

Initial code version if known.
Date/time of first start
Date/time of first drive

Stats that I'd like pretty graphs of:

Scaled bar graph and/or coloured pie chart of each

Country
HW type
Control type
Vehicle make
Vehicle model (this'll get big, perhaps by make?)
Type of fuel config (including "none")
Type of ign config (including "none")

Additionally, a curve of engines run over time based on the first start time/date, scaled appropriately, or sub scales of this?

Fred.

One more field:

Forum thread ID number for "vehicles" section thread, construct link automatically, such that spam can't be had.

+1 I think this is a great idea.... do you ever sleep?

Only sometimes :-p

+1, on the idea and sleep comment

https://github.com/fredcooke/FreeEMS-History

I've started a repository for this. Don't contribute to it yet, the structure is not finalised. Once it is, I'll fill out what I can, then leave it to others to add their own details where applicable.

Fred.

Another field:

Crank/cam sensor type and pattern?

How about "decoder_name" ? I think that beats describing it. You had to use one to run the engine, so you should know what it's called. Good point.

BTW, input_style was supposed to cover that, however thanks for reminding me that decoder name was missing! :-)

I might change input_style to rpm_input_style too. It can remain a free text field to allow the weird and wonderful and unique in future, including all of the odd ball details required!

Fred.