Standalone Logging to MicroSD w/ OPv2.0

I'm starting this post to get some help from the guys who are really into datalogging and the whole open-source thing. With my twinscroll project at the point where it is running pretty smooth, and all the little gremlins taken care of, I can finally focus on getting my datalogging setup to monitor the engine at all times.

My plan is to utilize the MicroSD logging that is now supported on the OPv2.0 and with my 8GB MicroSDHC card that I bought for $20 at Radioshack yesterday, I can get about ~20yrs worth of data before needing to dump it to my computer.

I have a couple basic issues that I need to sort out:

1. What data to log for general health of the engine and for my own curiosity? Here's what I have been monitoring and what I would like to add:

• A/F Correction #1 (%)
• A/F Learning #1 (%)
• A/F Sensor #1 (AFR)
• CL/OL Fueling* (status)
• Engine Load (2-byte)** (g/rev)
• Engine Speed (RPM)
• Ignition Total Timing (degrees)
• Knock Sum* (count)
• Manifold Relative Pressure (PSI)
• Throttle Opening Angle (%)

Adding:

• LC1 Output
• Mass Airflow (g/s) - Unless this can be derived from Engine Load.
• Closed Loop Fueling Target (2-byte) - @ NSFW's recommendation.

2. I don't know how to parse all this information that I am collecting. I realize this is specific to my goals, so when it comes to plotting how my turbo is working on it's compressor map this is very straight-forward. However for monitoring general health, I don't really know what to do.

3. Finally, I don't know how to setup the logcfg.txt file for standalone logging. It seems like there are a lot of options for setting up parameters, scaling them, and grouping them, and I don't know the most efficient way to do it. I think I would like to log any time the car is 1) running and 2) coolant temperature is >= 160 (or something). Also, I would like to start a new log any time I go WOT.


Any insight would be appreciated... In the meantime I am going to take a stab at the logcfg.txt file and post it up for review.

Pardon the newbie question but ... what hardware are you using to datalog?

Right now I use my laptop with RomRaider connected via Tactrix Open Port v2.0 (OPv2.0).

The OPv2.0 has a built in microSD card slot so you can datalog without hooking up a computer, but you need to specify what parameters to log with a logcfg.txt file in the root directory of the microSD card.

Here is the thread on OpenECU.org: http://forums.openecu.org/viewtopic....icrosd+logging

Well, apologies for threadjacking with such a noob question, I was not aware of the existence of said OPV2.0. That is indeed a neat thing. I assume the same trigger to start/stop logging (rear defroster)? I have a list of parameters I was told to datalog but I am hesitant because I am a newbie at logging and don't want to potentially post the wrong thing.

Ah, the heck with it. Others can correct me if I am wrong
Engine Load (2-byte)** (g/rev)
Engine Speed (rpm)
IAM (4-byte)* (multiplier)
Ignition Total Timing (degrees)
Knock Sum* (count)
Manifold Relative Pressure (4-byte)* (psi relative)
Mass Airflow (g/s)
Mass Airflow Sensor Voltage (V)
Primary Wastegate Duty Cycle Angle (%)
Throttle Opening Angle (%)

It's no problem man... I'm a newbie to this stuff too.

There are a wide variety of triggers you can use. From what I have seen you can use any switch in the OBD2 data chain, or you can use logic functions with engine parameters.

For example, you can make it so that it only logs when RPM>0, coolant temp >=160, and the cruise control button is "on". What's more, you can have it start a new log any time there is some additional criteria... like every time you go WOT it starts a new log. Cool huh?

The problem is the logcfg.txt file needs to be formatted in programming language. The parameter ID, the RPN scaling, the groups, bits, etc... all things I'm not sure what to do with. Also, I don't know which type of ECU I have... CAN or K-line?

For example:

type = ssmcan

paramname = Engine_Speed(rpm)
paramid = 0x00000E
databits = 16
scalingrpn = x,4,/

paramname = Ignition_Total_Timing(degrees)
paramid = 0x000011
databits = 8
scalingrpn = x,128,-,2,/

paramname = Intake_Air_Temperature(C)
paramid = 0x000012
databits = 8
scalingrpn = x,40,-

paramname = Coolant_Temperature(C)
paramid = 0x000008
databits = 8
scalingrpn = x,40,-

paramname = Mass_Airflow(g/s)
paramid = 0x000013
databits = 16
scalingrpn = x,100,/

paramname = Throttle_Opening_Angle(%)
paramid = 0x000015
databits = 8
scalingrpn = x,100,*,255,/

paramname = Mass_Airflow_Sensor_Voltage(V)
paramid = 0x00001D
databits = 8
scalingrpn = x,50,/

paramname = Primary_Wastegate_Duty_Cycle(%)
paramid = 0x000030
databits = 8
scalingrpn = x,100,*,255,/

paramname = Fine_Learning_Knock_Correction(degrees)
paramid = 0x000199
databits = 8
scalingrpn = x,0.25,*,32,-

paramname = A/F_Learning_#1_A_(Stored)*(%)
paramid = 0xFF2C90
isfloat = 1
scalingrpn = x,100,*

paramname = A/F_Learning_#1_B_(Stored)*(%)
paramid = 0xFF2C98
isfloat = 1
scalingrpn = x,100,*

paramname = A/F_Learning_#1_C_(Stored)*(%)
paramid = 0xFF2CA0
isfloat = 1
scalingrpn = x,100,*

paramname = Engine_Load_(1-byte)**(g/rev)
paramid = 0xFF6A5F
databits = 8
scalingrpn = x,.015625,*

paramname = Feedback_Knock_Correction_(1-byte)**(degrees)
paramid = 0xFF6A69
databits = 8
scalingrpn = x,.3515625,*,45,-

paramname = IAM_(1-byte)**(multiplier)
paramid = 0xFF6A6B
databits = 8
scalingrpn = x,.0625,*

paramname = Manifold_Relative_Pressure_(4-byte)*(psi_relative)
paramid = 0xFF643C
isfloat = 1
scalingrpn = x,0.01933677,*

paramname = mylc1.afr
paramid = 0x0102 ; get lambda from first LC-1
scalingrpn = x,14.7,* ; scale to an AFR

paramname = defogger_sw
paramid = 0x64
databits = 1
offsetbits = 5
isvisible = 0

conditionrpn = defogger_sw,1,==
action = start

conditionrpn = defogger_sw,0,==
action = stop

Originally Posted by fishbone

Ah, the heck with it. Others can correct me if I am wrong
Engine Load (2-byte)** (g/rev)
Engine Speed (rpm)
IAM (4-byte)* (multiplier)
Ignition Total Timing (degrees)
Knock Sum* (count)
Manifold Relative Pressure (4-byte)* (psi relative)
Mass Airflow (g/s)
Mass Airflow Sensor Voltage (V)
Primary Wastegate Duty Cycle Angle (%)
Throttle Opening Angle (%)

Log either mass airflow g/s or sensor volts. You don't need both. Also just check the IAM prior to logging. FWIW...seems easier to just log with the laptop.

Once I get home I can share my logcofg.txt that I use. I have it automatically come on with coolant temperature as well.

You will love microSD datalogging. Its so easy. You get boatloads of data and pretty good sampling rates. I never did get LC-1 working but I did not dive that deep into it either.

Originally Posted by Ridgeracer

FWIW...seems easier to just log with the laptop.

Debatable. You can also setup to log with one of the car's switches... so if you just keep the Tactrix plugged in all the time, if you are ever in the mood to log, just trigger it. You can log whenever you want w/o the need for a laptop or any setup.
Its great for logging on the fly. Its also great for logging in CL to scale the maf. I logged all my CL driving for weeks and summarized it... you can really fine-tune the maf for daily driving. I just got in the car and drove, it did the logging automatically for me.

Originally Posted by LGTspecB

Debatable. You can also setup to log with one of the car's switches... so if you just keep the Tactrix plugged in all the time, if you are ever in the mood to log, just trigger it. You can log whenever you want w/o the need for a laptop or any setup.
Its great for logging on the fly. Its also great for logging in CL to scale the maf. I logged all my CL driving for weeks and summarized it... you can really fine-tune the maf for daily driving. I just got in the car and drove, it did the logging automatically for me.

Exactly... I hate having the cable draped over my steering column and I find myself constantly looking at the computer to check the knock sum, and then alter my driving based on it. It's uncomfortable and unsafe.

If I could figure out how to properly set it up for normal CL logging and occasional conditional logging (like if I want to do a WOT run to plot on my compressor map) then it will be perfect.

Checkout this post on RomRaider

http://www.romraider.com/forum/post58238.html

That is awesome enthusiast. Thanks!

I will play with it at lunch and try to make something to start from.

So with my '06 (ECUID A2WF200N) do I have the K-line or CAN ECU type?

Originally Posted by Underdog

So with my '06 (ECUID A2WF200N) do I have the K-line or CAN ECU type?

K-Line