Firmware 7.1

[jason.a]

Thanks for the data point. Yes, 2.10.71 is the previous "full release" that they did for 7.1. If they follow their usual pattern you should either get 2.12.126 fairly soon (or we'll see a newer build that hopefully addresses the charging issue). BTW: do you have dual chargers?

Yes, I have dual chargers as well. I normally charge off a HPWC on a 100A circuit (usually at 60A but I know it works all the way up to 80A), so if I get .126 or a later version I'll be able to check pretty quickly if the bug still exists.

 

[S100D]

Yes, I have dual chargers. So that could be a possible reason I haven't been updated yet.

I got the .126 update on 02/28 and updated it as soon as I noticed the upgrade was available. I have dual chargers and did not know there was a charging issues until I read this thread. I waited 2 minutes after the charging level got up to half the set charging amps. I ran the same test with the amps set and the levels below:

Set amps Max Charging amps
--------- ---------------------
44 amps - 22 amps
50 amps - 25 amps
60 amps - 30 amps
64 amps - 64 amps
80 amps - 80 amps

When I set the amps 64 and 80 amp, it increased to 32 and 40 amps and then after about 1 to 2 minutes, it continued to increase to 64 and 80 amps.
There is definitely an issue.

I also noticed for the first time that after I stop the charge and before I unplugged the charging cable that I got a message that said that I had Charging Cable Fault. I have never seen this before. If I remember correctly it only happened when I had the charge level set at 64 and 80 amps.

 

[cinergi]

I have the bug on my recent-model as well. I charge at 80 so didn't notice but sure enough if I set it between 41 and 72 I'd see the bug. There's also quite a bit more clicking coming from the chargers ... (it's faint and you'd have to know what's normal ahead of time to notice it)

 

[Andyw2100]

I got the .126 update on 02/28 and updated it as soon as I noticed the upgrade was available. I have dual chargers and did not know there was a charging issues until I read this thread. I waited 2 minutes after the charging level got up to half the set charging amps. I ran the same test with the amps set and the levels below:

Set amps Max Charging amps
--------- ---------------------
44 amps - 22 amps
50 amps - 25 amps
60 amps - 30 amps
64 amps - 64 amps
80 amps - 80 amps

When I set the amps 64 and 80 amp, it increased to 32 and 40 amps and then after about 1 to 2 minutes, it continued to increase to 64 and 80 amps.
There is definitely an issue.

This is different from where Mike had indicated the threshold was. He had indicated the threshold was at 72, so we should test at 64 to see if the problem would manifest itself. I did that, and it did not, and I concluded I did not have the issue. But based on your results above, I should test at 60 amps (or lower) to see what happens.

 

[BertL]

I got the .126 update on 02/28 and updated it as soon as I noticed the upgrade was available. I have dual chargers and did not know there was a charging issues until I read this thread. I waited 2 minutes after the charging level got up to half the set charging amps. I ran the same test with the amps set and the levels below:

Set amps Max Charging amps
--------- ---------------------
44 amps - 22 amps
50 amps - 25 amps
60 amps - 30 amps
64 amps - 64 amps
80 amps - 80 amps

When I set the amps 64 and 80 amp, it increased to 32 and 40 amps and then after about 1 to 2 minutes, it continued to increase to 64 and 80 amps.
There is definitely an issue.

I also noticed for the first time that after I stop the charge and before I unplugged the charging cable that I got a message that said that I had Charging Cable Fault. I have never seen this before. If I remember correctly it only happened when I had the charge level set at 64 and 80 amps.

Interesting. So, I literally used the stopwatch on my Apple Watch, and sure enough, if I start a manual charge, the display indicates amps increasing and stabilizing between 39-40A -- then, if I wait long enough (just over 1 min, or in a 2nd test closer to 2 min as you also saw), the ramp up continues to my normal 79A. Again, I'm running a 100A circuit, with HPWC set to 80A and dual-chargers on my S90D, with 17" set to 80A for my home charging. Unlike you, I do not receive an unusual "Charging Cable Fault" message after I stopped the manual charging -- all appears normal that way on my MS. I have not tried the other amperage combinations you did, but for my selfish purposes, can live with the new delay the latest firmware has introduced before enabling my 2nd charger. It's not that bad it matters to me now while we await a fix (or some comment) from Tesla.

Thx!

 

[msnow]

Yeah, I'm unclear if the blue arrows is the result of a map update or firmware update. I have the blue arrows and the latest firmware, but no map update, yet.

I sent an email to Tesla asking them to verify if I have the updated maps even though I didn't receive a notification. I just received a response from their Technical Support Specialist that said:

"I have been able to confirm your vehicle does have the current navigation update in your vehicle. Unfortunately there is no “date” for the update, just a version number, but your vehicle is listed as having downloaded and installed this update."

He would not provide the version number or screenshot so I guess unless someone comes up with a creative method to verify this I'll just have to trust them.

 

[Patrick W]

I sent an email to Tesla asking them to verify if I have the updated maps even though I didn't receive a notification. I just received a response from their Technical Support Specialist that said:

"I have been able to confirm your vehicle does have the current navigation update in your vehicle. Unfortunately there is no “date” for the update, just a version number, but your vehicle is listed as having downloaded and installed this update."

He would not provide the version number or screenshot so I guess unless someone comes up with a creative method to verify this I'll just have to trust them.

I did receive the map update and after the update I saw that the credit line at the lower right side of the map display read: "Map data © 2016 Google"

How does that compare to what your display shows?

 

[Andyw2100]

I sent an email to Tesla asking them to verify if I have the updated maps even though I didn't receive a notification. I just received a response from their Technical Support Specialist that said:

"I have been able to confirm your vehicle does have the current navigation update in your vehicle. Unfortunately there is no “date” for the update, just a version number, but your vehicle is listed as having downloaded and installed this update."

He would not provide the version number or screenshot so I guess unless someone comes up with a creative method to verify this I'll just have to trust them.

Did you try looking for the Stan Musial Memorial Bridge, as I suggested in the post referenced below, and as you said you were going to try?

Firmware 7.1 - Page 169

 

[msnow]

Did you try looking for the Stan Musial Memorial Bridge, as I suggested in the post referenced below, and as you said you were going to try?

Firmware 7.1 - Page 169

Yes, post 1690 upthread. Long story short, it shows up on the 17" Google map display but I couldn't find a way to verify the updated Navigon map data by having it display on the IC. It was a good idea though.

 

[msnow]

I did receive the map update and after the update I saw that the credit line at the lower right side of the map display read: "Map data [emoji767] 2016 Google"

How does that compare to what your display shows?

Mine also shows the same thing but that is referencing Google's map data such as roads and traffic not the Navigon map data we/Tesla use for turn by turn directions. I took a screen shot of Google maps traffic from my iPhone to illustrate.

 

[Andyw2100]

Yes, post 1690 upthread. Long story short, it shows up on the 17" Google map display but I couldn't find a way to verify the updated Navigon map data by having it display on the IC. It was a good idea though.

Ahh, I had seen your original post where you said you'd try it, but then never went back, so missed the edit where you reported what happened. Oh well.

I guess driving from California to St. Louis to check wouldn't exactly be convenient.

 

[msnow]

Ahh, I had seen your original post where you said you'd try it, but then never went back, so missed the edit where you reported what happened. Oh well.

I guess driving from California to St. Louis to check wouldn't exactly be convenient.

Lol, almost 2000 miles! Maybe I could catch a Cards/Dodgers game with FlasherZ while I'm there.

 

[Urgo]

Lol I get it, new release notes. Chill Tesla
https://www.teslamotors.com/sites/default/files/Model_S_release_notes_7_1_1_us_cn.pdf
https://www.teslamotors.com/sites/default/files/7.1.1._Release_Notes_ROW.pdf
https://www.teslamotors.com/sites/default/files/7.1.1._Release_Notes_ROW_1.pdf
https://www.teslamotors.com/sites/default/files/7.1.1._Release_Notes_ROW_0.pdf
https://www.teslamotors.com/sites/default/files/7.1.1._Release_Notes_ROW_13.pdf
https://www.teslamotors.com/sites/default/files/7.1.1._Release_Notes_ROW_12.pdf
https://www.teslamotors.com/sites/default/files/7.1.1._Release_Notes_ROW_22.pdf
... and so on lol

from the my tesla page

 

[Andyw2100]

I got the .126 update on 02/28 and updated it as soon as I noticed the upgrade was available. I have dual chargers and did not know there was a charging issues until I read this thread. I waited 2 minutes after the charging level got up to half the set charging amps. I ran the same test with the amps set and the levels below:

Set amps Max Charging amps
--------- ---------------------
44 amps - 22 amps
50 amps - 25 amps
60 amps - 30 amps
64 amps - 64 amps
80 amps - 80 amps

When I set the amps 64 and 80 amp, it increased to 32 and 40 amps and then after about 1 to 2 minutes, it continued to increase to 64 and 80 amps.
There is definitely an issue.

This is different from where Mike had indicated the threshold was. He had indicated the threshold was at 72, so we should test at 64 to see if the problem would manifest itself. I did that, and it did not, and I concluded I did not have the issue. But based on your results above, I should test at 60 amps (or lower) to see what happens.

So I retested tonight, setting the amps at 56 instead of 64, and it turns out I --DO--, in fact, have the bug. Anyone who concluded they do not, based on having thought the above/below threshold was 70 should check what happens at 60 amps or lower. Thanks to S85D for identifying that.

I'm now wondering if there really is anyone who has the update, who has dual chargers, who is not affected by this bug. I believe Cottonwood posted up thread that he was not, but I wonder if he either tested the same way I did, at too high a threshold, or if, since he charges at 56 amps, he may have just not noticed that he actually hasn't been charging at 56 amps. A third possibility is that in some other way Cottonwood failed to follow the protocol to generate the error. For example, if he only tried his normal, scheduled charging, and the error doesn't come into play unless you first disable scheduled charging, or something along those lines.

Cottonwood--If you wouldn't mind, when you have the chance would you consider unplugging, turning off scheduled charging, lowering your charging rate to, say 50, and then plugging in and seeing what happens? That goes for anyone else who believes they are unaffected as well.

It seems it would be useful to determine if this is a bug that affects 100% of dual charger Model Ss.

Thanks.

 

[neroden]

I wonder if part of the "70amp" barrier half-charge bug is a result of Programmer A (from before) having the dual-charger code out there and the ramp up split between the two chargers, and Programmer B made changes into the codebase b/c of the Model X and that is interfering with the dual-charger split logic somehow? Just a wild guess here, but I find it interesting that the X "better charger" goes up to 72 amp and this bug only affects use under that level but above 40; like if they were trying to tweak the logic around between standard 40 amp charging vs. single-charger 72 amp charging.

Almost certainly. Frankly, this demonstrates incompetence at QA in Tesla's programming department, which I have suspected from the get-go. They are *not* testing their software properly. There should be a testsuite to simulate every hardware configuration ever sold. Current best practice when programming is that any time a new capability is added, a test is added to the suite to check for regressions, and in some shops it's not even allowed to add code without adding tests.

 

[dirkhh]

Yes, post 1690 upthread. Long story short, it shows up on the 17" Google map display but I couldn't find a way to verify the updated Navigon map data by having it display on the IC. It was a good idea though.

IIRC you can scroll through the full directions used for navigation when showing the Nav app on the 17". So what happens if you ask Navigon to navigate to an address just on the other side of the bridge from where you are? Yeah, it's 2000 miles, lots of stops and stuff... but you should be able to see if the directions have you cross the bridge or go another way, right?

 

[S100D]

Interesting. So, I literally used the stopwatch on my Apple Watch, and sure enough, if I start a manual charge, the display indicates amps increasing and stabilizing between 39-40A -- then, if I wait long enough (just over 1 min, or in a 2nd test closer to 2 min as you also saw), the ramp up continues to my normal 79A. Again, I'm running a 100A circuit, with HPWC set to 80A and dual-chargers on my S90D, with 17" set to 80A for my home charging. Unlike you, I do not receive an unusual "Charging Cable Fault" message after I stopped the manual charging -- all appears normal that way on my MS. I have not tried the other amperage combinations you did, but for my selfish purposes, can live with the new delay the latest firmware has introduced before enabling my 2nd charger. It's not that bad it matters to me now while we await a fix (or some comment) from Tesla.

Thx!

I called Tesla 24/7 support late yesterday and the support person told me that he had not heard of this issue. He said he was forwarding it to the Austin Service Center and they would call me in the next couple of days. I think it will take a software upgrade to resolve the issue and the SC will not be able to help.

 

[msnow]

IIRC you can scroll through the full directions used for navigation when showing the Nav app on the 17". So what happens if you ask Navigon to navigate to an address just on the other side of the bridge from where you are? Yeah, it's 2000 miles, lots of stops and stuff... but you should be able to see if the directions have you cross the bridge or go another way, right?

I thought it would let me step or scroll through the directions but after several scrolls it kept taking me back to the original starting location. I was connected to my home wifi too. Maybe someone else can try and see if they get better results.

 

[basf_audio]

I have the bug on my recent-model as well. I charge at 80 so didn't notice but sure enough if I set it between 41 and 72 I'd see the bug. There's also quite a bit more clicking coming from the chargers ... (it's faint and you'd have to know what's normal ahead of time to notice it)

I just tested this out as well - same issue. Set at 80 - ramps up to 80. Less than that - only the first charger gets used. Even if I adjust it while it's charging - it never engages the second charger until I stop and start the charging.

 

[Cottonwood]

Cottonwood--If you wouldn't mind, when you have the chance would you consider unplugging, turning off scheduled charging, lowering your charging rate to, say 50, and then plugging in and seeing what happens? That goes for anyone else who believes they are unaffected as well.

I don't use scheduled charging and my car charges fine (many uses) when set to 56 Amps. I will try setting to less than 50 Amps when I get a chance.

These results are on my Sig P85, SN:0037 running 2.12.126