i'm working on my mill toolchanger. i was thinking of using a component for probing tool length , rather than from gcode macros or remapping
looking at auto toolsetting from the toolchanger carousel , and my thought was to be able to probe each tool when the carousel is loaded and optionally as it came into use when running gcode and issuing an M6T3 for example . and store it's length in the tooltable for next time it's used etc for example as the tool was picked , it could query if the tool had been measured or not by a flag in the tooltable , if not it could then do a tool setting move to the probe plate .. reset it's tool length in the table and then return to gcode program , this would also be the case if for example a tool had snapped and been replaced during running , the tool would then need to be reset . having a panel in axis showing the tools and be able to select say tool6 to be selected for setting tool length next time it is used , seems a good way to acheive this the problem i see is if this was done in the middle of running gcode , and a toolchange is commanded i.e M6T6 , the state or position in gcode cannot be saved to be able to return to after a tool probe is done , if done in a component . i think looking at Michaels remapping M6 toolchange example this can be achieved , although looking at storing each individual tool information back to the tool table may need some thought , or at least for me ! .... embedding this within the codebase seems right, which in turn keeps the user gcode clean and reusable . anyone have any better ideas , or am i looking at this totaly wrong ! Dave ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
