You know.
This reminds me back in the old modem days, the war between K-Flex and X2 .....and of course Hayes standard.
They really NEED to settle on a standard and ALL adhere to it. THAT would make e vehicles so much more attractive to new customers. They all hear how difficult it is to get a working charger, and that scares them. and it should !! Nobody wants to be stranded in Bugtussle, OK.
It just makes more business sense too, WHY would you turn away customers and alienate people? Oh that makes them want to buy MY product because it's all that is supported. umm no that makes them RESENT you because you did that and avoid your product out of anger.... (pay attention Elon).
I mean, it's NOT that hard, pick a protocol and standard and DO IT.
Ok, car and charger have to talk, THIS is the communication protocol..... x,1,3200,4. ADHERE TO IT.
the 'config' file which tells the charger what the car can take has a design, say 10 lines or blocks.
Block 1, port type
Block 2, battery capacity
Block 3, max charge rate
Block 4, top off rate
Block 5, ramp rate
Block 6, finishing charge
Block 7, min voltage
Block 8, max voltage
Block 9, temperature
Block 10, safety crap
Ok ok, you get the idea
The charger now, has a config file so the car knows what it is dealing with.
Block 1, min voltage
Block 2, max voltage
Block 3, max amps
Block 4, max kw
block 5, ramp rate
Block 6, max charge time....
etc ok bla bla you get the idea.
You build a charger you ADHERE to this protocol for your communications.
You build a car you ADHERE to this protocol to TALK to the chargers.
This way, no matter who you are, what you built, it charges properly and EVERYONE benefits.
.json how f hard is it???
Aaron