I'll look into this, but will I need to know any code or anything?

It sounds as though a few people have this working, but not working very well.

no mode23 for the CT9A, so all that would be needed is the logcfg.txt and correct format on the SD card, and the BETA ECU flash.

Am I missing anything?

 

I do have this working in my car, and it works very well.

All you need is:

1) OpenPort 2.0 with sufficient firmware (included in Ecuflash 1.43.3150beta)
2) microSD card inserted into OP2.0
3) logcfg.txt file with correct requests (you can see examples in the file presented in this topic) placed in the root of the microSD card
4) if you want to log AFRs this way - WBO2 wired directly in the ECU (check MrFred's how-to here - https://www.evolutionm.net/forums/ec...ial-cable.html)

That's it - OP2.0 will start logging to the separate file all the parameters for which there are requests in the logcfg.txt file each time you connect it to the car.

Last half year I run the car with 88580714 in it (thanks Tephra for awesome developments) and logging works perfectly, with the stock ROM 88840016 it was working fine as well.

 

Awesome. I'll give this a try if I can get my laptop back this weekend. I would ultimately like to see a write up for this for the CT9A guys.

 

Actually my post above constitutes well over 70% of such write up. And yes, it's that easy.

 

I just noticed you were in Europe. I wonder how all of this will translate over to the USDM 88590015 rom? Does anyone forsee this being an issue?

 

Sorry to bring this thread back from the dead, but I must be doing something wrong.
I'm using ecuflash V1.43.3252, I've placed the logcfg.txt file in the root directory of the micro SD card, but it doesn't log.
If a trigger is not specified shouldn't it log constantly?
I've attached my logcfg...what am I missing?

 

I have a problem trying to get the program to work with my computer. I am using a Macbook Pro. Anyone think they can give me any help on how to get it working properly?

 

I've attached aa copy of my logcfg.txt file for anyone to look @.
I've defined quite a few things copying them from evoscan.
Most are commented out but can be used.
I am logging a UEGO WB through the ECU so that part wouldn't work for everyone.
I also have an omni 4 bar installed and am logging boost.
This is on a 2003 EVO 8 with a 94170715 tephra7 rom.
Hope it helps some people.

 

Much appreciated timv because my next question would be how to set up the trigger...thanks man

 

No problem.
If no triggers are defined, it will start logging as soon as the car is turned on.
In the subaru world, you could define the rear defogger switch to turn on/off logging.
Not sure if that can be read through the ECU on evos to do the same. Was a nice feature for doing WOT logs.

 

Not quite sure if that's possible either, but I tried using the TPS as the trigger:

conditionrpn = TPS,80,>
action = start
conditionrpn = TPS,80,<
action = stop

But no logging...does the code look right to you. (Start logging over 80%TPS and stop under 80%TPS)

 

From what I know, that looks like it should work.
Make sure you have TPS being logged also, not commented out or it will not be able to find it.
You can check the logcfg.out file on your memory card and read the errors.
It is actually pretty helpful once you decipher it.
The last line or so should point you in the direction of why it isn't logging.
Good luck.

 

Hmmm, still no luck using the TPS as the trigger. Anyone successfully set this up care to share their .txt

 

If you post the logcfg.out file, we can look @ it and see if it points to something.
Post your logcfg.txt also, could help.

 

Tried a couple different settings but still no luck triggering with TPS...I attached the files for you guys to take a look, maybe I'm missing something.