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 2004-11-11 17:35:46

pczombie
Member
From: Ohio
Registered: 2004-11-11
Posts: 2
Website

Machine run time VS Vericut

What values do I change to get a more accurate time output versus machine run time?

Offline

#2 2004-11-11 18:41:08

BillH
VERICUT Specialist
From: Irvine, CA
Registered: 2004-10-08
Posts: 146
Website

Re: Machine run time VS Vericut

The speed and acceleration of each axis is set in Model > Model Definition > Component Attributes tab. Select each motion axis in the Active Component choice list, then set its values. The values are saved in the machine file.

You can set values for Rapid Rate, Acceleration, Deceleration, and Max Feed Veloicity.

Rapid Rate tells VERICUT the maximum each axis moves when in rapid mode.

Max Feed Velocity is maximum feed rate, regardless of what's programmed.

These values, plus the Acceleration and Deceleration values are used in the time calculation if you check Setup > G-Code > Settings > Apply Acceleration to Cycle Time. If you don't check this VERICUT assumes infinite acceleration for each axis.

These values, plus Acceleration and Deceleration are also used by OptiPath and Curve Fitting when you enable it. Additionally Max Velocity for Direction Change is used to output a small motion at direction changes that exceed the axis' deceleration capabilities.

Hope this helps,
Bill

Offline

#3 2004-11-11 19:06:47

pczombie
Member
From: Ohio
Registered: 2004-11-11
Posts: 2
Website

Re: Machine run time VS Vericut

Thanks Bill,  I will give it a try.

Offline

#4 2004-11-11 19:17:27

vhubbard
Beta User
From: Dallas, TX
Registered: 2004-11-11
Posts: 222
Website

Re: Machine run time VS Vericut

We have Vericut  batch mode setup to generate machine time estimates for our jobs.  We can generate a report showing the time for each tool if needed.  Getting correct times takes some setup work.

Machine limits, feeds and rapid rates for each axis must be defined correclty. 

For things like tool change, spindle run up, axis clamping and pallet shuttling we use the DwellTime macro in the control to fine tune the run times.

Accel/Decel should be defined and enabled.  Currently only 1 Accel/Decel setting is allowed.  Maybe in the future there will be an Accel/Decel setting for FEED and RAPID modes to match settings in the machines.  It does make a difference.

Machine kinematics need to be defined correctly.  Travel from Tool change position to part, retract moves etc all add up, even in rapid. 

We even do full Macro B simulation of our probing routines. 

Those pesky Stops in the tape for clamp changes etc are real hard to get a time for.

Tool preselect time is hard to predict with random loaded tool belts.  Many times 0, others 30 seocnds depending on the machine, tool position and run time of previous tools.

Vericut is normally a little "faster" than actual.   All in all it is the best time estimators we have had.

Offline

#5 2004-11-12 01:19:32

BillH
VERICUT Specialist
From: Irvine, CA
Registered: 2004-10-08
Posts: 146
Website

Re: Machine run time VS Vericut

Good points Val.

Regarding tools in pockets...

We added the "Tool Chain" component in VERICUT 5.4. Its time is added in the calculation. You can setup the shape of the tool chain path, the distance between pockets, and the pocket-to-pocket time. Then, depending on whether you're doing tool pre-select or not, the time could be important, as you point out.

Of course, that means the shop floor has to load the tools the same way you did in your simulation (yeah, right!).

Offline

Board footer