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

I have a V3.0 MSII, running the latest version of code 2.891.

My issue I discovered trying to configure the TPS in the car taking the closed and open values, both returned 14 as the ADC count. So I started digging deeper to see if my wiring was messed up, if I had voltage and the correct resistance at the TPS wires etc and all that checked out. So then I put the stim on and tested to see if the TPS value would go up and down as I turned the pot and it didn't. I have gone through the troubleshooting section and have found this part as being off currently:

"You can also check the resistance from the CPU pin #26 (near the H1 boot header) to R9 - on the side of R9 nearest the DB37 you should have less than 1.0 ohm (0.1 is better), - on the side of R9 nearest the DB9 you should have ~1K Ohm"

Right now I get 1K Ohm nearest the DB37 of R9 and 0.0 Ohm when tested nearest the DB9 side of R9.

Another thing to note is the TPS readings have worked with the board before, I pulled the MS out of my car about 2 years ago and am putting it back with with a different manifold style etc, so something has happened between now and then.

I need help on what to do and where to look further to fix this.

Thanks,

Bryan

Check the voltage at CPU pin 26 on the Stim when you turn the trim pot - does it move as you adjust the pot?

Matt, not sure if I understood your direction for testing, I put the + lead of the meter on pin 26 of the MSII daughter card and the - on the ground strip for the board. I turned the stim pot and the voltage did go up and down, 3.9v for full lock one way and 0.0 full lock the other.

-Bryan

beast02 wrote:Matt, not sure if I understood your direction for testing, I put the + lead of the meter on pin 26 of the MSII daughter card and the - on the ground strip for the board. I turned the stim pot and the voltage did go up and down, 3.9v for full lock one way and 0.0 full lock the other.

-Bryan

That is exactly what I meant. If you try to calibrate the TPS on the Stim (using full lock to lock as "open" and "closed", with "closed" being the 0 volt position), what do you get for open and closed ADC values?

I tried this test with the stim calibrating the TPS (before I posted here) and I believe I got 0 values for both wide open and fully closed, though I will test again tonight when I am back home.

Thanks,

Bryan

Ok, I did the test and I get 1 (fully counter-clockwise) and 14 (fully clockwise) as the closed and open values

This could be corrupted firmware or a bad MS2 daughter card. I'd try reloading the code - without reloading the MSQ - and repeat the TPS calibration, see if the ADCs change more this time.

Ok, so I loaded the code (at least I think I did). By this you mean power down, put the jumper on, open MS download 2.0. File open, select the code (in this case monitor_v2.891.abs) and burn.

I did this, it said successful at the end of all the script. Then I powered down, moved the jumper, opened Megatune, RPM bounced from 0 to 8000rpm rhythmically, I calibrated TPS and it opened with the values as 0 and 1023, then when I calibrated it gave me 1023 for both open and closed.

Not sure if I did what you told me to correctly.

-Bryan

Sounds like you may have made a bit of a goof in the calibration procedure - you need to use the two Get Current buttons separately when the pot is at one end of the rotation and at the other end.

No, I did do the fully open and closed values and got 1023 and 1023 (1023 when fully closed and 1023 when fully open), when I opened the calibration window up, the default setting was at 0 and 1023 (just mentioning this as usually when I opened it was at 0 and 0)

Sorry, looks like I had misinterpreted your post. This sounds like a fault with the daughter card.

Welp, good and bad news!

I bought a new MS-II card, put it in and loaded code, had the same issue.....bummer I thought. Well I should have done this earlier......but I loaded older code on (2.67) and was able to get things to work, on the new card and the old car.....so the problem must have come from the newest version of code and the setting up of it I guess (slightly different than the pre-2.8 code)


-Bryan

It could be a setting you've loaded is corrupted. If you reload the 2.891 firmware but do not load a tune, does it still have the problem?