I hope this is not a stupid question
Do the end mill numbers in the tool table in MSM have to match up to the ones in my cad/cam package (fusion360)?
Stuart
Tool table
Re: Tool table
Hi,
Here' an overview of the general work flow interaction between a CAM package and a CNC control:
(Note that this approach is not specific to fusion 360 or Mach. )
In the cam package you usually define tools that the package then uses to generate tool paths for cutting a part from stock.
For example a 2" long drill or a 4" diameter face mill etc.
The tools the Cam package defines are identified by a tool number.
When the cam package creates the gcode that will run on a CNC control, the gcode includes command to mount the tool that is being used. This is typically a T<tool number> M6 line in the gcode.
When the CNC control runs the gcode, the control sees the M6 (tool change) command and the tool gets mounted (either by pausing to wait for the operator to say the tool has been mounted, or by getting that tool # from a Tool changer etc).
So the tool # used in the Cam program (fusion 360 in your example) is used to identify to the CNC control the physical tool to mount.
Now then there is another aspect of tool handling that needs to be done to make everything work: the tool table data.
Tool tables usually include a text description of the tool. This is what is shown to the operator when the tool needs to be mounted.
So T5M6 causes the text description for tool #5 from the table to be shown to the operator. If T5 is a drill is may say "2" long 0.25" diam drill".
The tool table data needs to be set up BEFORE then gcode program is run so that the tool table data matches the CAM program tools.
In addition to the text description, the tool table data needs to be set up so that the CNC control knows the physical dimensions of the tools. Typically this is the diameter of the tool and the "length" of the tool.
When the gcode program runs it will go to the tool table and get the tool dimension info for a tool from the tool table. it is rather important that this data match what the CAM program expects. If the cam program was created and is going to drill 1 1.5" deep hole using a 2" long drill tool, but the drill mounted is only 1" long, then the program will probably crash the tool holder into the stock when it tries to drill a 1.5" deep hole with a 1" long drill.
Note that the CNC control tool table usually has a "tool length offset" (TLO) value and not a "physical tool length" (PTL) value in the tool table. The two things are not the same. TLO values are established by touching off tools etc. They are used so that the CAM side can create a program without having to know the exact PTL of a tool at the time the CAM program is generated. Otherwise the Cam program would need to be recreated every time a tool it was going to be used was changed (e.g. replacing old toll with a new tool).
These are basic CNC control concepts and getting familiar with them will be of help as you learn more about running CNC machines.
There is info re TLO setting in the MSM Manual, and Peter SMIDs book "CNC programming handbook" has good explanations of these topics.
Dave
Here' an overview of the general work flow interaction between a CAM package and a CNC control:
(Note that this approach is not specific to fusion 360 or Mach. )
In the cam package you usually define tools that the package then uses to generate tool paths for cutting a part from stock.
For example a 2" long drill or a 4" diameter face mill etc.
The tools the Cam package defines are identified by a tool number.
When the cam package creates the gcode that will run on a CNC control, the gcode includes command to mount the tool that is being used. This is typically a T<tool number> M6 line in the gcode.
When the CNC control runs the gcode, the control sees the M6 (tool change) command and the tool gets mounted (either by pausing to wait for the operator to say the tool has been mounted, or by getting that tool # from a Tool changer etc).
So the tool # used in the Cam program (fusion 360 in your example) is used to identify to the CNC control the physical tool to mount.
Now then there is another aspect of tool handling that needs to be done to make everything work: the tool table data.
Tool tables usually include a text description of the tool. This is what is shown to the operator when the tool needs to be mounted.
So T5M6 causes the text description for tool #5 from the table to be shown to the operator. If T5 is a drill is may say "2" long 0.25" diam drill".
The tool table data needs to be set up BEFORE then gcode program is run so that the tool table data matches the CAM program tools.
In addition to the text description, the tool table data needs to be set up so that the CNC control knows the physical dimensions of the tools. Typically this is the diameter of the tool and the "length" of the tool.
When the gcode program runs it will go to the tool table and get the tool dimension info for a tool from the tool table. it is rather important that this data match what the CAM program expects. If the cam program was created and is going to drill 1 1.5" deep hole using a 2" long drill tool, but the drill mounted is only 1" long, then the program will probably crash the tool holder into the stock when it tries to drill a 1.5" deep hole with a 1" long drill.
Note that the CNC control tool table usually has a "tool length offset" (TLO) value and not a "physical tool length" (PTL) value in the tool table. The two things are not the same. TLO values are established by touching off tools etc. They are used so that the CAM side can create a program without having to know the exact PTL of a tool at the time the CAM program is generated. Otherwise the Cam program would need to be recreated every time a tool it was going to be used was changed (e.g. replacing old toll with a new tool).
These are basic CNC control concepts and getting familiar with them will be of help as you learn more about running CNC machines.
There is info re TLO setting in the MSM Manual, and Peter SMIDs book "CNC programming handbook" has good explanations of these topics.
Dave
Productivity Software for Personal CNC Machinists
http://www.CalypsoVentures.com
http://www.CalypsoVentures.com
Re: Tool table
Thank you Dave for the prompt reply
Looks like I need to set up both so they agree with each other , I have been using the setup report ( f360) to keep track of the tool changes , now you have explained it ,it is the best way to avoid I D Ten T errors
BTW I am getting on well with MSM now I have stopped over thinking things
Stuart
Looks like I need to set up both so they agree with each other , I have been using the setup report ( f360) to keep track of the tool changes , now you have explained it ,it is the best way to avoid I D Ten T errors
BTW I am getting on well with MSM now I have stopped over thinking things
Stuart
Re: Tool table
Dave
Thanks for th reply
Got it sorted somewhat but I have ordered the book you suggested
Stuart
Thanks for th reply
Got it sorted somewhat but I have ordered the book you suggested
Stuart