Hi, guys, I need your help.
Does anyone have a logcfg.txt file they could email me that they know works 100% on an Evo 7 to log to SD card that I can test?
My tuner and I have tried multiples files and multiple SD cards but it will still not log, the lights on the 2.0 just slowly cycle. The files work on my tuners Evo 9 so it logs to SD card.
I even returned the new 2.0 I purchased in case was faulty and returned for another new one and still not working.
It will log to Evoscan with the 2.0 connector no issue just wont log to SD card.
Or anyone with any other ideas? diff in Evo 9 & 7 Ecu? My tuner is well known and knows this stuff back to front and he is baffled. Any help would be appreciated.
Thanks in advance.

 

Is the SD card formatted FAT32 ?

 

Thanks mate, Yes is formatted to Fat32

 

;----------------mut2----------------
type=mut2

; you can also set an OBD pin to a voltage, ground, or a high impedance state
; the first number is the OBD pin number, the second number is the pin voltage with the following values:
;
; 8000-18000 : voltage in millivolts for OP2 Rev C and earlier
; 5000-25000 : voltage in millivolts for OP2 Rev D and later
; -1 : set pin to high impedance (default state)
; -2 : pull pin to ground
;
; keep in mind that if you are applying a non-zero voltage to more than one pin, all of those voltages
; must be the same

; the following setpinvoltage sets OBD pin 1 to ground, which is needed to enable logging on older Mitsubishis
; it is commented out as it is not needed for newer models (e.g. EVO 8/9)
;
; setpinvoltage=1,-2


paramname=TPS
paramid=0x17
scalingrpn=x,0.39215686,*

paramname=RPM
paramid=0x21
scalingrpn=x,31.25,*

paramname=Load1B
paramid=0x41
scalingrpn=x,1.2,*

paramname=MAP
paramid=0x38
scalingrpn=x,0.19347,*,14.5,-

;paramname=WGDC
;paramid=0x86
;scalingrpn=x,0.5,*

paramname=TimingAdv
paramid=0x06
scalingrpn=x,20,-

paramname=KnockSum
paramid=0x26

;paramname=AFRMAP
;paramid=0x32

;paramname=AirTemp
;paramid=0x3A
;priority=2

;paramname=CoolantTempC
;paramid=0x10
;scalingrpn=x,40,-
;priority=2

;paramname=FuelTrim_Low
;paramid=0x0C
;scalingrpn=x,0.19607843,*,25,-
;priority=2

paramname=FuelTrim_Middle
paramid=0x0D
scalingrpn=x,0.19607843,*,25,-
priority=2

;paramname=FuelTrim_High
;paramid=0x0E
;scalingrpn=x,0.19607843,*,25,-
;priority=2

;paramname=O2FeedbackTrim
;paramid=0x0F
;scalingrpn=x,0.19607843,*,25,-
;priority=2

;paramname=EGRTemp
;paramid=0x12
;scalingrpn=x,-2.7,*,597.7,+
;priority=2

paramname=AFR
paramid=0x3C
scalingrpn=x,.02,*,2,*,9.6,+


;paramname=Baro
;paramid=0x15
;scalingrpn=x,0.5,*
;priority=2

;paramname=ISCSteps
;paramid=0x16


;paramname=Airflow
;paramid=0x1A
;scalingrpn=x,6.29,*

paramname=AF1
paramid=0x04
scalingrpn=x
isvisible=0

paramname=AF2
paramid=0x05
scalingrpn=x
isvisible=0

paramname=AirFlow2B
scalingrpn=AF1,256,*,AF2,+,6.29,*,64,/

;paramname=ECULoad
;paramid=0x1C
;scalingrpn=x,0.625,*

;paramname=AccelEnrich
;paramid=0x1D
;scalingrpn=x,0.39215686,*

;paramname=O2SensorRear
;paramid=0x1F
;scalingrpn=x,0.0195,*

;paramname=TargetIdle
;paramid=0x24
;scalingrpn=x,7.8,*
;priority=2

;paramname=OCTNumber
;paramid=0x27
;priority=2

paramname=IPW00
paramid=0x29
scalingrpn=x
isvisible=0

paramname=IPW01
paramid=0x2A
scalingrpn=x
isvisible=0

paramname=InjPulseWidth
scalingrpn=IPW00,256,*,IPW01,+,1000,/

;paramname=AirVol
;paramid=0x2C

;paramname=Speed
;paramid=0x2F
;scalingrpn=x,1.242742384,*

;paramname=Knockvoltage
;paramid=0x30

;paramname=MDP
;paramid=0x38
;scalingrpn=x,1.25,*

;paramname=KnockADC
;paramid=0x6A
;priority=2

;paramname=KnockBase
;paramid=0x6B
;priority=2

;paramname=KnockVar
;paramid=0x6C
;priority=2

;paramname=KnockChange
;paramid=0x6D
;priority=2

;paramname=KnockDynamics
;paramid=0x6E
;priority=2

;paramname=KnockFlag
;paramid=0x6F
;priority=2


;----------------zt2----------------
; the "zt2" channel type can listen on any protocol for incoming numeric text
; the default protocolid is 9, which corresponds to the 3/32" jack receive-only serial port
; the default baud rate and setting are 9600,N,8,1. all of these can be changed for other scenarios

; the zt2 channel looks for a specific header sequence (0,1,2) and then begins parsing the incoming
; bytes that follow. paramid in this case specifies which byte in the sequence the parameter starts at.
; we have defined all the known ZT-2 parameters here for both the 14 and 16-byte protocols, so you
; should not need to add anything more. you can comment out parameters you do not need if you choose,
; but do not change the order of the active parameters
;
; uncomment the section below to use this

;type=zt2

;paramname = AFR
;paramid = 4
;databits = 8
;scalingrpn = x,0.1,*

;paramname = EGT
;paramid = 5
;databits = 16
; (no scaling needed for celsius)

;paramname = RPM2
;paramid = 7
;databits = 16
; the value from the ZT2 is basically a timing pulse interval
; Cm = num cyl / 2
; RPM = 60 * 38400 / (Cm * RPMdata)
; so for 4cyl, RPM = 1152000 / RPMdata
;scalingrpn = 1152000,x,/

;paramname = MAP
;paramid = 9
;databits = 16
;issignmagnitude = 1
; MAP units are PSI for positive values, inHg for negative
; note that signed integers for the ZT-2 are unusual in that the
; MSB is considered a sign bit instead of using two's complement
;scalingrpn = x,0.1,*

;paramname = TPS
;paramid = 11
;databits = 8
; (no scaling needed for % throttle)

;paramname = USER1
;paramid = 12
;databits = 8
;scalingrpn = x,0.0196078,* ; convert 0-255 to 0-5V



;==================================

type=calc

paramname=LogEntryDate ; Dummy entry - Designed to produce an EvoScan style format
; that can be loaded into "Log and Power Graph" without (much)
scalingrpn=0 ; reformatting.

paramname=LogEntryTime ; Dummy entry
scalingrpn=0

paramname=LogNotes ; Dummy entry
scalingrpn=0

paramname=Custom ; Dummy entry - EvoScan seems to need this at the end
scalingrpn=0

 

thats a ctr+a of my log config. There's some stuff going on there that won't give good data out of the box for you, but it should log something. Also make sure your windows isn't doing something dumb like naming the file "logcfg.txt.txt".

 

Thanks for the info mate much appreciated - I will send to my tuner so he can look over the file - he did mention about evo 5/6 with the voltage on the pins but wasn’t sure about evo 7
Will let you know if it works
just need this 2.0 to log to sd for racing as having the laptop in the car with the 1.3 to log is a pain in the ****

 

Hi mate,
I found the issue, was something to do with the laptop saving the file, I saved the file to another pc then re tested my tuners file and it now Logs. The pin voltage mod was not required.
I did test another file with the pin voltage mod also and it Logs too, but obviously not required for my Evo 7.
Thanks again for your help much appreciated, sorry to waste your time! and good info for others if this issue arises