HeadTable 5-axis tnc530 Tool Lenght Problem *Deckel-Maho CNC )

[ngmajid]

Hi

I am working on a Table Head (XYZ Head=B  Table C) 5axis (DMG - Deckel) VMC Machine. (The picture is attached.
The Machine's forth Axis is C and Fifth Axis is B.
I use one Fixed Tool and Define it by "Tool CALL 0 Z S700"
But in 5 Axis operations. The Tool position is in wrong  place.

My questions:
Can I use Zero tool lenght, for this type of machine?


If yes, I'll need Define it in "HMI Tool Manager"  or   by "Tool Def " in PostProcessor?
Thanks

[mega]

I don't see an attachment..

[neurosis]

I don't see an attachment..

I don't think they're a high enough level to use attachments.  They'd have to post a photo using imgur. 

[gcode]

This question is also posted on eMC with pictures

[mkd]

Can I use Zero tool lenght, for this type of machine?

How sharp is your spindle?

[mkd]

The Z in the tool call is smilar to g43/g17 on fanuc, so that just activates the TLO along the tool axis.
 The number "0" is just that; the tool number, not the length.
 If you want to tweak the length or radius comp from the program, that would be also done in a tool call line, only using DLxx.xxx and DRxx.xxxx. (good luck doing that to you fanook fanboys)

[mkd]

#10004 =0 (change this 0 value to adjust z height)

is that an absolute or increment value?
either way, 90% chance your average shop guy f's that up frequently. IMNSHO.

[CNCAppsJames]

If you want to tweak the length or radius comp from the program, that would be also done in a tool call line, only using DLxx.xxx and DRxx.xxxx. (good luck doing that to you fanook fanboys)

G10G91L11P1R.0001 (Change TLO wear by .0001 from whatever it is now)
G10G91L13P1R-.0001 (Change TR/D wear comp by -.0001 from whatever it is now)

[CNCAppsJames]

Orrrrrrrrr
[#_TOFS[2]]= Length Wear for the currently active tool
[#_TOFS[4]]= Radius/Diameter Wear for the currently active tool





Bring it...

[CNCAppsJames]

Orrrrrrrrrrr
[#_OFSHW[1]] for a specific tool's LW (shown for T1)
[#_OFSDW[1]] for a specific tool's DW (shown for T1)
[#_OFSRW[1]] for a specific tool's RW (shown for T1)

[CNCAppsJames]

...good luck doing that to you fanook fanboys)

You REALLY should rethink your strategery when talking shit on FANUC controls. IOW know the room.

You shoudl SERIOUSLY stop listening to your coworkers that are feeding you that Eurotrash control is king Kool-Aid. They are going off ANCIENT intel.

[CNCAppsJames]

Oh and I almost forgot... if I'm on a Matsuura;

G10G91L11P#517R.0001 (Change current tool in the spindle's TLO wear by .0001 from whatever it is now)
G10G91L13P#517R-.0001 (Change current tool in the spindle's TR/D wear comp by -.0001 from whatever it is now)

[#_OFSHW[#517]] for a specific tool's LW (shown for T1)
[#_OFSDW[ #517 ]] for a specific tool's DW (shown for T1)
[#_OFSRW[ #517 ]] for a specific tool's RW (shown for T1)

[gcode]

While we're talking smack,
I loves me some Okuma OSP 200 and ....
We're getting a 2nd Okuma MU1000 5axis HBM this year.
It's got an OSP300 and some really cool looking optional features
It's got one for use with big insert endmills.
The laser presetter measures the runout and the control adjusts the feed rate to keep the fpt constant
That's pretty freaking cool

[CNCAppsJames]

Honestly I do love it when people talk smack about FANUC controls. Every time someone says "FANUC cant" I either reinforce a feature/function I already know, or I get a good reason to learn something new by digging even deeper into the manuals.

So please do keep it up. You all are making me even better at my job and I'm grateful.  

[mkd]

Orrrrrrrrrrr
[#_OFSHW[1]] for a specific tool's LW (shown for T1)
[#_OFSDW[1]] for a specific tool's DW (shown for T1)
[#_OFSRW[1]] for a specific tool's RW (shown for T1)

Great stuff! The best part of trolling when CNC Apps guy is around is the knowledge bombs that get dropped.
Well aware of the G10 tricks, totally lost with the rest of that code.
[#_OFSDW[1]] yadda yadda. No clue.
After you alter all those you need to issue a new g43 and and or g41, right? What happens when you want to abort in the middle and restart the program, at the top or in the middle? Good luck with that...Read on...

Heidenhain has length and radius plus tool table values for wear (DL and DR). There is a syswrite command to alter those from a program and then you can try and remember what they were and put them back later in the program, like a fanuc.
The thing that fanuc CAN'T do is to have live "prog" wear comps independent of table values.
So you want to tweak on a particular program and tune all the comps for a job and comp for shitty programmer's failure to comp proper stock allowance or tolerance? Heidy got you covered.
TOOL CALL DL-.001
That's it. Done.
And when you're done comping that finish pass:
TOOl CALL DL.0
This architecture is built into the control so you can monitor the table and program comps in your normal run screen.
Best part is comping in the program doesn't alter the tool table for the next guy/next part.
I guess you could write a macro to comp a value from a fanuc program but not quite the same level of user friendliness.