The Fluke FEV350 and FEV500 don't fail with a generic "Error 4" the way a lot of test equipment does. They fail with a specific, named sub-test result, a control pilot colour indicator, or a symbol on the test screen, and each one points at a genuinely different part of the circuit. Reading "control pilot red" correctly, for instance, means understanding it as a signal outside its expected limit for the current CP state, not as a single fault type; reading an FEV500 IMD "Trip Test fail" correctly means first checking whether the station even has an insulation monitoring device fitted at all, because a station without one will legitimately fail that specific sub-test every time. This guide works through what the actual documented results mean and what to check first for each.
FEV350: the control pilot colour indicator is doing more work than it looks like
The FEV350's control pilot state indicator uses four colours, and each one describes a distinct condition on the CP signal, not a pass/fail toggle:
- Gray: the control pilot signal is off for that CP state, meaning the station simply isn't asserting that state at the moment. Not a fault by itself, just an indication of which state is currently inactive.
- Yellow: the signal is in the process of being evaluated against the limits for that state. A transient indicator during a test in progress, not a result.
- Green: the control pilot signal is within the limits for the CP state, the pass condition.
- Red: the control pilot signal is not within the limits for the CP state, the fail condition.
Worked scenario: a technician runs a Control Pilot test on a newly commissioned Type 2 AC charger and the indicator shows red during the transition from CP state A to CP state C, the transition the test specifically exercises. Because the Control Pilot test measures the CP signal's voltage, frequency and duty cycle against the limits set for the station type in the configuration menu, and converts the measured duty cycle into a maximum current (Imax) value, a red result during this transition means one of three things: the station's pilot signal voltage levels are outside the expected range for that state, the signal frequency has drifted, or the duty cycle (and therefore the current the station is advertising) doesn't match what the station's own configuration says it should be offering. The FEV350 saves up to ten of these state-change events with their associated output voltage readings, and can display them as a table or a curve diagram, which is the right next step here: look at the actual waveform rather than just the colour, because a clean square wave sitting at the wrong voltage level points at a different fault (a marginal signal driver in the station) than a distorted or noisy transition (a poor connection or interference somewhere in the CP signal path).
FEV350: the PE Pre-Test result is a stop condition, not a data point
Before any other test runs, the FEV350 requires a PE Pre-Test: touching a bare finger to the instrument's PE PRE-TEST sensor for three seconds to check for hazardous voltage on the station housing and PE conductor. If that result shows greater than 50 V, the documented instruction is to stop the test immediately, because there may be hazardous voltage present at the PE terminal and metal parts of the charging station. This is worth flagging precisely because it's easy for a new technician to treat every FEV350 screen as "just another test result to record," when a PE Pre-Test failure is a genuine stop-work condition until the underlying earthing fault is found and corrected, not a line item to note and continue past. The manual also notes the test may not catch an open PE (a PE conductor connected to phase, or simply disconnected, rather than to ground), which is a real limitation worth knowing: a clean PE Pre-Test result does not, on its own, prove the earth conductor is properly connected to ground, only that no hazardous voltage is currently present on the parts it can sense.
FEV350: what the "M" symbol on an RCD or RDC-DD test actually tells you
During a 30 mA RCD trip test or a 6 mA RDC-DD trip test, the FEV350 runs two distinct sub-tests, trip time (does the device open the circuit within the time required by the applicable standard, based on the mains system, voltage supply and RCD type configured for the station) and trip current (does the device open the circuit at a sufficient current level as required by that same standard). An "M" symbol on the display indicates the RCD, RDC-DD, or GFCI device being tested has not tripped. A failed trip current sub-test with a device that otherwise trips correctly on the time sub-test points toward a device whose sensitivity has drifted rather than a wiring fault; a device that fails to trip on either sub-test at all is a more fundamental protective device failure, and either result is a legitimate reason to stop and replace or recalibrate the RCD/RDC-DD before returning the charging point to service, rather than treating a marginal reading as close enough.
FEV500: reading a SLAC failure correctly
A CCS2 fast charger's digital communication runs power-line communication (PLC) over the control pilot line at frequencies between 2 MHz and 30 MHz, a range genuinely susceptible to attenuation and crosstalk, particularly where multiple charging points sit close together. The FEV500's SLAC (Signal Level Attenuation Characterization) test exists specifically to isolate the correct EVSE, the one physically connected, from any other nearby station whose signal might otherwise be picked up. For a successful test, the signal strength needs to fall between 0 dB and 10 dB, though the instrument will accept signal strength up to 20 dB before rejecting the link entirely.
Worked scenario: a technician tests a CCS2 station in a multi-bay commercial car park and the SLAC result reads consistently above 10 dB, or the FEV500 appears to intermittently identify a different EVSE-ID than expected. Given that PLC signal quality genuinely degrades with distance, cabling condition, and interference from adjacent stations, this pattern is a strong indicator of a physical-layer communication problem, a poor PLC coupling at the connector, cabling degradation, or genuine crosstalk from a neighbouring bay, rather than an insulation, earthing or power electronics fault. It is worth checking connector condition and cable routing before assuming the station's charging controller itself is defective, because SLAC failures very often trace back to the communication path, not the power path.
FEV500: why an insulation resistance "fail" is not always what it looks like
IEC 62196-1 clause 21 specifies an insulation resistance requirement of 5 MΩ for the DC power path. The FEV500's own pass/fail threshold, however, is set lower, at 500 kΩ, and this is a deliberate design choice rather than a relaxed standard: the station's own internal insulation monitoring device (IMD) sits electrically in parallel with the measurement being taken, and because the IMD itself presents a finite resistance, it pulls the measured resistance value down from what the "ideal" isolated conductor would show on its own. The FEV500's 500 kΩ threshold accounts for this parallel loading effect. A technician who is not aware of this and expects to see something closer to the textbook 5 MΩ figure may misread a perfectly healthy 600 kΩ to 2 MΩ reading as marginal, when it is in fact a normal result for a station with a functioning IMD connected.
FEV500: the IMD "Trip Test fail" that isn't actually a fault
This is the single most useful troubleshooting fact in this article, precisely because it inverts the instinctive read of a failed result. The FEV500's IMD test has two parts: a No Trip test, applying a high-resistance test resistor between a DC line and PE that should not trigger the station's insulation monitoring device, and a Trip test, applying a lower-resistance test resistor specifically designed to reliably trigger it. Not every EVSE contains an IMD at all. Where a station has no IMD fitted, the No Trip test will correctly display as passed (there's nothing there to nuisance-trip), but the Trip test will fail, accompanied by a warning message, simply because there is no monitoring device present to respond to the simulated fault.
Worked scenario: a technician runs the FEV500's guided Autotest on a CCS2 station and the IMD Trip test comes back failed. Read in isolation, this looks identical to the genuinely serious finding we described in our guide to insulation resistance testing for EV charging circuits, a monitoring system that should be catching future insulation faults and isn't. The first and correct diagnostic step is not to assume the worse case, but to check the station manufacturer's documentation for whether that specific model is architected with an IMD at all. If it isn't, the No Trip test passing and the Trip test failing with the associated warning message is the expected, healthy result for that station design, not a defect. If the station's documentation confirms an IMD is fitted and the Trip test still fails, then the earlier, more serious read applies: the station's own protection against a developing insulation fault during a live charging session is not functioning, and that charger should not return to service until it's resolved.
FEV500: Load Test aborts and residual voltage timing
The Load Test runs during an actual energy transfer phase, checking that the voltages the station delivers between DC+ and PE, and DC- and PE, stay within an acceptable range for the full duration of the test. If that check fails at any point, the FEV500 performs an error shutdown and aborts all remaining tests, rather than logging a single failed reading and continuing, which is worth knowing before you start a test sequence: a Load Test abort ends the session, and whatever tests hadn't yet run need to be repeated from the start once the underlying issue is found. Separately, the FEV500 checks that residual voltage between the DC+ and DC- lines drops below 60 V DC within one second of the charging plug releasing, a real safety-relevant timing measurement (not an arbitrary instrument default) that protects whoever handles the connector immediately after a session ends; a slow or incomplete residual voltage decay is a legitimate reason to hold a station out of service.
When the connector itself won't release
Both the FEV350 and FEV500 use a mechanical locking connector, and the FEV500's own manual documents a manual release procedure for exactly the scenario where a malfunction or power loss leaves the plug locked: using the Stop button first, and if that doesn't release it, a manual mechanism accessed by removing a small cover between the vent and the connector and inserting a thin tool (Fluke specifies roughly a 70 mm long, sub-8 mm diameter flathead screwdriver) into the release hole. This is worth having in a technician's back pocket before it's needed in the field, rather than discovering it for the first time with a locked connector and a queue of vehicles waiting.
The general troubleshooting order that follows from all of this
- Never skip or treat the PE Pre-Test as routine. A result over 50 V is a stop condition, and a passing result still doesn't rule out an open PE.
- Read the specific sub-test that failed, not just "the test failed." Trip time and trip current are different failure modes with different likely causes; SLAC, RISO, IMD and Load Test each point at a different physical layer of a CCS2 station.
- Check whether the failed result reflects a design characteristic before assuming a fault. The IMD Trip Test on a station without an IMD is the clearest example, but it's worth applying the same discipline generally: know what the station is supposed to do before deciding a result is abnormal.
- Use the waveform or curve view where the instrument offers one, rather than relying on a colour or pass/fail summary alone, particularly for control pilot faults where the shape of the signal tells you more than the pass/fail flag does.
For the broader context of what each of these tests is actually verifying and why, see our guides to insulation resistance testing for EV charging circuits and EV charging modes explained. For how these results get captured, compiled and reported once a test session is complete, see our TruTest software workflow guide.