New Ecoboost Owner, general acceleration questions.

ajpturbo said:
Of course the dealer is going to say you need a new processor....I would never bother a dealer for a problem after a bad reflash...that type of problem is way over their heads.

The exact strategy is not the same as the exact file that was loaded to the car..the data could be the same.maybe I'm not explaining it well or you refuse to understand it......if I give u a can of Pepsi and u want another I give u another can...they are the same drink and formula but it wasn't the exact same can....not saying it will make an appreciable difference but they aren't the same..

It's too bad sct doesn't have the time to defend themselves on these forums...they could give good insight

Sct recovers ecu's all the time..I would've called them before a trip to the dealer

I am not certain if you skipped over some of the previous response, but it looks that way. If you look at what was typed, we stated the customer sent in the processor to the manufacturer of his old device and they verified the processor was bricked. so this was not dealer greed, this was, in fact, a bricked controller.

and you are 100% incorrect on the strategy code. whether GM, Ford, or Chrysler, the main file is exactly the Same. Ford uses strategy, and SW ID to verify the file. Chrysler uses cal ID and their version of strategy, and GM uses multiple segment ID's to tell you what a file is. All of the vehicle specific info is located in a different area of the processor which does not get, or need to get programmed. Nor is it programmed by the dealership when updating.

Every SHO on the planet built with the same code has the same file in it from ford for the calibration. That is why the dealer types in the SW ID and strategy to download the file from ford rather than a VIN.

This is NOT a debatable piece of info. Normally we aren't so blunt to say so, but you are completely incorrect on your understanding of how these are handled.
 
Sorry I can't type that much at work..yes I did miss some...but a failed component that is broken is broken and you are assuming that the other device caused it to fail.....

I've seen ecu's fail during a reflash fords ids software and the vcm ii which is the oem level equipment used at dealer ships...I have one and u can download any any all of the strategies that come from ford...my gdm1 was updated to gdm2 and there was 1 insignificant change to the tune...the stategies that are downloaded from ford are the exact tunes  that get loaded to the car but the 100% same tune would be the one I download from my ecu....does it make a difference, probably not...just saying
 
Good info!  Is there any physical damage that causes this "bricking"?  Or is it simply that the PCM software does not ride on a kernel that manages updates?  Such as the HAL that made Windows NT so stable.  So there is no provision for "rollbacks" in the event of an incomplete operation such as caused by a power outage?
 
SHOdded said:
Good info!  Is there any physical damage that causes this "bricking"?  Or is it simply that the PCM software does not ride on a kernel that manages updates?  Such as the HAL that made Windows NT so stable.  So there is no provision for "rollbacks" in the event of an incomplete operation such as caused by a power outage?

There are many possibilities for "why" a pcm was bricked, but it could be a corrupt file, invalid checksum, or not using the proper flash process for the processor. Of course power losses are a potential issue as well, but there are all kinds of sources for failure.
 
Back
Top