PLC logbook contains debugging information (fixed from V1.6)

Corrected from:
Cabinet Controller c520 V1.6
Cabinet Controller c550 V1.6
Cabinet Controller c750 V1.6

Response of the new version:
The controller does not write debugging information to the PLC logbook when an OPC/UA client accesses variables of the controller.

What happens? 
The PLC logbook of the controller is filled with debugging information, e.g.:
Error ID 21222: AxesGroupInErrorStop

A dialogue appears in the PLC Designer with the message:
The current log process has been stopped to prevent memory shortage.

When does the behaviour occur? 
The behaviour described above occurs when an OPC/UA client accesses variables of the controller. After a short time, several 1000 debugging entries are already visible in the PLC logbook on the 'Log' tab of the controller.

Which products are affected? 
Cabinet Controller c520
Cabinet Controller c550
Cabinet Controller c750

Short-term measures: 
Use the controller logbook on the 'Diagnostics' tab of the controller. Debugging messages are not entered here.
 
Evaluation / recommendations:
When accessing variables of the controller via OPC/UA, a large number of entries are generated in the PLC logbook of the controller. Due to the large number of entries, it is difficult to analyse a malfunction in the machine using the PLC logbook. Alternatively, the controller logbook can be used for this purpose.

Automatic Translation

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