Hi everyone,

I had today a question from a customer on the maximum length / duration allowed for a path recording program using our URCap function.  My first answer was to say that the only limitation was the memory left on the controller to run / record such program.  

I also mentioned that from a programming standpoint,  it's definitely more convenient to work with a set of smaller path recording segment programs than a single long one when comes the time to modify it, since as of now, it's not possible to edit the path recording program. 

@Nicolas_Lauzier @Annick_Mottard  Do you see other limitations?

There is no actual limit to the length or duration of the path you want to record. The only limit would be the available memory to store your program in. Also, if you record a long path, the inconvenience is the time it takes for your program to start running. The longer your path is, the longer it takes before your program actually runs when you click the start button. 

Like you mentioned, @mikebeauchemin, it is easier to work with smaller paths. It is much simpler to correct an error while recording a smaller path.

Hello,

Unfortunately, it's not possible to change the 10 minutes duration it's within the software and not a parameter to be changed.  The reason behind this limit is related to the number of captured data and the capacity of the UR controller memory space while replaying it.  It's also not convenient if you want to modify a portion of the program.  A good practice would be to split the trajectory in multiple paths and that is why we did create the feature:  '' Multi-Point Path''.   Can you share with us the application on which you are trying to use a path than more than 10 minutes?  I would be interested in understanding what you are trying to achieve and to see how we could help with existing features and if there is something we could optimize in our software.