S4TUX Posted December 5, 2023 Report Posted December 5, 2023 I recently started working with the built in Unitronics PLC US7-B5-B1 and I am unable to detect the PLC when connected via ethernet. It works fine when connected via USB, I can detect and download a new software just not via ethernet. Can anyone advise me on how to troubleshoot this? My end goal is to broadcast some tags using OPCUA and I installed an OPCUA client on my PC to test the connection but am not able to establish connection with the PLC. I figured troubleshooting the unilogic detection issue my help me resolve the OPCUA issue.
MVP 2023 Flex727 Posted December 5, 2023 MVP 2023 Report Posted December 5, 2023 1 hour ago, S4TUX said: Broken link.
S4TUX Posted December 5, 2023 Author Report Posted December 5, 2023 1 hour ago, Flex727 said: Broken link. It is an image showing the discovery window that pops up when you click on PC-PLC communication in Unilogic.
MVP 2023 Flex727 Posted December 5, 2023 MVP 2023 Report Posted December 5, 2023 Is your PC on the same subnet as the PLC (10.2.5.xxx)? Also, are you plugged into the correct Ethernet port on the PLC? Are you using an Ethernet hub or a crossover cable?
S4TUX Posted December 5, 2023 Author Report Posted December 5, 2023 Not sure how to make that determination but when I do IPconfig in CMD, I see my subnet listed as 255.255.255.0 and that of the PLC listed as 255.255.0.0 (not the same). On the PLC IP panel settings in UniApps, I see the subnet mask listed as 255.255.255.0 same as mine.
MVP 2023 Flex727 Posted December 5, 2023 MVP 2023 Report Posted December 5, 2023 1 hour ago, S4TUX said: I see my subnet listed as 255.255.255.0 That is your Subnet MASK, not your subnet. Your subnet is 192.168.0. You need to make the subnet match between the PC and PLC (the first 3 octets must be the same and the 4th octet different). The subnet of the PLC, as you show above is 10.2.5. Also, are you certain that 10.2.5.83 is the IP address of the PLC? Even so, go into UniApps and change it to 192.168.0.xxx (anything other than 71). Or, you can go into your PC network settings and change your PC IP address to 10.2.5.xxx (anything other than 83). Once you do that you should be able to communicate if you are plugged into the correct port with a crossover cable or through an ethernet hub.
MVP 2023 Flex727 Posted December 5, 2023 MVP 2023 Report Posted December 5, 2023 Also, don't get confused between your wired ethernet address and your wireless address on your PC. When you do IPConfig in a command window, confirm which address is which since they are usually on different subnets. You want to make sure you use your wired IP address subnet. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now