Stepan
Member
In order for Plug & Charge (ISO 15118-2) to work, 4 entities have to implement their side of it.Since plug and charge from Tesla to non-Tesla uses the standardized protocol that EA also uses, does that mean that we can now plug and charge at EA as well?
1. OEM (Rivian)
2. Charge Point Operator (Tesla/EA/RAN)
3. Mobility Operator (Rivian, Blue Oval Network, etc)
4. Certificate "warehouse" (Rivian, Hubject, etc)
EA and Mobility Operator (In our case, Rivian) and certificate warehouse all have to set themselves up to be able to integrate with each other. And while the communcation between the charger and the car is well defined, setting up billing, communicating progress, charger status, etc, between charge point operator and mobility operator is a lot less standardized, with several competing specifications. Given tesla's track record, they probably are also not using any of them, so its not very transferrable to EA.
There are several factors that are all working against P&C happening on EA anytime soon:
1. [For customers] all charging memberships (EA Pass+, Tesla Supercharger Membership) are invalid, as those systems today are completely separate, via Rivian you will always be paying prenegotiated prices (most likely full price). Since these memberships pay for themselves after 2-3 charges, p&c is completely useless to anyone using it with any amount of frequency.
2. [For customers] At least in case of Ford, charge credit cards (Think Cosco's 4% cash back for "fuel ups") do not correctly classify those purchases as fuel ups. I've never been billed by Rivian for charging, but same issue could exist here.
3. [For Rivian] Rivian is busy trying to hit their own commitment of opening up RAN in 2024, which means same people that would be working with EA to integrate are busy ensuring seamless first party experience. As more evidence of this, all of EA's chargers are listed at 150kwh in the nav/app and have been for years. This tells me Rivian isn't prioritizing EA at all.
4. [For EA] Their software is a mess. Their own app and chargers do not know when they're working or not, let alone allowing 3rd parties visibility is extremely restrictive. Their first party vehicle (I.D. 4) only got recently enabled, only for the latest model year and it crashed systems for both EA and VW. If I was in charge of that software team, Rivian P&C would be very low on my priority list.
AFAIK, Tesla Superchargers uniquely added a pre-check to control OEM access to their network. Once an OEM implements full p&c (as per terms with Tesla), and the car can talk full 15118 protocol, has the right certificates to authorize communication (requires OTA) with the superchargers, you can use the tesla app to initiate charge and transact (be billed) for it. This is why people can already charge their Rivians as 2024.07 update installed the certificates and by initiating charge in the tesla app, the handshake goes through.
Depending on your technical level, this could be useful:
https://www.switch-ev.com/blog/basics-of-plug-and-charge
I should add there is another "simpler" option that EV Go and EVConnect does, called Autocharge and sometimes confusingly Plug and Charge. Autocharge only uses a "mac address" aka a unique identifier for each car. The charging network uses the car's MAC address, and "remembers" it to automate future sessions. Tesla and EA do not use that all (besides, maybe, internal tracking).
Sponsored