I've been following a particular blog for about as long as I've worked at CADD Edge and have been looking for an excuse to post an article on it. A TV segment featuring their DP1e electric race car now on YouTube finally prompted me to write the article.
If Green isn't your thing and Horsepower is then head over to blog and check out the dp1.
Dennis Palatov has documented the evolution of his passion for driving from the enthusiast to designer to manufacturer. Originally a track day enthusiast and engineer, Dennis decided the ultimate track car was not available to him and he decided to design and build it himself. His blog takes chronicles the process from napkin sketch through prototype, testing, and production. Dennis has done his design in SolidWorks and verified a lot of it with SolidWorks Simulation.
That passion has turned into a company, Palatov Motorsport. Other cars are now in the works as well like a two seater and an entry level track car, for the weekend enthusiat.
I could go on and on, but that is because there is so much there I would just say check it out for yourself. If your into driving, there are entries on his past vehicles. Who knew a Scion Xb was trackable? If engineering and design is your thing you could spend hours reading about the challenges they've overcome. And as a SolidWorks user I am impressed to see the amazing use of the entire product suite, from body design, structural frames, simulations and photo renderings. Check out the blog, the company if your shopping, the youtube channel or follow them on facebook. It will take the most time, but I'd reccomend reading the blogs from the beginning. Think of it as reading a book and you won't be disappointed.
SolidWorks Enterprise PDM CADD Edge Tech Tip #3
Just like with the SolidWorks Workgroup PDM product, SolidWorks Enterprise PDM has the benefit of the users working on their files locally and communicating or committing changes to/from the vault only when required. Having the SolidWorks “Save” operations local as opposed to going across a network is a huge improvement in the SolidWorks performance and it also offloads the network traffic and the associated strain on the network infrastructure. (This goes over very well with the IT staff!)
The version information displayed to the user lets them know how their locally cached version of a file compares to the vaulted versions available. The local cache version information is available in the Windows and Web clients as well as right in the SolidWorks and other CAD integrated clients.
If the locally cached file is newer than the vaulted version, the user sees something like the following: -/6. The "-" indicates a locally modified version of the file is cached locally and the "6" indicates that the vaulted (or most recently checked in) version is version 6. This scenario would indicate the need for a check in when the user wants to create a new version of the file, in this case version 7.
In the SolidWorks interface the user also has the visual indication with a green up arrow icon.
If the locally cached file is older than the vaulted version, the user sees something like the following: 4/6. The "4" indicates that the locally cached file is the vaulted version 4 of the file, and the "6" indicates that the latest available version is actually version 6.
This scenario would indicate the need for the user to get the latest version of the file if they want to be up to date. This can be done right inside of the SolidWorks or CAD application through the integrated client or with any of the other available clients as well. And, again, the integrated client in SolidWorks would show a red down arrow to indicate the out of date file.
Just as with any PDM system, it is up to the user to manage their local cache. There is an option to delete the local copy of a file during the check in process if they know that they are not going to be working on it again for a while and they can also select any file or folder and delete the local cache in order to manage their local disk space.
The real beauty of the Enterprise PDM local cache, is that the location of the files is exactly as they are in the vault. There is no need to keep track of a separate "Local View" that may look entirely different than the "Vault View". The user is always working in a local view of the vault itself called a local file vault view.
Speaking of the local file vault view, stay tuned for the next SolidWorks Enterprise PDM Tech Tip!
One question that always comes up when programming a part in a CAM system is just how accurate do the speeds and feeds have to be? This has been something debated over and over.
Let’s start by defining the RPM formula from the Machinery’s Handbook.
N = 12V/πD
D =Cutter Diameter
So for a HSS end mill in Cold Drawn 1212 Carbon Steel the suggested FPM is 160, and we will be using a 1” cutter.
RPM = (12 * 160)/(3.14*.500) or 611 RPM.
We have the RPM how about the feed? We only have two choices in the Machinery’s Handbook 22nd edition for depth of cut .250 and .05. So much for the 1-5/8 LOC. At .250" depth of cut, .004" is the recommended chip per tooth.
So for a 4 flute 1” HSS end mill in 1212 we should be running 611RPM, 9.8IPM, at .25"DOC. We are all set now right?
Let’s take a close look at what happens when cutting an arc. A 1” end mill programmed to cut a 2” radius at 10 IPM. The center of the tool moves at 10 IPM. When cutting on the outside of the radius the cutting edge of the tool ends up slowing down to 8 IPM. When cutting on the inside of the radius the cutting edge of the tool ends up speeding up to 13 IPM. That’s a total of 5 IPM difference using the same tool and the same programmed feedrate.
What hasn’t been accounted for? How are we holding the part? Is it a new, used, or resharpened cutter? How rigid is the machine spindle (30, 40, 50 taper?) Is it a knee mill or machining center? Is it a horizontal or vertical mill? What is the horse power of the machine? What type of coolant is being used and how much (flood, mist)?
Ok let’s face it, at the time of programming there are so many unaccounted for variables, unless we create some kind of complicated database we can only program the speeds and feeds close to what we THINK they should be, or by what the tool has run at in the past on similar cuts. After all isn’t that why there are speed and feed overrides on the machine?
How many bar bets have you lost over which release of SolidWorks supported "Multi-Body Parts?"(Answer:2003) OK I really hope this doesn't happen outside of SolidWorks World. Unless you've been very dilligent about archiving each "What's New Guide" you don't really have a way to answer these all important questions. Please don't call us at support. :)
Instead head over to Ricky Jordan's blog and peruse his archive of What's New Guides. He's compiled them going all the way back to SolidWorks 95! Of course everything was new in 95 so he's got the user guide posted instead.
Thanks to John Hall for pointing this out to me and of course to Ricky for putting it together.