View Single Post
Old 10-25-2013, 08:25 AM   #24
endrswrd
Member
 
Join Date: Jul 2013
Drives: 2013 LTD BRZ
Location: Dayton Ohio
Posts: 49
Thanks: 0
Thanked 16 Times in 12 Posts
Mentioned: 1 Post(s)
Quote:
Originally Posted by Td-d View Post
Hey endrswrd, I figured you'd land up in this thread eventually

Patience, Kimosabi.
I am very excited Td-d, and I have some local guys who cant wait either!

One thing I do need to do if I can get my hands on a car is work with merp to add some boost control stuff. The only major thing I really need to make these maps better for FI is getting an EBCS(and all the associated TD and boost cut) to work with the stock ecu. Gotta look for a sensor we can hijack!

Should be really easy considering the ecu is in the engine bay lol.

Quote:
Originally Posted by moto-mike View Post
Yes and no. While you can scale stock stuff, with the EcuTek RaceROM custom mapping we can bypass the stock logic. This is huge. All of the FI programming we do on the BRZ involves this so we can base it off of MAP or do boost based fueling/timing. With this you can up the boost, put in boost failsafe, change fueling relative to boost, and make ECU based boost control. Load based is great for NA, but sucks with big boost (or even low boost on high compression) since you're so close to the edge.
Same thing can be done in OS, it just is going to take some time. I am a software developer by day, and actually get to do some DoD based RE work for my company as well. I am well aware the stock rom isnt the best setup, but adding boost logic from other subarus will be straightforward once I have a car to work with. I know for sure merp would help as I am sure alot of guys would love to go completely OS for their BRZ tuning needs. Realistically, the boost cut is easy, its adding in an EBCS that will be more difficult. But there are cars who wont need this either (sc guys), and would just need emergency boost cut (doubtful for a SC but its nice to have).
endrswrd is offline   Reply With Quote