This issue has already been fixed in 2025R1.

If you want to re-run the automatic screenshot, you can refer to the following methods:

* $root refers to the iSLM installation directory. The following commands are for CMD.

1. To re-run the screenshots for the Solution:

$root\tools\data-processor.exe screenshotAllSolt

2. To re-run the screenshots for all Runs:

$root\tools\data-processor.exe screenshotRuns

To activate iSLM HTTPS secure connection, you must purchase an SSL certificate and apply it by iSLM Startup Tool.

The following content will introduce you how to activate iSLM HTTPS secure connection.

• Step 1 : Create a folder named “certs” under Moldex3D > iSLM folder, and put the application certificate into “certs” folder.

• Step 2 : Open iSLM StartUp Tool, and click Machine, then the Machine Configurations window will appear.

• Step 3 : Turn on the Elastic toggle switch, enter the domain name in the Elastic Host field, and input “443” in the Port field. After completing these steps, click Save to submit. Additionally, when using a web browser, you need to append the “Port” to the domain name.
  *Note:
  – An example of domain name is ”www.example.com”. Additionally, if you do not use the default Port 443 of the https protocol, you need to add Port after the domain name, EX: https://www.example.com:8080

• Step 4 : Click Service, and the Service Configurations window will appear.

• Step 5 : In Gateway tab, change the Port column to “443”, change the file names of Cert and Pem to the relative path of certs under the installation path, and select “true” in the drop-down menu of TLS; then click Save in the lower right corner to send it out.
  *Note:
  – If you do not use the default Port 443 of the https protocol, you need to add Port after the domain name, EX: https://www.example.com:8080

• Step 6 : Click Restart to restart the iSLM service.

Please refer to the  chapter 1.2 (Support Https Protocol) in the Help for more detailed information.

Currently, there is no solution available when data corruption issues occur after relocating the iSLM database.

Therefore, users must ensure that the new iSLM database can start and function properly before deleting the original database. If data corruption occurs after relocation, the folder data can be copied again.

For backend servers, it is recommended to use the following hardware specifications as a reference. Please note that these specifications represent the minimum standard, and it is advisable to opt for higher-performance servers if possible.

• DELL T640 (https://www.dell.com/zh-tw/work/shop/cty/pdp/spd/poweredge-t640)

• RAID 10 allow max 4 disks offline

• 8TB disk space can support at least 800 sets of mold information (including Moldex3D Projects)

           – Assuming each project requires 10 GB

• UPS can hold the system 8 mins for shutdown

Currently, the AI-related features include Mold Design Discovery, Gate Design Discovery, similarity comparison, and gate extraction recognition.

Mold Design Discovery:

The purpose of this feature is used to compare the uploaded model files with projects stored in the Knowledge Base to evaluate their similarity. After the comparison, the system predicts molding outcomes based on information from the underlying database, such as material properties and parting directions. The predictions include recommended gate counts, injection pressure estimates, clamping force, and shrinkage rate forecasts.

Gate Design Discovery:

This feature sends the current plastic part model for similarity comparison. It allows users to apply gate designs from past similar projects to the new plastic part model, making the gate design process easier to complete.

Sure, but the DB server does not support using NAS.

Relocation Steps Between Different Hosts (Steps for Relocating Server1 to Server2):

• Step 1: Stop the iSLM service on Server1.

                Launch MDXiSLMStartUpTool as Administrator and Stop all services after

• Step 2: Stop the iSLM-DB service on Server1.

                Execute Moldex3D iSLM Stop DB as an Administrator, and use the job administrator to confirm that all services starting with Moldex3D iSLM have been Stopped. If there are any, you can right-click to stop it manually (Moldex3D iSLM DataBase Server should be the least stopped)

• Step 3: Copy the database from Server1 to Server2.

                Copy the folder data into the iSLM-DB installation path of Server1 (or another user-specified path during installation) to Server2. It is recommended to place it in the default path C:\Moldex3D\iSLM-DB or a disk with larger space

• Step 4: Reinstall iSLM and iSLM-DB on Server2.

                Launch installation of iSLM (optional) and iSLM-DB on Server2, and directs the iSLMDB Data Folder to the folder copied from Server1

                 ￚ If no need to install iSLM on Server2, refer to Step 5 to modify Server1 settings, or otherwise refer to Step 6.

• Step 5: Scenario where iSLM remains on Server1 but iSLM-DB is on Server2.

                If iSLM and iSLM-DB are not both installed on Server2,

                 ￚ In Configure menu of StartUp Tool, click Database to modify iSLM setting (Server1)

                 ￚ Select islmDB as the Database Name, and specify Host with Server2 IP

                  ￚ After the modification saved, click Start to activate the iSLM service

• Step 6: Scenario where both iSLM and iSLM-DB are removed from Server1.

                  ￚ After confirming the connection to the iSLM-DB on Server2, the iSLM web can be used normally. The Moldex3D-iSLM-DB can be removed via the control panel on Server1 by using the uninstall program feature.

                   ￚ The original folder of Server1 will be retained and can be removed if the service working fine through Server2

The possible cause of this result is that the Reload Project function was not executed in the iSLM Startup Tool beforehand. If you are certain that there are enough projects in iSLM to perform these two functions, please ensure that the Reload Project function is executed after the upgrade installation. This will ensure that the existing project data can be accessed by these two functions.

The reason for this issue is that although the Workflow includes Cooling and Warpage analysis, the user has used Gate Design Discovery. When the project only has gate without a complete runner system, these two types of analyses cannot be performed. Therefore, if you want to run Cooling or Warpage analysis, it is recommended to manually select the gate option. Additionally, when manually creating the gate, use the Runner & Cooling Channel Wizard to complete the runner and cooling channel setup. This will allow both analyses to be executed successfully.

When the system fails to generate a report and the message “Not enough reference projects in iSLM. Please upload more projects and try again.” appears on the page, it indicates that no similar projects are available for comparison. You can resolve this issue by increasing the number of Moldex3D projects.

After using the Auto Launch feature, you can go to the Activity Center to track the analysis progress.

The Activity Center is designed for users to monitor the progress of project uploads, conversions, or creations. It also includes a linking function that allows users to quickly navigate to the corresponding page to check the project execution status.