Arc Specification Errors

Home › Forums › TinyG › TinyG Support › Arc Specification Errors

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • May 20, 2016 at 8:37 pm #9686
    LonV
    Member

    Hey guys, I’m using Goko for my Tinyg (because I don’t really like a web based tool like Chilipeppr :D) and it works pretty well, but I get to a certain point in my cuts and I start getting “arc specification errors” reported by the Tinyg and Goko alerts me and then will let me resume, but I would have to click that 1000 times to get the file to finish. The same Gcode through chilipeppr doesn’t result in any such behavior.

    Is there a way to suppress these errors? Or other ideas?

    Thanks,

    Lon

    May 22, 2016 at 6:32 am #9687
    cmcgrath5035
    Moderator

    I have never heard of Goko, so have no idea what it is attempting to do.
    The errors are likely tinyG applying Gcode arc specification rules that the Gcode generator has ignored.

    Is your Gcode in inch mode or mm mode.
    If inch, regenerate in mm.
    Sometimes the small errors in converting inch back to mm is enough to trigger these errors.
    TinyG does all it’s work in mm, converting from inch when it has to.
    Running mm Gcode bypasses that conversion overhead.

    Have you tried running the Gcode with CoolTerm or Chilipeppr?
    Does it run OK there?
    Neither of those Gcode streaming tools act on error messages returning from tinyG.

    May 23, 2016 at 9:17 pm #9698
    LonV
    Member

    Thanks for responding. Everything I do is in mm, so that’s not likely it. I’m using Fusion360 with the TinyG post-processor to generate Gcode. It looks like Goko just doesn’t silently ignore these messages back from TinyG.

    I believe I did run it with Chillipeppr and it ran “fine”. In my case, Chilipeppr doesn’t run very well with large Gcode files…which is why I was exploring other options.

    Thanks for the info, I’ll figure something out. 😀

    -Lon

    May 23, 2016 at 9:44 pm #9699
    cmcgrath5035
    Moderator

    CP turned on a similar monitor the tinyG error stream last summer – it was a also a train wreck.

    January 17, 2017 at 7:00 am #10179
    psyko
    Member

    Hi LonV

    Sorry, I just found your topic (yeah almost 7 month later…)
    I’m the developper behind Goko. Did you find what was causing your error ?
    In this case Goko simply reports the error from TinyG to the user.
    Most likely it’s because the start and end point of the arc command are not equally spaced from the center point….

    A feature to specify some error to ignore is somehow on my todo list, but I’m not sure this one should be ignored.
    Do you have any GCode to reproduce it ?
    Can you please use github or forum of Goko for this topic ?
    discuss.goko.fr
    https://github.com/cncgoko/Goko

    Thanks a lot, and again, sorry for the late answer…

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.