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
G3 Counter Clockwise Arcs #500
Comments
that's super weird, I use it all the time for CNC milling, and it works 2014-08-25 20:11 GMT+02:00 Veloce7 notifications@github.com:
Courage et bonne humeur. |
This is what we tried: This exact code will work when a G2 command is entered but not this G3 command. -Mark
|
I just looked at the code and I don't see anything that would cause this Thanks. 2014-08-26 7:46 GMT+02:00 Veloce7 notifications@github.com:
Courage et bonne humeur. |
G0 X0 Y0 works properly. Same g-code with G3 ends on X10 Y10 (last command is ignored). Not sure if this makes sense but it seems there's some inconsistency between G2/G3. |
Yeah this has been reported several times now, but I looked at the code and can't find anything that could cause this. |
Been doing some testing myself and I've found that some G3 commands seem to work. I'm testing with this file and it stopped at line 1165 but if you search the file you'll see that there are other G3 command sent before this line. Maybe this help debug the code. |
@GeorgeIoak there are modal G3 arcs you have in your g-code
and these are not supported by smoothieware - you need either post process such lines so each of them is prefixed with G3 like this:
or fix the output of your CAM processor. It might be a good idea to enable modal G3 codes in smoothie if it doesn't break command parsing. |
Thanks @sorki for looking at that file. I used Autodesk Fusion 360 to generate that file. I think it has an option for post processing but it seems since Smoothie allows other g-codes to be modal that G3 could be "upgraded" to be modal as well? |
G0 and G1 are currently semi-modal, the caveat is there needs to be a preceding space on the X or Y.
|
Is that something that is "supposed" to be done or just a requirement for Smoothie? I'm new to g-code and post processing but it seems odd that the file needs to have a certain format. Coming from PCB design, when you generate gerbers you never have to worry if the file is properly formatted. |
Different controllers provide different features and g-code has to adapt to that. Formatting is also an issue as parsers are implemented differently. Even pcb2gcode/heekscnc won't output g-code which is valid for smoothie. We are trying to fix these so they provide output profile for smoothie but for closed source apps you can only post-process. Always check your g-code prior feeding it to your machine - especially if it's cnc or do a dry run well above machined surface when not sure if it's correct (e.g. when using new CAM software). |
It is a smoothie caveat, added to be able to process code generated by pycam which preceded modal gcode with a space. Smoothie is NOT compliant with most gcode specs. it is hacked to "work well enough" for most gcode generators that people use with smoothie. FWIW a lot of the gcode generated by most 3D slicers is also not gcode compliant, and would be rejected by a compliant gcode parser. |
Another odd behaviour I've found today: using
the machine goes up nicely in helical arc. But
results in Z only movement with weird pauses. |
I see that Fusion360 has quite an extensive list of post processors. They have GRBL, TinyG, Mach3, as well as many of the industrial machines. I believe I had chosen GRBL when I created that test file. The configuration files for each supported machine I believe are written in JS so with a little work I think a custom Smoothie version could be created. Other than having a preceding space for modal G0-G3 can you think of anything else? |
I believe the Fusion 360 team is currently making a Smoothie post-processor. If you look at the Smoothie-support or Smoothie-dev mailing list you'll On Tue, Mar 24, 2015 at 10:16 PM, George Ioakimedes <
Courage et bonne humeur. |
That is related to #500 |
I found this post in the [AutoDesk forums], (http://camforum.autodesk.com/index.php?topic=5032.msg17546#msg17546) and it looks like only 1 line needed to be changed. I'll modify their GRBL configuration file and check the output file against the original I posted. |
I unfortunately couldn't find the original project that created that file but I made a new one and I believe that the new format should work well with Smoothie. Have a look here. |
I am not sure S1000 M3 will do what you expect M3 S1000 may work better. |
OK, that was another easy change. That line now gets output as M3 S1000 Here's a link to the configuration file that others can use with Fusion 360 and/or modify when needed. |
The G2 command works, but G3 does nothing.
The text was updated successfully, but these errors were encountered: