Logging with no Laptop - RA logcfg files here
thanks for the links and info Razor. I ~think~ I've got a logcfg.txt put together for my 2010 USDM RA, but i'm stuck trying to figure out the addresses i need to use for the triggers (want to use cruise on/off method for logging), and my GoogleFu isn't turning up anything really useful on how to find addresses or convert my hex to ECUFlash definition file to help figure out what's what.
Thread Starter
Joined: Aug 2003
Posts: 14,094
Likes: 1,093
From: Mid-Hudson, NY
thanks for the links and info Razor. I ~think~ I've got a logcfg.txt put together for my 2010 USDM RA, but i'm stuck trying to figure out the addresses i need to use for the triggers (want to use cruise on/off method for logging), and my GoogleFu isn't turning up anything really useful on how to find addresses or convert my hex to ECUFlash definition file to help figure out what's what.
Trending Topics
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
Hi Bryan.
Hopefully, the following information is in line with your thread's basic intent. If it's too tangential, let me know, and I'll shorten it to a one-line link to a thread somewhere else!
-------------------------
As well as "type=inno" and "type=ascii" modes, the Tactrix standalone logger is capable of supporting a built-in ADC circuit ("type=adc"). This is an analogue 0-5V reading from Pin 8 (unused, apparently).
A raw millivolt log is done like this:
The ADC reading I get skips around a bit - it jitters by plus or minus 0.05V. But it's good enough.
I use this ADC method to log my Innovate LC-1, because the Taxtrix unit's implementation of LC-1 digital link is currently broken. My wideband's 0V-5V analogue output is mapped to 10.0:1 - 15.0:1 range, so the standalone ADC logging is configured as follows:
Rich
Hopefully, the following information is in line with your thread's basic intent. If it's too tangential, let me know, and I'll shorten it to a one-line link to a thread somewhere else!
-------------------------
As well as "type=inno" and "type=ascii" modes, the Tactrix standalone logger is capable of supporting a built-in ADC circuit ("type=adc"). This is an analogue 0-5V reading from Pin 8 (unused, apparently).
A raw millivolt log is done like this:
Code:
;----------------adc----------------
type=adc ; log from built-in ADC channels
paramname=millivolts
paramid=8 ; paramid is pin number on OBD connector.
; Valid pins are 8 and 16.
; values are pre-scaled to millivolts.
scalingrpn=x
I use this ADC method to log my Innovate LC-1, because the Taxtrix unit's implementation of LC-1 digital link is currently broken. My wideband's 0V-5V analogue output is mapped to 10.0:1 - 15.0:1 range, so the standalone ADC logging is configured as follows:
Code:
;----------------adc----------------
type=adc ; log from built-in ADC channels
paramname=WideBandAF
paramid=8 ; paramid is pin number on OBD connector.
; Valid pins are 8 and 16.
; values are pre-scaled to millivolts.
scalingrpn=x,0.001,*,10.05,+ ; Here we scale from millivolts to AFR.
;
; The LC-1 is configured to output:
; 0V = 10:1
; 5V = 15:1
;
; Includes a 0.05V "fudge factor", as my OP2.0
; ADC reading is ever so slightly low.
Rich
Credit goes to richardjh for the following code from his "tweaking and tuning" thread.
Add these parameters at the beginning of the logcfg.txt file. You will have to change the header of the output log file from "time" to "LogEntrySeconds" but this makes the output file EcuEdit AND EvoScan friendly.
*Note - the logcfg.txt files provided by Razorlab will open in EcuEdit in their original format*
Add these parameters at the beginning of the logcfg.txt file. You will have to change the header of the output log file from "time" to "LogEntrySeconds" but this makes the output file EcuEdit AND EvoScan friendly.
*Note - the logcfg.txt files provided by Razorlab will open in EcuEdit in their original format*
Code:
;-------------parameters------------- ; paramname=LogEntryDate ; Dummy entry - Designed to produce an EvoScan style format paramid=0x808a4b ; that can be loaded into "Log and Power Graph" without (much) scalingrpn=0 ; reformatting. sampgroup = 1 ; Use a sample group to avoid impacting logging performance. paramname=LogEntryTime ; Dummy entry paramid=0x808a4b scalingrpn=0 sampgroup = 1 paramname=LogNotes ; Dummy entry paramid=0x808a4b scalingrpn=0 sampgroup = 1
Last edited by omegis; Apr 25, 2011 at 04:12 PM.
Thread Starter
Joined: Aug 2003
Posts: 14,094
Likes: 1,093
From: Mid-Hudson, NY
Credit goes to richardjh for the following code from his "tweaking and tuning" thread.
Add these parameters at the beginning of the logcfg.txt file. You will have to change the header of the output log file from "time" to "LogEntrySeconds" but this makes the output file EvoScan and EcuEdit friendly.
Add these parameters at the beginning of the logcfg.txt file. You will have to change the header of the output log file from "time" to "LogEntrySeconds" but this makes the output file EvoScan and EcuEdit friendly.
I know. I should've added that disclaimer. I've opened it in EcuEdit too w/o the parameters but was trying to avoid sounding "wordy". The parameters I provided are meant to assist in viewing logs with EvoScan. If anything, they won't hinder the ability to view logs within EcuEdit.
Last edited by omegis; Apr 25, 2011 at 04:14 PM.
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
There also seems to be a buglet in EvoScan's graphing that wants a dummy entry like "Custom" at the end of the log. It's like EvoScan can't graph the final data column - my version, anyway. If you get this, tweak some more! 
Remember to use sample groups to avoid slowing things down with all the dummy entries.
Rich
Remember to use sample groups to avoid slowing things down with all the dummy entries.
Rich
Code:
paramname=WGDC_Active paramid=0x808b6d scalingrpn=x,2,/ sampgroup=1
Then I remembered something about setting sampgroup= values to slow up sampling of data from sensors that don't read quickly changing data (e.g. Baro, and temp sensors). Once I remembered that, and commented out the sampgroup= line from my logcfg.txt file I found my log files appeared to log better/more accurate WGDC information.
***EDIT: Thought I'd add this information for people that are trying to fine tune their WGDC tables using data logged with this method...
Last edited by nunyas; May 10, 2011 at 01:59 PM.
Bryan (or anyone that knows for that matter),
I decided that I want to start logging my SST temps using this method of logging. The following is what I put in my logcfg.tct file:
This doesn't seem quite right. My test log only logged values of "419". I did some reverse calculations and came up with a value of 255. If I were to use the EvoScan calculation (x-50) for this (from the "2009+ Ralliart Evoscan addresses / info" thread), my log entries would be 205.
My test log was only about a minute long at idle w/ 1 throttle blip, but it was long enough to register changes in AIT, MAT, and ECT, but like I said the SST Temp didn't change during this time.
Does that information look correct for the logcfg.txt file? Or is the stand alone logger not capable of logging this particular address?
I decided that I want to start logging my SST temps using this method of logging. The following is what I put in my logcfg.tct file:
Code:
paramname=SSTTemp paramid=CAN28-0 scalingrpn=x,1.8,*,40,- sampgroup=1
My test log was only about a minute long at idle w/ 1 throttle blip, but it was long enough to register changes in AIT, MAT, and ECT, but like I said the SST Temp didn't change during this time.
Does that information look correct for the logcfg.txt file? Or is the stand alone logger not capable of logging this particular address?