2 Replies Latest reply on Apr 24, 2018 3:43 PM by Vladimir Urazhdin

    Using a spreadsheet to generate top level assembly configurations.

    Josh Roat

      I'm looking for a way to automatically generate configurations using a spreadsheet. My current top level assembly has 4 or 5 sub-assembly's with 9 or 10 configurations each. I want to be able to create a configuration for each possible combination of sub-assemblies. For instance:

       

      Top Level Configuration 1: Sub-assembly 1, configuration 1; Sub-assembly 2, configuration 1...

      Configuration 2: SA 1, C 2; SA 2, C 1...

      Configuration 3: SA 1, C 3; SA 2, C 1...

      Configuration 4: SA 1, C 1; SA 2, C 2...

       

      I looked into DriveWorks, however, it's out of my budget and it sounds like it creates a new file for every combination, not a configuration.

        • Re: Using a spreadsheet to generate top level assembly configurations.
          Kevin Chandler

          Hello,

           

          Try Design Tables with derived configurations.

          See help.

           

          Cheers,

           

          Kevin

          • Re: Using a spreadsheet to generate top level assembly configurations.
            Vladimir Urazhdin

            Josh Roat wrote:

             

            I'm looking for a way to automatically generate configurations using a spreadsheet. My current top level assembly has 4 or 5 sub-assembly's with 9 or 10 configurations each. I want to be able to create a configuration for each possible combination of sub-assemblies. For instance:

             

            Top Level Configuration 1: Sub-assembly 1, configuration 1; Sub-assembly 2, configuration 1...

            Configuration 2: SA 1, C 2; SA 2, C 1...

            Configuration 3: SA 1, C 3; SA 2, C 1...

            Configuration 4: SA 1, C 1; SA 2, C 2...

             

            I looked into DriveWorks, however, it's out of my budget and it sounds like it creates a new file for every combination, not a configuration.

            Besides that, when DriveWorks (and Tacton too) generates a new project, it renames all affected assembly items. It creates an additional headache: all equations and external links must be moved from SW models into DriveWorks equation area.