ABB AC500-S Safety User Manual page 402

Usage of safety CPU with V3 non-safety CPU PM56xx
C.5.2.3 Troubleshooting
ID
1.
2.
3.
4.
5.
6.
402
NOTICE!
If you use the compatibility mode
V2 to AC500 V3 (compatibility mode)" on page 400, refer also to the trouble-
shooting for cyclic non-safe data exchange with AC500 V2
"Cyclic non-safe data exchange" on page 383.
Behavior
Cyclic non-safe variables
not updated in safety
and/or non-safety CPU.
Safety CPU cycle time too
high for the given applica-
tion.
Variable can't be used in
application because it is
not defined or variable is
not listed in "Input Assis-
tant".
The used size of a variable
is bigger than expected.
Build errors.
Variable in the table is not
added.
3ADR025091M0208, 12, en_US
Ä Appendix C.5.2.1 "Migration from AC500
Potential cause
Configuration has not been
updated.
Amount of cyclic non-safe
data is too big.
Configuration has not been
updated.
In some cases, one or more
fill bytes are required to fulfill
the data alignment. This is
done automatically in
Automation Builder.
Inconsistent internal data.
Missing or wrong values for
the variable definition.
Ä Appendix B.5.2
Remedy
Clean and build/rebuild non-
safety CPU application.
Create safety configuration
data. Check for error mes-
sages. Login to non-safety
and safety CPU and down-
load the applications.
Check if configured variables
are really necessary for the
particular use case. Reduce
the number of variables to
increase the performance.
Clean and build/rebuild non-
safety CPU application.
Create safety configuration
data. Check for error mes-
sages.
Reorganize the variables in
the used DUTs. Try to use
the biggest data type at first.
Bad example:
● VAR0 : BYTE
● VAR1 : DWORD
● VAR2 : BYTE
● VAR3 : WORD
Good example:
● VAR1 : DWORD
● VAR3 : WORD
● VAR0 : BYTE
● VAR2 : BYTE
Clean the non-safety appli-
cation and build it again.
Enter at least variable name
"Variable (CPU)" and type.
These values are manda-
tory.
2020/06/19