[help needed] Critical error: Pin "PA0" continued from github

[Cartoonian]

Just to recall whats already been said

I was following along with the software guide provided here and I started up the console to this message:

EngineState: CRITICAL error: Pin "PA0" required by "TPS 1 Secondary" but is used by "MAF" 20200820@frankensoNA6

The logs contain this message repeating:

2020-08-20_17_07_39_910: Error processing version [20200820@25130source MIATA_NA6_VAF 412]

I have the Frankenso with the jumpers done for the na95.
Sorry if it's something simple.

I'm using Tuner Studio to change the pins, but selecting "Disabled" seems to have no effect on whether or not the error will appear. I have now changed the TPS input to the PA2 pin as seen here in an effort to get rid of the error to no avail. Now I'm going to reset to the NA6 settings and go from there.

[AndreyB]

there are four TPS sensors right? do you have three or four disabled?

[mck1117]

Your TPS config window should look like this. The secondary should be set to "NONE", as pictured.

image.png (109.96 KiB) Viewed 4800 times

[Cartoonian]

Okay I changed that and now the "Acc Pedal2" is set to the same thing. I'm going to go through and see how many more are assigned to PA0. I'll update you in a bit. Thank you for your help.

[mck1117]

there are four TPS sensors right? do you have three or four disabled?

In the pins page there are 2: TPS1 ADC input and TPS2 ADC input

The first was disabled and the second was set to PA0.

Unfortunately we haven't yet invented the ability to read minds, can you post a screenshot of what you're seeing in TS?

[Cartoonian]

Here is what I'm currently looking at:

[mck1117]

Do you have an accelerator pedal? If not, set that one to "NONE" too.

(if you have a cable throttle body, the answer is no)

[Cartoonian]

Yea I've got it set to none, everything is good now so far. I feel a bit like moron for this thread, but I appreciate the help from both of you

[mck1117]

Hey, no problem! It's a flaw we're working on figuring out a solution to. Right now, when we add a new analog input field (new sensor, etc), it ends up defaulting to something other than NONE, so a firmware update results in a state where you can end up with an invalid configuration.