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

I just finished installing MS-II, v 2.2 board, on my 70 Porsche 914. I used a Subaru TPS and made sure to wire everything up correctly. Using Megatune, I calibrated the TPS and Megatune read it wonderfully, 0 % at closed throttle and 100% at WOT. Then, when I cranked the engine over, it goes to 170% and stays there! What is that! It isn't like it jumps around or anything, it just goes really high. I made sure to use shielded wiring on my coil signal for pin 24. I am not running spark just yet, so I didn't even hook that up in the harness. I made sure to ground the TPS at the battery terminal with all the other ground wires for the MS. What could be causing such a reading?

Oh, I'm using version 1.31, kinda old, but I began this project awhile ago. Could this be part of my problem? Megatune is version 2.25.

****UPDATE****

GOT IT. Disregard above. I figured out that it is necessary to reset the MS once the values have been saved. That took care of the problem. Now, when cranking, the TPS reads as it should. On to the next problem... More postings on this later, I suspect.

that almost sounds like the either the wiring is bad, or the TPS harness isn't plugged in, which was my case
-teb

I thought maybe wiring too, but the wiring was still right when I checked it for the fifth time. As noted in my update above, I finally did get it to work, but that's when the other wierd stuff started to happen, foremost of which was the message that the firmware versions in Megatune and MS were different and that table corruption would occur unless Megatune shut down. At that point I figured I needed to update to the latest firmware version 1.34 (I use MS-II on the v2.2 board). I also decided to pull the board and clean it with alcohol and recheck my solder joints. Some of them were potentially suspect, so I have taken care of them. I will reinstall the MS tomorrow and see how it turns out.

that error message shows up when you don't have the megatune config'd right
did you change the config to match your new code versions?

I did. Actually, I think what happened is that I used another guys .msq file. We have the same car, but he was running a different version and maybe that messed it up. Not sure. I did make sure to "activate" the proper code in the configurator. I hooked it up to the stimulator and it seems to be working much better now. We'll see when I hook it up to the car tomorrow.