Sure that would work, but then of course your just running a stock S at that point. Which is fine, just depends on what your goal is. If you want to lower vtec or have any breathing mods, you need to make the NEO/fpr/wideband investment anyway to tune with. With the ap1 ecu you still get the higher rev limit as well.

 

used aem 1052U FTW!

 

Blasphemy

 

I need the vafc ($150 used anyway) for the vted mods as mentioned. Could have cheaped out on the fpr for $40 but i went brand name for $100. Aem at $600 is probably a good idea but aem reliability gives me a bit of a bad feeling.

 

Ehh. I but my aem 1052u used back in 2009/2010 and it's been fine so far lol

 

I've had a bad taste regarding them in MK4 supras, its probably unjustified.

I could throw on a Megasquirt if I wanted to run the DWB cam triggers too..... or if they ever make code for the MS2 that works on the AP1 triggers.

 

The MS2 won't receive any new features (including new wheel decoders) as it has reached it's maximum flash space. Our Enhanced MS3 does support the AP1 triggers and is plug and play for the S2000.

 

Its been "discussed" that the MS2 was going to get a fixed AP1 trigger setup, but I'm not holding out for it.

I'm well aware I need to grab a MS3 brain but it doesnt fit in the microsquirt socket in the DIYPNP box I have laying around. I may just make a ms2/3.0 into a ms3/3.0 and use the ECU connector I have to make a boomslang type harness for it.

What cam sensor input circuit do you use for the MS3/3.x?

 

The AP1 triggers are never going to be supported on the MS2.

On top of that, since the S2000 has sequential fuel and ignition, you will run out of outputs before you know it.

Btw the standard MS3 doesn't support VTEC. Sure you can use a spare programmable output to activate it, but it won't autoswitch maps when you want it to, nor have custom VTEC engagement maps, or customizable coolant gauge mapping, or OBD-II...the list is endless.

 

Custom Vtec stuff doesnt interest me, but considering MS3 handles variable camshafts fine, I wouldnt think that vtec would be any more of an issue. MS3 traction control is what I would prefer anyway, and 2 injector drivers will work fine for me, no need for full sequential injection.

As far as OBD2 goes, I would be fine with the CAN bus as it is supported by most anything I would want to use, or I could write the OBD2 headers to communicate with the OBD2 based race computer i have.... Just to make you mad.