Reach41

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • in reply to: Arc Specification Errors and Decimal Accuracy #11744
    Reach41
    Member

    I am working in inches. I made one change: var xyzFormat = createFormat({decimals:(unit == MM ? 3 : 4) , I changed to MM ? 4 : 5. That fixed the problem I was having with generating a single hole out of three. All three were on the same y line, the only variance was in the x position.

    in reply to: TinyG not reading arc commands correctly? #11742
    Reach41
    Member

    My first comment in the forum is to thank you. I have everything all set up, and have been making parts on a Sherline mill converted to CNC for about a month. I use Tinyg, Fusion 360 and Chilipeppr. Every once in awhile there have been difficulties with arcs. I’m currently making 2×8 Legos out of solid brass. On the bottom of them there are three blind holes of .188 diameter, and a pocket with a lot of curves that surrounds them. The pocket works fine, and two of the three holes are cut properly, but the third hole comes out decidedly unround, and the controller kicks out an error stating that a G2 parameter is illegally set. There are three arcs of 120 degrees that machine out the circumference of each hole, and all three G2 codes for the arcs kick up the same error. The other two holes, which are the same size and depth, differing only where the fall along the X axis, work just fine. I’ve run the gcode through two different visualizers, one being Chilipeppr, and everything looks normal, so it’s not Fusion 360 or the Tinyg post processor. I’ve read a couple of times here and there about switching to metric, which I’m about to try, but I hadn’t seen much about avoiding the canned arc cycles in Tinyg with directly coded line segments. Clearly, if all else fails, that will work.

Viewing 2 posts - 1 through 2 (of 2 total)