MS1-Extra
Quick Guide to Tuning and Using MegaTune

Only for use with the MS1 Extra code (MS1 - 68H908 based microprocessors)

By Philip Ringwood (daxtojeiro), James Murray (jsmcortina) and Ken Culver (muythaibxr)


Before you start any hardware mods please read this entire manual and the Software Manual, available HERE.

For other MS1 Extra Manuals please see HERE

Warning for
E-Bay buyers!!
Please see the Official Suppliers list before buying through E-Bay.
This is there for your protection.

Please Note:

All of these instructions / diagrams are to be used at your own risk, like most things there is more than one way to do the same thing, what we have tried to do is to offer a method that we have tested or that others have tested for us. No warranty expressed or implied.

Use at your own risk.


To-Do-List Before Starting -- Basics to Getting Started -- Tuning Offline using Datalogging -- Tuning the VE table Live -- Finalising your VE Table

Adding another Gauge (Speed/Oil Pressure/Fuel Pressure, etc) -- Datalogging another sensor

 

Important Note:
Adjustments made in MegaTune are only sent to the ECU if you press the "TAB
Button" on your keyboard after making the change!! (This doesn't apply when tuning the maps in 3D mode)
In order to keep changes ensure you select BURN TO ECU, this then sends the adjustments into the permanent memory of the ECU!
I find the best method to make adjustments is to alter the value then press the TAB Button, this ensures they are sent. If the change is OK click BURN TO ECU, check it has been sent by clicking FETCH FROM ECU. You'll soon get the hang of it :o)

 

To-Do List Before Starting

Once the ECU is wired up to the engine and the sensors are all connected there are a few things that need to be done to help you get running smoothly.

• PWM settings for Hi-Lo Impedance Injectors. (Constants Page in MegaTune)

You need to measure the resistance of the injectors your engine is using. Pop the connector off the injector and measure the resistance across the 2 pins on the injector in ohms using a multimeter.
If the resistance is greater than 10 Ohms then you have Hi-Impedance injectors.
If the resistance is lower than 4 Ohms you have Lo-Impedance injectors.

If you are running high-impedance injectors (greater than 10 Ohms), then set the:
PWM Time Threshold = 25.4 mS
PWM Current Limit (%) = 100%.

If you are running lo-impedance injectors (less than 4 Ohms), then start with:
PWM Time Threshold = 1.0 mS
PWM Current Limit (%) = 30%

• Throttle Position Sensor Calibration:

With the ignition on and the engine not running go into Tools - Calibrate TPS. With the throttle fully shut click on the top "GET CURRENT" then with the throttle fully open (foot on throttle pedal) click the lower "GET CURRENT"
The values are in raw ADC (MS1...0 - 255 = 0 - 5V )
The closed value MUST be lower than the fully open value, if not you have the throttle position sensors 5V and ground round the wrong way.

Note: The setting changes wont take place untill MegaTune and the MS ECU is restarted.

• Calibrate the Air and Coolant Sensors:

If you haven't done so already then have a read on how to calibrate OEM sensors. Remember that in MS1-Extra MegaTune needs to have 3 ini files saved in the correct directory.

To check the sensors are roughly correct, check that the readings in MegaTune for Coolant and Air are around the same temperature reading before starting the engine. If they are > 10deg or so apart from each other then you should check your sensors resistances again.

• Acceleration Enrichments:

The Thresholds are better turned so high that they don't cut in whilst tuning the VE table, this ensures you are not trying to compensate in the tuning for anything other than the VE table. To do this go into the Acceleration Wizard and set the TPSdot Threshold and the MAPdot Threshold to something like the below settings:

 

Basics to getting Started

It is important to understand that if the engine doesn't start or fire at all then it is NOT the VE Table (fuel map) that needs tuning, so don't go off and adjust that as yet. The ONLY fuel that goes into the engine during cranking is set by the Cranking PW, so if it doesn't fire you will need to look at the Cranking. Once it fires and the RPM goes above approx 300RPM then the VE table is used by the ECU. Start with this check list:

• Always check timing at cranking before getting too carried away with fuel. If the sparks don't come at the right time then it won't start, so check its firing with a strobe at approx. 10deg BTDC during cranking. If it doesn't, fix that first by checking/adjusting the Trigger Angle in Spark Settings, twisting the dizzy, checking alignment of crank / cam sensors, etc.

• Check that you have an RPM reading during cranking on the MegaTune screen, it needs to be reasonably steady and around 150-300RPM, if you have no RPM reading then you have a trigger problem, the ECU is not seeing your hall sensor or VR sensor, etc.

• Check you get a PW reading on the MegaTune screen, this should be wrougly the same as you've set in Cranking Settings. If you get a PW of ZERO then you may have the throttle pot wired up wrong. The ECU goes into Flood Clear Mode when youve got your foot flat on the accelerator to clear a flooded condition, this means it adds NO fuel.

•• For MS1-Extra if the TPS is OK but you still get a PW of ZERO then check the setting for TPS for Flood Clear aren't set too low in More Cranking Settings .

 

• If you need to open the accelerator during cranking (foot on throttle a little) and then it starts you are adding too much fuel during cranking as you are letting in more air to weaken the mixture with your foot. So reduce the Cranking PW time at the relevant temp setting.

• If it doesn't fire despite what you do with the throttle it will probably need more fuel, only add a little at a time, 0.2mS increments.

It is a good idea to set the Priming Pulse to ZERO whilst tuning, the Priming Pulse adds a little amount of fuel to prime and bleed the injectors on power up. This can soon flood the engine whilst you are tuning as you will turn the ignition on and off a lot!

If you are starting the engine for the first time then it is recommended to adjust the REQ_FUEL (in the Engine Constants page) to richen or lean the engine until it is warm, an increase in REQ_FUEL richens the mixture across the whole map, a decrease in it leans the mixture. (NOTE: Press the TAB button and then press BURN TO ECU to force your settings into the ECU) We recommend using the REQ_FUEL because you can then re-tune you VE table to keep it all smooth for a good starting point, if you adjusted the VE table to keep it running then the chances are your idle areas would be either very high or very low compared to the rest of the map. Once you have the engine warm you can set the REQ_FUEL back to the calculated or original value, BUT you then will need to reset your VE table to compensate. (Basically the REQ_FUEL increases/decreases fuel over the entire map, so when you reset it you will need to change the VE table so the same amount of fuel is added) To do this, ensure the ECU is powered up but engine is not running. Remember what the REQ_FUEL value is for a reasonable idle (in other words what the value ended up being while you were adjusting it to get it to run OK for the first time), then change the REQ_FUEL back to where it should. Next go to the VE Table and select "TOOLS - VE Specific - Reset ReqFuel" and set the Current ReqFuel value to the value you remembered from earlier and the New ReqFuel value to the calculated or original value. When it asks you to burn select YES, this will then adjust the whole VE table, in the case below the VE values will increase to compensate fro a decrease in REQ_FUEL, so you should end up with a good smooth map to start tuning from.

Once you have the idle tuned when warm dont touch it again while the engine is cold. Only adjust the Warmup Enrichments to get a nice idle / running engine when the engine is cold. This enrichment is basically additional fueing thats added ontop of the fuel map (VE Table) to richen the mixture when the engine is cold. 100% would mean it uses the fuel map, 110% means it adds 10% to the fuel map, etc. So next time you start it from cold get ready on the warmup enrichments page.

 

Please Note:

If you have lo-impedance injectors (less than 4 Ohms) , after getting a good idle you need to adjust the PWM duty cycle on the Constants Page in MegaTune down in 1% increments until you notice a change in idle quality (be sure to hit the "send to ECU" button each time you change the value). This is the point where the current limit is too much and the injectors are not being held fully open. Then move the value back up 3 - 5% (for example, if the idle falters at 45%, then put in a number of 48% to 50%). Move on to adjusting the time threshold. Lower the time threshold by 0.1 milliseconds at a time until the idle quality deteriorates. Then increase it 0.3 ms.


Don't start driving until you have a good stable idle, it isn't very safe to drive a car which won't idle. Adjust the fuel map once the engine is warm to get a strong idle, you should use the Live Mapping theory below to get a smooth idle, it will probably be a little rich, don't worry too much to start with. At idle a small change in the VE value can change the mixture a lot in some cases, so take time to adjust this and give it time to react.

 

Tuning Offline using Datalogs:

The MS will naturally datalog the inputs from TPS, O2, Coolant Temp and the Air temp sensor. It also datalogs the fuel Pulse Width, Dwell, Spark Advance, etc, etc, etc, there are in excess of 20 seperate streams of data that MS1-Extra logs (MS2-Extra streams a lot more than that) onto a laptop whilst it's running the datalogger.

To do this you need MegaTune running and select File -- Datalogging -- Record or ALT-L

The default file name is a time/date stamp. Once you select SAVE it starts datalogging a file with all the above parameters being logged. The bottom right corner of MegaTune shows LOGGING highlighted in black.

The file is saved in an xls (excel) format. This can be opened in Excel if you wish, but it's better to use MegaLogViewer, this is a superb program and can help you tune your engine quickly. If using a WideBand lambda sensor and MS1-Extra, make sure you select the correct wideband sensor from the list in MegaLogViewer from the drop down menu in Calculated Fields - WideBand O2 AFR tab. If using a narrowband you don't need to do this. If you're using MS2-Extra then the ECU would have sent the actual AFR rather than the voltage so no conversion is needed.

Once you have datalogged a gentle run in the car, pull over to the side of the road and shut MegaTune down. Open MegaLogViewer and open the datalog, it will be stored in "c:/programfiles/megasquirt/car1/" Then select Open MSQ and select the msq you were using at the time the log was made. You will be able to see on the datalog where the engine was running lean or rich, etc, by moving the log around looking at the O2 reading and watching the highlighter move on the VE and Spark tables. This gives you the points to adjust on the VE table. If you want to try the VE Analyser, which is highly recommended, select it and select Run Analyser. Obviously if your using a wideband lambda the results will be far more accurate and you can then change the AFR targets in the MSQ. If usin a narrow band the targets are a little harder to get as the sensor doesnt really give any information other than rich/lean of 14.7 AFR.

 

Before datalogging;
• Turn the Accel Enrichment off, by setting the thresholds to an excessive amount, e.g. MAPdot 3000 or TPSdot to 20V/Sec in the Accel Wizard.
Turn EGO Correction ON when using MegaLogViewer, see HERE for more on how to set up the O2 correction (EGO).
Ensure the engine is up to operating temperature before logging, this ensures you only tune the VE table and no additions are thrown into the mix.

 

After you've run the analyser the VE table will have several red numbers, these are the values that have been changed by the analyser. Basically it looks at the AFR for the points of the VE table in the datalog and decides how much to change them depending on the average value of the AFR in the datalog. Click on Accept New Table and then EXIT.Save the msq (Save MSQ As) and then close MegaLogViewer. Turn the MS ECU back on and open the new msq file in MegaTune, Burn it to the ECU and your ready for another datalogging session. It is highly advisable to start at low loads and revs, do several logs and only move on to next rpm range slowly when the changes become small in the analyser.


Tuning the VE Table Live

Ensure the engine is up to operating temperature before starting tuning the VE table so that there are no warmup enrichments added to the mix. Also turn the accel enrichments off by setting the MAPdot to 3000KPa and TPSdot to 20V/S so that all your tuning is the VE. I always turn the EGO correction off so that theres no correction going on, to do this goto Basic Settings -- Exhaust Gas Settings and set the Controller Step Size to ZERO. Now all your going to tune is the table, the corrections can be turned on again later once the table is tuned.

A lambda sensor is critical to tune any engine unless your a real expert! A wideband lambda will make life so much easier too.

Start by driving slowly, keeping load low and engine speed low untill your happy that all is OK then move upwards. To tune the VE table live there are a couple of options. The best way is to use the 3D display (MegaTune Tuning -- VE Table) and drive to each cross point tuning as you go, this will need a driver and a passenger!! Te green blob is where the engine is on the map and the cross hair (RED) is where you are tuning, so use the arrow keys to go to the points you want to tune. Use the AFR gauge in the left side of the screen to see what the mixture is doing and increase or decrease the points where the green blob is to get the AFR correct. To increase the value (richen) press the "Q" button to slowly increment it or the "E" button to increase the value by 5. Like wise the "W" button decreases it and "R" leans it off by 5 in one go. By gradually driving and tuning the points you will soon get a feel for what is needed. Its impossible to tune all the points, as its unlikely youll drive at light throttle at 6000rpm, etc, so you will have to estimate the table at some of the points. The table should slowly increase in value as you go up the KPa scale and also increase in value as the RPM increases, it may fall off slightly as you pass the maximum torque point.

If you start off and you find your having to drastically change the values then it may be better to pull over and adjust the entire table in the same direction before going too far. So say you've had to add 10-20 to the first few points, you will find the entire map will probably need the same doing before you can fine tune it.

To do this pull over and close the 3D table down, and open the VE Table in Basic Setting -- Fuel VE Table1
As the engine should have already been tuned for a good idle leave that part alone for now. All we need to alter is the parts where you feel were a long way, so if cruising at 2000RPM was nearly OK but as soon as you went up the load a little it went weak you will need to increase the table all the way across the rev range but only above crusing KPa. To do this move the mouse cursor to the start of where you want to alter (e.g. 100KPa - 600RPM) and hold the left mouse key down, drag across the VE table and a box will appear. Position the box so it is all the way across the RPM range above the crusing KPa.

Now we have the area to increase highlighted and a box appears in the right corner which we can use to change the highlighted area. In this case we want to add say 20 to the area, so we will enter 20 in the box and hit the "+" on the screen. Equally we could decrease it by 20 by pressing the "-" or times it by say 1.05 or what ever. The "=" would set all the highlighted range to 20 in our example.

It is important to note that untill you "BURN TABLE" the changes you make will be lost if you turn the MS ECU off, so select File -- Burn to ECU every so often or "ALT - B"

The AFR you aim for can vary depending on your engine, but usually an AFR of 14.7 is for cruising and 12.5-13.5 for wide open throttle, a boosted engine will need a richer mix, maybe up to 11.5AFR.

 


Finalising your VE Table

Once youve done a few datalogs and run them through the analiser or your done some live tuning, you will probably notice the map has only been tuned where you drive, so the low KPa areas of 5000+RPM would not have been changed and some other areas may have been missed. This is because you dont drive there, but to keep the map lookin good it is a good idea to look at it every-so-often during tuning and smooth it out a little if theres large lumps or if it leaving small numbers next to large ones. To do this simply look either at the VE Table in Basic Settings or in the 3D graph. If you look at the VE table above, youll see a smooth increase in value as the RPM increases and as the KPa increases, this is how it should be, if you have anything like below it may be that the values around the large numbers need increasing and that value may need decreaseing as it is probably compensating for too small values around it.

In this example the numbers no longer increase with KPa like they should and theres a couple of large numbers next to numbers a lot smaller, this isn't right. Start by smoothing out the numbers around it and re-tune those points, ensure your Accel enrichments are off, etc. Don't be too worried by this, the example is an extreme just to show you what to look for. It shows that you need to tune all areas around the points your drive to get a nice map rather than a lumpy map.


Adding another Gauge (Speed/Oil Pressure/Fuel Pressure, etc)
There are 2 ADC (Analogue to Digital Convertor) inputs (JS4 and JS5) on the MS1 processor that can be used to send a 0-5V signal to. The circuit below will need to be built to condition the signal and protect the processor. JS4 and JS5 can be used as the input pads on the MS1-Extra ECU.

NOTE: It is VERY important the microprosessor is never connected to anything more than 5V, anything higher WILL permanently damage it!!!

Once the circuit is wired up the next changes will need to be made to MegaTune so it shows / logs the inputs. This may sound daunting, but it's not as bad as it seems.

Start by opening the msns-extra.ini file found in c:/programfiles/megasquirt/megatune2.25/mtCfg using NOTEPAD or a similar text editor.
You may have to alter the view in windows to see it's description as an ".ini" file, it is a size of approx 184KB

This file is where we can get MegaTune to display and log various parameters and change the ADC (raw data from the 0-5V Analogue to Digital Convertor) to something we can understand in the real world. The ADC varies from 0 - 255, thats 0 - 5V on the input. So if we have 5V on the analogue input the ADC would be 255. If we have 2.5V on the input the ADC would be 127 and 0V on the input the ADC = 0.

So every ADC count is:
5V / 255 = 0.01961 Volts,
this means the resolution in MS1 for ADC is 0.01961 Volts

So the ADC value is:
ADC Value = Volts at input / 0.01961

Or looking at it the other way
Volts = ADC * 0.01961

Now we know what ADC means we can change the msns-extra.ini file so MegaTune displays the value we can understand. There are 2 ADC ports spare on the MS1-Extra ECU, these are JS4 and JS5. In the msns-extra.ini file these are refered to as egtADC (JS4) and fuelADC (JS5). So the value of egtADC and fuelADC will be 0-255 depending on the voltage at its input pad. If you search for these names in the ini file you will see where they are used to generate a few gauges, etc.
Search for "timeroll" it should bring you to here:

tpsDOTTY = { mapProportion4 ? 0 : (tpsADC - tpsLast) * 0.19 } ; * 0.019 / 0.1 to convert it to V from ADC and to 1Sec from 0.1Sec
mapDOTTY = { mapProportion4 ? (mapADC - tpsLast) / 0.1 : 0 } ; Divide by 0.1 to convert from 0.1Sec to 1Sec

tpsDOT = { tpsDOTTY < 0 ? 0 : tpsDOTTY } ; Only display positive or it gets confusing to read
mapDOT = { mapDOTTY < 0 ? 0 : mapDOTTY } ; Only display positive or it gets confusing to read

Timeroll = { portc & 0b00000100 }
waterIlog = { porta & 0b00010000 }

MAFVolts = { fuelADC * 0.0196078 }
;-------------------------------------------------------------------------------

[Datalog]

Note: A semicolon ";" in front of anything in MegaTune ini files means it is ignored, so comments can be placed after a ";", etc.

Here you will see that variable name "fuelADC" is used to generate the value of a name MAFVolts, basically this means that the ADC is converted from a raw count back into a voltage. (as Volts = ADC * 0.0196078) So if you simply wanted to know the volts at the input then there is already the facility to do that. Simply connect the input to JS5 and select the MAFGauge when in MegaTune. See HERE

But we want to try something a little different. We are going to set up a pressure sensor which has a linear 0 - 5V output = 0 - 75psi
To do this we need to work out what each ADC count will mean in terms of PSI.

So at 75psi we will have 5V (255 ADC)
Therefore every ADC count means 75psi / 255 = 0.2941psi

To make MegaTune display the pressure in PSI we will need to add a variable name and a formula just under the MAFVolts statement e.g:

tpsDOTTY = { mapProportion4 ? 0 : (tpsADC - tpsLast) * 0.19 } ; * 0.019 / 0.1 to convert it to V from ADC and to 1Sec from 0.1Sec
mapDOTTY = { mapProportion4 ? (mapADC - tpsLast) / 0.1 : 0 } ; Divide by 0.1 to convert from 0.1Sec to 1Sec

tpsDOT = { tpsDOTTY < 0 ? 0 : tpsDOTTY } ; Only display positive or it gets confusing to read
mapDOT = { mapDOTTY < 0 ? 0 : mapDOTTY } ; Only display positive or it gets confusing to read

Timeroll = { portc & 0b00000100 }
waterIlog = { porta & 0b00010000 }

MAFVolts = { fuelADC * 0.0196078 }

Oilpress = { fuelADC * 0.2941 }
;-------------------------------------------------------------------------------

[Datalog]

Note: All names and variables are CASE SENSITIVE!!

Now the variable name "Oilpress" in MegaTune will be a pressure value. Next we need to tell MegaTune to display it as a gauge. To do this we need to search for "fuelGauge" in the ini file, this will bring us to:

; Extra Stuff

fuelGauge = fuelpress, "Fuel Pressure", "lb/in", 0, 80, 30, 40, 60, 65, 1, 1
#if CELSIUS
egtGauge = egttemp, "EGT", "C", 0, 1000, 0, 0, 1450, 1480, 1, 1
#else
egtGauge = egttemp, "EGT", "F", 0, 2200, 0, 0, 1450, 1480, 1, 1
#endif
CltIatGauge = CltIatDeg, "Clt IAT Angle", "Deg", -10, 10, -10, -10, 10, 10, 1
KnockGauge = KnockDeg, "Knock Retard", "Deg", -20, 0, -20, -20, 1, 1
egoCorrGauge2 = egoCorrection2, "EGO Correction2", "%", 50, 150, 90, 99, 101, 110, 0, 0

These are the gauges that we ave added for the extra code. As you can see there is an egtGauge, this converts a 0-5V signal to 0-1000C display for EGT, etc.

So we will add an Oil Pressure gauge by adding:

; Extra Stuff

oilpGauge = Oilpress, "Oil Pressure", "PSI", 0, 75, 0, 0, 60, 70, 0, 0

fuelGauge = fuelpress, "Fuel Pressure", "lb/in", 0, 80, 30, 40, 60, 65, 1, 1
#if CELSIUS
egtGauge = egttemp, "EGT", "C", 0, 1000, 0, 0, 1450, 1480, 1, 1
#else
egtGauge = egttemp, "EGT", "F", 0, 2200, 0, 0, 1450, 1480, 1, 1
#endif
CltIatGauge = CltIatDeg, "Clt IAT Angle", "Deg", -10, 10, -10, -10, 10, 10, 1
KnockGauge = KnockDeg, "Knock Retard", "Deg", -20, 0, -20, -20, 1, 1
egoCorrGauge2 = egoCorrection2, "EGO Correction2", "%", 50, 150, 90, 99, 101, 110, 0, 0

This means we have called the gauge oilpGauge, it displays the Oilpress variable we defined earlier and the label for the gauge will be Oil Pressure. The Gauge will also display PSI in the middle to show its in PSI.
The next two number represent the max and min the gauge will display, i.e. 0-75PSI.
The next four number are what te value need to reach to turn the gauge a different warning colour, Ive set the first two to ZERO, this means they wont be used as a warning untill it reaches 60PSI then it will change colour.
The last two number represent how many decimal points the display goes down to, in our case theres no need for any decimals so I entered ZERO, but if you were measuring smaller values then here you can change it to your desired values.

Getting the EXACT syntax is quite critical, if you miss spell or miss a commar out it could stop MT running. So save a copy of the original ini file somewhere safe before you start.

To select your new gauge to work you have a few options. You can change the gauge on the front screen of MT by right clicking on a gauge and SWAP it to one in the list, your gauge will be in the list now too. This method is a little painful as you must swap it every time you restart MT. A better way is this:

Open the msns-extra.ini file again. Find "[FrontPage]" in the ini file. This will bring up the main screens layout in the ini file:

#if NARROW_BAND_EGO
egoLEDs = 0.0, 1.0, 0.5 ; NB settings.
#else
; If you reverse these range values as you see below, then the LED
; bar will work as you expect, high on the right, low on the left.
egoLEDs = 4.0, 1.0, 2.5 ; WB settings.
#endif

; Gauges are numbered left to right, top to bottom.
;
; 1 2 3 4
; 5 6 7 8

;Gauge Setup 0

gauge1 = RpmHiResGauge
gauge2 = cltGauge
gauge3 = pulseWidth1Gauge
gauge4 = dutyCycle1Gauge
gauge5 = mapGauge
gauge6 = matGauge
gauge7 = afrGauge
gauge8 = advanceGauge

#if ALPHA_N
gauge5 = tpsADCGauge
#endif

Here is where MegaTune decides which gauges to use when it starts to run. So change one of these to your new gauge and it will start with yours on the main display:

#if NARROW_BAND_EGO
egoLEDs = 0.0, 1.0, 0.5 ; NB settings.
#else
; If you reverse these range values as you see below, then the LED
; bar will work as you expect, high on the right, low on the left.
egoLEDs = 4.0, 1.0, 2.5 ; WB settings.
#endif

; Gauges are numbered left to right, top to bottom.
;
; 1 2 3 4
; 5 6 7 8

;Gauge Setup 0

gauge1 = RpmHiResGauge
gauge2 = cltGauge
gauge3 = oilpGauge
;gauge3 = pulseWidth1Gauge
gauge4 = dutyCycle1Gauge
gauge5 = mapGauge
gauge6 = matGauge
gauge7 = afrGauge
gauge8 = advanceGauge

#if ALPHA_N
gauge5 = tpsADCGauge
#endif

Note that the statement gauge3= pulseWidth1Gauge now has a semicolon infront of it, so that will be ignored by MegaTune, otherwise MT would have used that gauge if it was lower in the text file.


Datalog a New Sensor:

Once the sensor has been added into MegaTune (see above) it is also possible to datalog it and veiw it in MSLVV. To do this you simply need to change the msns-extra.ini file again. So find "MSLVV_COMPATIBLE" in the ini file. A little lower (actually this is the very bottom of the file) you will see this:

entry = advSpark, "Spark Angle", float, "%.1f"
entry = egttemp, "EGT", int, "%d"
entry = fuelpress, "Fuel Press", int, "%d"
entry = KnockDeg, "Knock", int, "%d"
entry = RpmHiRes, "RPM", int, "%d"
entry = barometer, "barometer", int, "%d"
entry = porta, "porta", int, "%d"
entry = portb, "portb", int, "%d"
entry = portc, "portc", int, "%d"
entry = portd, "portd", int, "%d"
entry = batteryVoltage, "batt V", float, "%.1f"

; entry = XForce, "X GForce", float, "%.2f" ; X on X7
; entry = YForce, "Y GForce", float, "%.2f" ; Y on X6
; entry = MAFVolts, "MAF Volts", float, "%.2f" ; MAF on X7

; TEST ONLY - DONT USE
; entry = iTime, "iTime", int, "%d"
; entry = iTimeX, "iTimeX", int, "%d"
; entry = iTimefull, "iTimeFull", int, "%d"
#endif

Basically these are the parameters that are logged when MegaTune starts datalogging. Here we can enter our variable we made earlier "Oilpress". To do this we simply type in as follows (remember it is CASE sensitive!):

entry = advSpark, "Spark Angle", float, "%.1f"
entry = egttemp, "EGT", int, "%d"
entry = fuelpress, "Fuel Press", int, "%d"
entry = KnockDeg, "Knock", int, "%d"
entry = RpmHiRes, "RPM", int, "%d"
entry = barometer, "barometer", int, "%d"
entry = porta, "porta", int, "%d"
entry = portb, "portb", int, "%d"
entry = portc, "portc", int, "%d"
entry = portd, "portd", int, "%d"
entry = batteryVoltage, "batt V", float, "%.1f"

entry = Oilpress, "Oil Press", int, "%d"

; entry = XForce, "X GForce", float, "%.2f" ; X on X7
; entry = YForce, "Y GForce", float, "%.2f" ; Y on X6
; entry = MAFVolts, "MAF Volts", float, "%.2f" ; MAF on X7

; TEST ONLY - DONT USE
; entry = iTime, "iTime", int, "%d"
; entry = iTimeX, "iTimeX", int, "%d"
; entry = iTimefull, "iTimeFull", int, "%d"
#endif

Any new datalogs will now have a new entry named "Oil Press" that can be viewed in MSLVV, we could call it anything we wanted. We used the int, "%d" as we are only interested in whole numbers, if you wanted to log a smaller value and needed to log it down to decimal places then use float, "%.1f" this will log to 1 decimal place, change the 1 to a 2 for two decimals, etc.


If you have a question, comment, or suggestion for this FAQ, e-mail Phil or James or Ken or post it on the MS-Extra forum.

No part of this manual may be reproduced or changed without written permission from Philip Ringwood, James Murray and Ken Culver


2004, 2005 Bruce Bowling and Al Grippo. All rights reserved.