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 2009-09-18 06:22:25

chimpchoker
Member
Registered: 2009-09-18
Posts: 3

Vericut predicted runtime

Hi all,
         If anyone can help solve this mystery I would be very grateful. My problem is as follows, the time taken to bore 4 holes, 100mm deep, at a feedrate of 80mm per min should be, and actually is on the machine, around 5 minutes. However, Vericut's predicted time is just under 11 minutes. This is just too far out to be an acceleration/decceleration problem and I was hoping someone would know of a setting that could be set wrong in our setup, or if anybody has had the same large margin of error in anything they have done.

Many thanks

Offline

#2 2009-09-18 15:49:01

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

Re: Vericut predicted runtime

Make sure the control has the right Cycle macro tied with your bore cycle.   Sounds like you may have a CyclesBore called out when you need a CyclesBoreDrag or CyclesBoreOrient called out.  CyclesBore feeds in and out while the others Rapid out I believe.

Offline

#3 2009-09-21 08:07:29

chimpchoker
Member
Registered: 2009-09-18
Posts: 3

Re: Vericut predicted runtime

Thanks vhubbard, this sounds very likley as the predicted time is around twice the actual. Sorry to be a pain but my experience with vericut goes as far as setting a job up and running the simulation, so I would appreciate it if you could walk me through how I would tie the correct macro with the bore cycle.

Offline

#4 2009-09-21 16:28:36

MIKEFITZ
Member
From: Chicopee, MA
Registered: 2009-06-18
Posts: 104

Re: Vericut predicted runtime

Click Configuration > Word Address > Cycles. selct the appropriate g code entry, (g85, whatever). right click on it, click modify. in the text field beneath Macroname, type "cycles" if the list doesn't show all the cycles options. selelct the desired cycle, (CyclesBoreDrag, CyclesBoreOrient) and hit Modify. Make sure the Word field says G, and the Range field says the number associated with that command, in this case 85, or whatever code you are modifying. after this, you should be good to go. hope this helps.


Mike
Hoppe Tool

Offline

#5 2009-09-22 07:44:56

chimpchoker
Member
Registered: 2009-09-18
Posts: 3

Re: Vericut predicted runtime

Thanks Mike, we're using release 5.4.2 and it dosn't seem to be configured this way. Any ideas where I can find this area in our release?

Offline

#6 2009-09-22 11:07:22

MIKEFITZ
Member
From: Chicopee, MA
Registered: 2009-06-18
Posts: 104

Re: Vericut predicted runtime

I'm not positive, but if you hit F1 it should call up the help for Vericut. Type "Configuration" in the search bar, and that should bring up a list of topics that will help. I'm using Ver. 6.1.2 myself, so I'm not sure about some of the differences between the two versions. Also, if you open the training sessions, there should be a session about configurating your controls.


Mike
Hoppe Tool

Offline

#7 2009-09-23 05:45:22

rhinos
Member
From: Czech Republic
Registered: 2005-03-17
Posts: 19

Re: Vericut predicted runtime

I have similar problem.
In version 6.0 - 6.1.2 is the time calculated correctly, but since version 6.2 is a relatively large error in the time simulation.
Solution should be version 7, but they still have no


Manufacturing of Turbine blades

Offline

Board footer