How Changing Communication Modules Impacts IF16 Scaling

Question:

Recently, we upgraded an ENBT module to an EN2T in both our Main ControlLogix Rack, which houses an L82E processor, and a remote Rack connected to multiple 1794 racks. Additionally, we replaced 3-1794-AENT modules with 1794-AENTR modules. Following the upgrades, we encountered a issue with the scaling of inputs on an IF16 module in the Remote Rack. Any insights on how the module replacement may have affected these analog inputs? Any suggestions or advice would be greatly appreciated. Thank you in advance.

Top Replies

It appears that it is not possible to simply modify the cards in the project tree; they must be deleted and re-created. It seems that the ENBT was deleted and replaced with the EN2T, and the AENT was replaced with the AENTR in a similar manner. It is likely that the configuration for the IF16 was not properly set after the module was added to the tree. If you have a previous version of the program, you can compare the settings in that project with the current configuration.

Are you unable to locate a 1794-IF16 module? Is your IF16 installed in a remote 1756 chassis, or do you have a different input module in the Flex IO chassis? While you cannot alter an existing module, upgrades can be done without removing any data. It may require going offline to download, which can be a little cumbersome, but it's a simpler alternative to deleting and re-inserting. In a recent project, a L81 controller with an ENBT in slot 2 and a 1794-AENT on the network was successfully configured. Adding an EN2T in another slot and transferring the 1794 rack was easily done. Module transfer between chassis, such as from ENBT to EN2T or from AENT to AENTR, proved to be seamless. Ensure to update the slot/IP address to match the old configuration and remove any unused adapters. The only issue that may arise is with MSG instructions pointing to specific modules, which will require reconfiguration. It is recommended to compare settings with an older version of the program.

MikeyN mentioned that there is no direct way to change the cards in the project tree without deleting and recreating them. It appears that someone deleted the ENBT and replaced it with the EN2T, and the same process was followed for the AENT to AENTR. It is likely that the configuration for the IF16 module was not set to the same settings as before when adding it to the tree. To avoid this issue and maintain module configurations, it is recommended to add the new communication module first, transfer existing modules from the old to the new one, delete the old module, and then configure the IP and name of the new module to match the old one. If you still have an older version of the program, you can compare the settings from the previous project to the current one for reference. Edit: Joseph made a similar suggestion earlier.

It sounds like you've made a pretty significant hardware upgrade. The issue with the scaling of inputs on the IF16 module might have to do with the transition from ENBT to EN2T and AENT to AENTR. EN2T, for instance, has a faster data rate than ENBT, and AENTR has dual port capabilities while AENT does not. Changes in data rate and how the data is handled could potentially cause issues with input scaling. I'd suggest revisiting the configuration of your IF16 modules, specifically the properties related to scaling. Sometimes a significant hardware change warrants a review of those settings to ensure they still align with the new modules. Also, verify the firmware version compatibility amongst the replaced modules to ensure a smooth communication. Hope this helps!

More Replies →

Streamline Your Asset Management
See How Oxmaint Works!!

✅   Work Order Management

✅   Asset Tracking

✅   Preventive Maintenance

✅   Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

To add a comment, please sign in or register if you haven't already..   

Frequently Asked Questions (FAQ)

FAQ: 1. How might changing communication modules, such as upgrading from an ENBT to an EN2T and replacing 1794-AENT modules with 1794-AENTR modules, impact the scaling of analog inputs on an IF16 module in a Remote Rack?

Answer: - The changes in communication modules may affect the way data is transmitted and processed between the devices, potentially leading to issues with scaling analog inputs on the IF16 module.

FAQ: 2. What could be causing the scaling issue on the IF16 module following the module replacements in the ControlLogix system?

Answer: - The issue with analog input scaling on the IF16 module could be due to compatibility issues, configuration changes, or communication settings that need to be adjusted after the module replacements.

FAQ: 3. How can the scaling issue on the IF16 module be resolved after upgrading communication modules and replacing modules in the ControlLogix system?

Answer: - To address the scaling issue, it is recommended to review the configuration settings of the IF16 module, verify the communication setup between the devices, and ensure that the replacement modules are properly configured and compatible with the system.

FAQ: 4. Are there specific troubleshooting steps or best practices to follow when encountering scaling issues on analog inputs after changing communication modules in a ControlLogix system?

Answer: - When facing scaling problems post-module replacements, it is advisable to check for firmware updates, validate the module configurations, inspect the wiring connections, and consult the device manuals or technical support for further guidance on resolving the issue.

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo  â†’