jerrah

I'm currently investigating the feasibility of installing a DIYPNP into my 1991 NA6.

I'm sure the build would be fairly straightforward and I am hoping to install the following:

Wideband LC-1
MapDaddy
IAT
Variable TPS
Knocksense MS

The long term objective is to install bigger injectors and a BEGI turbo kit but I just want to get it running N/A in the short term.

I originally considered the MegasquirtPNP but the DIYPNP has really appealed to me but I think I need some clarification of what I should be doing to create the base map / firmware to get my car started. Obviously if I don't get these settings right I could cause damage to car.

I presume the DIYPNP is a µS not a MSII board? Does that change whether I'm using MSII code or not?

Which firmware should I be trying to install on it? MS2-extra? And which version?

DIYautotune advised me that the base maps from the MS1 based MSPNP will not work on the DIYPNP and that the example MSQ for a '95 Miata should work to get my engine started. Given that these are two different engines I'm not 100% sure this would work so I hope to get the '95 MSQ open and then double check it against a 90-93 MSPNP MSQ to ensure the basic settings are correct.

When I try to load the '95 MSQ into Tunerstudio or MegaTune I get errors.
The DIYAutotune spreadsheet says the file has the code version: MS2/Extra 2.1.1 beta but when I tried to load the file I get an error stating the file has a signature: MS2Extra Rel 3.0.3h. Is the file listed incorrect or do I need to have a different Tunerstudio project? Or a Rel 3.0 ECU ini?

Should I be running MS2/Extra 2.1.1 or 3.0.3h on the DIYPNP?

Would I my plan of exporting the fuel and spark tables from a MS1 into DIYPNP format and ensuring the details are correct likely work?

JustinHoMi

That's right, the DIYPNP is based on the microsquirt module. You'll want to use the MS2/Extra code.

You're getting errors b/c 2.1.1 and 3.0.3 are prerelease and are in active development. Those tunes were created with slightly earlier versions of the firmware. I haven't gone through the errors one-by-one, so I can't comment on what they are. Most likely new features, but it's also possible that it's due to renamed variables.

I don't know whether the import/export functionality will work going from MS1 to MS2. You can always try and see if the numbers look correct or not.

jerrah

Thanks for that. I've resolved this with DIYAUTOTUNE.

The released file was from a pre-release version.