Anyone having problems charging with Tesla (DC and AC)?

[borski]

This sucks. I had no idea Gravity wouldn't work on Tesla Destination chargers. WTF?

It does. I’ve used them fine. Some destination charger owners set their chargers to “Tesla only” and some of the older chargers are not SAE J3400 compatible.

Unlike the original Tesla connector, which used CAN bus communication, NACS employs the ISO 15118 protocol used by CCS1, allowing for vehicles with a CCS1 port to charge at a NACS station using an adapter, and allowing Tesla vehicles to charge at a CCS1 station using an adapter.

Tesla vehicles built before 2021 require an ECU retrofit to support charging at a CCS1 station. The Supercharger network remains backward compatible with both the original connector and NACS.

So the older destination chargers are also likely not NACS-compatible, which is why they don’t work, and are instead using the old Tesla CAN protocol. That’s my guess.

I've tried 5 in the last 24 hours. Just says CABLE CONNECTED then does nothing. Another fail by Lucid. I've charged our Porsche Macan on these same chargers, using my Teslatap adapter.

That is because TeslaTap includes a chip that pretends it is a Tesla. If you tried a different adapter it may not work.

 

[Saksak]

This sucks. I had no idea Gravity wouldn't work on Tesla Destination chargers. WTF?

I've tried 5 in the last 24 hours. Just says CABLE CONNECTED then does nothing. Another fail by Lucid. I've charged our Porsche Macan on these same chargers, using my Teslatap adapter.

Anyone tried using 2 adapters? NACS-to-J1772, and then back to NACS? I wonder if that might fool it? I didn't bring my Teslatap on this trip to try it.

This is not a fail by Lucid. Every non-Tesla vehicle that has a NASC port will have this problem.

Summarizing @borski’s post, the old Telsa destination chargers uses a legacy Tesla-proprietary communication protocol (Tesla has abandoned it in favor of the ISO protocol). The Teslatap has a special chip that converts that legacy protocol to the J1772 protocol, which is why it worked on your other EV’s with the J1772 port.

The sandwich should work, in theory. I don’t know if it would be safe.

 

[dbsb3233]

This is not a fail by Lucid. Every non-Tesla vehicle that has a NASC port will have this problem.

Summarizing @borski’s post, the old Telsa destination chargers uses a legacy Tesla-proprietary communication protocol (Tesla has abandoned it in favor of the ISO protocol). The Teslatap has a special chip that converts that legacy protocol to the J1772 protocol, which is why it worked on your other EV’s with the J1772 port.

The sandwich should work, in theory. I don’t know if it would be safe.

Ah, thank, that explains it. They didn't include the TeslaTap magic that allows it to work when they went native NACS in the Gravity, which is why it works on most other non-Teslas (since most are J-1772). I remember that TeslaTap said they did something special where you have to let it do the handshake first to let it establish that protocol before plugging in the car.

I'll have to bring the TeslaTap next trip. As long as the adapters make good contact, I would think it's safe enough for L2 power. I wouldn't wanna go there on DCFC though.

Another poster mentioned a hack of unplugging and replugging it quickly after it just sits there saying CABLE CONNECTED. I'll test that today.