Assembly configurations in Solidworks - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new configuration named 'Config1' in SolidWorks assembly.

Solidworks

AssemblyDoc.AddConfiguration2("[1]", "", "");

Drag options to blanks, or click blank then click option'

AConfig1

BNewConfig

CAssemblyConfig

DDefault

Attempts:

3 left

💡 Hint

Common Mistakes

Using an incorrect configuration name string.

Leaving the name argument empty.

The method AddConfiguration2 requires the configuration name as the first argument. 'Config1' is the correct name to create the new configuration.

2fill in blank

medium

Complete the code to activate the configuration named 'Config2' in the assembly document.

Solidworks

AssemblyDoc.ShowConfiguration2("[1]", true);

Drag options to blanks, or click blank then click option'

AConfig1

BActiveConfig

CDefault

DConfig2

Attempts:

3 left

💡 Hint

Common Mistakes

Using a configuration name that does not exist.

Passing false instead of true to activate.

The method ShowConfiguration2 activates the configuration by its name. 'Config2' is the correct configuration to activate here.

3fill in blank

hard

Fix the error in the code to delete the configuration named 'Config3' from the assembly.

Solidworks

AssemblyDoc.DeleteConfiguration("[1]", true);

Drag options to blanks, or click blank then click option'

AConfig2

BConfig1

CConfig3

DDefault

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to delete a configuration that does not exist.

Using the wrong configuration name.

The DeleteConfiguration method requires the exact name of the configuration to delete. 'Config3' is the correct name here.

4fill in blank

hard

Fill both blanks to set the suppression state of a component named 'Part1' in configuration 'ConfigA'.

Solidworks

AssemblyDoc.Extension.SelectByID2("Part1", "COMPONENT", 0, 0, 0, false, 0, null, 0);
AssemblyDoc.SetSuppression2("[1]", [2]);

Drag options to blanks, or click blank then click option'

AConfigA

BswSuppressed

CswResolved

DConfigB

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong configuration name.

Using swResolved instead of swSuppressed.

The first argument to SetSuppression2 is the configuration name ('ConfigA'), and the second is the suppression state constant (swSuppressed) to suppress the component.

5fill in blank

hard

Fill all three blanks to create a new configuration 'ConfigX', set it active, and suppress a component 'PartX' in it.

Solidworks

AssemblyDoc.AddConfiguration2("[1]", "", "");
AssemblyDoc.ShowConfiguration2("[2]", true);
AssemblyDoc.Extension.SelectByID2("PartX", "COMPONENT", 0, 0, 0, false, 0, null, 0);
AssemblyDoc.SetSuppression2("[3]", swSuppressed);

Drag options to blanks, or click blank then click option'

AConfigX

BConfigY

DConfigZ

Attempts:

3 left

💡 Hint

Common Mistakes

Using the same configuration name for all blanks.

Confusing which configuration to activate and which to suppress.

First, create the configuration 'ConfigX' (blank 1). Then activate 'ConfigY' (blank 2) - this is a trick to test attention. Finally, suppress 'PartX' in 'ConfigX' (blank 3). The correct sequence is to create 'ConfigX', activate 'ConfigY', and suppress in 'ConfigX'.

Practice

1. What is the main purpose of assembly configurations in SolidWorks?

easy

A. To export assemblies to different file formats

B. To simulate motion of parts in an assembly

C. To create multiple versions of an assembly within a single file

D. To generate 2D drawings from 3D models

Solution

1. Step 1: Understand the concept of assembly configurations

   Assembly configurations allow you to have different versions of the same assembly in one file.

2. Step 2: Compare options given

   Exporting assemblies to different file formats, simulating motion of parts in an assembly, and generating 2D drawings from 3D models describe other features of SolidWorks, not assembly configurations.

3. Final Answer:

   To create multiple versions of an assembly within a single file -> Option C

4. Quick Check:

   Assembly configurations = multiple versions in one file [OK]

Hint: Think: one file, many assembly versions [OK]

Common Mistakes:

• Confusing configurations with exporting files
• Mixing up assembly motion simulation with configurations
• Thinking configurations generate drawings

2. Which of the following is the correct way to create a new assembly configuration in SolidWorks?

easy

A. Click 'File' > 'Export' > 'New Configuration'

B. Use the 'Save As' command to save a new file

C. Drag and drop parts into the assembly window

D. Right-click the assembly name in the ConfigurationManager and select 'Add Configuration'

Solution

1. Step 1: Identify how to add configurations

   In SolidWorks, new configurations are added via the ConfigurationManager by right-clicking the assembly name.

2. Step 2: Eliminate incorrect options

   Using the 'Save As' command to save a new file, dragging and dropping parts into the assembly window, and clicking 'File' > 'Export' > 'New Configuration' describe unrelated actions.

3. Final Answer:

   Right-click the assembly name in the ConfigurationManager and select 'Add Configuration' -> Option D

4. Quick Check:

   Add configuration = right-click in ConfigurationManager [OK]

Hint: Right-click assembly in ConfigurationManager to add configs [OK]

Common Mistakes:

• Trying to create configurations by saving new files
• Confusing part insertion with configuration creation
• Looking for configuration options under export

3. Given an assembly with two configurations: Config1 where Part A is visible and Config2 where Part A is hidden, what will happen if you switch from Config1 to Config2?

medium

A. Part A will remain visible in both configurations

B. Part A will be hidden in Config2 but visible in Config1

C. Part A will be deleted from the assembly

D. The assembly will crash due to conflicting configurations

Solution

1. Step 1: Understand visibility control in configurations

   Configurations can control part visibility independently, so Part A can be visible in one and hidden in another.

2. Step 2: Analyze the effect of switching configurations

   Switching to Config2 hides Part A, but Config1 keeps it visible; no deletion or crash occurs.

3. Final Answer:

   Part A will be hidden in Config2 but visible in Config1 -> Option B

4. Quick Check:

   Visibility changes per configuration = Part A hidden in Config2 [OK]

Hint: Visibility can differ per configuration [OK]

Common Mistakes:

• Assuming parts get deleted when hidden
• Thinking visibility is global, not per configuration
• Believing conflicting configs cause crashes

4. You created a new assembly configuration but notice that changes to part positions are not saved when switching configurations. What is the most likely cause?

medium

A. Part positions are not set to vary between configurations

B. The assembly file is corrupted

C. You forgot to save the assembly file

D. Configurations only control part visibility, not position

Solution

1. Step 1: Understand configuration control over part properties

   Configurations can control part visibility, size, and position if set to vary.

2. Step 2: Identify why position changes are not saved

   If part positions are not set to vary, changes won't be saved per configuration.

3. Final Answer:

   Part positions are not set to vary between configurations -> Option A

4. Quick Check:

   Positions must vary to save changes per config [OK]

Hint: Enable 'vary' for part positions to save changes [OK]

Common Mistakes:

• Assuming file corruption causes this
• Forgetting to save the file
• Believing configurations can't control position

5. You want to create an assembly with three configurations: Default, Compact, and Extended. In Compact, some parts are hidden and others moved closer. In Extended, all parts are visible but some are repositioned. Which approach correctly manages these configurations?

hard

A. Use assembly configurations to control part visibility and position for each version

B. Create separate assembly files for each version to avoid confusion

C. Use part configurations inside each part instead of assembly configurations

D. Only change part colors to differentiate versions

Solution

1. Step 1: Analyze requirements for multiple versions

   You need to control visibility and position differently in each configuration.

2. Step 2: Match approach to requirements

   Assembly configurations allow controlling visibility and position per version in one file, fitting the need.

3. Step 3: Eliminate other options

   Separate files increase management effort; part configurations control part internal states, not assembly layout; color changes don't affect visibility or position.

4. Final Answer:

   Use assembly configurations to control part visibility and position for each version -> Option A

5. Quick Check:

   Assembly configs control visibility & position per version [OK]

Hint: Use assembly configs to vary visibility and position per version [OK]

Common Mistakes:

• Creating multiple files instead of configurations
• Using part configs for assembly layout changes
• Relying on color changes only