> For the complete documentation index, see [llms.txt](https://dante-solutions-inc.gitbook.io/dante-6.3-help-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dante-solutions-inc.gitbook.io/dante-6.3-help-documentation/readme/additional-topics-introduction/rotational-induction-hardening-process.md).
# Rotational Induction Hardening Process
DANTE has the capability of customized rotational induction heating using a film subroutine. To use this capability, the ABAQUS DFLUX subroutine is called by the model. The thermal boundary conditions in the input file are given below as an example, where only the element set name can vary (‘ALLELEMENTS’ in the example):
```
*DFLUX, OP=NEW
ALLELEMENTS, BFNU
```
* The film subroutine will call the file “Model\_Name” + “\_DFLUX\_POWER.TXT”, which should be located in the current working directory (CWD). For example, if the model name is Job-1, then the subroutine file name should be “Job-1\_DFLUX\_POWER.TXT”. The DFLUX\_POWER.TXT file will call an additional power file unique to rotational induction hardening. The additional file contains the process parameters and must be named “ ROTATION\_SCAN\_PROCESS\_IH\_POWER.TXT.”
* The “DFLUX\_POWER.TXT” file uses keyword definitions, with ‘\*’ indicating a keyword and ‘\*\*’ indicating a comment line.
To use Rotational Scanning induction heating, the value of the **\*Power\_Check** keyword should be set to -2 in the “Model\_Name”\_DFLUX\_POWER.TXT file; no other information is necessary. An example of this file is given below, where “\*\*” indicates a comment line only and “\*” indicates a keyword:
```
** Power Density File
** Input POWER File Name: Mesh_ordered_coords.txt
**
*POWER_CHECK
-2
*END_POWER
```
To use Rotational Scanning induction heating, a file must be used to define the rotational scanning process. The required file name is **“ROTATION\_SCAN\_PROCESS\_IH\_POWER.TXT”**, and this file should be in the same directory as the input file when submitting the job. This file has a fixed format and a fixed name. For example, line-9 defines the point on the axis to define the rotation. An example of the file format and inputs is shown below. A brief description of each parameter follows Figure below.
```
** File Name (Fixed): ROTATION_SCAN_PROCESS_SPRAY.TXT
** File Format is Fixed, (not keyword based)
** Defining Rotation Spray Process Paramaters
** "ITYPE_QUENCH" should be set to 2 in *_FILM-QUENCH.TXT File
** Limit to rotation spray around axis parallel to X, Y, Z
**Point on the Axis of the Part (XC, YC, ZC) for rotation
0, 0, 0
** Axis for Rotation; X(1 / -1); Y(2 / -2); Z(3 / -3)
3
** Defining Rotation Angle vs. Time (Degree)
** Number of points (Max. 100)
3
**Time(s), Rotation Angle (degree)
0.00, 0.0
8.00, 0.0
50.0, 180
** Initial Spray Angle; Width Spray (degree)
** Defined by Tail Line of 1st Nozzle, and the width goes to rotation direction
330, 30
** Number of Spray Zones; Spacing Angle between Zone
1, 50.0
** Defining the (HTC vs. Temperature) Profile and Ambient
** Ambient Temperature (C)
20.0
** Air Coolimng HTC(W/mm^2K)
0.000025
** Number of points (Max. 100)
2
**HTC(W/mm^2K), Temperature (C)
0.011000, 20
0.011000, 1000
**End of File
```
***Part Radius*****:** This is the radius of the part, in mm. The radial direction must be defined using the global coordinate system.
***Point on the Axis of the Part*****:** This is a point that is coincident with the axis of the part.
***OD or ID of Cylinder*****:** Defines whether the rotation occurs on a convex surface (OD) or concave surface (ID).
***Axis for Rotation*****:** This is the axis of rotation around a global axis and follows the righthand rule for the direction of rotation; i.e., positive is counter-clockwise rotation and negative is clockwise rotation. The **Axis for Rotation** must be parallel to the X, Y, or Z Axis. The current version does not allow for the axis of rotation to be in multiple global planes; the axis of rotation must lie in a single spatial plane; XY, XZ, or YZ.
***Defining Rotation Angle vs. Time – Number of Points*****:** This sets the number of data pairs to define the rotation angle. The rotation angle can be constant or a function of time.
***Defining Rotation Angle vs. Time – Time, Rotation Angle*****:** These are the data pairs, consisting of time and rotation angle (not part angle); time must be in ascending order and the rotation angle should progress in the appropriate rotation direction (defined by the **Axis for Rotation**). This parameter is added to the **Initial Position of Inductor** to determine the actually starting position of the inductor. The example in Figure 2 starts the inductor head at 90° (because the **Initial Position of Inductor** is 0°; alternatively, the inductor could also start at 90° if the **Rotation Angle** is set to 0° at time zero and the **Initial Position of Inductor** is set to 90° **OR** if the **Rotation Angle** is set to 30° at time zero and the **Initial Position of Inductor** is set to 60°.). The inductor then dwells for 1 second before rotating 120° in 30.5 seconds. The rotation angle is increased for the last 10 seconds, covering 60° in that time.
***Initial Position of Inductor, Width Coverage of Inductor*****:** This is the initial position of the inductor, which is added to the **Rotation Angle** to determine the actually starting position of the inductor, and the width of the inductor, in mm. The position defines the position of the inductor tail. The width of the inductor is then swept along the direction of rotation and sets the head of the inductor. Figure below shows an example where the tail of the inductor starts at 90° (**Initial Position** is set to 90° and the **Rotation Angle** at time zero is set to 0°), with a spray width coverage of 30°. The start of the defined tail should be between \[0°, 360°], and the width is always positive.
*Figure: Example showing the initial position of the inductor and the inductor width.*
***Number of Inductors; Spacing Angle between Inductor*****:** The **Number of Inductors** sets the total number of separate inductors, which are separated by a finite distance; this is not intended to model a dual coil inductor. The **Spacing Angle** defines the spacing between inductors, calculated from the center of an inductor to the center of the next inductor. Figure below shows an example where the first inductor tail is at 90°, with a 30° inductor width, and the second inductor is separated by 90° from the first inductor. For multiple inductors, the spacing between each inductor should be ≥ the inductor width.
*Figure: Example showing multiple inductor spacing.*
***Defining the DFlux vs. Depth Profile – Number of Points*****:** Two pieces of information are required to define the power versus depth: the number of points defining the tabular data and the tabular data. The **Number of Points** is simply how many data pairs are used to define the power verses depth.
***Defining the DFlux vs. Depth Profile – Depth, DFlux Values*****:** Two pieces of information are required to define the power versus depth: the number of points defining the tabular data and the tabular data. The **Depth, DFlux Values** are simply the data pairs are used to define the power verses depth. Depth is in the first column, in mm, and the power value in the second column, in W.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://dante-solutions-inc.gitbook.io/dante-6.3-help-documentation/readme/additional-topics-introduction/rotational-induction-hardening-process.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.