Tool offset patch

I think it should go here

Crhis know the limitation of my English will try my best.

<Tool Editor>

4 = geometry tool = -80.01
10004 = wear tool = 0.6

(I do not use g92 or g54)

1) proceed to "compensate" my tool in Z axis.

2) I press the key "tool-set", digit 0

3) The value of Z in absolute position is 0.6 (take the offset value (10004))

4) delete the offset value (10004) placed him 0, I press apply, reload. back to "compensate"

5) I press key "tool-set" digit 0, and the value returns to 0.6 (the value of wear (10004) is again 0.6)

6) repeat the operation and got it.

7) the third or fourth attempt takes the value 0 at absolute and the wear (10004).

8) when I try to change the tool, get the message "request not found tool 10004 in tool table".

9) I go to the tool-editor, all erased.


I think that happens when you go to "Compensate" a tool that has already been compensated before.

Chris you are right, if you clear the table tool, 1000n always says not found. never says tool-n is not, so you just put t1 without wear. but when it compensates the value set to "n" not "1000n" I think there is the conflict.


Thanks,


Jorge

definitely T1000n holds the tool geometry and nominal offsets.
Tn holds the wear offsets.

I'm not sure why this is. I would have thought the other way would make sense.
also then the tool request dialog would ask for tn rather then t1000n.

It's an easy fix but I don't want to do it if there is a real reason not too.

As for the erasing toolfile I haven't got it to erase yet - but I'm using a slightly different patch - I will try the original patch.

Thanks for information Jorge.

Chris M

Why is T10004 not wear offset 100 and geometry 04?
I thought that the patch only covered tools up to 99?

T10004 is not a valid tool number to call ( there can not be a tool number above 99 in Fancuc lathe code as I understand it)

but it is a valid entry in the toolfile - its the wear offset #4

wear offsets are given a 10000 offset to differentiate them from geometry offsets.


Also the first two numbers are geometry and nominal offsets, the last two are wear offsets (opposite of what you quoted)

Sorry About that Chris I thought I attached it.

Here is a copy again.

I don't know what the problem is. I will have to go into he office and attach it. The pc at the machine wont do it for some reason.

_______________

I just remembered, it wont attach a .tbl file.

Ok one thing I'm seeing is everyone thinks tool entry 10000n is for wear offsets.

It is _not_.

It is for geometry offsets. (the patch is very clear about this)

As long as you never enter a toolsetting it wouldn't matter.
But the toolsetting button overwrites the T10000n entry not the Tn entry.
Thats an important difference.

As the patch stands:
geo offsets are entry T10000n
wear offsets are entry Tn

I personally think this is wrong too. But I didn't write the patch so i don't know why that was done that way.
I am trying to find out why on the maillist.

Chris M

You need separate lines for wear offset and geometry offset because the wear offset does not have to be the same number as the tool number.

T101 and T102 are perfectly valid tool numbers in a program (same physical tool different offsets)

Chris M

Well need is too strong a word. but it would be easily confusing the other way.

Hello Chris,

I have been following the thread on the developers mailing list, and realized that I might have been mis-leading on this all along. Sorry for any inconvenience.

A few things I am sure of on our end,

1. The first two digits of the tool call is the tool geometry info on our other machines, for the most part also refered to as "Fixed Offsets".
2. All of the machines in our shop that have other commercial controls on them, all have 2 different databases or tables, Fixed offsets, and Wear offsets. So as far as I can tell when the tool call is made, the first two digits gather info from the Fixed offset file, and the second two digits gather info from the Wear Offset file. Once the operators have all of there tools touched off they vary rarely reference the fixed tool data, due to using the G92 command they only need to touch off 1 tool on every new part, and everything else follows.

Thanks

Rick

My two cents
The Cincinnati Milacron Way:

Call a Tool T0800 for example Would be tool 8 with no wear offset but it would read the Geometry offset or the Fixed offset is what Milacron called it. When I call T0808 it would call the wear offset into the program. Milacron used two Offset tables Fixed Offsets and Assignable Offsets these are Geometry and wear respectively. This make it possible to call and use the tool with no wear offset or call and use the tool with any assignable offset you so chose for that operation, example T0810 wich would be Tool 8 with the geometry off set entered in the tool 8 fixed offset tool table and with wear offset 10 as entered in the assignable table.

I hope this can help resolve.
I have the link of the book, but not if it was good place here.

if there is no problem in placing the link, let me know.




Jorge Viloria