Fusion 360 post processing with the post processor from the sticky thread
- Deveraux
- Offline
- Junior Member
Less
More
- Posts: 38
- Thank you received: 8
18 Jan 2023 09:47 - 18 Jan 2023 09:54 #262328
by Deveraux
Fusion 360 post processing with the post processor from the sticky thread was created by Deveraux
Hi,
So i got my machine up and running i just imported the pp for Fusion360 from the sticky thread.
I want to start finetuning the settings for each Material i use.
As far as i understood the complete z axis stuff is handled by plasmaC except for Kerf width, the lead in lead out and compensation.
Is the feed rate setting from plasmac being used since my generated g code has " F#<_hal[plasmac.cut-feed-rate]> " ?
Does Fusion handle any other settings except of the tool dimensions and the compensation ?
Any help would be much appreciated.
Greetings
So i got my machine up and running i just imported the pp for Fusion360 from the sticky thread.
I want to start finetuning the settings for each Material i use.
As far as i understood the complete z axis stuff is handled by plasmaC except for Kerf width, the lead in lead out and compensation.
Is the feed rate setting from plasmac being used since my generated g code has " F#<_hal[plasmac.cut-feed-rate]> " ?
Does Fusion handle any other settings except of the tool dimensions and the compensation ?
Any help would be much appreciated.
Greetings
Last edit: 18 Jan 2023 09:54 by Deveraux.
Please Log in or Create an account to join the conversation.
- andypugh
- Away
- Moderator
Less
More
- Posts: 23159
- Thank you received: 4856
04 Feb 2023 12:18 #263667
by andypugh
Replied by andypugh on topic Fusion 360 post processing with the post processor from the sticky thread
Did you sort this out?
Please Log in or Create an account to join the conversation.
- phillc54
- Offline
- Platinum Member
Less
More
- Posts: 5702
- Thank you received: 2084
05 Feb 2023 03:37 #263735
by phillc54
Replied by phillc54 on topic Fusion 360 post processing with the post processor from the sticky thread
The PP usually needs to select a material although it is not mandatory, that can be achieved either by a M190 as below or by using "magic comments" in the gcode file to create a temporary material.the P2 denotes material number 2
The magic comments are handled slightly differently depending on whether you are using PlasmaC or QtPlasmaC.
You can also manually select the material and not have any material handling in the gcode.
F#<_hal[plasmac.cut-feed-rate]> will set the feedrate to the currently selected material, regardless of whether that material is selected from gcode or manually.
All Z axis motion is handled by PlasmaC/QtPlasmaC, so you don't require any in the gcode file.
M190 P2
M66 P3 L3 Q1
The magic comments are handled slightly differently depending on whether you are using PlasmaC or QtPlasmaC.
You can also manually select the material and not have any material handling in the gcode.
F#<_hal[plasmac.cut-feed-rate]> will set the feedrate to the currently selected material, regardless of whether that material is selected from gcode or manually.
All Z axis motion is handled by PlasmaC/QtPlasmaC, so you don't require any in the gcode file.
Please Log in or Create an account to join the conversation.
- Deveraux
- Offline
- Junior Member
Less
More
- Posts: 38
- Thank you received: 8
09 Feb 2023 08:46 - 09 Feb 2023 16:54 #264115
by Deveraux
Replied by Deveraux on topic Fusion 360 post processing with the post processor from the sticky thread
So i did sort it out.
As phillc stated the feedrate will be handled via plasmac using plasmac and the Fusion PP on the Sticky thread.
I did modify the postprocessor as i did not want the material to be chosen via Gcode since i want to have the same file and chose the material in plasmac. I did not want to have to delete the M190 P# command everytime i postprocess something.
Second thing i modified in the PP was the Centerpunch Feature as the M3 command used by the PP does not work for my machine (Linuxcnc 2.8.4 plasmac + Mesa7i96s with a Cebora Plasma Prof 52) i changed the M3 command so it uses the Spindle rotate clockwise command instead of counterclockwise and now the centerpunch Feature is working again.(Using the original PP from sticky my machine does the centerpunch movements but like 5cm in the air the z axis does not move down, probe or fire the Torch).
Last thing which was very important is to turn of the merge circles option (either in Post Dialog or in the PP itself) since i got arc radius differs from start do end errors with any file.
I tried setting the Tolerances in the INI file <---- did not work.
Changing from incremental g91.1 to absolute coordinates did not work either.
Also tried the smoothing in Fusion, almost every tolerance setting in Fusion and Cam tolerance in the PP Dialog which did not work either.
until i turned off the merge circles option and it worked.
I dont know if i am allowed to share the PP here for other People since docwelch created it but if its allowed i can post it if anyone has the same problems as i did.
Also sorry for the late reply i did some grassroots error searching for a few days only changing 1 setting at a time and looking for a difference in behaviour to fix the Arc radius error which took days and most of my freetime to finally find a solution ^^.
As phillc stated the feedrate will be handled via plasmac using plasmac and the Fusion PP on the Sticky thread.
I did modify the postprocessor as i did not want the material to be chosen via Gcode since i want to have the same file and chose the material in plasmac. I did not want to have to delete the M190 P# command everytime i postprocess something.
Second thing i modified in the PP was the Centerpunch Feature as the M3 command used by the PP does not work for my machine (Linuxcnc 2.8.4 plasmac + Mesa7i96s with a Cebora Plasma Prof 52) i changed the M3 command so it uses the Spindle rotate clockwise command instead of counterclockwise and now the centerpunch Feature is working again.(Using the original PP from sticky my machine does the centerpunch movements but like 5cm in the air the z axis does not move down, probe or fire the Torch).
Last thing which was very important is to turn of the merge circles option (either in Post Dialog or in the PP itself) since i got arc radius differs from start do end errors with any file.
I tried setting the Tolerances in the INI file <---- did not work.
Changing from incremental g91.1 to absolute coordinates did not work either.
Also tried the smoothing in Fusion, almost every tolerance setting in Fusion and Cam tolerance in the PP Dialog which did not work either.
until i turned off the merge circles option and it worked.
I dont know if i am allowed to share the PP here for other People since docwelch created it but if its allowed i can post it if anyone has the same problems as i did.
Also sorry for the late reply i did some grassroots error searching for a few days only changing 1 setting at a time and looking for a difference in behaviour to fix the Arc radius error which took days and most of my freetime to finally find a solution ^^.
Last edit: 09 Feb 2023 16:54 by Deveraux.
The following user(s) said Thank You: paulsao
Please Log in or Create an account to join the conversation.
- Deveraux
- Offline
- Junior Member
Less
More
- Posts: 38
- Thank you received: 8
09 Feb 2023 17:07 - 09 Feb 2023 17:14 #264153
by Deveraux
Replied by Deveraux on topic Fusion 360 post processing with the post processor from the sticky thread
In case anyone is interested which changes i did to the PP here we go:
In the .cps file:
Line 27: tolerance = spatial(0.002, MM);
changed to: tolerance = spatial(0.001, MM);
Line 50: MergeCircles: true --->>> MergeCircles: false
Line 344: writeBlock(mFormat.format(190), pFormat.format(tool.number));
(deleted so the Gcode does not specify the Material anymore)
Line 525: writeBlock(mFormat.format(3), $Format.format(2), sFormat.format(1)); //start the torch
changed to: writeBlock(mFormat.format(3), $Format.format(0), sFormat.format(1)); //start the torch
(the above corresponds to the M3 $2 S1 command which spins the spindle counterclockwise
which did not work for my machine it did centerpunch however using the M3 $0 S1 command so i changed the 2 to 0 and everything worked fine)
If anyone has better ideas or suggestions feel free to share, changing these things in the PP finally got my machine working, cutting, and centerpunching.
I have just finished my first CNC machine so my solutions might not be the most optimal or even good but this is what got my machine working ^^
Any improvements are always welcome
regards
In the .cps file:
Line 27: tolerance = spatial(0.002, MM);
changed to: tolerance = spatial(0.001, MM);
Line 50: MergeCircles: true --->>> MergeCircles: false
Line 344: writeBlock(mFormat.format(190), pFormat.format(tool.number));
(deleted so the Gcode does not specify the Material anymore)
Line 525: writeBlock(mFormat.format(3), $Format.format(2), sFormat.format(1)); //start the torch
changed to: writeBlock(mFormat.format(3), $Format.format(0), sFormat.format(1)); //start the torch
(the above corresponds to the M3 $2 S1 command which spins the spindle counterclockwise
which did not work for my machine it did centerpunch however using the M3 $0 S1 command so i changed the 2 to 0 and everything worked fine)
If anyone has better ideas or suggestions feel free to share, changing these things in the PP finally got my machine working, cutting, and centerpunching.
I have just finished my first CNC machine so my solutions might not be the most optimal or even good but this is what got my machine working ^^
Any improvements are always welcome
regards
Last edit: 09 Feb 2023 17:14 by Deveraux.
The following user(s) said Thank You: phillc54, paulsao
Please Log in or Create an account to join the conversation.
- paulsao
- Offline
- Elite Member
Less
More
- Posts: 233
- Thank you received: 22
21 Feb 2023 19:39 #264978
by paulsao
Replied by paulsao on topic Fusion 360 post processing with the post processor from the sticky thread
I'm also a fusion 360 user for a year now, and the merging circles thing was the biggest issue resolved since the radius bug was generated. I want to know if they have the trial or paid version to compare a cerntepunch code since I have problems and I have to fix it by editing the code and I want it to be automatic on the pp
Please Log in or Create an account to join the conversation.
Moderators: snowgoer540
Time to create page: 0.154 seconds