I moved the PLC, and connected it to the switch where my laptop is connected, and everything works fine. One is the remarks about the network getting in the way of Ethernet/IP are correct.
Or you could just get a LabVIEW RT system and have that be the one talking to the PLC.Īfter my last posting I discovered two things. I'm guessing you won't want to go down this route. Then you can create the EtherNet/IP session in LabVIEW with a special qualifier added to the session name ("sessionName :LocalIP=192.168.1.1") to indicate a single local IP address to bind to, where you would bind a different address from the one Rockwell is using. You could possibly use VMware on the machine and have the two "systems" isolated that way.Ī more complex way would be to add multiple IP addresses to your system (either with multiple NICs if you use DHCP, or just manually add multiple IPs if doing static IP addressing) and then somehow force the Rockwell software to bind only to a specific IP address instead of all of them (I have no idea if this is possible in their software). Generally RSLogix just communicates with the PLCs using explicit messaging, which would not require it to listen on that port.
It shouldn't need to listen on that port unless it is expecting to be the target of communication, which I don't think you would ever do. Unfortunately, there is likely no easy way to run both unless you can figure out a way to disable the Rockwell driver from attaching to that port. So if I understand you correctly, you had a rung on the PLC that was essentially doing a loop-back of data? And everything is working now when RSLogix is closed?
0 kommentar(er)
