Version 35 works with both, but Rockwell recommends FactoryTalk LinX for all new Ethernet/IP projects. RSLinx Classic remains for legacy serial/DF1 communications.
Studio 5000 Version 35 generally considered a solid, mature release
that is preferred by many users over the newer Version 36 because it retains traditional instruction naming (e.g., keeping instead of the newer
). It is particularly strong for process and motion applications due to enhanced virtualization and expanded hardware support. Key Features & Enhancements Process Industry Focus : Expanded SequenceManager
support for 5x80P controllers and new built-in process instructions ( ) for easier integration with PlantPAx. Virtualization : Introduced Axis-Test Mode
, allowing for the testing of Kinetix, PowerFlex, and iTRAK motion devices without physical hardware using FactoryTalk Logix Echo. Improved Downloads studio 5000 version 35
: Users report significantly faster and more robust download speeds when using FactoryTalk Linx
as the communication software compared to the older RSLinx Classic. Modern Interface
: Includes a modern, web-based UI for Add-On Profiles (AOP) to provide a consistent configuration experience. Safety Signature Improvements
: Safety tag values no longer impact the safety signature on GuardLogix 5380 and 5580 controllers, allowing online edits without full downloads. Rockwell Automation Known Issues & Considerations I/O Tree Bugs
: Some users reported that v35 initially "broke" I/O trees for certain devices; however, patches released in 2024 (e.g., for 1756 Analog I/O) have addressed many of these module profile errors. Compatibility Conflicts Version 35 works with both, but Rockwell recommends
: There is a documented conflict with CodeMeter Runtime (often installed with SICK software) that can cause v35 to fail to open with an afutil.dll Performance Requirements
: While it can run on lower specs, 8 GB of RAM and an Intel Core i5 are highly recommended to avoid sluggishness or "stuttering" during operation. Release Note - Rockwell Automation
This review is structured to help engineers, system integrators, and maintenance technicians decide whether upgrading is worth the time and potential headaches.
Version 35 is positioned to advance productivity, safety, and cybersecurity for Logix‑based automation systems, while emphasizing reuse, diagnostics, and tighter cross‑domain integration (motion, drives, HMI). Proper planning—especially around firmware compatibility, libraries, and security—will maximize benefits and reduce migration risk.
If you’d like, I can produce a tailored migration checklist, a one-week training agenda for engineers, or a compatibility matrix template for your existing controllers and modules. Which would you prefer? Version 35 is positioned to advance productivity, safety,
Here’s a professional yet engaging post for Studio 5000 Logix Designer Version 35, tailored for LinkedIn, a blog, or an internal company announcement.
In terms of raw "heaviness," v35 feels similar to v32 and v33.
Bugs: V35 is generally considered stable. It did not suffer the same initial backlash that v32 had (which had early issues with controller task overlapping). However, as with any Rockwell release, always check for the latest "Tech Note" patches. Many users skip v35 entirely to jump to v36, which further refines the features introduced here. If you are on v35 and stable, there is no desperate need to move, but if you are starting fresh, v36 might be the safer long-term bet.
Studio 5000 v35 introduces updates across the Logix Designer, View Designer, and connected utilities focusing on expanded controller support, enhanced safety integration, improved diagnostics, and updated libraries/modules for newer hardware families.
Version 35 is the minimum required firmware for several new CompactLogix 5480 and ControlLogix 1756-L8xE series enhancements.
With the rise of OT cyber threats, V35 makes CIP Security (CIP Secure) easier to deploy. New features include:
This is the standout feature of v35. Previously, implementing PLS functionality required creating complex arrays and ladder logic to track position and turn outputs on/off based on cam profiles.