Version 35 marks the debut of the , establishing a programmable API wrapper around the IDE. Utilizing C++ script commands, automation engineers can programmatically:
Addressing user requests for improved simulation, V35 brings enhanced support for motion applications. Users can now . This feature supports physical controllers and emulated controllers through FactoryTalk Logix Echo V2 , allowing engineers to test and validate motion routines without needing physical hardware, saving time and preventing damage during testing. Automated Scripting Utility (SDK)
To help tailor any further technical advice, let me know you plan to use with V35, which version you are upgrading from , or if you are focused on safety or motion control applications . Share public link
Engineers can now test motion profiles and axis configurations more safely without risking physical machine damage.
Improved virtual motion testing with Kinetix, PowerFlex, and iTRAK using FactoryTalk Logix Echo. Process Efficiency: New process instructions ( ) and SequenceManager support for 5x80P5 x 80 cap P
: When the "Almost Complete" screen appeared, click Skip Activation to proceed. The 30-day evaluation period would begin at this point.
: For those in heavy industry, V35 embedded new process instructions (like P_valveMP ) directly into the software, making it easier to build massive plants without starting from scratch.
Use the upgraded Logix Designer Compare Tool bundled with v35 to quickly identify code deltas between a running controller and your offline backup.
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.
Given the potential for software conflicts and operating system compatibility challenges, many experienced users recommended a virtualization strategy:
