MS2extra alpha 3.0.3r boost control conflict
 

I just upgraded from 3.0.3n to 3.0.3r and I get a boost outpu control conflict. My boost control is on PAO, and I can't find anything in this version that uses this output. If I turn off boost control everything is fine. I reverted back to 3.0.3n and everything is OK.

Has anyone else had this issue?

So this is real horse poop. I have flashed back to 3.0.3n and loaded my latest msq, and a known good previous msq. I still get the error below.

https://www.miataturbo.net/forum/mem...ms/140/740.jpg

If I turn off boost control I get no error. Should I reinstall tunerstudio?

I worked through this, but have no idea what I did to get it to work. I flashed back to 3.0.3n and loaded a msq that was made with this firmware. I got the error posted above.

I then opened multiple msq files that were created with previous 3.0.3x firmware and it opened them up with no error.

I reopened a 3.0.3n and still got the error message.

I opened up the previous msq that worked, I believe it was a 3.0.3h and copied all my settings from a later msq screencap. I then saved it, opened it up, and it worked, no error message. I unplugged the power from my diypnp multiple times during this process to try and find the culprit.

Out of curiosity I wanted to see if this one would work if I reflashed 3.0.3r, and it works.

Earlier today I flashed back and forth between 3.0.3r and 3.0.3n multiple times trying to fix this. Full flash with jumper and without.

The only obvious difference from flashing now and from earlier is that my diypnp is not 25 degrees; it is now in the house.

Anyway, this has been a good waste of 4 hours :bang:

Do you have a copy of the MSQ that was giving you trouble? I could have a look at it and see if there are any clues in it about what's going on.

yes. I'll give you the one that wouldn't work and the new one that does. The new one was created from a msq that was 3.0.3h.

Good one: is from 1-10-2010
Bad one: 1-5-2010

The only thing I changed on 1-5-2010 were my spark and fuel tables. I couldn't open brains msq in tunerstudio so I manually put his values into my tables. I did change the req fuel calculator from 12.7 to 14.7. I've been running very rich under warmup. rpm stays at 2k for a while.

I think I see what's going on: Coil on plug output uses PA0 as spark output D if you don't have the ECU type specified as a Microsquirt.

When I am burning a new firmware do I select the ms2extra version of the firmware or the microsquirt2extra version? I always select the ms2 version. If I'm supposed to select the microsquirt2, then I bet I haven't been burned on this before because I normally tell tunerstudio to keep the tunerstudio settings.

Tell it you have a Microsquirt. This may have been the problem.

Thanks, will do. I'm glad someone knows what they are doing. I need all the help I can get. :bowdown:

I changed it to microsquirt. I started messing with it tonight. All of a sudden after it won't crank. I star messing around and get teh boost control error again. Now it doesn't give me the option to selece PAO for boost control. Only Fidle. Did they change the code for the "r" version so we have to use a different pin for boost control? I'm in the process of going back to "h"

No - I suppose now you have turned

Microsquirt module to activated, as well as

Microsquirt full to activated.

Please set Microsquirt_full to deactivated.

Its in the Project Properties - Settings menu.

Greets

I always set microsquirt full to deactivated and microsquirt module to activated. But thanks, I did make that mistake initially when I first started with diypnp and tunerstudio.

I have been making the mistake of telling the firmware uploading software to use MS2 instead of microsquirt2. I fixed this last night.

I still select MS2 in project properties.

My laptop went dead last night and I forgot my power cord at work. I then started on my desktop computer. I reflashed telling it microsquirt. I set up a new project. It initially gave me a "pin conflict" error when I had PAO for boost and D14 for coil on plug. I then changed coil on plug to the other option and burned it to the ECU. I then unplugged it and plugged it back in. No error. I then switched the coil on plug setting back to D14 and burned it to the ecu, power cycled, and received no error. Just as I was setting my iat, clt values my computer died. (power supply, I think) In any case I did not get to test it.

I am going to remove and reinstall tunerstudio on my laptop. I think I have a setting saved somwhere that keeps getting reflashed to the ecu.

Update: After reinstalling the software I don not get any conflict on my msq. Hopefully this solves the problem. I will try it tonight.
In case anyon ewants it. Here is an updated inc file that includes an AEM 230x wideband option in project properties, and it includes diyautotune clt/iat resistor values in the drop down menu. You will need to remove the .txt and replace it with .ini

I uninstalled tunerstudio and reinstalled it. All is well. I think a series of mistakes on my part caused the problem in the first place.