I'm trying to get an issue resolved with some older Schneider Electric charging stations at a location in WV (14 of them in fact). Have you ever experienced this? Hoping to get at least a few fixed/replaced so we can support a few Roadster owners who have never been able to successfully charge for an upcoming event in May.
From Schneider support...
This sounds like an issue with the CCID (Charge Circuit Interrupt Device) device. It is intended to detect a fault when the current differences between the phases is greater than 20mA. Prior to late 2012, the CCID setpoint was 5mA (early EV industry Standard). The 5mA setpoint proved to be too sensitive and was thus changed to 20mA. Commercial outdoor units do not have a part number change to indicate the 20mA vs 5mA CCID. Check the serial number of those devices, located on the nameplate on left side of unit. Date codes starting with 11 or 12 and only 5 digits long will have the 5mA CCID setpoint. If the EVSE has a 5mA setpoint, then it should be replaced for a 20mA CCID unit.
If you find the the units have a serial number starting with 11 or 12, we can work with APUS to see if they would like to move forward with correcting this issue.
From Schneider support...
This sounds like an issue with the CCID (Charge Circuit Interrupt Device) device. It is intended to detect a fault when the current differences between the phases is greater than 20mA. Prior to late 2012, the CCID setpoint was 5mA (early EV industry Standard). The 5mA setpoint proved to be too sensitive and was thus changed to 20mA. Commercial outdoor units do not have a part number change to indicate the 20mA vs 5mA CCID. Check the serial number of those devices, located on the nameplate on left side of unit. Date codes starting with 11 or 12 and only 5 digits long will have the 5mA CCID setpoint. If the EVSE has a 5mA setpoint, then it should be replaced for a 20mA CCID unit.
If you find the the units have a serial number starting with 11 or 12, we can work with APUS to see if they would like to move forward with correcting this issue.