-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Where to change idle timeout value #29
Comments
It should only be the robot controller that automatically closes active EGM communication channels, for example if:
I haven't really used EGM motions for extended time periods, so I haven't noticed any upper limit for continuously running EGM. I usually start EGM, do my motions (for a few minutes maximum) and then stop EGM until I need it again. This is mainly because it is better for the robot to not have EGM active all the time. Anyway, I just tried out some longer running scenarios with RobotStudio simulations, and it appears there is an upper limit of about 15 minutes as you have noticed. I can't find anything about this in the manual, so I suggest you to ask about this in the official ABB Robotics User Forum (if you haven't already done so). |
I will close this issue, because I think it is due to internal workings of Please feel free to keep posting comments. |
An update to my post. The trick is to change line 281 |
I followed #16, and understand both the EGM convergence timeout or idle timeout will cause the EGM to stop. Our task requires the EGM to keep opening for at least 30 minutes. The EGM convergence timeout DEFAULT_CONDITION_TIME has been set to 1800s. The problem is the EGM will stop and jump back to idle after only 15 mins every time (we use StateMachine Add-in). When you talk about the idle timeout, is this based on the driver side or the Add-in side? and where I can modify that value?
Thanks
The text was updated successfully, but these errors were encountered: