Openport Stand-Alone Logging Beta

[cboles]

start and stop conditions apply to any type of logging. i could also make a "new file" action. take a look at the subaru samples - i just didn't bother copying those examples into the mitsu samples yet. you might consider using some sort of switch on your dash such as the defogger to trigger logging since i imagine there are also times when you are at WOT that you are just driving and don't want your file chopped up.

c

Hey Colby,

This new version seems to work pretty well

I tested the RPN stuff and priority.

If we can get your full layered priority working that would be awesome too

Also does the stop/start logging apply to mitsucan? I am interested in having a Point of Interest registered in the log file - the simplest way would be to simply restart the logging.

Normally I log TPS and any POI's I want marked I just hit WOT for a short while..

Cheers
D.

[Tephra]

Yeh at the moment I don't want or expect the logger to chop @ WOT... its just for marking the 1 or 2 rows of interest in the 10's of thousands!

[cboles]

Well I'm hoping that the logging GUI in EcuFlash will help with these types of things a lot - allowing you to search, highlight, and jump to areas that match some criterion, much like you do in a text editor today.

Yeh at the moment I don't want or expect the logger to chop @ WOT... its just for marking the 1 or 2 rows of interest in the 10's of thousands!

[Mart]

I am having problem with a RAM parameter I believe.

Car: 06 sti (4312594006)
Param: Engine Load (4-Byte)*

; Engine Load (4-Byte)
paramname = Engine_Load
paramid = 0xFF4F58
isfloat = 1 ; the raw data is a 32-bit floating point number (no need to set databits = 32)

<conversions>
<conversion units="g/rev" storagetype="float" expr="x" format="0.00" />
</conversions>

Everything I log is something like:

1.14E-19
1.09E-19
1.13E-19
1.10E-19
1.14E-19


Am I missing something?

thanx

[cboles]

I'll check it out tomorrow for you. Last time I checked it was working correctly

I am having problem with a RAM parameter I believe.

Car: 06 sti (4312594006)
Param: Engine Load (4-Byte)*

; Engine Load (4-Byte)
paramname = Engine_Load
paramid = 0xFF4F58
isfloat = 1 ; the raw data is a 32-bit floating point number (no need to set databits = 32)

<conversions>
<conversion units="g/rev" storagetype="float" expr="x" format="0.00" />
</conversions>

Everything I log is something like:

1.14E-19
1.09E-19
1.13E-19
1.10E-19
1.14E-19


Am I missing something?

thanx

[haproot]

Thank you Cboles for the hard work! I was curious. Would I be able to log Feedback knock correction and or Fine learning knock correction?

I found my ecuid in the logger.xml I'm thinking thats where some of you guys are getting your parameters.. So how would this info help me setup my logcfg.txt file to log knock correction?

Code: Select all

  <ecuparam id="E39" name="Feedback Knock Correction (4-byte)*" desc="Current feedback timing correction.">
<ecu id="6912783007">
     <address length="4">0xFF7F14</address>


Car is an 08 STi

[legaulois]

I have a problem on a STI 2008 EUDM, but it's generates more file .cvs .

I tested
paramname = map
paramid = 0xFF63FC
isfloat = 1
databits = 32
scale1 = 0.01933677
Or
paramname = iam
paramid = 0xFF2D34
isfloat=1
databits = 32
scale1 = 1

Code logcfg.txt

Code: Select all

type = ssmcan           

paramname = RPM           
paramid = 0x0E           
databits = 16           
scaletype = linear         
scale1 = 0.25

paramname=speed
paramid = 0x10
scale1 = 0.621371192

paramname = mrp
paramid = 0x24
scale1 = 0.145098
scale2 = -18.572549

paramname = map
paramid = 0xFF63FC
isfloat = 1
databits = 32
scale1 = 0.01933677

paramname = throttle
paramid = 0x15
scale1 = 0.3921569

paramname = timing
paramid = 0x11
scale1 = 0.5
scale2 = -64

paramname = defogger
paramid = 0x64
databits = 1
offsetbits = 6

trigparam = defogger
condition = eq   
value = 1
action = start

trigparam = defogger
condition = eq
value = 0
action = stop

Code logcfg.out

Code: Select all

channel type: ssmcan
protocol id: 6
baud: 500000

param name: RPM
param id: 0x0000000E
read width: 2 bytes
data width: 16 bits
data offset: 0 bits
float: 0
scale type: linear
scale1: 0.250000
scale2: 0.000000

param name: speed
param id: 0x00000010
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
scale type: linear
scale1: 0.621371
scale2: 0.000000

param name: mrp
param id: 0x00000024
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
scale type: linear
scale1: 0.145098
scale2: -18.572550

param name: map
param id: 0x00FF63FC
read width: 0 bytes
data width: 0 bits
data offset: 0 bits
float: 1
scale type: linear
scale1: 0.019337
scale2: 0.000000

param name: throttle
param id: 0x00000015
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
scale type: linear
scale1: 0.392157
scale2: 0.000000

param name: timing
param id: 0x00000011
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
scale type: linear
scale1: 0.500000
scale2: -64.000000

param name: defogger
param id: 0x00000064
read width: 1 bytes
data width: 1 bits
data offset: 6 bits
float: 0
scale type: linear
scale1: 1.000000
scale2: 0.000000

trigger action: start condition: defogger == 1.000000

trigger action: stop condition: defogger == 0.000000

result


but also, in this case not log
paramname = map
paramid = 0xFF6A10
databits = 16
scale1 = 0.01933677
Or
paramname = iam
paramid = 0xFF6A4F
databits = 8
scale1 = 0.0625
Or
paramname = load
paramid = 0x07
offsetbits = 6
scale1 = 0.3921569

Thank you

[Mart]

Are you using something like that for the ieee float conversion?

// Bit 31 Sign Bit
long n_sign = (value >> 31) & 0x1;

// Bits 30 - 23 Exponent Field
long n_exponent = (value >> 23) - 127;

// Bits 22 - 0 Significand

float n_coefficient = (float)(value & 0x7FFFFF);

n_coefficient = n_coefficient/0x800000 + 1;

return pow((float)-1,n_sign) * n_coefficient *(pow((float)2,n_exponent));

that did the trick for me with my SSM tool If I remember correctly.

Mart

I'll check it out tomorrow for you. Last time I checked it was working correctly

I am having problem with a RAM parameter I believe.

Car: 06 sti (4312594006)
Param: Engine Load (4-Byte)*

; Engine Load (4-Byte)
paramname = Engine_Load
paramid = 0xFF4F58
isfloat = 1 ; the raw data is a 32-bit floating point number (no need to set databits = 32)

<conversions>
<conversion units="g/rev" storagetype="float" expr="x" format="0.00" />
</conversions>

Everything I log is something like:

1.14E-19
1.09E-19
1.13E-19
1.10E-19
1.14E-19


Am I missing something?

thanx

[haproot]

Thank you Cboles for the hard work! I was curious. Would I be able to log Feedback knock correction and or Fine learning knock correction?

I found my ecuid in the logger.xml I'm thinking thats where some of you guys are getting your parameters.. So how would this info help me setup my logcfg.txt file to log knock correction?

Code: Select all

  <ecuparam id="E39" name="Feedback Knock Correction (4-byte)*" desc="Current feedback timing correction.">
<ecu id="6912783007">
     <address length="4">0xFF7F14</address>


Car is an 08 STi

On the commute to work I tried testing out logging with the latest release. Had it setup to start/stop with the defogger switch. And it didn't take any logs at all. It was working with the initial release so idk strange.

I tried this for feedback knock correction. but of course nothing logged at all. the logcfg.out file does show that all my parameters were setup.. it doesn't show any errors either.

Code: Select all

;Feedback Knock Correction (4-byte)
paramname = FBKC
paramid = 0xFF7F14
isfloat = 1


Here's my triggers area

Code: Select all

; if the condition evaluates to a non-zero value, that action is taken

;conditionrpn = RPM,0,>   
;action = start

;conditionrpn = RPM,0,==
;action = stop

; here is a second triggering example using the rear defogger switch
; uncomment it and comment out the sample above to use it

conditionrpn = defogger_sw,1,==
action = start

conditionrpn = defogger_sw,0,==
action = stop


[Mart]

Same here, start/stop with the defogger switch doesnt seem to work. The RPM condition does work for me.

Mart

Thank you Cboles for the hard work! I was curious. Would I be able to log Feedback knock correction and or Fine learning knock correction?

I found my ecuid in the logger.xml I'm thinking thats where some of you guys are getting your parameters.. So how would this info help me setup my logcfg.txt file to log knock correction?

Code: Select all

  <ecuparam id="E39" name="Feedback Knock Correction (4-byte)*" desc="Current feedback timing correction.">
<ecu id="6912783007">
     <address length="4">0xFF7F14</address>


Car is an 08 STi

On the commute to work I tried testing out logging with the latest release. Had it setup to start/stop with the defogger switch. And it didn't take any logs at all. It was working with the initial release so idk strange.

I tried this for feedback knock correction. but of course nothing logged at all. the logcfg.out file does show that all my parameters were setup.. it doesn't show any errors either.

Code: Select all

;Feedback Knock Correction (4-byte)
paramname = FBKC
paramid = 0xFF7F14
isfloat = 1


Here's my triggers area

Code: Select all

; if the condition evaluates to a non-zero value, that action is taken

;conditionrpn = RPM,0,>   
;action = start

;conditionrpn = RPM,0,==
;action = stop

; here is a second triggering example using the rear defogger switch
; uncomment it and comment out the sample above to use it

conditionrpn = defogger_sw,1,==
action = start

conditionrpn = defogger_sw,0,==
action = stop


[cboles]

The current version of the firmware no longer uses the "scale1" setting - it uses "scalingrpn" and RPN equations instead. i'm not sure why it is logging for you at all with these errors. what does your logcfg.out say?

I have a problem on a STI 2008 EUDM, but it's generates more file .cvs .

I tested
paramname = map
paramid = 0xFF63FC
isfloat = 1
databits = 32
scale1 = 0.01933677
Or
paramname = iam
paramid = 0xFF2D34
isfloat=1
databits = 32
scale1 = 1

Code logcfg.txt

Code: Select all

type = ssmcan           

paramname = RPM           
paramid = 0x0E           
databits = 16           
scaletype = linear         
scale1 = 0.25

paramname=speed
paramid = 0x10
scale1 = 0.621371192

paramname = mrp
paramid = 0x24
scale1 = 0.145098
scale2 = -18.572549

paramname = map
paramid = 0xFF63FC
isfloat = 1
databits = 32
scale1 = 0.01933677

paramname = throttle
paramid = 0x15
scale1 = 0.3921569

paramname = timing
paramid = 0x11
scale1 = 0.5
scale2 = -64

paramname = defogger
paramid = 0x64
databits = 1
offsetbits = 6

trigparam = defogger
condition = eq   
value = 1
action = start

trigparam = defogger
condition = eq
value = 0
action = stop

Code logcfg.out

Code: Select all

channel type: ssmcan
protocol id: 6
baud: 500000

param name: RPM
param id: 0x0000000E
read width: 2 bytes
data width: 16 bits
data offset: 0 bits
float: 0
scale type: linear
scale1: 0.250000
scale2: 0.000000

param name: speed
param id: 0x00000010
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
scale type: linear
scale1: 0.621371
scale2: 0.000000

param name: mrp
param id: 0x00000024
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
scale type: linear
scale1: 0.145098
scale2: -18.572550

param name: map
param id: 0x00FF63FC
read width: 0 bytes
data width: 0 bits
data offset: 0 bits
float: 1
scale type: linear
scale1: 0.019337
scale2: 0.000000

param name: throttle
param id: 0x00000015
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
scale type: linear
scale1: 0.392157
scale2: 0.000000

param name: timing
param id: 0x00000011
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
scale type: linear
scale1: 0.500000
scale2: -64.000000

param name: defogger
param id: 0x00000064
read width: 1 bytes
data width: 1 bits
data offset: 6 bits
float: 0
scale type: linear
scale1: 1.000000
scale2: 0.000000

trigger action: start condition: defogger == 1.000000

trigger action: stop condition: defogger == 0.000000

result


but also, in this case not log
paramname = map
paramid = 0xFF6A10
databits = 16
scale1 = 0.01933677
Or
paramname = iam
paramid = 0xFF6A4F
databits = 8
scale1 = 0.0625
Or
paramname = load
paramid = 0x07
offsetbits = 6
scale1 = 0.3921569

Thank you

[cboles]

I don't have to do any conversion - the OP2 uses IEEE 32-bit floats internally for logging, so I simply cast the 32-bit data as a float. As I said, it used to work, so I will have to look at what got broken...

Are you using something like that for the ieee float conversion?

// Bit 31 Sign Bit
long n_sign = (value >> 31) & 0x1;

// Bits 30 - 23 Exponent Field
long n_exponent = (value >> 23) - 127;

// Bits 22 - 0 Significand

float n_coefficient = (float)(value & 0x7FFFFF);

n_coefficient = n_coefficient/0x800000 + 1;

return pow((float)-1,n_sign) * n_coefficient *(pow((float)2,n_exponent));

that did the trick for me with my SSM tool If I remember correctly.

Mart

I'll check it out tomorrow for you. Last time I checked it was working correctly

I am having problem with a RAM parameter I believe.

Car: 06 sti (4312594006)
Param: Engine Load (4-Byte)*

; Engine Load (4-Byte)
paramname = Engine_Load
paramid = 0xFF4F58
isfloat = 1 ; the raw data is a 32-bit floating point number (no need to set databits = 32)

<conversions>
<conversion units="g/rev" storagetype="float" expr="x" format="0.00" />
</conversions>

Everything I log is something like:

1.14E-19
1.09E-19
1.13E-19
1.10E-19
1.14E-19


Am I missing something?

thanx

[cboles]

I'll go check that in my car too - I'm not sure how this got broken, or if it is. Are you doing CAN or K-line logging?

Same here, start/stop with the defogger switch doesnt seem to work. The RPM condition does work for me.

Mart

Thank you Cboles for the hard work! I was curious. Would I be able to log Feedback knock correction and or Fine learning knock correction?

I found my ecuid in the logger.xml I'm thinking thats where some of you guys are getting your parameters.. So how would this info help me setup my logcfg.txt file to log knock correction?

Code: Select all

  <ecuparam id="E39" name="Feedback Knock Correction (4-byte)*" desc="Current feedback timing correction.">
<ecu id="6912783007">
     <address length="4">0xFF7F14</address>


Car is an 08 STi

On the commute to work I tried testing out logging with the latest release. Had it setup to start/stop with the defogger switch. And it didn't take any logs at all. It was working with the initial release so idk strange.

I tried this for feedback knock correction. but of course nothing logged at all. the logcfg.out file does show that all my parameters were setup.. it doesn't show any errors either.

Code: Select all

;Feedback Knock Correction (4-byte)
paramname = FBKC
paramid = 0xFF7F14
isfloat = 1


Here's my triggers area

Code: Select all

; if the condition evaluates to a non-zero value, that action is taken

;conditionrpn = RPM,0,>   
;action = start

;conditionrpn = RPM,0,==
;action = stop

; here is a second triggering example using the rear defogger switch
; uncomment it and comment out the sample above to use it

conditionrpn = defogger_sw,1,==
action = start

conditionrpn = defogger_sw,0,==
action = stop


[Mart]

K-Line power baby!!

[quote="cboles"]I'll go check that in my car too - I'm not sure how this got broken, or if it is. Are you doing CAN or K-line logging?

[quote="Mart"]Same here, start/stop with the defogger switch doesnt seem to work. The RPM condition does work for me.

Mart

[Mart]

I will implement this week that Engine Load parameter with my custom SSM/Display (no tactrix cable) tool and double check the value I should expect.

I don't have to do any conversion - the OP2 uses IEEE 32-bit floats internally for logging, so I simply cast the 32-bit data as a float. As I said, it used to work, so I will have to look at what got broken...

[/quote]