Can you post your config file? That would be the easiest way of seeing what's going on.
This is a discussion on OP2 Stand Alone logging woes. within the Tuning: Electronic Engine Management forums, part of the Tech & Modifying & General Repairs category; Flashed to TP Stage 1 last week and it runs great. Logging with Romraider took some finagling and cursing but ...
Flashed to TP Stage 1 last week and it runs great. Logging with Romraider took some finagling and cursing but works smoothly now (even the dubious dyno feature). But for the past week I have been unable to get the stand alone function to work properly. If I use the defrogger trigger I get an empty logcfg.out file. If I use rpm >0 just to see numbers I get 509 identical .csv files with one line each and the numbers are insane, 10700+rpm 104.39mph etc. After more research into this than I can even imagine I am just stumped now.
I have FW version 1.12.3688, everything works and seems to calculate the TP suggested parameters (using the TP definitions) fine with RR, just the stand alone seems to be beyond my comprehension.
Anyone have any insight or similar issues?
Not as many parts left over this time... what am I missing?
Can you post your config file? That would be the easiest way of seeing what's going on.
Isaac -- 2003 WRX sedan Stg II
Proud owner of a N.E.R.D, Member 1.38×10-23
He who shall be last, shall be sideways and smiling... - Jeremy Clarkson
Sure, I do have the CAN enable patch up and running according to ecuflash (ver 1.44.whatever). I couldnt use freakin's config maker from the RR forums due to some error so this has been bashed out pretty much by hand going over TP definitions and some samples found here and eslewhere. I altered some of the scaling that TP had from division to multiplication as per the Heide example config file.
type = ssmcan
;P3 - A/F Correction #1(%)
paramname = A/F_Correction_#1(%)
paramid = 0x000009
scalingrpn = x,128,-,0.78125,*
;P4 - A/F Learning #1(%)
paramname = A/F_Learning_#1(%)
paramid = 0x00000A
scalingrpn = x,128,-,0.78125,*
;P8 - RPM
paramname = Engine Speed
paramid = 0x00000E
databits = 16
scalingrpn = x,0.25,*
;P9 - Vehicle Speed(mph)
paramname = Vehicle_Speed(mph)
paramid = 0x000010
scalingrpn = x,0.621371192,*
;P10 - Ignition Total Timing(degrees)
paramname = Ignition_Total_Timing(degrees)
paramid = 0x000011
scalingrpn = x,128,-,0.5,*
;P11 - Intake Air Temperature(F)
paramname = Intake_Air_Temperature(F)
paramid = 0x000012
scalingrpn = x,40,-,1.8,*,32,+
;P12 - Mass Airflow(g/s)
paramname = Mass_Airflow(g/s)
paramid = 0x000013
databits = 16
scalingrpn = x,0.01,*
;P18 - Mass Airflow Sensor Voltage(V)
paramname = Mass_Airflow_Sensor_Voltage(V)
paramid = 0x00001D
scalingrpn = x,0.2,*
;P36 - Primary Wastegate Duty Cycle(%)
paramname = Primary_Wastegate_Duty_Cycle(%)
paramid = 0x000030
scalingrpn = x,0.39216,*
;P90 - IAM(multiplier)
paramname = IAM(multiplier)
paramid = 0x0000F9
scalingrpn = x,0.0625,*
;P91 - Fine Learning Knock Correction(degrees)
paramname = Fine_Learning_Knock_Correction(degrees)
paramid = 0x000199
scalingrpn = x,0.25,*,32,-
;E86 - Engine Load (1-byte)**(g/rev)
paramname = Engine_Load_(1-byte)**(g/rev)
paramid = 0xFF6865
scalingrpn = x,.015625,*
;E92 - A/F Sensor #1 (2-byte)**(estimated AFR)
paramname = A/F_Sensor_#1_(2-byte)**(estimated AFR)
paramid = 0xFF6838
databits = 16
scalingrpn = x,.0001220703,*,14.7,*
;E93 - Throttle Plate Opening Angle (2-byte)**(%)
paramname = Throttle_Plate_Opening_Angle_(2-byte)**(%)
paramid = 0xFF6832
databits = 16
scalingrpn = x,0.0022706535,*
;E94 - Feedback Knock Correction (1-byte)**(degrees)
paramname = Feedback_Knock_Correction_(1-byte)**(degrees)
paramid = 0xFF686F
scalingrpn = x,.3515625,*,45,-
;P21 - Fuel Injector #1 Pulse Width(ms)
paramname = Fuel_Injector_#1_Pulse_Width(ms)
paramid = 0x000020
scalingrpn = x,0.256,*
isvisible = 0
;P7 - Manifold Absolute Pressure(psi)
paramname = Manifold_Absolute_Pressure(psi)
paramid = 0x00000D
scalingrpn = x,0.1450980392,*
isvisible = 0
;P24 - Atmospheric Pressure(psi)
paramname = Atmospheric_Pressure(psi)
paramid = 0x000023
scalingrpn = x,0.1450980392,*
isvisible = 0
; Defogger Switch Trigger
paramname = Rear Defogger Switch
paramid = 0x64
databits = 1
offsetbits = 5
isvisible = 0
type = calc
;P201 - Injector Duty Cycle(%)
paramname = Injector_Duty_Cycle(%)
scalingrpn = Engine Speed,Fuel_Injector_#1_Pulse_Width(ms),*,0.0008333 333,*
;P202 - Manifold Relative Pressure (Corrected)(psi)
paramname = Manifold_Relative_Pressure_(Corrected)(psi)
scalingrpn = Manifold_Absolute_Pressure(psi),Atmospheric_Pressu re(psi),-
;conditionrpn = Rear Defogger Switch,1,==
;action = start
;conditionrpn = Rear Defogger Switch,0,==
;action = stop
conditionrpn = Engine Speed,1800,>
action = start
conditionrpn = Engine Speed,0,==
action = stop
The rpm trigger was just my most recent attempt to see if it would start on something other than idle, but no it didnt. In fact it just made an empty .out file and the little green light was strobing fast the whole time it was plugged in.
Not as many parts left over this time... what am I missing?
Hmm, I don't see any glaring syntax issues with the config sheet, so I'd recommend double-checking your data bits and parameter IDs and make sure they match your ECU.
Isaac -- 2003 WRX sedan Stg II
Proud owner of a N.E.R.D, Member 1.38×10-23
He who shall be last, shall be sideways and smiling... - Jeremy Clarkson
The defrost button trigger usually doesn't work right.. just click log on the laptop.
2012 WRX Ltd. Wagon AE5k500L ECUID 8112585007
I do appreciate yall looking at this. I needed a fresh set of eyes as I was losing my mind very slowly and in small small bits. My wife, the professional engineer, just smiled and said sorry while doing her best to not ask about emissions violations.
Not as many parts left over this time... what am I missing?
Update.
Started over, new config file
type = ssmcan
paramname = Engine_Speed(rpm)
paramid = 0x00000E
databits = 16
scalingrpn = x,4,/
conditionrpn = Engine_Speed(rpm),0,>
action = start
conditionrpn = Engine_Speed(rpm),0,==
action = stop
Worked fine, made one file over the course of a minute idling in my garage and was able to verify the data just by sitting there looking at my tach. Troubleshooting 101, simple first, then add to it.
Not as many parts left over this time... what am I missing?
Actually, I agree with that. I've had issues with that button working for whatever reason (both in standalone mode and when connected to the laptop). Good call on changing the trigger setup, I might have to plagerize your code there.
Depending on what you want to do, though, ignition on to off might make a much bigger log than you need. Maybe use the throttle % and only trip when you go WOT?
Isaac -- 2003 WRX sedan Stg II
Proud owner of a N.E.R.D, Member 1.38×10-23
He who shall be last, shall be sideways and smiling... - Jeremy Clarkson
The WOT is my eventual choice for the stand alone logging, but getting there is taking teaching an old dog new tricks.
Just switched up the baby step log to incorporate the defrogger switch, lifted it from Heide264's example.
type = ssmcan
paramname = Engine_Speed(rpm)
paramid = 0x00000E
databits = 16
scalingrpn = x,0.25,*
paramname = defogger_sw
paramid = 0x64
databits = 1
offsetbits = 5
isvisible = 0
conditionrpn = defogger_sw,1,==
action = start
conditionrpn = defogger_sw,0,==
action = stop
;conditionrpn = Engine_Speed(rpm),0,>
;action = start
;conditionrpn = Engine_Speed(rpm),0,==
;action = stop
Worked perfectly, a new log with every defrogger on. Ignored the rpm trigger entirely. Still only recording RPM's and not very useful but maybe just adding one parameter at a time I will get to where I have some useful logs. And maybe, just maybe sort out what is causing the initial issue... Earlier today I went back to the first logcfg I had made and got a whole new set of wacky numbers again. Apparently when I thought I was warming it up in the garage before some errands this morning and getting the car loaded with recycling I was actually pegged out at 104.39mph and 10743 rpm with an IAM of 10.5.... in the garage.
Not as many parts left over this time... what am I missing?
I just saw this post - sorry for taking so long.
Looks like you got the idea. It's always tough to get that up and running. Normally with my issues, it is either related to messing with start/stop parameters or scaling. The OP2.0 really hates odd things... like spaces in between scaling terms for example.
If you didn't know, they just put out a new official version of EcuFlash on the tactrix site. It incorporates all the changes from the shady Evo forum version I've been using (supposedly). I haven't tried it yet, but you may want to download that and update the firmware on the cable. Especially if you start adding in things like sampgroup and a wb02 input, the firmware starts to become important.
The RPM stuff is touchy. I always just use it to compare to zero. The recent update allows you to use a # before a parameter to denote "previous"... so you can say if the RPM has increased or anything of the such. I have a feeling the cable is recording so fast, however, it won't be of much use.
Also - I fry SD cards every few months. I start getting weird wingdings here and there, and it randomly skips a sample in my log (you'll notice when the columns don't line up correctly). It happens. I just buy a couple of the cheapo ones on amazon at a time.
2011 STi Build LogOriginally Posted by Trainrex
Resident Tuner @ WTF Tuning, LLC
-Part 1 - Reading, Data Logging, and Analyzing Data
-Part 2 - Turbocharger 101 & Basic Boost Control
-Part 3 - EcuFlash, Experimental Defintions, and a Drive By Wire Intro
Thanks for the heads up on the updates, I will find out if there in lies my solution or if I will continue adding one parameter at a time till I am done. I used RPM as it is the only parameter other than speed I can verify sitting in my garage. Also good info about the SD card. I am sure to burn this one up with all my baby steps.
I will probably keep updating this mainly for a record in case others are having issues and are as stubborn as I am (why wont you work dammit!?!??!?!). I think some of the issues I was having initially is my reading comprehension sucks ass compared to my trial and error learning. Many of the threads out there start from the assumption the reader has a comprehensive understanding of the vernacular as well as subject matter. I put a couple of those books mentioned in the WTFtuning thread on my wishlist for some light reading while I save for sway bars and endlinks.
Thanks again for all the input from everyone. The extra sets of eyes are more help than anything.
Not as many parts left over this time... what am I missing?
FWIW, I bought Engine Management: Advanced Tuning by Greg Banish and Forced Induction Performance Tuning A Practical Guide to Supercharging and Turbocharging by A. Graham Bell from that list. I'd recommed both, particularly the A. Graham Bell one. The writing style is much more verbose than the Banish book, but I found the information the most useful.
Isaac -- 2003 WRX sedan Stg II
Proud owner of a N.E.R.D, Member 1.38×10-23
He who shall be last, shall be sideways and smiling... - Jeremy Clarkson
I had some major issues with copying the addresses over correctly and getting RPN setup right for scaling... so I built a tool that did it for me. Just go here, upload your RomRaider Logger Profile XML (your saved parameters), pick your options and call it a day!
OpenPort LogCfg Generator
Bigger write up: RomRaider • View topic - Tactrix Standalone Logging Config Tool
Last edited by hunterjm; 01-08-2013 at 05:46 PM.
Isaac -- 2003 WRX sedan Stg II
Proud owner of a N.E.R.D, Member 1.38×10-23
He who shall be last, shall be sideways and smiling... - Jeremy Clarkson
Bookmarks