HI,
venom51 wrote:In the manual it states that the master tool must be measured offline to establish the touch plate position for tool length offset measurement.
I'll need to get specific re some terminology here...
When you say the "...touch plate..." I'll assume you mean the Tool Change Position Touch Plate.
and when you say "...establish the touch plate position..." I think you mean determining and teaching MSM the MCz level of the top of of the TCP TP.
Ok, given those assumptions, Yes MSM has to know the MCz level of the TCP TP before it can use the TCP TP To measure tool TLO values.
This requirement is true, completely independently of whether one is using master tool mode (and hence a master tool) or not.
venom51 wrote:Does that hold true if you are using the touch probe as the master tool and measure it each time you start a set up?
The MCz level of the TCP TP MUST be known before it can be used to measure
any tool's TLO. It doe not matter if the tool being measured is a Probe or a drill bit.
Separate two concepts and I think this will become clearer:
The TCP TP is used to measure physical tool lengths (PTLs). From physical tool lengths, A TLO value is computed and entered in the tool table (assuming you are using ATLO in the tool page options). The technique used to calculate a TLO, is dependent on other options. The option combinations are covered in the user manual.
For the case of Master tool mode = ON, then the TLOs are calculated as the difference between the master tool PTL and the PTl of the tool being measured.
venom51 wrote:...using the touch probe as the master tool and measure it each time you start a set up?
Setting the WC 0 point is comes AFTER the TLO is measured/calculated -
And the Calculated TLO value can not be correct if the MCZ level of the TCP TP is not correct.
venom51 wrote:
So the process would be as follows.
1. Install touch probe via non-repeatable tool holder.
OK, you are counting on the fact that the probe tool will ALWAYS be measured after it is mounted.
If the probe is the master, then this will also update the master tool PTL in the table.
venom51 wrote:
2. Measure and set the TLO for the probe via the table mounted touch plate.
OK - as long as the TCP TP MCZ level has been calibrated and it has not moved since the calibration.
venom51 wrote:
3. Set part zero via the mounted touch probe.
Yes, the WC 0 will be set correctly.
venom51 wrote:
4. Load program and run.
OK
venom51 wrote:
5. First tool is measured via the table mounted touch plate and it's offset set.
By "it's" I think you mean "the tool being mounted is measured and the TLO for the tool being mounted is set in the table".
This is correct.
venom51 wrote:
Will that result in a proper tool offset for any non-repeatable tool?
Yes. as long as the tool is measured as part of the tool change, the TLO will be udpated during the tool change. Thus if the tool is mounted in an NRH holder, it will be measured and be ok for TLO tool table entry.
What I do on my machine is follow the rule of 1) I always use ATLO option for all tool changes and thus all tool get measured when mounted as part of a tool change.
I never use "skip RH" - I waste a little time re-measureing tools in RH holders thaw way - but I"m not doing production runs where that matters to me.
I find it much easier to always measure each and every tool - then if I changed a RH holder and forgot that I did so, it does not bite me - as the tools always get measured and update each and every time they get mounted.
Finally, don't forget that completely "mounting" a tool is a multi step process:
a) GCode program issues T# M6 to mount a new tool
b) MSM goes to the TCP, and the human physically mounts the tool - the tool is not physically mounted, but not logically mounted from the view of the CNC control.
c) MSM sees the tool is physicially mounted and that ATLO is on, and so it measures the tool using the TCP TP
d) the TLO is calculated (mode dependent) and the TLO value is written to the tool table.
We now have the TLO value - But is has NOT been applied (activated) to the Tool!
e) now the gcode program has to do G43 H#
to actually tell mach to use the TLO value.
many people forget step e) ... or learn the hard way that their CAM program post processor for their cam program is not outputting the G43... and then things don't work.
and DO NOT do T3 M6 G43 H# as one line!
(See MSM release notes) There is a bad mach bug that bites you if these are all on one line!
Use two lines to avoid the mach bug.
T# M6
G43 H#
Dave