Log Outputs of the Protocol Stack
Log outputs are the only way for the user to monitor the behavior of the integrated protocol stack.
Tip
By setting the log filter, more outputs are written in the logger than provided by the default setting. To do this, the value Logger.0.Filter is set to 0xFFFFFFFF in the configuration file of the RTE CODESYSControl_User.cfg, in the segment [CmpLog].
*** SysSocketlwIP -> No network-adapter for LwIP available!None of the network adapter drivers were loaded because they either do not exist in the configuration (component list) or they were not installed for at least one network adapter by means of the Windows Device Manager.
*** SysSocketlwIP -> x network-adapters for LwIP available.At least one network adapter is available for use by the integrated protocol stack.
*** SysSocketlwIP -> Switched to Winsock, use of unknown adapter! Winsock: 0xxxxxxxx.A socket with the handle address after the colon was passed to the IP stack of Windows for further use. In most cases, the cause is a call from SysSockBind or SysSockSendTo to an adapter address unknown to the internal protocol stack, such as 127.0.0.1 (localhost) or 0.0.0.0 (ANY_ADDR).
The output of these kinds of logs is normal when starting the runtime system because internal components such as the OPC UA server, the web server, or the CmpBlkDrvTcp link to localhost/ANY_ADDR.
*** Error: SysSocketlwIP driver -> local receive buffer overrun.If the runtime system is extremely busy (for example due to IEC tasks which consume more than 80 or 90 percent of the total available computing power), then it may happen that received Ethernet frames cannot be evaluated in time by the protocol stack before the receive buffer is full. In the case of UDP, this data is lost and a repetition depends on the overlying protocol. For TCP connections, a block repetition is provided.
Other
*** Error…log outputs should not occur and if necessary should be reported to the support team.