In my application I will be using the SyncInterruptWait. The API docs say to disable the service thread. What API capabilities are lost other than path motion when disabling the service thread?
Hi @markj,
We’re going to correct the documentation on that one. It doesn’t need to be disabled and it shouldn’t affect you.
Is there anything you are concerned about or something I can help with?
Just a new user wanting to understand the impact of disabling the service thread is all. Just to clarify, I do not need to disable the service thread to use SyncInterruptWait?
Correct!
Update for Context: This answer applies to Linux uses not Intime users. Disabling the service thread for Intime users is still something you’ll want to do.
Excellent. Just one more question on the service thread. I guess I could verify this under the debugger but does the service thread run in my process or the RMP process?
Hi @markj,
The service thread will run in your process.
1 Like
@markj — a correction to the INtime half of the answer above.
The Linux guidance is unchanged: you don’t need to disable the service thread to
use SyncInterruptWait().
The INtime caveat we added has been relaxed in RMP 11.1.0, which fixes
SyncInterrupt and other interrupts being usable at the same time on
Windows/INtime. If you’re on INtime and were disabling the service thread solely
because of that interaction, re-test on 11.1.0 before carrying the workaround
forward.
1 Like