Jeff's Blog

Tips, Tricks and Thoughts about SolidWorks

Jeff Mirisola



  • View Jeff Mirisola's profile on LinkedIn

Email Jeff

  • Send Jeff an Email

Subscribe

  •  Jeff's Tool Shed
  • Add to Technorati Favorites

Email Newsletter

  • Enter your email address:

    Delivered by FeedBurner

Blog powered by TypePad

Blogs

  • Southern Plate
  • Anna Wood
  • Ben Eadie
  • Brian McElyea
  • Christine Vrooman
  • Chuck Paulsen
  • Devon Sowell
  • Gabi Jack
  • Jason Raak
  • Josh Mings
  • Lenny Kikstra
  • Lou Gallo
  • Matt Lombard
  • Mike Puckett
  • Phil Way
  • Ricky Jordan
  • Rob Rodriguez
  • Stefan Berlitz
  • Thomas Parel
  • Tim Huff
  • Vince Adams
  • SolidWorks Blog
  • SolidWorks Community
  • SolidWorks Podcasts
  • SolidWorks Roadster

Weblinks

  • Eng-Tips
  • SolidMentor
  • SolidWorks Forum

Podcasts & Videos

  • Lou Gallo
  • SolidWorks Podcasts
  • CADjunky
View Patrick Cook's profile on LinkedIn
See how we're connected

Dealing with imported data

This will be a short post but, hopefully, a useful one.

Have you ever imported a non-native SolidWorks file only to see errors? If you right click on one of those errors, you'll see an option called 'Import Diagnostics'. Choosing that will bring up a new dialogue box that gives you a list of the errors. At this point you have the choice of fixing all faces, fixing all gaps or, by right clicking on one of the offenders, fixing them individually. Through trial and error, I've found that fixing all faces will fix the gaps. Naturally, though, there are instances where this doesn't work. I've had times when the "fix" actually causes the offending surface to be incorrectly fixed. After you've fixed the errors, you'll end up with a bunch of bodies (unless you have FeatureWorks, but that's a different post). At this point, go to Tools->Features->Combine. With any luck, you'll be able to combine all the bodies.

Where, often times, these erroneous imports are surfaces, you can utilize the surfacing tools in SolidWorks to repair them as well. I'm no expert on surfacing, so I don't want to go too deep into the "how" portion. I would recommend getting familiar with the 'Delete Face' option, as well as the 'Filled Surface'. Perhaps a surfacing expert (Matt, you reading?) might be able to shed a bit more light on this subject.

This is how I deal with imported data. How do you do it?

Posted by Jeff Mirisola on December 16, 2008 | Permalink | Comments (1) | TrackBack (0)

Technorati Tags: Import Diagnostics, Imported Files, SolidWorks, Surfacing

Let's Talk Sheetmetal

I really like the Sheetmetal functionality in SolidWorks. I like that it's fairly intuitive and does a nice job of creating your part. There is one aspect of it, however, that many people seem to miss. That would be the unfold/fold commands. When you have a part that's been bent, and you need to cut some holes in it, this is the way you want to go, especially if you're putting a hole in that straddles one of the bends. How do you use it? Simple. From your sheetmetal toolbar, select the 'Unfold' button. At this point, you'll need to select a fixed face. You'll then be prompted to select your bends. Generally, I simply 'select all'. Hit the check mark and your part will unfold. One thing to note is that your 'Flatten' feature is still surpressed. You can now insert your cuts. Once done, select the 'Fold' button, the fixed face from before and the bend(s) you used. Voila! Your holes are done. Why not just use the 'Flatten' feature? Because the cuts you put in would be surpressed in the "unflattened" state. I know, from experience, that this can be rather frustrating.

Posted by Jeff Mirisola on September 24, 2008 | Permalink | Comments (3) | TrackBack (0)

Technorati Tags: Sheet Metal, SolidWorks

Stumbling onto "new" things

So I've stumbled onto a couple of things in SolidWorks that I thought I'd share. I'm hoping that these weren't common knowledge...

First, have you ever brought a huge piece of equipment into a new assembly only to find that the assembly template's planes are miniscule? Did you know you can right click on the plane and select 'Auto-size'? I stumbled across that one two days ago.

Next, and I'm really feeling like an idiot over this one, is renaming. I spent a good portion of yesterday fighting with a renaming macro. As you may recall, I'm dealing with non-native assemblies. When you import said assemblies, all the lower level parts are named "Import1", "Import2", etc. When you have multiple assemblies that you are going to combine into one large assembly, all those like-named parts cause problems. This is why I was fighting with the macro yesterday (many thanks to you guys on eng-tips!). Just as I was about to strangle the kid we hired to help us out, even though none of this was his fault, I "discovered" something in the 'Save-As' dialog. You know how you can choose References when doing a save-as? And then you can change the file paths for all those lower level parts? Well, there's an option button there, too. Damn if you can't add a prefix or suffix to the file names. I'm honestly embarrassed about not knowing that.

Posted by Jeff Mirisola on July 31, 2008 | Permalink | Comments (4) | TrackBack (0)

Technorati Tags: Planes, SolidWorks

Weldments and my IPod

What do Weldments in SolidWorks and my IPod have to do with each other you might ask? Nothing, aside from the fact that I'm listening to ITunes as I write this post. I finally broke down and bought an IPod Nano a few weeks ago and have now spent more money on song downloads than I did on the damn player. Right now, I'm listening to my 80's playlist, reliving my high school years...

Now for the meat of this post, Weldments. Up until recently, I never used the Weldments function in SolidWorks very much. Lately, though, I've been using it on an almost daily basis. Have you used it? I know that there are some that don't like it very much, but I don't see why. I'm enjoying the hell out of it. It really makes things easier if you ask me. With a fairly simple skeleton sketch, you can create a nice weldment, complete with a cutlist, in no time. As with so much in SolidWorks, it's pretty intuitive as well. Granted, I use to teach how to use weldments, when I was on the "other side", but it didn't take me long to get the hang of it. Now I'm not claiming to be an expert at it. I'm sure there's some tricks that I don't know on how to make it even more simple, but as I've said so often before, if I can do it, anyone can.

If you're in a field that creates welded structures, I strongly recommend you check out weldments. There's a tutorial in SolidWorks to get you started, then dive right in and started creating your own.

If you've used weldments, and have some tips and tricks, I'd love to hear from you!

GO SOX!!

Posted by Jeff Mirisola on July 17, 2008 | Permalink | Comments (1) | TrackBack (0)

Technorati Tags: IPod, SolidWorks, Sox, Weldments

Clean Install...huh...what?

Clean install. What is it? It's what you should be doing when moving from one major release to the next. Why? Because I said so. Ok, so that's not a valid reason. However, I've often said, "if you just do things my way, there won't be any problems." I digress, though...
Back to clean installs. First the 'why?'. It's actually quite simple. By doing a clean install, you remove all traces of the previous version of SolidWorks from your machine. By removing this legacy data, you lessen the chances of having dangling bits of data floating around to screw up your new installation. There have been many times when someone will call in, or I'll read something in a forum, where a user is bemoaning the latest version of SolidWorks. They'll harp on about it being full of bugs. After determining that s/he simply stuck in their DVD and upgraded, a clean install is recommended. Lo and behold, no more bugs! (Ok, so there probably are still some legitimate bugs left, but not anywhere near what they were experiencing.) Naturally, there is a codicil to  this whole thing. There are users out there, myself included, who need to have multiple versions on their machines.  Since I started running two separate installs, I've found that I tend to have to reinstall more often. Though, working for a VAR presents a whole host of new and exciting problems....
I've always found it strange how a very small percentage of the user community will complain about "numerous bugs" in a new release and suddenly said new release is crap.  It never ceases to amaze me how negative reviews travel so much faster and wider than the positive reviews. What prompted this quasi-rant? A post located here, in the Eng-Tips forum. Because the original poster had one customer complaining about their '08 install, his company was prepared to NOT install '08 and wait for '09. This, in my opinion, is simpy ridiculous. Since '08 came out, people have been raving about it. Yes, it's had some problems. Yes, people had trouble adjusting to the new UI, but come on! '08 has to be one of the most stable releases yet! Is it perfect? Hardly. Remember, though, that SolidWorks is created by Humans and Humans make mistakes. Ergo, the program will have mistakes. Can you name any software product that doesn't?
How do you go about doing a clean install? Well, I'm glad you asked. First things first. Use your copy settings wizard to, duh, copy your settings. Next, use Add/Remove programs to remove SolidWorks. Once this is done, go to C:\Program Files and remove any SolidWorks folders in there. After that, go to Start->Run and type in regedit. This will bring up your Registry Editor. Under HKEY_LOCAL_MACHINE->Software, remove any SolidWorks or SRAC folders. Do the same under HKEY_CURRENT_USER->Software. You've now completed a clean install.

Posted by Jeff Mirisola on May 11, 2008 | Permalink | Comments (2) | TrackBack (0)

Technorati Tags: Clean Install, Humans, SolidWorks

Dangling Command Manager?

If your 2008 command manager looks like the one in the picture, here's a fix I stumbled across:
• Turn off the command manager (RMB in the toolbar area).
• Drag any remaining toolbars into the graphics area.
• Turn the command manager back on.

I don't know who, what or why, but this fix worked on my machine. 
Command_manger



Go Pats! 

See you at SolidWorks World!

Posted by Jeff Mirisola on November 29, 2007 | Permalink | Comments (0) | TrackBack (0)

Technorati Tags: Command Manager, Pats, SolidWorks World

February 2009

Sun Mon Tue Wed Thu Fri Sat
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28

Recent Comments

  • Kerri Dunne on Kerri Dunne - The brains behind SWW
  • Lou Gallo on Kerri Dunne - The brains behind SWW
  • Devon T. Sowell on Off-topic Soapbox Rant
  • Steve Calvert on Off-topic Soapbox Rant
  • fcsuper on Off-topic Soapbox Rant
  • fcsuper on Off-topic Soapbox Rant
  • Brian McElyea on Off-topic Soapbox Rant
  • Gary Hall on Off-topic Soapbox Rant
  • Dale on Dell M4300
  • Steve Calvert on Jeremy Luchini – Mr. Certification

Categories

  • Hardware Review
  • Instructional
  • Personal
  • Rant
  • Software Review
  • SolidWorks Community
  • SolidWorks Tips
  • Web/Tech
  • Weblogs

Recent Posts

  • Kerri Dunne - The brains behind SWW
  • Let's talk about Vuuch
  • Off-topic Soapbox Rant
  • Jeremy Luchini – Mr. Certification
  • SolidWorks World 2009 – The Finale
  • SolidWorks World – The Final Day
  • SolidWorks World – The real Day 1
  • SolidWorks World 2009
  • Flying to Orlando
Add me to your TypePad People list

Archives

  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008

More...