Optionally Measure Tools at Start overwriting

[jasonmrye]

I put this as a response for an older post that started with the same essential situation I find myself in, but I did not follow how to implement the answer. If the Answerer of that post gets back to me - cool. If y'all are able to help in any way - also cool. I'll provide any info that you need to help me with this, just let me know. The original question was asked by a user named "Jason" as well, but it's not me.

 I have a Haas vf2ss (new) with Next Gen control and am using that post processor when generating programs from Fusion. When I utilize Optionally Measure Tools at Start, my non-rotating length only tools do just fine (G65 P9023 A12 ...). However the diameter/length rotating tools that use A23 also put an "H" value into the tool offsets table. Tool 18 was probed for length and diameter manually before running the program then the Measure at Start was run again to catch up all the other tools as well. When the machine got to T18 in the sequence it overwrote the tool length from it's original measurement (3.0808") to the 2. that was next to the H in the line of code to measure it. It also happens on T11 (length/diameter rotating A23 H2.). That 2" height is what the Fusion Tool Library has listed as the tool's length - but why is it overwriting it in my machine when it's running the program? None of the other tools have offered to do this. 

Please HELP!

Thanks,

Jason Rye

[Tomek.G]

Hello @jasonmrye,

I already answered here:
https://forums.autodesk.com/t5/fusion-360-manufacture/optionally-measure-tools-at-start/m-p/11294387...

take a look and let us know.

[jasonmrye]

Thank you for answering again! I had not understood your original answer, but I think I do now. Just to make sure that I do though...So in order to utilize the Measure Tools at Start function, I will need to accurately input at least the approximate tool length into my tool library for the tools measuring both length and diameter? A small extra step that I'll happily do now that I know. If I'm wrong and not understanding it, let me know!

Thanks,

Jason Rye

[Tomek.G · Accepted solution]

Hi @jasonmrye,

The idea of this cycle is to set up a bunch of tools from scratch, therefore it completely ignores existing values in the tool table. 
There is a "tolerance": the measurement starts a little earlier than the declared tool length and tries to find a tool slightly shorter than the declared one. So the tool length must be approximately entered and fall within this tolerance area.