MS3 IdleVE table analyze live?

Zaphod · Post by **Zaphod** » Thu May 10, 2012 10:24 am

Is it possible to tune MS3 IdleVE table via VEanalyze live - or possible to get this feature.

LT401Vette · Post by **LT401Vette** » Thu May 10, 2012 10:36 am

I suppose you could add it to the ini. I haven't tried this, but it should work..

[VeAnalyze]
	;    tableName,  lambdaTargetTableName, lambdaChannel, egoCorrectionChannel, activeCondition
#if   NARROW_BAND_EGO
     veAnalyzeMap = idleve1Tbl, afrTSCustom, afr1, egocor1, { status6 & 0b00010000}
#elif LAMBDA
     veAnalyzeMap = idleve1Tbl, afrTable1Tbl, lambda1, egocor1, { status6 & 0b00010000}
#else
     veAnalyzeMap = idleve1Tbl, afrTable1Tbl, afr1, egocor1, { status6 & 0b00010000}
#endif
         lambdaTargetTables = afrTable1Tbl, afrTable2Tbl, afrTSCustom, 

       ; filter =  Name,        "DisplayName", outputChannel, operator, defaultVal, userAdjustable
       ; filter = minRPMFilter, "Minimum RPM", rpm,           <       , 500,      , true
       ; filter = maxRPMFilter, "Maximum RPM", rpm,           >       , 18000,    , true
       
         filter = std_xAxisMin ; Auto build with appropriate axis channels
         filter = std_xAxisMax ; Auto build with appropriate axis channels
         filter = std_yAxisMin ; Auto build with appropriate axis channels
         filter = std_yAxisMax ; Auto build with appropriate axis channels
#if NARROWBAND
#else
         filter = std_DeadLambda ; Auto build
#endif

#if CELSIUS          
         filter = minCltFilter, "Minimum CLT", coolant,       <       , 71,       , true
#else
         filter = minCltFilter, "Minimum CLT", coolant,       <       , 160,      , true
#endif
         filter = accelFilterTp, "TP Accel Enrich"  , engine,         &     , 16,       , false
         filter = decelFilterTp, "TP Decel Enrich"  , engine,         &     , 32,       , false
         filter = accelFilterMap,"MAP Accel Enrich" , engine,         &     , 64,       , false
         filter = decelFilterMap,"MAP Decel Enrich" , engine,         &     , 128,      , false
         filter = overrunFilter, "Overrun"    , pulseWidth1,  =       , 0,        , false
         filter = std_Custom ; Standard Custom Expression Filter.

LT401Vette · Post by **LT401Vette** » Thu May 10, 2012 10:57 am

I tried it on the bench anyway, that does it.

If you add just that one table to your custom.ini, the thing is that TS will only load VE Analyze for the one table as follows the standard model, it only loads the ini files included with TS if there was no such ini section in the ini's already loaded. So you really need to take the full contents of ms3VeAnalyzeMaps.ini and put it in a custom.ini, then add the above.

Place that custom.ini in your Projects projectCfg folder.

I have attached a custom.ini that is all set up. Just drop it in the folder:
[YourMS3Project]/project.Cfg/

Then when you open that project in TS, the idle table should be there..

Let us know how it works out.

Zaphod · Post by **Zaphod** » Thu May 10, 2012 12:53 pm

I am not sure I understand what this does then... Will the IdleVE table be in the veanalyze screen as reference? I will try tomorrow...

LT401Vette · Post by **LT401Vette** » Thu May 10, 2012 1:03 pm

Zaphod wrote:I am not sure I understand what this does then... Will the IdleVE table be in the veanalyze screen as reference? I will try tomorrow...

Yep... Just drop that custom.ini in the projectCfg folder and there will be a tab for the idleVe table.

Zaphod · Post by **Zaphod** » Thu May 10, 2012 11:24 pm

O.K. just did the test - when I start TS the idleVE table is active in the VEanalyze - but I can only switch to the normal VEtable1 once and not back to the idleVE. (that tab is greyed out)

LT401Vette · Post by **LT401Vette** » Fri May 11, 2012 5:20 am

Is Idle VE turned on in your Idle VE Settings?

What version firmware are you using?

Zaphod · Post by **Zaphod** » Fri May 11, 2012 5:40 am

Ah O.K. I stil had the idleVE turned of, because I didn't use it until now...

Works on the bench, have to get in the car to test "live"

Zaphod · Post by **Zaphod** » Tue May 22, 2012 10:24 am

Just wanted to give a heads up, that it works perfectly well..

djp0623 · Post by **djp0623** » Tue May 22, 2012 1:20 pm

When will this be a regular feature?

LT401Vette · Post by **LT401Vette** » Tue May 22, 2012 1:41 pm

I hadn't decided if it should be

I wanted to see how it works.
Dropping in the custom ini makes it pretty easy to try out.

To make it a regular feature, the one thing I would want to change is making it not the 1st tab in VE Analyze, it should be at the back. That will take a code change, so will be the next beta round.

shortbus · Post by **shortbus** » Tue May 29, 2012 10:33 am

cool.

Activate · Post by **Activate** » Wed May 30, 2012 6:37 am

It doesn't work for me,

I am using two table's one to get a more stable Idel VE1 (500-1049) and one for VE2 (1050-6000)

Thanks and greetings,

Erik.

LT401Vette · Post by **LT401Vette** » Wed May 30, 2012 6:41 am

Do you mean you are using table switching, not the idleVE table?

What is not working?

Activate · Post by **Activate** » Wed May 30, 2012 7:06 am

I am using table switching from 500-1049 and 1050 to 6000.

Also for spark I am hardware switching.

I will send my MSQ also.

2012-05-30_16.11.02.msq

I am getting errors when opening VE analyze live :

LT401Vette · Post by **LT401Vette** » Wed May 30, 2012 7:11 am

You appear to have an error. Your tables seem to be set up as OutputChannels.

What exactly did you do?

Activate · Post by **Activate** » Wed May 30, 2012 7:19 am

I put the text from the custom ini below my text in the custom ini, I have a gauge for boost,

This what I have in my ini :

[OutputChannels]
vacuum = {(barometer-map)*0.2953007} ; Calculate vacuum in in-Hg.
boost = {map < barometer ? 0.0 : (map-barometer)*0.1450377} ; Calculate boost in PSIG.

[GaugeConfigurations]
; Name Var Title Units Lo Hi LoD LoW HiW HiD vd ld
vacuumGauge = vacuum, "Engine Vacuum", "in-HG", 0, 30, 0, 0, 30, 30, 1, 1
boostgauge = boost, "Engine Boost", "PSIG", 0, 20, 0, 0, 15, 20, 1, 1

I have edit the other post!

Thanks and greetings,

Erik.

LT401Vette · Post by **LT401Vette** » Wed May 30, 2012 7:26 am

There is a [GaugeConfigurations] and [OutputChannels] section in the above attached custom.ini

So you can't just paste the contents of that ini in, you need to merge the section as a section can only be declared once in an ini.

Activate · Post by **Activate** » Wed May 30, 2012 7:33 am

Thanks for the answer,

How do I do that?

Thanks and greetings,

Erik.

LT401Vette · Post by **LT401Vette** » Wed May 30, 2012 7:34 am

take what ever lines you have in your ini under [GaugeConfigurations] and [OutputChannels] and add them to the [GaugeConfigurations] and [OutputChannels] sections in the attached ini

Megasquirt Support Forum (MSEXTRA)