I have noticed a change in charge port lock (locking pin) operation from my recent experiences, and wondered:
a) did anyone else notice ?
b) if anyone with 4.4 or even older software could check a few of these operations for me to validate my concerns
The previous experience I had (especially around the design of the CapturePro device) with charge port lock operation was the following:
What I'm seeing now with my V4.5 Model S:
Has anyone else noticed this, or can they add any data to the operation of their car with older SW rev?
If this change is validated to be true and no other method exists to unlock the charge port except the J1772 button, then the CapturePro device is rendered unusable (at least until or if SW update might make the lock policy different) -- the reason can be explained in more detail in the other more appropriate thread, but I wanted to alert drivers of the more general issue of this change.
Feedback would be appreciated here. :crying:
David Smith
a) did anyone else notice ?
b) if anyone with 4.4 or even older software could check a few of these operations for me to validate my concerns
The previous experience I had (especially around the design of the CapturePro device) with charge port lock operation was the following:
interior charge-port button | stop J1772 charger | press J1772 handle button | |
---|---|---|---|
owner in range | unlock | unlock | unlock |
owner out of range | stay locked | stay locked | stay locked |
What I'm seeing now with my V4.5 Model S:
interior charge-port button | stop J1772 charger | press J1772 handle button | |
---|---|---|---|
owner in range | stay locked | stay locked | unlock |
owner out of range | stay locked | stay locked | stay locked |
Has anyone else noticed this, or can they add any data to the operation of their car with older SW rev?
If this change is validated to be true and no other method exists to unlock the charge port except the J1772 button, then the CapturePro device is rendered unusable (at least until or if SW update might make the lock policy different) -- the reason can be explained in more detail in the other more appropriate thread, but I wanted to alert drivers of the more general issue of this change.
Feedback would be appreciated here. :crying:
David Smith
Last edited: