LC1 to Tactrix

[imdrax]

I like the standalone logging option, I will try and set it up today. On my mac osx ecuflash is only available up to 1.38, where as on windows it has 1.42, are there noticeable upgrades in 1.42 to make it worth it to run on windows?

[KickAss]

for the standalone logging to work, you will need the beta 1.43 version. You can download it from tactrix' website as well. The 1.43 updates the firmware on the cable to be able to do standalone logging.

[imdrax]

Thanks kickass, do you know if i need to use standard "stereo" adapters or do i need to convert using "stereo to mono" adapters?

[KickAss]

stereo is needed. You need the smaller pin audio cable, the 2.5mm version, male - to - male.

[imdrax]

ok, i bought the stereo to mono, ill return them and pick up the stereo to stereo. Im pasting my initial log txt file below, can you tell me if it looks like im missing anything? or should i be good to go? im still running my ap stage 2 flash until i can get a base tune ready for the ecuflash.

; uncomment the line below to minimize the information written to logcfg.out
; this will greatly decrease the startup time to begin logging if you already
; have a working logcfg.txt without any problems
;
; debug=noout

; 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 KWP2000 ReadMemoryAddress command over the ISO15765, which works
; for CAN based mitsubishis that have had their ROMs modified to allow the use of this command.
; this command is also known as "mode23" on some forums. since this command reads directly from
; ECU memory, the paramid addresses used are different for different ROM versions. the following
; example is for the USDM EVO X ROMs in the 526800xx series.

;----------------mrmacan evox----------------
; log channel settings
type=mrmacan

;-------------parameters-------------

paramname=RPM
paramid=0x808746
databits=16
scalingrpn=x,3.90625,*

paramname=PSIG
paramid=0x80871a
databits=16
scalingrpn=x,0.0483675,*,14.5,-

paramname=Timing
paramid=0x808a07
scalingrpn=x,20,-

paramname=Knock
paramid=0x808a4b

paramname=LoadFuel
paramid=0x80876e
databits=16
scalingrpn=x,0.3125,*

paramname=IPW
paramid=0x80a944
databits=16
scalingrpn=x,0.001,*

paramname=TPS
paramid=0x8086f9
scalingrpn=x,32,-,0.505882,*
priority=2

paramname=MAF_Airflow_gs
paramid=0x8087e0
databits=16
scalingrpn=x,0.02,*
priority=2

;paramname=Speed_mph
;paramid=0x8087e7
;scalingrpn=x,1.26,*
;priority=2

paramname=ActiveWGDC
paramid=0x808b53
scalingrpn=x,0.5,*

;paramname=WGDC_Correction
;paramid=0x808b51
;scalingrpn=x,0.5,*,64,-

;paramname=PassiveWGDC
;paramid=0x80a53f
;scalingrpn=x,0.5,*

paramname=LTFT_Idle
paramid=0x804573
scalingrpn=x,0.1953125,*,25,-
priority=2

paramname=LTFT_Cruise
paramid=0x804575
scalingrpn=x,0.1953125,*,25,-
priority=2

;paramname=RearO2AFR
;paramid=0x80934e
;databits=16
;scalingrpn=x,0.008671875,*,10,+

;-------------triggers---------------
;
; note that parameters must be previously defined
; before defining triggers using them
;
; triggers allow you to control when logging starts and stops
; this example sets up triggers such that logging only occurs
; when the engine is running (RPM > 0)
;
; triggers consist of some evaluation of the form [trigparam] [condition] [value]
; and a resulting action which is done if the evaluation is true

;paramname=CruiseLight
;paramid= 0x8045C5
;databits=1
;offsetbits=5
;isvisible=0
;priority=2

;conditionrpn = CruiseLight,1,==
;action = start

;conditionrpn = CruiseLight,0,==
;action = stop

paramname=CruiseMomentary
paramid= 0x80AB1E
databits=1
offsetbits=1
isvisible=0
priority=2

conditionrpn = CruiseMomentary,1,==
action = start

conditionrpn = CruiseMomentary,0,==
action = stop


;----------------inno----------------
type=inno
; log from an innovate MTS bus via the 3/32" jack
; multiple LC-1 and other MTS devices (e.g. TC-4) are supported
;
; each MTS parameter has a special parameter ID:
;
; paramid parameter
; 0x0101 LC-1 #1 lambda
; 0x0102 LC-1 #1 AFR
; 0x0201 LC-1 #2 lambda
; 0x0202 LC-1 #2 AFR
; 0x0301 LC-1 #3 lambda
; 0x0302 LC-1 #4 AFR
; (etc)
;
; 0x0001 aux #1 data (e.g. TC-4 #1 channel 1)
; 0x0002 aux #2 data (e.g. TC-4 #1 channel 2)
; 0x0003 aux #3 data (e.g. TC-4 #1 channel 3)
; 0x0004 aux #4 data (e.g. TC-4 #1 channel 4)
; 0x0005 aux #5 data (e.g. TC-4 #2 channel 1)
; (etc)

; the LC-1 parameters are already scaled correctly and require no scalingrpn setting
; however, the LC-1 is known to lose its stored AFR multiplier, so we recommend calculating
; AFR from lambda like this

paramname = mylc1.afr
paramid = 0x0101 ; get lambda from first LC-1
scalingrpn = x,14.7,* ; scale to an AFR

; since the MTS bus does not describe the contents of the aux channels, you need to know what they are
; and how to scale them. in this example we assume you have a TC-4 connected and you want to view the
; thermocouple readings in celsius, two of which are in the EGT mode, two in CHT mode

;paramname = mytc4.egt1
;paramid = 0x0001
;scalingrpn = x,1.06842619,*

;paramname = mytc4.egt2
;paramid = 0x0002
;scalingrpn = x,1.06842619,*

;paramname = mytc4.cht1
;paramid = 0x0003
;scalingrpn = x,0.293255131,*

;paramname = mytc4.cht2
;paramid = 0x0004
;scalingrpn = x,0.293255131,*

[KickAss]

I have no idea how to get the files working, Golden can answer that better. But yeah, you will need an ECUFlash based ROM for this whole thing to work.

[desiromeo812]

I use standalone logging, While it works wonders I cannot view logs in EVOSCAN. Logs work perfect in Virtual dyno. In evoscan they open and give me some errors and only part that works is the "grid" area and even that will not display LC1 values.

Can someone please send me their cfgLOG.txt file that puts out values/settings that work in their evoscan.

Not trying to treadjack but since we are speaking on the same issue I figured I ask.

And Kickass, you do not need 2 USb inputs or serial to USB, all you need is to tap into rearo2 wire for ECU logging and you can set up LC1 to log thru evoscan/Ecu.

[KickAss]

Yeah, I was talking about running an LC1 separately without tapping into the rear O2. That is what the OP is trying to do. He doesn't have it tapped into the rear O2.

[imdrax]

correct, i have my rear o2 installed and remaining functional. I want to switch over the using the ECUflash/tactrix and ditch the Cobb AP but i just dont really know how to proceed, i dont want to un marry the cobb until i have a solid map ready to flash in from ecuflash.

[desiromeo812]

Originally Posted by KickAss

Yeah, I was talking about running an LC1 separately without tapping into the rear O2. That is what the OP is trying to do. He doesn't have it tapped into the rear O2.

Oh ok.. I didnt read that part.. Are you able to assist with my Issue? do your Standalone logs work in Evoscan?