Status - Time

mcam · 2014-07-28 03:47:36

I've been trying to get an accurate cycle time returned in the status window. However, I notice if I use MDI and apply G0 X-500. I get a returned time of 10 seconds. Given that this is a metric machine, with a X rapid rate of 40000mm/min, I would expect it to move a lot quicker than 10 seconds

Can someone tell me where it gets the figure arrowed below as this seems to be the rate of movement?

I tried changing accel/decel figures, but nothing changes.

g0 x-500
Debug: DELTA:From axis=(0 0 570 0 0 0 0 0 0 0 0 0)
Debug: DELTA:To axis=(-500 0 570 0 0 0 -800 0 0 0 0 0)
Debug: DELTA:Distance=(-500 0 0 0 0 0 -800 0 0 0 0 0)
Debug: DELTA:Times=(0.0125 0 0 0 0 0 0.16 0 0 0 0 0)
Debug: DELTA:Adjusted Times=(0.16 0 0 0 0 0 0.16 0 0, 0 0 0)
Debug: DELTA:Adjusted Rates=( This figure ----------> -3125 <------ This Figure 35000 30000 18000 100 18000 -5000 100 100000 100 100 100000)
Debug: DELTA:Current Time = 0.16
Debug: TIMING:RAPID: Feed == 3125, time = 0.16
RAPID 0
Debug: DELTA:axis = (-500 0 570 0 0 0 -800 0 0 0 0 0)
Debug: DELTA:old axis = (0 0 570 0 0 0 0 0 0 0 0 0)
Debug: delta time = 0.16
GOTO/-500.4, 0, 570, 0, 0, 1 0
Debug: TIMING:Delta time = 0.16
Debug: TIMING:Time associated with new Motion/Dwell = 0.16
Debug: TIMING:Total time = 0:00:10

Regards,

Mike

MustaphaC · 2014-07-28 15:51:36

From the debug, looks like your machine moves a U axis also to -800... Can you check that and the rapid rate you have for that axis?

Last edited by MustaphaC (2014-07-28 15:52:14)

mcam · 2014-07-29 03:31:29

Yes, U axis is the door open command. Rapid rate for that is set to 100metres/min.

MustaphaC · 2014-07-29 08:46:32

OK, I recommend you use a different sub-system for the U axis to avoid any interference. Another point to check is to see if "Apply Acceleration to Cycle Time" is checked?
You can find this option in Project Tree, select the setup branch, in configure panel go to "G-Code" tab, you will see option "Apply Acceleration to Cycle Time", uncheck it if check and try again

mcam · 2014-08-10 21:04:01

Thanks, I am slowly getting results. This configuration will take some time to perfect

vhubbard · 2014-12-05 14:54:32

I have been working to get accurate times from Vericut for years. We change the Acceleration settings for Rapid, Feed, and the Various High Speed modes in the control. (new function added about 2 years ago) You can get close on time depending on the job, but never close enough. "Apply Acceleration to Cycle Time" enables the ACC/DEC calculation for each move in Vericut. You should see times get longer with this enabled, which is more accurate.

Acceleration and Deceleration, ACC/DEC, as calculated by Vericut is linear from what I was told. On most machines it is a bell curve ACC/DEC. Bell curve ACC/DEC is much slower at the start of the move, but accelerating in a non-linear fashion. The Linear ACC/DEC used by Vericut will often report faster machining times.

When you have longer moves, 1"/25mm or more and very few short moves, Vericut can get within 5-15%. With a high percentage of short moves, .1" /2.5mm or less and high feed rates Vericut will show the moves much faster than they are at the machine. Vericut will report times up to 50% shorter than actual run time.

On a job with 1 million moves and the majority of the moves being in the .04/1mm range and feeds of 400-1000IPM/10-25MM, Vericut is off by up to 40%.

The slower the feed and longer the move, the less ACC/DEC calculations matter.

I don't see time calculations getting better until Vericut can simulate Bell Curve ACC/DEC.

Last edited by vhubbard (2014-12-05 14:55:49)

VERICUT Users' Forum

#1 2014-07-28 03:47:36

Status - Time

#2 2014-07-28 15:51:36

Re: Status - Time

#3 2014-07-29 03:31:29

Re: Status - Time

#4 2014-07-29 08:46:32

Re: Status - Time

#5 2014-08-10 21:04:01

Re: Status - Time

#6 2014-12-05 14:54:32

Re: Status - Time

Board footer