Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.
Use your display name or email address to sign in:
I use misc integers on most of my dynamic milling operations.
This might have something to do with your dynamic milling issue. Pre-version 2018 you could do all of the text work much more efficiently inside the post. Now with XML sadly it's more efficient to do it through the machine def - control def. I understand because of language varieties this makes life easier for MC but it makes more work for the customer no matter what language is being used.
Can you tie a condition to mi$, mr$, canned text, a drill parameter or custom drill parameters?
Edit: Nevermind, I missed that or already doing that. Try adding a condition that will reinitialize it until your done with the probing. I'm done for the weekend and I don't have my post at home.
Try searching here for pmachine and you will see a different example but it will show the process.
Mic 6 is a cast aluminum material so a cut thread will have less holding pressure than with wrought/ extruded material. Depending on the thread usage you may want to roll tap to get the increased holding pressure.
The post debugger will either give you the post line number for each block (F7) or give you a post line for each variable on each block (F5) but if you don't know how the post operates or how to edit what you need then the debugger will do you little good. Depending on your answer you will have what you need or may want to call your reseller to see if they have a post class and/or have them fix your post as needed.
You can also search this site for answers or post questions in the post forum.
You can have as many speed and feed versions of the same tool as you want. Copy the original tool, adjust speeds and feeds as needed then save the tool with either the changed feed/speed or as what process that tool is created for.
You can rig it like this,
pcoolanton
if machine <> 300 & machine <> 800,
[
if coolant$ = 1,
[
sm08, e$
sm08_2, e$
]
if coolant$ = 2,
[
sm08, e$
sm08_1, e$
sm08_2, e$
]
if coolant$ = 3,
[
sm08_1, e$
sm08_2, e$
]
]
but the custom coolant is the better way to go.
I had this problem on 2017. What I starting doing was open the first instance and moved it to the far left of my tool bar and open another session and others as needed. If I lost the configs I would close all of the used files first and then close the first instance. When I opened the first instance everything would be back to normal.
I was told that card is doing a couple million calculations per second.
I am (was) (maybe still am) looking at a RTX 2080 ti for my card. I'm replacing my everyday computer for normal home stuff. Writing posts will be a lower percentage of my total time. I actually feel like I'm stealing money by getting that computer.
I mentioned to our President of operations that I was going to buy a gaming computer to replace my old one then start writing a post for our mill turns. He said we use a gaming computer for spectrometer calculations and he would buy that computer for me to work at home.
Here are the specs I got from R&D,
HP Z6 (2TB)
Cost: $4345
CPU: Intel Xeon Gold 5218 2.3GHz
RAM: 16GB (2666 MHz)
HDD: 2TB M.2 SSD
GPU: Nvidia Quadro RTX 5000
Check out this card
I think it might be just a touch overkill for my needs
Make sure your custom tooling is set to a level that will never be used by anything else. Our custom tooling starts at level 8001and ends at 10000. We're currently at 8630ish so we still have growing room.
We do this on all of our horizontal and verticals with no hand work every day. Most of the main and subs are on the same tool path file but the oversized programs have multiple files that get called with M198. As Colin stated it's not difficult to do but it does take preparation to know what the program is going to look like before it gets written into the post.
IF [#149EQ1]GOTO1
TRANSFORMED CODE
BLAH
BLAH
N1 (END OF TRANSFORMED CODE)
If #149 equals one then all code will be skipped until you reach block number one (N1). If #149 does not equal one then the transformed code will be read.
Edit: this will work for Fanuc and ARUMATIK (Kitamura). I would assume that Haas will also support this but I have no experience with them.
Are the master Macro B programs routers for the tool paths? If so you may be able to integrate them into the Mastercam. Our routers are integrated but each program operation can change the flow path through the router as needed for the process. If the master Macro B programs are fixed you should be able to copy them into the post and call each segment as needed thru canned text. It would be effectively be auto cutting and pasting.
eMastercam - your online source for all things Mastercam.
Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.