Firmware 7.1

[LetsGoFast]

I thought I was unaffected by this bug, but when I set the target to 60amps, I only charge at 30amps. At 80 amps, it works as expected (although it takes much longer to ramp up than it used to).

 

[Cottonwood]

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

I tried 48 Amps and that works fine, also. My time to go from the start of the half rate hover to starting the ramp towards full charge current is 20-25 second.

 

[Andyw2100]

I tried 48 Amps and that works fine, also. My time to go from the start of the half rate hover to starting the ramp towards full charge current is 20-25 second.

Just to be 100% clear, Cottonwood, you did unplug and then change the charging amps, right? (If you've been charging OK, adjusting down works fine.)

I'm only being so specific because assuming you did, you may be the only report so far of a dual charger car not affected by the bug.

 

[ccharleb]

Not sure if this is because of the maps update or .126 because I haven't received the maps update yet but do have .126 and my Nav IC looks like this:

Got 126 yesterday. No map update because I can't connect to Wifi at home (poor signal).
Line is orange.... so the blue line vs orange line might be related to the Navigon Map update.

 

[NOLA_Mike]

Just to be 100% clear, Cottonwood, you did unplug and then change the charging amps, right? (If you've been charging OK, adjusting down works fine.)

I'm only being so specific because assuming you did, you may be the only report so far of a dual charger car not affected by the bug.

We found the configuration that Tesla tested out the software on before sending it out!

Maybe this is Tesla's way of phasing out the dual chargers...

 

[brec]

Re the dual chargers issue with 2.12.126:

2016-02-27, 04:30 PM:

Same here. When I talked to Tesla they said they knew about the problem and were working on it.

2016-03-02, 07:49 AM:

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.

...In case more evidence of a substantial internal communication problem at Tesla, already mentioned upthread, is needed.

 

[dirkhh]

...In case more evidence of a substantial internal communication problem at Tesla, already mentioned upthread, is needed.

No, I think most of us are painfully aware just how utterly disconnected and dysfunctional they are...

 

[msnow]

No, I think most of us are painfully aware just how utterly disconnected and dysfunctional they are...

It's worse than even a few months ago. The customer facing people are nice and polite and everything but they are usually either at the wrong level, unknowledgeable, or not empowered to address the problem. It used to be different and there was a sense of problem ownership. Something changed and I don't know why. I hope this is a short term problem.

 

[NOLA_Mike]

No, I think most of us are painfully aware just how utterly disconnected and dysfunctional they are...

I think the ultimate evidence in this particular case is the fact that this update continued to roll out days after the bug reports started being sent in.

 

[msnow]

Got 126 yesterday. No map update because I can't connect to Wifi at home (poor signal).
Line is orange.... so the blue line vs orange line might be related to the Navigon Map update.

Thanks, that does narrow it down. The question I have is unless the SvC installed it for me (unbeknownst to me) how come I didn't get the notification.

 

[green1]

I hope this is a short term problem.

If by short term, you mean until a real competitor appears and forces Tesla to actually take the customer experience seriously... then yeah... short term...

 

[Berty1970]

Hi,

I didn't see it yet but wanted to let you know that I received an update yesterday and now have Summons!!! So, Summons is now in Canada. Haven't tried it yet.

Regards,

Bertrand

 

[cgiGuy]

I didn't see it yet but wanted to let you know that I received an update yesterday and now have Summons!!! So, Summons is now in Canada

You were ordered to testify in court? :wink:

 

[Cottonwood]

Just to be 100% clear, Cottonwood, you did unplug and then change the charging amps, right? (If you've been charging OK, adjusting down works fine.)

I'm only being so specific because assuming you did, you may be the only report so far of a dual charger car not affected by the bug.

Yes, I unplugged and plugged back in with each change. I have not had any issues charging at any level with my early, dual-charger P85, SN:0037

 

[msnow]

If by short term, you mean until a real competitor appears and forces Tesla to actually take the customer experience seriously... then yeah... short term...

I was hoping for a different kind of short term...like a realization that it's starting to affect the brand and change direction quickly.

 

[Bill D]

... you may be the only report so far of a dual charger car not affected by the bug.

FYI - I have two Teslas on 7.1 (2.12.126) with dual chargers. My P85 (Feb 2014 28xxx) does not have this charging bug, but my P90D has this charging bug.

I set both to 50A "not scheduled". My P85 went to 25A for 20 seconds then went up to 50A. My P90D went to 25A, I waited 15 min and it never went above 25A.

 

[Andyw2100]

Yes, I unplugged and plugged back in with each change. I have not had any issues charging at any level with my early, dual-charger P85, SN:0037

FYI - I have two Teslas on 7.1 (2.12.126) with dual chargers. My P85 (Feb 2014 28xxx) does not have this charging bug, but my P90D has this charging bug.

I set both to 50A "not scheduled". My P85 went to 25A for 20 seconds then went up to 50A. My P90D went to 25A, I waited 15 min and it never went above 25A.

Very interesting.

Thanks, guys, for helping narrow down, at least a bit, what's going on.

I expect Tesla will have an update out within another day or two that resolves this all anyway, but it's interesting (at least to me) trying to figure out why not all cars are affected.

 

[drsaab]

My nov 2014 autopilot S85 has the charging bug.

 

[Cyberax]

I expect Tesla will have an update out within another day or two that resolves this all anyway, but it's interesting (at least to me) trying to figure out why not all car are affected.

Tesla does not have "model years" and does about 30 hardware revisions every week.

This is the flip side of the coin - they simply CAN NOT test all possible combinations of hardware and inevitably screw it up.

 

[whitex]

Tesla does not have "model years" and does about 30 hardware revisions every week.

This is the flip side of the coin - they simply CAN NOT test all possible combinations of hardware and inevitably screw it up.

They can and do test it on all possible configurations - they simply release it and then wait for the phone to ring. :wink::tongue:

With progress comes a price - constant improvements/evolution rather than waiting for next model year, OTA providing quick and free new features, bug fixes, etc, they all come at a price of being a part of QA process sometimes. The silver lining is Tesla's ability to send out an OTA to fix things without you having to visit any SC.