-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bring in Header Info as Part of the Post Process #4
Comments
Also I have to say this is AWESOME!! Regardless of my suggestion, having this has been so cool! You have had to put so much work into this repo! Great job and thank you for making it available to people like me who want to breakout of the Luban software and use Fusion 360 for my CNC stuff. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I noticed that the .cnc files given by Fusion 360 using the Post Process there are a few things missing that are in the .cnc file provided by the Luban Software when it creates a .cnc file.
While it is not necessarily a problem it does open up an opportunity for the Fusion 360 Post Process to get closer to being similar to how the makers of Snapmaker have designed G-code files for their CNC machine. This is particularly helpful when still using the Luban software to preview G-code. Also using the software to send it to the Machine.
Describe the solution you'd like
The solutions would be to take the exported .cnc files provided by Luban Software and working the format it into the Fusion 360 Post Process. Luban provides a set of "header" comments (example below), could this data be worked into the Fusion 360 Post Process? For example what Luban calls "Work Speed" Fusion 360 calls "Cutting Feedrate".
The text was updated successfully, but these errors were encountered: