Data Log Trigger

[scnicholl]

Have MSII V3.0
Can I set a trigger to start logging?

[Matt Cramer]

Sorry, MegaTune does not support this. (Edit - see below, I didn't know about that feature.)

[Bernard Fife]

scnicholl,

MegaTune can use a trigger to start logging, but the trigger has to be one determined of the outpc values (like rpm, MAP, etc.). The settings for the datalog triggering are in the custom.ini file:

Code: Select all

#unset AUTOMARK_LOGGING_FEATURES
#if    AUTOMARK_LOGGING_FEATURES
   [OutputChannels]
      ; Make up some variable names...
      highLoad = { rpm >= 3500 && throttle >= 50 }
      enable   = { rpm >= 2000 }

   [Datalog]
      enableWrite = enable    ; Log entries are only written when the variable
                              ; "enable" is true, see it's definition above.

      markOnTrue  = highLoad  ; A datalog marker is written when "highLoad"
                              ; transitions from false to true.  The marker
                              ; looks like "MARK 001 highLoad" to distinguish
                              ; it from the manual markers.

#endif 

You need to change:

Code: Select all

#unset AUTOMARK_LOGGING_FEATURES

to

Code: Select all

#  set AUTOMARK_LOGGING_FEATURES

In the case above, the datalog will be triggered if rpm >= 2000. If the rpm is below this, the datalog will not be written to. You could easily add (or change this to) some things like

{ throttle >= 80 || rpm >= 4500 }, (high loads or high rpms only) or
{ coolant > 180 }, (only when warmed up) or
{ seconds >= 20 }, (don't use the first few seconds) or
{ engine > 3 }, (only if there are codes that aren't normal running or cranking) etc.

However, MegaTune doesn't support a separate hardware trigger for a datalog (unless this is reflected in one of the outpc values, such as a spare port). The values you can use are listed in the [OutputChannels] section of the controller ini file.

Lance.

[scnicholl]

Thanks Lance
I will give that a try