You are not logged in.
Pages: 1
I'm using APT code to simulate 5 axis programming.
How does Vericut handle the time it takes to do a pure rotational move?
I tried a 90º turn and the time increment was zero. Does accurate time calculations require G Code and a machine that's setup?
Thanks
Offline
Yes, you are correct in assuming that simulating G-code tool paths can provide the most accurate time calulations. VERICUT simulating G-codes can reveal programming errors that are not possible to detect in an APT/CLS simulation. This is because VERICUT's machine file provides detailed information about how the machine moves, for example: correct rapid rates per axis, interpolation properties, prioritized rapid motion behavior (often refered to as "squared-off" or "hockey-stick" motion), and rotary pivot behavior (rotation about head center versus tool tip, etc.).
When simulating APT/CLS tool paths, VERICUT has limited information about how the tool is moving: feed rate (if programmed), rapid rate (via the "Fast Feed" Motion setting, and possibly some information about rotary behavior as configured in the APT Settings window. Machine time is calculated based on the distance the tool travels and assocaited feed rate for the motion. I believe your example of the tool rotating about the tool tip does not add time for rotation since the tool tip is stationary. Typical multi-axis motions where the tool tip and tool axis vector are changing do add calculated time for the motion.
Hope this helps explain things a little better for you. --Gene
Offline
Gene-
Thanks. That makes more sense.
Offline
Pages: 1