Openport Stand-Alone Logging Beta

[freakin]

im not sure if the OP2 likes funny characters in the paramnames you could try removing things like * # and () etc then repeat.. let me know if thats killing it and I will strip it from my app

[CasopoliS]

im not sure if the OP2 likes funny characters in the paramnames you could try removing things like * # and () etc then repeat.. let me know if thats killing it and I will strip it from my app

Already tried that for RPM. I will try the others. Thanks.
EDIT - no dice. Even with simple names I get no CSVs. How long does it have to be plugged in before it starts writing the CSV? I kept it plugged in for a while, but the blue light never comes on.

I wonder if it has something to do with the ECU-specific parameters?

[freakin]

does it work with the sample file?

have you verified the version of the s/w on the OP?

[CasopoliS]

does it work with the sample file?

have you verified the version of the s/w on the OP?

It works with the sample file. I am guessing it is having a issue with the ECU -specific parameters?

EDIT - This one works (see below) except knock sum started out at 168... which was weird. I am used to it being 0-32 or something like that.

So, one of the other parameters I was trying must not be right and that is why it was not working before. I don't have time to test it now. Maybe the 4-byte stuff is not working right.

Code: Select all

type = ssmcan

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 = 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,*

paramname = Knock_Sum*(count)
paramid = 0xFF7FEC
databits = 8
scalingrpn = x


conditionrpn = Engine_Speed(rpm),0,>
action = start

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


[mdedwar]

Since using the stand alone logging I have had to recalibrate the LC-1 twice as the LC-1 started showing weird values even through the logworks software. Not sure if this is a problem with pluging it in to the tactrix cable and it randomly reseting the LC-1 or some other problem with the LC-1 (eg lose wire somewhere). However when it is calibrated it has worked fine.

Cheers,
Matt.

Hi Colby,
I spoke to soon. My LC-1 data is logging funny. All the values look like they need to have 10 added to them. They are all between 4.x 5.x at idle. This did work but maybe it was with an old version.

Cheers,
Matt.

[Tephra]

I am also getting some weird log files.

Not so much content, but creation of them.

I went for a 2x 3 hour drives on saturday - expecting a 10+ meg files... Havn't got any.

Also this morning I expected a 2mg file and only got a 1.25m and a 0.25 mg files.

Colby - can you check the logic for creating log files? I think something is up.

btw - I am upto log0126.csv if that helps you!

Cheers
David

[CasopoliS]

Ok here is my update.

The 4byte stuff does not work. Its won't even create a log file if a 4-Byte parameter is called out.

The following Logcfg file works, but the readings are off.
logcfg:

Code: Select all

type = ssmcan

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

paramname = AFR
paramid = 0x000046
databits = 8
scalingrpn = x,128,/,14.7,*

;paramname = Load4byte
;paramid = 0xFF6C40
;isfloat = 1
;scalingrpn = x

paramname = CL/OL
paramid = 0xFFA44D
databits = 8
scalingrpn = x,6,+

;paramname = AFL4byte
;paramid = 0xFF793D
;isfloat = 1
;scalingrpn = x,100,*

;paramname = AFC4byte
;paramid = 0xFF764C
;isfloat = 1
;scalingrpn = x,100,*,100,-

;paramname = MRP4byte
;paramid = 0xFF6A78
;isfloat = 1
;scalingrpn = x,0.01933677,*

paramname = Knock_Sum
paramid = 0xFF7FEC
databits = 8
scalingrpn = x


conditionrpn = Engine_Speed(rpm),0,>
action = start

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

Output file from above logcfg file:

Code: Select all

sample   time   Engine_Speed(rpm)   AFR       CL/OL    Knock_Sum
0        1.390812   10756.5          19.2937   24     168
1        1.690812   10756.5          19.2937   24     168
6        1.940812   10756.5          19.2937   24     168
11       2.190812   10756.5          19.2937   24     168


Here is another logcfg file that works:

Code: Select all

type = ssmcan

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 = 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 = Engine_Speed(rpm),0,>
action = start

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

And here is the output, which is pretty much correct. I think learning and correction are swapped though. The weird part is, the logcfg files are VERY similar, but yield different results. For instance, RPM and AFR are correct below, but they are called out the same as the above file. What gives?

Code: Select all

sample   time   A/F_Correction_#1(%)   A/F_Learning_#1(%)   Engine_Speed(rpm)   Manifold_Relative_Pressure(psi)   A/F_Sensor_#1(AFR)
0   4.330606          0         4.6875   198.5   -0.580392   14.7
1   4.380606           0         4.6875   198.5   -0.580392   14.7
2   4.430606           0         4.6875   198.5   -0.580392   14.7
3   4.480606           0         4.6875   213.25   -0.72549   14.7


[CasopoliS]

So, to summarize my post above... the readings seem to change based on the other parameters that are also being logged. I can get speed and AFR correct, but as soon as I add other parameters they become incorrect. Hope this helps with the development.

EDIT: After some testing I see that adding Knock Sum to the file will screw up the other values alone. So maybe it has something to do with logging ECU-specific parameters that are screwing up the logs???? Anyone else seeing the same thing? I can log "standard" parameters, but parameters that have a different looking address based on the ECU number seem to screw up the log.

[mdedwar]

So, to summarize my post above... the readings seem to change based on the other parameters that are also being logged. I can get speed and AFR correct, but as soon as I add other parameters they become incorrect. Hope this helps with the development.

EDIT: After some testing I see that adding Knock Sum to the file will screw up the other values alone. So maybe it has something to do with logging ECU-specific parameters that are screwing up the logs???? Anyone else seeing the same thing? I can log "standard" parameters, but parameters that have a different looking address based on the ECU number seem to screw up the log.

you have the wrong type set.

set type=ssmk for ram params to work

[CasopoliS]

Awesome, thanks. I did not realize that.

Now my Tactrix won't respond when plugging it in. The leds just slowly fade in and out of colors rather than the green and red lights flashing. Not sure why. Car is running and its plugged in to the OBD port, and not plugged into USB.

[Tephra]

Colby - I think I found a bug.

time cannot go higher than MAXINT - ie 4290 ish seconds.

Fix that and that should hopefully fix LONG trip recordings

In fact I am not even sure how "time" is meant to work, this morning (after leaving the car OFF for 16 hour) my time started at 2000ish seconds.

The ignition was off, but the car was NOT locked (I had the keys in the car) maybe the car detected the keys (Evo FastKey here) and kept the car awake?!?!?

[freakin]

colby, are you able to detail the limitations such as characters in strings, and string length etc please.

[sql_dev]

Thanks, it worked. By the way, how does this type change affect the frequency of updates? It seems slower now, but I have not done a comparison yet.

Hi Colby,
I just tried again and I still have the same issue. Please see my cfg file below. My car is 2009 WRX. I verified I have the latest OP2 firmware version 1.10.2702.

You have the type wrong. You need to use type=ssmk if you want to use ram params.

[CasopoliS]

Love this tool!

This is my logcfg file and it works great on my 08 LGT. I am using this to do CL logging.

Code: Select all

type=ssmk

paramname = Coolant
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 = RPM
paramid = 0x00000E
databits = 16
scalingrpn = x,4,/

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

paramname = CL/OL_Fueling*(status)
paramid = 0xFFA44D
databits = 8
scalingrpn = x,6,+

paramname = Engine_Load_(2-byte)**(g/rev)
paramid = 0xFF7044
databits = 16
scalingrpn = x,.00006103516,*

paramname = Manifold_Relative_Sea_Level_Pressure_(2-byte)
paramid = 0xFF7052
databits = 16
scalingrpn = x,760,-,0.01933677,*

paramname = Knock_Sum*(count)
paramid = 0xFF7FEC
databits = 8
scalingrpn = x

conditionrpn = Coolant,76,>
action = start

conditionrpn = RPM,0,==
action = stop

[CasopoliS]

Colby - I think I found a bug.

time cannot go higher than MAXINT - ie 4290 ish seconds.

Fix that and that should hopefully fix LONG trip recordings

In fact I am not even sure how "time" is meant to work, this morning (after leaving the car OFF for 16 hour) my time started at 2000ish seconds.

The ignition was off, but the car was NOT locked (I had the keys in the car) maybe the car detected the keys (Evo FastKey here) and kept the car awake?!?!?

Has anyone else confirmed this? I plan to do some long CL driving so a fix for this would be great.