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 18:32:20

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

3 suggestions

Multiple suggestions
1. I need a way to identify when Machine Macros have been added to a release.  Many machine simulation enhancements are driven with these macros.  Something as simple as listing the rev it became available within the macro's online documentation. 

1A.  Reference in the documentation which Sample/Library files use the Macro.  One programming example is worth many pages of text.

2.  Be able to name individual holders and have Vericut report which holder in the tool assembly caused a collision.  Taps, reamers and other tools with non cutting ends can have a small holder defined for use as the tool tip/center.   When this tip/center encounters uncut material a holder cutting material error is reported.  We do this now and we get the generic Holder removed material message.  It would be much better if we could name this holder "Tool Tip" and then Vericut would report Tool Tip cut material, much clearer to the user what is wrong.   

3. Accel/Decel settings for both Feed and Rapid conditions in a machine tool.  Newer machines Rapid Accel/Decel values can be 10x or more higher than the Feed Accel/Decel values.   Current Vericut time estimates are not as accurate as they could be since Vericut only supports 1 Accel/Decel setting for both.

Offline

#2 2006-09-08 17:55:45

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

Re: 3 suggestions

In Vericut 6.0x
1. has been improved.

2. Listing which holder caused a collision has been implemented.

Waiting on 1A and 3.

Offline

#3 2013-07-01 14:56:08

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

Re: 3 suggestions

7.2.3 fixes #3.   New macros allow changing the ACC/DEC setting in the control.  Takes some work but can be done.

Examples of the .ctl code.
This is set when going to RAPID modes  Values hard coded since high speed modes do not effect RAPID only feed moves. G0
Rapid, G0, G80
        <Macro Name="SetComponentAcceleration" Scan="no" AfterMotion="no">
          <Override  Type="text"  Value="X"/>
          <Override  Type="value"  Value="192"/>
        </Macro>
        <Macro Name="SetComponentAcceleration" Scan="no" AfterMotion="no">
          <Override  Type="text"  Value="Y"/>
          <Override  Type="value"  Value="192"/>
        </Macro>
        <Macro Name="SetComponentAcceleration" Scan="no" AfterMotion="no">
          <Override  Type="text"  Value="Z"/>
          <Override  Type="value"  Value="192"/>
        </Macro>
This is used when going to Feed modes,  G01, G02, G03 and cycles.
        <Macro Name="SetComponentAcceleration" Scan="no" AfterMotion="no">
          <Override  Type="text"  Value="X"/>
          <Override  Type="expression"  Value="#$xac"/>
        </Macro>
        <Macro Name="SetComponentAcceleration" Scan="no" AfterMotion="no">
          <Override  Type="text"  Value="Y"/>
          <Override  Type="expression"  Value="#$yac"/>
        </Macro>
        <Macro Name="SetComponentAcceleration" Scan="no" AfterMotion="no">
          <Override  Type="text"  Value="Z"/>
          <Override  Type="expression"  Value="#$zac"/>
        </Macro>

These variables are set to define the FEED ACC/DEC at the start of processing and also are reset as needed when the various high speed modes are called out in the control.
        <Variable Name="$XAC" Scan="no" AfterMotion="no">
          <Override  Type="value"  Value="38"/>
        </Variable>
        <Variable Name="$YAC" Scan="no" AfterMotion="no">
          <Override  Type="value"  Value="76"/>
        </Variable>
        <Variable Name="$ZAC" Scan="no" AfterMotion="no">
          <Override  Type="value"  Value="41"/>
        </Variable>

The trick now is getting the IPM/sec*sec values for feed and high speed modes to put in the definitions.  Sales brochures usually only list the RAPID ACC/DEC if anything.

Offline

#4 2014-04-24 19:12:47

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

Re: 3 suggestions

3 can be implemented with some coding in the control since 7.2 or 7.3, but it is simple linear ACC/DEC.  Better, but now we need Bell-Curve acc/dec to match what is happening with many small moves.

Offline

Board footer