Issues

Home › Forums › TinyG › TinyG Support › Issues

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • November 29, 2015 at 9:30 am #9016
    leversole
    Member

    Just got my OX replica going…using CAMBAM and ChiliPeppr with the latest V8 (purchased about two weeks ago) TinyG…
    On two cut jobs the router did something unexpected. On one file with two depth cuts, it “forgot” to do a couple of the cuts, and on another file, it did a random move diagonaly and rapid across the work without raising the bit which ruined it. I have run the code in several simulators, no issues. Thinking maybe something in the file is not supported? Can chiliperr send code “too fast” for the TinyG to keep up with?

    I am sure the first thing you will ask is to post my code, whcih I will try to tfigure out and do…

    Thanks

    November 29, 2015 at 9:56 am #9017
    leversole
    Member

    Here is the GCode for one of the issues…

    EMF_Logo

    November 29, 2015 at 10:48 am #9018
    leversole
    Member

    and a picture of the chilipeppr and actual…

    EMF2
    EMF2

    November 29, 2015 at 12:55 pm #9019
    leversole
    Member

    I must have some settings wrong, picture shows what should be a 5 inch circle…I have attached my TinyG settings, can someone take a look please?

    Thanks
    TinyG Settings

    5 inch circle

    November 29, 2015 at 4:43 pm #9023
    leversole
    Member

    I solved the riddle of the circles not being round! After much learning about arcs, looking at all of my TinyG settings, and other head/scratching/hair pulling, it dawned on me that my X axis might be two tight, back off some and viola, everything (at least with the circles) is beautiful…I dont think this explains my first post, but after I make some more test cuts, I will go back and recreate the file for my forst issue.

    November 29, 2015 at 10:55 pm #9025
    cmcgrath5035
    Moderator

    On two cut jobs the router did something unexpected. On one file with two depth cuts, it “forgot” to do a couple of the cuts, and on another file, it did a random move diagonaly and rapid across the work without raising the bit which ruined it. I have run the code in several simulators, no issues. Thinking maybe something in the file is not supported? Can chiliperr send code “too fast” for the TinyG to keep up with?

    I assume you are focused on the “forgot” to do a couple cuts and the ranom move diagonally… comments.

    Both could be symptoms of issues with tinyG’s interpretation of the Gcode into machine movement directions, particularly relating to arc commands (G2 and G3 Gcode commands).
    Unfortunately, simulators do help your visualize Gcode directives, but there are many ways for simulators to make interpretations of Gcode that are not or cannot be implemented by tinyG.

    Suggestions: Review this:

    to get an idea of some of the Gcode commands that are not implemented or fully supported.

    Also, please confirm that you are running the latest FW, 440.20.

    While likely not in play here, have you run enough basic Gcode to verify the dimensional accuracy of your machine’s settings. e.g. when commanded to trace a 6.5″ circle, do you get a 6.5″ circle?

    It will take some time to analyze your Gcode. In the meantime, I believe CamBam has an option to use only short linear segments, no arcs. You could try that to see if it performs more accurately for you.

    To your final question above relative to ChiliPepprb overrunning tinyG; that is doubtful. ChiliPeppr, and SPJS specifically, are designed around a buffer fill algorithm and strategy that aims to prevent overflow while keeping tinyG “fully engaged”.

    November 29, 2015 at 10:55 pm #9026
    cmcgrath5035
    Moderator

    On two cut jobs the router did something unexpected. On one file with two depth cuts, it “forgot” to do a couple of the cuts, and on another file, it did a random move diagonaly and rapid across the work without raising the bit which ruined it. I have run the code in several simulators, no issues. Thinking maybe something in the file is not supported? Can chiliperr send code “too fast” for the TinyG to keep up with?

    I assume you are focused on the “forgot” to do a couple cuts and the ranom move diagonally… comments.

    Both could be symptoms of issues with tinyG’s interpretation of the Gcode into machine movement directions, particularly relating to arc commands (G2 and G3 Gcode commands).
    Unfortunately, simulators do help your visualize Gcode directives, but there are many ways for simulators to make interpretations of Gcode that are not or cannot be implemented by tinyG.

    Suggestions: Review this:

    to get an idea of some of the Gcode commands that are not implemented or fully supported.

    Also, please confirm that you are running the latest FW, 440.20.

    While likely not in play here, have you run enough basic Gcode to verify the dimensional accuracy of your machine’s settings. e.g. when commanded to trace a 6.5″ circle, do you get a 6.5″ circle?

    It will take some time to analyze your Gcode. In the meantime, I believe CamBam has an option to use only short linear segments, no arcs. You could try that to see if it performs more accurately for you.

    To your final question above relative to ChiliPepprb overrunning tinyG; that is doubtful. ChiliPeppr, and SPJS specifically, are designed around a buffer fill algorithm and strategy that aims to prevent overflow while keeping tinyG “fully engaged”.

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