29.5.2007
After looking at the Megatune, i think it would be nice if we can also have the following Failsafe option:
- MAT above set limit retard for every Y degrees Celcius the timing by X.
- This is in the firmware already:
- For this there is no choises in Megatune (it works as it is in the Firmware or i am wrong?)
- This is in the firmware already:
http://www.vems.hu/wiki/index.php?page=GenBoard%2FManual%2FMatRetard
http://www.vems.hu/wiki/index.php?page=GenBoard%2FUnderDevelopment%2FTemperatureCompensation
http://www.vems.hu/wiki/index.php?page=VemsFrontier%2FIntakeTemperature
- EGT above X degrees then Retard timing - Lower boost
- Add fuel and Lower boost would be best, retarding timing would further increase EGT.
- Through the Wideband: if not the Set amount then retard - cut boost.
- Good idea, maybe with a time hysteris to eliminate quick Lambda spikes. (Kevin Black)
What do you think about it? Is it simple through the Megatune?
Cheers
Vasilis
It would be nice if VEMS will support something like this:
-Boost Control (and fail safe-i.e. if the Motronic sees that it cannot control Boost the it switches the Boost valve and i only run with the safe Wastegated 0.5 Bar)
-EGT Ignition Retard and/or Boost Control so if the EGT is too high the System will take Care of it.
-Intake Temperature Sensor ckeck so it could also retard timing if the IAT will be too High.
- What do you think about this?
- In the Stock Motronic if the Temp is above a temp it retards timing to prevent detonation.
- very reasonable
I know that the Safe-Safe option i would like are too many but i think these option are the ones that Holding many people away in installing Stand Alone Systems. The Car will also be Used from others that are not allways with their eyes on the Gauges.
Reference sensor data
proposal: when the car runs well with all the sensors etc, let the system Log the sensor inputs (for say 10 minutes, with all kind of driving-Full-part throttle and stop-go) and save these sensor data as reference.
If ECU reads different than this reference, it could log the sensors as defective so if something fails, we could have some diagnosis.
Problems:
- no memory to store that much data
- even on PC, the comparison is - well, nontrivial
- depending on usage, the engine warms up faster or slower
- a cold winter morning would flag the temp sensors as defective
- what sensors would this apply ?
- MAT sensor - easy to have a min-max, very hard to have other rules
- CLT sensor - easy to have a min-max, very hard to have other rules
- MAP sensor - easy to have a min-max, we already have fuelcut below and fuelcut above certain MAP
- hard to think of saving other sensors' data as reference
- ... ?