- Posts: 19306
- Thank you received: 0
Manual tool change + tool lengh touch off
Please Log in to join the conversation.
I reworked it to remove unneccessary code and parameters, I think the ini file is a better place to set parameters than gcode file.
Still Work in Progress, mostly for documentation, but I made some manual tool changes and everything goes fine.
I produces extensive output while it's WiP, one can remove PRINT to reduce verbosity.
I'm new in LinuxCNC, have some exeprience in gCode as I 3D print since several years now but had to RTFM again and again to understand some features.
Don't hesitate to make any remark.
Please Log in to join the conversation.
I can't get rid of huge backlash on my machine (mechanical issue), the opposite move naturally compensate this backlash and makes no difference (I guess) on a well calibrated machine.
Please Log in to join the conversation.
Please Log in to join the conversation.
it goes through all the motions; moves to position> asks for tool> checks tool height etc. all fine.
The problem is it isnt storing the offset in the tool table or showing in the bottom of axis. I can see the numbers are being written to the .var file but then it doesnt seem to do anything with it. The only way i can get it to update the offset is by manually pressing the tool touchoff button in the axis gui.
Im new to linux and linuxcnc and cnc in general so i know ive probably done (or not done) something dumb!
any help or direction in which to look would be appreciated.
edit to add relevent info from hal/ini etc.
in hal added-
 net probe-in => motion.probe-input
net probe-in <= nyx.0.in-11-not
loadusr -W hal_manualtoolchange
In postgui added-net tool-change iocontrol.0.tool-change => hal_manualtoolchange.change
net tool-changed iocontrol.0.tool-changed <= hal_manualtoolchange.changed
net tool-number iocontrol.0.tool-prep-number => hal_manualtoolchange.number
net tool-prepare-loopback iocontrol.0.tool-prepare => iocontrol.0.tool-prepared
in ini added-
SUBROUTINE_PATH = /home/russ/linuxcnc/nc_files
REMAP =M6 modalgroup=6 ngc=tool-change
REMAP = M600 modalgroup=6 ngc=tool-job-begin
TOOL_CHANGE_AT_G30 = 0
in tool-change.ngc I changed params to suit machine and nothing else.
Â
Please Log in to join the conversation.
it goes to the correct height if I manually input the correct offset into the tool table.
and it goes to the correct height if I disable the tool table.
Any ideas please? everything looks like it works as it should except the tool table isnt getting changed. (if that is how it should work??)
Ive done ok so far, I litterally started for the first with LCNC about 3 weeks ago and have manually set up the machine without using the configs wizards ( i cant because im using unsuported servos with an obscure controller) and have been trying to get this tool setter to work for the last 4 days (as in 8am to 6pm days) and it now has me stumped.
Please Log in to join the conversation.
After eg. T99 is used to touchoff X Y Z , and afterwards probed, it is reverenced with #<_ToolZRef> = #5063
All following probed tools getting offset from first tool with G43.1 Z[#<_ToolZ> - #<_ToolZRef>]
linuxcnc.org/docs/2.8/html/gcode/g-code.html#gcode:g43.1
That is why tooltable is not used for length and G43 is not needed in gcode. DIAM entrys should be done, if cuttercompensation used.
from tool-change:
( My sequence of Running; )
( 1. Use a T99, a .250" Rod, to touch off X, Y, and Z of WCS as modeled in CAM )
( 2. Manually input M600 ) or just enter #<_ToolDidFirst> = 0 in MDI
( 3. Manually call an M6 T99, tool will touch off on toolsetter and store tool height )
( 4. Load program and run, M6 in program will prompt tool change, after changing, tool will touch off and Z will adjust )
( 5. Run any and all code using the same desired Z height for the WCS as designed )
( 6. For new WCS repeat from Step #1 )
Please Log in to join the conversation.
I had just spent the last few hours trying to get gcode to update the tool table but ill just disable it and make sure I number my tools properly. now I can at least put this part to bed, now i need to start looking into a debounce feature since the toolsetter is re-triggering sometimes after detection.
Please Log in to join the conversation.
I don't need to probe tool lengths as my machine has repeatable tool holders. (What spindle are you using? Given the effort that you are going to in the rest of the router build I would be surprised if you were not using a tool-changing spindle)
Please Log in to join the conversation.
Please Log in to join the conversation.
