Syvecs Forums

Hi,

I recently fitted a second map sensor in order to log EGBP. I assigned this sensor as map2A. The first time I went WOT I hit boost cut, as EGBP climbed over 1.9bar (nothing suprising there). I increased the boost cut threashold to 4bar as a temp workaround, but this is obviously not an ideal scenario long term as it is in effect disabling an important safety feature. I have had a pretty good look through SCal and I can't see any way of seeing/assigning which map sensors are monitored as part of the boost cut strategy. Can anyone suggest a better solution, short of submitting a feature request for the inclusion of EGBP as a sensor option, or a way to configure which sensors are monitored for boost cut in a future release of the S6 firmware?

Cheers
Richard

Richard,

The boost cut will trigger on the maximum value of map1A, map1B, map2A or map2B. Normally map2 is used for cylinders defined as being in Bank 2, so whilst using it as a logging input shouldn't affect any of the run time computations for the engine (all cylinders on a Subaru are normally in Bank 1) it is perhaps not ideal. Since the parameter you are trying to log is a gauge pressure not an absolute pressure, you could use some other pressure parameter in place of the egbp, or if you don't mind math functions, simply log the sensor voltage and display it as a math channel.... if the sensor is 0 at 0.5V and 10 bar at 4.5v and on AV4 (AN12) then you could define a math function egbp = ((an12v - 0.5)*2500) to get egbp in millibar. Failing that you could put it in as ccp or cdp, neither of which should affect the boost cut, but ccp has an upper limit of 2000mbar so you may need to "compress" the signal and "expand" it again in SView with a math function.

With regard to egbp as a defined input it is on the todo list, delta-P across the head can be quite useful from a strategy point of view so whilst we're not adding "useless" inputs any more, egbp is definitely "useful" and will be added in due course.

Hope this helps,

Pat.

Thanks Pat,

I guessed you'd have some work around

I'm using the KMS 4bar sensor. I will revert to logging the sensor voltage directly and use the math's channels in SView to convert this to a value based on my sensors linerisation.

Looking forward to the inclusion of EGBP as a sensor option in a future release.

Cheers
Richard

RichardB wrote:Thanks Pat,

I guessed you'd have some work around

I'm using the KMS 4bar sensor. I will revert to logging the sensor voltage directly and use the math's channels in SView to convert this to a value based on my sensors linerisation.

Looking forward to the inclusion of EGBP as a sensor option in a future release.

Cheers
Richard

EGBP still on the waiting list ?