Quote:
Originally Posted by Dynotronics1
only if you read line by line in the code
It has always been, and always will be, that someone will be able to see, on some level, that the code has changed. Question is, can it be done at the dealer, or even the factory level, and is it worth the cost and time to do so?
Short answer is, no.
|
Having used the commercial-grade OEM tools (Caldesk, INCA, etc) and certain in-house tools I can say that I can EASILY see if anyone has changed something from the production calibration.
First, there can be a software build version into the code that has been flashed onto the ECU. So for example, if the manufacturer changes the spark table from a 10x10 to 16x16, a new software version will be released. That's what moves around a bunch of the memory addresses so that some reverse engineering would need to be re-done on newer model years. Then there are checksum addresses that can be matched to the library of production calibrations. No match = tampering. Now maybe ECUtek basically leaves those in such a state that it hides the change. I'm not an expert on that.
All that's academic and has very little bearing on ECUtek vs BRZedit. But I can tell you right now that Toyota and Subaru have a handful of guys outside of Japan who have access to the tools and information needed to determine tampering. I can't speak for every dealer tool though. From my experience with using dealer tools, they are designed to be idiot proof. You plug into the customer car and it will just update it to whatever the library in the tool specifies. Those libraries can change all the time because the dealer tools require regular updates from the internet. I presume Techstream is like that.
The way it works in at the OEM's is that the actual software code (Matlab Simulink models etc) is kept under very tight security. By that I mean, very few people know exactly how everything is calculated, and often they are not the ones doing the tuning hands on. The tools needed to access the ECU, the memory address files (ASAP2 .A2L format usually), and the actual ROM binary have a little wider availability. It's typically on a need-to-know basis though.