### iPart Thread Parameters Example - Existing

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-F30C4B36-98DE-4236-A2C6-B404F6E97CAC

This example demonstrates the parameters for an existing thread within an iPart factory. It specifies the thread family and designation.

```text
Thread1:Family="ANSI Unified Screw Threads" Thread1:Designation="7/16-14 UNC"
```

--------------------------------

### Modify Inventor Deployment Shortcut Paths for USB/DVD Drive

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-B3CA11B1-AE19-426D-8348-F59952C0DA55

This snippet illustrates how to change the Target and Start paths in an Autodesk Inventor deployment shortcut (.lnk file) when the deployment image is hosted on a USB or DVD drive. It converts network paths to local drive paths, allowing clients to install from removable media.

```text
Replace
```
\Server_Location\Shared_Folder\MyDeployConfig\Img\Setup.exe /qb /I \Server_Location\Shared_Folder\MyDeployConfig\Img\MyDeployConfig.ini /language en-us
```

with
```
E:\MyDeployConfig\Img\Setup.exe /qb /I E:\MyDeployConfig\Img\MyDeployConfig.ini /language en-us
```
```

--------------------------------

### Example Parameter Formats for Custom Tasks

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-F0C878E0-E0B6-41D1-9E95-33BFEC5EC3CC

Illustrates the expected formats for task parameters when using COM objects or executables for file conversions within Inventor Task Scheduler. The examples show separators for input and output file paths.

```Shell
E:\Datasets\Version12\part1111.idw|E:\Datasets\Version12\part1111.dwg
E:\Datasets\Version12\part1111.idw;E:\Datasets\Version12\part1111.dwg
```

--------------------------------

### iPart Thread Parameters Example - Replacement

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-F30C4B36-98DE-4236-A2C6-B404F6E97CAC

This example shows the parameters for a replacement thread in an iPart factory, highlighting a change in designation. It's used to illustrate potential failures if the thread class is not properly defined.

```text
Thread1:Family="ANSI Unified Screw Threads" Thread1:Designation="7/16-18 UNS"
```

--------------------------------

### Motion File Format Example - Autodesk Inventor

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-FECAD92B-D5EA-4B46-B8F6-EDC0C92F2608

Provides an example of the text file format required for custom motion data in Autodesk Inventor's cam generators. The file uses tab, semicolon, or pipe delimiters and contains position and elevation values.

```text
0;0
0.1;0.028
0.2;0.104
0.3;0.216
0.4;0.352
0.5;0.5
0.6;0.648
0.7;0.784
0.8;0.896
0.9;0.972
1;1
```

--------------------------------

### Example iProperty Expression Syntax

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-9ED64200-A0CA-4F27-A308-9BF7ADB22D06

Demonstrates the syntax for creating an iProperty expression, which includes custom text and parameter/iProperty names enclosed in brackets. This expression is evaluated to display a combined value.

```autodesk inventor
_=DIN1026 - U 140 x <G_L> _

```

--------------------------------

### iPart Thread Parameters with Class - Existing

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-F30C4B36-98DE-4236-A2C6-B404F6E97CAC

This example illustrates an existing thread definition for an iPart, including the thread class. This is crucial for ensuring compatibility with replacement threads.

```text
Thread1:Family="ANSI Unified Screw Threads" Thread1:Designation="7/16-14 UNC" Thread1:style-class="1A"
```

--------------------------------

### Define Parameter: Add two values

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-49F96380-DE36-47B9-88BE-0C851A43D414

This example shows how to define a parameter by adding two values. The equal sign separates the parameter name ('DIST') from its calculated value. Inventor parses this expression to create the parameter and assign the result of the equation.

```inventor-expression
DIST = (4 mm + 25.4 mm)
```

--------------------------------

### iLogic DoubleForEquals Comparison Example

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-1DF09784-4ABD-4BA8-914B-3172866244EA

Demonstrates how the DoubleForEquals data type in iLogic handles floating-point comparisons, especially when dealing with potential round-off errors. This example shows a comparison that would fail with a standard Double but succeeds with DoubleForEquals due to its tolerance for single-precision comparison.

```VB.NET
If d0 = 13/16 Then ... 
```

--------------------------------

### iProperty Expression with Evaluated Value

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-9ED64200-A0CA-4F27-A308-9BF7ADB22D06

Shows an example of an iProperty expression after it has been evaluated. The parameter '<G_L>' is replaced by its actual value 'XYZ', resulting in a combined string.

```autodesk inventor
_DIN1026 - U 140 x XYZ_

```

--------------------------------

### Example: Measure Distance Between Points (iLogic)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-14C7DC35-2701-4238-A05D-7309C35744ED

A specific example demonstrating how to measure the minimum distance between two work points in iLogic. This is a common use case for verifying spacing or alignment between features.

```iLogic
distance = Measure.MinimumDistance("Work Point1", "Work Point2")
```

--------------------------------

### iPart Thread Parameters with Class - Replacement

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-F30C4B36-98DE-4236-A2C6-B404F6E97CAC

This example shows a replacement thread definition for an iPart, including the thread class. Matching the thread class between existing and replacement threads is essential to prevent generation errors.

```text
Thread1:Family="ANSI Unified Screw Threads" Thread1:Designation="7/16-18 UNS" Thread1:style-class="2A"
```

--------------------------------

### Sample CSV for Wire Import - Autodesk Inventor

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-30B323C1-2032-4469-AD2A-6E1C3DC3706A

This sample CSV file demonstrates the format for importing individual wires into an Autodesk Inventor harness assembly. It includes columns for Wire ID, Wire Name, connection points (RefDes1, Pin1, RefDes2, Pin2), class, and strip length. Lines starting with '//' are treated as comments.

```csv
//Wire ID,Wire Name,RefDes1,Pin1,RefDes2,Pin2,class,Strip Length
1004,16AWG-BLK,U4,2,J2,11,Data,0.2
1045,24AWG-RED,U4,3,J3,12,Power,0.1
1042,18AWG-ORG,TB1,15,J6,W,Data,0.25
1036,18AWG-BLK,J6,B,CB1,LN1,Ground,
1017,20AWG-WHT,CB2,LN5,J4,G,Neutral,
1034,22AWG-GRN,CB2,LD5,J2,12,,
```

--------------------------------

### Set MultiValue List for Parameters

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-6B4885C8-7E75-4FEA-8DEF-EA7D40F33EB3

These examples demonstrate how to set a list of available values for a parameter using MultiValue.SetList. This can include numerical values, equations, or string values, and can be applied to parameters within parts or components.

```VB.NET
MultiValue.SetList("d0", 0.5, 0.75, 1.0, 1.25)
```

```VB.NET
MultiValue.SetList("d0", "3/8", "d1 * 2", "d1 * 3")
```

```VB.NET
MultiValue.SetList("filename.ipt.str0", "Value1", "Value2")
```

```VB.NET
MultiValue.SetList("Part1:1", "d0", 0.5, 0.75, 1.0, 1.25)
```

--------------------------------

### Sample CSV for Cable and Wire Import - Autodesk Inventor

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-30B323C1-2032-4469-AD2A-6E1C3DC3706A

This sample CSV file illustrates the format for importing cables and their associated wires, as well as discrete wires, into an Autodesk Inventor harness assembly. It supports Cable ID and Conductor ID for defining cable structure. Lines starting with '//' are comments.

```csv
//Wire ID,Cable ID,Library Name,Conductor ID,REFDES 1,Pin 1,REFDES 2,Pin 2
1001,CA1,Belden 4C 22AWG,1,J1,2,J5,6
1002,CA1,Belden 4C 22AWG,2,J1,3,J5,7
1003,CA1,Belden 4C 22AWG,3,J1,11,J5,8
1004,CA1,Belden 4C 22AWG,4,J1,12,J5,9
1005,,18 AWG BLU,,SP1,2,J6,1
1005,,18 AWG BLU,,J3,2,J6,1
1006,,18 AWG BLK,,J3,3,J6,3
1007,,18 AWG RED,,J3,4,J6,2
1008,CA2,Belden 4C 22AWG,1,J2,1,J8,3
1009,CA2,Belden 4C 22AWG,2,J2,2,J8,4
1010,CA2,Belden 4C 22AWG,3,J2,3,J8,5
1011,CA2,Belden 4C 22AWG,4,J2,4,J8,6
```

--------------------------------

### Modify Inventor Deployment Shortcut Paths for New Server Domain

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-B3CA11B1-AE19-426D-8348-F59952C0DA55

This snippet shows how to update the Target and Start paths within an Autodesk Inventor deployment shortcut (.lnk file) when moving the deployment image to a new server domain. It replaces absolute server paths with new ones, ensuring clients can access the deployment from the updated location.

```text
Replace
```
\Server_Location\Shared_Folder\MyDeployConfig\Img\Setup.exe /qb /I \Server_Location\Shared_Folder\MyDeployConfig\Img\MyDeployConfig.ini /language en-us
```

with
```
\New_Server_Location\New_Shared_Folder\MyDeployConfig\Img\Setup.exe /qb /I \New_Server_Location\New_Shared_Folder\MyDeployConfig\Img\MyDeployConfig.ini /language en-us
```
```

--------------------------------

### Use Built-in Functions: Inverse Tangent

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-49F96380-DE36-47B9-88BE-0C851A43D414

Shows how to use Inventor's built-in functions, such as 'atan' (inverse tangent), to create complex expressions. This example calculates an angle based on the ratio of two side lengths, incorporating unit conversions.

```inventor-expression
30 deg + atan(4 in / 3 in)
```

--------------------------------

### Debugging External DLLs in Inventor

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-32B66838-22E4-4A0A-B5BB-862350C76B36

External .NET DLLs can be debugged by setting the project's build output path to the Inventor Bin folder (e.g., 'iLogicAdd') and configuring Visual Studio to start Inventor.exe as the external program. This enables debugging features like Edit and Continue.

```text
Project Properties -> Compile -> Output path: [Inventor Install Path]\Bin\iLogicAdd
Project Properties -> Debug -> Start external program: [Inventor Install Path]\bin\Inventor.exe
```

--------------------------------

### Format Text File for Spline Tangency Points

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-566567EE-D657-4BC5-B330-05B423B43049

Defines the structure for a text file used to input tangency points for splines in Autodesk Inventor. It includes formats for comments, tangent values, and point coordinates, along with an example.

```plaintext
// comments  |  You can include one or more lines of commentary in the file. Each line must start with “//”. Comment lines are optional. The value they provide is that you can note the purpose of the spline.  
---|---  
[Tangents] T1 T2  | Specify the value of the tangent for the beginning (T1) and ending (T2) points of the sector. These values are shown as the “initial” and “final” slope in the user interface. If no value is supplied, an implied tangent value of 0.0 (horizontal tangent) is assumed. As with comment lines, this line is optional, but as noted, where no tangent value is given some assumptions must be made.  
X 1 Y 1 | the list of point coordinates, you can list as many points as you need. Specify one point per row.  
Example  |  //  // Simulation input spline points  // Value: Joint Torque (N mm)  // Reference: Time s  [Tangents] -3.40775 -5.27803  +0.000 +0.000  +4.313 +1.510  +7.954 -9.756  +1.000 +0.000  
```

--------------------------------

### iLogic Vault Workflow Enhancements in Inventor 2024

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-A0B07812-EB30-4898-B53E-1112CF02DB2C

This section details new iLogic functions in Inventor 2024 that simplify Vault integration. It enables automation of tasks like checking out files, getting files, and searching Vault. The description notes that this functionality requires Vault Professional and does not interface with Vault Basic. Code snippets are available in the editor to aid quick implementation.

```text
Note: iLogic Vault code requires Vault Professional and will not interface with Vault Basic.
```

--------------------------------

### Set Excel Data Start Row - GoExcel.FindRowStart

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-E897A20C-3859-435A-AA5F-8B6D5921FFAE

The GoExcel.FindRowStart property specifies the first row in an Excel spreadsheet that contains actual data. This is used in conjunction with functions like GoExcel.FindRow. The default value is 2, assuming one title row. Adjust this value if you have multiple title rows or no title rows.

```VBA
GoExcel.FindRowStart = 2
```

```VBA
GoExcel.FindRowStart = 3
```

--------------------------------

### Assigning iProperties from iLogic Parameters (VB.NET)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-9372F2A9-377E-40AB-92AA-5FC371BACF8C

Shows how to set Inventor iProperty values using text and true/false parameters defined within an iLogic rule. The 'Project' and 'Custom' categories are used as examples.

```vb.net
iProperties.Value("Project","Description") = string1
iProperties.Value("Custom","Passed") = boolean1
```

--------------------------------

### iLogic Select Case Statement with Range and Relational Operators

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-4D3AE24D-A418-4E43-AE05-B3A7918ABBA7

Shows how to use various formats within Case clauses, including comma-separated lists, ranges (To), and relational operators (Is). This example categorizes plate sizes.

```vbnet
Select Case width
Case 1,2,3,4,5
MessageBox.Show("Small Plate", "Size")
Case 6 to 15
MessageBox.Show("Medium Plate", "Size") 
Case Is > 15
MessageBox.Show("Large Plate", "Size")
End Select
```

--------------------------------

### Get Document Path (iLogic)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-622DED58-5CCB-423C-89E6-57ABBEB139A5

Retrieves the folder path of the current Inventor document as a text string. No dependencies are required. Returns the path string.

```iLogic
ThisDoc.Path
```

--------------------------------

### Get Workspace Path (iLogic)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-622DED58-5CCB-423C-89E6-57ABBEB139A5

Returns the path of the active Inventor project workspace. If no workspace is defined, it returns an empty string. No arguments are needed.

```iLogic
ThisDoc.WorkspacePath()
```

--------------------------------

### Use Fractional Input Strings: Feet and Inches

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-49F96380-DE36-47B9-88BE-0C851A43D414

Demonstrates entering fractional values for imperial units (feet and inches) using specific formatting. The single quotation mark (') for feet and double quotation mark (") for inches are required. This format is retained and displayed appropriately based on the unit system.

```inventor-expression
10'-6 1/2"
```

--------------------------------

### Example: Measure Distance Between Components (iLogic)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-14C7DC35-2701-4238-A05D-7309C35744ED

Illustrates measuring the minimum distance between two specific components in an assembly using their names in iLogic. This provides a simplified way to check component separation.

```iLogic
distance = Measure.MinimumDistance("partA:1", "partB:1")
distance = Measure.MinimumDistance("Wheel1", "Wheel2")
```

--------------------------------

### Use Internal Parameters: Radians and Degrees

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-49F96380-DE36-47B9-88BE-0C851A43D414

Illustrates using Inventor's internal parameters like PI and converting between radians and degrees. This allows for more concise and readable expressions when dealing with trigonometric or angular calculations.

```inventor-expression
(PI rad/ 4ul + (35 deg * PI rad / 180 deg))
```

--------------------------------

### Using Isolate Function for Unit Consistency in Inventor

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-EE98BCED-5623-4E3B-9E98-432C6738B081

Demonstrates the use of the 'isolate' function in Autodesk Inventor to maintain unit consistency within equations that involve parameters with different unit types. This example shows how to calculate pattern occurrences based on a parameter named 'Width'.

```autodesk-inventor-equations
isolate(Width;mm;ul)
```

--------------------------------

### Example: Measure Distance Plane to Plane (iLogic)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-14C7DC35-2701-4238-A05D-7309C35744ED

Shows how to measure the minimum distance between two work planes in iLogic. This function is valuable for checking the gap between planar surfaces or the thickness of components.

```iLogic
distance = Measure.MinimumDistance(“Work Plane1”, “Work Plane2”)
```

--------------------------------

### Get Path and Filename (iLogic)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-622DED58-5CCB-423C-89E6-57ABBEB139A5

Retrieves the full path and filename of the current Inventor document. An optional boolean argument controls whether the file extension is included. Returns the path and filename string.

```iLogic
ThisDoc.PathAndFileName(False) ' Without extension
ThisDoc.PathAndFileName(True) ' With extension
```

--------------------------------

### Unit Prefixes in Inventor Expressions

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-0106478A-B340-4164-A81B-866062877D60

Shows how to use unit prefixes in Autodesk Inventor expressions by entering the prefix symbol instead of the full name. It provides examples of common prefixes and their corresponding symbols and values, noting that prefix symbols are case-sensitive.

```Inventor Expressions
3.5 ul * 2.6 nm
```

--------------------------------

### Get Thread Type of Hole/Threaded Feature (iLogic)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-5B7BB5EF-1516-43AE-9C3A-FC5ACDC95555

Retrieves the current thread type of a specified hole or threaded feature. Examples of thread types include 'ANSI Unified Screw Threads' and 'ANSI Metric M Profile'. To modify the thread type, use the Feature.SetThread function.

```iLogic
currentType = Feature.ThreadType("featurename")
' Alternatively, for a component:
currentType = Feature.ThreadType("componentName", "featurename")
```

--------------------------------

### Linear Motion Formulas for Cam Calculation

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-944089A6-3061-405A-B250-0C774C474C5E

Formulas for calculating lift, speed, acceleration, and pulse for linear motion in cams. This simple motion causes significant shock at the start and end, and is rarely recommended without modifications.

```text
Lift: f_y(z) = z
Speed: f_v(z) = 1
Acceleration: f_a(z) = 0
Pulse: f_j(z) = 0
Note: For z = 0 and z = 1, the proper value should be infinite, but zero is used in calculations.
```

--------------------------------

### If-Then-Else Statement Format - iLogic

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-808441CB-4CCC-468C-9C44-FB1299500DF4

This format defines a conditional block where a specific set of statements is executed if the condition is true, and an alternative set is executed if the condition is false. It requires a clear start with '_If', a condition, '_Then', the true statements, '_Else', the false statements, and '_End If'.

```iLogic
_If <conditional expression> Then_
_<one or more statements to be executed if condition is true>_
_Else_
_<one or more statements to be executed if condition is false>_
_End If_
```

--------------------------------

### Use Unitless Values: Exponents

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-49F96380-DE36-47B9-88BE-0C851A43D414

Explains how to represent and use unitless values in Inventor expressions by appending 'ul'. This ensures clarity, especially when performing operations like exponentiation where units might otherwise be ambiguous.

```inventor-expression
3 mm * ((3 ul) ^ 2 ul)
```

--------------------------------

### Get Model Document from Drawing in iLogic

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-FA2587E0-8106-466C-AEDC-93CF9F6497C7

This function retrieves the model document (part or assembly) associated with a drawing document. If no model is present or multiple models exist, it returns the first one found. Access it using '_doc = ThisDoc.ModelDocument_'.

```VB.NET
_doc = ThisDoc.ModelDocument
```

--------------------------------

### COM Interface Methods for Custom Tasks

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-F0C878E0-E0B6-41D1-9E95-33BFEC5EC3CC

Defines the essential methods for a COM component to interact with Inventor's Task Scheduler. These methods manage task initiation, options, and process identification. Reference 'ServiceModuleInterfaceDef.tlb' for implementation details.

```C++
HRESULT StartTask();
HRESULT KillTask(void);
HRESULT SetOptions ([in] VARIANT varOptions);
HRESULT GetInventorProcessID([in, out] SAFEARRAY(long)* ppsaInventorProcIDs);
HRESULT SetCommand)(*[in} enumTaskCmd enumTaskCmd);
```

--------------------------------

### Using Inventor Parameters as VB.NET Variables (VB.NET)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-EF53484C-D750-41F8-9AB1-032B73BB071F

Illustrates how Inventor parameters can be treated as Visual Basic variables within iLogic rules. Parameter values are read into variables when the rule starts and saved back to the model when the rule finishes.

```vb.net
d1 = d0 * 0.5
```

--------------------------------

### Get View Properties

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-89DC0590-BE14-47E6-B83A-0A8F5B2163AA

Retrieves properties of a view, including its name, height, and width in drawing document units.

```iLogic
viewName = myView.Name
viewHeight = myView.Height
viewWidth = myView.Width
```

--------------------------------

### Running Rules with Arguments (IiLogicAutomation)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-32B66838-22E4-4A0A-B5BB-862350C76B36

The IiLogicAutomation interface provides functions to run rules with custom arguments. This allows modifying rule behavior without creating duplicates. Arguments are passed using an Inventor.NameValueMap object.

```VB.NET
Function RunRuleWithArguments(ByVal doc As Inventor.Document, ByVal ruleName As String, ByVal ruleArguments As Inventor.NameValueMap) As Integer
Function RunExternalRuleWithArguments(ByVal doc As Inventor.Document, ByVal ruleName As String, ByVal ruleArguments As Inventor.NameValueMap) As Integer
Function RunRuleDirectWithArguments(ByVal rule As iLogicRule, ByVal ruleArguments As Inventor.NameValueMap) As Integer
```

--------------------------------

### Get Active Sheet Properties

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-89DC0590-BE14-47E6-B83A-0A8F5B2163AA

Retrieves properties of the active sheet, including its name, size (as a string), height, and width in document units.

```iLogic
sheetName = ActiveSheet.Name
sheetSize = ActiveSheet.Size
sheetHeight = ActiveSheet.Height
sheetWidth = ActiveSheet.Width
```

--------------------------------

### Create Relative Path Batch File for Inventor Deployment

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-B3CA11B1-AE19-426D-8348-F59952C0DA55

This snippet demonstrates how to create a batch (.BAT) file containing a relative path for an Autodesk Inventor deployment shortcut. This method is an alternative to directly modifying .lnk files, as it bypasses Windows' limitations with relative paths in shortcuts, enabling deployment from various locations.

```batch
Copy the original Target line:
```
\Server_Location\Shared_Folder\MyDeployConfig\Img\Setup.exe /qb /I \Server_Location\Shared_Folder\MyDeployConfig\Img\MyDeployConfig.ini /language en-us
```

Paste this into a text file and rename it so the extension is .BAT. Save this file in the SAME directory as the original shortcut.

Modify the pasted Target line to be relative as:
```
.\MyDeployConfig\Img\Setup.exe /qb /I .\MyDeployConfig\Img\MyDeployConfig.ini /language en-us
```

Save the .BAT file.
```

--------------------------------

### Get Current MultiValue List

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-6B4885C8-7E75-4FEA-8DEF-EA7D40F33EB3

Retrieves the current list of values for a specified parameter. The returned list is a VB.NET ArrayList object.

```VB.NET
values = MultiValue.List("d0")
```

--------------------------------

### Use Mixed Units: Inches and Millimeters

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-49F96380-DE36-47B9-88BE-0C851A43D414

Demonstrates using mixed units (inches and millimeters) within an expression. Conversion factors are used to ensure correct calculation when combining different unit types. This ensures accurate results regardless of the default system units.

```inventor-expression
(2 in + 4 mm * 1 in / 25.4 mm)
```

--------------------------------

### Check for Hardware Conflicts using msinfo32

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-D6B5DFF4-7888-4A66-BCA4-380050EF8366

This procedure explains how to use the System Information tool (msinfo32) to identify hardware conflicts that may be affecting Inventor's performance. It helps in pinpointing devices that share resources and advises on updating drivers.

```text
1. Open System Information: Press Win + R, type msinfo32, and press Enter.
2. Navigate to Conflicts/Sharing: In the left pane, expand Hardware Resources and select Conflicts/Sharing.
3. Identify Conflicts: Note any devices listed as conflicting, especially those related to the graphics or network card.
4. Update Drivers: Update the drivers for the identified conflicting devices.
```

--------------------------------

### Get or Set View Scale

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-89DC0590-BE14-47E6-B83A-0A8F5B2163AA

Retrieves or sets the scale of a view. The scale can be accessed or modified either as a numerical value or as a text string (e.g., '1:2', '4.1').

```iLogic
viewScaleNumber = myView.Scale
viewScaleString = myView.ScaleString

myView.Scale = 1.5
myView.ScaleString = "1:2"
```

--------------------------------

### Extended Block If (If-Then-ElseIf) Statement Format - iLogic

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-808441CB-4CCC-468C-9C44-FB1299500DF4

This format provides a way to check multiple conditions sequentially. It starts with an '_If' for the first condition, followed by optional '_ElseIf' blocks for subsequent conditions, and concludes with an optional '_Else' block for cases where none of the preceding conditions are met. Each block must end with '_End If'.

```iLogic
_If <conditional expression 1> Then_
_<one or more statements to be executed if condition 1 is true>_
_ElseIf <conditional expression 2> Then_
_<one or more statements to be executed if condition 2 is true>_
...
_ElseIf <conditional expression n> Then
__<one or more statements to be executed if condition n is true>
__Else
__<one or more statements to be executed if none of the above conditions is true>__
End If_
```

--------------------------------

### Launch File (iLogic)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-622DED58-5CCB-423C-89E6-57ABBEB139A5

Launches a specified file using its path and filename. If no path is provided, iLogic searches in the document's folder. It can open data files with associated applications.

```iLogic
ThisDoc.Launch("path\file.ext")
```

--------------------------------

### VB.NET Boolean Parameter Example in iLogic

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-9372F2A9-377E-40AB-92AA-5FC371BACF8C

Illustrates assigning Boolean values (True or False) to VB.NET variables in iLogic rules. These values do not require surrounding quotes.

```vb.net
boolean1 = True
boolean2 = False
```

--------------------------------

### JT File Export Configuration Options

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-68FCAD0E-93BD-4D90-B9FE-9CF82AA4E64D

Configuration file settings for exporting to JT format, controlling Brep inclusion, Brep type, assembly structure, and file version. These options allow fine-tuning of the exported JT file's content and organization.

```INI
includeBrep = true
includeGeom = true

# Brep Only
# includeBrep = true
# includeGeom = false

# Facets Only
# includeBrep = false
# includeGeom = true

# Brep type
# autoXtBrep = true
# autoXtBrep = false

# Structure
# structureOption = "MONOLITHIC"
# structureOption = "PER_PART"
# structureOption = "FULL_SHATTER"

# Version
# JtFileFormat = "80"
# JtFileFormat = "105"
```

--------------------------------

### Contig Command-Line Usage for Fragmentation Analysis and Defragmentation

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-D6B5DFF4-7888-4A66-BCA4-380050EF8366

This code snippet demonstrates the command-line usage of the Contig utility for analyzing file fragmentation and performing defragmentation. It is useful for optimizing Inventor program files or other critical application data on disk.

```bash
Contig /a *.*
Contig /s *.*
```

--------------------------------

### Get Current Row Value (iLogic)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-020555BE-6197-4D27-8B31-A4D62E2CC2E8

Retrieves the cell value from the current row of an iFeature, typically after a row has been found using iFeature.FindRow. Supports both numerical and string values.

```iLogic
i = iFeature.FindRow("RectangularPocket1", "pocketdepth", "=", 0.250)
pocketlength = iFeature.CurrentRowValue("pocketlength")
pocketwidth = iFeature.CurrentRowValue("pocketwidth")

```

```iLogic
Part_number = iFeature.CurrentRowStringValue("Part Number")

```

--------------------------------

### Sketch Pattern Performance Improvement in Inventor

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-A0B07812-EB30-4898-B53E-1112CF02DB2C

This code snippet describes a general performance enhancement for sketch-driven patterns in Inventor. The improvement applies not only to the computation of these patterns but also to the highlighting of pattern occurrences when the mouse hovers over them in the browser view. This aims to provide a smoother user experience.

```text
This is a general improvement for sketch driven pattern, not only for compute, but also for highlighting a sketch driven pattern occurrence when moving the mouse on the browser view.
```

--------------------------------

### VB.NET String Parameter Example in iLogic

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-9372F2A9-377E-40AB-92AA-5FC371BACF8C

Demonstrates how to assign a string value to a VB.NET variable within an iLogic rule. String values must be enclosed in double quotes.

```vb.net
string1 = "Left Side"
```

--------------------------------

### Running Rules with Arguments (iLogicVB)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-32B66838-22E4-4A0A-B5BB-862350C76B36

The iLogicVB interface offers functions to execute rules with arguments, enabling dynamic rule adjustments. Arguments are provided via an Inventor.NameValueMap.

```VB.NET
Function RunRule(ByVal ruleName As String, ByVal ruleArguments As Inventor.NameValueMap) As Integer
Function RunRule(ByVal compoOrDocName As Object, ByVal ruleName As String, ByVal ruleArguments As Inventor.NameValueMap) As Integer
Function RunExternalRule(ByVal ruleName As String, ByVal ruleArguments As Inventor.NameValueMap) As Integer
```

--------------------------------

### Set or Get Current Sheet Border

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-89DC0590-BE14-47E6-B83A-0A8F5B2163AA

Assigns or retrieves the name of the current border on the sheet. The specified border name must exist in the drawing resources or the defined ResourceFileName drawing.

```iLogic
ActiveSheet.Border = "OtherBorder"
```

```iLogic
currentName = ActiveSheet.Border
```

--------------------------------

### Capture Current State for Constraints.Add in iLogic

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-C5ADE109-10E9-41A0-BC4A-BE73AA68A1C7

Generates the Constraints.Add function to create a new constraint from a selected file within an iLogic rule. This enables automated constraint creation in assemblies.

```VB.NET
Constraints.Add(constraintName, geom1, geom2)
```

--------------------------------

### Autodesk Inventor Reserved System Parameters

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-EE98BCED-5623-4E3B-9E98-432C6738B081

Lists the predefined system parameters in Autodesk Inventor, PI and E, along with their numerical values. These constants can be directly used within equations.

```autodesk-inventor-equations
PI 3.14159265358979323846264338328
```

```autodesk-inventor-equations
E 2.71828182845904523536
```

--------------------------------

### Get Flat Pattern Extents (iLogic)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-B6A1BDDF-F2D4-4C42-9466-4754910BB714

Provides functions to obtain the dimensions of the unfolded flat pattern. These include length (X), width (Y), and area (X*Y) of the flat pattern extents.

```iLogic
SheetMetal.FlatExtentsLength

```

```iLogic
SheetMetal.FlatExtentsWidth

```

```iLogic
SheetMetal.FlatExtentsArea

```

--------------------------------

### Example: Measure Distance Between Planes in Assembly (iLogic)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-14C7DC35-2701-4238-A05D-7309C35744ED

Demonstrates measuring the distance between work planes of two different components within an assembly using iLogic. This is key for analyzing spatial relationships between parts.

```iLogic
distance = Measure.MinimumDistance(“Wheel1”, “Workplane1”, “Wheel2”, Workplane2”)
```

--------------------------------

### Spring Calculation: Spring Output Parameters

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-41EC6C7F-D976-4EFA-8E15-756084A514D0

This section covers the calculation of common spring output parameters, performed in a specific order. It includes formulas for hook height factor, spring constant, and length of the coiled part, with variations for springs with and without initial tension.

```General
Common for all types of spring calculation, and calculated in the following order.
```

```General
Spring without initial tension
---
|  L z = t n + d [in]
```

```General
Spring with initial tension
|  L z = 1.03 (n + 1) d [in]
```

--------------------------------

### Example: Measure Distance Axis to Axis (iLogic)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-14C7DC35-2701-4238-A05D-7309C35744ED

Provides an iLogic code snippet for measuring the minimum distance between two work axes. This is useful for determining the separation between linear features or hole centerlines.

```iLogic
distance = Measure.MinimumDistance("Work Axis1", "Work Axis2")
```

--------------------------------

### Get Document Filename (iLogic)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-622DED58-5CCB-423C-89E6-57ABBEB139A5

Retrieves the filename of the current Inventor document. An optional boolean argument controls whether the file extension is included. Returns the filename string.

```iLogic
ThisDoc.FileName(False) ' Without extension
ThisDoc.FileName(True) ' With extension
```

--------------------------------

### Prompt for User Input (iLogic/VB.NET)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-900B9ACC-861D-4301-AAFA-7BCEAF306066

Creates a dialog box that prompts the user for text input. It accepts a prompt message, a window title, and an optional default entry for the input field. The entered value is returned.

```VB.NET
myparam = InputBox("Prompt", "Title", "Default Entry")
```

--------------------------------

### Find iPart/iAssembly Row by Criteria (iLogic)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-4BA100AA-B55A-4A08-AD8F-79AA27771C7E

Searches an iPart or iAssembly table for a row that matches specific criteria in given columns. It then sets the active configuration to the found row. Useful for dynamic configuration selection based on multiple parameters.

```iLogic
iPart.FindRow("port_1_flange_screw", "Thread_Diameter", ">=", 0.45, "Thread_Length", ">=", 2.0)
```

--------------------------------

### Spring Calculation: Limit Force and Deflection Formulas

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-AC82433B-23FF-4FE5-A6C3-84FE7B92BC39

This section details the formulas for the spring limit force (F9) and the deflection at the limit state (s9). It defines the variables used, including spring constant (k) and initial spring tension (F0), which are essential for understanding the spring's behavior at its operational limits.

```text
**Spring limit force**
**Deflection in limit state**
where: 
|  k  |  spring constant [N/mm]   
---|---|---
|  F 9 |  working force of spring loaded at limit [N]   
|  F 0 |  spring initial tension [N]   
```

--------------------------------

### Example: Measure Distance Point to Axis (iLogic)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-14C7DC35-2701-4238-A05D-7309C35744ED

Illustrates measuring the minimum distance between a work point and a work axis using iLogic. This function is applicable when assessing the relationship between a point feature and a linear feature.

```iLogic
distance = Measure.MinimumDistance(“Work Point1”, “Work Axis1”)
```

--------------------------------

### Enable Rule Tracing in iLogic

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-BE996AA3-DE49-4765-86A7-129DD7B42A4A

Shows how to enable detailed rule tracing messages by setting the active log level to Trace. This helps visualize when rules are entered, exited, and what triggers them.

```iLogic
iLogicVb.Automation.LogControl.RuleEntryExitMessageLevel = TraceLevel.Trace
```

--------------------------------

### Set or Get Current Sheet Title Block

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-89DC0590-BE14-47E6-B83A-0A8F5B2163AA

Assigns or retrieves the name of the current title block on the sheet. The title block name must be available in the current drawing's resources or the specified ResourceFileName drawing.

```iLogic
ActiveSheet.TitleBlock = "ANSI - A"
```

```iLogic
currentName = ActiveSheet.TitleBlock
```

```iLogic
ThisDrawing.ResourceFileName = "DrawingResources1.idw"
ActiveSheet.TitleBlock = "Custom - A"
```

--------------------------------

### Set MultiValue List using Alternative Method

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-6B4885C8-7E75-4FEA-8DEF-EA7D40F33EB3

An alternative method to set a list of values for a parameter using a Double array.

```VB.NET
MultiValue.List("d0") = New Double() {0.5, 0.75, 1.0, 1.25}
```

--------------------------------

### Update Device Drivers for Optimal Performance

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-D6B5DFF4-7888-4A66-BCA4-380050EF8366

Outdated or incorrect drivers for various hardware components can lead to performance degradation in Inventor. This section guides users to update drivers for essential devices through Device Manager and manufacturer websites.

```text
1. Open Device Manager: Press Win + R, type devmgmt.msc, and press Enter.
2. Identify Devices: Locate and note the manufacturers of devices such as Hard Disk Drives, Controllers, CD/DVD drives, Monitors, Network Cards, Sound Cards, Keyboards, Mice, and any 3D input devices or peripherals.
3. Download Latest Drivers: Visit the manufacturer's website for each device and download/install the latest available drivers or firmware.
```

--------------------------------

### API: Create Arc2d by Three Points in Inventor

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=Inventor_ReleaseNotes_updates_2025_1_fixed_bugs_july_html

This snippet demonstrates the use of the `CreateArc2dByThreePoints2` method for creating an arc with three points, replacing the deprecated `CreateArc2dByThreePoints` method in Inventor's 2D Sketch API. It addresses an issue where the Pattern command might prepend values, leading to errors.

```C#
using Inventor;
using System;

public void CreateArcExample(PlanarSketch sketch) {
    try {
        Point p1 = sketch.InventorDocument.Application.TransientGeometry.CreatePoint(0, 0, 0);
        Point p2 = sketch.InventorDocument.Application.TransientGeometry.CreatePoint(1, 0, 0);
        Point p3 = sketch.InventorDocument.Application.TransientGeometry.CreatePoint(1, 1, 0);
        
        // Use the new method to create an arc
        Arc2d newArc = sketch.SketchCurves.CreateArc2dByThreePoints2(p1, p2, p3);
        
        // The old method is deprecated and should not be used:
        // Arc2d oldArc = sketch.SketchCurves.CreateArc2dByThreePoints(p1, p2, p3);

        Logger.Log("Arc created successfully.");
    } catch (Exception ex) {
        Logger.LogError("Error creating arc: " + ex.Message);
    }
}
```

--------------------------------

### Capture Current State for Components.Add in iLogic

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-C5ADE109-10E9-41A0-BC4A-BE73AA68A1C7

Generates the Components.Add function to create a component from a selected file within an iLogic rule. This is useful for automating the addition of components to an assembly.

```VB.NET
Components.Add("path/to/component.ipt")
```

--------------------------------

### Get Current Document in iLogic

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-FA2587E0-8106-466C-AEDC-93CF9F6497C7

This function retrieves the Inventor Document object for the rule currently being executed. It is essential for examining or modifying the active model. The document can be accessed via '_doc = ThisDoc.Document' or the older syntax '_doc = iLogicVb.RuleDocument_'.

```VB.NET
_doc = ThisDoc.Document
```

```VB.NET
_doc = iLogicVb.RuleDocument
```

--------------------------------

### Set MultiValue List from iProperties Materials

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-6B4885C8-7E75-4FEA-8DEF-EA7D40F33EB3

Assigns a list of available materials from the active iProperties standard to a text parameter.

```VB.NET
MultiValue.List("MyStringParam") = iProperties.Materials
```

--------------------------------

### Defragment Inventor Program Files using Contig

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-D6B5DFF4-7888-4A66-BCA4-380050EF8366

Defragmenting Inventor program files can improve startup times and document opening speeds, especially for large assemblies. This snippet details using the Contig utility from Sysinternals to analyze and defragment Inventor's program files.

```text
1. Download Contig: Obtain contig.exe from Microsoft Sysinternals and place it in a folder included in your system's PATH environment variable (e.g., C:\\Windows).
2. Open Command Prompt: Press Win + R, type CMD, and press Enter.
3. Navigate to Inventor Bin Folder: Change directory to your Inventor installation's Bin folder (e.g., cd "C:\\Program Files\\Autodesk\\Inventor <version>\\Bin").
4. Check Fragmentation: Run "Contig /a *.*" to check the average fragmentation of files.
5. Defragment Files: If fragmentation is high (average > 1.5 fragments/file), run "Contig /s *.*" to defragment files in the current folder and subfolders.
6. Reboot: Restart your computer after defragmentation.
```

--------------------------------

### Min and Max Functions (Min, Max, MinOfMany, MaxOfMany)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-8F529B43-8779-42BB-A8C1-39F091C1FC31

iLogic provides functions to find the minimum and maximum of two or multiple arguments. Min() and Max() compare two values, while MinOfMany() and MaxOfMany() compare lists of values. These are standard VB.NET Math functions.

```VB.NET
// Compare two arguments
Min(2, 4) = 2
Max(2, 4) = 4

// Compare multiple arguments
MinOfMany(2,4,3,6,7,8) = 2
MaxOfMany(2,4,3,6,7,8) = 8
```

--------------------------------

### Basic and Complex Equations in Autodesk Inventor

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-0106478A-B340-4164-A81B-866062877D60

Demonstrates the use of simple and complex mathematical equations for numeric parameters within Autodesk Inventor. These equations can involve basic arithmetic, unit conversions, and system-defined constants like PI.

```Inventor Expressions
2 ul *(6+3)
```

```Inventor Expressions
(PI rad/5 ul +(25 deg *PI rad)/180 deg))
```

--------------------------------

### Get Inventor Part Feature in iLogic

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-FA2587E0-8106-466C-AEDC-93CF9F6497C7

This function provides direct access to a part feature within an Inventor model. It returns an object of type Inventor.PartFeature for further programmatic control. Access it using '_feat = Feature.InventorFeature("featureName")_'.

```VB.NET
_feat = Feature.InventorFeature("featureName")_
```

--------------------------------

### Spring Calculation: Deflection Formulas

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-AC82433B-23FF-4FE5-A6C3-84FE7B92BC39

This section defines the formulas for calculating preloaded spring deflection (s1) and total spring deflection (s8). These calculations are essential for understanding how much a spring compresses or extends under different load conditions.

```text
**Pre loaded spring deflection**
s 1 = L 1 - L 0 [mm] 
**Total spring deflection**
s 8 = L 8 - L 0 [mm]
```

--------------------------------

### Autodesk Inventor Unit Prefixes and Symbols

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-EE98BCED-5623-4E3B-9E98-432C6738B081

Details the unit prefixes supported in Autodesk Inventor equations, including their symbols and numerical values. This allows for precise unit conversions and calculations.

```autodesk-inventor-equations
exa (E) 1.0e18
```

```autodesk-inventor-equations
peta (P) 1.0e15
```

```autodesk-inventor-equations
tera (T) 1.0e12
```

```autodesk-inventor-equations
giga (G) 1.0e9
```

```autodesk-inventor-equations
mega (M) 1.0e6
```

```autodesk-inventor-equations
kilo (k) 1.0e3
```

```autodesk-inventor-equations
hecto (v) 1.0e2
```

```autodesk-inventor-equations
deca (da) 1.0e1
```

```autodesk-inventor-equations
deci (d) 1.0e-1
```

```autodesk-inventor-equations
centi (c) 1.0e-2
```

```autodesk-inventor-equations
milli (m) 1.0e-3
```

```autodesk-inventor-equations
micro (micro) 1.0-6
```

```autodesk-inventor-equations
nano (n) 1.0-9
```

```autodesk-inventor-equations
Pi co (p) 1.0e-12
```

```autodesk-inventor-equations
femto (f) 1.0-15
```

```autodesk-inventor-equations
atto (a) 1.0e-18
```

--------------------------------

### Get Active Sheet Metal Style (iLogic)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-B6A1BDDF-F2D4-4C42-9466-4754910BB714

Reads the currently active Sheet Metal Rule. The retrieved style name can be assigned to an iLogic text parameter or a local variable for further use in rules, enabling conditional model manipulation.

```iLogic
CurrentStyleParameter=SheetMetal.GetActiveStyle()

```

--------------------------------

### Autodesk Inventor Supported Mathematical Functions

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-EE98BCED-5623-4E3B-9E98-432C6738B081

Provides a list of mathematical functions available in Autodesk Inventor, including trigonometric, hyperbolic, and general-purpose functions. Each function specifies its return unit type and expected input unit type, along with any specific notes on usage or limitations.

```autodesk-inventor-equations
cos(expr)
```

```autodesk-inventor-equations
sin(expr)
```

```autodesk-inventor-equations
tan(expr)
```

```autodesk-inventor-equations
acos(expr)
```

```autodesk-inventor-equations
asin(expr)
```

```autodesk-inventor-equations
atan(expr)
```

```autodesk-inventor-equations
cosh(expr)
```

```autodesk-inventor-equations
sinh(expr)
```

```autodesk-inventor-equations
tanh(expr)
```

```autodesk-inventor-equations
acosh(expr)
```

```autodesk-inventor-equations
asinh(expr)
```

```autodesk-inventor-equations
atanh(expr)
```

```autodesk-inventor-equations
sqrt(expr)
```

```autodesk-inventor-equations
sign(expr)
```

```autodesk-inventor-equations
exp(expr)
```

```autodesk-inventor-equations
floor(expr)
```

```autodesk-inventor-equations
ceil(expr)
```

```autodesk-inventor-equations
round(expr)
```

```autodesk-inventor-equations
abs(expr)
```

```autodesk-inventor-equations
max(expr1;expr2)
```

```autodesk-inventor-equations
min(expr1;expr2)
```

```autodesk-inventor-equations
ln(expr)
```

```autodesk-inventor-equations
log(expr)
```

```autodesk-inventor-equations
pow(expr1;expr2)
```

```autodesk-inventor-equations
random(expr)
```

```autodesk-inventor-equations
isolate(expr;unit;unit)
```

--------------------------------

### Get iPart Active Row Number

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-4BA100AA-B55A-4A08-AD8F-79AA27771C7E

Returns the numerical index of the currently active row within an iPart or iAssembly component instance. This can be used to identify the specific row being worked with, and subsequently retrieve its values using other iPart functions.

```iLogic
rowNumber = iPart.RowNumber("port_1_flange_screw:1")
```

--------------------------------

### Access Inventor Application Object in iLogic

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-FA2587E0-8106-466C-AEDC-93CF9F6497C7

This function provides access to the main Inventor application object for the current session. It serves as the entry point to the Inventor API, allowing direct interaction with Inventor functionalities. It can be accessed using both the newer 'ThisApplication' syntax and the older 'app = InventorVb.Application' syntax.

```VB.NET
app = ThisApplication
```

```VB.NET
app = InventorVb.Application
```

--------------------------------

### Get Inventor Component Occurrence in iLogic

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-FA2587E0-8106-466C-AEDC-93CF9F6497C7

This function retrieves a direct reference to a component occurrence within an Inventor model. It returns an object of type Inventor.ComponentOccurrence, allowing manipulation of specific components. Use '_compo = Component.InventorComponent("componentName")_' to access it.

```VB.NET
_compo = Component.InventorComponent("componentName")_
```

--------------------------------

### iLogic If...Then...Else...EndIf Syntax

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-52017003-BF2A-4643-99BD-102A117935FF

This snippet demonstrates the basic structure of an If...Then...Else...EndIf statement in iLogic. It allows for different actions to be performed based on whether a condition evaluates to true or false. Use the 'If...Then...EndIf' and 'Else' snippets from the iLogic Edit Rule dialog.

```iLogic
If My_expression Then
    ' Action to perform if true
Else
    ' Action to perform if false
End If
```

--------------------------------

### Get iPart Active Row Member Name

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-4BA100AA-B55A-4A08-AD8F-79AA27771C7E

Retrieves the member name of the currently active row for an iPart or iAssembly component instance. This function is particularly useful in rules triggered by component change events, allowing logic to react to the selected row.

```iLogic
memberName = iPart.RowName("port_1_flange_screw:1")
```

--------------------------------

### Spring Design: Input Value Checking and Parameter Calculation

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-AC82433B-23FF-4FE5-A6C3-84FE7B92BC39

This section details the initial checks performed on input values for spring design calculations. It also specifies the parameters that are designed to ensure the spring hook height conforms to the selected hook type, while also fulfilling strength and geometric conditions.

```text
**Specified maximum working force, determined material, assembly dimensions, and spring diameter**
First the input values for the calculation are checked and calculated.
Then the wire diameter, number of coils, spring free length, and the F 1 minimum working force are designed, so that the spring hook height conforms the selected hook type.
The strength and geometric conditions also must be fulfilled.
```

--------------------------------

### Dynamic Factor (Kfv) Calculation (ISO and DIN)

Source: https://help.autodesk.com/view/INVNTOR/2025/ENU/index_guid=GUID-6E2214C0-AA32-4B6F-8D48-660473C28C8F

Details the dynamic factor (Kfv) calculation for bending under ISO and DIN standards. It includes considerations for the ratio of tangential force to face width and references table values.

```text
for ISO and DIN: 
 at K A F t / b w < 100 considering K A F t / b w = 100 
 where: K P , K Q ... table values
```