Q about MLV and AFR target tables.
#1
Elite Member
Thread Starter
iTrader: (5)
Join Date: Mar 2007
Location: NYC
Posts: 1,970
Total Cats: 1
Q about MLV and AFR target tables.
When doing VE analysis does it use your AFR table from your MSQ or the one in MLV? Can you choose? Otherwise, you have to set the table in MLV by hand, correct?
#5
Elite Member
iTrader: (21)
Join Date: Jun 2006
Location: Point Pleasant, NJ
Posts: 2,957
Total Cats: 2
you can use the one that's in your MSQ or the default one in MLV(that you should change by hand first). You have that option in VE Analyzer. I use the default one in MLV for it's higher res.
analysis settings are to the right in VE Analyzer when you are showing the advanced options.
i don't run that table shown, thats the default one it came with. i don't tune with my desktop.
analysis settings are to the right in VE Analyzer when you are showing the advanced options.
i don't run that table shown, thats the default one it came with. i don't tune with my desktop.
#6
Elite Member
Thread Starter
iTrader: (5)
Join Date: Mar 2007
Location: NYC
Posts: 1,970
Total Cats: 1
I'm a retard. I was using an older version. For some reason when I originally installed it and updated it it didn't take, or something. I've got the latest version and I see the cell change feature now. Thanks
#7
Elite Member
Thread Starter
iTrader: (5)
Join Date: Mar 2007
Location: NYC
Posts: 1,970
Total Cats: 1
More MLV questions
As long as I'm asking dumb questions, let me continue.
1. What should you have ignition events, step size and authority set to in the ego setting in megatune while making a log for mlv?
2. Should they be at different values normally?
3. At what kpa should you be going open loop?
4. Could you stay closed loop always or is that not advisable?
1. What should you have ignition events, step size and authority set to in the ego setting in megatune while making a log for mlv?
2. Should they be at different values normally?
3. At what kpa should you be going open loop?
4. Could you stay closed loop always or is that not advisable?
#9
Boost Pope
iTrader: (8)
Join Date: Sep 2005
Location: Chicago. (The less-murder part.)
Posts: 33,052
Total Cats: 6,615
1. What should you have ignition events, step size and authority set to in the ego setting in megatune while making a log for mlv?
The same as for normal driving. When first starting out with a rough table, I'd set authority to 20, step to 2 or 3, and ignition events to maybe 20. The idea being to let the MS itself make rapid, large changes to get the mixture into the ballpark. During this time, I'd have MLV set to "Easy."After a day or two of that, as the tables start to take shape, turn the step down to 1, and run MLV at "Normal." A week or two of that will get the mixture quite close.
Presently, I have authority at 10, step size 1, ignition events 60. This seems to be a good daily driver setting once your tables are dialed in. I still run logs through MLV pretty much every day for fine-tuning, with MLV set to "Hard." Normally it tried to adjust a bunch of cells by 1 or 2, usually rich one day and lean the next. That tells me that the map is pretty much dialed in.
One thing to note- MLV isn't very good at tuning your idle cell. I'll usually do that one by hand in realtime, and then going forward, set that cell to a specific value regardless of what MLV does to it.
2. Should they be at different values normally?
See above 3. At what kpa should you be going open loop?
Depends on how much you trust your O2 sensor. Personally, I go open-loop at 100kpa for no reason other than that it's a nice round number. Start with the boosted cells set deliberately over-rich, and MLV will still fine-tune them even if MS not not making active corrections. 4. Could you stay closed loop always or is that not advisable?
I guess you could, but my theory is that when in boost, MAP and RPM are changing far too rapidly for Gego to be of much real use.
#11
1. What should you have ignition events, step size and authority set to in the ego setting in megatune while making a log for mlv?
The same as for normal driving. When first starting out with a rough table, I'd set authority to 20, step to 2 or 3, and ignition events to maybe 20. The idea being to let the MS itself make rapid, large changes to get the mixture into the ballpark. During this time, I'd have MLV set to "Easy."After a day or two of that, as the tables start to take shape, turn the step down to 1, and run MLV at "Normal." A week or two of that will get the mixture quite close.
Presently, I have authority at 10, step size 1, ignition events 60. This seems to be a good daily driver setting once your tables are dialed in. I still run logs through MLV pretty much every day for fine-tuning, with MLV set to "Hard." Normally it tried to adjust a bunch of cells by 1 or 2, usually rich one day and lean the next. That tells me that the map is pretty much dialed in.
One thing to note- MLV isn't very good at tuning your idle cell. I'll usually do that one by hand in realtime, and then going forward, set that cell to a specific value regardless of what MLV does to it.
2. Should they be at different values normally?
See above 3. At what kpa should you be going open loop?
Depends on how much you trust your O2 sensor. Personally, I go open-loop at 100kpa for no reason other than that it's a nice round number. Start with the boosted cells set deliberately over-rich, and MLV will still fine-tune them even if MS not not making active corrections. 4. Could you stay closed loop always or is that not advisable?
I guess you could, but my theory is that when in boost, MAP and RPM are changing far too rapidly for Gego to be of much real use.I spent 2 hrs manually tunning mine while chasing the green dot. I seem to be getting good mileage. But I had forgot to turn back on my ego correction and something else. Plus I forgot the original settings. So I've been reading back through the manual, and have decided to just copy my VE table, reburn the original map and change the table.
Next time I will keep a note pad. And I won't leave it setting for two weeks.
Anyway a detailed sticky "How To" to MLV would be awsome, and save alot of trouble. I know if I had known MS could be tuned in this manner. I would of jumped on the band wagon from the start.
Thanks.
#12
I'm unable to find the root cause for it, so I do what you mentioned. since I know what my car likes in the idle cells I just leave it there and set the Min. MAP = 34.
#13
As long as I'm asking dumb questions, let me continue.
1. What should you have ignition events, step size and authority set to in the ego setting in megatune while making a log for mlv?
2. Should they be at different values normally?
3. At what kpa should you be going open loop?
4. Could you stay closed loop always or is that not advisable?
1. What should you have ignition events, step size and authority set to in the ego setting in megatune while making a log for mlv?
2. Should they be at different values normally?
3. At what kpa should you be going open loop?
4. Could you stay closed loop always or is that not advisable?
Ok, I have the dumbest but maybe most simple question in this thread. Where in Megatune do I adjust these settings?
__________________
Best Car Insurance | Auto Protection Today | FREE Trade-In Quote
#16
Thankyou gentlemen.
__________________
Best Car Insurance | Auto Protection Today | FREE Trade-In Quote
__________________
Best Car Insurance | Auto Protection Today | FREE Trade-In Quote
#17
I agree that a good explanation of tuning the VE tables would make a good sticky.
Johndoe,
Make sure when you open MLV that you then open the MSQ file you are currently using. Your VE table automatically loaded in might not be the current one if you've been playing around with it.
Is people here primarily using the MLV to tune the VE table or are people using Autotune also? What exactly do the Autotune settings do?!?
Johndoe,
Make sure when you open MLV that you then open the MSQ file you are currently using. Your VE table automatically loaded in might not be the current one if you've been playing around with it.
Is people here primarily using the MLV to tune the VE table or are people using Autotune also? What exactly do the Autotune settings do?!?
#19
Elite Member
Thread Starter
iTrader: (5)
Join Date: Mar 2007
Location: NYC
Posts: 1,970
Total Cats: 1
I've read here that people don't have much luck or don't trust autotune. On other forums it seems like many more people are using autotune.
In regards to MLV maybe we should start a poll about who turns enrichments and ego off when logging for MLV and who leaves them on. In Joe's post above he makes it seem like it will work better with EGO correction on but I've read elsewhere that it doesn't matter one way or the other.
In regards to MLV maybe we should start a poll about who turns enrichments and ego off when logging for MLV and who leaves them on. In Joe's post above he makes it seem like it will work better with EGO correction on but I've read elsewhere that it doesn't matter one way or the other.
Last edited by johndoe; 07-29-2008 at 06:34 PM.
#20
I leave gego and enrichments on.
From the MLV FAQ-
Do I need to disable Gego for VE Analysis? - Gego is factored into the VE Analysis formula. Say the current table VE value for a single calculation is 50 and Gego is 110, 55 will be used as the actual VE value. If Analysis determines that it was lean for that record, the 55 value will be increased accordingly and added as a weighted recommendation. So by running with Gego on, you benefit by having both the ECM learned correction and the current O2 to use as input for correcting the table, instead of just the current O2 output. Having both is better, especially with a NB O2 sensor. So while I would recommend leaving Gego on with either a WB or NB sensor, I highly recommend leaving it on for a NB.
Do I need to disable Accel enrich for VE Analysis? - Accel enrich log records are filtered and ignored by the VE Analysis engine. So if you step through your log record by record in MLV, watch where you slammed your foot to the floor. The Accel indicator will be on, each of those records will not be used in VE Analysis, then continue steping forward the number of records you have WB delay set to +1. That is the first AFR value that will be used in VE Analysis after the accel enrich event. With the WB delay set correctly, most impact of accel enrich inaccuracy will be ignored. Also consider this, with Accel enrich on, there could be some residual over rich records, but if Accel enrich is disabled you have the same potential for some residual lean records. I think it is in your benefit to let VE analysis correct some of the impacts of accel enrich, if you really feel there is a section where accel enrich is causing excessive residual rich record, you should probably consider lowering your accel enrich for that area.
http://www.ideasandsolutions.biz/Meg...sFAQ.html#gego
From the MLV FAQ-
Do I need to disable Gego for VE Analysis? - Gego is factored into the VE Analysis formula. Say the current table VE value for a single calculation is 50 and Gego is 110, 55 will be used as the actual VE value. If Analysis determines that it was lean for that record, the 55 value will be increased accordingly and added as a weighted recommendation. So by running with Gego on, you benefit by having both the ECM learned correction and the current O2 to use as input for correcting the table, instead of just the current O2 output. Having both is better, especially with a NB O2 sensor. So while I would recommend leaving Gego on with either a WB or NB sensor, I highly recommend leaving it on for a NB.
Do I need to disable Accel enrich for VE Analysis? - Accel enrich log records are filtered and ignored by the VE Analysis engine. So if you step through your log record by record in MLV, watch where you slammed your foot to the floor. The Accel indicator will be on, each of those records will not be used in VE Analysis, then continue steping forward the number of records you have WB delay set to +1. That is the first AFR value that will be used in VE Analysis after the accel enrich event. With the WB delay set correctly, most impact of accel enrich inaccuracy will be ignored. Also consider this, with Accel enrich on, there could be some residual over rich records, but if Accel enrich is disabled you have the same potential for some residual lean records. I think it is in your benefit to let VE analysis correct some of the impacts of accel enrich, if you really feel there is a section where accel enrich is causing excessive residual rich record, you should probably consider lowering your accel enrich for that area.
http://www.ideasandsolutions.biz/Meg...sFAQ.html#gego