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.

Pages: 1

#1 2010-10-23 17:49:32

Tinhman
Member
Registered: 2010-06-26
Posts: 23

Cycle time for G83 is way off.

Could somebody please guide me how to fix this problem??
I am using ver. 7.xx
Thank you in advance.

Offline

#2 2010-10-25 15:58:05

Tinhman
Member
Registered: 2010-06-26
Posts: 23

Re: Cycle time for G83 is way off.

Hello,
any one??
please

Offline

#3 2010-10-27 07:55:27

MustaphaC
VERICUT Specialist
From: Le Mans, France
Registered: 2004-10-14
Posts: 130
Website

Re: Cycle time for G83 is way off.

Which control are you using?

Mustapha

Offline

#4 2010-10-27 18:27:11

Tinhman
Member
Registered: 2010-06-26
Posts: 23

Re: Cycle time for G83 is way off.

VARIAXIS M730

Offline

#5 2010-10-28 07:09:53

MustaphaC
VERICUT Specialist
From: Le Mans, France
Registered: 2004-10-14
Posts: 130
Website

Re: Cycle time for G83 is way off.

A possible reason could be the units interpretation of the feedrate, MM/MIN vs. MM/REV for example. If using MM/REV then spindle speed needs to be correct etc...
If you use the G-Code debug and check the cycle time you can see each single motion with the corresponding time. For example:
- Open the sample project file "fanuc_subroutines_multiple_parts.vcproject" in the samples folder
- Configure project to stop at line #40
- Create a G-Code log file by Project > G-Code > Process Options, use Browse to select folder and file name, for example "Debug.log", in Debug tab use "Debug Macro" + "Cycle Values" + "Debug Timing", OK
- Press play
- Step by step until G#3G99Z-#26R.1F#9Q.1 (at that point #3=83
- Now open the G-Code log file by Project > G-Code > Process Options, "View G-Code Log File"
- At the end you get the information about the last NC block, something like this:

G#3G99Z-#26R.1F#9Q.1
  Debug: MACRO:BlockInit, WORD:, TEXTSTR=, VALUE=0
  Debug: MACRO:CyclesDeep, WORD:G, TEXTSTR=#3, VALUE=83   CONDITIONAL: * *
  Debug: MACRO:SetCycleRetractLevel, WORD:G, TEXTSTR=2, VALUE=0   CONDITIONAL: * *
  Debug: MACRO:SetCycleDepth, WORD:Z, TEXTSTR=0, VALUE=-0.45   CONDITIONAL: (CYCLE ON) and (ABS_INC ABSOLUTE) and (MOTION_PLANE XY)
  Debug: MACRO:SetMotionFlag, WORD:Z, TEXTSTR=-#26, VALUE=-0.45   CONDITIONAL: (CYCLE ON) and (ABS_INC ABSOLUTE) and (MOTION_PLANE XY)
  Debug: MACRO:SetCycleRapidLevel, WORD:R, TEXTSTR=0, VALUE=0.1   CONDITIONAL: (CYCLE ON) and (ABS_INC ABSOLUTE)
  Debug: MACRO:FeedRate, WORD:F, TEXTSTR=#9, VALUE=10   CONDITIONAL: * *
    FEDRAT/10,IPM                                                                200
  Debug: MACRO:CycleStepValue, WORD:Q, TEXTSTR=.1, VALUE=0.1   CONDITIONAL: (G 73 83)
    CYCLE/DEEP, RAPTO, 0.1, FEDTO, -0.45, STEP, 0.1, CLEARANCE                   200
  Debug: Drill Cycle Arguments
  Debug:    motion_plane = XY Plane
  Debug:    initial_point = (0.5, 0.866, 0.5)
  Debug:     Rapid Level = 0.1, type = Absolute
  Debug:    Part Surface = -0.1, type = Incremental From Rapid Level
  Debug:    Depth = -0.45, type = Absolute
  Debug:    Retract Level = 0, type = Incremental From Rapid Level
  Debug:    step_down = 0.1
  Debug:    step_up = 0
  Debug: Drill Cycle Apt Parameters
  Debug:    GotoPoint = (0.5, 0.866, 0)
  Debug:    Tool Vector = (0, 0, 1)
  Debug:    RapidTo = 0.1
  Debug:    FeedTo = -0.45
  Debug:    RetractTo = 0.1
  Debug:    StepDown = 0.1
  Debug:    StepUp= 0
  Debug: Time Attributes: Drill cycle: RAPTO
  Debug: Delta time = 0.002
  Debug: Time Attributes: Drill cycle: Step RAPTO
  Debug: Time Attributes: Drill cycle: Step down
  Debug: Delta time = 0.01
  Debug: Time Attributes: Drill cycle: Step up
  Debug: Delta time = 0.0005
  Debug: Time Attributes: Drill cycle: Step RAPTO
  Debug: Time Attributes: Drill cycle: Step down
  Debug: Delta time = 0.02
  Debug: Time Attributes: Drill cycle: Step up
  Debug: Delta time = 0.001
  Debug: Time Attributes: Drill cycle: Step RAPTO
  Debug: Delta time = 0.0005
  Debug: Time Attributes: Drill cycle: Step down
  Debug: Delta time = 0.02
  Debug: Time Attributes: Drill cycle: Step up
  Debug: Delta time = 0.0015
  Debug: Time Attributes: Drill cycle: Step RAPTO
  Debug: Delta time = 0.001
  Debug: Time Attributes: Drill cycle: Step down
  Debug: Delta time = 0.02
  Debug: Time Attributes: Drill cycle: Step up
  Debug: Delta time = 0.002
  Debug: Time Attributes: Drill cycle: Step RAPTO
  Debug: Delta time = 0.0015
  Debug: Time Attributes: Drill cycle: Step down
  Debug: Delta time = 0.02
  Debug: Time Attributes: Drill cycle: Step up
  Debug: Delta time = 0.0025
  Debug: Time Attributes: Drill cycle: Step RAPTO
  Debug: Delta time = 0.002
  Debug: Time Attributes: Drill cycle: Step down
  Debug: Delta time = 0.015
  Debug: Time Attributes: Drill cycle: Dwell
  Debug: Time Attributes: Drill cycle: RAPTO
  Debug: Delta time = 0.0028
  Debug: Time Attributes: Drill cycle: RETRACTO
  Debug: MACRO:BlockFinish, WORD:, TEXTSTR=, VALUE=0
  Debug: Total time = 3.5195

As you can see, you have the Feedrate used (FEDRAT/10,IPM) and the time corresponding to each Step up, Step Down, RAPTO (Rapid Motion to) etc...

See if you have a Delta Time somewhere which is not expected then try to find the cause.

I hope that will help you to get a more accurate G83 cycle time

Mustapha

Offline

#6 2010-10-29 16:05:33

Tinhman
Member
Registered: 2010-06-26
Posts: 23

Re: Cycle time for G83 is way off.

Thanks for the reply.
Well, it seems over my head :? . But i will try it when a have alittle more time.
Happy friday.

Offline

#7 2010-10-29 18:45:19

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

Re: Cycle time for G83 is way off.

...or you can simply send your files to Technical Support, they can quickly look at it for you.

Offline

Pages: 1

Board footer