T5BEV - Proposed solution: Add check for Sock != INVALID_SOCKEt in T5BEVFrame_SendEventList or _T5BEVFrame_Send
Description
The Service Engine under Linux closed unexpectedly in a test scenario.
The issue has been addressed and a check for Sock != INVALID_SOCKET has been added.
The behavior is now as expected.
To benefit from this fix:
- Update your zenon Software Platform to the latest build of zenon 15 or higher.
Item ID: 305068
Version: 15.00 Build: 481184
Related Articles
'T' cannot be translated
Summary In the module Batch Conrol there are several spots where durations can be configured. The format of these properties is '0T 00:00:00' where 'T' stands for the German word 'Tag' ('day' in english). It is, unfortunately, not possible to ...
FAQ: How can I monitor and react on the communication status of my devices with zenon?
Data quality is very important to the integrity of a HMI or SCADA system. As such, zenon has numerous ways to monitor the communication status of different devices within your automation environment. Here are some options that you can use in your ...
zenLogSrv: no TCP keep alive for listening socket
Description The TCP server of zenLogSrv.exe did not send TCP keep alive messages to check if the TCP connection is still available. The issue has been addressed by automatically enabling TCP server now automatically enables the TCP keep alive for the ...
Remote-Transport: no TCP keep alive for listening socket
Description The TCP server of process zensysSrv (used for remote transport) did not send TCP keep alive messages to check if the TCP connection is still available. The issue has been addressed by automatically enabling TCP keep alive for the ...
In Docker-Compose: no TCP keep alive for listening socket, port 50780
Description In Docker the TCP server of process zenLogSrv.exe did not send a TCP keep alive to check if the TCP connection is still available. The issue has been addressed by automatically enabling TCP server now automatically enables the TCP keep ...