Bone stock '94. DIY MSIv3, parallel install with a boomslang following Brain's writeup. Hires 10g firmware, currently using the .msq from DIYautotune and their fuel & spark maps. The car started right up, and it just took me a couple minutes to dial in the trigger angle.
I easythermed it using the appropriate values in the writeup (in my case, 1450 bias for both) and the IAT and CLT readings look good in Megatune. MAP at idle is in the vicinity of 28-30 kPa, tach works fine (I did the cap mod).
I'm getting a CEL, not blinking an actual code, just staying solidly on, all the time. The MAF itself is disconnected and I have the IAT sensor plugged into the two pins in the MAF plug per the writeup. I did a search and it seems the CEL could be due to no MAF signal to the stock ECU. There were some ideas tossed around (resistor between two other pins in the MAF connector?) but I didn't see what I thought was a nice tested & proven resolution to the problem other than A) pulling the bulb or B) going standalone. Is there a simple way to spoof the stock ECU, assuming this is what's causing the CEL?
Other than the CEL, no problems. I drove around the neighborhood a bit and it ran fine. Nothing has really been tuned yet but it seemed fairly smooth all things considered. It's responsive and smooth when I get on the gas, although it seems a little more "sudden" and less smooth on decel compared stock. I just took it easy, didn't go WOT or much above 4000 rpm since I've got 87 octane in the tank at the moment.
I still have the stock NBO2. Yes, an LC1 is in my future. Is there any point to running either autotune or the VE analyzer in MLV, using the stock O2 sensor?
Thanks to all you guys for lighting the way. I'm really stoked that the car runs off a computer that I built! It's like the first time I fired up that tube preamp I built, or the first decent batch of beer I brewed. Sure there's lots of room for improvement, but I've got a touch of the proud poppa syndrome.