Safety modules: Data type of the instantiated function module has changed (corrected from controller device description V01.08 / V03.21.02)

Corrected from: 
Library:   L_EtcSlaveConfig  from V03.25.00

The library L_EtcSlaveConfig becomes effective via referencing in the controller device description files:
  • Controller (3200C, p500, c300, p300):   from controller device description V03.21.02
  • Controller (c520, c550):                            from controller device description V01.08.00              
(Update via Easy Package Manager with Service Pack)
 
Response of the new version:
The function blocks automatically instantiated when inserting a safety terminal now support the original data type (ETCSlave) again.


What happens?
When a safety terminal is inserted into the EtherCAT device tree, a function block is automatically instantiated to provide further information about the EtherCAT slave, e.g. the physical slave address.
The basic type of this function block has changed in the meantime, so that function blocks created with older library versions that access the EtherCAT slave FB can no longer be compiled.

When does the behaviour occur?
  • Use of an EtherCAT safety terminal and
  • certain interfaces of the EtherCAT slave function block are to be accessed from the application and
  • the accesses were already created with older library versions.
Which products are affected? 
Library: L_EtcSlaveConfig   V03.24.00

The library L_EtcSlaveConfig becomes effective via referencing in the controller device description files:
  • Controller (3200C, p500, c300, p300):    only controller device description V03.21.01
  • Controller (c520, c550):                             only controller device description V01.07.xx

Short-term measures / evaluation / recommendations:


Automatic Translation

URL for linking this AKB article: https://www.lenze.com/en-de/go/akb/202200192/1/
Contact form