TR-Electronic CDV582 - Page 144

Troubleshooting and diagnostic options
 TR-Electronic GmbH 2019, All Rights Reserved Printed in the Federal Republic of Germany
Page 144 of 154 TR - ECE - BA - GB - 0139 - 02 11/21/2019
Continued
Error type
Diagnostic message / Meaning
Solution
F:0067
d
Safety watchdog time value is 0 ms
(F_WD_Time)
- Valid monitoring times: 10…10000 ms,
see Chapter 6.8.8 on Page 136.
F:0068
d
Parameter F_SIL exceeds SIL from
special device application
- The set value (SIL1, SIL2, SIL3,
NoSIL) must correspond to the value
of the device application,
see Chapter 6.8.2 on Page 135.
F:0069
d
Parameter F_CRC_Length does not
match the generated values
- This parameter is not adjustable and
can only be preselected by selecting
the corresponding safety-related
submodule:
(BP) = 3-Byte-CRC
(XP) = 4-Byte-CRC
F:0070
d
Version of F parameter set incorrect
- The requested version does not match
the implemented version. The
measuring system cannot be operated
with this application (incompatible),
see Chapter 6.8.6 on Page 135.
F:0071
d
Data inconsistent in received F-
Parameter block (CRC1 error)
- The checksum value calculated for the
set safety-related F-parameters
(F_Par_CRC) is incorrect.
see Chapter 6.8.10 and 6.8.11 on
Page 136.
F:0072
d
Device-specific or unspecified
diagnosis information, see manual
Different iParameter settings were
detected for the shared device modules.
- The iParameter settings of all
configured modules must be identical,
see Chapter 8 on Page 138.
F:0073
d
Save iParameter watchdog time
exceeded
- Check the parameterization of the iPar
server.
F:0074
d
Restore iParameter watchdog time
exceeded
- Check the parameterization of the iPar
server.
F:0075
d
Inconsistent iParameters
(IParCRC error)
- The checksum value calculated for the
set safety-related iParameters
(F_iPar_CRC) is incorrect,
see Chapter 6.8.9 and 6.8.11 on
Page 136.
F:0076
d
F_Block_ID not supported
- Check the parameterization of the
PROFIsafe communication.
F:0077
d
Transmission error: data inconsistent
(CRC2 error)
- Try to localize the error using
diagnostic variables (depending on the
control).
- Check whether the PROFINET
connection between F-CPU and
measuring system is faulty.
Continued on next page