EasyManua.ls Logo

BFT PERSEO-CBE - 14 Error Handling

BFT PERSEO-CBE
24 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
- 41 -
Control unit
EN
ENGLISH
14. ERROR HANDLING
The control board can store up to 10 di erent errors, with no. of occurrences limited to 10, for each event.
In case of blocking (severe) error, it is possible to restart the board by pressing both keys “+” and “-“ for 5 seconds or by switching o
and on the power supply. When restarting by means of keys, a memory check is performed and automatic recovery of out-of-range
parameters is done. The parameters are set to default factory values, so a new setup should be done, if necessary.
In level 4 menu, parameter H55, shows the list of events and error stored in memory. The display shows alternatively the error code
(xx and the number of occurrences. Use “+” e “-“ for scroll the whole list.
At the end of the list, an exit code is presented: quitting (by pressing “F”) with
 the error list is preserved, quitting with  the
error history is cleared to zero.
Events/warning not severe are stored in memory, without blocking the normal behaviour of the control board.
List of errors and events with the indication of blocking/not blocking:
FAULT AND EVENTS TABLE:
Par Description BLOCKING
(
Internal error on memory access. YES
(
Out of range memory address. YES
(
Fuse F3 or F4 blown or not present. YES
(
STOP occurred, changing the normal automation behaviour.(*) NO
(
Obstacle detected during operation. NO
(
Time-out elapsed while opening. NO
(
Time-out elapsed while closing. NO
(
Break on U-Link communication. NO
(
Programmed maintenance cycles reached. NO
(
Close limit switch not working (when present and enabled). NO
H
MODBUS: unknown command. YES
(
MODBUS: parity parameter error. Internal error. YES
H
MODBUS: wrong parameter or data length. YES
(
Communication parameter unknown YES
(*) Events occurrence that change the normal behaviour, such as STOP, obstacle detection, etc., are stored.
For example, if STOP input activates during a static status (automation stopped), the event is not saved; but if it prevents a movement
or inhibits a command, it is stored.

Related product manuals