Openport Stand-Alone Logging Beta

[cboles]

this is done through reading RAM, so basically it is already supported if you know what addresses to read...

Merchgod over at Romraider has created a freeware called Learning View. Program allows him to see temporary and stored dtc codes using OP. Here's the thread, maybe you can implement something similar to the standalone logging. http://www.romraider.com/forum/topic2772.html

[poohbear]

Well I got the stand alone to work... you guys are correct though going k-line seems very slow im seeing large gaps in the logging... I may switch over to CAN but im a little sketched out about patching my 09... I wanna see a few others go at it first... Would be great if we could get some time stamps.... An implemented battery in a new tactirx would be awesome... I would almost buy another cable for that option

What param are you guys using for engine load. I used relative load and im getting some off the chart numbers im used to 3.07 at the most and now im seeing 33+ ... In romraider there was an engine load caluclated... whats the correct param for stand alone to get calculated engine load?

[cboles]

don't be afraid to flash that puppy... i have been using this patch on my own car for a while...

Well I got the stand alone to work... you guys are correct though going k-line seems very slow im seeing large gaps in the logging... I may switch over to CAN but im a little sketched out about patching my 09... I wanna see a few others go at it first... Would be great if we could get some time stamps.... An implemented battery in a new tactirx would be awesome... I would almost buy another cable for that option

What param are you guys using for engine load. I used relative load and im getting some off the chart numbers im used to 3.07 at the most and now im seeing 33+ ... In romraider there was an engine load caluclated... whats the correct param for stand alone to get calculated engine load?

[poohbear]

Is yours an 09 though? I guess im thinking the patch likley to react different on different maps or ecu's? If I change patch it will i still be able to use learning view? any word on what param for propper calculated engine load? or do i have to write a script to calculate it out in the txt file?

don't be afraid to flash that puppy... i have been using this patch on my own car for a while...

Well I got the stand alone to work... you guys are correct though going k-line seems very slow im seeing large gaps in the logging... I may switch over to CAN but im a little sketched out about patching my 09... I wanna see a few others go at it first... Would be great if we could get some time stamps.... An implemented battery in a new tactirx would be awesome... I would almost buy another cable for that option

What param are you guys using for engine load. I used relative load and im getting some off the chart numbers im used to 3.07 at the most and now im seeing 33+ ... In romraider there was an engine load caluclated... whats the correct param for stand alone to get calculated engine load?

[cboles]

that patcher is not some dumb code that just overwrites bytes at a fixed addresses. it finds the specific function in your rom (which has to match exactly) and changes it to the new code i wrote. it doesn't even show up as an option unless everything is matching up 100% and it knows it can do it. there have been zero problems with this. the patch has nothing to do with maps.

all parameters are converted from internal ECU representations to human readable numbers using "scalings" with any sort of logger. you can just let the OP2 do the conversion for you. read up in this thread and look at some sample logcfg.txt files to learn how scalingrpn can do this.

Is yours an 09 though? I guess im thinking the patch likley to react different on different maps or ecu's? If I change patch it will i still be able to use learning view? any word on what param for propper calculated engine load? or do i have to write a script to calculate it out in the txt file?

don't be afraid to flash that puppy... i have been using this patch on my own car for a while...

Well I got the stand alone to work... you guys are correct though going k-line seems very slow im seeing large gaps in the logging... I may switch over to CAN but im a little sketched out about patching my 09... I wanna see a few others go at it first... Would be great if we could get some time stamps.... An implemented battery in a new tactirx would be awesome... I would almost buy another cable for that option

What param are you guys using for engine load. I used relative load and im getting some off the chart numbers im used to 3.07 at the most and now im seeing 33+ ... In romraider there was an engine load caluclated... whats the correct param for stand alone to get calculated engine load?

[poohbear]

this may be a touchy question but why not have the logcfg.exe program have available params with scalingrpn already applied? or is this somthing for later down the line? Also with the patched rom to use CAN will I lose the option of checking with learningview?

EDIT > i see the scalinggrpn is already applied

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

But why is that engine load so different from what im used to seeing in romraider?

[mfb]

For engine load on the my 09 fxt, this is what I use for CAN:

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

I just use the log config creator made by freakin. Thread and download here http://forums.openecu.org/viewtopic.php?f=57&t=4396 It uses the definitions of Romraider for Logging. Sampling rate versus time is 40 per second. That's the number of cells I see on my csv when viewed in Excel.

[poohbear]

^ yeah thats what Iw as using to create my txt files also.. I wonder if im just using the wrong param then

[mfb]

How do we log innovate lc-1 using can?

[cboles]

How do we log innovate lc-1 using can?

The LC-1 doesn't use CAN. You log it by plugging the 2.5mm plug into the OP2, and then adding the inno logging channel to your logcfg.txt file. There is a sample for this in subaru k-line adc lc1.txt.

Code: Select all

;----------------inno----------------
type=inno
; log from an innovate MTS bus via the 3/32" jack
; multiple LC-1 and other MTS devices (e.g. TC-4) are supported
;
; each MTS parameter has a special parameter ID:
;
; paramid   parameter
; 0x0101    LC-1 #1 AFR
; 0x0102    LC-1 #1 lambda
; 0x0201    LC-1 #2 AFR
; 0x0202    LC-1 #2 lambda
; 0x0301    LC-1 #3 AFR
; 0x0302    LC-1 #4 lambda
;           (etc)
;
; 0x0001    aux #1 data (e.g. TC-4 #1 channel 1)
; 0x0002    aux #2 data (e.g. TC-4 #1 channel 2)
; 0x0003    aux #3 data (e.g. TC-4 #1 channel 3)
; 0x0004    aux #4 data (e.g. TC-4 #1 channel 4)
; 0x0005    aux #5 data (e.g. TC-4 #2 channel 1)
;           (etc)

; the LC-1 parameters are already scaled correctly and require no scalingrpn setting
; however, the LC-1 is known to lose its stored AFR multiplier, so we recommend calculating
; AFR from lambda like this

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

; since the MTS bus does not describe the contents of the aux channels, you need to know what they are
; and how to scale them. in this example we assume you have a TC-4 connected and you want to view the
; thermocouple readings in celsius, two of which are in the EGT mode, two in CHT mode

;paramname = mytc4.egt1
;paramid = 0x0001
;scalingrpn = x,1.06842619,*

;paramname = mytc4.egt2
;paramid = 0x0002
;scalingrpn = x,1.06842619,*

;paramname = mytc4.cht1
;paramid = 0x0003
;scalingrpn = x,0.293255131,*

;paramname = mytc4.cht2
;paramid = 0x0004
;scalingrpn = x,0.293255131,*

in the above i have un-commented the lc-1 parameter so you should get a parameter called mylc1.afr with your AFR value in your logs

[mfb]

So I just add this to my logcfg file, just right before the trigger? Example,

Code: Select all

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

The additional lc1 command I added is correct? If you were to group them (slow sampling), how will you do it with the current Logcfg I have?

[cboles]

no - you need to have all of your ssmcan param stuff together, then afterwards declare an new channel with

Code: Select all

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


the type = inno is essential to let the parser know you are talking about a new channel, not ssmcan anymore. likewise, you can define any ssmcan parameters after you declare type = inno...

So I just add this to my logcfg file, just right before the trigger? Example,

Code: Select all

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

The additional lc1 command I added is correct? If you were to group them (slow sampling), how will you do it with the current Logcfg I have?

[mdedwar]

Hi Colby,
Is there any chance of supporting longer param names as well as supporting spaces etc?

eg: Primary Open Loop Map Enrichment (2-byte)** instead of having to do somthing like this Primary_Open_Loop_Map_Enrich

This would save me having to modify the tuning spreadsheets that I use over on the RomRaider site.

Cheers,
Matt.

[mfb]

Hi Colby,

Where do I put the trigger, just at the end or one for each channel?

Trigger I use is :

Code: Select all

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

conditionrpn = defogger_sw,1,==
action = start

conditionrpn = defogger_sw,0,==
action = stop

[Ceddy]

Colby,

MUT2 logging breaks when you have over around 38 items.

The name in the trigger section gets messed up.

GOOD

Code: Select all

trigger action: start condition: AC_sw,0.000000,==
trigger action: stop condition: AC_sw,1.000000,==

--- storage info ---
log channels: 2
log parameters: 38
log stringlist: 513 chars
log floatlist: 31 floats
logging interval will be 250000us

BAD

Code: Select all

trigger action: start condition: x,0.000000,==
trigger action: stop condition: x,1.000000,==

--- storage info ---
log channels: 2
log parameters: 39
log stringlist: 526 chars
log floatlist: 31 floats
logging interval will be 250000us

AC_sw gets changed to: x, +, or other symbols.