Support Ended for InGear NET.LOGIX Driver

At DMC, we strive to provide our clients with stable, up-to-date solutions that stand the test of time. However, in our ever-changing world, components sometimes reach the end of their lifespans, or EOL.

Such is the fate of the InGear NET.LOGIX Driver.

This post explores this recent shift in the tech ecosystem; what exactly happened to InGear, why support has ended, and what you should use instead if your application still relies on NET.LOGIX today.

InGear Drivers End-Of-Life

Once a common choice for communicating between .NET software and Allen-Bradley LOGIX series PLCs, all software drivers have been fully discontinued. This isn’t a “maintenance mode” situation; driver development has stopped, and the license servers used to establish new development environments are no longer available, making ongoing support impossible.

Where did InGear go?

InGear NET.LOGIX was designed at a time when .NET drivers were the primary method for communicating with Allen-Bradley Logix controllers. Since then, the ecosystem has evolved:

• Rockwell has extended its native support for other communication options.
• Open-source libraries like libplctag have gained greater adoption among developers.
• Security and deployment expectations have increased significantly, changing driver demands.

With this shift, InGear NET.LOGIX’s developer decided that it was better to focus its efforts and investments in other areas.

And don’t feel bad if you missed the announcement that support for InGear NET.LOGIX driver has ended. There was no formal public EOL date; their website simply displays an unprotected 404 page with no documentation, downloads, or publicly available support channels.

Which Driver Should I Use Now?

If your application still relies on InGear Net.LOGIX, the good news is, you’re not stuck. We have successfully migrated systems to modern, actively maintained alternatives. In a previous post, we walked through a free and open-source option: Replacing the NET.LOGIX InGear Driver with libplctag.NET, including considerations to make about system architecture as well as migration tips.

This is just one of the many instances in which DMC engineers regularly modernize PLC communication layers as part of broader automation and application development projects, helping teams reduce technical debt and maintain system reliability and efficiency.