I've been away from G-coding for a while, but I've run into a problem with Vectric creating G codes using G2 for archs instead of G02. How do I state imperial units with the code "G20" ? It seems as though the controller is interpreting this as an arch "G2" followed by "0" which is just non-sense. The same would apply for G17 (use XY plane). It seems like the controller is reading "G1" (straight line) followed by "7"...again non-sense. Please help.
Reviewed There are no instances of "G2'0'.." or "G2 0" (other than the correct G20 in the header) in this file though In the file G17 is continuous and won't be interpreted as you assume above, it would be seen as "G17" G2 is valid
I tried using that post processor and it converted all arcs to G1 line segments. Is that what you would expect? And I guess my original question is still open about how it understands a G20 code as something other than G2 0?
Not true: It has Arc support OpenBuilds-Vectric-Postprocessor/OpenBuilds_inch.pp at master · OpenBuilds/OpenBuilds-Vectric-Postprocessor We do make use of Min_Arc_radius OpenBuilds-Vectric-Postprocessor/OpenBuilds_inch.pp at master · OpenBuilds/OpenBuilds-Vectric-Postprocessor to prevent errors with small circles but that only applies to smaller circles G20 = one command G2 [space] something else = two commands or one command and a verb. There is no space in G20 it won't get interpreted as anything else Lets get down to it though - lets drop the assumptions and tell us whats actually happening, seems the wrong tree is getting barked up
As far as what's really going on, I used to use one of these LEAD 1010's with all this same software at a maker's space. I've since bought my own and I'm trying to get everything setup to match what I was accustomed too. Last night I ran code from the other post processor, which blew through 150 lines in about 2 seconds, then smashed my bit straight down into the work piece. I'll try using the post processor you suggested tonight and if there's any further issues I'll let you know.
Peter, thank you for your help yesterday. Once I switched to the open builds post processor everything worked fine. I also found a previous post you made to someone else about a loose wire causing a stepper motor to operate in the wrong direction sporatically, and that led me to a loose wire on my motor as well. I'm all set now.
