Charlescrown

OK well it looks like I need to spend some time teaching myself to use graphs in XL. That's one area I have never been. I have setup my OP2 to log so when I get the car back together I will have a play around with it. The problem I have is its a track car only and they wouldn't like to see a laptop in the car but I suppose I could strap it under the seat. I have Evoscan and its a great program but how to correlate the formulas is at this stage daunting for me. I really need to log knock as well as wideband fuel figures so I don't blow it up again. 2 meets ago it was a stinking hot summer day and I think it was detonating and I couldnt hear it. I am also going to put the Tephra program in which uses your CEL to flash when it pings.

jrainwater

iTrader: (10)

Log more then just those two parameters actually. Afr vs Afr map, knock vs knock voltage, timing, air flow, rpm, tps, there's more. I'll update when I'm not driving lol.

codgi

iTrader: (22)

Its not that hard once you know what it is you want to log. I would say figure that out in evoscan and once you know what you want to log and ensure the formulas in the xml are correct its just a matter of porting them over just post up once you know what you want in the ECUFlash forum and you'll get help there.

Charlescrown

OK well as I said I need to spend some time with this one. My knowledge of Excel is very limited.
I went to do the hardware upgrade and it wanted me to put in a license number? Dont know where to get it so I have sent Tactrix an email so when I get that sorted out I will proceed further.
I'm in the process of putting the engine back together and taking my time to make sure it's right. Might do some work on the head first so it's still a few weeks away before I can try logging.

codgi

iTrader: (22)

Yeah you'll need to contact tactrix for that (license). It's been a while since I've had to do it so I don't remember much about that.

Charlescrown

Tactrix said you don't need to put in a licence number as it's still in development and only for business use. They said ECUFLASH will always be available free to single users. Now I got that sorted I would really appreciate an example of a logging program for Excel to help get me started. I have no idea where and what to put into Excel to get it to display a log.

intj123

iTrader: (1)

I use evoscan on my laptop for logging and to actually reflash the ecu with the edited rom using ecuflash.

Charlescrown

I have done the same with Evoscan but they won't like a laptop in the car when on the track so I want to log to the sd card in the OP2 then look at it on a laptop. That's where I have the problem. What commands do I need to put onto the SD card to allow it to capture the data?

Biggiesacks

https://www.evolutionm.net/forums/ev...-computer.html

Pretty sure this all still works. Its how i set mine up.

superbovine

iTrader: (23)

^^^ cool, thanks for that. I think I went through that once before, but I know I did not notice the bit about firmware updating it first. Perhaps that is my issue.

codgi

iTrader: (22)

This is a good start.

OP: Like I said earlier you can also search the ECUFlash forum for "logcfg" and that should give some examples.

Once setup correctly then all you do when the car comes in is pop the SD card out of the cable put it in the computer and open in any program which can open csv files (Excel, Office Online, Google Docs etc.) and you'll have your data.

Charlescrown

Great it's starting to make sense. I thought I had to do a lot more than just setup the logcfg.txt file and plug it in. Looking forward to having a play with it once my engine is back together. I am using Version 1.44.3721. Are there any issues logging with that version as the older Beta version is not available.

Biggiesacks

Yah the logcfg stays the same between the different versions. You should be fine.

Charlescrown

Great thanks for all the help. I now understand what needs to be done. I also downloaded all the MUTT3 data request commands so I should now be able to start setting up what I want to log. I started working on my engine by doing lots of pre assembly clearance checks and grinding the ring gaps so hopefully it should be back together in a few weeks.

Charlescrown

Well the car is now running and still no luck data logging to the Tactrix.
This is a copy of my logcfg.
Any help would be much appreciated.

; sample logging configuration file for openport 2.0
; must be named logcfg.txt and be placed in the root directory of the
; microSD card inserted in the openport in order to work

; this sample logs using the MUT-II protocol over the K-line, which works
; for many mitsubishis, including the EVO 8 and 9

;----------------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=TimingAdv
paramid=0x06
scalingrpn=x,20,-

paramname=CoolantTemp
paramid=0x07
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=0x0E
scalingrpn=x,0.19607843,*,25,-
priority=2

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

paramname=O2Sensor
paramid=0x13
scalingrpn=x,0.0195,*

paramname=Battery
paramid=0x14
scalingrpn=x,0.0733,*
priority=2

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

paramname=ISCSteps
paramid=0x16

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

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

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=RPM
paramid=0x21
scalingrpn=x,31.25,*

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

paramname=KnockSum
paramid=0x26
priority=2

paramname=OCTNumber
paramid=0x27
priority=2

paramname=InjPulseWidth
paramid=0x29
scalingrpn=x,0.256,*

paramname=AirVol
paramid=0x2C

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

paramname=Knock
paramid=0x30

paramname=AFRMAP
paramid=0x32

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

paramname=AirTemp
paramid=0x3A
priority=2

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

paramname=WGDC
paramid=0x86
scalingrpn=x,0.39215686,*

conditionrpn=Engine_Speed(rpm),100>
action=start

conditionrpn=Engine_Speed(rpm),0,==
action=stop