One of the most frequently searched sections of any release note is the compatibility grid. Below is the verified compatibility table as of v35’s general availability (GA) date.
In response to recent industrial cyber incidents (e.g., ICS-CERT alerts), v35 introduces verified security controls:
Note: If you disable audit logging, the release notes warn that this voids the verified compliance for NIST SP 800-82.
The silence in the room was no longer peaceful; it was expensive. Downtime cost $10,000 an minute.
"Sarah, I have to go offline," Elias shouted into the phone. "I need to reconfigure the Motion Group attributes. It's a v35 protocol change."
"Do it fast!"
He went offline, his fingers flying across the keyboard. He opened the Motion Group properties. Under the Axis Assignment tab, he unchecked the box labeled "Enable CIP Sync Optimization"—a new default in v35 that confused the older drives.
He checked the logic again. He didn't have time to run a full verification.
He clicked Verify.
Error: 0. Warnings: 0.
He re-downloaded the project. The tension in the room was palpable. The progress bar seemed to move slower than before. studio 5000 v35 release notes verified
As the controller rebooted, Elias leaned in, inches from the screen.
The I/O tree populated. Power: Green. Ethernet: Green. Safety: Green. Motion Module: ...
The icon turned Green.
"Elias?" Sarah’s voice came back. "The drives are spinning up. We have control."
Elias slumped back in his chair, the adrenaline crash hitting him all at once. One of the most frequently searched sections of
v35 decouples alarms from the HMI server configuration more aggressively. The verified change is the introduction of Tag-Based Alarm properties for BOOL arrays.
To ensure accuracy, the following were performed by an independent control systems engineer:
A quiet but powerful change: UDTs can now be directly aliased to DINT and REAL arrays without the need for MOVE instructions. Verified use cases include:
Warning from release notes: While JSON import/export works verified, nested UDTs exceeding 5 levels deep require manual verification via the
Verify Structuretool.