Logging with the (Beta) Standalone Tactrix Cable Logger (No More Computer!)
Jan 19, 2010, 02:49 PM
#1
Evolved Member
Thread Starter
iTrader: (4)
Join Date: Feb 2008
Location: Edmonton, Alberta
Posts: 610
Likes: 0
Received 0 Likes
on
0 Posts
Logging with the (Beta) Standalone Tactrix Cable Logger (No More Computer!)
How To:
Logging with the (Beta) Standalone Tactrix Cable Logger (No More Computer!)
Parts Needed:
- Tactrix Open Port 2.0 Adapter
- microSD Card
- Computer with Interwebs
- mode23 Enabled ROM loaded onto your car
- (Optional but important- Wideband O2 Sensor. Innovate LC-1 can plug in directly, all others, such as AEM UEGO, require hooking up by a specific method)
Tools Required:
- None, actually. It's that cool.
Recommended Number of People:
- 1 is good, but having someone cooking food simultaneously is ideal.
Difficulty:
- 1 out of 10 if you can get through my wordy How To
Time to Complete:
- Minutes to have it running, but you may spend some time adjusting your parameters slightly.
Thanks for Finding Things:
Tephra
(and of course, Colby for the Open Port Adapter and work on the Standalone Logger)
Step by Step Instructions:
0 - NOTE: This is for the BETA release of the standalone logger. It takes some playing with text rather than a shiny GUI. It's difficult to predict the future, but I imagine that this logging ability will be simplified and made much nicer to setup.
1 - Download the required "beta" ECUFlash version. The most updated beta version will be in the first post of this
http://forums.openecu.org/viewtopic.php?f=57&t=4319,
but the direct link to the version I used when this was written was here
http://mail.tactrix.com/ecuflash/ecu...0_win_beta.exe
2 - Install it, accepting any agreements and driver installations that pop up.
3 - Plug your Open Port cable into a USB port, start up ECUFlash.
4 - Run the Help -> Licensing to force a firmware update of your adapter. Once completed, you can close every open window.
5 - Unplug your cable and insert the microSD card into the slot on the adapter.
6 - Plug the cable back in. With the microSD card installed, it acts as a card reader, so the microSD card will show up in My Computer (or Finder for us OSX users). Ensure the card is formatted as FAT16 or FAT32. Open up the empty drive. If it's not empty, make it so.
From this point on, the principle is simple: the adapter will take parameters indicated by a "logcfg.txt" file located at the root of the microSD and will request those parameters from the ECU. The resulting responses are recorded to the SD card.
Save the attached logcfg.txt file to use as a template and make changes as you see fit. I have commented out EVERY parameter except RPM, so remove the ";"'s in front of the ones you want to log. I'm hoping that people will contribute parameters in the discussion of this "How To" thread, so check there if you're missing anything. While I have some parameters, I can only confirm that they work for my car - USDM 526800xx series. I'm pretty sure all of the ones I use are also good for USDM MRs as well. However, if you're on a different ROM series, it's very simple to figure out what you would put in the logcfg if you have EvoScan working well. Find the parameter you'd like to log, right click the item and look at it's properties. The address, evaluation and ResponseBytes are the important pieces of information.
7 - Parameters
For North American people, the attached logcfg.txt will likely be more than enough. However, if the addresses for USDM Mode 23 don't work with your car, you may need to do some work. In addition, as more address come to light, you may wish to add them.
The address can be copied over to a paramid (if it starts with "23"xxxxxxx, use 0x instead of 23 - For Example, 23808a07 becomes 0x808a07).
The evaluation needs to be formatted into a "scalingrpn". Look at a few examples (check the attached logcfg) to get the hang of it, but the basic idea is to simplify as much as possible first, then put it in. Just ask if you need help!
If ResponseBytes is 1, nothing needs to be done.
For Example:
If ResponseBytes is 2, add "databits=16".
For Example:
8 - Triggers
Now the fun stuff. This section allows you to specify WHEN you want the adapter to start logging. Unfortunately, I only have confirmed USDM ROM triggers, but if you have something that doesn't work, get in touch with me and I'll try to find the address. Obviously, choose one method and put it in your logcfg.
Log All the Time
If nothing is specified (or everything is commented out), the logging will start when the car is turned on, and stop when the car is off. This is great for track days, finding out your LTFTs, or just because you don't want to fiddle with buttons. This is also good because it doesn't require any additional logged parameters, so this is what to use if you want the fastest of fast logging.
Log When Cruise Control is On
Whenever your "Cruise" light is on, the adapter is logging. This is definitely my choice, although it technically does require a logging slot to record the status of the Cruise flag. I have to give Tephra a HUGE thanks for digging through and finding this address, all I did was test a couple things out.
Insert these into your logcfg.txt (they're already in the attached one, just uncomment the needed fields). If you find the response slow, remove the "priority=2" line.
Log When Cruise Control is Held Down
The adapter is only logging as you are holding down the Cruise On/Off switch. It is independent of the "Cruise Light", just keep holding it down. Again, if you find the response slow, remove the "priority=2" line.
Insert these into your logcfg.txt
9 - AFR Logging
Innovate LC-1
Disclaimer - I don't have one, so I haven't tested it yet.
- Make sure that "paramname = inno.afr" is not commented at the bottom of the logcfg
- Plug in your 3/32" cable into the jack of the Open Port adapter and connect the other end to your wideband connector.
- If everything is calibrated properly, you should have AFRs logged!
AFR via Rear O2 ADC
- If you've followed my other guide on how to set this up (https://www.evolutionm.net/forums/ev...ut-serial.html), you can use this:
My Specific AEM UEGO Setup
You WILL HAVE TO CHANGE THE SCALING to match your specific setup. Even between AEM UEGO gauges, the Eval in EvoScan will be different. Mine is "2*(4.44*x/1024)+10", which simplified to the above scaling. Since you will have a different ground voltage, you need to calibrate it yourself as I mentioned in the other How To. Don't assume my calculation will work, it's only there as an example. Had I known that this logger was going to be released, I would have used an LC-1 for my car 
.
10 - Done! Plug in the adapter to your car. Make sure it blinks properly during logging: Red and Green often (Request and Response, looks orange/yellow) with the occasional blue (write to card). If it is doing the multicolour fade thing, something is wrong with your cfg file.
REMEMBER THIS - If you leave the adapter plugged in, it continues to use power even when not logging. Unplug it when you're done to avoid draining the battery.
11 - To get your logged parameters, just plug in the adapter (with the microSD card plugged in) to your computer. I suppose you could use a card reader instead, but I don't have one. Pull the CSV files off and analyze to your heart's content!
Logging with the (Beta) Standalone Tactrix Cable Logger (No More Computer!)
Parts Needed:
- Tactrix Open Port 2.0 Adapter
- microSD Card
- Computer with Interwebs
- mode23 Enabled ROM loaded onto your car
- (Optional but important- Wideband O2 Sensor. Innovate LC-1 can plug in directly, all others, such as AEM UEGO, require hooking up by a specific method)
Tools Required:
- None, actually. It's that cool.
Recommended Number of People:
- 1 is good, but having someone cooking food simultaneously is ideal.
Difficulty:
- 1 out of 10 if you can get through my wordy How To
Time to Complete:
- Minutes to have it running, but you may spend some time adjusting your parameters slightly.
Thanks for Finding Things:
Tephra
(and of course, Colby for the Open Port Adapter and work on the Standalone Logger)
Step by Step Instructions:
0 - NOTE: This is for the BETA release of the standalone logger. It takes some playing with text rather than a shiny GUI. It's difficult to predict the future, but I imagine that this logging ability will be simplified and made much nicer to setup.
1 - Download the required "beta" ECUFlash version. The most updated beta version will be in the first post of this
http://forums.openecu.org/viewtopic.php?f=57&t=4319,
but the direct link to the version I used when this was written was here
http://mail.tactrix.com/ecuflash/ecu...0_win_beta.exe
2 - Install it, accepting any agreements and driver installations that pop up.
3 - Plug your Open Port cable into a USB port, start up ECUFlash.
4 - Run the Help -> Licensing to force a firmware update of your adapter. Once completed, you can close every open window.
5 - Unplug your cable and insert the microSD card into the slot on the adapter.
6 - Plug the cable back in. With the microSD card installed, it acts as a card reader, so the microSD card will show up in My Computer (or Finder for us OSX users). Ensure the card is formatted as FAT16 or FAT32. Open up the empty drive. If it's not empty, make it so.
From this point on, the principle is simple: the adapter will take parameters indicated by a "logcfg.txt" file located at the root of the microSD and will request those parameters from the ECU. The resulting responses are recorded to the SD card.
Save the attached logcfg.txt file to use as a template and make changes as you see fit. I have commented out EVERY parameter except RPM, so remove the ";"'s in front of the ones you want to log. I'm hoping that people will contribute parameters in the discussion of this "How To" thread, so check there if you're missing anything. While I have some parameters, I can only confirm that they work for my car - USDM 526800xx series. I'm pretty sure all of the ones I use are also good for USDM MRs as well. However, if you're on a different ROM series, it's very simple to figure out what you would put in the logcfg if you have EvoScan working well. Find the parameter you'd like to log, right click the item and look at it's properties. The address, evaluation and ResponseBytes are the important pieces of information.
7 - Parameters
For North American people, the attached logcfg.txt will likely be more than enough. However, if the addresses for USDM Mode 23 don't work with your car, you may need to do some work. In addition, as more address come to light, you may wish to add them.
The address can be copied over to a paramid (if it starts with "23"xxxxxxx, use 0x instead of 23 - For Example, 23808a07 becomes 0x808a07).
The evaluation needs to be formatted into a "scalingrpn". Look at a few examples (check the attached logcfg) to get the hang of it, but the basic idea is to simplify as much as possible first, then put it in. Just ask if you need help!
If ResponseBytes is 1, nothing needs to be done.
For Example:
Code:
paramname=Timing paramid=0x808a07 scalingrpn=x,20,-
For Example:
Code:
paramname=RPM paramid=0x808746 databits=16 scalingrpn=x,3.90625,*
Now the fun stuff. This section allows you to specify WHEN you want the adapter to start logging. Unfortunately, I only have confirmed USDM ROM triggers, but if you have something that doesn't work, get in touch with me and I'll try to find the address. Obviously, choose one method and put it in your logcfg.
Log All the Time
If nothing is specified (or everything is commented out), the logging will start when the car is turned on, and stop when the car is off. This is great for track days, finding out your LTFTs, or just because you don't want to fiddle with buttons. This is also good because it doesn't require any additional logged parameters, so this is what to use if you want the fastest of fast logging.
Log When Cruise Control is On
Whenever your "Cruise" light is on, the adapter is logging. This is definitely my choice, although it technically does require a logging slot to record the status of the Cruise flag. I have to give Tephra a HUGE thanks for digging through and finding this address, all I did was test a couple things out.
Insert these into your logcfg.txt (they're already in the attached one, just uncomment the needed fields). If you find the response slow, remove the "priority=2" line.
Code:
paramname=CruiseLight paramid= 0x8045C5 databits=1 offsetbits=5 isvisible=0 priority=2 conditionrpn = CruiseLight,1,== action = start conditionrpn = CruiseLight,0,== action = stop
The adapter is only logging as you are holding down the Cruise On/Off switch. It is independent of the "Cruise Light", just keep holding it down. Again, if you find the response slow, remove the "priority=2" line.
Insert these into your logcfg.txt
Code:
paramname=CruiseMomentary paramid= 0x80AB1E databits=1 offsetbits=1 isvisible=0 priority=2 conditionrpn = CruiseMomentary,1,== action = start conditionrpn = CruiseMomentary,0,== action = stop
Innovate LC-1
Disclaimer - I don't have one, so I haven't tested it yet.
- Make sure that "paramname = inno.afr" is not commented at the bottom of the logcfg
- Plug in your 3/32" cable into the jack of the Open Port adapter and connect the other end to your wideband connector.
- If everything is calibrated properly, you should have AFRs logged!
AFR via Rear O2 ADC
- If you've followed my other guide on how to set this up (https://www.evolutionm.net/forums/ev...ut-serial.html), you can use this:
My Specific AEM UEGO Setup
Code:
paramname=RearO2AFR paramid=0x80934e databits=16 scalingrpn=x,0.008671875,*,10,+
.10 - Done! Plug in the adapter to your car. Make sure it blinks properly during logging: Red and Green often (Request and Response, looks orange/yellow) with the occasional blue (write to card). If it is doing the multicolour fade thing, something is wrong with your cfg file.
REMEMBER THIS - If you leave the adapter plugged in, it continues to use power even when not logging. Unplug it when you're done to avoid draining the battery.
11 - To get your logged parameters, just plug in the adapter (with the microSD card plugged in) to your computer. I suppose you could use a card reader instead, but I don't have one
. Pull the CSV files off and analyze to your heart's content!
Last edited by xPRimNT; Jan 19, 2010 at 02:54 PM.
Jan 19, 2010, 02:50 PM
#2
Evolved Member
Thread Starter
iTrader: (4)
Join Date: Feb 2008
Location: Edmonton, Alberta
Posts: 610
Likes: 0
Received 0 Likes
on
0 Posts
I thought I'd post up the contents of my sample logcfg.txt too, in case it ever stops being "attached" to the first post.
Code:
; 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 ;----------------inno---------------- type=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. ;paramname = inno.afr ;paramname = inno.lambda
Trending Topics
Feb 4, 2010, 01:17 PM
#12
Evolving Member
iTrader: (3)
Join Date: Jul 2009
Location: Gillette Wyoming
Posts: 191
Likes: 0
Received 0 Likes
on
0 Posts
Well if you want IDC here you go.
NOTE if you want IDC you have make sure that the IPW is uncommented ; or you can't log anything.
paramname=IDC
paramid=0X808746
databits=16
scalingrpn=IPW,RPM,*,1200,/
And for sh*ts and grins.
Manifold Air Temp
paramname=MATS
paramid=0X80865F
scalingrpn=x,1.8,*,40,-
Intake Air Temp
paramname=IATS
paramid=0X808659
scalingrpn=x,1.8,*,40,-
Coolant Temp
paramname=CTS
paramid=0X80863F
scalingrpn=x,1.8,*,40,-
Battery
paramname=Battery
paramid=0x8086EF
scalingrpn=x,18.75,*,255,/
Boost Error
paramname=BoostError
paramid=0x808B50
scalingrpn=x,128,-,2,/
Have not tested this one but should work. (For MR guys I think.)
Gear in use
paramname=Gear
paramid=0x80886E
databits=16
scalingrpn=x,22.6,/
NOTE if you want IDC you have make sure that the IPW is uncommented ; or you can't log anything.
paramname=IDC
paramid=0X808746
databits=16
scalingrpn=IPW,RPM,*,1200,/
And for sh*ts and grins.
Manifold Air Temp
paramname=MATS
paramid=0X80865F
scalingrpn=x,1.8,*,40,-
Intake Air Temp
paramname=IATS
paramid=0X808659
scalingrpn=x,1.8,*,40,-
Coolant Temp
paramname=CTS
paramid=0X80863F
scalingrpn=x,1.8,*,40,-
Battery
paramname=Battery
paramid=0x8086EF
scalingrpn=x,18.75,*,255,/
Boost Error
paramname=BoostError
paramid=0x808B50
scalingrpn=x,128,-,2,/
Have not tested this one but should work. (For MR guys I think.)
Gear in use
paramname=Gear
paramid=0x80886E
databits=16
scalingrpn=x,22.6,/
Last edited by Whitewind; Feb 4, 2010 at 02:41 PM.
Feb 15, 2010, 07:43 AM
#13
Evolving Member
iTrader: (3)
Join Date: Jul 2009
Location: Gillette Wyoming
Posts: 191
Likes: 0
Received 0 Likes
on
0 Posts
Okay little more
Mivec Intake Target
paramname=Intake MIVEC Target
paramid=0x80942E
databits=16
scalingrpn=x,4096,-,0.01953125,*
Mivec Intake Actual
paramname=Intake MIVEC Actual
paramid=0x809466
databits=16
scalingrpn=x,4096,-,0.01953125,*
Mivec Exhaust Target
paramname=Exhaust MIVEC Target
paramid=0x80943A
databits=16
scalingrpn=x,4096,-,0.01953125,*
Mivec Exhaust Actual
paramname=Exhaust MIVEC Actual
paramid=0x809472
databits=16
scalingrpn=x,4096,-,0.01953125,*
Mivec Intake Target
paramname=Intake MIVEC Target
paramid=0x80942E
databits=16
scalingrpn=x,4096,-,0.01953125,*
Mivec Intake Actual
paramname=Intake MIVEC Actual
paramid=0x809466
databits=16
scalingrpn=x,4096,-,0.01953125,*
Mivec Exhaust Target
paramname=Exhaust MIVEC Target
paramid=0x80943A
databits=16
scalingrpn=x,4096,-,0.01953125,*
Mivec Exhaust Actual
paramname=Exhaust MIVEC Actual
paramid=0x809472
databits=16
scalingrpn=x,4096,-,0.01953125,*
Last edited by Whitewind; Feb 15, 2010 at 02:43 PM.