Collection that provides access to all of the existing setups in a document.
| Name | Description |
| add |
Creates a new setup. |
| classType |
Static function that all classes support that returns the type of the class as a string. The returned string matches the string returned by the objectType property. For example if you have a reference to an object and you want to check if it's a SketchLine you can use myObject.objectType == fusion.SketchLine.classType(). |
| createInput |
Creates a new SetupInput object that is used to specify the input needed to create a new setup. |
| item |
Function that returns the specified setup using an index into the collection. |
| itemByName |
Returns the setup with the specified name. |
| itemByOperationId |
Returns the setup with the specified operation id. |
| Name | Description |
| count | The number of setups in the collection. |
| isValid | Indicates if this object is still valid, i.e. hasn't been deleted or some other action done to invalidate the reference. |
| objectType | This property is supported by all objects in the API and returns a string that contains the full name (namespace::objecttype) describing the type of the object. It's often useful to use this in combination with the classType method to see if an object is a certain type. For example: if obj.objectType == adsk.core.Point3D.classType(): |
| Name | Description |
| Additive Manufacturing MJF API Sample | Demonstrates how to automate the creation of an additive MJF manufacturing setup and arrange components within the build volume of a 3D printer. To run the sample script, have a design with one or more components open in Fusion’s DESIGN workspace. This script will switch the UI from the DESIGN workspace to the MANUFACTURE workspace, create a new Manufacturing Model, and create an Additive Arrange using that manufacturing model as an input. The setup will select an MJF 3D printer from Fusion’s machine library and a print setting from the print setting library. All components in the Manufacturing model will be automatically arranged within the build volume of the selected MJF machine. |
| Create Setups From Hole Recognition API Sample | This sample script demonstrates how to create a correctly oriented setup using Hole Recognition functionality. The Fusion Manufacturing Extension is required for Hole Recognition. The script starts by opening a sample model from the CAM Samples folder via its URN. The model comprises a 3 way coupling containing holes in various orientations and mounted on a fixture. A reference setup is created for the model using a simple stock mode and offsets. The Hole Recognition feature of the Fusion Manufacturing Extension creates 5 hole groups containing 11 holes between them. For each unique hole group vector captured, a new setup is created and its orientation transformed to match the vector. |
| Generate Setup Sheets API Sample | Demonstrates generating the setup sheets for an existing toolpath. Before running: Run from Scripts and Add-Ins. This sample may open dialogs or require interactive choices; keep Fusion in the foreground. Use a design with CAM data as required by the script. Many CAM samples switch to the MANUFACTURE workspace and may need an existing setup or manufacturing model. |
| Generate Toolpaths API Sample | Demonstrates generating the toolpaths in the active document. Before running: Run from Scripts and Add-Ins. This sample may open dialogs or require interactive choices; keep Fusion in the foreground. Use a design with CAM data as required by the script. Many CAM samples switch to the MANUFACTURE workspace and may need an existing setup or manufacturing model. |
| Hole and Pocket Recognition API Sample | This sample script demonstrates three different methods for feature recognition: one for holes and two for pockets. The script starts by creating a simple component which is then used to demonstrate the three methods. After the features are recognized, they are colored and milling and drilling operations are created for each feature. RecognizedHoleGroup returns a list of BRepFaces that can be used as selections for the drilling operation. RecognizedPocket also returns some BRepFaces but it needs additional processing before the output can be used for creating machining operations. The sample script demonstrates a couple of different methods, including finding the pocket BRepFaces and creating sketches from the recognized pockets. This script works only if the Manufacturing Extension is active. |
| Manufacturing Workflow API Sample | Manufacturing Workflow API Sample. This sample script starts by creating a simple component, which is then used to describe a milling workflow. It creates a setup and a few operations, picks tools from a Fusion sample tool library using loops and queries, and post-processes the operations using an NC program. |
| Post Toolpaths API Sample | Demonstrates posting toolpaths in the active document using an NC program: import a post configuration from the post library, choose which setups or operations to include, set NC program and post parameters, and run Before running: Run from Scripts and Add-Ins with a design that contains at least one CAM setup with toolpaths. The script prompts for what to post (all setups, first setup, or first operation) and optionally opens the NC file when complete. It may offer to switch to the MANUFACTURE workspace. |
| Set Vise Origin As Setup WCS Origin API Sample | This sample script demonstrates how to define our setup WCS origin relative to our vise origin from either a component, a sketch point or a joint origin. The Work Coordinate System is a reference point set in our CAM workspace and on our machine. All machine coordinates are drawn from the WCS. This script demonstrates defining the WCS by each of 4 alternative methods: Setup by default with no origin defined. Setup using vise origin as WCS origin. Setup using a sketch point as WCS origin. Setup using a joint origin as WCS origin. |
| Turning Workflow API Sample | Turning Workflow API Sample. This sample script starts by opening a simple component, which is then used to describe a basic turning workflow. It creates a setup and a few operations, picks tools from a Fusion sample tool library using loops and queries, and post-processes the operations using an NC program. |