OkiePC
Lifetime Supporting Member
If you are connecting to an exisitng PLC/HMI for the purpose of uploading running code, you need to set your laptop IP configuration to a compatible address. BootP should have nothing to do with this.
Then, you may need to stop and start RSLinx (or add a new driver and give it a name for this project), and configure it to be compatible.
I recommend adding a new Ethernet/IP driver for this project. It will find everything on the PC default NIC card that is on the same subnet as the NIC configuration. You can follow the DOS method above or change the IP config from within windows. I normally don't even have to stop RSLinx, but I do usually kill any old drivers and recreate them after a new driver is named with that IP scheme.
BootP should not enter the picture until it comes time to set up a brand new Compactlogix with firmware before downloading.
I scanned the threads quickly, so I may have missed this, but also, the existing IP addresses, and subnet masks may come into play. Don't use a duplicate IP address...very strange things will likely happen.
Then, you may need to stop and start RSLinx (or add a new driver and give it a name for this project), and configure it to be compatible.
I recommend adding a new Ethernet/IP driver for this project. It will find everything on the PC default NIC card that is on the same subnet as the NIC configuration. You can follow the DOS method above or change the IP config from within windows. I normally don't even have to stop RSLinx, but I do usually kill any old drivers and recreate them after a new driver is named with that IP scheme.
BootP should not enter the picture until it comes time to set up a brand new Compactlogix with firmware before downloading.
I scanned the threads quickly, so I may have missed this, but also, the existing IP addresses, and subnet masks may come into play. Don't use a duplicate IP address...very strange things will likely happen.
Last edited:
