Welcome to the North American Subaru Impreza Owners Club Monday July 15, 2019
Home Forums WikiNASIOC Products Store Modifications Upgrade Garage
NASIOC
Go Back   NASIOC > NASIOC Technical > Engine Management & Tuning > Open Source Reflashes

Welcome to NASIOC - The world's largest online community for Subaru enthusiasts!
Welcome to the NASIOC.com Subaru forum.

You are currently viewing our forum as a guest, which gives you limited access to view most discussions and access our other features. By joining our community, free of charge, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is free, fast and simple, so please join our community today!

If you have any problems with the registration process or your account login, please contact us.
* Registered users of the site do not see these ads. 
Reply
 
Thread Tools Display Modes
Old 01-18-2013, 07:42 PM   #1
Ziggyrama
Scooby Specialist
 
Member#: 53665
Join Date: Jan 2004
Chapter/Region: NESIC
Location: Northboro, MA
Vehicle:
2011 STI Stg2 w/ ELH
Focal 2way Active w/ DSP

Default SD card logging, alternative start/stop switch

If you're using SD card fast logging and you don't like using the defogger switch to trigger and stop the logging, there is an alternative. Personally, I don't like using the defogger as it pumps unnecessary current through the back window and if I really want to use it on the back window, I have to disconnect Tactrix so that I don't get extraneous logs on the SD card. For those of you with 08+ WRXs and STIs, there's a better way. Instead of the defogger, I decided to use the cruise control buttons on the steering wheel instead. The set button can act as a start and cancel button as stop. To pull this off, you have to change the logger configuration file and define a new way of starting and stopping the logger:

1. On the SD card, open LogCfg.txt text file with an editor of choice.

2. Add the following sections to the file which define cruise control buttons and how to use their signals to start and stop the logger.

Code:
; cruise set signal
paramname = cruise_set_coast
paramid = 0x000121
databits = 1
offsetbits = 5
isvisible = 0

; cruise cancel signal
paramname = cruise_cancel
paramid = 0x0000D7
databits = 1
offsetbits = 0
isvisible = 0

; start action, 
conditionrpn = cruise_set_coast,1,==
action = start

; stop action
conditionrpn = cruise_cancel,1,==
action = stop
3. Comment out your current start and stop actions by placing semicolon in front of the section that defines your current start and stop actions. The logger will ignore them and if you ever decide to go back to using the defogger switch, you'll have an easy way to reference it.

Note, I tested this with latest EcuFlash version 1.44.3719.

How did I find these addresses? They come from RomRaider's logger definition file. I'm not sure if these switches vary between ROMs. Based on the definition file, they seem to be universal for all the ROMs.
* Registered users of the site do not see these ads.
Ziggyrama is offline   Reply With Quote
Sponsored Links
* Registered users of the site do not see these ads.
Old 01-23-2013, 07:01 PM   #2
stackedape
Scooby Newbie
 
Member#: 344670
Join Date: Jan 2013
Default

Look at you my Brotha, teaching the folk! hahaha
stackedape is offline   Reply With Quote
Old 01-23-2013, 08:42 PM   #3
Ziggyrama
Scooby Specialist
 
Member#: 53665
Join Date: Jan 2004
Chapter/Region: NESIC
Location: Northboro, MA
Vehicle:
2011 STI Stg2 w/ ELH
Focal 2way Active w/ DSP

Default

Quote:
Originally Posted by stackedape View Post
Look at you my Brotha, teaching the folk! hahaha
Hey Bro, good to see you on the site!
Ziggyrama is offline   Reply With Quote
Old 02-14-2014, 03:02 PM   #4
uk2006wrx
Scooby Newbie
 
Member#: 331547
Join Date: Sep 2012
Default

Thanks that's really useful to learn, and agree this is a neater way of triggering the logging.
uk2006wrx is offline   Reply With Quote
Old 12-16-2018, 08:37 PM   #5
pdximpreza
Scooby Newbie
 
Member#: 17606
Join Date: Apr 2002
Chapter/Region: NWIC
Location: Portland area, OR
Vehicle:
2008 STI hatchback
Silver

Default

I know necro'ing threads bothers people. But search engines pull up this thread, and I don't find much information on it. So I thought I would post what I have found here so that others who do a Google search wont find multiple thread hits and have to try and dig through it.

Ziggy's information is great, unless you want to try and figure out what other alternate triggers you might want to use on your own.

First you can use ANYTHING the logger is capturing to start and stop the log. You can chose an RPM, coolant temp, throttle position, anything you are capable of and defined in your logcfg.txt. If you are like me, you are using the website http://romraider.com/logcfg/ to create the logcfg.txt from the Romraider profile. So you aren't digging into who its all figured out.

The addresses and offset bits are found in the logger definition .xml. So the latest I am using is logger_STD_EN_v346.xml. I use Notepad++ to open it because it allows me to collapse the file structure. I then did a ctrl+F 'find' for cruise, and I found what Ziggy used. Here is the line;

<switch id="S65" name="Cruise Control Set/Coast Switch" desc="S65" byte="0x000121" bit="5" ecubyteindex="45" target="1" />

Now the reason why I was motivated to write this is, how do you determine what that offset bit is supposed to be? Thats the bit=5 on that line in the logger def.

So for instance cruise resume is offsetbit = 4 instead.

So my next step is I don't want to use cruise set. I want to use the cruise light. I tried using the cruise toggle, but its only momentary so I get 3 lines of data. But nothing in the logger def is obvious for that light. So now I will log each of these cruise other cruise values, mainly;

<switch id="S77" name="Cruise Control Signal" desc="S77-TCU input." byte="0x00006A" bit="6" ecubyteindex="28" target="2" />

and

<switch id="S133" name="Cruise Control System Status" desc="S133" byte="0x000121" bit="0" ecubyteindex="45" target="3" />

To see if one of those holds a high 1 status like the 'cruise' on light on the dash.

So I will just add this to my logcfg.txt;

; Cruise Control Signal
paramname = Cruise1
paramid = 0x121
databits = 1
offsetbits = 6

; Cruise Control System Status
paramname = Cruise2
paramid = 0x121
databits = 1
offsetbits = 0

Unfortunately with the cruise status I have to drive the car because of the cruise inhibitor when its not running or moving... But normally you can just go plug the OP2.0 in and turn the key over to power up the ECU and press the switches you're going to use. Then check your log. If it works then you can add the isvisible = 0 so its no longer logged and then configure your trigger with that paramname.

I think I'll have to go through and edit that sound it makes sense outside my head.
pdximpreza is offline   Reply With Quote
Old 12-16-2018, 09:56 PM   #6
Ziggyrama
Scooby Specialist
 
Member#: 53665
Join Date: Jan 2004
Chapter/Region: NESIC
Location: Northboro, MA
Vehicle:
2011 STI Stg2 w/ ELH
Focal 2way Active w/ DSP

Default

Nice job! Wow, I totally forgot I wrote this up few years ago. Glad to see folks find it useful.
Ziggyrama is offline   Reply With Quote
Old 12-17-2018, 12:07 AM   #7
pdximpreza
Scooby Newbie
 
Member#: 17606
Join Date: Apr 2002
Chapter/Region: NWIC
Location: Portland area, OR
Vehicle:
2008 STI hatchback
Silver

Default

Thank you! There is honestly almost nothing regarding this topic! But it allows so much possibilities. Like logging if it starts knocking. Or logging if it starts over heating. But the only examples are RPM and the defroster. This thread was the only thing that gave me hope at doing something more haha.

Cheers!
pdximpreza is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

All times are GMT -4. The time now is 04:08 PM.


Powered by vBulletin® Version 3.7.0
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
Powered by Searchlight © 2019 Axivo Inc.
Copyright ©1999 - 2017, North American Subaru Impreza Owners Club, Inc.