The thoughts, opinions and commentary posted in this blog are mine and mine only. I speak only for myself and no other person(s) or entities. Questions, comments or complaints can be posted in the 'comments' section of each post or you can email me directly.
Thanks for reading!
...can be a royal PITA!! If things continue this way, I'm going to end up bald. Frankly, I don't want to be bald. It's bad enough that I have some gray coming in. That's right, I'm not aging gracefully. I'm fighting tooth and nail to stay young. However, the ACIS file I've been dealing with is making an already difficult battle even more difficult.
I know, I know, SolidWorks handles ACIS all the time, along with a slew of other file types. I know. Not this one, though. This one is wreaking havoc on my mental well-being. The file originated out of revit and is 143MB sat file. When I first imported it, I spaced out and did it across the network. Hush, I know I screwed up. Thankfully, it only took 14.5 hours to convert...no, that's not an exaggeration. Unfortunately, everything came in suppressed. I tried unsuppressing everything all at once, but that turned out to be another mistake. SolidWorks stopped responding (read: flatlined), and I had to pull the plug (FYI - Computer specs: Dell T3400, Core2Duo E6850 @ 3GHz, 8 Gigs RAM on a 1GB network). Meanwhile, my partner-in-crime here, Mike, did the smart thing and moved the ACIS file to his hard drive and opened it from there. It only took 5 hours to get it to open up in SolidWorks. (I should mention here that, once opened, there are 3500+ parts in the assembly.) He was then able to get everything to unsuppress in 30 minutes. Yee-ha! We saved the assembly, moved it, and all its associated parts, onto a memory stick and transferred it to my computer. I opened up the file on the stick and...where's the assembly?? We went back to his computer but it wasn't there. It wasn't on the stick. It was gone. How the hell does that happen?
I've been on the phone with the local VAR (Quest Integration). Those guys have been great in dealing with me. I say me, and not the issue, because I can be a handful when I get aggravated. I've talked to some other users and a couple of people at SolidWorks, but have yet to find a solution.
As I sit here writing, the assembly is up on my other monitor and everything appears to be unsuppressed. Unfortunately, SolidWorks also appears to be locked up. Again. I don't want to bring up my task manager as I know what I'm bound to see (SolidWorks Office Premium 2008 x64 Edition...Not Responding).
What's my point here? Why am I rambling on nonsensically? Because I'm hoping that one of you out there have been through this before and can either give me a fix, or commiserate with me. Thank God it's Thursday (I work 4/10's). Tomorrow I'm going salmon fishing. Saturday, I'm relaxing. I'll come back here on Monday, refreshed, and go at it again. So long as I don't go bald, it'll all be good.
Ok, as most of you know, I'm self-employed now. A job opportunity fell into my lap so I started my own company, JRM Consulting & Design, Inc. Not a super catchy name like Matt's (Dezign Stuff), but it'll do for now. I'm still not used to referring to myself as "President", but that's a personal issue.
Anyway, the project I'm working on is going to require routing in the not too distant future. I've done a bit of routing in the past, but nothing like what I'm going to be doing. It's going to be a huge undertaking on a pretty massive scale. I already know that some of what I'll need to route (HVAC) probably won't be doable with Routing, but I figured I'd solicit some advice from the community.
While I can't be overly specific, I'm working on a large building. Part of the job entails routing all the piping, HVAC, power, plumbing, etc. Have any of you done anything on a scale such as this? Cable runs of 2000'+? 10" drain pipes? How about a 110V circuit? I know there are users out there who have a lot more experience with routing and I'd love to hear from you guys. I'd hate to think of the amount of 3D sketching I'll have to do if I can't use routing for most of it...thank God it's an hourly contract!
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!!
SolidWorks and NASA are sponsoring a "Create the Future" contest with a top prize of $20,000! Just go http://www.createthefuturecontest.com/ and enter your awe inspiring dream. Remember, I only expect 10% of your winnings...
Good Luck!
I remember when I first saw SolidWorks back in about 1998. I had just become part of the Technical Publications team at Genie, charged with illustrating and writing parts manuals. At the time, the illustrations were created in some convoluted process that included AutoCAD, CorelDraw and an EPS converter. I happened to walk by one of the design engineers, saw him working with SolidWorks and wondered why we couldn't created the illustrations from it. When I asked some of the "old timers" from Tech Pubs about it, I was told that you couldn't get a true Isometric view from SolidWorks and "we've always done it this way". Well, that last part is what got me started on SolidWorks. I hate that answer. Plus, I knew that you could get pretty much any view you wanted from SolidWorks. Much to the chagrin of the aforementioned "old timers", I illustrated my first manual completely from SolidWorks drawings. Last I heard, all the manuals at Genie are now done that way.
Fast forward to present day. As I wrote some weeks ago, I'm no longer working for a reseller. As a matter of fact, I'm my own boss now. An opportunity fell into my lap and I started my own business (JRM Consulting & Design, Inc. - for those of you wanting to know). The company I'm working for saw a potential for SolidWorks to do some great things for them and took the leap and purchased a few seats. That's where I come in, along with another consultant. While they had an inkling of what SolidWorks can do, we've shown them even more. The coolest thing for me is how enthralled they are by the power and versatility of SolidWorks. Whoever initially showed them SolidWorks must have only scraped the surface. Hell, we've only scraped just below the surface and these guys look like a group of kids on their first visit to Disneyland. Not that I'm complaining. It's because of their excitement that I spend 4 days a week away from home working.
What's my point? The people I'm working for have been in, and around, engineering for decades and are just now taking the leap to 3D. All it took was one person to show another person the power of SolidWorks for it to happen. It seems to me that there is a very small segment that truly can say 2D is all they need. The rest of the engineers, designers, drafters, etc, that haven't made the leap just need the right person to show them. Are you that person, or do you still need to make the leap?
I have returned to the light. After experiencing life on the reseller side of things, I'm returning to where I should have stayed...as a user. What does this mean for all of you? Many more postings full of my wit, charm and insight. I don't plan on too many product reviews, but more about SolidWorks, and it's add-ins.
I'm really looking forward to starting my new position on June 30th. Between now and then, I'm hoping to revamp my blog; give it a polishing. So be patient and let all your friends know that the brainwashing didn't work!
One week ago, today, I was let go from my position as a SolidWorks AE. Honestly, I wasn't overly surprised by it and, coincidentally, I'd been looking for another position anyway. (I could go off on a rant right now about the whole situation, but it would serve no purpose.) While I enjoyed being an AE, I didn't like certain aspects of the company I was working for so, ultimately, it's for the best. One of the good things about it is I can look for a new position freely, without having to do it on the "downlow". I will say, though, I hate job hunting and all that goes along with it. I know that I don't interview well, which causes a bit of consternation when I do go to interview. Usually, I'm up front about it so the interviewer knows before-hand. My hope here is that they won't be too critical afterwards. I don't know that it actually works or not...
Anyway, I know it's been a while since I posted anything worthwhile, but I plan to get back on the horse soon and regale you all with witty posts. So, be patient my loyal reader (not a typo by the way), I'll be back soon.
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.
I guess it's just a day to rant.
I live in the Pacific Northwest, specifically just outside of Seattle, and I have to say that the SolidWorks community around her is pretty pathetic. I would guess there to be, easily, 2000+ users in the area and the turnout at the local SASPUG (Seattle Area Power User Group) meetings isn't just below low, it's virtually non-existent. I hear all the time about user group meetings that have 50-75+ attendees. Why are things not so good here, and perhaps where you are? I believe that the blame can be placed into three areas:
1) Employers who are lackadaisical about encouraging employees to attend user group meetings.
2) Users, themselves, who figure they can't learn anything by going.
3) Local VAR support of said user group is weak.
Let's start with employers, shall we? Why would you purchase thousands of dollars worth of software then turn your users loose on it without encouraging your users to learn it inside and out? Yes, some employers pony up the cash to send their employees to training at their VAR but we all know that only scratches the surface. It's at the user group meetings that you learn tips & tricks, new ways of creating the wheel and, in some cases, your users can find out that they actually can do that. I can't tell you how many times I've smacked my forehead after finding out some little tidbit of information. C'mon, Mr. Executive! Users who know the ins and outs of the software are only going to help increase profits! Sheesh. Hey, here's an idea for you, if you have a fair amount of users, start your own internal group! I bet Richard would be happy to help you get started.
Users..."I know enough to get by." "If I don't know it, I'm sure someone around here does." "I just don't have time." "User group? What's a user group?"
Ever hear these comments? I have. I have to tell ya, for those of you who aren't lucky enough to go to SolidWorks World (yet another rant in that statement), your user groups can go a long way towards expanding your knowledge. Wouldn't it make more sense to 'learn' something at a meeting and be able to use it in the future than to have to go around the company trying to find someone who knows how to add fins to your flux-capacitor? If you don't know what a user group is...ugh. Where the hell have you been?
VARS - This one should be a no brainer. VAR stands for 'Value-added Reseller'. The "value" part certainly doesn't come from only selling SolidWorks, it comes from supporting it. To not support your local user group is flat out doing a disservice to the very people you're supposed to be servicing.
If you don't know if there's a user group in your area, click here to find out. Participate, whether it's as a member of the audience or as a presenter. Believe me, if you know what you're talking about, the organizer of your local group will be more than happy to have your help!!
Ok, I'm done ranting for today. Not sure what got into me, but I'm feeling better. Thanks for reading.
I've been more than lax lately in posting, I've been downright lazy. I'd love to say that I've been too busy, but I'd be lying. I've just had writer's block, I suppose. I am, however, going to try to be more diligent. Only time will tell. To that end, I want to talk about the meaning behind the title of this post.
I know of companies that, though they are on subscription, are "behind the times" in releases. I know of one company that is still using '06 even though they're probably paying $50,000+/year in subscription fees. The question I have is "why?". Why would this happen? This particular company is a large manufacturer and could benefit greatly from '08. Why would they allow themselves to get behind the times? In this instance, it's their IT department. When SolidWorks installs are managed by IT departments that don't "get it", they end up hindering engineering. While I do understand the need for software management, software should be managed by people who understand and, God forbid, use the software. The whole reason for alpha and beta testing of the newest versions is to give the people in charge of the installs the ability to...wait for it...TEST the software prior to implementing it company wide.
SolidWorks usually releases new versions around August, with SP1.0 coming 6-8 weeks later. One would think that by December or January, a company could have all its "testing" done and implement the newest version. When an IT department is so "all-powerful", as is the case here, they end up costing the company money. I've heard that they're talking about going from '06 directly to '08. How much time do you suppose is going to be lost while all the users try to figure out the new interface? I say "figure out", because training doesn't come into play there. That could probably be another post...
My point is this, manage your installs wisely. You pay x-dollars/seat of SolidWorks for support and upgrades. By not upgrading, you're throwing money out the window. That money should be benefiting the company by improving the tools when improvements are available. Granted, "improvements" may be a subjective term here, but you get my point. When an IT department is given carte-blanche over a SolidWorks install, many of them will, well, screw it up.
Ok, I'm starting to ramble here and, before I really start to rant (ala Matt), I'm going to end this post. I would, however, love to hear your thoughts on companies that fall "behind the times".
Recent Comments