There are a lot of paths that "could be made to work". I have reverse-engineered the legacy supercharger protocol, so I could make an adapter that would allow charging a non-Tesla EV at a supercharger, and in-fact, I did this in 2017 for a client, and the owner promptly received a cease-and-desist from Tesla. (Which they abided by)
Over the years I have also been hired as an independent consultant for several companies, including one of the top-tier charging equipment manufacturers to help them investigate adapting Tesla compatibility well before any of the NACS announcements of late. It's not a technology limitation, it's more business and politics. Tesla wants in on the government cheese, so they will do what they need to do to qualify for grant and incentive money. They are already having trouble keeping up with supercharger build-outs just for Tesla owners. They do not want to jeopardize one of the primary selling points of Tesla ownership by suddenly making it difficult for their customers to use the supercharging network. They will do this slowly and on their terms, by rolling out sites with upgraded superchargers that will support 3rd party EVs, and they will try to get public money to do so. They don't really have any motivation to trip all over themselves to clog the existing supercharging network with a bunch of 3rd part EVs blocking multiple stalls. On Wed, Jun 21, 2023 at 12:50 PM Ron via EV <ev@lists.evdl.org> wrote: > Just spitballing here... > > What about VIN equivalents in the adapter itself or manufacturers building > their charge ports and in-vehicle networking to Tesla specs? > > All of this stuff is well over my head, but having written Palm Pilot > programs that interface with mainframe systems, it strikes me that there > are usually ways to effectively and reliably extend systems without > breaking them. > > But, as I said, all of this is well over my head. :) > -- > Ron > > On June 21, 2023 11:23:40 a.m. CST, "(-Phil-) via EV" <ev@lists.evdl.org> > 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 > >> > < > _______________________________________________ > 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/71e026fd/attachment.htm> _______________________________________________ Address messages to ev@lists.evdl.org No other addresses in TO and CC fields HELP: http://www.evdl.org/help/
