Fusion 360 Bore issue

Home › Forums › TinyG › TinyG Support › Fusion 360 Bore issue

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • May 7, 2017 at 9:32 pm #10361
    CloudLabs
    Member

    Unsure if this is a tinyg question or for ChiliPeppr, but here it is. Sending using ChiliPeppr.

    I’m attempting to bore a 4.1mm hole with a 3.175mm (0.125in) end mill and something is amiss. The bit is plunging into the stock instead of doing a helical bore. Running the toolpath though CAMotics shows a correct helical pattern.

    I’m using the tinyg post processor found here: http://cam.autodesk.com/posts/?p=tinyg

    This is the output toolpath: https://www.dropbox.com/s/to9qufozn285ff9/Y%20Axis%20Plate%20TP%201.nc?dl=0

    May 7, 2017 at 10:20 pm #10362
    cmcgrath5035
    Moderator

    Your job is likely hitting a bug/Gcode specification issue in tinyG.
    I assume you are running $fv=440.20.

    MM mode (G21) is sometimes a solution but you are already using G21.

    Next best suggestion is to regenerate your job with no arcs, which is reported to be possible with correct backend options.
    Unfortunately, no experience with F360 here, Google search might help.

    May 9, 2017 at 8:31 pm #10367
    CloudLabs
    Member

    Hi cmcgrath5035,

    Thanks for your response. After poking around myself at the post processor and ultimately getting the toolpath to run, I found this:

    https://github.com/synthetos/TinyG/issues/181

    allowHelicalMoves = false

    Making the above change created the helix moves as lines instead of arcs. Unfortunately the few jobs I test ran afterwards the board could not keep up with all the moves and started stuttering significantly. I may try moving the SPJS to the local machine using ChiliPeppr.

    May 9, 2017 at 9:41 pm #10369
    cmcgrath5035
    Moderator

    I am not quite sure what you mean by

    board could not keep up with all the moves and started stuttering significantly. I may try moving the SPJS to the local machine

    For sure, SPJS is more efficient at keeping the tinyG planning buffer full, which will reduce buffer starvation and maintain fill as much as possible.

    Good Luck

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