I probably should know this but .... I dont !

[sammy]

Sorry for the dumb questions but I need to understand how the configurator works,
Background
I changed the settings.ini file to handle my Lambda Sensor.

I chose ".... PLX ...” as it is supposed to work with my SLC DIY unit that I built.
I have the SLC wired up from its pin 9 (EGT Linier output) to the MS Relay board’s ‘o2’ input.
When I change anything in Megatune, it normally asks me to burn it to the controller, but when I change anything in the Configurator is'nt visable as to what happens to the changes.

When I view the AFR:Fuel Ratio gauge in Megatune it's stuck on full.
Everything else that I have connected so far work fine (I.e. CTL, ATS, TPS,etc )

Questions
When I change a setting in the Configurator how does the controller get to know about that?
Does that info wind up in the MSQ file too?

I cracked open the SMQ file in notepad but couldn't find the changes I made for the AFR sensor Maybe I was looking in the wrong place, or maybe there are not there? (hence why it’s not working?)

So how does the unit know to deal with my SLC and why won’t MS pick mine up? Any ideas?

Sam

[trakkies]

I'd use Tunerstudio. The Lambda sensor config is part of the setup before you start any tuning. It's in Project Properties Settings.
I've not used MegaTune for ages - but have read it may not work properly with some of the later codes.

[LT401Vette]

The settings in the Configurator are not actually sent to the controller. Those are really Project properties for the MegaTune Project.
They set up conditions flags so MT knows what parts of the ini to load when loading the ini files(s)

For example looking at this ini snippet from the MSII 2.905 ini:

Code: Select all

#if   NARROW_BAND_EGO
      egoTarget       = scalar,  U08,    598,             "v",        0.01000,   0.00000,  0.00,    2.00,      4 ; * (  1 byte)
#elif LAMBDA
      AFRTarget       = scalar,  U08,    598,             "Lambda",   0.006803,   0.00000,  0.00,   2.00,      3
#else
      AFRTarget       = scalar,  U08,    598,             "AFR",      0.10000,   0.00000,  0.00,   25.50,      1
#endif

You can see that the same memory address is used whether you have NARROW_BAND_EGO, LAMBDA or anything else set for your EGO sensor. However, only the the line that fits your settings will be loaded when you open the project, so the setting will be displayed to you with the defined units, scale and tranform of the raw data.

For MS1, all the AFR target values were always seen to the tuning software as raw ADC values, so All possible WB options were defined in the settings.ini, lambdaSensor.ini and if used elsewhere they needed to be defined in the controllers ini file too. Then the RAW ADC where converted by the Tuning Software into something that makes more human sense. The trouble with this was that you had to do as your doing and edit all these files every time you wanted to support a new sensor.

In MS2 this changed. The WB selection in the configurator isn't used for anything more than the above conditions:
NARROW_BAND - so all EGO values will be transformed to be displayed as volts
LAMBDA - EGO related values will be transformed to be viewed as Lambda
else - anything else which would cover any other EGO sensor selection will be displayed as AFR.

So if you have an MSII, in reality your EGO sensor selection in the configurator doesn't matter beyond whether it is a Narrow band, you want to view Lambda or anything else is assumed to be a WB sensor and displayed in AFR.
The values for AFR are returned directly from the firmware, the firmware gets them from when the AFR table was written during "Calibrate AFR Tables..." under the Tools menu.

[sammy]

Hi folks
thanks for you help, youve given me heaps to go on
Sam

[LT401Vette]

While my description tries to informative, I should say that I agree with Dave on the easy way out .

[sammy]

Thanks for your advice, I sorted the problem out after i read your response .... ( yep i didn’t calibrate the AFR properly)
I think I will be switching to Tunerstudio, but bvefore I do I have another question.

When I enter and Burn my calibration parameters for CTL & MAT and AFR(?) everything seems to work ok, but if I close down Megatune then start it again (with the same MSQ file.. etc), the values are defaulted to the original GM ones.

The controller seems to have the correct ones burnt in there; it’s just that Megatune doesn’t seem to store them anywhere outside of the controller.

So doesn’t Megatune write these to the MSQ file? I tried cracking open the file and doing a search in it, but they don’t seem to be in there.
sam

[LT401Vette]

Yes, the Calibration dialog is really a utility program built into the app. MT doesn't have visibility into.what is actually on the controller and doesn't save it to the msq.

[kjones6039]

When I enter and Burn my calibration parameters for CTL & MAT and AFR(?) everything seems to work ok, but if I close down Megatune then start it again (with the same MSQ file.. etc), the values are defaulted to the original GM ones.

Perfectly normal in MT & TS! The values are stored in MS when you click burn.

Ken