Robodk's cycle time estimations in offline simulations are exactly the same as if I calculate the time of tcp with basic motion equations. I mean this is fine for offline simulations, but is there any way to be more accurate? we have some minor delays for the signal in the start and at the end of the motion, or due to the inertia, or when we go beyond manufacturer's proposed inputs fot velocity and acceleration.