Jump to content
LegacyGT.com

Standalone Logging to MicroSD w/ OPv2.0


Underdog

Recommended Posts

How far did you have to push it in before it clicked? Maybe a picture of how far it sticks out once you feel it click. I know this sounds dumb but I used my nail and the damn thing still wouldn't click.
Link to comment
Share on other sites

  • Replies 88
  • Created
  • Last Reply
How far did you have to push it in before it clicked? Maybe a picture of how far it sticks out once you feel it click. I know this sounds dumb but I used my nail and the damn thing still wouldn't click.

 

Mine clicks in once you push it to the inner edge of the clear plastic. The outer edge of my card sits at about the middle of the clear plastic.

 

Does that make sense?

Link to comment
Share on other sites

  • 3 weeks later...
  • 6 months later...

so does anyone have a logcfg that you can share? I'm having trouble getting mine to trigger

 

 

type=ssmcan

 

paramname = Engine_Speed

paramid = 0x00000E

databits = 16

scalingrpn = x,4,/

 

paramname = Throttle_Opening_Angle(%)

paramid = 0x000015

databits = 8

scalingrpn = x,100,*,255,/

 

paramname = Ignition_Total_Timing

paramid = 0x000011

databits = 8

scalingrpn = x,128,-,2,/

 

paramname = Mass_Airflow

paramid = 0x000013

databits = 16

scalingrpn = x,100,/

 

paramname = Throttle_Opening_Angle

paramid = 0x000015

databits = 8

scalingrpn = x,100,*,255,/

 

paramname = Mass_Airflow_Sensor_Voltage

paramid = 0x00001D

databits = 8

scalingrpn = x,50,/

 

paramname = Primary_Wastegate_Duty_Cycle

paramid = 0x000030

databits = 8

scalingrpn = x,100,*,255,/

 

paramname = Engine_Load_(2-byte)**

paramid = 0xFF530C

databits = 16

scalingrpn = x,.00006103516,*

 

paramname = IAM_(1-byte)**

paramid = 0xFF5339

databits = 8

scalingrpn = x,.0625,*

 

paramname = Manifold_Relative_Pressure_(4-byte)*

paramid = 0xFF4F34

databits = 32

scalingrpn = x,0.01933677,*

 

paramname = Knock_Sum*

paramid = 0xFF5CEC

databits = 8

scalingrpn = x

 

;-------------triggers---------------

paramname = defogger_sw

paramid = 0x64

databits = 1

offsetbits = 5

isvisible = 0

 

conditionrpn = defogger_sw,1,==

action = start

 

conditionrpn = defogger_sw,0,==

action = stop

Link to comment
Share on other sites

  • 1 year later...
If you're doing some cruising closed loop logs, 10 mins wouldn't be bad. You'd just have to filter out the data later either through a program or by hand.

 

This.

 

In fact when I am collecting data to scale the MAF for closed loop I tend to take several 30+ minute drives, and filter then scatter plot all of the data from those drives. For this task I do not use the defogger trigger. For long term logging I use coolant temp as the trigger.

 

Nice to see other people using this feature.

Link to comment
Share on other sites

the lc feeds via serial port into the computer, not the tactrix

 

They actually both work.

Unfortunately, I still haven't figured out how to get my LC1 to feed into the tactrix so most of my logging is still to a net book.

 

The lc-1 comes with a jack that will plug right into the openport 2. I had a hell of a time getting the standalone logging stuff figured out.

 

First off the latest version of ecuflash is not available at openecu.org. The latest version on that website seemed to have an issue with capturing data from the lc-1. Over on the evoscan website you can find a newer version of ecuflash. That new version of ecuflash has a new firmware for the openport. Once the openport was flashed the lc-1 started logging as expected.

 

**IMPORTANT**

 

The version of ecuflash that is on the evoscan website has a driver that does not work with romraider. What I did to get everything working is this.

 

1. Install ecuflash from evoscan, accept driver installs.

2. Update openport firmware with "licensing" menu.

3. Using device manager delete the openport driver from your system.

4. Uninstall ecuflash.

5. Install ecuflash from openecu site, accept driver installs.

6. Uninstall ecuflash.

7. Install ecuflash from evoscan, REJECT the driver installs.

 

If you do this you end up with the latest firmware on the tactrix device, the latest ecuflash, and the openport driver from the version that is compatible with romraider.

 

I had to do this because there is no way to "flash back" the original firmware. And after the firmware upgrade the earlier versions of ecuflash would BSOD my system.

 

This is probably not a supported configuration, and any damage done would be your own fault. But having said that it has worked out fine for me.

Link to comment
Share on other sites

lordelder-I got the rest of the standalone logging to work, just not the LC1 part. I did those steps already but I'll try again. :/

 

Well lets address the log config file to be sure syntax is correct...

This is one of my logging configs:

type=ssmcan

paramname = Engine_Load_(Relative)(%)
paramid = 0x000007
databits = 8
scalingrpn = x,100,*,255,/

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

paramname = A/F_Correction_#1(%)
paramid = 0x000009
databits = 8
scalingrpn = x,128,-,100,*,128,/

paramname = A/F_Learning_#1(%)
paramid = 0x00000A
databits = 8
scalingrpn = x,128,-,100,*,128,/

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(F)
paramid = 0x000012
databits = 8
scalingrpn = 32,9,x,40,-,*,5,/,+

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 = Manifold_Relative_Pressure(psi)
paramid = 0x000024
databits = 8
scalingrpn = x,128,-,37,*,255,/

paramname = A/F_Sensor_#1(AFR)
paramid = 0x000046
databits = 8
scalingrpn = x,128,/,14.7,*

conditionrpn = Coolant_Temperature(C),76,>
action = start

conditionrpn = Engine_Speed(rpm),0,==
action = stop

type=inno
paramname = Lc1_Afr
paramid = 0x0101       ; get lambda from first LC-1
scalingrpn = x,14.7,*  ; scale to an AFR

I have an 08 so my car supports CANbus. I think your 06 does not support CAN so your "type" setting would be ssmk.

 

If you look at the very end of my config I have the LC1 entry there. Placement matters here because you are setting a new type setting for the LC1. Put it after all your normal ecu params.

 

On another topic:

 

If anyone is curious why I am logging load relative % it is because of the limitations with CAN logging. CAN cannot log ram or "extended" parameters.

 

CAN logging is higher resolution so it is rather nice if you dont need to log extended parameters. Keep in mind CAN logging samples data at about 50 rows a second. It will create much larger csv files than kline. Excel may truncate data if you are trying to collect long term (closed loop fuel trim) data for scatterplotting.

 

If anyone has a CAN car once you figure out your logging profile for your tuning task its parameters will dictate whether you can use CAN logging. K-Line logging works on CANbus cars as well so if you need to log an extended param (knock sum for example) just use ssmk.

 

Also if you plan to use Airboys spreadsheet I find it helps to snip the first column (sample) off of your data. His spreadsheet will use the sample column as time if you don't snipt it. Boy do those dyno plots look odd.

Link to comment
Share on other sites

No use still, the lc1 column just reads 0 with the inno plugged in at the end.

 

Did you flash the latest firmware to the openport? You have to download this version:

http://www.evoscan.com/ecuflash/ecuflash_1433252_win.exe

 

Once the software is loaded open ecuflash. Goto the help --> licensing menu and it will flash the openport's firmware.

 

That is the long version of step 2 from my previous post. Sorry if it wasn't clear enough.

 

Again this is likely not the officially supported way to use the software so tinker at your own risk.

 

If you did flash the openport device successfully I don't know what to tell you. Does the lc-1 work with your computer just fine?

 

Where in Texas are you?

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.




×
×
  • Create New...

Important Information

Terms of Use