Currently the API is getting the THCenabled signals with 50Hz (20msec),
but as said the update on the screen and LEDs is done in a 60msec loop, I did not think this is required with so high latency.
I don't think we can do much better than 20msec, I mean we probably could make it faster with the ethernet controllers, but not with the USB ones.
Also there may be some small variations in the update frequency, because you know Windows is not realtime and this 20msec time interval is so low.
And then your plugin has to send the data down to your THC controller which again takes some time.
I think it would be better to go the way which Keith adviced is to create a configurable physical output on the motion controller for the THC enable signal
and then connect that directly to your THC controller. This way the data can be there with no delays, realtime-like.
What do you think?
Do you have a THC enabled signal input on your THC?
All industrial CNC has this future inside CNC kernel.
Yes, the UCCNC also handles the THC internally, enabling and disabling the THC in syncron with the motion buffer,
but to output this information to the external world is the not so easy task.