Tool OFFSET MISMATCH Problem <SOLVED>

[Muzzer]

Bear in mind that the PP continues to be evolved (by Autodesk presumably), so you risk missing out on critical updates if you stick with one version for all time. Have a look at the revision history and release notes from time to time to understand what has been changed. You can expand the history by clicking on "previous versions".
https://cam.autodesk.com/hsmposts?p=centroid

I doubt this problem is an issue with the PP and I wouldn't expect the answer to lie in editing your own PP. There are many users of this PP and it shares much of its DNA with dozens of other PPs, so any fundamental issue like this would have been identified and rectified long ago. Instead, I would check the settings (I would experiment with the settings in the tool library using a very simple operation involving a tool change). I'll see if I can point to what I was talking about earlier, although I'm unlikely to be able to do that today / for a while.

[lavrgs]

Since I'm working on refining toolpaths, posting one at a time worked. I may have found that putting the post in the local library allows changes that were not previously available. I'll test that theory..
Thanks for the link to the Autodesk post. I will compare the updated Autodesk version to what I was using. The Swissi post does seem to allow unchecking the tool preload and takes care of the "Tool Problem" I'm sure the Autodesk version can be changed because this problem was discussed on their forum - I just didn't find the path to make the correction by unchecking tool pre-load.

I'm now playing with Fusion at home I can see that I need to load "my machine" to the cloud so it's available. Maybe Autodesk will create My Tree J325 in their Machine Library...9-)

Thanks to all who contributed to my on going education

Bill

[slodat]

Check the post processor tab in your tool library..

[tblough]

Back to your original problem. How exactly did the program not work? Was the only problem that it stopped to insert tool 4 but still showed offset H8?

That would not have caused a problem because after the tool change there were no moves in Z until after the height offset was changed to H4. The program would have run fine.

[lavrgs]

So the proper offset would have eventually caught up? I was nervous/ puzzled watching the tool move above the part while showing the wrong offset. When you’re running an 0.0312 tool it doesn’t take much to make me nervous

[tblough]

Code: Select all

N81215 T4 M6
N81220 T13
N81225 S2500 M3
N81230 G54
N81240 G0 X-0.1415 Y0.1305
N81245 G43 Z0.62 H4
N81250 Z0.2

As you can see above, there are no Z moves until after the H4 is enabled. This same thing happened earlier in the program when you changed to tool 8. H13 was still active after that tool change until a few lines later when H8 was activated.

Code: Select all

(Adaptive1)
N135 M1
N140 T8 M6
N145 T4
N150 S3000 M3
N155 G54
N160 M8
N170 G0 X-1.5123 Y-1.0446
N175 G43 Z0.62 H8
N180 Z0.22