- Posts: 14
- Thank you received: 0
Manual tool change + tool lengh touch off
orangecat wrote:
hancock wrote: I looked into my gcode and i found that after every tool change
Code:N60 G43 Z15. H1
That's the problem. G43 H1 will reset the tool offset that the touch-off set, to be the tool offset stored in the tool table for tool 1.
By removing G43 H1, all should work well. I don't know if you want to move to Z15 at this point. Maybe not, in which case the entire line can be removed.
Thanks for all the help! It seems that it was indeed the problem. I removed the H and Z values before but the G43 was constantly resetting the offset. Took some time to figure out how to remove the code from the post-processor but know I can work again :woohoo:
And if anyone has the same problem, this is the line I removed from the "linuxcnc.cps"-post-processor:
Thanks again & great community!
Please Log in to join the conversation.
For reference, because it's lost in the middle of this thread, the link to the manual tool change code can be found here:
forum.linuxcnc.org/forum/10-advanced-con...h-off?start=30#48235
Please Log in to join the conversation.
It's me again and I stumbled upon another problem with the routine.
When I use a 1mm bit again during a file, I get the error that the "Move in line 120 would hit the positive limit of Joint 2".
The line 120 in the file "too-change.ngc" is:
G53 G1 F[#<_TravelFeed>] Z[#5183 - #<_ToolZLast> + #<_ToolZ>] ( return to where we were in Z, ajusting for tool length change )
As far as I understand it, the problem is that the newly adjusted hight of the Z-axis is somehow colliding with my limits but I have now idea why because when I run the program again, the Z-hight is correctly adjusted and I get no error.
I don't want to mess around in that part of the code but it would be great if I could get it to work properly because right now I have to remove all line pre the current step from my Gcode. The offset is still correct.
Thanks for any suggestions!
Cheers,
Hancock
Please Log in to join the conversation.
N60 G43 Z15. H1
really should have been replaced with:
N60 Z15.
that would (typically) move the tool above the work before a tool change so that a shorter tool wouldn't give a limit error when moving back.
Please Log in to join the conversation.
orangecat wrote: that code from earlier:
N60 G43 Z15. H1
really should have been replaced with:N60 Z15.
that would (typically) move the tool above the work before a tool change so that a shorter tool wouldn't give a limit error when moving back.
I replaced the code in my post-processor so I don't have the "G43" and "H1" in my gcode anymore. But it still happens...
For example this is my code
Thanks a lot for your help and routine - other than that, it works like a charm!!
Please Log in to join the conversation.
It should be safe to remove this G53 Z0. as it appears to be a part of the tool change routine and there's no X,Y movement that follows.
Alternatively you could just remove the offending line:
from tool-change.ngc .G53 G1 F[#<_TravelFeed>] Z[#5183 - #<_ToolZLast> + #<_ToolZ>] ( return to where we were in Z, adjusting for tool length change )
Please Log in to join the conversation.
Please Log in to join the conversation.
But it [was] only a guess [EDIT: and it was WRONG. Read on.]. Can you comment whether it's true or not? And if true, if an adjustment might be made to accommodate the different approach?
Thank you.
(I have to separate passes because the immensity of them put together is too much for the memory.)
Please Log in to join the conversation.
send M600 command
load first file which should contain 1 or more M6 commands.
run it.
load next file which may contain 0 or more M6 commands.
run it.
repeat loading next files and running them until job is complete.
unless you issue another M600 command to indicate start of job, all following files are considered to be part of the same job and may contain M6 commands.
Please Log in to join the conversation.
Thank you. It is now transparent, even to this blockhead.
(And it is going to change my life...)
EDIT: It changed my life all right. :S It is Aug. 18. It was only two weeks ago that I got it working, preparatory to doing the first real job on a new machine. However, the rest of the preparations were equally intense, causing me to FORGET ALL ABOUT HAVING SET THIS UP! This is my Keystone-Kops account of chasing my tail trying to figure out WHY my machine seems possessed and acting on its own--moving to a location that's NOT EVEN IN MY CODE! :blush: Turns out transparency is a double-edged sword. (My memory's never been the same since watching Memento...)
Please Log in to join the conversation.
