Hi,
#1. When charging on EVSE with internal schedule due to time of day variable rates, M3 does not wake up once EVSE starts advertising. No other J1772 car i have or had had trouble following J1772 pilot signal regardless of when it transitions.
My problem is that since i am charging two cars on a shared EVSE in a sequential mode, the charge availability time is not guaranteed to happen at the same time every time because it depends on car placement in the charging queue and how long it takes to charge the other car.
My current workaround is to have Tesla to always to be the first in the sequence and also have it scheduled at the same time EVSE is scheduled to start, so the EVSE starts advertising at the same time Tesla is ready to charge. But it is a nuisance since i have to care about sequencing the cars (sometimes i miss) and because sometimes EVSE may pause for a while when it doesn't like the ground current detected enough for Tesla to go back to sleep before EVSE error auto resets.
Another possible workaround is to put the car into sentry mode, which keeps awake and seems to force it checking EVSE dvertisements during the night; but this has also proven to be hit or miss; but mostly because this is also a nuisance just like charge sequencing, since sentry mode resets every time and i have to remember to set it on every time i plug.
#2. Again, when used on shared EVSEs in shared mode (pretty typical in commercial EVSEs that supply 3.3kw if two cars are plugged, but then let a car go all the way up to 6.6 once the other car completes and more charging badwidth becomes available), Tesla more likely than not to get stuck charging at 3.3kw or slightly above it but does not go up to 6.6 kw once it becomes available. Again, this pretty much ignores the J1772 pilot guidance.
This prevents me from using shared mode at home because it does not ensure that available charging bandwidth is fully utilized, resulting in longer charging times or overnight undercharges. My current workaround is that I use sequential mode at EVSE (it places cars in a queue with full bandwidth available to either car from the start of the charging session), but this is not preferable because it exacerbates problem #1 (charging starts at an undetermined time) and because it creates higher strain on equipment than it needs be.
Just like issue #1, this never had been a problem with any other cars but Tesla.
Both issues look like J1772 compliance issues. These scenarios are all standard for J1772s EVSEs and actually happen every day without problems in other cars.
One EVSE designer i spoke to expressed an opinion that this also used to be an issue with Model S, but then they apparently fixed that.
Do you happen to have any insights/workarounds for these? I suspect if there were, i would know about it by now, but I thought i would check with the forum anyway. Thanks.
#1. When charging on EVSE with internal schedule due to time of day variable rates, M3 does not wake up once EVSE starts advertising. No other J1772 car i have or had had trouble following J1772 pilot signal regardless of when it transitions.
My problem is that since i am charging two cars on a shared EVSE in a sequential mode, the charge availability time is not guaranteed to happen at the same time every time because it depends on car placement in the charging queue and how long it takes to charge the other car.
My current workaround is to have Tesla to always to be the first in the sequence and also have it scheduled at the same time EVSE is scheduled to start, so the EVSE starts advertising at the same time Tesla is ready to charge. But it is a nuisance since i have to care about sequencing the cars (sometimes i miss) and because sometimes EVSE may pause for a while when it doesn't like the ground current detected enough for Tesla to go back to sleep before EVSE error auto resets.
Another possible workaround is to put the car into sentry mode, which keeps awake and seems to force it checking EVSE dvertisements during the night; but this has also proven to be hit or miss; but mostly because this is also a nuisance just like charge sequencing, since sentry mode resets every time and i have to remember to set it on every time i plug.
#2. Again, when used on shared EVSEs in shared mode (pretty typical in commercial EVSEs that supply 3.3kw if two cars are plugged, but then let a car go all the way up to 6.6 once the other car completes and more charging badwidth becomes available), Tesla more likely than not to get stuck charging at 3.3kw or slightly above it but does not go up to 6.6 kw once it becomes available. Again, this pretty much ignores the J1772 pilot guidance.
This prevents me from using shared mode at home because it does not ensure that available charging bandwidth is fully utilized, resulting in longer charging times or overnight undercharges. My current workaround is that I use sequential mode at EVSE (it places cars in a queue with full bandwidth available to either car from the start of the charging session), but this is not preferable because it exacerbates problem #1 (charging starts at an undetermined time) and because it creates higher strain on equipment than it needs be.
Just like issue #1, this never had been a problem with any other cars but Tesla.
Both issues look like J1772 compliance issues. These scenarios are all standard for J1772s EVSEs and actually happen every day without problems in other cars.
One EVSE designer i spoke to expressed an opinion that this also used to be an issue with Model S, but then they apparently fixed that.
Do you happen to have any insights/workarounds for these? I suspect if there were, i would know about it by now, but I thought i would check with the forum anyway. Thanks.
