440.16 Firmware still having arc issues

Home › Forums › TinyG › TinyG Support › 440.16 Firmware still having arc issues

Viewing 8 posts - 31 through 38 (of 38 total)
1 2 3
  • Author
    Posts
  • August 10, 2015 at 6:30 am #8198
    alden
    Member

    I was able to download the file. Taking a look.

    August 10, 2015 at 8:18 am #8199
    alden
    Member

    I ran the file and did not find a runaway, but I’m not 100% sure of that. There were a few challenges to overcome.

    I do not have a table with an X dimension of 24″. I’m testing on a Shapeoko2 with an effective X dimension of 11.5 inches (after you take the size of the X carriage into account). So I turned the X motor power way down, disabled limit switches, and let it crash in X. This may mask a runaway in X if the runaway did, in fact, return in short order.

    I did not find a runaway move in 3 runs (Coolterm) against different builds (master, edge (444.16), and my current experimental branch). I might have missed a move error due to the X dimension problem as it could have happened when X was crashed.

    I run numbered files, so I numbered yours if you are interested:
    https://www.dropbox.com/s/sbht5ybiwcqbvwh/wwerrorGcode-NUMBERED.nc?dl=0

    Would you mind dry running the file again, and perhaps generate a file with 10″ wingspan I can run? If it fails again can you record the approximate line number and some description of the failure. It may be a Chilipeppr line number but that’s close enough.

    Sorry for your issues.

    August 10, 2015 at 12:30 pm #8200
    wephotography
    Member

    I just added a screenshot of the failure area of the code. I ran the file four times, twice in 440.18 and twice in 442.04 with the exact result. I have noticed in the past that if i change the dimensions of the file or change bit size it can alter or remove the outcome of errors. Ive cut full run test pieces with no issues, changed my settings to a smaller bit for accuracy and resulted in a runaway or a circle cut. Ive also added the full original code file as i was running on my machine. That one is WWlogogcode. Would I be any more stable with an arduino/grbl set up?

    August 10, 2015 at 12:34 pm #8201
    wephotography
    Member

    Looks like right around 6200 in chillipeppr numbering

    August 10, 2015 at 1:21 pm #8202
    alden
    Member

    What happens to that line? Does it continue or return?

    As for more stable with another system, I don’t know. The problems seem to be localized to PartKam files, which generate some pretty crazy moves. Perhaps you might have better luck with the follow on – Makercam.

    I am committed to finding out the issue, however.

    August 10, 2015 at 2:11 pm #8204
    wephotography
    Member

    I use makercam for everything as theres not many options for mac users in the cam world. Im not sure ive had to force stop the machine as it runs until it hits the machines Y rails. All the runaway cuts ive had just keep going until it runs out of machine room so im assuming none of them return like the circles do.

    • This reply was modified 9 years, 3 months ago by wephotography.
    August 11, 2015 at 6:22 am #8211
    alden
    Member

    Thanks for your help in locating the errant line. The fix is in the tinyg github and updater as master-candidate-440.19. Please let me know how this works for you. It passed all the tests for the files you gave me.

    August 11, 2015 at 11:49 pm #8226
    wephotography
    Member

    All files running perfectly with 440.19. G2 & G3 arcs. Even ran a file that was 99 percent arc commands and all good. Thanks again for the help.

  • Author
    Posts
Viewing 8 posts - 31 through 38 (of 38 total)
1 2 3
  • You must be logged in to reply to this topic.