OpenFlash Headers in 2017 &a Tune -- success & no tune yet

[imnotsureaboutbrz]

have anyone dyno'd thier results on the 2017 car's yet?

[Mr. Kurtz]

I'd be really excited to see someone's Dyno result on an unmodified 2017 with an Openflash tune.


Sent from my iPhone using Tapatalk

[invaliduser]

I'd be really excited to see an official (non beta) openflash tune for the 2017.

Sent from my Pixel XL using Tapatalk

[Mr. Kurtz]

That too


Sent from my iPhone using Tapatalk

[imnotsureaboutbrz]

As soon as I'm out of my breakin period I'm gonna go get a baseline synopsis run done. Maybe if a official 2017 tune is available I can do a before and after during the one session.

[Tysoncrosby21]

I'm glad I got my tablet free, I'd be pissed if I spent 500 dollars on a tuning tablet for a car that's been out six months and no word from the company about 2017 tunes.

Sure they have "beta" tunes. But where's an actual stable release tune.

[StraightOuttaCanadaEh]

Is there a tune for MY17 in the works yet?

[Carbinebbq]

Originally Posted by StraightOuttaCanadaEh

Is there a tune for MY17 in the works yet?

Beta yes. Haven't seen an official OTS tune. I'm running Stage 2 on my 2017. AT however.

Sent from my SAMSUNG-SM-G930A using Tapatalk

[Joetheegyptian]

What am I risking with the beta tune? I'm no mechanic but I feel like beta software shouldn't be controlling an engine.

[Shady195]

Originally Posted by Joetheegyptian

What am I risking with the beta tune? I'm no mechanic but I feel like beta software shouldn't be controlling an engine.

The same thing you risk by flashing your car in general. Bricking your ECU and voiding your warranty.

If I had to guess from the actual tune standpoint its safe, but I'm sure there are some differences with the definitions that may make logging/other features a bit trickier.

[steve99]

Originally Posted by Joetheegyptian

What am I risking with the beta tune? I'm no mechanic but I feel like beta software shouldn't be controlling an engine.

Originally Posted by Shady195

The same thing you risk by flashing your car in general. Bricking your ECU and voiding your warranty.

If I had to guess from the actual tune standpoint its safe, but I'm sure there are some differences with the definitions that may make logging/other features a bit trickier.

When the oft guys talk beta tune its not the flash process thats beta , so theirs no additional risk of bricking ecu. Its just the tune has been release to a controlled number of people for road testing on different car to see no unforseen issues show up. The original tune would have been developed on a single car on a dyno and their just testing it works on the street on multiple cars in different temperatures on different brands of fuel etc

With oft you can return the ecu to a 100% original state by flashing back stock tune to car thats storred in oft. With say ecutek thirs always adifference even if you flash to stock due to the embedded ecutek licience, This cannot be removed with the standard ecutek software, so the CVN or checksum value number is different from stock if the dealer looks for it. Wheras with oft or tactrix the cvn will match stock

[JonRZ]

I'm pretty sure regardless of tune company and ecutek vs oft, if the dealership really investigated, the modified dates on these files would have been updated even if returning to the original file and thus there would always be a record if you 'messed with' your ecu.

But perhaps I'm wrong in how Subaru accesses these files or what information is captured.

[steve99]

Originally Posted by JonRZ

I'm pretty sure regardless of tune company and ecutek vs oft, if the dealership really investigated, the modified dates on these files would have been updated even if returning to the original file and thus there would always be a record if you 'messed with' your ecu.

But perhaps I'm wrong in how Subaru accesses these files or what information is captured.

ecu has no date reference and its time reference starts from a reset or reflash


It does store a few counters like number of starts since a reset/reflash
time and time since DTC reset or time a DTC has been active and distance since active.


These counter/timers are cleared on a reflash but also when you reset ECU, ie remove a battery terminal. So not rearly usable as definitive proof of ecu reflash as it could have just been reset ie power removed as this clears the DTC and resets counters.


Techstream used by Toyota techs does not have any reference to flash counters. Have asked Subaru techs and it appears the Subaru SSM tool doesn't either.


It would certainly be possible for the ecu or another module in car to store flash counts though, or that Higer level service engineers have tools to access more info in ecu or other modules.


What the normal tech/dealer does have access to is the CVN or checksum value number. This is a checksum on the ECU ROM/TUNE area. So if its not 100% stock they can detect this by comparing the CVN of whts in ECU with a list of CVN for stock ROMS.


This is how thay can detect ECUTEK even if you flash a sotck rom with ecutek the CVN is not stock due to the embedded ecutek licience info in rom.


Where as with OFT/Tactrix a stock rom flashed back is 100% stock. So these systems are certainly less detectable than Ecutek.

[JonRZ]

Hmm interesting. I know with my Speed3, things are a little more noticible. Thanks for the info! I'm awaiting a 2017 MT (non-beta) map as I always like a tune