2017.28.4cf44833 (spoiler: nothing new in release notes)

[RobIII]

I just got 2017.28.4cf44833. Screenshots here. Added it to ev-fw.com but doesn't show up there (yet). I guess it needs confirmation or something. Also see this reddit post (from "EDIT2" onwards). Bit disappointed it's not the auto-wipers or something

 

[chillaban]

And the version numbers get even more interesting.

 

[Duke-U]

Got it too, minor fixes. Drove it around the block but nothing very obvious yet. Boy it would help if they gave release notes, even if the liability issues were left out.

 

[boaterva]

Here we go, an even weirder number on the release side: eight digits now...

The 17.30.xxx one is the firmware reported to be in use on the cars at the reveal event, so could be Model 3 specific, as noted.

And, on the numbering, I guess this proves we're actually on the git numbering permanently, as permanently as a trend of two can set.

 

[mblakele]

Hmm, we're well past week 28 of 2017. I'm beginning to think the week number is also a branch id of sorts.

If so maybe 28 represents the last feature work before something big lands. Maybe the TM3 code, which might give older vehicles a facelift. Or maybe something for AP.

 

[Patrick W]

Remember to add to the Tesla Firmware Upgrade Tracker:
Tesla Firmware Upgrade Tracker Web App

 

[WouterNLD]

Just installed it too. Haven't tried it though and the update on ev-fw.com did not go through either.

Could it be the uncorking? @Duke-U

 

[RobIII]

And the version numbers get even more interesting.

Why? Seems like a "normal" (since last update's switch) commit hash (which was 17.28.c528869)?

 

[RobIII]

Remember to add to the Tesla Firmware Upgrade Tracker:
Tesla Firmware Upgrade Tracker Web App

Already did

Added it to ev-fw.com but doesn't show up there (yet).

The 17.30.xxx one is the firmware reported to be in use on the cars at the reveal event, so could be Model 3 specific, as noted.

2017.30 37ca7cf

 

[escheffers]

Ah couldn't find a post about this version yet, so I just created one my self. Haven’t been able to test it yet. Will do so tomorrow.
Hopefully it will hit the brakes earlier if there is a stopped car before me.

 

[RobIII]

I can also tell that it's at least less than 540MB. Been capturing traffic stats from my car and the entire capture file is 540MB but includes several days worth of data. Trying to figure out the (rough) estimate now.

 

[BlueRocket]

And the version numbers get even more interesting.

Hexadecimal?

 

[BlueRocket]

Great... Maybe one of these updates will put me at parity with 17.17.4

 

[boaterva]

Why? Seems like a "normal" (since last update's switch) commit hash (which was 17.28.c528869)?

Well, perhaps 'normal'. You would think the hash would be a constant length, no? Or that the 'c' was a prefix? If not, the change in length is a bit weird. In either case, we need more data.

And we have again/still (since we have the 17/2017.30 case) the weirdness of sometimes it shows up as the year, and sometimes the 'short 17 form.

Also, it has been noted that 17.28.c528859 is really 17.28.27 with a patch always applied or some bug fix added to get the c... version. So, something else could be going on here. @verygreen has looked internally and seen both version numbers on his car at the same time (base software, and added developer patch, IIRC).

So, the 'new' numbering is still a strange combo of base 'old style' and git release hashcode, whatever.

 

[RobIII]

Hexadecimal?

They seem to be commit hashes.

Well, perhaps 'normal'. You would think the hash would be a constant length, no? Or that the 'c' was a prefix? If not, the change in length is a bit weird. In either case, we need more data.

Ah, didn't notice the difference in length!

 

[boaterva]

They seem to be commit hashes.

Seriously, shouldn't they be the same length in all cases? Someone (on reddit? I disremember) said it was a Git source code ID string. I believe the patch/developer ID mentioned above may have had the same string for an ID on it. Meaning it's the internal ID for the release? Again, we need more data.

 

[calisnow]

Great... Maybe one of these updates will put me at parity with 17.17.4

lol did you never even get updated to 17.17.4???

 

[RobIII]

Seriously, shouldn't they be the same length in all cases?

Yep, agree. Missed that (see my edit).

 

[BlueRocket]

lol did you never even get updated to 17.17.4???

Just liked 17.17.4 better than current 17.28.c... I would settle for auto wipers and speed - dependent audio volume!

 

[RobIII]

Actually, there seems to be a space in the number...

2017.28.4 cf44833

Could be interpreted as 2017.28.4 (Hash cf44833) maybe? I can't find an image of c528869 to see if there's a space in there maybe too.