Workflow for related component files

[metd01567]

I'm looking for advice on workflow. I'm creating a 3D "typeset font" with a pair of components for each character: a backing plate and a face.  So far I've been working in a single file. I use a common set of user parameters and sketches to control offsets, extrudes, sweeps and revolves in the child components. 

I've attached a simplified example.  I included it in an empty design, then re-built the character from the included profiles.  It mostly works, but to import user parameters I've got to start experimenting with the add-in GoogleSheeter (since I'm on a mac).

Bottom line, is this a reasonable way to go?  Do you have a different suggestion for the user parameters?

I'll admit that my first pass didn't follow Rule #1 for the sketches.  All of the sketches were overlaid and it was impossible to select the profile I wanted.  So each sketch must be in a separate component so that I can turn them on and off.

[metd01567]

I'm proceeding with the workflow below, but I'd still appreciate comments.  I don't especially like it.

- Create a master component file to hold the common profiles and user parameters.  Each profile is in a separate sub-component, so I can control visibility.

- Create and update all user parameters in the master component file.  I wrote a simple python script (so it would work on my mac) to save/load user parameters.   Whenever I change a common parameter, I edit in the master; save; then reload in each derived component file.

- As I build derived components for each typeset character (in separate files), I start by loading the user parameters.  Then I insert the master component.  When a sub-component needs to use a profile, I project the profile sketch from the master component into a sketch contained in the using component.  I select "link", so master profile changes propagate throughout after updating.

Discipline is required to create and edit parameters in the master, and keep the derived components up to date.  I might convert my script to an add-in, and implement a warning indicator when the user parameters are out of date.  That would also let me update parameters in any file, as needed.

[lichtzeichenanlage · Accepted solution]

---

@metd01567 wrote:

... I wrote a simple python script (so it would work on my mac) to save/load user parameters.   Whenever I change a common parameter, I edit in the master; save; then reload in each derived component file...

---

I guess you don't have to do this that way anymore, because Fusion 360 now has a native derive function. 

[laughingcreek · Accepted solution]

So instead of answering your question, I'm going to give you some un-solicited advise.  

Now that you've worked out how want your geometry to look, I would suggest going back and recreating it with a more simplified process.  I think this will make this who venture easier to achieve.  All the moves and copies etc can be difficult to trace when it comes time to make adjustments and fix things.

Attached is an example of what I mean. I didn't take the time to make all the dimensions match yours, but it's pretty close.  look at the last component i added to your original model.  Notice there are only 2 sketches, and 3 solid features (1 extrude and 2 sweeps). There are no move commands, no copy/past, and no other various hijinks to try and follow. 

FWI

[metd01567]

Thanks very much, I've stumbled across derive a few times, but never tried it.

I read this forum thread which helped me understand: https://forums.autodesk.com/t5/fusion-360-design-validate/insert-derive-vs-insert-design-any-woohoo-...

I think you were referring to user parameters in a derived vs inserted component.  That's nice and I'm sure I'll use it in simpler designs.  For this, I think configuration management will be easier with a separate parameter file that is accessible from any design file.  That means using an add-in but I'm OK with that.  I'll probably go with GoogleSheeter eventually, but I've got to think through accounts and access since I've got a lot of unrelated data in my google account already.

Note I tried deriving, but the derived component's user parameters did not show up.  I'm sure I did something wrong, I'll figure it out.

You might also be referring to selection of sub-components when deriving.  That's great and I've got a few designs where that would have helped greatly. I didn't like them landing in the root component though, it creates more clutter.  For example I tried derive from the plate component.  It lands in the root and can't be renamed.  It was quick and easy though, again I've got other places where that will be handy.

[metd01567]

Yes, of course, that single sweep is much simpler.  Thanks for taking the time to think it through and re-doing it for me.

As you suggest, I'm thinking through my whole approach.  I'll crunch down the number of sketches.  At the same time I might reduce the number of inter-sketch references, and rely on user parameters for the simpler profiles.

Overall, I feel ready to go.  I can already see that I'll run into trouble the first time I scale the font, or change the base plate design.  So I might incrementally develop the characters, fleshing out only the ones I need for the next sign.

Thanks for the help.

[lichtzeichenanlage]

Yes, my comment was about populating parameters via a script. You can do this with the insert derived function. You just have to mark the parameters in the source as favorite. 

In your scenario it might be useful for sub-components or sketches, too.