Good idea?? Vericut compare cutr def in .tls 2 apt Cutter

DaveF · 2005-12-08 01:51:20

I would like to see Vericut compare the cutter def in the vericut.tls file to the Cutter definition in the aptsource / or / g-code

The numbers are allready there.

This is the next disaster, yet to come.

There is no link from the CAM system to the Vericut.tls.

you can select change tool by :

tool number
vericut-TC
tool name
list
file name

The fear is with a Vericut.tls, or master Catalogue, etc., that you can make a mistake and issue a wrong LOADTL , LOAD/TOOL command

Thereby, you load tool 2, instead of tool 3, and process Vericut with the wrong tool.

Since Vericut can read any of these cutter definitions, in the future, it could compare and return an error, if the tool defined int the Vericut.tls was 1.000, but the cutter statement ins the aptsource said CUTTER/2, .125, 4

That would be for aptsource.

For g-code, we output a message at the cutter statement

(PP >REST: 9015 GAGELEN: 7.000 DIA=.400 COR=.200)
(PP >TOOL#15 LENGTH= .2 NO SIDE ANGLE)

Perhaps that could slerp up those numbers, populate a table, if there was some way to compare to the actual values of the vericut.tls cutters.

any thoughts?

Dave

Volkov · 2005-12-08 10:50:40

You can compare actual tool parameters with ones defined in APT:
1. Define your postprocessor to output params as comment as you described above -
for example, for tool diameter(PP>DIA=.400)
2. Define word "(PP>DIA=" in VERICUT Word Format menu.
3. Define to assign variable on detecting word "(PP>DIA=" in Word/Address menu.
4. Compare the variable defined with current tool diameter on tool change event. (Macro for detecting dynamic parameters is SetDynamicVars)

DaveF · 2005-12-08 15:06:24

Thanks Igor

I have not used that macro yet.

It looks very powerful at 1st glance in the help file.

I see the following listed.

CurToolDiam #?The current tool diameter will be set in the specified variable number. Example: Override Text=CurToolDiam 7000

I didn?t see a radius or height.

Are there other variables that are not listed in the help file????

My guess is that Vericut has a library of variables it constantly tracks, just like a postprocessor does.

8)

SergeV · 2005-12-08 18:34:58

These system variables must be set in the control. Some of the controls have many of them already configured. The best example is the Fanuc controls. Open Library fan15m.ctl,
Setup > Control > Adv. Options; Events tab

You can choose which variable to populate with the information you need.

Serge

DaveF · 2005-12-08 19:12:52

Thanks serge

I see in the help:

Override Text=CurToolDiam 7000

Are there macros for cutter fillet radii, length, and angle ??

:?

SergeV · 2005-12-08 20:50:50

All current the functionalities are listed in Help. The goal is to mimic the information available on the machine control.

the tool information available is:

Cutter Compensation value
Current Tool Number
Current Tool Diameter
Current Tool offsets
Current tool type (milling or turning)

DaveF · 2005-12-09 02:07:48

Thanks Serge.

I am trying to back door this cutter check i desire, with "the Vericut I have today"

I put in an enhancement request with my local A.E. today, and will let CGTech decide proper implementation if any.

you can select cutter by definition, and Vericut knows what it is.

you can select cutter by vericut.tls and Vericut knows what it is.

I suggest Vericut look at both, and compare.

so the question for the forum users is, is this something you think Vericut should do with a check box??

If that is not possible, adding current tool fillet and current tool length macros could be added in future releases.

The good news is, It looks like I can pursue Diameter only checking today, without checking the rad, and length, and angle, using the method Igor described.

I don?t always use Vericut the way it is intended to be used, but I try to get the job done.

VERICUT Users' Forum

#1 2005-12-08 01:51:20

Good idea?? Vericut compare cutr def in .tls 2 apt Cutter

#2 2005-12-08 10:50:40

Re: Good idea?? Vericut compare cutr def in .tls 2 apt Cutter

#3 2005-12-08 15:06:24

Re: Good idea?? Vericut compare cutr def in .tls 2 apt Cutter

#4 2005-12-08 18:34:58

Re: Good idea?? Vericut compare cutr def in .tls 2 apt Cutter

#5 2005-12-08 19:12:52

Re: Good idea?? Vericut compare cutr def in .tls 2 apt Cutter

#6 2005-12-08 20:50:50

Re: Good idea?? Vericut compare cutr def in .tls 2 apt Cutter

#7 2005-12-09 02:07:48

Re: Good idea?? Vericut compare cutr def in .tls 2 apt Cutter

Board footer