Tecnomatix 2420 Release Notes
Tecnomatix 2420 Release Notes
Release Notes
Unpublished work. © 2024 Siemens
This Documentation contains trade secrets or otherwise confidential information owned by Siemens Industry Software Inc. or its affiliates
(collectively, “Siemens”), or its licensors. Access to and use of this Documentation is strictly limited as set forth in Customer’s applicable
agreement(s) with Siemens. This Documentation may not be copied, distributed, or otherwise disclosed by Customer without the
express written permission of Siemens, and may not be used in any way not expressly authorized by Siemens.
This Documentation is for information and instruction purposes. Siemens reserves the right to make changes in specifications and other
information contained in this Documentation without prior notice, and the reader should, in all cases, consult Siemens to determine
whether any changes have been made.
No representation or other affirmation of fact contained in this publication shall be deemed to be a warranty or give rise to any liability of
Siemens whatsoever.
If you have a signed license agreement with Siemens for the product with which this Documentation will be used, your use of this
Documentation is subject to the scope of license and the software protection and security provisions of that agreement. If you do
not have such a signed license agreement, your use is subject to the Siemens Universal Customer Agreement, which may be viewed
at https://www.sw.siemens.com/en-US/sw-terms/base/uca/, as supplemented by the product specific terms which may be viewed at
https://www.sw.siemens.com/en-US/sw-terms/supplements/.
SIEMENS MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS DOCUMENTATION INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT OF INTELLECTUAL PROPERTY.
SIEMENS SHALL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, LOST DATA OR
PROFITS, EVEN IF SUCH DAMAGES WERE FORESEEABLE, ARISING OUT OF OR RELATED TO THIS DOCUMENTATION OR THE INFORMATION
CONTAINED IN IT, EVEN IF SIEMENS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
TRADEMARKS: The trademarks, logos, and service marks (collectively, "Marks") used herein are the property of Siemens or other parties.
No one is permitted to use these Marks without the prior written consent of Siemens or the owner of the Marks, as applicable. The use
herein of third party Marks is not an attempt to indicate Siemens as a source of a product, but is intended to indicate a product from,
or associated with, a particular third party. A list of Siemens' Marks may be viewed at: https://www.plm.automation.siemens.com/
global/en/legal/trademarks.html. The registered trademark Linux® is used pursuant to a sublicense from LMI, the exclusive licensee of
Linus Torvalds, owner of the mark on a world-wide basis.
Performance Improvements..................................................................6-1
Robot Center..........................................................................................8-1
Robotic Enhancements..........................................................................9-1
OLP 2402..............................................................................................11-1
Each release update contains multiple fixes and improvements for the main release. In addition to the new
content, each update includes the content of all previous updates.
Process Simulate provides a notification that release updates are available for installation.
When opening Process Simulate users receive a notification of the availability of a new release update. This
allows them to download and install the release update immediately from Siemens Support Center.
A Themes setting has been added to the Appearance Tab in the Options dialog box. You can use the
Themes setting to select the light (default) or dark UI theme.
To better support the use of the dark theme, many icons in most dialog boxes were redesigned. The
renewed icons also appear in the light theme user interface.
From the Viewers group of the Home ribbon you can open several viewers that are designed to load
specific object types:
All trees are based on common infrastructure which creates standardization in Process Simulate.
The new Object Viewer infrastructure provides greater flexibility and more robust capabilities, and
replaces the old Object, Operation, and Logical Collection trees.
Note
For operations with no robots assigned, such as object flow, manual welding, and gun-only operations
(and also load assist operations), use the Assembly Automatic Path Planner. Note that you can still use
the previous Automatic Path Planner (APP) command, Legacy Automatic Path Planner that works both
for assembly and robotic operations. By default, it is not on the ribbon.
To start using the Robotic Automatic Path Planner, click the new Open Robotic Automatic Path Planner
icon in the Path Editor, or use the Open Robotic Automatic Path Planner command from the ribbon.
Robotic Automatic Path Planner offers the Interlock solving algorithm option to synchronize robots
associated with operations nested in the compound operation and prevent collisions.
Officially released this version, the Robotic Automatic Path Planner has additional features compared to
the beta version, with better handling for:
• Self-collisions—you can allow the Automatic Path Planner to automatically handle the collisions
between the robot and the gun (default behavior of APP) or you can use the active collision sets only.
• Smart gun tips collision detection—you can choose to always run Automatic Path Planner with smart
gun tips collision detection on, even if the option is not enabled in the Process Simulate settings. This
allows you to benefit from the safety of the feature without any performance impact when running the
simulation with collision detection on.
• Setup commands for additional controllers are supported: Kawasaki and Yaskawa.
• Modules and parallel tasks are displayed in different branches.
• All functionalities available from the Robot Modules dialog box can now be performed from the Robot
Center.
• The Refresh button is added, enabling you to manually update the tree with modifications that are not
automatically refreshed in the trees and Graphic Viewer.
Note
This button is temporary and will be removed when all refreshing events are supported in subsequent
versions.
Conveyor Improvements
• Detach Part / Skid from Conveyor on Stopper—when a part or skid moving on a conveyor stops by
hitting a stopper type control point, Process Simulate internally marks it as a pickable part. Now other
devices attempting to grip it can do so without the conveyor attempting to reattach it to itself. For
example, at conveyor intersections, parts can be grabbed by the next conveyor smoothly and moved in
another direction.
• Part and skid stacking on separate conveyors (ER 10309848 / ER 9403471)—in this version, when
several parts (or skids) flow from one conveyor to the next and collide with each other while on the
different conveyors, they stack up one after the other in the same way they do when the parts are on
the same conveyor.
• The conveyor application now offers simulation performance improvements reaching 10% or better.
Additional Enhancements
• Move location to TCPF (ER 8438719) is now a standalone command that you can add to the ribbon
from the customization menu. Because it is not contained in the Robot Jog dialog box, you can create
Note
This is fully implemented only when the cloned robot's information is created (or refreshed) in
Tecnomatix version 2402 EAP (Early Adopter Program) or later.
• Safety Robots Manager—support was added for Kawasaki Cubic-S. A new Operations check report is
available (in Beta version).
The Enable automatic usage of cull parts option improves graphic performance dynamically by hiding
smaller objects from the display. When you zoom in, the system recalculates the data, and previously
hidden objects may become visible. Conversely, zooming out may hide additional objects, as determined
by the percentage value.
◊ Ability to select .xml as target program file in the Download dialog box
• Fanuc
◦ ER10736760—support partial EmergencyStop reset (do not reset simulation variables such as
registers after an Emergency Stop)
◦ Robot Setup
◊ ER10777270—wherever data is read from SYSTEM.VA, also attempt to read from SYSVARS.VA with
least priority
◦ Simulation
◊ ER10790511—support numerical register values in the "JMP LBL" command
• Kawasaki
◦ ER10734662—support motion to HOME Pose:
◊ Add Import Home Poses facility in Robot Setup
◊ Support the following instructions in simulation:
‒ SETHOME <accuracy>, HERE
‒ SET2HOME <accuracy>, HERE
◦ Support for ACCEL and DECEL commands
◊ ACCEL <acceleration> <ALWAYS>
◊ DECEL <deceleration> <ALWAYS>
<acceleration> and <deceleration> are in % from 0.01 to 100
The image below illustrates how to define the Fixture Assembly Root (Mfg0MEFixtureRootRevision) as a
compound Kinematics Equipment using the Tecnomatix Doctor mapping configuration.
Note
The system still supports Compound Kinematic Equipment created in Teamcenter from non-workarea
types regardless of these mapping file definitions.
To ensure that data created by the simulation engineer is successfully saved to Teamcenter, it is important
to validate that the modified data complies with the server logic. To achieve this, enhancements were
introduced in this version.
Process Simulate now fully applies the server configuration of permitted types (TcAllowedChildTypes) for
both resource structure and process structure authoring. Process Simulate ensures that all commands or
actions that impact the hierarchy of either the process structure or the resource structure follow these
configurations. It applies to both adding an object below the selected process or resource and to assigning
a resource, MFG, or part to an operation.
In addition, two new options were added to the Teamcenter Settings in Tecnomatix Doctor to further
enforce server restrictions:
• Enforce Object Checkout (Beta)—When a number of users (of Process Simulate or other applications)
work on the same project and have an overlapping data scope, it is important to ensure there is only a
single author at one time. In this version, you can configure Process Simulate so that a user can modify
objects only if they are checked out by that user.
• Validate write access (Beta)—activate this option to ensure users can modify only objects that they
are authorized to change in order to ensure the server can be updated with these changes. Objects that
users cannot modify are marked as read-only because they are released, or are checked out by another
user, or privileges are insufficient.
When the access state of a workarea (compound-resource) or a process or operation is read-only or
checked out by others, any command or action that modifies those objects or the structure below is
deactivated.
This applies to move/copy-paste/delete actions as well as to other commands that add or modify objects
in resource and process structures, for example New Object, New Human, Move Weld Location,
Modify Operation Properties. The read-only state of the object may be due to its released status, lack
of permissions, site ownership, or being checked out by others.
To ensure successful update to Teamcenter, activating the Validate write access option makes sure that
users can only modify objects that they are authorized to change.
Note
• This capability applies to both Process Simulate on Teamcenter and Process Simulate on Teamcenter
Standalone (the state of the objects in the study is according to their state at the time they were
loaded to Process Simulate).
• New capabilities do not fully apply to previously saved psz-tc files.
In version 2402 the Object and Operation viewers now provide clear indications about the access state of
objects. The following overlay icons may appear next to resources and processes:
Locked
When a command is inactive due to the resource or process being locked, a tooltip displays explaining the
root cause.
Enforce Object Checkout and Validate write access options do not apply to authoring resource instances
(resource occurrence information) such as position, global mount and attach, robot setup.
Note
This is a Beta version and the improved capability does not yet fully apply to those commands that
manipulate weld/via locations—these are still pending.
Clicking Yes updates the mapping file with the latest changes.
The Posture Monitor is a simple yet powerful way to assess ergonomic compliance in real time. It enables
you to quickly identify if task demands are within recommended limits. Numeric values for each joint
are presented in the Posture Monitor dialog box, and now for version 2402, postural warnings are
highlighted directly on the human in your scene. Colored spheres display on individual joints when they
fall outside of the preferred posture ranges.
Human postures can be monitored in real time with the Posture Monitor enabling you to avoid
uncertainty when evaluating human postures by turning on real time figure highlighting for continuous
feedback about the tasks being performed.
New options have been included in the Force Solver, allowing you to tailor results for each scenario. If an
analysis pertains to the upper body only, you can now exclude portions of the lower body from an analysis.
Optionally, when assessing the strength demands of a task, you can remove:
• Ankles
• Ankles and knees
• Ankles, knees, and hips
This supports focused analysis results and avoids confusion when sharing findings with others.
The Task Simulation Builder (TSB) now supports creating a custom motion library, which is a powerful
utility for building realistic simulations. You can record real human movements and organize them into
categories for later viewing and inclusion in a simulation. This new feature can save you time during
simulation creation and improves the realism of your simulations by inserting motions captured from real
humans.
You can create library entries in several ways, including recording motions from a motion capture tool or
whole body virtual reality tracking session, or by recording portions of an existing simulation. You can add
or remove library contents, and libraries can be shared among colleagues for mutual benefit.
When you create a new simulation with TSB, you can insert motions from the library. This is especially
valuable when you need to include a common task motion in a new simulation, avoiding re-work and
Additionally, the motion library framework can serve as a valuable resource when you populate it with
recordings of typical operator motions. Such a repository can serve as a reference for how operators
execute specific actions, helping to guide simulation authoring.
Path Planning
• The ITxPathPlanningContext interface has two new methods, OperationRecorder and
SequenceRecorder, which return a recorder (ItxPathPlanningOperationRecorder) that can save and
restore the state of an operation or a compound operation respectively, typically before and after a
ITxPathPlanningCalculator.Run call.
• The ITxPathPlanningOperationParameters interface exposes the new
ShouldHandleSelfCollisionsAutomatically property allowing to specify whether collisions between the
robot and its mounted parts should be automatically handled or if the active collision sets should be
strictly considered.
• The ITxPathPlanningOperationParameters interface exposes the new
SmartGunTipsCollisionDetectionMode property allowing to specify whether Smart Guntip collision
detection mode should be forced during calculations even if deactivated on the Process Simulate level
(the current defined range is used if forced).
• The ItxPathPlanningSmartPlanningQuery interface exposes the new
ShouldOnlyInsertJointMotionLocations property allowing to specify whether automatically inserted
via locations should use the motion type of the next fixed location or if only joint motion via locations
should be inserted.
• The ItxPathPlanningOperationCollisionCheckingQueryResult interface exposes the new
IsCollisionCheckComplete read-only property allowing to know if the entire operation has been tested
for collisions. Usually false if the entire operation cannot be properly simulated.
• The ITxPathPlanningSequenceInterlockSolvingQueryResult interface exposes the new
BlockingOperations read-only property allowing to know which operations were problematic and
caused a failure of the corresponding ITxPathPlanningSequenceInterlockSolvingQuery.
• The ITxPathPlanningSequenceInterlockSolvingQueryResult interface exposes the new
BlockingOperationReport method which allows retrieving more information on why a specific
operation was blocking for the corresponding query (see BlockingOperations) through the new
TxPathPlanningSequenceInterlockSolvingBlockingOperationReport class.
• The ITxPathPlanningZoneAssignmentQueryResult interface exposes the new
TxPathPlanningZoneAssignmentFailureCause read-only property allowing to know what is the cause
of failure of the corresponding ITxPathPlanningZoneAssignmentQuery.
• The ITxPathPlanningBasicPlanningSegmentResult interface exposes the new Succeeded read-only
property allowing to know whether the segment was successfully handled by the calculator. The
OLP
• The GetRobotProperty method which returns a given robot property by name (returned type depends
on the input property name), was added to the ITxRoboticControllerServices interface.
• The GetOperationKeyWordsControls method which gets all operation keywords controls for a certain
template and for a specific operation, was added to the TxOlpDownloadTemplateServices class.
• TxOLPUtilities exposes a new method, CalcTaughtFrame, which calculates the absolute location of the
taught location.
Model Objects
• The ITxRobot interface exposes the ControllerChanged event which notifies the robot when the
controller is changed.
• The ITxSafetyZoneObject interface exposes the BreachingObjects property which gets the currently
breaching safety objects.
• The ITxLogicalCollection interface exposes the new CanBeRemoved method allowing to check if a
specified object can be removed from the collection. The classes that implement the interface are
TxLogicalCollection, TxLogicalGroup, TxLogicalRoot.
• The TxTcProcess interface implements the new AddObjectAfter method allowing to check if an object
can be added after a specified child.
• The ITxObject interface exposes the new IsTransientChanged event. The event is fired when the
IsTransient state of the object is changed.
• The ITxOrderedCompoundOperation interface exposes the new Reversed event. The event is fired
when the order of operation locations in a path becomes reversed.
To support Process Simulate on Teamcenter, the data authoring validation feature was introduced in this
version. A series of .NET API additions were made to enable custom applications to implement authoring
validation.
Input validation
• The new TxCompositeValidator and TxComposableValidator classes were introduced to enable the
use of more than one validator per control.
• The new TxObjectAccessValidator, TxObjectAssignmentValidator and TxObjectRelationValidator
classes provide specific data authoring validation.
Other
• TxCompoundOperationCreationData now supports the ITxObjectBehaviorCreationData interface.
This enables the creation of Compound Operation objects with Display behavior.
• ITxTcAnyServicesProvider was extended with more properties. For one of them, a change event was
introduced in ITxTcServicesProvider.
• The new TxCommandTypeFilterEnabler provides a selection enabler that enables the commands if
there is exactly one object in the selection and that object passes the filter.