SlaveCam
-
Posts
774 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Forums
Downloads
Store
eMastercam Wiki
Blogs
Gallery
Events
Everything posted by SlaveCam
-
How to change default wireframe color in project?
SlaveCam replied to SlaveCam's topic in Industrial Forum
Nope -
When I open an existing project It ALWAYS defaults back to a certain color. How do I save this setting? - Configuration wireframe color has no effect - Plane color has no effect
-
Anybody else wished it was possible to extract edges from solid using section views?
-
I find opinfo much simpler to use than the old complicated mechanism for getting parameters. Is there any drawback in mixing the two? I can't rewrite the post for opinfo fully, but instead start gradually using it more and more.
-
This is definitely something that should be doable in a custom DLL. We have different uses for the custom drill cycles and hard-coding movement pattern to them is not a good thing IMO, especially when there many variables even to a simple pecking cycle so you should then be able to adjust them all to get 100% proper backplot.
-
Read Mazatrol work offset in ISO/EIA subprogram
SlaveCam replied to SlaveCam's topic in Machining, Tools, Cutting & Probing
Hi and thanks. This control doesn't seem to be new enough as those variables did not work. But after hours of digging, I finally found the proper ones: X=#5341, Y=#5342, Z=#5343 (source: https://www.factorydaily.com/fdattachs/fdattachs7/112716211424392.pdf) -
Any advice from a Mazatrol (M plus, 20 years old control) guru is most welcome. The process is that we use probe to get the initial part zero and this is done in a Mazatrol prog. The Mazatrol prog then calls a sub that is made by Mastercam(tm). The problem is that I am not having much luck figuring out how to read the work offset data from the Mazatrol program at the EIA side. What system parameter(s) are the axis values stored? (I know you can directly set those values in G54..G59 but that is not a solution here)
-
Changing drill rpm at a point in progress
SlaveCam replied to So not a Guru's topic in Industrial Forum
Sure there are many workarounds, but most of them count as hack in my book. Why not just remove the limit? We're not in 80s using 640KB of memory any more. -
Changing drill rpm at a point in progress
SlaveCam replied to So not a Guru's topic in Industrial Forum
Custom drill cycles is the way to go. Unfortunately they are limited in number. I am already running out of them. -
QuickParameters NET-hook for Mill and Router Operations
SlaveCam replied to Zaffin_D's topic in Industrial Forum
I think it's about time Mastercam started implementing plug-in architecture so that you could customize the GUI directly with your own dll's. Operations tree is the best (worst) example; I always find it outright messy and slow to use, being so congested with text the information gets easily lost in it. Even alternating background coloring of operations would help. -
Time for a sanity check. I tested this this morning and thought it works, now after some modifications I get tool dia and radius same for every tool. I reverted back to the original code above and still the same. Btw. is there a shortcut to "expand all regions" in Code Expert?
-
Now whoever told you that?! Why disable it in the first place since the user is already being warned when you press the button.
-
I have actually never had to use more than one post per machine definition. So, how do I un-gray "Select Post" button in the post dialog so that I won't have to change the post in machine definition to use it? Edit: Apparently not possible.
-
Awesome, thank you.
-
None of our horizontal mills support dynamic work offset, that is, the work offset rotates automatically with the pallet. Because of this I have started implementing logic into my post that uses G55 as the source work offset and after each rotation, the rotated work offset is written into G56 that is used by every rotated plane. G54 is always (0,0,0) and thus reserved for center-of-rotation programming, meaning every single program prior to 2018. The reason I am forced to do this is because probing is becoming very common it is a huge PIA to handle rotations with work offset corrections.
-
Is there a readily available post processor that writes a tool list similar to the one that right click->tool list over operations tree does?
-
QuickParameters NET-hook for Mill and Router Operations
SlaveCam replied to Zaffin_D's topic in Industrial Forum
This will definitely come in useful. Not too many nethook examples around. Thanks for sharing. -
Thanks. I am looking forward to get some quick training in it but I'm quite certain it has no place for complex 5-axis jobs.
-
My thoughts as well. It is obviously good for the simpler things. Smoothcam as a name is pretty much not recognized by Google so maybe it is a name our local machine tools vendor made up.
-
I have not used the software but keep noticing that Integrex machinists in our shop keep falling back to Smoothcam even though we have Mill-Turn and I would of course prefer that everything was programmed in Mastercam (and not mix two different cam software). Is it so much easier and faster to use than MC? The problem is that operators come to me asking for drill point coordinates and drill vectors for Smoothcam programming and I have to provide them with printouts from MC. I know Mill-Turn is not the easiest thing to learn, so how limited is Smoothcam when compared to MC?
-
It is better if you ever want to advance into learning the C-hook API. And personally, I dislike the syntax of Basic. Knowing even one language of the C family tree is a big advantage.
-
A bit offtopic, but I recommend ditching VB and learning C# as early as possible in the learning phase
-
I'm about to embark on the same quest. We have a document management system (M-Files) yet nobody uses it for what would be really useful. Controlling different Mastercam project versions!
-
Every answer seems to be praising a 3D mouse, but I did not manage to get used to one (SpaceNavigator), despite two weeks of effort, after which I gave up. It kept slowing me down too much so I always resorted back to mouse, otherwise it would have been impossible to get things done. The learning curve is very steep or I am getting too old.
-
Because programs posted/ran separately have FMS-specific commands at the beginning. Those commands must be run only once per program.
