Logging with the (Beta) Standalone Tactrix Cable Logger (No More Computer!)
paramname=RPM
paramid=0x21
scalingrpn=x,31.25,*
conditionrpn = RPM,2500,>
action = start
;
conditionrpn = RPM,2000,<
action = stop
need to have the paraname=RPM part befor the start stop function
Got a new one though to log WOT, starts at 96% TPS and stops less than 2500rpm
paramid=0x21
scalingrpn=x,31.25,*
conditionrpn = RPM,2500,>
action = start
;
conditionrpn = RPM,2000,<
action = stop
need to have the paraname=RPM part befor the start stop function
Got a new one though to log WOT, starts at 96% TPS and stops less than 2500rpm
Question: Been using an alteration of this for awhile and it works well. But the stop fuction starts a new log each time so typically I set it to 0 so that it only starts new loggs when the key is turned off. The issue with that is I tend to get stuck scrolling through a lot of warm up idling and staging lane waiting in the logs. Is there any type of pause/resume action that can be used or some sort of loop you can put the script in when rpm drops into idle range and then continues once the rpm starts up again.
Adding anouther trigger for example the mph would still require starting new loggs each time and that won't fix my situation. Any ideas?
I personally like the cruise control on/off function. makes logging much easier and can keep the range of data as narrow or wide as desired. Usually I'll log for the entire trip, once going, but if I have the opportunity to try some "different" driving behaviors, I'll flick the cruise off and back on to start a new log at the point where I know I'd like to observe specifically.
Still no dice logging for boost on my 2013 RA 
I have tried all of the following, but only see values of "-14.5" in the logs.
paramname=Boost
paramid=0x80876A
scalingrpn=x,0.04824345,*,14.5,-
paramname=Boost
paramid=0x80876A
scalingrpn=x,0.19348,*,14.5,-
paramname=Boost (JDM 3BAR)
paramid=0x80871A
scalingrpn=x,0.19348,*,14.5,-
paramname=Boost (OMNI 4BAR)
paramid=0x80871A
scalingrpn=x,0.2369,*,14.5,-
paramname=PSIG
paramid=0x80871a
databits=16
scalingrpn=x,0.0483675,*,14.5,-
Any other suggestions?

I have tried all of the following, but only see values of "-14.5" in the logs.
paramname=Boost
paramid=0x80876A
scalingrpn=x,0.04824345,*,14.5,-
paramname=Boost
paramid=0x80876A
scalingrpn=x,0.19348,*,14.5,-
paramname=Boost (JDM 3BAR)
paramid=0x80871A
scalingrpn=x,0.19348,*,14.5,-
paramname=Boost (OMNI 4BAR)
paramid=0x80871A
scalingrpn=x,0.2369,*,14.5,-
paramname=PSIG
paramid=0x80871a
databits=16
scalingrpn=x,0.0483675,*,14.5,-
Any other suggestions?
I live in the USA, its just that real Evo's don't come with cruise control. Ya know for example, Evo I, II, III, IV, V, VI, VII, VIII, and IX. The steering ratio is too tight so it was deemed an unsafe option to include on Mitsubishi's part.
You Evo X guys are the first to get cruise control. All the previous models were too serial for crazy non race car options like that.
I'm kidding of course, but no really...
You Evo X guys are the first to get cruise control. All the previous models were too serial for crazy non race car options like that.
I'm kidding of course, but no really...
Last edited by Live4Redline; Aug 7, 2013 at 09:22 AM.
I have standalone logging working in my 2008 X AUDM GSR with SST on 53050109 rom which inherits 53050009 using Mode 23 but I would like to add "Gear in Use" to help in checking knocksum occurrences.
Here's the first part of my logcfg.txt file showing the Gear in Use section:
What do I need to change in my logcfg.txt to get the right Gear in Use values? or is this not possible?
Here's the first part of my logcfg.txt file showing the Gear in Use section:
; 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
;debug=noout
; 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 AUDM EVO X ROMs in the 53040010 series.
;----------------mrmacan evox----------------
; log channel settings
type=mrmacan
zerosampletime = 1
fillmissingsamples = 0
paramname=KnockSum
paramid=0x808a43
scalingrpn=x
paramname=Speed
paramid=0x80a352
databits=16
scalingrpn=x,128,/
sampgroup=2
paramname=Gear
paramid=0x80886E
databits=16
scalingrpn=x,22.6,/
paramname=RPM
paramid=0x80873e
databits=16
scalingrpn=x,1000,*,256,/
;*** Barometer ***
paramname=Baro
paramid=0x80A8F9
scalingrpn=x,0.07251887,*
paramname=PSIG
paramid=0x808712
databits=16
scalingrpn=x,4,/,0.19347,*,14.35,-
My csv file produces this:; must be named logcfg.txt and be placed in the root directory of the
; microSD card inserted in the openport in order to work
;debug=noout
; 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 AUDM EVO X ROMs in the 53040010 series.
;----------------mrmacan evox----------------
; log channel settings
type=mrmacan
zerosampletime = 1
fillmissingsamples = 0
paramname=KnockSum
paramid=0x808a43
scalingrpn=x
paramname=Speed
paramid=0x80a352
databits=16
scalingrpn=x,128,/
sampgroup=2
paramname=Gear
paramid=0x80886E
databits=16
scalingrpn=x,22.6,/
paramname=RPM
paramid=0x80873e
databits=16
scalingrpn=x,1000,*,256,/
;*** Barometer ***
paramname=Baro
paramid=0x80A8F9
scalingrpn=x,0.07251887,*
paramname=PSIG
paramid=0x808712
databits=16
scalingrpn=x,4,/,0.19347,*,14.35,-
sample time KnockSum Speed Gear RPM Baro PSIG
53 6.625 0 0 15.2212 828.125 14.5763 -4.24119
54 6.75 0 2.14063 14.3363 839.844 14.5763 -4.14446
55 6.875 0 2.14063 14.1593 851.563 14.5763 -4.43466
56 7 0 2.14063 13.8053 871.094 14.5763 -4.33793
57 7.125 0 2.14063 14.115 886.719 14.5763 -4.5314
58 7.25 0 2.14063 13.4513 898.438 14.5763 -4.96671
59 7.375 0 2.14063 13.4513 914.063 14.5763 -5.06344
I'm getting numbers like 15.2212, 14.3363, 14.1593 etc for gear in use.53 6.625 0 0 15.2212 828.125 14.5763 -4.24119
54 6.75 0 2.14063 14.3363 839.844 14.5763 -4.14446
55 6.875 0 2.14063 14.1593 851.563 14.5763 -4.43466
56 7 0 2.14063 13.8053 871.094 14.5763 -4.33793
57 7.125 0 2.14063 14.115 886.719 14.5763 -4.5314
58 7.25 0 2.14063 13.4513 898.438 14.5763 -4.96671
59 7.375 0 2.14063 13.4513 914.063 14.5763 -5.06344
What do I need to change in my logcfg.txt to get the right Gear in Use values? or is this not possible?
Last edited by gregburrowes; Jan 3, 2014 at 06:37 PM.
Hi, has been a while that I post something here in this forum.
I need your help by logging with the Tactrix cable.
Please have a look a my logging file and tell my if it´s correct or not, because I´m getting
strange values that can´t be true.
I need the right scales factors for RPM, Speed in km/h
An other question, how do I configure the logging file to get number
with only two decimal positions?
Now there are 5 to 7 and excel scaled it up to 147794,00 V instead of 14,7 V
Third question, I after my engine blows away I did a swap form 4B10 to a 4B12.
A friend modified me the 4B10 Rom and a few weeks everything was fine.
Since a while the car jumps into limp mode with DTC P1241 Torque Limiter.
But it´s not a fault of the MAF, because with the OEM 4B12 Rom their isn´t this problem, just CEL from the missing EGR and temp. sensor in the tank.
I found out, that sometimes the MAF worth point out a 0, after that the fault come.
So can some please tell me how I can disable the P1241?
I only need the address for my definitionfile!
Attached my log.cfg and my Rom
I post it here, because in the normal section I found less about ECU issues.
Thank you!
Cheers Mike!!
I need your help by logging with the Tactrix cable.
Please have a look a my logging file and tell my if it´s correct or not, because I´m getting
strange values that can´t be true.
I need the right scales factors for RPM, Speed in km/h
An other question, how do I configure the logging file to get number
with only two decimal positions?
Now there are 5 to 7 and excel scaled it up to 147794,00 V instead of 14,7 V
Third question, I after my engine blows away I did a swap form 4B10 to a 4B12.
A friend modified me the 4B10 Rom and a few weeks everything was fine.
Since a while the car jumps into limp mode with DTC P1241 Torque Limiter.
But it´s not a fault of the MAF, because with the OEM 4B12 Rom their isn´t this problem, just CEL from the missing EGR and temp. sensor in the tank.
I found out, that sometimes the MAF worth point out a 0, after that the fault come.
So can some please tell me how I can disable the P1241?
I only need the address for my definitionfile!
Attached my log.cfg and my Rom
I post it here, because in the normal section I found less about ECU issues.
Thank you!
Cheers Mike!!
I am getting a lot of numbers that can't be right for my 2010 RA. I have heard you can get the formulas from evoscan but when I look at them they don't seam the be in the same format. Any help with someones working 2010 RA log or how I utilize the formulas from evoscan?
They are based on "Reverse Polish Notation". Yes it doesn't make a lot of sense and Golden Evo is the easiest place to get the stand alone logging files.
EXAMPLE:
EvoScan:
Display=2-Byte RPM
Log Reference= 2ByteRPM
RequestID=2380875c
Eval=3.90625*x
StandAlone:
;*** 2-Byte RPM ***
paramname=2ByteRPM
paramid=0x80875C
databits=16
scalingrpn=x,3.90625,*
EXAMPLE:
EvoScan:
Display=2-Byte RPM
Log Reference= 2ByteRPM
RequestID=2380875c
Eval=3.90625*x
StandAlone:
;*** 2-Byte RPM ***
paramname=2ByteRPM
paramid=0x80875C
databits=16
scalingrpn=x,3.90625,*
I am getting a lot of numbers that can't be right for my 2010 RA. I have heard you can get the formulas from evoscan but when I look at them they don't seam the be in the same format. Any help with someones working 2010 RA log or how I utilize the formulas from evoscan?
i have an evo 8 ROM id: 96420008
having issues getting this to work.
using this for my log
;----------------mut2----------------
type=mut2
;---------------------------------------
paramname=Load2Byte1Raw
paramid=0x00
scalingrpn=x,256,*
paramname=Load2Byte2Raw
paramid=0x01
paramname=TPS
paramid=0x17
scalingrpn=x,0.39215686,*
paramname=RPM
paramid=0x21
scalingrpn=x,31.25,*
paramname=2ByteRPM
paramid=0x808746
databits=16
scalingrpn=x,3.90625,*
paramname=TimingAdv
paramid=0x06
scalingrpn=x,20,-
paramname=Airflow
paramid=0x1A
scalingrpn=x,6.29,*
paramname=Speed
paramid=0x2F
scalingrpn=x,1.242742384,*
priority=2
;paramname=Gear ;<-- Works but Disabled
;paramid=0x80886e
;databits=16
;scalingrpn=x,22.6,/
;priority=2
paramname=MAP
paramid=0x38
scalingrpn=x,1.25,*
paramname=KnockSum
paramid=0x26
;paramname=AFRMAP ;Testing *FAILED (Does not work)
;paramid=0x8088f5
;scalingrpn=x,1881.6,/
;paramname=AFRMAPxTEST ;Testing *FAILED (Does not work)
;paramid=0x32
;scalingrpn=x,1881.6,/
;paramname=LoadCalc ;<-- Disabled in exchange for 1Byte Load
;scalingrpn=0
;paramname=ECULoad ;<-- Disabled in exchange for 1Byte Load
;paramid=0x1C
;scalingrpn=x,0.625,*
paramname=Load1Byte ;<-- WORKS
paramid=0x41
scalingrpn=x,1.2,*
;----------------inno----------------
; log from an innovate bus via the 3/32" jack
; currently the LC-1 is the only supported device
; in the "inno" case the parameters are already pre-defined, you just
; need to reference them by name so that they are included in the log
; output. note that these parameters won't become valid until the LC-1
; has been calibrated and the sensor is warmed up.
type=inno
paramname = inno.afr
paramname = inno.lambda
;------BOOST CONTROLER STUFF------
paramname=ActiveWGDC
paramid=0x808b53
scalingrpn=x,0.5,*
paramname=BoostError
paramid=0x808B50
scalingrpn=x,128,-,2,/
paramname=WGDC_Correction
paramid=0x808b51
scalingrpn=x,0.5,*,64,-
paramname=PassiveWGDC
paramid=0x80a53f
scalingrpn=x,0.5,*
paramname=LoadFuel
paramid=0x80876E
databits=16
scalingrpn=x,.3125,*
;paramname=IATS ;<-- Works but Disabled
;paramid=0X808659
;scalingrpn=x,1.8,*,40,-
;---------------------------------
;---------FUEL TRIMS--------------
; ORGNINAL MATH =x,0.19607843,*,25,-
; EVOSCAN MATH =x,0.1953125,*,25,-
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,-
paramname=FuelTrim_InUse
paramid=0x50
scalingrpn=x,0.19607843,*,25,-
priority=2
paramname=O2Feedback_Trim
paramid=0x50
scalingrpn=x,0.19607843,*,25,-
priority=2
;---------------------------------
;-----------TRIGGERS------------
;----Only log when engine is running----
conditionrpn = RPM,0,>
action = start
conditionrpn = RPM,0,==
action = stop
;-----------WIDEBAND------------
;---AEM via OP2 Jack---
type=ascii
paramname=WidebandAF
paramid=1
;----------------------
----------EXTRA----------------
type=calc
paramname=Load2Byte
scalingrpn=Load2Byte1Raw,Load2Byte2Raw,+,0.3125,*
paramname=LogEntryDate
scalingrpn=0
paramname=LogEntryTime
scalingrpn=0
paramname=LogNotes
scalingrpn=0
paramname=Custom
scalingrpn=0
;___________________________________
do i just need scaling? or what am i missing? my out file shows all the columns just all 0's in AFR.
i have a newer version of Ecuflash 1.44.3721 i believe. do i need to downgrade that to the 1.34 version in the OP and then update my taxtrix? OR does the newer versions after that beta all include the same ability? it could just be that? (i hope)
having issues getting this to work.
using this for my log
;----------------mut2----------------
type=mut2
;---------------------------------------
paramname=Load2Byte1Raw
paramid=0x00
scalingrpn=x,256,*
paramname=Load2Byte2Raw
paramid=0x01
paramname=TPS
paramid=0x17
scalingrpn=x,0.39215686,*
paramname=RPM
paramid=0x21
scalingrpn=x,31.25,*
paramname=2ByteRPM
paramid=0x808746
databits=16
scalingrpn=x,3.90625,*
paramname=TimingAdv
paramid=0x06
scalingrpn=x,20,-
paramname=Airflow
paramid=0x1A
scalingrpn=x,6.29,*
paramname=Speed
paramid=0x2F
scalingrpn=x,1.242742384,*
priority=2
;paramname=Gear ;<-- Works but Disabled
;paramid=0x80886e
;databits=16
;scalingrpn=x,22.6,/
;priority=2
paramname=MAP
paramid=0x38
scalingrpn=x,1.25,*
paramname=KnockSum
paramid=0x26
;paramname=AFRMAP ;Testing *FAILED (Does not work)
;paramid=0x8088f5
;scalingrpn=x,1881.6,/
;paramname=AFRMAPxTEST ;Testing *FAILED (Does not work)
;paramid=0x32
;scalingrpn=x,1881.6,/
;paramname=LoadCalc ;<-- Disabled in exchange for 1Byte Load
;scalingrpn=0
;paramname=ECULoad ;<-- Disabled in exchange for 1Byte Load
;paramid=0x1C
;scalingrpn=x,0.625,*
paramname=Load1Byte ;<-- WORKS
paramid=0x41
scalingrpn=x,1.2,*
;----------------inno----------------
; log from an innovate bus via the 3/32" jack
; currently the LC-1 is the only supported device
; in the "inno" case the parameters are already pre-defined, you just
; need to reference them by name so that they are included in the log
; output. note that these parameters won't become valid until the LC-1
; has been calibrated and the sensor is warmed up.
type=inno
paramname = inno.afr
paramname = inno.lambda
;------BOOST CONTROLER STUFF------
paramname=ActiveWGDC
paramid=0x808b53
scalingrpn=x,0.5,*
paramname=BoostError
paramid=0x808B50
scalingrpn=x,128,-,2,/
paramname=WGDC_Correction
paramid=0x808b51
scalingrpn=x,0.5,*,64,-
paramname=PassiveWGDC
paramid=0x80a53f
scalingrpn=x,0.5,*
paramname=LoadFuel
paramid=0x80876E
databits=16
scalingrpn=x,.3125,*
;paramname=IATS ;<-- Works but Disabled
;paramid=0X808659
;scalingrpn=x,1.8,*,40,-
;---------------------------------
;---------FUEL TRIMS--------------
; ORGNINAL MATH =x,0.19607843,*,25,-
; EVOSCAN MATH =x,0.1953125,*,25,-
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,-
paramname=FuelTrim_InUse
paramid=0x50
scalingrpn=x,0.19607843,*,25,-
priority=2
paramname=O2Feedback_Trim
paramid=0x50
scalingrpn=x,0.19607843,*,25,-
priority=2
;---------------------------------
;-----------TRIGGERS------------
;----Only log when engine is running----
conditionrpn = RPM,0,>
action = start
conditionrpn = RPM,0,==
action = stop
;-----------WIDEBAND------------
;---AEM via OP2 Jack---
type=ascii
paramname=WidebandAF
paramid=1
;----------------------
----------EXTRA----------------
type=calc
paramname=Load2Byte
scalingrpn=Load2Byte1Raw,Load2Byte2Raw,+,0.3125,*
paramname=LogEntryDate
scalingrpn=0
paramname=LogEntryTime
scalingrpn=0
paramname=LogNotes
scalingrpn=0
paramname=Custom
scalingrpn=0
;___________________________________
do i just need scaling? or what am i missing? my out file shows all the columns just all 0's in AFR.
i have a newer version of Ecuflash 1.44.3721 i believe. do i need to downgrade that to the 1.34 version in the OP and then update my taxtrix? OR does the newer versions after that beta all include the same ability? it could just be that? (i hope)
Last edited by sandman121383; Jul 3, 2014 at 01:37 PM.




