Design table limits in SW 2006 1

[DesignerGuy16]

I've got a big machine I'm automating configurations in.

I know SW 2006 has the same column limits as Excel 2003 (256 columns). Any way to get around that? I'm pushing 150 columns and climbing fast.

We have Excel 2007, which has 16,000 column limit. I think it would likely just cut off reading anything after 256 columns though if I made an external design table.

James Spisich
Design Engineer, CSWP

 

[CorBlimeyLimey]

Firstly take a look at DriveWorks and DriveWorks Express. It may be able to handle what you need.

Next, Can you break your assy down into sub-assys, each having their own DT (and sub-assys with DTs).

Providing the results are pulled into the first sheet, for propagation to the model, you should be able to use multiple sheets within a DT to perform calculations which require data stored in columns not required for actual model input.

 

[DesignerGuy16]

The only thing I can do to minimize what I have is to dump some set screws into sub-assemblies. Because of the complexity of patterns I have to basically enter similar screws into 3 different panels, and control them via suppression states/patterns.

The rest I physically have to have for configuration purposes on the main-level. It's still a work in progress, but the macro will be much more complexity when I actually have those items complete in my model.

To give you an idea of size, if I configure 8 modules in my assembly there will be over 40,000 parts in the assembly when all is said and done.



James Spisich
Design Engineer, CSWP

 

[rgrayclamps]

Hi, James:

I am utterly shocked by what you are trying to do. If you write books, you want multiple of volumes, then chapters, and then section, etc.

I am not sure if you are heading right way.

 

[DesignerGuy16]

I don't think you have a grasp as to what I'm trying to accomplish or the scope.

I already have layer upon layer of sub-assemblies. Problem is the shear number of configurations and combinations. The logical place to put much of this is actually on the main level so I only need to generate one new BOM when we get a machine order.

Problem is worst case scenario on this machine is looking at an assembly over 40,000 parts.

The main level of this machine is like a set of encyclopedia brittanica. Each sub-assembly is packed with as many parts that will not change as possible. Problem is every variable in the system and the options grow exponentially. Our sales likes "options".. so it's complex.

Yea it may look crazy, but:
a) Everything written into the design table works great and isn't very difficult to follow if you're actually looking at the assembly.
b) Most of the equations are written as they are due to limitations with Solidworks using excel. Ex. you can't chain multiple If, then commands in one cell like you can in regular excel.
c) I'm dealing with a very large machine that has nearly 20 different configurable variables. All said and done there will be thousands of possible configurations. I'd rather drive that through a couple of drop-down boxes than try to remember all of the combinations and relations.

James Spisich
Design Engineer, CSWP

 

[TheTick]

Why keep all of the "User Notes" columns? That could make some space.

 

[DesignerGuy16]

Doh, that was a brain fart in a vain attempt to try and group like items. I think I'll just do that by varying the text style instead. I'm going to move the actual selection boxes down as well. That should net me like 50 columns. Hopefully it all fits, but I have a feeling I'll have to cheat to win at this one.

I'm maybe 60% done with importing and redesigning everything back into this model. This is a legacy machine done in AutoCAD. It has little to no assembly documentation, poorly organized BOM's, multiple errors, etc.

I'm trying to get 100% documentation, streamlined error free BOM creation. Should be 20 minutes per machine vs 8+ hours and guessing with hardly enough information for a customer to know what's going on.

Does SW 2010 support Excel 2007 .xlsm macro books? Please tell me I have something to look forward to someday if we ever upgrade.

James Spisich
Design Engineer, CSWP

 

[Updraft]

James,

As TheTick recommended, get rid of anything you don't need: User Notes, your notes, etc. If anything is common to all configs then it is not needed either.

I see that you are using multiple tabs in the spreadsheet. This is good and an often overlooked capability of the Design Table. Perhaps you can make more use of these tabs by moving any intermediate items, such as calculations, especially ones showing intermediate results, to these other tabs. All you want on your main tab is the minimum list of items that change.

If you are using fasteners in holes and need to handle the different fasteners and different quantities there are a couple of things that may help:
1) Change Configurations of the fastener rather than supress one size and insert another. For all the fasteners of the same type, but different size this will save many columns and maintenance of the DT will be much easier.
2) Put the first fastener of a given type in the first hole of a series created with the hole wizard. I recently discovered this and am so thrilled. When creating a series of holes that would be in a pattern I used to create the first one by itself then create an appropriate feature pattern, such as four holes on a bolt circle. I have since learned that all I have to do is put four positions (sketch points) of the hole in that single hole feature. In the assembly I then insert a fastener in one of the holes, then use Feature Driven Component Pattern and select the hole wizard feature as the Driving Feature. Now if the number or spacing of the holes changes the fasteners change to suit. The only trick here is to place the fastener on the first hole of that hole wizard. This is easy to change the mates to the first hole if you don't get it on the first shot.

- - -Updraft

 

[CorBlimeyLimey]

Updraft ... In SW09, you no longer have to use the seed hole of the pattern; you now have the option of specifying any hole as the seed hole when placing the component to be patterned.

 

[DesignerGuy16]

The fasterers are basically fillers for when a certain height isn't used.

2x across per side (2x) x 3 heights x 3 tiers = 36 states to control.

Right now they aren't patterned (being lazy, wanting to keep things driven), but at best I can do..

2x across per side, x 3 heights + 3 patterns = 15 states to control. Gets me another 11 columns if I need them.

The only fastener in the design table is the same set screw, it doesn't change configurations, just suppression states depending on what product clearance is required.

James Spisich
Design Engineer, CSWP

 

[rgrayclamps]

Hi, James:

I fully understand what you are trying to do.

Sorry I do not have a solution for you, but you want to take a look at normalization of components and modulization of your assemblies.

Just my 2 cents.

 

[Updraft]

CBL,

Thanks! You get another star from me. I've been using SWX since it came out. I always enjoy learning something to make my life a little easier.

- - -Updraft

 

[DesignerGuy16]

Had another idea that I think is a clear winner. I have everything organized into folders anyways. I can control the suppression state of everything in the folder by controlling the folder itself. That cuts my "control" columns in half again after I consider patterns.

James Spisich
Design Engineer, CSWP