Context: most of these questions are in relation to being able to duplicate functionality that we currently have in the MLC firmware such as running a PLC task that is tied to the Motion Update or Sercos cycle, or even in running a cyclic task at a set interval. The questions revolve around dedicated processor power/time to execute code or described another way: real-time.
I have heard conflicting comments about Blockly and Python. Do they run in the real-time environment?
What languages are real-time and what are not? One ppt seems to show that only C/C++ is possible.
What to expect from the real-time API library, how will it interact with the rest of the control and programming that is non-real-time?
What does "8 million data point access per second" mean as described in the presentations? This seems slow in high axis count applications. Can this be described differently to explain performance of the system? What is considered an "access" and would not the speed of the access depend on what is accessed?
The Blockly demo is sending motion commands to a drive. Is this access similar to how the Open Core Interface for Controls works from outside the MLC? Or is there real-time access?
Solved! Go to Solution.