Estimating time accurately

Home › Forums › TinyG › TinyG Support › Estimating time accurately

Tagged: , ,

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • May 16, 2017 at 6:53 am #10383
    mrzk
    Member

    Hello
    Based on my understanding of the physics of movement, I need to consider jerk in time calculation to achieve my goal, which is estimating time of gcode accurately. Unfortunately the explanations on this link were too vague for me and I couldn’t find any other useful links to this situation. Can anybody help me with this problem?

    May 16, 2017 at 7:59 am #10385
    cmcgrath5035
    Moderator

    A general comment would be that the execution time of a given Gcode file is a complex combination of a lot of parameters plus , potentially, the performance of the Gcode delivery link. For example, Chilipeppr was initially developed to focus on keeping the motion planner as busy as possible and is buffer fill managed. G code delivered by UGS or CoolTerm might not run as fast.
    Most folks on this forum think in terms of XYZ CNC machines. Are you, or perhaps are you working on a complex motion robot?

    Can you bound your need for time estimation?
    A simple bound might be “How long can I walk away from the machine while the job runs”

    A complex bound might be a system that dynamically generates Gcode to compensate for motion that has just occurred.

    And, by the way, some Gcode might run a little faster on G2core than on tinyG because the compute engine has more horsepower, depending on the complexity of the effective tool path.
    What are you designing around?

    May 17, 2017 at 4:07 am #10387
    mrzk
    Member

    Let me make my question simpler. How long will it take to move from x=0 to x=600 with feed rate of 1500mm/min and jerk of 50000000 mm/min3? (In this case, I don’t care about the transmitting time of gcode and processing it. I only need the time of movement)

    P.S.: I made my own diy 3 axes CNC machine and now I’m working on a customized software for it

    May 17, 2017 at 8:00 am #10388
    cmcgrath5035
    Moderator

    I don’t know how to calculate it.

    You could create a simple Gcode file that makes the move, run it on tinyG with steppes disconnected or with spindle up (in air) and capture the return status stream, which will show the ramp up and ramp down in velocity.

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