Warning Status.Interfaces.Ethernet.4.1 in output.log

PLCnext Technology & PLCnext Controls
1

Using a 3152 i’ve sometimes the following warning in the output.log.

27.07.22 14:42:30.388 Arp.Device.Interface.Internal.DeviceStatus WARN - DeviceStatus: Ident "Status.Interfaces.Ethernet.4.1.Duplex" not found``27.07.22 14:42:30.389 Arp.Device.Interface.Internal.DeviceStatus WARN - DeviceStatus: Ident "Status.Interfaces.Ethernet.4.1.Baudrate" not found``27.07.22 14:42:31.397 Arp.Device.Interface.Internal.DeviceStatus WARN - DeviceStatus: Ident "Status.Interfaces.Ethernet.4.1.Link" not found``27.07.22 14:42:31.398 Arp.Device.Interface.Internal.DeviceStatus WARN - DeviceStatus: Ident "Status.Interfaces.Ethernet.4.1.Duplex" not found``27.07.22 14:42:31.398 Arp.Device.Interface.Internal.DeviceStatus WARN - DeviceStatus: Ident "Status.Interfaces.Ethernet.4.1.Baudrate" not found27.07.22 14:42:32.383 Arp.Device.Interface.Internal.DeviceStatus WARN - DeviceStatus: Ident "Status.Interfaces.Ethernet.4.1.Link" not found``27.07.22 14:42:32.385 Arp.Device.Interface.Internal.DeviceStatus WARN - DeviceStatus: Ident "Status.Interfaces.Ethernet.4.1.Duplex" not found

Why this message appear and disapear? What is Ethernet 4 (Only 3 interfaces on the 3152).
How to solve it.

Alexandre

2

I just discovered than pressing the stop button of plcnext cockipt , will trigger the warning flood of the output.log

3

I think this only occurs when PLCnext Engineer is connected to the device. If I remember correctly, PLCnext Engineer queries the status of all possible Ethernet ports, including the left-side extension, even if it the left-side extension is not installed.
I am currently checking this with the PLCnext Engineer support team.

4

I think this only occurs when PLCnext Engineer is connected to the device. If I remember correctly, PLCnext Engineer queries the status of all possible Ethernet ports, including the left-side extension, even if it the left-side extension is not installed.</p>I am currently checking this with the PLCnext Engineer support team.</p>

I confirm it’s related to PLCnext Engineer, on 2022.3 and 2022.6. Problem appear depends what we doing in plcnext and stop when i close plcnext. Annoying bug when we use Output.log to debug app

5

In firmware version 2022.6, which will (hopefully) be released later this month, this issue is addressed by only logging the first error of this type, and then not logging subsequent errors of the same type.
Ultimately this problem should be fixed in a future version of PLCnext Engineer.