MSefi.com read only forum (Jan.15,2018)

those settinig do affect pip. with the settings i had, the pip was being ignored in regards to timing out put. it was still getting rpm input though.

fastbarry wrote:those settinig do affect pip. with the settings i had, the pip was being ignored in regards to timing out put. it was still getting rpm input though.

I'm confused here.

PIP is generated in the EDIS module. It is then sent from EDIS to MS, to drive the MS tach input. How can you be "still getting rpm input" if "PIP was being ignored"?

No PIP = no tach = no rpm!
PIP has nothing to do with "timing out put"!
I am not aware of any setting in MS that effects the PIP signal generated by the EDIS module!

SAW is a whole other thing. SAW is generated in MS and then sent to the EDIS module to control timing.

Am I not reading your post incorrectly?

Ken

kjones6039 wrote:

fastbarry wrote:those settinig do affect pip. with the settings i had, the pip was being ignored in regards to timing out put. it was still getting rpm input though.

I'm confused here.

PIP is generated in the EDIS module. It is then sent from EDIS to MS, to drive the MS tach input. How can you be "still getting rpm input" if "PIP was being ignored"?

No PIP = no tach = no rpm!
PIP has nothing to do with "timing out put"!
I am not aware of any setting in MS that effects the PIP signal generated by the EDIS module!

SAW is a whole other thing. SAW is generated in MS and then sent to the EDIS module to control timing.

Am I not reading your post incorrectly?

Ken

ms was effectively ignoring the pip for use as a timing reference. it was still physically recieving signal so it still had a rpm reference for other funtions.

you are correct. ms can not physicaly alter the pip signal from the edis module. what i should have said was, those settings do affect how the pip is recieved.



this is how i understand it any way.


barry

Understood.

Ken

Is there any documentation about setting these for EDIS?