cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

SmartAssembly Coding & Capabilities

Participant

SmartAssembly Coding & Capabilities

We're interested in SmartAssembly for a project we have.  It will involve a model using a number of curves generated from .pts tables.  We would want to code both the initial setup, and revisions using new point data.  To do one set, it's simply start the offset points operation, set the coordinate system, browse to the table, then done.  Making the curve is even simpler.  And to update means just edit definition of the pts table, browsing to new, and all that.  Doing it multiple times, it's a couple of simple steps, set within a loop, where the names of the tables increment through a preset sequence (TURN01_V1, TURN01_V2, TURN02_V1, etc).

 

Question is, does smartassembly have this capability, or more specifically, is that something that can be coded for use in smart assembly?  I am not looking for the code, just some feedback from SA users as to whether we are looking at the right software?

Tags (1)
3 REPLIES 3

Re: SmartAssembly Coding & Capabilities

Yes, it already has that capability.  Very straight forward to do.

Highlighted

Re: SmartAssembly Coding & Capabilities

So if I want to work in a .prt environment, and do coding for the points tables, what is your recommendation for setting up the project. Do I need set up a template, or can I generate my part, and then have smartassembly coding that I can call to add the features.?

Re: SmartAssembly Coding & Capabilities

SmartAssembly doesn't really create features (other than holes).  It can create features by inserting UDFs or running mapkeys, so I guess it just depends on your use case.  If you creating these points from scratch is what you want, then just create a UDF that makes the necessary features and then use SmartAssembly to place this in your models.  Personally I tend to use template models more and just alter what already exists.  Keep in mind that you wouldn't necessarily need to create every single point inside the points feature.  The number of points can be adjusted programmatically.  I'd also suggest naming the features so they're easy to reference from your program.

Announcements