MS3 .ini file
#1
MS3 .ini file
Hi everyone,
Fairly new here and finally getting ready to dip our toes into Megasquirt waters ... ;- ). Starting efforts to megasquirt our 92' Miata NA race car and wanted to ask if anyone would be willing to share a MS3(v3.0) .ini-file with us (bought our MS3 second hand and it unfortunately didn't come with one)?
Here is our planned configuration:
- Car: 1992 Miata NA (manual trans)
- Engine: 2005 NB VVT
- ECU: MS3 (V3.0) with MS3X
- Fuel: Batch (OEM 2005 injectors)
- Ignition: Wasted spark (OEM 2005 COPs)
- Crank Position: OEM 2005 sensor / trigger wheel (4 tooth)
- Cam position: OEM 2005 sensor (on valve cover)
- TPS: OEM 1.8 (variable)
- IAT: GM Open Element
- ICV: OEM 2005 (attached to TB)
- Coolant temp: OEM 1992 or 2005 sensor
- MAP: Native MS3
- O2: Innovate wideband
- VVT: OEM 2005 solenoid
- Alternator Voltage Control: undecided (NA 1.6 embedded or 1.8 ECU-control)
Thanks much in advance! :-)
Fairly new here and finally getting ready to dip our toes into Megasquirt waters ... ;- ). Starting efforts to megasquirt our 92' Miata NA race car and wanted to ask if anyone would be willing to share a MS3(v3.0) .ini-file with us (bought our MS3 second hand and it unfortunately didn't come with one)?
Here is our planned configuration:
- Car: 1992 Miata NA (manual trans)
- Engine: 2005 NB VVT
- ECU: MS3 (V3.0) with MS3X
- Fuel: Batch (OEM 2005 injectors)
- Ignition: Wasted spark (OEM 2005 COPs)
- Crank Position: OEM 2005 sensor / trigger wheel (4 tooth)
- Cam position: OEM 2005 sensor (on valve cover)
- TPS: OEM 1.8 (variable)
- IAT: GM Open Element
- ICV: OEM 2005 (attached to TB)
- Coolant temp: OEM 1992 or 2005 sensor
- MAP: Native MS3
- O2: Innovate wideband
- VVT: OEM 2005 solenoid
- Alternator Voltage Control: undecided (NA 1.6 embedded or 1.8 ECU-control)
Thanks much in advance! :-)
#4
Correct, the INI file collection is already included with all TunerStudio versions. And if you encounter a firmware version not included with its standard collection, it can look online and access an even larger database.
INI files define the menu configuration and available settings but do not contain any of the tune.
INI files define the menu configuration and available settings but do not contain any of the tune.
#5
Thanks, Matt. So just echoing back what I understand from your kind explanation ... the INI file selection is based on the installed firmware version (e.g. latest version 1.4.0) and expresses the technical functions and capabilities of the hardware in the software interface (menus). A base map (to be installed later) will provide the general settings to get the engine running and from which to tune further. Right?
Thread
Thread Starter
Forum
Replies
Last Post