04-28-2020, 01:13 PM
Calling programs given their name is not supported by most drivers.
Instead, you can work around this limitation by calling a program ID. So if you trigger a program such as Program(4), the program ID 4 will be executed. An example is available here:
//m.sinclairbody.com/forum/Thread-online-p...81#pid5081
Therefore, RoboDK drivers automatically receive and trigger a program "ID" on the robot side (may need to be implemented on the robot controller).
Instead, you can work around this limitation by calling a program ID. So if you trigger a program such as Program(4), the program ID 4 will be executed. An example is available here:
//m.sinclairbody.com/forum/Thread-online-p...81#pid5081
Therefore, RoboDK drivers automatically receive and trigger a program "ID" on the robot side (may need to be implemented on the robot controller).