GenBoard/UnderDevelopment/FirmWare/MiscOutputs (2005-04-28 07:56:46)

Misc output related subpage of GenBoard/UnderDevelopment/FirmWare

Also some general method (see interpretere below) to define functions for misc output actuation


Interpreter

There are more and more stuff that needs flexible configuration, without firmware recompile, eg. misc outputs. Currently condition is wired for most common function, RPM,MAP,TPS ranges

I think we cannot avoid a simple language/interpreter. Maybe a postscipt-like (but binary) code: words of 16 bits that are

---

Michael's Ideas...

There are a few parts to this challenge. First of all it's necessary to cater to a potentially long list of functions. Adding canbus enabled switches allows for an impressive range of features. VSS encoders, clutch switches, ALS enable switches, boost knobs are all potential inputs. On the output side one can have as many outputs as there are spare channels. Potentially extra drivers could be available via CANbus.

First the outputs...

I assume at this point we're dealing with a finite number - limited by the number of spares you have. This could still number 8 or more.

Outputs may potentially be switched based on CLT, TPS, MAP, RPM, IAT to name a few off the top of my head.

Another sort of output may need to be driven from a table. TGV/TVIS/IAB control, electronic throttle and others come to mind.

The output may need to be on/off or PWM.

The code for doing these checks is fairly trivial. Efficient storage of the parameters is somewhat less trivial.

A dynamic size for these functions would require a lot of work. First you would need a means of specifying the size of each record and secondly you would need a means of properly shuffling things around should changes be made. Anyone remember Norton Defrag?

Ok, the sun is coming up... I'll add more later.