EATON
HFX Product Family Installation and Operation Manual E-ELCL-II002-E2 July 2019
52
Illegal_flash write is active – This is an indication
that CODESYS is attempting to write to a restricted
address in flash.
Cpu_addr_err is active – This fault occurs if the CPU
attempts to read or write an illegal or mis- aligned
address. CODESYS will trigger this fault if you don't
do a clean all.
Illegal_instr is active – This is similar to cpu_addr_err;
however, it is for illegal instructions encountered by
the CPU
FPU_exception is active – This fault is not supported
by our hardware
MRAM_fail is active – This indicates a detected CRC
error or other problem with the MRAM used to store
RETAIN variables. If this error occurs it is a major
hardware failure.
PWMx_loss control is active – This is an indication
that an output channel has failed. It should occur if
the PWM driver fails in a shorted condition.
It indicates that the program is instructing the output
off, but the output is still flowing current. When
this occurs it will then trip the secondary protection
which is the internal solid state relay. This fault may
also occur if a higher than supply voltage is placed on
the output pin as this will cause reverse current to
flow (through the body diode of the high side FET),
which should be detected and thus trip the solid
state relay.
CODESYS exception is active – CODESYS has its
own exception implementation. Take for example
the watchdog you can enable for each task. If you
set enable the task watchdog and violate it then
CODESYS throws an exception and displays an error
message in the IDE and this fault will mirror that
activity.
CODESYS low mem is active – running low on
CODESYS memory. There is 16KB of internal
"dynamic" memory that is allocated to CODESYS –
This is used for all of their code. There is information
about this on the EDIS "Debug Sys" page.
CODESYS out of dn mem is active – similar to low
memory fault above, but this is when the operating
system is out of dynamic memory.
CODESYS bad pointer is active – CODESYS internal
code calls a function that checks if memory is good
CODESYS target mismatch – The CODESYS target
description does not match the firmware
CODESYS exception is active – CODESYS has its
own exception implementation. Take for example
the watchdog you can enable for each task. If you
set enable the task watchdog and violate it then
CODESYS throws an exception and displays an error
message in the IDE and this fault will mirror that
activity.
CODESYS watchdog is active – This is monitoring
the internal CODESYS task in firmware that executes
all things CODESYS. Subtly but significantly different
from the watchdog you enable in CODESYS via the
IDE. This will happen if CODESYS locks up for any
reason. Take for example you write a while(TRUE)
{} loop in IEC code. Since everything runs from a
single context, CODESYS will never see that the
while(TRUE) loop has locked up, but the operating
system will and in turn trigger this error. The
watchdog time for this is configured in"CODESYS
Runtime Watchdog" under System Config
Configuration tab. The default for the "CODESYS
watchdog" is 2 seconds so your individual task
watchdog should be less.
CODESYS low mem is active – running low on
CODESYS memory. There is 16KB of internal
"dynamic" memory that is allocated to CODESYS –
This is used for all of their code. There is information
about this on the EDIS "Debug Sys" page.
CODESYS out of dn mem is active – similar to low
memory fault above, but this is when the operating
system is out of dynamic memory.
CODESYS bad pointer is active – CODESYS internal
code calls a function that checks if memory is good
CODESYS target mismatch – The CODESYS target
description does not match the firmware
HFX Product Family