Connect your tools
Connect native simulation applicationsPreview
Use a licensed Windows simulation application through Adam Desktop.
Connect a native application when your work depends on its existing study, solver, model format, or installed environment. Adam's connector prepares the integration on your Windows workstation; you supply the application and its required license.
Choose the connection
| Integration in Adam | Applications and setup notes |
|---|---|
| SOLIDWORKS | Simulation shares the SOLIDWORKS connection. Install the Simulation add-in and provide the appropriate license. |
| Ansys | Groups Mechanical, Fluent, Workbench, SpaceClaim, Discovery, and LS-DYNA. Install only the applications you use. |
| Abaqus/CAE | Live integration requires Abaqus 2024 or later with Python 3. |
| COMSOL Multiphysics | Runs COMSOL model Java in a COMSOL that Adam opens for you (a COMSOL Desktop connected to a local server), or in batch in a separate COMSOL with no window. Needs comsolcompile, comsolbatch, comsolmphserver, and comsolmphclient from the same installation. |
| Simcenter STAR-CCM+ | Runs Java macros in the simulation you have open in STAR-CCM+, or in batch in a separate STAR-CCM+ with no window. |
| Altair HyperMesh | Live integration requires HyperMesh 2026.1 or later. |
LS-DYNA runs batch jobs and doesn't connect to a window you have open. Supported operations in the other applications depend on their native APIs and installed release.
Match the workflow to the integration
| Path | Implemented workflow scope |
|---|---|
| Mechanical | Scripts in a Mechanical window open on your workstation, or in a separate background Mechanical with no window for solves. Adam's Mechanical extension lets windows you open connect; restart Mechanical once after it installs. |
| Fluent | PyFluent scripts in a Fluent window open on your workstation, or in a separate background Fluent with no window for solves. Fluent 2025 R1 or later. Adam adds a startup hook to your Fluent startup file (.fluent in your user folder) so windows you open connect; restart Fluent once after it installs. |
| Workbench | Scripts in a Workbench window open on your workstation, or in a separate background Workbench with no window for updates. Adam's Workbench extension lets windows you open connect; it installs once Workbench has run on the workstation, then restart Workbench once. |
| SpaceClaim and Discovery | Geometry scripts in a SpaceClaim or Discovery window open on your workstation, or in a separate background instance with no window. Adam's add-in, built on your workstation when the integration installs, lets windows you open connect. It goes into each Ansys release's install folder, so Windows asks for administrator rights once; if you decline, select Install on the integration to try again. Restart open windows once after it installs. A Discovery connection does not establish support for its simulation fields. |
| Abaqus/CAE and HyperMesh | Model inspection, queries, and scripts in the Abaqus/CAE or HyperMesh window open on your workstation, through Adam's plugin, or scripts in a separate background run with no window. The connector installs the plugin; Abaqus/CAE loads it when it starts, and HyperMesh must be closed while it installs. |
| LS-DYNA | Keyword decks solved in a separate LS-DYNA with no window, from the Ansys installation; the run's files and its termination are reported back |
| COMSOL and STAR-CCM+ | Java model code or macros in the model or simulation you have open, or in a separate application with no window; the files each run writes in its own folder, and the end of its logs, are reported back |
| SOLIDWORKS Simulation | Study inspection and guarded static mesh, solve, and displacement helpers through the SOLIDWORKS bridge |
These paths do not provide the same operations. In particular, HyperMesh preprocessing does not by itself run a downstream solver, and SOLIDWORKS CAD connectivity does not establish that a requested Simulation study type is supported. Ask Adam to inspect the available operations for the intended workflow before changing a study.
Set up the workstation
Install and verify the native application
Use the Windows workstation where the application is installed. Confirm it starts and that you can use the required license or module.
Connect Adam Desktop
Open the application's integration in Adam and follow the pairing steps.
Allow the integration to install
The connector installs Adam's extension, add-in, plugin, or startup hook for the application by itself. Built-in entries do not require a separate Python installation or a custom MCP address. If an install can't finish by itself, select Install on the integration to try again.
Complete any application-specific step
Follow restart instructions shown by the connector. Save your work before restarting an application.
Verify the model with a read-only request
Confirm the application version, native session, and intended study or model before changing it.
Some Ansys preparation paths depend on native scripting entitlements or permissions in the installation directory. If preparation fails, preserve its diagnostic message and confirm the installed release and permissions with your administrator or Adam support.
Understand readiness
| Observation | What it establishes |
|---|---|
| An installation is detected | The application appears to be installed |
| The integration installs | Adam's extension, add-in, plugin, or hook is in place |
| A native session connects | Adam can communicate with that session |
| A model is read successfully | Adam can inspect the selected model |
| A solve finishes | The solver reports a completed run; numerical and engineering checks remain |
Detection does not test license availability.
Check my connection to [application] on [computer]. Identify the application version and open model or study. Read its analysis type, geometry identity, and existing results where available. Keep this read-only and distinguish connection readiness from solver or license availability.
Recover without duplicating work
If a connection drops during an operation, the native application may still be running. Ask Adam to inspect the current job, document, and output state before retrying. Cancellation support differs by application; verify that the native solver has stopped.
For preparation problems, include the application and version, connector status, task URL, and non-secret error text when contacting support.
Next: Study setup, Structural analysis, Fluid analysis, or Simulation troubleshooting.