Sheetcam Post Processor and Material Feedrate Warning
- little_sparky
- Offline
- Premium Member
Less
More
- Posts: 137
- Thank you received: 16
05 Dec 2020 02:46 #191101
by little_sparky
Sheetcam Post Processor and Material Feedrate Warning was created by little_sparky
Hey Guys,
I just updated PlasmaC to version v0.186 I believe it is and I got this material warning when loading a G-code file. When I ran the program it used the feedrate set within Sheetcam, not the material parameters in plasmaC.
I have been using Rod's 'SpaceShipPlasma -rev3' post processor with great effect for almost a year now, do I need to make a slight adjustment to this, or am I doing something else wrong?
Thanks
I just updated PlasmaC to version v0.186 I believe it is and I got this material warning when loading a G-code file. When I ran the program it used the feedrate set within Sheetcam, not the material parameters in plasmaC.
I have been using Rod's 'SpaceShipPlasma -rev3' post processor with great effect for almost a year now, do I need to make a slight adjustment to this, or am I doing something else wrong?
Thanks
Attachments:
Please Log in or Create an account to join the conversation.
- snowgoer540
- Offline
- Moderator
Less
More
- Posts: 2393
- Thank you received: 782
05 Dec 2020 02:51 #191102
by snowgoer540
Replied by snowgoer540 on topic Sheetcam Post Processor and Material Feedrate Warning
I’d recommend the post processor in the sticky of this Topic.
The error message does say the exact problem which is that your fees rate is being set by the gcode instead of using the syntax that pulls feed rate from your material file, and in this case they don’t match.
Without seeing your gcode, of course
The error message does say the exact problem which is that your fees rate is being set by the gcode instead of using the syntax that pulls feed rate from your material file, and in this case they don’t match.
Without seeing your gcode, of course
The following user(s) said Thank You: little_sparky
Please Log in or Create an account to join the conversation.
- little_sparky
- Offline
- Premium Member
Less
More
- Posts: 137
- Thank you received: 16
05 Dec 2020 05:06 #191107
by little_sparky
Replied by little_sparky on topic Sheetcam Post Processor and Material Feedrate Warning
That fixed it, thank you!
The following user(s) said Thank You: snowgoer540
Please Log in or Create an account to join the conversation.
- MaikTheBike
- Offline
- New Member
Less
More
- Posts: 14
- Thank you received: 1
13 Nov 2021 21:24 #226369
by MaikTheBike
Replied by MaikTheBike on topic Sheetcam Post Processor and Material Feedrate Warning
Hi,
I get the same message when using the Fusion 360 postprocessor.
If I understand it correctly the cutting speed in the G-Code will be ignored and instead the material #0 speed (saved in PlasmaC in the RUN-tab) is used.
But how can I run the program with the speed saved in material #1 or material #2 or any other material ?
thanks...
I get the same message when using the Fusion 360 postprocessor.
If I understand it correctly the cutting speed in the G-Code will be ignored and instead the material #0 speed (saved in PlasmaC in the RUN-tab) is used.
But how can I run the program with the speed saved in material #1 or material #2 or any other material ?
thanks...
Please Log in or Create an account to join the conversation.
- phillc54
- Offline
- Platinum Member
Less
More
- Posts: 5698
- Thank you received: 2081
13 Nov 2021 22:13 #226373
by phillc54
Replied by phillc54 on topic Sheetcam Post Processor and Material Feedrate Warning
Follow the G-Code here:
linuxcnc.org/docs/devel/html/plasma/qtpl...ic_material_handling
I have a change in the wings where this won't be an issue in the future but I haven't got around to completing it.
linuxcnc.org/docs/devel/html/plasma/qtpl...ic_material_handling
I have a change in the wings where this won't be an issue in the future but I haven't got around to completing it.
The following user(s) said Thank You: rodw
Please Log in or Create an account to join the conversation.
Moderators: snowgoer540
Time to create page: 0.116 seconds