Page 7 of 13
Posted: Tue Sep 13, 2005 9:04 pm
by Clinton_H
I just upgraded after using the first version of autotune now i can't get it to work again. I tried coping the ini file over to the custom ini and it's still not working. Any ideas? I don't have the box and autotune on the VE1 tune screen anymore, could someone do a step by step on how to move and where to move the new files if it's not too much trouble. Thanks.
Posted: Wed Sep 14, 2005 6:31 am
by efahl
Don't forget that I added the zLimits, too. You could use that to keep the decel leaning inside some reasonable range, say zLimits = 25, 200 and it won't ever go below 25%.
Posted: Wed Sep 14, 2005 6:34 am
by efahl
dbubb wrote:I've looked around several places, but have not been able to find out if v619 will work with MSnS Extra firmware 024s11
Dan,
Build 619 will work, but you'll have to edit the msns-extra.ini a bunch, because I reworked a lot of the #set names in build 555. The left column in the table below shows what the values were, the right shows what they are now... Other than that the 024 ini file should work fine.
Code: Select all
DIY_TechE_NonL DIYWB_NON_LINEAR
FIDLE FIDLE_GAUGE
GM300KPa DELETED (identical to MPXH6300A)
IAC IAC_GAUGE
Innovate0_5 INNOVATE_0_5_LINEAR
Innovate1_2 INNOVATE_1_2_LINEAR
MSpark DELETED
PWM PWM_GAUGE
TechEdge_Lin TECHEDGE_LINEAR
WB_NB_EMULATOR WB_1_0_LINEAR
WB_Non_Above WB_UNKNOWN
Zeit_100 ZEITRONIX_NON_LINEAR
Eric
Posted: Wed Sep 14, 2005 6:41 am
by efahl
Clinton_H wrote:I don't have the box and autotune on the VE1 tune screen anymore,
Clinton,
This is probably because the name of the table editor is not correct in the AutoTune section of your ini file. Grab the whole chunk from
http://www.msefi.com/viewtopic.php?p=72083#72083 and paste that into your custom.ini. Then change the line that reads
table =
veTableMap ; Should be the map3d_id of a TableEditor entry.
so that it reads
table = veTable
1Map ; Should be the map3d_id of a TableEditor entry.
for Extra or MS-II, or leave it alone for B&G v3 MS-I code.
Eric
Posted: Wed Sep 14, 2005 11:22 am
by bazzer
Still don't seem to be able to get it to work.
I am using 024s9 extra code and downloaded version 619 of Megatune.
Tried various options for the
Dont get any options in the Tune VE 1 screen.
What should I see without it connected ?
Help
Bazzer
Posted: Wed Sep 14, 2005 6:20 pm
by efahl
bazzer wrote:Dont get any options in the Tune VE 1 screen.
What should I see without it connected ?
Bazzer,
The only evidence that you have auto-tune enabled is a check box at the bottom of the dialog. I've just fixed up custom.ini in build 623, you might want to grab that build, copy the c:/Program Files/MegaSquirt/MegaTune2.25bxxx/carMtCfg/custom.ini to your car1/mtCfg/ directory and run with that...
(Oh, my server appears to have been hacked yesterday, so I took it down. I fixed my sig to point to downloads on here on MS-EFI.)
Eric
Posted: Wed Sep 14, 2005 11:30 pm
by bazzer
Cheers Eric
I just got it working. I had to put the options in the MS-Extra.ini file rather than the custom.ini file. Then I got the check box.
Many thanks !!!
Posted: Thu Sep 15, 2005 3:37 am
by boost junkie
I put the lines at the bottom of the msns-e.ini file and I got the check box... I haven't tried to use it yet. Should I move to the custom.ini file?
Posted: Thu Sep 15, 2005 5:43 am
by efahl
Putting the AutoTune in either place will work, but...
The reason I say you should put it in your custom.ini is because that file is left untouched by the MegaTune installer, so if you upgrade from build 619 to 623, then 623 ignores all your changes in msns-extra.ini (because it's in MegaTune2.25bXXX/mtCfg), but it keeps the changes in custom.ini. If you look in your car1/audit.log, then you'll see the sequence of file reads, and find that megatune.ini first reads msns-extra.ini, then at the end it reads custom.ini, so anything in custom.ini supercedes the stuff before it.
This is basically an ease-of-use issue and should have nothing to do with functionality.
Eric
Posted: Thu Sep 15, 2005 6:51 am
by boost junkie
Ah, makes sense... Thanks for clearing that up.