Software update 2018.4.5

[verygreen]

I'm guessing there's a few version for various vintage cars/hardware setups? i.e. 2018.4.1 and 2018.4.5 are the same release really, just different cars get different versions of the same thing. I have 2018.4.1 ec044c8 and have a 2015 P90D with AP1. I don't imagine a 2017 100D with AP2.X is going to get the same version as me.

all cars (S and X, any vintage) get 100% byte for byte identical firmware file, it's just the bits your car does not have would not be used.

 

[docdailey]

I'm guessing there's a few version for various vintage cars/hardware setups? i.e. 2018.4.1 and 2018.4.5 are the same release really, just different cars get different versions of the same thing. I have 2018.4.1 ec044c8 and have a 2015 P90D with AP1. I don't imagine a 2017 100D with AP2.X is going to get the same version as me.

I have a 2017 S100d and have 4.1

 

[thegruf]

DON'T PANIC!

indeed - but this is automotive - not a desktop
sigh

 

[apacheguy]

all cars (S and X, any vintage) get 100% byte for byte identical firmware file, it's just the bits your car does not have would not be used.

While that’s true for the CID, the APE firmware is a separate download so not all cars have these bytes.

 

[verygreen]

While that’s true for the CID, the APE firmware is a separate download so not all cars have these bytes.

True, but all the cars have the bits to download those bytes, so in my book it falls squarely into "does not use all of the bytes"

 

[sakimano]

I have a 2017 S100d and have 4.1

ec044c8?

 

[Scott_K]

My update failed too...unfortunately have to now can’t update until they send it again.

 

[docdailey]

ec044c8?

Yes

 

[docdailey]

 

[PatrickCH4313]

You have a short VIN number !

 

[PatrickCH4313]

My update failed too...unfortunately have to now can’t update until they send it again.

I have to wait too until they send it again.

 

[docdailey]

You have a short VIN number !

Must have gotten cut off

 

[Firewired]

I got it two days ago. Installed fine. Here are screenshots:

 

[Scott_K]

This is my first firmware update as a Tesla owner. Seems to be a relatively high number of us experiencing install failures (@PatrickCH4313 @kholy @BrainCandy @toolioiep @moonraker9 @Electric_Zen @S75D ...). Is this something that frequently happens, or is this just a bad release?

 

[scottf200]

This is my first firmware update as a Tesla owner. Seems to be a relatively high number of us experiencing install failures (@PatrickCH4313 @kholy @BrainCandy @toolioiep @moonraker9 @Electric_Zen @S75D ...). Is this something that frequently happens, or is this just a bad release?

I've been around a while and it sure seem unusual. They are generally much smoother.

 

[Firewired]

I have had a Tesla since 2014. The number on this thread sure seems higher. In the past I have only seen an occasional report of install failure.

 

[sakimano]

Yes

 

[Snowstorm]

Hey, at least a failed firmware update doesn't brick your car. Can't be said for BIOS updates on computers or graphics cards. I once had to de-solder a flash memory that held the video card firmware and swap it with a one with good firmware on it to get it to work again. Tesla have done a good job to ensure that a failed updated doesn't also corrupt the portion that allows you to try again.

 

[ChrML]

Hey, at least a failed firmware update doesn't brick your car. Can't be said for BIOS updates on computers or graphics cards. I once had to de-solder a flash memory that held the video card firmware and swap it with a one with good firmware on it to get it to work again. Tesla have done a good job to ensure that a failed updated doesn't also corrupt the portion that allows you to try again.

I would be very disappointed if they hadn't thought about that and had no recovery option during unexpected failures. Should be common sense for a programmer .

 

[chillaban]

Most of these update "failures" (as they are called by the car) don't appear to actually be failures, but rather a preflight check failing and the car refusing to apply the update as a result. That seems to be a layer of defense working as intended.

It seems like some cars have an identity crisis about what door sensors they have. I would guess a running part change and a snafu in terms of which cars are marked to have the old vs new sensor config?