Hi Phil
Slowly getting to grips with TS but have a few questions:
Does TS use custom.ini ? If so, how do I get TS to use the custom.ini file?
In which directory should the custom.ini file be?
Does TS read the megasquirt-ii.ini file every time I open the project or only the first time I create it (using project / new project / other)?
Does TS read physically the same file I used when creating the project every time I start TS or does it create a copy of the file it read the first time I created the project and then use this copy from then on?
Does TS read the custom.ini file every time I open the project or only the first time I create it?
Does TS use custom.ini ?
Moderator: LT401Vette
-
- Super MS/Extra'er
- Posts: 1004
- Joined: Thu Feb 16, 2006 6:18 am
- Location: George, South Africa
Does TS use custom.ini ?
Kind regards
Philip
'74 Jensen Interceptor 440ci (EFI'ed with MS2 and wasted spark + GM 4L60e GPIO controlled - both on Extra FW)
Philip
'74 Jensen Interceptor 440ci (EFI'ed with MS2 and wasted spark + GM 4L60e GPIO controlled - both on Extra FW)
-
- Super MS/Extra'er
- Posts: 12733
- Joined: Sat Jul 16, 2005 8:07 am
- Location: Moorseville, NC
- Contact:
Re: Does TS use custom.ini ?
The idea is to get rid of the custom.ini, I want to put in UI's that let users do what they would have in the custom.ini, but for the short term, it does read the custom.ini every time from the dir:
[ProjectFolder]\projectCfg
If it finds a file in that folder it should read it. If it gives you any trouble, send me your custom ini and I'll see what's up.
It does read your megasquirt-ii.ini file every time, but not the one selected, a copy of it was placed in the dir:
[ProjectFolder]\projectCfg
This is to keep your project self contained, so you can just copy the project folder to another place or computer and it will still work fine.
Also, as a warning, TunerStudio is not fixed on the specific name megasquirt-ii.ini. It will be named that if that was the file name you browsed to, but most of the included files have their own names. So just copying a megasquirt-ii.ini to the folder won't do it. You need to either create a new project or set the ini in the Project Properties dialog. Once you have set it there, you can edit the one in the project folder.
[ProjectFolder]\projectCfg
If it finds a file in that folder it should read it. If it gives you any trouble, send me your custom ini and I'll see what's up.
It does read your megasquirt-ii.ini file every time, but not the one selected, a copy of it was placed in the dir:
[ProjectFolder]\projectCfg
This is to keep your project self contained, so you can just copy the project folder to another place or computer and it will still work fine.
Also, as a warning, TunerStudio is not fixed on the specific name megasquirt-ii.ini. It will be named that if that was the file name you browsed to, but most of the included files have their own names. So just copying a megasquirt-ii.ini to the folder won't do it. You need to either create a new project or set the ini in the Project Properties dialog. Once you have set it there, you can edit the one in the project folder.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
-
- Super MS/Extra'er
- Posts: 1004
- Joined: Thu Feb 16, 2006 6:18 am
- Location: George, South Africa
Re: Does TS use custom.ini ?
Thanks Phil
I've only recently discovered the value of the custom.ini file as being the solution to not having to modify the megasquirt-ii.ini file every time a new one comes along.
I've only recently discovered the value of the custom.ini file as being the solution to not having to modify the megasquirt-ii.ini file every time a new one comes along.
Kind regards
Philip
'74 Jensen Interceptor 440ci (EFI'ed with MS2 and wasted spark + GM 4L60e GPIO controlled - both on Extra FW)
Philip
'74 Jensen Interceptor 440ci (EFI'ed with MS2 and wasted spark + GM 4L60e GPIO controlled - both on Extra FW)
-
- Super MS/Extra'er
- Posts: 12733
- Joined: Sat Jul 16, 2005 8:07 am
- Location: Moorseville, NC
- Contact:
Re: Does TS use custom.ini ?
Yeah I've lived that to, back in the days there were new MS1 Extra firmwares coming out, it is a PITA to keep editing the main ini
That's why I don't want to get rid of the custom.ini purpose, I just want to put a UI on it so people don't have to dig in files. Usually users are serious MS'er before they understand the custom.ini.
That's why I don't want to get rid of the custom.ini purpose, I just want to put a UI on it so people don't have to dig in files. Usually users are serious MS'er before they understand the custom.ini.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
-
- Super MS/Extra'er
- Posts: 1004
- Joined: Thu Feb 16, 2006 6:18 am
- Location: George, South Africa
Re: Does TS use custom.ini ?
IMHO, that's only because nowhere (that I have seen at least) is the file struture of MT and purpose of the various ini files well described) - something rather lacking in my view. The MS documentation is nonetheless very good indeed - its just this topic that I think could be improved upon, perhaps under the title "advanced MT usage"...LT401Vette wrote:Usually users are serious MS'er before they understand the custom.ini.
Kind regards
Philip
'74 Jensen Interceptor 440ci (EFI'ed with MS2 and wasted spark + GM 4L60e GPIO controlled - both on Extra FW)
Philip
'74 Jensen Interceptor 440ci (EFI'ed with MS2 and wasted spark + GM 4L60e GPIO controlled - both on Extra FW)