VEAL tuning secondary injectors

[nathaninwa]

I wanted to tune low boost this morning using Veal and noticed it stops tuning when the primary injectors are turned off and I stage fully to the secondarys. Is this normal behavior, and can I work around it so the program looks at injector I and J?

[LT401Vette]

Are the secondary injectors running off a different table?

[nathaninwa]

Yes, I do table switching at 3000rpm. Secondary injectors are staged at 5psi. I bring up VE3 in Veal and it will tune everything below 150kpa (what the primarys run up to) but wwon't tune anything the secondarys are running.

[nathaninwa]

http://www.msextra.com/forums/viewtopic ... 1&start=40

page three, third to last post is my current tune. Post boost code 2 vss.

[LT401Vette]

The start auto tune button works independently for each table.

In VEAL did you click start on VE Table 3?
Is it on but saying table inactive even after the switch takes place?

[nathaninwa]

I didn't look to see if the inactive button changed, I'll check that at lunch today.

But, it did tune the lower half of the table where the primary injectors are working still.

Edit, II've also noticed this running veal on the data log, it won't correct in the secondary injector area, but will in the primary area.

[LT401Vette]

So your secondary injectors come on at 150 kPa using VE Table 3, and your primary injectors are still running on VE Table 1.
But this is where VEAL stops tuning VE Table 1 when the secondary injectors come on.

Is that correct?

[nathaninwa]

Kinda of.

I use VE1 and VE3 to create a larger VE table. I found with alot more vacuum points and rpm spreads cruise and general drivabilty went up, but I also have a large dynamic boost range I found table switching at 3000rpm worked best.

So ve1 is from idle to 3000 rpm and from 20 to 155kpa.
ve3 is from 3000 rpm with a 50 and 75kpa row, but then from 110 to 320kpa.

My staged switch point is in the 150kpa range

So it is possible to stage the secondarys in on VE1, but my spool doesnt allow that, so the secondarys are mainly on VE3.

I found this morning that anything below the 150kpa point on VE3 was autotuned, but anything where the secondarys are active there was no tuning.

Lunch is in about a half hour,I'll report back with the active/inactive indicator.

[LT401Vette]

What it seems the problem is, The table active logic for VE table 3 is the same as the Indicator for VE1&VE2 / VE3&VE4: status1 & 0b00100000
So VEAL is only active on VE table 3 if bit 5 is set in status1. This is the logic for it is a pure table switching where it is running on VE table 1 or 3. I think the secondary injectors is what is making that not right.

One sure fire way to make it work...

Change the name of the attached file to custom.ini and put it in the dir:
[YourTunerStudioProject]/projectCfg/

This will disable that logic and VE table 1 and VE table 3 will always tune if on.
I would be care full to only run VEAL on one or the other at a time though.

[nathaninwa]

I will see about loading this tonight. At lunch I saw the indicator switch top active, then back to inactive when I felt the secondarys kick in.

Thanks Phil, now I just need to revisit the trip/feet setup. I have it checked in the log fields, but only trip/meters shows up.

[nathaninwa]

Just to be sure, I saved as, put to desktop, renamed to custom.ini and dragged it over to my cars folder and dropped it in the projectcfg folder. That's all I need to do? Do I need to open the projectcfg folder and delete anything?

[LT401Vette]

That is it, just put it there. That has a modified version of the [VeAnalyze] ini section in the TS installer. The one with the installer is loaded lazy, if the section was already loaded it doesn't load what is in the installer. The custom.ini is always loaded right after mainController.ini if there is a custom.ini in the dir.

One thing to make sure of.... The way windows hides extensions by default, you may not see the .ini. If that is the case, son't add the .ini or the real file name will end up being custom.ini.ini and TS won't find it.

[nathaninwa]

I just looked in the cfg folder and its called custom.ini I dragged and dropped the file, closed TS, then reopened. Went for a drive, the indicator says correcting table the whole time Im above 3000rpm, but wont correct the table when the secondarys are on. Im running req_fuel switching and I made it pig rich, like a 9.5 under boost, then a 10.5 under boost and no correction was done, expect in the areas where the primarys are working.

I also tried VEAL on the datalog and it only corrected the small area the primarys were working. I had about 8 good pulls for it to try and work with.

[LT401Vette]

My bad, I had the Table inactive filter defined in 2 ways in that custom.ini, I only disabled 1 of them.
The attached should do it.

[nathaninwa]

I deleted the first custom.ini and renamed, dragged and dropped the second custom.ini. made 3 pulls into boost and the same corrections with primary only. I fattened it up again and got as much as 6 numbers changes per cell, but stops once the primarys stage out.

[LT401Vette]

Try it again... I didn't get all the #if blocks.

[nathaninwa]

Loaded new custom ini file, no go. Only tunes where the primarys are working.

[LT401Vette]

Are you able to see file extensions?

[nathaninwa]

Im pretty sure I can. What should I be looking for? Im running Windows 7.

[LT401Vette]

When looking in that folder, do you see a file called mainController or a file called mainController.ini