Skip to main content
R
razmosis13-Aquamarine
13-Aquamarine
February 18, 2014
Solved

Integrating Vericut

  • February 18, 2014
  • 1 reply
  • 2458 views

Just tried to integrate vericut with Creo yesterday. When Vericut is launched from Creo, version 7.1.5 launches. I spoke with IT (new machine) and 7.1.5 has never been installed on the machine. When I run it independant of Creo, I run version 7.3.

Any thoughts on what's going on, or thoughts on whether running Vericut through Creo is any better than running it on its own?

Thanks,

Matt


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
Best answer by GabrielZaha

Matt,

Vericut 7.1 is included with Creo 2 distribution. It was installed when Creo was installed. This is typicaly called embeded-mode

The main disadvantage of running in embeded mode is that it only runs CL files. You can't verify the actual machine code.

On the other hand, embeded mode does not require to have the machine controller and geometry defined.

In our office every time we are running the standalone mode most of the time. The only machine where we check the programs on embeded mode is an old 3-axis machine.

If you search the knowledge-base there are few articles that are describing how to set-up Creo to start in standallone mode. Here is one of them: https://www.ptc.com/appserver/cs/view/solution.jsp?n=129496

I hope this will help you,

Gabriel Zaha

1 reply

G
GabrielZaha14-AlexandriteAnswer
14-Alexandrite
February 18, 2014

Matt,

Vericut 7.1 is included with Creo 2 distribution. It was installed when Creo was installed. This is typicaly called embeded-mode

The main disadvantage of running in embeded mode is that it only runs CL files. You can't verify the actual machine code.

On the other hand, embeded mode does not require to have the machine controller and geometry defined.

In our office every time we are running the standalone mode most of the time. The only machine where we check the programs on embeded mode is an old 3-axis machine.

If you search the knowledge-base there are few articles that are describing how to set-up Creo to start in standallone mode. Here is one of them: https://www.ptc.com/appserver/cs/view/solution.jsp?n=129496

I hope this will help you,

Gabriel Zaha

R
razmosis13-AquamarineAuthor
13-Aquamarine
February 18, 2014

Thanks Gabriel, it certainly is a big help! Even if you cannot use them together to verify code, the graphics are a lot better than Creo's default NC check. Is there any disadvantage in using it in that way, then opening Vericut to verify the code independantly?

Matt

G
GabrielZaha14-Alexandrite
14-Alexandrite
February 18, 2014

Personally I don't see any disadvantage in running Vericut independently.Setting up a simulation take a little longer. We have a library of templates and this is helping us to save a lot of time.

Beside checking for collisions and part gouging we also verify other things like the amount of stock left for hard finishing operations. Bottom line: for us running Vericut independently is advantageous.

Terms & ConditionsCookie settingsAccessibility statement