Openport Stand-Alone Logging Beta

[Tephra]

ok no worries.

could we add a very simple "don't log when tps > xyz" option? only available on priority <> 1 items obviously

[cboles]

The triggering has changed since what you must have last read. it should look like this now:

Code: Select all

type=mut2

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

conditionrpn=RPM,1800,>
action=start

conditionrpn=RPM,1800,<
action=stop

Also note in this example that I changed your intended logging conditions, because they didn't make sense and generally wouldn't log anything. This version starts logging above 1800 RPM and stops when you drop below 1800. Were you trying log a single pull (e.g. from 1800 to 7000)? I may have to add some new action states that cause the start and stop to retrigger properly for that. At present, stopping logging when above 7000 won't work very well because as soon as you drop below 7000 again, logging will resume because of the start condition. I need to add some memory (hysteresis) states so that once you have stopped above 7000, you need to go below 1800 to be able to start again.

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

[dolphin]

Were you trying log a single pull (e.g. from 1800 to 7000)? I may have to add some new action states that cause the start and stop to retrigger properly for that...

Yes! That was an idea I believe it's what the most tuners want, to log in a particular gear from ~2000rpm (before turbo begins boosting) to 7000rpm (or any other rpm near engine redline point).

Many thanks for the response, I'll try these parameters today and leave a feedback.

P.S. Is there any difference in baud rate, I have set in Ecuflash(15625 or 62500)?

[sql_dev]

Hi!

I just tried to log with my new OP2 and I have a problem. You see, I added several parameters by myself.

Every time I try to log with any of my new params, OP2 will create a lot of small log files, with one headers row and two log rows. All columns have some values, there are no empty ones. But: many-many files...

As soon as I remove my params, OP2 creates only one file, adds many data rows in it, as it should be. I tried to enable debug output, but I cannot see any messages/errors etc in it.

Adding this single new param makes OP2 do many files trick.

paramname = Engine_Load_1b
paramid = 0xFF6A06
scalingrpn = x,0.015625,*

Alex.

[MattS00]

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

What about having two or three different data groups, which can be set in similar way to the priority level? That way two sets of start/stop conditions could be set, and the thrid set would be logged all the time.

conditionrpn=RPM,1800,>
datagroup=2
action=start

conditionrpn=RPM,1800,<
datagroup=2
action=stop

condition=RPM,1800,<
datagroup=1
action=start

contitionrpn=RPM,1800>
datagroup=1
action=stop

[legaulois]

Hi!

I just tried to log with my new OP2 and I have a problem. You see, I added several parameters by myself.

Every time I try to log with any of my new params, OP2 will create a lot of small log files, with one headers row and two log rows. All columns have some values, there are no empty ones. But: many-many files...

As soon as I remove my params, OP2 creates only one file, adds many data rows in it, as it should be. I tried to enable debug output, but I cannot see any messages/errors etc in it.

Adding this single new param makes OP2 do many files trick.

paramname = Engine_Load_1b
paramid = 0xFF6A06
scalingrpn = x,0.015625,*

Alex.

bad firmware version, go to page 1, upload and follow the procedure. except for 08-09 STI will be on a next update

[sql_dev]

Hi!

I just tried to log with my new OP2 and I have a problem. You see, I added several parameters by myself.

Every time I try to log with any of my new params, OP2 will create a lot of small log files, with one headers row and two log rows. All columns have some values, there are no empty ones. But: many-many files...

As soon as I remove my params, OP2 creates only one file, adds many data rows in it, as it should be. I tried to enable debug output, but I cannot see any messages/errors etc in it.

Adding this single new param makes OP2 do many files trick.

paramname = Engine_Load_1b
paramid = 0xFF6A06
scalingrpn = x,0.015625,*

Alex.

bad firmware version, go to page 1, upload and follow the procedure. except for 08-09 STI will be on a next update

Hm, strange. I have done all that. Anyway, I just reinstalled everything, removed op20pt32.dll again.
How can I tell if the new firmware was applied? Is there any pop-up window or message?

[dolphin]

How can I tell if the new firmware was applied? Is there any pop-up window or message?

Just connect the cable to the car and press read or compare, in the ecuflash log will be written, what firmware you are using

[ladams00]

Colby, +1 for K-line speed patches (A2ZJB10J)

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.

[Mart]

with my custom SSM tool, as soon as I query an extended parameter, the query rate drop dramatically:( I want it too

Colby, +1 for K-line speed patches (A2ZJB10J)

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.

[sql_dev]

How can I tell if the new firmware was applied? Is there any pop-up window or message?

Just connect the cable to the car and press read or compare, in the ecuflash log will be written, what firmware you are using

So, it flashed something... But the multi-file issue is still here, not affected by the reflash at all. As soon as I add a parameter with long ID (like this: 0xFF6A00), OP2 starts making many-many files.

First EcuFlash log.
[14:22:32.218] reading firmware
[14:22:32.234] flash file version is 1.10.2702
[14:22:32.781] main code version : 1.10.2696
[14:22:33.296] waiting for bootloader (may be installing drivers)... press any key to abort
...
[14:22:46.781] ---erasing---
[14:22:46.890] erasing 1
[14:22:46.984] erasing 2
[14:22:47.093] erasing 3
[14:22:47.296] ---writing---
[14:22:47.359] writing 1k
...
[14:22:51.562] writing 60k
[14:22:51.562] flash complete!!!
[14:22:55.671] J2534 API Version: 04.04
[14:22:55.671] J2534 DLL Version: 0.50.2705 Oct 17 2009 16:35:03
[14:22:55.671] Device Firmware Version: 1.10.2702

Second EcuFlash log.
[14:24:52.140] J2534 API Version: 04.04
[14:24:52.140] J2534 DLL Version: 0.50.2705 Oct 17 2009 16:35:03
[14:24:52.140] Device Firmware Version: 1.10.2702
...

[dolphin]

The triggering has changed since what you must have last read. it should look like this now...

Sorry, but it wasn't working for me.
What baud rate OP 2.0 as a stand-alone can support? Like I mentioned before, I set it @ 62500 with Ecuflash. Second question would be, is it important which ROM file I am running on my ECU?

Please, let me know if you need further info, or I can help with logging testing in any way!

[altaic]

Hey Colby, how would I go about logging to microsd in sniffer mode (I have already installed an obd2 tap cable)? I'm taking my car to the dealer either tomorrow or the day after, and I want to log the session.

[Tephra]

Hi Colby,

Sometimes after a Flash the logger won't start automatically logging.

Any ideas?

Cheers
D.

[cboles]

Hi Colby,

Sometimes after a Flash the logger won't start automatically logging.

Any ideas?

Cheers
D.

what model car? maybe the ECU needs resetting post flash? once it won't start logging, what do you have to do to get it working again?