Lenze Global Drive PLC Developer Studio - Manual (Page 93)

Drive PLC
Appendix
8.5 System error messages
8−13
L
DrivePLC DE 6.0
No. Remedy Cause Meaning Display
125 CE14 FIF−CAN BUS−OFF status
(too many faulty telegrams
received) PLC has received too many faulty telegrams sent
via system bus and has disconnected itself from
the bus
·
Check wiring/cable
·
Check bus termination (if any)
·
Check screen contact of the cables
·
Check PE connection
·
Check bus load
·
Reduce baud rate (observe cable length)
201
...
208
oveR−RUN TASK1
...
oveR−RUN TASK8 Task with Id.2
...
Task with Id.9 Time−out (see task configuration):
Task processing takes longer than the monitoring
time set
·
Set task run−time
·
If necessary, change monitoring time
·
Determine time−out reason by checking the
task run−times at the task monitor
·
Swap out time−critical program parts to a
slower task
209 FLOAT SYS−T System task Floating−point error (REAL):
Error in real calculation (e.g. divided by 0)
·
Check real calculation (program code)
·
The error is eliminated as in a task overflow 210 FLOAT CYCL.−T Cyclic task (PLC_PRG)
211
...
218
FLOATTASK1
...
FLOATTASK8 Task with Id.2
...
Task with Id.9
219 overrun Cycl.−T Time−out in
cyclic task (PLC_PRG) Task processing takes longer than the monitoring
time set
·
Set task run−time
·
If necessary, change monitoring time
·
Determine time−out reason by checking the
task run−times at the task monitor
·
Swap out time−critical program parts to a
slower task
220 NoT−FKT−CREDIT Insufficient units on the target
system It was tried to load a program with technology
functions to a PLC not providing corresponding
units Use the T−variant of the PLC
230 No Program PLC program error No PLC program loaded Load PLC program to PLC
231 Unallowed Lib Library function is not
supported You have called a library function in the PLC
program. This function is not supported, e.g.
because the required hardware is not available Remove library function or ensure that the
required hardware devices are provided
232 NoCamData Motion profiles (cam data) are
not available When functions of the LenzeCamControl.lib
function library were called, the controller
recognised that there are no motion profiles (cam
data) loaded in the PLC memory
·
Ensure that valid cam data were attached to
the project via the DDS cam support
·
Re−load the PLC program (maybe the
Online
WReset (original) command has been
executed in DDS)
240 ovrTransQueue Error Free CAN objects" Overflow of send order memory
·
Reduce number of send orders
·
Prolong cycle time
241 ovr Receive Error Free CAN objects" Too many receive telegrams Reduce number of telegrams on bus
250 2.Flash Err Error during FLASH memory
access The PLC program tries to access a faulty FLASH
memory or FLASH memory does not exist Ensure that the PLC has a FLASH memory. If
FLASH memory already exists, contact Lenze.
251 AddData CsErr Error during FLASH memory
access Check sum error occurred when loading data into
the FLASH memory Check the check sum of the file to be loaded and
repeat data transfer
252 AddData DlErr Error during FLASH memory
access Error occurred when downloading data into the
FLASH memory (e.g. time−out, transmission error,
mains failure during data transfer) Check/repeat data transfer
260 Err NodeGuard "Life guarding event" PLC has been configured as a CAN slave with
"node guarding" and has not received any "node
guarding" telegram within the node lifetime of the
CAN master.
·
Check system bus (CAN) and CAN configuration
·
Ensure that "node guarding" has been
activated in the CAN master
·
Adapt node lifetime to CAN master setting