stopcrazypp
Well-Known Member
The problem with Chademo from what I remember reading is that Chademo protocol controlls the charging cycle rather than the car. Tesla does not want to allow someone elses protocol to charge their batteries. An intermediary would have to be constructed to simulate a charging battery allowing the car to continued to dictate the charge, and tell Chademo when to ramp down and finish charging.
Anyone correct me if this is incorrect.
I take it you are referring to this post?
But he also says that he doesn't like CHAdeMO since it goes into the internals of the car (CAN bus). He expects that quick chargers will be retrofitted to the new SAE standard. (Did I get that part right?)
In general though, your interpretation is incorrect. The car does have to send battery parameters to the CHAdeMO station and the station does send data signals to the car, but it is the car that controls the charging cycle (by sending signals with the charging current specified, it also sends the 0 current signal to signify to stop charging).
http://www.chademo.com/05_protocol.html
I think the engineer was more concerned about security (you can do a lot more with a CAN bus than just charging) and that you have to send detailed battery information to the charger (which you presumably don't have to with the J1772-DC). Plus, like TEG says, it's a lot more complicated than J1772 since you need full bi-directional support (whereas J1772 is quite "dumb"/simple and just uses a pilot signal, J1772-DC will add PLC).