Hi,
Okay, your router acts as a DHCP server on the network 10.0.0/24
Because of the whole network is set as DHCP range, it’s hard to say what IP adresses are already in use by other devices.
But in one of the linked screenshots I can see, that you used the same IP address for your windows adaoter and inside the PLC - in both cases 10.0.0.101
But IP addresses have to be different but inside the same network.
So, having 10.0.0.101 inside the PLC you must not use that IP on the Windows side but a different one, for example 10.0.0.102
To use static IPs safely inside your network, you should also change your routers DHCP range to get a area of free IPs for static use.
Be aware: I don’t know your network and the number of devices used inside, therefore I can’t say how many dynamic IPs you need!
But, as an example: if you set “2” as start and “100” as end IP in your router, then IP adresses from 10.0.0.2 - 10.0.0.100 are used for DHCP, and adresses from 10.0.0.101 - 10.0.0.254 are free for static use.
The strange thing that I can’t explain is: when the PLC was set to DHCP client, and also your Windows device was set as DHCP client, and both devices were connected to the router, then a communication should have been possible before… I don’t know why that hasn’t worked.
Of course you then don’t know the IP address your PLC got from the DHCP server, and if “search for PLC” doesn’t work for whatever reason, it’s not so easy to determine the IP address.
In the case that your router can display the DHCP leases, you could check it for devices with MAC address beginning with 00:60:65… this should be a B&R device.
Or you could try to follow this guide:
But all of this is about determining an unkown IP address.
I would suggest to try a valid static IP addresses setup first, to eliminate other issues.
Best regards!