Page 1 of 1

Dictionary for MegaLogViewer Calculated Fields

Posted: Tue May 22, 2007 8:34 am
by LT401Vette
This is a list of all the optional calculated fields in MLV and their meaning. I will keep adding to it and include it on the MLV site.

Wideband O2 AFR - Air Fuel Ratio calculated based on O2 field for specified WB sensor. This is for MS1 only, MS2 typically logs AFR directly to an afr field.

Wideband O2 Lambda - Lambda calculated based on O2 field for specified WB sensor. This is for MS1 only, MS2 typically logs Lambda directly.

Boost(psi) - Converts MAP to psi with 0 = to atmospheric pressure.
- Input: "Engine off MAP pressure in KPA" - The MAP value while the engine is not running, corrects for sea level and error.

VAC(inHg) - Converts MAP to vacuum in inHg
- Input: "Engine off MAP pressure in KPA" - The MAP value while the engine is not running, corrects for sea level and error.

Boost-Vac - Below atmospheric pressure Vacuum in inHg, above Boost in PSI
- Input: "Engine off MAP pressure in KPA" - The MAP value while the engine is not running, corrects for sea level and error.

TP ADC - Calculates the original ADC value based on TP in percentage.
- Inputs:
- "Maximum TPS ADC" - the ADC value with your throttle at wide open.
- "Minimum TPS ADC" - the ADC value with your throttle in idle position

MPH\ Xxx\ Gear
- Inputs:
- "Tire Diameter(in.)" - Drive tire outside diameter in inches
- "Final Drive Ratio" - Axle drive ratio
- "Transmission gear ratio" - ratio for the transmission gear used

KPH\ Xxx\ Gear
- Inputs:
- "Tire Diameter(cm.)" - Drive tire outside diameter in centimeters
- "Final Drive Ratio" - Axle drive ratio
- "Transmission gear ratio" - ratio for the transmission gear used

HP - Horsepower calculated from rate of speed change. Car must be in the defined gear on level ground for accurate results. Currently uses US measurement units only.
- Inputs:
- "Min TP to calculate for" - Filter condition, HP will only be calculated when TP is over this value. This heavy calculation will slow log load times if hp is calculated for the entire file.
- "Tire Diameter(in.)" - Drive tire outside diameter in inches
- "Final Drive Ratio" - Axle drive ratio
- "Transmission gear ratio" - ratio for the transmission gear used
- "Converter stall speed (0 for manual trans)" - Converter flash stall, the RPM that you flash to from a stop with traction.

New or changed for 2.68:

Fuel Flow - Total Fuel flow for combined injectors in lb/hr or cc/min depending on what rating is used for the injector input.
- Inputs:
- "Injector Opening Time" - the injector open time configured in you MS, usually 1.0
- "Alternating(enter 0.5) or Simultaneous (enter 1)" - whether your injectors are configured to fire Simultaneously or alternating.
- "Number of Squirts" - Number of squirts per cycle configured in your MS
- "Injector Size" - the rated or corrected rating for your injector
- "Number of Cylinders/Injectors" - Number of injectors.

Instant MPG - point in time fuel economy in Miles per gallon. Like the instant MPG gauge in many modern cars.
- Inputs:
- "Injector Opening Time" - the injector open time configured in you MS, usually 1.0
- "Alternating(enter 0.5) or Simultaneous (enter 1)" - whether your injectors are configured to fire Simultaneously or alternating.
- "Number of Squirts" - Number of squirts per cycle configured in your MS
- "Injector Size" - the rated or corrected rating for your injector
- "Number of Cylinders/Injectors" - Number of injectors.
- "Tire Diameter(in.)" - Drive tire outside diameter in inches
- "Final Drive Ratio" - Axle drive ratio
- "Transmission gear ratio" - ratio for the transmission gear used, for Instant MPG usually your high gear. 1.0 in non overdrive transmission, less if overdrive equipped.

Posted: Tue Jul 10, 2007 1:32 pm
by LT401Vette
Some of the standard core MegaSquirt field definitions:
---------Eric Fahlgren's description of headers in the datalog file---------
Time - Real time clock in 0.001 resolution.
SecL - Low byte of MS internal clock, rolls at 255 back to zero.
RPM - Revolutions Per Minute, RPM/100 on some MS1 embedded codes.
MAP - Manifold Absolute Pressure in kPa.
TP - Throttle Position in percent.
O2 - EGO sensor voltage.
MAT - Manifold Air Temperature in user-selected scale (either F or C).
CLT - CooLant Temperature, also in user selected scale.
Engine - Engine bits.
Gego - Gamma EGO in percent.
Gair - Gamma Air temperature in percent.
Gwarm - Warmup Enrichment Gamma in percent.
Gbaro - Barometric Correction Gamma in percent.
Gammae - Enrichment Gamma, product of all of the above gammas, in percent.
TPSacc - TP acceleration enrichment pulse in ms.
Gve - Gamma VE (table lookup value), for bank 1, in percent.
PW - Final pulsewidth, for bank 1, in ms.
Gve2 - Gamma VE (table lookup value), for bank 2, in percent.
PW2 - Final pulsewidth, for bank 2, in ms.

Re: Dictionary for MegaLogViewer Calculated Fields

Posted: Wed Oct 29, 2008 3:45 pm
by Ralco_Be
LT401Vette wrote: .........
HP - Horsepower calculated from rate of speed change. Car must be in the defined gear on level ground for accurate results. Currently uses US measurement units only.
- Inputs:
- "Min TP to calculate for" - Filter condition, HP will only be calculated when TP is over this value. This heavy calculation will slow log load times if hp is calculated for the entire file.
- "Tire Diameter(in.)" - Drive tire outside diameter in centimeters
Isn't this an error? When I put the values in centimeters, my ca has 260 Hp ?
With the tire Diameter in inches, the calculation is better...

Re: Dictionary for MegaLogViewer Calculated Fields

Posted: Wed Oct 29, 2008 5:33 pm
by LT401Vette
oops, yes it should say inches. i.e the (in.)
cm would really mess up the output.

Re:

Posted: Sat Aug 21, 2010 11:40 am
by Mario
LT401Vette wrote:Some of the standard core MegaSquirt field definitions:
---------Eric Fahlgren's description of headers in the datalog file---------
Time - Real time clock in 0.001 resolution.
SecL - Low byte of MS internal clock, rolls at 255 back to zero.
RPM - Revolutions Per Minute, RPM/100 on some MS1 embedded codes.
MAP - Manifold Absolute Pressure in kPa.
TP - Throttle Position in percent.
O2 - EGO sensor voltage.
MAT - Manifold Air Temperature in user-selected scale (either F or C).
CLT - CooLant Temperature, also in user selected scale.
Engine - Engine bits.
Gego - Gamma EGO in percent.
Gair - Gamma Air temperature in percent.
Gwarm - Warmup Enrichment Gamma in percent.
Gbaro - Barometric Correction Gamma in percent.
Gammae - Enrichment Gamma, product of all of the above gammas, in percent.
TPSacc - TP acceleration enrichment pulse in ms.
Gve - Gamma VE (table lookup value), for bank 1, in percent.
PW - Final pulsewidth, for bank 1, in ms.
Gve2 - Gamma VE (table lookup value), for bank 2, in percent.
PW2 - Final pulsewidth, for bank 2, in ms.
Is there and updated list of definitions availale?

Re: Dictionary for MegaLogViewer Calculated Fields

Posted: Sun Jul 17, 2011 9:30 pm
by Trump
Could some one advist what the Status 1,2,3,4, and 5 are and where I can find this info?

Re: Dictionary for MegaLogViewer Calculated Fields

Posted: Mon Jul 18, 2011 6:13 am
by LT401Vette
Those fields are specific to the firmware, however are relatively consistent across the extra and ms3 firmware, but what ones are available will depend on your firmware.

Any way, they are bit flag fields where different bits will be turned on to indicate the on/off state of various items. They are often used to drive the indicators on the dashborad. That is the best place I know of to find out what bits mean what is to look at the indicators in the ini file.

i.e. snippet from an ms3 ini:

Code: Select all

   indicator = { status1 & 0b00000001}, "Need Burn",   "Need Burn",   white, black, red,   black
   indicator = { status1 & 0b00000010}, "Data Lost",   "Lost Data",   white, black, red,   black
   indicator = { status1 & 0b00000100}, "Config Error",   "Config Error",   white, black, red,   black
   indicator = { status1 & 0b00001000}, "Not synced", "Synced", red, black, green, black
   indicator = { status1 & 0b00100000}, "VE1/2", "VE3/4", white, black, green, black
   indicator = { status1 & 0b01000000}, "SPK1/2", "SPK3/4", white, black, green, black

Now by looking at that you can see that in status1, if the 1st bit is set, "Needs Burn" is being reported. If the 3rd bit is set, there is a "Config Error"

So while in MLV just looking at a status field is not very useful. If you have a specific condition you are looking for, you can create a new field based on these.
For Example if you want to see in MLV if you were running on the switched tables "VE3/4", you can create a new custom field:

Field Name:TableSwitched
Formula: ([status1] | 32) == 32 ? 1 : 0

You will now have a new field after a reload called TableSwitched where it will have a value of 1 when you are on the switched tables and a value of 0 if not.

Re: Dictionary for MegaLogViewer Calculated Fields

Posted: Thu Feb 26, 2015 11:46 pm
by maximus
Hi, didnt find how to append a new dictionary ? I created one for my needs and put in FieldMaps directory, but seems MLV need some setting to see it.

Re: Dictionary for MegaLogViewer Calculated Fields

Posted: Fri Feb 27, 2015 7:29 am
by LT401Vette
I'm not sure what the FieldMaps directory has to do with the Field Dictionary. It didn't even exist in 2007 when this thread was alive.

What the Field Maps are for is for MLV to map know file namings to a canonical naming. This way the formulas can be written to the canonical naming, then MLV can use the field map when evaluating the expression, thus the same formula will work with a current MS3 or an old MS1 even though they have different names for field representing the same thing.

Re: Dictionary for MegaLogViewer Calculated Fields

Posted: Sat Feb 28, 2015 12:29 am
by maximus
Thxs for reply.
As a newbie here, I wanted to post on similar thread rather than create a new topic..
My purpose is to create a dictionary to "speak" the same language as MLV with logs coming from ecuEdit(used to log subaru/evo with it).
So I can use same filters, formulas and short naming conventions inside MLV.
eg : Air\ Flow\ Sensor\ Voltage\ (V) is not very friendly to use with MLV ;)

Re: Dictionary for MegaLogViewer Calculated Fields

Posted: Wed May 31, 2017 5:04 pm
by TrendSetter
is there any kind of documentation that specifies what all the expected fields are named for these calculated fields?
I am using mlvhd to view csv logs from an openlog2.0 on a evo and i can define the field names as needed. I want to start using the hp and acceleration calculations built in to the software but none seem to work right now with my current field names.
When i try to activate the fields they seem to fail silently so there is no feedback for me to troubleshoot.

Re: Dictionary for MegaLogViewer Calculated Fields

Posted: Wed May 31, 2017 5:34 pm
by whittlebeast
This is a Megasquirt specific site but if you PM me your email address, I may be able to help. I bet you could even guess my gmail address.

Andy

Re: Dictionary for MegaLogViewer Calculated Fields

Posted: Tue Apr 03, 2018 10:55 pm
by Flaming_Crossbow
Hi guy's, What are these fields for and why do i have readings for them while not having EGT sensor etc connected.
EGT 6 temp
EGT 7 temp
ADC6
ADC7
status1
PORTs BDE
PORTs AM
PORT T

Re: Dictionary for MegaLogViewer Calculated Fields

Posted: Wed Apr 04, 2018 12:17 pm
by jsmcortina
Those are covered in the datalogging section of the Megasquirt2 TunerStudio Reference Manual. You can download it from the Manuals link above.

James

Re: Dictionary for MegaLogViewer Calculated Fields

Posted: Mon May 27, 2019 9:45 pm
by dll67
Is there a manual for megalogviewer hd .. specifically field definitions. Iam looking for what "MsPerCycle" and am getting frustrated with broken links and incomplete information.
I'll try decrypting it from the data

Re: Dictionary for MegaLogViewer Calculated Fields

Posted: Mon May 27, 2019 11:46 pm
by dll67
dll67 wrote:Is there a manual for megalogviewer hd .. specifically field definitions. Iam looking for what "MsPerCycle" and am getting frustrated with broken links and incomplete information.
I'll try decrypting it from the data
Its looking like "MsPerCycle" is milliseconds per engine revolution