|
|
XoomSpeed Post processor for Fusion 360 Feb '23
update
Make a donation
The following is a list of all the modifications included
in the Feb '23 release. To download this version, right click
this link and select 'Save Target As...'
- Delay after flood cooling on to allow pump
to get up to speed.
In the post-processor options, look in the Coolant group for the
option named Delay after turning on flood coolant (s). If
this is set to a non-zero value, then a delay is added after turning on
flood coolant to allow the coolant pump to start up.
This is active for standard cooling setups only, ie not the Tormach
SmartCool or the XoomSpeed coolant modules.
- Tapping with chip breaking.
For drilling operations, Fusion 360 now has a cycle type option named
Tapping with chip breaking. This version of the poist-processor
implements this option using LinuxCNC's
G33.1 command. This code implements a full retract after every
peck, hence Fusion's Chip break distance and Accumulated pecks
values aren't used. All of the other parameters for this option are
fully supported on all machine that support rigid tapping (MX mills).
- Add x, y, z coords to inspection probing
descriptions.
When using the inspection probing feature,
the description part of each probing op is used as a title in the final
inspection report. If you use a CAM pattern to perform multiple
inspection operations on the same feature, it can be useful to have the
nominal x, y or z coordinates included in that description to
differentiate between different instances in the pattern.
For example, if you wish to check the width of a slot at 10 locations
along its length, then a CAM pattern of a single probe operation can do
this, but in the final report, up til now, the description would read
'Slot width'.
With this release, if you enter the probe operation's description as
Slot width @ X={x}
The the {x} character sequence will be replaced by the x coordinate of
that probe operation when the final report is printed, so the report will
read
Slot width @ X=1.7
{y} and {z} are substituted in the same way.
- Output g-code subroutines
In the post processor options section G-code generation there is an
option named Use sub programs.
If you check this option, then the program will be output as a sequence of
g-code subroutines, 1 for each CAM operation. The top of the program
then consists simply of a sequence of calls to those subroutines.
Each call includes the CAM operation's name as a comment.
This is intended to make it easier to restart a program at any CAM
operation.
Note. In order for this to work, every operation subroutine has to
start by selecting the correct tool, WCS, spindle direction and speed and
coolant mode. In the current version of PathPilot, the coolant mode
selection in particular may introduce a delay compared to code generated
without this option.
- WCS probing speeds.
Fusion's WCS probing CAM operations now all have additional feed rates
named Link feed rate and Measure feed rate. To avoid
introducing incompatabilities with exiting programs, the post-processor
defaults to ignoring these values. However, in the Integrated
probing post-processor parameter section there are now options named
CAM Op 'Link feed rate' overrides 'Fast probing speed' and CAM
Op 'Measure feed rate' overrides 'Slow probing speed'. As you
might expect, setting these options means that the new speeds from the CAM
ops replace the ones specified in post-processor properties.
- Block delete support
If you right click any CAM operation in Fusion, there's an option to mark
that operation as Optional. Code for operations marked in
this way is now output with a leading '/' character at the start of every
line. PathPilot starts with the block delete function turned on, so
these lines will be skipped and there's no way from the PathPilot UI to
turn block delete on and off. If you want to use this function, see
the page on our block delete
plugin.
- Block delete for Manual NC
Due to the way Fusion handles Manual NC CAM ops, it's not currently
possible for the post-processor to detect the optional flag being set on
ManualNCs. In order to achieve block delete switching of tool
setting and checking operations - a very good use case for block delete -
there's an option in the Toolsetter section of the post-processor
options to make all tool setting (G37) or all tool checking (G37 Px)
operations optional. If you turn on either of these options, then
all appropriate lines of g-code will be output with the block delete '/'
character.
- Coolant modes.
Fusion has always supported more coolant modes than the post-processors
and what can be done is strongly dependant on the hardware fitted.
I've attempted to make it clearer what the different hardware setups can
do and how the Fusion coolant modes are mapped to the available hardware.
The main step is to introduce a new setting in the post-processor
Coolant section. The property is named Coolant equipment.
The different available settings and the affect they have are listed in
the following table.
| Coolant equipment |
Fusion coolant mode |
Action |
| Standard |
Mist or flood |
M8 |
| |
Any other |
M8 but issue warning |
| |
|
|
| Separate flood and mist |
Mist |
M7 |
| |
Flood |
M8 |
| |
Any other |
M8 but issue warning |
| |
|
|
| SmartCool |
Mist or Air |
M7 + different scan modes based on
operation type |
| |
Flood+Mist |
M8 but issue warning due to no
multiCool + different scan modes based on operation type |
| |
Flood |
M8 + different scan modes based on
operation type |
| |
Any other |
M8 but issue warning + different
scan modes based on operation type |
| |
|
|
| SmartCool + MultiCool |
Mist or air |
M7 + different scan modes based on
operation type |
| |
Flood + mist |
M8 + Q code to specify air blast
time + different scan modes based on operation type |
| |
Flood |
M8 + different scan modes based on
operation type |
| |
Any other |
M8 but issue warning + different
scan modes based on operation type |
| |
|
|
| XoomSpeed coolant module |
Mist |
M7. Ouput settings and duty
cycle programmed via coolant module setup. Scan modes set per
tool. |
| |
Air |
M7P1. Ouput settings and duty
cycle programmed via coolant module setup. Scan modes set per
tool. |
| |
Flood |
M8. Ouput settings and duty
cycle programmed via coolant module setup. Scan modes set per
tool. |
| |
Flood + mist |
M7P2. Ouput settings and duty
cycle programmed via coolant module setup. Scan modes set per
tool. |
| |
Any other |
M8 but issue warning. Ouput
settings and duty cycle programmed via coolant module setup.
Scan modes set per tool, also in coolant module. |
Home
This site was last updated
03/27/23
|
