page 43 of 49
This error code is sent when the power supply voltage
drops by more than 10% of nominal
EVSE_FAULTS_
AUTO_RECOVER
Y
The charger is designed to automatically recover from
noncritical faults. This is an auto-recovery flag, sent
together with another fault flag to indicate that the
charger will attempt to recover from the fault. For
example, in over/undervoltage situations, the charger
will recover once the supply voltage falls back within its
nominal value.
EVSE
calibration
data error
The RTM has calibration data such as Voltage, Current,
Power, Energy and RCD as well as the device Serial
Number. The fault indicates that the MCU cannot access
these data. The fault may be cleared by an authorized
technician by reloading the calibration data
Stuck power relay fault: the charger monitors its relay
contacts and has detected that the neutral contact has
failed to open and remains closed
Stuck power relay fault: the neutral contact has failed to
close and remains open
Stuck power relay fault: the line contact has failed to
open and remains closed
Stuck power relay fault: the line contact has failed to
close and remains open
Device open
cover
detected by
tamper switch
This status flag is set to “1”, when the device detects the
opening of the main cover. At time of detecting of this
event the timestamp is recorded into NVM. The flag is
cleared at power cycle.
VendorID3 : Main MCU errors
Debugging information related to the SCARAB's main CPU.
Reset reason
cannot be
determined
The CPU cannot determine the cause of the reset.
Reset due to
power-on
event
The CPU was reset by a power cycle situation.
The main CPU was reset by an external trigger, such
as a debugging tool or another MCU in the
Compact.
Software
reset via
esp_restart
Reset triggered via an OCPP command (Soft Reset)
or via the web client / installer's app.
Reset can also be triggered following a firmware
upgrade.
To Next Page
Loading...