After the initial failure of the VIRTINDEX, my other trials were run right from the Galil's memory. The context of my trials was only to discover the best way to create and detect any kind of 'event' that could trigger the threading cycle reliably.
What we don't know is how the Galil is eating up clock cycles as all these commands are being executed. What baffled me is that the time duration could vary as much as 30% when rerunning the same logic in a loop. Maybe the Galil has its own 'overhead' in the form of built in routines that may or may not run consecutively with the logic of a given loop.
__________________
First you get good, then you get fast. Then grouchiness sets in.
(Note: The opinions expressed in this post are my own and are not necessarily those of CNCzone and its management) |