Tesla (including non-tesla) Network Confusion

It looks like some contributors (including country editors) do not pay attention when entering “Tesla” as the network operator. OCM has two variants of Tesla network:

  • Tesla (including non-tesla)
  • Tesla (Tesla-only charging)

Here is the screenshot of Canadian province of British Columbia showing charging stations which have the network set as “Tesla (including non-tesla)”. All of them are incorrect:

https://imagizer.imageshack.com/img924/9026/ot91I9.png

There are only three Tesla Superchargers with Magic Dock in Canada, which were retrofitted as follows:

Calgary, AB - Nov. 2023
Deep River, ON - Aug. 2023
North Bay, ON - Aug. 2023

https://map.openchargemap.io/index.html?id=283703

https://map.openchargemap.io/index.html?id=146043

https://map.openchargemap.io/index.html?id=146063

I have cleaned out all the stations with incorrect variant of Tesla network in Eastern Canada, but did not have time to process Alberta and BC. USA needs some cleanup too, anyone willing to do it can start with PlugShare’s map of CCS compatible Tesla Superchargers available here:

https://www.plugshare.com/map/tesla-ccs-locations

I had cleaned out the provinces of Alberta and BC over the weekend and now someone put Tesla (including non-tesla) supercharges all over the place in Eastern Canada again. I have just cleaned out about 50 of them. If this is erroneous data imported from AFDC then we just have to live with it, but if it is a country editor not paying attention then maybe he/she should consider taking some break from editing OCM for a week or two.

I’m confused about why there is a differentiation between Tesla stations that support CCS and NACS, and Tesla stations that support only NACS. Isn’t it possible to differentiate between these by checking the supported connector types?
My personal view is that this is an unneeded redundancy that naturally leads to synchronization errors such as these. It also violates the principle of minimum data storage.
Consider what I feel is the similar case of Rivian which is split into two providers. There is the '“Rivian Adventure Network” that has 200 kW CCS chargers and the “Rivian Waypoints L2 Network” which has 20 kW L2 chargers. Consider the conundrum when a station has both connector types? Is this one station or two, and if one station, which one? Seems to me that from a user’s perspective they’d prefer to have it all be one provider and if then they can choose one or both connector types in the filter section. When they do select a provider, they can see that the single location has both types of connectors.
Just my opinion, …

1 Like

If the Data Provider is set to ADFC then this is our import that’s doing it. We can change that - currently there’s no way to know if a tesla site via AFDC is open to non-tesla.

@andyk the differentiation we have for Tesla are done using the network choice: Tesla chargers which do support non-tesla vehicles (e.g. various sites in the US and Australia etc, but not all), Tesla chargers which are tesla only. Currently destination chargers (non networked dumb chargers) which are conceptually “tesla” but not really owned or operated by them are lumped in with these and may or may not accept non-tesla vehicles depending on their dip switch settings.

Really what we probably need is a feature in our data model to say if a connection will only accept a specific manufacturer brand but there’s a potential that gets messy if some manufactures share with some others (e.g. Porsche)

More broadly our data model needs a revision to allow connections to be split into EVSE connection groups at a site, then each EVSE connection group can have one or more associated networks. That way a single geographic site could have chargers from a few different networks each with independent connector types and optional restrictions. I’ve intended to make that particular change since about 2015 though.

@ AndyK

To my knowledge, the only Tesla Superchargers which currently support charging non-Tesla vehicles in the US and Canada are those equipped with Magic Dock adapters. So yes, at this point we have redundancy in OCM settings for those two countries. However, please keep in mind that OCM has global coverage and NACS is currently used only in the following countries:

Canada
Mexico
USA
Japan
South Korea
Ukraine (50/50 split with CCS2)

Everywhere else all new Tesla cars are either equipped with some variant of CCS2 charging port or with GB/T port (in China). Here are the best links I could find on the web:

https://imgur.com/5961m3H

https://teslamotorsclub.com/tmc/threads/tesla-charge-ports-plugs-from-china-north-america-and-europe-compared-for-models-s-x-3-y.246571/#post-6118446

So, let’s take an example of Australia, where all Tesla Superchargers only have CCS2 connectors and all EVs (Teslas and non-Teslas) have CCS2 charging ports. Some of those Superchargers support charging non-Tesla vehicles and some do not, so having them labelled as belonging to separate network operators makes perfect sense.

In 2025 and beyond we might have a similar situation in North America when new non-Tesla EVs equipped with NACS charging port start entering the market. It is unlikely that Tesla just decides to flip the switch and open the whole Supercharger network to all those new cars at the same time.