u/Best-Explanation31

I'm running a T-joint indentation analysis with two loading phases:

Step 1: Axial preload on the chord. No prescribed displacement on the brace, but the brace crown point already displaces passively (let's call it UY_residual ≈ -0.9 mm) due to chord deformation.

Step 2: Prescribed displacement applied to the brace top to simulate an indentation punch (-4 mm).

The problem: ANSYS treats the -4 mm as an absolute target. So instead of continuing from -0.9 mm down to -4.9 mm, the node returns to zero first, then goes to -4 mm. This creates a physically incorrect displacement reversal at the start of indentation.

I've tried both Remote Displacement and APDL D command — same issue with both.

What worked: Reading UY_residual via /POST1 + SET, 1, LAST + *GET inside the Step 2 Commands Object, then applying D, ALL, UY, (UY_residual + increment) as the absolute target.

Questions:

Is there a native Mechanical way to prescribe displacement relative to the current deformed state?

Is the /POST1 + *GET approach inside a Commands Object the standard practice for this?

Thanks.

Hi everyone,

I'm running a parametric study using the Parameter Set in Workbench (Ansys 2025 R2) and I need some help extracting data.

The Goal: Export the time-history data (Force and Deformation for all substeps) to a CSV/TXT file for each Design Point.

The Setup:

My geometry is updated via SpaceClaim for each DP, so the topology changes. Because of this, I'm strictly using Named Selections to scope my results.

I've tried using User Defined Results (Expression: UY) and Deformation Probes scoped to these Named Selections.

I'm using a Python Code object in the tree (Target Callback: After Post) to export the data.

The Problem:

When I run the Design Points, Mechanical runs in the background (GUI is closed). Because the GUI is closed, calling resultado.TabularData or using resultado.ExportToTextFile() throws an error (e.g., 'UserDefinedResult' object has no attribute 'TabularData' or Index out of range). The API seems to disable tabular extraction for these objects when running in batch mode.

The Question:

What is the simplest, most robust way to extract this time-history data using Python when the Mechanical GUI is closed? Do I have to dig into DPF, or is there a simpler workaround to get the Tabular Data out of a Named Selection while in background mode?

Any tips or snippets would save my life. Thanks!