-
Posts
2,337 -
Joined
-
Days Won
100
Content Type
Profiles
Forums
Downloads
Store
eMastercam Wiki
Blogs
Gallery
Events
Posts posted by JParis
-
-
I have found 2019 to be considerably slower opening larger files (100+ megs)...I have a solidstate drive....a local installation on files on the solidstat drive, 32 gigs K4000 Videocard
I have tried opening same file across the network and local......no discernible noted difference
I have just chalked it up to slow performance plain and simple
Not griping about just fetting the job done as I can
- 1
-
It can be a sitting only position but it would have to be for a company that employs programmers only as programmers.
Generally speaking, to land a job like that requires years of machining experience, which means being on your feet a lot...
Many smaller shops will have machinists who also program, that can mean a good deal of time on your feet...
As you're asking the question, I'm going to "assume" you don't have any real manufacturing experience behind you....if that's accurate, considering your situation and what you'd need to most likely need to do to be successful as a desk jockey only, I would suggest a different path...simply because you won't have the ability to do the necessary floor time.
-
If you copied your config from a previous version, delete it and restart Mastercam make a fresh new one
-
17 hours ago, jlw™ said:
Randy has a solution here that works for me pretty much every time. It adds a little work but it works:
Thanks, faster for me in most cases just to use the stl's
-
In the config there's a chord height setting, it can help, just be careful how much you turn it up...
At least it's there in the full version but I would imaging it is in the HLE as well
and be aware, on board graphics cards are not supported and under perform as well as most need hardware acceleration turned off ust to function
- 1
-
2 minutes ago, gcode said:
I have never had any luck using toolpaths to define stock models.
The regen times are just too long to be a workable solution
and I have had too many times where the stock model has "holes" in it.....
Which has caused issues...
There are times stock models work just fine, VMC flat work....once you get in rotary and multi-axis work....most times you'll find you have to modify your gameplane...stl's still work and for the most part, that's what I use as well as the bulk of my work is HMC/Multi-axis or Mill/Turn
-
What resolution is your screen set to? That's the only way to get better look is to run as high a resolution as your screen and card can handle
-
Rolldie...looks like a cam slot....good application for it I think
- 3
-
What database? Mastercam doesn't have a database in that kind of sense...
You can output reports, there are several methods from Active reports to .set sheets, X+ and several other ways as well
-
I prefer to set mine up like so...
ptap$ #Canned Tap Cycle pdrlcommonb pitch = 1 / n_tap_thds$ #added 7/2/07 ADDED Peck Tapping option -09/05/2018, result = newfs(17, feed) # Set for tapping Feedrate format pcan1, pbld, n$, *sgdrlref, *sgdrill, pxout, pyout, pfzout, pcout, [if peck1$ > 0, *peck1$], prdrlout, *pitch, !feed, strcantext, e$ # changed from *feed to *pitch, !feed 7/2/07 pcom_movea
- 1
-
16 minutes ago, SlaveCam said:
Anybody yet found any actual use for automatic work offset?
I use it when transform parts in a strip on verticals mostly
-
Mastercam considers by default a new plane, a new work offset...
Set them to what you want...if only G54 is desired set the work offset value to 0
- 1
-
If the logic has not already been added to the post, it's a 100% post issue....the control def fields are just the method of inputting the data.
If the post doesn't know what to do with said data, it will do absolutely nothing different
- 1
-
Use wear and be done with it
-
3 minutes ago, Jbowen said:
Ok, anything I can do to use X9?
Nope, they, the HLE's time out purposely...
It's 4 versions old, soon to be 5....Hopefully they're using a later version by this time
-
There are no glitched in Mastercam
The are fairies with pixie dust that makes magical things happen
or deranged gnomes...never really sure which at times
-
Set the depth to the top of the surface to be chamfered, then click on the calculator button next to the depth box, set the diameter in there, set to "Add to"
-
-
Try the machine in tape mode....click to sent the program....hit cycle start
- 1
-
This is one of those things I would be surprised to really ever see in Mastercam.
It would need to take them into the realm of a full blown CAD package....with that comes all of the other tools that design CAD users expect in the software they employ, otherwise, it would still just be a CAM system with some basic CAD functionality. While I agree it would be nice to have it become a parametric modeler, I just don't know how feasible it in the Mastercam world. I think Mastercam would have to be sold off for it to have any real chance at that, then the buyer would need to blend it into their package.
As we currently see in the world of CAM consolidation, many names are bought just to see them discontinued within a few versions.
JM3C
-
So you're trying to stuff 25-30 years of knowledge into a 12 month bag
-
It's a c-hook
- 1
-
3 minutes ago, nperry said:
I'm just curious why this is rule of thumb?
Thanks.
You A rotation outputs will be backwards....
If you look at Top & Front the X axis runs to the right...if you look at Back and Bottom the X axis runs to the left
- 1
-
Just now, Newbeeee™ said:
That's a ball ache then surely? Okay, lots of tool blocks are reasonably standardised, but lots aren't.
Done once and it's in there....that's something that is "supposed" to be opened up eventually and in truth, it needs to be, as does the ability to switch from a chuck to a spindle nose
That flexibility at the user level is highly desirable
- 1
Transform toolpath work offset?
in Industrial Forum
Posted
Are you trying to use a work offset shift or just a coordinate shift?
If you're reating a now work offet, you'll need to set that position in your control....
If you're just using coordinate shift the you set a value distance in the transform operation..
The answer ultimately depends on exactly what you're trying to do