Scribd
Upload
287 views3 pages

Speed Up VERICUT Simulation Process

This document discusses techniques for speeding up control simulations in VERICUT while still accurately detecting problems. It recommends removing unnecessary display elements, cutting the NC program to end, using OpenGL graphics acceleration, removing the machine view, simulating without animation, and updating the display periodically after a set number of blocks. These strategies reduce the graphic processing load during simulation while still allowing collision and error detection.

Uploaded by

Le Huynh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
287 views3 pages

Speed Up VERICUT Simulation Process

This document discusses techniques for speeding up control simulations in VERICUT while still accurately detecting problems. It recommends removing unnecessary display elements, cutting the NC program to end, using OpenGL graphics acceleration, removing the machine view, simulating without animation, and updating the display periodically after a set number of blocks. These strategies reduce the graphic processing load during simulation while still allowing collision and error detection.

Uploaded by

Le Huynh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Session 3

Control Simulation Speed

Simulating large toolpath will take time. Here are some tricks to speed the simulation
process while still accurately detect problems.

1. Open project file [Link]


• Launch VERICUT
• File > Open
• Shortcut = Training
• File = Fadal6030_table_setup.VcProject
• Open
• Display the Project Tree

2. Remove Display for all axes if Present


• In the graphic window, right-click, Display Axes > Clear Axes

3. Cut NC Program to the end


• Play to End

4. Reset the Cut part


• Once the simulation stops, Reset Model

5. Set the machine view to use the hardware accelerated


display mode (OpenGL)
• In the Machine view, Right-click, Accelerated (OpenGL)
• Play to End

The simulation is always as fast as its slowest component. The machine view has more
display to update therefore requires more graphic processing. By using the OpenGL
mode, VERICUT sends the display processing to the graphics card.

VERICUT V6 Session 3 1
Next, we will remove the machine view and keep only the Workpiece view
6. Reset the Cut part
• Reset Model

7. Cut part with Workpiece view only


• View > Layout > Standard > 1 view

• Play to End

Even if the machine is not displayed, the machine collisions and over travel errors will be
detected and reported.
8. Cut part without animation
• Reset Model
• In the Project tree, select Setup : 1 , right-click, Motion
• Check No Animation
• OK
• Play to End

Even if there is no animation, all the errors are still detected either in the Workpiece view
or in the machine view.

On very large NC Programs, a combination of No Animation and Stop At : Tool change


will allow you to simulate fast and still see the part at every stage of fabrication.

VERICUT V6 Session 3 2
Another option is to have the animation on but update the display periodically after a
specified number of NC blocks.
9. Cut part with the display updated every 100 lines
• Reset Model
• In the Project tree, select Setup : 1 , right-click, Motion
• Un-Check No Animation
• Skip Cut = 100
• OK
• Play to End

10. Exit VERICUT


• File > Exit
• Ignore All Changes

Conclusion
In this session, we have seen how to speed up the simulation by reducing the graphic load
while maintaining the same error detection.

VERICUT V6 Session 3 3

You might also like