Hello Everyone,
Im a new member based in Austin Tx. Im also new to wiki page editing so bear with me for a while. VEMs attracted me because it had integrated ignition control. I soon realized though that it was far more capable than any other system in a working mans price range that Ive ever seen.
Here is a short description of the project I have in mind.
The target is a 1988 Alfa Romeo Milano 3.0 v6. This is a Bosch L-jet overhead cam 2 valve per cylinder 60 degree alloy v6 with removeable (wet) cylinder sleeves. The combustion chamber shape is very good for a 2 valve design as are the ports. This engine has somewhat restricted intake design since its shared with its smaller 2.5l sibling so Im strongly considering a rework of the intake to go along with the VEMs installation. A big project for sure.
Some VEMs features Id like to include initially:
- EGT (two EGT channels are possible, and now both channels can be logged)
- WB02
- Coil on Plug (6) - try to find out more about the ignition transformers. Eg. if they have power or logiclevel input.
- Offboard MAP sensor.
- Crank and Cam VR pickups
Q. A new software feature Id like to see is a Temperature based Rev Limiter . On motors with light flywheels this can protect the engine while cold. How feasible would this be to implement?
- the firmware code would be something like 2 lines, but allocating variables, getting them configured from MegaTune and testing, etc... always takes some time.
Q. What about VEMs and ITB ? Ive heard ITBs sometimes need multiple maps based on throttle position but have no experience with this. How do you accurately montitor MAP/MAT?
- MAT is no problem
- MAP can be measured in one ITB, but much better solution to have a "2 stars" ('manifolds') of small equilizer tubes, MAP in the middle of one, and idle-valve in the middle of the other.
- AlphaN is often used for these, at least at low RPM. Note that mapping/tuning consumes more time than for speed-density
Q. I did a CVS checkout of the firmware and did a test build on a linux platform as an excercise. Looks like the compile worked ok (avr-gcc) but in the boot subdir make fails because ioinit.c is missing. Is CVS the wrong way to retrieve firmware source?
- Developers use SubVersionSvn now. You can pick 1.0.29 from GenBoard/UnderDevelopment/FirmwareChanges and play with the source. Are you thinking about firmware development ?
-Tom.