Some content on this site is available only to logged-in subscribers. Contact Us for information on becoming a subscriber.

InSource.Solutions | InSource Training | InSource Client Portal
InSource Solutions Logo
Log In Sign Up
InSource.Solutions InSource Training InSource Client Portal Log In Sign Up
  • Home
  • AVEVA Communication Drivers
  • AVEVA Communication Drivers Tech Notes

TN - IO - 26090314 Unsupported ABCIP OI Firmware Versions

Last updated: September 3rd, 2026

Description

  • Author: Dan Hojecki
  • Published: September 3rd, 2026

Details:

  • Document Version: 001
  • Applies to Version(s): OI ABCIP 2023.1 and newer (Communication Drivers Pack)

 

 

Description  

AVEVA's approach to testing ABCIP versions has evolved, but if a version is not listed in the Technology Matrix it does not necessarily mean it is incompatible.

 

Solution Steps:

Maintaining the lab infrastructure to test and support infinite legacy firmware versions was becoming unsustainable. In some cases, the hardware required to test old firmware is no longer obtainable, so when an old lab PLC fails, they cannot replace it. The decision was made to test and support firmware versions that are currently supported by Rockwell at the time of ABCIP releases. If new firmware comes out after release, they will test it against existing ABCIP releases that are still in Full Support per the Software Support Lifecycle Policy and the Technology Matrix will be updated accordingly. The thought is that if a firmware version is not supported by Rockwell, AVEVA should not be supporting communication to that firmware version. Running old firmware can also be a cybersecurity vulnerability.

Newer ABCIP versions will likely work with older firmware, but it is not guaranteed nor supported. If Product Development suspects a problem is related to compatibility with old firmware, it will be the responsibility of the customer to test the reported issue against supported firmware to rule that out first. Running ABCIP with unsupported firmware should only be a temporary scenario until the PLC can be updated.

                                     _____________________________________________________________________________________________________

 

incompatible outdated
Give feedback about this article

Recommended articles

[ISS Support Case] OI ABCIP support for SLC500 Firmware 30

Direct email: I would like to find out what is the latest OI server that will communicate with Studio 5000 firmware 33, SLC500 and compact logic firmware 30. I read from Insource website and found out the OI ABCIP vG2.0 only supports up to Firmware 30. Thanks https://knowledge.insourcess.com/?title=Visualization_and_Supervisory_Control%2FDA_%2F%2F_OI_Servers%2FMaximize_%26_Optimize%2FTN_DAS163_DA_and_OI_Server_Hardware_Compatibility_Guide.

Read More

[ISS Support Case] ABCIP connection to 1756L84ES Poor Performance

Direct Email. REF CASE: 8390 and SR 960275396. AVEVA indicated there are some known issues reported by Rockwell related to Firmware version 32.xxx, including v32.013. FAQ 000021344 CompactLogix 5380 v32.014 Release Notes . Per AVEVA's recommendation the client upgraded firmware resulting in even worse performance. "....we had some down time on the production line yesterday, so we took that opportunity to upgrade our controllers to from V32.013 V33.015. That turned out to be *worse*! The data gaps we were reading we much more pronounced. So we reverted back to V32 on the controllers to get it back to the way it was before. I then ran an experiment this morning, turning off all of the HMIs on the line, and then stopping our data collection and OPC server. Turning off the HMIs made a significant impact on the communication (MSG Class 3) utilization. Turning off the data historian made a little impact, and turning off the OPC Server did not affect the utilization at all. I then turned the OPC Server and the data historian back on, and then turned the HMIs back on one at a time. With each HMI, the data gaps increased. At this time, I am seeing a gap of about 0.4-0.5 seconds, occurring regularly every 2 seconds. Im still trying to understand what could be causing this periodic interruption.''

Read More

[ISS Support Case] Getting Bad Quality in an Object Troubleshooting ABCIP

Created an object in app server and cannot get a good quality read on it. wwClient tried to validate items but adds and item still gets bad quality End device ControlLogix PLC (some tags are working) Tags were previously working / existing system. Work was done on the PLC and then this issue surfaced all point are discrete deployed DDESLC CORE G-2.1 v5.1.0 ABCIP G-2.0 v7

Read More
Support Icon

CONTACT SUPPORT

How to reach us

10800 Midlothian Turnpike Tpke, Suite 209, Richmond, VA 23235

1.877.INSOURCE

Technical Support - 1.888.691.3858

Contact Us

  • InSource Solutions
  • InSource Training
  • InSource Client Portal
  • Log In
InSource Solutions Group Logo

© 2026 InSource Solutions. All Rights Reserved.

Knowledge Base Software powered by Helpjuice

Expand