Hi,
by now I’m not completely sure what’s happening.
4808 is a online protocol status that means more or less “the communication driver is unable to reach the PLC configured for online connection”.
Status 4808 can happen for many different reasons, e.g. “wrong online connection in Automation Studio”, “issues with the physical network configuration”, “project dependent, non-default online settings inside the PLC”, “too less timeout”, and more things like that.
Therefore, regarding to your description, I’ve some additional questions that maybe help me to understand this specific issue:
-
Because of the used IP address is pingable, I assume that the initial setup of the Automation Runtime is already done (e.g. by offline installation), am I right?
-
SDM is also not reachable, what is the error in the browser? Is it ERR_CONNECTION_TIMED_OUT, or ERR_CONNECTION_REFUSED, or something else?
-
You wrote “I have assigned to each device ETH port the same IP addess” - does that mean, that both ETH1 and ETH2 are in the same subnet? If yes, please try to setup the interfaces in different subnets.
More then one ETH interface in the same subnet could cause communication problems, all ETH interfaces of the PLC have to be configured in different IP subnets (e.g. ETH1 192.168.1.x / 255.255.255.0 and ETH2 in 192.168.2.x/255.255.255.0). If both interfaces are in the same IP subnet, maybe the response data for a network request is sent to the “wrong” ETH interface.