Openport Stand-Alone Logging Beta

[legaulois]

I have these problems for STI 08 EUDM, I expect the new version.

Thank you

[cboles]

OK - there is a new version up now that should fix the SSM and float bugs. I'm still working on the SSM CAN ECU ROM patch. I'm adding some cool stuff that should also make the logging of multi-byte parameters (such as floats) more than twice as fast. These patches could also be added to K-line ROMS, where the speed improvement is more desperately needed.

[MattS00]

Today I noticed that coolant temp is not reporting correctly with the beta release, but it appears to be reporting correctly in evoscan. I have a 2000 Eclipse with a h8/539 ecu. The request id and scaling forumla is the same in the OP2.0 and evoscan. For some reason when trying the OP2.0 beta the data is inverted. I get higher numbers when the engine is colder.

[Mart]

Hi Colby,

problem solved with float for me. However, I noticed that paramater Engine Load (Relative) (SSM 0x07) always stay at 99.998 in my log on my 06 STI.
I can see the Engine Load ( Extended parameters ) g/rev moving around but the standard SSM parameter seem stuck. Is it normal?

Please more info about that ROM patch for multi-bytes parameters!!

thanx

Mart

OK - there is a new version up now that should fix the SSM and float bugs. I'm still working on the SSM CAN ECU ROM patch. I'm adding some cool stuff that should also make the logging of multi-byte parameters (such as floats) more than twice as fast. These patches could also be added to K-line ROMS, where the speed improvement is more desperately needed.

[haproot]

Hi Colby,

problem solved with float for me.

Same here, my values are now showing up properly for float/extended parameters. Engine Load (4-byte) and Knock Advance (4-byte) are showing the proper values so far. Thanks!

Looking forward to more updates. Great work Colby!

[cboles]

I'll check to see what is going on - I think load was one of the things I verified on my 08 STI.

With regards to the ROM patch, initially it is just for the 08 STI ROM, but it does the following:

* Allows access to RAM paramters (e.g. 0xFFxxxx)
* Allows multiple bytes to be read with a single address request to reduce the communications overhead.
e.g.:
0xF2xxxx would read two bytes at 0xFFFFxxxx
0xF4xxxx would read four bytes at 0xFFFFxxxx

Hi Colby,

problem solved with float for me. However, I noticed that paramater Engine Load (Relative) (SSM 0x07) always stay at 99.998 in my log on my 06 STI.
I can see the Engine Load ( Extended parameters ) g/rev moving around but the standard SSM parameter seem stuck. Is it normal?

Please more info about that ROM patch for multi-bytes parameters!!

thanx

Mart

[cboles]

Today I noticed that coolant temp is not reporting correctly with the beta release, but it appears to be reporting correctly in evoscan. I have a 2000 Eclipse with a h8/539 ecu. The request id and scaling forumla is the same in the OP2.0 and evoscan. For some reason when trying the OP2.0 beta the data is inverted. I get higher numbers when the engine is colder.

Is this something that has changed in the latest release, or has it always been the case?

[haproot]

Quick question. How would I log Accelerator Pedal Angle? Throttle seems to give the actual throttle plate angle. Here's what I found in the logger.xml.. actually it's all I could find. Also my IDC doesn't seem to be calculating properly. It's over 100 all the time. Thanks.

Code: Select all

<parameter id="P30" name="Accelerator Pedal Angle" desc="Accelerator pedal angle." ecubyteindex="11" ecubit="2">
                    <address>0x000029</address>
                    <conversions>
                        <conversion units="%" expr="x*100/255" format="0.00" />
                    </conversions>


[MattS00]

Today I noticed that coolant temp is not reporting correctly with the beta release, but it appears to be reporting correctly in evoscan. I have a 2000 Eclipse with a h8/539 ecu. The request id and scaling forumla is the same in the OP2.0 and evoscan. For some reason when trying the OP2.0 beta the data is inverted. I get higher numbers when the engine is colder.

Is this something that has changed in the latest release, or has it always been the case?

I don't know, this is the first time I logged coolant temp. The request id is 0X07 and the scaling is x,1.8,*,32,+ I have yet to update to the most current beta release.

[jarencibia]

Thanks for the betas Coby! This is very convenient for logging now.

Does anyone know how to log the extended parameter closed/open loop status for maf scaling? (this is for the 2004 subaru wrx 16 bit ecu)
I have the parameters below set up for logging in my logcfg file.....just need to log closed/open loop status



paramname = IAT
paramid = 0x12
scalingrpn = x,0.40,-
priority = 2

paramname = MAF
paramid = 0x13
databits = 16
scalingrpn = x,0.01,*

paramname=MAFv
paramid=0x01D
scalingrpn = x,0.02,*

paramname=AFC#1
paramid=0x009
scalingrpn = x,128,-,0.781,*

paramname=AFL#1
paramid=0x00A
scalingrpn = x,128,-,0.781,*

[cboles]

that would be:

Code: Select all

paramname=pedal_angle
paramid=0x29
scalingrpn=x,0.3921569,*

Quick question. How would I log Accelerator Pedal Angle? Throttle seems to give the actual throttle plate angle. Here's what I found in the logger.xml.. actually it's all I could find. Also my IDC doesn't seem to be calculating properly. It's over 100 all the time. Thanks.

Code: Select all

<parameter id="P30" name="Accelerator Pedal Angle" desc="Accelerator pedal angle." ecubyteindex="11" ecubit="2">
                    <address>0x000029</address>
                    <conversions>
                        <conversion units="%" expr="x*100/255" format="0.00" />
                    </conversions>


[haproot]

that would be:

Code: Select all

paramname=pedal_angle
paramid=0x29
scalingrpn=x,0.3921569,*

that works great. Thank you!

[dolphin]

I have upgraded my OP 2.0 firmware, as written in the first post, but no luck with logcfg.txt files. I have tried several configurations to triger logging start. My car is Evo VIII.
Could anybody suply working logcfg.txt or just begining of the code

P.S. Is this alright?

Code: Select all

type=mut2

paramname=RPM
paramid=0x21
scalingrpn=x,31.25,*

trigparam=RPM
condition=gt
value=1800
action=start

trigparam=RPM
condition=lt
value=7000
action=stop

[Tephra]

Colby,

Can you give me a quick howto on how to do something like:

when TPS > 80, then stop logging a certain item

Can it be done?

Cheers
David

[cboles]

There is no way to change what is logged on the fly, if that is what you are asking. You can only start and stop logging altogether. There is really a limited amount of space in the OP2 to code these types of things and still leave room for other protocol support and features.

Colby,

Can you give me a quick howto on how to do something like:

when TPS > 80, then stop logging a certain item

Can it be done?

Cheers
David