-
Posts
26 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
eMastercam Wiki
Blogs
Gallery
Events
Posts posted by Alex_AMEAB
-
-
Read from parameter 20007 instead. It's the fifth value. You need to format variables to hold as many values as the value you want to read.
fmt 2 dummy1 fmt 2 dummy2 fmt 2 dummy3 fmt 2 dummy4 fmt "A" 11 radtla if prmcode$ = 20007, dummy1 = rpar(sparameter$, 5)
Radtla will now output your arbor diameter.
-
If you're using the old coolant commands this could solve your problem.
Define label "used_coolant". use this to save your coolant$ value in ptlch$. Then set up a condition in pretract.
used_coolant : 0 # Coolant M code selection for V9 style coolant sm09 : "M09" #Coolant Off sm08 : "M08" #Coolant Flood sm08_1 : "G83" #Coolant Mist sm08_2 : "M08" #Coolant Tool scoolant : "" #Target for string ptlch$ .... n$, *sgcode, pfzout, strr0, smaxrate, scoolant, e$ used_coolant = coolant$ #Make sure to put this line after scoolant. .... pretract .... if used_coolant = 2, n$, "G84", !scoolant, e$, else, n$, scoolant, e$ #Add this in front of scoolant. ...
-
So what if you have different sizes of the same tool, like a concave, convex, or double angle cutter. Do I have to redraw for each thickness or will MCAM scale like it does for all other tools.
If your tool can be defined as any of the predefined tools in Mastercam, you can draw it, scale it down 1/the size your tool is drawn, define it as one of the tool types, use your geometry and mcam will scale it.
-
First you draw one half of the profile of the tool in 2D. Do no use any centreline. Save your tool geometry in the tool folder.
Then create a new tool, chose "Undefined" as tool type. Switch to the first tab and then chose custom file as profile, select the file with your tool.
Set the diameter of the tool and you're done.
- 1
-
-
Was that directed to me or Jeremy? Because i couldnt find anything in the change notes about the xss and css files
-
This is my solution:
pfcout #if index = zero & rot_on_x #[ if use_rotmcode & (fmtrnd(cabs) <> fmtrnd(prv_cabs) | sof), *sindx_mc if absinc$ = zero, *cabs, !cinc, !cout_i else, *cout_i, !cinc, !cabs #]
It looks like rot_on_x is set to 0 first time the post enters the ptlch_com section. Therefore no A0 output.
Doing this will move the output of A to the G00 G90 G54 yada yada line (uless you move it in the post ofc).
Seems to have no effect on the output when doing simultanious 4axis toolpaths
edit: This is from mpmaster
-
Have anyone else had problems copying the css and xss file from X5 to X6? It worked fine from X4 to X5, but now i get an error when X+ is trying to read the files.
Error message "Attempted to access an unnamed file past its end."
2D Dynamic Toolpath in X6
in Industrial Forum
Posted
Dynamic core with solid linking. Set the bottom face as your machining region and set the walls (or top of the walls if they are completely vertical) as avoidance regions.