Looking for guidance on changing the IP scheme of a FactoryTalk SE program for networking purposes. The original setup had PLCs on a shared network (192.168.254.xxx), but now I need to segment the network due to connectivity changes. For instance, equipment at one location should be moved to 192.168.225.xxx. Despite some unsuccessful attempts today, I temporarily adjusted the network masks to 255.255.224.0 to maintain communication while making the switch. After changing the PLC's IP address and updating the network in rslinx enterprise within FactoryTalk Studio, the system still failed to reconnect. Am I on the right path? Planning to give it another go tomorrow.
Today, significant progress was achieved by reconfiguring the PLC IP addresses and reconnecting the RSLinx. After rebooting, everything started functioning correctly. However, there is a persistent issue with the FactoryTalk directory. The system consists of a client computer running FTview and a "server" computer with a virtual machine hosting the FactoryTalk project. Changing the IP on the virtual machine disrupts the connection to the FT directory on the client. Despite attempts to specify the location, the issue persists. Any advice on resolving this issue would be appreciated.
It is essential to utilize the Ethernet (ETH) driver for inter-subnet routing. ETHIP applies to scenarios where all devices are on the same broadcast domain.
It sounds like you're on the right track. The key here will be to ensure that every component within your network is accurately updated to reflect these changes. Remember, all devices, HMI, PLCs and other endpoints need to be accounted for - update the subnet masks where required. Also, when working with RSlinx enterprise, double check your shortcut configuration, too. They are critical for maintaining connectivity between the PLCs and FactoryTalk Studio SE. Don't forget to restart your devices after making changes as some updates may require a power cycle to properly engage. It's a complex process, so make sure to take detailed notes of all settings prior to getting started. That way, you may revert if need be. Keep on troubleshooting and you'll get it sorted!
Your approach does seem justified, but it might be that you're missing some routing rules after changing the IPs. Remember, the PLC network runs on a strictly predefined IP scheme and routing rules. Changing these may require some more in-depth changes that go beyond just tweaking IPs here and there. That being said, after updating your PLCs IP, make sure you've also updated any associated I/O, HMI terminals, and additional devices related to your network in FactoryTalk Studio. It's almost like changing your home address - you have to inform everyone who sends you mail. Also, resetting the power of your PLCs and peripheral devices after the changes might help with registering the new information. Finally, it's a good practice to backup your project before the changes. Happy networking!
It seems like you've taken some right steps, but changing IP schemes usually also requires you to follow up with changes in your DNS and gateway settings to corroborate the new scheme. I'd suggest you cross check your routing tables to ensure your routes are updated to match your reconfiguration. In terms of the FactoryTalk, ensure that the devices are in the same network path as your FactoryTalk directory. Also, pay attention to subnetting; your mask seems a bit off for a 192.168.225.xxx IP, it’s generally best to use 255.255.255.0 for these range of addresses unless you have a specific reason not to. Best of luck on your retry tomorrow!
It seems you're on the right track! Definitely adjust the Network Mask to make the range available in the PLC's IP. You've also correctly updated the network in RSlinx Enterprise. However, one item you may have overlooked is updating the IP in the FactoryTalk SE shortcuts. Make sure to adjust these to match the new IP of the PLCs. Also, whenever there are changes to the network scheme, it's helpful to double-check the subnet and default gateway as well, to ensure everything is in sync. Hang in there, these network migrations can be a bit tricky at first, but with methodical steps, the process tends to smoothen out.
It sounds like you're doing a solid job troubleshooting the IP reconfiguration! When changing IP addresses, ensure that you're also updating any applicable routing tables or gateway settings on your PLCs and network devices, which might be blocking the new connections. Have you checked the Firewalls or security settings that might be affecting communication too? Sometimes, stepping back and double-checking all the settings after a change can help spot something that got overlooked. Good luck with your next attempt; these network changes can be tricky, but it sounds like you're on the right track!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: To change the IP scheme in FactoryTalk SE, you need to adjust the IP addresses of the PLCs and update the network settings in RSLinx Enterprise within FactoryTalk Studio.
Answer: Answer: If your FactoryTalk SE system fails to reconnect after making IP and network changes, double-check the IP addresses, subnet masks, and ensure that all settings are correctly configured.
Answer: Answer: Temporarily adjusting network masks to maintain communication during IP scheme changes can be a helpful troubleshooting step, but it's important to ensure all devices are properly configured for the final IP scheme.
Answer: Answer: If you encounter connectivity issues in FactoryTalk SE after changing the IP scheme, verify the IP configurations of all devices, check network connectivity, and ensure that all changes are accurately reflected in both the PLCs and FactoryTalk Studio settings.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.