Data buffering issue on 3D cut?

Home Forums TinyG TinyG Support Data buffering issue on 3D cut?

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #12115
    kevinmcnally
    Participant

    Hello!

    My tinyG controller works great for everything from 2D cuts to much more complex 3D cuts. However, in a cut I am presently trying to make I’m using an operation in fusion 360 called a 3D pencil. It’s relatively simple and is calculated to only take 16 seconds but is executed very slowly, taking around a minute for a 20 millimeter shallow cut in wood. I posted about this problem on the fusion 360 forum and they came up with a great work around but also mentioned there may be a data buffering issue since there is no reason for the original pencil cut to be slower than 16 seconds. A link to the post and solution can be found here:
    href=”https://forums.autodesk.com/t5/fusion-360-manufacture/3d-pencil-operation-painfully-slow-how-do-i-speed-this-up/td-p/10849995″>

    I’m using an almost brand new Sony vaio just in case that’s relevant.
    Are there any tips to dealing with this kind of speed issue?

    Best regards,

    Kevin

    #12116
    cmcgrath5035
    Moderator

    Note: I am unable to open the URL above, it returns an “Invalid Parameters Specified” message.

    Do you have a CAM system (Chilipeppr, CNC.js, etc) delivering your Gcode?
    If not, what flow control options are you using?

    Any Modern computer hardware (as of 10 years ago) should be able to keep the planning buffer full, I would think.

    #12117
    kevinmcnally
    Participant

    Thanks for taking a look at this.
    Perhaps this link will work?
    https://forums.autodesk.com/t5/fusion-360-manufacture/3d-pencil-operation-painfully-slow-how-do-i-speed-this-up/td-p/10849995

    I use chilipeppr.

    Kevin

    #12118
    cmcgrath5035
    Moderator

    Nope, maybe I would need to be logged in to that forum?

    Chilipeppr uses the information on tinyG buffer fill to manage flow..

    I am making the assumption the 2D motion is ‘snappy’ , i.e. not slowed.
    Are you using arcs to define the cut, or very short segments (linear interpolation)? Are you seeing any error messages in the console?

    There are of course a zillion parameters to ask about. Do normal 2D jobs run ‘snappy’?

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