Unigraphics to Vericut interface

rklutts · 2004-11-11 18:35:22

Anyone getting the UG to Vericut interface to work at all? How do you get UG to pass cutter description to Vericut?

Thanks

RDawson · 2004-11-11 20:42:50

If I understand your question correctly:

Sometime around V18 UG made a change to how the Vericut interface works. We had to purchase a seperate license to get it to work. Once we did this we had to open UG by going to the Vericut folder>Windows>Commands>ugv_(your version #).bat file. It's been working this way ever since. I imagine there is a way to do it outside UG but, it would be time consuming.

rklutts · 2004-11-11 23:07:09

We are on HP Unix so our unix tech is looking into getting that part working. Do you pass cutter info along by any special statements in the g-code? How is that handled? With several people we are trying to move away from setting up tools in tool manager.

Thanks
Ron

RDawson wrote:

If I understand your question correctly:
Sometime around V18 UG made a change to how the Vericut interface works. We had to purchase a seperate license to get it to work. Once we did this we had to open UG by going to the Vericut folder>Windows>Commands>ugv_(your version #).bat file. It's been working this way ever since. I imagine there is a way to do it outside UG but, it would be time consuming.

RDawson · 2004-11-12 16:32:55

rklutts wrote:

We are on HP Unix so our unix tech is looking into getting that part working. Do you pass cutter info along by any special statements in the g-code? How is that handled? With several people we are trying to move away from setting up tools in tool manager.

We've always used the CLS file to define all the tools. I haven't used Unix since V16, so I'm unsure if anything has changed since then.

Are you using the posted NC code to run through Vericut? If so, you may want to try the CLS files if you have them.

ElyW · 2004-11-12 17:02:13

Ron,

The UG to VERICUT interface runs the same on UNIX as it does on Windows. The interface will automatically create a VERICUT Tool Library based on the tools defined in your machining operation within UG, regardless if you run CLS or G-code data. This way you define the cutter once in UG and they will be available for you in VERICUT.

rklutts · 2004-11-12 17:29:26

Ely,

We have been trying for 6 months and we still haven't gotten the UG to Vericut interface to work correctly. Maybe some of my issues with defining cutters will go away when that gets working.

Ron

ElyW wrote:

Ron,
The UG to VERICUT interface runs the same on UNIX as it does on Windows.

ElyW · 2004-11-15 17:26:50

:idea:
Don,

One other thought regarding the UG interface on UNIX, you want to make sure that you are running VERICUT V5.4.1 or higher with ugv_v20 library That is because the ugv_v20 library released with/after VERICUT 5.4.1 is a 64 bit library that works with UG-NX(2) on HP.

Previous UGV libraries are 32 bit libraries that do not work with UG-NX and UG-NX2.

GeneG · 2005-11-10 23:30:53

Mr. Klutts, according to our Tech. call records, upgrading to 5.4.4 enabled you to run the UG to VERICUT interface successfully on HP and Windows computers. This note was just to let others know that the advice about upgrading to a recent version of VERICUT solved this problem. --Gene

VERICUT Users' Forum

#1 2004-11-11 18:35:22

Unigraphics to Vericut interface

#2 2004-11-11 20:42:50

Re: Unigraphics to Vericut interface

#3 2004-11-11 23:07:09

Re: Unigraphics to Vericut interface

#4 2004-11-12 16:32:55

Re: Unigraphics to Vericut interface

#5 2004-11-12 17:02:13

Re: Unigraphics to Vericut interface

#6 2004-11-12 17:29:26

Re: Unigraphics to Vericut interface

#7 2004-11-15 17:26:50

Re: Unigraphics to Vericut interface

#8 2005-11-10 23:30:53

Re: Unigraphics to Vericut interface

Board footer