Patch for Failsafes on stock ECU
Jul 2, 2008, 09:38 PM
#1
Evolved Member
Thread Starter
iTrader: (17)
Join Date: Nov 2005
Location: NNJ
Posts: 2,544
Likes: 0
Received 0 Likes
on
0 Posts
Patch for Failsafes on stock ECU
I was thinking that since we now have the ability to log boost with the stock ECU and also feed wideband AFR into the ECU we can setup some failsafes. I am talking about failsafes the way the zietronix does it.
For those who don't know, the zeitronix can look at Boost, RPM, TPS, AFR, and EGT. The zietronix then allows you to set parameters that will trigger a warning light. An example parameter could be boost>20psi & RPM>3000 & TPS>80% & AFR>12.5
The stock ECU can see all of these except EGT. In theory I think it would be possible to have the stock ECU do this function. I'm not sure that it is really needed with a knock patch but some people might want it.
I personally have the Zeitronix and use it with the parameters shown above but I was thinking why use that if the stock ECU can do it.
What do you guys think? Is it worth it? Anyone want to code it (I wish I knew how).
For those who don't know, the zeitronix can look at Boost, RPM, TPS, AFR, and EGT. The zietronix then allows you to set parameters that will trigger a warning light. An example parameter could be boost>20psi & RPM>3000 & TPS>80% & AFR>12.5
The stock ECU can see all of these except EGT. In theory I think it would be possible to have the stock ECU do this function. I'm not sure that it is really needed with a knock patch but some people might want it.
I personally have the Zeitronix and use it with the parameters shown above but I was thinking why use that if the stock ECU can do it.
What do you guys think? Is it worth it? Anyone want to code it (I wish I knew how).
Jul 2, 2008, 10:15 PM
#2
What would be the action taken once a condition has been exceeded?
Really (and feel free to correct me) KnockSum is the only thing we are interested in, overboosting will be handled by BoostLimit table.
If we see knock then backing of the GAS is probably the best thing we can do to protect the engine...
Really (and feel free to correct me) KnockSum is the only thing we are interested in, overboosting will be handled by BoostLimit table.
If we see knock then backing of the GAS is probably the best thing we can do to protect the engine...
Jul 3, 2008, 06:47 AM
#4
Evolved Member
Thread Starter
iTrader: (17)
Join Date: Nov 2005
Location: NNJ
Posts: 2,544
Likes: 0
Received 0 Likes
on
0 Posts
I guess knock is really the only thing we are worried about, I mean if you lean out and don't get knock then technically thats ok I guess.
I was thinking you could cut boost but instead of using an extra output from the ECU I figured you could just reduce the WGDC.
With your existing patch, what happens when knock level 1 is exceeded, what about when knock level 2 is exceeded?
Might be cool to make the CEL light flash for knock level 1, and give the option of having knock level 2 reduce the WGDC or possibly even reduce timing slightly.
I was thinking you could cut boost but instead of using an extra output from the ECU I figured you could just reduce the WGDC.
With your existing patch, what happens when knock level 1 is exceeded, what about when knock level 2 is exceeded?
Might be cool to make the CEL light flash for knock level 1, and give the option of having knock level 2 reduce the WGDC or possibly even reduce timing slightly.
When you say "failsafe", I think "last desperate attempt to save the motor". Might just be a question of terminology?
Trending Topics
Jul 29, 2008, 04:44 PM
#10
This would make me very happy:
If/and statements, like the zeitronix, for the stock ECU, something like:
if Knock=10 and TPS=100 then WGDC=0 (or whatever you want the WGDC to default to)
On the flipside, engineering something like that into the AltMap trigger would work as a failsafe
if Knock=10 and TPS=100 then switch to AltMap (and you could setup the AltMap to be your failsafe maps)
ECU+ has something like this, with if/and statements that, if triggered, reduce timing and add fuel in whatever percentage you input.
If/and statements, like the zeitronix, for the stock ECU, something like:
if Knock=10 and TPS=100 then WGDC=0 (or whatever you want the WGDC to default to)
On the flipside, engineering something like that into the AltMap trigger would work as a failsafe
if Knock=10 and TPS=100 then switch to AltMap (and you could setup the AltMap to be your failsafe maps)
ECU+ has something like this, with if/and statements that, if triggered, reduce timing and add fuel in whatever percentage you input.
Jul 29, 2008, 04:55 PM
#11
Evolving Member
iTrader: (14)
Join Date: Feb 2006
Location: Westchester, NY
Posts: 305
Likes: 0
Received 0 Likes
on
0 Posts
This would make me very happy:
If/and statements, like the zeitronix, for the stock ECU, something like:
if Knock=10 and TPS=100 then WGDC=0 (or whatever you want the WGDC to default to)
On the flipside, engineering something like that into the AltMap trigger would work as a failsafe
if Knock=10 and TPS=100 then switch to AltMap (and you could setup the AltMap to be your failsafe maps)
ECU+ has something like this, with if/and statements that, if triggered, reduce timing and add fuel in whatever percentage you input.
If/and statements, like the zeitronix, for the stock ECU, something like:
if Knock=10 and TPS=100 then WGDC=0 (or whatever you want the WGDC to default to)
On the flipside, engineering something like that into the AltMap trigger would work as a failsafe
if Knock=10 and TPS=100 then switch to AltMap (and you could setup the AltMap to be your failsafe maps)
ECU+ has something like this, with if/and statements that, if triggered, reduce timing and add fuel in whatever percentage you input.
I think the best way to implement this would be to set it up so that it switches to the alt map when the failsafe is engaged. This would take care of boost if you are controlling that with the ecu, fuel, and timing.
It would be also cool to add in a few parameters that can be used with the spare inputs on the ecu. So we could input the signal to the ecu and use it as part of the failsafe. Wideband and meth flow are just a few ideas that come to mind.
Jul 29, 2008, 05:13 PM
#13
Evolving Member
iTrader: (14)
Join Date: Feb 2006
Location: Westchester, NY
Posts: 305
Likes: 0
Received 0 Likes
on
0 Posts
Well as long as their pump gas tunes are safe on pump, there should be no problem if the failsafe kicks. On race you will be running higher octane so the pump gas map would be fine, and with meth you would be running the normal pump anyway. I think that it would be fine as long as their pump gas tunes are conservative and can act as a failsafe.
Jul 29, 2008, 05:36 PM
#15
Well as long as their pump gas tunes are safe on pump, there should be no problem if the failsafe kicks. On race you will be running higher octane so the pump gas map would be fine, and with meth you would be running the normal pump anyway. I think that it would be fine as long as their pump gas tunes are conservative and can act as a failsafe.