Confused about wideband selection...

[Broke4speed]

First off, TunerStudioMS is responsible for getting me back into the EFI game (currently running dual carbs after a previous MS'd supercharged car) .

Second...I'm slightly confused about the Wideband Selection portion of the project config. I am running an NGK Powerdex wideband, and it was added to the MT menus but it's not listed in TS. If I select 'other', how can TS know what the voltage output of my wideband is? I have the math required to convert the voltages to AFR or Lambda...but where do I put it?

[LT401Vette]

I'll add it to the next build easily enough, I didn't realize I was missing any that MT had.

In the mean time to get you going... Are you running an MS1 or MS2? It sounds like you are running an MS1.

[LT401Vette]

What MegaTune installer are you looking at? I'm not finding the Powerdex.

If you have the math, post it here I'll get it in.

[Broke4speed]

Hmm, I think I was either incorrect or something has changed. I'm not finding it either. For now, I've changed the way the TS interprets the 'unknown' AFR volts from it's original equation to the NGK one ( 9 + AFRVout x 1.4 ). It is an MS1, on a very confusing older spark layout. It's using the Bosch ICM, and it took me a bit of time to sort out which jumper configuration it was using, since the wires weren't labeled very well...and all one color. I don't imagine it's a huge issue, since I can easily just log the voltage vs the AFRs if I have to. I'm getting back into MS, and I recall that I had made a few changes to my .ini files that I simply cannot find now so I can't import them over.

Ah well, all this fuss and I can't even start my install for a few months. Nothing like being anal-retentive I guess .

[LT401Vette]

Ah well, all this fuss and I can't even start my install for a few months.

That takes the pressure off getting it sorted out before the next build

I will add that WB, at least to MSII.

For MS1 it is a little more complicated. Because... Adding the option and the math for MS1 is quite simple and just editing a couple text files. But, in MS1 the firmware ini file reverences the WB selected and ini changes to support the new WB would have to be added in several places. Not a huge effort for 1 firmware, but to cover all of them and not break compatibility with all the existing ini files makes it a little more sticky. I need to think out options a bit more.