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.
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!
It seems like you've done quite a comprehensive upgrade. Now, about the issue with the IF16 module, it could potentially be related to the firmware compatibility or some settings might have been reset during the replacement. Remember, IF16 modules on an AENTR need to have their input data arranged in a different manner than on an AENT. So, if the code was not updated to reflect this, it might be the root of your problem. Also, look at the jumpers on the IF16 itself, make sure they're correctly set for your voltage/current requirements. I'd recommend revisiting the module configuration in RSLogix 5000. Hope that helps.
It's quite possible that the new EN2T and 1794-AENTR modules may have a different default scaling setting or configuration compared to the older modules they replaced. I recommend checking the scaling parameters of the IF16 module - if they have been reset or changed during the upgrade process, it could potentially explain the issue you're experiencing. Additionally, you might want to review the firmware version of your new modules to ensure compatibility with existing hardware and software. Remember always to backup your configuration settings before making any changes like this in the future.
It sounds like you've made some significant upgrades, and it's not uncommon to run into scaling issues after replacing modules like that. The transition from AENT to AENTR modules could affect the configuration settings and how the I/O is interpreted, especially if the new modules handle data differently or if there were changes in the way analog values are processed. I’d recommend double-checking the configuration settings for the IF16 module, as the scaling parameters may need to be adjusted to align with the new architecture. Additionally, look at any updated manuals or documentation for the AENTR modules; there could be new features or requirements that impact how data is being communicated. Good luck!
It sounds like you've made quite a few upgrades! The AENTR modules are a bit different from the older AENTs, especially in terms of how they handle communication and possibly the scaling of inputs. One thing to check is whether the scaling settings in your program still align with the new configuration since signal types and scaling factors can vary between modules. Additionally, make sure that the input configuration channels on the IF16 are properly set up to match the new data format that the AENTR might be providing. Sometimes, a mismatch in expected input types or ranges can lead to scaling issues. If everything seems correct, I’d recommend checking the firmware version as well, just to ensure compatibility throughout your system. Good luck!
It sounds like a significant upgrade! The transition from AENT to AENTR modules often changes how data is processed and communicated, especially regarding protocols and scaling. I'd recommend checking if the configuration settings for the IF16 module were updated accordingly after the change, as the new AENTR might interpret inputs differently. Also, ensure that any scaling values in your logic or control routines align with the new configuration - sometimes a simple mismatch can lead to unexpected behavior. If you haven’t already, reviewing the documentation for both the new modules and the IF16 might reveal some tweaks you need to apply. Good luck!
It sounds like you’ve been through quite the upgrade process! Since you replaced the AENT modules with AENTR ones, you may want to double-check the configuration settings for the IF16 module. The newer AENTR modules have different characteristics, which can impact the communication and scaling of connected I/O. Ensure that the parameters in your controller for the IF16, especially the data type and scaling settings, align with your new setup. Sometimes a simple mismatch in scaling configuration, or an overlooked firmware update, can lead to those odd input issues. Good luck, and I hope it’s an easy fix!
✅ 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 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.
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.
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.
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.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.