Openport Stand-Alone Logging Beta

[cboles]

are we evo owners able to do standlone 2 byte logging, just say if I wanted 2 byte load which is mut00 and mut01, would it be paramid=0x00,0x01 or paramid=0x0001, if both are wrong could anyone tell me how it's done if it can indeed log byte?

I didn't know there were multibyte MUT parameters, so the code for this wasn't quite working. I am testing a fix for this now. When I put the fixed version up, you will specify such a parameter like this:

Code: Select all

paramid=0x00
databits = 16


(when a parameter is more than one byte in length for mitsubishi / subaru / etc, the OP2 does the right thing and request the additional bytes, incrementing the paramid as it goes.)

[cboles]

are we evo owners able to do standlone 2 byte logging, just say if I wanted 2 byte load which is mut00 and mut01, would it be paramid=0x00,0x01 or paramid=0x0001, if both are wrong could anyone tell me how it's done if it can indeed log byte?

What Evos does this 2 byte parameter work with? I have implemented this in firmware now, but on the Evo 8 ECU I have (not connected to an engine), the 16-bit paramid=0x00 value I get is 8874, while the paramid=0x1C load value I get is 0, as I would expect.

[burnzy]

it works on evo 7-9, it's been implemented on all the tephra roms and can be added on stock roms. I'm a bit of a noob when it comes to coding and all that. All I know is that in evoscan request id is 00 requestid2 is 01, and eval is 0.3125*x
can you tell me what i'd need to put in to logcfg for that.

[cboles]

it works on evo 7-9, it's been implemented on all the tephra roms and can be added on stock roms. I'm a bit of a noob when it comes to coding and all that. All I know is that in evoscan request id is 00 requestid2 is 01, and eval is 0.3125*x
can you tell me what i'd need to put in to logcfg for that.

OK, so its a patched ROM thing... I have it implemented for the next firmware release. At that time, it will work like I have shown above. If you are really desperate, you could just log the paramids 0x00 and 0x01 as two separate parameters, then create a calculated parameter with a formula like

Code: Select all

type=mut2            
paramname=load00
paramid=0x00
paramname=load01
paramid=0x01

type = calc            
paramname = load
scalingrpn = load00,256,*,load01,+,0.3125,*


but it will be much more efficient to do it the other way in the next release.

[Ceddy]

Colby,

I couldn't find a list of commands for the logger config file.

Would it be possible to do Block logging.

Like MUT sends one request byte but receives 16 response bytes.
Response Byte 1 = TimingAdv, 2 = Load, 3 = TPS, etc.

MUT is relatively slow because it does 1 byte at a time comms.
The Block logging Mod is relatively easy to do on the Mitsus, and speeds things up a lot.
And an added bonus is all logged items are from the same time interval.

Code: Select all

type=mut2           
paramname=block
paramid=0x00
databits = 128

type = calc           
paramname = TimAdv
databits = 8
offsetbits = 120              // Select only top 8 bits
scalingrpn = x, 20, +


I know my code probably isn't correct.

But is something like this possible?

[ptharris]

Colby

When I turn off my car it seems to write to the SD card usual about 2-3kb file, I use the defogger switch for start stop, so as soon as I turn off the defog switch it stops logging but then logs again when I turn off car. Some times I also get multiple small files when logging to SD card instead of 1 constent file.

Any ideas?

Cheers Phil

[xPRimNT]

First off, huge thanks to colby! This has been great, even though I'm a bit of a "late adopter".

For my Evo X friends, tephra (thanks tephra!) found the addresses for "Cruise Control", so we can use that as a trigger.

(I've only tested on 526800xx, but should work for USDM MRs as well)

Log When Cruise Control is On

Code: Select all

paramname=CruiseLight
paramid= 0x8045C5
databits=1
offsetbits=5
isvisible=0

conditionrpn = CruiseLight,1,==
action = start

conditionrpn = CruiseLight,0,==
action = stop


Log When Cruise Control is Held Down

Code: Select all

paramname=CruiseMomentary
paramid= 0x80AB1E
databits=1
offsetbits=1
isvisible=0

conditionrpn = CruiseMomentary,1,==
action = start

conditionrpn = CruiseMomentary,0,==
action = stop


Also, just a reminder that the Lambda*14.7 would be a great addition. I don't have an LC-1 (in hindsight, I would have went with LC-1 if this had been out when I was shopping for widebands), but I've seen it get confused.


Thanks again.

[latool]

I’m try to using my openport2.0 for logging with SD Card, but after I install ecuflash 1.4227 here is the link,
“Here is how to install and use this beta:

* Download and install http://mail.tactrix.com/ecuflash/ecufla ... n_beta.exe
* Run EcuFlash and do a Help|Licensing operation. This will cause a firmware update to 1.10.xxxx, which has the logging support.
* If you go to the C:\Program Files\OpenECU\OpenPort 2.0\samples\logging directory you will see some example logging configuration files. These are text files you can open in a text editor and read.
* Copy the appropriate text file to your microSD card and rename it logcfg.txt. Make sure your text editor does not end up writing the file as logcfg.txt.txt.
* Disconnect the OP2 from your PC and plug it in to your car and go for a drive.
* Come back and connect your OP2 to the PC and examine the CSV files…”

But after I install, my openport wont work, sometimes the ecuflash detect it but it said the log window like this:


[20:15:30.987] EcuFlash Version 1.42.2720
[20:15:30.987] OS Version Windows XP
[20:15:30.987] Qt Version 4.5.2
[20:15:31.065] 57 memory models read.
[20:15:31.065] scanning for metadata models in C:/Documents and Settings/eshendra/My Documents/EDWIN/TACTRIX/rommetadata
[20:15:39.834] 643 ROM metadata models scanned.
[20:15:39.834] checksum module "subarudbw" loaded.
[20:15:39.834] checksum module "mitsucan" loaded.
[20:15:39.834] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[20:15:39.834] flashing tool "wrx02" loaded.
[20:15:39.834] flashing tool "wrx04" loaded.
[20:15:39.834] flashing tool "sti04" loaded.
[20:15:39.834] flashing tool "sti05" loaded.
[20:15:39.834] flashing tool "mitsukernel" loaded.
[20:15:39.834] flashing tool "mitsukernelocp" loaded.
[20:15:39.834] flashing tool "mitsubootloader" loaded.
[20:15:39.834] flashing tool "shbootmode" loaded.
[20:15:39.881] flashing tool "shaudmode" loaded.
[20:15:39.881] flashing tool "subarucan" loaded.
[20:15:39.881] flashing tool "mitsucan" loaded.
[20:15:47.009] J2534 error [unable to open device].
[20:15:47.009] unable to connect to vehicle interface.
[20:15:47.009] interface close
"

even if I try to install the previous version of ecuflash, please give me advice to make my OP2.0 works again, thanks

[paul_p1]

Does the Wideband logging function work with a LM-1, I can't seem to get mine to log.

[latool]

I’m try to using my openport2.0 for logging with SD Card, but after I install ecuflash 1.4227 here is the link,
“Here is how to install and use this beta:

* Download and install http://mail.tactrix.com/ecuflash/ecufla ... n_beta.exe
* Run EcuFlash and do a Help|Licensing operation. This will cause a firmware update to 1.10.xxxx, which has the logging support.
* If you go to the C:\Program Files\OpenECU\OpenPort 2.0\samples\logging directory you will see some example logging configuration files. These are text files you can open in a text editor and read.
* Copy the appropriate text file to your microSD card and rename it logcfg.txt. Make sure your text editor does not end up writing the file as logcfg.txt.txt.
* Disconnect the OP2 from your PC and plug it in to your car and go for a drive.
* Come back and connect your OP2 to the PC and examine the CSV files…”

But after I install, my openport wont work, sometimes the ecuflash detect it but it said the log window like this:


[20:15:30.987] EcuFlash Version 1.42.2720
[20:15:30.987] OS Version Windows XP
[20:15:30.987] Qt Version 4.5.2
[20:15:31.065] 57 memory models read.
[20:15:31.065] scanning for metadata models in C:/Documents and Settings/eshendra/My Documents/EDWIN/TACTRIX/rommetadata
[20:15:39.834] 643 ROM metadata models scanned.
[20:15:39.834] checksum module "subarudbw" loaded.
[20:15:39.834] checksum module "mitsucan" loaded.
[20:15:39.834] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[20:15:39.834] flashing tool "wrx02" loaded.
[20:15:39.834] flashing tool "wrx04" loaded.
[20:15:39.834] flashing tool "sti04" loaded.
[20:15:39.834] flashing tool "sti05" loaded.
[20:15:39.834] flashing tool "mitsukernel" loaded.
[20:15:39.834] flashing tool "mitsukernelocp" loaded.
[20:15:39.834] flashing tool "mitsubootloader" loaded.
[20:15:39.834] flashing tool "shbootmode" loaded.
[20:15:39.881] flashing tool "shaudmode" loaded.
[20:15:39.881] flashing tool "subarucan" loaded.
[20:15:39.881] flashing tool "mitsucan" loaded.
[20:15:47.009] J2534 error [unable to open device].
[20:15:47.009] unable to connect to vehicle interface.
[20:15:47.009] interface close
"
even if I try to install the previous version of ecuflash, please give me advice to make my OP2.0 works again, thanks

Problem fixed.. anyway how do i connect to lc-1 to OP2? just simply plug in the serial out of lc-1 to OP2 3/32 hole using male-2-male jack? thanks..

[cboles]

Where can I find details about this mod?

Colby,

I couldn't find a list of commands for the logger config file.

Would it be possible to do Block logging.

Like MUT sends one request byte but receives 16 response bytes.
Response Byte 1 = TimingAdv, 2 = Load, 3 = TPS, etc.

MUT is relatively slow because it does 1 byte at a time comms.
The Block logging Mod is relatively easy to do on the Mitsus, and speeds things up a lot.
And an added bonus is all logged items are from the same time interval.

Code: Select all

type=mut2           
paramname=block
paramid=0x00
databits = 128

type = calc           
paramname = TimAdv
databits = 8
offsetbits = 120              // Select only top 8 bits
scalingrpn = x, 20, +


I know my code probably isn't correct.

But is something like this possible?

[cboles]

yep!

Problem fixed.. anyway how do i connect to lc-1 to OP2? just simply plug in the serial out of lc-1 to OP2 3/32 hole using male-2-male jack? thanks..

[Tephra]

the block logging isn't really a mod.

mode23 (readbymemoryaddress) allows you to retrieve upto 255 bytes of data.

if you have a few parameters all near each other you could request 1 large block and then cut it up when the ECU returns it to you.

you would save on the overhead of multiple calls back and forth...

[cboles]

I have posted a new version at the top of this thread. Take a look, read the release info carefully, and check it out!

Colby

[Tephra]

nice.

everything is working pretty well.

although I did find today that a log stopped half way through and a new file/log was created. (not near any maxint boundaries or anything)

bit weird??!?