12-17-2019, 10:23 PM
Your first assumption is correct: the time to trigger an event is different depending on the programming language (and, if you use the C++ plug-in interface it is much faster).
If you create a program using the RoboDK API or the plugin-interface, the result will be the same as if you created it manually using the GUI.
The fastest communication lag is the plug-in interface (by far). In this case you generate a DLL that is loaded by RoboDK and you have access to the low level functions RoboDK as immediate calls. Contrary to the standard RoboDK API, you need to trigger the Update/Render calls from your code. Among other things, the plugin interface allows you to customize the appearance of RoboDK. More information and examples here:
https://github.com/RoboDK/Plug-In-Interface
If you create a program using the RoboDK API or the plugin-interface, the result will be the same as if you created it manually using the GUI.
The fastest communication lag is the plug-in interface (by far). In this case you generate a DLL that is loaded by RoboDK and you have access to the low level functions RoboDK as immediate calls. Contrary to the standard RoboDK API, you need to trigger the Update/Render calls from your code. Among other things, the plugin interface allows you to customize the appearance of RoboDK. More information and examples here:
https://github.com/RoboDK/Plug-In-Interface