Owner's manual

8644/phoenix - 85
SYSTEM DESCRIPTION
Error description
Parameter error on the PROFIBUS (SET_PRM-Telegram)
Type No. Cause of error Resolution
1 1 An incorrect terminal number is being
used.
Check whether the terminal is
parameterizable.
2 A parameter block is incomplete. The number of terminals and parameter
blocks does not match.
3 The data length of the parameter block is
too small.
Check the number of parameters.
4 The data length of the parameter block is
too big.
Check the number of parameters.
5 The internal block for configuration,
security value and PCP is too small.
Check the configuration of the parameters
for the terminals.
6 Header byte of the module parameter is
not correct.
Check the first byte of the module
parameters.
7 PCP initialisation of a terminal that has no
PCP functionality.
Check the planning.
8 Too many data blocks for the terminal. The number of terminals and parameter
blocks does not match.
9 Incomplete data block in a de-activated
terminal.
Check the number of parameters.
Parameter error on the PROFIBUS (CHK_CFG-Telegram)
Type No. Cause of error Resolution
2 1 Fewer AirLine terminals were configured
than are present in the station.
Add the terminals in the configuration.
2 More AirLine terminals were configured
than are present in the station.
Delete the superfluous terminals from your
configuration or add the missing terminals
to the station.
3 The first byte of the special ID format of
the AirLine terminal contains errors.
Ascertain the precise location of the error
with the aid of the device-specific diagnosis
in your control.
4 Too few bytes from the special ID format
for the last AirLine terminal configured.
Check the ID format.
5 The sum of configured process data for
inputs and outputs on the station is greater
than 184 bytes (DIP8=OFF) or 176 bytes
(DIP8=ON).
Bring together serveral AirLine terminals in
the configuration so that the process data
become compressed (fewer empty bits).
6 The ID code of the configuration does not
match that of the AirLine terminal.
Ascertain the precise location of the error
with the aid of the device-specific diagnosis
in your control. Check the configuration in
the hardware configurator.