We sometimes observe trajectories being stopped (softly) in the middle of execution. We have not found any error messages or other reasons for this and have a hard time debugging. We then re-send a new and shortened trajectory containing the remaining way points and it succeeds.
We send trajectories that can be quite sparse (eg 90° motion) at times and dense when simulating a cartesian segment. Could that be an issue, should we interpolate more?
We sometimes observe trajectories being stopped (softly) in the middle of execution. We have not found any error messages or other reasons for this and have a hard time debugging. We then re-send a new and shortened trajectory containing the remaining way points and it succeeds.
We send trajectories that can be quite sparse (eg 90° motion) at times and dense when simulating a cartesian segment. Could that be an issue, should we interpolate more?
Where does the
printf
in MotoPlus go to?Any ideas and hints what to look out for?