Shop Floor Connect / DNC Connect / 3rd Party Integration / Mcenter Service Release 2604

The new Shop Floor Connect, DNC Connect, 3rd Party Integration, API, MMR Service version 2604 is released and now available. Please look below for the enhancements and changes of the different modules.

The release is now available to all customers with a maintenance contract in our new helpdesk. Please register on the following page. You will then receive confirmation of your access. You can then submit support requests and download the releases. All customers who do not yet have access to our helpdesk and want to download the software, please request access via the following link.

Please send an email to service@aplusb-solutions.com if you want the release on a data medium. Direct Siemens PLM Software customers can get the release from the GTAC download area.

This Shop Floor Connect Release 2604 supports all Teamcenter UA versions from 12.x up to the actual version Teamcenter 2512.

Urgent Service notes

• DNC Connect only supports the actual NX versions who are under maintenance from Siemens.
• For customers who want to update on the Teamcenter 11.3 version or higher: From TC 11.3 and on, a new license verification will be done upon the creation of manufacturing objects like MEProcess, MEOP, MEWorkArea and their sub-types (including custom types). This check will be done on server side per Teamcenter policy and to ensure license verification. It will use two new feature keys: 1) mfg_planning_lite for verifying MEProcess, MEOP and their sub-types 2) mfg_plant_author for verifying MEWorkArea and its sub-types.
  This new license check will be done in addition to other license verification that exists today. If you don’t find them in your Teamcenter 11.3 or higher license key please get in contact with Siemens Digital Industries Software.

SFC/DNC Connect/3rd Party Integration/Mcenter Service

Shop Floor Connect

Enhancements

• Upgrade internal Tomcat to version 9.0.117.
• ActiveDNC: The configuration key ‘Download.Limit.Enabled’ can now be configured based on the group (and role) of the logged-in Teamcenter user.
• ActiveDNC: An additional icon is now available in the toolbar for a dataset’s files, which allows you to open the view in a new, separate browser tab.
• The update script now checks whether a global CATALINA_HOME environment variable is set. If so, this value is overwritten so that the correct Apache Tomcat of the SFC_ServerService is terminated.
• SFCCore: The configurable Teamcenter attribute for limiting the number of downloads of a dataset can now be configured at the dataset and/or the ItemRevision level. If the attribute is found on an ItemRevision, it applies to all datasets in that revision. If the attribute exists and is filled in on both the dataset and the ItemRevision, the value entered on the dataset takes precedence.

Bugfixes/Changes

• SFCCore: A problem has been fixed in the API function ?SFC_WF_PerformEPMTaskAction_20192? that caused the SFC CacheManager to stop processing further queries when an error occurred.
• Common: Support for Teamcenter 2512, migration from 32-bit to 64-bit on Windows, and renaming the Apache Tomcat directory from ‘Tomcat 5.0’ to ‘tomcat’.
• SFCAdmin: In the email server configuration screen, the specified SMTP port was not used when TLS was enabled. Instead, port 465 was always used. This issue has been resolved.
• Update: The update script now checks whether write permissions are available for its own files (based on the version.txt file). If this file cannot be overwritten, an error message with instructions is displayed and the update is canceled.

MI-Server

Enhancements

• Upgrade internal Tomcat to version 9.0.117.
• The update script now checks whether a global CATALINA_HOME environment variable is set. If so, this value is overwritten so that the correct Apache Tomcat of the SFC_ServerService is terminated.

Mcenter Service

Enhancements

• MFG_MMR: When transferring work packages to Mcenter, all existing program groups (MENCProgram) are now taken into account, just as with NcPackage in the tool plan, and all tools are transferred. The name of the original program group is not transferred to Mcenter. When uploading modified NC programs back to Teamcenter, the name of the target program group can now be configured via ‘MMR.Programs.Upload.Activity.Name’ (e.g., ‘uploads’). Otherwise, the upload dataset is stored in the first program group found.

Bugfixes/Changes

• MFG_MMR: A problem has been fixed regarding the upload of modified NC programs, which caused the upload process to terminate with a NullPointerException while searching for the target ItemRevision in Teamcenter (getTCItemID).
• MFG_MMR: A problem with transferring NC packages (Teamcenter to Mcenter) has been fixed. A NullPointerException occurred when transferring the NC files and the task in Teamcenter continued to run in an endless loop.
• MRL_MMR:Classification data from Teamcenter is now retrieved using the API function ‘classification._2011_12.Classification.getClassificationObjectInfo’. Previously, ‘classification._2007_01.Classification.getClassificationObjects’ was used. The new function returns additional information. However, the format of the return values for numbers and value lists has changed: Floating-point numbers are now always output with a “period” as the decimal separator, and value lists are output in the format “[Key] [Value]”.
• MRL_MMR: The following configuration entries have been changed and must be manually adjusted during an update to ensure that numerical values are transferred correctly to Mcenter: MRL2MMR.mapping.assemblyV2.attributes.properties ———————————————— Old: ToolClassV2.D6.Pattern = {0,number} New: ToolClassV2.D6.Pattern = {0,number,#.###} MRL2MMR.mapping.component.attributes.properties ———————————————– Old: ToolComponent.Weight.Pattern = {0} New: ToolComponent.Weight.Pattern = {0,number}
• MRL_MMR: The following entry has been added to the mapping configuration ?MRL2MMR.mapping.assemblyV2.attributes.properties.default?: ToolClassV2.CuttingEdgeDefinitionV2.CuttingEdgeGeometryV2.A1.pv.0,4 = ClassificationAttribute:-45270
  After the update, the entry must be manually added to the active configuration file!

Subject to change without notice!