Here is a another version to try.
I have made a couple of improvements to the "OEM" reflash process to make it more robust if there are any missing responses on the CAN bus (I'm making the ECU very busy trying to run as fast as possible, which can lead to it dropping commands sometimes).
This version also has firmware that supports logging, using UDS mode 0x23 requests which read from RAM directly. There is a sample of how to do this at
C:\Program Files (x86)\OpenECU\EcuFlash\samples\logging\subaru brz uds.txt
in your installation. You will need to use the OP2 once in EcuFlash (you can even just go to the Help | Licensing page) to get the OP2 firmware update to happen first. The you can copy subaru brz uds.txt as logcfg.txt on your microSD card and you should be good to go. You will probably want to add some trigger conditions - you can look at some of the other examples to see how that is done if you don't know already.
The good news is that this form of logging is pretty fast (> 1000 32-bit parameters / second), so I might not add a custom mod to do any special new logging method. The only downside of this method is that you need to know all of the RAM addresses of the parameters in order to use it - there are no common SSM-style PIDs here. I have automated ways of finding all of the common parameters, so if we run into any new ROMs, this shouldn't be much of a problem anyways.
One important thing to note is that these mode 0x23 requests allow you to read large blocks of memory at once, so the OP2 tries to take advantage of this by sorting your parameters by address and figuring out when it is quicker to request many parameters at once (when their addresses are close enough together). This is also means that sometimes logging additional parameters comes at virtually no speed expense if their addresses are right next to the other parameters. If you look at my sample file, you will see that may RAM parameters are in fact right next to each other, which is good news.
Unless there are some problems with this beta, this will probably be the last version before I switch everyone over to using a Tactrix flashing kernel instead of the OEM flashing method. This will make the flashing considerably faster as it won't be rewriting the entire code/data calibration area with each flash.
Let us know if you are having any problems with this.
http://www.tactrix.com/downloads/ecu...ta_1444018.exe
Colby