I am faced with the challenge of having to split my 1756-L7x controller into two due to resource usage nearing its limit. While most areas of the plant have their own remote racks, three of them contain cards that need to be controlled by different controllers. Which Rack Connection type should I select on the remote ethernet modules (1756-EN2T and 1756-ENBT) to facilitate this setup? Is it possible to have "Rack Optimization" on one controller and "None" on the other, or do both controllers need to have "None"? Can I set "Rack Optimization" on the first controller and "Listen Only - Rack Optimization" on the second if the second controller only requires input modules on that rack?
Leveraging the Power of Tagging for Improved Online Visibility
One effective approach is to centralize ownership under one controller and establish a system for data exchange between the two controllers. This method enables seamless transfer of information from the first controller to the second one.
alan_505 suggested consolidating ownership under one controller and utilizing the produced-consumed relationship between two controllers to transfer data. I am contemplating this approach and evaluating factors such as reliability and ease of migration. Depending on the details provided in response to my original post (OP), I may opt for this solution.
Is it possible to perform "Rack Optimization" on the primary controller and "Listen Only - Rack Optimization" on the secondary controller if the latter only requires input modules on its rack? The answer is yes, this is the optimal setup. When implementing a "Rack Optimization" configuration, it will take control of the owner connection for all discrete modules within a 1756 chassis. While multi-CPU ownership is not typical, it is crucial to thoroughly document this setup by using labels or creating a diagram near the I/O chassis to clearly indicate which controller owns each module.
In response to Ken Roach's advice on configuring a setup for optimal performance, it is highly recommended to implement the "Rack Optimization" setting to take charge of the owner connection for all discrete modules within a 1756 chassis. While multi-CPU ownership is rare, thorough documentation should be done to indicate which controller owns which modules, with the use of labels or a diagram. Now, what should be done if there are individual discrete output cards in the same remote rack that need to be controlled by different controllers? Would setting "None" for the remote ENBT card connection in each controller's I/O tree be the solution?
In this configuration, you can indeed have one controller set to 'Rack Optimization' and the other to 'None' or 'Listen Only- Rack Optimization' if the second controller only needs to read data and not control the operation. The essential thing is, ensure that only one controller is controlling the I/O, and the other one is just monitoring. Remember to consider your overall network bandwidth to make sure it doesn't get overloaded, especially if you are shifting towards a listen-only setup. The 'Rack Optimization' option tends to reduce unnecessary network traffic, but if the second controller only requires to read inputs, 'Listen Only- Rack Optimization' may work just as well. It's all about optimizing for your specific scenario and needs.
In your scenario, it's certainly viable to have different Rack Connection types on each controller. You can configure one with Rack Optimization and the other with None. Keep in mind that Rack Optimization works best when the controller requires a significant amount of data from the modules on that rack. As for your question about Listen Only - Rack Optimization, this configuration is typically used when you indeed only need inputs from another controller's rack. So yes, setting up Rack Optimization on the first controller and Listen Only – Rack Optimization on the second seems like an excellent approach if the second controller mainly requires input modules on that rack. Just make sure to properly configure your I/O messaging between controllers.
While it's a somewhat tricky situation, it's not impossible to manage. You can indeed have one set to "Rack Optimization" and another controller set to "None". Setting these different configurations for each controller won't result in conflict. The "Rack Optimization" option optimizes the communication between the controller and the I/O chassis. The controller with the "None" setting will likely be less efficient in terms of data communication, but if you're nearing your limit on a single controller, it's a practical compromise. If the second controller only needs input modules, setting it to "Listen Only - Rack Optimization" could also be a viable option. Ultimately, the selection depends on the specific needs and optimization of your plant. Don't forget to make sure your firmware versions are up to date to properly support the configurations.
From my experience, you should be fine using Rack Optimization on one controller and None on the other, provided that the other controller does not need to write to any of the I/O. However, if the second controller does need to write data, you might run into issues with controlling the same I/O from two different controllers. Your idea of setting "Listen Only - Rack Optimization" for the second controller seems pretty viable, assuming the second only requires inputs. Just make sure your major and minor fault settings are appropriately configured in case of any unexpected hiccups.Routing and module configurations always require a bit of puzzle-solving when you're splitting control like this, so don't forget to thoroughly test your setup after changes.
You’ve got a solid plan in mind! When splitting the workload between your controllers, you'll want to ensure that the remote I/O configurations match their intended uses. You can definitely have different rack connection types for each controller; it's entirely possible for one to have "Rack Optimization" and the other to use "None." Just keep in mind that if the second controller only needs to read inputs, "Listen Only - Rack Optimization" could be an effective option since it minimizes unnecessary traffic. This way, you maintain performance while efficiently managing your resources. Just double-check your wiring and communication settings, and you should be good to go!
It sounds like you're in a bit of a complex situation, but it's definitely manageable! You can indeed set different connection types for the remote Ethernet modules for each controller. Having “Rack Optimization” on one controller while setting the other to “None” is completely feasible; they don’t need to match as long as both controllers can communicate properly with the modules they're intended to control. As for your second question, using "Listen Only - Rack Optimization" on the second controller can work perfectly fine too. Just make sure that the configuration matches the intended functionality you need from each controller and the associated modules. Remember to test your setup thoroughly to ensure everything communicates as expected!
âś… 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: - The recommended Rack Connection type for splitting a 1756-L7x controller with remote racks depends on the specific setup and requirements. It is essential to consider factors such as resource usage, card control, and controller configurations to determine the most suitable Rack Connection type.
Answer: - Yes, it is possible to have different Rack Connection types on remote ethernet modules for different controllers. This flexibility allows for customized configurations based on the specific needs of each controller and the remote racks they are connected to.
Answer: - Yes, it is possible to set "Rack Optimization" on one controller and "None" on the other controller in a split setup. This configuration can be useful when one controller requires optimized rack communication while the other does not, allowing for efficient resource allocation and control.
Answer: - Yes, controllers can have different Rack Connection settings if one controller only requires input modules on a specific rack. In such cases, setting "Rack Optimization" on one controller and
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.