Tactrix 2.0/Romraider users

There is a new update to the Romraider ECU/Logger Definitions

http://www.romraider.com/forum/topic1642.html <-Logger Defs
http://www.romraider.com/forum/topic360.html <-ECU Defs

And if you are an XPT user with a login you can access his ECU defs here:
http://www.osecuroms.org/viewtopic.php?f=70&t=581 <-XPT ECU defs

Also, SD card logging is working! It's very limited at this time but I'm sure more info will be released. Gave it a try and it works great so far. It seems to have a very fast sample rate.
http://forums.openecu.org/viewtopic.php?f=57&t=4319

Cheers!

Thanks Luke!!! Yeah Braden from XPT is the shit. I am running a revised pro tune on both of my STi's from XPT.

Thanks for the update Luke. I am going to have to take a run with you and check it out. I was hoping this feature was going to be making an appearance soon.

<New update to the sd card logger 10/10/09

I'm excited for this. ECUFlash is what I use to tune the 3g eclipse

Me too! It's looking very promising. Has logging for Mitsubishi as well.

Here's a log from the SD card logger. Working pretty good so far. Still has some more work to be done.
My knock advance isn't reading properly or maybe I have the wrong parameter. IDC isn't being calculated properly either lol.

Are you running Windows 7?

Negative my laptop is running XP.

Yeah Luke it looks good!! Yeah your knock advance doesn't really line up with your timing. I bet it is the wrong parameter. We should go log your car I will work your laptop and we can try some different parameters to iron out your logs.

heeb101 wrote:

Yeah Luke it looks good!! Yeah your knock advance doesn't really line up with your timing. I bet it is the wrong parameter. We should go log your car I will work your laptop and we can try some different parameters to iron out your logs.

Cboles just released another update. There was an issue with floating parameters (extended parameters like knock advance) I double checked and I do have the right memory address being read. It's just not being displayed properly. It would give me values like 1.14E-17 which is totally wrong. Basically it's a bug.

When this is all worked out it's sounding like Cboles is gonna release a new version of ECUFlash that has a GUI to do all this for you. So instead of editing a text file to get your parameters setup and logging you just point and click to what car you have, what parameters you want, how you want the logs to start and stop etc, etc and it will make a config file for you.

Gonna give the recent update a try tomorrow.

The anticipation is killing me Luke, did you end up trying it out yet?

DoodieHead wrote:

The anticipation is killing me Luke, did you end up trying it out yet?

Yep gave it a try on the way to work this morning. My parameters are reading correctly now. I have to enable a couple others and see how they're working as well.
So far so good!

Sweet just tried a couple other parameters that haven't been reading correctly and they are now working properly. Very nice. Now this is actually becoming useful to the point where I can make minor tweaks based off of the logs.

A GUI has been released for configuring your OP2.0 sd card logger. Good stuff!

http://forums.openecu.org/viewtopic.php?f=57&t=4396

Reviving from the dead!

Looks like it's been polished up quite a bit, I haven't checked on the openport logging for some time. But now, they have CAN support so the logging data is very fast and allows for very high resolution. I just took some logs and a 4th gear pull from 2000rpm to redline took up about 7 pages of scrolling down in an excel spreadsheet, when before I only got about 1.

So now I can see every little nuance. Very cool, makes for finding little inconsistencies much easier than before. If you have an 08+ subaru/Mitsu with a CAN bus, logging with this method should be possible. And the coolest part is, I can plug an LC1 digital signal right into the openport once I get it installed. So wideband data can be included. Only thing is I had to patch my rom with a beta version of EcuFlash to allow the CAN logging. That step was actually very easy.

To read up go here:
http://forums.openecu.org/viewforum.php?f=57&sid=ff6a1957b60ccdd69dc4ea02497ee164

Just to give you guys and idea on how fast this is, here is one page of a log. The highlighted column is RPM, if you compare it to the log I have posted above, you can see it's definitely much faster.

Holy cow! That went from 7 samples in 1000 rpms to 7 samples in 50 rpms! That's insanely faster