VERICUT Users' Forum

Due to relentless spammers, we are no longer automatically accepting new forum registrations. If you wish to register for this forum, please send an e-mail to: info@cgtech.com

You are not logged in.

#1 2006-01-20 14:09:35

tri
Member
From: MA
Registered: 2005-11-28
Posts: 17

cycle time question???

Vericut Time Vs. Machine Time:: DMC 60T

Cycle time from Vericut is off from what the operator records from machine.

What do I need to do in order for Vericut to generates the right time?
Rapid feedrate of the axes is set to machine information.
I noticed that ToolChain also plays part in cycle time.

I had this job run in Vericut, and before I add in ToolChain::
  The time come out from Vericut to be 83mins.
  The actual machined time is 90mins.
But when I added in ToolChain::
   Vericut = 138mins

Does anyone know the solution to this??
Thanks,

Offline

#2 2006-01-20 16:21:24

SergeV
Senior Member
From: Irvine, CA
Registered: 2004-10-08
Posts: 507
Website

Re: cycle time question???

If you added some axis motions to your tool chain assembly (like in vericut.usr) it might be that the cycle time is considered in the calculation. if you have such motions, add the macro ProcessTimeOnOff before and after the motions in your control.

also verify that the tool change parameters in the Tool Chain component attributes are set correctly.


To test the tool change time:
Open Info> Status
MDI: T1 M06
-- notice the difference in time.

Offline

#3 2006-01-20 22:23:28

tri
Member
From: MA
Registered: 2005-11-28
Posts: 17

Re: cycle time question???

I do have the ProcessTimeOnOff macro in my control.
Toolchange parameters might not be set correctly ::
Tool exchange time is set @ 5sec.
This is the website where i got my tool change parameter:
http://www.gildemeister.com/us,milling, … ument&ma=2
Likely, it didn't tell me much.

I had this job run in Vericut, and before I add in ToolChain::
The time come out from Vericut to be 83mins.
The actual machined time is 90mins.
But when I added in ToolChain::
Vericut = 138mins

Let just say:  if I dont' have toolchain and run this two jobs::
Job #1: machine time = 90mins
            vericut time = 83mins
Job #2: machine time = 30mins
            vericut time = 20mins

And now I added in the toolchain and rerun that two jobs::
Job #1: vericut time = 138mins
Job #2: vericut time = 32mins

:?  :?  :?  I'm really confusing!!!

There is another one... I ran this job #3 on vericut and get 18mins.
But it's not fast enough. So, I went back and speed up the feedrate, and rpm.
Then I reran it through vericut and got 19mins. yikes
How is that posible???

Offline

Board footer