VERICUT Users' Forum

BillH

VERICUT Specialist

From: Irvine, CA

Registered: 2004-10-08

Posts: 146

Website

May lose collision data when updating files to 6.x

Problem:
Opening a pre-6.0 project or user file in 6.x, and not saving the machine file may cause a loss of some collision table rows.

Solution:
Be sure you save the machine file. The software dings you when you exit or open another project, that the file was not saved. But doesn't tell you the consequences of not saving it.

Details:
VERICUT 6.0 (and later) stores project-specific collision pairs in the project and machine-specific collision pairs in the machine. Previously (5.4 and earlier) the collision table was saved only in the user file. If the machine file is not saved, then the machine-specific collision pairs will be lost, only the project-specific collsion pairs will be saved.

Software change:
VERICUT 6.1.3 (and later) will display a warning message in the logger when a pre-6.0 user file is opened, warning to be sure to save the machine. And the software will prompt to save the machine when exiting or opening another project, as usual.

If the user ignores both these warnings and does not save the machine, then: an additional pop-up notice will display when a 6.0 (or later) project is opened, and that project references a pre-6.0 machine (a machine that has no collision information). The notice will warn about missing collision information.

The same is true for axis limit data, but the consequences on the shop floor are not as serious.