Note that I was talking in terms of a Ford supplied adapter, with a Ford
supplied phone app.
I sincerely doubt that each SuperCharger has an up to date list of every
VIN that Tesla ever produced. So, they MUST talk back to the Tesla
servers to validate the VIN. This means that Ford - who is going to be
using the Tesla Supercharger API with their system, is likely to be able
to make this work. Even if the existing CCS communications doesn't
include a VIN (or equivalent ID), the fact it's being used with a Ford
supplied adapter and phone app, means that the specific car owner can be
identified for billing.
I did NOT say that any random person on the street can make their own
CCS adapter to make it work.
On 6/21/2023 10:23 AM, (-Phil-) wrote:
No, but there is no way to bill it. Tesla handles billing on SWCAN
supercharger protocol by VIN, the car controls the supercharger, there
is no back-end auth. So the only technical way to build such an
adapter would be to spoof a Tesla, and "steal" the power, which is
theft of service, and probably access device fraud (I am not an
attorney), which carries a 10 year sentence.
On Wed, Jun 21, 2023 at 10:16 AM John Lussmyer via EV
<ev@lists.evdl.org> wrote:
So, you are saying that it's technically impossible to build a CCS
adapter that can translate the CCS standard communications to
whatever
the current Tesla super chargers have. i.e. Ford Lied about it.
it is physically impossible, even if you have the Ford app that will
work with Tesla superchargers, and it tells the system that using a
special Ford Custom CCS adapter is ok, that it can't ever work.
On 6/21/2023 8:51 AM, (-Phil-) wrote:
> The broken record continues:
>
> Only the superchargers that support CCS signalling native (V4)
or the
> two (so far) V3 retrofitted with Magic dock will be able to be
used by
> 3rd party EVs, adapter or not!
>
> It's all right there at 4.5.1 in the "official" Tesla document:
>
https://tesla-cdn.thron.com/static/HXVNIC_North_American_Charging_Standard_Technical_Specification_TS-0023666_HFTPKZ.pdf?xseo=&response-content-disposition=inline%3Bfilename%3D%22North-American-Charging-Standard-Technical-Specification-TS-0023666.pdf%22
<https://tesla-cdn.thron.com/static/HXVNIC_North_American_Charging_Standard_Technical_Specification_TS-0023666_HFTPKZ.pdf?xseo=&response-content-disposition=inline%3Bfilename%3D%22North-American-Charging-Standard-Technical-Specification-TS-0023666.pdf%22>
>
<https://tesla-cdn.thron.com/static/HXVNIC_North_American_Charging_Standard_Technical_Specification_TS-0023666_HFTPKZ.pdf?xseo=&response-content-disposition=inline%3Bfilename%3D%22North-American-Charging-Standard-Technical-Specification-TS-0023666.pdf%22
<https://tesla-cdn.thron.com/static/HXVNIC_North_American_Charging_Standard_Technical_Specification_TS-0023666_HFTPKZ.pdf?xseo=&response-content-disposition=inline%3Bfilename%3D%22North-American-Charging-Standard-Technical-Specification-TS-0023666.pdf%22>>
>
> It's the first link; "Technical Specification" on this page:
> https://www.tesla.com/support/charging-product-guides#NACS-resources
>
> It specifies "For DC charging, communication between the EV and
EVSE
> shall be power line communication over the control pilot line as
> depicted in DIN 70121.", which is NOT supported by current V1,
V2, and
> V3 superchargers all over North America. In addition, the
location
> and length of Tesla's whips are not able to reach almost any
other EV
> without it blocking multiple parking spots.
>
_______________________________________________
Address messages to ev@lists.evdl.org
No other addresses in TO and CC fields
HELP: http://www.evdl.org/help/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.evdl.org/private.cgi/ev-evdl.org/attachments/20230621/e57c1e51/attachment.htm>
_______________________________________________
Address messages to ev@lists.evdl.org
No other addresses in TO and CC fields
HELP: http://www.evdl.org/help/
