RomRaider

Hello, I am new to tuning the subaru platform and trying to figure this out. quick background - was a service engineering operations instructor for a domestic manufacturer for a few years, but got bored and went back to teching at a dealer currently(I'm stuck). I taught engine performance theory+op, diag+testing, electronics, electrical, blah blah blah at a factory credential level. By no means am I a professional tuner, but I do understand what I am trying to accomplish with the car, I just need help getting there on the subaru platform. I've tuned a procharged e46 bmw, and I have a good bit of experience tuning the evo x platform and loved that process. I am hoping someone can help me maybe with "translation" from the evo x process.(at this point I've spent hours researching the forum and find myself running in circles looking for answers). On evo x I had tephramod and rax fast datalogging, with the parameters on evoscan that I needed. For subaru, I currently have a merpmod patched AE5R100V(2015 USDM sti), and romraider logger. Right now I have the 370v logger definition, but my list of pids available don't seem to include ones I see in the posts throughout the forum. I keep circling around and see a list of "extended parameters" like boost error being included for example, but none of the stuff with the asterisk(I've read on the one post that there is an asterisk to show that the parameter is an extended parameter) - basically I am trying to figure out what pids are used for stuff like TargetAFR/Target Boost/wastegate duty cycle correction like I had on evo x, so that I can monitor my actual vs. desired and make adjustments needed. For the subaru I am looking to be able to monitor/record a target afr to plot the % diff between actual and desired within the maf scale table or SD VE table for OL adjustment, a wastegate duty cycle correction or boost error to plot within a histogram that matches the target boost table, a knock counter to plot within a histogram that matches the timing table, probably more, but this is the most important to me right now. Can anybody point me in the right direction? thank you. sorry for the obvious lack of knowledge. I tried lol, like I said I just feel like I keep running in circles on the forum.

some formatting will certainly help more people be able to understand your request just for future posts.

For this one, if you have the logger defs and the ECU defs (as in you can open the rom in romraider editor as well) then you should have any extended parameters appear when you connect to the car for logging.

If the parameters you're after aren't there for logging then you do also have the option to switch roms and do a full flash to a more supported rom type.

-Thank you for your response!
-Sorry for the format this was my first forum post ever, I definitely see what you mean after I read it back lol.
-The way I read/interpret your response to my concern is this: If I have the correct logger defs and the ECU defs(confirmed), but the extended parameters do not appear when I connect to the car for logging(confirmed)- then I have the option to switch roms to a more supported rom type as long as it is a VA sti rom - meaning I can just try flashing a rom for a MY16 or MY17(for example) to the car and verify if the extended parameters I am looking for are now present when I connect to the car for logging. (So just because my oem read file was an AE5R100V does not mean I NEED to use an AE5R100V moving forward.)
-Am I correct with my interpretation?

Thank you!

I did some digging and came up with MY16 being the safest option for me as what I found said that MY15 and MY16 are pretty much the same, but I guess there are some differences from 15/16 once you get into 17+. Now gotta track down an MY16 rom to test. thanks!

Worked! 2016 rom it is. Thank you!

yes that's it exactly, and also make sure you can open the rom in romraider editor as the ECU defs need to be working for the logger to see all the parameters as well