Don wrote:Nobody is asking (or expecting) Mitsu to stand behind an OEM EVSE which has been modified
What I think we have a right to expect is . . . . that if the customer us using any EVSE which is 100% compliant with the J1772 standard, then the car should recognize that and function as advertised
Giving us a built-in 'hiccup' in the cars software so it only works properly with this or that brand of EVSE just isn't acceptable - I know everyone is tired of hearing my anology, but this is exactly the same as if an ICE vehicle manufacturer built a car which would only operate on Chevron gas . . . . because they had some sweetheart deal with Chevron
Thats a separate issue, the OP complained about Mitsubishi technicians poo-poo'ing his modified EVSE. That's a given, I wouldn't have said anything to them about it because the technicians are going to suspect that right away.
This problem is very different from gasoline, its a software/hardware compatability problem. Petrolium companies can put all kinds of twists on the gasoline standard by putting additives into the fuel, but your car will still run. Software is very different, depending on how its coded - the software may be expecting only one value not a range of values, its all in the keystroke (x = 1 or x >= 1 && x <=5).
From reading all of the documents on the Open EVSE site, I know I came across something that said the J1772 is a standard but not all companies follow it to the letter. With all the EVSEs we have on this forum and with all the different results we are getting, I can see this to be true. Obviously some did follow the J1772 standards and others put their own twist on it.
Being in the software industry myself, I know the nightmare this is for Mitsubishi. Building software is very difficult because you never know what the end user is going to do with it. We have to code for every possible possibility and we still miss a lot and get complaints and support tickets. I'm glad I only code internal projects where I can be guaranteed what web browser is being used. There are HTML standards and everyone is SUPPOSED to follow it, but everyone knows that each browser has their own twists on the standard.
We are basically driving a computer and its going to have its quirks and bugs when used with various adapters. Liken this to the early days of PCs when we wanted to add a video card or some other peripheral. What a headache! Very lucky if it even worked with your brand of computer and setting all the dip switches a hundred different ways and staying up all freaking night to realize the video card wasn't even compatible even though the box said it was! I remember those days very clearly, especially since I was a field service technician back then.
I know this sounds like fanboy crap but I just don't see where Mitsubishi is at fault here. The remote works with the supplied EVSE. The remote is not a standard piece of equipment on an Electric Vehicle - its a nicety and a mileage saver. Some cars overseas don't even come with the remote. If you aren't getting the results you desire, then I'd suggest not modifying the supplied EVSE or buying one of the EVSEs where the remote does work. Also, all the cars are charging from the various EVSE, again Mitsubishi delivered as advertised. I don't recall reading anywhere that the remote is guaranteed to work with all EVSEs. That is asking for a lot of extra expense that would raise the price of the car.